Administrator Manual

v e r s i o n 3.1.0

AT310_AM_E2

experts in radio network planning & optimisation software

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

Forsk Head Office
7 rue des Briquetiers 31700 Blagnac France

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

sales_us@forsk.com +1 312 674 4800 +1 312 674 4847

sales@forsk.com +33 (0) 562 747 210 +33 (0) 562 747 211

enquiries@forsk.com.cn +86 20 8553 8938 +86 20 8553 8285

support_us@forsk.com +1 888 GoAtoll (+1 888 462 8655) 8.00 am to 8.00 pm (EST) Monday - Friday

support@forsk.com +33 (0) 562 747 225 9.00 am to 6.00 pm (CET) Monday - Friday

atollsupport@forsk.com.cn +86 20 8557 0016 9.00 am to 5.30 pm (GMT+8) Monday - Friday

www.forsk.com

Atoll 3.1.0 Administrator Manual

© Forsk 2011

Atoll 3.1.0 Administrator Manual Release AT310_AM_E2 © Copyright 1997 - 2011 by Forsk The software described in this document is provided under a licence agreement. The software may only be used/copied under the terms and conditions of the licence agreement. No part of this document may be copied, reproduced or distributed in any form without prior authorisation from Forsk. The product or brand names mentioned in this document are trademarks or registered trademarks of their respective registering parties. The Atoll Administrator Manual contains administrator-level information and instructions. It is divided into three parts. The first part of the Administrator Manual provides information on installing Atoll and setting up and working with databases in multi-user environments. The second part contains recommendations and information on Atoll configuration and initialisation files. And, the third part describes the database structures of the technology modules.

4

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Table of Contents

Table of Contents

1
1.1 1.2 1.3 1.4 1.5 1.5.1 1.5.2 1.5.3 1.5.4 1.5.5 1.6

Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Supported Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Supported Database Management Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Supported Installation Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Recommended Hardware and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 User Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Database Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Citrix Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Floating Licence Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 File Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Recommended Computer Network Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2
2.1 2.2 2.3 2.4 2.5 2.6 2.7

Installing Atoll and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Installing Atoll Using the Setup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Installing Atoll C++ Development Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Setup Command Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Installing and Uninstalling Add-ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Installing and Uninstalling Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Atoll Command Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Troubleshooting and Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3
3.1 3.2 3.3

Setting Up Distributed Calculation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Setting Up Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Setting Up Atoll to Access the Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Distributed Calculation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4
4.1 4.1.1 4.1.2 4.1.3 4.2 4.2.1 4.2.2

Managing Licences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Working with Floating Licences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 HASP Licence Manager and Device Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 nhsrv.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 nethasp.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Using the Atoll Licence Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Licence Manager Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Updating Licence Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

5
5.1 5.2 5.3 5.3.1 5.3.2 5.4 5.5 5.5.1 5.5.2 5.5.3 5.6 5.7 5.7.1 5.7.2 5.7.3 5.7.4 5.8 5.9 5.9.1

Managing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Atoll Database Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Atoll Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Creating New Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Creating a New Database Using the Atoll Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Creating a New Database Using Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Upgrading Existing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Working With Multi-level Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Creating Project Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Archiving Project Databases to Master Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Refreshing Project Databases from Master Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Setting Database Access Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Managing Data Modifications History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Setting Up Data Modifications History Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Enabling/Disabling Data Modifications History Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Updating After Data Structure Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Purging Old Data Modifications History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Using Oracle With Atoll. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Appendices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Appendix 1: Advanced Customisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

5

Atoll 3.1.0 Administrator Manual Table of Contents

© Forsk 2011

5.9.2

Appendix 2: Setting Up Databases for Co-planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

6
6.1 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.2.5 6.3 6.3.1 6.3.2 6.4 6.4.1 6.4.2 6.4.3 6.4.4

Multi-user Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Setting Up Multi-user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Components of Multi-user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Master Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Master Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Shared Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Shared Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 User Atoll Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Managing User Accounts and Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Defining Database and Interface Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 Creating and Editing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 Appendix 1: Checking Data Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 Appendix 2: Database Regionalisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 Appendix 3: Calculating Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 Appendix 4: Path Loss Matrices From Different Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

7
7.1 7.1.1 7.1.2 7.1.3 7.1.4 7.2 7.3

Coordinate Systems and Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Coordinate Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 Definition of a Coordinate System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 Types of Coordinate Systems in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 Coordinate Systems File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 Creating a Coordinate System in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 BSIC Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

8
8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 8.9.1 8.9.1.1 8.9.2 8.9.2.1 8.9.3 8.9.3.1 8.9.3.2 8.9.3.3 8.9.3.4 8.9.4 8.9.4.1 8.9.5 8.9.6 8.9.7 8.9.8 8.9.9 8.9.10 8.9.11 8.9.12 8.9.13 8.9.14 8.9.15 8.9.15.1 8.9.15.2 8.9.15.3 8.9.15.4 8.9.15.5

Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Digital Terrain Model (DTM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85 Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 Clutter Heights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 Vector Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Population Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Custom Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Geographic Data File Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 BIL Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 HDR Header File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 TIFF Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 TFW Header File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 BMP Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 BMP File Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 BMP Raster Data Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 Raster Data Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 BPW/BMW Header File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 PNG Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 PGW Header File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 DXF Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 SHP Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 MIF Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 TAB Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 ECW Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 Erdas Imagine Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 Planet EV/Vertical Mapper Geographic Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 ArcView Grid Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 Other File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 Generic Raster Header File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 Planet Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 DTM Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 Clutter Class Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 Vector Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 Image Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Text Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

6

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Table of Contents

8.9.15.6

MNU Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

9
9.1 9.1.1 9.1.2 9.2 9.3 9.4 9.5 9.5.1 9.5.2 9.6 9.6.1 9.7 9.7.1 9.7.2 9.7.3 9.8 9.8.1 9.8.2 9.8.3 9.9 9.9.1 9.9.1.1 9.9.1.2 9.9.2 9.9.3 9.9.4

Radio Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
XML Import/Export Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Index.xml File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 XML File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 RF 2D Antenna Pattern Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Import Format of 3D Antenna Pattern Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Microwave 2D Antenna Pattern Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Microwave NSMA Antenna File Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 WG 16.89.003 Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 WG 16.99.050 Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Microwave NSMA Radio File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 WG 21.99.051 Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Path Loss Matrix File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Pathloss.dbf File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Pathloss.dbf File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 LOS File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Path Loss Tuning File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Pathloss.dbf File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Pathloss.dbf File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 PTS File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Interference Matrix File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 CLC Format (One Value per Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 CLC File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 DCT File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 IM0 Format (One Histogram per Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 IM1 Format (One Value per Line, TX Name Repeated). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 IM2 Format (Co- and Adjacent-channel Probabilities) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

10
10.1 10.2 10.3 10.4 10.5 10.6 10.7 10.8 10.9 10.10 10.11 10.12 10.13 10.14 10.14.1 10.14.2

Administration and Usage Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . .129
Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Path Loss Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Calculation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Atoll Administration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Process Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Coverage Prediction Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 CW Measurements and Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Antenna Patterns and Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Traffic Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Atoll API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Performance and Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Appendix: Memory Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Disk Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 RAM Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

11
11.1 11.1.1 11.1.2 11.1.3 11.1.4 11.1.5 11.1.6 11.1.7 11.1.8 11.1.9 11.1.10 11.2 11.2.1 11.2.2 11.2.3 11.2.4

Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141
Contents of User Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Geographic Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Folder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Automatic Neighbour Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Automatic Frequency Planning Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Automatic Scrambling Code Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Automatic PN Offset Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Microwave Radio Links Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Contents of Additional Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Print Setup Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Table Import/Export Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Coverage Prediction Report Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 CW Measurement Import Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

7

Atoll 3.1.0 Administrator Manual Table of Contents

© Forsk 2011

11.2.5 11.3

Drive Test Data Import Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Contents of the Custom Predictions File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

12
12.1 12.1.1 12.1.1.1 12.1.1.2 12.1.1.3 12.1.1.4 12.1.1.5 12.1.1.6 12.1.1.7 12.1.1.8 12.1.1.9 12.1.1.10 12.1.1.11 12.1.1.12 12.1.1.13 12.1.1.14 12.1.1.15 12.1.1.16 12.1.1.17 12.1.1.18 12.1.1.19 12.1.1.20 12.1.1.21 12.1.1.22 12.1.1.23 12.1.1.24 12.1.1.25 12.1.1.26 12.1.1.27 12.1.1.28 12.1.1.29 12.1.1.30 12.1.1.31 12.1.1.32 12.1.1.33 12.1.1.34 12.1.1.35 12.1.1.36 12.1.1.37 12.1.2 12.1.2.1 12.1.2.2 12.1.2.3 12.1.2.4 12.1.2.5 12.1.2.6 12.1.2.7 12.1.2.8 12.1.2.9 12.1.2.10 12.1.2.11 12.1.2.12 12.1.3 12.1.3.1 12.1.3.2 12.1.3.3 12.1.4 12.1.4.1 12.1.4.2 12.1.4.3 12.1.4.4

Initialisation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Atoll Initialisation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the Default Formats of Site and Transmitter Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling Automatic Renaming of Transmitters and Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the TIFF Colour Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating an Event Viewer Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Increasing the Maximum Printing Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duplicating Linked Path Loss Matrices on Save As . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restricting the List of Predictions for Creating Sector Traffic Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Path Loss Calculation Details in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Coverage Prediction Polygons in Text Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Web Map Services Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Improving Point Analysis Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Loading Vector Files Dynamically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Precision for the Antenna Pattern Verification at Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Opening Exported XLS Files Automatically in MS Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disallowing Creation of New Documents from Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blocking Access to Macros and Add-ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling Saving and Opening ZIP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Notification for Donor Transmitter Parameter Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Display Precision of Floating Point Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Path to Linked Geo Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Only Visible Geo Data in Prediction Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting BMP, TIF, and PNG Files with a TAB Reference File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Co-Planning: Linking the Sites Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling Normalisation of MIF/TAB Vector Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adding the Duplicate Site to the Original Site’s Site List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Only Visible Clutter Classes in Interference Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying % of Covered Clutter Classes w. r. t. the Focus Zone in Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying % of Covered Traffic Classes w. r. t. the Focus Zone in Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Synchronising Private and Shared Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting the Logo 2 Check Box by Default in Print Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Filtering Predictions by Technology When Reading the XML Studies File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Event Viewer Messages for MapInfo File Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Coverage Prediction Report Resolution For Population Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Coverage Prediction Report Precision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Hot Spot Reference Surface in Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting Only Visible Value Interval Layers of Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GUI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Parameters for the Default Sites Symbol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using a Unique Symbol for Remote Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keeping Transmitter Symbols From Changing on Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Filled Symbols for Inactive Transmitters on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Refreshing the Display Automatically When a New Station is Dropped. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hiding Information Displayed in the Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Date and Time in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Maximum Number of Lines in Coverage Prediction Tool Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Display for Downlink Smart Antenna Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Coverage Prediction Comments in the Legend Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Leading Zeros in the CELL_IDENTITY Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making the Antenna Additional Electrical Downtilt Accessible. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Distributed Calculation Server Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Detecting and Listing Distributed Calculation Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Distributed Calculation Server Priority. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the Default Detection Time-Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Licence Management Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting an Alarm for the Licence End Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blocking Access to Technology Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Blocking Access to ACP and AFP Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the NetHASP Licence Manager Idle Time Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 169 169 170 170 170 171 171 171 172 172 172 173 173 173 174 174 174 174 174 174 175 175 175 175 175 176 176 176 176 176 177 177 177 177 177 178 178 178 178 178 179 179 179 179 179 180 180 180 180 180 181 181 181 181 181 182 182 182 182 183

8

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Table of Contents

12.1.5 12.1.5.1 12.1.6 12.1.6.1 12.1.6.2 12.1.6.3 12.1.6.4 12.1.6.5 12.1.6.6 12.1.6.7 12.1.6.8 12.1.7 12.1.7.1 12.1.7.2 12.1.7.3 12.1.7.4 12.1.7.5 12.1.7.6 12.1.7.7 12.1.7.8 12.1.7.9 12.1.7.10 12.1.7.11 12.1.7.12 12.1.7.13 12.1.7.14 12.1.7.15 12.1.7.16 12.1.7.17 12.1.7.18 12.1.7.19 12.1.7.20 12.1.7.21 12.1.7.22 12.1.7.23 12.1.7.24 12.1.7.25 12.1.7.26 12.1.8 12.1.8.1 12.1.8.2 12.1.8.3 12.1.8.4 12.1.8.5 12.1.8.6 12.1.8.7 12.1.8.8 12.1.8.9 12.1.8.10 12.1.8.11 12.1.8.12 12.1.8.13 12.1.8.14 12.1.8.15 12.1.9 12.1.9.1 12.1.9.2 12.1.9.3 12.1.9.4 12.1.9.5 12.1.9.6 12.1.9.7 12.1.9.8 12.1.9.9 12.1.9.10 12.1.9.11 12.1.9.12

ACP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Specifying the Location of the Acp.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Database Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Checking Data Integrity After Database Upgrade and Data Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Setting an Automatic Database Integrity Check at Open or Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Modifying the Default Database Connection Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Making Atoll Case-Sensitive for Database Import From Planet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Setting the Sign for KClutter When Importing Data From Planet EV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Enabling/Disabling Password Prompt at Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Archiving Data to Databases Using Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Enabling Partial Refresh from Recently Upgraded Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Common Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Setting the Antenna Patterns Modelling Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Disabling Automatic Locking of Coverage Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Enabling Shadowing Margin in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Setting a Default Value for the Cell Edge Coverage Probability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Enabling Indoor Coverage in Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Modifying the Resolution for the LOS Area Calculation Around a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Disabling the Temporary Local Storage of Path Loss Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Embedding Path Losses in New Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Stopping Calculations on Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Warning About Prediction Vailidity When Display Options are Modified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Reading Exact Altitudes From the DTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Setting a Common Display Resolution For All Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Allocating Neighbours Based on Distance Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Setting the Priorities for GUI and Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Setting the Number of Parallel Processors and Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Disabling Parallel Calculation of Monte Carlo Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Performing Calculations in Read-Only Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Identifying Transmitter, Repeater, and Remote Antenna Coverage Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Changing the Rounding Method Used for Profile Extraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Estimating Required and Used Memory Size for UMTS Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Disabling Calculations Over NoData Values for DTM and Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Co-Planning: Calculating Predictions in the Current Document Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Co-Planning: Calculating Predictions in Serial or in Parallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Forcing Neighbour Symmetry Only Inside Focus Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Using Poisson Distribution in Monte-Carlo Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Calculating EIRP from Max Power in Signal Level Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 GSM GPRS EDGE Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Considering Overlapping Zones for IM Calculation Based on Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Setting the Default BSIC Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Selecting the Interference Matrices Used During the AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Checking Database Consistency Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Disabling the Maximum Range Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Enabling the Support for Multi-band Transmitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Setting the Best Server Calculation Method in Same Priority HCS Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Hiding Advanced AFP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Making Redundant Fields in the Transmitters Table Read-only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Setting the Transmission Diversity Gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Adding Grouped HCS Servers Option in Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Deactivating Frequency Band Filtering in IM Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Starting TRX Indexes at 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Hiding the TRX Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Extending the Allowed Value Range for C/I and Reception Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 UMTS HSPA, CDMA2000, and TD-SCDMA Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Suppressing Cell Name Carrier Suffixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Disabling Macro-diversity (SHO) Gains in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Calculating and Displaying Peak or Instantaneous HSDPA Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Setting the Power to Use for Intra-cell Interference in HSDPA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Enabling Coverage Predictions of Connection Probabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Setting the Calculation Method for HS-PDSCH CQI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Enabling Orthogonality Factor in Pilot EC/NT Calcaultion in HSDPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Setting the Maximum Number of Rejections for Mobiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Setting the Maximum Number of Rejections for HSDPA Mobiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Defining an Offset With Respect to The Thermal Noise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Setting Precision of the Rasterization Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Defining the Number of Iterations Before Downgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

9

.1 Displaying Additional Information in Drive Test Data . . . . . .2. .9. . . . . . . . .2. .17 Selecting SC and PN Offset Allocation Strategies Available in the GUI .2 Automatically Creating Custom Zones on the Optimisation Tab . . . . . . . . . . .2. . . . . . . . . . . .11. . . . .12. . . . . . .8. 12. .11. . . 12.1. . . . . . . . .2.9. . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12. . . . . .10 Renaming OPUSC Zone to PUSC UL . . 12. . .2. . . . . . . . . . . . . . . .9. . . . . . . . . . . . . . . .10. . . . . . . .2 Defining Reconfiguration Values for Cells Using Custom Atoll Fields . . . . . . . . .10. . . . . . . . . . . . . . . . . . . . . . . . 12.1. . . . . . . . . . . . . . . . . . .1. . . . . . .11. . . . . . . . . . . . . . . . . . . . 12. . . . . . . .1 Managing Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12. . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 Deactivating Uniform Distribution of Resources . . . . . . . .10. . . .12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 Defining a Fixed Interval Between Scrambling Codes . .2. . . . . . . . . . . .12. . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12. . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2.2. . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 Defining the BCCH and BSIC Columns for FMT Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 Default Values for EMF Exposure. . . . . . . . .2 Setting the Number of Transmitters per Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . .1 Default Values on the Optimisation Tab . . . . . . . . .1. . . . .2.9 Defining Site Class Options . . . . . . . . . . . . . . . .8. . . . . . . . . . . . . . . .9. . . . . .8 Defining Reconfiguration Values in Custom Atoll Fields . . . . . . . . . . 12. . . . . . . . . . . . . . . . . . . . . . . . . . 12. . . . . . . . . . . . .5 Importing Drive Test Data with Scrambling Codes as Integers . . . . . . . . . . .1.11 Microwave Radio Links Options . . . . . . 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . 12. . . . . .6 Defining Channel Number Prefix and Suffix for Display . . . . . . . . . . . . . . . .1. . . 12. . . . . . . . . .14 Displaying Ec/I0 of Rejected Mobiles in Simulation Results . . 12. . . . . . . . .6 Default Values on the Antennas Tab . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . .16 Displaying Automatic Allocation Cost Values . . . . . .5 Enabling Multi-antenna Interference Calculation in WiMAX. . . . . . . . . . . .9. . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . .2. . . . . . .2. . . . . . . . . . . . . . . . . . . .10. . . . . . . . . . . . . .10. . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12. . . . . . .2. .9 Ignoring Inter-Neighbour Physical Cell ID Collision . . . . . . . . . . . . . . . . . . 12. . . . . . . . . . .10. . . . . . . . . . . . . . . . . . .1. . . .2. . . . . . . . 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Taking Second Order Neighbours into Account in the AFP . . . . . . . .10. . . . . . . . . . . . . . .10 Defining the Appearance of the Optimisation Dialogue . . . . . . . . 12. . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 Other Components of the Optimisation Dialogue. . . . . .2. . . . . . . . . . . .1 Defining the Colours in the Quality Analysis Maps . . . . . . . . . . . .2. . . 12. . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . .1 Defining the Antenna Masking Model .10. . . .2. . .1. . . . . . . . . . . . . . . .Automatic Cell Planning Properties Dialogue . . . . .10. . .1. . . . . . .3 Updating A>>B and B>>A Profiles in Real-time. . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . .19 Compressed Mode: Restricting Inter-carrier and Inter-technology Neighbour Allocation . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . .2 ACP Initialisation File . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 Ignoring Inter-Neighbour Preamble Index Collision . . . . . . . . . . . . . .12 Defining the Functionality of the Commit Tab . . . . . . . . . . . . .12. . . . . . . . . 12. . . . .2. . . . . . . .1. . . . . .1. .2 GUI Options . . . . . . . . . 12. . . . . . . . 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . .11. . . . . .1. . . . . . . . . . . . 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 Defining the Appearance of New Maps. . . . . . . . . . . . . . . .2. . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . 12. . . . . . . . . . . . . . . . . .15 Switching Back to the Old Best Server Determination Method . . . . . 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1. .6 Including Cyclic Prefix Energy in LTE Signal Level Calculation . 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10. . . . . . . . . . . . . . . . 12. . . .9. . .8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . .2. . . 12. .1. . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . .5 Using Old Min C/I Values . . . . . . . . . . 12. . . . . . . . .0 Administrator Manual Table of Contents © Forsk 2011 12. . . . . . . . . . . 12. . . . . . . . . . . . . .2. .1 Defining Reconfiguration Values for Transmitters and Repeaters Using Custom Atoll Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10. . . . . . . . . . . . . . . . . . . . . . . . . .10 WiMAX and LTE Options . . . . . . . . . . . . . . . . . . . . . . . . . 12. . 12. .1. .2. . . . . . . . . . . . . .12 Activating Basic Preamble Index/Physical Cell ID Allocation . . . . . . . . 12. . 12. . . . . . . . . . . . . .4 Default Values on the Reconfiguration Tab . . . 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . .9. . . . . . . .2. . . .1. . . 12. . . . . . . . . . . . . . . . . . . . . . 12. . . . . .1. . . . . . . . . . . . .2 Using Only Bearers Common Between the Terminal’s and Cell’s Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Excluding Standby Channels from Interference Calculations . . . . . . . . . . . . . . . .3 Disabling Multi-antenna Interference Calculation in LTE. .9. . . . 12. . . . . . . . . . . . . . . . . . . . . . . . . .1. . . .2. . . . . . . . . . . . . . . . . . . . .11. . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12. . . . . . . . . . . .4 Disabling Sheilding Factor on Wanted Signal at Receiver . . . .2 Automatically Assigning Site Classes in the ACP . . . . . . . . . . . . . . . . . . . . .3 Recalculating Distances of Points From There Serving Cells at Import. .1. . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Blocking Access to IEEE Parameters in WiMAX. . . . . . . . . . . . . . . . . .1. . . .12 Measurement Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Defining Automatic Site Classes . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 Enabling Display of Signals per Subcarrier Point Analysis in LTE . . . . . . . . . . . . . . . . . . . . 12. . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10. . . . . . . . . . . . . . . . . . . . .16 Exporting Optimisation Results in XML . . . . . . . . . . . . . . . . . . 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . .11.2. . . . . . . .10. . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . .1. . . . .10. . 12. . .15 Defining the Default Font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Adjusting the Working of the Proportional Fair Scheduler . . . . .2. . . . . . . . . . . . . . . . .7. . . . . . . . . . . . . . . . . .Atoll 3. . . . . . . .1. .20 Setting the Maximum AS Size for SC Interference Prediction . . . . . . . . .2. . . . . . . . . 12. . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10. . 12. . . . . . . . . . . . . . .1. . . . . . 12. . . . . . . . . . . .2. . . . . . . . 12. . . . . 12.2. . . . . . . 198 198 198 199 199 199 199 199 200 200 200 200 200 201 201 201 201 201 202 202 202 202 202 203 203 203 203 203 203 203 204 204 204 204 204 204 205 205 205 205 206 206 206 207 211 213 214 214 214 215 215 216 217 217 218 218 219 219 219 220 221 221 221 221 221 222 10 .2. . . . . . . . . . . . . . . . . .9. . . . . . . . . . . . . . 12. . . . . . . . . . . 12. . . . .13 Defining the Appearance of the Overlay Window . . . . . . . . . . . . . . . . . . . . . . . . . . 12. . . . . . . .2. 12. . . . . . . . . . . . . . . . . 12.2. . 12. . . . . . . . . .2. .9. . .3 Defining Reconfiguration Values for Sites Using Custom Atoll Fields . . . . . .1. . . . . . . . . . . 12. .3 Default Values on the Objectives Tab . . . . . . . . . . . . . . 12.12. . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12. . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . .7 Defining the Functionality of the ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 Setting the Maximum UL Reuse Factor for HSUPA Users’ Noise Rise Estimation . .9. .2. . . . .14 Setting PDCCH to 100% Loaded in LTE Interference Calculations .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . .10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 Defining Reconfiguration Values for Antennas Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 Excluding Near-field Interference from Calculations . . . .7 Excluding Cyclic Prefix Energy in WiMAX Signal Level Calculation . . . . . . . . . . . . . . . . . . . .14 Defining the Appearance of the Graph Tab. .9. . . . . . . . . . . . . . . . . . . . .8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 Displaying Uplink Total Losses in Coverage by Signal Level . . . . . . . . . . . . 12. . . . . . . . . . . . . . . . 12. . . . . . . . . .2.2. . . . . . 12. . . . . . . . . . . . . . . . . . . 12. . . . 12. . . . . . . . . . . . . . . . .2. . . . . . . . . . 12. . . . . . . . . .1. . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . 242 EGPRSServicesUsage Table . . 248 QualityIndicators Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Balancing Speed. . . . . . . . . . . . . . . . . . . . .4 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . 224 Accessing Raster Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Multi-antenna Interference Calculation (WiMAX) .2 13. . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. .15 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Calculation Thread Pool Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Cyclic Prefix Energy in Signal Level Calculation (LTE) . . . . . . . .8 to 3. . . . . . . . . . . . . . . . . . . .3. . . .37 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 EGPRSEquipments Table. . 247 NeighboursExt Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 EMF Exposure Core Options . . . . . . . . . . . . . . . . . . . . .21 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Signal Level. . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . 247 NeighboursConstraints Table . . . .20 13. . . . . . . . . .2. . . . . . . . . . . . . . . . . . 244 FrequencyBands Table . . . . . . . . . . . . . . . . . . . . . . . 227 Validity of Coverage Predictions . . . . . . . . . 245 FrequencyGroups Table . . . . . . . . . 244 EGPRSUserProfiles Table. . . . . . . .8 12. . . . . . . . . . . . . . . . . . . . . 240 EGPRSCodingSchemes Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 13. . . . . . . . . . . . . . . . . . . . . . . . . . . .1 13. . . . . . . .7 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 13 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 EGPRSDimensioningModel Table. . . . . . . . . . .2. . . . . . 235 AfpModels Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . .231 Changes in Data Structure From 2. . . . . . . .1 12. . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 EGPRSMobility Table . . . . . . . . . . . and Accuracy in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Deleted Tables and Fields . . . . . . . . . 247 NeighboursConstraintsExt Table . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . .18 13. . 237 CellTypes Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . .2. . . . .25 13. . . . . . . . . . . . . . . . . . . 225 Multi-antenna Interference Calculation (LTE) . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . 247 Networks Table . . . . . . . . . . . . . . . . . . . . . . . . . .17 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . .23 13. . 224 Accessing Path Loss Matrices. . . . . . . . . . . . 225 Cyclic Prefix Energy in Signal Level Calculation (WiMAX) . . . . .0 Administrator Manual Table of Contents 12. . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. . . . . . 236 BSICDomains Table . . . . . . . . . . . . . . . . . . . . .30 13. . . . . . . . . .26 13. . . . . . . . . . . . . . . . . . . . . .3. . 243 EGPRSTerminals Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . 241 EGPRSEnvironmentDefs Table . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . .32 13. . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 13. . . . . . . . . . . . . . . . . . . . . . . . .5 13. . . . . . . . . . . . . . . . . . .22 13.39 13. . . . . .5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Enabling Multi-technology Optimisation Including WiMAX . . . . . . . 237 CodecEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4. . . . .34 13. . . . . . . . . . . .10 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . .2 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 FeederEquipments Table .14 12. . . . . . . . . . . . . . . . . . .1 ACP Core Engine Options. . . . . . . . . . . . . . . . . . . . . . .1 12. . . . . . . . . . . . . 238 CoordSys Table . . . . . . . . . . . . . . . . . . . . . 245 FrequencyDomains Table . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . 223 Macro Diversity Gain (UMTS Only) . . . . . . .3. . . . . . . . . . . . . . . . . . . . 222 Memory Management Settings . . . . . . . . . . .15 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . .19 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . .27 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 13. . . . . . . . . . . .29 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Signal Level and Macro Diversity Gain Calculation Options . . . . . . . . . . . . . .40 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 13. . . . . . . . . . . . . . . . . . .2. . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Antennas Table .3. . . . . . . . . . . . . . . . . .2. . . . . . . . . 246 HSNGroups Table. . . . . . . . . . . . . . . . . . . 238 CodecModes Table . . . . . . . . . . 239 CustomFields Table . . . . .2 13. . . . . . . . . .2 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 HSNDomains Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 13. . . . . . 242 EGPRSServices Table . . . . . . .3 13. . . . . . . . . . . . . 246 Neighbours Table. . . . . . . . . . .24 13. . . . . . . . . . . . . . . . . .5 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 GSM GPRS EDGE Data Structure. . . . . . . . . . . . . . . . . . . . . . . . . 238 CodecQualityTables Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Fixed Ratio Between Pilot Power and Max Power (UMTS) . . . . . . . . . . .9 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 CodecModeAdaptations Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 InterNetChProtect Table. . . . . . . . . .2. . . . . .9 13. . . . . . . . . . . . . . 222 Log File Settings . . . . . . . . 233 Added Tables and Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 BTSEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 12. . . . . . . . . . . . . . 243 EGPRSTrafficEnvironments Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 BSICGroups Table . . . . . .10 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 12. . . . . . . . . . . . . . . . . 248 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3. . . . . . . . . . . . . . . . . . . Memory Use. . . . . . . . . . . . . . 237 ChannelModels Table . . . 248 PropagationModels Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Preamble Segmentation (WiMAX) . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Determining Transmitter Altitude . . . . . . . . . . . . . . . . . . . . . 241 EGPRSQuality Table. . . . . . . . . . . . . . . . . . . . . . . .1 . . . . . . . . . 242 EGPRSServiceQuality Table. .16 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 12. . . . . . . . . . .4 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . 226 Other Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 Layers Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 13. . . . . . . . . . . . . .1 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 12. . . . . . . . . . . . . . . . . . . . . . . . . . .AT310_AM_E2 Atoll 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . .13 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 14. . . . . . . . HSUPAUECategories Table . . .11 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SecondaryAntennas Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 14. . .28 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Networks Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSConfigurations Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . Neighbours Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Separations Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . PropagationModels Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRXs Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SitesLists Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 14. .25 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 14. . . . . . . . . . . . . . .60 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 Administrator Manual Table of Contents © Forsk 2011 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SecondaryAntennas Table. . . . . . . . . CDMAEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TplTransmitters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ServiceQualityTables Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SeparationRules Table . . . . . . . . . . . . . . . . . . . . .53 13. . . .62 13. . . . . . . . . . . . . . . . . . . .16 14. .10 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Changes in Data Structure From 2. . . . . . . . . . . . . . . . . . . . . . . . . . . .23 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 14. . . . . . . . . . . . . . . . . . . . . . . . . . .47 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . Sites Table. . . . . . . .39 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 14. . . . . . . . . . . . CustomFields Table . . . . . . . . . . . . . TRXTypes Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antennas Table. . . . Repeaters Table . . . . . . . . . .17 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 13. . . . . . . . . . Deleted Tables and Fields . . . . . . . . . . . . . . . . . Separations Table. . . . . . . . . Units Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSConfigurationNames Table . . . . . . . . . . . . . . . . . . . HSUPABearerSelection Table . . . . . . . . . . . . . . . . . . .63 Receivers Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NeighboursConstraints Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSDPABearerSelectTables Table. . . . . . . . . . . . .46 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HSUPAQualityTables Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDMAEquipmentsCEsUse Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . InterNetChProtect Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sites Table. . . . . . . . . . . . . . . . . . . . . . . . Receivers Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 14. . . . . . . . . . . . . . . .21 14. . . . . . . . . .9 14. . TMAEquipments Table . . . . . . . . . . . . . . R99Bearers Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . TRXEquipments Table . . . . . . . .4 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NeighboursConstraintsExt Table. . . . . . . . . . . . . . . . . . . . . .32 14. . . . . . . . . . . . . . . . .36 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 13. . . . . . . . . . . . . . . . . . . .1 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CdmaEqptsHSUPARssUse Table . . . . . . . . . .45 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FrequencyBands Table. . . . . . . .1 14. HSDPAQualityTables Table . . . . . . . . . . . . . . . . . . . . . . . SitesLists Table . . . . . . . . . . . . HSDPABearers Table . . . . . . . RepeaterEquipments Table .14 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . QualityIndicators Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 14. . . . . . . . . . . . . . . . . . . . . .8 to 3. . . . . . . . .33 14. . . . . . . . . . . . . . . . . . . . . . . . 266 266 267 268 268 269 270 271 271 272 273 273 273 274 274 274 274 275 275 276 276 276 276 277 277 277 278 278 279 279 280 280 280 281 282 282 282 282 283 283 283 284 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TxsListsNames Table . . . . . . . . . . . . . . . . . . . . . . . . . . TRGConfigurations Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . FeederEquipments Table. . . . . . . . . . . . . . . . . . .54 13. . . . . . ScramblingCodesGroups Table . . .55 13. . . . . . . ScramblingCodesDomains Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 . . . .42 13. . . . . . . . .7 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRGs Table . . . . . . . . . . . . . . . . . . . . . . . RepeaterEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . .24 14. . . . . . . . . . . . . . . . . . CDMACells Table . . . . . . . . . . . . .59 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . InterfReductionFactors Table . . . . . . . . . . . . . . . . . NeighboursExt Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 14. . HSPAMIMOConfigs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TxsLists Table . . . . . . . . . . . . . . . . . . . . . . . . . .26 14. BTSEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Added Tables and Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Atoll 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 249 250 250 251 251 251 252 252 252 252 254 256 257 259 259 260 260 260 261 261 261 14 14. . . . . . . .37 14. . . . .51 13. . . . . . . . . . . . . . . . . . . . . . . .35 14. . . . . . . . . . . . . . . .12 14. . .48 13. . . . . . . . . CoordSys Table . . . . . . . . . . . . . . . Repeaters Table . . .44 13. . . . . . . . . . . . . . . . . . . . . . . . . . SitesListsNames Table . . . . . . . . . HSUPABearers Table . . . . . . . . . . . . . . Transmitters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 UMTS HSPA Data Structure. . . . . . . . . . . . . . . . . . . . . .5 14. . . . . . . . . . . . . . . . . . . . . . . . SitesListsNames Table . . . . . . . . . . .19 14. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 15. . . . . . . . . . . . . . . . .10 15. . . . . . . . . . . . . . . . 284 Transmitters Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 T4GEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 UMTSUserProfiles Table . . . . . . . 315 T4GMobility Table . . . . . . . . . . . . .38 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 15. . .36 15. . . . . . . . . . . . . . . . 318 T4GUserProfiles Table. . . . . . . . . . . . . . . . . . . . . . . .1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 14. . . . . . . . . . . . . . . . . . . . . .45 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 UMTSServicesQuality Table . . . . . . . . . . . . . . 312 T4GEnvironmentDefs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 15. . . . . . 287 TxsLists Table . . . . . . . . . . . . . . . . . . 289 UERxEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 14. . . . . . . . 301 BTSEquipments Table . . . . . . . . . . . . . . . . . . . . .13 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 T4GUECategories Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 TplTransmitters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 SecondaryAntennas Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Deleted Tables and Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 15. . . 316 T4GTerminals Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 15. . . . . . . . . . . . .1 15. . . . . . . . . . . 312 T4GBearers Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .AT310_AM_E2 Atoll 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 Schedulers Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 T4GTraficEnvironments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 CustomFields Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 15. . . . .14 15. . . . . . . . . . . . . . . . . . . . .4 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 TxsListsNames Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 SitesLists Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 PropagationModels Table. . . . . . . . . . . . . . . . . . . . . . . 308 Repeaters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Sites Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Networks Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Added Tables and Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 15. . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Units Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Neighbours Table. .7 15. . . . . . . . .55 14. . . . . . . . . . . . . . . . . . . 303 FrequencyBands Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 CoordSys Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 15. . . . . . . . . . . . . . . . . . . . . . . 290 UMTSMobility Table . . . . . . . . . . . . . . . . . . . . 306 NeighboursExt Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 UMTSTerminals Table . .41 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 LTE Data Structure . . . . . . . . . . . . . .23 15. . . . . . . . . . . . . . . . . . . . . . . . . . 311 T4GBearerQualityCurves Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 15. . . . . . . . . . . . . . 311 SitesListsNames Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 15. . . . . . . . . . . . . . . . . . . . . . . . . . .29 15. . . . . . . . . 308 QualityIndicators Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 UMTSEnvironmentDefs Table . . . . . . . . . . . . . . . . . . . . . . . . . 305 lpcigroups Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 Antennas Table . . . . . 290 UMTSServices Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 15. . . . . . . . . . . . . . . . 289 UECategories Table . . . . . . . . . . . . . . . .18 15. . . . . . . . . . . 314 T4GMimoConfigs Table. . . .0 Administrator Manual Table of Contents 14. . . . . . . . . . . . . . . . . .37 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 NeighboursConstraints Table . . . . . . . . .42 14. . . . . . . . . . . . . . . . . . . . 303 FeederEquipments Table . . . . . . . . . .20 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 MUGTables Table . . . . . . . . . . . . . . . . 315 T4GServices Table . . 311 SmartAntennas Table . . . . . .26 15. . . . . . . . . . . . . 304 lpcidomains Table . . . . . . . . . . . . . 311 SmartAntennasModels Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 15. . . . . . . . . . . . . . . . . .51 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 UMTSTraficEnvironments Table. . . . . . . . . . . . . . . . . . . . . .48 14. . . . . . . . . 304 lframeconfigs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 15. . 293 15 15. . . . . . . . . . . . . . . . . . . . . . . . . .2 15. . . .8 to 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 InterNetChProtect Table. . .3 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 14. . . . . . . . . . . 312 T4GBearersRequiredCI Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 T4GServicesUsage Table . . . . . . . . .16 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 UMTSServicesUsage Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 TplTransmitters Table .41 15. . 318 Transmitters Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 NeighboursConstraintsExt Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 TMAEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 15. . . . . . . . . . . 318 TMAEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . 308 RepeaterEquipments Table . . . . . . . . . . . . . . . . . . . . . 308 Receivers Table . . . . . . . . . . . . . . . . . . . . . . . . .24 15. . . . . . . . . .295 Changes in Data Structure From 2. . . . . . . . . . . .53 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 T4GCells Table . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . 322 TxsListsNames Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DORABearersProba Table . UMTSTerminals Table . . . . . . . . .3 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmitters Table . . . . . . . . . . . . . . NeighboursConstraintsExt Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDMAEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 17.32 17. .14 17. . . . . . . . . . . .2 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TMAEquipments Table . . . . . . . . . . . . . . . . . Networks Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 17. . . . . . . . . . . . . . . . . . . . . . .41 17. . . . . . . . . . . . . . . . Deleted Tables and Fields . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . .8 17. .5 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 16 16. . . . . . . . . . . . . . . Common Tables With Merged Structures . . . . . . . . . . . . . . . . . . . . . CustomFields Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Neighbours Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 17. . . . . . . . . . . . . . . . . . . . . . UMTSUserProfiles Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . InterNetChProtect Table . . . . . .10 17. . . . . . . . . . . . . . . . . . . . . . . . .1. . 335 Changes in Data Structure From 2. . . . . . .31 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 16. . . . . . . . . . . . . . . . . . . .37 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UERxEquipments Table . . . . . . . . . . . . . . . . . .8 to 3. . . . . . . . . . . . . . Antennas Table. . . . . . . . . . . . . . . . . . . . . . . . . .42 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 338 339 340 340 340 341 342 342 343 344 344 344 345 345 345 345 346 346 346 346 347 347 347 348 348 349 349 349 350 350 350 351 351 352 352 352 353 353 353 356 357 357 357 357 358 358 358 360 360 361 362 362 362 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 17. . . . . . . .7 17. . . . Sites Table. . . . . . . . . . . . . . . . . UMTSServicesQuality Table. . . . . . . DORATerminalT2PRatios Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ULBearersSelection Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTSEquipments Table . . . . . . . . . . . . TxsListsNames Table . . . . . . . . . . . . . . . .49 TxsLists Table . . . . . .2 17. . . . . . . . . . . . . . . . .0 Administrator Manual Table of Contents © Forsk 2011 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technology-specific Tables . . . . . . . .40 17. . . . . . . . . . . . . .24 17. . . . . . . . . . . . . . . InterfReductionFactors Table . . . 322 Units Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Separations Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 17. . . . . . . . . UMTSServices Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 Common Tables With Identical Structures . . . . . . . . . . . . . . . . . . . . 325 326 327 329 331 17 17. . . . . . . . . .45 17. . . . . . . . . . . . . . . . . . . . . . .33 17.9 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 17. .21 17. . . . .Atoll 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . QualityIndicators Table . . . . . . . . . .22 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receivers Table. . . . . . . PropagationModels Table . SitesListsNames Table . . . . . . . . . . . . . . . . . . . . . . . SitesLists Table . . . . . . . . . . . . . . .5 3GPP Multi-RAT Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . Added Tables and Fields. . . . . . . . . . . . . . . . .23 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 17. . . . . .46 17. . . . . . . . . . . . . . . . . . . . . .26 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 17. . . . . . . . . . . . . . .38 17. DORABearers Table . . . . . . . . . . . . . PnCodesDomains Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 17. . . .1 . . . . . . . UMTSMobility Table . . . . . . . . . . . . UMTSServicesUsage Table . . . . . . . . . . . . . . . . CoordSys Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 17. NeighboursConstraints Table . . . . . . . . . . . . . . . . . . . DLDORABearers Table . . . . . . . . . . . . . . .50 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 CDMA2000 Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NeighboursExt Table . . . . . . . . . . . . FeederEquipments Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TplTransmitters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TxsLists Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Repeaters Table . . .36 17. . . . . . . . . . . . . . . . . . . . . . . Bi-directional Neighbour Relations Tables. . . . SecondaryAntennas Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CarriersType Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDMACells Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Units Table . . . . . . . . . . . . . . . . . . . . . . . . . . . Multi-RAT Traffic Model Tables . . . . . . . . . . . . . . . . . . . . . . . FrequencyBands Table. . . . . . . . .48 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 17. . . . . . . . . . . . . .11 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDMAEquipmentsCEsUse Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 16. ServiceQualityTables Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UMTSEnvironmentDefs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PnCodesGroups Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 17. . . . . . . . . . . . . . . . . . . UMTSTraficEnvironments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 17. . . . . . . . . . .6 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DLBearersSelection Table . . . . . . . . . . . . . . . . . . . . . . . . . . .3 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RepeaterEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 15. . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .56 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 ServiceQualityTables Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 SitesListsNames Table . . . 393 UECategories Table . . . . . . . . .9 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 CodesRelativityClusters Table . . . . . . . . . . . . . . . . . 398 Units Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387 SitesLists Table. . . . . . . . . . . . . . . . . . . . . . . 393 TxsListsNames Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 HSDPABearerSelectTables Table . . . . . . . . . . . . . . . . . . . . . .51 18. . . . .17 18. . . . .8 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365 Changes in Data Structure From 2. . . . . . . . . . . 396 UMTSServicesUsage Table . . 385 ScramblingCodesGroups Table. . . . . . . . . . . . 398 15 . . . 373 CDMACellsTS Table . . . . . . . 376 CoordSys Table . . . . . . . . . . .27 18. . . . . 372 CDMACells Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 18. . . . . . . . . . . . . . . . . . .41 18. . . . . . . . . . . . . . . . . . . . . . .20 18. . . . . . . . . . . . . . . . . . . .25 18. . .59 18.48 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 Antennas Table . . . . . . . . . . . . . . . . . . . . . . . . . .50 18. . . . . 384 Repeaters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .AT310_AM_E2 Atoll 3. . . . . . . . . . . . . . . . . . . . .23 18. 385 SecondaryAntennas Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 PropagationModels Table. . . . . . . . . . . . . .49 18. . . . . . . . . . . . 387 SmartAntennas Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 AntennasLists Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 18. 377 FeederEquipments Table . . . . . 380 NeighboursConstraintsExt Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 UMTSTerminals Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 18. . . 378 HSDPABearers Table . . . . . . .52 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 Added Tables and Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 CustomFields Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 HSUPABearers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 UMTSUserProfiles Table . . . . . . . . . . . . . . . . .32 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394 UMTSEnvironmentDefs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 NeighboursConstraints Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 TMAEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 InterNetChProtect Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 Transmitters Table. . . . . . . . . . . . . . . . . . . 381 NeighboursExt Table . . . . . . . . . . . . .24 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 18.53 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 18. . . . . . . . . .47 18. . . . . . . . . . . . .10 18. . . . . . . . . . . . . . . . . .46 18. . . . . . 386 Sites Table . . . . .1. . . . . . . . 375 CDMAEquipmentsCEsUse Table. . . . . . . . . . . . . . . . . . . . . . 377 FrequencyBands Table . . . . . . . . . 383 RepeaterEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394 UMTSMobility Table . . . . . . . . . . . . . 388 SmartAntennasModels Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 AntennasListsNames Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 QualityIndicators Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 ScramblingCodesDomains Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 TD-SCDMA Data Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 18. . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 18. . . . . . . . . . . . . . . . . . . . . . 378 HSUPABearerSelection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 TplTransmitters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Receivers Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 18. . . . . . . . . . . . . . . . . .1 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 .3 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 TxsLists Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 18. . . . . . . . . . . . . . 394 UMTSServices Table . . . . . . . .40 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 InterfReductionFactors Table . . .14 18. . . . . . . . . . . . . . . . . . . . . . 393 UERxEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 18. . 384 SACIGainCDF Table . .21 18.54 18.16 18. . . . . . . . . . . . . . . . . 397 UMTSTraficEnvironments Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 to 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 18. . . . . . . . . . . . . . . . . . . . . . . . . .36 18. . . . . . . 380 Neighbours Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 18. . . . . . . 381 Networks Table . . . . . . . . . . . . . . . 375 CDMAEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 BTSEquipments Table . . . . . . . . . . . . . . .57 18. . . . 386 Separations Table . . . . . . . . . . . .45 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 18. . . . . . . . . . . . . .2 18. . . . . . . . . . . . . . . . . . . . . . .55 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 18. . . . . . . . . . . . . . . . . . . . . . 386 ServiceRUsUse Table . . . . . . . . . . . . . . . . . . . 383 R99Bearers Table. . . . . . . . . . . . . . . . . . . . . . . . . . .6 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 Deleted Tables and Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 Administrator Manual Table of Contents 18 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 HSUPAUECategories . . . .1. . . . . . . . . . . . . . . 395 UMTSServicesQuality Table . . . . . . . . . . . . . . . . .

. . . . . . . . . . .40 19. . . . . . . . . . WUserProfiles Table . . . . . . . . . . . . . . . . . . . . . . NeighboursExt Table . . . . Neighbours Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 Administrator Manual Table of Contents © Forsk 2011 19 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 19. . . . . . . . . . . . . . . . TxsLists Table . Added Tables and Fields. . . . . . . . . . . . . . . . . . . . . . . . . . .4 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FrameConfigurations Table . . . . . SmartAntennas Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 19. . . . . . . . . . . . . . . . . . . . . . . . . Receivers Table. . . . . . . . . .47 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WServices Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 19. . . . . . . . . . . . . . . . . . . . . . . . . . Networks Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 19. . . . . . . . . . . . . SitesListsNames Table . . . . . . . . . . . . . . . . . .1. . . . . . . . . Sites Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 20. . . . . . . . . . . . . . . . . . . . . .11 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 to 3. . .34 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 19. . . . . . . . . SmartAntennasModels Table . . . MWAntennas Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Atoll 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SecondaryAntennas Table. . . . . . . . .26 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 19. . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 20. . WTerminals Table . . . . . . . . . . . . . . . . . . . . .1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 401 405 405 405 406 407 407 407 408 408 408 409 409 409 410 410 411 412 412 413 413 413 414 414 415 415 415 416 416 416 416 419 420 420 420 421 421 421 421 423 423 423 424 424 424 425 426 426 427 427 20 20. . . . . . . . . . . . . . . . . .2 19. . . . . . . . . . . . . . . . TMAEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . PropagationModels Table . . . . . . . . .14 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WBearers Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 Changes in Data Structure From 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . SitesLists Table . . . . . . . . . . . . . . . . . .12 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Repeaters Table . . . . . . . . . . . . . . . .4 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 . . . . . . . . . . . . . . .1 20.1 20. . .27 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 20. . . . . . . . . . . . . WBearersRequiredCI Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 19. . . . . . . . . . . . . . . . WCells Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 19. . Mapping Between Old and New Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 19. . . . . .1 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TplTransmitters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WPIDomains Table. . . . . . . . . .32 19. . . . . . . Modified Fields . . . . . . . . . . . . . . . . . . . . . . . .42 19. . . . . . . CustomFields Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 20. . . . . . . . . . . . . . . . WTraficEnvironments Table . . . . . . . . . . . . . . . . . . . . . .17 19. . . . . . . . . . . . . . .6 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 19. . . . . . . . . Transmitters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 20. . . . . . . . . . . Antennas Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MWCapacities Table . . . . . . . . . . . . . . . . . . . . . Deleted Tables and Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NeighboursConstraintsExt Table. TxsListsNames Table . MWBranchingConfigs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WServicesUsage Table. . . . . . . . . . . . . . . . . . . . . . BTSEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 19. . . . . . . . . . . . . . . . . . . .48 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WMobility Table. . . . . . . . . . . . . . Deleted Tables and Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PermutationZones Table . .24 19. . . . . . . . . . . . . . . . . . . . . WBearerQualityCurves Table . . . FrequencyBands Table. . . . . . . . . . . . . . . . . . . . . . . . WEquipments Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Added Tables and Fields. . . . . . . . . . . . . . . . . . . . .8 19. . . . . . . . . . . . . . . . . . . . . . . . . . . CoordSys Table . . . . . . . . . . . . . FeederEquipments Table. WEnvironmentDefs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedulers Table . . . . . . . . . NeighboursConstraints Table . . . . . . . . . . . . . . . . . . . . . . . . . .1 19. . . . . . . . . . . . . . . . . . . MUGTables Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 19. . . . . . . . . . . . . . . . . . . . . . CustomFields Table .8 to 3. . . . . . . .8 Microwave Links Data Structure. . . . . . . . . . . . . . . . . . . . . . . . . . WMimoConfigs Table . . . . . . . . . . . . . . . . .37 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WPIGroups Table . . . . . . . . . . . . . . . . . .45 19. . . . . . . RepeaterEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . .18 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . InterNetChProtect Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 429 432 433 433 435 436 436 437 437 437 437 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 19. . . . . .4 20.19 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CoordSys Table . . . . . . . . .5 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . QualityIndicators Table . . . . . . . . . .1. . . . . . . . . . . . . . . . . .49 WiMAX Data Structure .1. . . . . . . . . MWBands Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Units Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1. . . . . . . . . . . . . . . . . . . . . . .22 19. . . . 429 Changes in Data Structure From 2. . . . . . . . . . . . . . MWCompatibilities Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 20. . . . . . . . . . .31 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .15 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 MWCompatibilitiesGuides Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 MWManufacturers Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 MWFamilies Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 MWModulations Table . . . . . 454 Units Table . . . . . . . . . . . . . . . . . .AT310_AM_E2 Atoll 3. . . . . . . . . . . . . . . .18 20. . .28 20. . . . . . . . . . . . . . . . .30 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .0 Administrator Manual Table of Contents 20. . . . . . . . . . . . . . . . . . .34 20. . . . . . . . . . . . . . . . . . .1. . . . . . . 448 MWMultiHops Table . . . . . . . . . 448 MWPMP Table . . . . . . . . . . . . . . . . . . 443 MWHubs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 20. . . . . . .10 20. . . . . . . . . . . . . . . . . . . . . . . 450 Networks Table . . . . . . . . . . . . . . . . . . . . .25 20. . . . . . . . .29 20. . . . . . . . . . . . . . . . . . . . . . . . . . . 454 17 . . .23 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 20. . . . . . . . . . . . . . . . . . . 448 MWMultiHopsLinks Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 MWLinks Table . . . . . . . . . . . . . . . . . . . .27 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 MWFamilyBands Table .12 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 MWFamilyChSpacings Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 20. . . . . . . . . . . . . . . . . . . . . . . . . . 443 MWIrfs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 MWLinkTypes Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 20. . . . . . . . . . . . . . . . . . . . . . . . 441 MWFamilyBrConfigs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 MWEPOLinkClass Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 MWEquipments Table. . . . . . . . . . . . . . . .16 20. . . . . . . . . . . . . . . . . 442 MWGuides Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 20. . . . . . . . . . . . . . . . . . . . . . . . . . 453 SitesListsNames Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 20. . . . . . . . . . . . . . . . . . . . 448 MWPorts Table . . . . . . . . . . . . . . . . . .24 20. . . .33 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 Sites Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 MWSubbands Table . . . . . . . . . . . . . . . . . . . . . . . . 452 PropagationModels Table. . . . . . . . . . . . . . . 450 MWTplLinks Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 MWDefaultsCurves Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 MWFamilyModulations Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 20. . . . . . . . . . . . . . . . .14 20. .9 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 SitesLists Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 MWEPO Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 MWRepeaters Table . . . . . . . . .

0 Administrator Manual Table of Contents © Forsk 2011 18 .Atoll 3.1.

In this part. and to manage databases and multi-user environments. the following are explained: • • • • • • "Getting Started" on page 21 "Installing Atoll and Components" on page 25 "Setting Up Distributed Calculation Server" on page 35 "Managing Licences" on page 39 "Managing Databases" on page 45 "Multi-user Environments" on page 65 .Part 1 Getting Started This part of the administrator manual provides the information to install and set up Atoll and its components.

.

1 Supported Technologies Atoll supports the following technologies: • • • • • • • • GSM GPRS EDGE UMTS HSPA LTE 3GPP Multi-RAT (i. The version 12. configure.2 Supported Operating Systems Atoll supports the following versions of Microsoft Windows operating systems: • • • • • • Microsoft Windows XP (32-bit and 64-bit) Microsoft Windows Vista (32-bit and 64-bit) Microsoft Windows 7 (32-bit and 64-bit) Microsoft Windows 2003 Server Microsoft Windows 2008 Server (32-bit and 64-bit) Microsoft Windows 2008 Server R2 1.AT310_AM_E2 Atoll 3. the following are explained: • • • • • • "Supported Technologies" on page 21 "Supported Operating Systems" on page 21 "Supported Database Management Systems" on page 21 "Supported Installation Configurations" on page 22 "Recommended Hardware and Software" on page 22 "Recommended Computer Network Architecture" on page 23. Sybase client version 12. user documents are connected to a central database..0 should be used. The following table shows where the database must be installed: 21 . in which users store their work on a common project. from initial design to densification and optimisation. and deploy Atoll and how to set up back-end databases and manage users in a multiuser environment. combined GSM.4 is not supported. The physical location of databases varies according to the type of the database. Atoll supports the following RDBMS: • • • • • Oracle via the OLE DB interface Microsoft SQL Server Microsoft Access Sybase Any database that accepts UDL files and supports the ODBC interface • • • Oracle client version 10.0 works with Microsoft Windows XP. and flexible multi-technology network design and optimisation platform that supports wireless operators throughout the network lifecycle.e. scalable.3 or later should be used.0 Administrator Manual Chapter 1: Getting Started 1 Getting Started Atoll is an open.1. In a multi-user environment. not with the later versions.5. UMTS. Database structures of the different technology modules are also provided for reference. This manual explains how to install. Atoll supports a wide range of implementation scenarios.3 Supported Database Management Systems In a multi-user environment. and LTE) CDMA2000 1xRTT EV-DO TD-SCDMA WiMAX Microwave links 1. Sybase client version 12.0.5. from standalone to enterprise-wide server-based configurations using distributed and multithreaded computing.5. 1. databases allow several users to share data without the risk of data inconsistency. In this chapter.2.

2 Database Servers The following table lists the required and recommended hardware and software for an Oracle database server.5. Server No Yes Yes Yes Client computer Yesa No Yes (Oracle client) Yes 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. where users run Atoll sessions on the servers through the Citrix interface. The same configuration can be considered valid for other database systems as well. Atoll can be installed in a: • Standalone configuration Atoll installed on each individual user computer with a fixed licence key plugged in each computer.Floating licence: nethasp. 1. you must install Oracle client on the user computers as well. Dual-core or better 2 GB or more At least 10 GBa Microsoft Windows XP Professional SP3 / Microsoft Windows 7 . if any. The servers may be Citrix-based.Atoll 3. The floating licence management server allocates licence tokens to Atoll sessions run by the users on the servers.0 Administrator Manual Chapter 1: Getting Started © Forsk 2011 Database Microsoft Access Microsoft SQL server Oracle Sybase a.1 User Computers The following table lists the required and recommended hardware and software for user computers (clients) intended for running with Atoll.4 Supported Installation Configurations Depending on your requirements. 1. The Oracle client version must correspond to the Oracle database installed on the database server.ini file in the Atoll installation folder Depends on the size of the locally stored geographic data and path loss matrices. Processor RAM Free hard disk space Operating system Other requirements a. 1. 1.1.5 Recommended Hardware and Software This section provides guidelines for dimensioning client computers and servers on your network for optimum performance with Atoll.Fixed licence: 1 USB port required to plug-in the fixed licence key . • Server-based multi-user configuration Atoll installed on servers connected to user computers and a floating licence management server on a network. If you are working with an Oracle database. Processor RAM Dual-core 3 GB or more 22 .5. • 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. This section lists the recommended hardware and software for: • • • • • "User Computers" on page 22 "Database Servers" on page 22 "Citrix Servers" on page 23 "Floating Licence Servers" on page 23 "File Servers" on page 23.

The following table lists the required and recommended hardware and software for Citrix servers intended for running with Atoll.5. Users can work with Atoll installed on these servers through Citrix MetaFrame. Processor RAM Free hard disk space Operating system Citrix 1 dual-core processor per 2 to 3 users (1 quad-core per 4 to 6. recalculating path loss matrices for these 40 cells. hardware.6 Recommended Computer Network Architecture The following network architecture recommendations are based on benchmark test results carried out on the network of an average-sized operator.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.1. For more information. with around 40 to 60 Atoll licences.5 File Servers File servers may store geographic data. The required hard disk space has to be determined from the file sizes of these data. Atoll configuration and initialistaion files. defining user rights.AT310_AM_E2 Atoll 3. 1. 120 GB or morea Microsoft Windows 2003 Server / Microsoft Windows 2008 Server / Unix / Linux Oracle 10g or 11g / Microsoft SQL Server 2005 / Sybase Adaptive Server 12. 23 .3 Citrix Servers Citrix servers are intended for installing and running Atoll. The "Routine Operation" consists in modifying parameters for 40 cells in 30 minutes. Based on these recommendations. 1. This bandwidth is needed during calculations for data exchange between Atoll sessions and the 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. and calculating a best server coverage prediction. each user is assumed to carry out a "Routine Operation" 5 times during a three-hour working period. and user projects. 1.0 or later The recommended bandwidth between Citrix servers and Citrix clients for satisfactory performance is 300 Kbps per user. path loss matrices. see "Working with Floating Licences" on page 39. Must have the floating licence key plugged in.5.0 Administrator Manual Chapter 1: Getting Started Free hard disk space Operating system RDBMS a. Must have the HASP licence manager installed and running. The results show the requirements in terms of network. etc.0 Tablespace of around 100 MB per 10000 transmitters. and so on) 1 GB per user 72 GB or more Microsoft Windows 2003 Server / Microsoft Windows 2008 Server Citrix (XenApp) MetaFrame Presentation Server 4. Must have a steady and reliable network connection with user computers / Citrix servers. The recommended bandwidth between the user computers / Citrix servers and the file servers is 30 Mbps per user performing calculations..5. 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: Number of sites in the calculation area: Per-sector path loss calculation radius: Path loss calculation resolution: 1660 sites (around 5000 cells) 300 sites (900 cells) 20 km (i.5.e. matrices of 40 km x 40 km each) 50 m In order to simulate the average activity of Atoll users. 1. Can be one of the Citrix servers. and software.

0 Administrator Manual Chapter 1: Getting Started © Forsk 2011 Although a best server coverage prediction does not require a lot of computer resources for calculations. Computer Network Architecture A centralised network architecture is the most widely used network architecture by Atoll users. which is related to the size of the planning project. Figure 1. it requires Atoll to load all the path loss matrices in memory. Link From End-user Citrix server To Citrix server File server Recommended Bandwidth 300 kbps per user 30 Mbps per user performing calculations 24 .Atoll 3. one processor per 2 to 3 users is recommended. as recommended. The benchmark tests have been based on this simulated data transfer activity. the required number of Citrix servers depends on the number of processors and the number of endusers. The figure below shows the recommended architecture along with a per-user network bandwidth requirement between different network components.1: Recommended Network Architecture and Bandwidth Requirements Citrix MetaFrame is used to centralise data and balance user loads between servers.1. Thus. Computer Network Dimensioning You should set up your network according to the number of Atoll users. When the path loss matrices are stored on a file server. The required number of Citrix servers depends on the number of users. this operation creates a considerable data transfer activity over the network. On the average. A network based on such an architecture with Citrix servers must provide high speed connections between the Citrix servers and the file servers. A country-wide project would have larger network dimensions than a project that covers a city.

1. you must unplug the key before the installation and wait for the installation to finish before inserting it in. Click OK. You can select a different location by clicking Browse.1. Select Change User Account Control settings. The default installation folder for Atoll is C:\Program Files\Forsk\Atoll in the 32-bit versions of Microsoft Windows. • • • • Microsoft Windows Vista Microsoft Windows 7 Microsoft Windows 2008 Server Microsoft Windows 2008 Server R2 To disable UAC: a. 25 . Disable UAC (User Account Control) for the following versions of Microsoft Windows. 2. Go to Control Panel > User Accounts.AT310_AM_E2 Atoll 3. c. The Select Destination Location dialogue appears. with a step-wise description of the installation. 3. Figure 2. Click Next. • • • Click Next to proceed to the next step. The User Account Control Settings dialogue appears. Run the Atoll setup. d. You can. and C:\Program Files (x86)\Forsk\Atoll in the 64-bit versions. Select the destination folder for the installation.1: Atoll Setup Wizard 2. Click Back to go back and modify previously set options. The setup program uses a wizard interface. or Click Cancel to cancel the installation.0 Administrator Manual 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. Choose Never notify. If you are installing Atoll on other versions of Microsoft Windows. proceed to step 1. b.1 Installing Atoll Using the Setup Wizard To install Atoll: • • If you work with fixed licences.

1. the Logon Information dialogue appears. the Select Start Menu Folder dialogue appears. 26 . You can select a different folder by clicking Browse. Select the Start Menu folder for Atoll. b. Figure 2.Atoll 3.2: Select Destination Location Dialogue 4. Figure 2. If you did not select this component. Click Next. and allow other users of the domain to access this service. 5. Click Next. Custom installation: Atoll and the selected components will be installed. and Password. • • • Full installation: Atoll and all its components will be installed. proceed to step 7. Enter the Domain name. In which case.4: Select Components Dialogue a.0 Administrator Manual Chapter 2: Installing Atoll and Components © Forsk 2011 Figure 2. If you selected the Distributed Calculation Server component for installation. Select the components to install. This information will be used to run the distributed calculation service on the computer.3: Select Components Dialogue 6. The default Start Menu folder for Atoll is Atoll. Compact installation: Only Atoll will be installed. The Select Components dialogue appears. Click Next. The Select Start Menu Folder dialogue appears 7. Username.

0 Administrator Manual Chapter 2: Installing Atoll and Components Figure 2.5: Select Start Menu Folder Dialogue 8. Restarting the computer is necessary for the driver to work. proceed to step 1. you can assign read/write access rights to this folder to administrators and read-only rights to end-users. Figure 2. you must publish it to make it access to users. Disable UAC (User Account Control) for the following versions of Microsoft Windows.1.ini • [Atoll installation folder]\coordsystems\Favourites. Review the installation parameters. The Ready to Install dialogue appears. If you work with fixed licences. Click Next. If you are installing Atoll C++ development kit on other versions of Microsoft Windows. Click Install.cs These files are not removed when Atoll is uninstalled. restart the computer. 9. 27 .AT310_AM_E2 Atoll 3. On the versions of Microsoft Windows that support UAC (disabled before the installation). empty ones are created by the setup: • [Atoll installation folder]\Atoll. • If you have installed Atoll on a Citrix server. plug in the fixed licence key. Atoll should be installed for testing the add-ins. Atoll and its selected components are installed on the computer. To restrict access to the Atoll installation folder. run Atoll once using an administrator account and with UAC disabled when the installation is complete. • • • If you work with fixed licences and you installed the Driver for Fixed Licence Keys.6: Ready to Install Dialogue 10.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. • If the following files do not already exist in the installation folder. 2.

Choose Never notify. Run the Atoll C++ development kit setup.8: Select Destination Location Dialogue 4. Review the installation parameters. Click OK. The Select Destination Location dialogue appears.1. 3. Click Next. b.Atoll 3. or Click Cancel to cancel the installation. You can. Click Back to go back and modify previously set options.0 Administrator Manual Chapter 2: Installing Atoll and Components © Forsk 2011 • • • • Microsoft Windows Vista Microsoft Windows 7 Microsoft Windows 2008 Server Microsoft Windows 2008 Server R2 To disable UAC: a. 1. 28 .7: Atoll C++ Development Kit Setup Wizard 2. Figure 2. d. The User Account Control Settings dialogue appears. Go to Control Panel > User Accounts. with a step-wise description of the installation. 5. You can select a different location by clicking Browse. Click Next. Select Change User Account Control settings. Figure 2. The default installation folder for Atoll C++ Development Kit is C:\Program Files\Forsk\Atoll in the 32-bit versions of Microsoft Windows. and C:\Program Files (x86)\Forsk\Atoll in the 64-bit versions. The Ready to Install dialogue appears. Select the destination folder for the installation. c. • • • Click Next to proceed to the next step. The setup program uses a wizard interface.

• /DIR="x:\folder name" Overrides the default installation folder displayed on the Select Destination Location wizard page. Use quotes if the filename contains spaces. The following command line parameters are accepted by the Atoll setup program. For example. • /SAVEINF="file name" Instructs the setup to save installation settings to the specified file. when automating the installation through batch files. When the setup is silent the wizard window is not displayed but the installation progress window is.1. for example. error messages during installation are displayed. the log file will tell you if the file was actually skipped and why.3 Setup Command Line Parameters You can also install Atoll and its components from the command line. • /NORESTART Instructs the setup not to restart the computer even if necessary. If it is very silent it will reboot without asking. Use quotes if the folder name contains spaces. Use quotes if the file name contains spaces. • /LOG="file name" Causes the setup to create a log file listing file installation and actions taken during the installation process. Everything else is normal.9: Ready to Install Dialogue 6. Useful along with /SILENT or /VERYSILENT. • /LOADINF="file name" Instructs the setup to load the settings from the specified file after having checked the command line. • /SVRPASSWD=password 29 . If the setup is silent and it requires to restart the computer. So. and also the startup prompt. When a setup is very silent the installation progress window is not displayed. /VERYSILENT Instructs the setup to be silent or very silent. • /SILENT. it will display a Reboot now? message box. which can be useful to administrators. 2. the setup will abort with an error message. Use quotes if the file name contains spaces. Click Install. Atoll C++ Development Kit is installed on the computer. • /NOCANCEL Prevents the user from cancelling the installation by disabling the cancel button and ignoring clicks on the close button. Use quotes if the folder name contains spaces. If the file cannot be created. The Atoll setup program accepts optional command line parameters. For example. if you suspect a file is not being installed as it should be.AT310_AM_E2 Atoll 3. but the /NORESTART option is not used (see below). • /GROUP="folder name" Overrides the default Start Menu folder name displayed on the Select Start Menu Folder wizard page. • /SVRACCOUNT="domainname\username" The domain name and user name for installing the distributed calculation server. and to other programs calling the setup program. This can be helpful for troubleshooting. This file can be prepared using the /SAVEINF command as explained above.0 Administrator Manual Chapter 2: Installing Atoll and Components Figure 2.

10: Add-ins and Macros Dialogue 30 . The DLL is registered. 2. • /COMPONENTS="comma separated list of component names" Overrides the default component settings.Atoll_Server. The context menu appears. Only the specified components will be selected. the /COMPONENTS parameters are ignored. which place the add-ins’ DLLs in appropriate locations and register them. Add-ins developed by Forsk have dedicated setup programs. Right-click the DLL file in Windows Explorer. the distributed calculation server. The setup procedures in these cases are described in the add-ins’ documentation. It is possible to access and work with add-ins and macros when there is no ATL file open in Atoll. To install an add-in by registering its DLL: 1. select Tools > Add-ins and Macros. and the driver for fixed licence keys: /COMPONENTS="Atoll. 3. The setup type names are: • • • Full installation: full Compact installation: compact Custom installation: custom For full and compact setup types. • /TYPE=type name Overrides the default setup type. In Atoll. The Add-ins and Macros dialogue appears (see Figure 2. You can also register the DLL from the command prompt using regsrv32. 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. Atoll loads it in the list of available add-ins. Figure 2.10 on page 30).RainbowDongle" 2.1. Using this command line parameter causes the setup to automatically select a custom installation type. Select Register.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 registery. Select the add-in’s check box to activate it. Once an add-in is installed. or clear the check box to deactivate it. To activate or deactivate an installed add-in in Atoll: 1. Close Atoll.exe.0 Administrator Manual Chapter 2: Installing Atoll and Components © Forsk 2011 Password for installing the distributed calculation server. 2.Atoll 3.

The DLL is unregistered. Icon: Assign an icon to the selected macro.0 Administrator Manual Chapter 2: Installing Atoll and Components Add-ins installed by the Atoll setup are uninstalled when Atoll is uninstalled. Select Unregister. • -Provider providername 31 . This may be helpful for troubleshooting.5 Installing and Uninstalling Macros Atoll can load and execute macros written in VBScript. 3. select Tools > Add-ins and Macros.cfg file located in the Atoll installation folder. To remove a macro from Atoll: 1. To uninstall any other add-in by unregistering its DLL: 1. 2.10 on page 30). This may be used to override the default loading of the Atoll. refer to "Contents of User Configuration Files" on page 142. 4. select Tools > Add-ins and Macros.6 Atoll Command Line Parameters Atoll supports the following optional command line parameters: Atoll. • -Cfg "cfgfilename" Instructs Atoll to load the specified user configuration file when run. Click Delete. You can also unregister the DLL from the command prompt using regsrv32.1.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. In Atoll. 3. To load a macro in Atoll: 1. Other commands available in the Add-ins and Macros dialogue are: • • • • Edit: Edit the selected macro in the default text editor. If you leave the timeout empty. The context menu appears. • • To disable the macro timeout. set it to 0.exe /u. For more information. This may be used to override the default loading of the Atoll. Click Open. "inifilename" is the full path and file name of the initialisation file inside quotes. 3.10 on page 30). Click Add. "cfgfilename" is the full path and file name of the user configuration file inside quotes. 2. select the macro you wish to remove.ini file located in the Atoll installation folder. The Add-ins and Macros dialogue appears (see Figure 2. Right-click the DLL file in Windows Explorer. The macro is added to Atoll.AT310_AM_E2 Atoll 3. 2. In the list of available macros. The Add-ins and Macros dialogue appears (see Figure 2. Close Atoll. 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. • -Ini "inifilename" Instructs Atoll to load the specified initialisation file when run. In Atoll. The Open dialogue appears. 2. Select the macro file you wish to load. Refresh: To reload the selected macro file. Icons assigned to macros appear in the Macros toolbar. Run: Execute the selected macro. 2. "logfilename" is the full path and file name of the log file inside quotes. the default value (24 days) is used.

If Atoll is unable to access the fixed licence key.4.0 Administrator Manual Chapter 2: Installing Atoll and Components © Forsk 2011 Instructs Atoll to use the mentioned providername to access the database server (Microsoft Access: Microsoft. 2. UserId. The driver’s setup program (SPI761. • -DataSource server Instructs Atoll to access the mentioned database server using the given provider. Restarting the computer is necessary for the driver for fixed licence keys to work. or Oracle: MSDAORA. try reinstalling the Sentinel SuperPro driver manually. build. Atoll version and build • You can get information about Atoll (version.1. verify that the fixed licence key correctly plugged in and that the licence has not expired. type of licence and remaining time before expiration.com. In case the fixed or the floating licence key becomes unavailable. Do not change the computer’s date. in case you have to uninstall a certain patch. You can also download the driver from http://www. contact Forsk’s customer support.7 Troubleshooting and Other Information Read and follow the instructions in "Installing Atoll Using the Setup Wizard" on page 25 carefully for a smooth installation. you must published it to make it available to the users. you should not install the driver for fixed licence keys on: • • • • • Microsoft Windows 2003 Server Microsoft Windows 2008 Server Microsoft Windows 2008 Server R2 • • • • Citrix • The current version of the driver for fixed licence keys (Sentinel SuperPro driver) installed with Atoll is the 7. It is also recommended to keep the Windows updates uninstall folders. • -Project projectaccount Instructs Atoll to access the mentioned Oracle database server using the mentioned projectaccount.safenet-inc. under the Windows folder. If the key becomes available again.. 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. and Project are case sensitive.) by selecting Help > About Atoll in the main menu in Atoll. • -UserId username Instructs Atoll to access the mentioned Oracle database server using the mentioned username.6. • The keywords Provider. Pay special attention to updates and patches related to networking. 32 . However.OLEDB.Atoll 3. Atoll will ask the users currently accessing the key to save their open documents before Atoll closes. even after a clean installation. DataSource. • -Password password Instructs Atoll to access the mentioned Oracle database server using the mentioned password. If you have installed Atoll on a Citrix MetaFrame server.exe) is copied to the Sentinel subfolder in the Atoll installation folder by the setup if you selected the Driver for Fixed Licence Keys component during the installation. Atoll will let the users continue working. Restart the computer when asked by the setup.1).Jet. If you get a protection key error message. etc.0. Password. named "$NtUninstall. • Fixed licence keys • Fixed licence keys cannot be used with "Server"-type operating systems. Therefore.. Microsoft Windows Updates • It is recommended to install new Windows updates.1.". Some of the update patches may require uninstall folders of older patches to be available for their own installation. If problems occur and you are unable to resolve them with the help of the following information.

Uninstalling Atoll and its components It is recommended to uninstall Atoll and its components through Control Panel. Select Uninstall. select Atoll from the list of installed programs. Right-click the ATL file in the Windows Explorer. b. In Windows XP. 2. click the Summary tab and then the Advanced button. Sample add-ins. 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. and possible workarounds. Schedule for upcoming versions. The support website also offers you: • • A problem report template. More documents are available for download on the Forsk’s support website. To access the ATL file properties: 1. List of holidays. macros. • In Windows Vista. The context menu appears. and scripts • • • • • • Sample geographic data.1. b. Windows 7. 3. In the Install/Uninstall tab. 33 . For full contact details for customer support. Acknowledgement • Atoll uses Inno Setup for installation. Click the Remove button. In Windows Vista and 7. right-click Atoll.0 Administrator Manual Chapter 2: Installing Atoll and Components Atoll file version and technology ATL file properties store the Atoll version and build number in which the file was last saved.jrsoftware. Select Properties from the context menu.php. List of known issues. For more information. Go to Control Panel > Programs and Features. The Atoll version and build number in which the ATL file was last saved are stored in the Revision number property. see page 3. The file properties dialogue appears. or Windows 2008 Server: a. see http://www. The technologies of the document are listed in the Category property. and the technologies contained in the file. c.AT310_AM_E2 Atoll 3. To uninstall Atoll: • In Windows XP or Windows 2003 Server: a. Go to Control Panel > Add or Remove Programs. Documentation. The Atoll User Manual and other documents are available on the installation CD. In the Uninstall or change a program window. c.org/isinfo. click the Details tab. The context menu appears. Add-ins installed by the Atoll setup are uninstalled when Atoll is uninstalled. List of fixed issues in the versions available for download.

1.Atoll 3.0 Administrator Manual Chapter 2: Installing Atoll and Components © Forsk 2011 34 .

AT310_AM_E2 Atoll 3. 3.1. On the Log On tab. The service does not require any active user session on the computer. During calculations. and hence has lower memory requirements than Atoll. 3. The distributed calculation server uses the standard Atoll API to exchange data with the path loss calculator and Atoll.1 Setting Up Servers When installed. Select Properties.0 Administrator Manual 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. see "Distributed Calculation Server Options" on page 181. The distributed calculation service is an optional service that may be installed at the same time as Atoll.. To modify the user account through which the distributed calculation service is run on a computer: 1. the distributed calculation server. You may set up as many distributed calculation servers as required. The distributed calculation service does not have a user interface. see "Installing Atoll and Components" on page 25. i. Consequently. right-click the Atoll Server service. the distributed calculation servers require access to geographic data for calculating the path loss matrices.ini file. The distributed calculation service must be run with a user account that has sufficient privileges to access the required data.e. the service keeps running even when there is no user logged on. 2. the distributed calculation service automatically starts and remains available as long as the computer is turned on. is visible to all the other computers on the network through Atoll. 4. enter the user name and password for the user account through which you wish to run this service. The Atoll Server Properties dialogue appears. The context menu appears. Any version of Atoll can work with the distributed calculation service of the same or later version. any version of the distributed calculation service can work with the same or previous versions of Atoll (versions still maintained by Forsk). Go to Control Panel > Administrative Tools > Services. 6.1: Atoll Server Properties 5. For distributed calculation server options available through the Atoll. Click OK. A computer on which the distributed calculation service is installed and running is called a distributed calculation server. For more information on installation. In the list of services. 35 . Figure 3. The Atoll distributed calculation service is listed as Atoll Server in the Services management console under Control Panel >Administrative Tools. The service’s executable (AtollSvr. This computer. The distributed calculation service supports dual-processor configurations and up to four threads.exe) is installed in the Atoll installation folder. Log on to the computer with a user account with administrator rights.

right-click the Atoll Server service. close the command prompt window corresponding to it. b. This will remove the distributed calculation service from the computer. 2. In the list of services. the path loss calculations run by the user are distributed over the available calculation servers. b. 3. a.3 Distributed Calculation Process Once distributed calculations have been set up on the calculation server and on the user sides. right-click the Atoll Server service. For each new instance of the service. 3.0 Administrator Manual Chapter 3: Setting Up Distributed Calculation Server © Forsk 2011 Running More Than One Instance of the Service By default. The calculation process is as follows: 1. double-click the AtollSvr. Go to Control Panel > Administrative Tools > Services. a command prompt window opens. b. manually run service. In the list of services. Log on to the computer with a user account with administrator rights. and select Stop or Start from the context menu. Type "<Atoll Installation Path>\AtollSvr. To manually run additional distributed calculation services. Select Tools > Distributed Calculations from the main menu. Log on to the computer with a user account with administrator rights. If you run more than 9 additional distributed calculation services. click All. Remove the distributed calculation servers that you do not wish to include. Stopping and Starting the Distributed Calculation Server To stop the distributed calculation service: 1. Atoll searches for the available distributed calculation servers on the network. Click Run. The Distributed Calculations dialogue appears. Atoll user runs path loss calculations. Atoll sends the needed network data to the available calculation servers. 2. 2.1. run up to 9 additional distributed calculation services (a total of 10 including the first one) manually. The available distributed calculation servers are listed in the edit box. Click OK. 36 . Uninstalling the Distributed Calculation Server To uninstall the distributed calculation service: 1. click Detect. Stop the distributed calculation service: a. c. Atoll can detect a total of 10 instances of the distributed calculation service. The Run dialogue appears. a single instance of the distributed calculation service is run. 3.2 Setting Up Atoll to Access the Servers To activate distributed calculations in Atoll: 1. To use selected distributed calculation servers only. 3. To use all the available distributed calculation servers. The selected distributed calculation servers are now available for path loss calculations. Go to Control Panel > Administrative Tools > Services.exe file located in the Atoll installation folder. To stop an additional.exe /UnregServer". c. 2. Select Start > Run. however. Either Atoll sends the needed geographic data to the calculation servers or the servers access the geographic data on a file server. and select Stop from the context menu. <Atoll Installation Path> is the path to the Atoll installation folder. Unregister the service: a. Select the Activate distributed calculation check box.Atoll 3. 3. You can. they will not be detected by Atoll and can cause the operating system to stop responding. 3.

However. If no thread is available. Atoll transfers the calculations back to the local computer. Atoll uses one thread on the local computer and calculates the path loss matrices one by one. 6. not necessarily on the user’s computer that requested the calculations). In order to reduce the amount of data flow in the network. Any error or warning messages generated are passed back to the Atoll session and displayed in the Event Viewer.AT310_AM_E2 Atoll 3. 7. distributed calculation servers send the results directly to the storage location (which may also be on a file server.0 Administrator Manual Chapter 3: Setting Up Distributed Calculation Server 4. the request is placed in a queue to wait for a thread to become available. Distributed calculation servers calculate the path loss matrices one by one. to avoid memory saturation. Distributed calculation servers that have spare threads start the calculations using these threads. For each calculated path loss matrix. a confirmation is sent to the Atoll session. 37 . Atoll user may then request the path loss matrices from the file server if they are needed for coverage predictions. It does not attempt creating more than one thread.1. If an error occurs on any of the distributed calculation servers. 5.

1.Atoll 3.0 Administrator Manual Chapter 3: Setting Up Distributed Calculation Server © Forsk 2011 38 .

not HASP HL.com/support/hasp/hasp4/enduser.1.20 or above. 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. • • • 4. nhsrv. The HASP licence manager may be installed on a computer running Windows 2000 or later. If a computer is connected to a floating licence server and also has a fixed licence key plugged in. For information on the Atoll licence management utility. nethasp. remember to download setup files for HASP4. HASP hardware key is supported by Windows 2000 Server and Windows 2003 Server with HASP Licence Manager 8. The driver for fixed licence keys can be installed at the same time as Atoll. Newer versions may be available for download at the website than those provided on the Atoll installation disk. Atoll uses a 3rd-party floating licence management system called HASP from Aladdin. A USB port must be available on the server for plugging in the floating licence key.x or Envelope 12. and the HASP monitor from http://www3. In a floating licence environment.aspx. For more information. 39 .0 Administrator Manual 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.ini file: Installed on the computers to facilitate access to the floating licence server. the fixed licence key is accessed first. The floating licence management system includes: • • • • • • HASP floating licence key: Hardware key programmed with the numbers of tokens available for each module. The floating licence management software and the floating licence key control the number of potential Atoll users. Each computer that runs Atoll takes one token from the floating licence key. or Computers connected to a licence server with a floating licence key plugged in to a USB port on the server. but a shared licence key with multiple tokens is available to users through a server. When downloading setup files from the Aladdin website. The floating licence server may be one of the computers on which Atoll is installed. the HASP device driver. HASP licence manager: Interface between Atoll and the floating licence key. Default settings are used otherwise. see "Working with Floating Licences" on page 39. on which the floating licence management software has been installed and a floating licence key plugged in.x". licence keys are not plugged in to each individual user’s computer.safenet-inc. The token is released and made available for other users when all the Atoll sessions on the computer are closed. It uses the HASP device driver for communicating with the floating licence key. see "Installing Atoll and Components" on page 25. A floating licence system has a defined maximum number of tokens available.ini file: Installed on the floating licence server to enable computers to use tokens. • You can download the HASP licence manager. This is the maximum number of computers on which Atoll may be run simultaneously. The correct (recommended) version of the device driver setup to download is the one that works with "HASP4 API v8.AT310_AM_E2 Atoll 3. even if more than one Atoll session is run on the same computer. see "Using the Atoll Licence Manager" on page 41. A floating licence server is a computer.1 Working with Floating Licences A floating licence key may be used when users work with Atoll on computers on a network. HASP monitor: Enables you to check the number of used and available tokens. 4.1 HASP Licence Manager and Device Driver The HASP licence manager controls the allocation and retrieval of licence tokens available on a floating licence key. nhsrv.ini and nethasp. accessible to other computers on a network. HASP device driver: Interface between the HASP licence manager and floating licence key.1.ini files are used if they exist.

This means that the licence manager will run as a service. The following options should be selected when installing the HASP licence manager: • Choose "Service" as the type of installation. Go to Control Panel > Administrative Tools > Services.0 Administrator Manual Chapter 4: Managing Licences © Forsk 2011 • • • • • Do not plug the floating licence key in the server before installing the device drivers. If this is the case.ini file may be used to define a list of computers allowed to request tokens from the floating licence server. If the floating licence server is protected by a firewall. Atoll will ask the users currently accessing the key to save their open documents before Atoll closes. If the key becomes available again.ini file must be located in the HASP licence manager installation folder. An icon will be available in the task bar. The HASP licence manager window displays a list of supported protocols which can be modified through the Load and Remove menus. In the list of services. and the floating licence key must be installed on the server. Atoll will let the users continue working. • Accept automatic driver installation. If you selected "Service" as the type of installation. Once installed. port 475 must be open when using the UDP or TCP protocols. The icon remains available in the taskbar as long as the service is running. the floating licence key must always remain plugged in. This will install the HASP device driver required by the HASP licence manager. • You may also copy (from the installation CD) or create the nhsrv. Closing this window does not stop the licence manager. the licence manager will start in service mode. try changing the latency associated to the HASP licence manager in accessing the key. or on one or several other computers. To stop the HASP licence manager: a. remove any such application from memory.Atoll 3. plug in the floating licence key. see "nhsrv. start the HASP licence manager. Once the HASP licence manager has been installed.1. You can access the network communication protocols by double-clicking this icon. The HASP monitor displays the list of computers using tokens available on the floating licence key. File Location If used. and will be accessible even if there is no user logged on.2 nhsrv. Installation and Startup The HASP licence manager. the HASP device driver. • • Once the device driver is successfully installed. and select Stop from the context menu. To restrict access to the HASP licence manager installation folder. In case the fixed or the floating licence key becomes unavailable. the nhsrv. You may choose to install it as an application. 40 . 4. For more information on the contents of the nhsrv. b. right-click the HASP Loader service. to monitor the token allocation and retrieval activity. Check if there is any application running on the server that might be causing the problem.ini File The nhsrv.ini File" on page 40.1. HASP Monitor (Optional) You can install the HASP monitor on the floating licence server. If this is not possible. The HASP licence manager settings in this file can be modified according to the your requirements. you can assign read/ write access rights to this folder to administrators and read-only rights to end-users.ini file on the floating licence server (in the HASP licence manager installation folder). The floating licence key may become unavailable and a key protection error message appears in Atoll if the licence management server is heavily loaded. Wait for the HASP licence manager setup to indicate when to plug in the key.ini file. 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.

<IpAddr1>. for some reason. and update licence keys.3 nethasp. These fields define the timeout delays depending to the network.(b)Send TCP or UDP packets .(a)IP address of the floating licence server . Complete syntax may be found on the HASP installation CD or on the Aladdin website. If.Use the NETBIOS protocol .1. For HASP Licence Manager 8.ini file located in the Windows folder. 4.1.AT310_AM_E2 Atoll 3.<IpAddr2>.domainname. File Contents The following is a sample of the nethasp. Only one server name is supported in the nethasp.Enabled or Disabled .Use the TCP/IP protocol .ini file located in the Atoll installation folder has priority over any nethasp.com.1. Aladdin recommends UDP as the default TCP/IP method. it is not possible to store the file in the Atoll installation folder. Modifying parameters in the licence manager without proper input from Forsk customer support may damage your fixed or floating licences and block access of Atoll users to the licences. for servername.20 and later.ini file. which in turn has priority over any nethasp.ini file located in a folder listed in the system path variable.ini file enables Atoll to locate the floating licence server quickly.] . They may be useful in slow networks and should be set only if required.1.ini File The nethasp.ini file.0 Administrator Manual Chapter 4: Managing Licences File Contents The following is a sample of the nhsrv. [NH_COMMON] NH_IPX = Disabled NH_NETBIOS = Disabled NH_TCPIP = Enabled [NH_TCPIP] NH_SERVER_ADDR = 3CT000J NH_TCPIP_METHOD = UDP NH_USE_BROADCAST = Disabled a. File Location The nethasp. remove the semi-colon before NHS_IP_LIMIT 4. This avoids making a copy of the file in each Atoll installation folder.Example: 10.Enabled or Disabled . finding the floating licence server on the network may take a long time.For use.2 Using the Atoll Licence Manager Atoll Licence Manager enables you to monitor.Enabled or Disabled b..Specifies the IP addresses of computers served by the licence manager . • • Remove the NH_SESSION and NH_SEND_RCV entries from the nethasp..1.NHS_IP_LIMIT = <IpAddr0>[.Use the IPX protocol . Complete syntax may be found on the HASP installation CD or on the Aladdin website.Use TCP/IP broadcast .ini file with the minimum required information. enter servername only.1. and you wish to access the same floating licence server.Enabled or Disabled . troubleshoot. it may 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. [NHS_SERVER] .ini file that shows how to set a list of computers allowed access to the floating licence server. Without the nethasp.ini file in the Windows folder instead of the Atoll installation folder may be useful if you have more than one version of Atoll installed.ini file if these exist. 10.* . It is recommended to enter the server name within the domain. You must not use the licence manager without full instructions and details from Forsk customer support. . For example.1.ini file should be located in the Atoll installation folder (recommended). Storing the nethasp.. 41 .

select a licence key in order to display the information related to it.1 Licence Manager Interface To open the Atoll licence manager: 1. Run Lic. the Modify buttons are reserved for Forsk use only. Figure 4. for reprogramming the licence key.exe. Under Selected key the following information is available for the selected key: • • • • • • • Number: Unique key number given by the key provider. Under Number of licences. when requested. Location (server): Name of the floating licence management server on which the floating licence key is plugged. the following dates and durations are available: • • • • Licence start Licence end Duration of validity Time bomb 42 .1. all the Atoll modules available on the selected key are listed along with the numbers of licence tokens of each. for reprogramming the licence key. Under Modules and licences. Go to the Atoll installation folder.Atoll 3. Type: The type of key. The licence manager opens (see Figure 4. Under Dates and durations. The Clear all button is reserved for Forsk use only. Fixed licence or Floating licence.1 on page 42). This number must be communicated to Forsk. when requested. 2. This number must be communicated to Forsk. Reference: Unique floating licence key reference provided by Forsk.2.1: Atoll Licence Manager 4. Under Available licences. This reference is also printed on the sticker on the key.0 Administrator Manual Chapter 4: Managing Licences © Forsk 2011 4. Close Atoll. 3.

The licence manager opens (see Figure 4. 5. The Time bomb date is the end date for maintenance.ini file. You may then choose to either purchase maintenance for the next year. select the key to update. To update a licence key. If the key does not appear in the available licences list.AT310_AM_E2 Atoll 3.1. Go to the Atoll installation folder. Under Key programming. 6. Select the ALIC file provided by Forsk. • • • • Do not attempt to modify the Time bomb settings on the fixed licence key. Atoll can inform you about the approaching time bomb date 30 days in advance. 4.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. 4. all of the above information is summarised. 3.0 Administrator Manual Chapter 4: Managing Licences A purchased Atoll licence corresponds to a particular Atollversion. the licence key stops working. This alert can be configured through the Atoll. However. Under Profile signature. Forsk reprograms your licence keys to allow access to new versions. Under Available licences. The key is updated. Run Lic. Under Current profile summary. Click Open. 43 . Do not attempt to reprogram a licence key without full information and support from Forsk customer support. When you purchase maintenance. in which case users can continue working with the existing version. click Load. The Open dialogue appears.2. Contact Forsk’s customer support. Each key has a unique PID. yearly maintenance must be purchased in order to access newer versions with updates and bug fixes. 2. the PID (profile signature or ID) is the encrypted description of the user rights available on the key. To update a licence key: 1. you must have the ALIC file sent by Forsk. There is no time limit on using this version. When the time bomb date passes. 7.1 on page 42). or have the licence key reprogrammed without maintenance for the next year. Do not change the computer’s date.exe. and benefit from the new features and bug fixes. check that it is plugged in to your computer. Close Atoll.

0 Administrator Manual Chapter 4: Managing Licences © Forsk 2011 44 .Atoll 3.1.

e. and a microwave links database can be stored on the same database server using the same RDBMS (Oracle. primary keys are listed in bold and italic characters. a UMTS. For the list of tables and fields. see: • • • • • • • • "GSM GPRS EDGE Data Structure" on page 231 "UMTS HSPA Data Structure" on page 263 "LTE Data Structure" on page 295 "3GPP Multi-RAT Data Structure" on page 325 "CDMA2000 Data Structure" on page 335 "TD-SCDMA Data Structure" on page 365 "WiMAX Data Structure" on page 399 "Microwave Links Data Structure" on page 429.AT310_AM_E2 Atoll 3. or with documents connected to databases. and the equivalent field types and sizes in different RDBMS: 45 . to a another RDBMS (for example. These unidirectional arrows should be read as: = n or ∞ 1 In the tables. primary keys are in bold and underlined characters. For example. Standalone documents are more portable. their sizes. in each database template. UMTS. Databases (using RDBMS) may then be created from any Atoll document. These databases are hence also based on the data structure defined by the Atoll database templates. documents without any back-end database. TD-SCDMA. LTE. and their relationships. In multi-user environments. In this chapter. i. Each database template is an MS Access MDB file located in the templates folder in the Atoll installation folder. In the database schema figures.0 Administrator Manual Chapter 5: Managing Databases 5 Managing Databases In Atoll. If you export the content of an ATL document which is already connected to a database. A database server can store one or more database. you can work with standalone documents. if you export a document connected to an Oracle database to Sybase or Microsoft Access). Database template files must not be modified without consulting Forsk customer support. and Microwave Radio Links) are based on database templates. several users work on the same project and a central data storage is necessary for keeping the data modifications made by a team radio planning and optimisation engineers. The following table lists the types of fields used in Atoll database templates.1 Atoll Database Templates All the technology modules available in Atoll (GSM. but due to the complex nature of the upgrade process.1. it is highly recommended to use the Atoll Management Console for upgrading existing databases. In each new major release. Atoll enables you create databases. database templates undergo modifications required to support new features. a GSM. manage and resolve data conflicts. however a back-end database is required when working in a multi-user environment. respectively. WiMAX. some field types will be converted according to the above table but this conversion does not have an impact on the document in Atoll. upgrade them to newer versions.. CDMA2000. and create and work with multi-level databases. These modifications are applied to existing Atoll documents and databases by Atoll and the Atoll Management Console. It is also possible to upgrade an existing database manually. • • • • The relationships in the database schema figures are represented by arrows. for example). These templates are used for creating Atoll documents with the appropriate data structure required for planning for any technology. and required fields are in bold characters. the following are explained: • • • • • • • • "Atoll Database Templates" on page 45 "Atoll Management Console" on page 46 "Creating New Databases" on page 48 "Upgrading Existing Databases" on page 50 "Working With Multi-level Databases" on page 52 "Setting Database Access Privileges" on page 57 "Managing Data Modifications History" on page 57 "Using Oracle With Atoll" on page 60 5. archive and refresh data with databases.

see "Atoll Management Console" on page 46 and "Upgrading Existing Databases" on page 50. 46 . The Atoll Management Console runs using the Microsoft Management Console environment. 3. right-click the Database item under the Administration Atoll. The Atoll Management Console lets you: • • • • • Create databases (see "Creating New Databases" on page 48) Upgrade database structures from one major version to the next (see "Upgrading Existing Databases" on page 50) Work with multi-level databases (see "Working With Multi-level Databases" on page 52) Manage data modifications history in databases (see "Managing Data Modifications History" on page 57) Manage user accounts and access rights (see "Managing User Accounts and Access Rights" on page 67) The Atoll Management Console supports: • • Oracle Microsoft SQL Server The Atoll Management Console can be installed with Atoll. For more information on the Atoll Management Console and upgrading databases. The Data Link Properties dialogue appears. For more information. If you export the contents of an Atoll document. The context menu appears. you must register your database server in order to have the databases installed on the server to be available in the Atoll Management Console. Select Register a New Server. if you export a document connected to an Oracle database to SQL Server).0 Administrator Manual Chapter 5: Managing Databases © Forsk 2011 Atoll Field Type Float Double Integer Short Boolean Text Memo Binary Length 4 8 4 2 2 Variable* Variable Variable Oracle Equivalent Field Type FLOAT FLOAT NUMBER NUMBER NUMBER VARCHAR2 VARCHAR2 LONG RAW Length 32 64 11 6 1 Variable* 2000 Microsoft SQL Server Equivalent Field Type real float int tinyint bit varchar varchar image Length 4 8 4 1 1 Variable* 4000 16 Sybase Equivalent Field Type real float int tinyint bit varchar text image 16 Length 4 8 4 1 1 Variable* Microsoft Access Equivalent Single Double Long Integer Integer Yes/No Text* Memo OLE Object * Lengths for these fields are specified in parentheses in the database structure tables. To register a database server: 1. some field types will be converted according to the above table. respectively. This conversion does not have any impact on the document in Atoll. 2.2 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. 5. see "Installing Atoll and Components" on page 25. in the left pane. On the Provider tab. In the Atoll Management Console window. select the provider for your database server depending on whether it is Oracle or SQL Server.1. You can run the Atoll Management Console from the Windows Start menu program group or by double-clicking Atollmgmt. to another RDBMS (for example. Click the Provider tab.msc in the Atoll installation folder. When the Atoll Management Console is run for the first time.Atoll 3. already connected to a database.

and Version of the database. and the user name and password required to access the database server. you must create a new user owner of the database. Click Next. not yet upgraded to A master database may have one or more project databases created from and connected to it. • • The technology of the network modelled by the database. The current user may be the owner of one of the listed databases. Select Properties. enter the server name. The type of the database: master or project. 5. 2. ) or The right pane lists the databases available on the connected database server currently selected in the left pane. Click OK. right-click the database in the list. The context menu appears. Description.0 Administrator Manual Chapter 5: Managing Databases Figure 5. Figure 5. The path of the shared path loss folder. The selected database server is registered and available in the Atoll Management Console (see Figure 5. The following details are available for databases created or upgraded using the Atoll Management Console: • • Whether the database corresponds to the current Atoll version ( the current version. 47 . In the right pane. 3. The Properties dialogue contains two tabs: • • General tab: The General tab displays the Name.1: Data Link Properties dialogue . You now have access to the features offered by the Atoll Management Console. Registered database servers may be connected ( disconnected ( ).2 on page 47). For more information on master and project databases. Type. On the Connection tab. ) or a previous version ( ).2: Atoll Management Console The tree in the left pane lists the registered database servers. Statistics tab: The Statistics tab displays the number of records in each table of the database.Provider Tab 4. 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.1. To view details of a database: 1. Owner. The database Properties dialogue appears. For each new database. You can check to see if the entered information is correct by clicking the Test Connection button.AT310_AM_E2 Atoll 3. see "Working With Multi-level Databases" on page 52.

3 Creating New Databases New databases may be created using the Atoll Management Console or by directly exporting a document to a database from Atoll. The context menu appears. Figure 5.1 Creating a New Database Using the Atoll Management Console You can create new databases in Oracle and SQL Server using the Atoll Management Console. 2.0 Administrator Manual Chapter 5: Managing Databases © Forsk 2011 5. To create a new database: 1.3.1. You must have administrator rights to the database and to the server for creating new databases. right-click the database server on which you want to create a new database.3: New Database Wizard 48 . the following are explained: • • "Creating a New Database Using the Atoll Management Console" on page 48 "Creating a New Database Using Atoll" on page 49 5. in the left pane. The New Database Wizard dialogue appears. In this section.Atoll 3. In the Atoll Management Console window. Select New > Database.

The Ready to create database page appears. 5.1. Click Next. Upgrading such databases using the Atoll Management Console may take a long time because the Atoll Management Console must search for the data required for the upgrade in the whole database. To create a new database: 1. Click Next. and ATOLL_BUILD fields. enter the user name and password of the database owner. 7. Select a Transmission power unit and a Reception threshold unit.3. Enter a Name for the new database and select the Network type. Create a new Atoll document or open an existing one.e. 9. 11. the ATOLL_ADMIN table is used to speed up the database upgrade to the next version. 6. Select Document > Database > Export. The Network type can be one of the database templates installed with Atoll. For more information on upgrading databases. 2.. Select Use the current connection if you wish to create a new database using the current user. It is not added to Microsoft Access databases. Click Next. Click Next. The new database will be created from this document. The Atoll Management Console creates the new database with the defined parameters on the selected database server. 7. Click Execute. The Specify the database owner page appears. Master or Project) Atoll database template used to create the database An image of the schema of the original database Among other uses. see "Upgrading Existing Databases" on page 50. 8. The Export to a Database dialogue appears.AT310_AM_E2 Atoll 3. Run Atoll. This page provides a summary of the selected parameters. In the Export to a Database dialogue. 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. Click Save. The Specify units and coordinate systems page appears. Depending on the selected database type. ATOLL_VERSION.2 Creating a New Database Using Atoll You can create new databases in all supported RDBMS using Atoll. 5. The Name the database and specify a network type page appears. Atoll creates a new database based on the document. A database created using the Atoll Management Console contains an ATOLL_ADMIN table with the following structure: Field NAME DESCRIPTION ATOLL_VERSION ATOLL_BUILD ATOLL_DBTYPE ATOLL_TEMPLATE DBSCHEMA Type Text (50) Text (255) Text (10) Integer Text (10) Text (50) Memo Description The name of the database Description of the database The current version of Atoll Current build of Atoll Type of Atoll database (i. 10. 4. Atoll asks whether you wish to connect the document to the new database. Atoll and the Atoll Management Console must have the same version. select a Cartographic projection system and the System to be used in the database.0 Administrator Manual Chapter 5: Managing Databases 3. This means that the Atoll Management Console can create databases based on the database templates installed with Atoll of the same version. 6. with just the NAME. This table stores the data required by the Atoll Management Console for database upgrade. Under Coordinate systems. integer DB_RECORD_ID field. All the tables in a database created using the Atoll Management Console (except the COORDSYS and UNITS tables) contain a non-modifiable. select the database type in the Save as type list. This field is used to store the ID of every record in the table. A database created using Atoll contains an ATOLL_ADMIN table with the following structure: 49 . 4. 5. instead of the Atoll Management Console. Databases created with Atoll. Click Yes or No. and databases that have never been upgraded using the Atoll Management Console contain a smaller ATOLL_ADMIN table. 3.

You can use the ODBC interface (used by Sybase as well) to access all databases that accept UDL files and the ODBC interface. If you skip or have skipped an intermediate major version. group the radios of the same series under the same radio series name in the FAMILY field.0 Administrator Manual Chapter 5: Managing Databases © Forsk 2011 Field NAME ATOLL_VERSION ATOLL_BUILD Type Text (50) Text (10) Integer Description The name of the database The current version of Atoll Current build of Atoll • • • • Before creating the database.. Before creating the database.1. see "Upgrading Databases for the First Time" on page 52 first. make sure that you have added any required custom fields. data structure changes must be made in the database in order to support the new features added in the version. To upgrade a database using the Atoll Management Console: 1. If you want to add a custom field to the data structure after you have created the database. Upgrading your database will be simpler if you do not skip a major version. Select Upgrade Database. you will have to add it directly in the database and not through Atoll. i.INI\Sybase Where "Sybase" represents the logical name used for the ODBC connection. For example. you must upgrade your database twice in order to make it compatible with the new version. The Database Upgrade Wizard displays the current database version and the version to which the database will be upgraded. 2.e. Add a "string" called "WorkArounds2" in: HKEY_CURRENT_USER\Software\ODBC\ODBC. 50 . i.. 5. make sure that you have defined the coordinate systems and units in the source document. Open the Windows registry using regedit. 2. The data structures of standalone Atoll documents. documents not connected to any database are upgraded when they are opened in the new Atoll version.Atoll 3. i. If you are upgrading a database which was neither created nor already upgraded (at least once) using the Atoll Management Console.exe.0 database using the ODBC driver: 1.4 Upgrading Existing Databases In each new major release.1. In the Atoll Management Console window.x before upgrading to Atoll 3. Enter the radio series names in this field for each radio. 3.x.8. WorkArounds2 = 152. Custom fields of the source document are created in the new database. 2. Assign the value "152" to "WorkArounds2". The Microwave Radio Links template now supports Radio Series. you should first upgrade the database to Atoll 2.e. Similar microwave radios belong to the same radio series. right-click the database that you want to upgrade. The Database Update Wizard dialogue appears.x. Without this manual organisation of the microwave radios into radio series. In order to be able to archive to and refresh data from a Sybase 12. add a custom field named FAMILY of type Text (50) to the MWEquipments table. if you are currently using Atoll 2. In order to organise the microwave radios (microwave equipment) in radio series before the database upgrade: 1.x. 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.7. Do not skip a major Atoll version. You can upgrade Oracle and SQL Server databases using the Atoll Management Console.e. The context menu appears..5. the database upgrade will create one radio series for each microwave radio. In Atoll 2.8. in the right pane.

1. 5. and saving it in the new version. If there is more than one template corresponding to the network. For information on manually upgrading a database. it is highly recommended to use the Atoll Management Console for upgrading existing databases. 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. for example. refresh. see "Upgrading Databases Manually" on page 52. Once disconnected from its database. the Database Upgrade Wizard asks to select the views to upgrade. 1. 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.0 Administrator Manual Chapter 5: Managing Databases 3. It is also not possible to interact with the upgraded database (archive. 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. Click Next. The Database Upgrade Wizard reads the database to determine the Atoll database template using which it was created. If you use the Atoll Management Console’s history management tool. When users open their existing documents in the new Atoll version. If. The Atoll Management Console upgrades the database. Ask all the end-users to fully refresh data in their Atoll documents from the database. To make the document write-accessible in the previous Atoll version. The wizard first upgrades the schema of Table1 and then upgrades the definition of the view. Atoll upgrades the document data structures to make them compatible with the new version. Obsolete fields in the data structure are automatically deleted from the database by the Atoll Management Console during the upgrade. • • • • • It is possible to upgrade an existing database manually (not recommended) by adding and deleting tables and fields as required by the new 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. see "Managing Data Modifications History" on page 57. For more information. Once the database has been upgraded to 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 not possible to reconnect the document to any database. the definition of a view is given by the condition: Select Field1. are not allowed). you must repair the upgraded database in order to continue using this tool. 51 . or • Upgrading the database to the new version and then opening and saving the document in the new Atoll version. Field2 from Table1 where (Condition1). disconnecting it from the database. it must be disconnected from the upgraded database. Click Next. 4. etc. However. The upgraded definition will take the newly added fields into account. and 2. Enter a Name and description for the database. Install the new Atoll versions for the end-users. Select the views that you want the Atoll Management Console to upgrade and click Execute. it is possible to open the document in the previous Atoll version as read-only. select the template to be used for the upgrade and click Next. The Name the database page appears. If some of the tables in a database have been replaced by views. due to the complex nature of the upgrade process.AT310_AM_E2 Atoll 3.. On selecting the upgrade option.

Create a new database as explained in "Creating a New Database Using Atoll" on page 49.dll again. Install the new version of Atoll and the Atoll Management Console. Upgrade the database (as described in "Upgrading Existing Databases" on page 50).dll. Upgrade the database (as described in "Upgrading Existing Databases" on page 50) using the Atoll Management Console to the existing version of Atoll. For the Atoll Management Console to be able to recognize obsolete or deleted fields from database tables. Once the Atoll Management Console has performed the necessary modifications. 52 . If you have already installed the new version of the Atoll Management Console. and the database administrator manages the connections and data exchange between the project databases and the master database.5 Working With Multi-level Databases Atoll Management Console allows you to set up and work with multi-level databases. the setup overwrites the Windows registery key that stores the information about the Admin. and the existing version of the Atoll Management Console can no longer be used. The Atoll Management Console adds additional fields to the ATOLL_ADMIN table and DB_RECORD_ID fields in all the tables. Once the Atoll Management Console has been used to upgrade a database. Before installing the new version of Atoll. as described in "Creating a New Database Using the Atoll Management Console" on page 48. f. you will have to register the old Admin. and upgrade the database to the new version using the new Atoll Management Console. Open the disconnected document of the previous Atoll version. register the new Admin. In this optional database architecture. When a new version of the Atoll Management Console is installed. the master database is not directly accessible to end-users. e. the database administrator will have to remove the obsolete fields manually. Save and close the document. upgrade the database to the existing version. using the new version of the Atoll Management Console. The end-users archive data to and refresh data from their respective project databases. Upgrading Databases Manually This procedure is for information only. 5. If you are upgrading your database using a script based on the data structure modifications listed in Part 3 of the Administrator Manual. automatic upgrade of the database using the Atoll Management Console is not possible. it will be able to recognize obsolete or deleted fields in the following upgrades. This means that when upgrading a database for the first time using the Atoll Management Console. • Using the previous Atoll version: a. • Using the new Atoll version: d. b. Disconnect the document from the database. you must also add the ATOLL_ADMIN table to the database. Create a new document from the database. c. see "Creating a New Database Using the Atoll Management Console" on page 48.dll file.0 Administrator Manual Chapter 5: Managing Databases © Forsk 2011 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. To upgrade the database: 1. install the Atoll Management Console (if not already installed) compatible with the existing version of Atoll.1. Groups of end-users work with their respective project databases which are in turn connected to the master database. It should used if and only if. 4. 2. For more information on this table. Atoll upgrades the document data structure to make it compatible with the new version. it is imperative that the ATOLL_ADMIN table exist in 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. 3. you can upgrade the database to the new Atoll version. you must first upgrade the database to the same version as the current version of the database. for some reason.Atoll 3. to the new version of Atoll.

5: Working With Project Databases Project databases can be used to improve performance and ensure data security and reliability. if a country-wide network database is accessible to all end-users: • • • • The probability of human error increases with the number of users who can modify data. End-users can here work with their local region’s project database. only its accessible copy is modified in the project database. For example. For routine city-wide planning. A project database contains the original master database. Instead allowing all the endusers to work directly with the master database.0 Administrator Manual Chapter 5: Managing Databases For example. an end-user does not require the entire country’s database to be loaded. thus allowing users to work with regional databases. When a user modifies a record. Creating and working with project databases restricts the number of users who have access to the master database.AT310_AM_E2 Atoll 3. Project databases may be created using filters on sites. you may have a country-wide master database and more than one regional project databases. and an copy of the master database accessible to the endusers. that remains hidden from the end-users. This reduces the risk of conflicts in the database as only the database administrator can archive modifications from project databases to the master database. and would not have to unnecessarily load country-wide data. one or many project databases may be created with copies of the entire master database or a part of the master database corresponding to a given physical location or region.1. Figure 5.4: Working With a Single Level Database Project databases are intermediate databases created from a common master database. The probability of conflicts increases with the number of users accessing the database. Figure 5. 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. The performance is reduced because the entire network is loaded every time a user accesses the database. A possible scenario is depicted in the figure below: 53 .

Click Next. The context menu appears. In this section. Select Create a Project Database. On this page. To create a project database from an existing master database: 1. 6. you must have enough rights to be able to create new tables in the master database schema. 8. Click Next. 2.6: Multiple Project Databases From a Single Master Database Multi-level databases may be set up using the Atoll Management Console with Oracle. 5. Some versions of Oracle let you create a new user through this dialogue but the new user is not assigned DBA rights. 3. In the Atoll Management Console window. choose from one of the following options: • Include all the sites of the master database 54 . The Project Database Creation Wizard dialogue appears. Enter a Name and Description for the new project database. The Name the database page appears. For creating a project database. Under Owner.5. 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.1 Creating Project Databases You can create project databases using the Atoll Management Console with Oracle.0 Administrator Manual Chapter 5: Managing Databases © Forsk 2011 Figure 5. 9. in the right pane. 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. The Specify the server and the owner of the project database page appears. select Current user if you wish to create the new project database using the current user. the following are explained: • • • "Creating Project Databases" on page 54 "Archiving Project Databases to Master Databases" on page 56 "Refreshing Project Databases from Master Databases" on page 57 5. 7.1. The Specify the sites to include in the project database page appears. which makes the new user unable to create the project database. 4. right-click the master database from which you wish to create a project database. Therefore. Click Next.Atoll 3. Select the Destination server for the project database.

The project database will have the type PROJECT listed in the Atoll Management Console window. • Include a site list contained in the master database Select this option if you wish to create a project database containing the network data corresponding to the sites included in a site list of the master database. with the following structure: Field NAME MASTER_CONNECTION MASTER_DBSCHEMA SEL_METHOD SEL_PARAM SEL_PGON Type Text (50) Text (255) Text (50) Short Text (255) Memo Description The name of the project database Connection parameters to the master database The name of the original schema of the master database Data extraction method used to select the sites to include in the project database Site selection method parameters (the SQL condition. The Atoll Management Console creates the new project database with the defined parameters on the selected database server. and select the file containing the polygon to use. in addition to the ATOLL_ADMIN table. 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 Select this option if you wish to create a project database containing the network data corresponding to the sites that verify an SQL condition (for example. 10. if any) Site selection polygon (if used) 55 .7: New Project Database Wizard A project database created using the Atoll Management Console contains an ATOLL_ADMIN_PRJ table.0 Administrator Manual Chapter 5: Managing Databases Select this option if you wish to create a project database that contains all the data of the master database. sites that have a common parameter or flag). and enter the SQL condition. Click Next. • Include the sites contained within a polygon contained in a file Select this option if you wish to create a project database containing the network data corresponding to the sites that are located inside a polygon. Figure 5. and select a site list.AT310_AM_E2 Atoll 3.1.

This may 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. 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. To view the above details of a project database: 1. The O_RECORD_ID field is used to locate records in the master database. For example. 2. All the tables in a project database contain a non-modifiable. Select the check boxes to the left of the changes that you wish to undo and click Undo Sel.Atoll 3. the ANTENNAS table of the master database is stored in the project database under the name O_ANTENNAS. Type. The Properties dialogue contains three tabs: • • General tab: The General tab displays the Name. and Version of the database. In the right pane. Click Archive All to archive all the changes to the master database. right-click the project database from which you wish to archive changes to its master database. The database Properties dialogue appears. • The project database contains a copy of all the original tables of the master database. Statistics tab: The Statistics tab displays the number of records in each table of the project database. Description. integer O_RECORD_ID field and a Boolean O_CHANGED field. the Archive dialogue appears.0 Administrator Manual Chapter 5: Managing Databases © Forsk 2011 You can view the details stored in the ATOLL_ADMIN_PRJ table in the project database properties.8: Archiving Changes in Master Databases 56 . the Project Database tab displays the Connection settings to and the Owner of the master database. The O_CHANGED field is set to TRUE for records modified in the project database. Owner. The names of the original tables are prefixed with "O_". The context menu appears. The Archive dialogue lets you select changes you want to archive. The COORDSYS and UNITS are not copied to the project database because their contents cannot be different from those of the master database. If pending changes exist. Modified records are archived in master database using the O_RECORD_ID of the project database and DB_RECORD_ID of the master database. to archive only the selected changes. The context menu appears. The Archive dialogue lists the records of the project database for which the O_CHANGED field is TRUE. this tab displays the site filtering Method and Settings used for creating the project database. right-click the project database in the list. to overwrite only the selected changes in the project database with data from the master database. Click Undo All to overwrite all the changes in the project database with data from the master database. in the right pane. 3. 2. Select Archive. Select the check boxes to the left of the changes that you wish to archive and click Archive Sel. In the Archive dialogue. To archive the changes from a project database to its master database: 1. Select the Check conflicts check box to see whether conflicts occurred during the archive. 3. In the Atoll Management Console window.1. Project Database tab: Under Source master database.5. 5. Select Properties. you can do the following: • • • • • • Select a site list in Filter by site list to filter the pending changes by a site list.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. Under Site selection. Figure 5.

on external table references. all the tables available in an Atoll database must be readable by all the users who have access to the database. UPDATE) may be granted on a limited number of tables. click Close.0 Administrator Manual Chapter 5: Managing Databases Under Errors. 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. Database roles enable you to define permission templates. Column. Click OK. in the right pane. To refresh a project database with data from its master database: 1.1. or on the geographic locations of sites (e. Transmitters. Table. through polygons. NeighboursExt 57 . Neighbours. For more information on managing user access rights. The history management tool keeps track of all the modifications made in the following Atoll tables: Technology GSM GPRS EDGE UMTS HSPA LTE Tracked Tables Sites. Neighbours. The context menu appears. see "Managing User Accounts and Access Rights" on page 67. • Row Level: Row level permissions can be set by defining custom views on Atoll tables. INSERT.5. the Refresh a Project Database dialogue appears. The list can be limited to a few databases based on the user connection properties (log in).AT310_AM_E2 Atoll 3. If pending changes exist. 3. TRXs. In the Refresh a Project Database dialogue. Triggers can also be used to prevent users making certain actions on the database. • Column Level: Similar to table level. You can grant user privileges for Database..g. NeighboursExt Sites. and DELETE privileges on database objects. 5. During the refresh. Access to these views can be based on user connection properties (log in). T4GCells. or when using the spatial features of databases). UPDATE. DELETE. For example. 2. 5. write access (INSERT. Once archive is complete. SecondaryAntennas. Neighbours. 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. right-click the project database that you wish to refresh with data from its master database.6 Setting Database Access Privileges You can assign different levels of privileges to different users for accessing (reading/writing) tables and views of a database. Repeaters. Different permissions for different users can be granted directly or through database roles. Repeaters. you can: • Select Refresh unmodified data only to keep any changes in the project database and only update unmodified records from the master database. Atoll Management Console displays errors that occurred during archive. SecondaryAntennas. Transmitters. You can use the Atoll Management Console for defining user access rights to database tables and elements in the Atoll GUI. the Atoll Management Console will reload records from the master database for which the O_CHANGED field is FALSE in the project database. custom fields may be assigned read and write permissions without restrictions.3 Refreshing Project Databases from Master Databases Project databases can be refreshed with data from the master database using the Atoll Management Console. which can then be assigned to existing or new users of the database. Repeaters. 5. 4. 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. The project database is refreshed with data from the master database. Different write permissions may be granted for columns of the tables. All of these permissions can be set as regular SELECT. • Table Level: For consistency reasons. NeighboursExt Sites. SecondaryAntennas. Transmitters. TRGs. Select Refresh. CDMACells. However. • 1.7 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. In the Atoll Management Console window.

WCells.7. Each history table has the same structure as the corresponding tracked table. NeighboursExt Sites. 58 . In the Atoll Management Console window. MWHubs. Data modifications history is enabled for the database. NeighboursExt Sites. 2. but with the following four additional fields. For each tracked table. MWPMP. in the right pane. MWMultiHopsLinks. The Data Modifications History Management dialogue appears. If you wish. The context menu appears. the Atoll Management Console adds new tables to the database structure. and the type of modification.9 on page 59). Transmitters. see "Enabling/ Disabling Data Modifications History Management" on page 59. the total numbers of records in these tables.1 Setting Up Data Modifications History Management When you set up history management for any database. All the modifications made in the tables listed in "Managing Data Modifications History" on page 57 are stored in the history tables added to the database. however. you can disable the data modifications history management for any table. Repeaters. opening any tracked table. SecondaryAntennas. you can see when a record was last modified. 5.16e Microwave Radio Links Tracked Tables Sites. it opens the Data Modifications History Management dialogue (Figure 5. The history management tool is available for Oracle databases. This dialogue lists all the tables for which the data modifications history management has been enabled. enable or disable history management for table as required (see "Enabling/Disabling Data Modifications History Management" on page 59 for more information). Repeaters. Select Manage Data Modifications History. Neighbours. right-click the database for which you wish to set up data modifications history management. To set up data modifications history management for a database: 1. Therefore. and the status of the history management.0 Administrator Manual Chapter 5: Managing Databases © Forsk 2011 Technology CDMA2000 1xRTT 1xEV-DO WiMAX 802. MWMultiHops. Transmitters. The following section describes how to set up the history management tool for an Oracle database using the Atoll Management Console. you can also purge old data modifications history (see "Purging Old Data Modifications History" on page 60 for more information). SecondaryAntennas. it adds a corresponding history table that has the same name as the tracked table with the suffix "_H". Click Yes when asked whether you wish to make your database compatible with the data modifications history tool. Once finished. by whom. CDMACells. MWRepeaters You can. These fields enable the Atoll Management Console to store the modifications made by users to each tracked table: Field HISTORY_ID MODIFIED_BY MODIFIED_DATE HISTORY_STATUS Type Integer Text (50) Date Text (10) Description A unique ID of the modification history record The user who made the modification The date when the modification was made 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. If you wish. MWLinks. For more information. Neighbours. The Atoll Management Console updates the database structure to make it compatible with the data modifications history tool.Atoll 3.1. 3.

right-click the database whose tables you wish to update. either automatically upgrading your database using the Atoll Management Console. Select Manage Data Modifications History. In the Atoll Management Console window. 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. the MODIFIED_BY. The context menu appears. right-click the database for which you wish to disable data modifications history management.1.3 Updating After Data Structure Upgrade When you modify the structure of a tracked database table (for which data modifications history management is enabled). In the Atoll Management Console window. Select Manage Data Modifications History. The Status in the Data Modifications History Management dialogue is set to OK for this table. The context menu appears.7. In the Data Modifications History Management dialogue. 3. in the right pane. 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. Select Disable in the context menu. The Data Modifications History Management dialogue appears. In the Data Modifications History Management dialogue. and a copy of each modification is stored in the history table corresponding to the table. or by modifying a field type. 2. The context menu appears. 59 . 4. 2. The Data Modifications History Management dialogue appears. The Data Modifications History Management dialogue appears. the corresponding data modifications history management table becomes invalid and has to be updated to match the new structure of the tracked table. right-click the table for which you wish to enable data modifications history management. in the right pane. 4. 5. right-click the database for which you wish to enable data modifications history management. the MODIFIED_BY. In the Atoll Management Console window. To disable data modifications history management for a table: 1. 2. Select Enable in the context menu. To update the data modifications history management tables: 1. or manually by adding or removing fields. right-click the table that you wish to update. The context menu appears. In the Data Modifications History Management dialogue. When history management is enabled for a table. Data modifications history management is now enabled for this table. and HISTORY_STATUS fields are updated with each modification. Select Manage Data Modifications History.2 Enabling/Disabling Data Modifications History Management You can enable or disable data modifications history management for any table.7. The context menu appears. MODIFIED_DATE. 3. The Status in the Data Modifications History Management dialogue is set to Deactivated for this table. 3. When history management is disabled for a table. right-click the table for which you wish to enable data modifications history management. To enable data modifications history management for a table: 1. in the right pane. The context menu appears. You can enable or disable history management for each individual table. History management is now disabled for this table.AT310_AM_E2 Atoll 3.9: Data Modifications History Management Dialogue 5.0 Administrator Manual Chapter 5: Managing Databases Figure 5.

8 Using Oracle With Atoll This section provides additional information about using Oracle databases with Atoll. All the history records before the selected date are deleted from the history table. define the service name "AtollDB". 5. Figure 5.ora file to enable communication with the Atoll database. To set up an Oracle database for use with Atoll: 1. 3. select the Keep creation and deletion records check box if you wish to keep the records of creation and deletion. In the Atoll Management Console window. Create an empty database.1. 2. The Record Purge dialogue appears (Figure 5. Number of records shows the number of records that will be left after the purge.e. right-click the database in which you wish to purge old data modifications history. The context menu appears. The context menu appears. Select Install/Repair in the context menu.4 Purging Old Data Modifications History All the modifications made by all the users are stored in the history management tables. purge old data modifications history (records) from these tables in order to gain space. i. The service name "AtollDB" must be specified to: • • • Export an Atoll document to an Oracle database (Server = Service name) Open an Atoll document from an "AtollDB" database (Server = Service name) Use Oracle tools to manage the "AtollDB" database (Host name = Service name) 60 . the database name "AtollDB" and SID "AtollDB" will be used. In the Data Modifications History Management dialogue. 4. 5. Under Options. these tables may quickly become very large and may require a lot of disk space. right-click the table for which you wish to purge old data modifications history. All the data modification history records before this date will be deleted. Select Purge in the context menu. creation and deletion records before the selected date are not deleted. If you selected the Keep creation and deletion records check box.7. to store the schema and data that will be created afterwards. Add an entry in the tnsnames. Therefore. Click Purge. 7.. 2. Under Purge data modifications recorded before. move the slider to select from which date onwards you wish to keep the data modification history records. in the right pane. The Atoll Management Console repairs the data structure of the history management table to match the structure of the corresponding tracked table. 3.10 on page 60). The Data Modifications History Management dialogue appears. Select Manage Data Modifications History. To purge old data modifications history from a history management table: 1.10: Record Purge Dialogue 5. In the following. You can. Data size shows the size of the records that will be left after the purge. 6.0 Administrator Manual Chapter 5: Managing Databases © Forsk 2011 4. if you wish.Atoll 3. Install Oracle on the database server and client computers.

In some cases. Create a new user (project account) with administrator rights and privileges. setting the display precision of floating point values the Atoll. These user accounts do not own tables. The database will be accessible through any of the user accounts from any client computer. UMTS. It is usually helpful to assign a name to the project account that indicates the type of project that you want to store (GSM. updating the field data by rounding the values stored in them: UPDATE TABLE_NAME SET FIELD_NAME = ROUND(FIELD_NAME. etc. This account will be used to create Atoll document tables and will be the owner of these tables. To create a new user. d. If the database fields contain data. 5. You can fix this problem by: • • In Atoll. Open the Add Database to Tree dialogue. right-click the User folder in the Security folder and select Create. Enter Username = "system" and Password = "manager". g. h. select Add selected databases from your local tnsnames.).ini option described in "Setting the Display Precision of Floating Point Values" on page 175. Atoll displays too many decimal values for fields of type "Float" in documents connected to Oracle databases. g. Select the "AtollDB" service. Open the Add Database to Tree dialogue. b. but only specify the access rights to the tables owned by the project account. To create a new user. right-click the User folder in the Security folder and select Create.. Create a project account. b. Once this is done.ora file. changing the field type from Float to Number and fix the number of decimal values for it in Oracle. 61 . Run DBA Studio on the database server (or a client computer with Oracle administration tools). 7. e. i. Create user accounts. select Add selected databases from your local tnsnames. Specify "Atoll" as the default tablespace for the new user accounts. f. c.AT310_AM_E2 Atoll 3. you have to refresh document data from the database in order to fix the display problem in Atoll. In the Add Database To Tree dialogue. In Oracle. This type of display is not due to any error in Atoll. h. Select the "AtollDB" service. Specify "Atoll" as the default tablespace and choose DBA for its privileges. For more information. • • If the database is new and the fields are empty. Open the connection dialogue for the "AtollDB" service. f.0 Administrator Manual Chapter 5: Managing Databases 4. see "Creating a New Database Using Atoll" on page 49. In the Add Database To Tree dialogue. Log on with the project account. 6.2). c. d. Create new user accounts with appropriate rights and privileges. To create a project account: a. e. To create a project account: a. Create database tables in the empty database "AtollDB" using the project account created in step 5.1. Open the connection dialogue for the "AtollDB" service.ora file. Create a tablespace called "Atoll". i. Run DBA Studio on the database server (or a client computer with Oracle administration tools).

SITES. SQL > drop table AtollADMINUMTS. password = ADMINGSM UMTS Project account = AtollADMINUMTS. SQL > grant delete on AtollADMIN.Atoll 3. SQL > create view AtollADMINGSM.1. 2.SITES.9.SITES to AtollADMINUMTS with grant option.SITES table and copy all sites from AtollADMINGSM. SQL > drop table AtollADMINGSM. SQL > grant insert on AtollADMIN.SITES.SITES to AtollADMINUMTS with grant option.SITES to AtollADMINGSM with grant option. you must log on as the owner of the tables through SQL Plus 8. SQL > grant update on AtollADMIN.SITES view. SQL > create table AtollADMIN.SITES to AtollADMINUMTS with grant option.SITES. or to restrict the connection to a set of transmitters for some users (example 2).SITES.SITES to AtollADMINUMTS with grant option.1 Appendix 1: Advanced Customisation You can use SQL in order to manage access to and share the Sites table (example 1). SQL > connect AtollADMINUMTS/ADMINUMTS@AtollDB. 4.SITES as select * from AtollADMINGSM. SQL > create unique index AtollADMIN_SITES on AtollADMIN. 3.SITES. SQL > grant select on AtollADMIN. 62 .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.SITES to AtollADMINGSM with grant option. Add a ‘POSTCODE’ field to the SITES table. SQL > grant delete on AtollADMIN. Create the AtollADMIN. Rename the SITES table to be able to hide it by a view. SQL > connect AtollADMINGSM/ADMINGSM@AtollDB. SQL > alter table SITES add (POSTCODE number). 2. SQL > connect AtollADMIN/ADMIN@AtollDB. Replace the AtollADMINGSM. Follow the same procedure for UMTS (AtollADMIN.SITES to AtollADMIN. SQL > connect AtollADMIN/ADMIN@AtollDB.SITES already created). SQL > grant insert on AtollADMIN. SQL > grant update on AtollADMIN. Example 1: Managing Site Sharing Assumptions: • • • • Connection string = AtollDB GSM Project account = AtollADMINGSM. 5. password = ADMIN To share the Sites table: 1. SQL > grant select on AtollADMIN.SITES table by an AtollADMINGSM. Commit.0 Administrator Manual Chapter 5: Managing Databases © Forsk 2011 5. password = ADMINUMTS Common Project account = AtollADMIN. SQL > commit.SITES to AtollADMINGSM with grant option. SQL > create view AtollADMINUMTS. SQL > connect AtollADMIN/ADMIN@AtollDB. Example 2: Managing Users by Postal Code To restrict access to transmitters for some users by postal code: 1. To implement the following two examples.SITES as select * from AtollADMIN.SITES as select * from AtollADMIN.SITES to AtollADMINGSM with grant option.SITES(NAME).

TD-SCDMA. SQL > create view TRANSMITTERS as select * from PRIVATE_TRANSMITTERS where SITE_NAME in (select NAME from SITES). In the following. 63 .9. i. i. and WiMAX). the second requires setting up sharing of the Sites table between the databases of the two technologies being co-planned.. SQL > insert into POSTCODETABLE values (‘USER1’. In other words. 2. by linking Atoll documents. Open the GSM document in Atoll. SQL > create table POSTCODETABLE (USERNAME varchar2(30).2 Appendix 2: Setting Up Databases for Co-planning Two co-planning approaches are possible in Atoll: • • Co-planning GSM. Co-planning any two radio technologies (GSM. SQL Server. and LTE using a unified multi-technology data structure. Create a POSTCODETABLE table to link users and postcodes (one user may be linked to several postcodes). The error message "ORA-01402: view WITH CHECK OPTION . exist in the databases.. we assume that the Sites tables of the GSM and UMTS documents contain the same data and that two users. SQL > rename TRANSMITTERS to PRIVATE_TRANSMITTERS. 75). or Sybase: 1. POSTCODE number). Create a view owned by this user hiding the actual SITES table through these commands. This section describes table sharing between GSM and UMTS. so that Atoll can only select transmitters whose associated sites are present in the SITES view. You can fill this table using this instruction. named GSMUser and UMTSUser in this example. Hide the TRANSMITTERS table. while the first approach provides an integrated multi-technology co-planning environment. CDMA2000. SQL > commit.1. 4. UMTS. LTE. 3.0 Administrator Manual Chapter 5: Managing Databases SQL > rename SITES to PRIVATE_SITES. "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. 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.e.AT310_AM_E2 Atoll 3. 5. working with a 3GPP Multi-RAT document. with two separate data structures. SQL > create view SITES as select * from PRIVATE_SITES where POSTCODE in (select POSTCODE from POSTCODETABLE where USERNAME =USER) with check option.e. 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. Delete all the transmitters from the Transmitters table and all the sites from the Sites table. In terms of database. 5. 6. UMTS. Commit. the Sites and Antennas tables.clause violation" appears if you try to archive a record that does not match the project. 3. Make backups of the GSM and UMTS documents. To set up a shared Sites table for a GSM-UMTS co-planning project in Oracle. the Sites tables in the databases of the two technologies must be views of a common Sites table.

Enter UMTSUser as the name of the schema you want to use.1 on page 231 shows the relations of the Sites table with other tables in a GSM database.Atoll 3. Export the UMTS document to a Microsoft Access database (UMTS.0 Administrator Manual Chapter 5: Managing Databases © Forsk 2011 4.mdb). 9. 13. If a user archives the changes made in one document but forgets to archive the changes made in the other. The Link Tables dialogue appears. Delete. Export the GSM document to a Microsoft Access database (GSM. To ensure database consistency. In Microsoft Access 2003 and earlier. a.mdb in Microsoft Access. Open the GSM document in Atoll. Log in as UMTSUser to the database. 64 . 14. Atoll automatically saves or archives the other. The Create View dialogue appears. Select the Sites table. 2.mdb which is linked to the Sites table in UMTS. 5. we propose to replace the GSM Sites table with the UMTS one. b. select File > Get External Data > Link Tables.mdb. Delete all the transmitters from the Transmitters table and all the sites from the Sites table. To set up a shared Sites table for a GSM-UMTS co-planning project in Microsoft Access: 1. 10. Delete the Sites table. Right-click the Sites table and select Create a View from the context menu. and Select. 3. 11. 6. Open GSM. Select Sites as the object used to model the view. Therefore. this may create inconsistencies between the two networks. Enter Sites as the view name.mdb. 10. you may save or archive the linked documents at the same time. Click Create. 12. 5.mdb). d. Select Table as object type.mdb in Microsoft Access.mdb as data source and select Link to data source by creating a linked table. Figure 13. select External Data > Access Database. The tables contain the same data. In Microsoft Access 2003 and earlier. 7. Open the UMTS document in Atoll 8. 7. 8. Update. specify UMTS. the Link dialogue appears. 9. Enter GSMUser as the name of the schema which will contain the view. Log in as GSMUser to the database. the Get External Data . Set up user privileges for the Sites view in GSMUser to allow each user to Import. Ensuring Database Consistency Between Linked Documents When users work with two Atoll documents and databases at the same time. 4. c. i. The UMTS Sites table has more fields compared to the GSM Sites table. 11. Click OK. Make backups of the GSM and UMTS documents. Delete the Sites table.. Open GSM. you have to define the relations of this table with the other tables in the database. Once the linked Sites table has been created in the GSM database. Microsoft Access creates a Sites table in GSM.1. This can be done using a macro triggered by the save or archive operation. The view of the Sites table from UMTSUser is created in GSMUser. Select UMTS. when a user saves or archives one document. Export the GSM document to the database by entering the user name and password for GSMUser. The GSMUser Sites table is now the same as UMTSUser Sites table. Click OK. it is important to have a protection mechanism against database inconsistencies. In Microsoft Access 2007 and later.Access Database dialogue appears. e. 6. In Microsoft Access 2007 and later. Export the UMTS document to the database by entering the user name and password for UMTSUser.e. Open the UMTS document in Atoll. 12.

Figure 6. For more information. As the users work on the network and archive changes in the database. see "Appendix 1: Checking Data Integrity" on page 71. For more information. In this chapter. different user groups may work on different regions of a country-wide network. see "User Atoll Documents" on page 67. 6. 5. Create the private path loss matrices folder for the master Atoll document and calculate the private path loss matrices.0 Administrator Manual 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. For more information.1 Setting Up Multi-user Environments The general process of setting up a multi-user environment is described below. Export the master Atoll document to a new database and keep the document connected to the new database. groups of users may work on specific parts of a common. 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. 2. see "Shared Path Loss Matrices" on page 67.1: Components of Multi-user Environments 65 . see "Master Atoll Document" on page 66 and "Shared Geographic Data" on page 66. large-scale project. 3. Create user Atoll documents from the master database. For more information. the Atoll administrator should regularly run data integrity checks on the master Atoll document after loading modified data from the master database. 1. In large. structured multi-user environments. see "Master Database" on page 66. • • The Atoll administrator should regularly update the shared path loss matrices. 4. the following are explained: • • • "Setting Up Multi-user Environments" on page 65 "Components of Multi-user Environments" on page 65 "Managing User Accounts and Access Rights" on page 67 6.1 on page 65 shows the components of a multi-user environment.AT310_AM_E2 Atoll 3. Each component is described in detail in "Components of Multi-user Environments" on page 65. For example. For more information. Create the master Atoll document with the required network data and geographic data. sharing data over a network. In the user Atoll documents.2 Components of Multi-user Environments Figure 6.1.

However. for example). this is not the case with other RDBMS.Atoll 3. However. For more information on regionalisation. Custom fields added in an Atoll document connected to a Microsoft Access database are automatically added to the database. An empty database can also be created using the Atoll Management Console. If you wish to add custom fields in the Atoll document. see "Creating a New Database Using Atoll" on page 49). prediction definitions. For more information on database management. The administrator can set up different user configuration files (CFG) for separate user groups. one master document per region). such as Oracle. and it is recommended that these be stored externally and not embedded in Atoll documents. for example). The recommended database server configuration is provided in "Recommended Hardware and Software" on page 22. transmitters. see "Appendix 2: Database Regionalisation" on page 71. User configuration files can be shared and exchanged between users working on the same project. Geographic data files are usually large files. see "Configuration Files" on page 141. see "Managing Databases" on page 45. a GSM database and a UMTS database can be stored on the same database server using the same RDBMS (Oracle.2 Master Database The master database stores the radio network data shared by all the end-users. sites. and populated with data later on (for more information. User configuration files (CFG or GEO) are used to store the parameters related to geographic data.1 Master Atoll Document It is the source Atoll document that contains the entire project’s network data. For more information. measurements can be stored in user configuration files (see "Configuration Files" on page 141 for details). The recommended file server configuration is provided in "Recommended Hardware and Software" on page 22. zones. For large networks. i.1. 6. you can also work with more than one master Atoll document (for example..2. you can subdivide the network’s master database into regions. traffic maps. Geographic data are usually located on file servers and linked to the document. etc. It is possible to load a user configuration file automatically when running Atoll. The private path loss matrices of this document are used as shared path loss matrices by the end-users. The master Atoll document allows the administrator to globally manage all the data shared by the end-users. For example.0 Administrator Manual Chapter 6: Multi-user Environments © Forsk 2011 In this section. Master Atoll documents should not have redundant radio network data (same sites. and then update your Atoll document from the database. the multi-user environment set up remains the same. The shared path loss matrices folder is usually located on a file server accessible to all the users on the network. It is created and maintained by the Atoll administrator. Only radio network data are stored in the database.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. see "Atoll Command Line Parameters" on page 31. For exceptionally large networks. 66 . User configuration files can be created so that only the geographic data required by a user are loaded. 6. folder configurations. The same database server can be used to store one or more master databases corresponding to different technologies. Parameters related to geographic data files. For more information. 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. see "Creating a New Database Using the Atoll Management Console" on page 48). The document also contains the required geographic data for path loss calculations. It can be created by exporting the radio network data in the master Atoll document to a database from Atoll (for more information. This document is initially used to create the radio network database with which all the end-users work. antennas.e.2. see "Appendix 2: Database Regionalisation" on page 71. For more information on regionalisation.2. and should ideally cover different geographical regions. you should first add the field in the database. not embedded in the ATL file. the following are explained: • • • • • "Master Atoll Document" on page 66 "Master Database" on page 66 "Shared Geographic Data" on page 66 "Shared Path Loss Matrices" on page 67 "User Atoll Documents" on page 67 6. their paths.

For more information on regionalisation. the regionalisation should be set up before creating the user documents. edit user account information.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. For more information. end-users are not allowed to modify the shared path loss matrices. This task can be carried out using a macro. for example edit clutter or traffic in their respective projects. 2. and radio data and parameters in Atoll. If you wish to add custom fields in the Atoll document.AT310_AM_E2 Atoll 3. In order to be able to manage user accounts and access rights using the Atoll Management Console. Click Yes when asked whether you want to make your database compatible with the user management tool. Select Manage Users.2. 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. you first have to make the database compatible with the user management tool. These path losses are calculated using the master Atoll document by the Atoll administrator.2. The private path loss matrices of the master Atoll document are used as shared path loss matrices by the end-users. such as Oracle. Shared path loss matrices are only used in calculations if valid private path loss matrices are not available. However. the geographic data. 6. This is done automatically when the user management tool is run on a database for the first time. Therefore. For any modifications made by end-users in their Atoll documents that render some shared path losses invalid. In the Atoll Management Console window. The User Management dialogue appears (see Figure 6. and the shared path loss matrices folder. User documents are the working documents of the Atoll end-users connected to the master database. in order to use shared path loss matrices. right-click the database whose user accounts you wish to manage. The database has to be of the same version as the Atoll Management Console being used to manage user accounts and access rights. this is not the case with other RDBMS. see "Appendix 3: Calculating Path Loss Matrices" on page 72. 3. you must delete the corresponding private path loss matrices.0 Administrator Manual Chapter 6: Multi-user Environments If users modify geographic data locally. 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 define user access rights to different components of a project such as database tables. These may contain the entire project network data or only a part of it. The Atoll administrator is the owner of the shared path loss matrices. Atoll calculates the invalid path loss matrices locally for the end-users and stores them in their private path loss matrices location.5 User Atoll Documents User Atoll documents are created from the master database. Shared path loss matrices are available for use in calculations to all the end-users. The shared path loss matrices must be unlocked in order for users to be able to work with them. If users are going to work on regions of a network. You can check whether path loss matrices are unlocked in the Propagation tab of the Transmitters folder’s properties dialogue. they should store these modified geographic data locally so that the modifications do not impact other users. and then update your Atoll document from the database. 6. Custom fields added in an Atoll document connected to a Microsoft Access database are automatically added to the database. End-users should have read-only access to this folder. The Atoll Management Console adds a GUIUserRights table in the database with the following structure: Field ATOLL_USER Type Text (50) Description Name of the user account 67 .3 Managing User Accounts and Access Rights The Atoll Management Console enables you to create and delete database user accounts. 6.1. see "Appendix 2: Database Regionalisation" on page 71.2 on page 68). and must have read/write access to the shared path loss matrices folder. and to calculate the shared path loss matrices using the master Atoll document on a routine basis. However. To make your database compatible with the user management tool: 1. you should first add the field in the database.

The GUIUserRights table is also stored in the Atoll document.PASSWORD The syntax is explained in detail in "Defining Database and Interface Access Rights" on page 68. the GUIUserRights table does not exist.. and is updated when the document is saved. 6. his interface access rights are read and applied to the Atoll interface (table grids and properties dialogues). If the user is listed in the GUIUserRights table.2 on page 68). and still have their usual interface access rights applied in the document. for example. see "Defining Database and Interface Access Rights" on page 68). The contents of the RIGHTS field have the following syntax: RADIOPARAMS. When database connection properties are modified for a document. Atoll reads and applies the interface access rights defined for the new user. If interface access rights are defined for a database. you can set the database and Atoll interface access rights using the Atoll Management Console. Atoll does not ask for the user name and password when a document is opened using the API. Select Manage Users. select the user account whose database and interface access rights you want to set.1. If interface access rights are not defined for a database. Hence. If the database is not reachable. The User Management dialogue appears (see Figure 6. the user is not listed in the GUIUserRights table. Under Atoll projects. or if the password is not correct. A message is displayed in the Event Viewer window to inform the user of his interface access rights.1 Defining Database and Interface Access Rights For any existing user account. To manage database and Atoll interface access rights for an existing user account: 1. However.2: User Account and Access Rights Management Dialogue 3. Figure 6. when a different user enters his user name and password in the connection properties. users can work on their documents without actually being connected to the database. select the project for which you want to manage user accounts. Atoll retrieves the interface access rights for the user when he enters his user name and password to access the database.0 Administrator Manual Chapter 6: Multi-user Environments © Forsk 2011 Field RIGHTS Type Memo Description Semi-colon separated set of interface access rights Each user’s interface access rights are stored in a unique record in the GUIUserRights table.e.PROPAGMODELS. In the Atoll Management Console window. 4. The interface access rights stored in the document are used.Atoll 3.CALCPARAMS. right-click the database whose user accounts you wish to manage. Under List of users. and a user creates a document from the database or opens a document connected to the database. the user’s interface access rights are set to read-only by default (for more information. 68 . a disconnected document cannot be reconnected to the database. all the users have unrestricted access to the Atoll interface. i. 2.3. It is possible to remove interface access restrictions by disconnecting the document from the database.

The database is not visible to these users and they are not allowed to create Atoll documents based on this database. The database and interface access rights of the selected user are saved in the database. site and transmitter lists. 69 . However. but not allowed to modify coverage conditions and display settings. • • 7. • Database access rights are stored in the user account properties in Oracle. remote antennas. however. • Standard: (CALCPARAMS = STD) Users with access to customised coverage predictions only. For more information on locked user accounts. intra. Under Database rights. you will not be able to set database access rights. Access to propagation models: • Full: (PROPAGMODELS = ALL) Users with read and write access to all propagation models and their properties. Read-only: Users allowed to create Atoll documents from the database but without write permissions to any table of the database. You can use the Filter list to display: • • • • • All users: Users with access ( ). subcells. You can. 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.AT310_AM_E2 Atoll 3. • • Access to predictions: • All: (CALCPARAMS = ALL) Users with read and write access to all coverage predictions and their properties. subcells.e. you can select a database access Rights category: • • • No access: User without read and write access to the database. users are not allowed to modify radio network data and parameters. a user may have full access rights in the interface but not allowed to archive changes to the database. 6. microwave repeaters. and allowed to modify coverage conditions and display settings. For example. microwave hubs. 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. repeaters. transmitters.and inter-technology neighbours and exceptional pairs. Under Interface rights. microwave repeaters. cells. • Read only: (PROPAGMODELS = NONE) Users with read-only access to the properties of all the propagation models.2 Creating and Editing User Accounts You can create and edit user accounts using the Atoll Management Console. Adding and deleting propagation models is also not allowed. site and transmitter lists. cells. intraand inter-technology neighbours and exceptional pairs. Locked (deactivated) user accounts are marked with a yellow lock icon ( ). microwave point-to-point.0 Administrator Manual Chapter 6: Multi-user Environments Users who have database access rights in the selected database are marked with the green icon ( ).e. and multi-hop links. access rights in the interface should only be granted if the user has at least read-only access to the database. microwave point-to-point. see "Creating and Editing User Accounts" on page 69.3. still set interface access rights as explained below. 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. microwave hubs. repeaters. i. Administrator: Users with read and write access to all the tables of the database. • Customised only: (CALCPARAMS = NONE) Users with access to customised coverage predictions only. • Standard: (RADIOPARAMS = STD) Users with read and write access to radio network data tables and properties dialogues including sites. • Database access rights and access rights to radio data in Atoll can be set independently.. point-to-multipoint. transmitters. These tables include radio network data tables including sites. 6. • Read-only: (RADIOPARAMS = NONE) Users with read-only access to tables and properties dialogues. and multi-hop links. Users who do not have any database access rights in the selected database (Category = No Access) are marked with the red icon ( ). Standard: Users with read and write access to some tables of the database. Click OK. remote antennas. i.1. pointto-multipoint. If you are working with an RDBMS other than Oracle. secondary antennas. secondary antennas. • 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. users cannot archive changes made in the Atoll document to the database.

To delete a user account: a.3 on page 70). Under Advanced. 6. and select a Tablespace for the new user account. The user account is deactivated and can no longer be used. The Create/Edit User dialogue appears (Figure 6. modify the user’s Password or assigned Tablespace. b. b. click Edit. select the user account you want to deactivate. Under List of users. 4.Atoll 3. Under Users. To create a new user account: a.4 Appendices The following appendices provide additional information on: • • • "Appendix 1: Checking Data Integrity" on page 71 "Appendix 2: Database Regionalisation" on page 71 "Appendix 1: Checking Data Integrity" on page 71 70 .3 on page 70). enter a User name (in block letters) and Password. right-click the database whose user accounts you want to manage. and Unlimited tablespace privilege if you want to assign this system privilege to the user. d. select the user account you want to delete.3: Creating or Editing a User Account 6. Under List of users. 5. Under List of users. In the Atoll Management Console window. The user account is deleted. The new user account is created. d. select Use operating system authentication if you want to use OS authentication prefix with the user name. click Delete. 3. e. The modified user account information is saved. Under Users. c. and Unlimited tablespace privilege if you want to assign this system privilege to the user. c. To deactivate (lock) a user account: a. click Edit. select the user account whose information you want to edit. The User Management dialogue appears (see Figure 6. d. Under Users. The Create/Edit User dialogue appears (Figure 6. Under Advanced. Under Users. select Use operating system authentication if you want to use OS authentication prefix with the user name. 2. select Account locked check box.3 on page 70). b. To edit a user account: a. Click OK. Under Identification. Click OK. Click OK. click Create. c. Under Advanced. b. Figure 6. The Create/Edit User dialogue appears (Figure 6.2 on page 68).1. Under Identification.0 Administrator Manual Chapter 6: Multi-user Environments © Forsk 2011 To manage user accounts: 1. Select Manage Users.

transmitters without cells. 2. 3. which is provided in the standard Oracle installation. Dynamic regionalisation using Oracle Spatial or Oracle Locator Dynamic regionalisation can be based on Oracle Spatial. Specific documents explaining how to set up this regionalisation. and neighbours in GSM. Atoll lists the problems found in the Event Viewer.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. which does not create separate regional databases from the master database. You can implement this solution using Oracle Locator. To perform data integrity check: • In Atoll. end-users work with project databases.4. Atoll lists all the undefined records found in the Event Viewer. 6. 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. Data archive and refresh between the project databases and the master database are performed by the administrator alone. select Document > Data Audit > Microwave Link Data Check. transmitters with the same name. and WiMAX. you can create such regionalisation without installing Oracle Spatial. Atoll searches for records with integrity problems which may occur with objects that have foreign keys. select Document > Data Audit > Undefined Record Check. e. TRXs.AT310_AM_E2 Atoll 3. Records with integrity problems may be deleted when found. or geographic zones in the form of filtering polygons. For example. transmitters referring to an antenna that does not exist in the Antennas table. Atoll searches for undefined records such as sites without transmitters. Static regionalisation requires manual synchronisation between the master database and the regional project databases using the Atoll Management Console. transmitters located on sites that do not exist in the Sites table.4.e. Disadvantage: Manual Synchronisation between the master and the project databases. 4. In an Atoll multi-user environment. multi-level databases as explained in "Working With Multi-level Databases" on page 52. The Microwave Data Check dialogue appears. select the data to check. etc. Static regionalisation is carried out by creating project databases from the master database. For example. Atoll searches the microwave links tables for problems related to the selected checks. refreshing and archiving data as they continue to work on their respective regions of the network. To perform undefined record check: • In Atoll.1. you must archive the changes in the database in order to fix the problems for all the users working with that database.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. select Document > Data Audit > Duplicate Record Check. transmitters without subcells. Select List all the checks to list all the checks in the Event Viewer. TD-SCDMA. etc. Click OK. In the Microwave Data Check dialogue. sites with the same name. using Oracle. To perform duplicate record check: • In Atoll. LTE.g. Transmitters. To perform microwave data check: 1. SQL filters. the 71 . etc. but rather lets the different users work with the master database directly while managing their access privileges according to their user connection properties. Atoll searches for records that have the same identifier. and cells without neighbours in UMTS. In Atoll.).. Atoll lists all the duplicate records in the Event Viewer. These documents provide scripts for creating different types of users. i. select Document > Data Audit > Integrity Check. In a multi-level database environment. If you fix any problems in the Atoll document.0 Administrator Manual Chapter 6: Multi-user Environments 6. CDMA2000. in any Atoll master database are available on demand from Forsk.. Integrity problems occur when records refer records that do not exist. • • • Advantage: High performance.).

You should also make regular backups of the master Atoll document. 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.4. 6. whenever path losses are calculated. 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. make sure that the path loss matrices are: • • • Available in a format compatible with Atoll. should be masked) in order to be consistent with the path loss matrices calculated by Atoll. You can write a script or macro to update path loss matrices automatically at regular intervals. The context menu appears. Atoll calculates path loss matrices for all active transmitters in the folder or subfolder.1. Atoll calculates all the path loss matrices for all active transmitters in the folder or subfolder. among other information. A path loss update macro is available from Forsk on demand.0 Administrator Manual Chapter 6: Multi-user Environments © Forsk 2011 administrator. 3. 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. Disadvantage: Slow performance (archiving data in the database takes a long time). Atoll can also work with path loss matrices calculated by other tools. 2. If the path loss matrices are not valid. Right-click the Transmitters folder. You should only calculate the shared path loss matrices when they are not being accessed by users.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. 6. 2. 72 . Refresh the contents of the document with data from the database (Refresh). Select Calculations > Force Path Loss Matrix Calculation. Valid. 6. Open the master Atoll document (Open). Right-click the Transmitters folder. This file can be overwritten daily. To use path loss matrices from different sources. The Pathloss. To calculate all the path loss matrices (valid and invalid): 1. • • Advantage: Once set up. Atoll will automatically calculate them the next time they are used. Calculate path loss matrices (Calculate). 5. advanced user. The above macro could also create a backup ATL file of the master Atoll document on a regular basis. Start Atoll (Start).e. Stored at the location set in the Atoll document.4. Select Calculations > Calculate Path Loss Matrices. etc. Path loss matrices calculated by other tools should include antenna pattern attenuation (i.Atoll 3. 2. To calculate invalid path loss matrices only: 1. This file stores. Only invalid and nonexistent matrices are calculated.. File formats are described in "Path Loss Matrix File Format" on page 117. read-only user. Save the master Atoll document (Save). Close Atoll (Exit). The context menu appears. The script or macro should: 1.dbf file provides the means to manage several sources of path loss matrices.. The shared path loss matrices architecture can contain path loss matrices from different sources. does not require administrator intervention. and give examples of how to set up regions in the network and how to assign user rights to each region.

0 Administrator Manual Chapter 6: Multi-user Environments Let us assume that the shared path loss matrices folder where Atoll stores the generated path loss matrices files is C:\Path_Loss_Internal. you must create a new folder with a Pathloss. and the folder where the other tool stores its path loss matrices is C:\Path_Loss_External. if the path loss matrices generated by the other tool include Transmitter_1.dbf file in the Path_Loss_Mixed folder will have all the same entries as Pathloss. Figure 6. For example. To set up the shared path loss matrices folder for group B users. Figure 6.dbf file in the Path_Loss_Internal folder except for the path for the Transmitter_1 path loss matrices file. If a group B user changes some parameters which make some path loss matrices invalid.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.4 on page 73 explains this concept. Atoll will recalculate the private path loss matrices with the propagation models assigned to the transmitters.dbf file in it. The Pathloss. the Pathloss.1. This folder can be called C:\Path_Loss_Mixed.dbf file in the Path_Loss_Internal folder with the paths to the LOS files modified.AT310_AM_E2 Atoll 3. the Path_Loss_Mixed folder can be set as the shared path loss matrices folder in the ATL files of group B users. 73 . The Pathloss.dbf file in this folder can be a copy of the Pathloss. The external path loss matrix will no longer be used.dbf file in the Path_Loss_Mixed folder is updated with the correct paths corresponding to the different transmitters.4: Path Loss Architecture for Multiple Source Path Loss Matrices Once the Pathloss.

0 Administrator Manual Chapter 6: Multi-user Environments © Forsk 2011 74 .Atoll 3.1.

In this part.Part 2 Reference This part of the administrator manual provides recommendations and information on Atoll configuration and initialisation files. the following are explained: • • • "Administration and Usage Recommendations" on page 129 "Configuration Files" on page 141 "Initialisation Files" on page 169 .

.

• A geographic system is not a projection.0 Administrator Manual Chapter 7: Coordinate Systems and Units 7 Coordinate Systems and Units 7. 2nd Edition.edu/geography/gcraft/notes/gps/gps_f.1 Definition of a Coordinate System A geographic coordinate system is a latitude and longitude coordinate system.). Locations in a geographic system can be converted into other projections.1.1.1 Coordinate Systems A map or a geo-spatial database is a flat representation of data collected over a curved surface.C. Cartographic coordinate systems are obtained by transforming each (latitude.AT310_AM_E2 Atoll 3. 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. Projection is a means of producing all or part of a spheroid on a flat surface. gradient) with the latitude and longitude with respect to a meridian (e. For example. Map Projections Used by the US Geological Survey. It is up to the cartographer to choose the characteristic (distance. and a prime meridian. Snyder. Projection coordinate systems are geographic coordinate systems that provide longitude and latitude. John. northing) value. etc. or to make a compromise on several characteristics. The geodetic datum provides the position and orientation of the ellipsoid relative to the earth. Geographic Coordinate System The geographic coordinate system is a datum and a meridian. which cannot be done without distortion. These meridians are defined by the longitude with respect to Greenwich. Datum The datum consists of the ellipsoid and its position relative to the WGS84 ellipsoid. 1982. This projection method is useful for representing countries or regions that have a predominant east-west expanse. Meridian The standard meridian is Greenwich. longitude) value into an (easting. rotation. The projected zones are referenced using cartographic coordinates (metre. but a representation of a location on the surface of the earth in geographic coordinates (degree-minute-second.ign. yard. Atoll enables you to choose the most suitable geographic coordinate system for your geographic data. 77 . 313 pages. D. Paris for NTF system and Greenwich for ED50 system). This projection method is useful for mapping large areas that are oriented north-south. and the transformation method characterised by a set of parameters. Washington. United States Government Printing Office. 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).html 3. direction. References: 1. area.. http://www.colorado.pdf (French) 7. The latitude and longitude are related to an ellipsoid. A projection coordinate system is obtained by transforming each (latitude. http://geodesie. 2. http://www.. longitude) value into an (easting. translation. a geodetic datum. 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.epsg. P. but some geographic coordinate systems are based on other meridians.html 4.fr/contenu/fichiers/documentation/pedagogiques/ transfo. scale.. Different methods may require different sets of parameters. In addition to the ellipsoid.g. and distortion parameters define the datum. northing) value. or shape) that he wants to produce accurately on a flat surface at the expense of the other characteristics.org/Geodetic.

Atoll enables you to choose the projection coordinate system matching your geographic data. 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. in the status bar. If you change the display coordinate system in a document which is not connected to a database. there are two coordinate systems used in Atoll: • • Projection coordinate system Display coordinate system If you are working in a multi-user environment. Atoll does not use any coordinate system during the import process.Atoll 3. However. If you import vector geographic data (e. 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..g. Atoll reads the geo-referencing information from the file (or from its header file. 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.. All the raster geographic data files that you want to import and use in an Atoll document must have the same coordinate 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. It associates a geographic coordinate system and a projection. e. etc.g. Projection The projection is the transformation applied to project the ellipsoid of the earth on to a plane. it is possible to convert the coordinate systems of these data into the projection coordinate system of your Atoll document.1. there can be either two or four coordinate systems used in Atoll. You cannot work with raster geographic data files with different coordinate systems in the same document.0 Administrator Manual Chapter 7: Coordinate Systems and Units © Forsk 2011 Ellipsoid The ellipsoid is the pattern used to model the earth. The coordinates of each pixel of geographic data are converted to the display coordinate system from the projection coordinate system for display.1. By default. 78 . the two coordinate systems are the same. in dialogs. i. The projection coordinate system is used to keep the coordinates of sites (radio network data) consistent with the geographic data. traffic. 7.2 Types of Coordinate Systems in Atoll Depending on the working environment. measurements. If you import sites data. to determine the coordinates of each pixel. Display Coordinate System The display coordinate system is the coordinate system used for the display. documents not connected to databases. its Northwest pixel. the coordinates of all the sites are converted to the new display system. It is defined by its geometric parameters. The display coordinate system is also used for sites (radio network data).. You can set the projection coordinate system of your document in the Options dialog. in the Map window rulers. depending on the geographic data file format).e.) with different coordinate systems. i. You can set the display coordinate system of your document in the Options dialog.e. When you import a raster geographic data file. the coordinate system of the sites must correspond to the display coordinate system of your Atoll document. etc. the geo-referencing information of geographic data files are considered to be provided in the projection coordinate system of the document. If you are working with stand-alone documents.

Projection parameters are delimited by commas. A catalogue per region and a "Favourites" catalogue are available in Atoll. Dy. i. "United States . There can be 3 to 7 parameters defined in the following order: Dx. the projection and the display coordinate systems. Projection Method Code. data. In case you create a new coordinate system. -72. Users working on documents connected to a database can modify the coordinate systems in their documents locally. and ellipsoids. The line syntax for describing a coordinate system is: Code = "Name of the system". 79 . the coordinates of all the sites are converted to the new display system.Vermont" You should keep the following points in mind when editing or creating . its code must be an integer value higher than 32767. Datum Code. For UTM projections. S}. the currently chosen display coordinate system becomes the internal display coordinate system for the database.AT310_AM_E2 Atoll 3. 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. 0. The Favourites catalogue is initially empty and can be filled by the user by adding coordinate systems to it. Projection Parameters. {Ellipsoid Code. Each catalogue is described by an ASCII text file with . Dx. and save these changes in their documents. 230. offered in the tool.cs file will be: Code = "Name of the system". and the currently chosen projection coordinate system becomes the internal projection coordinate system for the database.5. Ry. 101. 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. The syntax of the line in the . "Europe . you must enter the ellipsoid code and parameters instead of the datum code in brackets. Rx. If you change the display coordinate system in a document which is connected to a database. 7. S.west" 32045 = "NAD27 / Vermont". 267. Only the administrator can modify the internal coordinate systems manually by editing the entries in the CoordSys and the Units tables. but they cannot modify the coordinate systems stored in the database. These parameters must be ordered according to the parameter index (see "Projection Parameter Indices" on page 82). When describing a new datum. Unit Code.1.cs file. 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.e. Dz. When exporting an Atoll project to a database. you must provide positive UTM zone numbers for north UTM zones and negative numbers for south UTM zones. 1. both geographic and cartographic. In a .9999643.. Projection Method Code.1. 2. Rx. Rz. Rz. and cannot be modified by users. Dz. If you change the display coordinate system in a document which is not connected to a database. Ry.cs files: • • The identification code enables Atoll to differentiate coordinates systems. All Atoll documents opened from a database will have the internal coordinate systems of the database as their default projection and display coordinate systems. Projection Parameters. 0. and projection parameter indices are listed in the tables below. Parameter with index 0 is the first one. You can add all other information as comments (such as usage or region).5.3 Coordinate Systems File Format The Coordsystems folder located in the Atoll installation directory contains all the coordinate systems. 6. 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). Unit Code. "Comments" • There can be up to seven projection parameters.0 Administrator Manual Chapter 7: Coordinate Systems and Units Internal Coordinate Systems The internal coordinate systems are the projection and the display coordinate systems stored in a database.cs extension. Coordinate systems are grouped by regions. each coordinate system is described in one line. Dy. • • Codes of units. "Comments" Examples: 4230 = "ED50". Although Atoll stores both the coordinate systems in the database. 42. projection methods. 500000.

0 Administrator Manual Chapter 7: Coordinate Systems and Units © Forsk 2011 Unit Codes Code 0 1 2 3 4 5 6 7 -1 Datum Codes Code 121 125 126 130 131 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 221 222 223 224 225 226 227 228 229 230 Datum Greek Geodetic Reference System 1987 Samboja Lithuania 1994 Moznet (ITRF94) Indian 1960 Adindan Australian Geodetic Datum 1966 Australian Geodetic Datum 1984 Ain el Abd 1970 Afgooye Agadez Lisbon Aratu Arc 1950 Arc 1960 Batavia Barbados Beduaram Beijing 1954 Reseau National Belge 1950 Bermuda 1957 Bern 1898 Bogota Bukit Rimpah Campo Inchauspe Cape Carthage Chua Corrego Alegre Cote d'Ivoire Deir ez Zor Douala Egypt 1907 European Datum 1950 Code 260 261 262 263 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 Datum Manoca Merchich Massawa Minna Monte Mario M'poraloko North American Datum 1927 NAD Michigan North American Datum 1983 Nahrwan 1967 Naparima 1972 New Zealand Geodetic Datum 1949 NGO 1948 Datum 73 Nouvelle Triangulation Française NSWC 9Z-2 OSGB 1936 OSGB 1970 (SN) OS (SN) 1980 Padang 1884 Palestine 1923 Pointe Noire Geocentric Datum of Australia 1994 Pulkovo 1942 Qatar Qatar 1948 Qornoq Loma Quintana Amersfoort RT38 South American Datum 1969 Sapper Hill 1943 Schwarzeck Segora Cartographic Units Metre Kilometre Foot Link Chain Yard Nautical mile Mile Unspecified -1 Unspecified Code 100 101 102 103 104 Geographic Units Radian Degree Grad ArcMinute ArcSecond 80 .1.Atoll 3.

90890985 6356034.1.189 6378160 6377397.38276679 Projection Method Undefined No projection > Longitude / Latitude Lambert Conformal Conical 1SP Lambert Conformal Conical 2SP Mercator Cassini-Soldner Transverse Mercator Transverse Mercator South Oriented Code 8 9 10 11 12 13 14 Projection Method Oblique Stereographic New Zealand Map Grid Hotine Oblique Mercator Laborde Oblique Mercator Swiss Oblique Cylindrical Oblique Mercator UTM Projection 81 .AT310_AM_E2 Atoll 3.0 Administrator Manual Chapter 7: Coordinate Systems and Units Code 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 247 248 249 250 251 252 253 254 255 256 257 258 Datum European Datum 1987 Fahud Gandajika 1970 Garoua Guyane Francaise Hu Tzu Shan Hungarian Datum 1972 Indonesian Datum 1974 Indian 1954 Indian 1975 Jamaica 1875 Jamaica 1969 Kalianpur Kandawala Kertau La Canoa Provisional South American Datum 1956 Lake Leigon Liberia 1964 Lome Luzon 1911 Hito XVIII 1963 Herat North Mahe 1971 Makassar European Reference System 1989 Code 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 322 326 901 902 903 Datum Serindung Sudan Tananarive 1925 Timbalai 1948 TM65 TM75 Tokyo Trinidad 1903 Trucial Coast 1948 Voirol 1875 Voirol Unifie 1960 Bern 1938 Nord Sahara 1959 Stockholm 1938 Yacare Yoff Zanderij Militar-Geographische Institut Reseau National Belge 1972 Deutsche Hauptdreiecksnetz Conakry 1905 WGS 72 WGS 84 Ancienne Triangulation Française Nord de Guerre NAD 1927 Guatemala/Honduras/Salvador (Panama Zone) Projection Method Codes Code 0 1 2 3 4 5 6 7 Ellipsoid Codes Code 1 2 3 4 5 6 Name Airy 1830 Airy Modified 1849 Australian National Spheroid Bessel 1841 Bessel Modified Bessel Namibia Major Axis 6377563.71919531 6356078.155 6377492.396 6377340.865 Minor Axis 6356256.50851316 6356165.018 6377483.96261866 6356173.44761111 6356774.

To create a new coordinate system from scratch: 1.2 6378136.145 6378249.86954978 6356514.98173817 6356583.79 6378249. 4. Click New. it is possible to add new geographic and cartographic coordinate systems.45104614 6356566. Select Document > Properties.96026256 6371000 Projection Parameter UTM zone number Longitude of origin Latitude of origin False Easting False Northing Index 4 4 5 5 6 Projection Parameter Scale factor at origin Latitude of 1st parallel Azimuth of central line Latitude of 2nd parallel Angle from rectified to skewed grid 7.5503009 6356100.61633668 6356514. The Coordinate Systems dialogue appears.27021959 6356752.231 6356103.31398972 6356751.Atoll 3.4 6378693.13884613 6371000 Minor Axis 6356617.2 6377276.51667196 6356751.2 6378249.556 6377301.71919530 6356863.96656909 6356514.93325557 6356655.41314024 6356097. 82 .16962789 6356774. 2. The Properties dialogue opens.43 6356515 6356514.52001609 6355862.7040359 6378300. Click the Browse button ( ) to the right of Projection.145 6378249.1. 3.94612795 6356774.84708038 6356752.01877305 6356759.243 6377304.4 Creating a Coordinate System in Atoll Atoll provides a large default catalogue of coordinate systems.1.063 6378137 6378200 6378160 6378388 6378160 6378245 6378145 6378135 6376523 6378297 6378300.76948868 6356750.345 6377298.0 Administrator Manual Chapter 7: Coordinate Systems and Units © Forsk 2011 Code 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 Projection Parameter Indices Index 0 0 1 2 3 Name Clarke 1858 Clarke 1866 Clarke 1866 Michigan Clarke 1880 (Benoit) Clarke 1880 (IGN) Clarke 1880 (RGS) Clarke 1880 (Arc) Clarke 1880 (SGA 1922) Everest 1830 (1937 Adjustment) Everest 1830 (1967 Definition) Everest 1830 (1975 Definition) Everest 1830 Modified GRS 1980 Helmert 1906 Indonesian National Spheroid International 1924 International 1967 Krassowsky 1940 NWL 9D NWL 10D Plessis 1817 Struve 1860 War Office WGS 84 GEM 10C OSU86F OSU91A Clarke 1880 Sphere Major Axis 6378293.583 6378137 6378137 6378136. The Coordinate System dialogue appears.63924683 6378206.3 6378249. However. Select the Coordinates tab.99694178 6356075.03899315 6356752. New coordinate systems can be created from scratch or initialised based on existing ones.31398972 6356818.50408554 6356911.31398972 6356752.8 6357069.

there is only one measurement unit used in Atoll for display. Transmission and Reception Power Units Depending on the working environment. Ry. Enter the longitude and latitude for a geographic coordinate system. specify the meridian and choose a Datum for the coordinate system. Only the administrator can modify it manually by editing the entry in the Units tables.. or you can change them using the document properties dialogue. Atoll uses two measurement units: • • A measurement unit for display in the Atoll document.). documents not connected to databases. You can also describe a geodetic datum by selecting "<Customized>" in the Datum list.AT310_AM_E2 Atoll 3. 7. there is only one measurement unit used in Atoll for display. but they cannot modify the antenna gain unit stored in the database. transmission. Under General. you can enter comments about its usage. i. An internal measurement unit for the database. b. 6. microwave link properties. In Use. etc. • Antenna Gain Units Depending on the working environment. It corresponds to the transmission/reception power unit defined in the current Atoll document. Select the coordinate systems catalogue to which you want to add the new coordinate system. you must select an Ellipsoid and enter parameters (Dx. documents not connected to databases. reception thresholds (coverage prediction properties. and temperature.e. It corresponds to the antenna gain unit defined in the Atoll document. antenna gain. enter a Name for the new coordinate system and select a Unit. The internal unit is the antenna gain unit stored in the database. If you are working in a multi-user environment. and in the status bar. In the Coordinate System dialogue: a. It corresponds to the transmission/reception power unit used in the master Atoll document when the database is created. If you are working with stand-alone documents. In this case. Atoll can use either one or two measurement units for the transmission/reception power. e. in the tables. select a coordinate system in the Coordinate Systems dialogue before clicking New in step 4. coverage predictions. or the type of projection and its set of associated parameters for a cartographic coordinate system (false easting and northing. Distance Units Atoll uses the distance unit defined in the current Atoll document as display unit of the distances in the dialogues. microwave link properties. The internal measurement unit is not stored in the database and cannot be changed. It is used for the display in the dialogues and in the tables. point analysis.0 Administrator Manual Chapter 7: Coordinate Systems and Units 5. The new coordinate system is added to the selected coordinate system catalogue. Under Category. and S) needed for the transformation of the datum into WGS84. Users working in documents connected to a database can modify the antenna gain unit and save this change in their documents locally. It corresponds to the antenna gain unit used in the master Atoll document when the database is created. d. and received signal levels (measurements. distance. Only the administrator can modify it manually by editing the entry in the Units tables. Dz.). you can define measurement units for reception. select the Type of coordinate system. If you are working in a multi-user environment. etc. The new coordinate system is initialised with the values of the selected coordinate system. Atoll uses two measurement units: • A measurement unit for display in the Atoll document.1.. Click OK. Metre is used as the internal measurement unit for the distance in all Atoll documents whether they are connected to databases or not. height and offset. Users working in documents connected to a database can modify the transmission/reception power unit and save this change in their documents locally. It corresponds to the transmission/reception power unit defined in the Atoll document. The internal unit is the transmission/reception power unit stored in the database. Dy. 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. and the first and second parallels).e.2 Units In the Atoll documents. i. Atoll assigns the code automatically. Rz. Rx. The associated ellipsoid is automatically selected. c.. 83 . To create a new coordinate system based on an existing system. Under Geo. An internal measurement unit for the database. If you are working with stand-alone documents.g. You can accept the default measurement units. Atoll can use either one or two measurement units for the antenna gain. but they cannot modify the internal power unit stored in the database.

Users working on documents connected to a database can modify the format in their documents locally. 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. and in the status bar. The internal format is the BSIC format stored in a database.0 Administrator Manual Chapter 7: Coordinate Systems and Units © Forsk 2011 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.. 84 . in the tables.e. The internal measurement unit is not stored in the database and cannot be changed. The internal measurement unit is not stored in the database and cannot be changed. there is only one BSIC format: • Display BSIC format If you are working in a multi-user environment. and save this change in their documents.1. If you are working with standalone documents. Atoll uses two type of formats: • • Display BSIC format for the Atoll document Internal BSIC format for the database The display format is used for the display in dialogs and tables. documents not connected to databases. but they cannot modify the format stored in the database. and cannot be modified by users. 7.3 BSIC Format Depending on the working environment. i. You can set the display format for your document from the Transmitters folder’s context menu. 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. All Atoll documents opened from a database will have the internal format of the database as their default BSIC format. Only the administrator can modify the internal format manually by editing the corresponding entry in the Units tables. there can be either one or two types of BSIC formats.Atoll 3. The BSIC format set by the administrator in the central Atoll project is stored in the database when the database is created.

clutter heights.1 Digital Terrain Model (DTM) The Digital Terrain Model (DTM) describes the ground elevation above the sea level. images. other Images Georeferencing Yes (via HDRfiles) Yes (via TFW files) Yes (via index files) Yes (via BPW or BMW files) Yes Yes Yes Yes Yes (embedded in the data file) Yes (embedded in the data file) Yes (embedded in the data file) Yes (via ERS files) • • • • WLD files may be used for georeferencing for any type of binary raster file. other Vector data. other DTM. images.0 Administrator Manual Chapter 8: Geographic Data 8 Geographic Data Atoll supports several geographic data types. other DTM. clutter heights. population. images. The different filters are: File Format BIL TIFF Planet BMP DXF SHP MapInfo (MIF. clutter classes. clutter classes. TAB) Erdas Imagine (IMG) ArcView Grid (TXT) Atoll Geo Data (AGD) Vertical Mapper (GRD. Space between points is defined by pixel size P (in metre). population. clutter heights. DTM files provide altitude value z (in metre) on evenly spaced points.1. scanned images. traffic maps. DTM maps are taken into account in path loss calculations by Atoll propagation models. population. other DTM. clutter classes. other Vector data. Figure 8. Pixel size must be the same in both directions. population. population. images.AT310_AM_E2 Atoll 3. clutter. vector traffic maps. other Vector data. population. The first point given in the file corresponds to the centre of the top-left pixel of the map (northwest point georeferenced by Atoll). traffic maps. traffic maps. vector traffic maps. population. other DTM. DTM (Digital Terrain Model). other DTM. traffic maps. Atoll offers import/export filters for the most commonly used geographic data formats. 8. clutter classes. clutter classes. GRC) ECW Import and Export in Atoll Both Both Both Both Import Both Both Import Export Both Both Import Geographic Data DTM. traffic maps. images. traffic maps. vector traffic maps. The smallest supported resolution for raster files is 1 m. vector data. images. vector traffic maps Vector data. Abscissa and ordinate axes are respectively oriented in right and downwards directions. vector data DTM. There is no restriction on the resolution of images. population. clutter classes. images. clutter classes. clutter classes. All the raster maps you want to import in an ATL document must be represented in the same projection system. clutter heights. DTM. population.1: Digital Terrain Model 85 . clutter heights. and custom geographic data. population. clutter heights. and clutter height maps must have an integer resolution. traffic maps.

while DTM refers to the ground altitude above sea level alone. By definition. Atoll takes the altitude of the southwest point of each bin to assign a colour. 16-bits integer. 8-bits integer) Vertical Mapper (GRD. Pixel size must be the same in both directions. these points are bin vertices. Figure 8. 8-bits integer) TIFF (16-bits integer.1. The first point given in the file corresponds to the centre of the top-left pixel of the map (northwest point geo-referenced by Atoll. GRC) Planet (16-bits integer) • • • Altitudes may differ within a bin. A clutter classes file file that contains N x N bins requires N2 code values. Figure 8. Bin size is defined by pixel size P (in metre). forest. In Atoll. open. residential. DEM (Digital Elevation Model) is the same as Digital Terrain Model (DTM).3: Clutter Classes Atoll supports a maximum of 255 clutter classes (8 bits/pixel). Abscissa and ordinate axes are respectively oriented in right and downwards directions. villages. DEM refers to the altitude above sea level including ground and clutter. 8. Clutter class maps are taken into account in path loss calculations by Atoll propagation models. Therefore. The clutter classes map is a grid representing the ground with each bin assigned a clutter class code corresponding to its clutter type. 86 . It is possible to specify an average height for each clutter class in Atoll. The method used to calculate altitudes in Atoll is described in the Technical Reference Guide.). DEM and DTM may not have the same meaning.0 Administrator Manual Chapter 8: Geographic Data © Forsk 2011 Four points (hence. 16-bits integer. In litterature.Atoll 3. four altitude values) are necessary to describe a “bin”. 8-bits integer) BMP (8-bits) Erdas Imagine (32-bits integer and real.2 Clutter Classes Clutter classes describe the land cover (dense urban. a DTM file that contains N x N bins requires N2 points (altitude values). To display a DTM map. buildings. etc. Clutter class files provide a clutter code per bin.2: Schematic view of a DTM file DTM file formats supported by Atoll are: • • • • • • BIL (32-bits integer and real.

16-bits) BMP (32-bits. 16-bits) Erdas Imagine (32-bits. Atoll takes the altitude of the southwest point of each bin to assign a colour. User profile traffic maps based on user profile densities and sector traffic maps (vector traffic maps) support the following formats: • • • • • MIF/TAB SHP DXF Planet AGD User profile traffic maps based on user profile environments (raster traffic maps) support the following formats: • • • • • • BIL (8-bits) TIFF (8-bits) BMP (8-bits) Erdas Imagine (8-bits) Vertical Mapper (GRD. Bin size is defined by pixel size P (in metre).1.AT310_AM_E2 Atoll 3. First point given in the file corresponds to the centre of the top-left pixel of the map (northwest point geo-referenced by Atoll.4 Traffic Data Atoll supports different kinds of traffic maps. GRC) Planet (16-bits integer) 87 . GRC) Planet (16-bits) User density traffic maps (raster traffic maps) support the following formats: • • • • • • BIL (32-bits. GRC) Planet (16-bits) The clutter code is the same inside a bin. • 8. 8. The method used to determine clutter heights in Atoll is described in the Technical Reference Guide. 8-bits integer) Vertical Mapper (GRD. 8-bits integer) TIFF (16-bits integer. GRC) Planet (16-bits integer) • Atoll considers the clutter height of the nearest point in calculations. To display a clutter height map. Clutter heights file formats supported by Atoll are: • • • • • • BIL (32-bits integer and real. Abscissa and ordinate axes are respectively oriented in right and downwards directions.3 Clutter Heights Clutter height files provide a clutter height value per bin. 16-bits integer. 8-bits integer) BMP (8-bits) Erdas Imagine (32-bits integer and real.0 Administrator Manual Chapter 8: Geographic Data Clutter classes file formats supported by Atoll are: • • • • • • BIL (8-bits) TIFF (8-bits) BMP (8-bit) Erdas Imagine (8-bits) Vertical Mapper (GRD. Clutter height maps are taken into account in path loss calculations by Atoll propagation models. Pixel size must be the same in both directions. 16-bits) TIFF (32-bits. 16-bits) Vertical Mapper (GRD. 16-bits integer.

24-bits) BMP (1 to 24-bits) Erdas Imagine (1. etc. or points (towns.). 32-bits) BMP (8. 32-bits) TIFF (8. 16. etc. 24-bits) Vertical Mapper (GRD. 24-bits) 8. 16. etc.6 Images Images include air and satellite images. 4. 16. 32-bits) MIF/TAB SHP Vertical Mapper (GRD. Populataion data can be used in Atoll in clutter statistics and coverage prediction reports. 8. 32-bits) BMP (8. Vector data can be imported in Atoll for display and to provide information about the geographic environment.1. Population data raster file formats supported by Atoll are: • • • • BIL (8. Custom file formats supported by Atoll are: • • • • • • • • BIL (8. 16. in Atoll. 8. Vector file formats supported by Atoll are: • • • • • MIF/TAB SHP DXF Planet AGD 8. 32-bits) TIFF (8. GRC) ECW (Enhanced Compressed Wavelet) (24 bits) Planet (1. 32-bits) Population data vector file formats supported by Atoll are: • • • • MIF/TAB SHP Vertical Mapper (GRD. coastlines.0 Administrator Manual Chapter 8: Geographic Data © Forsk 2011 8. 16. 8. lines (roads. 4. 4.8 Custom Data It is possible to import custom geographic data types. 32-bits) Erdas Imagine (8. 16.). GRC) AGD 88 .Atoll 3.5 Vector Data Vector data may be polygons (regions.).7 Population Data Population data describe the population distribution (number or density of inhabitants). other than those listed above. GRC) AGD 8. 24-bits) TIFF (1. Images can be imported in Atoll for display and to provide information about the geographic environment. 8. These maps can be taken into account in clutter statistics and coverage prediction reports. Image file formats supported by Atoll are: • • • • • • • BIL (1. 32-bits) Erdas Imagine (8. 4.

etc. ulxmap ulymap xdim ydim x coordinate of the centre of the upper-left pixel. layout Must be ‘bil’. An HDR file has the same name as the BIL file it refers to.9.AT310_AM_E2 Atoll 3. Other keywords are ignored. The header file is made of rows. of the image. 8. etc. 8 or 16 for DTMs or Clutter heights (altitude in metres).1. Number of bits per pixel per band. a colour map. The HDR structure is simple. number of bands. number of bits per pixel. Accepted values are M (Motorola byte order) or I (Intel byte order). This information is included in the header HDR file associated with the BIL file. Number of columns in the image. You can open an HDR file using any ASCII text editor. each row having the following format: keyword value where ‘keyword’ corresponds to an attribute type. byteorder Byte order in which image pixel values are stored.1 BIL Format Band Interleaved by Line is a method of organizing image data for multi-band images. It is a schema for storing the actual pixel values of an image in a file. this keyword can be replaced by datatype defined as follows: datatype This can be: Type of data read (in addition to the length) 89 . The pixel data is typically preceded by a file header that contains auxiliary data about the image. y size in metre of a pixel.1. and should be located in the same directory as the source file. pixeltype Type of data read (in addition to the length) This can be: UNSIGNDINT SIGNEDINT FLOAT Undefined Integer Real 8. 16 for path loss matrices (path loss in dB. y coordinate of the centre of the upper-left pixel.9 Geographic Data File Formats 8. such as the number of rows and columns in the image. skipbytes Byte to be skipped in the image file in order to reach the beginning of the image data. it is treated as an image format.0 Administrator Manual Chapter 8: Geographic Data 8. (1 for DTM and 8 bit pictures). dBµV and DBµV/m). x size in metre of a pixel. BIL data stores pixel information band by band for each line. Although BIL is a data organization schema. 16. field value in dBm.1 HDR Header File The header file is a text file that describes how data are organised in the BIL file. Four additional keywords may be optionally managed. 8 for clutter classes file (clutter code). and ‘value’ defines the attribute value. nrows ncols nbands nbits Number of rows in the image. An image description (number of rows and columns. Keywords required by Atoll are described below. BIL files are usually binary files without header.) has to be provided to be able to display the BIL file. 24 or 32 bits 16 or 32 bits 32 or 64 bits In some cases. Default value is 0. byte order.9. or row. Data are stored starting from the Northwest corner of the area. Number of spectral bands in the image. it is an ASCII text file containing eleven lines.

nrows ncols nbands nbits 1500 1500 1 8 or 16 Value corresponding to “NO DATA” byteorder M layout bil skipbytes 0 ulxmap ulymap xdim ydim 975000 1891000 20.00 8. By default. valuescale.1. greyscale. integer data types are chosen with respect to the pixel length (nbits).00 20. You have to enter spatial references of the image manually during the import procedure (x and y-axis map coordinates of the centre of the upper-left pixel.2 TIFF Format Tagged Image File Format supports all image types (monochrome. the data is 20 m.9. 24 or 32 bits) n bits (16 or 32 bits) n bits (32 or 64 bits) 3 colour components on 24 bits The other optional keywords are: valueoffset. 90 . and RGB full colour images). and nodatavalue.00 20. pixel size). palette colour. an associated file with TFW extension will be simultaneously created with the same name and in the same directory as the TIFF file it refers to.Atoll 3.0 Administrator Manual Chapter 8: Geographic Data © Forsk 2011 Un In Rn RGB24 Undefined Integer Real Integer n bits (8. Atoll will then use the TFW file during the import procedure for an automatic geo-referencing. TIFF files are not systematically geo-referenced. 16.00 Clutter Classes Sample nrows ncols nbands nbits 1500 1500 1 8 byteorder M layout bil skipbytes 0 ulxmap ulymap xdim ydim 975000 1891000 20. we have V = V read × valuescale + valueoffset nodatavalue DTM Sample Here. valueoffset valuescale Real value to be added to the read value (Vread) Scaling factor to be applied to the read value So.

It is possible to import Packbit. see "Hiding Information Displayed in the Status Bar" on page 179. If you are using compressed TIFF files. Atoll also supports BMW extension for the BMP related world files.14 bytes): 91 . When exporting (saving) a BMP file. The following tables give exact information about the data structures.3 BMP Format BMP format supports black & white.2.1 TFW Header File TFW files contain the spatial reference data of associated TIFF files.00 8.9. pixel size).00 2679900.00 0. Clutter Classes Sample 100. Large uncompressed files can be split into smaller ones. For more information. Description x dimension of a pixel in map units amount of translation amount of rotation negative of the y dimension of a pixel in map units x-axis map coordinate of the centre of the upper-left pixel y-axis map coordinate of the centre of the upper-left pixel Atoll does not use the lines 2 and 3 when importing a TIFF format geographic file. The image data may either contain pointers to entries in a colour table or literal RGB values. 16-. 8.0 Administrator Manual Chapter 8: Geographic Data • • • • • Tiled TIFF format is not supported. BITMAPINFOHEADER (bmih) contains information about the bitmap (such as size. BMP files are not systematically geo-referenced.1. it is recommended to use uncompressed files for better performance. and LZW compressed TIFF files. etc. see "Setting the TIFF Colour Convention" on page 170. • BITMAPFILEHEADER (Header .and true-colour images. 8. the Name column contains both generic name and the name assigned to this data element by the Microsoft API documentation. You can open a TFW file using any ASCII text editor. The TFW file structure is as follows: Line 1 2a 3 4 5 6 a. clutter class.3. FAX-CCITT3. 256. Atoll stores the georeferencing information in this file for future imports of the BMP so that the BPW file can be used during the import procedure for automatic geo-referencing. the Size-value contains the number of bytes used by this data element.9. not about the bitmap itself). an associated file with BPW extension is created with the same name and in the same directory as the BMP file it refers to.9. However.00 -100.1 BMP File Structure A BMP file has the following data structure: • • • • BITMAPFILEHEADER (bmfh) contains some information about the bitmap file (about the file. and the Description column gives a short explanation of the purpose of this data element. colours. performance may be improved by either hiding the Status Bar or by hiding some of the information displayed in the Status Bar (altitude. or clutter height). in case of DTM and clutter.AT310_AM_E2 Atoll 3.00 60000. it is an ASCII text file that contains six lines. BYTE contains the image data (whose format is specified by the bmih structure). Compressed TIFF files can be exported to uncompressed TIFF files using Atoll. The Start-value is the position of the byte in the file at which the explained data element of the structure starts. You can modify the colour palette convention used by Atoll when exporting TIFF files.00 0.). For more information. The TFW file structure is simple. RGBQUAD contains a colour table. You have to enter spatial references of the image manually during the import procedure (x and y-axis map coordinates of the centre of the upper-left pixel.

40 bytes): Size 4 4 4 2 Name Generic Size Width Height Planes MS API biSize biWidth biHeight biPlanes Description Specifies the size of the BITMAPINFOHEADER structure. Specifies the number of planes of the target device. Specifies the number of colour that are 'important' for the bitmap. • Pixel data: The interpretation of the pixel data depends on the BITMAPINFOHEADER structure. 0 = BI_RGB no compression 1 = BI_RLE8 8-bit RLE encoding 2 = BI_RLE4 4-bit RLE encoding Specifies the size of the image data. Not used. the specification for a colour starts with the blue byte. in pixels. Specifies the the horizontal pixels per meter. # of colours = 65536 24 = 24-bit palletized. # of colours = 16 8 = 8-bit palletized. If set to zero. Specifies the number of bits per pixel. it is valid to set this element to zero.0 Administrator Manual Chapter 8: Geographic Data © Forsk 2011 Start 1 3 7 9 11 • Start 15 19 23 27 Size 2 4 2 2 4 Name Generic Signature FileSize Reserved1 Reserved2 DataOffset MS API bfType bfSize bfReserved1 bfReserved2 bfOffBits Description Must always be set to 'BM' to declare that this is a BMP file Specifies the size of the file in bytes. Specifies the width of the image. while in a palette a colour always starts with the red byte. must be set to zero or 1. # of colours = 256 16 = 16-bit palletized. If there is no compression. # of colours = 1 4 = 4-bit palletized. 29 2 BitCount biBitCount 31 4 Compression biCompression 35 39 43 47 51 • Start 1 2 3 4 4 4 4 4 4 ImageSize XpixelsPerM YpixelsPerM ColoursUsed ColoursImportant biSizeImage biXPelsPerMeter biYPelsPerMeter biClrUsed biClrImportant RGBQUAD array (ColorTable): Size 1 1 1 1 Name Generic Blue Green Red Reserved MS API rgbBlue rgbGreen rgbRed rgbReserved Description Specifies the blue part of the colour Specifies the green part of the colour Specifies the red part of the colour Must always be set to zero In a colour table (RGBQUAD). in bytes (= 40 bytes). Not used.1. Specifies the height of the image. usually set to zero. It is important to know that the rows of a BMP are stored upside down meaning that the uppermost row which appears on the screen is actually the 92 . Must be set to zero. BITMAPINFOHEADER (InfoHeader . all colours are considered important. Must be set to zero. # of colours = 16M Specifies the type of compression. If set to zero the number of colours is calculated using the biBitCount element. Specifies the offset from the beginning of the file to the bitmap raster data. in bytes. in pixels. Specifies the the vertical pixels per meter.Atoll 3. 1 = monochrome pallete. Specifies the number of colours actually used in the bitmap.

Padding each line with zeros up to a 32-bit boundary will result in up to 28 zeros = 7 'wasted pixels'. The End-of-Bitmap is zero padded to end on a 32-bit boundary.).. The End-of-Bitmap is zero padded to end on a 32-bit boundary. Due to the 16bit-ness of this structure this will always be either two zero bytes or none. Pixel lines are padded with zeros to end on a 32-bit boundary. There are 256 colour table entries. Padding each line with zeros up to a 32-bit boundary will result in up to 3 bytes of zeros = 3 'wasted pixels'. its high order 4 bits representing the left of those. The resulting pixel pattern will have interleaved highorder 4-bits and low order 4 bits (ABABA. The following c bytes will be read as single pixel colours just as in uncompressed files. If the first byte is zero. The first byte specifies the number of consecutive pixels with the same pair of colour. the second its green. the second defines an escape code. End-of-line End-of-Bitmap Delta. The skipped pixels should get a colour zero. For uncompressed formats every line will have the same number of bytes. 3rd. Padding each line with zeros up to a 16-bit boundary will result in up to 2 zero bytes. pixels' colour is in c's high-order 4 bits. Another important thing is that the number of bytes in one row must always be adjusted by appending zero bytes to fit into the border of a multiple of four (16-bit or 32-bit rows). Colour indices are zero based.3. If the first byte is zero.. 8. The second byte defines their colour indices. 256 colour images: 93 . the second defines an escape code. left-to-right. If you are storing black and white pictures you should stick to this. 16 colour images: n (Byte 1) c (Byte 2) >0 0 0 0 0 any 0 1 2 >=3 Description n pixels to be drawn. meaning a pixel colour of 0 represents the first colour table entry. There are no colour table entries. For images with more than 256 colours there is no colour table. No zero padding necessary. If both colour indices are the same. The first holds its red. The 1st. Remember padding with zeros up to a 32-bit boundary.. Up to 12 bits of zeros follow. Encoding type 1-bit B&W images 1 0 4-bit 16 colour images 8-bit 256 colour images 16-bit High colour images 24-bit True colour images 4 0 8 0 16 0 24 0 4-bit 16 colour images 4 2 8-bit 256 colour images 8 1 8. The first byte specifies the number of consecutive pixels with the same colour. The following table provides the description of the raster data compression for 8-bit. 5th. its highest order bit representing the leftmost pixel of these 8.9. Every 4 bytes hold 1 pixel. Every 2 bytes hold 1 pixel. In all of them.2 BMP Raster Data Encoding Depending on the image BitCount and on the Compression flag there are 6 different encoding schemes. The fourth byte is reserved and should be zero.1. and the third its blue intensity. a pixel colour of 255 (if there are that many) represents the 256th entry. the even pixels' colour is in c's low-order 4 bits. There are no colour table entries. Every byte holds 1 pixel. Pixel data is stored in 2-byte chunks. Some readers assume that 0 is black and 1 is white. BitCount Compression Remarks Every byte holds 8 pixels. There are 2 colour table entries. The second byte defines two colour indices. Every byte holds 2 pixels. These colours do not have to be the 16 MS-Windows standard colours.3 Raster Data Compression The following table provides the description of the raster data compression for 4-bit. to put the file/memory pointer on a 16-bit boundary again. The pixel data is stored in 2-byte chunks.3.0 Administrator Manual Chapter 8: Geographic Data lowermost row stored in the bitmap. There are 16 colour table entries.AT310_AM_E2 Atoll 3. • • • • Pixels are stored bottom-up. with any other 2 colours this is not an issue. The following 2 bytes define an unsigned offset in x and y direction (y being up).9. Due to the 16bit-ness of this structure this will always be either two zero bytes or none. it results in just n pixels of colour c.. .

The following c bytes will be read as single pixel colours just as in uncompressed files. The header file is made of rows. PNG supports palettebased (palettes of 24-bit RGB or 32-bit RGBA colors). or RGBA images. Clutter Classes Sample 100. The following 2 bytes define an unsigned offset in x and y direction (y being up).4 PNG Format Portable Network Graphics (PNG) is a bitmapped image format that employs lossless data compression. Atoll stores the georeferencing information in this file for future imports of the PNG so that the PGW file can be used during the import procedure for automatic geo-referencing.9. greyscale. When exporting (saving) a PNG file.00 0.org/TR/PNG/. The world file parameters are: Line 1 2 3 4 5 6 Description x dimension of a pixel in map units amount of translation amount of rotation negative of the y dimension of a pixel in map units x-axis map coordinate of the centre of the upper-left pixel y-axis map coordinate of the centre of the upper-left pixel 94 .00 60000. For more information on the PNG file format.w3.00 8.00 0. A zero follows.00 -100.9. 8. and so does not support other color spaces (such as CMYK). but exports headers with BPW file extensions.Atoll 3. each row having the following description: Line 1 2 3 4 5 6 Description x dimension of a pixel in map units amount of translation amount of rotation negative of the y dimension of a pixel in map units x-axis map coordinate of the centre of the upper-left pixel y-axis map coordinate of the centre of the upper-left pixel Atoll supports BPW and BMW header file extensions for Import.3.9. not professional graphics.0 Administrator Manual Chapter 8: Geographic Data © Forsk 2011 n (Byte 1) c (Byte 2) >0 0 0 0 0 any 0 1 2 >=3 Description n pixels of colour number c End-of-line End-of-Bitmap Delta. if c is odd.1 PGW Header File 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. see www.00 2679900. PNG was designed for transferring images on the Internet.4.1. an associated file with PGW extension is created with the same name and in the same directory as the PNG file it refers to. putting the file/memory pointer on a 16-bit boundary again. 8.4 BPW/BMW Header File The header file is a text file that describes how data are organised in the BMP file. RGB. The skipped pixels should get a colour zero.

and Atoll. You can find more information at http://www. HEADER). defined in the corresponding MIF files. Each section ends with a 0 followed by the string ENDSEC. The text data is delimited with one row per record.com. SECTION. Each section starts with a group code 0 followed by the string. All of these files need to be present and kept together for the table to work.7 MIF Format MapInfo Interchange Format (MIF) allows various types of data to be attached to a variety of graphical items.com. 8. These ASCII files are editable. and the DBF file stores the attribute information of features. The SHP file stores the feature geometry.9. defined in the corresponding PRJ files.9. or Line Feed between lines. see "Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Files" on page 172. For more information about defining the mapping between coordinate systems. and Atoll. Each group code and value is a separate line. non-topological format for storing geometric locations and attribute information of geographic features. SHP files usually have associated SHX and DBF files. and work on all platforms supported by MapInfo. indicate the type of value that follows. The codes. a MIF and a MID file. You can define mappings between the coordinate system used for the ESRI vector files. These are defined as follows: • • • • • TAB: table structure in ASCII format DAT: table data storage in binary format MAP: storage of map objects in binary format ID: index to the MapInfo graphical objects (MAP) file IND: index to the MapInfo tabular (DAT) file You can find more information at http://www. The TAB file must have the following format: !table !version 300 !charset WindowsLatin1 Definition Table File "raster.AT310_AM_E2 Atoll 3. when you import a vector file. Inc.mapinfo. when you import a vector file.0 Administrator Manual Chapter 8: Geographic Data 8. the file header and the data section.8 TAB Format TAB files (MapInfo Tables) are the native format of MapInfo. TAB files are also supported as georeference information files for raster files (BMP and TIFF). For more information about defining the mapping between coordinate systems. You can define mappings between the coordinate system used for the MapInfo vector files. They actually consist of a number of files with extensions such as TAB. DXF files can have ASCII or binary formats. this file is displayed as a feature table. When there is no MID file. the SHX file stores the index of the feature geometry. In this way.9.bmp" Type "RASTER" 95 . known as group codes. You can define mappings between the coordinate system used for the MapInfo vector files. Two files.5 DXF Format Atoll is capable of importing and working with AutoCAD drawings in the Drawing Interchange Format (DXF). and MAP. In this way. Carriage Return plus Line Feed. DAT. and Carriage Return. when you import a vector file. Atoll can detect the correct coordinate system automatically. 8. see "Mapping Atoll Coordinate Systems with MapInfo/ ESRI Vector Files" on page 172. Atoll can detect the correct coordinate system automatically. For more information about defining the mapping between coordinate systems. defined in the corresponding MIF files. DXF files are organized into sections of records containing the group codes and their values.1. The MID file is optional. DXF files are composed of pairs of codes and associated values. But only the ASCII DXF files can be used in Atoll.6 SHP Format ESRI (Environmental Systems Research Institute. see "Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Files" on page 172.mapinfo.) ArcView GIS Shape files have a simple. A shape file is one of the spatial data formats that you can work with in ArcExplorer. contain MapInfo data. The MIF file has two sections.9. In this way. This is followed by a group code 2 and a string indicating the name of the section (for example. and Atoll. When a shape file is added as a theme to a view. all fields are blank. Atoll can detect the correct coordinate system automatically. 8. Graphics reside in the MIF file while the text contents are stored in the MID file. easy to generate.

10 Erdas Imagine Format Erdas Imagine IMG files use the Erdas Imagine Hierarchical File Format (HFA) structure.e. Therefore. You can create an MNU file to improve the clutter class map loading. containing RGB information (three bands are provided: the first band is for Blue. they are used to enhance performance when decreasing the resolution of the display. 96 . (llxmap.nrows) Label "Pt 2". the second one is for Green and the third for Red).. These files are automatically geo-referenced.llymap) (0.9. For more information.0 Administrator Manual Chapter 8: Geographic Data © Forsk 2011 (ulxmap. if there are pyramids (storage of different resolution layers).0) Label "Pt 1". (lrxmap.1. The colour-to-code association (raster maps) may be automatically imported from the IMG file. Datum etc.0) Label "Pt 4" The fields in bold are described below: Field File "raster. degrees or feet) The size of each cell in measurement units Coordinate space information (Projection.9. they do not require any additional file for geo-reference.urymap) (ncols. • 8. The ECW format is developed by Earth Resource Mapping.) 8. or clutter height).9.lrymap) (ncols. clutter class. For image files. For any type of file.Atoll 3.bmp) x coordinate of the centre of the upper-left pixel in metres y coordinate of the centre of the upper-left pixel in metres x coordinate of the centre of the lower-left pixel in metres y coordinate of the centre of the lower-left pixel in metres x coordinate of the centre of the lower-right pixel in metres y coordinate of the centre of the lower-right pixel in metres x coordinate of the centre of the upper-right pixel in metres y coordinate of the centre of the upper-right pixel in metres Number of rows in the image Number of columns in the image 8.nrows) Label "Pt 3". In case of 3 bands. 32 bit per pixel files are not supported. which contain numerical information (such as DTM). • If you are using compressed Erdas Imagine files. the number of supported bands is either 1 (colour palette is defined separately) or 3 (no colour palette but direct RGB information for each pixel).bmp" ulxmap ulymap llxmap llymap lrxmap lrymap urxmap urymap nrows ncols Description Name of the raster file (e.9 ECW Format The Enhanced Compressed Wavelet (ECW) files are geo-referenced image files. i. Each compressed image file contains a header carrying the following information about the image: • • • • • • The image size expressed as the number of cells across and down The number of bands (RGB images have three bands) The image compression rate The cell measurement units (meters. only 8 bit per pixel format is supported.g. Compressed files can be exported to uncompressed files using Atoll. can be considered as 24 bit per pixel files. and are stored in files with the GRD extension. (urxmap.. performance may be improved by either hiding the Status Bar or by hiding some of the information displayed in the Status Bar (altitude. ECW can compress images with up to a 100-to-1 compression ratio. see "Hiding Information Displayed in the Status Bar" on page 179. Some aspects of working with Erdas Imagine format in Atoll are: • • • • Atoll supports uncompressed as well as compressed (or partially compressed) IMG files for DTM.11 Planet EV/Vertical Mapper Geographic Data Format Vertical Mapper offers two types of grids: • Numerical continuous grids. raster.ulymap) (0. 8-bit images.

000000 nodata_value 0 . which contain alphanumeric (characters) information. whereas BIL images use only a metric coding.9. except for DTM images. You can open a WLD file using any ASCII text editor. IST images come from Istar and DIS images come from IGN (Institut Géographique National). followed by the content in the form of cell values. population.1. The contents of an ArcView Grid file are in ASCII and consist of a header. //Row 1 Top of the raster. it is an ASCII text file containing six lines. 8. and are stored in files with the GRC extension. Grid resolution. other data maps. GRC: DTM. clutter classes.. image. This is the geographic data format used by Planet EV. environment traffic. clutter classes and/or heights. OR Significant value relative to the bin centre or corner. and other data types. OR Significant value relative to the bin centre or corner. The format of these files is as follows: ncols XXX nrows XXX xllcenter XXX xllcorner XXX yllcenter yllcorner XXX cellsize XXX Number of columns of the grid (XXX columns).9. 8.12 ArcView Grid Format The ArcView Grid format (TXT) is an ASCII format dedicated to defining raster maps. Atoll is capable of supporting the Vertical Mapper Classified Grid (GRC) and Vertical Mapper Continuous Grid (GRD) file formats in order to import and export: • • GRD: DTM. and other data types. Number of rows of the grid (XXX rows).14 Generic Raster Header File WLD is a new Atoll specific header format that can be used for any raster data file for georeferencing. The WLD file structure is simple.. So. traffic density. population. each row having the following description: 97 . it is possible to directly import geographic data from Planet EV to Atoll using this format. It is also possible to export coverage predictions in GRD and GRC formats. population.13 Other File Formats Atoll supports IST and DIS formats. Bottom of the raster. These are ASCII files used for Digital Terrain Models only.9. the IST format uses a decimetric coding for altitudes. images. describing the content. The WLD file is a text file that describes how data are organised in the associated raster data file. Atoll can use the corresponding WLD file to read the georeferencing information related to the raster data file.AT310_AM_E2 Atoll 3. Syntax: ncols number of values separated by spaces. 8. The WLD file contains the spatial reference data of any associated raster data file. It may be used to export any raster map such as DTM. Description of the first row. : : //Row N Sample ncols 303 nrows 321 xllcorner 585300. clutter heights.0 Administrator Manual Chapter 8: Geographic Data • Classified grids.000000 yllcorner 5615700. nodata_value XXXOptional value corresponding to no data (no information). For DTM images. The IST format works in exactly the same way as the BIL format. The header file is made of rows. and even coverage predictions. image.000000 cellsize 100. At the time of import of any raster data file.

15 Planet Formats The Planet geographic data are described by a set of files stored in the same location. the value -9999 corresponds to ‘No data’ which is supported by Atoll. Line Spheroid Zone Description Projection Central meridian Latitude and longitude of projection central meridian and equivalent x and y coordinates in meters (optional) In the associated binary file.00 Description x dimension of a pixel in map units amount of translation amount of rotation negative of the y dimension of a pixel in map units x-axis map coordinate of the centre of the upper-left pixel y-axis map coordinate of the centre of the upper-left pixel 8.0 Administrator Manual Chapter 8: Geographic Data © Forsk 2011 Line 1 2 3 4 5 6 Clutter Classes File Sample 100.1 DTM Files The DTM directory consists of three files.Atoll 3.1.00 -100. Sample Index file associated with height file (DTM data): sydney1 303900 343900 6227900 6267900 50 98 . It contains five columns. 8.00 0. The format of the index file is as follows: Field File name East min East max North min North max Square size • Type Text Float Float Float Float Float Description Name of file referenced by the index file x-axis map coordinate of the centre of the upper-left pixel in meters x-axis map coordinate of the centre of the upper-right pixel in meters y-axis map coordinate of the centre of the lower-left pixel in meters y-axis map coordinate of the centre of the upper-left pixel in meters Dimension of a pixel in meters The projection file provides information about the projection system used. This file is optional. It is an ASCII text file with four lines maximum.00 2679900. The directory structure depends on the geographic data type.00 0.00 60000.9.9. it is an ASCII text file that holds position information about the file. You can open an index file using any ASCII text editor.15. the height file and two other files detailed below: • The index file structure is simple.

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 8: Geographic Data

Projection file associated with height file (DTM data): Australian-1965 56 UTM 0 153 500000 10000000

8.9.15.2 Clutter Class Files
The Clutter directory consists of three files; the clutter file and two other files detailed below: • The menu file, an ASCII text file, defines the feature codes for each type of clutter. It consists of as many lines (with the following format) as there are clutter codes in the clutter data files. This file is optional. Field Clutter-code Feature-name • Type Integer (>1) Text (32) Description Identification code for clutter class Name associated with the clutter-code. (It may contain spaces)

The index file gives clutter spatial references. The structure of clutter index file is the same as the structure of DTM index file. In the associated binary file, the value -9999 corresponds to ‘No data’ which is supported by Atoll.

Sample Menu file associated with the clutter file: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 open sea inlandwater residential meanurban denseurban buildings village industrial openinurban forest parks denseurbanhigh blockbuildings denseblockbuild rural mixedsuburban

8.9.15.3 Vector Files
Vector data comprises terrain features such as coastlines, roads, etc. Each of these features is stored in a separate vector file. Four types of files are used, the vector file, where x and y coordinates of vector paths are stored, and three other files detailed below: • The menu file, an ASCII text file, lists the vector types stored in the database. The menu file is composed of one or more records with the following structure: Field Vector type code Type Integer (>0) Description Identification code for the vector type

99

Atoll 3.1.0 Administrator Manual Chapter 8: Geographic Data

© Forsk 2011

Field Vector type name

Type Text (32)

Description Name of the vector type

The fields are separated by space character. • The index file, an ASCII text file, lists the vector files and associates each vector file with one vector type, and optionally with one attribute file. The index file consists of one or more records with the following structure: Field Vector file name Attribute file name Dimensions Type Text (32) Text (32) Description Name of the vector file Name of attribute file associated with the vector file (optional) eastmin: minimum x-axis coordinate of all vector path points in the vector file eastmax: maximum x-axis coordinate of all vector path points in the vector file northmin: minimum y-axis coordinate of all vector path points in the vector file northmax: maximum y-axis coordinate of all vector path points Name of the vector type with which the vector file is associated. This one must match exactly a vector type name field in the menu file.

Real

Vector type name

Text (32)

The fields are separated by spaces. • Sample Index file associated with the vector files sydney1.airport 313440 333021 6239426 6244784 airport sydney1.riverlake 303900 342704 6227900 6267900 riverlake sydney1.coastline 322837 343900 6227900 6267900 coastline sydney1.railways 303900 336113 6227900 6267900 railways sydney1.highways 303900 325155 6240936 6267900 highways sydney1.majstreets 303900 342770 6227900 6267900 majstreets sydney1.majorroads 303900 342615 6227900 6267900 majorroads The attribute file stores the height and description properties of vector paths. This file is optional.

8.9.15.4 Image Files
The image directory consists of two files, the image file with TIFF extension and an index file with the same structure as the DTM index file structure.

8.9.15.5 Text Data Files
The text data directory consists of: • The text data files are ASCII text files with the following format:

Airport 637111.188 3094774.00 Airport 628642.688 3081806.25 Each file contains a line of text followed by easting and northing of that text, etc. • The index file, an ASCII text file, stores the position of each text file. It consists of one or more records with the following structure: Field File name East Min East Max Type Text (32) Real Real Description File name of the text data file Minimum x-axis coordinate of all points listed in the text data file Maximum x-axis coordinate of all points listed in the text data file

100

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 8: Geographic Data

Field North Min North Max Text feature

Type Real Real Text (32)

Description Minimum y-axis coordinate of all points listed in the text data file Maximum y-axis coordinate of all points listed in the text data file This field is omitted in case no menu file is available.

The fields are separated by spaces. railwayp.txt -260079 693937 2709348 3528665 Railway_Station airport.txt -307727 771663 2547275 3554675 Airport ferryport.txt 303922 493521 2667405 3241297 Ferryport • 1 2 3 The menu file, an ASCII text file, contains the text features. This file is optional. Airport Ferryport Railway_Station

8.9.15.6 MNU Format
An MNU file is used for importing clutter classes or raster traffic files in TIFF, BIL, and IMG formats. It gives the mapping between the clutter or traffic class code and the class name. It is a text file with the same name as the clutter or traffic file with MNU extension. It must be stored at the same folder as the clutter or traffic file. It has the same structure as the menu file used in the Planet format. Field Class code Class name Type Integer (>0) Text (50) Description Identification code for the clutter (or traffic) class Name of the clutter (or traffic) class. It may contain spaces.

Either space or tab can be used as the separator. Clutter Classes Sample An MNU file associated to a clutter classes file: 0 1 2 3 4 5 none open sea inland_water residential meanurban

101

Atoll 3.1.0 Administrator Manual Chapter 8: Geographic Data

© Forsk 2011

102

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 9: Radio Data Formats

9 Radio Data 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, and WiMAX 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 transciever (TRX) can carry one ARFCN which may 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 "transmitterTRX type" pair. Base station: This is the generic name for a cell site ("site-transmitter-cell" or "site-transmitter-subcells"). Technologyspecific 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.

• • • • • • • •

9.1 XML Import/Export Format
All the data tables in an Atoll document can be exported to XML files. Atoll creates the following files when data tables are exported to XML files: • • An index.xml file which contains the mapping between the data tables in Atoll and the XML file created for each table. One XML file per data table which contains the data table format (schema) and the data.

When XML files are imported to a document, the table and field definitions are not modified, i.e., the Networks and CustomFields tables are exported to XML file but are not imported. The following sections describe the structures of the XML files created at export.

9.1.1 Index.xml File Format
The index.xml file stores the system (GSM, UMTS, etc.) and the technology (TDMA, CDMA, etc.) of the document, and the version of Atoll used for exporting the data tables to XML files. It also contains the mapping between the data tables in the Atoll document and the XML file corresponding to each data table. The root tag <Atoll_XML_Config...> of the index.xml file contains the following attributes: Attribute Atoll_File_System Atoll_File_Technology Atoll_File_Version Description Corresponds to the SYSTEM_ field of the Networks table of the exported document Corresponds to the TECHNOLOGY field of the Networks table of the exported document Corresponds to the Atoll version

The index file also contains the mapping between the tables exported from Atoll and the XML files corresponding to each table. This list is sorted in the order in which tables must be imported in Atoll. The list is composed of <XML_Table.../> tags with the following attributes: Attribute XML_File Atoll_Table Description Corresponds to the exported XML file name (e.g., "Sites.xml") Corresponds to the exported Atoll table name (e.g., "Sites")

A sample extract of the index.xml is given below:

103

Atoll 3.1.0 Administrator Manual Chapter 9: Radio Data Formats

© Forsk 2011

<Atoll_XML_Config Atoll_File_System="UMTS" Atoll_File_Technology="CDMA" Atoll_File_Version="3.x.x build xxxx"> <XML_Table XML_File="CustomFields.xml" Atoll_Table="CustomFields" /> <XML_Table XML_File="CoordSys.xml" Atoll_Table="CoordSys" /> ... </Atoll_XML_Config> Note that no closing tag </XML_Table> is required.

9.1.2 XML File Format
Atoll creates an XML file per exported data table. This XML file has two sections, one for storing the description of the table structure, and the second for the data itself. The XML file uses the standard XML rowset schema (schema included in the XML file between <s:Schema id=‘RowsetSchema’> and </s:Schema> tags). Rowset Schema The XML root tag for XML files using the rowset schema is the following: <xml xmlns:s='uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882' xmlns:dt='uuid:C2F41010-65B3-11d1-A29F-00AA00C14882' xmlns:rs='urn:schemas-microsoft-com:rowset' xmlns:z='#RowsetSchema'> The schema definition follows the root tag and is enclosed between the following tags: <s:Schema id=‘RowsetSchema’> <!-Schema is defined here, using <s:ElementType> and <s:AttributeType> tags -> </s:Schema> In the rowset schema, after the schema description, the data are enclosed between <rs:data> and </rs:data>. Between these tags, each record is handled by a <z:row … /> tag having its attributes set to the record field values since in the rowset schema, values are handled by attributes. Note that no closing tag </z:row> is required. A sample extract of a Sites.xml file containing the Sites table with only one site is given below: <xml xmlns:s='uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882' xmlns:dt='uuid:C2F41010-65B3-11d1-A29F-00AA00C14882' xmlns:rs='urn:schemas-microsoft-com:rowset' xmlns:z='#RowsetSchema'> <s:Schema id='RowsetSchema'> <s:ElementType name='row' content='eltOnly' rs:updatable='true'> <s:AttributeType name='NAME' rs:number='1' rs:maydefer='true' rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='NAME' rs:keycolumn='true'> <s:datatype dt:type='string' dt:maxLength='50'/> </s:AttributeType> <s:AttributeType name='LONGITUDE' rs:number='2' rs:maydefer='true' rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='LONGITUDE'> <s:datatype dt:type='float' dt:maxLength='8' rs:precision='15' rs:fixedlength='true'/> </s:AttributeType> <s:AttributeType name='LATITUDE' rs:number='3' rs:maydefer='true' rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='LATITUDE'> <s:datatype dt:type='float' dt:maxLength='8' rs:precision='15' rs:fixedlength='true'/> </s:AttributeType>

104

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 9: Radio Data Formats

<s:AttributeType name='ALTITUDE' rs:number='4' rs:nullable='true' rs:maydefer='true' rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='ALTITUDE'> <s:datatype dt:type='r4' dt:maxLength='4' rs:precision='7' rs:fixedlength='true'/> </s:AttributeType> <s:AttributeType name='COMMENT_' rs:number='5' rs:nullable='true' rs:maydefer='true' rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='COMMENT_'> <s:datatype dt:type='string' dt:maxLength='255'/> </s:AttributeType> <s:extends type='rs:rowbase'/> </s:ElementType> </s:Schema> <rs:data> <rs:insert> <z:row NAME='Site0' LONGITUDE='8301' LATITUDE='-9756'/> </rs:insert> </rs:data> </xml>

9.2 RF 2D Antenna Pattern Format
This section describes the format of the DIAGRAM field of the Antennas table. This field stores the antenna diagrams in a 2D (angle vs. attenuation) format. This is the format of the contents of the DIAGRAM field of the Antennas table when it is copied from, pasted to, imported to (from TXT or CSV files), and exported from (from TXT, CSV, or XLS files) the Antennas table. Antenna patterns can also be imported in Planet 2D-format antenna files and 3D antenna files. The file format required for 3D antenna file import is described in "Import Format of 3D Antenna Pattern Text Files" on page 107. The format of 2D antenna patterns containing co-polar diagrams only can be understood from Figure 9.1 on page 105.
Pattern Discriptor 1 Co-polar Horizontal Diagram Pattern Discriptor 2 Co-polar Vertical Diagram End

2 0 0 360 0 0 1 0 2 0.1 … 1 0 360 0 0 1 0.1 … 0
Figure 9.1: 2D RF Antenna Pattern Format Containing Co-polar Diagrams Only The contents of the DIAGRAM field are formatted as follows: • Pattern Descriptor 1: Space-separated list of parameters. • First entry: The number of co-polar diagrams. For example, 2. • Second entry: First co-polar diagram type = 0 for azimuth (horizontal) diagram. • Third entry: The elevation angle of the azimuth diagram. • Fourth entry: The number of angle-attenuation pairs in the first co-polar diagram. For example, 360. Co-polar Horizontal Diagram: Horizontal co-polar diagram (the second entry in the preceding descriptor is 0). The format is space-separated angle attenuation pairs. For example, 0 0 1 0 2 0.1.... Pattern Descriptor 2: Space-separated list of parameters. • First entry: Second co-polar diagram type = 1 for elevation (vertical) diagram. • Second entry: The azimuth angle of the elevation diagram. • Third entry: The number of angle-attenuation pairs in the second co-polar diagram. For example, 360. Co-polar Vertical Diagram: Vertical co-polar diagram (the first entry in the preceding descriptor is 1). The format is space-separated angle attenuation pairs. For example, 0 0 1 0.1.... End: The number cross-polar diagrams = 0.

• •

• •

The format of 2D antenna patterns containing co-polar and cross-polar diagrams can be understood from Figure 9.2 on page 106.

105

Atoll 3.1.0 Administrator Manual Chapter 9: Radio Data Formats

© Forsk 2011

Pattern Discriptor 1

Co-polar Horizontal Diagram

Pattern Discriptor 2

Co-polar Vertical Diagram

Pattern Discriptor 3

Cross-polar Horizontal Diagram

Pattern Discriptor 4

Cross-polar Vertical Diagram

2 0 0 360 0 0 1 0 2 0.1 … 1 0 360 0 0 1 0.1 … 2 0 0 360 0 0 1 0 2 0.1 … 1 0 360 0 0 1 0.1 …
Figure 9.2: 2D RF Antenna Pattern Format Containing Co-polar and Cross-polar Diagrams The contents of the DIAGRAM field are formatted as follows: • Pattern Descriptor 1: Space-separated list of parameters. • First entry: The number of co-polar diagrams. For example, 2. • Second entry: First co-polar diagram type = 0 for azimuth (horizontal) diagram. • Third entry: The elevation angle of the azimuth diagram. • Fourth entry: The number of angle-attenuation pairs in the first co-polar diagram. For example, 360. Co-polar Horizontal Diagram: Horizontal co-polar diagram (the second entry in the preceding descriptor is 0). The format is space-separated angle attenuation pairs. For example, 0 0 1 0 2 0.1.... Pattern Descriptor 2: Space-separated list of parameters. • First entry: Second co-polar diagram type = 1 for elevation (vertical) diagram. • Second entry: The azimuth angle of the elevation diagram. • Third entry: The number of angle-attenuation pairs in the second co-polar diagram. For example, 360. Co-polar Vertical Diagram: Vertical co-polar diagram (the first entry in the preceding descriptor is 1). The format is space-separated angle attenuation pairs. For example, 0 0 1 0.1.... Pattern Descriptor 3: Space-separated list of parameters. • First entry: The number of cross-polar diagrams. For example, 2. • Second entry: First cross-polar diagram type = 0 for azimuth (horizontal) diagram. • Third entry: The elevation angle of the azimuth diagram. • Fourth entry: The number of angle-attenuation pairs in the first cross-polar diagram. For example, 360. Cross-polar Horizontal Diagram: Horizontal cross-polar diagram (the second entry in the preceding descriptor is 0). The format is space-separated angle attenuation pairs. For example, 0 0 1 0 2 0.1.... Pattern Descriptor 4: Space-separated list of parameters. • First entry: Second cross-polar diagram type = 1 for elevation (vertical) diagram. • Second entry: The azimuth angle of the elevation diagram. • Third entry: The number of angle-attenuation pairs in the second cross-polar diagram. For example, 360. Cross-polar Vertical Diagram: Vertical cross-polar diagram (the first entry in the preceding descriptor is 1). The format is space-separated angle attenuation pairs. For example, 0 0 1 0.1....

• •

• •

• •

You may use a 3rd party software or develop a tool to to convert the contents of the DIAGRAM field into binary. In binary, each antenna is described by a header and a list of value pairs. The header is defined as follows: • • • • • • • flag: (Integer, 32 bits) -1 for omni diagrams, 0 for directional num: (Short integer, 16 bits) Number of diagrams (0, 1, 2, 3, 4) siz0: (Short integer, 16 bits) Size of the first diagram (horizontal co-polar section, elevation = 0°) siz1: (Short integer, 16 bits) Size of the second diagram (vertical co-polar section, azimuth = 0°) siz2: (Short integer, 16 bits) Size of the third diagram (horizontal cross-polar) siz3: (Short integer, 16 bits) Size of the fourth diagram (vertical cross-polar) prec: (Short integer, 16 bits) Precision of the following angle values (100)

Then follows the content of each of the defined diagrams, i.e., the diagrams whose sizes (siz0, siz1, siz2, siz3) are not zero. Each diagram consists of a list of value pairs. The number of value pairs in a list depends on the value of the siz0, siz1, siz2, and siz3 parameters. For example, siz2 = 5 means there are five value pairs in the third diagram. The value pairs in each list are: • • ang: (Short integer, 16 bits) The first component of the value pair is the angle in degrees multiplied by 100. For example, 577 means 5.77 degrees. loss: (Short integer, 16 bits) The second component of the value pair is the loss in dB for the given angle ang.

All the lists of value pairs are concatenated without a separator.

106

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 9: Radio Data Formats

9.3 Import Format of 3D Antenna Pattern Text Files
Text files containing 3D antenna patterns that may be imported in Atoll must have the following format: • • Header: The text file may contain a header with additional information. When you import the antenna pattern you can indicate the row number in the file where the header ends and the antenna pattern begins. Antenna Pattern: Each row contains three values to describe the 3D antenna pattern. The columns containing the values can be in any order: • Azimuth: Allowed range of values is from 0° to 360°. The smallest increment allowed is 1°. • Tilt: Allowed range of values is from -90° to 90° or from 0° to 180°. The smallest increment allowed is 1°. • Attenuation: The attenuation in dB.

9.4 Microwave 2D Antenna Pattern Format
This section describes the format of the PATTERN field of the MW Antennas table. This field stores the antenna diagrams in a 2D (angle vs. attenuation) format. This is the format of the contents of the PATTERN field of the MW Antennas table when it is copied from, pasted to, imported to (from TXT or CSV files), and exported from (from TXT, CSV, or XLS files) the MW Antennas table. Antenna patterns can also be imported in Planet 2D-format antenna files and 3D antenna files. The file format required for 3D antenna file import is described in "Import Format of 3D Antenna Pattern Text Files" on page 107. The format of 2D antenna patterns can be understood from Figure 9.3 on page 107.
Pattern Discriptor 1 Co-polar H-V Diagram Pattern Discriptor 2 Co-polar H-H Diagram

Pattern Discriptor 3

Co-polar V-V Diagram

Pattern Discriptor 4

Co-polar V-H Diagram

Pattern Discriptor 5

Cross-polar H-V Diagram

Pattern Discriptor 6

Cross-polar H-H Diagram

Pattern Discriptor 7

Cross-polar V-V Diagram

Pattern Discriptor 8

Cross-polar V-H Diagram

4 0 1 0 360 0 0 1 0.5 ... 0 0 0 360 0 0 1 0.5 ... 1 1 0 360 0 0 1 0.5 ... 1 0 0 360 0 0 1 0.5 ... 4 0 1 0 360 0 0 1 0.5 ... 0 0 0 360 0 0 1 0.5 ... 1 1 0 360 0 0 1 0.5 ... 1 0 0 360 0 0 1 0.5 ...
Figure 9.3: 2D Microwave Antenna Pattern Format The contents of the PATTERN field are formatted as follows: • Pattern Descriptor 1: Space-separated list of parameters. • First entry: The number of co-polar diagrams. For example, 4. • Second and third entries: First co-polar diagram type = 0 1, for H-V diagram. • Fourth entry: The elevation angle of the azimuth diagram. • Fifth entry: The number of angle-attenuation pairs in the first co-polar diagram. For example, 360. Co-polar H-V Diagram: Co-polar H-V diagram (the second and third entries in the preceding descriptor are 0 1). The format is space-separated angle attenuation pairs. For example, 0 0 1 0.5.... Pattern Descriptor 2: Space-separated list of parameters. • First and second entries: Second co-polar diagram type = 0 0, for H-H diagram. • Third entry: The azimuth angle of the elevation diagram.

• •

107

0 0 1 0.5. The format is space-separated angle attenuation pairs..5. The format is space-separated angle attenuation pairs. 9. Pattern Descriptor 4: Space-separated list of parameters. 0 0 1 0. • First and second entries: Fourth cross-polar diagram type = 1 0.. For example.050 recommendations. for V-V diagram. Pattern Descriptor 8: Space-separated list of parameters. For example. The format is space-separated angle attenuation pairs. The format is space-separated angle attenuation pairs. For example. 4. For example. for H-H diagram.. • Fourth entry: The number of angle-attenuation pairs in the third cross-polar diagram. For example. • Third entry: The azimuth angle of the elevation diagram... Co-polar V-H Diagram: Co-polar V-H diagram (the first and second entries in the preceding descriptor are 1 0). For example.. • First and second entries: Third cross-polar diagram type = 1 1. 0 0 1 0. 360. 0 0 1 0. 360. The NSMA formats are described below. for V-V diagram.89.89.. For example. • • • • • • • • • • • 9..5.. • First and second entries: Third co-polar diagram type = 1 1.5. For example. The format is space-separated angle attenuation pairs. Pattern Descriptor 7: Space-separated list of parameters. Cross-polar H-H Diagram: Cross-polar H-H diagram (the first and second entries in the preceding descriptor are 0 0). 360. • First and second entries: Second cross-polar diagram type = 0 0. Pattern Descriptor 5: Space-separated list of parameters.Atoll 3. • Third entry: The elevation angle of the azimuth diagram.. For example...003 and WG16.1 WG 16.99. Cross-polar V-H Diagram: Cross-polar V-H diagram (the first and second entries in the preceding descriptor are 1 0). for V-H diagram.. • Second and third entries: First cross-polar diagram type = 0 1. Pattern Descriptor 6: Space-separated list of parameters. 0 0 1 0.. For example. 0 0 1 0.5.5 Microwave NSMA Antenna File Formats You can import microwave antennas in Atoll from files in Planet microwave antenna and standard NSMA (National Spectrum Managers Association) formats. • First and second entries: Fourth co-polar diagram type = 1 0. For example. 360. For example. 360. • Fourth entry: The number of angle-attenuation pairs in the second cross-polar diagram. Cross-polar H-V Diagram: Cross-polar H-V diagram (the second and third entries in the preceding descriptor are 0 1).. which are described in the WG16. Pattern Descriptor 3: Space-separated list of parameters. • Fourth entry: The number of angle-attenuation pairs in the fourth cross-polar diagram.1. • Fifth entry: The number of angle-attenuation pairs in the first cross-polar diagram. For example.5. • Third entry: The azimuth angle of the elevation diagram..003 Format The antenna pattern file is an ASCII text file with the following structure: Field Antenna Manufacturer Antenna Model number Comment FCC ID number Reverse pattern ID number Length (Char) 30 30 30 16 16 Description Name under which the data was filed with the FCC Full model number as used when the data was filed with the FCC Field for comments on the current revision ID number issued by the Common Carrier Branch of the FCC This lists the reverse pattern FCC ID number 108 .5. • Fourth entry: The elevation angle of the azimuth diagram. 0 0 1 0.0 Administrator Manual Chapter 9: Radio Data Formats © Forsk 2011 • • • Fourth entry: The number of angle-attenuation pairs in the second co-polar diagram. • First entry: The number of cross-polar diagrams. • Third entry: The elevation angle of the azimuth diagram. Co-polar V-V Diagram: Co-polar V-V diagram (the first and second entries in the preceding descriptor are 1 1). • Third entry: The azimuth angle of the elevation diagram. 360.. The format is space-separated angle attenuation pairs. The format is space-separated angle attenuation pairs. Co-polar H-H Diagram: Co-polar H-H diagram (the first and second entries in the preceding descriptor are 0 0). • Fourth entry: The number of angle-attenuation pairs in the third co-polar diagram. for H-V diagram.... Cross-polar V-V Diagram: Cross-polar V-V diagram (the first and second entries in the preceding descriptor are 1 1).. • Fourth entry: The number of angle-attenuation pairs in the fourth co-polar diagram. 360.5. For example. For example. for V-H diagram.

Gain of the antenna at mid-band (dBi) This is the included angle centered on the main beam of the antenna and defines the angle where the antenna response falls -3 dB The data is preceded by an indication of the polarization the data. 0 degrees. MHP-100A120D (none) M15028 M15027 11-25-85 NONE 10700-11700 MHZ 48. The frequency is in Megahertz. This is to identify the full frequency range for which this pattern is valid and agrees with the range as specified in the printed pattern. the angle of observation starts from -180 degrees (defined as the left side of the antenna) and decrease in angle to the main beam . and then increase to +180 degrees.4 dB 0. The full data will cover the 10 (180) degrees centered about the main beam. the angle of observation starts from -5 (-90) degrees (defined as the antenna response below the main beam) and decrease in angle to the main beam. The antenna response is listed as dB down from the main lobe response and is shown as negative. HV: Horizontal polarized port response to a vertically polarized signal in the horizontal direction. The angle of observation is listed first followed by the antenna response.1. For the vertical direction. For the horizontal direction. Full compliment of data will show the antenna response in the horizontal direction for a 'horizontal cut' and in the vertical direction for a 'vertical cut'. 0 degrees.AT310_AM_E2 Atoll 3. they are to be duplicated in order that a full set of data be listed. All eight responses should be included.0 Administrator Manual Chapter 9: Radio Data Formats Field Date of data Manufacturer ID Number Frequency range Mid-band gain Half-power beam width Length (Char) 16 16 16 16 16 Description Date referenced on the published pattern Reference number assigned by the antenna manufacturer. The data is presented in two columns. The full data will cover the 360 degrees of the antenna. The commonly accepted polarization designators for linear polarization are to be used: HH: Horizontal polarized port response to a horizontally polarized signal in the horizontal direction. VV: Vertical polarized port response to a vertically polarized signal in the horizontal direction VH: Vertical polarized port response to a horizontally polarized signal in the horizontal direction ELHH: Horizontal polarized port response to a horizontally polarized signal in the vertical direction ELHV: Horizontal polarized port response to a vertically polarized signal in the vertical direction ELVV: Vertical polarized port response to a vertically polarized signal in the vertical direction ELVH: Vertical polarized port response to a horizontally polarized signal in the vertical direction The data count will be the number of data points to follow. If different polarizations have identical responses. and then increase to +5 (+90) degrees. Polarization +Space +Data count +Space 7 7 Angle +Space +Antenna Response +Space 7 7 Sample MARK ANTENNA PRODUCTS Inc.6 Deg HH 39 109 .

5 -63.5 -63. 160 -88 180 -88 HV 33 -180 -89 -170 -89 ..99.... 4..5.4 ..4 9. 180 -89 ELHH 7 -4 -36 -1..5 -63.0 Administrator Manual Chapter 9: Radio Data Formats © Forsk 2011 -180 -88 -160 -88 -150 -90 -97 -90 -66 -70 . 4 -36 ELHV 11 -4. 4 -36 ELVH 11 -4.050 Format The antenna pattern file is an ASCII text file with the following structure: 110 . 180 -89 VV 39 -180 -88 -160 -88 ...5 -63.Atoll 3..2 WG 16.1...4 ELVV 7 -4 -36 ...7 -30 .. 4.. 150 -90 160 -88 180 -88 VH 33 -180 -89 -170 -89 -160 -90 .4 .

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 9: Radio Data Formats

Field Revision Number Revision Date Comment1 Comment2 Antenna Manufacturer Model Number Pattern ID Number

Length (Char) 42 16 80 80 42 42 42

Abbreviated Name REVNUM REVDAT COMNT1 COMNT2 ANTMAN MODNUM PATNUM

Description Version of this standard to which the pattern conforms Date of the current revision of the standard Field for comments on the current revision Field for comments on the current revision Name of the antenna manufacturer Full model number as used when the data was taken NSMA ID number Used when more than one file is associated with a specific antenna model number. This field will contain the particular file number and the total number of files associated with that model number. An example of such a case would be a dual band antenna with two pattern files associated with it. Orientation of the feed hook when looking from the back of the antenna in the direction of the mechanical boresite Used to describe the antenna and its characteristics Used to describe the antenna and its characteristics Used to describe the antenna and its characteristics Used to describe the antenna and its characteristics Used to describe the antenna and its characteristics Date the pattern data was taken Lower frequency of the operating bandwidth of the antenna (MHertz). If the antenna can be operated in two distinct frequency bands, then the performance of the antenna in each band shall be described in separate files. Upper frequency of the operating bandwidth of the antenna (MHertz). If the antenna can be operated in two distinct frequency bands, then the performance of the antenna in each band shall be described in separate files Gain unit Gain of the antenna at the low frequency of the frequency band. The gain is in units described in GUNITS Gain of the antenna at the mid frequency of the frequency band and may include a full bandwidth tolerance. The gain is in units described in GUNITS Gain of the antenna at high frequency of the frequency band. The gain is in units described in GUNITS Nominal total width of the main beam at the -3 dB points in the azimuth plane. This is a mid-band measurement expressed in degrees and may include a full bandwidth tolerance Nominal total width of the main beam at the -3 dB points in the elevation plane. This is a mid-band measurement expressed in degrees and may include a full bandwidth tolerance Description of the antenna connector type Worst case limit of the antennas VSWR over the operating bandwidth Worst case power level in dB between the main lobe peak and the peak of the antenna’s back lobe. The back lobe peak does not necessarily point 180 degrees behind the main lobe. Amount that the main beam peak of the antenna (electrical boresite) is dowtilted below the mechanical boresite of the antenna. This is a midband measurement and may include a tolerance. This measurement is expressed in degrees.

Pattern File Number

13

FILNUM

Feed Orientation Description1 Description2 Description3 Description4 Description5 Date of data Low Frequency (MHz)

13 80 80 80 80 80 16 21

FEDORN DESCR1 DESCR2 DESCR3 DESCR4 DESCR5 DTDATA LOWFRQ

High Frequency (MHz)

21

HGHFRQ

Gain Units Low-band gain

15 12

GUNITS LWGAIN

Mid-band gain High-band gain

16 12

MDGAIN HGGAIN

Mid-band Az Bmwdth

16

AZWIDT

Mid-band El Bmwdth Connector Type VSWR Front-to-back Ratio(dB)

16 80 13 10

ELWIDT CONTYP ATVSWR FRTOBA

Electrical Downtilt (deg)

16

ELTILT

111

Atoll 3.1.0 Administrator Manual Chapter 9: Radio Data Formats

© Forsk 2011

Field Radiation Center (m)

Length (Char) 13

Abbreviated Name RADCTR

Description Height of the center of the radiating aperture above the mechanical bottom of the antenna (m). It is not necessarily the phase center of the antenna. Measurement made on dual polarization antennas. It is the maximum amount of power over the antennas operating bandwidth that is coupled between ports. It is the power ratio (dB) between a reference signal injected into one port and the amount of coupled power returned back out of the other port. Maximum amount of average RF input power which can be applied to each of the antennas input ports in the antennas operating frequency range (Watts). Mechanical length of the antenna (m). This does not include the antenna mount. For a circularly symmetric parabolic antenna this would be the diameter. Mechanical width of the antenna (m). This does not include the antenna mount. For a circularly symmetric parabolic antenna this would be the diameter. Mechanical depth antenna (m). This does not include the antenna mount. weight of the antenna in kg. This includes the antenna mount.

Port-to-Port Iso (dB)

12

POTOPO

Max Input Power (W)

17

MAXPOW

Antenna Length (m)

14

ANTLEN

Antenna Width (m) Antenna Depth (m) Antenna Weight (kg) Future Field Future Field Future Field Future Field Future Field Pattern Type # Freq this file Pattern Freq (Mhz) # Pattern cuts Pattern Cut Polarization

14 14 16 80 80 80 80 80 16 10 21 11 11 15

ANTWID ANTDEP ANTWGT FIELD1 FIELD2 FIELD3 FIELD4 FIELD5 PATTYP NOFREQ PATFRE NUMCUT PATCUT POLARI

Pattern type, either “typical” or “envelope”. The number of pattern frequencies which comprise the full data set. Frequency of the pattern data for a typical pattern (MHz). Number of pattern cuts which comprise the full data set. Geometry of a particular pattern cut. Particular polarization of a pattern cut. The first polarization is the polarization of the antenna-under-test and the second the polarization of the illuminating source. The two polarizations are separated by a /. The number of data points in a particular pattern cut data set. The first and last angle (in degrees) of the antenna pattern data. Pattern data shall be expressed monotonically, with respect to angle. Azimuths shall be stated as either –180 to +180 or 0 to 360 degrees. A verbal description of the physical orientation of the x-axis on the antenna. A verbal description of the physical orientation of the y-axis on the antenna. A verbal description of the physical orientation of the z-axis on the antenna. The data is presented in three columns. The angle of observation is listed first followed by the antenna magnitude response and phase response. In most cases the phase response will not be included in the data set. “S” designates the sign of the number. The antenna power magnitude is listed in the units specified in the antenna units field (GUNITS). The angle and phase data are expressed in units of degrees.

# Data Points First & Last Angle

13 25

NUPOIN FSTLST

X-axis Orientation Y-axis Orientation Z-axis Orientation

53 53 53

XORIEN YORIEN ZORIEN

Pattern cut data

28/point

End of file

11

ENDFIL

This field designates the end of the file with the characters EOF

112

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 9: Radio Data Formats

Sample REVNUM:,NSMA WG16.99.050 REVDAT:,19990520 ANTMAN:,RADIO WAVES INC MODNUM:,HP4-64 DESCR1:,4 FT LOW SIDELOBE ANTENNA PATNUM:,9005 DTDATA:,20030807 LOWFRQ:,6425 HGHFRQ:,7125 GUNITS:,DBI/DBR LWGAIN:,35.5 MDGAIN:,35.9 HGGAIN:,36.3 AZWIDT:,2.8 ELWIDT:,2.8 ELTILT:,0 ANTLEN:,1.2, PATTYP:,ENVELOPE, NOFREQ:,NA, PATFRE:,NA, NUMCUT:,4, PATCUT:,AZ, POLARI:,H/H, NUPOIN:,29, FSTLST:,-180,180 -180,-60,
-100,-60,

-51,-42.3, ... PATCUT:,AZ, POLARI:,H/V, NUPOIN:,11, FSTLST:,-180,180 -180,-60, -22,-60, ... PATCUT:,AZ, POLARI:,V/V, NUPOIN:,33, FSTLST:,-180,180 -180,-60, ... PATCUT:,AZ, POLARI:,V/H, NUPOIN:,11, FSTLST:,-180,180 -180,-60,

113

Atoll 3.1.0 Administrator Manual Chapter 9: Radio Data Formats

© Forsk 2011

... ENDFIL:,EOF,

9.6 Microwave NSMA Radio File Formats
Atoll enables you to import microwave radios that are in standard NSMA (National Spectrum Managers Association) format defined by the recommendation WG 21.99.051 or in Pathloss format (version 4.0). The NSMA format is described below.

9.6.1 WG 21.99.051 Format
The file is an ASCII text file with the extension NSM. It consists of rows; each data item is placed on a separate row started with the specific name of the item. The name and data items are separated with commas (,). Each text field is enclosed in double quotes (""). Numeric values are not enclosed with quotes and must not contain any embedded commas. The file has the following structure: Row "$HDR", File type, "$" "EQUIP_MFG", Equipment manufacturer "MFG_MODEL", Model number "REV_NUM", Document revision number "REV_DATE", Document revision date "RADIO_ID", Radio ID number "FCC_CODE", FCC code "EQ_DATE", Equipment data date "EMISSION", Emission designator "MAX_LOADING", Number of circuits "DATA_RATE", Data rate "RADIO_CAP", Number of lines, Signal standard "MODULATION", Modulation type "DEVIATION", Deviation "FREQ_RANGE", Low frequency, High frequency "POWER_OPTION", Power #1, Power #2, etc., "POWER_RANGE", Transmit power low, Transmit power high "STABILITY", Carrier stability "ATPC_POWER", Power reduction "ATPC_STEP", Step size "ATPC_TRIG", Receiver level "THRESH_DIG", Threshold for 10-6 BER, Threshold for 10-3 BER "THRESH_ANA", Threshold for 30dB analog signalto-noise level, Threshold for 37dB analog signal-tonoise level Description File header. The file type indicates the data contained, the format and the version of the format. For version 1.0 of the Equipment format, this value must be “EQUIP1.0”. Manufacturer with no abbreviations Manufacturer model number Document revision number - Not used by Atoll Document revision date - Date format: yyyy-mm-dd - Not used by Atoll Radio identification - Not used by Atoll FCC code - Not used by Atoll Date equipment data was recorded by manufacturer - Date format: mm-dd-yyyy - Not used by Atoll Code designating the bandwidth and modulation type Number of voice circuits Payload data rate in Mbits/s Radio capacity - The Number of Lines is the number of installed DS1’s, DS3’s, etc. The Signal Standard is a text field for the type of interface (e.g., DS3) Type of modulation Frequency deviation in kHz (analog radio only) - Not used by Atoll Frequency range in MHz over which this radio model works Transmit power options in dBm (when discrete power levels are available) Transmit power range in dBm with adjustable power levels Tolerance of transmitter output frequency expressed as a percent of carrier frequency - Not used by Atoll ATPC power reduction in dB ATPC step size in dB when power increases to compensate for reduction in receive level- Not used by Atoll Receiver level in dBm at which ATPC first activates - Not used by Atoll Receiver threshold in dBm at the specified thresholds (digital radio only) Receiver threshold in dBm at the specified thresholds (analog radio only) - Not used by Atoll

114

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 9: Radio Data Formats

Row "BRANCHING", Configuration, Transmitter loss, Main receiver loss, Protect receiver loss "MAX_RSL", Overflow threshold for 10-6 BER, Overflow threshold for 10-3 BER "DFM", DFM for 10-6 BER, DFM for 10-3 BER "TX_SPECTRUM", Number of points "CURVE_POINT", Frequency shift in MHz, Response in dBm/4Hz "TX_FILTER", "FCC_BANDWIDTH", FCC bandwidth "99%_BANDWIDTH", 99%power bandwidth "3DB_BANDWIDTH", 3dB bandwidth

Description System configuration and branching losses in dB Configuration may be:NP = not protected; MHSB = monitored hot standby; MHSD = monitored hot space diversity; FD = frequency diversity diversity; 1:M = multiline Maximum receive level in dBm (overflow threshold) Dispersive fade margin (dB) at the specified BER (digital radio only) Not used by Atoll Number of points used to define the transmitter mask graph Data points of the transmitter mask graph Not used by Atoll FCC channel bandwidth in MHz used to calculate the FCC spectrum mask - Not used by Atoll Bandwidth occupied by the transmitter in MHz (including 99% of the transmitted power) Bandwidth occupied by the transmitter in MHz (between the 3dB points) - Not used by Atoll

"T/T_FREQ_SEP", Same Antenna&Polarization, Same Minimum required frequency separation between two transmitters Antenna & Different Polarization, Different Antenna in MHz - Not used by Atoll & Polarization "T/R_FREQ_SEP", Same Antenna&Polarization, Same Antenna & Different Polarization, Different Antenna & Polarization "T/R_FIXED", T/R spacing #1, T/R spacing #2, etc., Minimum required frequency separation between the closest transmitter and receiver in MHz - Not used by Atoll Some radios only allow fixed transmit-receive frequency separations. If applicable, show all allowable frequency separations in MHz - Not used by Atoll Number of points used to define the Threshold-to-Interference (T/I) graph. The interfering transmitter and victim receiver are the same type of radio, using the same modulation and data rate. Data points of the T/I graph Number of points used to define the Threshold-to-Interference (T/I) graph. The interfering transmitter is a CW tone and the victim receiver is a digital radio. This T/I curve is used to model FM transmitters interfering into digital receivers - Not used by Atoll Data points of the T/I graph - Not used by Atoll Other capacity radio into specified radio RADIO_ID refers to the Radio Identification of the interfering transmitter. Interferor Bandwidth shall correspond to the FCC or ITU emission bandwidth of the interferor, specified as a real number in MHz. Data points of the T/I graph Baseband frequency range in kHz (analog radio only) - Not used by Atoll Number of points used to define the receiver mask graph Data points of the receiver mask graph Not used by Atoll Not used by Atoll Not used by Atoll Not used by Atoll

"T/I_LIKE", Number of points "CURVE_POINT", Frequency shift in MHz, Response in dB "T/I_CW", Number of points

"CURVE_POINT", Frequency shift in MHz, Response in dB "T/I_OTHER", RADIO_ID, Interferor Bandwidth, Number of points

"CURVE_POINT", Frequency shift in MHz, Response in dB "BB_FREQ", Low frequency, High frequency "RX_RF_FILTER", Number of points "CURVE_POINT", Frequency shift in MHz, Response in dB "RX_IF_FILTER", Number of points "CURVE_POINT", Frequency shift in MHz, Response in dB "IF_FILTER_EXT", Switch-on point, Number of points "CURVE_POINT", Frequency shift in MHz, Response in dB

115

Atoll 3.1.0 Administrator Manual Chapter 9: Radio Data Formats

© Forsk 2011

Row "RX_BB_FILTER", Number of points "CURVE_POINT", Frequency shift in MHz, Response in dB "COM_COUNT", Number of comments "COMMENT", Description #1 "COMMENT", Description #2 "COMMENT", Description #n "$TLR", File type, "$"

Description Not used by Atoll Not used by Atoll Number of comments Comment Comment Comment File trailer. The file type indicates the data contained, the format and the version of the format. For version 1.0 of the Equipment format, this value must be “EQUIP1.0”.

Sample "$HDR", "EQUIP1.0", "$" "EQUIP_MFG", "Alcatel USA" "MFG_MODEL", "MDR-6706-8" "REV_NUM", "Version 1.0" "REV_DATE", "03-01-1999" "RADIO_ID", "JF6-9406" "FCC_CODE", "EQ_DATE", "02-24-1999" "EMISSION", "2M50D7W" "MAX_LOADING", 192 "DATA_RATE", 12.4 "RADIO_CAP", 8, "DS1" "MODULATION", "128 TCM" "DEVIATION", "FREQ_RANGE", 5850, 7125 "POWER_OPTION", 15, 29, 31 "POWER_RANGE" "STABILITY", 0.001 "ATPC_POWER", 10 "ATPC_STEP", 1 "ATPC_TRIG", -65 "THRESH_DIG", -79, -81 "THRESH_ANA" "BRANCHING", "Non-Protected", 0, 0 "BRANCHING", "Monitored Hot-Standby", 0, 0.5, 10 "MAX_RSL", -10, -8 "DFM", 68, 70 "TX_SPECTRUM", 25 "CURVE_POINT", -3.12, -85.65 ... "CURVE_POINT", 3.12, -85.51 "TX_FILTER", 0 "FCC_BANDWIDTH", 2.5 "99%_BANDWIDTH", 2.48 "3DB_BANDWIDTH", 2.08 "T/T_FREQ_SEP", 49, 2.5, 28 "T/R_FREQ_SEP", 132, 105, 33

116

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 9: Radio Data Formats

"T/R_FIXED" "T/I_LIKE", 171 "CURVE_POINT", -125.000, -130.7 ... "CURVE_POINT", 125.000, -133.0 "T/I_CW", 171 "CURVE_POINT", -125.000, -152.9 ... "CURVE_POINT", 125.000, -143.0 "T/I_OTHER", "", 0, 0 "BB_FREQ" "RX_RF_FILTER", 68 "CURVE_POINT", -125, -113.7 ... "CURVE_POINT", 125, -110.5 "RX_IF_FILTER", 0 "IF_FILTER_EXT", 0 "RX_BB_FILTER", 0 "COM_COUNT", 1 "COMMENT", "T/I Data for 6.425-7.125 GHz band" "$TLR", "EQUIP1.0", "$"

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

9.7.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 0...n n+1 last DBF Header The DBF header size is variable and depends on the field count. Description 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 record optional: 0x1a (eof byte) If .dbf is not empty Remarks

117

Atoll 3.1.0 Administrator Manual Chapter 9: Radio Data Formats

© Forsk 2011

Byte 00

Size 1

Contents 0x03 0x04 0x05 0x43 0xB3 0x83 0x8B 0x8E 0xF5

Description plain .dbf plain .dbf plain .dbf with .dbv memo var size with .dbv and .dbt memo with .dbt memo with .dbt memo in D4 format with SQL table with .fmp memo Last update digits Number of records in file Header size in bytes Record size in bytes Reserved Begin transaction End Transaction ignored Encrypted normal visible multi-user environment use production index exists index upon demand language driver ID codepage437 DOS USA codepage850 DOS Multi ling codepage1251 Windows ANSI codepage1250 Windows EE ignored reserved Field Descriptor (see next paragraph) Header Record Terminator

Applies to FS, D3, D4, D5, Fb, Fp, CL D4, D5 (FS) D5, Fp (FS) FS FS FS, D3, D4, D5, Fb, Fp, CL D4, D5 D4, D5 Fp All All All All All D4, D5 D4, D5 FS, D3, Fb, Fp, CL D4, D5 All D4,D5 Fp, D4, D5 All D4, D5 Fp Fp Fp Fp FS, D3, Fb, Fp, CL All all all

01 04 08 10 12 14

3 4 2 2 2 1

YYMMDD ulong ushort ushort 0,0 0x01 0x00 0x00

15 16 28 29

1 12 1 1

0x01 0x00 0 (1) 0x01 0x00 n 0x01 0x02 0x03 0xC8 0x00

30 32 +1

2 n*32 1

0,0 0x0D

Field descriptor array in the DBF header (32 bytes for each field): Byte 0 11 12 Size 11 1 4 Contents ASCI ASCI n,n,n,n n,n,0,0 0,0,0,0 16 17 18 20 21 23 1 1 2 1 2 1 byte byte 0,0 byte 0x00 n,n 0,0 0x01 Description field name, 0x00 termin field type (see next paragraph) Fld address in memory offset from record begin ignored Field length, bin (see next paragraph) decimal count, bin reserved Work area ID unused multi-user dBase ignored Set Fields Applies to all all D3 Fp FS, D4, D5, Fb, CL all \ FS,CL: for C field type all / both used for fld lng all D4, D5 FS, D3, Fb, Fp, CL D3, D4, D5 FS, Fb, Fp, CL D3, D4, D5

118

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 9: Radio Data Formats

Byte 24 31

Size 7 1

Contents 0x00 0...0 0x01 0x00

Description ignored reserved Field is in .mdx index ignored

Applies to FS, Fb, Fp, CL all D4, D5 FS, D3, Fb, Fp, CL

Field type and size in the DBF header, field descriptor (1 byte): Size C 1...n Type Char Description/Storage ASCII (OEM code page chars) rest= space, not \0 term. n = 1...64kb (using deci count) n = 1...32kb (using deci count) n = 1...254 D8 F 1...n N 1...n Date Numeric Numeric 8 ASCII digits (0...9) in the YYYYMMDD format ASCII digits (-.0123456789) variable pos. of float.point n = 1...20 ASCII digits (-.0123456789) fix posit/no float.point n = 1...20 n = 1...18 L1 Logical ASCII chars (YyNnTtFf space) ASCII chars (YyNnTtFf?) M 10 Memo 10 digits repres. the start block posit. in .dbt file, or 10 spaces if no entry in memo Variable, bin/asc data in .dbv 4bytes bin= start pos in memo 4bytes bin= block size 1byte = subtype 1byte = reserved (0x1a) 10 spaces if no entry in .dbv binary data in .ftp structure like M binary data in .dbt structure like M OLE objects structure like M binary int max +/- 32767 binary int max +/- 2147483647 binary signed double IEEE Applies to all FS Fp, CL all all FS, D4, D5, Fp

all FS, Fp, CL D3, D4, D5, Fb FS, D3, Fb, Fp, CL D4, D5 (FS) all

V 10

Variable

FS

P 10 B 10 G 10 22 44 88

Picture Binary General short int long int double

Fp D5 D5, Fp FS FS FS

Each DBF record (fixed length): Byte 0 1…n Size 1 1… Description deleted flag "*" or not deleted " " x-times contents of fields, fixed length, unterminated. For n, see (2) byte 10…11 Applies to All All

9.7.2 Pathloss.dbf File Contents
The DBF file provides information that is needed to check validity of each path loss matrix. Field TX_NAME FILE_NAME Type Text Text Description Name of the transmitter Name (and optionally, path) of .los file

119

1. X-coordinate of the top-left corner of the path loss matrix upper-left pixel Y-coordinate of the top-left corner of the path loss matrix upper-left pixel Resolution of path loss matrix in metre Number of rows in path loss matrix Number of columns in path loss matrix Frequency band Transmitter antenna mechanical tilt Transmitter antenna azimuth Transmitter height in metre X-coordinate of the transmitter Y-coordinate of the transmitter Ground height above sea level at the transmitter in metre Receiver height in metre Logical number referring to antenna pattern. "No data" values are represented by +32767. Antennas with the same pattern will have the same number. users must retrieve the propagation models from the same central database.Atoll 3. Maximum path loss stated in 1/16 dB. Atoll indicates if losses due to the antenna pattern are taken into account in the path loss matrix. +32767] with a 1/16 dB precision. These coordinates enable Atoll to determine the rectangle including the computation zone. In the same way. 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. when no calculation radius is set. This information is used. In order to benefit from the calculation sharing feature. 120 .3 LOS File Format The LOS (path loss results) files are binary files with a standard row-column structure. c. the associated model ID changes. When model parameters are modified. This enables Atoll to detect path loss matrix invalidity. to check the matrix validity.7. 0: antenna losses not taken into account 1: antenna losses included MODEL_SIG Text ULXMAP ULYMAP RESOLUTION NROWS NCOLS FREQUENCY TILT AZIMUTH TX_HEIGHT TX_POSX TX_POSY ALTITUDE RX_HEIGHT ANTENNA_SI MAX_LOS CAREA_XMIN CAREA_XMAX CAREA_YMIN CAREA_YMAX WAREA_XMIN WAREA_XMAX WAREA_YMIN WAREA_YMAX LOCKED Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Boolean INC_ANT Boolean a. This can be done using the Open from database command for a new document or the Refresh command for an existing one. Data are stored starting from the southwest to the northeast corner of the area. Otherwise. A unique Model_SIG is assigned to each propagation model. 9. Lowest x-coordinate of centre pixel located on the calculation radiusb Highest x-coordinate of centre pixel located on the calculation radius Lowest y-coordinate of centre pixel located on the calculation radius Highest y-coordinate of centre pixel located on the calculation radius Lowest x-coordinate of centre pixel located in the computation zonec Highest x-coordinate of centre pixel located in the computation zone Lowest y-coordinate of centre pixel located in the computation zone Highest y-coordinate of centre pixel located in the computation zone Locking status 0: path loss matrix is not locked 1: path loss matrix is locked. These coordinates enable Atoll to determine the area of calculation for each transmitter.0 Administrator Manual Chapter 9: Radio Data Formats © Forsk 2011 Field MODEL_NAME Type Text Description Name of propagation model used to calculate path loss Signature (identity number) of model used in calculations. You may check it in the propagation model properties (General tab). The file contains 16-bit signed integer values in the range [-32768. two identical propagation models in different projects do not have the same model IDa. The Model_SIG is used for the purpose of validity. b.

pts file Not used Not used Not used Not used 9. For more information on the path loss tuning algorithm. 9. A tuning file can contain several measurement paths. see the Technical Reference Guide.dbf File Format See "Pathloss. Path losses surrounding the measurement points are smoothed for homogeneity.3 PTS File Format The PTS (path loss tuning) files contain a header and the list of measurement points. IM2 LTE and WiMAX: IM2.1 Pathloss. and not in precentage (between 0 and 100%).AT310_AM_E2 Atoll 3. TXT. 9.0 Administrator Manual Chapter 9: Radio Data Formats 9. When interference matrix files are imported. CSV Interference matrix files must contain interference probability values between 0 and 1.dbf File Format" on page 117. LTE.8. 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 .2 Pathloss. and WiMAX AFPs (automatic frequency planning tools). Path losses are tuned by merging measurement data with propagation results on pixels corresponding to the measurement points and the pixels in the vicinity.8. 9.1. path) of . IM1.9 Interference Matrix File Formats Interference matrices are used by GSM.dbf File Contents The DBF file provides information about the measured transmitters involved in the tuning. Interference matrices can be imported and exported using the following formats: • • GSM: CLC. Measuremment paths that are used for path loss tuning are stored as a catalogue in a folder containing a pathloss.8.dbf file and one PTS (path loss tuning) file per transmitter. IM0. Atoll does not check their validity and imports interference probability values for loaded transmitters only.8 Path Loss Tuning File Format Atoll can tune path losses calculated by propagation models using CW measurements or drive test Data.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. 121 . Field TX_NAME FILE_NAME AREA_XMIN AREA_XMAX AREA_YMIN AREA_YMAX Type Text Text Float Float Float Float Description Name of the transmitter Name (and optionally.

1 CLC Format (One Value per Line) The CLC format uses wo ASCII text files: a CLC file and a DCT file. If the column is empty. This column cannot be null. The first part is a header used for format identification. It must start with and contain the following lines: # Calculation Results Data File. 9. # Version 1. In GSM interference matrices: • The interferer TRX type is not specified and is always considered to be BCCH.05. Sample # Calculation Results Data File. Commented lines start with #. and with an accuracy of 0. 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. If no DCT file is available.0 Administrator Manual Chapter 9: Radio Data Formats © Forsk 2011 In the following format descriptions and samples.5 dB accuracy and probability values are calculated and stored with an accuracy of 0.Atoll 3.9.9. its value is identical to the one of the line above. For subcells other than the BCCH. If not. # Fields are: ##------------#------------#------------#-----------#------------------# 122 . it is possible to set "All". If the column is null.1.05. if the power offset of a subcell is X dB. If no power offset is defined on the interfered TRX type. # Remark: Tab separated format. Between two fixed C/I value. and 3 must be defined only in the first line of each histogram. Atoll looks for the associated DCT file in the same directory and uses it to decode transmitter identifiers. Commented lines start with #. Interfered subcell. Column3 Column4 Column5 Interfered TRX type C/I threshold Probability C/I > Threshold The columns 1. and 22 dB. TCH). 14. BCCH. The C/I values have 0. Interference matrices are imported by selecting the CLC file to import. there can be up to three additional values (this number depends on the probability variation between the fixed values). all subcells with no power offset are not duplicated (e. Tab separated format. Subcells have different powers defined as offsets with respect to the BCCH. 1. including five fixed ones: –9. then its interference histogram will be shifted by X dB with respect to the BCCH interference histogram.1. C/I results do not incorporate power offset values. In order to save storage. Probability to have C/I the value specified in column 4 (C/I threshold).0001 for probabilities lower than 0. • • 9. lines starting with the "#" are considered as comments. 2.1. C/I value. Identification number of the interferer transmitter. Atoll assumes that the transmitter identifiers are the transmitter names. The lines after the header are considered as comments if they start with "#". Atoll saves probabilities for several C/I values (6 to 24 values).1. # Version 1. If the column is null. This field must not be empty.1 CLC File Format The CLC file consists of two parts. The second part details interference histogram of each interfered subcell-interfering subcell pair. 8.002 for probabilities between 1 and 0. its value is identical to the one of the line above. 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 Column1 Column2 Name Interfered transmitter Interfering transmitter Description Identification number of the interfered transmitter. its value is identical to the one of the line above. For each interfered subcell-interferer subcell pair.g.

The parameter settings of this header can be wrong if # the "export" is performed following an "import". # Cell edge coverage probability 75%. they must have the following format: <Column1><tab><Column2><newline> Column Column1 Column2 Column3 Column4 Column5 Column6 Name Transmitter name Transmitter Identifier BCCH during calculation BSIC during calculation % of vic’ coverage % of int’ coverage Type Text Integer Integer Integer Float Float Description Name of the transmitter Identification number of the transmitter BCCH used in calculations BSIC used in calculations Percentage of overlap of the victim service area Percentage of overlap of the interferer service area 123 . Tab separated format. Commented lines start with #.1. they are not repeated. The first part is a header used for format identification. 9. # Margin is 5.944 0.1. # # Service Zone Type is "Best signal level of the highest priority HCS layer".752 0.316 0.944 .772 8 1 0.812 0.872 0.892 0.dct file is divided into two parts. # Traffic spreading was Uniform ##---------------------------------------------------------------------# 1 2 TCH_INNER 9 10 11 14 15 16 17 22 25 1 2 BCCH.AT310_AM_E2 Atoll 3.0 Administrator Manual Chapter 9: Radio Data Formats #| Interfered | Interfering| Interfered | C/I #| Transmitter| Transmitter| Trx type | Probability | | Threshold | C/I >= Threshold | ##------------#------------#------------#-----------#------------------# # # Warning. The lines after the header are considered as comments if they start with "#". 1 0. They # are correct when the "export" follows a "calculate".2 DCT File Format The .TCHa 8 9 10 13 14 17 a. 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. A single record indicates that the histograms belong to TCH and BCCH both.84 0.292 If the TCH and BCCH histograms are the same.9. If not.844 0.832 0. # Version 1.904 0.904 0.1.

# Traffic spreading was Uniform (percentage of interfered area) ##---------------------------# Site0_0 Site0_1 Site0_2 Site1_0 Site1_1 Site1_2 Site2_0 Site2_1 1 2 3 4 5 6 7 8 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 9. # Fields are: ##-----------#-----------#-----------#-----------#---------#---------# #|Transmitter|Transmitter|BCCH during|BSIC during|% of vic'|% of int'| #|Name |Identifier |calculation|calculation|coverage |coverage | Tab separated format.1. The parameter settings of this header can be wrong if # the "export" is performed following an "import". Tab separated format. This entry cannot be null. Sample # Calculation Results Dictionary File. If not. The second part details interference histogram of each interfered subcell-interferer subcell pair.g. # Cell edge coverage probability is 75%. BCCH.2 IM0 Format (One Histogram per Line) This file contains one histogram per line for each interfered/interfering subcell pair. # # Service Zone Type is "Best signal level per HCS layer". all subcells with no power offset are not duplicated (e. they must have the following format: <Column1><tab><Column2><tab><Column3><tab><Column4><newline> The 4 tab-separated columns are defined in the table below: Column Column1 Column2 Column3 Column4 Name Interfered transmitter Interfering transmitter Interfered TRX type C/I probability Description Name of the interfered transmitter. In order to save storage.1.Atoll 3.im0 file consists of two parts. They # are correct when the "export" follows a "calculate". # Version 2. # Version 1.1. Commented lines start with #. C/I value and the probability associated to this value separated by a space character. The histogram is a list of C/I values with associated probabilities.0 Administrator Manual Chapter 9: Radio Data Formats © Forsk 2011 The last four columns describe the interference matrix scope. # Margin is 5. Interfered subcell. Commented lines start with #. Name of the interferer transmitter. One transmitter per line is described separated with a tab character. The . ##-----------#-----------#-----------#-----------#---------#---------# # # Warning. The lines after the header are considered as comments if they start with "#". It must start with and contain the following lines: # Calculation Results Data File.9. The first part is a header used for format identification. TCH). 124 .

832 10 0.636 15 0.896 7 0.804 13 0.9.932 1 0. # Margin is 5. The first part is a header used for format identification.84 11 0.im1 file consists of two parts.848 9 0.844 11 0. # Version 1.996 -6 0.932 4 0. # # Service Zone Type is "Best signal level of the highest priority HCS layer". The histogram is a list of C/I values with associated probabilities.764 14 0. Tab separated format.816 10 0.892 7 0. If not.924 4 0.TCH-9 1 -6 0. TX Name Repeated) This file contains one C/I threshold and probability pair value per line for each interfered/interfering subcell pair. Commented lines start with #.936 0 0. Name of the interferer transmitter.932 1 0.564 Site0_3 Site0_2 BCCH.876 8 0.972 -1 0.976 -4 0. They # are correct when the "export" follows a "calculate".644 15 0.AT310_AM_E2 Atoll 3.66 Site0_2 Site0_3 BCCH. The . The parameter settings of this header can be wrong if # the "export" is performed following an "import". # Traffic spreading was Uniform ##---------------------------------------------------------------------# # Site0_2 Site0_1 BCCH. 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 Column1 Column2 Name Interfered transmitter Interfering transmitter Description Name of the interfered transmitter.904 7 0. # Cell edge coverage probability 75%.556 Site0_3 Site0_1 BCCH.712 17 0.964 -2 0.688 14 0.856 8 0.996 -6 0.716 15 0.804 14 0.94 1 0. Commented lines start with #.616 18 0.852 8 0.1.976 -4 0.772 13 0. Tab separated format.824 11 0. It must start with and contain the following lines: # Calculation Results Data File.3 IM1 Format (One Value per Line.744 14 0.608 18 0. # Version 1. The lines after the header are considered as comments if they start with "#". 125 .96 0 0.972 -3 0.TCH-10 1 -9 0.948 0 0.832 9 0.924 4 0.996 -6 0.896 7 0.948 0 0.0 Administrator Manual Chapter 9: Radio Data Formats Sample # Calculation Results Data File.86 9 0.928 4 0.94 1 0. # Remark: C/I results do not incorporate power offset values.1.TCH-10 1 -9 0.784 11 0.964 -1 0.TCH-10 1 -9 0.98 -3 0.1.644 9.692 18 0. # Fields are: #-----------------------------------------------------------------------#Transmitter Interferer TRX type {C/I Probability} values #-----------------------------------------------------------------------# # Warning.864 8 0. The second part details interference histogram of each interfered subcell-interferer subcell pair.

824 9.TCH BCCH.and Adjacent-channel Probabilities) IM2 files contain co-channel and adjacent-channel interference probabilities for each interfered transmitter – interfering transmitter pair.848 0.TCH BCCH.TCH BCCH.g.. 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. Probability to have C/I the value specified in column 4 (C/I threshold).964 0.TCH BCCH.Atoll 3. C/I value.924 0.976 0.864 0. TCH).TCH BCCH. # Traffic spreading was Uniform ##---------------------------------------------------------------------# Site0_2 Site0_2 Site0_2 Site0_2 Site0_2 Site0_2 Site0_2 Site0_2 Site0_2 Site0_2 Site0_2 Site0_2 . In GSM.996 0. The parameter settings of this header can be wrong if # the "export" is performed following an "import". # Version 1. # # Service Zone Type is "Best signal level of the highest priority HCS layer". # Calculation Results Data File.TCH BCCH.4 IM2 Format (Co.TCH BCCH.932 0.. all subcells with no power offset are not duplicated (e.TCH BCCH. # Margin is 5.1. They # are correct when the "export" follows a "calculate". # Fields are: #-----------------------------------------------------------------------#Transmitter Interferer TRX type C/I Probability #-----------------------------------------------------------------------# # Warning.0 Administrator Manual Chapter 9: Radio Data Formats © Forsk 2011 Column Column3 Column4 Column5 Sample Name Interfered TRX type C/I threshold Probability C/I > Threshold Description Interfered subcell. Tab separated format.TCH -10 -9 -6 -4 -1 0 1 4 7 8 9 10 1 0. # Cell edge coverage probability 75%. there is only one set of values for all the subcells of the interfered transmitter. Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 BCCH. This column cannot be null.832 0.TCH BCCH. In order to save storage.TCH BCCH. The four columns are defined in the table below: 126 . # Remark: C/I results do not incorporate power offset values. This field must not be empty.936 0.1. BCCH.TCH BCCH.9.896 0. Commented lines start with #.

0.Site0_2.024 Site0_3.02 Site0_3.0.226 0. Commented lines start with #.Site0_1.0 Administrator Manual Chapter 9: Radio Data Formats Column Column1 Column2 Column3 Column4 Sample Name Interfered transmitter Interfering transmitter Co-channel probability Adjacent-channel probability Description Name of the interfered transmitter Name of the interferer transmitter Co-channel interference probability Adjacent channel interference probability # Calculation Results Data File.276 0. # Cell edge coverage probability 75%.Site0_1. # Fields are: #-----------------------------------------------------------------------#Transmitter Interferer Co-channel Adjacent channel #-----------------------------------------------------------------------# # Warning.0.0.27.028 127 .024 0.226667.1.0.1.226. # Version 1. They # are correct when the "export" follows a "calculate".27 0.0.276.024 0. # # Service Zone Type is "Best signal level of the highest priority HCS layer". # Remark: C/I results do not incorporate power offset values. # Traffic spreading was Uniform ##---------------------------------------------------------------------# Site0_2 Site0_2 Site0_3 Site0_3 Site0_1 Site0_3 Site0_1 Site0_2 0.0.02 0.024 Site0_2.AT310_AM_E2 Atoll 3.226667 0. Tab separated format.0. These columns can also be separated with a semilcolon: Site0_2.Site0_3. # Margin is 5. The parameter settings of this header can be wrong if # the "export" is performed following an "import".028 The columns in the sample above are separated with a tab.

1.0 Administrator Manual Chapter 9: Radio Data Formats © Forsk 2011 128 .Atoll 3.

AT310_AM_E2 Atoll 3. disable the display of some of the information contained in the status bar. 1 Gbps. for example. Atoll is designed to optimise memory consumption... ECW files can be of any size (no limitations). which enables it to perform efficiently with regional tiles (1 tile/file per region). it is strongly recommended to: • • • Either. This approach avoids the need to replicate the geographic data on all the workstations.". For a country-wide project. clutter class. an absolute path. and "C" is the share name of disk C.0 Administrator Manual Chapter 10: Administration and Usage Recommendations 10 Administration and Usage Recommendations This chapter lists various technical recommendations for optimising your work with Atoll. BIL files. Merging small tiles to build a regional tile can improve performance greatly. is represented as "\\Computer\C\Program Files\Forsk\Geo Data\. If you define paths to geographic data files using the UNC.. \\Computer\C\Program Files\Forsk\Geo Data\. Atoll will be able to keep track of the linked files even if the Atoll document is moved to another computer.. In all other cases. it is recommended to link geographic data files to the Atoll documents.... such as altitude.. see "Hiding Information Displayed in the Status Bar" on page 179. Or. Following the UNC. hide the status bar that displays geographic data information in real time.1. such as "C:\Program Files\Forsk\Geo Data\..g. Link or Embed • • Only embed geographic data in ATL files if you wish to make a portable document. this may lead to hundreds of files describing the geographic data. it is recommended to use uncompressed DTM and clutter files. \Program Files\Forsk\Geo Data\. where "Computer" is the computer name. for example. and clutter height using an option in the Atoll. • Recommended Formats • In order to improve performance. If you are using compressed geographic data files. Geographic data should either be located on each server or accessible through a fast network connection. You can restrict access to the geographic data locations by assigning read/write access rights to administrators and read-only rights to end-users. It is recommended to set the paths to linked geographic data files using the Universal Naming Convention (UNC).ini file.". 10. it is recommended to place all the geographic data on a file server accessible to all the users. compressed TIF or Erdas Imagine. Size of Tiles • Some network planning tools require geographic data to be available in small tiles in order to work more efficiently. In Atoll.1 Geographic Data Location of the Geographic Data • • • In multi-user environments. The following table shows the recommended file formats for different geographic data: Geographic data type Scanned maps Vectors Recommended file format ECW SHP 129 ... You can hide the status bar from the View menu. Example: Absolute Path Relative Path UNC Path C:\Program Files\Forsk\Geo Data\. e. To note as well: • • • Recommended file size: 100 to 200 MB Erdas Imagine Pyramids files can be bigger. can cause performance reduction due to decompression of these files in real time. Using compressed geographic data files.

e. For example. and the corresponding shared path loss matrices are valid.2 Path Loss Matrices Shared Path Loss Matrices • Shared path loss matrices should be accessible through a fast network connection.. If private path loss matrices are invalid.0 Administrator Manual Chapter 10: Administration and Usage Recommendations © Forsk 2011 10. you must not create tables and fields with names longer than 20 characters. Example: Absolute Path Relative Path UNC Path C:\Program Files\Forsk\PathLosses\.x before upgrading to Atoll 3.. such as ORDER. For more information. i... These results are accessed by Atoll during calculations. 30 Mbps at least per user.g. valid or invalid. Oracle databases allow a maximum length of 30 characters for field and table names. • It is recommended to set the paths to the private and shared path loss matrices folders using the Universal Naming Convention (UNC).. This can be useful for disk space management.. Link or Embed • Only embed path loss matrices in ATL files if you wish to make a portable document. whose corresponding shared path loss matrices are valid. where "Computer" is the computer name. is represented as "\\Computer\C\Program Files\Forsk\PathLosses\. and "C" is the share name of disk C. which will result in less fragmentation.. Limiting the length of table and field names to 20 characters will help avoid database connection and consistency problems. see "Synchronising Private and Shared Path Loss Matrices" on page 177. Do not skip a major Atoll version.8.1. Externalising path loss matrices does not reduce the performance of display and calculations in Atoll.". Following the UNC. if you are currently using Atoll 2. Table and field names must not start with a numeric character (0-9). etc. for use in Atoll. creating project databases..1. etc.x.. e.. In all other cases. 10. a-z. \\Computer\C\Program Files\Forsk\PathLosses\. Table and field names should be not more than 20 characters long. Externalising path loss matrices to shared or private path loss folders will keep the ATL file size reasonable.7. • Private Path Loss Matrices • Atoll synchronises the private path loss matrices with the shared path loss matrices. It is recommended to define a rule for making backups of the database at regular intervals.x.. you must upgrade your database twice in order to make it compatible with the new version. it is recommended to link path loss matrices to the Atoll documents. • • • Table and field names should only use alphanumeric characters (A-Z. This is because Atoll adds some characters to the table and field names for certain operations: creating associated triggers. and should be available to the users through a fast network connection. 1 Gbps. Upgrading your database will be simpler if you do not skip a major version. 130 . an absolute path. 0-9). \Program Files\Forsk\PathLosses\.". You can make Atoll verify and remove private path loss matrices. If you define paths to the private and shared path loss matrices folders using the UNC. However. 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. Tables and Fields • • Table and field names are case sensitive. Atoll will be able to keep track of the linked files even if the Atoll document is moved to another computer. Atoll deletes the invalid private path loss matrices and uses the shared ones.Atoll 3.3 Databases Database Upgrade • • • Create backups of the database before upgrading. DATE. such as "C:\Program Files\Forsk\PathLosses\. Table and field names must not contain an SQL or RDBMS-specific keyword. you should first upgrade the database to Atoll 2. If you skip or have skipped an intermediate major version..

0 Administrator Manual Chapter 10: Administration and Usage Recommendations • • • • • Table and field names must not contain spaces or special characters. should always have default values assigned. you should avoid adding custom fields to the neighbour management tables. When setting up your database for the first time. allocate them the appropriate size that would suffice. etc. • Path loss calculations are carried out by a separate process (AtollSvr). for the most part. grouping. brackets ({}). The principal difference observed might be the inability to run multiple Atoll sessions on the server without getting error messages. carrying out calculations. Rather. integrated in the Distributed Calculation Server. make sure that all the users have the same decimal separator.). Atoll’s interface will also be more efficient and the overall processing time for various tasks will be improved. 131 . system or user-defined. users will be able to use these for sorting. Using the Distributed Calculation Server. To improver performance.e. a 255-character long Text type field would. Some requirements of the different user groups may be satisfied if a few general-purpose user-defined fields are added in Atoll tables when setting up the database. square brackets ([]). • A queuing system. If you must add Text fields. This set up can introduce considerable improvements in both the number of Atoll sessions per server and the calculations. which means high CPU and RAM resource consumption. and text (limited size)) to the Sites and Transmitters tables. try to anticipate user requirements in terms of custom fields in Atoll tables.AT310_AM_E2 Atoll 3. Troubleshooting and Solution As the cause of this problem is resource saturation on the server. parentheses (()). unless absolutely necessary. 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. you should first add the field in the database. This approach may help the database function a long time before users require the addition of other custom fields. i. • A failover mechanism automatically switches and hands over the path loss calculations back to Atoll in case a problem occurs. • • • To improver performance. This notably improves the memory and CPU consumption. or other purposes. Atoll users might experience a decrease in server performance and stability in a multi-user Citrix environment. as described below. if you add three user-defined fields (one of type integer. This is especially the case with large Atoll documents and propagation models that require considerable memory. The CustomFields table enables you to define default values and choice lists for any field in any table in Atoll.4 Calculation Server Computation Server Stability and Resource Management In certain conditions. exclamation marks (!). such as periods (. increases to more than four. and as path loss calculations share the amount of memory allocated to the Atoll session. For example. general application failures. if your projects allow it. and then update your Atoll document from the database. which allow sorting and other functions. reduce the size of the fields corresponding to the sites and transmitters’ names. interrogation marks (?). Such problems may occur when the number of Atoll sessions on the server. The values defined in this table have priority over the internal predefined default values.1. 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. 10. To improver performance. or server crashes. the total memory requirement may exceed the Microsoft Windows’ (32-bit editions) limit of 2 GB per process. If you define floating point default values. a Distributed Calculation Server should be set up. occupy disk space for no purpose. use numeric field types. float. do not add user-defined fields of Text type. which has its own memory allocation apart from 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. Boolean fields. path loss calculations can be performed outside Atoll. For example. including user-defined fields that you add to the Atoll tables. the amount of memory needed for calculations does not impacts the Atoll memory allocation. manages the calculation requests from different Atoll sessions. 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.. If you wish to add custom fields in the Atoll document. filtering.

you can copy these files to their respective locations on the new server to have the exact configuration and set-up as the first. • To avoid ‘out of memory’ problems. Virtual memory can be increased from 8 GB to 16 GB. traffic information. but apart from that you will be able to work with Atoll normally. performing certain types of coverage predictions. please refer to the following URL: http://www. and other technologyspecific parameters.mspx (/3GB section in “Memory Support and Windows Operating Systems”). You can use the configuration files to store your created coverage prediction studies locally. Before creating study templates. state the actual number of processors in the INI file. 10. User Configuration File (CFG) • • • Use Atoll to create these files and avoid modifying these files manually as human errors can create problems. 132 . different groups of users. If you have already configured these files for one server. • 10. or create them. you can also use the study duplicate feature to create copies of existing coverage prediction studies. and hence bypassing the resource control procedure established above. For 32-bit Windows operating systems.). These groups of users may be. which would store their respective coverage prediction studies parameters. for example. you can also make some other system improvements: • To avoid error messages caused by requesting a large number of files over the network. 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. avoid creating study templates unless these will be needed for a long time by a number of users. If you are using Windows 2000 Server.com/whdc/system/platform/server/PAE/PAEmem.5 Atoll Administration Files There is no specific order in which configuration and initialisation files should be created or installed on Atoll workstations and servers. And. for example. This is different from the 2 GB per process limit.6 Process Memory 32-bit Operating Systems Atoll can support 3 GB address space on a properly configured 32-bit system. 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. For more information. and the XML studies file. macros. 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. Separate configuration files based on. This means.. you can also increase the default Windows memory allocation limit from 2 GB to 3 GB as explained in "Process Memory" on page 132.aspx. Apart from the above setup. These files are optional. performing the AFP.1. and for. groups of users focusing on certain operations (i. The following link provides information on how you can setup your Windows 2003 Server systems to activate the 3 GB switch at startup: http://technet. If you do not copy these files. Initialisation File (INI) • • It is highly recommended that the Atoll initialisation file be created and modified only by the administrator.microsoft. and you are setting up another server.ini file should be set made read-only for end-users. groups of users working on different technologies.microsoft.Atoll 3. Uncheck image visibility to avoid loading unnecessary data in the memory. for example. and other common parameters in your Atoll documents. • Custom Predictions File • Coverage prediction studies can easily be duplicated within Atoll. etc.com/en-us/library/bb124810.0 Administrator Manual Chapter 10: Administration and Usage Recommendations © Forsk 2011 In order to prevent users from deactivating the use of the Distributed Calculation Server. make sure that this study template is aimed at serving a number of users. You can set up your configuration files in the following manner: • • A common configuration file that points to the geographic data. groups of users working on different regions. neighbour allocation parameters. Separate configuration files created for your 2G and 3G projects.e. not obligatory. you will not have the same configuration of the new server. the Atoll.

For performance reasons. containing the list of antenna names. However. it may have a significant impact on performance depending on the number of measurement points in the Atoll document. i. • 133 . You will have to replace the name of the pattern inside the file by the name of the pattern file itself. Closed polygonal vectors (surfaces. 2. Open polygonal vectors (lines. This option is available in the Display tab of the Properties dialogues for CW Measurements and Drive Test Data folders. which would in fact be the pattern (antenna file) names. This approach is more efficient in terms of performance than selecting this option and setting the Cell edge coverage probability to 50%.AT310_AM_E2 Atoll 3. you can create a new file. You should place this file at the same location as the antenna patterns (files). zones and areas. 10.) 6. etc.e. • 10. etc. DTM. it is advised to clear the Shadowing taken into account check box. please follow the recommended procedure described in the Measurements and Model Calibration Guide. Although this approach only displays measurement points as small squares. Visible objects of the Data tab All the visible objects of the Data tab are displayed above those in the Geo tab. generic maps. Transparent raster maps (clutter class maps. in order to import these antennas correctly. and then raster layers. To solve this issue.e. rain. named "Index". traffic. The following table lists the levels of precision that are usually sufficient: Size of the coverage prediction City Center City County State Country Display resolution 5m 20 m 50 m 100 m According to the size 10. i. When performing a CW measurements drive test campaign.9 CW Measurements and Drive Test Data • It is recommended to use Fast Display in order to increase display speed.) 10. etc. clutter height maps. The following order should be followed: 1. etc. you should set the display resolutions of coverage predictions according to the precision required. it is strongly recommended to place vector layers on the top of coverage prediction plots. etc. Non-transparent maps (images. Sites and Transmitters must be on the very top.10 Antenna Patterns and Import • Antenna names used in some tools..7 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. You can do this by transferring these vector layers to the Data tab using the context menu. roads and other linear items. Unidimensional vectors (points) 3.) 4. above all other layers. then vector layers. Some Kathrein antenna pattern files might have names different from the antenna pattern names present inside the file.) 5.. i. it is advised to place vector layers on top of raster layers before printing a project.) 7.1.0 Administrator Manual Chapter 10: Administration and Usage Recommendations 64-Bit Operating Systems The 64-bit editions of Microsoft Windows provide 4 GB of memory per process. can be different from those used in their corresponding antenna files. such as NetAct. To improve memory consumption and optimise the calculation times.e.. You should place sites and sectors on the top. Multi-format maps (vector or raster maps. This will replace the antenna names with the new antenna names.8 Coverage Prediction Calculations • • If you do not want Atoll to calculate the shadowing margin during a coverage prediction. population.

navigate to the directory containing the antenna pattern files. traces of records that no longer exist in the database. Create a CFG file from your existing ATL file with all the required information. creating objects through CreateObject or CoCreateInstance may fail. neighbour allocation parameters. You can open the Command Prompt window by selecting Start > Run. and unloading and reloading these DLL files refreshes the memory allocation. 10. User density traffic maps provide you with a means to define a density for each set of service. is an additional electrical downtilt. This advice is applicable to any application running under Microsoft Windows because many common DLL files are accessed by applications. the correct functioning of Atoll requires an open user session on the computer. you should use sector traffic maps or user density traffic maps. do not already include the effect of an electrical tilt.g. has less fragmented data. Create a new ATL from the database to create a fresh ATL file. 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. Atoll is an application that requires creating tool bars. you should restart your Citrix server every week or fortnight. which can be defined in the antenna properties dialogues in Atoll. etc. c. and takes up less space on the hard disk. It might be redundant to define an additional electrical downtilt for antennas whose patterns already include electrical tilt." • The electrical tilt. so..11 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. terminal type.0 Administrator Manual Chapter 10: Administration and Usage Recommendations © Forsk 2011 • A Planet Index file contains the path to and the name of each antenna file available. and mobility type. e. Particularly. Therefore.Atoll 3. In the Command Prompt window. which has all the same information as the old ATL file. creating menus.g. refer to "Configuration Files" on page 141. Users should verify whether the antenna patterns of the antennas in their projects. You can completely refresh your project by following these steps: a. The file will also contain a line with its own name. geographic data set. e. Import the CFG file in the new ATL file. If you have been working on your existing ATL file for a long time. etc. The same is true for add-ins working with Atoll. You can easily create the index file from the Microsoft Windows command prompt. closing and restarting Atoll. you should use a text editor to remove the line containing the file name "Index. accessing printers. In certain cases. For more information.. e. You now have a clean ATL file to work with. • • If you are working in a Citrix MetaFrame environment.. Sector traffic maps are best suited for traffic data issued by the OMC. entering "cmd" and pressing ENTER. before importing this file into Atoll. 134 . Even though it is possible to load and use Atoll when there is no user session open on a computer. coverage prediction parameters. Close the old ATL file. 10. it might be more appropriate to start working on a completely fresh ATL file. For higher precision on traffic data. and reopening the document. Unexpected errors can occur. b. even when it is accessed through the API. and improved performance. 10. d. it might become unnecessarily large and might contain some useless remains from your earlier operations. etc. Creating such an Index file when there are hundreds of antenna patterns available can be a difficult task.13 Performance and Memory Memory Refresh • You can avoid memory fragmentation while working with Atoll documents by saving the Atoll document from time to time. reading user profile options from the Windows’ registry. with one name per line.1. Open the existing ATL file in Atoll that you want to replace.12 Atoll API Correct functioning of Atoll when using Atoll through the API is guaranteed during interactive user sessions only. its correct functioning is not guaranteed. The exact time should be determined by the administrator depending on the state of the network (LAN).

if you set it too high. • File Size • Coverage predictions calculated over large areas require more memory. means that the computations will take into account all the interferers. If the network is large but homogeneous.. Performance and Memory Issues in Large GSM Projects Memory problems might be experienced in the C/I coverage prediction studies. For 32-bit Windows operating systems.AT310_AM_E2 Atoll 3. The default value for this threshold (-130 dBm). you can also increase the default Windows memory allocation limit from 2 GB to 3 GB as explained in "Process Memory" on page 132. if the Atoll session has been open for a long time.000 or so. But. you might have around 10. and the AFP while working on large GSM networks. • Externalise DTM. defined in the Predictions tab of the Predictions folder’s Properties dialogue.g. verify that the calculation radii and resolutions assigned to the different types of transmitters are consistent. Adapt calculation radii to the cell type and the EIRP: Before calculating path loss matrices. However.000 transmitter records. The proper value for this threshold depends on the Reception Thresholds and the C/I Thresholds defined in the Subcells table. clutter. You will also reduce the ATL file size by externalising the interference matrices.0 Administrator Manual Chapter 10: Administration and Usage Recommendations Memory Allocation • If you have to open several large ATL files simultaneously on the same computer. Atoll loads only the data necessary for your working area. Also. so that the ATL file size does not become unnecessarily large. memory problems may even appear while working on smaller networks. Atoll loads interference matrices from the external files to the memory only when needed. If you load a large network. then this size limit might decrease to around 5. You can reduce memory consumption by making copies of your Atoll document. interference matrices calculations. these problems may only appear if the number of transmitters is over 15. If you calculate path loss matrices for all types of cells over a large calculation radius. Properly configure the interference thresholds: These thresholds indicate the level after which an interferer can be ignored. in a typical large GSM network. and up to 150. and any other data that can be externalised. e. 50. 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. Large network projects are more susceptible to these problems. Path Loss Calculation • Before starting path loss calculation. The extended path loss matrices can be calculated using a lower resolution. such as the neighbour relation data. Each Atoll session on the same computer has its own memory space allocated by the operating system. The optimum value would be Min AllSubcells ( RT i – CIT i – M ) . For calculating path loss matrices over large areas.000 transmitters or so. and large calculation radii and low resolutions for extended path loss matrices. with each pixel having many overlapping path loss matrices. you might lose important interference information. take care to correctly associate calculation radii and resolutions to different types of cells. 20. it will unnecessarily burden the C/I and interference matrices computations. This is because the process memory space (memory space allocated to Atoll by the operating system) becomes fragmented. this document will require more memory for loading all the coverage predictions. The main path loss matrices should be calculated using the same resolution as the resolution of the geographic data available. Define short calculation radii and fine resolutions for the main path loss matrices. you should use the dual resolution feature in Atoll.000 TRX records. For example.1. For example. Atoll will load a lot of data that might not be necessary all the time. If you are working on an Atoll document covering a large area. calculating path loss matrices of picocells over large calculation radii would only waste memory and disk space. with coverage predictions calculated over the entire network. and keeping a few coverage predictions in each copy.000 neighbour records. Large coverage predictions can take up a considerable amount of memory even if they are not displayed on the map. • Regionalisation • Use database regionalisation or site lists if you are working on smaller parts of a large network. Atoll will be required to load a lot of data that might not be necessary all of the time. if there are large city centres involved. This approach decreases the calculation time significantly compared to calculating just one matrix per transmitter using a fine resolution. These ATL files will be faster to load and work with compared to a single ATL file with all the coverage predictions. Each computer consumes a single licence token independent of the number of Atoll sessions opened simultaneously. twice the resolution of the geographic data. Which means the minimum value of the factor RT i – CIT i – M computed for all • • • 135 . it is better to open each in a separate Atoll session rather than to open them all in the same Atoll window. path loss matrices. Externalise embedded interference matrices: You can store interference matrices listed in the Interference Matrices folder in external files.000 subcell records.

This will provide rough global interference matrices which can be locally improved. To decrease the amount of memory used by Atoll in such cases. Avoid loading neighbours and custom fields which are not required. you can add 1 or 2 dB to this value for that TRX type. CITi the C/I threshold of this subcell. the AFP plan will not be optimal. remove coverage prediction studies. their deviation from the approximate values will be negligible.14 Appendix: Memory Requirements This part gives some aspects of memory requirements (both RAM and hard disk space) for Atoll depending on the network to be planned. RTi is the reception threshold of the subcell i. a GSM and a UMTS document can cause memory saturation especially if the documents contain large. • • If the memory-critical task is the AFP session: Try to make the document lighter. These interference matrices will be less memoryconsuming. However. you can set the "Information to retain" option to "Only the Average Simulation and Statistics". and M is a safety margin. loading. it is important to have at least a 3-dB margin for the interference energy aggregation in C/I 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. and an interference threshold of -112 dBm. depending on the size) coverage predictions and other calculations using larger pixel sizes. 10. With this option Atoll uses much less memory because it only keeps limited information in memory during the simulation process.. This can be performed by creating views in the database. We recommend a safety margin of 5 dB. It depends mainly on the size of the planning area. This means that you can generate nation-wide interference matrices with low resolutions based on the percentage of interfered area (to improve computation time). In networks with only a few cells. but only the input parameters that have a considerable impact on memory requirements. Loading vectors in the linked document is not necessary and only consumes more memory. you can: • • Load vector layers in main document only. For more information. • • Performance and Memory Issues in UMTS/CDMA Simulations • In order to optimise memory usage during simulations. see "Appendix 2: Setting Up Databases for Co-planning" on page 63. It is recommended to perform detailed planning with smaller pixel sizes in high density areas.14. which can be reduced if any problem is encountered. i.0 Administrator Manual Chapter 10: Administration and Usage Recommendations © Forsk 2011 subcells. the amount of disk space required is chiefly 136 .1. If you want a certain TRX type to carry GPRS/EDGE traffic.g. and country-wide (or region-wide. Atoll is capable of performing computations in pixel sizes different from those of the raster maps in a project. RAM allocation and calculation time. Since this interference threshold is used both in interference matrices calculation and in interference predictions. If the memory-critical task is interference matrices generation: You can generate interference matrices in a piecewise manner. it will unnecessarily load the interference matrix generation and the AFP. Please note that the figures mentioned in the following sections are approximate. and will considerably improve the disk space requirements. and the number of cells. e. and though actual figures may vary. and calculate local interference matrices with higher resolutions and reliabilities. 10. for example. Where. Then. These approximate values are computed through simplified formulas. The 12 dB and 9 dB default values already include safety margins. and use the option of safety margin in the AFP module’s Cost tab. with a cell edge coverage probability of 50% (which means no access to clutter for reading standard deviation values). This approach will provide overall satisfactory results. the pixel size. If there are too many or too few entries in your interference matrices. and possibly skip this step. 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. use polygon or site list filters to focus on each important location. country-wide networks. 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. These formulas do not consider all the input parameters. and try to generate interference matrices with fewer entries. exit and restart Atoll.Atoll 3. Simulation results are detailed enough to be used in generating coverage prediction studies.1 Disk Space Requirements The amount of disk space required for data varies from project to project. Make sure that the computation zone in your project completely encompasses the filtering zones that you define. • Do not define very high C/I quality thresholds (Default values: 12 dB for BCCH and 9 dB for TCH). If you increment these values too much.

If an embedded geographic data file is deleted from the project. For example. each ATL file will require the same amount of disk space.) does not depend on the number of cells. traffic density or environments. one DTM map. You can consider 14 bytes per pixel as a rough estimate to determine the disk space required for each individual ATL file. Atoll automatically compresses the ATL file to avoid file fragmentation. There can be a single layer for the entire network or a layer per transmitter. Temporary Disk Space Atoll requires some disk space to temporarily store intermediate results during calculations. Atoll coverage predictions may require between 1 bit and 2 bytes per pixel of the calculation area. and one background image. the propagation results for a sector with a calculation area of 1024 x 1024 pixels will require 2 MB disk space. but only on the size of the planning area in pixels. Likewise. Background images require from 1 to 3 bytes per pixel. If embedded path loss matrices are externalised. Cell-specific results require 2 bytes per pixel. These files are erased after the calculations or once the storage has finished. transmitters and cells. one traffic map. a temporary file is created when using the "Save As" command. 137 . clutter classes. it is important to consider the disk space required by the propagation prediction results of each cell. sector. The same rule applies to extended path loss matrices as well. In networks with a large number of sites. This data can be shared between different planning alternatives of the same network. DTM or clutter height maps require 2 bytes per pixel. A file is created in the system’s temporary directory whose size depends on the calculations. Network-Wide Output Network-wide output (raster results) mainly depends on: • • • • The size of the planning area The pixel size The number of coverage predictions The types of coverage predictions Coverage predictions may have a number of layers depending on the calculation criteria. images. Cell-Specific Results For a project with a large number of cells. the cell calculation area and the calculation resolution are important factors.1. you may estimate 6 bytes per pixel of the input area. Traffic maps require 1 byte per pixel (2 bytes for Planet format). Network-Wide Input The file sizes for raster maps (DTM. • • Atoll can compress the coverage prediction results when saving a ATL file to avoid file fragmentation. This file is described in the section on RAM requirements. The resulting size depends on the number of layers and the number of colours and thresholds. Here. it is the number of these network entities that governs this requirement. If there are different ATL files for planning the same part of the network in different ways. clutter heights. The following information can provide you with an estimate of disk usage for different geographic data: • • • • • Clutter class maps require 1 byte per pixel (2 bytes for Planet format). Pixel size plays an equally important role in all cases.AT310_AM_E2 Atoll 3.0 Administrator Manual Chapter 10: Administration and Usage Recommendations determined by the size of the planning area. Population maps or other generic maps require from 1 to 4 bytes per pixel. or subcell. For one clutter map. etc. Atoll automatically compresses the ATL file to avoid file fragmentation. Therefore.

To activate the memory estimation feature. If the amount of unused spaces is more than half of the useful space. The memory requirement of these calculations is a function of the following: • • • • • • • • • • The number of sites involved The number of transmitters involved The number of cells involved The number of mobiles generated by the UMTS simulation The number of transmitters covering a pixel The number of services simulated The number of neighbours per cell The "Detailed Results" and "Limit Active Set to Neighbours" flags The number of links per mobile The number of channel elements per site Most of these parameters have minor influences and the actual requirements are mostly governed by the number of cells and the number of mobiles generated.1. For more information.25 × m R = 14. • • Please note that this is the peak requirement.2 RAM Requirements Usually.ini file. Atoll estimates the size of unused spaces in the file due to fragmentation. A more accurate estimation of the used and required memory for UMTS simulations is available in the Source Traffic tab of the new simulation group dialogue. Furthermore. Loading a project with 500 sites. This approximation also considers effects due to the operating system. as their size is usually much smaller than the DTM. a few predictions. see "Estimating Required and Used Memory Size for UMTS Simulations" on page 190. 512 MB of RAM in a workstation is sufficient for all operations with Atoll. It is a conservative approximation and in most cases the actual RAM requirement will be below these calculated figures. ATL files store database tables and calculation results. Assuming that there are three carriers used and the number of transmitters and mobiles is high enough so that the other input can be ignored. Each additional site requires between 1 and 2 KB. clutter height. Monte Carlo Simulations UMTS Monte-Carlo simulations are calculations that consume large amounts of memory. When saving an ATL file. An empty ATL file requires around 500 KB. the size of vector files is negligible compared to that of other geographic data. the required memory can be roughly approximated by: R = 14. you must add an option in the Atoll. such as memory over-allocation due to fragmentation. • 138 . 10. provided that there are no other applications being used in parallel that consume large amounts of memory.3 × m for normal simulations using the "detailed results" option with R: peak RAM requirement in KBytes t: number of transmitters affecting the computation zone m: number of mobiles generated by the UMTS simulation Example: To calculate for 500 sites (or 1500 transmitters) and 2400 mobiles. Starting Atoll without loading a project requires around 20 MB of RAM (as monitored with the Windows Task Manager). Less memory will be required once the calculations are terminated. which is negligible compared to the size of the propagation results.0 Administrator Manual Chapter 10: Administration and Usage Recommendations © Forsk 2011 Other Disk Space Requirements Other objects in a ATL file that require disk space can easily be neglected in real-life scenarios since the required disk space depending on the size of the planning area and the number of transmitters is much higher. around 28 MB of RAM are required for a normal simulation and 30 MB if detailed results are to be stored as well.Atoll 3. and clutter class maps.0 × t + 3. Atoll proposes compressing the file. and some simulations may increase the consumed memory to around 50 to 100 MB.14.0 × t + 4.

i. If a coverage prediction calculates the signal strength of the UMTS pilot in less than 16 colours.0 Administrator Manual Chapter 10: Administration and Usage Recommendations Coverage Predictions RAM required during coverage prediction calculations (network-wide raster result) is the same as the required additional disk space.e. Atoll temporarily allocates an average of 4 bytes more per pixel (8 bytes. this equals 5. which equals 20.. For large networks. During the calculation. if the best server margin is not zero) of the calculation area. Atoll divides the coverage prediction computations into smaller tiles. temporary memory is required for calculations like "Coverage by transmitter" and "Coverage by signal level". This subdivision is invisible to the user. Atoll would also require 4 more bytes per pixel. 139 . it would require a memory of 4 bits per pixel. and carries out the computations on them successively.8 MB more apart from the 2. between 1 bit and 2 bytes per pixel of the calculation area.1.6 MB. Apart from this. to avoid loading the entire computation zone in memory.2 million pixels. or a total of 2. For these. Example: The Paris region has a size of around 10 x 13 km.6 MB. For a calculation resolution of 25 m.AT310_AM_E2 Atoll 3.

Atoll 3.0 Administrator Manual Chapter 10: Administration and Usage Recommendations © Forsk 2011 140 .1.

not in user configuration files. 141 . this file is named "Studies. By default. • 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 the User Manual. This file will be ignored if a user configuration file is loaded through the command line parameter. to update the paths to geographic data files). These files are optional. or b. It is possible to edit the contents of these files in an XML editor and make changes if required (for example. A user configuration file may be automatically loaded when Atoll is run if: a. A user configuration file containing the geographic data settings and other parameter settings can be saved with a CFG extension.0 Administrator Manual Chapter 11: Configuration Files 11 Configuration Files Configuration files can be used to store parameter and display settings. For more information on how to create and load user configuration files in Atoll. For more information on working with customised predictions in Atoll. and geographic export zones 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) Microwave link parameters Full paths to macro files • • Projection and display coordinate systems are stored in the database. see "Contents of Additional Configuration Files" on page 164. see the User Manual. but are useful means for making work easier. For more information on the contents of user configuration files. printing. The file is named "Atoll. Simulation settings are not stored in user configuration files. see "Contents of the Custom Predictions File" on page 168.AT310_AM_E2 Atoll 3.1. 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.cfg" and is located in the Atoll installation folder. • Custom predictions file (UTF-8 encoded XML files) This file contains the list and parameter settings of customised coverage predictions. see "Contents of User Configuration Files" on page 142. These files may store: • • • • • • • • • • Geographic data settings Filtering.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. User configuration files must be created using Atoll to ensure correct syntax and structure. For more information on the contents of the custom predictions file. not required for working with Atoll. computation. The file is identified in the command line parameter -Cfg "cfgfilename" (see "Atoll Command Line Parameters" on page 31 for more information). focus.

The following details are available: • • • • • • • • • • "Geographic Data Set" on page 142 "Folder Configuration" on page 145 "Zones" on page 145 "Coverage Predictions" on page 152 "Automatic Neighbour Allocation Parameters" on page 154 "Automatic Frequency Planning Parameters" on page 156 "Automatic Scrambling Code Allocation Parameters" on page 157 "Automatic PN Offset Allocation Parameters" on page 158 "Microwave Radio Links Parameters" on page 160 "Macros" on page 163. <LineStyle>. EC_IO_STDDEV. visibility flag <visible>. MIMO_GAIN_FACTOR. selected field <FieldSelector>. FORTHO • Under <TD-SCDMA>: STDDEV. <DatumShiftX>. <SecondaryColor>.0 Administrator Manual Chapter 11: Configuration Files © Forsk 2011 11. STTD_GAIN_OFFSET • Under <1XRTT>: STDDEV. and label font style <Style> • <Items> properties. FORTHO_DL. and <FillStyle> • <AddToLegend>: Add to legend option checked or not • <Type>: Data type properties. font colour <Color>. <MainColor>.16e>: STDDEV. <LineWidth>. EB_NT_UL_STDDEV. such as: label font name <Name>. <ProjectionLatitudeOrigin>. geoclimatic parameters.1. label font background colour <BackColor>. such as for each item: <Value>. label font size <Size>. <CoordinateSystemCode>. <ProjectionZone>. EB_NT_UL_STDDEV. EB_NT_DL_STDDEV. minutes. and <ProjectionAngle> Clutter Classes: • <Name>: Name of the folder • <Display>: (Different combinations of the following parameters exist in different display settings. NAME.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.1. ANGULAR_SPREAD • Under <IEEE_802.) • Display type <type>. <ProjectionScaleFactor>. and other vector layers: • <Name>: Name of the folder • <Display>: (Different combinations of the following parameters exist in different display settings. <Legend>. <ProjectionMethod>.) • Displate type <type>. <ProjectionFirstParallel>. <DatumShiftY>. EB_NT_UL_STDDEV. such as: <records> and <fields>. such as <Name>. 11. <EllipsoidCode>. <EllipsoidMinorRadius>. INDOOR. <Max>. for the fields stated above. DIV_GAIN_OFFSET_UL • <DefaultValues>. and visibility range between <minZoom> and <maxZoom> • <Items> properties. and visibility range between <minZoom> and <maxZoom> • <SymbolFont> properties. INDOOR. which are. such as: font name <Name>. <Type>. <Min>. HEIGHT • Under <GSM>: STDDEV. and seconds for geographic coordinate systems Population. ANT_HOP_GAIN • Under <UMTS>: STDDEV. INDOOR. MIMO_GAIN_FACTOR. vector traffic maps. EB_NT_DL_STDDEV. <SecondaryColor>. <ProjectionLongitudeOrigin>. EC_IO_STDDEV. • Common: CODE. coordinate system information. FORTHO_UL. ALPHA. selected field <FieldSelector>. <DatumRotationX>. <Min>. and <Integrable> • <File>: Contains the file format. Clutter Heights and Digital Terrain Models: • <Name>: Name of the folder • • 142 . <ProjectionSecondParallel>. <Legend>. <ProjectionFalseNorthing>. if any • Coordinate system information for vector format data including: <CoordinateSystemName>. INDOOR. font size <Size>.1 Geographic Data Set The following parameters are saved for various geographic data types: • • <DegreeFormat>: Format used to display degrees. <Max>. and font style <Style> • <LabelFont> properties. <DatumCode>. SM_GAIN_FACTOR. <LineStyle>. EB_NT_DL_STDDEV. INDOOR. <Formats>. • <Format> of and <Path> to linked files. STTD_OFFSET_DL. <LineWidth>. TX_DIV_GAIN. <DatumRotationZ>. FORTHO.Atoll 3. <DatumShiftZ>. COVERI_STDDEV. COVERI_STDDEV. <DatumRotationY>. <DatumScaleFactor>. STTD_OFFSET_UL • Under <LTE>: STDDEV. transparency level <Opacity>. such as for each item: <Value>. COLOR. and <FillStyle> • <AddToLegend>: Add to legend option checked or not • <Attributes>. <EllipsoidMajorRadius>. ALPHA. background colour <BackColor>. visibility flag <visible>. EC_IO_STDDEV. DIV_GAIN_OFFSET_DL. label font colour <Color>. path. <MainColor>. <ProjectionFalseEasting>. COVERI_STDDEV. INDOOR.

such as for each item: <Value>. <LineStyle>. <Legend>.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> <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> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </LabelFont> <Items> <Item> <Min>900. and <FillStyle> <AddToLegend>: Add to legend option checked or not <File>: <Format> and <Path> to linked files. <MainColor>.0 Administrator Manual Chapter 11: Configuration Files • • • Sample <Display>: (Different combinations of the following parameters exist in different display settings.</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> 143 . <SecondaryColor>.1.AT310_AM_E2 Atoll 3. <Min>.</Min> <Max>1000. visibility flag <visible>. if any Sample with display set to value intervals. <Max>. selected field <FieldSelector>. <LineWidth>. <?xml version="1. transparency level <opacity>.) • Displate type <type>. and visibility range between <minZoom> and <maxZoom> • <Items> properties.

</Min> <Max>56.</Max> <Legend>54 <=Height (m) <56</Legend> <MainColor>255 38 0</MainColor> <SecondaryColor>255 38 0</SecondaryColor> <LineStyle>5</LineStyle> <LineWidth>10</LineWidth> <FillStyle>1</FillStyle> </Item> </Items> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> </Display> <Attributes> <fields> <field length="1" type="uint" name="CODE"/> <field length="4" type="int" name="COLOR"/> <field length="50" type="text" name="NAME"/> <field length="4" type="real" name="HEIGHT"/> </fields> <records/> </Attributes> <Name>Clutter Classes</Name> <AddToLegend>0</AddToLegend> <DefaultValues> </DefaultValues> </ClassifiedClutter> <Altitudes> // or <BuildingHeights> <Name>Digital Terrain Model</Name> // or <Name>Clutter Heights</Name> <Display> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> <Type>ByIntervals</Type> <FieldSelector>0</FieldSelector> <Opacity>50</Opacity> 144 .1.Atoll 3.0 Administrator Manual Chapter 11: Configuration Files © Forsk 2011 <Type>800</Type> <Integrable>1</Integrable> </Type> <Files/> </Population> // or </GeoClimaticParams> or </Vectors> <ClassifiedClutter UseOnlyDefault="0"> <Display> <Type>ByIntervals</Type> <FieldSelector>3</FieldSelector> <Opacity>50</Opacity> <Items> <Item> <Min>54.

the points forming these polygons.. The first and the last points have the same coordinates.000000</Point> </CalculationZone> <FocusZone> <Point>35950.000000</Point> <Point>33.000000 -33.000000 -15445. focus.AT310_AM_E2 Atoll 3.</Min> <Max>1000.1.</Max> <Legend>900 <=Altitude <1 000</Legend> <MainColor>255 96 0</MainColor> <SecondaryColor>255 96 0</SecondaryColor> <LineStyle>5</LineStyle> <LineWidth>10</LineWidth> <FillStyle>1</FillStyle> </Item> </Items> </Display> <AddToLegend>0</AddToLegend> </Altitudes> // or </BuildingHeights> </Geodataset> </Atoll> 11.000000</Point> <Point>33. <?xml version="1.3 Folder Configuration The following parameters are saved for the following folders: • Sites folder: • <Name>: Name of the folder • <Display>: • Displate type <type>.0" encoding="UTF-8"?> <Atoll> <CalculationZone> <Point>35950.000000</Point> <Point>35950. visibility flag <Visible>.000000</Point> <Point>33.000000 -33.0 Administrator Manual Chapter 11: Configuration Files <Items> <Item> <Min>900.1.1.2 Zones The user configuration files store the coordinates of the vertices of the filtering. i.000000</Point> <Point>35950. printing.000000 -15445. and visibility range between <MinZoom> and <MaxZoom> 145 . Sample The following sample has rectangular computation and focus zones of the same size.000000 -33.000000 -15445.000000 -15445.000000</Point> <Point>35950. selected field <FieldSelector>.000000 -33.000000</Point> </FocusZone> <Atoll> 11.e. and geographic export zone polygons.000000 -15445.000000</Point> <Point>35950. computation.000000 -15445.000000</Point> <Point>33.

this tag contains the default configuration <Filter>. this tag contains the default configuration <Filter>. such as for each <Item>: <Value>. <Groups>.0 Administrator Manual Chapter 11: Configuration Files © Forsk 2011 • • • • <SymbolFont> properties. and visibility range between <MinZoom> and <MaxZoom> • <LabelFont> properties. label font size <Size>. label font colour <Color>. and Point to Multipoint folders: • <Name>: Name of the folder • <Display>: • Displate type <Type>. label font size <Size>. font size <Size>. label font background colour <BackColor>. Multi-Hops. such as for each <Item>: <Value>. font colour <Color>. background colour <BackColor>.. this tag contains the configuration <Name> and the <Filter>. such as font name <Name>. label font background colour <BackColor>. <Symbol>. label font background colour <BackColor>. visibility flag <Visible>. <SecondaryColor>. and label font style <Style> • <Items> properties. this tag contains the default configuration <Filter>. and label font style <Style> • <SiteDisplay> properties. font colour <Color>. <Groups>.1. and label font style <Style> • <Items> properties. label font size <Size>. label font colour <Color>. font colour <Color>. and visibility range between <minZoom> and <maxZoom> • <AddToLegend>: Add to legend option checked or not • <DefaultConfiguration>: The default configuration for the folder • <LabelFont> properties. <SecondaryColor>. and <Sort> criteria Transmitters. background colour <BackColor>. such as: • <SymbolFont> properties. <Legend>. <Symbol>. and <Sort> criteria Links folder: • <Name>: Name of the folder • <Display>: Contains visibility flag <visible>. and <Sort> criteria • <Configuration>: If any configuration exists for the folder. such as: • <SymbolFont> properties. such as: label font name <Name>. i. <LocalMargin>. this tag contains the configuration <Name> and the <Filter>. label font background colour <BackColor>. its <Code> and whether it is in the <Filter> or not • <Advanced>: Any advanced filter used for filtering • <PathLosses>: Path loss tuing parameters. such as label font name <Name>. such as: font name <Name>. font size <Size>. <Legend>. <GlobalMargin>. <MainColor>. and label font style <Style> • <Symbol>: Symbol used for microwave links • <ShowText>: Caption for microwave links shown or not • <RepeaterDisplay> properties. font size <Size>. and <Threshold> • <Display>: • • • 146 . <Groups>. selected field <FieldSelector>. such as: label font name <Name>. such as label font name <Name>. and <SymbolSize> • <DataTips>: List of <items> displayed in tip texts • <Labels>: List of <items> displayed in labels • <AddToLegend>: Add to legend option checked or not • <DefaultConfiguration>: The default configuration for the folder. <Groups>. and font style <Style> • <LabelFont> properties. background colour <BackColor>. label font colour <Color>. such as: font name <Name>. <PerpendicularAxisRadius>. label font size <Size>. this tag contains the configuration <Name> and the <Filter>.Atoll 3. <Groups>. and font style <Style> • <LabelFont> properties. label font colour <Color>. <Groups>. and <Sort> criteria • Antennas folder: • <Name>: Name of the folder • <DefaultConfiguration>: The default configuration for the folder. and font style <Style> CW Measurements folder: • <DefaultConfiguration>: The default configuration for the folder • <Distance>: The minimum <Min> and maximum <Max> distance for measurement filtering • <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>.e. and <Sort> criteria <Configuration>: If any configuration exists for the folder. <MainColor>. and <Sort> criteria • <Configuration>: If any configuration exists for the folder. <ParallelAxisRadius>. and <SymbolSize> • <DataTips>: List of <items> displayed in tip texts • <Labels>: List of <items> displayed in labels <AddToLegend>: Add to legend option checked or not <DefaultConfiguration>: The default configuration for the folder.

label font size <Size>. <SecondaryColor>.0" encoding="UTF-8"?> <Atoll> <FoldersConfigurations> <Sites> <Name>Sites</Name> <Display> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> <Type>ByValues</Type> <FieldSelector>8</FieldSelector> <SymbolFont> <Name>Wingdings</Name> <Size>-120</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>32</Style> </SymbolFont> <LabelFont> <Name>MS Shell Dlg</Name> <Size>-80</Size> 147 . label font colour <Color>. i. <ParallelAxisRadius>. label font size <Size>. and font style <Style> • <LabelFont> properties. selected field <FieldSelector>. and <SymbolSize> • <DataTips>: List of <items> displayed in tip texts • <Labels>: List of <items> displayed in labels <AddToLegend>: Add to legend option checked or not Drive Test Data folder: • <Techno>: Name of the technology (if exported from a 3GPP Multi-RAT document. such as for each <Item>: <Legend>. and visibility range between <MinZoom> and <MaxZoom> • <SymbolFont> properties.1. such as: label font name <Name>. <Symbol>. • <DefaultConfiguration>: The default configuration for the folder • <Clutter>: For each <Class>. label font colour <Color>. <MainColor>. font size <Size>. background colour <BackColor>.AT310_AM_E2 Atoll 3. <PerpendicularAxisRadius>. selected field <FieldSelector>. label font background colour <BackColor>. such as for each <Item>: <Legend>. and <SymbolSize> • <DataTips>: List of <items> displayed in tip texts • <Labels>: List of <items> displayed in labels • <AddToLegend>: Add to legend option checked or not Propagation Models and Smart Antenna Models folders: • <Name>: Name of the folder • <DefaultConfiguration>: The default configuration for the folder. <Groups>.e. font colour <Color>. label font background colour <BackColor>. and label font style <Style> • <Items> properties. <LocalMargin>. such as: font name <Name>. <MainColor>. such as: font name <Name>. and <Sort> criteria • Sample <?xml version="1. and <Threshold> • <Display>: • Displate type <Type>. background colour <BackColor>. its <Code> and whether it is in the <Filter> or not • <Advanced>: Any advanced filter used for filtering • <PathLosses>: Path loss tuing parameters. visibility flag <Visible>. <GlobalMargin>. visibility flag <Visible>. font size <Size>. and visibility range between <MinZoom> and <MaxZoom> • <SymbolFont> properties. and font style <Style> • <LabelFont> properties. font colour <Color>. and label font style <Style> • <Items> properties. this tag contains the default configuration <Filter>. <SecondaryColor>. such as: label font name <Name>..0 Administrator Manual Chapter 11: Configuration Files • • • Displate type <Type>. <Symbol>.

1.Atoll 3.0 Administrator Manual Chapter 11: Configuration Files © Forsk 2011 <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>33</Style> </LabelFont> <Items> <Item> <Value>Vendor</Value> <Legend>Vendor</Legend> <MainColor>255 0 0</MainColor> <SecondaryColor>255 255 255</SecondaryColor> <Symbol>164</Symbol> <SymbolSize>120</SymbolSize> </Item> </Items> <DataTips> <Item>0</Item> </DataTips> <Labels> <Item>0</Item> </Labels> </Display> <AddToLegend>1</AddToLegend> <DefaultConfiguration> <Groups>Type</Groups> </DefaultConfiguration> </Sites> <Antennas> <Name>Antennas</Name> <DefaultConfiguration> <Filter>([CONSTRUCTOR]= Kathrein)</Filter> </DefaultConfiguration> <Configuration> <Name>Conf</Name> <Filter>([CONSTRUCTOR]= Kathrein)</Filter> </Configuration> </Antennas> <Transmitters> // or <MWMultiHops> // or <MWHubs> <Name>Transmitters</Name> // or <Name>Multi-Hops</Name> // or <Name>Point to Multipoint</Name> <Display> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> <Type>ByValues</Type> <FieldSelector>0</FieldSelector> <Items> </Items> <DataTips> <Item>0</Item> 148 .

AT310_AM_E2 Atoll 3.1.0 Administrator Manual Chapter 11: Configuration Files </DataTips> </Display> <AddToLegend>1</AddToLegend> <DefaultConfiguration/> </Transmitters> // or </MWMultiHops> // or </MWHubs> <MWLinks> <Name>Links</Name> <Display> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> </Display> <AddToLegend>0</AddToLegend> <DefaultConfiguration/> <LabelFont> <Name>MS Shell Dlg</Name> <Size>-83</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </LabelFont> <SiteDisplay> <SymbolFont> <Name>Wingdings</Name> <Size>80</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </SymbolFont> <LabelFont> <Name>MS Shell Dlg</Name> <Size>-80</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </LabelFont> </SiteDisplay> <Symbol>65444</Symbol> <ShowText>0</ShowText> <RepeaterDisplay> <SymbolFont> <Name>Wingdings</Name> <Size>80</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </SymbolFont> </RepeaterDisplay> </MWLinks> 149 .

</PerpendicularAxisRadius> <GlobalMargin>30.</Max> </Distance> <DistanceUnit>0</DistanceUnit> <Measure> <Min>-105.1.0 Administrator Manual Chapter 11: Configuration Files © Forsk 2011 <CWMeasurements> <DefaultConfiguration> <Distance> <Min>0.</Min> <Max>-90.</Min> <Max>180.Atoll 3.</LocalMargin> <Threshold>-130. 500)</Advanced> </DefaultConfiguration> <PathLosses> <ParallelAxisRadius>200.</Max> </Measure> <MeasureUnit>0</MeasureUnit> <Angle> <Min>-180.</Threshold> </PathLosses> <Display> <Type>ByIntervals</Type> <FieldSelector>Error (P-M) (dB)</FieldSelector> <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> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </LabelFont> 150 .</Max> </Angle> <Relative>Yes</Relative> <Clutter> <Class> <Code>1</Code> <Filter>Yes</Filter> </Class> </Clutter> <Advanced>([DIST]&gt.</ParallelAxisRadius> <PerpendicularAxisRadius>100.</Min> <Max>1000.</GlobalMargin> <LocalMargin>30.

0 Administrator Manual Chapter 11: Configuration Files <Items> <Item> <Min>-20.</ParallelAxisRadius> <PerpendicularAxisRadius>100.AT310_AM_E2 Atoll 3.</GlobalMargin> <LocalMargin>30.</Min> <Legend>Error (P-M) (dB) &gt.</LocalMargin> <Threshold>-130.1.</PerpendicularAxisRadius> <GlobalMargin>30.</Threshold> </PathLosses> <Display> <Type>ByIntervals</Type> <FieldSelector>Ec_I0</FieldSelector> <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> 151 .=-20</Legend> <MainColor>255 0 0</MainColor> <SecondaryColor>0 0 0</SecondaryColor> <Symbol>167</Symbol> <SymbolSize>100</SymbolSize> </Item> </Items> <DataTips> <Item>M (dBm)</Item> </DataTips> <Labels> <Item>M (dBm)</Item> </Labels> </Display> </CWMeasurements> <TestMobileData> <Techno>GSM</Techno> <DefaultConfiguration> <Clutter> <Class> <Code>1</Code> <Filter>Yes</Filter> </Class> </Clutter> <Advanced></Advanced> </DefaultConfiguration> <PathLosses> <ParallelAxisRadius>200.

4 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 • <Name>: Name of the folder • <Resolution>: Prediction resolution • <Configuration>: <Filter>. <LineStyle>. Display tab: • <Display>: (Different combinations of the following parameters exist in different display settings.1. and visibility range between <minZoom> and <maxZoom> • <Items> properties. and <Sort> criteria for the prediction • <LockedStudy>: Locked or not Conditions tab: Depend on technologies and prediction types. <SecondaryColor>. <MainColor>. <Max>..0 Administrator Manual Chapter 11: Configuration Files © Forsk 2011 <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </LabelFont> <Items> <Item> <Min>-60. visibility flag <visible>. <Groups>.. <LineWidth>. and <FillStyle> • <AddToLegend>: Add to legend option checked or not • <DataTips>: List of <items> displayed in tip texts • • Sample GSM coverage by signal level <?xml version="1. <Min>. • <Reliability>: Cell edge coverage probability • <Indoor>: Indoor coverage checked or not • <WithShadowing>: Shadowing margin taken into account or not • .) • Display type <type>.</Min> <Legend>Ec_I0 &gt.=-60</Legend> <MainColor>255 0 0</MainColor> <SecondaryColor>0 0 0</SecondaryColor> <Symbol>167</Symbol> <SymbolSize>100</SymbolSize> </Item> </Items> </Display> </TestMobileData> <PropagationModels> // or <SmartAntennasModels> <Name>Propagation Models</Name> // or <Name>Smart Antenna Models</Name> <DefaultConfiguration/> </PropagationModels> // or </SmartAntennasModels> </FoldersConfigurations> </Atoll> 11. such as for each item: <Value>.1. selected field <FieldSelector>.0" encoding="UTF-8"?> <Atoll> <Studies> <CoverageTRXStudy> <Techno>GSM</Techno> <Name>GSM: Coverage by Signal Level 0</Name> 152 . opacity <Opacity>.Atoll 3. <Legend>.

=-95</Legend> <MainColor>0 255 217</MainColor> <SecondaryColor>0 0 0</SecondaryColor> <LineStyle>5</LineStyle> <LineWidth>15</LineWidth> <FillStyle>1</FillStyle> </Item> <Item> <Min>-105.</Min> <Legend>Best Signal Level (dBm) &gt.=-85</Legend> <MainColor>70 255 0</MainColor> <SecondaryColor>0 0 0</SecondaryColor> <LineStyle>5</LineStyle> <LineWidth>15</LineWidth> <FillStyle>1</FillStyle> </Item> <Item> <Min>-95.AT310_AM_E2 Atoll 3.</Min> <Legend>Best Signal Level (dBm) &gt.</Min> <Legend>Best Signal Level (dBm) &gt.1.=-105</Legend> <MainColor>0 0 255</MainColor> <SecondaryColor>0 0 0</SecondaryColor> <LineStyle>5</LineStyle> <LineWidth>15</LineWidth> <FillStyle>1</FillStyle> </Item> </Items> <DataTips> <Item>c0000000</Item> <Item>c0000001</Item> </DataTips> 153 .0 Administrator Manual Chapter 11: Configuration Files <Display> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> <Type>ByIntervals</Type> <FieldSelector>80000008</FieldSelector> <Opacity>50</Opacity> <Items> <Item> <Min>-75.=-75</Legend> <MainColor>255 147 0</MainColor> <SecondaryColor>0 0 0</SecondaryColor> <LineStyle>5</LineStyle> <LineWidth>15</LineWidth> <FillStyle>1</FillStyle> </Item> <Item> <Min>-85.</Min> <Legend>Best Signal Level (dBm) &gt.

This tag contains the name of the technology to which the parameters belong.5 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.Atoll 3.</Min> </FieldDbm> <Reliability>0. 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 154 .1.0 Administrator Manual Chapter 11: Configuration Files © Forsk 2011 </Display> <AddToLegend>1</AddToLegend> <Resolution>50</Resolution> <LockedStudy>0</LockedStudy> <ComputeHisto>1</ComputeHisto> <HistoPerTx>0</HistoPerTx> <HistoLabel></HistoLabel> <Conditions> <FieldDbm> <Min>-105.1.75</Reliability> <TRXType>BCCH</TRXType> <DefTrgThreshold>1</DefTrgThreshold> <Indoor>0</Indoor> <WithShadowing>0</WithShadowing> </Conditions> </CoverageTRXStudy> </Studies> </Atoll> 11.

0 Administrator Manual Chapter 11: Configuration Files • • <UseGlobalThreshold>: Coverage conditions for WiMAX and LTE: Whether to use a global minimum preamble C/ N or RSRP. 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.0" encoding="UTF-8"?> <Atoll> <ANP_options> <Techno>UMTS</Techno> <numMax>16</numMax> <resolution>-1</resolution> <minField>-10500</minField> <margin>500</margin> <useCoSite>1</useCoSite> <useAdjacent>1</useAdjacent> <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> 155 . 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.AT310_AM_E2 Atoll 3. intra-technology neighbour allocation only) Parameters specific to WiMAX 802.1.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: <?xml version="1. TD-SCDMA.

<defSeparations__CONF_NEIGH_BOUR_BT>: Default neighbour separation rule a for BCCH and a TCH type TRX..1. <defSeparations__CONF_NEIGH_BOUR_BB>: Default neighbour separation rule for two BCCH type TRXs.1.0" encoding="UTF-8"?> <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> <allocType>315</allocType> <freezeState>0</freezeState> <numMinutes>1000</numMinutes> <useDTX>0</useDTX> <defSeparations__CONF_CO_SITE_BB>: Default co-site 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_SITE_TT>: Default co-site separation rule for two TCH type TRXs. <defSeparations__CONF_CO_CELL_BB>: Default co-transmitter separation rule for two BCCH type TRXs.6 Automatic Frequency Planning Parameters The following parameters are saved for automatic frequency planning (GSM GPRS EDGE documents): • • • • • • • • • • • • • • • • • • • • • • Sample <?xml version="1. <defSeparations__CONF_CO_CELL_TT>: Default co-transmitter separation rule for two TCH type TRXs.0 Administrator Manual Chapter 11: Configuration Files © Forsk 2011 <maxCos>10000</maxCos> <UseGlobalThreshold>0</UseGlobalThreshold> <EcIoMin>-1400</EcIoMin> <usePmax>0</usePmax> <PerCentMaxPower>5000</PerCentMaxPower> <EcIoMax>-700</EcIoMax> <useEcIoMax>0</useEcIoMax> </ANP_options> </Atoll> 11. <defSeparations__CONF_NEIGH_BOUR_TT>: Default neighbour separation rule for two TCH type TRXs.e. <defSeparations__CONF_CO_CELL_BT>: Default co-transmitter separation rule for a BCCH and a TCH type TRX. i.Atoll 3. modification of existing TRXs allowed or not 156 . <allocType>: The parameters/resources to be allocated (memorised from the last AFP session) <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.

AT310_AM_E2 Atoll 3.0 Administrator Manual Chapter 11: Configuration Files <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> 11. 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) <PerCentMaxPower>: The percentage of the maximum downlink power is <usePmax> is set to 0 (not used in TDSCDMA) <Max1stNghbCost>: The maximum cost of 1st order neighbours <Max2ndNghbCost>: The maximum cost of 2nd order neighbours <Max3rdNghbCost>: The maximum cost of 3rd order neighbours <CoplanCost>: The cost for inter-technology neighbours <MaxCoClusterCost>: The maximum cost for same-cluster/SYNC_DL neighbours <MaxDistCost>: The maximum cost for a minimum reuse distance constraint violation <ExcepPairCost>: The cost for exceptional pair constraint violation <UseIndoor>: Coverage conditions: Use indoor losses defined per clutter class or not <UseCloseNghbs>: Take the Close Neighbours constraint into account or not (TD-SCDMA only) <CloseDistance>: Maximum distance within which close neighbours are located (TD-SCDMA only) <CloseImportance>: Minimum importance value of close neighbour (TD-SCDMA only) <MaxCloseCost>: Maximum cost of a close neighbour relation (TD-SCDMA only) 157 .1. 2nd.7 Automatic Scrambling Code Allocation Parameters The following parameters are saved for automatic scrambling code allocation (UMTS HSPA and TD-SCDMA documents): • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Sample <?xml version="1.1. 1st. i.e.0" encoding="UTF-8"?> <Atoll> <SCP_options> <MinEcI0>-1500..</MinEcI0> <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.

</margin> <reliability>5000.</CloseDistance> <CloseImportance>3000.</reliability> <DistanceMin>200000.</CloseImportance> <MaxCloseCost>100</MaxCloseCost> </SCP_options> </Atoll> 11.0 Administrator Manual Chapter 11: Configuration Files © Forsk 2011 <margin>500.</DistanceMin> <Strategy0>1</Strategy0> <Strategy1>1</Strategy1> <Strategy2>1</Strategy2> <Strategy3>1</Strategy3> <Strategy>0</Strategy> <FromScratch>1</FromScratch> <UseCurrentNghbs>1</UseCurrentNghbs> <NghbOrder>1</NghbOrder> <ComputeNghbs>0</ComputeNghbs> <UseMaxCodes>1</UseMaxCodes> <UseShadowing>1</UseShadowing> <SameCodeForCarriers>0</SameCodeForCarriers> <NbClusterPerSite>3</NbClusterPerSite> <ClustNghbs>0</ClustNghbs> <Clust2ndNghbs>0</Clust2ndNghbs> <NbCodesPerCluster>8</NbCodesPerCluster> <UseDistance>1</UseDistance> <UseExcepPairs>1</UseExcepPairs> <minField>-10500</minField> <usePmax>0</usePmax> <PerCentMaxPower>5000</PerCentMaxPower> <Max1stNghbCost>100</Max1stNghbCost> <Max2ndNghbCost>50</Max2ndNghbCost> <Max3rdNghbCost>5</Max3rdNghbCost> <CoplanCost>100</CoplanCost> <MaxCoClusterCost>50</MaxCoClusterCost> <MaxDistCost>100</MaxDistCost> <ExcepPairCost>100</ExcepPairCost> <UseIndoor>0</UseIndoor> <UseCloseNghbs>1</UseCloseNghbs> <CloseDistance>80000.8 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 158 .Atoll 3.1.1.

</TDrop> <reliability>6000.</DistanceMin> <Strategy0>1</Strategy0> <Strategy1>1</Strategy1> <Strategy2>1</Strategy2> <Strategy>2</Strategy> <FromScratch>1</FromScratch> <UseCurrentNghbs>1</UseCurrentNghbs> <NghbOrder>1</NghbOrder> <ComputeNghbs>1</ComputeNghbs> <SameCodeForCarriers>0</SameCodeForCarriers> <PilotIncr>4</PilotIncr> <PNClusterSize>3</PNClusterSize> <UseDistance>1</UseDistance> <UseExcepPairs>1</UseExcepPairs> <UseMaxCodes>1</UseMaxCodes> <MinEcI0>-1600.0 Administrator Manual Chapter 11: Configuration Files • • • • • • • • • • • • • • • • • • • • Sample <UseCurrentNghbs>: Use existing neighbours or not <NghbOrder>: The order of neigbours to take into account. i. 2nd.AT310_AM_E2 Atoll 3.</reliability> <UseShadowing>0</UseShadowing> <minField>-10500</minField> <usePmax>0</usePmax> <PerCentMaxPower>5000</PerCentMaxPower> <Max1stNghbCost>100</Max1stNghbCost> <Max2ndNghbCost>50</Max2ndNghbCost> <Max3rdNghbCost>5</Max3rdNghbCost> <CoplanCost>100</CoplanCost> <MaxDistCost>100</MaxDistCost> <ExcepPairCost>100</ExcepPairCost> <UseIndoor>0</UseIndoor> 159 .1. 1st..0" encoding="UTF-8"?> <Atoll> <PNO_options> <DistanceMin>200000.e. or 3rd <ComputeNghbs>: Calculate neighbours using the addition Ec/I0 conditions or not <UseShadowing>: Shadowing taken into account or not <SameCodeForCarriers>: Allocate same PN offset to cells of the same transmitter or not <PilotIncr>: Value for the PILOT_INC <PNClusterSize>: Number of PN offsets per cluster <UseDistance>: Take the minimum reuse distance into account or not <UseExcepPairs>: Take exceptional pairs into account or not <UseMaxCodes>: Use a maximum of codes or not <minField>: Minimum pilot signal level constraint <usePmax>: Use the maximum downlink transmission power or not <PerCentMaxPower>: The percentage of the maximum downlink power is <usePmax> is set to 0 <Max1stNghbCost>: The maximum cost of 1st order neighbours <Max2ndNghbCost>: The maximum cost of 2nd order neighbours <Max3rdNghbCost>: The maximum cost of 3rd order neighbours <CoplanCost>: The cost for inter-technology neighbours <MaxDistCost>: The maximum cost for a minimum reuse distance constraint violation <ExcepPairCost>: The cost for exceptional pair constraint violation <UseIndoor>: Coverage conditions: Use indoor losses defined per clutter class or not <?xml version="1.</MinEcI0> <TDrop>-1800.

uplink. <QualityObjective3>: Quality objectives <AvailabilityObjective0>. and <visible> <AddToLegend>: Add microwave links to legend window or not <QualityModel>: Quality model used for calculations <QualityObjective0>. <QualityObjective1>.9 Microwave Radio Links Parameters The following parameters are saved for microwave radio links: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Sample <?xml version="1.1. <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. <maxZoom>.0" encoding="UTF-8"?> <Atoll> <Microwave> <Name>Microwave Radio Links</Name> <Display> <minZoom>500</minZoom> <Name>: Name of the Microwave Radio Links folder <Display>: Display parameters for the microwave links. both) <ClutterCategory0> through <ClutterCategory36>: Bitsets for clutter category properties <ClutterDryCategory0> through <ClutterDryCategory36>: Soil type 160 . such as <minZoom>. <AvailabilityObjective1>.1.0 Administrator Manual Chapter 11: Configuration Files © Forsk 2011 </PNO_options> </Atoll> 11. downlink.Atoll 3. <QualityObjective2>.

</InterferenceDistanceMax> <InterferenceDropMin>1.AT310_AM_E2 Atoll 3.30000019</refDelayNM> <EquipPercent>33.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.1.e-003</BER1> <BER2>1.0 Administrator Manual Chapter 11: Configuration Files <maxZoom>20000000</maxZoom> <visible>Yes</visible> </Display> <AddToLegend>0</AddToLegend> <QualityModel>6</QualityModel> <QualityObjective0>3</QualityObjective0> <QualityObjective1>4</QualityObjective1> <QualityObjective2>2</QualityObjective2> <QualityObjective3>1</QualityObjective3> <AvailabilityObjective0>3</AvailabilityObjective0> <AvailabilityObjective1>2</AvailabilityObjective1> <AvailabilityObjective2>1</AvailabilityObjective2> <RainModel>5</RainModel> <RBER>1.</InterferenceRainSurfCorrelation> <InterferenceAutoWeight>0</InterferenceAutoWeight> <InterferenceUseAtpc>0</InterferenceUseAtpc> <InterferenceWidth>250</InterferenceWidth> <InterferenceOverShoot>0</InterferenceOverShoot> <CochannelOnly>0</CochannelOnly> <IgnoreIntraLinkInterference>1</IgnoreIntraLinkInterference> 161 .e-012</RBER> <ALFA1>10</ALFA1> <ALFA2>1</ALFA2> <RefDelayM>6.</InterferenceDropMinGlobal> <InterferenceCalcGo>1</InterferenceCalcGo> <InterferenceCalcReturn>1</InterferenceCalcReturn> <InterferenceCalcUplink>0</InterferenceCalcUplink> <InterferenceCalcDownlink>0</InterferenceCalcDownlink> <InterferenceRainSurfCorrelation>100.</EquipPercent> <RainPercent>33.88</kMin> <UseAtpc>0</UseAtpc> <P0Method>1</P0Method> <IgnoreXPD>1</IgnoreXPD> <IgnorePR>0</IgnorePR> <WhichBER>5</WhichBER> <BER1>1.</InterferenceDropMin> <InterferenceDropMinGlobal>3.</RainPercent> <kMoy>1.33</kMoy> <kMin>0.30000019</RefDelayM> <refDelayNM>6.

Atoll 3.1.0 Administrator Manual Chapter 11: Configuration Files © Forsk 2011 <Resolution>50</Resolution> <INTERF_DETAIL>both</INTERF_DETAIL> <ClutterCategory0>0</ClutterCategory0> <ClutterDryCategory0>B</ClutterDryCategory0> <ClutterCategory1>1</ClutterCategory1> <ClutterDryCategory1>B</ClutterDryCategory1> <ClutterCategory2>1</ClutterCategory2> <ClutterDryCategory2>B</ClutterDryCategory2> <ClutterCategory3>1</ClutterCategory3> <ClutterDryCategory3>B</ClutterDryCategory3> <ClutterCategory4>0</ClutterCategory4> <ClutterDryCategory4>B</ClutterDryCategory4> <ClutterCategory5>1</ClutterCategory5> <ClutterDryCategory5>B</ClutterDryCategory5> <ClutterCategory6>2</ClutterCategory6> <ClutterDryCategory6>B</ClutterDryCategory6> <ClutterCategory7>2</ClutterCategory7> <ClutterDryCategory7>B</ClutterDryCategory7> <ClutterCategory8>2</ClutterCategory8> <ClutterDryCategory8>B</ClutterDryCategory8> <ClutterCategory9>4</ClutterCategory9> <ClutterDryCategory9>B</ClutterDryCategory9> <ClutterCategory10>2</ClutterCategory10> <ClutterDryCategory10>B</ClutterDryCategory10> <ClutterCategory11>2</ClutterCategory11> <ClutterDryCategory11>B</ClutterDryCategory11> <ClutterCategory12>2</ClutterCategory12> <ClutterDryCategory12>B</ClutterDryCategory12> <ClutterCategory13>2</ClutterCategory13> <ClutterDryCategory13>B</ClutterDryCategory13> <ClutterCategory14>2</ClutterCategory14> <ClutterDryCategory14>B</ClutterDryCategory14> <ClutterCategory15>1</ClutterCategory15> <ClutterDryCategory15>E</ClutterDryCategory15> <ClutterCategory16>1</ClutterCategory16> <ClutterDryCategory16>E</ClutterDryCategory16> <ClutterCategory17>0</ClutterCategory17> <ClutterDryCategory17>E</ClutterDryCategory17> <ClutterCategory18>1</ClutterCategory18> <ClutterDryCategory18>E</ClutterDryCategory18> <ClutterCategory19>1</ClutterCategory19> <ClutterDryCategory19>E</ClutterDryCategory19> <ClutterCategory20>1</ClutterCategory20> <ClutterDryCategory20>E</ClutterDryCategory20> <ClutterCategory21>1</ClutterCategory21> <ClutterDryCategory21>E</ClutterDryCategory21> <ClutterCategory22>1</ClutterCategory22> <ClutterDryCategory22>E</ClutterDryCategory22> <ClutterCategory23>1</ClutterCategory23> 162 .

10 Macros The following parameters are saved for macros: • • • Sample <?xml version="1.0 Administrator Manual Chapter 11: Configuration Files <ClutterDryCategory23>E</ClutterDryCategory23> <ClutterCategory24>1</ClutterCategory24> <ClutterDryCategory24>E</ClutterDryCategory24> <ClutterCategory25>1</ClutterCategory25> <ClutterDryCategory25>E</ClutterDryCategory25> <ClutterCategory26>1</ClutterCategory26> <ClutterDryCategory26>A</ClutterDryCategory26> <ClutterCategory27>1</ClutterCategory27> <ClutterDryCategory27>A</ClutterDryCategory27> <ClutterCategory28>1</ClutterCategory28> <ClutterDryCategory28>A</ClutterDryCategory28> <ClutterCategory29>1</ClutterCategory29> <ClutterDryCategory29>A</ClutterDryCategory29> <ClutterCategory30>1</ClutterCategory30> <ClutterDryCategory30>A</ClutterDryCategory30> <ClutterCategory31>1</ClutterCategory31> <ClutterDryCategory31>E</ClutterDryCategory31> <ClutterCategory32>1</ClutterCategory32> <ClutterDryCategory32>E</ClutterDryCategory32> <ClutterCategory33>1</ClutterCategory33> <ClutterDryCategory33>E</ClutterDryCategory33> <ClutterCategory34>1</ClutterCategory34> <ClutterDryCategory34>E</ClutterDryCategory34> <ClutterCategory35>1</ClutterCategory35> <ClutterDryCategory35>E</ClutterDryCategory35> <ClutterCategory36>1</ClutterCategory36> <ClutterDryCategory36>E</ClutterDryCategory36> </Microwave> </Atoll> 11.1.vbs</Path> <Language>VBScript</Language> <Timeout>3600</Timeout> </File> </Macros> </Atoll> <Path>: Full path to the macro file <Language>: Language in which the macro is written <Timeout>: The target time allocated to macro execution 163 .AT310_AM_E2 Atoll 3.1.0" encoding="UTF-8"?> <Atoll> <Macros> <File> <Path>C:\TestsAddin\testEvents.

title text <text>.2 Contents of Additional Configuration Files Complete descriptions of the different additional configuration files are provided below.0 Administrator Manual Chapter 11: Configuration Files © Forsk 2011 11.1. and the inside map flag <Position vPos="" enable="" hPos="" insideMap=""/>. and font details <font height="" weight="" charset="" face="" italic=""/> Header/Footer tab: • Header logo <Logo>: Logo flag. comment text <text>.1 Print Setup Configuration The following parameters are saved for print setup: • Page tab <Page>: • Paper size and orientation <Paper size="" orientation=""/>. and font details <font height="" weight="" charset="" face="" italic=""/> • • Sample <?xml version="1. outer and inner position. vertical and horizontal position. and the inside map flag <Position vPos="" enable="" hPos="" insideMap=""/>.Atoll 3. logo image <bitmap>. and the inside map flag <Position vPos="" enable="" hPos="" insideMap=""/>. and the inside map flag <Position vPos="" enable="" hPos="" insideMap=""/>.2. vertical and horizontal position.0" encoding="UTF-8"?> <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> <Position vPos="0" enable="1" hPos="0" insideMap="0"/> <bitmap></bitmap> <Dimensions width="46" height="18"/> </Logo> <Title> <Position vPos="0" enable="0" hPos="1" insideMap="0"/> 164 . logo image <bitmap>. 11. vertical and horizontal position. and inside map flag <LegendPos enable="" majorPos="" minorPos="" insideMap=""/> • Comments <Comments>: Comments flag. footer text <text>. 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. and logo width and height in pixels <Dimensions width="" height=""/> • Footer text <Footer>: Footer flag. and font details <font height="" weight="" charset="" face="" italic=""/> • Footer logo <LogoBottom>: Logo flag. margins <Margins right="" left="" bottom="" top="">. and logo width and height in pixels <Dimensions width="" height=""/> • Header title <Title>: Header flag. and the inside map flag <Position vPos="" enable="" hPos="" insideMap=""/>. vertical and horizontal position. vertical and horizontal position.

2. </CHOOSEN_FIELDS> 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> 11.</FLD_SEPARATOR> <DEC_SEPARATOR>..2..0" encoding="UTF-8"?> <TITRE>1</TITRE> <FLD_SEPARATOR>&lt.tab&gt.3 Coverage Prediction Report Configuration The following parameters are saved for coverage prediction reports: • Sample <?xml version="1...2 Table Import/Export Configuration The following parameters are saved for table import/export: • • • • • Sample <?xml version="1.0 Administrator Manual Chapter 11: Configuration Files <text></text> <font height="14" weight="400" charset="1" face="MS Shell Dlg" italic="0"/> </Title> <LogoBottom> <Position vPos="1" enable="0" hPos="0" insideMap="0"/> <bitmap></bitmap> <Dimensions width="46" height="18"/> </LogoBottom> <Footer> <Position vPos="1" enable="0" hPos="1" insideMap="0"/> <text></text> <font height="14" weight="400" charset="1" face="MS Shell Dlg" italic="0"/> </Footer> </PrintConfiguration> 11.AT310_AM_E2 Atoll 3.0" encoding="UTF-8"?> <ReportConfiguration> <SelectedFields> <Field> <Title>Surface (km²)</Title> Columns selected in the Columns to be displayed dialogue <SelectedFields> including the field titles <Field> <Title> 165 .</DEC_SEPARATOR> <FIELDS> Site Transmitter . </FIELDS> <CHOOSEN_FIELDS> Site Transmitter .1.

4 CW Measurement Import Configuration More than one CW measurement import configurations can be saved in a single MeasImport.2.1.ini file..5 Gain=0 Losses=0 NbCol=23 Col0=1 Col3=4 Index 0 1 2 3 4 166 .txt Xindex=1 Yindex=2 MeasIndex=4 Unit=0 Frequency=2110 Height=1.0 Administrator Manual Chapter 11: Configuration Files © Forsk 2011 </Field> <Field> <Title>% of Covered Area</Title> </Field> . The following parameters are saved in the MeasImport.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 Text Integer Real Date <Ignore> Sample [ConfigurationName] Header=2 Separator=tab DecimalSeparator=. </SelectedFields> </ReportConfiguration> 11.Atoll 3. Pattern=*..

Pattern=*.16e NbCol=21 Col0=1 Col3=1 Index 0 1 2 3 4 5 6 167 .* Xindex=1 Yindex=2 Unit=0 Height=1.5 Gain=0 Losses=0 GenericNameIdOne= GenericNameIdTwo=BSID IdFormat=Decimal Techno=IEEE 802.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) 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 Text Integer Long Integer Single Double Date <Ignore> Sample [ConfigurationName] Header=2 Separator=tab DecimalSeparator=.5 Drive Test Data Import Configuration More than one drive test data import configurations can be saved in a single NumMeasINIFile.AT310_AM_E2 Atoll 3.ini file...0 Administrator Manual Chapter 11: Configuration Files Col5=0 . The following parameters are saved in the NumMeasINIFile.2. 11.1.

see "Coverage Predictions" on page 152. For more information. 168 .Atoll 3. 11.1.3 Contents of the Custom Predictions File The contents of the custom predictions file are the same as those of the coverage prediction list in the user configuration files excluding the <Atoll></Atoll> and <Studies></Studies> tags..0 Administrator Manual Chapter 11: Configuration Files © Forsk 2011 Col4=4 ..

but are useful means for selecting required calculation methods and other settings. 12. calculation settings. The Atoll initialisation file may be automatically loaded when Atoll is run if: a. 12. In case of sites. see "Atoll Initialisation File" on page 169.ini file exists. You have to restart Atoll in order to take into account any modifications in the Atoll. it is possible to specify prefixes to be used for naming sites and transmitters.0 Administrator Manual Chapter 12: Initialisation Files 12 Initialisation Files Initialisation files can be used to store operational and working environment settings.1.ini file in the Atoll installation folder for editing by pressing CTRL+SHIFT+i. see "ACP Initialisation File" on page 205.1. you must add these lines: [Site] Prefix = "newprefix" Each new site will then be named “newprefixN” instead of “SiteN”. For transmitters. The file is named "Atoll.1 Modifying the Default Formats of Site and Transmitter Names Through the Atoll. The file is identified in the command line parameter -Ini "inifilename" (see "Atoll Command Line Parameters" on page 31 for more information). or b.1.1 General Options 12. You should not modify any option until and unless you are absolutely sure of what you are doing. • • You can open the Atoll.AT310_AM_E2 Atoll 3. If no Atoll. and other options.ini file. For more information on these options. These files are optional. For more information on these options. you can define a prefix by adding these lines: [Transmitter] 169 .ini" and is located in the Atoll installation folder. This file will be ignored if an initialisation file is loaded through the command line parameter.1.ini file is created.ini file. not required for working with Atoll.1 Atoll Initialisation File The following main groups of options are available: • • • • • • • • • • • "General Options" on page 169 "GUI Options" on page 178 "Distributed Calculation Server Options" on page 181 "Licence Management Options" on page 182 "Database Options" on page 183 "Common Calculation Options" on page 185 "GSM GPRS EDGE Options" on page 191 "UMTS HSPA. and TD-SCDMA Options" on page 194 "WiMAX and LTE Options" on page 200 "Microwave Radio Links Options" on page 203 "Measurement Options" on page 204 The Atoll initialisation file is a powerful tool. • ACP initialisation file (INI files) This file contains calculation settings and other options for the ACP module. CDMA2000. where N is the site number or index. a blank Atoll. This chapter describes the formats of these files in detail: • Atoll initialisation file (INI files) This file contains conventions.

this suffix will be a letter.ini file: First = X Where. The default value is 1.log" will be created by Atoll as an ASCII text file. To do this.ini in order to save all the warning. the suffix X in the transmitter name Sitename_X will be a number.. or setting the prefix to <Auto> (Prefix = "<AUTO>"). i. it will not create any log.ini file must contain these lines: [TiffExport] PaletteConvention = Gis 12.ini: [EventsObserver] LogPath = FullPath\LogFile. you can also initialise the number suffix at any other number than 1. The starting suffix in this case will be A by default but can be changed to any other character through the second line. Not adding the above lines.e.1. Automatic renaming according to site names is enabled by default.log The path should be the full path to the log file. it may be disabled by adding the following lines in the Atoll. each transmitter will be named Sitename_X. and can have any file name and extension. However. the Atoll.1.1.e. 12. Atoll automatically renames the transmitters and cells related to the site according to the new site name. the first colour indexes represent the useful information and the remaining colour indexes represent the background.4 Creating an Event Viewer Log File You can define a log file path and file name in Atoll. Similarly. To do so. If Atoll is unable to overwrite the existing log file. You can also define whether the suffix X in the transmitter’s name should be a number or a letter. error and information messages displayed in the Event Viewer window to a log file. You may export TIFF files with a palette containing the background colour at index 0 along with other colour indices representing the foreground.1. Atoll will overwrite any already existing log file with the same name.2 Disabling Automatic Renaming of Transmitters and Cells When the name of any site is modified. renaming a transmitter renames the corresponding cells automatically. "3Gcells" refers to cell renaming when the transmitter name is changed. 170 . i. If you are using number suffixes. which can be. The following two lines define this option in the Atoll.1. will instruct Atoll to keep the conventional naming method. the default. for example. 12.ini file: SuffixIsNum = 0 or 1 FirstCharSuffix = "A" When SuffixIsNum = 1. you can add the following lines under the [Transmitter] section of the Atoll. it is also possible to remove the underscore character "_" from the transmitter’s name. the transmitter can be named SitenameX instead of Sitename_X. "LogFile. "\\Server\Drive\Root\Folder\Atoll\" or "C:\Program Files\Forsk\Atoll\" (without quotation marks).. X is a number.ini file: [AutoRename] Transmitters = 0 3GCells = 0 • • "Transmitters" refers to transmitter renaming when the site name is changed.1. To do this. This can be helpful when working on TIFF files exported by Atoll in other tools.1.ini file: Underscore = 0 or 1 Setting this value to 0 means the underscore character will not be used when naming transmitters.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 Prefix = "newprefix" 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). To do this. add the following lines to Atoll. Furthermore.Atoll 3.3 Setting the TIFF Colour Convention In the default palette. When it is set to 0. add the following line in the [Transmitter] section of the Atoll.

If two files point to the same linked path loss matrices folder. you can add the following lines to the Atoll.1..ini file: [Print] MaxDPI = 300 300 dpi is given as an example only. If you set StoreExternPrivLosFilesOnCopy to 0. the command line log file will have priority over the one mentioned in the Atoll.1.e. or by modifying the shortcut parameters. Atoll does not create the linked path loss matrices folder corresponding to the created file. but it will no longer point to any private path loss matrices folder. with 0 dB margin.ini file: [Perfos] StoreExternPrivLosFilesOnCopy = 0 StoreExternPrivLosFilesOnCopy is set to 1 by default. Atoll lists all the best server coverage prediction available in the Predictions folder.exe -log LogFile. 12. In the list of available best server coverage predictions.log". 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). 12.AT310_AM_E2 Atoll 3. whether they were created using a margin or without. 12.1.0 Administrator Manual Chapter 12: Initialisation Files You can also start Atoll. If you want Atoll not to make copies of the linked path loss matrices.. you can add another option in the Atoll.ini file. and the linked path loss matrices of the original Atoll document are used for the new Atoll document as well.ini file: [Perfos] ConfirmStoreExternPrivLosFilesOnCopy = 1 ConfirmStoreExternPrivLosFilesOnCopy is set to 0 by default.ini file. If you want Atoll to list only the best server coverage predictions that were created without a margin. To add this confirmation step on Save As. If you want Atoll to print your maps in a higher resolution than 150 dpi. 171 .1. Atoll uses an existing best server coverage prediction in order to be able to distribute the live traffic data geographically. if you have more than one file that points to the same private path loss matrices folder.7 Restricting the List of Predictions for Creating Sector Traffic Maps When you create a sector traffic map. i. by starting it with "Atoll. you can add the following lines to the Atoll.1. Therefore. When StoreExternPrivLosFilesOnCopy is set to 1. specifying a log file. which means that Atoll makes copies of the linked path loss matrices on Save As. add the following lines in the Atoll. The option available in Atoll.ini is more suitable for running Atoll using macros. and run Atoll with the -log option in the command line. traffic map based on cell coverage areas. Apart from these options. A file open in Atoll has exclusive access rights to its private path loss matrices.ini file: [Studies] SelectNullMarginOnly = 1 SelectNullMarginOnly is set to 0 by default. the file open first will have access to the the path loss matrices. which means that Atoll lists all the best server coverage predictions available. You will be able to open the second file. you should not open them at the same time. This option is ignored when Atoll is run in non-interactive mode. either from the command line.1.ini file to make Atoll ask the whether the user wants Atoll to make copies the linked path loss matrices or not. and copying these files may take a long time and use a lot of disk space. i. for example using the API. There can be a large number of LOS files. If you have a log file defined in the Atoll. you can add the following lines to the Atoll.5 Increasing the Maximum Printing Resolution By default. Atoll lets you select the best server coverage prediction on which the traffic map will be based.1.e. 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.6 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 limits the printing resolution to 150 dpi (dots per inch) to improve performance and consume less memory when printing.

45.1. Click the Properties button. click the browse button (.69601444. [MITAB] .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. If you want access to these details.ini file: [MITAB] Coordinate system definition in the header file = Coordinate system code in Atoll In this way. 0. These details are listed in the Events tab of the Event Viewer. 4. "m".1.9996.10 Exporting Coverage Prediction Polygons in Text Format You can export coverage predictions in the form of polygons to text format files. 2. and the number of calculations that failed.8989188889.) to the left of the Projection field. Atoll displays details about these calculations in the Tasks tab of the Event Viewer. setting DisplayIndividualSuccessOrFailure to 1 will display whether the path loss calculation succeeded or failed for each transmitter. On the Coordinates tab. The coordinate system definition is different in the PRJ files. datum. "m". 0. You can defne a mapping between the two coordinate systems by adding the following lines in the Atoll. In MIF files. or to a summary of these details.1.1. 3. 2200000 = 27595 12.1. the CoordSys clause defines the coordinate systems. NTF Earth Projection 1. The Coordinate System properties dialogue opens.1. The syntax used in Atoll.1. These details cannot be copied or saved. Select Tools > Options.Atoll 3. "m". 0 = 32654 . unit. 104.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 12.9 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. Atoll is able to exactly detect the coordinate system used by the vector file being imported. WGS 84 / UTM zone 31N Earth Projection 8. 0. 141. 46. 104.ini follows the syntax of the CoordSys clause in MIF files. NTF (Paris) / France II étendue Earth Projection 3. 107 = 4275 . Using the same syntax for MIF and PRJ files. 172 . 0. 1002. 3. 0.. To access the coordinate system codes through Atoll: 1.8. 500000. The coordinate system code is available in the properties dialogue. the number of path loss matrices calculated successfully. and setting DisplayOverallSuccessOrFailure to 1 will display the total number of path loss matrices calculated. 104. 0. and other information. once the calculations have finished. WGS 84 / UTM zone 53N Earth Projection 8. 47. The coordinate system codes in Atoll are stored in the CS files in the coordsystems folder. 12. 500000. 1. Select a coordinate system in the pane.. 0 = 32653 . The Coordinate Systems dialogue opens. A few examples of such mapping are given below.9996. "m". WGS 84 / UTM zone 54N Earth Projection 8.8 Displaying Path Loss Calculation Details in the Event Viewer During path loss calculations. 500000. Atoll is able to read the detect the coordinate systems for both MapInfo and ESRI vector files. 0 = 32631 . 600000. The Options dialogue opens. 97 = 4301 . 135. you can add the following lines in the Atoll. Tokyo Earth Projection 1.

The option PtAnalysisMargin lets you define the margin with respect to the best server signal level.11 Defining Web Map Services Servers Web Map Services allow you to directly import geographic data from specialised servers into Atoll. Atoll can dynamically load the data from SHP and TAB vector files when the following option is set in the Atoll. calculation speed.ini file as follows: [WMS] S1 = Server1 S2 = Server2 .. In addition to the above.txt)" to Atoll.1.1. SHP.12 Improving Point Analysis Performance You can improve the performance.13 Loading Vector Files Dynamically Vector geo data from files imported in an Atoll document are loaded in the memory when the document is open. only the largest polygon is exported for coverage layers having more than one polygon. TAB.0 Administrator Manual Chapter 12: Initialisation Files Enabling this option influences the export feature for all exportable vector fomats (MIF. These servers will be available in the WMS data import dialogue in Atoll.1. You can enable this feature by adding the following lines in the Atoll. 12.. To restrict the number of transmitters considered in the Point Analysis tool. 173 .1.. When you set LoadVectors to 1. which means that the data from imported vector files are loaded in memory. X is the maximum number of transmitters. add the following lines in the Atoll. AGD. When this option is enabled. you can also set the number of transmitters for which arrows are displayed from the pointer location in the map window. The default value for PtAnalysisMargin is 30 dB.1.ini file: [ReceptionTab] NumberOfTransmitterDisplayed = Z Z is the number of transmitters for which arrows generated from the pointer location will be displayed in the map window. Atoll calculates the signal levels from all the transmitters within Y dB margin from the best server signal level.AT310_AM_E2 Atoll 3.ini file: [Studies] EnableLBS = 1 Setting EnableLBS to 1 adds a new coverage prediction export format "LBS Polygon Files (*. From the point of view of performance. 12. of the Point Analysis tool by restricting the number of transmitters for which the received signal levels are calculated. SN = ServerN You can define any number of servers by incrementing the index N. i. TXT).ini file: [Import] LoadVectors = 1 LoadVectors is set to 0 by default. The list of WMS servers can be defined in the Atoll.1. add the following lines in the Atoll.ini file: [Perfos] PtAnalysisNbServersMax = X PtAnalysisMargin = Y The option PtAnalysisNbServersMax lets to define the maximum number of transmitters (servers) to consider for the calculation of the received signal levels. this option is only advisable when working with large vector data files.e. Atoll reads the data from the vector files directly.1. The polygons are exported in a comma separated values format. 12. For setting this number.

1. the pattern attenuations are considered the same if they differ less than 100 dB.1. add the following lines in the Atoll.19 Enabling Notification for Donor Transmitter Parameter Modifications Atoll can notify you whenever a donor transmitter parameter. 12. is modified. To ensable this feature.5 dB.ini file: [GUIUserRights] EnableNewDocFromTemplate = 0 EnableNewDocFromTemplate is set to 1 by default.1.1.1. which has an impact on a repeater.ini file: [Transmitter] CheckImpactOnRepeaters = 1 CheckImpactOnRepeaters is set to 0 by default. Atoll can automatically run MS Excel once the export is complete and open the XLS file created by the export in MS Excel. or selected columns. i. 12.ini file: [GUIUserRights] EnableMacrosAddins = 0 EnableMacrosAddins is set to 1 by default.18 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..14 Setting the Precision for the Antenna Pattern Verification at Import Atoll checks whether the vertical and horizontal patterns are correctly aligned at the extremities.e.15 Opening Exported XLS Files Automatically in MS Excel When you export an entire data table.ini file: [Export] AutoOpenWithExcel = 1 AutoOpenWithExcel is set to 0 by default.Atoll 3. 12.5 × 10 = 5 . 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. By default.17 Blocking Access to Macros and Add-ins You can block access to the Add-ins and Macros dialogue by adding the following lines in the Atoll. which means that no notifications are displayed. 12.1.ini file: [GUIUserRights] EnableZip = 0 EnableZip is set to 1 by default.1. To activate the notification. X will be 0. 12. add the following option in the Atoll. For example. the option is inactive. to an MS Excel file.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 12.1.1.1.1. if you want to set the precision to 0. 174 . If you want to change this default precision.ini file: [Antenna] PrecisionTimes10 = X Where X is the required precision in dB multiplied by 10. and the horizontal pattern attenuation at 180° is the same as the vertical pattern attenuation at the 180° less the pattern electrical tilt angle.1.16 Disallowing Creation of New Documents from Templates You can disallow the creation of new Atoll documents from templates by adding the following lines in the Atoll.1. add the following lines in the Atoll.

and PNG formats.1. For example. whether the geographic data is visible on the map or not. In order to link to another file..1.1.20 Setting the Display Precision of Floating Point Values Most floating point values in Atoll are formatted for displaying two digits after the decimal point.23 Exporting BMP.1. 12. By default. and PGW for PNG). i.ini file: [Geo] ReportObeysVisibility = 1 ReportObeysVisibility is set to 0 by default. you must follow the normal file import procedure. the Find button in the Properties dialogue is available only for missing geographic data files. This corresponds to maximum precision.21 Changing the Path to Linked Geo Data Files You can change the path to a linked geographic data file by clicking the Find button in the Properties dialogue of the file. in case of documents connected to databases (other than MS Access).ini file: [CoPlanning] LinkSites = 1 175 . and generic geographic data by adding the following lines in the Atoll. TFW for TIF. However.1. in order to display two digits after the decimal point. in addition to the Transmitters and Predictions folders. you can add the following lines in the Atoll.. Such formatted floating point values include thresholds and power values in dBm. You can change the default behaviour for population. Atoll can export the georeference information in a TAB file instead of the default respective World files (BPW or BMW for BMP.1. 12. If you want Atoll to export the georeference information in a TAB file when you export in BMP.1.1.0 Administrator Manual Chapter 12: Initialisation Files 12. When changing the path to a linked geographic data file. However.22 Using Only Visible Geo Data in Prediction Reports By default. some non-formatted floating point values may be displayed with too many digits after the decimal point. You can set the display precision for non-formatted floating point values in Atoll dialogues and tables. of a document to another (main) document using the File > Link With command by adding the following lines in the Atoll. excluding geographic coordinates and formatted floating point values.ini file: [Geo] FindGeoButtonAlwaysActive = 1 FindGeoButtonAlwaysActive is set to 0 by default.ini file: [RasterExport] GeorefWithTAB = 1 GeorefWithTAB is set to 0 by default.e. and PNG Files with a TAB Reference File When exporting BMP.1.24 Co-Planning: Linking the Sites Folder You can link the Sites folder.e.AT310_AM_E2 Atoll 3. all the digits after the decimal point available in the database are displayed. TIF. the linked files that Atoll is unable to locate and load. add the following lines in the Atoll. you must provide the new path to the same file. and PNG files..e. 12. This option may be useful when you have changed the location of a geographic data file. 12. TIF.ini file: [Grids] NbDecimals = 2 This option applies to all non-formatted floating point parameters in Atoll. You do not have to restart Atoll for it to take this option into account.1. you can enable the Find button even for available geographic data files by adding the following lines in the Atoll. TIF. traffic. Atoll takes into account all the geographic data when generating prediction reports. i.1. NbDecimals is set to -1 by default. This option does not allow linking to another file instead. and you wish to change the path to the new location. i.

0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 LinkSites is set to 0 by default. r.29 Displaying % of Covered Traffic Classes w.ini file: [Clutter] PerClassPercentagesRelativeToCoverageInReport = 0 PerClassPercentagesRelativeToCoverageInReport is set to 1 by default.25 Disabling Normalisation of MIF/TAB Vector Files When importing vector files.28 Displaying % of Covered Clutter Classes w.27 Using Only Visible Clutter Classes in Interference Prediction Reports By default. 12. 176 .26 Adding the Duplicate Site to the Original Site’s Site List When you duplicate a site.ini file: [Clutter] OnlyVisibleClassesInInterferenceReport = 1 OnlyVisibleClassesInInterferenceReport is set to 0 by default. You can change the default behaviour by adding the following lines in the Atoll.1. you can choose to add the duplicate site to the site list (if any) of the original site by adding the following lines in the Atoll. and a vector whose vertices coordinates are defined counterclockwise creates a hole. 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. t. t. 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. 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. the Focus Zone in Reports In coverage prediction reports.1. MapInfo vectors do not follow the same convention. The visibility of clutter classes on the map can be managed through the Display tab of the properties dialogue of the Clutter Classes folder. and hence their normalisation at the time of import may take a long time. If you want to disable this normalisation when importing MIF and TAB vector files.1.1.1. 12. Atoll takes into account all the clutter classes when generating reports on interference-based coverage predictions. for example.1. the Focus Zone in Reports In coverage prediction reports.ini file: [Traffic] PerClassPercentagesRelativeToCoverageInReport = 0 PerClassPercentagesRelativeToCoverageInReport is set to 1 by default. water. 12. 12. r.ini file: [MITAB] DisableNormalization = 1 DisableNormalization is set to 0 by default.1.Atoll 3. add the following lines in the Atoll.1.1. 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. Using this option you can exclude clutter classes which are not relevant in coverage prediction reports. 12. whether the clutter classes are visible on the map or not.1.1. Atoll displays the percentages of covered clutter classes with respect to the total surface area of all the clutter classes covered by the prediction.ini file: [Site] AddToSiteListOnDuplicate = 1 AddToSiteListOnDuplicate is set to 0 by default. add the following lines in the Atoll.

and Atoll does not display any messages related to MapInfo file import and export. If you wish to have the Logo 2 check box selected by default for any new Atoll document.ini file: [Print] LogoFooterChecked = 1 LogoFooterChecked is set to 0 by default. you can add the following lines in the Atoll..g. 12.1.0 Administrator Manual Chapter 12: Initialisation Files 12.1. and only load the predictions specific to the technology of the current active Atoll document.ini contains the following lines: [Pathlosses] FullResyncPrivShared = 1 If you have private path loss matrices tuned using measurement data. add the following lines to the Atoll.34 Setting Coverage Prediction Report Resolution For Population Maps Atoll uses the default resolution.AT310_AM_E2 Atoll 3. 177 . Atoll always writes the technology type in the XML studies file when customized coverage predictions are saved in it. and you can save the print setup parameters in CFG files (see "Print Setup Configuration" on page 164).1. defined in the Predictions folder’s properties dialogue. 12. separate the WiMAX and LTE coverage predictions. e.32 Filtering Predictions by Technology When Reading the XML Studies File In the XML studies file. If you wish to filter the customized predictions stored in the XML studies file by their technology.1.1. • • 12.31 Selecting the Logo 2 Check Box by Default in Print Setup Print setup parameters are stored in the Atoll documents. Atoll verifies whether the shared and private path loss matrices are valid. some common CDMA coverage predictions may be available for both CDMA2000 and UMTS.33 Enabling Event Viewer Messages for MapInfo File Import/Export You can enable the display of Event Viewer information.1.ini file: [MITAB] EnableMessages = 1 EnableMessages is set to 0 by default.1.ini contains the following lines: [Pathlosses] FullResyncPrivShared = 0 Atoll deletes any corresponding valid and invalid private path loss matrices and uses the valid shared ones for calculations if Atoll. or error messages related to MapInfo files by adding the following lines in the Atoll.30 Synchronising Private and Shared Path Loss Matrices When calculations are run. setting FullResyncPrivShared to 1 will make Atoll automatically delete them when calculations are run. If the shared path loss matrices are valid.1. 12. add the following lines in the Atoll. In order to use a different resolution for higher or lower precision.1. You should set FullResyncPrivShared to 0 when working with tuned private path loss matrices.ini file: [Population] ReportResolution = X Where X is the resolution for the conversion of population map vectors into raster. for rasterization of the population maps.1.1. This option is only relevant for reading the XML studies file. Atoll deletes any corresponding invalid private path loss matrices and uses the valid shared ones for calculations if Atoll.ini file: [Studies] CustomStudiesFilteredByTechno = 1 CustomStudiesFilteredByTechno is set to 0 by default. or some common OFDMA coverage predictions may be available for both WiMAX and LTE. FullResyncPrivShared is set to 1 by default. warning.

You can define the parametes 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 178 .1.2. the visibility check box of that level also controls the visibility check box of the prediction itself. just precise enough to get the required accuracy.1. 12.. This means that if the visibility check box of the only level of such a prediction is cleared. Atoll exports only visible coverage predictions. 12.ini file: [Studies] ExportOnlyVisibleLevels = 1 ExportOnlyVisibleLevels is set to 0 by default.ini file: [Studies] ReportDecimalPlacesPercent = X Where X is the number of digits following the decimal. the prediction will itself be hidden and will not be exported. 12.1.1.37 Exporting Only Visible Value Interval Layers of Coverage Predictions By default. the performance (calculation speed) can be considerably decreased depending on the size of the population maps in the document.2 GUI Options 12.e. 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 hot spots covered by each coverage layer (display thresholds) with as reference the hot spot surface area.ini file: [Studies] ReportDecimalPlacesAbsolute = X Where X is the number of digits following the decimal.ini file: [Studies] UseFullHotSpotSurfaceOnReport = 1 UseFullHotSpotSurfaceOnReport is set to 0 by default.Atoll 3. 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. Atoll exports all its levels.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. add the following lines in the Atoll.1. If you wish to export only the visible levels of a coverage prediction displayed by value intervals. 12. Atoll exports all the layers (levels) of a coverage prediction being exported.1. It is recommended to set this parameter to an optimum value. If a coverage prediction consists of only one level. add the following lines in the Atoll. which means that when any coverage prediction is exported. visible or not. i.36 Changing Hot Spot Reference Surface in Prediction Reports In a coverage prediction report.35 Setting Coverage Prediction Report Precision You can set the precision of the floating point values displayed in the absolute value columns of coverage prediction reports by adding the the following lines in the Atoll.1.1.1.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 If you set ReportResolution to a very precise (low) value.ini file.

0 Administrator Manual Chapter 12: Initialisation Files Color = Colour of the symbol The default sites symbol is used when a new document is created in Atoll.2.3 Keeping Transmitter Symbols From Changing on Search When using the Search Tool. add the following lines in the Atoll. or clutter height).ini file. remote antennas are displayed using the same symbol on the map as transmitters. Erdas Imagine. 12. and remote antennas on the map. Performance may be improved by either hiding the Status Bar or by hiding some of the information displayed in the Status Bar (altitude.1.2. ECW) can cause performance loss due to real-time decompression.1. nonmodifiable symbol for remote antennas on the map by adding the following lines in the Atoll. Example: [SitesSymbol] FontName = Wingdings Symbol = ¤ Size = 12 Color = 0 12.ini file: [Transmitter] ChangeSymbolOnSearch = 0 ChangeSymbolOnSearch is set to 1 by default.ini: 179 . Atoll empties the symbols of inactive trasnmitters. the remote antenna symbol will be fixed and no longer linked with the transmitter symbol.4 Displaying Filled Symbols for Inactive Transmitters on the Map By default. add the following lines to the Atoll.AT310_AM_E2 Atoll 3. repeaters. and to set the symbol.2. repeaters.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 adding the following lines in the Atoll.6 Hiding Information Displayed in the Status Bar Using compressed geo data formats (TIFF. You can use a unique.2. If you wish to display filled symbols for inactive transmitters. all the transmitters that do not fulfil the search criteria are displayed as grey lines on the map.ini file: [Transmitter] AutoSynchronizeDisplay = 1 AutosynchroniseDisplay is set to 0 by default. If you want these transmitters to keep their original symbols. 12.1. You can use the copy/paste features to set the symbol in the Atoll.1. and remote antennas on the map. To know the name of the font to use. 12.2.ini file: [RemoteAntennas] FrozenSymbol = 1 FrozenSymbol is set to 0 by default. clutter class. When you set FrozenSymbol to 1.2 Using a Unique Symbol for Remote Antennas By default. To hide information in the Status Bar.1. add the following lines in the Atoll. you can use the Windows’ Character Map tool.ini file: [Transmitter] EmptySymbolWhenInactive = 0 EmptySymbolWhenInactive is set to 1 by default.1. 12.

8 Setting the Maximum Number of Lines in Coverage Prediction Tool Tips If you have more than one coverage prediction displayed on the map. DisplayClutterClass and DisplayClutterHeight respectively refer to the display of altitude. calculated during Monte Carlo simulations using the Optimum Beamformer and Conventional Beamformer can be displayed in two different ways. 12. When you set DrawSingleElementPattern to 1. the tool tip might not display correctly.Atoll 3.ini file: [SAModel] DrawSingleElementPattern = 1 DrawSingleElementPattern is set to 0 by default.2. By default. For example.1.ini file: [EventsObserver] milliseconds = 1 date = 1 12. To display this information. 12. By default.1.1.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 following lines in the Atoll. If you want to display these diagrams taking into account the antenna pattern of the single antenna element. the angular distributions of downlink transmitted power density.ini file: [Display] CellIDNbDigits = X 180 . i. clutter class. and clutter height. you must set the minimun number of digits the CELL_IDENTITY field should contain by adding the following lines in the Atoll. Atoll does not display leading zeros in the CELL_IDENTITY field of the Transmitters table in GSM and the Cells tables in UMTS. the diagram displayed will represent g n ( ϕ ) ⋅ S ϕ ⋅ R Avg ⋅ S ϕ . add the following lines to the Atoll.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 [StatusBar] DisplayZ = 0 DisplayClutterClass = 0 DisplayClutterHeight = 0 DisplayZ.2. and TD-SCDMA.2. the tool tips display the tip text for all the coverage predictions available at a pixel up to 30 lines by default. If you set it to a very large value. add the following option in the Atoll. MultiplePlotsTipTextLines is set to 30. If you want Atoll to display leading zeros. and time with milliseconds in the Event viewer. these diagrams represent the average array correlation matrices and are symmetric about the x-axis (same on the front and back).2.7 Displaying Date and Time in the Event Viewer You can instruct Atoll to display the date.9 Changing the Display for Downlink Smart Antenna Results The downlink smart antenna simulation results. in which case the displayed diagram is S ϕ ⋅ R Avg ⋅ Sϕ .2.ini file: [Studies] CommentsInLegend = 1 The comments are displayed between the name of the coverage prediction and the thresholds. cell identity "00678" is displayed as "678".1. You can change this default number of tool tip text lines through the following option in the Atoll.11 Displaying Leading Zeros in the CELL_IDENTITY Field By default. CDMA2000. H H 12.e. CommentsInLegend is set to 0 by default. 12.1. however.ini file: [Studies] MultiplePlotsTipTextLines = X X is the number of lines to display in the tool tips.1.

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 12: Initialisation Files

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.

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

12.1.3 Distributed Calculation Server Options
12.1.3.1 Detecting and Listing Distributed Calculation Servers
You can use Atoll to detect distributed calculation servers and list them in the Atoll.ini file. A computer, serving as a 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.

12.1.3.2 Setting the Distributed Calculation Server Priority
By default, the Atoll distributed calculation server (AtollSvr.exe) runs with a normal process priority. However, it is 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 lines in the Atoll.ini file: [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.

12.1.3.3 Modifying the Default Detection Time-Out
The default time-out (2 seconds) for locating calculation servers within the network might be too short in certain cases. You can increase this time-out by adding the following lines to the Atoll.ini file:

181

Atoll 3.1.0 Administrator Manual Chapter 12: Initialisation Files

© Forsk 2011

[RemoteCalculation] DetectTimeOut = 5000 In this example, the detection time-out is set to 5000 ms.

12.1.4 Licence Management Options
12.1.4.1 Setting an Alarm for the Licence End Date
You can set a warning message about the licence end date to appear a certain number of days before this date. The Atoll.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.

12.1.4.2 Blocking Access to Technology Modules
This option is useful when working with a floating licence management system where a floating licence server manages and distributes tokens between several Atoll users. When you run Atoll and open a radio access technology document (GSM or UMTS, for example), Atoll consumes one Atoll Platform licence and one licence of the document’s radio access technology. In addition, one Measurements licence and one Microwave Radio Links licence are also consumed even if the document does not contain any measurements or microwave links. You can block access to the Measurements and Microwave Radio Links licence consumption by adding the following lines in the Atoll.ini file: [License] Measures = 0 MW = 0 Where, Measures and MW respectively refer to the Measurements and Microwave Radio Links module licences. Setting these options to 0 means that you will not have access to the Measurements or the Microwave Radio Links modules. This option is particularly useful in giving different licence rights to users. For example, you could have a group of users working on cellular radio technologies, GSM or UMTS, that uses measurements data, and another group of users working on microwave links projects. In this case, you could create two Atoll.ini files, the first not allowing the first group to use the Microwave Radio Links licence, and the second not allowing the second group to use the Measurements module. This way, the first group of users can work on GSM and UMTS Atoll documents with measurements without consuming Microwave Radio Links licences which will be reserved to the second group. You can also block access to the radio technology licences for users or user groups working on microwave links only. 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 GSM GPRS EDGE UMTS HSPA CDMA2000 TD-SCDMA WiMAX 802.16e LTE Microwave Radio Links Measurements Add GSM = 0 UMTS = 0 CDMA = 0 TD-SCDMA = 0 WiMAX = 0 LTE = 0 MW = 0 Measures = 0

You can also block access to GSM, UMTS, or LTE radio access technologies in 3GPP Multi-RAT documents using these options.

12.1.4.3 Blocking Access to ACP and AFP Modules
You can block access to the ACP and AFP licences for users or user groups. To block access to ACP or AFP modules, add the corresponding lines in the [License] section of the Atoll.ini file:

182

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 12: Initialisation Files

ACP_GSM = 0 ACP_UMTS = 0 ACP_WiMAX = 0 ACP_LTE = 0 GSM_AFP = 0 WiMAX_AFP = 0 LTE_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 both must not be set to 0.

12.1.4.4 Changing the NetHASP Licence Manager Idle Time Setting
The floating licence manager has an idle time parameter with 10 minutes as default value. Atoll sessions consuming 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.

12.1.5 ACP Options
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.

12.1.5.1 Specifying the Location of the Acp.ini File
By default, Atoll ACP uses the global acp.ini file, located in the installation directory of Atoll. You can set an option in 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 an other location, add the following line to the atoll.ini file: [ACP] iniFile = /path/to/the/ACP.ini

12.1.6 Database Options
12.1.6.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.

183

Atoll 3.1.0 Administrator Manual Chapter 12: Initialisation Files

© Forsk 2011

12.1.6.2 Setting an Automatic 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, you have to add the following line in the Atoll.ini file: [Database] IntegrityChecker = 1 If this option is set to 1, Atoll performs SELECT filters in the database to guarnatee data integrity.This feature enables selection directly in the database in order to avoid integrity problems in the future.

12.1.6.3 Modifying the Default Database Connection Timeout
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, add the following lines in the Atoll.ini file: [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.

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

12.1.6.5 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] ChangeKclutterSign = 1 ChangeKclutterSign is set to 0 by default.

12.1.6.6 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

184

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 12: Initialisation Files

• •

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.

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

12.1.6.8 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 may cause data integrity problems), add the following lines in the Atoll.ini file: [MajorVersionChange] EnablePartialRefreshInMigration = 1 EnablePartialRefreshInMigration is set to 0 by default.

12.1.7 Common Calculation Options
12.1.7.1 Setting the Antenna Patterns Modelling Method
In order to set the modelling method for antenna patterns, the Atoll.ini file may contain following information: [Antenna] AngleCalculation = 2000 or 3000 Catalog Vertical Diagram Orientation = 0 or angle value InterpolatePatternEvenIfOnlyOneDiagram = 0 or 1 The values 2000 and 3000 are only valid for Forsk’s propagation model library, i.e., the propagation models available with Atoll by default. Setting AngleCalculation = 2000 makes the propagation models calculate "unmasked" path losses, i.e., path losses without considering the transmitter antenna patterns. Setting AngleCalculation = 3000 makes the propagation models calculate the angles of incidence to each pixel instead of path loss. Catalog Vertical Diagram Orientation is only a display option. It enables representing the antenna’s vertical diagram with a certain orientation. Adjusting Catalog Vertical Diagram Orientation= 90, for example, will rotate the vertical diagram by 90° in clock-wise direction. 0 corresponds to the default display. The InterpolatePatternEvenIfOnlyOneDiagram can be used to change the way Atoll interpolates antenna attenuation patterns for antennas with only one diagramme available, vertical or horizontal. With InterpolatePatternEvenIfOnlyOneDiagram = 0 (default, new method), Atoll uses the one available diagramme for both vertical and horizontal planes. With InterpolatePatternEvenIfOnlyOneDiagram = 1 (previous method), Atoll uses the available diagramme for the plane to which it corresponds, vertical or horizontal, and an isotropic attenuation diagramme (a 0 dB circular attenuation pattern) for the plane for which no diagramme is available.

12.1.7.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:

185

Atoll 3.1.0 Administrator Manual Chapter 12: Initialisation Files

© Forsk 2011

[Studies] AutoLock = 0 This setting is read by Atoll without Atoll having to be restarted.

12.1.7.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 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 dialogues 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 dialogues, 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 in Calculations" on page 195.

12.1.7.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).

12.1.7.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 dialogues 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.

12.1.7.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:

186

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 12: Initialisation Files

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

12.1.7.7 Disabling the Temporary Local Storage of Path Loss Files
If you are working with a shared path loss folder, Atoll automatically copies the path loss files that it needs during calculations to the local computer for improving performance. This feature improves the performance many times if the shared path loss folder is located across a network because accessing a local hard disk is much faster than accessing a file over the network. However, you can instruct Atoll not to store these temporary copies of the path loss results in the system’s temporary files folder by adding the following lines in the Atoll.ini file: [PathLosses] PrivateCopies = 0 • • 0: Temporary copies disabled 1: Temporary copies enabled (default)

Use this option only if you are critically short of hard disk space. However, note that disabling temporary local copies might decrease the performance as it adds file access delays over the network.

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

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

12.1.7.10 Warning About Prediction Vailidity 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.

12.1.7.11 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 in the Atoll.ini file:

187

Atoll 3.1.0 Administrator Manual Chapter 12: Initialisation Files

© Forsk 2011

[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

12.1.7.12 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 dialogue. If you create a new coverage prediction, Atoll reads the default resolution from the Predictions folder’s properties 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 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. In this way, when you create coverage predictions without defining resolutions for them, you can modify the default resolution of the Predictions folder’s properties and, therefore, change the display resolution for all the coverage predictions, new or existing. To return to the normal working, you can either remove the lines from the Atoll.ini file, or set SpecifyResolutionAfterComputation to 1.

12.1.7.13 Allocating Neighbours Based on Distance Only
If you want Atoll to allocate neighbours, and to calculate the neighbour importance, based on the distance criterion only, add the following lines in the Atoll.ini file: [Neighbours] CoefDistanceOnly = 1 CoefDistanceOnly is set to 0 by default. With CoefDistanceOnly = 1 neighbours are selected for distance reasons only and other reasons (coverage, co-site, etc.) are not considered. The neighbour importance depends on the distance from the reference transmitter and it is calculated as follows: IF = Min(Di) + Delta(Di)(Di) Using the default values of Min(Di) and Max(Di), we have: IF = 1% + 9%(Di)

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

188

AT310_AM_E2

Atoll 3.1.0 Administrator Manual Chapter 12: Initialisation Files

12.1.7.15 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 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, Atoll will use actual number of available threads. 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.

12.1.7.16 Disabling Parallel Calculation of Monte Carlo Simulations
For UMTS HSPA and CDMA2000 1xRTT 1xEV-DO documents, Atoll can perform multi-thread calculations of Monte Carlo simulations. If you want to disable the parallel calculation, add the following lines to the Atoll.ini file: [CDMA] ParallelSimulations = 0 ParallelSimulations is set to 1 by default. The Generator Initialisation must be set to 0 in order for the simulations to be calculated parallely.

The parallel calculation of Monte Carlo simulations in TD-SCDMA, WiMAX 802.16d, WiMAX 802.16e, and LTE documents is disabled by default. It shoud not be enabled in TD-SCDMA documents.

12.1.7.17 Performing Calculations in Read-Only Documents
By default, when you open a read-only Atoll document, it is not possible to run calculations in it. If you want to run calculations in read-only documents, you will have to 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.

12.1.7.18 Identifying Transmitter, Repeater, and Remote Antenna Coverage Areas
In GSM GPRS EDGE, UMTS HSPA, LTE, and WiMAX documents, you can create a "Coverage by Aerial" signal level coverage prediction for separate coverage areas of transmitters and their repeaters and remote antennas.

189

add the following lines in the Atoll.21 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.ini file: [CDMA] PredictSimuMemorySize = 1 PredictSimuMemorySize is set to 0 by default which means the feature is not active. real values are rounded up or down to their nearest integer values. using the previous method.ini file: [Studies] AerialStudy = 1 12.1. Estimated memory size within the green region means low consumption.1.0. 190 .Atoll 3.ini file: [CoPlanning] LinkedPredictionsComputationMode = Parallelized LinkedPredictionsComputationMode is set to Serialized by default. add the following lines in the Atoll.7.1.8. from Atoll2. which means the path loss matrices and unlocked coverage predictions in the current and linked documents are calculated in serial.1.8. add the following lines in the Atoll.0 onwards. 12. 12. This option only works with the propagation models available with Atoll by default. add the following lines in the Atoll.8 m was rounded to 98 m.1.7. 98. or select the command from a context menu in the current document. For example.19 Changing the Rounding Method Used for Profile Extraction Before Atoll2.ini file: [FskPropagModels] OptimOnNoData = 1 By default. OptimOnNoData is set to 0. However.7. 12. and within the red region means very high consumption.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 In order to make this coverage prediction available in Atoll.20 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 dialogue. add the following lines in the Atoll.23 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. within the orange region means high consumption. in which case the simulations might generate an out of memory error and not complete. press F7. within the yellow region means medium consumption.1. it is rounded to 99 m.ini file: [CoPlanning] ComputeLinkedPredictions = 0 ComputeLinkedPredictions is set to 1 by default.7.7. To activate the memory estimation feature. 12.22 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. real values for altitudes read from the DTM files were rounded down to their integer values. If you want to switch back to the previous method. If you want Atoll to calculate only the unlocked coverage predictions in the Predictions folder of the current document. add the following lines in the Atoll. and not in the linked Predictions folder from another document. but with the new method.ini file: [Calculations] RoundAltitudes = 0 RoundAltitudes is set to 1 by default.

12. Calculations are carried out starting with the current document in the order of the coverage predictions in the Predictions folder. and LTE. 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.ini file: [Studies] EIRPfromMaxPower = 1 EIRPfromMaxPower is set to 0 by default. RandomTotalUsers is set to 1.1.8.26 Calculating EIRP from Max Power in Signal Level Predictions Atoll calculates the EIRP from the pilot power in UMTS and CDMA2000. i.8 GSM GPRS EDGE Options 12.1. mobiles are generated in each simulation following a Poisson distribution. This option applies to Coverage by Transmitter. CDMA2000.ini file: [Features] IM_TRAFFIC_OVERLAP = 1 12. Coverage by Signal Level. add the following lines in the Atoll.7.2 Setting the Default BSIC Format You can set the default BSIC format to be used by Atoll by adding these lines in the Atoll. However. Atoll does not consider the overlapping to improve performance. add the following lines in the Atoll.8.0 Administrator Manual Chapter 12: Initialisation Files If you set LinkedPredictionsComputationMode to any other value. 12.1 Considering Overlapping Zones for IM Calculation Based on Traffic When calculating interference matrices based on traffic.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. If you wish to calculate the EIRP from the Max Power values when calculating signal level-based coverage predictions. overlapping between coverage areas of different transmitters is taken into account when the option "Best Server" is selected and a positive margin is defined.e. This means that there are small variations in the number of randomly distributed mobiles from one simulation to another. and reference signal power in LTE.1. to have the same number of mobiles generated in each simulation of a group. add the following lines in the Atoll. 12. Atoll makes calculated neighbour relations symmetrical even if one of the transmitter in the neighbour relation is located outside the Focus Zone.1. To disable this type of distribution. the calculations are performed in parallel but without being managed by a task list. For interference matrices calculation based on "All" the servers (not Best Server).7. you can instruct Atoll to consider the overlapping during these calculations as well by adding the following lines in the Atoll..1. 191 . and Overlapping Zones predictions in UMTS. 12. When you run an automatic neighbour allocation with the Force Symmetry option selected.ini file: [Simulation] RandomTotalUsers = 0 By default.25 Using Poisson Distribution in Monte-Carlo Simulations By default.24 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).1.AT310_AM_E2 Atoll 3.1.ini file: [Neighbours] ForceSymmetryInFocusZone = 1 ForceSymmetryInFocusZone is set to 0 by default.7.

Atoll uses the "@" character to identify the multi-band transmitters.ini file: [Studies] MultiBandManagement = 1 MultiBandManagement is set to 0 by default. The First Value method was the default method in earlier versions of Atoll which allowed multiple interference matrix import. remote antennas. the worst case value in all the active interference matrices is taken into consideration. • • Worst Case Method: For each interference matrix relationship. In the Multi-Band Propagation Parameters table and in the database. First Value Method: For each interference matrix relationship.8.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 12.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. 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". which is the worst case one. and through the Subcells > Multi-Band Propagation Parameters command in the context menu of the Transmitters folder.1. 1 refers to the default method. If this option is set to 1. the first IM is the one at the top.1. and you have the "@" character in the names of repeaters. If you do not want Atoll to automatically delete such records when opening the document from a database. when a document is opened from a database or refreshed.ini file: [AFP] WorstCaseIM_FskAfp = 0 or 1 This option is valid for Forsk’s AFP. Atoll deletes these records when opening the document from a database. 12. which improves Atoll’s performance.8.ini file: [Refresh] TRXIntegrity = 1 By default. Atoll will use the maximum range parameter and set it to the default value of 35 km.8.ini file: 192 . i. this option is considered to be set to 0. Setting this value to 0 will instruct the AFP to use the second method.Atoll 3. Atoll updates the values of the fields "Number of TRXs" and "Channels" of the Transmitters table.5 Disabling the Maximum Range Parameter The maximum cell range parameter (System tab of the Predictions folder’s properties dialogue) in GSM GPRS EDGE documents is used by default and set to 35 km. if you are working on a document with multi-band transmitters.8. or subcells without a donor/main transmitter. 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 transmitter’s properties dialogue.1. you have to sett the following option in the Atoll. add the following lines in the Atoll.1. This option should not be used with Sybase databases. the first value found in any active interference matrix is taken into consideration. with the values from the TRGs and the TRXs tables respectively.3 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. 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 Explorer window. To turn on the multi-band modelling feature. 12. add the following lines to the Atoll.6 Enabling the Support for Multi-band Transmitters Atoll is capable of modelling transmitters with subcells (TRX groups) belonging to different frequency domains. Therefore. 12.1.e.

9 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.10 Setting the Transmission Diversity Gain If a subcell is using transmission diversity. MAIO. 12. The signal level received from the serving transmitter must be higher than the minimum reception threshold ( T Rec ) for its HSC layer. Modifying values in one table might cause inconsistencies between the two tables in some cases.8. CanEditTRXInfoAtTXLevel is set to 1 by default. You can use the 2nd strategy by adding the following lines in the Atoll.1. you have to sett the following option in the Atoll. MultiBandManagement is set to 0. Setting SimpleUserGUI to 1 hides the Interference Matrices. the air-combining gain of 3 dB is applied to all the received signal levels.e.ini file: [Studies] CleanMultiCellManagement = 1 CleanMultiCellManagement is set to 0 by default. You can make these redundant fields uneditable in the Transmitters table by adding the following lines in the Atoll. during calculations. The default strategy is the 1st one. which means that the fields are editable. 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 you want Atoll to automatically delete such records when opening the document from a database.8. HCS If there are two HCS layers with the same priority: • HCS 1st strategy: The serving transmitter is the one for which the difference between the received signal level and T Rec HCS is the highest. Where.8. and Advanced tabs.ini file: [GSM] CanEditTRXInfoAtTXLevel = 0 The redundant fields in the Transmitters table are the BCCH and the Number of TRXs fields. 12.1.1. 12.0 Administrator Manual Chapter 12: Initialisation Files [Studies] RemoveBadMultiCells = 0 RemoveBadMultiCells is set to 1 by default. Atoll does not automatically delete such records. i. wanted (C) as well as interfering (I).ini file: [Studies] 2GTxDiversityGain = X 193 .AT310_AM_E2 Atoll 3. You can modify the default value of 3 dB by adding the following lines in the Atoll.1.8. 12.1.. If you are not working with multi-band transmitters.ini file: [Studies] UseThresholdForSameLayerPriorities = 0 UseThresholdForSameLayerPriorities is set to 1 by default. 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.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.ini file: [AFP] SimpleUserGUI = 1 SimpleUserGUI is set to 0 by default.8 Hiding Advanced AFP Parameters You can hide the advanced parameters from the Atoll AFP properties dialogue by adding the following lines in the Atoll.

11 Adding Grouped HCS Servers Option in Calculations By default..ini file: [3GCells] NoSuffixIfUniqueCarrier = 0 or 1 194 . if the interfered subcell uses the GSM900 band and a potential interferer uses the GSM1800 band. Setting FirstTRXIndex to any other value has the same effect as setting it to 1. add the following lines in the Atoll. then this potential interferer is ignored. To do this.1. the first carrier is also the last carrier in the global parameters.8.ini file: [IM] FilterByFrequencyBands = 0 FilterByFrequencyBands is set to 1 by default.8. 12.9 UMTS HSPA. add the following lines in the Atoll. 12. which corresponds to the default value ranges. 12.8.9. and the two bands do not overlap.ini file: [GSM] FirstTRXIndex = 1 FirstTRXIndex is set to 0 by default. the Grouped HCS Servers option is not available in the list of choices for Server in coverage predictions. 12.1. For example. If you wish to extend this range to 30 dB and -134 dBm for the C/I and reception thresholds respectively.1.12 Deactivating Frequency Band Filtering in IM Calculation When calculating interference matrices. add the following lines in the Atoll.1.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.ini file: [GSM] TRXIndexHidden = 1 TRXIndexHidden is set to 0 by default.8.1. CDMA2000.ini file: [GSM] WideRangeSubcellThresholds = 1 WideRangeSubcellThresholds is set to 0 by default. traffic capture. add the following lines in the atoll. TRXs are indexed by Atoll starting at index 0. i.Atoll 3.1. Any interferer whose assigned frequency band overlaps with the frequency band assigned to the interfered subcell is not filtered. To make this option available. 12.ini file: [TMP] ExtraServZone = 1 12.e. If you wish to start the indexing at 1. add the following lines in the Atoll. and TD-SCDMA Options 12. You can deactivate this filtering by adding the following lines in the Atoll. 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.15 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 rception threshold allows values from -116 to 50 dBm.13 Starting TRX Indexes at 1 By default.14 Hiding the TRX Index If you wish to hide the TRX index column.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 Where X is the value of the air-combining gain in dB.1.8.1. and interference matrix calculations. Atoll filters potential interferers based on the frequency bands used by the interfered and interfering subcells.

1. you can choose whether to perform intra-cell interference calculations based on total cell power (Ptot) or maximum cell power (Pmax). If you wish. and DL and UL Eb/Nt based on the respective standard deviations. Atoll will: • • • • Not display the number of simultaneous HSDPA users in the simulation results.1. you can deactivate the macro-diversity gain calculation for the pilot Ec/Io only by adding the following lines in the Atoll. Display the instantaneous throughput per site in the Sites tab of the simulation results. SiteN_X. and site in simulation results. You can instruct Atoll to use maximum power in stead by adding the following lines in the Atoll.ini file: [CDMA] AddPilotSHOGain = 0 AddPilotSHOGain is set to 1 by default. This will result in cell names which will be same as the transmitter names.1. To do this.1. Display the MUG table in the cell properties. Atoll performs this calculation based on the total power. Place a certain part of HSDPA users in a waiting queue during simulations.ini file: [CDMA] PmaxInIntraItf = 1 195 . SiteN_X(C). By default. Atoll will: • • • • Display the number of simultaneous HSDPA users in the simulation results. meaning that C is unique.9.0 Administrator Manual Chapter 12: Initialisation Files This is set to 0 by default. If you choose to display the peak HSDPA throughputs. The HSDPA throughput for each user will be calculated by taking into account the MUG corresponding to the current number of connected HSDPA users. enter the following lines in the Atoll.ini file: [Shadowing] WithSHOGain = 0 WithSHOGain is set to 1 by default.AT310_AM_E2 Atoll 3. which means that cell names will follow the normal convention of Atoll. HSDPA resource scheduling will not be carried out. Display the instantaneous gross and instantaneous application level throughputs per mobile and per cell in the simulation results. 12. To do this.2 Disabling Macro-diversity (SHO) Gains in Calculations In UMTS HSPA and CDMA2000 documents.ini file: [CDMA] HSDPAAvgSimuResults = 1 HSDPAAvgSimuResults = 0 by default. Input from this are used to calculate the peak gross throughput per cell when the scheduling algorithm is "Proportional Fair". then this option can be set to 1.9. 12. If there is only one carrier.3 Calculating and Displaying Peak or Instantaneous HSDPA Throughput In UMTS HSPA documents. macro-diversity gains are calculated for pilot Ec/Io. you can choose to display and work with either peak values or instantaneous values of the HSDPA throughputs per mobile.4 Setting the Power to Use for Intra-cell Interference in HSDPA In HSDPA prediction studies. In Average Simulation results.9. you can add the following lines in the Atoll. Display the peak gross and peak application level throughputs per mobile and per cell in the simulation results. Display the average HSDPA throughput per user in the Cells tab of the simulation results. 12.ini file: [CDMA] HSDPAThroughputPeak = 0 or 1 • • 0: Instantaneous throughput (Default) 1: Peak throughput If you choose to display the instantaneous HSDPA throughputs. the average HSDPA throughput per user can be calculated excluding the simulations where no HSDPA users were served. You can deactivate the calculation and use of macro-diversity gains in all the calculations by adding the following lines in the Atoll. cell.

the HS-PDSCH CQI will be calculated using the formula: EC EC ( CQI ) HS – PDSCH = ( CQI ) pilot –  -----. 12.1.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). Otherwise. it will no longer be considered in the next iterations.9.ini file: [CDMA] CQIDeltaWithPower = 0 or 1 CQIDeltaWithPower is set to 1 by default.9.Atoll 3.ini file: [CDMA] UseStudyCnxProba = 1 MinUsersPerBin = X This coverage prediction study is available in the list of prediction studies if UseStudyCnxProba is set to 1. To modify the default value. The default value of this option is 5.  N T pilot  N T HS – PDSCH If you set CQIDeltaWithPower to 1. %Pilot Finger is related to the CPICH physical channel only and models the loss of energy in the CPICH signal due to multipath. the HS-PDSCH CQI will be calculated using the formula: ( CQI ) HS – PDSCH = ( CQI ) pilot – P pilot + P HS – PDSCH The above equations are in dB.1. 12. 12. You can instruct Atoll to use the Orthogonality Factor in the calculation of pilot EC/NT in HSDPA instead of %Pilot Finger by adding the following lines in the Atoll.9.1.1.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 • • 0: Intra-cell interference calculation based on total power (Default) 1: Intra-cell interference calculation based on maximum power 12.7 Enabling Orthogonality Factor in Pilot EC/NT Calcaultion in HSDPA %Pilot Finger and the Orthogonality Factor model two different effects on the CPICH quality.1.ini file: [CDMA] MaxRejections = X If a mobile is rejected X number of times. you can select the formula used for calculating HS-PDSCH CQI in Atoll by adding the following lines in the Atoll. Refer to the Technical Reference Guide for more details. enter the following lines in the Atoll.6 Setting the Calculation Method for HS-PDSCH CQI If you choose the “CQI based on CPICH quality” option in Global Parameters.ini file: [CDMA] OrthoInCPICH = 1 12.5 Enabling Coverage Predictions of Connection Probabilities You can perform coverage prediction studies for connection probabilities in UMTS HSPA documents by adding the following lines in the Atoll. The Orthogonality Factor is related to the correlation between the CPICH physical channel and other intra-cell physical channels.9.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.1.ini file: [CDMA] HSDPAMaxRejections = X 196 . 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. +  -----.9. If you set CQIDeltaWithPower to 0.

The step of rasterization means the size of the bin used to approximate the vector shape with bins.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. but the density might be different since the surface area has changed (Number of users = User Density x Area). You can set it to a higher value if you observe performance degradation. If the coordinates of the vector polygons are not accurate.9. which perform the conversion from vector to raster.11 Setting Precision of the Rasterization Process During Monte Carlo simulations.1: Rasterization Process The primitive libraries. 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. at the mobile location. If you want Atoll to increase the precision of the rasterization process for hotspots in your network.1. but only for small polygons which are defined by the options “SurfRatio” or “MaximumSurf”.ini file: [CDMA] CutOffSimu = X Where. 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.1. The vector polygon and the raster bin have the same traffic density in the following figure. nearly all. Improve = 0 means that the normal rasterization method will be used for all polygons. deal in terms of float values for the x and y coordinates of the vector polygons. Setting this option to 1 implies that this algorithm will not be used globally for all polygons.ini file: [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 rasterization method for small polygons. 12. The figure below depicts this effect for a vector polygon which is just slightly larger than 1 raster pixel. Figure 12. You can add the following lines in the Atoll. it is possible that the raster pixel found from the vector polygon will be shifted 1 bin to the right or to the left. Precision = 1 (by default) means that the rasterization resolution (step) used by the algorithm for small polygons is 1 metre. Since these are float values. calculations performed on each mobile only take into account the cells whose received power. cases.1. this accuracy might not be enough for highly precise vector polygons defining traffic hotspots. However.0 Administrator Manual Chapter 12: Initialisation Files Where X is the number of times an HSDPA mobile should be rejected to be considered permanently rejected for the simulation. 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. During Monte Carlo simulations. • 197 . The accuracy of this conversion from vectors to raster is high enough for most.9. X is the offset value in dBs. Such a rasterization means that the number of users in the vector remains correct. 12.AT310_AM_E2 Atoll 3.

and will be rasterized using the accurate algorithm. If you set PFSchedulerCQIFactor = 0. a polygon will be considered small. add the following lines in the Atoll.0. 12.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 If you set Precision = 1.9. 198 . To display the Ec/I0 from the best server for the rejected mobiles. The default value of this option is 30.15 Switching Back to the Old Best Server Determination Method Before Atoll 2. PFSchedulerCQIFactor = 50 by default. To switch back to this best server determination method. • 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.1. Atoll will still keep 5 m as the normal raster bin size.12 Defining the Number of Iterations Before Downgrading You can set the number of iterations that Atoll should carry out before starting the downgrading.9. which represents the proportional fair scheduler weight.1.8. m.ini file: [CDMA] MultiBandSimu = 0 MultiBandSimu is set to 1 by default.13 Adjusting the Working of the Proportional Fair Scheduler In UMTS HSPA documents.14 Displaying Ec/I0 of Rejected Mobiles in Simulation Results In UMTS and CDMA simulation results. you can set the SurfRatio to 0.ini file: [CDMA] DisplayEcIoOfRejected = 1 DisplayEcIoOfRejected is set to 0 by default.1.Atoll 3. If you set PFSchedulerCQIFactor = 100. if either the ratio of its surface area to the surface area of the normal raster bin is equal to or less than SurfRatio. the Ec/I0 AS1 column in the Mobiles tab may list the Ec/I0 values from the best server for all the mobiles. the proportional fair scheduler functions like the Round Robin scheduler. 12.ini file: [CDMA] PFSchedulerCQIFactor = X Where X is a number between 0 and 100.9. add the following lines in the Atoll. 12. So.ini file: [CDMA] IterBeforeDown = X Where X is the integer number of iterations. To modify the default value. connected or rejected. • 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. The normal raster bin size in an Atoll document is the finest resolution among the geographic data available in the document.1. the proportional fair scheduler functions like the Max C/I scheduler. enter the following lines in the Atoll. one with a 20 m resolution and the other with a 5 m resolution. the performance (calculation speed) can be considerably decreased depending on the size of your network. 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. 12.1. and you remove the 5 m one from your document. It is recommended to set a higher value for the Precision option. If your Atoll document contains two geographic data files.9. or if its surface area is less than MaximumSurf. If you want to use just the MaximumSurf option. you can adjust how the proportional fair scheduler functions by adding the following lines in the Atoll.

17 Selecting SC and PN Offset Allocation Strategies Available in the GUI In the Atoll. 4 The allocation strategies 1. add the following lines in the Atoll.9.9. 3.1.16 Displaying Automatic Allocation Cost Values You can display the cost values calculated by Atoll for different relations when allocating scrambling codes and PN offsets.1. add the following lines in the Atoll. 12.ini file: [CDMA] CodeStrategies = 1.ini file: [PSC] ConstantStep = 1 ConstantStep is set to 0 by default. 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 dialogue.AT310_AM_E2 Atoll 3.20 Setting the Maximum AS Size for SC Interference Prediction You can set the maximum active set size to a fixed number of transmitters for the scrambling code interference coverage prediction by adding the following lines in the Atoll.9. To display cost values.ini file: [PSC] DisplayCostValues = 1 DisplayCostValues is set to 0 by default.19 Compressed Mode: Restricting Inter-carrier and Inter-technology Neighbour Allocation You can prevent Atoll from allocating inter-carrier and inter-technology neighbours to cells located on sites whose equipment does not support compressed mode. 12.0 Administrator Manual Chapter 12: Initialisation Files 12. add the following lines in the Atoll.ini file: [Neighbours] CompressModeEval = 1 CompressModeEval is set to 0 by default.ini file. 2. 12.ini file: 199 .1. 2.1. To select the allocation strategies.18 Defining a Fixed Interval Between Scrambling Codes You can define a fixed interval between scrambling codes assigned to cells on a same site when the allocation is based on a distributed strategy (Distributed per Cell or Distributed per Site).9.9. To apply the defined interval.1. 3. by adding the following lines in the Atoll. and 4 correspond to the following: • In UMTS: • 1: Clustered • 2: Distributed per Cell • 3: One Cluster per Site • 4: Distributed per Site In TD-SCDMA: • 1: Clustered • 2: Distributed per Cell • 3: One SYNC_DL Code per Site • 4: Distributed per Site In CDMA2000: • 1: PN Offset per Cell • 2: Adjacent PN-Clusters per Site • 3: Distributed PN-Clusters per Site • • 12.1.

the Total Number of Subcarriers changes into a combo box with the following five values: 128. you can activate the Uplink Total Losses and Minimum Uplink Total Losses display options in the Coverage by Signal Level prediction by adding the following lines in the Atoll.e. 1024. you will get the same results in the coverage prediction as the SC Interference tab in the point analysis. 256.1. Total. Subchannel Groups (Segment 1). In the Permutation Zones table. This may cause unnecessary rejection of some HSUPA users in very low traffic cases.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. Number of Data Subcarriers. the first DL PUSC permutation zone cannot be deactivated.1. and Data.16d: • • Under Channel Configuration in the Global Parameters tab of the Transmitters folder’s properties dialogue: Number of Subchannels per Channel and Number of Subcarriers per Channel. which means that all the parameters are modifiable.22 Setting the Maximum UL Reuse Factor for HSUPA Users’ Noise Rise Estimation In UMTS HSPA simulations. 512.10.ini file: [WiMAX] ModifiableIEEEParams = 0 By default.ini file: [OFDM] 200 . ModifiableIEEEParams is set to 1. and Subchannel Groups (Segment 2) for FFT sizes < 1000. In the Frame Configurations table and in the General tab of the properties dialogue of the frame configurations: Number of Preamble Subcarriers.1.10.ini file: [Studies] UplinkLosses = 1 UplinkLosses is set to 0 by default. 802. In the Frame Configurations table. Uplink total losses are calculated from the downlink total losses by replacing the downlink transmitter losses by uplink transmitter losses. it means that the following parameters will be unmodifiable in the GUI: • 802. In the Permutation Zones table: Subchannel Groups (Segment 0). Atoll assumes a constant uplink reuse factor for estimating the maximum available noise rise per HSUPA user.10 WiMAX and LTE Options 12. add the following lines in the Atoll.ini file: [UMTSSimus] MaxReuseFactor = X MaxReuseFactor is set to 5 by default.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 [Studies] SCActivesetMaxSize = X Where X is the maximum number of transmitters in the active set. i. Used.1 Blocking Access to IEEE Parameters in WiMAX You can disallow modification of the parameters that come from the IEEE specifications.1.21 Displaying Uplink Total Losses in Coverage by Signal Level In UMTS and CDMA documents.16e: • • • • • 12. If you set SCActivesetMaxSize = 10. 12. 12. When you set ModifiableIEEEParams to 0. In the Permutation Zones table: Number of Used Subcarriers. 12.1. and are not supposed to be changed. and Number of Subchannels per Channel. by adding the following lines in the Atoll.Atoll 3.1. You can set an upper limit for the uplink reuse factor by adding the following lines in the Atoll.9. 2048.

7 Excluding Cyclic Prefix Energy in WiMAX Signal Level Calculation The useful signal level calculation may exclude the energy corresponding to the cyclic prefix part of the total symbol duration. If desired. SS & PBCH per subcarrier and PDCCH & PDSCH per subcarrier are not available options in a point analysis.ini file: [WiMAX] MultiAntennaInterference = 1 MultiAntennaInterference is set to 0 by default. When the DisplaySignalsPerSCInPtA option is set to "0" or is absent.10.. interference levels are calculated for the total symbol durations. Independant of the option. you must add the following lines in the Atoll.1. including the energy useful symbol duration and the cyclic prefix energy. When UseCommonBearersOnly is set to 1. interference levels are calculated for the total symbol durations. and RS per subcarrier. excluding the energy corresponding to the cyclic prefix part of the total symbol duration. However. This option affects the interference calculation in C/(I+N).5 Enabling Multi-antenna Interference Calculation in WiMAX In case of more than one antenna being used at an interferer. i.10.1.3 Disabling Multi-antenna Interference Calculation in LTE If more than one antenna is being used at an interferer. you must add the following lines in the Atoll.10. Interference calculated for RSSI and RSRQ always includes the effect of multiple antennas used by interferers. For this.ini file: [LTE] ExcludeCPFromUsefulPower = 0 ExcludeCPFromUsefulPower is set to 1 by default.0 Administrator Manual Chapter 12: Initialisation Files UseCommonBearersOnly = 1 UseCommonBearersOnly is set to 0 by default. 201 .ini file: [LTE] MultiAntennaInterference = 0 MultiAntennaInterference is set to 1 by default. If you wish to switch back to the old MIMO interference calculation method. including the energy useful symbol duration and the cyclic prefix energy.4 Enabling Display of Signals per Subcarrier Point Analysis in LTE By default a point analysis in LTE displays RS per channel. 12. 12.10.ini file: [LTE] DisplaySignalsPerSCInPtA=1 DisplaySignalsPerSCInPtA is set to 0 by default. 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.ini file: [WiMAX] ExcludeCPFromUsefulPower = 1 ExcludeCPFromUsefulPower is set to 0 by default.1.1.e. the interference from all the antennas is taken into account. you must add the following lines in the Atoll. the interference from all the antennas can be taken into account.10.AT310_AM_E2 Atoll 3. PDCCH & PDSCH per channel.1. you can include the cyclic prefix energy in the useful signal level calculation by adding the following lines in the Atoll. 12. SS & PBCH per channel. In order to do so. you can also use a point analysis to display SS & PBCH per subcarrier and PDCCH & PDSCH per subcarrier by adding the following lines in the Atoll.6 Including Cyclic Prefix Energy in LTE Signal Level Calculation The useful signal level calculation takes into account the useful symbol energy (Es). 12. 12. Independant of the option.1. hence taking into account only the energy belonging to the useful symbol duration. where interference from only one antenna was considered.

12.1.1. respectively. the preamble index collision is not verified between neighbours of a cell.8 Ignoring Inter-Neighbour Preamble Index Collision The automatic preamble index allocation algorithm in Atoll takes into account the possible collision of preamble indexes assigned to neighbours of a cell. With InterNeighbourIDCollisions = 1.12 Activating Basic Preamble Index/Physical Cell ID Allocation Preamble and physical cell ID allocation is now part of the WiMAX and LTE AFP modules.. the audit lists the cell pairs that are neighbours of a cell and are allocated the same preamble index.10.ini file: For activating the basic preamble index allocation: [License] Basic_WiMAX_AFP = 1 For activating the basic physical cell ID allocation: [License] 202 . zone permbases) distributes the allocated resources uniformly. The preamble index audit based on neighbours also takes this option into account. If you wish to deactivate the uniform distribution of resources.1.11 Deactivating Uniform Distribution of Resources By default. still use these no longer supported features by making them available in Atoll through the following options in the Atoll.e.10.1. The physical cell ID audit based on neighbours also takes this option into account. the audit lists the cell pairs that are neighbours of a cell and are allocated the same physical cell ID. If you want to disable this constraint. You can. If you want to disable this constraint.ini file: [LTE] InterNeighbourIDCollisions = 0 InterNeighbourIDCollisions is set to 1 by default.10. the physical cell ID collision is not verified between neighbours of a cell.1. you can rename the OPUSC permutation zone to PUSC UL by adding the following lines in the Atoll. i. 12.ini file: [WiMAX] InterNeighbourPICollisions = 0 InterNeighbourPICollisions is set to 1 by default. during automatic allocation of resources (channels. This means that Atoll tries to not allocate the same physical cell ID to two neighbours of a cell.10 Renaming OPUSC Zone to PUSC UL If you wish to work with two PUSC UL permutation zones. add the following lines in the Atoll. add the following lines in the Atoll. add the following lines in the Atoll.Atoll 3. however. allow Atoll to allocate the same physical cell ID to two neighbours of a cell. preamble indexes.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 12.ini file: [WiMAX] ReplaceOPUSCwithPUSCUL = 1 ReplaceOPUSCwithPUSCUL is set to 0 by default. 12.ini file: [OFDM] UniformIDDistribution = 0 UniformIDDistribution is set to 1 by default. physical cell IDs. The preamble index and physical cell ID allocation features that used to be available in the WiMAX and LTE modules are no longer supported. When InterNeighbourPICollisions = 0.9 Ignoring Inter-Neighbour Physical Cell ID Collision 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.e. allow Atoll to allocate the same preamble index to two neighbours of a cell.1. With InterNeighbourPICollisions = 1.10. 12.10. This means that Atoll tries to not allocate the same preamble index to two neighbours of a cell. i. When InterNeighbourIDCollisions = 0..

This produces inconsistent results in the 2 directions.ini file: [MWCalculations] UpdateOppositeHop = 1 UpdateOppositeHop is set to 0 by default.10. add the following lines in the Atoll.ini file: [OFDM] SecondNeighbours = 1 SecondNeighbours is set to 0 by default.1. 12.14 Setting PDCCH to 100% Loaded in LTE Interference Calculations By default. If you wish to set the PDCCH to 100% loaded.11.1 Excluding Near-field Interference from Calculations If you want to exclude the effect of near-field interference from interference calculations.1. 12. interference received from co-site sources is ignored. 12. i.ini file: [MWCalculations] 203 .11. and diversity-standby channels from interference calculations. only weight the interference from PDSCH by the downlink traffic load and not the interference from the PDCCH.ini file: [LTE] ApplyDLLoadOnPDCCHInterf = 0 ApplyDLLoadOnPDCCHInterf is set to 1 by default. The WiMAX AFP takes first order neighbours into account when allocating preamble indexes and downlink and uplink zone permbases. add the following lines in the Atoll.1. when a change is made on the A>>B link.0 Administrator Manual Chapter 12: Initialisation Files Basic_LTE_AFP = 1 12.11. 12. the downlink interference calculated from PDSCH and PDCCH is weighted by the downlink traffic loads of the interfering cells. changes in one direction automatically updated in the other direction. When IgnoreCositeInterference is set to 1..1. add the following lines in the Atoll.1.1. add the following lines in the Atoll. If you want the AFP to take both first and second order neighbours into account.AT310_AM_E2 Atoll 3. add the following lines in the Atoll. 12..11 Microwave Radio Links Options 12.2 Excluding Standby Channels from Interference Calculations If you want to exclude the standby.10. If you want to make the profile update real-time in both directions. i.1.11.3 Updating A>>B and B>>A Profiles in Real-time In the MW Analysis window’s Profile view.1.ini file: [MWCalculations] HSB_INTERFERER = 1 HSB_INTERFERER is set to 0 by default.e.13 Taking Second Order Neighbours into Account in the AFP The LTE AFP takes first order neighbours into account when allocating physical cell IDs.ini file: [MWCalculations] IgnoreCositeInterference = 1 IgnoreCositeInterference is set to 0 by default. add the following lines in the Atoll. it is not automatically taken into account in the B>>A direction in real time.e.4 Disabling Sheilding Factor on Wanted Signal at Receiver If you want to disable the use of the sheilding factor on the wanted signal at the receiver during interference calculations.

6 Defining Channel Number Prefix and Suffix for Display In the port definition dialogue. reports.1.1. 12.Scrambling Code Group pair (UMTS HSPA documents) PN Offset .ini file: [MWSubband] PrefixL = 11G_ SuffixL = Low PrefixU = 11G_ SuffixU = Up By default. 12. The default value of NumberOfTestMobileTransmitters is 7. and PrefixU are empty. 12. 12. 12. you can add the following lines in the Atoll. 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.1. you can define your own prefixes and suffixes for the display of these channel numbers.11.12.1.PN Offset Group pair (CDMA2000 1xRTT 1xEV-DO documents) You have to add the following lines in the Atoll.ini file: [TestMobileData] NumberOfTestMobileTransmitters = X Where X is the number of transmitters per drive test data path.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 . enter the following lines in the Atoll.12.Atoll 3. If you wish. You can change the number of transmitters per drive test data path by adding the following lines in the Atoll. and calculation results. add the following lines in the Atoll.2 Setting the Number of Transmitters per Drive Test Data Path By default. SuffixL. the sheilding factor is always taken into account when calculating interference.ini file: 204 .1. to display channels of the lower half-band of an 11 GHz frequency band as 11GHz_1_Low and those of the upper half-band as 11GHz_1_Up. PrefixL.ini file: [Compatibility] MWEquipment_CIMIN = 1 MWEquipment_CIMIN is set to 0 by default.12.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 ShieldingFactorOnWantedSignal = 0 ShieldingFactorOnWantedSignal is set to 1 by default.5 Using Old Min C/I Values If you wish to use Min C/I values defined or calculated in old versions of Atoll. and SuffixU = ’.ini file to display this information: [TestMobileData] ShowCoupleInfo = 1 Setting ShowCoupleInfo to 0 hides this information.BSIC pair (GSM GPRS EDGE documents) Scrambling Code .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.12 Measurement Options 12. On the transmitter side. For example.11. which means that the sheilding factor is taken into account at the receiver when calculating interference. channels belonging to the lower half-bands of any sub-band are displayed using their channel numbers and those belonging to the upper half-bands are displayed with their channel numbers suffixed with a prime (’). This option changes the display in Atoll but does not have any effect on the values stored in the ATL files and databases.1.1.

ini file in the Atoll installation directory. or (PN Offset. (BSIC.AT310_AM_E2 Atoll 3. You can define a different location for the acp. 12.ini file. such as [ACPTplGeneralPage]. SC Group).ini by preceding the line with a semi-colon (".ini file can be modified directly using the ACP .12. PN Offset Group) pair as the point. under ACP Automatic Cell Planning on the Setup Template tab.1. 12.1 Managing Preferences Some of the settings provided in the acp. 12.1.1.ini file until and unless you are absolutely sure of what you are doing.ini file: [ACP] iniFile = /path/to/the/ACP. and the scrambling codes are imported according to the numeric data type selected for the scrambling code column in the import dialogue. you can add the following lines in the Atoll. The ACP initialisation file is a powerful tool. In order for the ACP initialisation file to be used by Atoll. you should place the acp.ini file by setting the following option in the atoll. These settings are referred as "local settings.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.ini The following sections describe the options available in the acp. Column1 and Column2 are the titles of the two columns in the . 12.fmt files generated by the TEMS Investigation GSM tool contain a number of columns.") or with a hash mark ("#").12. To define which of these columns should be imported as the BCCH column and which one as the BSIC column in Atoll.0 Administrator Manual Chapter 12: Initialisation Files [TestMobileData] RecalcDist = 1 or 0 The default value of RecalcDist is 1.ini file.ini file: [TestMobileDataImportFmt] BCCHColumn = Column1 BSICColumn = Column2 Where." Local settings are the settings found in sections using the "Tpl" keyword. 205 . You should not modify any option in the acp.fmt file corresponding to the BCCH and the BSIC columns respectively.4 Defining the BCCH and BSIC Columns for FMT Import The . which means that Atoll will calculate the distance for each measurement point. It can be used to adjust the behaviour of the ACP.2.Automatic Cell Planning Properties dialogue. ACP either embeds these settings directly in the ATL document or in a user-defined acp. You can comment out any option in the acp. BCCH). The nearest serving cell is the one closest to the measurement point which has the same (Scrambling Code.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.

12 # The clutter classes that will constitute this zone 206 . The following option can be used to automatically create ACP custom zones from the hotspots in the Atoll project: zone.removeSiteCost=-5 12.antenna.cost=1 cost.0.0.2 Automatically Creating Custom Zones on the Optimisation Tab In the [ACPTplGeneralPage] section.type=0 # 0=off. 1=limt_to_max.1 Default Values on the Optimisation Tab In the [ACPTplGeneralPage] section.maxCost=50 cost. These settings redefined locally have precedence over the global settings.siteVisitCost=2 cost.1 cost.isSiteVisit=false cost.tilt.tilt. The settings in the acp.power.clutter=10.newSiteCost=10 cost.2 GUI Options In this section are the settings defining default values and defining certain aspects of the GUI configuration.name=MyClutterZone1 # The name of the zone (in this case from clutter) zone. 12.upgradeSiteCost=5 cost.isSiteVisit=true cost. zone.Atoll 3.etilt.ini file.Automatic Cell Planning Properties dialogue.isSiteVisit=true cost.Automatic Cell Planning Properties dialogue.2.azimuth.2. When using the acp. you can find the options used to set default values for the Optimisation tab. 2=apply_cost_to_change_plan cost.count=2 # The number of zones to be created. take precedence over the same settings defined in the global acp.cost=1 cost. defined using the ACP . 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.ini file.2.isSiteVisit=false cost.cost=0.1. you can also define any other settings even if they can not be set using the ACP .ini file are read when you start a new project to initialise the settings of the ACP.Automatic Cell Planning Properties dialogue.ini file to define options.2.2. 12.cost=0.cost=1 cost.etilt.antenna.power. and stored either in the Atoll project or a local acp.11.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: zone. These settings are local and are usually defined using Setup Template tab of the ACP .isSiteVisit=true cost. The following options can be used to set default values for the number of iterations and resolution: [ACPTplGeneralPage] nbIteration=100 resolution=50 Other options can be used to define the default values for calculating cost: cost.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 • • The local settings.azimuth. instead of using the ACP Automatic Cell Planning Properties dialogue.1 cost.

overlap.ecio. etc.cdma.autoPrediction=yes param.umts.minRxLevel=-120 param.shp # Absolute path to the SHP file.useSegmentation=1 param.umts.autoPrediction=yes param. GSM signal level.isShadowing=no param.coverage.coverage. WiMAX CINR.margin=10 param.): [ACPTplObjectivePage] param.margin=5 param.autoPrediction=yes param.wimax.ecio.isShadowing=no param.autoPrediction=yes param.wimax.1.cnir.cdma.autoPrediction=yes param.cdma.wimax.umts.minRxLevel=-120 param.isShadowing=no param.wimax.ecio.useFreqBand=1 param.autoPrediction=yes param.cellEdgeCov=0.bcch.lte.ecio. UMTS overlap.overlap.cellEdgeCov=0.autoPrediction=yes param. The following option is used to define the default value for traffic extraction resolution in metres: [ACPTplObjectivePage] traffic.minRxLevel=-105 param.gsm.minRxLevel=0 # 0=use defined TRG threshold.autoPrediction=yes param.ecio.cdma.overlap.overlap.overlap. WiMAX C/N.1.autoPrediction=yes param.75 param.gsm.wimax.rscp. 12.umts.gsm.isShadowing=no param.cdma.coverage.wimax.umts.75 param.75 param.umts.coverage.autoPrediction=yes param.1.extraction.75 param.margin=5 207 .cnir.2.3 Default Values on the Objectives Tab In the [ACPTplObjectivePage] section are the settings defining default values for the Objectives tab.75 param. UMTS RSCP.AT310_AM_E2 Atoll 3.wimax.cellEdgeCov=0.75 param.ecio.margin=10 param.cellEdgeCov=0.umts.wimax.gsm.2.rscp.overlap.overlap.coverage.file=c:\path\to\file.bcch.autoPrediction=yes param. in metres The following options are used to define the default values for the technology quality indicators (UMTS Ec/Io.rscp.overlap.lte.umts.isShadowing=no param.overlap.cdma.bcch.0 Administrator Manual Chapter 12: Initialisation Files zone.wimax.name=MyVectorZone2 # The name of the zone (in this case from SHP) zone.overlap.coverage.autoPrediction=yes param.cnir.cnir.cnir.wimax. GSM overlap.cellEdgeCov=0.resolution=50 # the traffic extraction resolution.overlap.75 param.wimax.isShadowing=no param.umts.cdma.cellEdgeCov=0.overlap.overlap.cdma.cdma.isShadowing=no param.gsm.margin=5 param. other=defined value param.overlap.gsm. LTE C/N.cellEdgeCov=0.

c.threshold=10 quality.quality=bcch objective.cn.name=GSM Coverage # Name of objective "0" defined. objective.coverage.cnir.operande=OR objective.conditions.conditions. or other zone idx objective.0.c.threshold=-85 quality.lte.cinr.threshold=-13 quality.umts.umts.0.threshold=20 quality.threshold=4 quality.rsrq.threshold=10 quality.coverage." a value of "0" means "<" (less than) and "1" means ">" (greater than).threshold=4 quality.bcch.cdma.minRxLevel=-105 param.threshold=-85 quality.ecio.lte. For the setting "objective.0.overlap.0.0.cdma.lte.wimax.0.lte.lte.umts.overlap.gsm. Others are available on the context menu used for creating new objectives.0.conditions.threshold=-12 quality.0. -1=focusZone.threshold=-85 quality.threshold=5 quality.ecio.autoPrediction=yes param.threshold=-85 quality.coverage.X.overlap.1.wimax.count=1 objective.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 param.isShadowing=no param.threshold=-85 quality. All objectives defined with the option "auto=yes" are automatically created during a new setup.target.cnir.threshold=-105 quality.cellEdgeCov=0.cn.conditions.overlap.cinr.overlap.overlap. objective.targetZone=-1 # -2=compZone.lte.threshold=-13 quality.0.cdma.Atoll 3.coverage.cnir.layer=gsm objective.75 param.rsrp.lte.threshold=-85 objective.conditions.lte.isShadowing=no param.weight=1 objective.coverage.auto=true objective.conditions.0.lte.threshold=-85 quality.operande. objective.lte.useSegmentation=1 The following options are used to define the default threshold for each objective rule: quality.lte.lte.isAbsoluteCoverage=yes 208 .threshold=20 quality.75 param.autoPrediction=yes param.cnir.0.wimax.wimax.lte.useFreqBand=1 param.threshold=-85 quality.lte.rscp.0.lte.rscp.X.count=14 # The total number of objectives to be defined.threshold=4 quality.gsm.cinr.0.wimax.cellEdgeCov=0.threshold=5 The following options are used to define the default objectives proposed by the ACP.lte.

conditions.conditions.name=GSM Cell Dominance # Name of objective "1" defined.isAbsoluteCoverage=yes objective.name=UMTS Soft Handover # Name of objective "5" defined.1.isAbsoluteCoverage=yes objective.conditions.target.conditions.5.0.1.5.0.operande=OR objective.1.3.5.layer=gsm objective.threshold=-85 objective.target.1.4.target.count=0 .3.4.AT310_AM_E2 Atoll 3.3.quality=overlap objective.0.2.0.operande=0 # "0" means "<" (less than) objective.operande=1 # "1" means ">" (greater than).conditions.absoluteCoverage=100 objective.operande=OR objective.0 Administrator Manual Chapter 12: Initialisation Files objective.quality=rscp objective.operande=AND objective..count=2 objective.conditions.quality=ecio objective.threshold=4 objective.count=2 objective.0.target.1. The following objective should be defined separately for each layer objective.name=UMTS Pilot Pollution # Name of objective "4" defined.3. objective.name=UMTS RSCP Coverage # Name of objective "2" defined.1.1.filter.threshold=-13 objective.auto=false objective.conditions.3.1.target.2.0.isAbsoluteCoverage=yes objective.layer=umts objective.conditions.name=UMTS EcIo # Name of objective "3" defined.5.2.0.auto=false objective.conditions.conditions.0.1.1.2.5.conditions.3. objective.conditions.absoluteCoverage=90 objective.4.0. objective.conditions.conditions.4.count=1 objective.4.conditions.quality=overlap objective.conditions.3.target.conditions.quality=overlap objective. objective. objective.0.layer=umts objective.quality=overlap 209 .layer=umts objective.conditions.4.0.1.conditions.0.1.4.2.4.conditions. objective.0.4.0.1.threshold=4 objective.count=1 objective.absoluteCoverage=100 objective.conditions.absoluteCoverage=100 objective.conditions.1.threshold=0 objective.conditions.target.conditions.conditions.layer=umts objective.conditions.operande=AND objective.0.1.1.conditions.3.0.conditions.2.count=1 objective.1.0.layer=gsm objective.1.operande=0 # "0" means "<" (less than) objective.0.4.conditions.

conditions.quality=coverage 210 .conditions.conditions.conditions.6.count=1 objective.1.0. objective.isAbsoluteCoverage=yes objective.conditions.0.count=1 objective.8.10.1.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 objective.threshold=-85 objective.8.10.operande=AND objective.9.1.0.0. objective.conditions.7.conditions.count=1 objective.6.0.conditions.threshold=10 objective.0.7.8.conditions.operande=0 objective.threshold=1 objective.target.5.7.0.quality=coverage objective.conditions.6.10.conditions.0.5.layer=wimax objective.6.operande=OR objective.9.conditions.conditions.conditions. objective.5.9.0.filters.layer=umts objective.5.Atoll 3.conditions.0.layer=lte objective.7.7.5.7.operande=1 # "1" means ">" (greater than) objective.9.5.quality=overlap objective.name=LTE RS CINR # Name of objective "9" defined.conditions.operande=0 # "0" means "<" (less than) objective.5.target.conditions.filters.layer=lte objective.operande=OR objective.8.6.9.conditions.0.conditions.quality=cinr objective.5.1.quality=rscp objective.count=1 objective.0.operande=1 # "1" means ">" (greater than) objective.threshold=-95 objective.conditions.conditions.conditions.conditions.name=CDMA Coverage # Name of objective "10" defined.absoluteCoverage=100 objective.conditions.conditions.conditions.10.0.count=1 objective.filters.5.0.filters.0.conditions.9.name=WiMAX Preamble CINR # Name of objective "7" defined.5.5.conditions.conditions.0.9.name=LTE RS Coverage # Name of objective "8" defined.target.0.threshold=10 objective.7.0.target.filters.conditions.8.name=WiMAX Preamble Coverage # Name of objective "6" defined.0.layer=umts objective.0.conditions.7.1. objective.layer=cdma objective. objective.isAbsoluteCoverage=yes objective.9.6.7.layer=wimax objective.quality=coverage objective.8.quality=cinr objective.5.threshold=4 objective.count=1 objective.threshold=-85 objective.absoluteCoverage=100 objective.operande=OR objective.operande=OR objective.0.

12.conditions.11.conditions.1.threshold=-13 objective.13.conditions.conditions.name=CDMA Soft Handover # Name of objective "13" defined.1.auto=false objective.12.conditions.target.0.1.conditions.13.0.conditions.operande=OR objective.12.0.13.target.12.11.layer=cdma objective.2.isAbsoluteCoverage=yes objective.count=1 objective.0.layer=cdma objective.conditions.12.conditions.conditions.0.operande=0 objective.0.quality=coverage objective.10.11.conditions.layer=cdma objective.13. objective.13.0.13.0.12.10.filters.11.count=1 objective.operande=AND objective. or mechanical tilt optimisation.13.target.conditions.12.0.auto=false objective.quality=ecio objective.operande=1 # "0" means "<" (less than) objective.conditions.quality=overlap objective.11.layer=cdma objective.11.target.absoluteCoverage=100 objective. instead they disable those reconfiguration options. objective.filters.13.operande=0 # "0" means "<" (less than objective.13.threshold=-95 12.11.0.count=2 objective.operande=0 # "0" means "<" (less than) objective.filters.0.conditions.isAbsoluteCoverage=yes objective.13.AT310_AM_E2 Atoll 3.threshold=-85 objective. objective.filters. antenna.13.0 Administrator Manual Chapter 12: Initialisation Files objective.0.threshold=4 objective.operande=AND objective.conditions.layer=cdma objective.threshold=4 objective.conditions.conditions.12.conditions.absoluteCoverage=100 objective.conditions.12.2.0.quality=overlap objective.13.13. 211 .13. The options in this section do not select the default reconfiguration options when set to "1".threshold=1 objective.1.quality=overlap objective.12.count=1 objective.12.conditions.4 Default Values on the Reconfiguration Tab In the [ACPTplReconfPage] section are the settings defining default values for the Reconfiguration tab.conditions.0.13.0.conditions.0.13.threshold=4 objective.1.conditions. The following options enable you to define the default reconfiguration that will be done: power.conditions.13.operande=OR objective.name=CDMA Pilot Pollution # Name of objective "12" defined.filters.11. azimuth.0.name=CDMA EcIo # Name of objective "11" defined.

If 0.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 [ACPTplReconfPage] umts.SyncMultiCellPower=1 cdma.disablePowerOptimisation=1 lte.1xevdo.1xrtt. If 0. If 0.feet=0 defaultTxHeightMax. If 0.SyncMultiCellPower=1 cdma.disablePreamblePowerOptimisation=1 wimax. If 0.Atoll 3.1xrtt.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm # around actual value.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm # around actual value.SyncMultiCellPower=1 wimax. use fixed value 37-46 gsm. use fixed value 37-46 The following options are used to define the default reconfiguration that will be done on transmitters and sites: disableAntennaOptimization=1 disableETiltOptimization=1 disableAzimuthOptimization=1 disableMechTiltOptimization=1 disableSiteSelection=1 The following options are used to specify default values for the reconfiguration ranges: defaultTxAzimuthVariation=20 defaultTxAzimuthStep=5 defaultTxAzimuthMinInterSector=0 defaultTxTiltMin=0 defaultTxTiltMax=5 defaultTxTiltStep=1 defaultTxETiltMin=0 defaultTxETiltMax=10 defaultTxHeightMin=0 defaultTxHeightMax=10 defaultTxHeightStep=5 defaultTxHeightMin.disableMaxPowerOptimisation=1 cdma.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm # around actual value.disablePowerOptimisation=1 gsm. use fixed value 37-46 wimax.1xrtt.disablePilotPowerOptimisation=1 cdma.SyncMultiCellPower=1 lte. use fixed value 37-46 cdma.disableMaxPowerOptimisation=1 umts.1.SyncMultiCellPower=1 umts.feet=30 defaultTxHeightStep.disablePilotPowerOptimisation=1 umts.1xevdo.feet=15 212 . use fixed value 37-46 lte.disableMaxPowerOptimisation=1 cdma.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm # around actual value.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm # around actual value.

AT310_AM_E2 Atoll 3. • 2: critical : EMF exposure is optimised independently of the effect it might have on coverage quality. only positions with a direct LOS to transmitters will register EMF exposure. distribution at all heights over area.2..0. eclass.e. # Default = 1 (yes) buildingDeeping=10 # if "onlyFacade" is set to 0. Each class is defined by a name. and Z planes: 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: onlyFacade=1 # Measurement only on facade in building propagation classes. When transparent mode is used.0. • 1: normal: There is a tradeoff between EMF exposure and coverage quality (default).2. Y. 2=critical The following options enable you to define the default resolution in metres in the X. useDiffraction=0 The following option defines whether the EMF module should use transparent mode.disableMaxPowerOptimization=0 12. The default is "1" (yes).count=2 # The total number of propagation classes defined. and whether it can be edited by the user. weightLevel=1 # 0=low. given that vectors are always given priority where they exist.disablePilotPowerOptimization=0 umts. no obstacle or indoor loss is accounted for.5 Default Values for EMF Exposure In the [ACPTplEMFPage] section are the settings defining default values for the EMF Exposure section of the Optimisation tab.position=0 # Distribution of measurement points: # 0=3D. i.6 defaultObjWeight=1 The following options enable you to define up to 16 propagation classes for EMF exposure.0 Administrator Manual Chapter 12: Initialisation Files umts.buildingLos=0 eclass. the depth in the building measured. isWorstCase=0 # Default is "0" (no) The following option defines the calculation radius (in metres) around transmitters when calculating EMF exposure: calculationRadius=300 The following options define the default threshold and weight for the EMF exposure objective: defaultObjThreshold=0. this option can be disabled if vectors are available for the entire area of interest. 2=2D on bottom eclass.linearBuildingLos=0 213 . eclass.1.name=Open eclass. useDhmFromClutter=1 # Default is "1" (yes) The following option defines whether the 3D propagation model is using diffraction. 1=2D on top.0. Thre are three possible values: • 0: Low: EMF exposure is optimised only if does not worsen coverage quality.0. but. 1=normal. The following option is used to enable the EMF exposure module: [ACPTplEMFPage] enable=1 The option "weightLevel" enables you to define the level of importance accorded to the optimisation of EMF exposure. When it is not. an indoor loss. 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.

editionFlag=0 # 0 can not be edited by user The following options enable you to map clutter classes to propagation classes. ACP considers that an antenna pattern is allowed for a given frequency band if its base frequency is within the allowed range (in MHz): freqBandRange=99 12.classCode=1 clutterMapping.2.Atoll 3.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 eclass.Automatic Cell Planning Properties dialogue.0. you enable the use of AEDT (additional electrical tilt) for managing different electrical tilt on each antenna pattern: enableAedt=1 By setting the following option.3. Using the Delegate Calculation to Model column.0.2..e. 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 dialogue). clutterMapping.2.clutterCode=10 clutterMapping. you can control the internal logic that ACP uses to assign different antenna patterns to different frequency bands.clutterCode=4 clutterMapping. The following options enable you to define default regex pattern that will is used to automatically calculating antenna groups: [ACPAntennaPage] autoGroupPattern=(.0. 12.Automatic Cell Planning Properties dialogue. and "Building" (ID "2"). 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 214 .classCode=2 clutterMapping.1. You can use the "advancedUI" option to display a column called Delegate Calculation to Model.classCode=0 clutterMapping. Any additional propagation classes will have an ID assigned when they are created.7.count=3 clutterMapping.*)_ autoGroupPattern_group=(.clutterCode=6 clutterMapping.1.7 Defining the Functionality of the ACP . "Vegetation" (ID "1").classCode=2 The following options define the default threshold and weight for the EMF exposure objective: [ACPEMFage] isPropClassesExtendable=1 # "1" enables user to create propagation classes.6 Default Values on the Antennas Tab In the [ACPAntennaPage] section are the settings defining default values for the Antennas tab. you can find the options used to set the choices available under Antenna Masking Method on the Setup Template tab of the ACP . 12. the second line defines the propagation class (by its ID under Propagation on the Optimisation tab of the ACP Setup dialogue). ACP will automatically apply the default antenna configuration each time a new setup is created (i.*)_ By setting the following option to "1" (default).1 Defining the Antenna Masking Model In the [ACPAntMaskModelPage] section.2. the configuration which have have been backed up by a user): autoRestoreDefaultConfig=1 By setting the following option to "1".1.ini file to define the functionality of the ACP .3.*)_ autoGroupPattern_ant=(.0.clutterCode=7 clutterMapping.2.2. The default propagation classes in the ACP are "Open" (ID "0").2.Automatic Cell Planning Properties Dialogue You can set options in the ACP.linearBuildingStart=0 eclass.2.

height.ini file. Additionally. the ACP does not extract custom fields.2.min=acp_gsmpower_min [ACPCustomFieldExtraction] tx.azimuth.max=acp_gsmpower_max in Transmitters and Repeaters table use to # The name of the custom column # initialize the reconfiguration parameter for each transmitter or repeater.optimize=acp_height_use in a custom field for a cell.height.2.tilt.min=acp_height_min # absolute value for height values Defining Reconfiguration Values for Transmitters and Repeaters Using Custom Atoll Fields tx.deltamin=acp_height_deltamin # relative values from current height tx. you can set options that azimuth angle tables in the Atoll database.optimize=acp_tilt_use is "0". tx. but ACP will not tx.gsm. the "Delegate Calculation to Model" # feature is disabled. it will use disk space to store the calculation results.gsm.azimuth.azimuth.min=acp_azim_min # absolute value for will enable ACP to extract data from custom fields from In the [ACPCustomFieldExtraction] section.step=acp_tilt_step tx.antenna.minInterSector=acp_azim_inter tx.tilt.0 Administrator Manual Chapter 12: Initialisation Files implements the appropriate methods of Atoll’s API).etilt. ACP will use the default value for that If a value is undefined parameter.antenna.max=acp_height_max In the [ACPCustomFieldExtraction] section.max=acp_azim_max extract the values entered in the custom fields and use them as default reconfiguration values when a new optimisation setup is created. tx.deltamax=acp_azim_deltamax in Custom Atoll Fields Defining Reconfiguration Values tx.step=acp_height_step the Atoll database. tx.1.8 tx.AT310_AM_E2 Atoll 3. tx.step=acp_azim_step update the Atoll tables with the new values.power.azimuth.min=acp_etilt_min [ACPAntMaskModelPage] tx.deltamax=acp_height_deltamax 12. nativeAllowFullPathLoss=1 # The relative values from current azimuth tx.deltamin=acp_azim_deltamin 12. ACP will tx.max=acp_etilt_max advancedUI=1 # The default tx.optimize=acp_ant_use tx. the feature is disabled.power. Delegating calculation to the propagation model provides more accurate tx.optimize=acp_gsmpower_use By default. tx.tilt. The custom columns in the Transmitters or Repeaters tables the Transmitters and Repeaters tables in must match the column name defined in the acp.e.height.azimuth.2.height..height.optimize=acp_etilt_use results but might take longer. tx.etilt.etilt.gsm. you can set options that will enable ACP to extract data from custom fields from tx.max=acp_tilt_max to allow "Optimised" propagation models (i.8.group=acp_ant_group # Best to define this column as a Boolean 215 .2. tx.min=acp_tilt_min tx. The values extracted can be updated in the ACP setup.1 tx. propagation models that use the "Optimised" The following option can be used mode) to use "Full Path Loss" mode: tx.azimuth.tilt.power.height.optimize=acp_azim_use # default is "0".azimuth.

height.tilt.optimize=acp_etilt_use tx.optimize=acp_pilotpower_use ccell.2.etilt.deltamin=acp_azim_deltamin tx.minInterSector=acp_azim_inter tx.etilt.power.min=acp_etilt_min tx.azimuth.azimuth.min=acp_pilotpower_min ccell.height.step=acp_height_step tx.etilt.power. The custom columns in the cells table must match the column names defined in acp. The following options can be used to define the custom columns in the CdmaCells table.gsm.height. the value of each is undefined.gsm.height.min=acp_tilt_min tx.optimize=acp_azim_use # relative values from current azimuth tx.2.maxPower. [ACPCustomFieldExtraction] wcell.pilotPower. These will be used for default reconfiguration options for WiMAX cells.min=acp_gsmpower_min tx.deltamax=acp_height_deltamax tx.min=acp_azim_min # absolute value for azimuth angle tx.step=acp_tilt_step tx.max=acp_height_max tx.height. By default.pilotPower.tilt.pilotPower.step=acp_pilotpower_step ccell.max=acp_gsmpower_max 12.tilt.max=acp_etilt_max tx.Atoll 3. you can set options that will enable ACP to extract data from custom fields from cells table in the Atoll database.min=acp_height_min # absolute value for height values tx.pilotPower.maxPower.max=acp_tilt_max tx.ini file.min=acp_maxpower_min ccell.2 Defining Reconfiguration Values for Cells Using Custom Atoll Fields In the [ACPCustomFieldExtraction] section.deltamin=acp_height_deltamin # relative values from current height tx.maxPower. the ACP does not extract custom fields.optimize=acp_height_use tx.azimuth.optimize=acp_tilt_use tx.azimuth.max=acp_azim_max tx.optimize=acp_gsmpower_use tx.max=acp_maxpower_max ccell.gsm.azimuth.maxPower.8.power.azimuth.azimuth. therefore the field will not be extracted.optimize=acp_maxpower_use ccell.power.min=acp_power_min 216 .step=acp_maxpower_step The following options can be used to define the custom columns in the WCells table.max=acp_pilotpower_max ccell.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 tx.power.tilt.optimize=acp_power_use wcell. [ACPCustomFieldExtraction] ccell.1.deltamax=acp_azim_deltamax tx.height. By default.step=acp_azim_step tx.

model" enables you to automatically form a multi-band antenna.step=acp_power_step The following options can be used to define the custom columns in the T4GCells table. 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. Tilt column.max=acp_power_max lcell.2.power.step=acp_power_step 12.power.heightLocked=acp_site_heightLocked 12.. all patterns related to the same physical antenna) and group the physical antennas at different frequencies into radomes by using the "antenna. # Default value is 'ACP_STATUS'. In the ACP Setup dialogue.locked=acp_site_locked site.8.3 Defining Reconfiguration Values for Sites Using Custom Atoll Fields In the [ACPCustomFieldExtraction] section. The "antenna.status=ACP_STATUS # Name of the custom column in Sites table.e.min=acp_power_min lcell. By default.optimize=acp_power_use lcell.etiltShare=ACP_ETILT_SHARE 217 . The following options can be used to define custom columns in the Sites table.cellsRemoveable=acp_site_cellsRemovable site.ini file: • Status of sites: By using the "site.2. These will be used for default reconfiguration options for LTE cells. all active sites are considered as existing sites.power. this is accomplished by selecting the check box in the Same Elec. Any sites with a label other than the one defined by the "site.candidate" option will be automatically set as candidate sites.4 Defining Reconfiguration Values for Antennas Using Custom Atoll Fields In the [ACPCustomFieldExtraction] section.status" option to define the name of the custom status column in the Sites table. [ACPCustomFieldExtraction] antenna.removeable=acp_site_removable site. [ACPCustomFieldExtraction] site.1. therefore the field will not be extracted.8. site. the value of each is undefined. The custom column in the Antennas table must match the column names defined in the acp.2.candidate=candidate # Name used to define a candidate site.max=acp_power_max wcell. These will be used for default reconfiguration options for each site..ini file. 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 . for physical antennas that always use same electrical tilt).candidate" option will be considered as existing sites.status. By default. The custom columns in the Sites table must match the column name defined by the settings in the acp.AT310_AM_E2 Atoll 3.power. The antenna model is by default set to the PHYSICAL_ANTENNA column of the Antennas table. Using the "antenna. Hence by default the auto antenna grouping is always enabled if antenna patterns are correctly assigned to physical antennas. [ACPCustomFieldExtraction] site. you can extract the status (candidate or existing) of sites for site selection.model" option.0 Administrator Manual Chapter 12: Initialisation Files wcell. All sites in the Sites table with the label set to the one defined by the "site.azimLocked=acp_site_azimLocked site.power.power. [ACPCustomFieldExtraction] lcell. you can set options that will enable ACP to extract data from custom fields from Antennas table in the Atoll database. you can set options that will enable ACP to extract data from custom fields from Sites table in the Atoll database. [ACPCustomFieldExtraction] antenna.e.2.etiltShare" option should contain a list of the spaceseparated frequencies for which the corresponding physical antennas must be linked (i.status.model=PHYSICAL ANTENNA 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.status.

1 Defining Automatic Site Classes In the [ACPGeneralPage] section.X.count=1 # Number of defined classes In the [ACPTplGeneralPage] section.name=Planned cost. that defines the # aedt range antenna.X.classes. cost. you can find the option used to define the whether the site class feature appears.tilt. The name of each class as it appears in the ACP is defined by an option called "cost.power.X.classes. cost.ini so that the ACP applies site classes based on optional data in the Atoll database.9. "false" if it does not. cost.cost: This key is used to define the cost of changing the antenna height.classes.classes.2.2. cost. "false" if it does not.9 Defining Site Class Options You can set options in the ACP.classes.X.height. in order to activate it.0. The corresponding settings for the class defined in "cost. you must set the "enableAedt" option to "1" first.1.cost: This key is used to define the cost of changing the antenna azimuth.classes.classes.aedtMax=ACP_AEDT_MAX 12.isSiteVisit: This key is set to "true" if this cost entails a site visit.tilt. The following is an example of the keys for the first site class (numbered "0") called "Planned" in this example.X.height. 12.siteVisitCost: This key is used to define the cost of a site visit.classes. "false" if it does not.cost: This key is used to define the cost of changing the mechanical tilt of the antenna.azimuth.2. cost.0. cost.classes.cost=1 218 .name" are defined using the following options: • • • • • • • • • • • • • • • • cost.classes.aedtMin=ACP_AEDT_MIN # The name of the custom column in ANTENNA table of type 'int'.classes. "false" if it does not.removeSiteCost: This key is used to define the cost of removing an existing site. To optimise AEDT.X.classes.Atoll 3.classes.X. cost.showUI=1 # The default is "1".X.cost: This key is used to define the cost of changing the electrical tilt of the antenna. cost.X.upgradeSiteCost: This key is used to define the cost of upgrading an existing site.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.classes.X.azimuth. You can both define site classes that automatically appear in the ACP Setup dialogue and set options in the ACP.newSiteCost: This key is used to define the cost of creating a new site.antenna. cost.cost: This key is used to define the cost of changing the power.isSiteVisit: This key is set to "true" if this cost entails a site visit. "false" if it does not.ini file to define site classes in the ACP.azimuth.aedtUse=ACP_AEDT_USE # The name of the custom column in ANTENNA table of type 'int'.isSiteVisit: This key is set to "true" if this cost entails a site visit.cost: This key is used to define the cost of changing the type of the antenna. [ACPTplGeneralPage] cost.classes.etilt.isSiteVisit: This key is set to "true" if this cost entails a site visit. "false" if it does not. [ACPCustomFieldExtraction] # The name of the custom column in ANTENNA table of type 'bool' used to # automatically generate patterns from the given aedt range antenna.power.X. cost.antenna. These settings are local settings. the site class feature is enabled.X.classes.isSiteVisit: This key is set to "true" if this cost entails a site visit.X.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 The following option can be used to name the custom columns in the Antennas table to automatically define the AEDT options. cost. cost. cost.classes. you can define the default values when the site class option is available.etilt. cost.classes. that defines the # aedt range antenna.X.classes.classes. cost.2.isSiteVisit: This key is set to "true" if this cost entails a site visit.X.classes. cost.classes.X.classes.name" where "X" is a sequential number.X.X. cost. The following option can be used to show or hide the site class feature and set the number of site classes defined: [ACPGeneralPage] cost.

power. For new candidate sites which are located on an existing site.0.0 Administrator Manual Chapter 12: Initialisation Files cost.classes.0.AT310_AM_E2 Atoll 3.upgradeSiteCost=5 cost.0.height.siteVisitCost=2 cost.0.cost=0.0.isSiteVisit=false cost.0.1 cost.newSiteCost=10 cost. 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.isSiteVisit=true cost.azimuth. you can define the custom field in the Site table of the Atoll database that identifies the site class of each site.power.10 Defining the Appearance of the Optimisation Dialogue In the [ACPMapPage] and [ACPMapDefault] sections are the settings defining the appearance of the Optimisation dialogue that appears when running an optimisation.0. the cost structure is automatically defined as well.classes.classes.classes. For new candidate sites which are not co-located on an existing site.2.tilt.1 Defining the Colours in the Quality Analysis Maps The following settings in the [ACPMapDefault] section are used to define the colours used in the quality analysis maps on the Quality Maps tab. By defining the costs of each site class as explained in "Defining Automatic Site Classes" on page 218. the site class is the same as the site on which the new candidate is located. the site class is set to "Default" and can be changed manually.0.1 cost.classes.2. [ACPCustomFieldExtraction] site.antenna.0. 219 .0.10.classes.classes.2.antenna.tilt. 12.cost=0.2.0.0.classes.1.2.cost=1 cost.9. 12.cost=1 cost.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.2.isSiteVisit=true cost.cost=1 cost.etilt.removeSiteCost=-5 12.2 Automatically Assigning Site Classes in the ACP In the [ACPCustomFieldExtraction] section.classes. Some options refer to the Graphs tab and some to the Quality Maps tab.classes.classes.classes.isSiteVisit=true cost.classes.classes.etilt.height.0.classes.0.isSiteVisit=false cost.isSiteVisit=true cost.0.

2.<techno>.range.7=[-3. The settings are the same for the various quality indicator of the various technologies.range.overlapgain for overlap maps colormap.<quality>.<quality>.<quality>.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 There are two possible formats for defining the range of colours on maps: 1.000000] RGB(255 128 0) colormap.1.range.3=[-11.<techno>.000000] RGB(0 196 196) colormap.000000 -9.<quality>. slCN.000000 -7.gain for objective status maps and a few others for change maps.6=[-5.<quality>. 12.<techno>. slgain. rsrq.maxPixelSize=6 # If autopixel is set.2 Other Components of the Optimisation Dialogue The following settings in the [ACPMapPage] section are used to define other components of the Optimisation dialogue that appears when running an optimisation.<quality>. lte.titleFontSize=16 # Size of title font in points The following option defines the width of the margin in pixels on the Quality Maps tab: config.isAutoPixel=1 # Automatically calculate point size from coverage surface config.overlap and colormap.rangeDefinition=[-5 RGB(255 0 0)] [-20 RGB(0 0 255)] -5 These colormap descriptions are used for default colormap and can easily be changed by the user. The default acp.000000] RGB(255 224 0) colormap.margin=2 220 . You can let ACP automatically define the pixel size or you can define the pixel size: config.Atoll 3.range.0=[-99999. slgain. cdma <quality> with: • • • • In UMTS: ecio.000000 -15. slC. cinrgain In addition a number of other colormaps can be defined for other type of maps: • • • colormap. etc. The following options define the background and foreground colours of the Quality Maps tab.000000 -13. eciogain In GSM: sl.<techno>.objective and colormap.range.000000 99999.background=0 # RGB code as integer(R+G*2^8+B*2^16): here black config.titleHeight=16 # Title height in pixels config. limit the pixel size to the set maximum. slC.range. the minimum and maximum value of the range followed by its RGB color representation.<techno>.1=[-15. gsm. cinr. slCN. calculate the pixel size of a point to try to cover the set percentage of the used surface config. ecgain.10. use this number of pixels for each point config.4=[-9. emf maps.pixelCoverage=50 # If autopixel is set. rsrp.000000] RGB(0 224 0) colormap.pixelSize=1 # If autopixel is not set.000000 -5.2=[-13.<quality>. slgain. The number of ranges is defined and. In WiMAX: sl.000000] RGB(0 128 255) colormap.range.<techno>. cinrgain In LTE: sl. where you replace: • • <techno> with umts.<techno>. ec.000000] RGB(0 0 255) colormap.<quality>.ini file installed with the ACP has a complete list. The following options define the pixel size used in the maps on the Quality Maps tab. with the RGB code as an integer: config.<techno>. colormap.<techno>. Detailed format: The detailed format enables you to set a non-uniform range.2. Uniform format description: A uniform format description using a range and step: [firstBreak startcolor] [lastBreak endColor] interval: colormap. for each range.foreground=16777215 # RGB code as integer(R+G*2^8+B*2^16): here white 8 16 The RGB code for white is calculated as follows: 255 + 255 × 2 + 255 × 2 = 16777215 .000000 -11. Some options refer to the Graphs tab and some to the Quality Maps tab.<quality>.nbRange=8 # Number of ranges to be defined colormap.000000 -3.objective. cinr.<quality>. wimax.5=[-7.000000] RGB(255 0 0) 2.000000] RGB(128 255 0) colormap.<techno>. The following options define the size of the map title on the Quality Maps tab: config.range.

" used in Japanese systems. and cells automatically created by ACP in Atoll as part of the candidate site selection.2.0 Administrator Manual Chapter 12: Initialisation Files The following options define the appearance of the map legend on the Quality Maps tab: config.1. config.14 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 dialogue.15 Defining the Default Font In the [ACPUI] section is the option for defining the default font to be used by the grid. In the example below.13 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. graph component. [ACPGraphPage] showTimeMarkers=1 # add time markers on the X axis.2.showAxis=1 The following options define the appearance of the histogram on the Quality Maps tab: config.focusLighterPercent=30 # Defines how much lighter the area outside the focus zone is displayed. the font "MS UI Gothic. addCandidateComment=Created from ACP candidate list 12. The following options define the appearance of the focus zone on the Quality Maps tab: config.showFocusZone=1 # Defines whether the focus zone is displayed. The following option defines the transparency of new maps: transparency=50 12. Default is "0" (OFF) 12.2.2. is set as the default font. config. A value of 100 disables it. opacity=100 12.12 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). config. [ACPCommitPage] allowUserChangeForCommit=false You can use the "addCandidateComment" option to create a comment in any site.2. and map component.11 Defining the Appearance of New Maps In the [ACPMapDefault] section is the option for defining the appearance of new maps created from optimisation results. config.showLegend=1 # Defines whether the legend is displayed.AT310_AM_E2 Atoll 3. No comment is added if this option is left blank.2. [ACPUI] 221 . Setting "allowUserChangeForCommit" to "true" allows the user to edit the set of changes on the Commit tab.showHistogram=1 # Defines whether the histogram is displayed. A value of 100 disables it. 12. this setting is not recommended.histogramHeight=60 # Defines the width of the histogram in pixels. transmitter.2.2.legendForeground=0 # RGB code as integer: here black The following option defines whether the axis is displayed on the Quality Maps tab: config.2. config.2.legendFontSize=11 # Defines the font used in points.legendWidth=40 # Defines the width of the legend in pixels.

graph component and map component DefaultFont=MS UI Gothic # for grid only. By default the support e-mail is set to Forsk support. define the used font size. The default setting for "computationThreadPoolSize" is "-1" and means that ACP will use one thread per processor core (CPU) available.3 Memory Management Settings The following options define how the ACP manages memory during calculations. useCrashReport=1 When the crash reporter is enabled. You can change this by editing the following option in the XCrashReport. no log file.2.ini file: [Email] Adress=support@theoperator.2. 222 . 4=resultSummary. The ACP tries to estimate the worst-case scenario in memory use.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 # define the font used by grid. as defined in "memLimitNumPos" is reached during a calculation. Using one of the following options.com Name=Support_name 12.Atoll 3. 2=setup." ACP uses only one thread.3 ACP Core Engine Options The settings in the [ACPCore] section are used to define how the ACP engine functions.acpReport.3.1. 8=resultSectors. The following option defines whether ACP generates a log file (with the name ATL_NAME_optim." ACP uses the number of threads specified by the "computationThreadPoolSize" option. The following option defines whether the crash reporter will run in case of an application crash. ACP provides the possibility of sending information by e-mail that can be used to help determine the reason the application crashed. 64=resultMaps. 0 mean default size DefaultGridFontSize=0 12..3.2. -1=all encoding=UTF-8 saveDefaultStylesheet=1 #save a default stylesheet if none exist defaultStylesheetName=. If "useComputationThreadPool" is set to "true. 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. if the application crashes. enableXmlExport=1 #enable the xml report from the ResultStatPage generateXmlSection=-1 # bit combination of following: 1=metadata.16 Exporting Optimisation Results in XML In the [ACPXmlReport] section are the options for defining the contents and appearance of an XML report generated from the Statistics tab of the optimisation Properties dialogue.2. 16=resultIterations.log): [ACPCore] generateLogFile=0 # The default is "0".xslt # name of the default stylesheet file.2. and indicates to the user when memory use seems too high. 32=resulstChangeset.2 Calculation Thread Pool Settings The following options define how the calculation thread pool will be managed. 12. useComputationThreadPool=true computationThreadPoolSize=-1 12.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. No sensitive project-related information is sent. Setting "memLimitNumPos" to "-1" deactivates this option.2. set it empty to disable stylesheet processing instruction 12. If "useComputationThreadPool" is set to "false.

5 Determining Transmitter Altitude The following option defines how ACP determines the transmitter altitude when no site altitude is defined in Atoll. If all three options are deactivated." ACP uses only the coordinates of the site. linkMode = 0 # The default 12. 1: When "linkMode" is set to "1. When "addPilotSHOGain" is set to "0. as defined in "memLimitUseableMemory.0 Administrator Manual Chapter 12: Initialisation Files • • memLimitMemory: Memory use is determined to be excessive when the estimated memory use in Mb.. memLimitMemory=-1 # A setting of "-1" deactivates this option." ACP uses the exact transmitter coordinates. When ACP estimates actual memory use (i.2 Macro Diversity Gain (UMTS Only) The following option defines whether ACP takes macro diversity gain into account in UMTS. 2: When "linkMode" is set to "2.3." Setting "memLimitUseableMemory" to "-1" deactivates this option. "useSiteAltitude" can have the following values: • • 0: When "useSiteAltitude" is set to "0. 1: When "addPilotSHOGain" is set to "1. the memory estimate is only a rough estimate.2. using either "memLimitMemory" or "memLimitUseableMemory"). This is the default setting.e. CDMA pilot power) using the "linkMode" option. The "abortIfMemLimitReach" option defines how ACP reacts if the defined maximum memory use is reached.3. This is the default value. ACP does not check excessive memory usage. By default.3. LTE Reference signal Power.2." ACP does not take macro diversity gain into account. "addPilotSHOGain" can have the following values: • • 0: When "addPilotSHOGain" is set to "0. excessive memory use is considered an estimate of 80% of the memory available to the process." ACP does not take reception or transmission losses into account.1 Signal Level You can define how ACP measures the signal level (UMTS RSCP. When using the option "abortIfMemLimitReach". memLimitUseableMemory=80 # A setting of "-1" deactivates this option.3." the ACP results will only match the results in Atoll if the following settings are made in the [CDMA] section of the atoll. as defined in "memLimitMemory" is reached during a calculation.4. GSM BCCH Power. abortIfMemLimitReach=0 12. By default (with "abortIfMemLimitReach" set to "0").1." ACP takes macro diversity gain into account. Depending on the project. Setting "memLimitMemory" to "-1" deactivates this option. then ACP will not start if the message indicating excessive memory use is displayed. 1: When "useSiteAltitude" is set to "1." ACP considers the signal level on the downlink and transmission losses are taken into account.4. ACP will attempt to allocate memory.4 Signal Level and Macro Diversity Gain Calculation Options The following options determine how ACP calculates the signal level and the macro diversity gain mode.AT310_AM_E2 Atoll 3. memLimitNumPos=-1 # A setting of "-1" deactivates this option. This is the default value. If unable to successfully allocate memory.2. memLimitUseableMemory: Memory use is determined to be excessive when the estimated memory use exceeds the percentage of the total memory available for Atoll. actual memory usage can be quite different. ACP is not prevented running even when 80% is exceeded. Any changes you make here must match corresponding changes in the atoll." ACP considers the signal level on the uplink and reception losses are taken into account.2. 223 . WiMAX Preamble Power.ini file. ACP displays a message and the calculation is stopped.ini file: AddPilotSHOGain=0 addPilotSHOGain=1 # The default 12. 12. including dx and dy offset. The "linkMode" option can have one of the following values: • • • 0: When "linkMode" is set to "0.

memory use.ini file: useSiteAltitude=1 useSiteAltitude=1 # The default 12.1.3." the ACP results will only match the results in Atoll if the following setting is made in the atoll. Default: When no changes are made to the acp.Automatic Cell Planning Properties dialogue. The analogous options for the high speed mode and the high precision mode are "maxMonitorCellSpeed" and "maxMonitorCellPrec". When "useSiteAltitude" is set to "1. ACP uses the default settings. respectively. High Precision: When the settings in this section are defined to give the results of the highest precision. you must set the ACP to access raster data for each document separately using the following option: 224 .6 Balancing Speed. The default settings can be overridden by changing the settings in this section. By defining the settings of the options in the acp.3. calculating the results will take the longest time and will use more memory. Memory Use.2.ini options that define how the selected mode works are described below: • maxMonitorCell: The "maxMonitorCell" defines the maximum number of cells monitored. threshLevelMonitorCell: The "threshLevelMonitorCell" defines the best server signal threshold (dB) in order to be monitored. The options described below are those used for the default operation mode The acp. • • The following options define the values ACP uses for default mode: maxMonitorCell=32 threshLevelMonitorCell = 35 The following options define the values ACP uses for high speed mode: maxMonitorCellSpeed=30 threshLevelMonitorCellSpeed = 30 The following options define the values ACP uses for high precision mode: maxMonitorCellPrec=35 threshLevelMonitorCellPrec = 40 Other options in the acp. This option affects memory and accuracy.ini file that each mode uses.ini file. The analogous options for the high speed mode and the high precision mode are "threshLevelMonitorCellSpeed" and "threshLevelMonitorCellPrec". and Accuracy in Calculations On the User Preferences tab of the ACP . 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 may be slightly less accurate.ini file can be used to define additional offsets that will be used by the specific technology that ACP is optimising: threshLevelOffUmts=0 maxMonitorOffUmts=0 threshLevelOffGsm=0 maxMonitorOffGsm=0 threshLevelOffWimax=5 maxMonitorOffWimax=5 threshLevelOffLte=10 maxMonitorOffLte=10 12. ACP enables you to select a mode of operation that balances balance speed. 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.Atoll 3. and accuracy.2. respectively.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 Any change you make here must match a corresponding change in the atoll.7 Accessing Raster Data When working in co-planning mode. This option affects memory use and accuracy. you have several Atoll document open and you are working with the ACP from the main document.ini file.

3. pathlossAccessMode=2 12. The maximum memory (in Mb) allowed for this block processing in Mb is controlled with the following setting: gisDataCacheMemMax=256 You can reduce this number if you experience issues with ACP failure due to memory allocation. If this option is set to "1. 2: ACP automatically detects the version of Atoll used.1." ACP will only take preamble segmentation into account if the segmentation flag of cell frame configuration is set to ON.8. wimaxPreambleSegmented=2 12.0 of Atoll." ACP will access path loss matrices directly.9 Preamble Segmentation (WiMAX) You can define how ACP takes segmentation into account using the "wimaxPreambleSegmented" option. the path loss matrices must be stored externally." ACP will access path loss matrices through Atoll. This is the default value.8. If this option is set to "0. wimaxMultiAntennaInterference=2 12. This option has the possible values: • • • 0: Interference independent of number of transmit antennas.2. With this setting. This option enables you to take into account the change in change in calculation methods from version 2. In version 2. This is the default value. 2: ACP automatically detects the version of Atoll used.0 Administrator Manual Chapter 12: Initialisation Files gisDataTechnoShared=0 Atoll ACP loads raster data with block-based processing to reduce memory usage.7. 225 . This is the default value. 1: Interference multiplied by number of transmit antennas. lteMultiAntennaInterference=2 12.3." ACP will access path loss matrices directly if they are external.3.11 Multi-antenna Interference Calculation (WiMAX) Refer to "Enabling Multi-antenna Interference Calculation in WiMAX" on page 201 for details. otherwise through Atoll if they are embedded. and hence the value used by Atoll for this option.0.2.7.3." ACP always takes preamble segmentation into account.10 Multi-antenna Interference Calculation (LTE) Refer to "Disabling Multi-antenna Interference Calculation in LTE" on page 201 for details. they can not be embedded. 1: If this option is set to "1.2.1. 2: If this option is set to "2.12 Cyclic Prefix Energy in Signal Level Calculation (LTE) Refer to "Including Cyclic Prefix Energy in LTE Signal Level Calculation" on page 201 for details.3.2. 2: If this option is set to "2. This option has two possible values: • • • 0: If this option is set to "0.7.1. This option has the possible values: • • • 0: This value is intended for versions of Atoll up to and including version 2. In version 2. 1: Interference multiplied by number of transmit antennas. 12.0 and up." ACP automatically detects the version of Atoll used.AT310_AM_E2 Atoll 3. 1: This value is intended for versions of Atoll of 2. the preamble was not considered as segmented unless the frame configuration used by the cell was flagged as segmented.1 to version 2. the preamble is considered by default to be segmented.8 Accessing Path Loss Matrices You can define how ACP accesses path loss matrices using the "pathlossAccessMode" option. This option has the possible values: • • • 0: Interference independent of number of transmit antennas. This is the default value.8.2. and hence the value used by Atoll for this option.

3. 1: Excluded. This is usually caused by inconsistencies between the vectors imported to create the 3D representation of the terrain and Atoll database. the combination of clutter heights and imported vectors used to create the 3D representation of the terrain) and DHM-offset. This option has the possible values: • • • 0: Included.0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 This option has the possible values: • • • 0: Included. The ACP automatically detects these transmitters and displays warnings in the Event Viewer. the default being 2 metres. just below the roof.Atoll 3.2. 1: Excluded. or LTE). and hence the value used by Atoll for this option. height is not reset. just below the roof. This is the default value.1.4 EMF Exposure Core Options In the [ACPEMFCore] section there are several options controlling the EMF exposure calculation engine. wimaxExcludeCPFromUsefulPower=2 12.e. the ACP forces the ratio between pilot power and maximum power to stay constant. 12. One set of options allows for the detection and auto correction of transmitter heights which are found to be indoors. The following option defines the internal resolution in metres for terrain 3D representation when the ACP rasterises input vectors: vectorRasterizationResolution=2 # "2" is the default.15 Enabling Multi-technology Optimisation Including WiMAX In order to use the ACP to optimise your WiMAX network with any other technology network (GSM. and hence the value used by Atoll for this option.2. 226 . 2: ACP automatically detects the version of Atoll used.2. When the height of a transmitter is within the Digital Height Model (i. UMTS.3. lteExcludeCPFromUsefulPower=2 12.3. The default distancebeneath the roof is 5 metres. set the following option in ACP. You can remove this constraint using the following option: umtsPilotPowerRatioFixed=0 12. 2: ACP automatically detects the version of Atoll used.2.13 Cyclic Prefix Energy in Signal Level Calculation (WiMAX) Refer to "Excluding Cyclic Prefix Energy in WiMAX Signal Level Calculation" on page 201 for details. then it is considered to be indoors.. This is the default value. The other option controls the resolution used internally to rasterize input vectors. resetTxHeightWhenIndoor=0 # "0" is the default.ini: [ACPImportProject] importWimax=1 importWimax is set to 0 by default. [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).14 Fixed Ratio Between Pilot Power and Max Power (UMTS) When optimising the maximum cell power in UMTS.

AT310_AM_E2 Atoll 3. # Default is "1" (true) If "autoCheckPredictionValidity" is set to "1.1. If it is set to "0." thereby enabling the verification of the validity of coverage predictions. autoCheckPredictionValidity=1 # "1" enables the automatic verification The following options can be used to enable other automatic verifications on the number of active transmitters.5.2. you can have ACP automatically recalculate the invalid coverage predictions using the following option." ACP will not automatically recalculate predictions. and locked status in the Atoll document: autoCheckPredictionFileValidity=1 # Check of path loss matrices before a run. their pathloss file size. 12. manageLockedPredictionAsvalid=1 # Treat locked prediction as always valid. autoCheckTxNumber=1 # Check number of active transmitters. autoPathlossRecomputation=0 227 .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.5 Other Options In the [ACPMisc] section are several additional ACP configuration options.2.0 Administrator Manual Chapter 12: Initialisation Files 12.

0 Administrator Manual Chapter 12: Initialisation Files © Forsk 2011 228 .1.Atoll 3.

Part 3 Data Structures This part of the administrator manual provides information on the data structures of the Atoll technology modules. the following are explained: • • • • • • • • "GSM GPRS EDGE Data Structure" on page 231 "UMTS HSPA Data Structure" on page 263 "LTE Data Structure" on page 295 "3GPP Multi-RAT Data Structure" on page 325 "CDMA2000 Data Structure" on page 335 "TD-SCDMA Data Structure" on page 365 "WiMAX Data Structure" on page 399 "Microwave Links Data Structure" on page 429 . In this part.

.

1 231 . The following subsections list the tables in the GSM GPRS EDGE template data structure.3 on page 233 depict the GSM GPRS EDGE database structure.1: GSM GPRS EDGE Template . and Figure 13. Figure 13.1 on page 231.2 on page 232.AT310_AM_E2 Atoll 3. Figure 13.1. Figure 13.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure 13 GSM GPRS EDGE Data Structure The GSM GPRS EDGE data structure is described below.

Atoll 3.2 232 .1.2: GSM GPRS EDGE Template .0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 Figure 13.

1 Added Tables and Fields Antennas Table Field PHYSICAL_ANTENNA Type Text (50) Description Physical antenna name Attributes Null column allowed: Yes Default value: CodecModeAdaptations Table Field MAL_LENGTH Type Integer Description MAL length Attributes Null column allowed: Yes Default value: 233 .3 13.1.3: GSM GPRS EDGE Template .AT310_AM_E2 Atoll 3.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure Figure 13.1 13.1 Changes in Data Structure From 2.1.8 to 3.

1.alternatively (antenna hopping) Attributes Null column allowed: Yes Default value: 0 234 .0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 CodecQualityTables Table Field MAL_LENGTH Type Integer Description MAL length Attributes Null column allowed: Yes Default value: CustomFields Table Field CHOICE_TYPE Type Integer Description 0: Choice List is optional.Atoll 3. this field indicates if they are used 0.simultaneously (TXDiv) or 1. 1: Choice List is mandatory Attributes Null column allowed: Yes Default value: 0 EGPRSQuality Table Field MAL_LENGTH Type Integer Description MAL length Attributes Null column allowed: Yes Default value: EGPRSServices Table Field DL_ACTIVITY DL_MBR REQ_AVERAGE_DL_RATE REQ_AVERAGE_UL_RATE UL_ACTIVITY UL_MBR Type Float Float Float Float Float Float Description Activity factor for voice services on the downlink DL Maximum Throughput Requested Average Downlink Rate (kbps) Requested Average Uplink Rate (kbps) Activity factor for voice services on the uplink UL Maximum Throughput Attributes Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 EGPRSTerminals Table Field DTX Type Boolean TplTransmitters Table Field COMMENT_ SHAREDMAST Type Text (255) Text (50) Description Comments Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Description DTX capability of terminal Attributes Null column allowed: No Default value: True Transmitters Table Field SHAREDMAST Type Text (50) Description Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: TRGConfigurations Table Field TX_DIVERSITY_MODE_DL Type Short Description If more than one antenna are used (TX_DIVERSITY_NBANT).

2 AfpModels Table For AFP models.alternatively (antenna hopping) Subcell’s Uplink Traffic load Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 13. Field DATA DESCRIPTION NAME SIGNATURE Type Binary Text (255) Text (50) Text (40) Description Model specific parameters User defined Name of the AFP model Unique Global ID of last model update Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: 235 .0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure TRGs Table Field BLOCKING_PROBA DTX_GAIN_DL TX_DIVERSITY_MODE_DL UL_TRAFFIC_LOAD Type Float Float Short Float Description Blocking probability (%) Downlink Gain due to DTX (dB) If more than one antenna are used (TX_DIVERSITY_NBANT).1.AT310_AM_E2 Atoll 3.1.simultaneously (TXDiv) or 1.2 Deleted Tables and Fields AntennasLists Table • Table AntennasListsNames Table • Table Neighbours Table • RANK NeighboursConstraints Table • RANK NeighboursConstraintsExt Table • RANK NeighboursExt Table • RANK TplTransmitters Table • • • ANTDIVGAIN AVERAGE_8PSK_POWER_BACKOFF COV_PROBA Transmitters Table • • • ANTDIVGAIN AVERAGE_8PSK_POWER_BACKOFF COV_PROBA 13. this field indicates if they are used 0.

Field Beamwidth COMMENT_ CONSTRUCTOR DIAGRAM ELECTRICAL_TILT FMax FMin GAIN NAME PHYSICAL_ANTENNA Type Float Text (255) Text (50) Binary Float Double Double Float Text (50) Text (50) Description Antenna beamwidth Additional information about antenna Antenna manufacturer name Antenna horizontal and vertical patterns Antenna electrical tilt (for information) Maximum operating frequency of the antennas Unit: MHz Minimum operating frequency of the antenna Unit: MHz Antenna isotropic gain Unit: dBi Name of antenna Physical antenna name Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: The format of the binary field.1. 13. Field DOMAIN_NAME EXCLUDED EXTRA Type Text (50) Text (225) Text (225) Integer Description Called grouping scheme. ….5 BSICGroups Table For BSIC groups belonging to BSIC domains. Set of resource groups. DIAGRAM. FIRST+2*STEP. Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 FIRST 236 . FIRST+STEP. FIRST+n*STEP. It is forbidden for EXTRA and EXLUDED to have common numbers Group elements are: FIRST. is described in "RF 2D Antenna Pattern Format" on page 105. LAST and STEP (separated with commas) BSIC to be added. Field NAME Type Text (50) Description Name of the domain Attributes Null column allowed: No Default value: 13. n is the greatest positive integer so that FIRST+n*STEP LAST.4 BSICDomains Table For names of BSIC domains.3 Antennas Table For antennas.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 Field TYPE Type Text (50) Description ProgID of the model Attributes Null column allowed: No Default value: 13. List of BSICs to be excluded from the series defined by FIRST.Atoll 3.

FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Attributes Null column allowed: No Default value: 13.8 ChannelModels Table For channel models.6 BTSEquipments Table For BTS equipment. But these fields are of type Text when accessed or retrieved from an add-in. Name of a resource group Group elements are: FIRST. FIRST+2*STEP.1. FIRST+STEP. Field IDEAL_LINK_ADAPTATION Type Boolean Description Automatic mode selection providing the best quality Attributes Null column allowed: No Default value: True 237 .9 CodecEquipments Table For codec configurations.7 CellTypes Table For cell types. Field NAME TX_DIV_GAIN Type Text (50) Float Description Name of the channel model Gain applied for subcells using TX diversity Attributes Null column allowed: No Default value: Null column allowed: No Default value: 0 13. FIRST+n*STEP.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure Field LAST NAME STEP Type Integer Text (50) Integer Description Group elements are: FIRST. Unique key. Field CONFIG_DL_LOSSES CONFIG_UL_LOSSES NAME NOISE_FIGURE RHO_FACTOR Type Float Float Text (50) Float Short Description Downlink losses due to the configuration of the BTS (duplexer and/or combiner) Uplink losses due to the configuration of the BTS (duplexer and/or combiner) Name of Base Station Equipment Noise figure of Base Station Rho factor (not used) Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 100 13.AT310_AM_E2 Atoll 3. 13. FIRST+STEP. FIRST+2*STEP.mdb) and in a database (if connected to one). …. …. Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 1 The FIRST and LAST fields of this table are of type Integer in the template (. n is the greatest positive integer so that FIRST+n*STEP LAST. Field NAME Type Text (50) Description Defines the list of TRXs of the station and associated parameters.

11 CodecModes Table For codec types and modes.12 CodecQualityTables Table For codec performance graphs. empty = all hopping modes MAL length C/(I+N) quality threshold for selecting this mode when there is no ideal link adaptation Mobility (empty = all mobilities) Attributes Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 13.10 CodecModeAdaptations Table For codec mode selection. 2= ideal FH. Field C_I_TABLE C_N_TABLE Type Memo Memo Description QI = f(C/I) table QI = f(C/N) table Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 238 .Atoll 3. Field CODEC_EQT CODEC_MODE FREQUENCY_BAND HOPPING MAL_LENGTH MIN_CIR MOBILITY Type Text (50) Text (50) Text (20) Short Integer Float Text (50) Description Codec equipment name Codec mode Frequency Band (empty = all bands) Frequency hopping 1=NH.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 Field IDEAL_QI_NAME NAME REFERENCE_NOISE Type Text (20) Text (50) Float Description Reference quality indicator name used for ideal link adaptation Name of Codec equipment Receiver reference noise Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: -113 13. Field _8PSK_MODULATION CODEC_TYPE HR MAX_RATE NAME SELECTION_PRIORITY Type Boolean Text (50) Boolean Float Text (50) Short Description Modulation is 8PSK Name of codec type Half rate support Maximum supported rate for this mode (kbps) Name of the codec mode Priority value used to select the best possible mode Attributes Null column allowed: No Default value: False Null column allowed: No Default value: Null column allowed: No Default value: False Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: 0 13.1.

1.13 CoordSys Table For the projection coordinate system and the database’s internal coordinate system ( this is the display coordinate system used when creating a database). 2= ideal FH. empty = all hopping modes MAL length Mobility (empty = all mobilities) Quality indicator name Attributes Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 13. Field CODE DATUM_CODE DATUM_ROTX DATUM_ROTY DATUM_ROTZ DATUM_SCALE DATUM_SHIFTX DATUM_SHIFTY DATUM_SHIFTZ ELLIPS_CODE ELLIPS_RMAJOR ELLIPS_RMINOR NAME PROJ_ANGLE PROJ_FALSE_EASTING PROJ_FALSE_NORTHING PROJ_FIRST_PARALLEL Type Integer Double Double Double Double Double Double Double Double Integer Double Double Text (50) Double Double Double Double Meters Meters Coordinate system name Decimal degrees Meters Meters Decimal degrees Arc-seconds Arc-seconds Arc-seconds Parts per million (ppm) Meters Meters Meters Description Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768) Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 239 .AT310_AM_E2 Atoll 3.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure Field CODEC_EQT CODEC_MODE FREQUENCY_BAND HOPPING MAL_LENGTH MOBILITY QI_NAME Type Text (50) Text (50) Text (20) Short Integer Text (50) Text (20) Description Codec equipment name Codec mode Frequency Band (empty = all bands) Frequency hopping 1=NH.

13. Field CAPTION CHOICE_LIST CHOICE_TYPE COLUMN_NAME DEFAULT_VALUE GROUP_NAME TABLE_NAME Type Text (50) Memo Integer Text (50) Text (50) Text (50) Text (50) Description Caption of the field (displayed instead of the name) Choice list for the field 0: Choice List is optional. "EGPRS2") Attributes Null column allowed: No Default value: 1 Null column allowed: No Default value: 0 Null column allowed: No Default value: 1 Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: ’GPRS’ 240 . Mercator.3: 16QAM. Table name Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: See "Tables and Fields" on page 130 for recommendations and information on user-defined fields. and choice lists. Lambert1SP. TransMercatorSO. Field name Default value for the field Name of the group to which that field belongs First part of the unique key. Lambert2SP. CassiniSoldner. EGPRS. NoProjection.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 Field PROJ_LATITUDE_ORIGIN PROJ_LONGITUDE_ORIGIN Type Double Double Description Decimal degrees Decimal degrees UTM.14 CustomFields Table For defining user-defined fields added to tables. captions. HotineOM.1: 8-PSK.1. 1: Turbo) Maximum rate obtained when there is no data transmission error Unit: kbps Modulation (0: GMSK. 2: QPSK. and EGPRS2 coding schemes. Field CS_NUMBER DATA_CODING MAX_THROUGHPUT MODULATION NAME TECHNOLOGY Type Short Short Float Short Text (50) Text (15) Description Coding scheme number Type of FEC coding (0: Convolutional. default values for any field (including user-defined fields). 1: Choice List is mandatory Second part of the unique key. TransMercator. ObliqueStereographic. 4: 32QAM) Name of the coding scheme Technology ("GPRS". "GPRS/EDGE". Undefined. NewZealandMapGrid. LabordeOM.15 EGPRSCodingSchemes Table For GPRS.Atoll 3. and group names for user-defined fields. SwissObliqueCylindical Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 PROJ_METHOD Short PROJ_SCALE_FACTOR PROJ_SECOND_PARALLEL PROJ_ZONE_NUMBER Double Double Integer Decimal degrees Used with UTM Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 13.

18 EGPRSEquipments Table For GPRS.1. Field NAME REFERENCE_NOISE TECHNOLOGY Type Text (50) Float Text (15) Description Equipment name Attributes Null column allowed: No Default value: Reference noise of the equipment which has been used to produce the Null column allowed: Yes curves Default value: -113 GSM.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure 13.19 EGPRSMobility Table For mobility types. Default value: GPRS 13. and EGPRS2 configurations. To allocate traffic to compatible transmitter Null column allowed: Yes mobile pair. Field MAX_CHANNELS MAX_TRXS_TO_ADD_FOR_P ACKET MIN_DEDICATED_PDCH NAME PDCH_BLOCKING_PROBA_KP I PDCH_DELAY_KPI PDCH_THROUGHPUT_MIN_K PI QUEUING_MODEL Type Text (4) Integer Integer Text (50) Boolean Boolean Boolean Text (50) Description Maximum number of TRXs that can be allocated Maximum allowed number of TRXs to add in order to reach required quality for packet switched services Minimum dedicated timeslots number for packet switched traffic Service Name Blocking probability KPI Service delay KPI Minimum throughput KPI Queuing model: Erlang B .16 EGPRSDimensioningModel Table For network dimensioning models. EGPRS. GPRS or GPRS/EDGE. Erlang C Attributes Null column allowed: No Default value: ’16’ Null column allowed: Yes Default value: 100 Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: No Default value: True Null column allowed: Yes Default value: ’Erlang B’ 13. Field NAME SPEED Type Text (50) Float Description Name of mobility type Average speed (km/h) Attributes Null column allowed: No Default value: Null column allowed: No Default value: 241 .AT310_AM_E2 Atoll 3.17 EGPRSEnvironmentDefs Table For traffic environment types. Field DENSITY ENVIRONMENT MOBILITY USER_PROFILE Type Float Text (50) Text (50) Text (50) Description Number of subscribers per km2 Environment name Type of mobility User profile Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: 13.

0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 13. Field AVAIL_CONNECTIONS DIMENSIONING_MODEL LOAD_BLOCKING_PROBA LOAD_DELAY LOAD_RF Type Float Text (50) Memo Memo Memo Description Number of available connections Name of the dimensioning model Set of values used to generate the chart Blocking=f(Load) Set of values used to generate the chart Delay=f(Load) Set of values used to generate the chart throughput reduction factor=f(Load) Attributes Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: ’1’ Null column allowed: Yes Default value: ’1’ Null column allowed: Yes Default value: ’1’ 13.20 EGPRSQuality Table For GPRS. and EGPRS2 performance graphs. Field C_THRESHOLD C_THROUGHPUTS COVERI_THRESHOLD COVERI_THROUGHPUTS CS_NAME EQUIPMENT FREQUENCY_BAND HOPPING MAL_LENGTH MOBILITY Type Float Memo Float Memo Text (10) Text (50) Text (20) Short Integer Text (50) Description Minimum power (C) required at the receiver in order for a coding scheme to be used Set of values used to generate throughput=f(C) graph Minimum carrier to interference ratio (C/I) required at the receiver in order for a coding scheme to be used Set of values used to generate the throughput=f(C/I) graph Coding scheme name Type of equipment Frequency Band (empty = all bands) Attributes Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: ’0’ Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Hopping mode corresponding to the curves ( 1=NH.21 EGPRSServiceQuality Table For graphs used for the packet-switched traffic dimensioning.1. EGPRS. 2= ideal FH.Atoll 3. GoS for circuit Null column allowed: Yes switched services Default value: 2 Maximum delay allowed for the service Null column allowed: Yes Default value: 1 242 .22 EGPRSServices Table For services. Field DL_ACTIVITY DL_MBR MAX_BLOCKING_RATE MAX_DELAY Type Float Float Float Float Description Activity factor for voice services on the downlink DL Maximum Throughput Attributes Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Maximum probability that a packet is blocked (delayed). empty = Null column allowed: Yes all hopping modes) Default value: MAL length Mobility (empty = all mobilities) Null column allowed: Yes Default value: Null column allowed: Yes Default value: 13.

0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure Field MAX_TS_SUPPORT MIN_THROUGHPUT MIN_THROUGHPUT_RATIO NAME REQ_AVERAGE_DL_RATE REQ_AVERAGE_UL_RATE TH_OFFSET TH_SCALE_FACTOR TYPE UL_ACTIVITY UL_MBR Type Integer Float Float Text (50) Float Float Float Float Short Float Float Description Maximum number of timeslots supported by the service Minimum user throughput requested for the service Dimensioning target of the % of surface where minimum throughput is reached Service Name Requested Average Downlink Rate (kbps) Requested Average Uplink Rate (kbps) Offset which should be added to the scale factor Percentage of end user throughput compared to MAC throughput Type of service (0: circuit. Field CODEC_EQUIPMENT DL_AVAIL_CARRIERS DL_AVAIL_TIME_SLOT DTX Type Text (50) Short Float Boolean Description Associated Codec Equipment (for voice services) Number of simultaneous carriers Number of timeslots the mobile terminal can multiplex in downlink DTX capability of terminal Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: True 243 . Field CALL_DURATION CALL_NUMBER DL_VOLUME SERVICE TERMINAL USER_PROFILE Type Float Float Float Text (50) Text (50) Text (50) Description Average duration of a call (for circuit switched services) Average number of calls per hour for circuit switched services or average number of sessions per hour for packet switched services Volume transferred on the downlink during a session (for packet switched services) Service that the subscriber may request Type of terminal used by the subscriber for the service User profile name Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: 13.24 EGPRSTerminals Table For terminal types.1. 2: circuit over packet) Activity factor for voice services on the uplink UL Maximum Throughput Attributes Null column allowed: Yes Default value: 4 Null column allowed: Yes Default value: 15 Null column allowed: Yes Default value: 95 Null column allowed: No Default value: ’1’ Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 95 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 13.AT310_AM_E2 Atoll 3. 1: packet.23 EGPRSServicesUsage Table For user profile parameters.

26 EGPRSUserProfiles Table For names of user profiles.Atoll 3.1. Field NAME Type Text (50) Description Name of the created user profile Attributes Null column allowed: No Default value: 13.25 EGPRSTrafficEnvironments Table For traffic environment clutter weighting.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 Field EGPRS_EQUIPMENT MAX_CS MAX_MCS NAME NOISE_FIGURE PMAX PRIMARY_BAND SAIC SECONDARY_BAND TECHNOLOGY Type Text (50) Short Short Text (50) Float Float Text (50) Boolean Text (50) Text (15) Description Associated GPRS/EDGE equipment (for PS services) Highest coding scheme (CS) available for GPRS Highest coding scheme (MCS) available for EDGE Terminal name Noise figure of the terminal Max power that can be used in UL (for UL calculations) Frequency band the mobile terminal is compatible with Terminal capability for Single Antenna Interference Cancellation (for future use) Frequency band the mobile terminal is compatible with (for dual-band mobile terminals) Technology supported by the mobile terminal Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 4 Null column allowed: Yes Default value: 12 Null column allowed: No Default value: Null column allowed: Yes Default value: 8 Null column allowed: Yes Default value: 33 Null column allowed: No Default value: Null column allowed: No Default value: False Null column allowed: Yes Default value: Null column allowed: Yes Default value: 13. Field CLUTTER_WEIGHTS NAME Type Binary Text (50) Description Internal binary format describing weights assigned to each clutter class Name of the created environment Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: 13. Field CONNECTOR_LOSSES_DL CONNECTOR_LOSSES_UL LOSS_PER_METER NAME Type Float Float Float Text (50) Description Feeder connector losses in downlink Feeder connector losses in uplink Feeder loss per meter Name of Feeder Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 244 .27 FeederEquipments Table For feeders.

29 FrequencyDomains Table For frequency bands belonging to frequency domains. FIRST+2*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. n is the greatest positive integer so that FIRST+n*STEP LAST. FIRST+STEP. FIRST+2*STEP. FIRST+n*STEP. Unique key.28 FrequencyBands Table For frequency bands. Field DOMAIN_NAME EXCLUDED EXTRA FIRST Type Text (50) Text (255) Text (225) Integer Description Called grouping scheme. Set of resource groups. …. FIRST+n*STEP. LAST Null column allowed: Yes and STEP (separated with commas) Default value: Frequencies to be added. Name of a Resource Group Group elements are: FIRST.30 FrequencyGroups Table For frequency groups belonging to frequency domains.AT310_AM_E2 Atoll 3. …. FIRST+STEP. …. FIRST+2*STEP. FIRST+STEP. Field FREQUENCY_BAND_NAME NAME Type Text (50) Text (50) Description Name of the frequency band on which domain is based Name of domain Attributes Null column allowed: No Default value: Null column allowed: No Default value: 13. Field CHANNEL_WIDTH EXCLUDED_CHANNELS FIRST_CHANNEL FREQUENCY LAST_CHANNEL MAX_CHANNEL_NUM MULTIPLEX_FACTOR NAME Type Double Text (255) Integer Double Integer Integer Integer Text (20) Description Width of each physical channel composing the frequency band Unit: kHz Physical channels you do not want to allocate Number of the first physical channel available in the network Frequency of the downlink carrier Unit: MHz Number of the last physical channel available in the network Extended Channel Offset (used for band E-GSM) Number of logical channels composing a physical channel Name of the frequency band Attributes Null column allowed: No Default value: 1 Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 1000 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: 1 Null column allowed: No Default value: 13. Attributes Null column allowed: No Default value: List of frequencies to be excluded from the series defined by FIRST. Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 1 LAST Integer NAME Text (50) STEP Integer 245 .1. It is forbidden for EXTRA and EXLUDED to have Null column allowed: Yes common numbers Default value: Group elements are: FIRST. Group elements are: FIRST.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure 13. FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST.

34 Layers Table For HCS layers. FIRST+n*STEP.33 InterNetChProtect Table For inter-network interference reduction factor graphs. n is the greatest positive integer so that FIRST+n*STEP LAST. FIRST+2*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Field ICP ITF_BW ITF_TECHNO V_BW Type Memo Double Text (50) Double Description Inter-network channel protection = f( Δ MHz) Interfering bandwidth (kHz) Interfering technology Victim bandwidth (kHz) Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: 0 13. Field DOMAIN_NAME EXCLUDED EXTRA FIRST Type Text (50) Text (225) Text (225) Integer Description Called grouping scheme. FIRST+STEP. FIRST+n*STEP. It is forbidden for EXTRA and EXLUDED to have common numbers Group elements are: FIRST. FIRST+STEP. name of a Resource Group Group elements are: FIRST. ….32 HSNGroups Table For HSN groups belonging to HSN domains. LAST and STEP (separated with commas) HSNs to be added. Attributes Null column allowed: No Default value: 13. FIRST+n*STEP. Field MAX_SPEED MIN_PRIORITY_POWER NAME Type Float Float Text (50) Description Threshold speed for a mobile considered eligible to reside on a layer Minimum power value for the HCS layer Name of the hierarchical cell structure layer Attributes Null column allowed: Yes Default value: 300 Null column allowed: Yes Default value: -130 Null column allowed: No Default value: 246 . FIRST+2*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. …. Unique key. Field NAME Type Text (50) Description Name of HSN (Hopping Sequence Number) domain. …. List of HSNs to be excluded from the series defined by FIRST. Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 1 LAST Integer NAME Text (50) STEP Integer 13.Atoll 3. FIRST+2*STEP. Group elements are: FIRST.1. FIRST+STEP.31 HSNDomains Table For names of HSN domains. Set of resource groups.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 13.

Field IMPORTANCE NEIGHBOUR STATUS TRANSMITTER Type Float Description Handover importance (for AFP use) Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Text (50) Second part of the unique key.35 Neighbours Table For intra-technology neighbour relations. First part of the unique key. 4=Symmetric. 1=Forbidden. 2=Co-site.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure Field PRIORITY Type Short Description Priority of the layer (largest value has the highest priority) Attributes Null column allowed: No Default value: 1 13. Choice list: 0=Forced. Integer Text (50) Type of constraint on the neighbourhood relationship. 1=Forbidden. Transmitters or cells Type of the neighbourhood (handover. Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: TRANSMITTER Text (50) 13. Constraint is used in automatic allocation.36 NeighboursConstraints Table For intra-technology neighbour allocation constraints. Field IMPORTANCE NEIGHBOUR STATUS Type Float Text (50) Integer Description Handover importance (for AFP use) Second part of the unique key. measurement…) Attributes Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 (Manual) Null column allowed: No Default value: Null column allowed: Yes Default value: REASON Integer TRANSMITTER TYPE Text (50) Text (50) 13.38 NeighboursExt Table For inter-technology neighbour relations. 1=Forced. Constraint is used in automatic allocation. List of neighbours from another project.1. 5=Distance. List of neighbours Reason of the neighbourhood Choice list: 0=Manual. Transmitters or cells 13. 6=Coverage. Choice list: 0=Forced. 247 . First part of the unique key. List of neighbours Type of constraint on the neighbourhood relationship. Field IMPORTANCE NEIGHBOUR Type Float Text (50) Description Handover importance (for AFP use) Second part of the unique key. 3=Adjacent.37 NeighboursConstraintsExt Table For inter-technology neighbour allocation constraints.AT310_AM_E2 Atoll 3. Transmitters or cells. First part of the unique key.

measurement…) TRANSMITTER TYPE Text (50) Text (50) 13.39 Networks Table For network-level parameters. 2=Co-site. List of neighbours from another project Integer Reason of the neighbourhood Choice list: 0=Manual.40 PropagationModels Table For propagation models. 6=Coverage.1.Atoll 3. 248 . etc. 3=Adjacent. Field DEFAULT_MODEL DEFAULT_RESOLUTION DMAX INTERFERERS_RX_THRESH NAME SHARED_RESULTS_FOLDER SYSTEM_ TECHNOLOGY THERMAL_NOISE Type Text (50) Float Float Float Text (50) Text (255) Text (50) Text (10) Float Shared results storage folder Name of the system Name of the technology Thermal noise Description Default propagation model Default calculation resolution Maximum radius for a cell Interferers' reception threshold Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: 50 Null column allowed: No Default value: -1 Null column allowed: Yes Default value: -130 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: ‘GSM’ Null column allowed: No Default value: ‘TDMA’ Null column allowed: Yes Default value: -121 13. Field Data Description Name Signature Type Type Binary Text (255) Text (50) Text (40) Text (50) Description Model specific parameters User defined Name of the propagation model Unique Global ID of last model update ProgID of the model Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: 13. First part of the unique key. 1=Forced. BLER. 5=Distance.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 Field IMPORTANCE NEIGHBOUR REASON Type Float Description Handover importance (for AFP use) Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 (Manual) Null column allowed: No Default value: Null column allowed: Yes Default value: Text (50) Second part of the unique key.). Transmitters or cells Type of the neighbourhood (handover. 4=Symmetric.41 QualityIndicators Table For quality indicators (BER.

5 Null column allowed: No Default value: 0 Null column allowed: No Default value: 13. Receiver antenna name (if empty an omni antenna is used) Height of the receiver Losses due to receiver radio equipment (up and downlink) Receiver name Attributes Null column allowed: No Default value: 18 Null column allowed: Yes Default value: Null column allowed: No Default value: 1. Field COMMENT_ MANUFACTURER MAX_AMPLIFIER_GAIN MAX_OUTPUT_DL MAX_OUTPUT_UL MIN_AMPLIFIER_GAIN NAME NOISE_FIGURE STEP_AMPLIFIER_GAIN TIME_DELAY Type Text (255) Text (50) Float Float Float Float Text (50) Float Float Float Description Comments Manufacturer of the repeater equipment Maximum gain of the amplifier (dB) Maximum downlink output power (dBm) Maximum uplink output power (dBm) Minimum gain of the amplifier (dB) Name of the repeater equipment Repeater noise Figure (dB) Step of amplifier gain (dB) Time delay in the equipment (microseconds) Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 90 Null column allowed: Yes Default value: 30 Null column allowed: Yes Default value: 12 Null column allowed: Yes Default value: 50 Null column allowed: No Default value: Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 5 249 .1. 2=CIR.42 Receivers Table For receiver parameters. Name of the managed quality indicator Flag which indicates if this indicator is used for PS services Flag which indicates if this QI must be interpolated or not Attributes Null column allowed: No Default value: True Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: No Default value: True Null column allowed: No Default value: True 13.43 RepeaterEquipments Table For repeater equipment.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure Field CS_QI MEAS_PARAM NAME PS_QI USE_INTERPOLATION Type Boolean Short Text (20) Boolean Boolean Description Flag which indicates if this indicator is used in CS services Name of the measured figure used for this QI determination Choice list: 1=C.AT310_AM_E2 Atoll 3. Field ADJ_CHANNEL_PROT ANTENNA HEIGHT LOSS NAME Type Float Text (50) Float Float Text (50) Description Protection against interfering signals from adjacent channels.

45 SecondaryAntennas Table For additional antennas. 13. The repeater EIRP taken into account in calculations is stored in the Repeaters table (the EIRP column of the Transmitters table is not used).Atoll 3.1.Fibre Name of the propagation model used to calculate prediction between donor and repeater Downtilt of the donor side antenna EIRP of the repeater If no equipment.Off air 2. Azimuth of the antenna Percentage of power dedicated to the secondary antenna Remote electrical tilt for secondary antenna Mechanical downtilt of the secondary antenna Attributes Null column allowed: No Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 250 .44 Repeaters Table For repeaters. Field ANTENNA AZIMUT PERCENT_POWER REDT TILT Type Text (50) Float Float Float Float Description Name of the antenna installed on the transmitter Second part of the unique key.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 13. the repeater is a passive component Name of the donor side feeder Length of donor side feeder Height of the donor side antenna Name of the donor side antenna Length of donor side uplink feeder Name of the transmitter (and of the transmitter used for coverage) Attributes Null column allowed: Yes Default value: 80 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: • • Repeater properties are saved in two tables: the donor-side parameters are in the Repeaters table and the coverage-side parameters in the Transmitters table.Microwave 3. Field AMPLIFIER_GAIN AZIMUT DONOR_CELLID DONOR_LINK_LOSS DONOR_LINK_TYPE DONOR_PROPAG_MODEL DOWNTILT EIRP EQUIPMENT_NAME FEEDER_NAME FEEDERLENGTH HEIGHT REC_ANTENNA REC_FEEDERLENGTH_UL TX_ID Type Float Float Text (50) Float Short Text (50) Float Float Text (50) Text (50) Float Float Text (50) Float Text (50) Description Gain of the amplifier Azimuth of the donor side antenna Name of the donor transmitter Loss (dB) between donor and donor side of the repeater 1.

AT310_AM_E2 Atoll 3. Field ALTITUDE COMMENT_ LATITUDE LONGITUDE NAME PYLON_HEIGHT SUPPORT_NATURE Type Float Text (255) Double Double Text (50) Float Short Description Real altitude Unit: m Additional information on the site Y coordinate X coordinate Site name Height of the pylon at site The nature of site. Second transmitter name in a symmetric relation. 3=Co-Site. 4=Neighbour Type of TRX or All Type of TRX or All Attributes Null column allowed: No Default value: 1 Null column allowed: No Default value: 1 Null column allowed: No Default value: ’All’ Null column allowed: No Default value: ’All’ 13. First transmitter subcell or All Second transmitter subcell or All First transmitter name in a symmetric relation.46 SeparationRules Table For default separation constraints between each type of subcells.47 Separations Table For separation constraints between types of subcells.1. 2=Co-Cell. Field DEFAULT_MIN_SEP RELATION_TYPE TRX_TYPE TRX_TYPE_OTHER Type Short Short Text (15) Text (15) Description Minimum separation requirement Type of the relation : 1=Co-Subcell. Field MIN_SEP TRX_TYPE TRX_TYPE_OTHER TX_ID TX_ID_OTHER Type Integer Text (15) Text (15) Text (50) Text (50) Description Minimum separation requirement.48 Sites Table For sites. This field is for information only Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 50 Null column allowed: Yes Default value: 0 251 . Attributes Null column allowed: No Default value: 1 Null column allowed: No Default value: “All” Null column allowed: No Default value: “All” Null column allowed: No Default value: Null column allowed: No Default value: 13. Transmitter name Attributes Null column allowed: No Default value: 13.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure Field TX_ID Type Text (50) Description First part of the unique key.

0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 13.50 SitesListsNames Table For names of site lists. Name of the list Second part of the unique key.NAME. Field DL_LOSSES NAME NOISE_FIGURE UL_GAIN Type Float Text (50) Float Float Description Downlink losses of Tower Mounted Amplifier Name of Tower Mounted Amplifier Noise figure of Tower Mounted Amplifier Uplink gain of Tower Mounted Amplifier Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 13.52 TplTransmitters Table For station templates.1.Atoll 3. Field ACTIVE ANTENNA_NAME AZIMUT BSIC_DOMAIN BTS_NAME CALC_RADIUS CALC_RADIUS2 CALC_RESOLUTION CALC_RESOLUTION2 CELL_RESELECT_OFFSET Type Boolean Text (50) Float Text (50) Text (50) Integer Integer Integer Integer Integer Description Transmitter activity: 'Yes' means that the transmitter is active Name of the main antenna installed on the transmitter Azimuth of the first antenna Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: A text field pointing to ResourceGroups. Field NAME Type Text (50) Description Name of the list Attributes Null column allowed: No Default value: 13. Default value: Name of the BTS equipment Calculation radius used to define each transmitter calculation area Unit: m Extended calculation radius Unit: m Calculation resolution Extended calculation resolution Cell reselection offset Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 252 .49 SitesLists Table For sites belonging to site lists. Field LIST_NAME SITE_NAME Type Text (50) Text (50) Description First part of the unique key. Name of the site Attributes Null column allowed: No Default value: Null column allowed: No Default value: 13.51 TMAEquipments Table For tower-mounted amplifiers. It limits the BSIC domain Null column allowed: Yes of the site.

takes precedence on the threshold value defined in the HCSLayers table Losses due to transmitter radio equipment Unit: dB Maximum number of inter-technology neighbours for the cell or the transmitter Maximum number of neighbours for the cell or the transmitter Maximum range (m) of coverage (for extended cells) Minimum range (m) of coverage (for extended cells) Miscellaneous downlink losses Miscellaneous uplink losses Template name Number of sectors Cell reselection offset for GPRS cells with PBCCH in use (For future use) Packet Broadcast Control Channel used or not (For future use) Reception threshold value for GPRS cells with PBCCH in use (For future use) Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 3 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: CODEC_EQUIPMENT CODING_SCHEME_NUMBER COMMENT_ EGPRS_EQUIPMENT EIRP ENABLE_EGPRS FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL FN_OFFSET HEIGHT LAYER LAYER_RECEPTION_THRESH OLD LOSSES MAX_EXT_NEIGHB_NUMBER MAX_NEIGHB_NUMBER MAX_RANGE MIN_RANGE MISCDLL MISCULL NAME NUM_SECTORS PBCCH_CELL_RESELECT_OFF SET PBCCH_IN_USE PBCCH_RECEPTION_THRESH OLD Text (50) Short Text (255) Text (255) Float Boolean Text (50) Float Float Integer Float Text (50) Float Float Short Short Integer Integer Float Float Text (50) Integer Integer Boolean Float 253 .0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure Field CELL_SIZE Type Float Description Hexagon radius Unit: m Attributes Null column allowed: Yes Default value: CELL_TYPE Text (50) This field marks a set of records in the TRGConfigurations tables (all the Null column allowed: Yes records for which TRG_CONFIG has the same value. Associated Codec equipment (for voice services) The number of coding schemes supported by the GPRS/EDGE transmitters Comments Name of the equipment assigned to the GPRS/EDGE station Transmitter’s effective isotropic radiated power 'Yes' enables you to consider the transmitter as a GPRS/EDGE station Name of the feeder equipment Length of downlink feeder Unit: m Length of uplink feeder Unit: m Frame number offset Antenna height above the ground Unit: m Name of the Hierarchical Cell Structure layer If filled-in.1.) Each of these Default value: records specifies a TRG that should exist in this transmitter.AT310_AM_E2 Atoll 3.

1 = Interferer only) Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 13.Atoll 3.1.53 Transmitters Table For transmitters.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 Field POWER PROPAG_MODEL PROPAG_MODEL2 REDT REQ_CHANNELS SHAREDMAST TILT TMA_NAME TRX_MAX_NUMBER TX_TYPE Type Float Text (255) Text (255) Float Integer Text (50) Float Text (50) Short Short Description Transmitter power Name of the propagation model used to calculate predictions Name of the propagation model used to calculate extended prediction Remote Electrical tilt Number of required physical channels Shared mast name: enables antenna sharing between transmitters Mechanical downtilt of the main antenna Name of the Tower Mounted Amplifier equipment Maximum number of TRX that can be allocated by TRX dimensionning Type of transmitter (0 = Normal. AFP not allowed to modify BSIC. Field ACTIVE ANTENNA_NAME AZIMUT BSIC BSIC_DOMAIN BSIC_FROZEN BTS_NAME CALC_RADIUS CALC_RADIUS2 CALC_RESOLUTION CALC_RESOLUTION2 CELL_IDENTITY CELL_RESELECT_OFFSET CELL_SIZE Type Boolean Text (50) Float Text (10) Text (50) Boolean Text (50) Integer Integer Integer Integer Integer Integer Float Description Transmitter activity: 'Yes' means that the transmitter is active Name of the main antenna installed on the transmitter Azimuth of the main antenna BSIC colour code (Base Station Identity Code) assigned to the station A text field pointing at the BSIC domain. Name of the BTS equipment Calculation radius used to define the calculation area Unit: m Extended calculation radius Calculation resolution Extended calculation resolution Cell identity Cell reselection offset Hexagon radius Unit: m Attributes Null column allowed: No Default value: True Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: False Null column allowed: Yes Default value: Null column allowed: Yes Default value: 4000 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 50 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 2000 254 .

Only TRGs belonging to non-HSN-frozen cells. Name of the Hierarchical Cell Structure layer If filled-in. takes precedence on the threshold value defined in the HCSLayers table Losses due to transmitter radio equipment Unit: dB Maximum number of inter-technology neighbours for the transmitter Maximum number of neighbours for the transmitter Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 43 Null column allowed: No Default value: False Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: False Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: False Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 255 . DCS1800_N_Normal Text (255) Text (50) Integer Text (255) Integer Double Float Float Text (50) Float Boolean Text (20) Text (50) Float Float Integer Boolean Float Text (50) Text (25) Boolean Text (50) Float Float Integer Integer Physical channels allocated to the transmitter Associated Codec equipment (for voice services) The number of coding schemes supported by the GPRS/EDGE transmitters Additional information about the transmitter Physical channel used as Broadcast Control Channel (BCCH) Used by the AFP assign priorities to transmitters X coordinate relative to the site location Y coordinate relative to the site location Name of the equipment assigned to the GPRS/EDGE station Transmitter’s effective isotropic radiated power 'Yes' enables you to consider the transmitter as a GPRS/EDGE station Name of the frequency band Name of the feeder equipment Length of feeder in DL Length of feeder in UL Frame Number offset Only TRXs that are not frozen and belong to non-frozen cells can be assigned frequencies by the AFP.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure Field CELL_TYPE CHANNELS CODEC_EQUIPMENT CODING_SCHEME_NUMBER COMMENT_ CONTROL_CHANNEL COST_FACTOR DX DY EGPRS_EQUIPMENT EIRP ENABLE_EGPRS FBAND FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL FN_OFFSET FROZEN HEIGHT HEXAGON_GROUP HOP_MODE HSN_FROZEN LAYER LAYER_RECEPTION_THRESH OLD LOSSES MAX_EXT_NEIGHB_NUMBER MAX_NEIGHB_NUMBER Type Description Attributes This field identifies a set of records in the TRGConfigurations tables (all Null column allowed: Yes Text (50) the records that point to this cell-type) each of these records specifies a Default value: TRG that should exist in this transmitter.AT310_AM_E2 Atoll 3. Antenna height above the ground Unit: m Group of hexagons used to create this transmitter The hopping mode of the default traffic TRG in this transmitter.1. and which have non_HSN_frozen configurations. can be assigned HSNs by the AFP.

54 TRGConfigurations Table For subcell types. 1 = Interferer only) Attributes Null column allowed: Yes Default value: 35000 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: False Null column allowed: Yes Default value: -102 Null column allowed: Yes Default value: Null column allowed: Yes Default value: ’Default model’ Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 16 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 NUM_TRX PBCCH_CELL_RESELECT_OFF SET PBCCH_IN_USE PBCCH_RECEPTION_THRESH OLD POWER PROPAG_MODEL PROPAG_MODEL2 REDT REQ_CHANNELS SHAREDMAST SITE_NAME TILT TMA_NAME TRX_MAX_NUMBER TX_ID TX_TYPE Float Integer Boolean Float Float Text (255) Text (255) Float Integer Text (50) Text (50) Float Text (50) Short Text (50) Short 13.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 Field MAX_RANGE MIN_RANGE MISCDLL MISCULL Type Integer Integer Float Float Description Maximum range (m) of coverage (for extended cells) Minimum range (m) of coverage (for extended cells) Miscellaneous DL loss Miscellaneous UL loss The total number of TRXs in this transmitter. Cell reselection offset for GPRS cells with PBCCH in use (For future use) Packet Broadcast Control Channel used or not (For future use) Reception threshold value for GPRS cells with PBCCH in use (For future use) Transmitter power Name of the propagation model used to calculate prediction Name of the propagation model used to calculate extended prediction Remote Electrical tilt Number of required TRXs Shared mast name: enables antenna sharing between transmitters Name of the site on which the transmitter is located (from the Sites table) Mechanical downtilt of the first antenna Name of the TMA equipment Maximum number of TRX that can be allocated by TRX dimensionning Transmitter name Type of transmitter (0 = Normal. it must correspond to the number of channels in the CHANNELS field. In the cases of no or Base band hopping.Atoll 3. Additional constraints on subcell quality (considered in AFP): maximum probability to have C/I lower than C_OVER_I_MIN.1. Field _8PSK_PWBCKFF ASSIGN_MODE BAD_QUAL_UB Type Float Text (25) Float Description Reduction of power due to 8PSK modulation One of the two options: «Free» or «Group constrained». Attributes Null column allowed: Yes Default value: 3 Null column allowed: No Default value: ‘Free’ Null column allowed: No Default value: 1 256 .

This is a default value of a subcell specific parameter. Average value of DL power control The percentage of traffic that is considered to overflow from the subcell. This is a default value of a subcell specific parameter. Second part of unique key Timeslot configuration If more than one antenna are used (TX_DIVERSITY_NBANT). Attributes Null column allowed: No Default value: 12 Null column allowed: No Default value: Null column allowed: No Default value: 1 Null column allowed: No Default value: True Null column allowed: No Default value: ‘Non Hopping’ Null column allowed: No Default value: -102 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 40 Null column allowed: No Default value: Null column allowed: No Default value: False Null column allowed: No Default value: 48 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 DEF_HOP_MODE Text (25) DEF_MIN_RECEPTION DEF_POWER_OFFSET DEF_TRX_EQUIPMENT FREQUENCY_DOMAIN HR_RATIO HSN_DOMAIN HSN_FROZEN MAXIMAL_MAL MEAN_POWER_CONTROL TRAFFIC_OVERFLOW_TARGE T TRX_TYPE TS_CONFIGURATION_NAME Float Float Text (25) Text (50) Float Text (50) Boolean Integer Float Float Text (15) Text (50) TX_DIVERSITY_MODE_DL Short TX_DIVERSITY_NBANT Short 13. It denotes the minimum received power required to be served by this subcell. The cost factor will be used to increase or decrease the importance of subcells of this configuration. Hopping mode can be “Non Hopping”.simultaneously (TXDiv) or 1. Field _8PSK_PWBCKFF AFP_BLOCKED_COST AFP_CONGESTION AFP_COST Type Float Float Float Float Description Power reduction due to 8PSK modulation Secondary AFP quality indicator Secondary AFP indicator depicting the spectral congestion state Main AFP quality indicator Attributes Null column allowed: Yes Default value: 3 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 257 . this field indicates if they are used 0. Only subcells that point to non-hsn_frozen configurations in nonhsn_frozen cells can by be assigned HSNs by the AFP. “Base Band Hopping”. Domains contain grouping info as well. Default TRX equipment of TRXs belonging to this subcell All frequencies assigned to TRXs of this configuration must belong to this domain. 2=TX diversity with 2 antennas.AT310_AM_E2 Atoll 3. 1. By default. or “Synthesized Hopping”.55 TRGs Table For subcells. Limitation on length of the MAL (Mobile allocation list).alternatively (antenna hopping) TX diversity Choice list: 1=No TX diversity. Percentage of Half Rate voice traffic in the subcell. This is a default value of a subcell specific parameter: the average power offset with respect to the BCCH channel.1. All HSNs assigned to subcells of this configuration must belong to this domain.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure Field C_OVER_I_MIN CELL_TYPE COST_FACTOR DEF_DTX Type Float Text (50) Float Boolean Description Minimum C/I First part of unique key. It is set to true if the TRXs of the subcell use Discontinuous transmission This is a default value of a subcell specific parameter.

Null column allowed: Yes Default value: ‘Non Hopping’ Null column allowed: Yes Default value: 40 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: False Null column allowed: Yes Default value: 48 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: -102 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: HR_RATIO HSN HSN_DOMAIN HSN_FROZEN MAXIMAL_MAL MEAN_POWER_CONTROL MIN_RECEPTION POWER_OFFSET PREFERRED_FREQ_GROUP PS_DATA_ERLANGS REQ_CHANNELS SYNCHRO_NAME Float Integer Text (50) Boolean Integer Float Float Float Text (50) Float Integer Text (50) 258 . All HSNs assigned to subcells of this configuration must belong to this domain. Default value: 1 Blocking probability (%) Minimum C/I By default. “Base Band Hopping”. Downlink Gain due to DTX (dB) Effective traffic overflow List of frequencies which should not be used by TRX of the current subcell. 1. Percentage of Half rate traffic in the subcell. Only subcells that point to non-hsn_frozen configurations in nonhsn_frozen cells can be assigned HSNs by the AFP.Atoll 3. The cost factor is used to increase or decrease the importance of subcells of this configuration. Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 12 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: True Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: All frequencies assigned to TRXs of this configuration must belong to this Null column allowed: Yes domain. Circuit switched demand in Erlangs Default TRX equipment of TRXs belonging to this subcell It is set to true if the TRXs of the subcell use Discontinuous transmission. Frequency group which should be used if possible Packet switched demand in data Erlangs (equivalent to avaraged used time slots) Number of required channels. The average power offset with respect to the BCCH channel. Defines synchronization sets. Assigned HSN. Average value of DL power control Minimum reception power required to be served by this subcell. Attributes Null column allowed: No Default value: False Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: ‘Free’ Additional constraints on subcell quality (considered in AFP): maximum Null column allowed: Yes probability to have C/I lower than C_OVER_I_MIN. Domains contain grouping info as well.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 Field AFP_FREEZE_DIM AFP_SEP_COST ASSIGN_MODE BAD_QUAL_UB BLOCKING_PROBA C_OVER_I_MIN COST_FACTOR CS_ERLANGS DEF_TRX_EQUIPMENT DTX DTX_GAIN_DL EFFECTIVE_TRAFFIC_OVERFL OW EXCLUDED FREQUENCY_DOMAIN HOP_MODE Type Boolean Float Text (25) Float Float Float Float Float Text (25) Boolean Float Float Text (250) Text (50) Text (25) Description Permit the AFP to not always respect the number of required TRXs Secondary AFP quality indicator One of the two options: “Free” or “Group constrained”. or “Synthesized Hopping”. Limitation on length of the MAL (Mobile allocation list). Default value: The hopping mode of a subcell can be “Non Hopping”.1.

Subcell’s Uplink Traffic load Attributes Null column allowed: No Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 1 TX_DIVERSITY_MODE_DL Short TX_DIVERSITY_NBANT TX_ID UL_TRAFFIC_LOAD Short Text (50) Float 13. Multiplexing_factor = 8).56 TRXEquipments Table For TRX equipment. Points to the TRX type table. (separated with spaces) Inter-network downlink noise rise Allows/disallows changing parameters of this TRX.AT310_AM_E2 Atoll 3.57 TRXs Table For TRXs.simultaneously (TXDiv) or 1. this field indicates if they are used 0. The percentage of traffic that is considered to overflow from one subcell. 2=TX diversity with 2 antennas. (The cell type can be retrieved by following this link). Timeslot configuration If more than one antenna are used (TX_DIVERSITY_NBANT). First part of a unique key. Field _8PSK_POWER COMMENT_ GMSK_POWER MAX_CS MAX_MCS NAME Type Float Text (100) Float Short Short Text (25) Description Nominal output power in 8PSK modulation Comments Nominal output power in GMSK modulation Highest coding scheme (CS) available for GPRS Highest coding scheme (MCS) available for EDGE Name of TRX equipment Attributes Null column allowed: Yes Default value: 44 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 47 Null column allowed: No Default value: 4 Null column allowed: No Default value: 12 Null column allowed: No Default value: 13. TRX equipment of this TRX Attributes Null column allowed: Yes Default value: 3 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: False Null column allowed: Yes Default value: Null column allowed: Yes Default value: 259 .1. Assigned MAIO (Mobile Allocation Index Offset).0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure Field TRAFFIC_LOAD TRAFFIC_OVERFLOW_TARGE T TRX_TYPE TS_CONFIGURATION_NAME Type Float Float Text (15) Text (50) Description TRAFFIC_LOAD = (Traffic in Erlangs) / (NUM_TRX * Multyplexing_factor ) (Where. Field _8PSK_PWBCKFF AFP_RANK CN_LIST DOWNLINK_EXTERNAL_NOIS E_RISE FROZEN MAIO TRX_EQUIPMENT Type Float Short Text (255) Float Boolean Integer Text (25) Description Reduction of power due to 8PSK modulation Rank of this TRX according to the AFP List of all frequencies assigned to a TRX. It is the transmitter to which this subcell belongs. Second part of a unique key.alternatively (antenna hopping) TX diversity Choice list: 1=No TX diversity.

The couple TX_ID. Field CIRCUIT_TS COMPOSITE_TS NAME PACKET_TS TRX_NUMBER Type Integer Integer Text (50) Integer Integer Description Number of timeslots that support circuit switched traffic Number of timeslots that support circuit and packet switched traffic Name of the configuration Number of timeslots that support packet switched traffic Zero based index of TRX Attributes Null column allowed: No Default value: 0 Null column allowed: No Default value: 8 Null column allowed: No Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 1 260 .1.60 TSConfigurations Table For timeslot configurations. The value of the field CELL_TYPE in the Transmitters table can therefore be retrieved and can serve in order to access relevant information in the TRGConfigurations table. the load balancing might fail. If they are in different pools.58 TRXTypes Table For TRX types (BCCH. Inter-network uplink noise rise Uplink noise rise Attributes Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 TX_ID Text (50) UPLINK_EXTERNAL_NOISE_R ISE UPLINK_NOISE_RISE Float Float 13. Indicates that a TRG_TYPE is the default traffic carrier (the OUTER zone).Atoll 3.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 Field TRX_NUMBER TRX_TYPE Type Integer Text (15) Description An order on TRXs in the same subcell. TCH. Tests in the code will verify that only one type is the default TCH. Field IS_BCCH IS_TCH_DEF NAME PRIORITY TRAFFIC_POOL Type Boolean Boolean Text (15) Short Short Description Indicates that a TRG_TYPE is the Common Broadcast carrier. Tests in the code will verify that only one type carries the broadcast.).59 TSConfigurationNames Table For names of timeslot configurations. etc. It points to Transmitters. Attributes Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 13. Field NAME Type Text (50) Description Name of the configuration Attributes Null column allowed: No Default value: 13. It is the second part of a unique key. TRG_TYPE is the key of the TRGs table to which this TRX belongs First part of a unique key. TCH_INNER. Type of TRX Priority of a certain type of TRX to carry traffic (largest value has the highest priority) All TRXs of the same pool can exchange traffic if they need to balance their loads.

1=dbµV. the database internal coordinate system. 1=Watts.AT310_AM_E2 Atoll 3. and the internal BSIC format. 2=dbµV/m. Projected coordinate system for geo data Reception unit when creating database Choice list: 0=dBm. Attributes Null column allowed: No Default value: Null column allowed: No Default value: 13.1. Name of the list. Field LIST_NAME TX_NAME Type Text (50) Text (50) Description First part of the unique key.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure 13. Name of the transmitter. Transmission unit when creating database Choice list: 0=dBm. Second part of the unique key.62 TxsListsNames Table For names of transmitter lists.63 Units Table For the reception and transmission units. Field BSIC_FORMAT COORD_SYSTEM GAIN_UNIT PROJECTION RECEPTION_UNIT TRANSMISSION_UNIT Type Integer Integer Integer Integer Integer Integer Description BSIC format Choice list: 0=Decimal. 1=dBi. 2=kWatts. Attributes Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: -1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: -1 Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 261 . Display coordinate system when creating database Unit used for gains (dBd or dBi) Choice list: 0=dBd. 1=Octal.61 TxsLists Table For transmitters belonging to transmitter lists. Field NAME Type Text (50) Description Name of the transmitter list Attributes Null column allowed: No Default value: 13. the projection coordinate system specified in the ATL document.

Atoll 3.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure © Forsk 2011 262 .1.

The following subsections list the tables in the UMTS HSPA template data structure.2 on page 264. and Figure 14. Figure 14.3 on page 265 depict the UMTS HSPA database structure. Figure 14.1 263 .AT310_AM_E2 Atoll 3.1: UMTS HSPA Template .1.1 on page 263.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure 14 UMTS HSPA Data Structure Figure 14.

2 264 .1.2: UMTS HSPA Template .Atoll 3.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 Figure 14.

1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure Figure 14.AT310_AM_E2 Atoll 3.3: UMTS HSPA Template .3 265 .

Attributes Null column allowed: No Default value: False Null column allowed: No Default value: 0 Type Text (50) Description Physical antenna name Attributes Null column allowed: Yes Default value: CustomFields Table Field CHOICE_TYPE Type Integer Description 0=Choice list is optional.8 to 3. 1=Dual-cell. 1=Transmit Diversity.1 Added Tables and Fields Antennas Table Field PHYSICAL_ANTENNA CdmaCells Field LOCKED_SC MIMO_SUPPORT Type Boolean Short Description Field used to freeze allocated SC of the cell during automatic allocation MIMO features supported: 0=None. 0=MAXC/I (MAx C/ I). 2=PF (Proportional Fair). 1=Dual-cell. 2=PF (Proportional Fair) Multi-carrier mode: 0=None. Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 2 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Type Text (255) Memo Short Short Text (50) Description Comments Multi-carrier HSDPA multi user gain MUG=f(#users) Scheduling algo used for HSDPA multi-carrier users. 1=Choice list is mandatory. 0=MAXC/I (MAx C/ I). Multi-carrier mode: 0=None.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 14. 1=RR (Round Robin). Attributes Null column allowed: Yes Default value: 0 HSUPAUECategories Field UE_CATEGORY_NAME Type Text (50) Description Name of the HSUPA UE category Attributes Null column allowed: Yes Default value: TplTransmitters Field COMMENT_ MC_HSDPA_MUG MC_HSDPA_SCHED_ALGO MULTI_CARRIER SHAREDMAST Transmitters Field MC_HSDPA_MUG MC_HSDPA_SCHED_ALGO MULTI_CARRIER SHAREDMAST Type Memo Short Short Text (50) Description Multi-carrier HSDPA multi user gain MUG=f(#users) Scheduling algo used for HSDPA multi-carrier users.1. 1=RR (Round Robin).Atoll 3.1 14. Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 266 .1 Changes in Data Structure From 2.1. 2=SU-MIMO.

HSSCCH Less operation. 1=Allowed. Guaranted downlink bit rate (kbps) Maximum downlink bit rate (kbps) Activity Factor for HSUPA users Guaranted uplink bit rate (kbps) Maximum uplink bit rate (kbps) Attributes Null column allowed: Yes Default value: 0.1.2 Deleted Tables and Fields AntennasLists Table • Table AntennasListsNames Table • Table Neighbours Table • RANK NeighboursConstraints Table • RANK NeighboursConstraintsExt Table • RANK NeighboursExt Table • RANK 267 . DL DRX / UL DTX. Continuous packet connectivity support: None. HS-FACH.AT310_AM_E2 Atoll 3.1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0. HS-FACH Attributes Null column allowed: Yes Default value: 0 14. HSSCCH Less operation. DL DRX / UL DTX. 1=Dual-cell. Name of the HSDPA UE category Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: UMTSServices Field ADPCH_ACTIVITY CARRIER_LIST CARRIER_SUPPORT CPC_SUPPORT DL_GBR DL_MBR EDPCH_ACTIVITY UL_GBR UL_MBR Type Float Text (50) Integer Short Float Float Float Float Float Description Activity Factor for HSDPA users List of preferred carrier numbers Carrier support type: 0=Prefered.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure UECategories Field MULTI_CARRIER UE_CATEGORY_NAME Type Short Text (50) Description Multi-carrier mode: 0=None.1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: UMTSTerminals Field CPC_SUPPORT Type Short Description Continuous packet connectivity support: None.

Field Beamwidth COMMENT_ CONSTRUCTOR DIAGRAM ELECTRICAL_TILT FMax FMin GAIN NAME PHYSICAL_ANTENNA Type Float Text (255) Text (50) Binary Float Double Double Float Text (50) Text (50) Description Antenna beamwidth Additional information about antenna Antenna manufacturer name Antenna horizontal and vertical patterns Antenna electrical tilt (for information) Maximum operating frequency of the antennas Unit: MHz Minimum operating frequency of the antenna Unit: MHz Antenna isotropic gain Unit: dBi Name of antenna Physical antenna name Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: The format of the binary field.2 Antennas Table For antennas.1. is described in the "RF 2D Antenna Pattern Format" on page 105. 14. Field CONFIG_DL_LOSSES Type Float Description Downlink losses due to the configuration of the BTS (duplexer and/or combiner) Attributes Null column allowed: Yes Default value: 0 268 . DIAGRAM.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 R99Bearers Table • • DL_CODING_FACTOR UL_CODING_FACTOR TplTransmitters Table • COV_PROBA Transmitters Table • COV_PROBA UMTSServices Table • • • CARRIER ENABLE_HSDPA ENABLE_HSUPA UMTSTerminals Table • HSUPA_DTX_SUPPORT 14.Atoll 3.3 BTSEquipments Table For NodeB equipment.

it is the maximum available power. Field ACTIVE AS_THRESHOLD CARRIER CELL_ID CELL_IDENTITY COMMENT_ DOWNLINK_EXTERNAL_NOIS E_RISE DYN_HS_SCCH_POWER_ALL OC DYN_HSDPA_POWER_ALLOC HS_SCCH_POWER HSDPA_MAX_CODES HSDPA_MAX_USERS HSDPA_MIN_CODES HSDPA_MUG_TABLE HSDPA_PWR HSDPA_SCHEDULER_ALGO HSPA_SUPPORT HSUPA_DLPOWER HSUPA_MAX_USERS HSUPA_UL_LOAD Type Boolean Float Integer Text (50) Integer Text (255) Float Boolean Boolean Float Short Short Short Memo Float Short Short Float Short Float Description Cell's activity: 'Yes' means that the cell is active Maximum difference with the best-server to enter active Set (dB) Carrier number Name of the cell Cell identity Additional information about the cell Inter-network downlink noise rise Allocation of power for HS-SCCH (True=Dynamic. ERGCH. In case of dynamic allocation. 2=HSPA.AT310_AM_E2 Atoll 3. 0=MAXC/I (MAx C/I).4 CDMACells Table For cells. False=Static) Allocation of power for HSDPA (True=Dynamic. False=Static) Value of power dedicated to a HS-SCCH channel. HSPA features supported: 0=None. E-HICH) Max number of HSUPA users managed simultaneously by the scheduler Uplink cell load factor due to HSUPA users: calculated by the WCDMA simulation algorithm Attributes Null column allowed: No Default value: True Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: True Null column allowed: No Default value: False Null column allowed: Yes Default value: Null column allowed: Yes Default value: 16 Null column allowed: Yes Default value: 64 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 2 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 15 Null column allowed: Yes Default value: 269 . 1=HSDPA. 1=RR (Round Robin). 2=PF (Proportional Fair). 3=HSPA+ Amount of power (dBm) dedicated to HSUPA DL channels (E-AGCH.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure Field CONFIG_UL_LOSSES NAME NOISE_FIGURE RHO_FACTOR Type Float Text (50) Float Short Description Uplink losses due to the configuration of the BTS (duplexer and/or combiner) Name of Base Station Equipment Noise figure of Base Station Rho factor to model self generated interference (100%=ideal) Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 100 14. Maximum number of HS-PDSCH codes Max number of HSDPA users managed simultaneously by the scheduler Minimum Number of HS-PDSCH codes Lookup table giving MUG=f(#users) Amount of power (dBm) dedicated to HSDPA Scheduling algo used for HSDPA users.

Number of HS-SCCH channels Number of served HSDPA users in the cell: calculated by the WCDMA simulation algorithm Number of served HSUPA users in the cell: calculated by the WCDMA simulation algorithm Power of other common channels except SCH Power of the pilot channel Maximum power supported by the transmitter Power Control Headroom (dB) for DCH (used in WCDMA simulation algorithm) Minimum reuse distance for scrambling codes Scrambling code domain name.1. Used in power control simulation MIMO features supported: 0=None. 2=SU-MIMO.5 CdmaEqptsHSUPARssUse Table For HSUPA resource consumption in site equipment. Power of the synchronisation (SCH) channel Scrambling code. 1=Transmit Diversity.Atoll 3. 270 .0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 Field LOCKED_SC MAX_DL_LOAD MAX_EXT_NEIGHB_NUMBER MAX_INTERCAR_NEIGHB_NB MAX_NEIGHB_NUMBER MAX_R99BEARER_DL_RATE MAX_R99BEARER_UL_RATE MAX_UL_LOAD MIMO_SUPPORT NUM_HS_SCCH NUM_HSDPA_USERS NUM_HSUPA_USERS OTHERS_CCH_POWER PILOT_POWER POWER_MAX PWR_HEADROOM REUSE_DIST SC_DOMAIN_NAME SCH_POWER SCRAMBLING_CODE TOTAL_POWER TX_ID UL_LOAD UL_REUSE_FACTOR UPLINK_EXTERNAL_NOISE_R ISE Type Boolean Float Integer Integer Integer Float Float Float Short Short Short Short Float Float Float Float Float Text (50) Float Integer Float Text (50) Float Float Float Description Field used to freeze allocated SC of the cell during automatic allocation Attributes Null column allowed: No Default value: False Maximum downlink load allowed (percentage of max power used). Used Null column allowed: Yes in power control simulation Default value: 50 Maximum number of inter-technology neighbours for the cell Maximum number of inter-carrier neighbours for this cell Maximum number of neighbours for the cell Max bearer rate available in DL (kbps) Max bearer rate available in UL (kbps) Maximum uplink load allowed (percentage). Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm Name of the transmitter Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm Uplink (I intra+ I extra)/ I intra: calculated by the WCDMA simulation algorithm Inter-network uplink noise rise Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1000 Null column allowed: Yes Default value: 1000 Null column allowed: Yes Default value: 75 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 30 Null column allowed: Yes Default value: 33 Null column allowed: Yes Default value: 43 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 21 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 14.

2=Random.) If true.7 CDMAEquipmentsCEsUse Table For channel elements consumption in site equipment. Used for combination of AS member contributions If true. selection of AS members is limited to the neighbours of the selected transmitter Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value: False Null column allowed: No Default value: 2048 Null column allowed: No Default value: 20 Null column allowed: No Default value: 40 Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: 1 Null column allowed: No Default value: False 14.1.) Number of channel elements used for UL overhead channels (pilot.. Field CHANNEL_ELTS_DL CHANNEL_ELTS_UL EQUIPMENT IUB_RATE_DL IUB_RATE_UL Type Integer Integer Text (50) Float Float Description Number of channel elements used for downlink Number of channel elements used for uplink First part of the unique key.. synchro. NodeBs of the site can manage compressed mode Supported rate per E1 line (kbps) Iub HSDPA Backhaul Overhead (%) Iub Common Transport Channel Backhaul Overhead per cell (rate in kps) Name of the manufacturer MUD factor for UL interference cancellation Equipment name Efficiency of the rake receiver.. Name of equipment Iub backaul rate for downlink (kbps) Iub backaul rate for uplink (kbps) Attributes Null column allowed: No Default value: 1 Null column allowed: No Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 15 Null column allowed: Yes Default value: 15 271 .0 Administrator Manual Chapter 14: UMTS HSPA Data Structure Field BEARER_INDEX CHANNEL_ELTS_UL EQUIPMENT IUB_RATE_UL Type Short Integer Text (50) Float Description Cell identity Inter-network downlink noise rise Name of the site equipment Inter-network uplink noise rise Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 15 14. Field CARRIER_SELECTION CES_OVERHEAD_DL CES_OVERHEAD_UL ENABLE_COMPRESSED_MOD E IUB_E1_RATE IUB_HSDPA_PERCENT IUB_OVERHEAD_DL MANUFACTURER MUD_FACTOR NAME RAKE_EFFICIENCY USE_NEIGHBOURS Type Short Integer Integer Boolean Float Short Float Text (50) Float Text (50) Float Boolean Description Attributes Carrier selection mode Null column allowed: No Choice list: 0=Min UL noise. synchro..AT310_AM_E2 Atoll 3. . . 3=Sequential. 1=Min DL power.6 CDMAEquipments Table For site equipment. Default value: 0 Number of channel elements used for DL overhead channels (pilot.

Atoll 3. NewZealandMapGrid. TransMercator. Attributes Null column allowed: No Default value: 14. CassiniSoldner.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 Field SERVICE Type Text (50) Description Second part of the unique key. NoProjection. ObliqueStereographic.1. Mercator. Lambert2SP. Field CODE DATUM_CODE DATUM_ROTX DATUM_ROTY DATUM_ROTZ DATUM_SCALE DATUM_SHIFTX DATUM_SHIFTY DATUM_SHIFTZ ELLIPS_CODE ELLIPS_RMAJOR ELLIPS_RMINOR NAME PROJ_ANGLE PROJ_FALSE_EASTING PROJ_FALSE_NORTHING PROJ_FIRST_PARALLEL PROJ_LATITUDE_ORIGIN PROJ_LONGITUDE_ORIGIN Type Integer Double Double Double Double Double Double Double Double Integer Double Double Text (50) Double Double Double Double Double Double Meters Meters Coordinate system name Decimal degrees Meters Meters Decimal degrees Decimal degrees Decimal degrees UTM. Service name.8 CoordSys Table For the projection coordinate system and the database’s internal coordinate system ( this is the display coordinate system used when creating a database). HotineOM. Lambert1SP. Undefined. TransMercatorSO. SwissObliqueCylindical Arc-seconds Arc-seconds Arc-seconds Parts per million (ppm) Meters Meters Meters Description Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768) Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Decimal degrees Null column allowed: Yes Default value: 0 PROJ_METHOD Short PROJ_SCALE_FACTOR PROJ_SECOND_PARALLEL Double Double 272 . LabordeOM.

Field CAPTION CHOICE_LIST CHOICE_TYPE COLUMN_NAME DEFAULT_VALUE GROUP_NAME TABLE_NAME Type Text (50) Memo Integer Text (50) Text (50) Text (50) Text (50) Description Caption of the field (displayed instead of the name) Choice list for the field 0=Choice list is optional.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure Field PROJ_ZONE_NUMBER Type Integer Description Used with UTM Attributes Null column allowed: Yes Default value: 0 14. captions. Second part of the unique key.1. default values for any field (including user-defined fields). 1=Choice list is mandatory.AT310_AM_E2 Atoll 3.11 FrequencyBands Table For frequency bands. Field name Default value for the field Name of the group to which that field belongs First part of the unique key. Table name Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: See "Tables and Fields" on page 130 for recommendations and information on user-defined fields. 14. and choice lists. and group names for user-defined fields. Field BAND_WIDTH FIRST_CARRIER FREQUENCY LAST_CARRIER NAME Type Double Integer Double Integer Text (50) Description Bandwidth (MHz) Number of the first carrier available on the network Average frequency of carriers Unit: MHz Number of the last carrier available on the network Name of the frequency band Attributes Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 2110 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 273 . Field CONNECTOR_LOSSES_DL CONNECTOR_LOSSES_UL LOSS_PER_METER NAME Type Float Float Float Text (50) Description Feeder connector losses in downlink Feeder connector losses in uplink Feeder loss per meter Name of Feeder Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 14.9 CustomFields Table For defining user-defined fields added to tables.10 FeederEquipments Table For feeders.

2: 64QAM) Peak RLC throughput (without BLER consideration) Transport Block Size (bits) Attributes Null column allowed: No Default value: 1 Null column allowed: Yes Default value: 5 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 14. Field BEST_BEARER_TABLE CQI_TABLE MOBILITY RX_EQUIP Type Memo Memo Text (50) Text (50) Description Tables BEST_BEARER_INDEX=f(CQI_HSPDSCH) Tables CQI=f(Quality) .12 HSDPABearers Table For HSDPA bearers. 1: 16QAM.13 HSDPABearerSelectTables Table For HSDPA bearer selection graphs. Field BEARER_INDEX DL_QI_TABLE MOBILITY QI_NAME RX_EQUIP Type Short Memo Text (50) Text (50) Text (50) Description Bearer index QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table UE mobility Name of the Quality Indicator Type of receiver of the User Equipment Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: “Standard” 14.15 HSPAMIMOConfigs Table For HSPA MIMO gains. 274 .Atoll 3.84 14.14 HSDPAQualityTables Table For HSDPA bearer performance graphs.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 Field SPREADING_WIDTH Type Double Description Spreading bandwidth definition Attributes Null column allowed: Yes Default value: 3.1. Quality defined by CQI_CPICH_BASED in Networks table UE mobility Type of receiver of the User Equipment Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: “Standard” 14. Field BEARER_INDEX HSPDSCH_NUM MODULATION RLC_PEAK_THROUGHPUT TRANSPORT_BL_SIZE Type Short Short Short Float Integer Description Unique key to address bearer Number of HS_PDSCH channels used Modulation (0: QPSK.

AT310_AM_E2 Atoll 3. Field BEARER_INDEX EDPDCH_NUM MIN_SF MODULATION RLC_PEAK_RATE TRANSPORT_BL_SIZE TTI_LENGTH Type Short Short Integer Short Float Integer Float Description Index of the bearer Number of E-DPDCH codes used Smallest Spreading Factor Modulation (0: QPSK.16 HSUPABearers Table For HSUPA bearers.1. 1: 16QAM) Peak RLC throughput (without BLER) Transport Block Size (bits) Duration of TTI (ms) Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 14.17 HSUPABearerSelection Table For HSUPA bearer selection thresholds. Field BEARER_INDEX EARLY_TERM_TABLE EC_NT_REQ MOBILITY REPEAT_NUM RX_EQUIP Type Short Memo Float Text (50) Integer Text (50) Description Index of the selected bearer Tables of probabilities of earlier termination=f(REPEAT_NUM) Required E-DPDCH Ec/Nt User’s mobility Number of retransmissions to ensure a correct transmission Reception equipment of the terminal Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: "Standard" 275 .0 Administrator Manual Chapter 14: UMTS HSPA Data Structure Field DL_DIVERSITY_GAIN HSDPA_BEARER_INDEX MAX_MIMO_GAIN_TABLE MIMO_RX_ANTENNAS MIMO_TX_ANTENNAS MOBILITY RX_EQUIP Type Float Short Memo Short Short Text (50) Text (50) Description Downlink diversity gain (D-TxAA) HSDPA Bearer index Maximum spatial multiplexing capacity gain graphs Number of reception antennas used for MIMO Number of transmission antennas used for MIMO UE mobility Type of receiver of the User Equipment Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: No Default value: ’Standard’ 14.

where MEAS_PARAM is read from the QualityIndicators table Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 1 Null column allowed: No Default value: "Standard" Null column allowed: Yes Default value: 14. 276 . Field BEARER_INDEX MOBILITY QI_NAME REPEAT_NUM RX_EQUIP UL_QI_TABLE Type Short Text (50) Text (50) Integer Text (50) Memo Description Bearer index User’s mobility Name of the Quality Indicator Number of retransmissions to ensure a correct transmission Reception equipment of the terminal QI=f(MEAS_PARAM).1.20 InterfReductionFactors Table For interference reduction factors between carriers. Field MAX_BLOCK_SIZE_10MS MAX_BLOCK_SIZE_2MS MAX_EDPDCH_NUM MIN_SF MODULATION TTI_2MS UE_CATEGORY UE_CATEGORY_NAME Type Integer Integer Short Integer Short Boolean Short Text (50) Description Maximum transport block size supported for TTI=10ms (bits) Maximum transport block size supported for TTI=2ms (bits) Maximum number of E-DPDCH codes for HSUPA Smallest Spreading Factor supported Modulation (0: QPSK.18 HSUPAQualityTables Table For HSUPA bearer performance graphs.19 HSUPAUECategories Table For HSUPA UE categories.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 14.Atoll 3. Field CARRIER1 CARRIER2 FACTOR Type Integer Integer Double Description First carrier Second carrier Interference reduction factor Attributes Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value: 200 14. 1: 16QAM) True if TTI=2ms is supported UE category for HSUPA Name of the HSUPA UE category Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: False Null column allowed: No Default value: Null column allowed: Yes Default value: 14.21 InterNetChProtect Table For inter-network interference reduction factor graphs.

6=Coverage. 277 . List of neighbours Type of constraint on the neighbourhood relationship. 3=Adjacent. First part of the unique key.23 NeighboursConstraints Table For intra-technology neighbour allocation constraints. First part of the unique key. 2=Co-site. Field FORCE_HHO IMPORTANCE NEIGHBOUR STATUS Type Boolean Float Text (50) Integer Description Force Handover type to hard handover in case of intra-carriers neighbours Handover importance (for AFP use) Second part of the unique key. 5=Distance. Field IMPORTANCE NEIGHBOUR Type Float Description Handover importance (for AFP use) Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Text (50) Second part of the unique key. 1=Forbidden. Constraint is used in automatic allocation.22 Neighbours Table For intra-technology neighbour relations.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure Field ICP ITF_BW ITF_TECHNO V_BW Type Memo Double Text (50) Double Description Inter-network channel protection = f( Δ MHz) Interfering bandwidth (kHz) Interfering technology Victim bandwidth (kHz) Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: 0 14. 1=Forced.AT310_AM_E2 Atoll 3.24 NeighboursConstraintsExt Table For inter-technology neighbour allocation constraints. Attributes Null column allowed: No Default value: False Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: TRANSMITTER Text (50) 14. Choice list: 0=Forced. 4=Symmetric. Transmitters or cells Type of the neighbourhood (handover. List of neighbours from another project. Field FORCE_HHO IMPORTANCE NEIGHBOUR Type Boolean Float Text (50) Description Force Handover type to hard handover in case of intra-carriers neighbours Handover importance (for AFP use) Second part of the unique key. Transmitters or cells.1. measurement…) Attributes Null column allowed: No Default value: False Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 (Manual) Null column allowed: No Default value: Null column allowed: Yes Default value: REASON TRANSMITTER TYPE Integer Text (50) Text (50) 14. List of neighbours Reason of the neighbourhood Choice list: 0=Manual.

First part of the unique key. 1=Forced.26 Networks Table For network-level parameters. Constraint is used in automatic allocation.Atoll 3.1. Field ADD_MRC_SOFTERSOFT COMPRESSED_DELTA_DL_Q UAL COMPRESSED_DELTA_UL_Q UAL COMPRESSED_ON_ECIO COMPRESSED_ON_RSCP COMPRESSED_THRESHOLD CQI_CPICH_BASED DEFAULT_HOGAIN_UL DEFAULT_MODEL DEFAULT_ORTHO_FACTOR DEFAULT_RESOLUTION DMAX HSDPA_NTISNTOT INTERFERERS_RX_THRESH Type Boolean Float Float Boolean Boolean Float Boolean Float Text (50) Float Float Float Boolean Float Description If true. 6=Coverage.25 NeighboursExt Table For inter-technology neighbour relations. Transmitters or cells Type of the neighbourhood (handover. measurement…) REASON Integer TRANSMITTER TYPE Text (50) Text (50) 14. HS-PDSCH and CPICH for CQI determination Interferers' reception threshold Attributes Null column allowed: No Default value: False Null column allowed: No Default value: 1 Null column allowed: No Default value: 1 Null column allowed: No Default value: True Null column allowed: No Default value: False Null column allowed: No Default value: -13 Null column allowed: No Default value: True Null column allowed: No Default value: 0 Null column allowed: Yes Default value: ‘Cost-Hata’ Null column allowed: No Default value: 0 Null column allowed: No Default value: 50 Null column allowed: No Default value: -1 Null column allowed: No Default value: False Null column allowed: Yes Default value: -130 278 . 4=Symmetric. Field IMPORTANCE NEIGHBOUR Type Float Description Handover importance (for AFP use) Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 (Manual) Null column allowed: No Default value: Null column allowed: Yes Default value: Text (50) Second part of the unique key. 5=Distance. First part of the unique key. gain due to MRC is taken into account for softer/soft cases Eb/Nt DL target overhead due to compressed mode activated Eb/Nt UL target overhead due to compressed mode activated Compressed mode activated on Ec/Io threshold (for future use) Compressed mode activated on RSCP threshold (for future use) Ec/Io threshold for compressed mode activation CQI determination ids based on CPICH quality (true) or on HS-PDSCH quality (false) Default soft handoff gain uplink Default propagation model Default orthogonality factor Default calculation resolution Maximum radius for a cell Nt includes or not pilot's signal for HS-SCCH. 3=Adjacent. Choice list: 0=Forced. 1=Forbidden.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 Field STATUS TRANSMITTER Type Integer Text (50) Description Type of constraint on the neighbourhood relationship. Transmitters or cells Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 14. 2=Co-site. List of neighbours from another project Reason of the neighbourhood Choice list: 0=Manual.

84 Null column allowed: No Default value: ‘UMTS’ Null column allowed: No Default value: ‘CDMA’ 14. Service Allowed DL min and max TCH powers are absolute values or relative to cell pilot power Cell total power is absolute value (dBm) or relative to Cell maximum power (%) RSCP threshold for compressed mode activation (for future use) Shared results storage folder Spreading width (MHz) Name of the system Name of the technology Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: No Default value: -100 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 3.). 4=DCH_EBNT. 2=CPICH_CI. BLER. Field CS_QI Type Boolean Description Flag which indicates if this indicator is used in CS services Name of the measured figure used for this QI determination Choice list: 1=CPICH_ECIO. 3=CPICH_ECNT.1.28 QualityIndicators Table For quality indicators (BER. etc.AT310_AM_E2 Atoll 3. 5=HSPDSCH_ECNT. Field Data Description Name Signature Type Type Binary Text (255) Text (50) Text (40) Text (50) Description Model specific parameters User defined Name of the propagation model Unique Global ID of last model update ProgID of the model Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: 14.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure Field IOISNTOT NAME NTISNTOT POWERS_RELATIVE_TO_PILO T PTOT_RELATIVE_TO_PMAX RSCP_COMPRESSED_THRESH OLD SHARED_RESULTS_FOLDER SPREADING_WIDTH SYSTEM_ TECHNOLOGY Type Boolean Text (50) Boolean Boolean Boolean Float Text (255) Float Text (50) Text (10) Description Io includes pilot signal or not Attributes Null column allowed: No Default value: True Null column allowed: No Default value: Nt includes pilot signal or not Cell paging and Synchro powers.27 PropagationModels Table For propagation models. Name of the managed quality indicator Flag which indicates if this indicator is used for PS services Flag which indicates if this QI must be interpolated or not Attributes Null column allowed: No Default value: True Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: No Default value: True Null column allowed: No Default value: True MEAS_PARAM Short NAME PS_QI USE_INTERPOLATION Text (20) Boolean Boolean 279 .

6 14.29 R99Bearers Table For release 99 bearers.1. 2: Conversational.30 Receivers Table For receiver parameters. 1: Interactive.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 14.31 RepeaterEquipments Table For repeater equipment.4: Streaming) Bearer nominal rate in uplink Unit: kbps Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 9.5 Null column allowed: No Default value: 0 Null column allowed: No Default value: 14. Field ADJ_CHANNEL_PROT ANTENNA HEIGHT LOSS NAME Type Float Text (50) Float Float Text (50) Description Protection against interfering signals from adjacent channels. 3: Background .Atoll 3.6 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 256 Null column allowed: No Default value: Null column allowed: Yes Default value: 21 For DL part of Bearer: Minimum transmitter power on traffic channel for Null column allowed: Yes the bearer not to exceed Default value: -20 Bearer type (0: Empty. Receiver antenna name (if empty an omni antenna is used) Height of the receiver Losses due to receiver radio equipment (up and downlink) Receiver name Attributes Null column allowed: No Default value: 18 Null column allowed: Yes Default value: Null column allowed: No Default value: 1. Field ACTIVE_SPREADING_FACTOR _DL DL_NOMINAL_BIT_RATE DPCCH_DPCH_RATIO_DL DPCCH_DPCH_RATIO_UL INACTIVE_SPREADING_FACT OR_DL NAME PTCH_MAX PTCH_MIN TYPE UL_NOMINAL_BIT_RATE Type Integer Float Float Float Integer Text (50) Float Float Short Float Description DL Spreading Factor for active users Bearer nominal rate in downlink Unit: kbps Ratio between DPCCH and DPCH powers in DL Ratio between DPCCH and DPCH powers in UL DL Spreading Factor for inactive users Bearer name For DL part of Bearer: Maximum transmitter power on traffic channel for the bearer not to exceed Attributes Null column allowed: Yes Default value: 256 Null column allowed: Yes Default value: 9. Field COMMENT_ MANUFACTURER MAX_AMPLIFIER_GAIN MAX_OUTPUT_DL Type Text (255) Text (50) Float Float Description Comments Manufacturer of the repeater equipment Maximum gain of the amplifier (dB) Maximum downlink output power (dBm) Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 90 Null column allowed: Yes Default value: 30 280 .

Field AMPLIFIER_GAIN AZIMUT DONOR_CELLID DONOR_LINK_LOSS DONOR_LINK_TYPE DONOR_PROPAG_MODEL DOWNTILT EQUIPMENT_NAME FEEDER_NAME FEEDERLENGTH HEIGHT REC_ANTENNA REC_FEEDERLENGTH_UL TOTAL_GAIN TOTAL_GAIN_UL TX_ID Type Float Float Text (50) Float Short Text (50) Float Text (50) Text (50) Float Float Text (50) Float Float Float Text (50) Description Gain of the amplifier Azimuth of the donor side antenna Name of the donor cell Loss (dB) between donor and donor side of the repeater 1. the repeater is a passive component Name of the donor side feeder Length of donor side feeder Height of the donor side antenna Name of the donor side antenna Length of donor side uplink feeder Total gain to be applied to donor cell pilot power Uplink total gain to be applied to mobile output power Name of the transmitter (and of the transmitter used for coverage) Attributes Null column allowed: Yes Default value: 80 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Repeater properties are saved in two tables: the donor-side parameters are in the Repeaters table and the coverage-side parameters in the Transmitters table.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure Field MAX_OUTPUT_UL MIN_AMPLIFIER_GAIN NAME NOISE_FIGURE STEP_AMPLIFIER_GAIN TIME_DELAY Type Float Float Text (50) Float Float Float Description Maximum uplink output power (dBm) Minimum gain of the amplifier (dB) Name of the repeater equipment Repeater noise Figure (dB) Step of amplifier gain (dB) Time delay in the equipment (microseconds) Attributes Null column allowed: Yes Default value: 12 Null column allowed: Yes Default value: 50 Null column allowed: No Default value: Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 5 14.AT310_AM_E2 Atoll 3.32 Repeaters Table For repeaters.Fibre Name of the propagation model used to calculate prediction between donor and repeater Downtilt of the donor side antenna If no equipment.Off air 2. 281 .Microwave 3.1.

Field ANTENNA AZIMUT PERCENT_POWER REDT TILT TX_ID Type Text (50) Float Float Float Float Text (50) Description Name of the antenna installed on the transmitter Second part of the unique key. Group elements are: FIRST. n is the greatest positive integer so that FIRST+n*STEP LAST.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 14.35 SecondaryAntennas Table For additional antennas. FIRST+2*STEP. Azimuth of the antenna Percentage of power dedicated to the secondary antenna Remote electrical tilt for secondary antenna Mechanical downtilt of the secondary antenna First part of the unique key. Set of scrambling code groups. FIRST+STEP. FIRST+STEP. Field DOMAIN_NAME Type Text (50) Description Resource domain name Attributes Null column allowed: No Default value: 14.33 ScramblingCodesDomains Table For names of scrambling code domains.36 Separations Table For scrambling code allocation constraints. FIRST+2*STEP. List of codes to be excluded from the series defined by FIRST. n is the greatest positive integer so that FIRST+n*STEP LAST. Called grouping scheme. FIRST+n*STEP. LAST and STEP (separated by blank characters) Codes to be added. Name of the scrambling code group Group elements are: FIRST. Group elements are: FIRST. n is the greatest positive integer so that FIRST+n*STEP LAST. ….1. Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 1 LAST Integer NAME Text (50) STEP Integer 14. FIRST+n*STEP. Field TX_ID Type Text (50) Description First part of the unique key. It is forbidden for EXTRA and EXLUDED to have common numbers. ….Atoll 3. FIRST+2*STEP.34 ScramblingCodesGroups Table For scrambling code groups belonging to scrambling code domains. FIRST+n*STEP. Transmitter name Attributes Null column allowed: No Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value: 14. …. Separator must be a blank character. First part of the unique key. First cell name in a symmetric relation Attributes Null column allowed: No Default value: 282 . FIRST+STEP. Field DOMAIN_NAME EXCLUDED EXTRA FIRST Type Text (50) Text (225) Text (225) Integer Description Second part of the unique key.

1.37 ServiceQualityTables Table For release 99 performance graphs. This field is for information only Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 256 Null column allowed: No Default value: 256 Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value: 12288 Null column allowed: No Default value: 12288 Null column allowed: No Default value: Null column allowed: Yes Default value: 50 Null column allowed: Yes Default value: 0 14. Field ALTITUDE CDMA_EQUIPMENT CHANNEL_ELEMENTS_DL CHANNEL_ELEMENTS_UL COMMENT_ LATITUDE LONGITUDE MAX_IUB_RATE_DL MAX_IUB_RATE_UL NAME PYLON_HEIGHT SUPPORT_NATURE Type Float Text (50) Integer Integer Text (255) Double Double Float Float Text (50) Float Short Description Real altitude Unit: m Equipment associated with the site Number of available channel elements for downlink Number of available channel elements for uplink Additional information on the site Y coordinate X coordinate Max Iub Backhaul rate for downlink Max Iub Backhaul rate for uplink Site name Height of the pylon at site The nature of site. Field DL_QI_TABLE MOBILITY QI_NAME RX_EQUIP SERVICE UL_QI_TABLE Type Memo Text (50) Text (50) Text (50) Text (50) Memo Description QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table UE mobility Name of the Quality Indicator Type of receiver of the User Equipment Name of the service (can be null for some QI) QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: “Standard” Null column allowed: No Default value: Null column allowed: Yes Default value: 14. Second cell name in a symmetric relation Attributes Null column allowed: No Default value: 14.39 SitesLists Table For sites belonging to site lists.AT310_AM_E2 Atoll 3. 283 .38 Sites Table For sites.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure Field TX_ID_OTHER Type Text (50) Description Second part of the unique key.

Field ACTIVE ANTDIVGAIN ANTENNA_NAME AS_THRESHOLD AZIMUT BTS_NAME CALC_RADIUS CALC_RADIUS2 CALC_RESOLUTION CALC_RESOLUTION2 CARRIERS Type Boolean Float Text (50) Float Float Text (50) Integer Integer Integer Integer Text (50) Description Transmitter activity: 'Yes' means that the transmitter is active Antenna diversity gain Unit: dB Name of the main antenna installed on the transmitter Max allowed difference with the best-server to enter the Active Set (dB) Azimuth of the first antenna Name of the BTS equipment Calculation radius used to define each transmitter calculation area Unit: m Extended calculation radius Unit: m Calculation resolution Extended calculation resolution Carriers used by the transmitter Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 284 .Atoll 3.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 Field LIST_NAME SITE_NAME Type Text (50) Text (50) Description First part of the unique key.40 SitesListsNames Table For names of site lists. Name of the list Second part of the unique key.41 TMAEquipments Table For tower-mounted amplifiers. Field DL_LOSSES NAME NOISE_FIGURE UL_GAIN Type Float Text (50) Float Float Description Downlink losses of Tower Mounted Amplifier Name of Tower Mounted Amplifier Noise figure of Tower Mounted Amplifier Uplink gain of Tower Mounted Amplifier Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 14. Field NAME Type Text (50) Description Name of the list Attributes Null column allowed: No Default value: 14.42 TplTransmitters Table For station templates. Name of the site Attributes Null column allowed: No Default value: Null column allowed: No Default value: 14.1.

AT310_AM_E2 Atoll 3. it is the maximum available power. 3: HSPA+ Amount of power (dBm) dedicated to HSUPA DL chanels (E-AGCH. Used Null column allowed: Yes in power control simulation Default value: Maximum number of inter-technology neighbours for the cell or the transmitter Null column allowed: Yes Default value: 285 . 2: HSPA. Maximum number of HS-PDSCH codes Max number of HSDPA users managed simultaneously by the scheduler Minimum Number of HS-PDSCH codes Lookup table giving MUG=f(#users) Amount of power (dBm) dedicated to HSDPA Scheduling algo used for HSDPA users. ERGCH. 1=RR (Round Robin). False=Static) Allocation of power for HSDPA (True=Dynamic. 0=MAXC/I (MAx C/I). cells' powers are shared for HSDPA users Number of channel elements for downlink Number of channel elements for uplink Comments Inter-network downlink noise rise Allocation of power for HS-SCCH (True=Dynamic.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure Field CDMA_EQUIPMENT CELL_SIZE CELLS_POWER_SHARING CHANNEL_ELEMENTS_DL CHANNEL_ELEMENTS_UL COMMENT_ DOWNLINK_EXTERNAL_NOIS E_RISE DYN_HS_SCCH_POWER_ALL OC DYN_HSDPA_POWER_ALLOC FBAND FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL HEIGHT HS_SCCH_POWER HSDPA_MAX_CODES HSDPA_MAX_USERS HSDPA_MIN_CODES HSDPA_MUG_TABLE HSDPA_PWR HSDPA_SCHEDULER_ALGO HSPA_SUPPORT HSUPA_DLPOWER HSUPA_MAX_USERS HSUPA_UL_LOAD MAX_DL_LOAD MAX_EXT_NEIGHB_NUMBER Type Text (50) Float Boolean Integer Integer Text (255) Float Boolean Boolean Text (50) Text (50) Float Float Float Float Short Short Short Memo Float Short Short Float Short Float Float Short Description CDMA equipment Hexagon radius Unit: m If true. E-HICH Max number of HSUPA users managed simultaneously by the scheduler Uplink transmitter load factor due to HSUPA users: calculated by the WCDMA simulation algorithm Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Maximum downlink load allowed (percentage of max power used). False=Static) Frequency band Name of the feeder equipment Length of downlink feeder Unit: m Length of uplink feeder Unit: m Antenna height above the ground Unit: m Value of power dedicated to a HS-SCCH channel. In case of dynamic allocation. 1: HSDPA. 2=PF (Proportional Fair) HSPA features supported: 0: None.

2=PF (Proportional Fair). 1=Dual-cell.1. 1=RR (Round Robin). Miscellaneous downlink losses Miscellaneous uplink losses Multi-carrier mode: 0=None.Atoll 3.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 Field MAX_INTERCAR_NEIGHB_NB MAX_IUB_RATE_DL MAX_IUB_RATE_UL MAX_NEIGHB_NUMBER MAX_R99BEARER_DL_RATE MAX_R99BEARER_UL_RATE MAX_UL_LOAD MC_HSDPA_MUG MC_HSDPA_SCHED_ALGO MISCDLL MISCULL MULTI_CARRIER NAME NOISE_FIGURE NUM_HS_SCCH NUM_HSDPA_USERS NUM_HSUPA_USERS NUM_RX_ANTENNAS NUM_SECTORS NUM_TX_ANTENNAS OTHERS_CCH_POWER PILOT_POWER POWER_MAX PROPAG_MODEL PROPAG_MODEL2 PWR_HEADROOM REDT Type Integer Float Float Short Float Float Float Memo Short Float Float Short Text (50) Float Short Short Short Short Integer Short Float Float Float Text (255) Text (255) Float Float Description Maximum number of inter-carrier neighbours for this cell Max Iub Backhaul rate for downlink Max Iub Backhaul rate for uplink Maximum number of neighbours for the cell or the transmitter Max bearer rate available in DL (kbps) Max bearer rate available in UL (kbps) Maximum uplink load allowed (percentage). Used in power control simulation Multi-carrier HSDPA multi user gain MUG=f(#users) Scheduling algo used for HSDPA multi-carrier users. Template name Noise figure used to determine the thermal noise at the transmitter Number of HS_SCCH channels Number of served HSDPA users in the cell: calculated by the WCDMA simulation algorithm Number of served HSUPA users in the cell: calculated by the WCDMA simulation algorithm Number of transmission antenna ports available at the transmitter Number of sectors Number of reception antenna ports available at the transmitter Power of common channels (except SCH) Power of the pilot channel Maximum power supported by the transmitter Name of the propagation model used to calculate predictions Name of the propagation model used to calculate extended prediction Power Control Headroom (dB) for DCH (used in WCDMA simulation algorithm) Remote Electrical tilt Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 3 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 286 . 0=MAXC/I (MAx C/ I).

AT310_AM_E2 Atoll 3.1. Losses in the downlink due to transmitter radio equipment Unit: dB Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm Uplink (I intra+ I extra)/ I intra: calculated by the WCDMA simulation algorithm Inter-network uplink noise rise Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 14. closed loop Maximum power sharable between sectors. open loop 3.TX div.TX div.No TX diversity 2.43 Transmitters Table For transmitters.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure Field REUSE_DIST RXLOSSES SC_DOMAIN_NAME SCH_POWER SHAREDMAST TILT TMA_NAME TOTAL_POWER TX_DIVERSITY_CFG TX_MAX_POWER TXLOSSES UL_LOAD UL_REUSE_FACTOR UPLINK_EXTERNAL_NOISE_R ISE Type Float Float Text (50) Float Text (50) Float Text (50) Float Integer Float Float Float Float Float Description Minimum reuse distance for scrambling codes Losses in the uplink due to transmitter radio equipment Unit: dB Scrambling code domain name Power of the synchronisation (SCH) channel Shared mast name: enables antenna sharing between transmitters Mechanical downtilt of the main antenna Name of the Tower Mounted Amplifier equipment Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm TX diversity configuration 1. Field ACTIVE ANTDIVGAIN ANTENNA_NAME AZIMUT BTS_NAME CALC_RADIUS CALC_RADIUS2 CALC_RESOLUTION CALC_RESOLUTION2 CELL_SIZE Type Boolean Float Text (50) Float Text (50) Integer Integer Integer Integer Float Description Transmitter activity: 'Yes' means that the transmitter is active Antenna diversity gain Name of the main antenna installed on the transmitter Azimuth of the main antenna Name of the BTS equipment Calculation radius used to define the calculation area Unit: m Extended calculation radius Calculation resolution Extended calculation resolution Hexagon radius Unit: m Attributes Null column allowed: No Default value: True Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 4000 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 50 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 2000 287 .

1. 1=RR (Round Robin). closed loop.Atoll 3. Noise figure used to determine the thermal noise at the transmitter Number of transmission antenna ports available at the transmitter Number of reception antenna ports available at the transmitter Attributes Null column allowed: No Default value: False Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 2 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 5 Null column allowed: No Default value: 1 Null column allowed: No Default value: 1 Null column allowed: Yes Default value: ’Default model’ Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: PROPAG_MODEL Name of the propagation model used to calculate prediction PROPAG_MODEL2 REDT RXLOSSES SHAREDMAST SITE_NAME TILT TMA_NAME TX_DIVERSITY_CFG Name of the propagation model used to calculate extended prediction Remote Electrical tilt Losses in the uplink due to transmitter radio equipment Shared mast name: enables antenna sharing between transmitters Name of the site on which the transmitter is located (from the Sites table) Mechanical downtilt of the first antenna Name of the TMA equipment TX diversity configuration: 1=No TX diversity. 3=TX Null column allowed: Yes div. 2=TX div. cells' powers are shared for HSDPA users Additional information about the transmitter X coordinate relative to the site location Y coordinate relative to the site location Frequency band Name of the feeder equipment Length of feeder in DL Length of feeder in UL Antenna height above the ground Unit: m Group of hexagons used to create this transmitter Multi-carrier HSDPA multi user gain MUG=f(#users) Scheduling algo used for HSDPA multi-carrier users.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 Field CELLS_POWER_SHARING COMMENT_ DX DY FBAND FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL HEIGHT HEXAGON_GROUP MC_HSDPA_MUG MC_HSDPA_SCHED_ALGO MISCDLL MISCULL MULTI_CARRIER NOISE_FIGURE NUM_RX_ANTENNAS NUM_TX_ANTENNAS Type Boolean Text (255) Float Float Text (50) Text (50) Float Float Float Text (50) Memo Short Float Float Short Float Short Short Text (255) Text (255) Float Float Text (50) Text (50) Float Text (50) Short Description If true. Default value: 0 288 . Miscellaneous DL loss Miscellaneous UL loss Multi-carrier mode: 0=None. 0=MAXC/I (Max C/ I). 1=Dual-cell. 2=PF (Proportional Fair). open loop.

Field MAX_BLOCK_SIZE MAX_HSPDSCH_NUM MIMO_SUPPORT MIN_INTERTTI_NUM MODULATION MULTI_CARRIER UE_CATEGORY UE_CATEGORY_NAME Type Integer Short Short Short Short Short Short Text (50) Description Maximum transport block size supported (bits) Maximum number of HS-PDSCH channels for HSDPA MIMO support: 0=None.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure Field TX_ID TX_MAX_POWER TXLOSSES Type Text (50) Float Float Description Transmitter name Maximum power sharable between sectors Losses in the downlink due to transmitter radio equipment Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: 43 Null column allowed: Yes Default value: 0 14. Name of the transmitter. 2=64QAM.1. Field LIST_NAME TX_NAME Type Text (50) Text (50) Description First part of the unique key. Multi-carrier mode: 0=None. UE category for HSDPA Name of the HSDPA UE category Attributes Null column allowed: Yes Default value: 26000 Null column allowed: Yes Default value: 5 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 14. 1=16QAM. Field NAME Type Text (50) Description Name of the type of receiver in the UE Attributes Null column allowed: No Default value: 289 .46 UECategories Table For HSDPA UE categories.44 TxsLists Table For transmitters belonging to transmitter lists. Field NAME Type Text (50) Description Name of the transmitter list Attributes Null column allowed: No Default value: 14. Name of the list. 1=MIMO.45 TxsListsNames Table For names of transmitter lists. 1=Dual-cell. Second part of the unique key.47 UERxEquipments Table For names of UE reception equipment. Attributes Null column allowed: No Default value: Null column allowed: No Default value: 14.AT310_AM_E2 Atoll 3. Minimum number of TTI between two TTI used Modulation: 0=QPSK.

Atoll 3. Field ADPCH_ACTIVITY BODY_LOSS CARRIER_LIST CARRIER_SUPPORT CPC_SUPPORT DL_ACTIVITY DL_DP DL_DPC DL_GBR DL_MBR DL_NPC Type Float Float Text (50) Integer Short Float Float Float Float Float Integer Description Activity Factor for HSDPA users Body loss List of preferred carrier numbers Carrier support type: 0=Prefered. 1=Allowed.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 14. HSSCCH Less operation. Continuous packet connectivity support: None.50 UMTSServices Table For services. Field DENSITY ENVIRONMENT MOBILITY USER_PROFILE Type Float Text (50) Text (50) Text (50) Description Number of subscribers per km2 Environment name Type of mobility Type of user profile Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: 14.49 UMTSMobility Table For mobility types.1.48 UMTSEnvironmentDefs Table For traffic environment types.1 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 290 . Field HSSCCH_ECNT MEAN_SPEED NAME TADD Type Float Float Text (50) Float Description HS-SCCH Ec/Nt target for HSDPA Mean mobile speed (km/h) used for HSDPA Type of mobility Minimum Ec/Io for best server selection Attributes Null column allowed: Yes Default value: -12 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: 14. DL DRX / UL DTX. HS-FACH Activity factor for circuit switched service on the downlink Packet inter arrival time (ms) on the downlink Reading time (distance) between two packet calls (ms) on the downlink Guaranted downlink bit rate (kbps) Maximum downlink bit rate (kbps) Number of packet calls during a session on the downlink Attributes Null column allowed: Yes Default value: 0.

Activity factor for circuit switched service on the uplink Packet inter arrival time (ms) on the uplink Reading time (distance) between two packet calls (ms) on the uplink Guaranted uplink bit rate (kbps) Maximum uplink bit rate (kbps) Number of packet calls during a session on the uplink Packet efficiency factor on the uplink Packet size (Bytes) on the uplink Uplink max Packet call size (kBytes) Uplink min Packet call size (kBytes) 'Yes' if the service supports soft handoff Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1500 Null column allowed: Yes Default value: 2000 Null column allowed: Yes Default value: 4 Null column allowed: Yes Default value: 0. 1=packet. 2=circuit over packet.1. 291 .1 Null column allowed: No Default value: True Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 95 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1500 Null column allowed: Yes Default value: 2000 Null column allowed: Yes Default value: 4 Null column allowed: No Default value: False 14.AT310_AM_E2 Atoll 3.51 UMTSServicesQuality Table For release 99 service access thresholds.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure Field DL_PACKET_EFFICIENCY DL_SP DL_SPC_MAX DL_SPC_MIN EDPCH_ACTIVITY ENABLE_DOWNGRADING NAME PRIORITY R99BEARER REQ_AVERAGE_DL_RATE REQ_AVERAGE_UL_RATE TH_OFFSET TH_SCALE_FACTOR TYPE UL_ACTIVITY UL_DP UL_DPC UL_GBR UL_MBR UL_NPC UL_PACKET_EFFICIENCY UL_SP UL_SPC_MAX UL_SPC_MIN USE_HANDOFF Type Float Integer Float Float Float Boolean Text (50) Integer Text (50) Float Float Float Float Short Float Float Float Float Float Integer Float Integer Float Float Boolean Description Packet efficiency factor on the downlink Packet size (Bytes) on the downlink Downlink max Packet call size (kBytes) Downlink min Packet call size (kBytes) Activity Factor for HSUPA users Service supports lower bearer than nominal bearer Service name Priority level of the service: parameter used in the WCDMA simulation Name of the R99 Bearer Requested Average Downlink Rate (kbps) Requested Average Uplink Rate (kbps) Offset to add to the above ratio Ratio between application throughput and RLC layer throughput Type of service: 0=circuit.

DL DRX / UL DTX. Field ACTIVE_SET_SIZE CPC_SUPPORT ENABLE_COMPRESSED_MOD E GAIN Type Short Short Boolean Float Description Maximum number of transmitters possibly connected to the receiver Continuous packet connectivity support: None. Field CALL_DURATION CALL_NUMBER DL_VOLUME Type Float Float Float Description Average duration of a call (for circuit switched services) Unit: s Average number of calls per hour for circuit switched services or average number of sessions per hour for packet switched services Data volume transferred on the downlink during a session (for packet switched services) Unit: Kbyte Service that the subscriber may request Type of terminal used by the subscriber for the service Data volume transferred on the uplink during a session (for packet switched services) Unit: Kbyte User profile name Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: SERVICE TERMINAL UL_VOLUME USER_PROFILE Text (50) Text (50) Float Text (50) 14. HS-FACH If true.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 Field DL_TARGET_QUAL DL_TGT_QUAL_DIVCLOSED DL_TGT_QUAL_DIVOPEN MOBILITY Type Float Float Float Text (50) Description Eb/Nt target on the downlink for a type of mobility Eb/Nt target on downlink in case of TX diversity closed loop Eb/Nt target on downlink in case of TX diversity open loop Second part of the unique key.52 UMTSServicesUsage Table For user profile parameters. the mobile connected to a compressed-mode-capable NodeB is able to manage compressed mode when necessary Receiver antenna gain Attributes Null column allowed: No Default value: 3 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: False Null column allowed: Yes Default value: 0 292 .Atoll 3. Name of the R99 Bearer Eb/Nt target on the uplink for a type of mobility Eb/Nt target on uplink in case of 2RX diversity Eb/Nt target on uplink in case of 4RX diversity 14. Type of mobility Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: “Standard” Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 RX_EQUIP SERVICE UL_TARGET_QUAL UL_TGT_QUAL_DIV2RX UL_TGT_QUAL_DIV4RX Text (50) Text (50) Float Float Float Type of receiver First part of the unique key.1.53 UMTSTerminals Table For terminals types. HSSCCH Less operation.

293 .AT310_AM_E2 Atoll 3. Field CLUTTER_WEIGHTS NAME Type Binary Text (50) Description Internal binary format describing weights assigned to each clutter class Name of the created environment Attributes Null column allowed: Yes Default value: Yes Null column allowed: No Default value: 14. Used for combination of Active Set member contributions Rho factor to model self generated interference Type of the User Equipment Receiver Secondary frequency band Category of the User Equipment for HSDPA Null column allowed: No Default value: 1 Null column allowed: Yes Default value: 21 Null column allowed: Yes Default value: -20 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: No Default value: 100 Null column allowed: Yes Default value: “Standard” Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 14.1. 2=HSPA.55 UMTSUserProfiles Table For names of user profiles.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure Field HSPA_SUPPORT HSUPA_UE_CATEGORY LOSS MUD_FACTOR NAME NOISE_FACTOR NOISE_FACTOR_SEC NUM_RX_ANTENNAS PMAX PMIN PRIMARY_BAND RAKE_EFFICIENCY RHO_FACTOR RX_EQUIP SECONDARY_BAND UE_CATEGORY Type Short Short Float Float Text (50) Float Float Short Float Float Text (50) Float Short Text (50) Text (50) Short Description HSPA features supported: 0=None. Field NAME Type Text (50) Description Name of the created user profile Attributes Null column allowed: No Default value: 14. the projection coordinate system specified in the ATL document.56 Units Table For the reception and transmission units. 1=HSDPA.54 UMTSTraficEnvironments Table For traffic environment clutter weighting. and the database internal coordinate system. Category of the User Equipment for HSUPA Receiver antenna loss Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Advanced Receiver Factor to model intra-cell interference reduction for Null column allowed: Yes HSDPA terminals only Default value: 0 Terminal name Noise figure used to determine the thermal noise at the receiver Null column allowed: No Default value: Null column allowed: Yes Default value: 8 Noise figure used to determine the thermal noise at the receiver (for the Null column allowed: Yes secondary frequency band) Default value: 8 Number of reception antenna ports available at the terminal Maximum receiver power on traffic channel Minimum receiver power on traffic channels Primary frequency band Efficiency of the rake receiver.

Transmission unit when creating database Choice list: 0=dBm. Projected coordinate system for geo data Reception unit when creating database Choice list: 0=dBm. 1=Watts. 2=kWatts.1. 2=dbµV/m. Attributes Null column allowed: Yes Default value: -1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: -1 Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 294 . 1=dbµV.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure © Forsk 2011 Field COORD_SYSTEM GAIN_UNIT PROJECTION RECEPTION_UNIT TRANSMISSION_UNIT Type Integer Integer Integer Integer Integer Description Display coordinate system when creating database Unit used for gains (dBd or dBi) Choice list: 0=dBd.Atoll 3. 1=dBi.

1 295 . Figure 15.1: LTE Template . and Figure 15. Figure 15.1.1 on page 295.3 on page 297 depict the LTE database structure.AT310_AM_E2 Atoll 3. The following subsections list the tables in the LTE template data structure.2 on page 296.0 Administrator Manual Chapter 15: LTE Data Structure 15 LTE Data Structure Figure 15.

Atoll 3.1.2: LTE Template .2 296 .0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 Figure 15.

1.1 15.1 Changes in Data Structure From 2.1. 1=Choice list is mandatory Attributes Null column allowed: Yes Default value: 0 FrequencyBands Table Field GUARD_BAND Type Float Description Guard band between carriers (MHz) Attributes Null column allowed: Yes Default value: 0 297 .AT310_AM_E2 Atoll 3.3: LTE Template .8 to 3.3 15.0 Administrator Manual Chapter 15: LTE Data Structure Figure 15.1 Added Tables and Fields Antennas Table Field PHYSICAL_ANTENNA Type Text (50) Description Physical antenna name Attributes Null column allowed: Yes Default value: CustomFields Table Field CHOICE_TYPE Type Integer Description 0=Choice list is optional.

FIRST+2*STEP. It is forbidden for EXTRA and EXLUDED to have common numbers. FIRST+STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. FIRST+STEP. 3.) Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 298 . FIRST+2*STEP. 4. FIRST+STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. …. 2. 6. 1. n is the greatest positive integer so that FIRST+n*STEP LAST. TDD: Special subframe configuration (0. 1=RSRP. FIRST+n*STEP. Group elements are: FIRST. 7. 1=Inter-carrier Attributes Null column allowed: Yes Default value: 0 Networks Table Field BS_SELECTION SSF_CONFIG Type Short Short Description Best server selection method: 0=RS C. Separator must be a blank character. FIRST+n*STEP. …. …. FIRST+2*STEP. FIRST+n*STEP. LAST and STEP (separated by blank characters) IDs to be added. Attributes Null column allowed: Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 1 LAST Integer NAME STEP Text (50) Integer Neighbours Table Field RELATION_TYPE Type Short Description Type of the neighbour relation: 0=Intra-carrier. Group elements are: FIRST. Name of the physical cell ID group in the domain Group elements are: FIRST.Atoll 3.1. 8.0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 lframeconfigs Table (New) Field N_RB_GROUP0 N_RB_GROUP1 N_RB_GROUP2 N_RB_TOTAL NAME Type Text (255) Text (255) Text (255) Short Text (50) lpcidomains Table (New) Field DOMAIN_NAME Type Text (50) Description Name of the physical cell ID domain Attributes Null column allowed: No Default value: Description Frequency blocks belonging to the first group (PSS ID 0) Frequency blocks belonging to the second group (PSS ID 1) Frequency blocks belonging to the third group (PSS ID 2) Number of frequency blocks for which the configuration is defined Name of the ICIC frame configuration Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: lpcigroups Table (New) Field DOMAIN_NAME EXCLUDED EXTRA FIRST Type Text (50) Text (225) Text (225) Integer Description Name of the physical cell ID domain List of IDs to be excluded from the series defined by FIRST. 5.

1.Fibre Name of the propagation model used to calculate prediction between donor and repeater Downtilt of the donor side antenna If no equipment.0 Administrator Manual Chapter 15: LTE Data Structure RepeaterEquipments Table (New) Field COMMENT_ MANUFACTURER MAX_AMPLIFIER_GAIN MAX_OUTPUT_DL MAX_OUTPUT_UL MIN_AMPLIFIER_GAIN NAME NOISE_FIGURE STEP_AMPLIFIER_GAIN TIME_DELAY Type Text (255) Text (50) Float Float Float Float Text (50) Float Float Float Description Comments Manufacturer of the repeater equipment Maximum gain of the amplifier (dB) Maximum downlink output power (dBm) Maximum uplink output power (dBm) Minimum gain of the amplifier (dB) Name of the repeater equipment Repeater noise Figure (dB) Step of amplifier gain (dB) Time delay in the equipment (microseconds) Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 90 Null column allowed: Yes Default value: 30 Null column allowed: Yes Default value: 12 Null column allowed: Yes Default value: 50 Null column allowed: No Default value: Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 5 Repeaters Table (New) Field AMPLIFIER_GAIN AZIMUT DONOR_CELLID DONOR_LINK_LOSS DONOR_LINK_TYPE DONOR_PROPAG_MODEL DOWNTILT EQUIPMENT_NAME FEEDER_NAME FEEDERLENGTH HEIGHT REC_ANTENNA REC_FEEDERLENGTH_UL TOTAL_GAIN TOTAL_GAIN_UL Type Float Float Text (50) Float Short Text (50) Float Text (50) Text (50) Float Float Text (50) Float Float Float Description Gain of the amplifier Azimuth of the donor side antenna Name of the donor cell Loss (dB) between donor and donor side of the repeater 1. the repeater is a passive component Name of the donor side feeder Length of donor side feeder Height of the donor side antenna Name of the donor side antenna Length of donor side uplink feeder Total gain to be applied to donor cell pilot power Uplink total gain to be applied to mobile output power Attributes Null column allowed: Yes Default value: 80 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 299 .Off air 2.Microwave 3.AT310_AM_E2 Atoll 3.

1=QPSK. 3=64QAM.1. 2=16QAM.Atoll 3.0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 Field TX_ID Type Text (50) T4GCells Table Description Name of the transmitter (and of the transmitter used for coverage) Attributes Null column allowed: No Default value: Field AAS_RESULTS AAS_USAGE FRAME_CONFIG NUM_DL_USERS NUM_UL_USERS PCI_DOMAIN_NAME Type Binary Float Text (50) Float Float Text (50) Description Angular distributions of downlink power Percentage of downlink traffic load carried by the smart antenna Name of the ICIC frame configuration Number of DL connected users for the cell Number of DL connected users for the cell Name of the physical cell ID domain Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: T4GServices Table Field DL_LOWEST_BEARER UL_LOWEST_BEARER Type Short Short Description The lowest bearer allowed to be used for this service in DL The lowest bearer allowed to be used for this service in UL Attributes Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1 T4GTerminals Table Field UE_CATEGORY Type Text (50) Description UE category Attributes Null column allowed: Yes Default value: T4GUECategories Table (New) Field BEST_MODULATION DL_TBS_MAX MAX_MIMO_RX_ANTENNAS NAME UL_TBS_MAX Type Short Float Short Text (50) Float Description Highest supported modulation in uplink Choice list: 0=BPSK. Maximum number of transport block bits per TTI in downlink Maximum number of reception antenna ports UE category name Maximum number of transport block bits per TTI in uplink Attributes Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 TplTransmitters Table Field COMMENT_ FRAME_CONFIG PCI_DOMAIN_NAME Type Text (255) Text (50) Text (50) Description Comments ICIC frame configuration Name of the physical cell ID domain Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 300 .

0 Administrator Manual Chapter 15: LTE Data Structure Field SA_NAME SHAREDMAST Type Text (50) Text (50) Description Name of the smart antenna equipment Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Transmitters Table Field SA_NAME SHAREDMAST Type Text (50) Text (50) Description Name of the smart antenna equipment Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 15. Field Beamwidth COMMENT_ CONSTRUCTOR DIAGRAM ELECTRICAL_TILT FMax FMin GAIN NAME Type Float Text (255) Text (255) Binary Float Double Double Float Text (50) Description Antenna beamwidth Additional information about the antenna Antenna manufacturer name Internal binary format containing the description of the antenna horizontal and vertical patterns Antenna electrical tilt Maximum frequency of created antenna Unit: MHz Minimum frequency of created antenna Unit: MHz Antenna isotropic gain Unit: dBi Name of antenna created in the current project Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 301 .1.AT310_AM_E2 Atoll 3.2 Deleted Tables and Fields Neighbours Table • FORCE_HHO NeighboursConstraints Table • FORCE_HHO TplTransmitters Table • • • • • ANTDIVGAIN CHANNEL CHANNEL_STATUS ID_STATUS PHY_CELL_ID Transmitters Table • ANTDIVGAIN 15.1.2 Antennas Table For antennas.

15.Atoll 3. Field CONFIG_DL_LOSSES CONFIG_UL_LOSSES NAME NOISE_FIGURE RHO_FACTOR Type Float Float Text (50) Float Float Description Downlink losses due to the configuration of the BTS (duplexer and/or combiner) Uplink losses due to the configuration of the BTS (duplexer and/or combiner) Name of Base Station Equipment Noise figure of Base Station Rho factor (not used) Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 15.3 BTSEquipments Table For eNodeB equipment.4 CoordSys Table For the projection coordinate system and the database’s internal coordinate system ( this is the display coordinate system used when creating a database).0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 Field PHYSICAL_ANTENNA Type Text (50) Description Physical antenna name Attributes Null column allowed: Yes Default value: The format of the binary field.1. DIAGRAM. Field CODE DATUM_CODE DATUM_ROTX DATUM_ROTY DATUM_ROTZ DATUM_SCALE DATUM_SHIFTX DATUM_SHIFTY DATUM_SHIFTZ ELLIPS_CODE ELLIPS_RMAJOR ELLIPS_RMINOR NAME Type Integer Double Double Double Double Double Double Double Double Integer Double Double Text (50) Meters Meters Coordinate system name Arc-seconds Arc-seconds Arc-seconds Parts per million (ppm) Meters Meters Meters Description Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768) Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 302 . is described in "RF 2D Antenna Pattern Format" on page 105.

Table name Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: See "Tables and Fields" on page 130 for recommendations and information on user-defined fields. Field CONNECTOR_LOSSES_DL CONNECTOR_LOSSES_UL Type Float Float Description Feeder connector losses in downlink Feeder connector losses in uplink Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 303 .AT310_AM_E2 Atoll 3. HotineOM. Lambert2SP. NoProjection. TransMercatorSO. Mercator. Field name Default value for the field Name of the group to which that field belongs First part of the unique key. 1=Choice list is mandatory Second part of the unique key. NewZealandMapGrid. Field CAPTION CHOICE_LIST CHOICE_TYPE COLUMN_NAME DEFAULT_VALUE GROUP_NAME TABLE_NAME Type Text (50) Memo Integer Text (50) Text (50) Text (50) Text (50) Description Caption of the field (displayed instead of the name) Choice list for the field 0=Choice list is optional. SwissObliqueCylindical Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 PROJ_METHOD Short PROJ_SCALE_FACTOR PROJ_SECOND_PARALLEL PROJ_ZONE_NUMBER Double Double Integer Decimal degrees Used with UTM Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 15. Undefined. 15. TransMercator. and choice lists. LabordeOM. default values for any field (including user-defined fields). CassiniSoldner. ObliqueStereographic.5 CustomFields Table For defining user-defined fields added to tables.6 FeederEquipments Table For feeders.0 Administrator Manual Chapter 15: LTE Data Structure Field PROJ_ANGLE PROJ_FALSE_EASTING PROJ_FALSE_NORTHING PROJ_FIRST_PARALLEL PROJ_LATITUDE_ORIGIN PROJ_LONGITUDE_ORIGIN Type Double Double Double Double Double Double Description Decimal degrees Meters Meters Decimal degrees Decimal degrees Decimal degrees UTM. Lambert1SP. and group names for user-defined fields.1. captions.

1=TDD.8 InterNetChProtect Table For inter-network interference reduction factor graphs. Physical channels you do not want to allocate Number of the first physical channel of the frequency band Guard band between carriers (MHz) Number of the last physical channel of the frequency band Number of resource blocks per channel Name of the frequency band Sampling frequency Unit: MHz UL frequency of the 1st channel Unit: MHz Attributes Null column allowed: No Default value: 28 Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: 2110 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: No Default value: Null column allowed: No Default value: 7. 304 .Atoll 3. Field ICP ITF_BW ITF_TECHNO V_BW Type Memo Double Text (50) Double Description Inter-network channel protection = f( Δ MHz) Interfering bandwidth (kHz) Interfering technology Victim bandwidth (kHz) Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: 0 15.0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 Field LOSS_PER_METER NAME Type Float Text (50) Description Feeder loss per meter Name of Feeder Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 15.1. Field ADJ_CHANNEL_PROT CHANNEL_WIDTH DL_FREQUENCY DUPLEXING_METHOD EXCLUDED_CHANNELS FIRST_CHANNEL GUARD_BAND LAST_CHANNEL N_RB NAME SAMPLING_FREQUENCY UL_FREQUENCY Type Float Double Double Short Text (255) Short Float Short Integer Text (50) Float Double Description Protection against interfering signals from adjacent channels Width of each physical channel composing the frequency band Unit: MHz DL frequency of the 1st channel Unit: MHz Duplexing method used in the frequency band Choice list: 0=FDD.68 Null column allowed: Yes Default value: 15.7 FrequencyBands Table For frequency bands.9 lframeconfigs Table For ICIC frame configurations.

…. FIRST+2*STEP. FIRST+2*STEP. Group elements are: FIRST.8 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 305 . FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST.1. Group elements are: FIRST. Field DOMAIN_NAME EXCLUDED EXTRA FIRST Type Text (50) Text (225) Text (225) Integer Description Name of the physical cell ID domain List of IDs to be excluded from the series defined by FIRST.0 Administrator Manual Chapter 15: LTE Data Structure Field N_RB_GROUP0 N_RB_GROUP1 N_RB_GROUP2 N_RB_TOTAL NAME Type Text (255) Text (255) Text (255) Short Text (50) Description Frequency blocks belonging to the first group (PSS ID 0) Frequency blocks belonging to the second group (PSS ID 1) Frequency blocks belonging to the third group (PSS ID 2) Number of frequency blocks for which the configuration is defined Name of the ICIC frame configuration Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 15. Separator must be a blank character.10 lpcidomains Table For physical cell ID domains. FIRST+n*STEP. FIRST+2*STEP. FIRST+STEP. FIRST+STEP. Mobility type for which the MUG table is defined. LAST and STEP (separated by blank characters) IDs to be added. FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. …. It is forbidden for EXTRA and EXLUDED to have common numbers. n is the greatest positive integer so that FIRST+n*STEP LAST. Attributes Null column allowed: Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 1 LAST Integer NAME STEP Text (50) Integer 15. Name of the physical cell ID group in the domain Group elements are: FIRST. Multi-user diversity gain table Name of the scheduler for which the MUG table is defined.11 lpcigroups Table For physical cell ID groups. Field DOMAIN_NAME Type Text (50) Description Name of the physical cell ID domain Attributes Null column allowed: No Default value: 15.AT310_AM_E2 Atoll 3.12 MUGTables Table For multi-user diversity gains of proportional fair schedulers. …. Attributes Null column allowed: No Default value: 16. FIRST+STEP. Field MAX_CINR MOBILITY MUG_TABLE SCHEDULER_NAME Type Float Text (50) Memo Text (30) Description C/(I+N) above which no MUG will be applied.

15 NeighboursConstraintsExt Table For inter-technology neighbour allocation constraints.1. Field IMPORTANCE NEIGHBOUR STATUS TRANSMITTER Type Float Text (50) Integer Text (50) Description Handover importance Neighbour cell or transmitter Constraint used in automatic allocation. Field IMPORTANCE NEIGHBOUR Type Float Text (50) Description Handover importance Neighbour cell Reason of the neighbourhood Choice list: 0=Manual. 6=Coverage. 1 = Forbidden. Field IMPORTANCE NEIGHBOUR Type Float Text (50) Description Handover importance Neighbour cell Attributes Null column allowed: Yes Default value: 1 Null column allowed: No Default value: 306 . 0 = Forced. Reference cell Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 15.16 NeighboursExt Table For inter-technology neighbour relations. 3=Adjacent. measurement…) Attributes Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 (Manual) Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: REASON Integer RELATION_TYPE TRANSMITTER TYPE Short Text (50) Text (50) 15. 1 = Forbidden. 1=Forced. 2=Co-site.13 Neighbours Table For intra-technology neighbour relations.14 NeighboursConstraints Table For intra-technology neighbour allocation constraints. 4=Symmetric. Type of the neighbour relation: 0=Intra-carrier. Reference cell Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 15. 5=Distance.0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 15.Atoll 3. Field IMPORTANCE NEIGHBOUR STATUS TRANSMITTER Type Float Text (50) Integer Text (50) Description Handover importance Neighbour cell Constraint used in automatic allocation. 1=Inter-carrier Reference cell Type of the neighbourhood (handover. 0 = Forced.

1 .0 Administrator Manual Chapter 15: LTE Data Structure Field REASON Type Integer Description Reason of the neighbourhood Choice list: 0=Manual. 1=Frame. 5. 3=Adjacent. 1.User Defined Shared results storage folder Switching point periodicity (TDD) Choice list: 0=Half Frame. 4. 3.Calculated from Max Power. 5=Distance. 2=Co-site. TDD: Special subframe configuration (0. 6=Coverage. Field AMS_SEL_CRITERION BS_SELECTION CELL_SELECTION DEFAULT_CP Type Short Short Short Short Description AMS criterion (0 . 1=Forced. 1 . 3 = Sequential) Default cyclic prefix Choice list: 0=Normal. Default propagation model Default calculation resolution Maximum radius for a cell Interferers' reception threshold Type of network Number of symbol durations per subframe for PDCCH overhead Margin Over Max Bearer Threshold defining C/I Target (dB) Average number of overhead resource blocks for PUCCH RS EPRE Definition Method 0 . 1=RSRP. 2 = Random. 4=Symmetric.17 Networks Table For network-level parameters. measurement…) Attributes Null column allowed: Yes Default value: 0 (Manual) Null column allowed: No Default value: Null column allowed: Yes Default value: TRANSMITTER TYPE Text (50) Text (50) 15. 6.Reference signal C/(I+N)) Best server selection method: 0=RS C. Serving cell selection method (0 = Min DL Load. 7. 8.1.Reference signal C/N. Reference cell Type of the neighbourhood (handover.AT310_AM_E2 Atoll 3.) Name of the system Name of the technlogy Thermal noise Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 2 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: "CostHata" Null column allowed: No Default value: 50 Null column allowed: No Default value: -1 Null column allowed: Yes Default value: -20 Null column allowed: No Default value: Null column allowed: No Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: 2 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: ‘LTE’ Null column allowed: No Default value: ‘OFDM’ Null column allowed: Yes Default value: -121 DEFAULT_MODEL DEFAULT_RESOLUTION DMAX INTERFERERS_RX_THRESH NAME PDCCH_SYMBOLS POWER_CONTROL_MARGIN PUCCH_AVG_NRB RS_EPRE_DEFINITION SHARED_RESULTS_FOLDER SP_PERIODICITY SSF_CONFIG SYSTEM_ TECHNOLOGY THERMAL_NOISE Text (50) Float Float Float Text (50) Short Float Float Short Text (255) Short Short Text (50) Text (10) Float 307 . 1 = Min UL Load. 1=Extended. 2.

1. Field ANTENNA HEIGHT LOSS NAME Type Text (50) Float Float Text (50) Description Receiver's antenna name (if empty an omni antenna is used) Height of the receiver Unit: m Losses due to receiver radio equipment (up and downlink) Unit: dB Name of the receiver Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: 1. BLER. etc.18 PropagationModels Table For propagation models. Name of the Quality Indicator Flag indicating whether the Quality Indicator is used for Data (PS) services Flag indicating whether the Quality Indicator must be interpolated or not Attributes Null column allowed: No Default value: True Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: True Null column allowed: No Default value: True 15.0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 15.19 QualityIndicators Table For quality indicators (BER.5 Null column allowed: No Default value: 0.). Null column allowed: No Default value: 15.Atoll 3.20 Receivers Table For receiver parameters. Field CS_QI MEAS_PARAM NAME PS_QI USE_INTERPOLATION Type Boolean Short Text (50) Boolean Boolean Description Flag indicating whether the Quality Indicator is used for Voice (CS) services Name of the measured figure used for this QI determination Choice list: 0=C. 1=CIR. Field Data Description Name Signature Type Type Binary Text (255) Text (50) Text (40) Text (50) Description Model specific parameters User defined Name of the propagation model Unique Global ID of last model update ProgID of the model Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: 15.21 RepeaterEquipments Table For repeater equipment. Field COMMENT_ MANUFACTURER MAX_AMPLIFIER_GAIN Type Text (255) Text (50) Float Description Comments Manufacturer of the repeater equipment Maximum gain of the amplifier (dB) Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 90 308 .

Microwave 3.0 Administrator Manual Chapter 15: LTE Data Structure Field MAX_OUTPUT_DL MAX_OUTPUT_UL MIN_AMPLIFIER_GAIN NAME NOISE_FIGURE STEP_AMPLIFIER_GAIN TIME_DELAY Type Float Float Float Text (50) Float Float Float Description Maximum downlink output power (dBm) Maximum uplink output power (dBm) Minimum gain of the amplifier (dB) Name of the repeater equipment Repeater noise Figure (dB) Step of amplifier gain (dB) Time delay in the equipment (microseconds) Attributes Null column allowed: Yes Default value: 30 Null column allowed: Yes Default value: 12 Null column allowed: Yes Default value: 50 Null column allowed: No Default value: Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 5 15.AT310_AM_E2 Atoll 3.1.22 Repeaters Table For repeaters. the repeater is a passive component Name of the donor side feeder Length of donor side feeder Height of the donor side antenna Name of the donor side antenna Length of donor side uplink feeder Total gain to be applied to donor cell pilot power Uplink total gain to be applied to mobile output power Name of the transmitter (and of the transmitter used for coverage) Attributes Null column allowed: Yes Default value: 80 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 309 .Off air 2.Fibre Name of the propagation model used to calculate prediction between donor and repeater Downtilt of the donor side antenna If no equipment. Field AMPLIFIER_GAIN AZIMUT DONOR_CELLID DONOR_LINK_LOSS DONOR_LINK_TYPE DONOR_PROPAG_MODEL DOWNTILT EQUIPMENT_NAME FEEDER_NAME FEEDERLENGTH HEIGHT REC_ANTENNA REC_FEEDERLENGTH_UL TOTAL_GAIN TOTAL_GAIN_UL TX_ID Type Float Float Text (50) Float Short Text (50) Float Text (50) Text (50) Float Float Text (50) Float Float Float Text (50) Description Gain of the amplifier Azimuth of the donor side antenna Name of the donor cell Loss (dB) between donor and donor side of the repeater 1.

25 Sites Table For sites. 2 – Best Bearer Null column allowed: Yes Default value: 2 15. 2 = Application Null column allowed: Yes Throughput Default value: 0 UL Bandwidth Allocation Target: 0 – Full Bandwidth.24 SecondaryAntennas Table For additional antennas. Field BEARER_SELECTION NAME SCHEDULING_METHOD TARGET_THROUGHPUT_DAT A TARGET_THROUGHPUT_VOI CE UL_BW_ALLOCATION Type Short Text (30) Short Short Short Short Description Attributes Bearer Selection Criterion: 0 – Bearer Index. 1 = Effective RLC Throughput.23 Schedulers Table For schedulers. Field ANTENNA AZIMUT PERCENT_POWER REDT TILT TX_ID Type Text (50) Float Float Float Float Text (50) Description Name of the antenna installed on the transmitter (from the Antennas table) Azimuth of the antenna Percentage of power dedicated to the secondary antenna Remote Electrical tilt of the secondary antenna Mechanical downtilt of the secondary antenna Transmitter name Attributes Null column allowed: No Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value: 15. Field ALTITUDE COMMENT_ LATITUDE LONGITUDE NAME Type Float Text (255) Double Double Text (50) Description Real altitude (user-defined) Unit: m Additional information about the site Y coordinate X coordinate Site name Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value: 310 . 15. 1 – Peak RLC Throughput. 3 = Max C/I Null column allowed: No Default value: Null column allowed: Yes Default value: 0 0 = Peak RLC Throughput. 2 = Round Robin.Atoll 3.0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 Repeater properties are saved in two tables: the donor-side parameters are in the Repeaters table and the coverage-side parameters in the Transmitters table. 1 = Proportional Demand.1. 2 = Application Null column allowed: Yes Throughput Default value: 0 0 = Peak RLC Throughput. 1 – Maintain Connection. 1 = Effective RLC Throughput. 2 Null column allowed: Yes – Effective RLC Throughput Default value: 0 Name of the scheduler 0 = Proportional Fair.

This field is for information only Attributes Null column allowed: Yes Default value: 50 Null column allowed: Yes Default value: 0 15.27 SitesListsNames Table For names of site lists.28 SmartAntennas Table For smart antenna equipment. Name of the site Attributes Null column allowed: No Default value: Null column allowed: No Default value: 15. Field NAME Type Text (50) Description Name of the list Attributes Null column allowed: No Default value: 15.29 SmartAntennasModels Table For smart antenna models. Field SA_DATA SA_DESCRIPTION SA_NAME SA_SIGNATURE SA_TYPE Type Binary Text (50) Text (50) Text (50) Text (50) Description Smart antenna model data Description of the smart antenna model Name of the smart antenna model Signature of the smart antenna model Type of the smart antenna model Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: 311 . Field BROADCAST_ANTENNA COMMENT_ NAME SA_MODEL Type Text (50) Text (255) Text (50) Text (50) Description Broadcast (main) antenna model for the smart antenna Comments Name of the Smart Antenna Smart antenna model used Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 15.1.26 SitesLists Table For sites belonging to site lists. Name of the list Second part of the unique key.AT310_AM_E2 Atoll 3. Field LIST_NAME SITE_NAME Type Text (50) Text (50) Description First part of the unique key.0 Administrator Manual Chapter 15: LTE Data Structure Field PYLON_HEIGHT SUPPORT_NATURE Type Float Short Description Height of the pylon at site The nature of site.

31 T4GBearers Table For bearers.30 T4GBearerQualityCurves Table For bearer performance graphs. Field AAS_RESULTS AAS_USAGE ACTIVE AMS_THRESHOLD Type Binary Float Boolean Float Description Angular distributions of downlink power Percentage of downlink traffic load carried by the smart antenna Cell's activity. C/(I+N) threshold for switching from spatial multiplexing to space-time transmit diversity Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: True Null column allowed: Yes Default value: 312 .32 T4GBearersRequiredCI Table For bearer selection thresholds. Name of the LTE radio bearer Spectral efficiency = Peak RLC Throughput per Hz Unit: bps/Hz Attributes Null column allowed: No Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 15. Field BEARER_INDEX MOBILITY QI_CURVE QI_NAME RX_EQUIP Type Short Text (50) Memo Text (50) Text (50) Description Bearer index Mobility type DL Quality QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table Name of the Quality Indicator Name of the reception equipment Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: 15.33 T4GCells Table For cells.Atoll 3. 1=QPSK. Field BEARERS_REQUIRED_COVERI MOBILITY RX_EQUIP Type Memo Text (50) Text (50) Description C/I required in DL for selecting a LTE bearer C/I_Req = f(Best(BEARER_INDEX)) CPE mobility Name of the reception equipment Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 15. Cell is active if true. Field BEARER_INDEX CODING_RATE MODULATION NAME SPECTRAL_EFFICIENCY Type Short Float Short Text (50) Float Description Modulation and coding scheme number Coding rate Modulation type Choice list: 0=BPSK. 2=16QAM.0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 15.1. 3=64QAM.

2 = Locked) Additional information about the cell The type of antenna diversity supported by the cell in downlink The type of antenna diversity supported by the cell in uplink Percentage of the downlink traffic load carried by the ICIC part of the cell Downlink cell traffic load Inter-network downlink noise rise Frequency band of the cell Name of the ICIC frame configuration Maximum difference in dB between the best server path loss and second best Server path loss to be considered in ICIC zone Inter -Cell Interference Coordination Support 0=None. 1 = Allocated. Manually specified by the user or calculated during simulations. 2 = Locked) Maximum traffic load allowed on downlink Maximum number of inter-technology neighbours for this cell Maximum number of intra-technology neighbours for this cell Max supported number of users for the cell Maximum traffic load allowed on uplink Noise rise received by cell edge traffic Uplink noise rise (dB).1. 1=Static DL.0 Administrator Manual Chapter 15: LTE Data Structure Field CELL_ID CHANNEL CHANNEL_STATUS COMMENT_ DIVERSITY_SUPPORT DIVERSITY_SUPPORT_UL DL_FFR_USAGE DL_LOAD DOWNLINK_EXTERNAL_NOIS E_RISE FBAND FRAME_CONFIG ICIC_DELTAPL_TH ICIC_SUPPORT ID_REUSE_MIN_DIST ID_STATUS MAX_DL_LOAD MAX_EXT_NEIGHB_NUMBER MAX_NEIGHB_NUMBER MAX_NUMBER_OF_USERS MAX_UL_LOAD NOISE_RISE_ICIC_UL NOISE_RISE_UL NUM_DL_USERS NUM_UL_USERS PBCH_POWER_OFFSET PCI_DOMAIN_NAME PDCCH_POWER_OFFSET Type Text (50) Integer Short Text (255) Short Short Float Float Float Text (50) Text (50) Float Short Float Short Float Integer Integer Integer Float Float Float Float Float Float Text (50) Float Description Name of the cell Channel number Channel allocation status (0 = Not allocated. 1 = Allocated. Number of DL connected users for the cell Number of UL connected users for the cell EPRE offset for PBCH with respect to RS EPRE Name of the physical cell ID domain EPRE offset for PDCCH with respect to RS EPRE Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 100 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 100 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 313 .AT310_AM_E2 Atoll 3. 2=Static UL The minimum reuse distance for the AFP and physical cell ID allocation Physical cell ID status (0 = Not allocated.

4.0.Atoll 3. 0.0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 Field PDSCH_POWER_OFFSET PHY_CELL_ID POWER RANK RS_EPRE RSRQ_THRES RX_EQUIPMENT SCH_POWER_OFFSET SCHEDULER SF_CONFIG TX_ID UL_FPC_CINR_MAX UL_FPC_FACTOR UL_FPC_NR_MAX UL_LOAD UL_MU_SM_GAIN UPLINK_EXTERNAL_NOISE_R ISE Type Float Integer Float Short Float Float Text (50) Float Text (50) Short Text (50) Float Float Float Float Float Float Description EPRE offset for PDSCH with respect to RS EPRE Physical cell ID Maximum output power Unit: dBm Zero based order used by scheduler for sequential cell selection Energy per resource Element of reference signals Required RSRP for coverage Reception equipment installed at the cell EPRE offset for SS with respect to RS EPRE Scheduler used by the cell Subframe configuration used by the cell in case of TDD frequency band Name of the transmitter to which the cell belongs Target PUSCH C/(I+N) provides Po_pusch and is driven by noise rise limitations of neighbouring cells.35 T4GEquipments Table For reception equipment.7.0. This field will be output from simulation.9.34 T4GEnvironmentDefs Table For traffic environment types.0. Field DENSITY ENVIRONMENT MOBILITY USER_PROFILE Type Float Text (50) Text (50) Text (50) Description Number of subscribers per km2 Environment name Type of mobility Type of user profile Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: 15. Factor enabling reduction of transmission powers of cell-edge users FPC Off.1 Maximum uplink noise rise Uplink cell traffic load Multi-user (collaborative) MIMO gain in uplink Inter-network uplink noise rise Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 43 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: -140 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 20 Null column allowed: No Default value: 1 Null column allowed: Yes Default value: 6 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 15.0.8.0.5.0. 314 .6.1.

1.0 Administrator Manual Chapter 15: LTE Data Structure Field NAME Type Text (50) Description Name of the reception equipment Attributes Null column allowed: No Default value: 15. Field MEAN_SPEED NAME Type Float Text (50) Description Mean mobile speed (km/h) used for HSDPA Type of mobility Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 15.37 T4GMobility Table For mobility types. Field BEARER_INDEX EQUIPMENT MAX_BLER MAX_MIMO_GAIN MIMO_RX_ANTENNAS MIMO_TX_ANTENNAS MOBILITY STTD_GAIN Type Short Text (50) Float Memo Short Short Text(50) Float Description Index of the LTE bearer Name of the equipment to which the MIMO gains correspond Maximum value of BLER for which the gains are applicable Graph of maximum MIMO gains vs. Field BODY_LOSS DL_ACTIVITY DL_DP DL_DPC DL_GBR DL_HIGHEST_BEARER DL_LOWEST_BEARER Type Float Float Float Float Float Float Short Description Losses due to the users body (dB) Activity factor for voice services on the downlink Packet inter-arrival time (ms) in downlink Reading time (distance) between two packet calls (ms) in downlink Minimum required transmission rate in DL (Guaranteed Bit Rate) The highest bearer allowed to be used for this service in DL The lowest bearer allowed to be used for this service in DL Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 15 Null column allowed: Yes Default value: 1 315 .AT310_AM_E2 Atoll 3.36 T4GMimoConfigs Table For MIMO gain graphs. C/(I+N) Number of MIMO antennas used for reception Number of MIMO antennas used for transmission User mobility Diversity gain that will be applied to the CINR (dB) Attributes Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 15.38 T4GServices Table For services.

Field CALL_DURATION Type Float Description Average duration of a call (for circuit switched services) Unit: s Attributes Null column allowed: Yes Default value: 316 .0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 Field DL_MBR DL_NPC DL_SP DL_SPC_MAX DL_SPC_MIN NAME PRIORITY REQ_AVERAGE_DL_RATE REQ_AVERAGE_UL_RATE TH_OFFSET TH_SCALE_FACTOR TYPE UL_ACTIVITY UL_DP UL_DPC UL_GBR UL_HIGHEST_BEARER UL_LOWEST_BEARER UL_MBR UL_NPC UL_SP UL_SPC_MAX UL_SPC_MIN Type Float Integer Integer Float Float Text (50) Short Float Float Float Float Short Float Float Float Float Float Short Float Integer Integer Float Float Description Maximum sustained trasmission rate in DL (Maximum Bit Rate) Number of packet calls during a session in downlink Packet size (Bytes) in downlink Downlink maximum packet call size (kBytes) Downlink minimum packet call size (kBytes) Service name Service priority (0: lowest) Requested Average Downlink Rate (kbps) Requested Average Uplink Rate (kbps) Offset to add to TH_SCALE_FACTOR Ratio between application level throughput and RLC layer throughput Service type Choice list: 0=Voice.Atoll 3.39 T4GServicesUsage Table For user profile parameters. Activity factor for voice services on the uplink Packet inter-arrival time (ms) in uplink Reading time (distance) between two packet calls (ms) in uplink Minimum required transmission rate in UL (Guaranteed Bit Rate) The highest bearer allowed to be used for this service in UL The lowest bearer allowed to be used for this service in UL Maximum sustained trasmission rate in UL (Maximum Bit Rate) Number of packet calls during a session in uplink Packet size (Bytes) in uplink Uplink maximum packet call size (kBytes) Uplink minimum packet call size (kBytes) Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1500 Null column allowed: Yes Default value: 2000 Null column allowed: Yes Default value: 4 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 95 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 15 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1500 Null column allowed: Yes Default value: 2000 Null column allowed: Yes Default value: 4 15. 1=Data.1.

Field ANTENNA DIVERSITY_SUPPORT GAIN LOSS MIMO_RX_ANTENNAS MIMO_TX_ANTENNAS NAME NOISE_FACTOR PMAX PMIN Type Text (50) Short Float Float Short Short Text (50) Float Float Float Description Receiver's antenna name (if empty an omni antenna is used) Antenna diversity support (0 = None.1.0 Administrator Manual Chapter 15: LTE Data Structure Field CALL_NUMBER DL_VOLUME SERVICE TERMINAL UL_VOLUME USER_PROFILE Type Float Float Text (50) Text (50) Float Text (50) Description Average number of calls per hour for circuit switched services or average number of sessions per hour for packet switched services Volume transferred on the downlink during a session (for packet switched services) Unit: Kbyte Service (from the Service table) that the subscriber may request Type of terminal (from the Terminal table) used by the subscriber for the service Volume transferred on the uplink during a session (for packet switched services) Unit: Kbyte User profile name Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 15.41 T4GTraficEnvironments Table For traffic environment clutter weighting.AT310_AM_E2 Atoll 3. 1 = MIMO) Terminal antenna gain (dB) Terminal antenna loss (dB) Number of MIMO antennas used for reception Number of MIMO antennas used for transmission Terminal name Noise figure used to determine the thermal noise at the receiver (dB) Maximum terminal power on traffic channel (dBm) Minimum terminal power on traffic channel (dBm) Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 8 Null column allowed: Yes Default value: 23 Null column allowed: Yes Default value: -40 Null column allowed: Yes Default value: "Default CPE Reception Equipment" Null column allowed: Yes Default value: RX_EQUIP Text (50) Name of the reception equipment available at the terminal UE_CATEGORY Text (50) UE category 15. Field CLUTTER_WEIGHTS NAME Type Binary Text (50) Description Internal binary format describing weights assigned to each clutter class Name of the created environment Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: 317 .40 T4GTerminals Table For terminal types.

3=64QAM. 1=QPSK. Field DL_LOSSES NAME NOISE_FIGURE UL_GAIN Type Float Text (50) Float Float Description Downlink losses of Tower Mounted Amplifier Name of Tower Mounted Amplifier Noise figure of Tower Mounted Amplifier Uplink gain of Tower Mounted Amplifier Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 15. 2=16QAM.43 T4GUserProfiles Table For names of user profiles. Field NAME Type Text (50) Description Name of the created user profile Attributes Null column allowed: No Default value: 15.42 T4GUECategories Table For UE categories.Atoll 3.45 TplTransmitters Table For station templates.0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 15. Field ACTIVE AMS_THRESHOLD ANTENNA_NAME AZIMUT BTS_NAME CALC_RADIUS CALC_RADIUS2 Type Boolean Float Text (50) Float Text (50) Integer Integer Description Transmitter activity: 'Yes' means that the transmitter is active CINR threshold in dB to switch from SM to STTD Name of the main antenna installed on the transmitter (from the Antennas table) Azimuth of the main antenna Name of the BTS equipment Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Calculation radius used to define each transmitter calculation area Unit: Null column allowed: Yes m Default value: Second calculation radius Unit: m Null column allowed: Yes Default value: 318 . Field BEST_MODULATION DL_TBS_MAX MAX_MIMO_RX_ANTENNAS NAME UL_TBS_MAX Type Short Float Short Text (50) Float Description Highest supported modulation in uplink Choice list: 0=BPSK.1. Maximum number of transport block bits per TTI in downlink Maximum number of reception antenna ports UE category name Maximum number of transport block bits per TTI in uplink Attributes Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 15.44 TMAEquipments Table For tower-mounted amplifiers.

AT310_AM_E2 Atoll 3. 1=Diversity. 3=AMS Type of diversity support used in uplink 0=None. 3=AMS. 2=Static UL The minimum reuse distance for the AFP and physical cell ID allocation Maximum traffic load allowed on downlink Maximum number of inter-technology neighbours Maximum number of intra-technology neighbours Max supported number of users for the cell Maximum traffic load allowed on uplink Miscellaneous downlink loss Miscellaneous uplink loss Template name Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 319 . 2=SU-MIMO.1. 1=Diversity. 2=SU-MIMO.0 Administrator Manual Chapter 15: LTE Data Structure Field CALC_RESOLUTION CALC_RESOLUTION2 CELL_SIZE CHANNEL_LIST COMMENT_ DIVERSITY_SUPPORT DIVERSITY_SUPPORT_UL DL_FFR_USAGE DL_LOAD DOWNLINK_EXTERNAL_NOIS E_RISE FBAND FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL FRAME_CONFIG HEIGHT ICIC_DELTAPL_TH ICIC_SUPPORT ID_REUSE_MIN_DIST MAX_DL_LOAD MAX_EXT_NEIGHB_NUMBER MAX_NEIGHB_NUMBER MAX_NUMBER_OF_USERS MAX_UL_LOAD MISCDLL MISCULL NAME Type Integer Integer Float Text(255) Text (255) Short Short Float Float Float Text (50) Text (50) Float Float Text (50) Float Float Short Float Float Integer Integer Integer Float Float Float Text (50) Description Calculation resolution Second calculation resolution Radius of the cell (schematically represented by an hexagon) Unit: m Channel numbers used by transmitters Comments Type of diversity support used in downlink 0=None. 4=MU-MIMO Percentage of the downlink traffic load carried by the ICIC part of the cell Downlink traffic load Inter-network downlink noise rise Frequency band of the cell Name of the feeder equipment Length of downlink feeder Unit: m Length of uplink feeder Unit: m ICIC frame configuration Antenna height above the ground Unit: m Maximum difference in dB between the best server path loss and second best Server path loss to be considered in ICIC zone Inter -Cell Interference Coordination Support 0=None. 1=Static DL.

Atoll 3. 1 = Interferer only) Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 320 .0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 Field NOISE_FIGURE NOISE_RISE_ICIC_UL NOISE_RISE_UL NUM_SECTORS PBCH_POWER_OFFSET PCI_DOMAIN_NAME PDCCH_POWER_OFFSET PDSCH_POWER_OFFSET PHY_CELLID_LIST POWER PROPAG_MODEL PROPAG_MODEL2 REDT RS_EPRE RSRQ_THRES RX_ANTENNAS_PORTS RX_EQUIPMENT RXLOSSES SA_NAME SCH_POWER_OFFSET SCHEDULER SF_CONFIG SHAREDMAST TILT TMA_NAME TX_ANTENNAS_PORTS TX_TYPE Type Float Float Float Integer Float Text (50) Float Float Text(255) Float Text (255) Text (255) Float Float Float Short Text (50) Float Text (50) Float Text (30) Short Text (50) Float Text (50) Short Short Description Total Noise figure used to determine the thermal noise at the transmitter (Temp) Noise rise received by cell edge traffic Uplink interference noise rise (dB) Number of sectors EPRE offset for PBCH with respect to RS EPRE Name of the physical cell ID domain EPRE offset for PDCCH with respect to RS EPRE EPRE offset for PDSCH with respect to RS EPRE Physical cell IDs used by transmitters Maximum cell output power (dBm) Name of the propagation model used to calculate prediction Name of the second propagation model used to calculate prediction Remote Electrical tilt Energy per resource Element of reference signals Required RSRP for coverage Number of reception antenna ports Reception equipment Losses on the uplink due to transmitter radio equipment Unit: dB Name of the smart antenna equipment EPRE offset for SS with respect to RS EPRE Scheduler used by the cell Subframe configuration used by the cell in case of TDD frequency band Shared mast name: enables antenna sharing between transmitters Mechanical downtilt of the main antenna Name of theTower Mounted Amplifier equipment Number of transmission antenna ports Type of transmitter (0 = Normal.1.

0.4.0. This field will be output from simulation.46 Transmitters Table For transmitters.7.5.AT310_AM_E2 Atoll 3.0.0 Administrator Manual Chapter 15: LTE Data Structure Field TXLOSSES Type Float Description Losses on the downlink due to transmitter radio equipment Unit: dB Target PUSCH C/(I+N) provides Po_pusch and is driven by noise rise limitations of neighbouring cells.0.0.8.6.0. Field ACTIVE ANTENNA_NAME AZIMUT BTS_NAME CALC_RADIUS CALC_RADIUS2 CALC_RESOLUTION CALC_RESOLUTION2 CELL_SIZE COMMENT_ DX DY FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL HEIGHT HEXAGON_GROUP Type Boolean Text (50) Float Text (50) Integer Integer Integer Integer Float Text (255) Float Float Text (50) Float Float Float Text (50) Description Transmitter activity: 'Yes' means that the transmitter is active Name of the main antenna installed on the transmitter (from the Antennas table) Azimuth of the first antenna Name of the BTS equipment Calculation radius used to define the calculation area Unit: m Second calculation radius Unit: m Calculation resolution Second calculation resolution Radius of the cell (schematically represented by an hexagon) Additional information about the transmitter X coordinate relative to the site position Y coordinate relative to the site position Name of the feeder equipment Length of downlink feeder Unit: m Length of uplink feeder Unit: m Antenna height above the ground Unit: m Group of hexagons which contains this transmitter Attributes Null column allowed: No Default value: True Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 4000 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 50 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 2000 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: 321 . Factor enabling reduction of transmission powers of cell-edge users 0.1 Maximum uplink noise rise Uplink traffic load Multi-user (collaborative) MIMO gain in uplink Inter-network uplink noise rise Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: UL_FPC_CINR_MAX Float UL_FPC_FACTOR UL_FPC_NR_MAX UL_LOAD UL_MU_SM_GAIN UPLINK_EXTERNAL_NOISE_R ISE Float Float Float Float Float 15.9.1.

Attributes Null column allowed: No Default value: Null column allowed: No Default value: 15. Second part of the unique key.0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 Field MISCDLL MISCULL NOISE_FIGURE POLARIZATION PROPAG_MODEL PROPAG_MODEL2 REDT RX_ANTENNAS_PORTS RXLOSSES SA_NAME SHAREDMAST SITE_NAME TILT TMA_NAME TX_ANTENNAS_PORTS TX_ID TX_TYPE TXLOSSES Type Float Float Float Text (1) Text (50) Text (50) Float Short Float Text (50) Text (50) Text (50) Float Text (50) Short Text (50) Short Float Description Miscellaneous downlink loss Miscellaneous uplink loss Total Noise figure used to determine the thermal noise at the transmitter Polarization of the antennas installed at the transmitter Name of the propagation model used to calculate prediction Name of the second propagation model used to calculate prediction Remote electrical tilt of the main antenna Number of antenna ports in reception Losses on the uplink due to transmitter radio equipment Name of the smart antenna equipment Shared mast name: enables antenna sharing between transmitters Name of the site at which the transmitter is located (from the Sites table) Mechanical downtilt of the first antenna Name of theTower Mounted Amplifier equipment Number of antenna ports in transmission Transmitter name Type of transmitter (0 = Normal. Name of the transmitter. Name of the list. Field NAME Type Text (50) Description Name of the transmitter list Attributes Null column allowed: No Default value: 322 .1.Atoll 3.48 TxsListsNames Table For names of transmitter lists.47 TxsLists Table For transmitters belonging to transmitter lists. 1 = Interferer only) Losses on the downlink due to transmitter radio equipment Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: "V" Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 15. Field LIST_NAME TX_NAME Type Text (50) Text (50) Description First part of the unique key.

1= dBi. and the database internal coordinate system.AT310_AM_E2 Atoll 3.1. 1=dbµV. 1=Watts. 2=kWatts. Transmission unit when creating database Choice list: 0=dBm.0 Administrator Manual Chapter 15: LTE Data Structure 15. the projection coordinate system specified in the ATL document. Field COORD_SYSTEM GAIN_UNIT PROJECTION RECEPTION_UNIT TRANSMISSION_UNIT Type Integer Integer Integer Integer Integer Description Display coordinate system when creating database Unit used for gains (dBd or dBi) Choice list: 0=dBd. Projected coordinate system for geo data Reception unit when creating database Choice list: 0=dBm. Attributes Null column allowed: Yes Default value: -1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: -1 Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 323 .49 Units Table For the reception and transmission units. 2=dbµV/m.

Atoll 3.0 Administrator Manual Chapter 15: LTE Data Structure © Forsk 2011 324 .1.

These tables contain a two-level definition of the above entities: a technology-independant level and a technology-specific level. Tables in the 3GPP Multi-RAT template data structure may be divided into the following categories: • Common tables with identical structures These tables are shared and used by all the technologies.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure 16 3GPP Multi-RAT Data Structure 3GPP Multi-RAT Atoll documents can contain any one. and traffic environments for all the three technologies. user profiles. • Technology-specific tables These tables are specific to technologies. For the list of these tables and their descriptions. For the list of these tables and their structures. There structures are the same as in single-technology documents. and relations with other tables) are the same as in single-technology documents. any two. see "Bidirectional Neighbour Relations Tables" on page 329. Field V_TECHNO With one additional field: Type Text (50) Description Victim technology Attributes Null column allowed: No Default value: Equivalent Single-technology Table Antennas Table BTSEquipments Table CoordSys Table CustomFields Table FeederEquipments Table InterNetChProtect Tablea PropagationModels Table RepeaterEquipments Table SitesLists Table SitesListsNames Table SmartAntennasModels Table TMAEquipments Table 325 . There structures (fields. and LTE. UMTS. The 3GPP Multi-RAT data structures can therefore be combinations of the three single-technology data structures. There structures are the merged versions of their equivalent single-technology tables. • Multi-RAT traffic model tables The multi-RAT traffic model allows you to define services. • Common tables with merged structures These tables are shared and used by all the technologies. their structures. For the list of these tables. terminals. see "Common Tables With Identical Structures" on page 325. keys.1 Common Tables With Identical Structures 3GPP Multi-RAT Table antennas btsequipments coordsys customfields feederequipments internetchprotect propagationmodels repeaterequipments siteslists siteslistsnames smartantennasmodels tmaequipments a. see "Common Tables With Merged Structures" on page 326.1. or all three 3GPP technologies: GSM. see "Technology-specific Tables" on page 327. and mobility types. see "Multi-RAT Traffic Model Tables" on page 331. • Bi-directional neighbour relations tables These tables contain neighbour relations and constraints per pair of technologies. 16. For the list of these tables and their equivalent tables in single-technology documents. For the list of these tables and their equivalent tables in single-technology documents.AT310_AM_E2 Atoll 3. There structures are the same as of their equivalent tables in single-technology documents. and their equivalent tables in single-technology documents.

Reference signal C/(I+N)) Best server selection method: 0=RS C.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure © Forsk 2011 16. 1=Extended. Serving cell selection method (0 = Min DL Load. 1 = Min UL Load. Default soft handoff gain uplink Default propagation model Default orthogonality factor Default calculation resolution Maximum radius for a cell Nt includes or not pilot's signal for HS-SCCH.1. Service Allowed DL min and max TCH powers are absolute values or relative to cell pilot power Cell total power is absolute value (dBm) or relative to Cell maximum power (%) Attributes Null column allowed: No Default value: False Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 2 Null column allowed: No Default value: 1 Null column allowed: No Default value: 1 Null column allowed: No Default value: True Null column allowed: No Default value: False Null column allowed: No Default value: -13 Null column allowed: No Default value: True Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: "CostHata" Null column allowed: No Default value: 0 Null column allowed: No Default value: 50 Null column allowed: No Default value: -1 Null column allowed: No Default value: False Null column allowed: Yes Default value: -130 Null column allowed: No Default value: True Null column allowed: No Default value: Null column allowed: No Default value: False Null column allowed: No Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: False Null column allowed: No Default value: False 326 . 1=RSRP.2 Common Tables With Merged Structures networks Table Field ADD_MRC_SOFTERSOFT AMS_SEL_CRITERION BS_SELECTION CELL_SELECTION COMPRESSED_DELTA_DL_Q UAL COMPRESSED_DELTA_UL_Q UAL COMPRESSED_ON_ECIO COMPRESSED_ON_RSCP COMPRESSED_THRESHOLD CQI_CPICH_BASED DEFAULT_CP DEFAULT_HOGAIN_UL DEFAULT_MODEL DEFAULT_ORTHO_FACTOR DEFAULT_RESOLUTION DMAX HSDPA_NTISNTOT INTERFERERS_RX_THRESH IOISNTOT NAME NTISNTOT PDCCH_SYMBOLS POWER_CONTROL_MARGIN POWERS_RELATIVE_TO_PILO T PTOT_RELATIVE_TO_PMAX Type Boolean Short Short Short Float Float Boolean Boolean Float Boolean Short Float Text (50) Float Float Float Boolean Float Boolean Text (50) Boolean Short Float Boolean Boolean Description If true. 1 .Reference signal C/N. 3 = Sequential) Eb/Nt DL target overhead due to compressed mode activated Eb/Nt UL target overhead due to compressed mode activated Compressed mode activated on Ec/Io threshold Compressed mode activated on RSCP threshold Ec/Io threshold for compressed mode activation CQI determination ids based on CPICH quality (true) or on HS-PDSCH quality (false) Default cyclic prefix Choice list: 0=Normal. gain due to MRC is taken into account for softer/soft cases AMS criterion (0 . HS-PDSCH and CPICH for CQI determination Interferers' reception threshold Io includes pilot signal or not Type of network Nt includes pilot signal or not Number of symbol durations per subframe for PDCCH overhead Margin Over Max Bearer Threshold defining C/I Target (dB) Cell paging and Synchro powers.Atoll 3. 2 = Random.

In each record.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure Field PUCCH_AVG_NRB RS_EPRE_DEFINITION RSCP_COMPRESSED_THRESH OLD SHARED_RESULTS_FOLDER SP_PERIODICITY SPREADING_WIDTH SSF_CONFIG SYSTEM_ TECHNOLOGY THERMAL_NOISE Type Float Short Float Text (255) Short Float Short Text (50) Text (10) Float Description Average number of overhead resource blocks for PUCCH RS EPRE Definition Method 0 .) Name of the system Name of the technlogy Thermal noise Attributes Null column allowed: No Default value: 2 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: -100 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 3. 2. 16. 6. Spreading width (MHz) TDD: Special subframe configuration (0. 8. sites Table The final structure is the same as the UMTS Sites table (see "Sites Table" on page 283). only parameters relevant for the row’s technology are used.84 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: -121 The networks table contains one record for each technology in the document. receivers Table The final structure is the same as the GSM Receivers table (see "Receivers Table" on page 249). units Table The final structure is the same as the GSM Units table (see "Units Table" on page 261). 1 . 4.Calculated from Max Power. 1.1.3 Technology-specific Tables GSM Technology Tables 3GPP Multi-RAT Table gafpmodels gbsicdomains gbsicgroups gcelltypes gcodecequipments gcodecmodeadapts gcodecmodes gcodecqualtables gcodingschemes gcsequipments gcsquality gdimensmodel gfreqdomains gfreqgroups gfrequencybands Equivalent GSM Table AfpModels Table BSICDomains Table BSICGroups Table CellTypes Table CodecEquipments Table CodecModeAdaptations Table CodecModes Table CodecQualityTables Table EGPRSCodingSchemes Table EGPRSEquipments Table EGPRSQuality Table EGPRSDimensioningModel Table FrequencyDomains Table FrequencyGroups Table FrequencyBands Table 327 .User Defined RSCP threshold for compressed mode activation Shared results storage folder Switching point periodicity (TDD) Choice list: 0=Half Frame. 3. 5.AT310_AM_E2 Atoll 3. 7. 1=Frame.

0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure © Forsk 2011 3GPP Multi-RAT Table ghsndomains ghsngroups glayers gneighbours gneighconstraints gneighext gneighextconstraints gqualityindicators grepeaters gsecondaryantennas gseparationrules gseparations gservicequality gtpltransmitters gtransmitters gtrgconfigs gtrgs gtrxequipments gtrxs gtrxtypes gtsconfignames gtsconfigs gtxslists gtxslistsnames UMTS Technology Tables 3GPP Multi-RAT Table ucells uceuse uequipments ufrequencybands uhsdpabearers uhsdpabearerselect uhsdpaqualtables uhspamimoconfigs uhsupabearers uhsupabearerselect uhsupaqualtables uhsuparessuse uhsupauecategories uinterfreducfactors uneighbours uneighconstraints uneighext uneighextconstraints upscdomains upscforbidpairs upscgroups Equivalent GSM Table HSNDomains Table HSNGroups Table Layers Table Neighbours Table NeighboursConstraints Table NeighboursExt Table NeighboursConstraintsExt Table QualityIndicators Table Repeaters Table SecondaryAntennas Table SeparationRules Table Separations Table EGPRSServiceQuality Table TplTransmitters Table Transmitters Table TRGConfigurations Table TRGs Table TRXEquipments Table TRXs Table TRXTypes Table TSConfigurationNames Table TSConfigurations Table TxsLists Table TxsListsNames Table Equivalent UMTS Table CDMACells Table CDMAEquipmentsCEsUse Table CDMAEquipments Table FrequencyBands Table HSDPABearers Table HSDPABearerSelectTables Table HSDPAQualityTables Table HSPAMIMOConfigs Table HSUPABearers Table HSUPABearerSelection Table HSUPAQualityTables Table CdmaEqptsHSUPARssUse Table HSUPAUECategories Table InterfReductionFactors Table Neighbours Table NeighboursConstraints Table NeighboursExt Table NeighboursConstraintsExt Table ScramblingCodesDomains Table Separations Table ScramblingCodesGroups Table 328 .Atoll 3.1.

AT310_AM_E2 Atoll 3.1.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure 3GPP Multi-RAT Table uqualityindicators ur99bearers urepeaters usecondaryantennas uservicequaltables uservicesquality utpltransmitters utransmitters utxslists utxslistsnames uuecategories uuerxequipments LTE Technology Tables 3GPP Multi-RAT Table lbearerqualitycurves lbearers lbearersrequiredci lcells lequipments lframeconfigs lfrequencybands lmimoconfigs lmugtables lneighbours lneighconstraints lneighext lneighextconstraints lpcidomains lpcigroups lqualityindicators lrepeaters lschedulers lsecondaryantennas lsmartantennas ltpltransmitters ltransmitters ltxslists ltxslistsnames luecategories Equivalent UMTS Table QualityIndicators Table R99Bearers Table Repeaters Table SecondaryAntennas Table ServiceQualityTables Table UMTSServicesQuality Table TplTransmitters Table Transmitters Table TxsLists Table TxsListsNames Table UECategories Table UERxEquipments Table Equivalent LTE Table T4GBearerQualityCurves Table T4GBearers Table T4GBearersRequiredCI Table T4GCells Table T4GEquipments Table lframeconfigs Table FrequencyBands Table T4GMimoConfigs Table MUGTables Table Neighbours Table NeighboursConstraints Table NeighboursExt Table NeighboursConstraintsExt Table lpcidomains Table lpcigroups Table QualityIndicators Table Repeaters Table Schedulers Table SecondaryAntennas Table SmartAntennas Table TplTransmitters Table Transmitters Table TxsLists Table TxsListsNames Table T4GUECategories Table 16.4 Bi-directional Neighbour Relations Tables 3GPP Multi-RAT Table guneighbours guneighconstraints glneighbours Descritpion UMTS neighbours of GSM transmitters Constraints on UMTS neighbours of GSM transmitters LTE neighbours of GSM transmitters 329 .

5=Distance. 2=Co-site.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure © Forsk 2011 3GPP Multi-RAT Table glneighconstraints ugneighbours ugneighconstraints ulneighbours ulneighconstraints lgneighbours lgneighconstraints luneighbours luneighconstraints Structure of the neighbour relations tables: Field IMPORTANCE NEIGHBOUR Type Float Text (50) Description Handover importance Second part of the unique key.1. 4=Symmetric.Atoll 3. Constraint is used in automatic allocation. 1=Forced. 6=Coverage. List of neighbours Descritpion Constraints on LTE neighbours of GSM transmitters GSM neighbours of UMTS cells Constraints on GSM neighbours of UMTS cells LTE neighbours of UMTS cells Constraints on LTE neighbours of UMTS cells GSM neighbours of LTE cells Constraints on GSM neighbours of LTE cells UMTS neighbours of LTE cells Constraints on UMTS neighbours of LTE cells Attributes Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 (Manual) Null column allowed: No Default value: Null column allowed: Yes Default value: REASON Integer Reason of the neighbourhood Choice list: 0=Manual. First part of the unique key. Transmitters or cells Type of the neighbourhood (handover. measurement…) TRANSMITTER TYPE Text (50) Text (50) Structure of the neighbour constraints tables: Field IMPORTANCE NEIGHBOUR STATUS Type Float Text (50) Integer Description Handover importance Second part of the unique key. List of neighbours Type of constraint on the neighbourhood relationship. First part of the unique key. Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: TRANSMITTER Text (50) 330 . 1=Forbidden. 3=Adjacent. Choice list: 0=Forced. Transmitters or cells.

See "T4GServices Table" on page 315. REQ_AVERAGE_UL_RATE. except the DL_ACTIVITY.1. and UL_ACTIVITY fields. 331 .13GPP Services Model Common multi-RAT service parameters are stored in the following table: • Field DL_ACTIVITY NAME REQ_AVERAGE_DL_RATE REQ_AVERAGE_UL_RATE TECHNO_PRIORITY UL_ACTIVITY services Table Type Float Text (50) Float Float Text (50) Float Description Activity factor for voice services on the downlink Service Name Requested Average Downlink Rate (kbps) Requested Average Uplink Rate (kbps) List of supported technologies in the order of priority Activity factor for voice services on the uplink Attributes Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Per-technology service parameters are stored in the following tables: • gservices Table Same structure as the services table in GSM. and UL_ACTIVITY fields. except the DL_ACTIVITY.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure 16. REQ_AVERAGE_UL_RATE. and UL_ACTIVITY fields. REQ_AVERAGE_UL_RATE. REQ_AVERAGE_DL_RATE.5 Multi-RAT Traffic Model Tables Service Tables Figure 16.AT310_AM_E2 Atoll 3. See "UMTSServices Table" on page 290. • uservices Table Same structure as the services table in UMTS. except the DL_ACTIVITY. • lservices Table Same structure as the services table in LTE. REQ_AVERAGE_DL_RATE. REQ_AVERAGE_DL_RATE. See "EGPRSServices Table" on page 242.

0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure © Forsk 2011 Terminal Tables Figure 16.23GPP Terminals Model Common multi-RAT service parameters are stored in the following table: • Field NAME terminals Table Type Text (50) Description Name of terminal Attributes Null column allowed: No Default value: Per-technology service parameters are stored in the following tables: • gterminals Table Same structure as the terminals table in GSM. Mobility Tables Figure 16.33GPP Services Model Common multi-RAT service parameters are stored in the following table: • Field NAME MEAN_SPEED mobility Table Type Text (50) Float Description Name of mobility type Average speed (km/h) Attributes Null column allowed: No Default value: Null column allowed: No Default value: Per-technology service parameters are stored in the following table: • umobility Table 332 .1. • lterminals Table Same structure as the terminals table in LTE. See "UMTSTerminals Table" on page 292. • uterminals Table Same structure as the terminals table in UMTS. See "T4GTerminals Table" on page 317.Atoll 3. See "EGPRSTerminals Table" on page 243.

See. except the MEAN_SPEED field. "EGPRSServicesUsage Table" on page 243.AT310_AM_E2 Atoll 3. servicesusage Table Same structure as services usage tables in all three technologies. for example. See "UMTSMobility Table" on page 290. 333 . for example. "EGPRSTrafficEnvironments Table" on page 244. "EGPRSUserProfiles Table" on page 244. environmentdefs Table Same structure as environment definition tables in all three technologies. for example.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure Same structure as the mobilities table in UMTS. See. "EGPRSEnvironmentDefs Table" on page 241. See.1. for example. userprofiles Table Same structure as user profiles tables in all three technologies. trafficenvs Table Same structure as traffic environment tables in all three technologies. See.

1.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure © Forsk 2011 334 .Atoll 3.

3 on page 337 depict the CDMA2000 1xRTT 1xEV-DO database structure. Figure 17. Figure 17.2 on page 336.1 on page 335.1.0 Administrator Manual Chapter 17: CDMA2000 Data Structure 17 CDMA2000 Data Structure Figure 17.AT310_AM_E2 Atoll 3.1: CDMA2000 1xRTT 1xEV-DO Template .1 335 . The following subsections list the tables in the CDMA2000 1xRTT 1xEV-DO template data structure. and Figure 17.

2 336 .0 Administrator Manual Chapter 17: CDMA2000 Data Structure © Forsk 2011 Figure 17.Atoll 3.1.2: CDMA2000 1xRTT 1xEV-DO Template .

3 337 .AT310_AM_E2 Atoll 3.0 Administrator Manual Chapter 17: CDMA2000 Data Structure Figure 17.1.3: CDMA2000 1xRTT 1xEV-DO Templates .

1=Choice list is mandatory Attributes Null column allowed: Yes Default value: 0 DLBearersSelection Table Field MODULATION Type Short Description 0=QPSK.1 Changes in Data Structure From 2. 2=16QAM.Atoll 3.1.1.8 to 3. 3=64QAM Attributes Null column allowed: No Default value: 0 TplTransmitters Table Field COMMENT_ MC_MODE_MUG MC_MODE_UL_ECNT_MIN MULTI_CARRIER SHAREDMAST Type Text (255) Memo Float Short Text (50) Description Comments Multi-user gain graph used in multi-carrier mode Required Ec/Nt for multi-carrier mode in the uplink 0=None.1 17. 1=8PSK.0 Administrator Manual Chapter 17: CDMA2000 Data Structure © Forsk 2011 17. 1=Multi-Carrier Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Transmitters Table Field MC_MODE_MUG MC_MODE_UL_ECNT_MIN MULTI_CARRIER SHAREDMAST Type Memo Float Short Text (50) Description Multi-user gain graph used in multi-carrier mode Required Ec/Nt for multi-carrier mode in the uplink 0=None. 1=Multi-Carrier Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 338 .1 Added Tables and Fields Antennas Table Field PHYSICAL_ANTENNA Type Text (50) Description Physical antenna name Attributes Null column allowed: Yes Default value: CdmaCells Table Field LOCKED_PNO Type Boolean Description Field used to freeze allocated PNO of the cell during automatic allocation Attributes Null column allowed: No Default value: False CustomFields Table Field CHOICE_TYPE Type Integer Description 0=Choice list is optional.

1=8PSK. 1=8PSK.2 Deleted Tables and Fields AntennasLists Table • Table AntennasListsNames Table • Table Neighbours Table • RANK NeighboursConstraints Table • RANK NeighboursConstraintsExt Table • RANK NeighboursExt Table • RANK TplTransmitters Table • COV_PROBA Transmitters Table • COV_PROBA 339 .0 Administrator Manual Chapter 17: CDMA2000 Data Structure ULBearersSelection Table Field MODULATION Type Short Description 0=QPSK. 2=16QAM.1. 2=16QAM. 1=Unlocked HO 0=QPSK.AT310_AM_E2 Atoll 3. 3=64QAM Attributes Null column allowed: No Default value: 0 UMTSServices Table Field MIN_RATE_DL MIN_RATE_UL Type Float Float Description Downlink guaranteed bit rate (kbps) Uplink guaranteed bit rate (kbps) Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 UMTSTerminals Table Field HANDOFF_TYPE MODULATION NUM_CARRIERS_MAX Type Short Short Short Description 0=Locked HO.1. 3=64QAM Maximum number of carriers supported in multi-carrier mode Attributes Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 3 17.

4 CarriersType Table For carrier type definition (1xEV-DO or 1xRTT). Field CONFIG_DL_LOSSES CONFIG_UL_LOSSES NAME NOISE_FIGURE RHO_FACTOR Type Float Float Text (50) Float Short Description Downlink losses due to the configuration of the BTS (duplexer and/or combiner) Uplink losses due to the configuration of the BTS (duplexer and/or combiner) Name of Base Station Equipment Noise figure of Base Station Rho factor to model self generated interference (100%=ideal) Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 100 17. Field CARRIER TYPE Type Integer Short Description Carrier number Carrier type Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 340 .1.0 Administrator Manual Chapter 17: CDMA2000 Data Structure © Forsk 2011 17. is described in "RF 2D Antenna Pattern Format" on page 105. Field Beamwidth COMMENT_ CONSTRUCTOR DIAGRAM ELECTRICAL_TILT FMax FMin GAIN NAME PHYSICAL_ANTENNA Type Float Text (255) Text (50) Binary Float Double Double Float Text (50) Text (50) Description Antenna beamwidth Additional information about antenna Antenna manufacturer name Antenna horizontal and vertical patterns Antenna electrical tilt (for information) Maximum operating frequency of the antennas Unit: MHz Minimum operating frequency of the antenna Unit: MHz Antenna isotropic gain Unit: dBi Name of antenna Physical antenna name Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: The format of the binary field.2 Antennas Table For antennas. DIAGRAM. 17.3 BTSEquipments Table For NodeB equipment.Atoll 3.

Used in power control simulation Set of values used to generate the graph MUG=f(number of users) Power of other common channels except SCH Power of the pilot channel PN Offset domain name.0 Administrator Manual Chapter 17: CDMA2000 Data Structure 17. Field used to freeze allocated PNO of the cell during automatic allocation Attributes Null column allowed: No Default value: True Null column allowed: Yes Default value: 204.1. PN Offset. Used Null column allowed: Yes in power control simulation Default value: 50 Maximum number of EV-DO users Maximum number of inter-technology neighbours for the cell Maximum number of inter-carrier neighbours for this cell Maximum number of neighbours for the cell Maximum uplink load allowed (percentage).AT310_AM_E2 Atoll 3.5 CDMACells Table For cells. Field ACTIVE BCMCS_RATE BCMCS_TS_PCT CARRIER CCH_TS_PCT CELL_ID CELL_IDENTITY COMMENT_ DOWNLINK_EXTERNAL_NOIS E_RISE DRC_ER_RATE IDLE_POWER_GAIN LOCKED_PNO MAX_DL_LOAD MAX_EVDO_USERS MAX_EXT_NEIGHB_NUMBER MAX_INTERCAR_NEIGHB_NB MAX_NEIGHB_NUMBER MAX_UL_LOAD MUG_TABLE PAGING_POWER PILOT_POWER PN_DOMAIN_NAME PN_OFFSET POOLED_PWR POWER_MAX Type Boolean Float Float Integer Float Text (50) Integer Text (255) Float Float Float Boolean Float Integer Integer Integer Integer Float Memo Float Float Text (50) Integer Float Float Description Cell's activity: True means that the cell is active BCMCS service rate % of time slots dedicated to Broadcast/MultiCast services Carrier number % of time slots dedicated to Common Control Channels Name of the cell Cell identity Additional information about the cell Inter-network downlink noise rise DRC Erasure Rate (ie % of time DRC values are in error) Gain dedicated to transmitted power in idle state. Amount of power which can be borrowed in the BTS power pool (dB) Maximum power supported by the transmitter Null column allowed: No Default value: 256 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 75 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 30 Null column allowed: Yes Default value: 33 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 1 Null column allowed: Yes Default value: 43 341 .8 Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 3 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: -10 Null column allowed: No Default value: False Maximum downlink load allowed (percentage of max power used).

3=Sequential.. Used for combination of AS member contributions (Sector Power Pooling) If True.Atoll 3.. sectors' powers available for TCH can be shared among all co-site sectors If true. Field CHANNEL_ELTS_DL Type Float Description Number of channel elements used for downlink Attributes Null column allowed: No Default value: 1 342 .. 2=Random.1.) Name of the manufacturer MUD factor for UL interference cancellation Equipment name Efficiency of the rake receiver. synchro. synchro.0 Administrator Manual Chapter 17: CDMA2000 Data Structure © Forsk 2011 Field REUSE_DIST ROT_RANGE ROT_TARGET SYNCHRO_POWER TADD TDROP TOTAL_POWER TX_ID UL_LOAD UPLINK_EXTERNAL_NOISE_R ISE Type Float Float Float Float Float Float Float Text (50) Float Float Description Minimum reuse distance for PN Offsets Delta of acceptable noise rise (dB) Receiver Noise Rise Over Thermal target (dB) Power of the synchronisation (SCH) channel Minimum Ec/Io for best server selection Ec/Io threshold for active set rejection Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm Name of the transmitter Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm Inter-network uplink noise rise Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 4 Null column allowed: Yes Default value: 23 Null column allowed: Yes Default value: -14 Null column allowed: Yes Default value: -17 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 17. selection of AS members is limited to the neighbours of the selected transmitter Attributes Null column allowed: No Default value: 0 Null column allowed: No Default value: False Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: 1 Null column allowed: No Default value: False Null column allowed: No Default value: False 17.7 CDMAEquipmentsCEsUse Table For channel elements consumption in site equipment.6 CDMAEquipments Table For site equipment. 1=Min DL power. Field CARRIER_SELECTION CE_SHARED_ALL_SECTORS CES_OVERHEAD_DL CES_OVERHEAD_UL MANUFACTURER MUD_FACTOR NAME RAKE_EFFICIENCY SPP USE_NEIGHBOURS Type Short Boolean Integer Integer Text (50) Float Text (50) Float Boolean Boolean Description Carrier selection mode Choice list: 0=Min UL noise. If true CE resources is shared between all sectors of the site Number of channel elements used for DL overhead channels (pilot. . ..) Number of channel elements used for UL overhead channels (pilot.

Terminal name. NoProjection. Name of equipment Second part of the unique key.AT310_AM_E2 Atoll 3. Lambert2SP. CassiniSoldner. Undefined. Attributes Null column allowed: No Default value: 1 Null column allowed: No Default value: Null column allowed: No Default value: 17. HotineOM. TransMercator. ObliqueStereographic. TransMercatorSO. Lambert1SP. SwissObliqueCylindical Arc-seconds Arc-seconds Arc-seconds Parts per million (ppm) Meters Meters Meters Description Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768) Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 PROJ_METHOD Short 343 .8 CoordSys Table For the projection coordinate system and the database’s internal coordinate system ( this is the display coordinate system used when creating a database).0 Administrator Manual Chapter 17: CDMA2000 Data Structure Field CHANNEL_ELTS_UL EQUIPMENT TERMINAL Type Float Text (50) Text (50) Description Number of channel elements used for uplink First part of the unique key. Mercator.1. LabordeOM. Field CODE DATUM_CODE DATUM_ROTX DATUM_ROTY DATUM_ROTZ DATUM_SCALE DATUM_SHIFTX DATUM_SHIFTY DATUM_SHIFTZ ELLIPS_CODE ELLIPS_RMAJOR ELLIPS_RMINOR NAME PROJ_ANGLE PROJ_FALSE_EASTING PROJ_FALSE_NORTHING PROJ_FIRST_PARALLEL PROJ_LATITUDE_ORIGIN PROJ_LONGITUDE_ORIGIN Type Integer Double Double Double Double Double Double Double Double Integer Double Double Text (50) Double Double Double Double Double Double Meters Meters Coordinate system name Decimal degrees Meters Meters Decimal degrees Decimal degrees Decimal degrees UTM. NewZealandMapGrid.

Field CAPTION CHOICE_LIST CHOICE_TYPE COLUMN_NAME DEFAULT_VALUE GROUP_NAME TABLE_NAME Type Text (50) Memo Integer Text (50) Text (50) Text (50) Text (50) Description Caption of the field (displayed instead of the name) Choice list for the field 0=Choice list is optional.11 DLDORABearers Table For downlink EV-DO Rev. 17. A bearers. 2=16QAM. 344 . 1=Choice list is mandatory Second part of the unique key. Field BEARER_INDEX CI_REQ EARLY_TERM_TABLE MOBILITY MODULATION NUM_SLOTS RX_EQUIP Type Short Float Memo Text (50) Short Integer Text (50) Description Index of selected bearer Required Pilot C/I Tables of Probabilities of Earlier Termination=f(REPEAT_NUM) UE mobility 0=QPSK. 1=8PSK.Atoll 3. captions.0 Administrator Manual Chapter 17: CDMA2000 Data Structure © Forsk 2011 Field PROJ_SCALE_FACTOR PROJ_SECOND_PARALLEL PROJ_ZONE_NUMBER Type Double Double Integer Description Attributes Null column allowed: Yes Default value: 0 Decimal degrees Used with UTM Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 17. and choice lists.1. Table name Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.9 CustomFields Table For defining user-defined fields added to tables. default values for any field (including user-defined fields). 3=64QAM Number of retransmissions to ensure a correct transmission Type of receiver of the User Equipment Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: "Standard" 17. and group names for user-defined fields.10 DLBearersSelection Table For downlink bearer selection thresholds. Field name Default value for the field Name of the group to which that field belongs First part of the unique key.

AT310_AM_E2 Atoll 3.12 DORABearers Table For uplink EV-DO Rev. Field AUX_PILOT_GAIN BEARER_INDEX HC_T2P_GAIN LL_T2P_GAIN TERMINAL Type Float Short Float Float Text (50) Description Auxiliary pilot gain EV-DO bearer index Traffic to pilot gain for High Capacity services Traffic to pilot gain for Low Latency services Terminal name Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 17.13 DORABearersProba Table For uplink EV-DO Rev. Field CONNECTOR_LOSSES_DL Type Float Description Feeder connector losses in downlink Attributes Null column allowed: Yes Default value: 0 345 . Field BEARER_INDEX RLC_PEAK_RATE TRANSPORT_BLOCK_SIZE Type Short Float Integer Description EV-DO bearer index RLC bearer rate Transport block size (Bits) Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 17.1. Field BEARER_INDEX PROBA SERVICE Type Short Float Text (50) Description EV-DO bearer index Probability of using a bearer Name of the service Attributes Null column allowed: No Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 17. A bearer probabilities.15 FeederEquipments Table For feeders.14 DORATerminalT2PRatios Table For uplink traffic to pilot gains. A bearers.0 Administrator Manual Chapter 17: CDMA2000 Data Structure Field BEARER_INDEX RLC_PEAK_RATE TRANSPORT_BLOCK_SIZE Type Short Float Integer Description EV-DO bearer index RLC bearer rate Transport block size (Bits) Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 17.

17 InterfReductionFactors Table For interference reduction factors between carriers.19 Neighbours Table For intra-technology neighbour relations. Field CARRIER1 CARRIER2 FACTOR Type Integer Integer Double Description First carrier Second carrier Interference reduction factor Attributes Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value: 200 17.2288 17.1.18 InterNetChProtect Table For inter-network interference reduction factor graphs.0 Administrator Manual Chapter 17: CDMA2000 Data Structure © Forsk 2011 Field CONNECTOR_LOSSES_UL LOSS_PER_METER NAME Type Float Float Text (50) Description Feeder connector losses in uplink Feeder loss per meter Name of Feeder Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 17. Field ICP ITF_BW ITF_TECHNO V_BW Type Memo Double Text (50) Double Description Inter-network channel protection = f( Δ MHz) Interfering bandwidth (kHz) Interfering technology Victim bandwidth (kHz) Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: 0 17. Field BAND_WIDTH FIRST_CARRIER FREQUENCY LAST_CARRIER NAME SPREADING_WIDTH Type Double Integer Double Integer Text (50) Double Description Bandwidth (MHz) Number of the first carrier available on the network Average frequency of carriers Unit: MHz Number of the last carrier available on the network Name of the frequency band Spreading bandwidth definition Attributes Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 2110 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 1.Atoll 3. 346 .16 FrequencyBands Table For frequency bands.

Choice list: 0=Forced. Transmitters or cells Type of the neighbourhood (handover.21 NeighboursConstraintsExt Table For inter-technology neighbour allocation constraints. 1=Forbidden. Field FORCE_HHO IMPORTANCE NEIGHBOUR STATUS TRANSMITTER Type Boolean Float Text (50) Integer Text (50) Description Force Handover type to hard handover in case of intra-carriers neighbours Handover importance (for AFP use) Second part of the unique key. 5=Distance. List of neighbours from another project 347 . Integer Text (50) Type of constraint on the neighbourhood relationship. First part of the unique key.0 Administrator Manual Chapter 17: CDMA2000 Data Structure Field FORCE_HHO IMPORTANCE NEIGHBOUR REASON Type Boolean Float Text (50) Integer Description Force Handover type to hard handover in case of intra-carriers neighbours Handover importance (for AFP use) Second part of the unique key. Choice list: 0=Forced. Field IMPORTANCE NEIGHBOUR Type Float Description Handover importance (for AFP use) Attributes Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Text (50) Second part of the unique key. Transmitters or cells. 2=Co-site. 1=Forced.1. 1=Forbidden. First part of the unique key. measurement…) Attributes Null column allowed: No Default value: False Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 (Manual) Null column allowed: No Default value: Null column allowed: Yes Default value: TRANSMITTER TYPE Text (50) Text (50) 17. 3=Adjacent. List of neighbours Type of constraint on the neighbourhood relationship.22 NeighboursExt Table For inter-technology neighbour relations. Attributes Null column allowed: No Default value: False Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 17. Constraint is used in automatic allocation. 6=Coverage. List of neighbours from another project.AT310_AM_E2 Atoll 3. First part of the unique key.20 NeighboursConstraints Table For intra-technology neighbour allocation constraints. Transmitters or cells 17. 4=Symmetric. Field IMPORTANCE NEIGHBOUR STATUS TRANSMITTER Type Float Description Handover importance (for AFP use) Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Text (50) Second part of the unique key. List of neighbours Reason of the neighbourhood Choice list: 0=Manual. Constraint is used in automatic allocation.

6=Coverage.2288 Null column allowed: No Default value: ‘1xRTT’ Null column allowed: No Default value: ‘CDMA’ Null column allowed: No Default value: False 17.Atoll 3. If false. Default soft handoff gain uplink Default propagation model Default orthogonality factor Default calculation resolution Maximum radius for a cell Interferers' reception threshold Io includes pilot signal or not Attributes Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: No Default value: 0 Null column allowed: Yes Default value: ‘Cost-Hata’ Null column allowed: No Default value: 0 Null column allowed: No Default value: 50 Null column allowed: No Default value: -1 Null column allowed: Yes Default value: -130 Null column allowed: No Default value: True Null column allowed: No Default value: Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1.1. 4=Symmetric. Field ADD_MRC_SOFTERSOFT AS_PARAMS_IN_CELL DEFAULT_HOGAIN_UL DEFAULT_MODEL DEFAULT_ORTHO_FACTOR DEFAULT_RESOLUTION DMAX INTERFERERS_RX_THRESH IOISNTOT NAME NTISNTOT POWERS_RELATIVE_TO_PILO T PTOT_RELATIVE_TO_PMAX SHARED_RESULTS_FOLDER SPREADING_WIDTH SYSTEM_ TECHNOLOGY UC_PWC_ON_PILOT Type Boolean Boolean Float Text (50) Float Float Float Float Boolean Text (50) Boolean Boolean Boolean Text (255) Float Text (50) Text (10) Boolean Nt includes pilot signal or not Cell paging and Synchro powers. 348 . 5=Distance.24 PnCodesDomains Table For names of PN offset domains.0 Administrator Manual Chapter 17: CDMA2000 Data Structure © Forsk 2011 Field REASON TRANSMITTER TYPE Type Integer Text (50) Text (50) Description Reason of the neighbourhood Choice list: 0=Manual. 2=Co-site. TADD and TDROP are considered defined in the cells table. gain due to MRC is taken into account for softer/soft cases If true. First part of the unique key. Service Allowed DL min and max TCH powers are absolute values or relative to cell pilot power Cell total power is absolute value (dBm) or relative to Cell maximum power (%) Shared results storage folder Spreading width (MHz) Name of the system Name of the technology True if uplink power control is based on pilot’s target Description If true. measurement…) Attributes Null column allowed: Yes Default value: 0 (Manual) Null column allowed: No Default value: Null column allowed: Yes Default value: 17. 1=Forced.23 Networks Table For network-level parameters. 3=Adjacent. these parameters are defined in the mobility type. Transmitters or cells Type of the neighbourhood (handover.

26 PropagationModels Table For propagation models. 4=DCH_EBNT. Separator must be a blank character.). FIRST+2*STEP. Field Data Description Name Signature Type Type Binary Text (255) Text (50) Text (40) Text (50) Description Model specific parameters User defined Name of the propagation model Unique Global ID of last model update ProgID of the model Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: 17. …. …. Group elements are: FIRST. n is the greatest positive integer so that FIRST+n*STEP LAST.AT310_AM_E2 Atoll 3. FIRST+STEP. FIRST+STEP. FIRST+2*STEP. …. 2=CPICH_CI. FIRST+n*STEP. Field DOMAIN_NAME EXCLUDED EXTRA FIRST Type Text (50) Text (225) Text (225) Integer Description Second part of the unique key. It is forbidden for EXTRA and EXLUDED to have common numbers. etc. List of codes to be excluded from the series defined by FIRST. Name of the PN code group Group elements are: FIRST. Field CS_QI MEAS_PARAM Type Boolean Short Description Flag which indicates if this indicator is used in CS services Name of the measured figure used for this QI determination Choice list: 1=CPICH_ECIO. FIRST+STEP. 3=CPICH_ECNT. LAST and STEP (separated by blank character) Codes to be added. FIRST+n*STEP.1. n is the greatest positive integer so that FIRST+n*STEP LAST. FIRST+2*STEP. Group elements are: FIRST.0 Administrator Manual Chapter 17: CDMA2000 Data Structure Field DOMAIN_NAME Type Text (50) Description Resource domain name Attributes Null column allowed: No Default value: 17. n is the greatest positive integer so that FIRST+n*STEP LAST. FIRST+n*STEP.27 QualityIndicators Table For quality indicators (BER. BLER.25 PnCodesGroups Table For PN offset groups belonging to PN offset domains. First part of the unique key. 5=HSPDSCH_ECNT. Domain of the PN code group. Name of the managed quality indicator Flag which indicates if this indicator is used for PS services Attributes Null column allowed: No Default value: True Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: No Default value: True NAME PS_QI Text (20) Boolean 349 . Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 1 LAST Integer NAME STEP Text (50) Integer 17.

Field COMMENT_ MANUFACTURER MAX_AMPLIFIER_GAIN MAX_OUTPUT_DL MAX_OUTPUT_UL MIN_AMPLIFIER_GAIN NAME NOISE_FIGURE STEP_AMPLIFIER_GAIN TIME_DELAY Type Text (255) Text (50) Float Float Float Float Text (50) Float Float Float Description Comments Manufacturer of the repeater equipment Maximum gain of the amplifier (dB) Maximum downlink output power (dBm) Maximum uplink output power (dBm) Minimum gain of the amplifier (dB) Name of the repeater equipment Repeater noise Figure (dB) Step of amplifier gain (dB) Time delay in the equipment (microseconds) Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 90 Null column allowed: Yes Default value: 30 Null column allowed: Yes Default value: 12 Null column allowed: Yes Default value: 50 Null column allowed: No Default value: Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 5 17.30 Repeaters Table For repeaters.5 Null column allowed: No Default value: 0 Null column allowed: No Default value: 17. Field ADJ_CHANNEL_PROT ANTENNA HEIGHT LOSS NAME Type Float Text (50) Float Float Text (50) Description Protection against interfering signals from adjacent channels.28 Receivers Table For receiver parameters. Receiver antenna name (if empty an omni antenna is used) Height of the receiver Losses due to receiver radio equipment (up and downlink) Receiver name Attributes Null column allowed: No Default value: 18 Null column allowed: Yes Default value: Null column allowed: No Default value: 1.Atoll 3.1.29 RepeaterEquipments Table For repeater equipment.0 Administrator Manual Chapter 17: CDMA2000 Data Structure © Forsk 2011 Field USE_INTERPOLATION Type Boolean Description Flag which indicates if this QI must be interpolated or not Attributes Null column allowed: No Default value: True 17. Field AMPLIFIER_GAIN AZIMUT Type Float Float Description Gain of the amplifier Azimuth of the donor side antenna Attributes Null column allowed: Yes Default value: 80 Null column allowed: Yes Default value: 0 350 .

1.32 Separations Table For PN offset allocation constraints. 351 .Off air 2.0 Administrator Manual Chapter 17: CDMA2000 Data Structure Field DONOR_CELLID DONOR_LINK_LOSS DONOR_LINK_TYPE DONOR_PROPAG_MODEL DOWNTILT EQUIPMENT_NAME FEEDER_NAME FEEDERLENGTH HEIGHT REC_ANTENNA REC_FEEDERLENGTH_UL TOTAL_GAIN TOTAL_GAIN_UL TX_ID Type Text (50) Float Short Text (50) Float Text (50) Text (50) Float Float Text (50) Float Float Float Text (50) Description Name of the donor cell Loss (dB) between donor and donor side of the repeater 1. the repeater is a passive component Name of the donor side feeder Length of donor side feeder Height of the donor side antenna Name of the donor side antenna Length of donor side uplink feeder Total gain to be applied to donor cell pilot power Uplink total gain to be applied to mobile output power Name of the transmitter (and of the transmitter used for coverage) Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Repeater properties are saved in two tables: the donor-side parameters are in the Repeaters table and the coverage-side parameters in the Transmitters table. Transmitter name Attributes Null column allowed: No Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value: 17.31 SecondaryAntennas Table For additional antennas.Microwave 3. 17. Field ANTENNA AZIMUT PERCENT_POWER REDT TILT TX_ID Type Text (50) Float Float Float Float Text (50) Description Name of the antenna installed on the transmitter Second part of the unique key.Fibre Name of the propagation model used to calculate prediction between donor and repeater Downtilt of the donor side antenna If no equipment. Azimuth of the antenna Percentage of power dedicated to the secondary antenna Remote electrical tilt for secondary antenna Mechanical downtilt of the secondary antenna First part of the unique key.AT310_AM_E2 Atoll 3.

33 ServiceQualityTables Table For 1xRTT performance graphs.34 Sites Table For sites.35 SitesLists Table For sites belonging to site lists. This field is for information only Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 256 Null column allowed: Yes Default value: 256 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 96 Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 50 Null column allowed: Yes Default value: 0 17.0 Administrator Manual Chapter 17: CDMA2000 Data Structure © Forsk 2011 Field TX_ID TX_ID_OTHER Type Text (50) Text (50) Description First part of the unique key.Atoll 3. Second cell name in a symmetric relation Attributes Null column allowed: No Default value: Null column allowed: No Default value: 17. 352 . Field DL_QI_TABLE MOBILITY QI_NAME RX_EQUIP SERVICE UL_QI_TABLE Type Memo Text (50) Text (50) Text (50) Text (50) Memo Description QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table UE mobility Name of the Quality Indicator Type of receiver of the User Equipment Name of the service (can be null for some QI) QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: ’Standard’ Null column allowed: No Default value: Null column allowed: Yes Default value: 17.1. First cell name in a symmetric relation Second part of the unique key. Field ALTITUDE CDMA_EQUIPMENT CHANNEL_ELEMENTS_DL CHANNEL_ELEMENTS_UL COMMENT_ EVDO_CES LATITUDE LONGITUDE NAME PYLON_HEIGHT SUPPORT_NATURE Type Float Text (50) Integer Integer Text (255) Integer Double Double Text (50) Float Short Description Real altitude Unit: m Equipment associated with the site Number of available channel elements for downlink Number of available channel elements for uplink Additional information on the site Number of EVDO CEs per carrier Y coordinate X coordinate Site name Height of the pylon at site The nature of site.

AT310_AM_E2 Atoll 3. Field NAME Type Text (50) Description Name of the list Attributes Null column allowed: No Default value: 17.37 TMAEquipments Table For tower-mounted amplifiers. Name of the site Attributes Null column allowed: No Default value: Null column allowed: No Default value: 17.0 Administrator Manual Chapter 17: CDMA2000 Data Structure Field LIST_NAME SITE_NAME Type Text (50) Text (50) Description First part of the unique key.1.38 TplTransmitters Table For station templates. Name of the list Second part of the unique key.36 SitesListsNames Table For names of site lists. Field DL_LOSSES NAME NOISE_FIGURE UL_GAIN Type Float Text (50) Float Float Description Downlink losses of Tower Mounted Amplifier Name of Tower Mounted Amplifier Noise figure of Tower Mounted Amplifier Uplink gain of Tower Mounted Amplifier Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 17. Field ACTIVE ANTDIVGAIN ANTENNA_NAME AZIMUT BCMCS_RATE BCMCS_TS_PCT BTS_NAME CALC_RADIUS CALC_RADIUS2 CALC_RESOLUTION CALC_RESOLUTION2 Type Boolean Float Text (50) Float Float Float Text (50) Integer Integer Integer Integer Description Transmitter activity: 'Yes' means that the transmitter is active Antenna diversity gain Unit: dB Name of the main antenna installed on the transmitter Azimuth of the first antenna BCMCS service rate % of time slots dedicated to Broadcast/MultiCast services Name of the BTS equipment Calculation radius used to define each transmitter calculation area Unit: m Extended calculation radius Unit: m Calculation resolution Extended calculation resolution Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 353 .

1. Used in power control simulation Multi-user gain graph used in multi-carrier mode Required Ec/Nt for multi-carrier mode in the uplink Miscellaneous downlink losses Miscellaneous uplink losses Set of values used to generate the graph MUG=f(num users) Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 354 .0 Administrator Manual Chapter 17: CDMA2000 Data Structure © Forsk 2011 Field CARRIERS CCH_TS_PCT CDMA_EQUIPMENT CELL_SIZE CHANNEL_ELEMENTS_DL CHANNEL_ELEMENTS_UL COMMENT_ DOWNLINK_EXTERNAL_NOIS E_RISE DRC_ER_RATE EVDO_CES FBAND FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL HEIGHT IDLE_POWER_GAIN MAX_DL_LOAD MAX_EVDO_USERS MAX_EXT_NEIGHB_NUMBER MAX_INTERCAR_NEIGHB_NB MAX_NEIGHB_NUMBER MAX_UL_LOAD MC_MODE_MUG MC_MODE_UL_ECNT_MIN MISCDLL MISCULL MUG_TABLE Type Text (50) Float Text (50) Float Integer Integer Text (255) Float Float Integer Text (50) Text (50) Float Float Float Float Float Integer Short Integer Short Float Memo Float Float Float Memo Description Carriers used by the transmitter % of time slots dedicated to Common Control Channels CDMA equipment Hexagon radius Unit: m Number of channel elements for downlink Number of channel elements for uplink Comments Inter-network downlink noise rise DRC Erasure Rate (ie % of time DRC values are in error) Number of EVDO channel elements per carrier Frequency band Name of the feeder equipment Length of downlink feeder Unit: m Length of uplink feeder Unit: m Antenna height above the ground Unit: m Gain dedicated to transmitted power in idle state Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Maximum downlink load allowed (percentage of max power used).Atoll 3. Used Null column allowed: Yes in power control simulation Default value: Maximum number of EV-DO users Maximum number of inter-technology neighbours for the cell or the transmitter Maximum number of inter-carrier neighbours for this cell Maximum number of neighbours for the cell or the transmitter Maximum uplink load allowed (percentage).

0 Administrator Manual Chapter 17: CDMA2000 Data Structure Field MULTI_CARRIER NAME NOISE_FIGURE NUM_SECTORS PAGING_POWER PILOT_POWER PN_DOMAIN_NAME POOLED_PWR POWER_MAX PROPAG_MODEL PROPAG_MODEL2 REDT REUSE_DIST ROT_RANGE ROT_TARGET RXLOSSES SHAREDMAST SYNCHRO_POWER TADD TDROP TILT TMA_NAME TOTAL_POWER TXLOSSES UL_LOAD UPLINK_EXTERNAL_NOISE_R ISE Type Short Text (50) Float Integer Float Float Text (50) Float Float Text (255) Text (255) Float Float Float Float Float Text (50) Float Float Float Float Text (50) Float Float Float Float Description 0=None. 1=Multi-Carrier Template name Noise figure used to determine the thermal noise at the transmitter Number of sectors Power of the paging channel Power of the pilot channel PN Offset code domain name Amount of power which can be borrowed in the BTS power pool (dB) Maximum power supported by the transmitter Name of the propagation model used to calculate predictions Name of the propagation model used to calculate extended prediction Remote Electrical tilt Minimum reuse distance for PN offsets Delta of acceptable noise rise (dB) Receiver Noise Rise Over Thermal target (dB) Losses in the uplink due to transmitter radio equipment Unit: dB Shared mast name: enables antenna sharing between transmitters Power of the synchronisation (SCH) channel Minimum Ec/Io for best server selection Ec/Io threshold for active set rejection Mechanical downtilt of the main antenna Name of the Tower Mounted Amplifier equipment Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm Losses in the downlink due to transmitter radio equipment Unit: dB Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm Inter-network uplink noise rise Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 3 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 355 .AT310_AM_E2 Atoll 3.1.

39 Transmitters Table For transmitters.1. 1=Multi-Carrier Noise figure used to determine the thermal noise at the transmitter Attributes Null column allowed: No Default value: True Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 4000 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 50 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 2000 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 5 356 .0 Administrator Manual Chapter 17: CDMA2000 Data Structure © Forsk 2011 17. Field ACTIVE ANTDIVGAIN ANTENNA_NAME AZIMUT BTS_NAME CALC_RADIUS CALC_RADIUS2 CALC_RESOLUTION CALC_RESOLUTION2 CELL_SIZE COMMENT_ DX DY FBAND FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL HEIGHT HEXAGON_GROUP MC_MODE_MUG MC_MODE_UL_ECNT_MIN MISCDLL MISCULL MULTI_CARRIER NOISE_FIGURE Type Boolean Float Text (50) Float Text (50) Integer Integer Integer Integer Float Text (255) Float Float Text (50) Text (50) Float Float Float Text (50) Memo Float Float Float Short Float Description Transmitter activity: 'Yes' means that the transmitter is active Antenna diversity gain Name of the main antenna installed on the transmitter Azimuth of the main antenna Name of the BTS equipment Calculation radius used to define the calculation area Unit: m Extended calculation radius Calculation resolution Extended calculation resolution Hexagon radius Unit: m Additional information about the transmitter X coordinate relative to the site location Y coordinate relative to the site location Frequency band Name of the feeder equipment Length of feeder in DL Length of feeder in UL Antenna height above the ground Unit: m Group of hexagons used to create this transmitter Multi-user gain graph used in multi-carrier mode Required Ec/Nt for multi-carrier mode in the uplink Miscellaneous DL loss Miscellaneous UL loss 0=None.Atoll 3.

Field LIST_NAME TX_NAME Type Text (50) Text (50) Description First part of the unique key.41 TxsListsNames Table For names of transmitter lists.0 Administrator Manual Chapter 17: CDMA2000 Data Structure Field PROPAG_MODEL PROPAG_MODEL2 REDT RXLOSSES SHAREDMAST SITE_NAME TILT TMA_NAME TX_ID TXLOSSES Type Text (255) Text (255) Float Float Text (50) Text (50) Float Text (50) Text (50) Float Description Name of the propagation model used to calculate prediction Name of the propagation model used to calculate extended prediction Remote Electrical tilt Losses in the uplink due to transmitter radio equipment Shared mast name: enables antenna sharing between transmitters Name of the site on which the transmitter is located (from the Sites table) Mechanical downtilt of the first antenna Name of the TMA equipment Transmitter name Losses in the downlink due to transmitter radio equipment Attributes Null column allowed: Yes Default value: ’Default model’ Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 17. Name of the transmitter. Field NAME Type Text (50) Description Name of the type of receiver in the UE Attributes Null column allowed: No Default value: 17. Name of the list.42 UERxEquipments Table For UE reception equipment. Attributes Null column allowed: No Default value: Null column allowed: No Default value: 17.1.AT310_AM_E2 Atoll 3. Second part of the unique key.43 ULBearersSelection Table For uplink bearer selection thresholds. Field BEARER_INDEX Type Short Description Index of selected bearer Attributes Null column allowed: Yes Default value: 0 357 . Field NAME Type Text (50) Description Name of the transmitter list Attributes Null column allowed: No Default value: 17.40 TxsLists Table For transmitters belonging to transmitter lists.

Field Type Description Attributes Null column allowed: Yes Default value: '38.44 UMTSEnvironmentDefs Table For traffic environment types.6 -4.5 307.2 2457. 614. 3=64QAM Number of retransmissions to ensure a correct transmission Type of receiver of the User Equipment Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: "Standard" 17. Field BODY_LOSS Type Float Description Body loss Attributes Null column allowed: No Default value: 0 358 .6 3.45 UMTSMobility Table For mobility types.2 9.3 1228.1.8 -7.8 5 1843.5' Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: -22 COVERI_THROUGHPUTS Memo Set of values used to generate the Rate=f(C/I) graph DELTA_TADD DELTA_TDROP NAME UL_ECNT_MIN Float Float Text (50) Float Delta (dB) to be added to the T_ADD defined in cell’s structure Delta (dB) to be added to the T_DROP defined in cell’s structure Type of mobility Minimum uplink Ec/Nt (EV-DO) 17.5 153. Field DENSITY ENVIRONMENT MOBILITY USER_PROFILE Type Float Text (50) Text (50) Text (50) Description Number of subscribers per km2 Environment name Type of mobility Type of user profile Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: 17.46 UMTSServices Table For services.4 1 921.2 -2.5 76.Atoll 3.0 Administrator Manual Chapter 17: CDMA2000 Data Structure © Forsk 2011 Field EARLY_TERM_TABLE HC_ECNT_REQ LL_ECNT_REQ MOBILITY MODULATION NUM_SUBFRAMES RX_EQUIP Type Memo Float Float Text (50) Short Integer Text (50) Description Tables of Probabilities of Earlier Termination=f(REPEAT_NUM) Required Pilot Ec/Nt for High Capacity services Required Pilot Ec/Nt for Low Latency services UE mobility 0=QPSK. 1=8PSK. 2=16QAM.6 11.4 -10.

1.’1’=’Data 1xRTT’ ‘2’=’EVDO’ 0="High Capacity" 1="Low Latency" Either occupancy time of the fundamental channel on the uplink for Null column allowed: Yes 1xRTT.0 Downgrading probability (153.8 -> 38.6 -> 76.0 Downgrading probability (38.AT310_AM_E2 Atoll 3.0 Downgrading probability (19. Occupancy time of the fundamental channel on the downlink Probability to transmit sixteen times the nominal rate on the supplementary channel (SCH) on the downlink Probability to transmit twice the nominal rate on the supplementary channel (SCH) on the downlink Probability to transmit four times the nominal rate on the supplementary channel (SCH) on the downlink Probability to transmit eight times the nominal rate on the supplementary channel (SCH) on the downlink EV-DO Rev.0 Administrator Manual Chapter 17: CDMA2000 Data Structure Field CARRIER DLFCH_ACTIVITYFACTOR DLRATE_16 DLRATE_2 DLRATE_4 DLRATE_8 DOWN_153K6_76K8 DOWN_19K2_9K6 DOWN_38K4_19K2 DOWN_76K8_38K4 ENABLE_DOWNGRADING EVDO_ULRATE_1 MIN_RATE_DL MIN_RATE_UL NAME PRIORITY QOS_CLASS Type Integer Float Float Float Float Float Float Float Float Float Boolean Float Float Float Text (50) Integer Short Description Carrier supporting the service. -1 means that all carriers can be used.8) (Unit 1/255) EV-DO Rev.4 -> 19.4) (Unit 1/255) True if downgrading is enabled for the service Probability to transmit at 9.0 Downgrading probability (76.2 -> 9.6) (Unit 1/255) EV-DO Rev. Probability to transmit sixteen times the nominal rate on the supplementary channel (SCH) on the uplink Probability to transmit twice the nominal rate on the supplementary channel (SCH) on the uplink Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 ULRATE_16 ULRATE_2 Float Float 359 .6 kbps for an EVDO service Downlink guaranteed bit rate (kbps) Uplink guaranteed bit rate (kbps) Service name Priority level of the service: parameter used in the WCDMA simulation 0="Best Effort" 1="Guaranteed Bit Rate" Table of Reverse Link throughputs=f(Forward Link application layer throughput) Attributes Null column allowed: No Default value: -1 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: True Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: '0 0 300 10 600 20 900 30 1200 40 1500 50 1800 60 2400 80' Null column allowed: No Default value: False Null column allowed: No Default value: 0 Null column allowed: No Default value: 95 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 TCP_ACK_CURVE Memo TCP_SERVICE TH_OFFSET TH_SCALE_FACTOR TYPE UL_OPERATION_MODE ULFCH_ACTIVITYFACTOR Boolean Float Float Short Short Float True if the user application is using TCP Offset to add to the above ratio Ratio between application throughput and RLC layer throughput '0'=’Speech’.2) (Unit 1/255) EV-DO Rev. or probability to transmit the nominal rate on the supplementary Default value: 1 channel (SCH) on the uplink in case of 1xEVDO.

Field DL_TARGET_QUAL FCH2PILOT MOBILITY PTCH_MAX PTCH_MIN RX_EQUIP SCH_RATE SCH2PILOT SERVICE TERMINAL UL_ECNT_MIN UL_TARGET_QUAL Type Float Float Text (50) Float Float Text (50) Integer Float Text (50) Text (50) Float Float Description Eb/Nt target on the downlink for each type of (mobility. Used if global flag UL_PWC_ON_PILOT is set to True Eb/Nt target on the uplink for each type of (mobility.6 -> 19.0 Administrator Manual Chapter 17: CDMA2000 Data Structure © Forsk 2011 Field ULRATE_4 ULRATE_8 UP_19K2_38K4 UP_38K4_76K8 UP_76K8_153K6 UP_9K6_19K2 USE_HANDOFF Type Float Float Float Float Float Float Boolean Description Probability to transmit four times the nominal rate on the supplementary channel (SCH) on the uplink Probability to transmit height times the nominal rate on the supplementary channel (SCH) on the uplink EV-DO Rev.4 -> 76.48 UMTSServicesUsage Table For user profile parameters.2 -> 38.1. Name of the service Second part of the unique key. Used if global flag UL_PWC_ON_PILOT is Null column allowed: Yes set to True Default value: 0 First part of the unique key. SCH rate) pair Attributes Null column allowed: Yes Default value: FCH power to Pilot power gain.8) (Unit 1/255) EV-DO Rev.0 Upgrading probability (38. Type of terminal Pilot’s Ec/Nt target.6) (Unit 1/255) EV-DO Rev.Atoll 3. Used if global flag UL_PWC_ON_PILOT is Null column allowed: Yes set to True Default value: 0 UE mobility Maximum transmitter power on fundamental traffic channel for the service Minimum transmitter power on fundamental traffic channel for the service Type of receiver SCH Rate factor (0 -> 16) Null column allowed: Yes Default value: Null column allowed: Yes Default value: 34 Null column allowed: Yes Default value: 14 Null column allowed: No Default value: ’Standard’ Null column allowed: No Default value: 0 SCH power to Pilot power gain.0 Upgrading probability (76.0 Upgrading probability (19. SCH rate) pair Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 17. Field CALL_DURATION CALL_NUMBER Type Float Float Description Average duration of a call (for circuit switched services) Unit: s Average number of calls per hour for circuit switched services or average number of sessions per hour for packet switched services Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 360 .4) (Unit 1/255) EV-DO Rev.2) (Unit 1/255) 'Yes' if the service supports soft handoff Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: False 17.8 -> 153.0 Upgrading probability (9.47 UMTSServicesQuality Table For 1xRTT service access thresholds.

6 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 8 Null column allowed: Yes Default value: 8 Null column allowed: Yes Default value: 3 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 23 Null column allowed: Yes Default value: -50 361 .49 UMTSTerminals Table For terminal types. 1=Unlocked HO Receiver antenna loss 0=QPSK. 2=16QAM. 1=8PSK. Field ACK_GAIN ACK_GAIN_DORA ACTIVE_SET_SIZE DRC_GAIN_NOHO DRC_GAIN_NOHO_DORA DRC_GAIN_SOFT DRC_GAIN_SOFT_DORA DRC_GAIN_SOFTER DRC_GAIN_SOFTER_DORA FWD_BASEDATARATE GAIN HANDOFF_TYPE LOSS MODULATION NAME NOISE_FACTOR NOISE_FACTOR_SEC NUM_CARRIERS_MAX PILOT_POWER_PCT PMAX PMIN Type Float Float Short Float Float Float Float Float Float Float Float Short Float Short Text (50) Float Float Short Float Float Float Description ACK gain ACK gain for 1xEvDo Rev A Attributes Null column allowed: Yes Default value: 4 Null column allowed: No Default value: 3 Maximum number of transmitters possibly connected with the receiver Null column allowed: Yes for the fundamental channel (FCH) Default value: 6 DRC gain (No handoff case) DRC gain (No handoff case) for 1xEvDo Rev A DRC gain (any kind of soft handoff) DRC gain (any kind of soft handoff) for 1xEvDo Rev A DRC gain (only softer handoff) DRC gain (only softer handoff) for 1xEvDo Rev A Downlink nominal rate supported by the receiver on the fundamental channel Receiver antenna gain 0=Locked HO.AT310_AM_E2 Atoll 3.1.0 Administrator Manual Chapter 17: CDMA2000 Data Structure Field SERVICE TERMINAL USER_PROFILE Type Text (50) Text (50) Text (50) Description Service that the subscriber may request Type of terminal used by the subscriber for the service User profile name Attributes Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: 17. 3=64QAM Terminal name Noise figure used to determine the thermal noise at the receiver Noise figure used to determine the thermal noise at the receiver (for secondary frequency band) Maximum number of carriers supported in multi-carrier mode Percentage of maximum power dedicated to the UL pilot channel Maximum receiver power on traffic channel Minimum receiver power on traffic channels Null column allowed: Yes Default value: -1 Null column allowed: No Default value: -1 Null column allowed: Yes Default value: -3 Null column allowed: No Default value: -3 Null column allowed: Yes Default value: -1 Null column allowed: No Default value: -1 Null column allowed: No Default value: 9.

4 kbps) Traffic gain (76. the projection coordinate system specified in the ATL document.50 UMTSTraficEnvironments Table For traffic environment clutter weighting.Atoll 3. and the database internal coordinate system. Used for combination of Active Set member contributions Number of links of the active set that will be combined Uplink nominal rate supported by the receiver on the fundamental channel Rho factor to model self generated interference RRI gain for 1xEvDo Rev A Type of the User Equipment Receiver Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 3 Null column allowed: No Default value: 9. 1:1xRTT_Data.51 UMTSUserProfiles Table For names of user profiles.8 kbps) Traffic gain (9.1.6 kbps) Traffic gain (19.52 Units Table For the reception and transmission units. 3:1xEvDo_RelA Traffic gain (153. Field CLUTTER_WEIGHTS NAME Type Binary Text (50) Description Attributes Null column allowed: Yes Internal binary format describing weights assigned to each clutter class Default value: Yes Name of the created environment Null column allowed: No Default value: 17.6 Null column allowed: No Default value: 94 Null column allowed: No Default value: -6 Null column allowed: No Default value: ‘Standard’ Maximum number of transmitters possibly connected with the receiver Null column allowed: Yes for the supplementary channel (SCH) Default value: 3 Secondary frequency band 0:Speech.0 Administrator Manual Chapter 17: CDMA2000 Data Structure © Forsk 2011 Field PRIMARY_BAND RAKE_EFFICIENCY RAKE_NUM_FINGERS REV_BASEDATARATE RHO_FACTOR RRI_GAIN_DORA RX_EQUIP SCH_AS_SIZE SECONDARY_BAND SUPPORTED_TECHNO TRAFFIC_GAIN_153_6 TRAFFIC_GAIN_19_2 TRAFFIC_GAIN_38_4 TRAFFIC_GAIN_76_8 TRAFFIC_GAIN_9_6 Type Text (50) Float Short Float Short Float Text (50) Short Text (50) Short Float Float Float Float Float Description Primary frequency band Efficiency of the rake receiver. Field NAME Type Text (50) Description Name of the created user profile Attributes Null column allowed: No Default value: 17.2 kbps) Traffic gain (38. 2:1xEvDo_Rel0.2 kbps) Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 18 Null column allowed: Yes Default value: 7 Null column allowed: Yes Default value: 10 Null column allowed: Yes Default value: 13 Null column allowed: Yes Default value: