Atoll 3.3.2 Administrator Manual
AtollDescripción completa
Views 231 Downloads 7 File size 4MB
Recommend stories
- Author / Uploaded
- ratelekoms
Citation preview
Version 3.3.2
Administrator Manual
AT332_AM_E0
AT332_AM_E0
Atoll 3.3.2 Administrator Manual Release: AT332_AM_E0 (November 2016) © Copyright 1997-2016 Forsk. All Rights Reserved. Published by: Forsk 7 rue des Briquetiers 31700 Blagnac, France Tel: +33 562 747 210 Fax: +33 562 747 211 The software described in this document is provided under a licence agreement. The software may only be used or copied under the terms and conditions of the licence agreement. No part of the contents of this document may be reproduced or transmitted in any form or by any means without written permission from the publisher. The product or brand names mentioned in this document are trademarks or registered trademarks of their respective registering parties. Third party services that are not part of Atoll are governed by the terms and conditions of their respective providers, which are subject to change without notice. The publisher has taken care in the preparation of this document, but makes no expressed or implied warranty of any kind and assumes no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information contained herein.
Atoll 3.3.2 Administrator Manual Table of Contents
AT332_AM_E0
Table of Contents
Atoll 3.3.2 Administrator Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 1
Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
1.1
Supported Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2
Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.3
Supported Database Management Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.4
Supported Installation Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.5 1.5.1 1.5.2 1.5.3 1.5.4 1.5.5
Recommended Hardware and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Single-user Standalone Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Multi-user Thick Client Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Multi-user Thin Client Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Floating License Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 File Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2
Atoll and Component Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
2.1
Installing Atoll Using the Setup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2
Installing Atoll C++ Development Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.3
Setup Command Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.4
Installing and Uninstalling Add-ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.5
Installing and Uninstalling Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.6
Atoll Command Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.7
Troubleshooting and Other Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3
Distributed Calculation Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
3.1 3.1.1 3.1.2 3.1.3
Setting Up Calculation Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Stopping and Starting the Distributed Calculation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Running More Than One Distributed Calculation Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Uninstalling the Distributed Calculation Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.2
Setting Up Atoll to Access the Calculation Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.3
Distributed Calculation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4
License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
4.1 4.1.1 4.1.1.1 4.1.1.2 4.1.2 4.1.3
Working with Floating Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Installing the Sentinel HASP Licensing System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Installing the HASP Device Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Installing the HASP License Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 nhsrv.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 nethasp.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.2 4.2.1 4.2.2 4.2.3
Using the Atoll License Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 License Manager Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Updating License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Generating a C2V File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5
Managing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 3
Atoll 3.3.2 Administrator Manual Table of Contents
5.1
Atoll Database Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
5.2
Customising Atoll Database Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
5.3
Atoll Management Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
5.4 5.4.1 5.4.2
Creating New Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Creating a New Database Using the Atoll Management Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Creating a New Database Using Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
5.5 5.5.1 5.5.2 5.5.3
Upgrading Existing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Upgrading Databases for the First Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Upgrading Databases Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 Adding a Technology in a Multi-RAT Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
5.6 5.6.1 5.6.2 5.6.3
Working With Multi-level Databases Using Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61 Creating Project Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 Archiving Project Databases to Master Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Refreshing Project Databases from Master Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
5.7
Setting Database Access Privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
5.8 5.8.1 5.8.2 5.8.3 5.8.4 5.8.4.1 5.8.4.2
Managing Data Modifications History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Setting Up Data Modifications History Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Enabling/Disabling Data Modifications History Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 Updating Data Modifications History after a Data Structure Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 Purging Old Data Modification Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 Purging Old Data Modification Records of a Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 Purging Old Data Modification Records of a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
5.9 5.9.1 5.9.2
Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 Appendix 1: Advanced Customisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 Appendix 2: Setting Up Databases for Co-planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
6
Multi-user Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.1
Setting Up Multi-user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.2.5 6.2.6
Components of Multi-user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 Master Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Master Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Shared Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Shared Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 Shared Microwave Link Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 User Atoll Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
6.3 6.3.1 6.3.2 6.3.3
Managing User Accounts and Access Rights in Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 Defining Database and Interface Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 Creating and Managing User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85 Resetting User Database Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
6.4 6.4.1 6.4.2 6.4.3 6.4.4
Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 Appendix 1: Checking Data Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 Appendix 2: Database Regionalisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 Appendix 3: Calculating Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Appendix 4: Path Loss Matrices From Different Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
7
Coordinate Systems and Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
7.1 7.1.1 7.1.2 7.1.3 7.1.4
Coordinate Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 Definition of a Coordinate System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 Types of Coordinate Systems in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 Coordinate Systems File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 Creating a Coordinate System in Atoll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
7.2
Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
7.3
BSIC Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8 4
© Forsk 2016
Atoll File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
AT332_AM_E0
Atoll 3.3.2 Administrator Manual Table of Contents
8.1 8.1.1 8.1.1.1 8.1.1.2 8.1.2 8.1.3 8.1.4 8.1.5
Geographic Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 HDR Header File for BIL Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 HDR Header File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Additional PRJ Projection File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 TFW Header File for TIFF Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 BPW/BMW Header Files for BMP Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 PGW Header File for PNG Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 JGW Header File for JPG Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8.2 8.2.1 8.2.2 8.2.3
Path Loss Matrix File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Pathloss.dbf File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Pathloss.dbf File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 LOS File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
8.3 8.3.1 8.3.2 8.3.3
Path Loss Tuning File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Pathloss.dbf File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Pathloss.dbf File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 PTS File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
8.4 8.4.1 8.4.1.1 8.4.1.2 8.4.2 8.4.3 8.4.4 8.4.5
Interference Matrix File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 CLC Format (One Value per Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 CLC File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 DCT File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 IM0 Format (One Histogram per Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 IM1 Format (One Value per Line, TX Name Repeated). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 IM2 Format (Co- and Adjacent-channel Probabilities) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 MNU Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
8.5 8.5.1 8.5.2
"Per Transmitter" Prediction File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 .dbf File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 .dbf File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
9
Administration and Usage Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . .123
9.1
Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
9.2
Path Loss Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
9.3
Atoll Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
9.4
Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
9.5
Calculation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
9.6
Atoll Administration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
9.7
Process Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
9.8
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
9.9
Coverage Prediction Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
9.10
CW Measurements and Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
9.11
Antenna Patterns and Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
9.12
Traffic Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
9.13
Atoll API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9.14
Performance and Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
10 10.1 10.1.1 10.1.2 10.1.3 10.1.4 10.1.5 10.1.6 10.1.7
Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135 Contents of User Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Geographic Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Map Centre and Zoom Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Folder Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Automatic Neighbour Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Automatic Frequency Planning Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
5
Atoll 3.3.2 Administrator Manual Table of Contents
10.1.8 10.1.9 10.1.10 10.1.11 10.1.12
© Forsk 2016
Automatic Scrambling Code Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic PN Offset Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automatic OFDM Resource Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Microwave Radio Links Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
152 154 155 156 159
10.2 10.2.1 10.2.2 10.2.3 10.2.4 10.2.5
Contents of Additional Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Print Setup Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table Import/Export Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Coverage Prediction Report Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CW Measurement Import Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drive Test Data Import Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
159 160 161 161 162 163
10.3
Content of the Custom Predictions File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
10.4
Content of the "Value Intervals" Predictions Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
11
Initialisation Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
11.1 Atoll Initialisation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1 General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.1 Managing Memory Allocation per Session in Atoll 64-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.2 Changing the Default Metre-to-Feet Conversion Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.3 Changing the Default Mile-to-Metre Conversion Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.4 Modifying the Default Formats of Site and Transmitter Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.5 Disabling Automatic Renaming of Transmitters and Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.6 Setting the TIFF Colour Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.7 Creating an Event Viewer Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.8 Displaying Insufficient Permission Messages in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.9 Increasing the Maximum Printing Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.10 Copying Externalised Calculation Results on Save As. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.11 Disabling External Storage of Numerical Coverage Prediction Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.12 Exporting Prediction Coordinates using the Projection Coordinate System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.13 Restricting the List of Predictions for Creating Sector Traffic Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.14 Displaying Path Loss Calculation Details in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.15 Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.16 Exporting Coverage Prediction Polygons in Text Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.17 Defining Web Map Services Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.18 Improving Point Analysis Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.19 Excluding Vectors from Imported KML/KMZ Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.20 Combining Imported Zone Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.21 Setting the Precision for the Antenna Pattern Verification at Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.22 Exporting Selected Data Tables to XML Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.23 Keeping the Original List Separator when Exporting in CSV Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.24 Opening Exported XLS Files Automatically in MS Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.25 Disabling Creation of New Documents from Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.26 Blocking Access to Macros and Add-ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.27 Disabling Saving and Opening ZIP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.28 Hiding the Propagation Models Folder in the Parameters Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.29 Forbidding Shared Antenna Modification in Multi-RAT Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.30 Enabling Notification for Donor Transmitter Parameter Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.31 Setting the Display Precision of Floating Point Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.32 Changing the Path to Linked Geo Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.33 Exporting/Importing Vector Data with a Display Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.34 Using Only Visible Geo Data in Prediction Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.35 Exporting BMP, TIF, and PNG Files with a TAB Reference File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.36 Exporting BIL Files with a PRJ Projection File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.37 Co-Planning: Linking the Sites Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.38 Disabling Normalisation of MIF/TAB Vector Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.39 Customising Performance Optimisation when Exporting Vector Files in TAB Format . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.40 Adding the Duplicate Site to the Original Site’s Site List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.41 Moving Sites without Moving Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.42 Real Altitude versus DTM Altitude in Sites’ Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.42.1 Duplicate/Moved Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.42.2 New Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.43 Using Only Visible Clutter Classes in Interference Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.44 Displaying % of Covered Clutter Classes w. r. t. the Focus Zone in Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1.1.45 Displaying % of Covered Traffic Classes w. r. t. the Focus Zone in Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6
167 167 167 168 168 169 169 170 170 170 170 170 171 171 171 171 172 172 173 173 173 173 174 174 174 174 174 174 175 175 175 175 175 175 176 176 176 176 176 177 177 177 177 177 177 178 178 178 178
AT332_AM_E0
11.1.1.46 11.1.1.47 11.1.1.48 11.1.1.49 11.1.1.50 11.1.1.51 11.1.1.52 11.1.1.53 11.1.1.54 11.1.1.55 11.1.1.56 11.1.1.57 11.1.1.58 11.1.1.59 11.1.1.60 11.1.1.61 11.1.1.62 11.1.1.63 11.1.1.64 11.1.1.65 11.1.1.66 11.1.1.67 11.1.1.68 11.1.1.69 11.1.1.70 11.1.1.71 11.1.1.72 11.1.2 11.1.2.1 11.1.2.2 11.1.2.3 11.1.2.4 11.1.2.5 11.1.2.6 11.1.2.7 11.1.2.8 11.1.2.9 11.1.2.10 11.1.2.11 11.1.2.12 11.1.2.13 11.1.2.14 11.1.2.15 11.1.2.16 11.1.2.17 11.1.2.18 11.1.2.19 11.1.2.20 11.1.2.21 11.1.3 11.1.3.1 11.1.3.2 11.1.3.3 11.1.4 11.1.4.1 11.1.4.2 11.1.4.3 11.1.4.4 11.1.4.5 11.1.5 11.1.5.1 11.1.5.2 11.1.5.3 11.1.5.4 11.1.5.5 11.1.5.6 11.1.5.7
Atoll 3.3.2 Administrator Manual Table of Contents
Synchronising Private and Shared Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Selecting the Logo 2 Check Box by Default in Print Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Filtering Predictions by Technology When Reading the XML Studies File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Enabling Event Viewer Messages for MapInfo File Import/Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Setting the Resolution of Population Maps in Coverage Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 Setting the Precision in Coverage Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Including Pixel-free Ranges in Coverage Prediction Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Changing Hot Spot Reference Surface in Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Exporting Only Visible Value Interval Layers of Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Avoiding Overlapping Pixels in Best Server Coverage Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Using Legacy Coverage Prediction Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Setting the Minimum ATL File Size Requiring Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Loading, Activating, and Setting Add-ins as Visible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Defining Online Map URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Changing the Default Cache Location for the Loaded Map Tiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Defining the Microsoft Bing Tile Server for Online Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Defining the Microsoft Bing Tile Server for Online Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Defining MapQuest for Online Searches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Managing Carriage Returns in Imported TXT/CSV Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Deleting the Filtering Zone on Removing Filters From Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Disabling the Database and Data Exchange Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Enabling Atoll to Automatically Restart on Improper Exit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Specifying Default Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Specifying the Default Storage of Favourite Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Restoring Focus and Computation Zones of a Favourite View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Fixing Antenna Electrical Azimuth and Tilt Values on Document Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Limiting the Antenna Selection Assistant to the Antenna folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 GUI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Defining the Parameters for the Default Sites Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Using a Unique Symbol for Remote Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Using the Transmitter Symbol for Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Keeping Transmitter Symbols From Changing on Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Displaying Filled Symbols for Inactive Transmitters on the Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Refreshing the Display Automatically When a New Station is Dropped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Hiding Information Displayed in the Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Displaying Date and Time in the Event Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Setting the Maximum Number of Lines to Coverage Prediction Tool Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Changing the Display for Downlink Smart Antenna Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Displaying Coverage Prediction Comments in the Legend Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Displaying Leading Zeros in the CELL_IDENTITY Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Making the Antenna Additional Electrical Downtilt Accessible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Increasing the Width of the Clutter Description Pane in the Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Hiding the Technology Name in the Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Displaying Objects’ Discrete Values with User-defined Colours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Displaying Vertical Beamwidth in Profile Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Locking Site and Transmitter Shading Colours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Case-insensitive Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Hexagonal Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Disabling Confirmation when Deleting a Site from the Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Distributed Calculation Server Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Detecting and Listing Distributed Calculation Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Setting the Distributed Calculation Server Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Modifying the Default Detection Time-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 License Management Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Setting an Alarm for the License End Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Blocking Access to Technology Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Blocking Access to the AFP Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Blocking Access to the ACP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Changing the NetHASP License Manager Idle Time Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Database Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Checking Data Integrity After Database Upgrade and Data Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Preselecting "Refresh Unmodified Data Only" by Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Automatically Running a Database Integrity Check at Open or Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Displaying Database Tables in the Event Viewer at Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Allowing Null Entries in Non-nullable Custom Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Automatically Running GSM Subcell Audit at Open or Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Modifying the Default Database Connection Time-out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
7
Atoll 3.3.2 Administrator Manual Table of Contents
11.1.5.8 11.1.5.9 11.1.5.10 11.1.5.11 11.1.5.12 11.1.5.13 11.1.5.14 11.1.5.15 11.1.5.16 11.1.5.17 11.1.6 11.1.6.1 11.1.6.2 11.1.6.3 11.1.6.4 11.1.6.5 11.1.6.6 11.1.6.7 11.1.6.8 11.1.6.9 11.1.6.10 11.1.6.11 11.1.6.12 11.1.6.13 11.1.6.14 11.1.6.14.1 11.1.6.14.2 11.1.6.15 11.1.6.16 11.1.6.17 11.1.6.18 11.1.6.19 11.1.6.20 11.1.6.21 11.1.6.22 11.1.6.23 11.1.6.24 11.1.6.25 11.1.6.26 11.1.6.27 11.1.6.28 11.1.6.29 11.1.6.30 11.1.6.31 11.1.6.32 11.1.6.33 11.1.6.34 11.1.6.35 11.1.6.36 11.1.6.37 11.1.7 11.1.7.1 11.1.7.2 11.1.7.3 11.1.7.4 11.1.7.5 11.1.7.6 11.1.7.7 11.1.7.8 11.1.7.9 11.1.7.10 11.1.7.11 11.1.7.12 11.1.7.13 11.1.7.14 11.1.7.15 11.1.7.16
8
© Forsk 2016
Changing the Database Export Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making Atoll Case-Sensitive for Database Import From Planet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Sign for KClutter When Importing Data From Planet EV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Clutter No Data Value for When Importing Data From Planet EV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling/Disabling Password Prompt at Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Archiving Data to Databases Using Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keeping Separate Work and Master Path Loss Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Partial Refresh from Recently Upgraded Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Type of Database Being Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Only the First Export to Database Error in a Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Common Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Antenna Patterns Modelling Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling Automatic Locking of Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Shadowing Margin in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting a Default Value for the Cell Edge Coverage Probability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling Indoor Coverage in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the Resolution for the LOS Area Calculation Around a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Embedding Path Losses in New Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping Calculations on Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warning About Prediction Validity When Display Options are Modified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reading Exact Altitudes From the DTM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting a Common Display Resolution For All Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Priorities for GUI and Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Number of Parallel Processors and Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parallel Calculation of Monte Carlo Simulations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parallel Calculation of Monte Carlo Simulations in GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parallel Calculation of Monte Carlo Simulations in UMTS HSPA and CDMA2000 . . . . . . . . . . . . . . . Performing Calculations in Read-Only Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying Transmitter, Repeater, and Remote Antenna Coverage Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling Rounding of Antennas’ Updated Half-power Beamwidth Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Rounding Method Used for Profile Extraction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Estimating Required and Used Memory Size for UMTS Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling Calculations Over NoData Values for DTM and Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Co-planning: Calculating Predictions in the Current Document Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Co-planning: Calculating Predictions in Serial or in Parallel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forcing Neighbour Symmetry Only Inside Focus Zone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Poisson Distribution in Monte Carlo Simulations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculating EIRP from Max Power in Signal Level Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Excluding Filtered Transmitters from the List of Neighbours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Weighting Factor of the Effective Inter-transmitter Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extending the Maximum Inter-site Distance to Repeaters and Remote Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forcing the Real Inter-site Distance Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prioritising Individual Inter-site Distances in Neighbour Importance Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keeping Assigned Neighbours that are not Symmetric with the Reference Transmitter . . . . . . . . . . . . . . . . . . . . . . . . Keeping Neighbours that Relate to Themselves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling and Disabling Per-site Path Loss Matrix Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining a Global Maximum Path Loss Calculation Radius . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preserving Loss and Noise Figures with no Assigned Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Linear Interpolation of Inter-technology IRF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Real-Time Profile Drawing Method in Point Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GSM GPRS EDGE Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Considering Inter-technology Interference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Considering Overlapping Zones for IM Calculation Based on Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Default BSIC Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking Database Consistency Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling the Maximum Range Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling the Support for Multi-band Transmitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Best Server Calculation Method in Same Priority HCS Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hiding AFP Advanced Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hiding AFP Hopping Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hiding Violations from Low Importance GSM Neighbours in AFP Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hiding Violations Between Non-synchronised MALs-MAIOs in AFP Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying the Thresholds for Important Violations in AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selecting the Interference Matrices Used During the AFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Maximum Number of Transmitters for Reuse Distance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the Maximum Number of Separation Violations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making Redundant Fields in the Transmitters Table Read-only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
193 193 193 194 194 194 194 195 195 195 195 195 196 196 196 196 197 197 197 197 197 198 198 198 199 199 199 199 199 200 200 200 200 200 201 201 201 201 201 201 202 202 202 202 202 203 203 203 203 203 204 204 204 204 204 204 205 205 205 206 206 206 206 206 207 207 207
AT332_AM_E0
11.1.7.17 11.1.7.18 11.1.7.19 11.1.7.20 11.1.7.21 11.1.7.22 11.1.8 11.1.8.1 11.1.8.2 11.1.8.3 11.1.8.4 11.1.8.5 11.1.8.6 11.1.8.7 11.1.8.8 11.1.8.9 11.1.8.10 11.1.8.11 11.1.8.12 11.1.8.13 11.1.8.14 11.1.8.15 11.1.8.16 11.1.8.17 11.1.8.18 11.1.8.19 11.1.8.20 11.1.8.21 11.1.8.22 11.1.8.23 11.1.8.24 11.1.9 11.1.9.1 11.1.9.2 11.1.9.3 11.1.9.4 11.1.9.5 11.1.9.6 11.1.9.7 11.1.9.8 11.1.9.9 11.1.9.10 11.1.9.11 11.1.9.12 11.1.9.13 11.1.9.14 11.1.9.15 11.1.9.16 11.1.9.17 11.1.9.18 11.1.9.19 11.1.9.20 11.1.9.21 11.1.9.22 11.1.9.23 11.1.9.24 11.1.9.25 11.1.9.26 11.1.9.27 11.1.9.28 11.1.9.29 11.1.9.30 11.1.10 11.1.10.1 11.1.10.2 11.1.11 11.1.11.1
Atoll 3.3.2 Administrator Manual Table of Contents
Setting the Transmission Diversity Gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Deactivating Frequency Band Filtering in IM Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Starting TRX Indexes at 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Hiding the TRX Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Listing TRX Types in Alphabetical Order in Subcells Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Automatically Correcting Out-of-range Subcell Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 UMTS HSPA, CDMA2000, and TD-SCDMA Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Suppressing Cell Name Carrier Suffixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Disabling Macro-diversity (SHO) Gains Calculation for Ec/Io and Eb/Nt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Calculating and Displaying Peak or Instantaneous HSDPA Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Setting the Power to Use for Intra-cell Interference in HSDPA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Enabling Coverage Predictions of Connection Probabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Setting the Calculation Method for HS-PDSCH CQI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Enabling Orthogonality Factor in Pilot EC/NT Calculation in HSDPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Setting the Maximum Number of Rejections for Mobiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Setting the Maximum Number of Rejections for HSDPA Mobiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Defining an Offset With Respect to The Thermal Noise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Setting Precision of the Rasterisation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Defining the Number of Iterations Before Downgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Adjusting the Working of the Proportional Fair Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Displaying the Ec/I0 of Rejected Mobiles in Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Switching Back to the Old Best Server Determination Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Switching Back to the Old Radio Bearer Allocation Algorithm for Multi-carrier EVDO Rev.B . . . . . . . . . . . . . . . . . . . . . 213 Displaying Automatic Allocation Cost Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Selecting SC and PN Offset Allocation Strategies Available in the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 Defining a Fixed Interval Between Scrambling Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Compressed Mode: Restricting Inter-carrier and Inter-technology Neighbour Allocation . . . . . . . . . . . . . . . . . . . . . . . 214 Setting the Maximum AS Size for SC Interference Prediction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Displaying Uplink Total Losses in Coverage by Signal Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Setting the Maximum UL Reuse Factor for HSUPA Users’ Noise Rise Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Configuring HSUPA Resource Allocation for Active Set Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 LTE, WiMAX, Wi-Fi, and LPWA Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Blocking Access to IEEE Parameters in WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Using Only Bearers Common Between the Terminal’s and Cell’s Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Enabling Display of Signals per Subcarrier Point Analysis in LTE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Including Cyclic Prefix Energy in LTE Signal Level Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Excluding Cyclic Prefix Energy in WiMAX and Wi-Fi Signal Level Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Ignoring Inter-Neighbour Preamble Index Collision in WiMAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Ignoring Inter-Neighbour Physical Cell ID Collision in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Renaming OPUSC Zone to PUSC UL in WiMAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Deactivating Uniform Distribution of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Taking Second Order Neighbours into Account in the AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Excluding the Adjacent Channel Overlap from the AFP Cost Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Synchronised/Unsynchronised LTE Downlink Interference Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Setting PDCCH to 100% Loaded in LTE Interference Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Calculating EIRP from RS EPRE in LTE Signal Level Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Averaging the Uplink Noise Rise in dB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Deactivating Service Max Throughput Demand Downgrading in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Displaying Pixels with Zero Throughput in Coverage Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Setting Uplink Noise Rise Control Parameters in LTE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Using the LTE ABS Patterns on Cell-edge Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Applying the LTE ABS Collision Probability on Interference from RS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Switching Between LTE Carrier Aggregation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Switching Between LTE Multi-Server Scheduling Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Switching Between LTE Carrier Aggregation PCell Selection Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Displaying Grid-of-Beam Patterns in Logarithmic Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Allowing Multi-cell Transmitters Using Different Frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Changing the LTE Cell-Edge Determination Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Filtering LTE Cell Groups Loaded From a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Allocating PRACH RSIs from Non-Overlapping Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Excluding DMRS Overhead from Cell Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Changing the Display Mode of the Number of Aggregated Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 3GPP Multi-RAT Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 BSIC, SC, and PCI Allocation with Inter-technology Neighbour Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Multi-RAT Technology Selection Default Behaviour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Microwave Radio Links Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Modifying the Default Format of Link Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
9
Atoll 3.3.2 Administrator Manual Table of Contents
11.1.11.2 11.1.11.3 11.1.11.4 11.1.11.5 11.1.11.6 11.1.11.7 11.1.11.8 11.1.11.9 11.1.11.10 11.1.11.11 11.1.11.12 11.1.11.13 11.1.12 11.1.12.1 11.1.12.2 11.1.12.3 11.1.12.4 11.1.12.5 11.1.12.6 11.1.12.7
© Forsk 2016
Updating A>>B and B>>A Profiles in Real-time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling Shielding Factor on Wanted Signal at Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Considering XPIF value in Interference for Dual-Polar Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Making the ITU-R P.530-5 Method Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Old Min C/I Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solving Alignment Issue in Generated Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining Default Configuration Files for Link Budgets Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining a Default Configuration File for the Channel Arrangement Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining a Default Template for Microwave Links Custom Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Considering ATPC for ANSI and ETSI Modes Similarly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hiding Clutter from the Profile Analysis View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Decoupling Calculation Method for Co-site Interference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Measurement Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Additional Information in Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Number of Transmitters per Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recalculating Distances of Points From There Serving Cells at Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Defining the BCCH and BSIC Columns for FMT Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Drive Test Data with Scrambling Codes as Integers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Drive Test Data for Active and Filtered Transmitters Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specifying the Location of the ACP.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
222 222 222 223 223 223 223 224 224 224 224 224 224 224 225 225 225 225 225 226
11.2 ACP Initialisation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 11.2.1 Managing ACP Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 11.2.2 ACP GUI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 11.2.2.1 Default Settings of the Optimisation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 11.2.2.2 Default Settings of the Optimisation > Cost Control Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 11.2.2.3 Default Settings of the Optimisation > Advanced Cost Control Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 11.2.2.4 Automatically Creating Custom Zones on the Optimisation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 11.2.2.5 Default Settings of the Objectives Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 11.2.2.6 Default Settings of the Reconfiguration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 11.2.2.7 Default Settings of the Reconfiguration > Sites vertical tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 11.2.2.8 Defining the Inter-site Distance in Co-located Site Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 11.2.2.9 Defining the Inter-antenna Distance in Co-located Transmitter Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 11.2.2.10 Custom Columns on Reconfiguration > Sites Vertical Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 11.2.2.11 Default Settings of the Reconfiguration > Transmitters Vertical Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 11.2.2.12 Custom Columns on the Reconfiguration > Transmitters/Remotes Vertical Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 11.2.2.13 Default Settings of the Optimisation > EMF Exposure Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 11.2.2.14 Default Settings of the Optimisation > Multi-Storey Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 11.2.2.15 Controlling Antenna Pattern Smoothing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 11.2.2.16 Default Settings of the Antenna Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 11.2.2.16.1 Global Antenna Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 11.2.2.16.2 Patterns Vertical Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 11.2.2.16.3 Physical Antenna Vertical Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 11.2.2.17 Defining the Antenna Masking Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 11.2.2.18 Defining Reconfiguration Values Using Custom Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 11.2.2.18.1 Defining Reconfiguration Values for Transmitters, Repeaters, and Secondary Antennas Using Custom Fields242 11.2.2.18.2 Defining Reconfiguration Values for Cells Using Custom Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 11.2.2.18.3 Defining Reconfiguration Values for Sites Using Custom Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 11.2.2.18.4 Defining Reconfiguration Values for Antennas Using Custom Fields . . . . . . . . . . . . . . . . . . . . . . . . . 244 11.2.2.19 Defining Site Class Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 11.2.2.19.1 Defining Automatic Site Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246 11.2.2.19.2 Automatic Assignment of Site Classes in the ACP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 11.2.2.20 Defining the Appearance of a Running Optimisation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 11.2.2.20.1 Defining the Colours in the Analysis Maps on the Quality Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 11.2.2.20.2 Other Components of the Optimisation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 11.2.2.21 Defining the Appearance of ACP Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 11.2.2.22 Defining New Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 11.2.2.23 Defining the Functionality of the Commit Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 11.2.2.24 Defining the Appearance of the Overlay Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 11.2.2.25 Defining the Appearance of the Graph Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 11.2.2.26 Defining the Default Font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 11.2.2.27 Exporting Optimisation Results in XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251 11.2.3 ACP Core Engine Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 11.2.3.1 Log File Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 11.2.3.2 Calculation Thread Pool Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 11.2.3.3 Number of Threads Used for Propagation Model Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
10
AT332_AM_E0
11.2.3.4 11.2.3.5 11.2.3.6 11.2.3.7 11.2.3.8 11.2.3.9 11.2.3.10 11.2.3.11 11.2.3.12 11.2.3.13 11.2.3.14 11.2.3.15 11.2.3.16 11.2.3.17 11.2.4 11.2.5 11.2.5.1 11.2.5.2
Atoll 3.3.2 Administrator Manual Table of Contents
Memory Management Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 Automatic Stops of the Search Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Considering Progressive Thresholds for Some Quality Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Macro Diversity Gains Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Transmitter Altitude Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254 Automatic Candidate Positioning Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Setting a Minimum Inter-site Distance for Site Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Balancing Speed, Memory Use, and Accuracy in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255 Accessing Raster Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Filtering Clutter Class Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Fixed Ratio Between Pilot Power and Max Power (UMTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Showing Initial/Final Total Poweror DL Load on Sectors Tab (UMTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Custom Columns on the Sectors tab of the Optimisation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 Enabling Multi-technology Optimisation Including WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 EMF Exposure Core Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 Other Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 EMF and Multi-Storey Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Validity of Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
11
Atoll 3.3.2 Administrator Manual Table of Contents
12
© Forsk 2016
Atoll 3.3.2 Administrator Manual Chapter : Atoll 3.3.2 Administrator Manual
AT332_AM_E0
Atoll 3.3.2 Administrator Manual This Administrator Manual explains how to install, configure, and deploy Atoll and how to set up back-end databases and manage users in a multi-user environment. Database structures of the different technology modules are also provided for reference.
About Atoll Atoll is a 64-bit multi-technology wireless network design and optimisation platform. Atoll is open, scalable, flexible, and supports wireless operators throughout the network life cycle, from initial design to densification and optimisation. Atoll includes integrated single RAN – multiple RAT network design capabilities for both 3GPP (GSM/UMTS/LTE) and 3GPP2 (CDMA/LTE) technology streams. It provides operators and vendors with a powerful native 64-bit framework for designing and optimising current and future integrated multi-technology networks. Atoll supports multi-technology HetNets, small cell planning, and Wi-Fi offloading. Atoll Microwave is a complete backhaul and microwave link planning solution based on the leading Atoll platform, which includes a high performance GIS and advanced data and user management features. Atoll Microwave can share its site database with Atoll radio planning and optimisation modules, thus allowing easy data consistency management across the operator organisation. Atoll’s integration and automation features help operators smoothly automate planning and optimisation processes through flexible scripting and SOA-based mechanisms. Atoll supports a wide range of implementation scenarios, from standalone to enterprise-wide server-based configurations. If you are interested in learning more about Atoll, please contact your Forsk representative to inquire about our training solutions.
About Forsk Forsk is an independent company providing radio planning and optimisation software solutions to the wireless industry since 1987. In 1997, Forsk released the first version of Atoll, its flagship radio planning software. Since then, Atoll has evolved to become a comprehensive radio planning and optimisation platform and, with more than 7000 installed licenses worldwide, has reached the leading position on the global market. Atoll combines engineering and automation functions that enable operators to smoothly and gradually implement SON processes within their organisation. Today, Forsk is a global supplier with over 450 customers in 120 countries and strategic partnerships with major players in the industry. Forsk distributes and supports Atoll directly from offices and technical support centres in France, USA, and China as well as through a worldwide network of distributors and partners. Since the first release of Atoll, Forsk has been known for its capability to deliver tailored and turn-key radio planning and optimisation environments based on Atoll. To help operators streamline their radio planning and optimisation processes, Forsk provides a complete range of implementation services, including integration with existing IT infrastructure, automation, as well as data migration, installation, and training services.
Getting Help The online help system that is installed with Atoll is designed to give you quick access to the information you need to use the product effectively. It contains the same material as the Atoll 3.3.2 User Manual. You can browse the online help from the Contents view, the Index view, or you can use the built-in Search feature. You can also download manuals from the Forsk web site at: http://www.forsk.com/MyForskAccount/
Printing Help Topics You can print individual topics or chapters from the online help. To print help topics or chapters: 1. In Atoll, click Help > Help Topics. 2. In the Contents tab, expand the table of contents. 3. Right-click the section or topic that you want to print and click Print. The Print Topics dialog box appears.
13
Atoll 3.3.2 Administrator Manual Chapter : Atoll 3.3.2 Administrator Manual
© Forsk 2016 Forsk
4. In the Print Topics dialog box, select what you want to print: • •
If you want to print a single topic, select Print the selected topic. If you want to print an entire section, including all topics and sections in that section, select Print the selected heading and all subtopics.
5. Click OK.
About Atoll Documentation The following PDF manuals are available for Atoll and Atoll Microwave and can be downloaded from the Forsk web site at: http://www.forsk.com/MyForskAccount/ • • • • • •
Atoll User Manual Atoll Administrator Manual Atoll Data Structure Reference Guide Atoll Technical Reference Guide Atoll Task Automation Guide Atoll Model Calibration Guide
To read PDF manuals, download Adobe Reader from the Adobe web site at: http://get.adobe.com/reader/ Hardcopy manuals are also available. For more information, contact to your Forsk representative.
Contacting Technical Support Forsk provides global technical support for its products and services. To contact the Forsk support team, visit the My Forsk web site at: http://www.forsk.com/MyForskAccount/ Alternatively, depending on your geographic location, contact one of the following support teams: •
Forsk Head Office For regions other than North and Central America and China, contact the Forsk Head Office support team: • • •
Tel.: +33 562 747 225 Fax: +33 562 747 211 Email: [email protected]
Opening Hours: Monday to Friday 9.00 am to 6.00 pm (GMT +1:00) •
Forsk US For North and Central America, contact the Forsk US support team: • • •
Tel.: 1-888-GO-ATOLL (1-888-462-8655) Fax: 1-312-674-4822 Email: [email protected]
Opening Hours: Monday to Friday 8.00 am to 8.00 pm (Eastern Standard Time) •
Forsk China For China, contact the Forsk China support team: • • •
Tel: +86 20 8557 0016 Fax: +86 20 8553 8285 Email: [email protected]
Opening Hours: Monday to Friday 9.00am to 5.30pm (GMT+08:00) Beijing, Chongqing, Hong Kong, Urumqi.
14
Chapter 1 Getting Started This chapter covers the following topics: •
"Supported Technologies" on page 17
•
"Supported Operating Systems" on page 17
•
"Supported Database Management Systems" on page 18
•
"Supported Installation Configurations" on page 18
•
"Recommended Hardware and Software" on page 18
•
"In a single-user or single-server configuration, storing locally shared data instead of using a file server can improve response time and calculation performance." on page 21
Atoll 3.3.2 Administrator Manual © Forsk 2016
16
Atoll 3.3.2 Administrator Manual Chapter 1: Getting Started
AT332_AM_E0
1 Getting Started Atoll is an open, scalable, and flexible multi-technology network design and optimisation platform that supports wireless operators throughout the network life cycle, from initial design to densification and optimisation. Atoll supports a wide range of implementation scenarios, from single-user standalone to enterprise-wide server-based configurations using distributed and multi-threaded computing. This manual explains how to install, configure, and deploy Atoll and how to set up back-end databases and manage users in a multi-user environment. In this chapter, the following are explained: • • • • •
"Supported Technologies" on page 17 "Supported Operating Systems" on page 17 "Supported Database Management Systems" on page 18 "Supported Installation Configurations" on page 18 "Recommended Hardware and Software" on page 18
1.1 Supported Technologies Atoll supports the following radio technologies: GSM/GPRS/EDGE, UMTS HSPA, CDMA2000 1xRTT/1xEV-DO, LTE, TD-SCDMA, WiMAX, and Wi-Fi. It also supports 3GPP Multi-RAT (GSM + UMTS + LTE) and 3GPP2 Multi-RAT (CDMA2000 + LTE). Atoll Microwave supports detailed design and analysis of microwave link networks.
1.2 Supported Operating Systems Atoll supports the following versions of Microsoft Windows operating systems. Atoll also supports VMWare ESXi 4.x, 5.1, and 5.5 virtualisation platforms. Supported Operating Systems for Atoll 64-bit • • • • • • •
Microsoft Windows 10 Professional and Enterprise (64-bit) Microsoft Windows 8 and 8.1 Professional and Enterprise (64-bit) Microsoft Windows 7 (64-bit) Microsoft Windows Server 2012 R2 Microsoft Windows Server 2012 Microsoft Windows Server 2008 R2 SP1 Microsoft Windows Server 2008 SP2 (64-bit) Among other Microsoft Windows components, Atoll 64-bit uses Microsoft Access Database Engine 64-bit. Microsoft Access Database Engine 64-bit is included in Microsoft Office 64-bit, and is also available as a free redistributable Microsoft Windows component from the Forsk support website. •
•
If the computer on which you wish to install and run Atoll 64-bit already has Microsoft Office installed, you must upgrade it to Microsoft Office 64-bit (version 2010 SP1 or newer). If you do not have Microsoft Office installed, you can download and install the Microsoft Access Database Engine 64-bit redistributable (version 2010 SP1) needed by Atoll 64-bit from the Forsk support website.
Note: Installing Microsoft Office 64-bit or the Microsoft Access Database Engine 64-bit requires uninstalling any 32-bit Microsoft Office components that may be installed on the computer. Supported Operating Systems for Atoll 32-bit • • • • • • • • •
Microsoft Windows 10 Professional and Enterprise (32-bit and 64-bit) Microsoft Windows 8 and 8.1 Professional and Enterprise (32-bit and 64-bit) Microsoft Windows 7 (32-bit and 64-bit) Microsoft Windows Vista SP2 (32-bit and 64-bit) Microsoft Windows XP Professional SP3 (32-bit and 64-bit) Microsoft Windows Server 2012 R2 Microsoft Windows Server 2012 Microsoft Windows Server 2008 R2 SP1 Microsoft Windows Server 2008 (32-bit and 64-bit)
17
Atoll 3.3.2 Administrator Manual Chapter 1: Getting Started
•
© Forsk 2016
Microsoft Windows Server 2003
1.3 Supported Database Management Systems In a multi-user environment, databases allow several users to share data without the risk of data inconsistency. In a multi-user environment, user documents are connected to a central database, in which users store their work on a common project. Atoll supports the following RDBMS: •
• •
Oracle 10g, 11g, and 12c • Use client versions 10.0.2.3 or later with Oracle 10g • Use client versions 11.2.0.4 or later with Oracle 11g Microsoft SQL Server 2005, 2008, 2012, and 2014 Microsoft Access 2003 and later
The physical location of databases varies according to the type of the database. The following table shows where the database must be installed:
a.
Database
Server
Client computer
Microsoft Access
No
Yesa
Microsoft SQL server
Yes
No
Oracle
Yes
Yes (Oracle client)
It is possible to work with an Atoll document connected to a Microsoft Access database even if Microsoft Access is not installed on the computer.
1.4 Supported Installation Configurations Depending on your requirements, Atoll can be installed in a: •
Single-user standalone configuration: Atoll installed on each individual user computer with a fixed license key plugged in each computer.
•
Multi-user thick client configuration: Atoll installed on each individual user computer on a network with a floating license management server that allocates license tokens to Atoll sessions run by users on their computers.
•
Multi-user thin client configuration: Atoll installed on servers connected to user computers and a floating license management server on a network. The floating license management server allocates license tokens to Atoll sessions run by the users on the servers. The servers can be Citrix-based, where users run Atoll sessions on the servers through the Citrix interface.
1.5 Recommended Hardware and Software This section provides guidelines for dimensioning client computers and servers on your network for optimum performance with Atoll. This section lists the recommended hardware and software for: • • • • •
"Single-user Standalone Configuration" on page 18 "Multi-user Thick Client Configuration" on page 19 "Multi-user Thin Client Configuration" on page 20 "Floating License Servers" on page 21 "File Servers" on page 21
1.5.1 Single-user Standalone Configuration In a single-user standalone configuration, the Atoll installation is local, i.e.: • •
Atoll is installed and run directly on the user workstation and all the core software and drivers are provided with the Atoll installer program. The following data is stored locally: coverage prediction files, geographic data, and user projects.
The user license is managed locally (fixed license): •
18
A USB port must be available on the user workstation to plug a fixed license key dongle.
Atoll 3.3.2 Administrator Manual Chapter 1: Getting Started
AT332_AM_E0
Figure 1.1: Single-user Standalone Configuration The following table lists the required/recommended hardware and software in a single-user standalone Atoll configuration: Atoll Workstation
a.
Processor
Core i7 at 2.5+ GHz
RAM
8 GB or more
Storage
512 GBa (SSD recommended)
Operating System
Windows 7 Windows 8/8.1 Professional or Enterprise
Depends on size of locally stored data.
1.5.2 Multi-user Thick Client Configuration In a multi-user thick client configuration, the Atoll installation is local, i.e.: • •
Atoll is installed and run directly on user workstations and all the base software and drivers are provided with Atoll. The following data is stored on user workstations: coverage prediction files, geographic data, and user projects.
The user licenses are managed locally (fixed licenses) or from a server (floating licenses): • •
A USB port must be available on the user workstation to plug a fixed license key dongle. The nethasp.ini file must be available on the workstation to provide information on accessing a floating license server through the network.
A connection with the central database is required during synchronisation operations, to exchange between users. If you are working with an Oracle database, you must install the relevant Oracle clients on the user computers.
Figure 1.2: Multi-user Thick Client Configuration The following tables list the required/recommended hardware and software in a multi-user thick client configuration:
Processor
Atoll Workstation
Atoll Database
Core i7 at 2.5+ GHz
Xeon E3/E5 family or equivalent
8 GB or more
8 GB or more
RAM Storage
512 GB
a (SSD recommended)
2x146 GB (RAID 1) or moreb
19
Atoll 3.3.2 Administrator Manual Chapter 1: Getting Started
© Forsk 2016
Operating System a. b.
Atoll Workstation
Atoll Database
Windows 7 Windows 8/8.1 Professional or Enterprise
Oracle: Windows / UNIX / Linux / Solaris SQL Server: Microsoft Windows
Depends on size of locally stored data. Tablespace of around 400 MB per 10,000 transmitters.
1.5.3 Multi-user Thin Client Configuration Users can work with Atoll installed on application servers through thin clients such as Remote Desktop or Citrix. In a multi-user thin client configuration, the Atoll installation is centralised, i.e.: • • •
Atoll is accessed via a thin client interface Server resources are used to run Atoll and perform calculations The following data is stored on a file server: coverage prediction files, geographic data, and user projects.
An asynchronous connection is required with the central database for data exchange between users. The user licenses are managed through the network and a limited bandwidth (300+ kbps per user) is required between servers and client workstations for satisfactory performance. If you are working with an Oracle database, you must install the relevant Oracle clients on the user computers.
Figure 1.3: Multi-user Thin Client Configuration The following tables list the required/recommended hardware and software in a multi-user thin client Atoll configuration: Atoll Application Server
Atoll Database Server
Processor
Xeon E5/E7 family 2 cores per user at 2.5 GHz or more
Xeon E3/E5 family or equivalent
RAM
4+ GB per user (min 8 GB)
8 GB or more
Storage
256 GB (SSD recommended)
2x146 GB (RAID 1) or morea
Operating System
Windows Server 2008 R2 SP1 Windows Server 2012 and 2012 R2
Oracle: Windows / UNIX / Linux / Solaris SQL Server: Microsoft Windows
Connectivity
Gigabit Ethernet or better
Gigabit Ethernet or better
Thin Client Configuration
Remote Desktop Citrix XenApp 6.5 or later
-
Virtualisation
VMWare ESXi 4.x / 5.1 / 5.5
-
-
Oracle 10g, 11g, 12c Microsoft SQL Server 2005, 2008, 2012, 2014
RDBMS a.
20
Tablespace of around 400 MB per 10,000 transmitters.
Atoll 3.3.2 Administrator Manual Chapter 1: Getting Started
AT332_AM_E0
1.5.4 Floating License Servers The floating license management server: • • • • •
Must be accessible to all the user computers / Citrix servers on the network in order to provide license tokens for Atoll sessions. Must have a steady and reliable network connection with user computers / Citrix servers. Must have the HASP license manager installed and running. For more information, see "Working with Floating Licenses" on page 43. Must have the floating license key plugged in. Can be one of the application servers.
1.5.5 File Servers File servers can store shared data, such as geographic data, path loss matrices, Atoll configuration and initialisation files, and user projects. The required hard disk space must be determined from the file sizes of this data. Gigabit Ethernet is recommended for connecting user computers, application servers, and file servers. Network bandwidth is required for data exchange between Atoll sessions and file servers. In a multi-user or multi-server configuration, the use of a file server can significantly improve data management by providing a central repository for shared files. In this case, a higher bandwidth is required between the user workstations and the file server (1 Gbps or higher). In a single-user or single-server configuration, storing locally shared data instead of using a file server can improve response time and calculation performance.
21
Atoll 3.3.2 Administrator Manual Chapter 1: Getting Started
22
© Forsk 2016
Chapter 2 Atoll and Component Installation This chapter covers the following topics: •
"Installing Atoll Using the Setup Wizard" on page 25
•
"Installing Atoll C++ Development Kit" on page 28
•
"Setup Command Line Parameters" on page 29
•
"Installing and Uninstalling Add-ins" on page 30
•
"Installing and Uninstalling Macros" on page 30
•
"Atoll Command Line Parameters" on page 31
•
"Troubleshooting and Other Information" on page 32
Atoll 3.3.2 Administrator Manual © Forsk 2016
24
Atoll 3.3.2 Administrator Manual Chapter 2: Atoll and Component Installation
AT332_AM_E0
2 Atoll and Component Installation The following sections describe the installation procedures for Atoll and its following components: • • • •
Driver for Fixed Licence Keys Distributed Calculation Server Atoll Management Console Add-ins and macros
You need administrator rights for installing Atoll and its components.
2.1 Installing Atoll Using the Setup Wizard To install Atoll: •
If you work with fixed licenses, you must unplug the key before the installation and wait for the installation to finish before plugging it back in.
•
Disable UAC (User Account Control) for the following versions of Microsoft Windows. If you are installing Atoll on other versions of Microsoft Windows, proceed to step 1. • • • • • •
Microsoft Windows Vista Microsoft Windows 7 Microsoft Windows 8 Microsoft Windows Server 2008 Microsoft Windows Server 2008 R2 Microsoft Windows Server 2012
To disable UAC: a. Go to Control Panel > User Accounts. b. Select Change User Account Control settings. The User Account Control Settings dialog box appears. c. Choose Never notify. d. Click OK. •
If you are installing Atoll 64-bit, make sure that the Microsoft Access Database Engine 64-bit is already installed on the computer. Microsoft Access Database Engine 64-bit is included in Microsoft Office 64-bit, and is also available as a free redistributable Microsoft Windows component from the Forsk support website. If the computer on which you wish to install and run Atoll 64-bit already has Microsoft Office installed, you must upgrade it to Microsoft Office 64-bit (version 2010 SP1 or newer). This will automatically install the Microsoft Access Database Engine 64-bit. If you do not have Microsoft Office installed, you can download and install the Microsoft Access Database Engine 64bit redistributable needed by Atoll 64-bit from the Forsk support website. Installing Microsoft Office 64-bit requires uninstalling any 32-bit Microsoft Office components that may be installed on the computer.
1. Run the Atoll setup. The setup program uses a wizard interface, with a step-wise description of the installation. You can: • • •
Click Next to proceed to the next step, Click Back to go back and modify previously set options, or Click Cancel to cancel the installation.
2. Click Next. The Select Destination Location dialog box appears. 3. Select the destination folder for the installation: •
If you are installing Atoll 32-bit, the default installation folder is: • C:\Program Files\Forsk\Atoll in the 32-bit versions of Microsoft Windows, or • C:\Program Files (x86)\Forsk\Atoll in the 64-bit versions of Microsoft Windows
•
If you are installing Atoll 64-bit, the default installation folder is: • C:\Program Files\Forsk\Atoll in the 64-bit versions of Microsoft Windows
You can select a different location by clicking Browse.
25
Atoll 3.3.2 Administrator Manual Chapter 2: Atoll and Component Installation
© Forsk 2016
Figure 2.1: Select Destination Location dialog box for Atoll 4. Select the Create a system restore point check box if you wish to the Atoll setup to create a system restore point. 5. Click Next. The Select Components dialog box appears. 6. Select the components to install. • • •
Full installation: Atoll and all its components will be installed. Compact installation: Only Atoll will be installed. Custom installation: Atoll and the selected components will be installed.
Figure 2.2: Select Components dialog box 7. Click Next. If you selected the Distributed Calculation Server component for installation, the Logon Information dialog box appears. If you did not select this component, the Select Start Menu Folder dialog box appears. In which case, proceed to step 8.
Figure 2.3: Select Components dialog box a. Enter the Domain name, Username, and Password. This information will be used to run the distributed calculation service on the computer, and allow other users of the domain to access this service. b. Click Next. The Select Start Menu Folder dialog box appears
26
Atoll 3.3.2 Administrator Manual Chapter 2: Atoll and Component Installation
AT332_AM_E0
8. Select the Start Menu folder for Atoll. The default Start Menu folder for Atoll is Atoll. You can select a different folder by clicking Browse.
Figure 2.4: Select Start Menu Folder dialog box 9. Click Next. The Ready to Install dialog box appears. 10. Review the installation parameters.
Figure 2.5: Ready to Install dialog box 11. Click Install. Atoll and its selected components are installed on the computer. •
If you work with fixed licenses and you installed the Driver for Fixed Licence Keys, restart the computer. Restarting the computer is necessary for the driver to work.
•
If you work with fixed licenses, plug in the fixed license key.
•
On the versions of Microsoft Windows that support UAC (disabled before the installation), run Atoll once using an administrator account and with UAC disabled when the installation is complete. •
If the following files do not already exist in the installation folder, empty ones are created by the setup: • [Atoll installation folder]\Atoll.ini • [Atoll installation folder]\AntennaImport.ini • [Atoll installation folder]\CWMeasurementsImport.ini • [Atoll installation folder]\DriveTestDataImport.ini • [Atoll installation folder]\coordsystems\Favourites.cs These files are not removed when Atoll is uninstalled.
•
If you have installed Atoll on a Citrix server, you must publish it to make it accessible to users.
To restrict access to the Atoll installation folder, you can assign read/write access rights to this folder to administrators and read-only rights to end users.
27
Atoll 3.3.2 Administrator Manual Chapter 2: Atoll and Component Installation
© Forsk 2016
2.2 Installing Atoll C++ Development Kit To install the Atoll C++ development kit: •
Visual C++ must be installed before installing the Atoll C++ development kit.
•
Atoll should be installed for testing the add-ins.
•
Disable UAC (User Account Control) for the following versions of Microsoft Windows. If you are installing Atoll C++ development kit on other versions of Microsoft Windows, proceed to step 1. • • • • • •
Microsoft Windows Vista Microsoft Windows 7 Microsoft Windows 8 Microsoft Windows Server 2008 Microsoft Windows Server 2008 R2 Microsoft Windows Server 2012
To disable UAC: a. Go to Control Panel > User Accounts. b. Select Change User Account Control settings. The User Account Control Settings dialog box appears. c. Choose Never notify. d. Click OK. 1. Run the Atoll C++ development kit setup. The setup program uses a wizard interface, with a step-wise description of the installation. You can, • • •
Click Next to proceed to the next step, Click Back to go back and modify previously set options, or Click Cancel to cancel the installation.
2. Click Next. The Select Destination Location dialog box appears. 3. Select the destination folder for the installation. •
If you are installing the Atoll C++ development kit with Atoll 32-bit, the default installation folder is: • C:\Program Files\Forsk\Atoll in the 32-bit versions of Microsoft Windows, or • C:\Program Files (x86)\Forsk\Atoll in the 64-bit versions of Microsoft Windows
•
If you are installing the Atoll C++ development kit with Atoll 64-bit, the default installation folder is: • C:\Program Files\Forsk\Atoll in the 64-bit versions of Microsoft Windows
You can select a different location by clicking Browse.
Figure 2.6: Select Destination Location dialog box 4. Click Next. The Ready to Install dialog box appears. 5. Review the installation parameters.
28
Atoll 3.3.2 Administrator Manual Chapter 2: Atoll and Component Installation
AT332_AM_E0
Figure 2.7: Ready to Install dialog box 6. Click Install. Atoll C++ Development Kit is installed on the computer.
2.3 Setup Command Line Parameters You can also install Atoll and its components from the command line. The Atoll setup program accepts optional command line parameters, which can be useful to administrators, and to other programs calling the setup program. For example, when automating the installation through batch files. The following command line parameters are accepted by the Atoll setup program. •
/SILENT, /VERYSILENT Instructs the setup to be silent or very silent. When the setup is silent the wizard window is not displayed but the installation progress window is. When a setup is very silent the installation progress window is not displayed. Everything else is normal. So, for example, error messages during installation are displayed, and also the startup prompt. If the setup is silent and it requires to restart the computer, but the /NORESTART option is not used (see below), it will display a Reboot now? message box. If it is very silent it will reboot without asking.
•
/NOCANCEL Prevents the user from cancelling the installation by disabling the Cancel button and ignoring clicks on the Close button. Useful along with /SILENT or /VERYSILENT.
•
/NORESTART Instructs the setup not to restart the computer even if necessary.
•
/SAVEINF="file name" Instructs the setup to save installation settings to the specified file. Use quotes if the file name contains spaces.
•
/LOADINF="file name" Instructs the setup to load the settings from the specified file after having checked the command line. This file can be prepared using the /SAVEINF command as explained above. Use quotes if the file name contains spaces.
•
/DIR="x:\folder name" Overrides the default installation folder displayed on the Select Destination Location wizard page. Use quotes if the folder name contains spaces.
•
/GROUP="folder name" Overrides the default start menu folder name displayed on the Select Start Menu Folder wizard page. Use quotes if the folder name contains spaces.
•
/LOG="file name" Causes the setup to create a log file listing file installation and actions taken during the installation process. This can be helpful for troubleshooting. For example, if you suspect a file is not being installed as it should be, the log file will tell you if the file was actually skipped and why. Use quotes if the filename contains spaces. If the file cannot be created, the setup will abort with an error message.
•
/SVRACCOUNT="domainname\username" The domain name and user name for installing the distributed calculation server.
•
/SVRPASSWD=password
29
Atoll 3.3.2 Administrator Manual Chapter 2: Atoll and Component Installation
© Forsk 2016
Password for installing the distributed calculation server. •
/TYPE=type name Overrides the default setup type. The setup type names are: • • •
Full installation: full Compact installation: compact Custom installation: custom
For full and compact setup types, the /COMPONENTS parameters are ignored. •
/COMPONENTS="comma separated list of component names" Overrides the default component settings. Using this command line parameter causes the setup to automatically select a custom installation type. Only the specified components will be selected. Component names are: • • • • •
Atoll: Atoll Export to Google Earth add-in: "Addins\GoogleEarth" Driver for fixed license keys: RainbowDongle Distributed calculation server: Atoll_Server Atoll Management Console: AMC
Example: To install Atoll, the distributed calculation server, and the driver for fixed license keys: /COMPONENTS="Atoll,Atoll_Server,RainbowDongle"
2.4 Installing and Uninstalling Add-ins The add-ins developed by Forsk have dedicated setup programs which are are described in each add-in’s documentation. Installed add-ins are automatically loaded by Atoll and appear in the Add-ins and Macros dialog box. If you wish that a certain add-in not be loaded, and hence be unavailable for activation in this dialog box, you can do so by adding an option in the Atoll.ini file. For more information, see "Loading, Activating, and Setting Add-ins as Visible" on page 181. To activate or deactivate an installed add-in in Atoll: 1. In Atoll, select Tools > Add-ins and Macros. The Add-ins and Macros dialog box appears. 2. Select the add-in’s check box to activate it, or clear the check box to deactivate it. Add-ins installed by the Atoll setup are uninstalled when Atoll is uninstalled. Available Add-ins The following Atoll add-ins can be downloaded in their most recent version from the Forsk web site at: http://www.forsk.com/support. For more information, contact to your Forsk representative. •
General add-ins: • Export to Google Earth (installed with Atoll) • Multistorey Prediction • Easy Location Converter • ArcView Grid ASCII Import • Multi-RAT Converter • Difference Plot • Update Sites With Geo Data • FCC Boundaries • Incidence Angle Footprint
•
Database add-ins: • History Module • Scenario Manager • Geo Selector
2.5 Installing and Uninstalling Macros Atoll can load and execute macros written in VBScript. To load a macro in Atoll: 1. In Atoll, select Tools > Add-ins and Macros. The Add-ins and Macros dialog box appears. 2. Click Add. The Open dialog box appears. 3. Navigate to the location where the macro you want to load is stored and select it.
30
Atoll 3.3.2 Administrator Manual Chapter 2: Atoll and Component Installation
AT332_AM_E0
4. Click Open. The New Script dialog box appears.
Figure 2.8: New Script dialog box for Macros 5. Specify the script settings: • •
Timeout: This is delay after which an unresponsive macro is stopped. To disable the macro timeout, set it to 0. If you leave the timeout empty, a value of 24 days is used. The default value is 60 seconds. UTF-8 Encoding: Select this option if the macro file contains non-ASCII characters (for example: "°" or "µ").
6. Click OK. The loaded macro appears under Macros in the Add-ins and Macros dialog box. To run a macro in Atoll: 1. In Atoll, select Tools > Add-ins and Macros. The Add-ins and Macros dialog box appears. 2. Under Macros, expand the folder containing the macro you want to run. 3. Select the macro you want to run. The Run button becomes active. 4. Click the Run button. Lists of macros available in Atoll can be stored in user configuration files. Macros listed in the user configuration files are added to Atoll when the user configuration files are loaded. For more information, refer to "Contents of User Configuration Files" on page 136. To remove a macro from Atoll: 1. In Atoll, select Tools > Add-ins and Macros. The Add-ins and Macros dialog box appears. 2. In the list of VBS files, select the one corresponding to the macro you want to remove. 3. Click Delete. Other commands available in the Add-ins and Macros dialog box are: • • •
Edit: Edit the selected macro in the default text editor. Icon: Assign an icon to the selected macro. Icons assigned to macros appear in the Macros toolbar. Refresh: To reload the selected macro file.
Available Macros and Scripts The following Atoll macros and scripts can be downloaded from the Forsk web site at http://www.forsk.com/support. For more information, contact to your Forsk representative. •
Macros: • Predictions Slideshow • Display Site Picture and Antenna Documentation • Show Hide Repeaters and Remote Antennas • Save Part of Document • GSM to UMTS • GSM to LTE • UMTS to LTE • CDMA2000 to LTE • Show in Google Maps Street View
•
Scripts: • Update Pathloss Matrices • Radio Data Import-Export • Propagation Models Import-Export • CW Measurements Import-Export • Test Mobile Data Import-Export
2.6 Atoll Command Line Parameters Atoll supports the following optional command line parameters:
31
Atoll 3.3.2 Administrator Manual Chapter 2: Atoll and Component Installation
© Forsk 2016
Atoll.exe [-log "logfilename"] [-Ini "inifilename"] [-Cfg "cfgfilename"] [-Provider providername -UserId username -Password password -DataSource server -Project projectaccount] •
-log "logfilename" Instructs Atoll to create a log file containing all the messages listed in the Events tab. This can be helpful for troubleshooting. "logfilename" is the full path and file name of the log file inside quotes.
•
-Ini "inifilename" Instructs Atoll to load the specified initialisation file when run. This can be used to override the default loading of the Atoll.ini file located in the Atoll installation folder. "inifilename" is the full path and file name of the initialisation file inside quotes.
•
-Cfg "cfgfilename" Instructs Atoll to load the specified user configuration file when run. This can be used to override the default loading of the Atoll.cfg file located in the Atoll installation folder. "cfgfilename" is the full path and file name of the user configuration file inside quotes.
•
-Stu "studiesfilename" Instructs Atoll to load the specified studies XML file when run. This can be used to override the default loading of the studies XML file located in "C:\Temp\studies.xml". "studiesfilename" is the full path and file name of the studies XML file inside quotes.
•
-Provider providername Instructs Atoll to use the mentioned providername to access the database server: Provider
Atoll version
providername
Microsoft Access
32-bit 64-bit
Microsoft.Jet.OLEDB.4.0 Microsoft.ACE.OLEDB.12.0
SQL Server
32/64-bit
SQLOLEDB
Oracle (Oracle driver)
32/64-bit
OraOLEDB.Oracle
•
-DataSource server Instructs Atoll to access the mentioned database server using the given provider.
•
-UserId username Instructs Atoll to access the mentioned Oracle database server using the mentioned username.
•
-Password password Instructs Atoll to access the mentioned Oracle database server using the mentioned password.
•
-Project projectaccount Instructs Atoll to access the mentioned Oracle database server using the mentioned projectaccount. •
The keywords Provider, Password, UserId, DataSource, and Project are case sensitive.
2.7 Troubleshooting and Other Information Read and follow carefully the instructions in "Installing Atoll Using the Setup Wizard" on page 25 for a smooth installation. If problems occur and you are unable to resolve them with the help of the following information, contact Forsk’s customer support. Microsoft Windows Updates •
•
32
It is recommended to install new Windows updates. However, it is also recommended to go through the description of each update patch to see whether it might have a negative effect on your system or network. Pay special attention to updates and patches related to networking. It is also recommended to keep the Windows updates uninstall folders, named "$NtUninstall...", under the Windows folder, in case you have to uninstall a certain patch. Some of the update patches might require uninstall folders of older patches to be available for their own installation.
Atoll 3.3.2 Administrator Manual Chapter 2: Atoll and Component Installation
AT332_AM_E0
Fixed license keys •
Fixed license keys cannot be used with "Server"-type operating systems. Therefore, you should not install the driver for fixed license keys on: • • • •
• •
• • •
•
Microsoft Windows Server 2003 Microsoft Windows Server 2008 Microsoft Windows Server 2008 R2 Microsoft Windows Server 2012
The current version of the driver for fixed license keys (Sentinel SuperPro driver) installed with Atoll is the 7.6.3. If Atoll is unable to access the fixed license key, even after a clean installation, try reinstalling the Sentinel SuperPro driver manually. The driver’s setup program (SPI763.exe) is copied by the setup to the Sentinel subfolder in the Atoll installation folder if you selected the Driver for Fixed Licence Keys component during the installation. You can also download the driver from http://www.safenet-inc.com. Restart the computer when asked by the setup. Restarting the computer is necessary for the driver for fixed license keys to work. If you get a protection key error message, verify that the fixed license key is correctly plugged in and that the license has not expired. In case the fixed or the floating license key becomes unavailable, Atoll will ask the users currently accessing the key to save their open documents before Atoll closes. If the key becomes available again, Atoll will let the users continue working. Do not change the computer’s date.
Citrix •
If you have installed Atoll on a Citrix XenApp server, you must publish it to make it available to the users.
Atoll version and build •
You can get information about Atoll (version, build, type of license and remaining time before expiration, etc.) by selecting Help > About Atoll in the main menu in Atoll.
Atoll file version and technology ATL file properties store the Atoll version and build number in which the file was last saved, and the technologies contained in the file. To access the ATL file properties: 1. Right-click the ATL file in the Windows Explorer. The context menu appears. 2. Select Properties from the context menu. The file properties dialog box appears. 3. In Windows XP, click the Summary tab and then the Advanced button. In Windows Vista, 7 and 8, click the Details tab. The Atoll version and build number in which the ATL file was last saved are stored in the Revision number property. The technologies of the document are listed in the Category property. Support website • • •
You can download the latest versions of Atoll from the Forsk’s support website by logging in with the user name and password provided to you by Forsk. The Atoll User Manual and other documents are available on the installation CD. More documents are available for download on the Forsk’s support website. The support website also offers you: • • • • • •
Sample add-ins, macros, and scripts Sample geographic data, List of fixed issues in the versions available for download, List of known issues, and possible workarounds, Schedule for upcoming versions, List of holidays.
For full contact details for customer support, see back cover. Acknowledgement •
Atoll uses Inno Setup for installation. For more information, see http://www.jrsoftware.org/isinfo.php.
Uninstalling Atoll and its components It is recommended to uninstall Atoll and its components through the Control Panel. To uninstall Atoll:
33
Atoll 3.3.2 Administrator Manual Chapter 2: Atoll and Component Installation
•
In Windows XP or Windows Server 2003: a. Go to Control Panel > Add or Remove Programs. b. In the Install/Uninstall tab, select Atoll from the list of installed programs. c. Click the Remove button.
•
In Windows Vista, Windows 7 and 8, or Windows Server 2008 and 2012: a. Go to Control Panel > Programs and Features. b. In the Uninstall or change a program window, right-click Atoll. The context menu appears. c. Select Uninstall.
34
© Forsk 2016
Chapter 3 Distributed Calculation Servers This chapter covers the following topics: •
"Setting Up Calculation Servers" on page 37
•
"Setting Up Atoll to Access the Calculation Servers" on page 39
•
"Distributed Calculation Process" on page 39
Atoll 3.3.2 Administrator Manual © Forsk 2016
36
Atoll 3.3.2 Administrator Manual Chapter 3: Distributed Calculation Servers
AT332_AM_E0
3 Distributed Calculation Servers Distributed calculation enables you to distribute the calculation of path loss matrices over many computers in a network. The distributed calculation service is an optional service that can be installed at the same time as Atoll. For more information on installation, see "Atoll and Component Installation" on page 25. A computer on which the distributed calculation service is installed and running is called a distributed calculation server. This computer, the distributed calculation server, is visible to all the other computers on the network through Atoll. You can set up as many distributed calculation servers as required. The distributed calculation service does not have a user interface, and hence has lower memory requirements than Atoll. The distributed calculation server uses the standard Atoll API to exchange data with the path loss calculator and Atoll. The distributed calculation service supports dual-processor configurations and up to four threads. Any version of Atoll can work with the distributed calculation service of the same or later version. Consequently, any version of the distributed calculation service can work with the same or previous versions of Atoll (versions still maintained by Forsk). For distributed calculation server options available through the Atoll.ini file, see "Distributed Calculation Server Options" on page 189.
3.1 Setting Up Calculation Servers When installed, the distributed calculation service starts automatically and remains available as long as the computer is turned on. The service does not require any active user session on the computer, i.e., the service keeps running even when there is no user logged on. The service’s executable (AtollSvr.exe) is installed in the Atoll installation folder. The Atoll distributed calculation service is listed as Atoll Server in the Services management console under Control Panel >Administrative Tools. During calculations, the distributed calculation servers require access to geographic data for calculating the path loss matrices. The distributed calculation service must be run with a user account that has sufficient privileges to access the required data. To modify the user account through which the distributed calculation service is run on a computer: 1. Log on to the computer with a user account with administrator rights. 2. Go to Control Panel > Administrative Tools > Services. 3. In the list of services, right-click the Atoll Server service. The context menu appears. 4. Select Properties. The Atoll Server Properties dialogue appears.
Figure 3.1: Atoll Server Properties 5. On the Log On tab, enter the user name and password for the user account through which you wish to run this service. 6. Click OK.
37
Atoll 3.3.2 Administrator Manual Chapter 3: Distributed Calculation Servers
© Forsk 2016
3.1.1 Stopping and Starting the Distributed Calculation Server To stop the distributed calculation service: 1. Log on to the computer with a user account with administrator rights. 2. Go to Control Panel > Administrative Tools > Services. 3. In the list of services, right-click the Atoll Server service, and select Stop or Start from the context menu.
3.1.2 Running More Than One Distributed Calculation Service By default, a single instance of the distributed calculation service is run. You can, however, run up to 9 additional distributed calculation services (a total of 10 including the first one) manually. Each instance of the service can calculate up to eight path loss matrices if the computer has eight processor cores available (one core per calculation). If the computer on which you are running the distributed calculation service has more than eight cores available, you can use these cores for calculations by running more than one instance of the distributed calculation service. Atoll can detect a total of 10 instances of the distributed calculation service. If you run more than 10 instances of the distributed calculation service, they will not be detected by Atoll. To run an additional instance of the distributed calculation service: 1. Run Command Prompt as administrator. 2. To create an instance of the service, type and run the following command: sc create AtollCalcSvr1 binPath= "C:\Program Files\Forsk\Atoll\AtollSvr.exe" start=auto DisplayName="Atoll DCS1" obj=\ password=
Where binPath should correspond to the location of the AtollSvr.exe file, DisplayName is the name of the service as it will appear in the Windows list of services. 3. To start the service created in step 2, type and run the following command: net start AtollCalcSvr1
4. Repeat steps 2 and 3 for each new instance of the service that you want to run by replacing "AtollCalcSvr1" and "Atoll DCS1" by "AtollCalcSvr2" and "Atoll DCS2", respectively, and so on. You can verify that the new service instances appear in the list of services through Control Panel > Administrative Tools > Services. You can also run additional instances of the distributed calculation service by double-click the AtollSvr.exe file located in the Atoll installation folder. For each new instance of the service, a command prompt window opens. To stop an additional, manually run service, close the corresponding command prompt window.
3.1.3 Uninstalling the Distributed Calculation Server To uninstall the distributed calculation service: 1. Log on to the computer with a user account with administrator rights. 2. Stop the distributed calculation service: a. Go to Control Panel > Administrative Tools > Services. b. In the list of services, right-click the Atoll Server service, and select Stop from the context menu. 3. Unregister the service: a. Select Start > Run. The Run dialogue appears. b. Type "\AtollSvr.exe /UnregServer". is the path to the Atoll installation folder. c. Click Run. This will remove the distributed calculation service from the computer.
38
Atoll 3.3.2 Administrator Manual Chapter 3: Distributed Calculation Servers
AT332_AM_E0
3.2 Setting Up Atoll to Access the Calculation Servers To activate distributed calculations in Atoll: 1. Select Tools > Distributed Calculations from the main menu. The Distributed Calculations dialogue appears. 2. Select the Activate distributed calculation check box. a. To use all the available distributed calculation servers, click All. b. To use selected distributed calculation servers only, click Detect. Atoll searches for the available distributed calculation servers on the network. The available distributed calculation servers are listed in the edit box. c. Remove the distributed calculation servers that you do not wish to include. 3. Click OK. The selected distributed calculation servers are now available for path loss calculations.
3.3 Distributed Calculation Process Once distributed calculations have been set up on the calculation server and on the user sides, the path loss calculations run by the user are distributed over the available calculation servers. The calculation process is as follows: 1. Atoll user runs path loss calculations. 2. Atoll sends the needed network data to the available calculation servers. 3. Either Atoll sends the needed geographic data to the calculation servers or the servers access the geographic data on a file server. 4. Distributed calculation servers calculate the path loss matrices one by one. Distributed calculation servers that have spare threads start the calculations using these threads. If no thread is available, the request is placed in a queue to wait for a thread to become available. 5. For each calculated path loss matrix, a confirmation is sent to the Atoll session. Any error or warning messages generated are passed back to the Atoll session and displayed in the Event Viewer. If an error occurs on any of the distributed calculation servers, Atoll transfers the calculations back to the local computer. However, to avoid memory saturation, Atoll uses one thread on the local computer and calculates the path loss matrices one by one. It does not attempt creating more than one thread. 6. In order to reduce the amount of data flow in the network, distributed calculation servers send the results directly to the storage location (which can also be on a file server, not necessarily on the user’s computer that requested the calculations). 7. Atoll user can then request the path loss matrices from the file server if they are needed for coverage predictions.
39
Atoll 3.3.2 Administrator Manual Chapter 3: Distributed Calculation Servers
40
© Forsk 2016
Chapter 4 License Management This chapter covers the following topics: •
"Working with Floating Licenses" on page 43
•
"Using the Atoll License Manager" on page 46
Atoll 3.3.2 Administrator Manual © Forsk 2016
42
Atoll 3.3.2 Administrator Manual Chapter 4: License Management
AT332_AM_E0
4 License Management Atoll can be used on: • •
Computers with fixed license keys plugged in to USB ports on the computers themselves. Computers connected to a license server with a floating license key plugged in to a physical USB port on the server or a network-attached USB hub.
The driver for fixed license keys can be installed at the same time as Atoll. For more information, see "Atoll and Component Installation" on page 25. The software for managing floating license keys must be installed on a server accessible to the computers on which Atoll is going to be used. For more information, see "Working with Floating Licenses" on page 43. For information on the Atoll license management utility, see "Using the Atoll License Manager" on page 46.
4.1 Working with Floating Licenses A floating license key can be used when users work with Atoll on computers on a network. In a floating license environment, license keys are not plugged in to each individual user’s computer, but a shared license key with multiple tokens is available to users through a server. A floating license server is a computer, accessible to other computers on a network, on which the floating license management software has been installed and a floating license key plugged in. The floating license server can be one of the computers on which Atoll is installed. The floating license management software and the floating license key control the number of potential Atoll users. A floating license system has a defined maximum number of tokens available. This is the maximum number of computers on which Atoll can be run simultaneously. Each computer that runs Atoll takes one token from the floating license key, even if more than one Atoll session is run on the same computer. The token is released and made available for other users when all the Atoll sessions on the computer are closed. If a computer is connected to a floating license server and also has a fixed license key plugged in, the fixed license key is accessed first.
4.1.1 Installing the Sentinel HASP Licensing System Atoll uses a 3rd-party floating license management system called Sentinel HASP from SafeNet. The floating license management system includes: • • • • • •
HASP floating license key: Hardware key programmed with the numbers of tokens available for each module. HASP license manager: Interface between Atoll and the floating license key. HASP device driver: Interface between the HASP license manager and floating license key. HASP monitor (optional): Enables you to check the number of used and available tokens. nhsrv.ini file: Installed on the floating license server to enable computers to use tokens. nethasp.ini file: Installed on the computers to facilitate access to the floating license server. nhsrv.ini and nethasp.ini files are used if they exist. Default settings are used otherwise.
The HASP device driver, the HASP license manager, and the floating license key must be installed on the server. Newer versions may be available than those provided on the Atoll installation disk, therefore it is recommended to download the latest HASP licensing products from the SafeNet web site. HASP hardware keys are supported by Windows 2000 Server and Windows Server 2003 with HASP License Manager 8.20 or above.
4.1.1.1 Installing the HASP Device Driver The HASP device driver enables communication between the hardware HASP floating license key and the License Manager software. The HASP device driver can be installed on a computer running Windows 2000 or later. A USB port must be available on the server for plugging in the floating license key. For virtual machines and computers that do not have a physical USB port, Atoll licensing supports network-attached USB hubs such as Digi AnywhereUSB.
43
Atoll 3.3.2 Administrator Manual Chapter 4: License Management
© Forsk 2016
Do not plug the floating license key into the server before installing the device driver. Wait for the HASP license manager setup to indicate when to plug in the key.
To install the HASP Device Driver: 1. Browse to the SafeNet download web site: http://sentinelcustomer.safenet-inc.com/sentineldownloads/ 2. Locate and download the following files: •
Sentinel HASP/LDK - Windows GUI Run-time Installer - version 6.64 or later.
3. Unzip the downloaded into a temporary directory. 4. Run the installer and follow the instructions provided. 5. Once the device driver is successfully installed, plug in the floating license key.
4.1.1.2 Installing the HASP License Manager The HASP license manager controls the allocation and retrieval of license tokens available on a floating license key. • •
•
•
If the floating license server is protected by a firewall, port 475 must be open for the UDP protocol. In case the fixed or the floating license key becomes unavailable, Atoll will ask the users currently accessing the key to save their open documents before Atoll closes. If the key becomes available again, Atoll will let the users continue working. The floating license key can become unavailable and a key protection error message appears in Atoll if the license management server is heavily loaded. Check if there is any application running on the server that might be causing the problem. If this is the case, remove any such application from memory. If this is not possible, try changing the latency associated to the HASP License Manager in accessing the key. You can optionally install the HASP Monitor on the floating license server, or on one or several other computers, to monitor the token allocation and retrieval activity. The HASP Monitor displays the list of computers using tokens available on the floating license key.
To install the HASP License Manager: 1. Browse to the SafeNet download web site: http://sentinelcustomer.safenet-inc.com/sentineldownloads/ 2. Locate and download the following files: •
HASP HL License Manager - version 8.32 or later.
3. Unzip the downloaded into a temporary directory. 4. Run the installer and follow the instructions provided. The installer is not compatible with Windows 8 or later. To install the HASP Device Driver on Windows 8 or later, right-click the installer, select Properties > Compatibility and run the program in Windows Vista (Service Pack 2) compatibility mode. 5. When prompted, choose "Service" as the type of installation. This means that the license manager will run as a service, and will be accessible even if there is no user logged on. You can choose to install it as an application, but in that case you will have to run the license manager manually every time you log on to the server and you will have to stay logged on for the license server to be available to the Atoll users. 6. Once installed, start the HASP license manager. If you selected "Service" as the type of installation, the license manager will start in service mode. An icon will be available in the task bar. You can access the network communication protocols by double-clicking this icon. When running, the HASP License Manager window displays a list of supported protocols which can be modified through the Load and Remove menus. Closing this window does not stop the license manager. The icon remains available in the taskbar as long as the service is running.
44
Atoll 3.3.2 Administrator Manual Chapter 4: License Management
AT332_AM_E0
Once the HASP license manager has been installed, the floating license key must always remain plugged in.
To stop the HASP license manager: 1. Go to Control Panel > Administrative Tools > Services. 2. In the list of services, right-click the HASP Loader service, and select Stop from the context menu. System administrators might want to restrict access to the HASP license manager installation folder. To do this, you can assign read/write access rights to this folder to administrators and read-only rights to end-users.
4.1.2 nhsrv.ini File The nhsrv.ini file can be used to define a list of computers allowed to request tokens from the floating license server. File Location If used, the nhsrv.ini file must be located in the installation directory (recommended) or a directory listed in the system path variable. File Contents The following is a sample nhsrv.ini file that shows how to set a list of computers allowed access to the floating license server. Complete syntax can be found on the HASP installation CD or on the Safenet website. [NHS_IP] NHS_USE_UDP NHS_USE_TCP NHS_IP_portnum
= enabled = enabled = 475
; enabled or disabled (default: enabled) ; enabled or disabled (default: enabled) ; IP port number (default: 475 (IANA registered)) ; CAUTION: clients must use the same port !
;NHS_IP_LIMIT = 10.24.2.18-99, 10.1.1.9/16, 10.25.0.0/24, ; 192.0.0.*, 194.0.*.*, 11.*.*.*, ; 10.24.7.8-12 /30, 10.24.2.17 ; specifies the range of stations that are allowed to access the LM ; the LAST byte may be a range (e.g., 10-120) ; the 4th, the 4th and 3rd, or the 4th and 3rd and 2nd byte may be an asterisk, ; acting as wildcard (e.g., 10.*.*.*, but NOT 10.*.20.1) ; an additional bitmask can be specified as number of one-bits (e.g., 10.0.0.0/8)
4.1.3 nethasp.ini File The nethasp.ini file enables Atoll to locate the floating license server quickly. Without the nethasp.ini file, finding the floating license server on the network can take a long time. File Location The nethasp.ini file must be located in the installation directory (recommended) or a directory listed in the system path variable. A nethasp.ini file located in the Atoll installation folder has priority over any nethasp.ini file located elsewhere. Storing the nethasp.ini file in the Windows folder instead of the Atoll installation folder can be useful if you have more than one version of Atoll installed, and you wish to access the same floating license server. This avoids making a copy of the file in each Atoll installation folder, but might not work on the latest versions of Windows. File Contents The following is a sample of the nethasp.ini file with the minimum required information. Complete syntax can be found on the HASP installation CD or on the Aladdin website. [NH_COMMON] NH_IPX = Disabled
;Use the IPX protocol - Enabled or Disabled
45
Atoll 3.3.2 Administrator Manual Chapter 4: License Management
© Forsk 2016
NH_NETBIOS = Disabled
;Use the NETBIOS protocol - Enabled or Disabled
NH_TCPIP = Enabled
;Use the TCP/IP protocol - Enabled or Disabled
[NH_TCPIP] NH_SERVER_ADDR = 3CT000J
;(a)IP address of the floating license server
NH_USE_BROADCAST = Disabled
;Use TCP/IP broadcast - Enabled or Disabled
a.
It is recommended to enter the server name within the domain. For example, for servername.domainname.com, enter servername only. Only one server name is supported in the nethasp.ini file. • •
Remove the NH_SESSION and NH_SEND_RCV entries from the nethasp.ini file if these exist. These fields define the timeout delays depending to the network. They can be useful in slow networks and should be set only if required.
4.2 Using the Atoll License Manager Atoll License Manager enables you to monitor, troubleshoot, and update license keys. You must not use the license manager without full instructions and details from Forsk support. Modifying parameters in the license manager without proper input from Forsk support can damage your fixed or floating licenses and block access of Atoll users to the licenses.
4.2.1 License Manager Interface To open the Atoll license manager: 1. Close Atoll. 2. Go to the Atoll installation folder. 3. Run Lic.exe. The License Management dialog box appears.
46
Atoll 3.3.2 Administrator Manual Chapter 4: License Management
AT332_AM_E0
Figure 4.1: Atoll License Manager 4. Under Available licenses, select a license key in order to display the information related to it. The Clear all button is reserved for Forsk use only.
Under Selected key the following information is available for the selected key: • • • • • • •
Number: Unique key number given by the key provider. This number must be communicated to Forsk, when requested, for reprogramming the license key. Type: The type of key, Fixed license or Floating license. Reference: Unique floating license key reference provided by Forsk. This number must be communicated to Forsk, when requested, for reprogramming the license key. This reference is also printed on the sticker on the key. Location (server): Name of the floating license management server on which the floating license key is plugged. Under Modules and licenses, all the Atoll modules available on the selected key are listed along with the numbers of license tokens of each. Under Number of licenses, the Modify buttons are reserved for Forsk use only. Under Dates and durations, the following dates and durations are available: • • • •
License start License end Duration of validity Time bomb
A purchased Atoll license corresponds to a particular Atollversion. There is no time limit on using this version. However, yearly maintenance must be purchased in order to access newer versions with updates and bug fixes. When you purchase maintenance, Forsk reprograms your license keys to allow access to new versions. The time bomb date is the end date for maintenance. When the time bomb date passes, the license key stops working. You can then choose to either purchase maintenance for the next year, and benefit from the new features and bug fixes, or have the license key reprogrammed without maintenance for the next year, in which case users can continue working with the existing version.
47
Atoll 3.3.2 Administrator Manual Chapter 4: License Management
© Forsk 2016
Atoll can inform you about the approaching time bomb date 30 days in advance. This alert can be configured through the Atoll.ini file. Do not attempt to modify the time bomb settings on the fixed license key. Contact Forsk support. Do not change the computer’s date. • •
Under Profile signature, the PID (profile signature or ID) is the encrypted description of the user rights available on the key. Each key has a unique PID. Under Current profile summary, all of the above information is summarised.
4.2.2 Updating License Keys Atoll License Manager enables administrators to update license keys by loading new key programming data from ALIC files provided by Forsk. To update a license key, you must have the ALIC file sent by Forsk. Do not attempt to reprogram a license key without full information and support from Forsk support.
To update a license key: 1. Close all Atoll sessions. Atoll reads license information from the key at the start of each session. This information is kept in memory as long as a session is running. If a license key is updated while a session is still running, the running session will not read the updated license information from the key and will expire according to the old license information. 2. Go to the Atoll installation folder. 3. Run Lic.exe. The license manager opens (see Figure 4.1 on page 47). 4. Under Available licenses, select the key to update. If the key does not appear in the available licenses list, check that it is plugged in to your computer. 5. Under Key programming, click Load. The Open dialogue appears. 6. Select the ALIC file provided by Forsk. 7. Click Save. The key is updated.
4.2.3 Generating a C2V File In some cases, Forsk support teams might ask you to provide a C2V file. This file can be generated by the Atoll License Manager. To generate a C2V file: 1. Close all Atoll sessions. 2. Go to the Atoll installation folder. 3. Run Lic.exe. The license manager opens (see Figure 4.1 on page 47). 4. Under Available licenses, select the key to update. If the key does not appear in the available licenses list, check that it is plugged in to your computer. 5. Under Key programming, click Create C2V. 6. Send the generated C2V file to Forsk support.
48
Chapter 5 Managing Databases This chapter covers the following topics: •
"Atoll Database Templates" on page 51
•
"Customising Atoll Database Structures" on page 52
•
"Atoll Management Console" on page 53
•
"Creating New Databases" on page 55
•
"Upgrading Existing Databases" on page 58
•
"Working With Multi-level Databases Using Oracle" on page 61
•
"Setting Database Access Privileges" on page 66
•
"Managing Data Modifications History" on page 67
•
"Appendices" on page 72
Atoll 3.3.2 Administrator Manual © Forsk 2016
50
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
AT332_AM_E0
5 Managing Databases In Atoll, you can work with standalone documents, i.e., documents without any back-end database, or with documents connected to databases. Standalone documents are more portable, however a back-end database is required when working in a multi-user environment. In multi-user environments, several users work on the same project and a central data storage is necessary for keeping the data modifications made by a team of radio planning and optimisation engineers. Atoll enables you to create databases, upgrade them to newer versions, archive and refresh data with databases, manage and resolve data conflicts, and create and work with multi-level databases. A database server can store one or more databases. For example, a GSM, a UMTS, and a microwave links database can be stored on the same database server using the same RDBMS (Oracle, for example). In this chapter, the following are explained: • • • • • • • •
"Atoll Database Templates" on page 51 "Customising Atoll Database Structures" on page 52 "Atoll Management Console" on page 53 "Creating New Databases" on page 55 "Upgrading Existing Databases" on page 58 "Working With Multi-level Databases Using Oracle" on page 61 "Setting Database Access Privileges" on page 66 "Managing Data Modifications History" on page 67
5.1 Atoll Database Templates All the technology modules available in Atoll (GSM, UMTS, LTE, CDMA2000, TD-SCDMA, WiMAX, Wi-Fi, and Microwave Radio Links) are based on database templates. These templates are used for creating Atoll documents with the appropriate data structure required for planning for any technology. Databases (using RDBMS) can then be created from any Atoll document. These databases are hence also based on the data structure defined by the Atoll database templates. In each new major release, database templates undergo modifications required to support new features. These modifications are applied to existing Atoll documents and databases by Atoll and the Atoll Management Console, respectively. It is also possible to upgrade an existing database manually, but due to the complex nature of the upgrade process, it is highly recommended to use the Atoll Management Console for upgrading existing databases. Each database template is an MS Access MDB file located in the templates folder in the Atoll installation folder. For the list of tables and fields, and their relationships, in each database template, see the Data Structure Reference Guide. Database template files must not be modified without consulting Forsk customer support.
The following table lists the types of fields used in Atoll database templates, their sizes, and the equivalent field types and sizes in different RDBMS: Atoll
Oracle Equivalent
Field Type
Length
Field Type
Length
Microsoft SQL Server Equivalent Field Type
Length
Microsoft Access Equivalent
Float
4
FLOAT
32
real
4
Single
Double
8
FLOAT
64
float
8
Double
Integer
4
NUMBER
11
int
4
Long Integer
Short
2
NUMBER
6
tinyint
1
Integer
Boolean
2
NUMBER
1
bit
1
Yes/No
Text
Variable
a
VARCHAR2
Variable1
varchar
Variable1
Text1
Memo
Variable
VARCHAR2
2000
varchar
4000
Memo
image
16
OLE Object
b
Binary
Variable
CLOB
> 2000
BLOBc
Variable
a.
Lengths for these fields are specified in parentheses in the database structure tables.
b.
Character large object
c.
Binary large object
51
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
© Forsk 2016
If you export the contents of an Atoll document, already connected to a database, to another RDBMS (for example, if you export a document connected to an Oracle database to SQL Server), some field types will be converted according to the above table. This conversion does not have any impact on the document in Atoll. For more information on the Atoll Management Console and upgrading databases, see "Atoll Management Console" on page 53 and "Upgrading Existing Databases" on page 58, respectively.
5.2 Customising Atoll Database Structures Atoll database structures can be customised by: • • •
Adding custom fields to data tables, Setting user-defined default values for fields, and Setting user-defined choice lists for text fields.
Custom fields, as well as user-defined default values and choice lists for standard and custom fields, are stored in the CustomFields table. Adding Custom Fields to Data Tables Do not add custom fields to data tables in the default document templates. It is recommended to add them in copies of the default templates so that the original database structure remains intact. If you add custom fields to a default template of your current Atoll version (N-1), and forget to add the same in the template of the next version (N), the Atoll Management Console of the next version (N) will consider that these fields were intentionally removed by the administrator. It will delete such custom fields from the database during upgrade.
Custom fields can be added to data tables at different stages keeping in mind that: •
•
•
Custom fields added directly to the Atoll database templates (MDB files), using Microsoft Access 2003, will be available in all new Atoll documents created from that template. A new database created by exporting such a document will also contain these custom fields. Custom fields added to an Atoll document through the Atoll user interface will not be automatically added to the corresponding Atoll database template. However, a new database created by exporting such a document will contain these custom fields. For more information on adding custom fields to Atoll documents through the user interface, see the User Manual. Custom fields added to an Atoll database will be available in all new Atoll documents created from that database.
To add a custom field to a data table: 1. Add the custom field to the definition of the data table by defining its name, type, and size. 2. Add a corresponding record in the CustomFields table and enter values for each of the following fields: Field
User Interface Caption
TABLE_NAME
52
Description Database name of the data table that contains the field
COLUMN_NAME
Name
Database name of the field
DEFAULT_VALUE
Default value
User-defined default value (optional)
CHOICE_LIST
Choice list
User-defined choice list for text fields (optional)
CAPTION
Legend
Caption of the field as it will appear in the user interface (optional but recommended)
GROUP_NAME
Group
Semicolon-separated list of the names of groups to which the field belongs (optional)
CHOICE_TYPE
Restricted
1: Custom field only accepts values listed in the choice list 0: Custom field accepts values other that those listed in the choice list
DISPLAY_TYPE
Read-only
1: Custom field is read-only in the user interface 0: Custom field is modifiable in the user interface
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
AT332_AM_E0
Custom fields are for information only and are not taken into account in calculations. You can find these fields on the Other Properties tab of an object’s Properties dialog box.
Setting User-defined Default Values for Fields You can set your own default values for standard as well as custom fields using the CustomFields table. User-defined default values entered in the CustomFields table have precedence over the predefined default values. To enter a user-defined default value for any field, add a new record in the CustomFields table and enter values for each of the following fields: Field
User Interface Caption
TABLE_NAME
Description Database name of the data table that contains the field
COLUMN_NAME
Name
Database name of the field
DEFAULT_VALUE
Default value
User-defined default value
For floating point default values, make sure that all the users use the same decimal symbol.
Setting User-defined Choice Lists for Text Fields You can set your own choice lists for standard as well as custom text fields using the CustomFields table. User-defined choice lists entered in the CustomFields table have precedence over the predefined choice lists. To enter a user-defined choice list for any text field, add a new record in the CustomFields table and enter values for each of the following fields: Field
User Interface Caption
TABLE_NAME
Description Database name of the data table that contains the text field
COLUMN_NAME
Name
Database name of the text field
CHOICE_LIST
Choice list
Choice list items, one per line
For example, you can replace the default choice list available for the SUPPORT_INFO field in the Sites table with a different list of options corresponding to the different types of towers and pylons that may exist in your network. • •
You can enter one of the choice list items in the DEFAULT_VALUE in order to set a default value for the text field. For custom text fields, you can set the CHOICE_TYPE to 1 if you want the custom text field to only accept values listed in the choice list. By default, CHOICE_TYPE is considered to be 0 meaning that users are allowed to enter values other than those defined in the choice list.
5.3 Atoll Management Console The Atoll Management Console provides the database administrator the possibility of globally managing the database with the easy-to-use step-by-step procedures which use wizard interfaces. The Atoll Management Console lets you: • • • • •
Create databases (see "Creating New Databases" on page 55) Upgrade database structures from one major version to the next (see "Upgrading Existing Databases" on page 58) Work with multi-level databases (see "Working With Multi-level Databases Using Oracle" on page 61) Manage data modifications history in databases (see "Managing Data Modifications History" on page 67) Manage user accounts and access rights (see "Managing User Accounts and Access Rights in Oracle" on page 81)
The Atoll Management Console supports: • •
Oracle Microsoft SQL Server
The Atoll Management Console can be installed with Atoll. For more information, see "Atoll and Component Installation" on page 25.
53
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
© Forsk 2016
You can run the Atoll Management Console from the Windows Start menu program group or by double-clicking the AMC.msc file in the management subfolder of the Atoll installation folder. The Atoll Management Console runs using the Microsoft Management Console environment. When the Atoll Management Console is run for the first time, you must register your database server in order to have the databases installed on the server to be available in the Atoll Management Console. To register a database server: 1. Open the the Atoll Management Console. 2. In the left pane, right-click Database under Administration Atoll. The context menu appears. 3. Select Register a New Server from the context menu. The Data Link Properties dialog box appears.
Figure 5.1: Data Link Properties dialog box - Provider Tab 4. On the Provider tab, select the provider for your database server and click Next. 5. On the Connection tab, enter the server name, user name, and password required to access the database server.
Figure 5.2: Data Link Properties dialog box - Connection Tab 6. Click Test Connection to verify that the information you entered is correct. An information message should appear to indicate that the "Test connection succeeded" . 7. Click OK. The selected database server is registered and available in the Atoll Management Console. You now have access to the features offered by the Atoll Management Console.
54
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
AT332_AM_E0
Figure 5.3: Atoll Management Console The tree in the left pane lists the registered database servers. Registered database servers can be connected ( disconnected ( ).
) or
The right pane lists the databases available on the connected database server currently selected in the left pane. The current user can be the owner of one of the listed databases; his name appears between parentheses in the title bar after the name of the database owner. One Oracle user can create and own one database. Therefore, for each new database, you must create a new Oracle user who will own the new database. The following details are available for databases created or upgraded using the Atoll Management Console: •
Name: name of the database preceded by an icon which indicates whether the database corresponds: • to the current version of Atoll ( ), or •
• •
to a previous version of Atoll not yet upgraded to the current version of Atoll (
)
Owner: name of the database owner. Version: most recent Atoll version to which the corresponding database was upgraded. Only the databases corresponding to the current and previous major releases of Atoll are listed. The version is indicated if the database has been upgraded via the AMC. • •
•
The databases corresponding to other major releases of Atoll are not listed. If the database server does not contain any database corresponding to the current/ previous major release of Atoll, no database is listed.
Type: database type (MASTER or PROJECT). A master database can have one or more project databases created from and connected to it. For more information on master and project databases, see "Working With Multi-level Databases Using Oracle" on page 61.
• •
Network: technology of the network modelled by the database (3GPP or 3GPP2 in case of multi-RAT). Shared Pathloss Directory: path to the shared path loss folder.
To view details of a database: 1. In the right pane, right-click the database in the list. The context menu appears. 2. Select Properties. The database Properties dialog box appears. 3. The Properties dialog box contains two tabs: • •
General: This tab displays the Name, Description, Owner, Type, and Version of the database. Statistics: This tab displays the number of records in each table of the database.
5.4 Creating New Databases New databases can be created using the Atoll Management Console or by directly exporting a document to a database from Atoll. In this section, the following are explained: • •
"Creating a New Database Using the Atoll Management Console" on page 55 "Creating a New Database Using Atoll" on page 57
5.4.1 Creating a New Database Using the Atoll Management Console You can create new databases using the Atoll Management Console.
55
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
© Forsk 2016
You must have administrator rights to the database and to the server for creating new databases.
To create a new database: 1. In the Atoll Management Console window, in the left pane, right-click the database server on which you want to create a new database. The context menu appears. 2. Select New > Database. The New Database Wizard dialog box appears.
Figure 5.4: New Database Wizard 3. Click Next. The Specify the database owner page appears. 4. Select Use the current connection if you want to create a new database using the current user, or select Create a new user and enter a Name and Password to create a new user that will be owner of the new database. If your password must contain special characters, for example, !, ?, etc., type the password inside double quotation marks: "mypassword!" instead of mypassword!
5. Click Next. The Name the database and specify a network type page appears. 6. Enter a Name for the new database and select the Network type. The Network type can be one of the database templates installed with Atoll.
56
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
AT332_AM_E0
Atoll and the Atoll Management Console must have the same version. This means that the Atoll Management Console can create databases based on the database templates installed with Atoll of the same version. 7. Click Next. The Specify units and coordinate systems page appears. 8. Select a Transmission power unit and a Reception threshold unit. 9. Under Coordinate systems, select a Cartographic projection system and the System to be used in the database. 10. Click Next. The Ready to create database page appears. This page provides a summary of the selected parameters. 11. Click Execute. The Atoll Management Console creates the new database with the defined parameters on the selected database server. A database created using the Atoll Management Console contains an ATOLL_ADMIN table with the following structure: Field
Type
Description
NAME
Text (50)
The name of the database
DESCRIPTION
Text (255)
Description of the database
ATOLL_VERSION
Text (10)
The current version of Atoll
ATOLL_BUILD
Integer
Current build of Atoll
ATOLL_DBTYPE
Text (10)
Type of Atoll database (i.e., Master or Project)
ATOLL_TEMPLATE
Text (50)
Atoll database template used to create the database
DBSCHEMA
Memo
An image of the schema of the original database
Among other uses, the ATOLL_ADMIN table is used to speed up the database upgrade to the next version. This table stores the data required by the Atoll Management Console for database upgrade. Databases created with Atoll, instead of the Atoll Management Console, and databases that have never been upgraded using the Atoll Management Console contain a smaller ATOLL_ADMIN table, with just the NAME, ATOLL_VERSION, and ATOLL_BUILD fields. Upgrading such databases using the Atoll Management Console can take a long time because the Atoll Management Console must search for the data required for the upgrade in the whole database. For more information on upgrading databases, see "Upgrading Existing Databases" on page 58. All the tables in a database created using the Atoll Management Console (except the COORDSYS and UNITS tables) contain a non-modifiable, integer DB_RECORD_ID field. This field is used to store the ID of every record in the table. It is not added to Microsoft Access databases.
5.4.2 Creating a New Database Using Atoll You can create new databases in all supported RDBMS using Atoll. To create a new database: 1. Run Atoll. 2. Create a new Atoll document or open an existing one. The new database will be created from this document. 3. Select Document > Database > Export. The Export to a Database dialog box appears. 4. In the Export to a Database dialog box, select the database type in the Save as type list. By setting an option in the Atoll.ini file, you can instruct Atoll to always use a defined database type (MS Access, SQL Server, or Oracle). In this case, the Export to a Database dialog box will be skipped and the database-specific authentication dialog box will appear immediately. For more information, see "Setting the Type of Database Being Used" on page 195. 5. Depending on the selected database type, enter the user name and password of the database owner. 6. Click Save. Atoll asks whether you want to connect the document to the new database. 7. Click Yes or No. Atoll creates a new database based on the document. A database created using Atoll contains an ATOLL_ADMIN table with the following structure:
57
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
© Forsk 2016
Field
Type
Description
NAME
Text (50)
The name of the database
ATOLL_VERSION
Text (10)
The current version of Atoll
ATOLL_BUILD
Integer
Current build of Atoll
• • •
Before creating the database, make sure that you have defined the coordinate systems and units in the source document. Before creating the database, make sure that you have added any required custom fields. Custom fields of the source document are created in the new database. If you want to add a custom field to the data structure after you have created the database, you will have to add it directly in the database and not through Atoll. Custom fields added to a database are available to users connected to the database when they create a new Atoll document from the database or refresh an existing one.
5.5 Upgrading Existing Databases In each new major release, data structure changes must be made in the database in order to support the new features added in the version. The data structures of standalone Atoll documents, i.e., documents not connected to any database are upgraded when they are opened in the new Atoll version. You can upgrade databases using the Atoll Management Console. •
•
Do not skip a major version of Atoll. For example, if you are currently using Atoll 2.8.x, you should first upgrade the database to Atoll 3.1.x before upgrading to Atoll 3.2.x. Upgrading your database will be simpler if you do not skip a major version. If you skip or have skipped an intermediate major version, you must upgrade your database twice in order to make it compatible with the new version. If you are upgrading a database which was neither created nor already upgraded (at least once) using the Atoll Management Console, see "Upgrading Databases for the First Time" on page 59 first.
The Microwave Radio Links template now supports Radio Series. Similar microwave radios belong to the same radio series. In order to organise the microwave radios (microwave equipment) in radio series before the database upgrade: 1. In Atoll 2.8.x, add a custom field named FAMILY of type Text (50) to the MWEquipments table. 2. Enter the radio series names in this field for each radio, i.e., group the radios of the same series under the same radio series name in the FAMILY field. Without this manual organisation of the microwave radios into radio series, the database upgrade will create one radio series for each microwave radio. To upgrade a database using the Atoll Management Console: 1. In the Atoll Management Console window, in the right pane, right-click the database that you want to upgrade. The context menu appears. 2. Select Upgrade Database. The Database Upgrade Wizard dialog box appears with the current database version and the version to which the database will be upgraded. 3. Click Next. The Name the database page appears. 4. Enter a Name and description for the database. 5. Click Next. The Database Upgrade Wizard reads the database to determine the Atoll database template using which it was created. If there is more than one template corresponding to the network, select the template to be used for the upgrade and click Next. The Atoll Management Console upgrades the database.
58
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
AT332_AM_E0
•
•
If some of the tables in a database have been replaced by views, the Database Upgrade Wizard asks to select the views to upgrade. Select the views that you want the Atoll Management Console to upgrade and click Execute. If, for example, the definition of a view is given by the condition: Select Field1, Field2 from Table1 where (Condition1); The wizard first upgrades the schema of Table1 and then upgrades the definition of the view. The upgraded definition will take the newly added fields into account. When you upgrade a 3GPP Multi-RAT database, the Atoll Management Console adds any missing tables to the database. For example, a database created by exporting a 3GPP Multi-RAT document containing only GSM contains only GSM tables. When upgraded, the Atoll Management Console will add the UMTS and LTE tables to the database as well.
Obsolete fields in the data structure are automatically deleted from the database by the Atoll Management Console during the upgrade. If you use the Atoll Management Console’s history management tool, you must repair the upgraded database in order to continue using this tool. For more information, see "Managing Data Modifications History" on page 67. Once the database has been upgraded to the new version, 1. Install the new Atoll versions for the end-users, and 2. Ask all the end-users to fully refresh data in their Atoll documents from the database. When users open their existing documents in the new Atoll version, they are asked whether they want to upgrade the documents’ data structures to the new version or to disconnect the documents from the database. On selecting the upgrade option, Atoll upgrades the document data structures to make them compatible with the new version. •
• •
• • •
The data structure of an Atoll document not connected to any database is automatically upgraded to the new Atoll version when the document is opened and saved in the new version. Once saved, it is not possible to open the document in an earlier Atoll version. The data structure of an Atoll document connected to a database not yet upgraded to the new version can be upgraded by: • Either opening the document in the new Atoll version, disconnecting it from the database, and saving it in the new version, or • Upgrading the database to the new version and then opening and saving the document in the new Atoll version. Once disconnected from its database, it is not possible to reconnect the document to any database. Obsolete fields in the data structure of a document not connected to any database are automatically deleted by Atoll when the document is saved in the new version. If the database has been upgraded to the new version but an Atoll document connected to the database has not yet been upgraded, it is possible to open the document in the previous Atoll version as read-only. It is also not possible to interact with the upgraded database (archive, refresh, etc., are not allowed). To make the document write-accessible in the previous Atoll version, it must be disconnected from the upgraded database.
It is possible to upgrade an existing database manually (not recommended) by adding and deleting tables and fields as required by the new version. For information on manually upgrading a database, see "Upgrading Databases Manually" on page 60.
5.5.1 Upgrading Databases for the First Time If you want to upgrade a database which was neither created nor already upgraded (at least once) using the Atoll Management Console, you must first upgrade the database to the same version as the current version of the database. This is required so that the Atoll Management console adds the required information to the database to make it upgradable to newer versions.
59
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
© Forsk 2016
To upgrade the database: 1. Before installing the new version of Atoll, install the Atoll Management Console (if not already installed) compatible with the existing version of Atoll. 2. Upgrade the database (as described in "Upgrading Existing Databases" on page 58) using the Atoll Management Console to the existing version of Atoll. The Atoll Management Console adds additional fields to the ATOLL_ADMIN table and DB_RECORD_ID fields in all the tables, as described in "Creating a New Database Using the Atoll Management Console" on page 55. Once the Atoll Management Console has performed the necessary modifications, you can upgrade the database to the new Atoll version. 3. Install the new version of Atoll and the Atoll Management Console. 4. Upgrade the database (as described in "Upgrading Existing Databases" on page 58), using the new version of the Atoll Management Console, to the new version of Atoll. When a new version of the Atoll Management Console is installed, the setup overwrites the Windows registry key that stores the information about the Admin.dll file, and the existing version of the Atoll Management Console can no longer be used. If you have already installed the new version of the Atoll Management Console, you will have to register the old Admin.dll again, upgrade the database to the existing version, register the new Admin.dll, and upgrade the database to the new version using the new Atoll Management Console. For the Atoll Management Console to be able to recognise obsolete or deleted fields from database tables, it is imperative that the ATOLL_ADMIN table exist in the database. This means that when upgrading a database for the first time using the Atoll Management Console, the database administrator will have to remove the obsolete fields manually. Once the Atoll Management Console has been used to upgrade a database, it will be able to recognise obsolete or deleted fields in the following upgrades.
5.5.2 Upgrading Databases Manually Due to the complex nature of the database upgrade process, it is highly recommended to use the Atoll Management Console for upgrading existing databases. You should only proceed with a manual upgrade of your database, as described below, if and only if an automatic upgrade using the Atoll Management Console is not possible. The following procedure is not recommended for customised Atoll databases and only suits very simple databases. Parameters and settings (triggers, views, user privileges, custom fields, etc.) defined in advanced database configurations are lost following the manual database upgrade. 1. In the previous version of Atoll, create a new document from the database. 2. In the new version of Atoll, open the document created in step 1. Atoll upgrades the document data structure to make it compatible with the new version. 3. Using the upgraded document, create a new database as explained in "Creating a New Database Using Atoll" on page 57. If you are upgrading your database using a script based on the data structure modifications listed in the Data Structure Reference Guide, you must: • •
60
Add the ATOLL_ADMIN table to the database. For more information on this table, see "Creating a New Database Using the Atoll Management Console" on page 55. For LTE databases, rename the smart antenna models and equipment as follows: • Delete existing smart antenna equipment ("Optimum Beamforming Smart Antenna") from the SmartAntennas table. • Delete existing smart antenna model ("Optimum Beamformer") from the SmartAntennasModels table. • Create a new smart antenna equipment ("Conventional Beamforming Smart Antenna") in the SmartAntennas table. Set the smart antenna model for this equipment to "Conventional Beamformer."
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
AT332_AM_E0
5.5.3 Adding a Technology in a Multi-RAT Database A multi-RAT document can be based on up to 3 technologies in 3GPP (GSM, UMTS, and LTE) and up to 2 technologies in 3GPP2 (CDMA2000 1xRTT and LTE). Provided such a document has already been exported to a database, you can add a technology to the corresponding database through the Atoll Management Console. 1. Start the Atoll Management Console. 2. When the Atoll Management Console opens, right-click on Database in the left pane. The context menu appears. 3. Select Register a New Server. The Data Link Properties dialog box is displayed. 4. On the Provider tab, select an OLE DB provider and click Next. 5. On the Connection tab, specify a database in the Select or enter a database name field. 6. Click the Test Connection button. If the connection is successful, click OK to close the Data Link Properties dialog box. 7. Upgrade the database if necessary, as explained in "Upgrading Existing Databases" on page 58. 8. In the right pane, right-click the database you want to upgrade with an additional technology and select Multi-RAT: View/Add Technologies. The Technologies in the Multi-RAT Database dialog box appears.
Figure 5.5: Technologies in 3GPP and 3GPP2 Databases 9. Select the technology you want to add and click OK. You cannot deselect a technology already present in a multi-RAT database.
A new record is added to the networks table for each technology added to the database.
5.6 Working With Multi-level Databases Using Oracle Atoll Management Console allows you to set up and work with multi-level databases using Oracle. In this optional database architecture, the master database is not directly accessible to end-users. Groups of end-users work with their respective project databases which are in turn connected to the master database. The end-users archive data to and refresh data from their respective project databases, and the database administrator manages the connections and data exchange between the project databases and the master database. For example, you can have a country-wide master database and more than one regional project databases. End-users can here work with their local region’s project database, and would not have to unnecessarily load country-wide data.
61
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
© Forsk 2016
Figure 5.6: Working With a Single Level Database Project databases are intermediate databases created from a common master database. A project database contains the original master database, that remains hidden from the end-users, and an copy of the master database accessible to the endusers. When a user modifies a record, only its accessible copy is modified in the project database. The original value in the master database remains unchanged until the database administrator archives all the modifications from the project databases to the master database.
Figure 5.7: Working With Project Databases Project databases can be used to improve performance and ensure data security and reliability. Instead allowing all the endusers to work directly with the master database, one or many project databases can be created with copies of the entire master database or a part of the master database corresponding to a given physical location or region. Creating and working with project databases restricts the number of users who have access to the master database. This reduces the risk of conflicts in the database as only the database administrator can archive modifications from project databases to the master database. For example, if a country-wide network database is accessible to all end-users: • • • •
The probability of human error increases with the number of users who can modify data. The probability of conflicts increases with the number of users accessing the database. The performance is reduced because the entire network is loaded every time a user accesses the database. For routine city-wide planning, an end-user does not require the entire country’s database to be loaded.
Project databases can be created using filters on sites, thus allowing users to work with regional databases. A possible scenario is depicted in the figure below:
62
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
AT332_AM_E0
Figure 5.8: Multiple Project Databases From a Single Master Database Multi-level databases can be set up using the Atoll Management Console. In this section, the following are explained: • • •
"Creating Project Databases" on page 63 "Archiving Project Databases to Master Databases" on page 65 "Refreshing Project Databases from Master Databases" on page 66
5.6.1 Creating Project Databases You can create project databases using the Atoll Management Console. For creating a project database, you must have enough rights to be able to create new tables in the master database schema.
To create a project database from an existing master database: 1. In the Atoll Management Console window, in the right pane, right-click the master database from which you want to create a project database. The context menu appears. 2. Select Create a Project Database. The Project Database Creation Wizard dialog box appears. 3. Click Next. The Specify the server and the owner of the project database page appears. 4. Select the Destination server for the project database. 5. Under Owner, select Current user if you want to create the new project database using the current user, or select Create a new user and enter a User name and Password to create a new user that will be owner of the new project database. Some versions of Oracle let you create a new user through this dialog box but the new user is not assigned DBA rights, which makes the new user unable to create the project database. Therefore, it is recommended to create the new user with DBA rights directly in the database before create the project database using the Atoll Management Console using the new user account. 6. Click Next. The Name the database page appears. 7. Enter a Name and Description for the new project database. 8. Click Next. The Specify the sites to include in the project database page appears. 9. On this page, choose from one of the following options: •
Include all the sites of the master database Select this option if you want to create a project database that contains all the data of the master database.
63
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
•
© Forsk 2016
Include a site list contained in the master database Select this option if you want to create a project database containing the network data corresponding to the sites included in a site list of the master database, and select a site list. This option is only available when at least one site list exists in the master database.
•
Select the sites to include using an SQL condition Select this option if you want to create a project database containing the network data corresponding to the sites that verify an SQL condition (for example, sites that have a common parameter or flag), and enter the SQL condition.
•
Include the sites contained within a polygon contained in a file Select this option if you want to create a project database containing the network data corresponding to the sites that are located inside a polygon, and select the file containing the polygon to use.
10. Click Next. The Atoll Management Console creates the new project database with the defined parameters on the selected database server. The project database will have the type PROJECT listed in the Atoll Management Console window.
Figure 5.9: New Project Database Wizard A project database created using the Atoll Management Console contains an ATOLL_ADMIN_PRJ table, in addition to the ATOLL_ADMIN table, with the following structure:
64
Field
Type
Description
NAME
Text (50)
The name of the project database
MASTER_CONNECTION
Text (255)
Connection parameters to the master database
MASTER_DBSCHEMA
Text (50)
The name of the original schema of the master database
SEL_METHOD
Short
Data extraction method used to select the sites to include in the project database
SEL_PARAM
Text (255)
Site selection method parameters (the SQL condition, if any)
SEL_PGON
Memo
Site selection polygon (if used)
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
AT332_AM_E0
You can view the details stored in the ATOLL_ADMIN_PRJ table in the project database properties. To view the above details of a project database: 1. In the right pane, right-click the project database in the list. The context menu appears. 2. Select Properties. The database Properties dialog box appears. 3. The Properties dialog box contains three tabs: • •
•
General tab: The General tab displays the Name, Description, Owner, Type, and Version of the database. Project Database tab: Under Source master database, the Project Database tab displays the Connection settings to and the Owner of the master database. Under Site selection, this tab displays the site filtering Method and Settings used for creating the project database. Statistics tab: The Statistics tab displays the number of records in each table of the project database.
The project database contains a copy of all the original tables of the master database. The names of the original tables are prefixed with "O_". For example, the ANTENNAS table of the master database is stored in the project database under the name O_ANTENNAS. The COORDSYS and UNITS are not copied to the project database because their contents cannot be different from those of the master database. All the tables in a project database contain a non-modifiable, integer O_RECORD_ID field and a Boolean O_CHANGED field. The O_RECORD_ID field is used to locate records in the master database. Modified records are archived in master database using the O_RECORD_ID of the project database and DB_RECORD_ID of the master database. The O_CHANGED field is set to TRUE for records modified in the project database.
5.6.2 Archiving Project Databases to Master Databases Changes made in the project databases can be archived to the master database using the Atoll Management Console. The Archive dialog box lets you select changes you want to archive. Before archiving the database, check that the structure of the O_ tables are consistent with the main tables in the project database. To archive the changes from a project database to its master database: 1. In the Atoll Management Console window, in the right pane, right-click the project database from which you want to archive changes to its master database. The context menu appears. 2. Select Archive. If pending changes exist, the Archive dialog box appears. The Archive dialog box lists the records of the project database for which the O_CHANGED field is TRUE. 3. In the Archive dialog box, you can do the following: • • • • • •
Select a site list in Filter by site list to filter the pending changes by a site list. Click Archive All to archive all the changes to the master database. Select the check boxes to the left of the changes that you want to archive and click Archive Sel. to archive only the selected changes. Click Undo All to overwrite all the changes in the project database with data from the master database. Select the check boxes to the left of the changes that you want to undo and click Undo Sel. to overwrite only the selected changes in the project database with data from the master database. Select the Check conflicts check box to see whether conflicts occurred during the archive. A conflict occurs when the project database contains a different original value of a field than the current value of the field in the master database. This can occur if the master database has been updated with changes from another source and the project database has not yet been refreshed with data from the master database.
65
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
© Forsk 2016
Figure 5.10: Archiving Changes in Master Databases Under Errors, Atoll Management Console displays errors that occurred during archive. 4. Once archive is complete, click Close.
5.6.3 Refreshing Project Databases from Master Databases Project databases can be refreshed with data from the master database using the Atoll Management Console. To refresh a project database with data from its master database: 1. In the Atoll Management Console window, in the right pane, right-click the project database that you want to refresh with data from its master database. The context menu appears. 2. Select Refresh. If pending changes exist, the Refresh a Project Database dialog box appears. 3. In the Refresh a Project Database dialog box, you can: •
•
Select Refresh unmodified data only to keep any changes in the project database and only update unmodified records from the master database. During the refresh, the Atoll Management Console will reload records from the master database for which the O_CHANGED field is FALSE in the project database. Select Cancel your changes and reload all data from the master database to overwrite modified and unmodified records in the project database with data from the master database.
1. Click OK. The project database is refreshed with data from the master database.
5.7 Setting Database Access Privileges You can assign different levels of privileges to different users for accessing (reading/writing) tables and views of a database. You can grant user privileges for Database, Table, Column, and Row levels keeping the following in mind: •
Database Level: Users trying to create a new Atoll document from a database are provided a list of available databases to select from. The list can be limited to a few databases based on the user connection properties (log in).
•
Table Level: For consistency reasons, all the tables available in an Atoll database must be readable by all the users who have access to the database. However, write access (INSERT, DELETE, UPDATE) can be granted on a limited number of tables.
•
Column Level: Similar to table level, all the columns of all the tables in an Atoll database must be readable and selectable by all the users who have access to the database. Different write permissions can be granted for columns of the tables. For example, custom fields can be assigned read and write permissions without restrictions.
•
Row Level: Row level permissions can be set by defining custom views on Atoll tables. Access to these views can be based on user connection properties (log in), on external table references, or on the geographic locations of sites (e.g., through polygons, or when using the spatial features of databases).
66
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
AT332_AM_E0
All of these permissions can be set as regular SELECT, INSERT, UPDATE, and DELETE privileges on database objects. Triggers can also be used to prevent users making certain actions on the database. Different permissions for different users can be granted directly or through database roles. Database roles enable you to define permission templates, which can then be assigned to existing or new users of the database. You can use the Atoll Management Console for defining user access rights to database tables and elements in the Atoll GUI. For more information on managing user access rights, see "Managing User Accounts and Access Rights in Oracle" on page 81.
5.8 Managing Data Modifications History The Atoll Management Console allows you to keep and manage the history of modifications made in the network data by different users. The history management tool keeps track of all the modifications made in the following Atoll tables: Technologies
Tracked Tables
GSM GPRS EDGE
Sites, Transmitters, TRGs, TRXs, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt
UMTS HSPA
Sites, Transmitters, CDMACells, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt
CDMA2000 1xRTT 1xEV-DO
Sites, Transmitters, CDMACells, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt
LTE
Sites, Transmitters, T4GCells, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt
WiMAX/Wi-Fi
Sites, Transmitters, WCells, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt
3GPP
sites, ltransmitters, utransmitters, gtransmitters, lcells, ucells, gtrgs, gtrxs, lrepeaters, urepeaters, grepeaters, lsecondaryantennas, usecondaryantennas, gsecondaryantennas, lneighbours, uneighbours, gneighbours, lneighext, uneighext, gneighext, guneighbours, ugneighbours, glneighbours, lgneighbours, ulneighbours, luneighbours
3GPP2
sites, ltransmitters, ctransmitters, lcells, ccells, lrepeaters, crepeaters, lsecondaryantennas, csecondaryantennas, lneighbours, cneighbours, lneighext, cneighext, lcneighbours, clneighbours
Microwave Radio Links/Backhaul
Sites, MWLinks, MWHubs, MWPmp, MWMultiHops, MWMultiHopsLinks, MWRepeaters, MWOTLinks, MWPorts, BHNodes, BHSegments, BHSegmentsMedia
You can, however, enable or disable history management for table as required (see "Enabling/Disabling Data Modifications History Management" on page 68 for more information). If you want, you can also purge old data modifications history (see "Purging Old Data Modification Records" on page 69 for more information). The history management tool is available for Oracle databases. The following section describes how to set up the history management tool using the Atoll Management Console.
5.8.1 Setting Up Data Modifications History Management When you set up history management for any database, the Atoll Management Console adds new tables to the database structure. For each tracked table, it adds a corresponding history table that has the same name as the tracked table with the suffix "_H". Each history table has the same structure as the corresponding tracked table, but with the following four additional fields. These fields enable the Atoll Management Console to store the modifications made by users to each tracked table: Field
Type
Description
HISTORY_ID
Integer
A unique ID of the modification history record
MODIFIED_BY
Text (50)
The user who made the modification
MODIFIED_DATE
Date
The date when the modification was made
HISTORY_STATUS
Text (10)
Status of the modification history record
The above fields are also added to all the tracked tables in order to store information about the latest modification. Therefore, opening any tracked table, you can see when a record was last modified, by whom, and the type of modification.
67
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
© Forsk 2016
To set up data modifications history management for a database: 1. In the Atoll Management Console window, in the right pane, right-click the database for which you want to set up data modifications history management. The context menu appears. 2. Select Manage Data Modifications History. The Data Modifications History Management dialog box appears. 3. Click Yes when asked whether you want to make your database compatible with the data modifications history tool. The Atoll Management Console updates the database structure to make it compatible with the data modifications history tool. Data modifications history is enabled for the database. Once finished, it opens the Data Modifications History Management dialog box (see Figure 5.11 on page 69). This dialog box lists all the tables for which the data modifications history management has been enabled, the total numbers of records in these tables, and the status of the history management. All the modifications made in the tables listed in "Managing Data Modifications History" on page 67 are stored in the history tables added to the database. If you want, you can disable the data modifications history management for any table. For more information, see "Enabling/ Disabling Data Modifications History Management" on page 68.
5.8.2 Enabling/Disabling Data Modifications History Management You can enable or disable data modifications history management for any table. You can enable or disable history management for each individual table. When history management is enabled for a table, the MODIFIED_BY, MODIFIED_DATE, and HISTORY_STATUS fields are updated with each modification, and a copy of each modification is stored in the history table corresponding to the table. When history management is disabled for a table, the MODIFIED_BY, MODIFIED_DATE, and HISTORY_STATUS fields are still updated with each modification, but the history of modifications is not stored in the corresponding history table. To enable data modifications history management for a table: 1. In the Atoll Management Console window, in the right pane, right-click the database for which you want to enable data modifications history management. The context menu appears. 2. Select Manage Data Modifications History. The Data Modifications History Management dialog box appears. 3. In the Data Modifications History Management dialog box, right-click the table for which you want to enable data modifications history management. The context menu appears. 4. Select Enable in the context menu. Data modifications history management is now enabled for this table. The Status in the Data Modifications History Management dialog box is set to OK for this table. To disable data modifications history management for a table: 1. In the Atoll Management Console window, in the right pane, right-click the database for which you want to disable data modifications history management. The context menu appears. 2. Select Manage Data Modifications History. The Data Modifications History Management dialog box appears. 3. In the Data Modifications History Management dialog box, right-click the table for which you want to enable data modifications history management. The context menu appears. 4. Select Disable in the context menu. History management is now disabled for this table. The Status in the Data Modifications History Management dialog box is set to Deactivated for this table.
5.8.3 Updating Data Modifications History after a Data Structure Upgrade When you modify the structure of a tracked database table (for which data modifications history management is enabled), either automatically upgrading your database using the Atoll Management Console, or manually by adding or removing fields, or by modifying a field type, the corresponding data modifications history management table becomes invalid and has to be updated to match the new structure of the tracked table. The Status column of the Data Modifications History Management dialog box shows an error for the tracked table whose history management table does not match its structure.
68
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
AT332_AM_E0
To update the data modifications history management tables: 1. In the Atoll Management Console window, in the right pane, right-click the database whose tables you want to update. The context menu appears. 2. Select Manage Data Modifications History. The Data Modifications History Management dialog box appears. 3. In the Data Modifications History Management dialog box, right-click the table that you want to update. The context menu appears. 4. Select Install/Repair in the context menu. The Atoll Management Console repairs the data structure of the history management table to match the structure of the corresponding tracked table.
5.8.4 Purging Old Data Modification Records History management tables store the lists of all the modifications made by all the users. These tables can therefore quickly become very large and require a lot of disk space. You can purge old data modifications history (records) from these tables in order to gain disk space. In this section, the following is explained: • •
"Purging Old Data Modification Records of a Table" on page 69. "Purging Old Data Modification Records of a Database" on page 70.
5.8.4.1 Purging Old Data Modification Records of a Table To purge old data modification records from a history management table: 1. In the Atoll Management Console window, in the right pane, right-click the database in which you want to purge old data modifications history. The context menu appears. 2. In the context menu, select Manage Data Modifications History. The Data Modifications History Management dialog box appears (see Figure 5.11 on page 69).
Figure 5.11: Data Modifications History Management dialog box 3. In the Data Modifications History Management dialog box, right-click the table for which you want to purge old data modifications history. The context menu appears. 4. In the context menu, select Purge. The table record purge dialog box appears (see Figure 5.12 on page 70).
69
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
© Forsk 2016
Figure 5.12: Table Record Purge dialog box 5. Under Purge data modifications recorded before, move the slider to select from which date onwards you want to keep the data modification history records. All the data modification history records before this date will be deleted. The fields under Record Information indicate the number of Records that will be left after the purge and the corresponding Size. 6. Under Options, select the Keep creation and deletion records check box if you want to keep the records related to creation and deletion. 7. Click Purge. All the history records before the selected date are deleted from the history management table. If you selected the Keep creation and deletion records check box, creation and deletion records before the selected date are not deleted.
5.8.4.2 Purging Old Data Modification Records of a Database To purge old data modification records from all the history management tables of a database: 1. In the Atoll Management Console window, in the right pane, right-click the database in which you want to purge old data modifications history. The context menu appears. 2. In the context menu, select Manage Data Modifications History. The Data Modifications History Management dialog box appears (see Figure 5.11 on page 69). 3. In the Data Modifications History Management dialog box, click the Scheduler button. The database record purge dialog box appears (see Figure 5.13 on page 70).
Figure 5.13: Database Record Purge dialog box
70
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
AT332_AM_E0
4. Under Conditions, select the records to purge: • • • •
None: select this option if you do not want data modification records to be purged. Keep only the last N records: if you select this option, enter the number of most recent records you want to keep. All older records will be purged. Keep only records of N last months: if you select this option, enter the number of months prior to which all records will be purged. Keep creation and deletion records: select this check box if you want to want to keep all the creation and deletion records, independent of the above options.
5. If you wish to purge records now, click the Run now button. 6. If you wish to schedule regular purges, under Scheduling, define the purge frequency: a. Period: Select the frequency of the scheduled regular purges. b. Day: Select the day of the week (Monday to Sunday), month (1 to 28), or year (1 to 365), depending on the purge periodicity defined in Period, on which the scheduled purges will run. c. Time: Enter the time, i.e., the hour (0 to 23) and minutes (0 to 59) at which scheduled purges will run. Scheduled regular purges will delete all the data modification records according to the criteria defined under Conditions. 7. Set the Off/On slider to On to activate the scheduled purges. Setting the Off/On slider to Off allows you to suspend scheduled purges while keeping the scheduler settings. 8. Click the Update button to store the schedule parameters. The current purge status is shown under Status. Status information includes: • • •
Last execution: Time of execution of the last purge. Result: Whether the last purge was successful or not. Next execution: Time of execution of the next scheduled purge.
You can click the View logs under Status to view the history of past purges (see Figure 5.13 on page 70). 9. Click the Close button. Scheduled regular purges are programmed as a scheduled job in Oracle using the DBMS_SCHEDULER.create_job function. The following SQL string generates scheduled job: "BEGIN DBMS_SCHEDULER.create_job (" "job_name => 'AHMS_%s'," "job_type => '%s'," "job_action => '%s'," "start_date => SYSTIMESTAMP," "repeat_interval => '%s'," "end_date => NULL," "enabled => %s," "comments => '%s'); END;" Here: Parameter
Description
job_name
AHMS_
job_type
PLSQL_BLOCK
job_action
Actual PL-SQL code for the purge
start_date
SYSTIMESTAMP
repeat_interval
Frequency of the scheduled purge For example, once a month, on the 15th, at 1:30am: "freq=month;monthday=15;byhour=1;byminute=30"
end_date
NULL
enabled
TRUE or FALSE, based on the user input
comments
Custom character string with codes for easy identification of the scheduler type
71
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
© Forsk 2016
5.9 Appendices The first appendix shows how to use SQL for Oracle database customisation and the second appendix shows how to set up databases for co-planning taking the example of GSM and UMTS MS Access databases.
5.9.1 Appendix 1: Advanced Customisation You can use SQL in order to manage access to and share the Sites table (example 1), or to restrict the connection to a set of transmitters for some users (example 2). To implement the following two examples, you must log on as the owner of the tables through SQL Plus 8. Example 1: Managing Site Sharing Assumptions: • • • •
Connection string = AtollDB GSM Project account = AtollADMINGSM, password = ADMINGSM UMTS Project account = AtollADMINUMTS, password = ADMINUMTS Common Project account = AtollADMIN, password = ADMIN
To share the Sites table: 1. Create the AtollADMIN.SITES table and copy all sites from AtollADMINGSM.SITES to AtollADMIN.SITES. SQL > connect AtollADMIN/ADMIN@AtollDB; SQL > create table AtollADMIN.SITES as select * from AtollADMINGSM.SITES; SQL > create unique index AtollADMIN_SITES on AtollADMIN.SITES(NAME); 2. Replace the AtollADMINGSM.SITES table by an AtollADMINGSM.SITES view. SQL > connect AtollADMINGSM/ADMINGSM@AtollDB; SQL > drop table AtollADMINGSM.SITES; SQL > connect AtollADMIN/ADMIN@AtollDB; SQL > grant delete on AtollADMIN.SITES to AtollADMINGSM with grant option; SQL > grant insert on AtollADMIN.SITES to AtollADMINGSM with grant option; SQL > grant select on AtollADMIN.SITES to AtollADMINGSM with grant option; SQL > grant update on AtollADMIN.SITES to AtollADMINGSM with grant option; SQL > create view AtollADMINGSM.SITES as select * from AtollADMIN.SITES; 3. Follow the same procedure for UMTS (AtollADMIN.SITES already created). SQL > connect AtollADMINUMTS/ADMINUMTS@AtollDB; SQL > drop table AtollADMINUMTS.SITES; SQL > connect AtollADMIN/ADMIN@AtollDB; SQL > grant delete on AtollADMIN.SITES to AtollADMINUMTS with grant option; SQL > grant insert on AtollADMIN.SITES to AtollADMINUMTS with grant option; SQL > grant select on AtollADMIN.SITES to AtollADMINUMTS with grant option; SQL > grant update on AtollADMIN.SITES to AtollADMINUMTS with grant option; SQL > create view AtollADMINUMTS.SITES as select * from AtollADMIN.SITES; 4. Commit. SQL > commit; Example 2: Managing Users by Postal Code To restrict access to transmitters for some users by postal code: 1. Add a ‘POSTCODE’ field to the SITES table. SQL > alter table SITES add (POSTCODE number); 2. Rename the SITES table to be able to hide it by a view.
72
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
AT332_AM_E0
SQL > rename SITES to PRIVATE_SITES; 3. Create a POSTCODETABLE table to link users and postcodes (one user can be linked to several postcodes). SQL > create table POSTCODETABLE (USERNAME varchar2(30), POSTCODE number); You can fill this table using this instruction. SQL > insert into POSTCODETABLE values (‘USER1’, 75); 4. Create a view owned by this user hiding the actual SITES table through these commands. SQL > create view SITES as select * from PRIVATE_SITES where POSTCODE in (select POSTCODE from POSTCODETABLE where USERNAME =USER) with check option; "with check option" is very important as it specifies that insert and update operations performed through the view must result in rows that the view query can select. 5. Hide the TRANSMITTERS table, so that Atoll can only select transmitters whose associated sites are present in the SITES view. SQL > rename TRANSMITTERS to PRIVATE_TRANSMITTERS; SQL > create view TRANSMITTERS as select * from PRIVATE_TRANSMITTERS where SITE_NAME in (select NAME from SITES); 6. Commit. SQL > commit;
The error message "ORA-01402: view WITH CHECK OPTION - clause violation" appears if you try to archive a record that does not match the project.
5.9.2 Appendix 2: Setting Up Databases for Co-planning Two co-planning approaches are possible in Atoll: •
Co-planning GSM, UMTS, and LTE using a unified multi-technology data structure, i.e., working with a 3GPP Multi-RAT document.
•
Co-planning any two radio technologies (GSM, UMTS, LTE, CDMA2000, TD-SCDMA, and WiMAX), with two separate data structures, by linking Atoll documents.
In terms of database, while the first approach provides an integrated multi-technology co-planning environment, the second requires setting up sharing of the Sites table between the databases of the two technologies being co-planned. The Sites table must be shared between the databases of the two technologies being co-planned so that the sites where sectors of both technologies are installed are listed only once in a common Sites table. In other words, the Sites tables in the databases of the two technologies must be views of a common Sites table. This section describes table sharing between GSM and UMTS, although the same description can be applied to any two radio technology modules of Atoll You can create views to share tables that have the same structure in the databases of the two technologies being co-planned, i.e., the Sites and Antennas tables. In the following, we assume that the Sites tables of the GSM and UMTS documents contain the same data and that two users, named GSMUser and UMTSUser in this example, exist in the databases. To set up a shared Sites table for a GSM-UMTS co-planning project in Oracle or SQL Server: 1. Make backups of the GSM and UMTS documents. 2. Open the GSM document in Atoll. 3. Delete all the transmitters from the Transmitters table and all the sites from the Sites table.
73
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
© Forsk 2016
4. Export the GSM document to the database by entering the user name and password for GSMUser. 5. Log in as GSMUser to the database. 6. Delete the Sites table. 7. Open the UMTS document in Atoll. 8. Export the UMTS document to the database by entering the user name and password for UMTSUser. 9. Log in as UMTSUser to the database. 10. Right-click the Sites table and select Create a View from the context menu. The Create View dialog box appears. a. Enter Sites as the view name. b. Enter GSMUser as the name of the schema which will contain the view. c. Select Table as object type. d. Enter UMTSUser as the name of the schema you want to use. e. Select Sites as the object used to model the view. 11. Click Create. The view of the Sites table from UMTSUser is created in GSMUser. The GSMUser Sites table is now the same as UMTSUser Sites table. 12. Set up user privileges for the Sites view in GSMUser to allow each user to Import, Update, Delete, and Select. To set up a shared Sites table for a GSM-UMTS co-planning project in Microsoft Access: 1. Make backups of the GSM and UMTS documents. 2. Open the GSM document in Atoll. 3. Delete all the transmitters from the Transmitters table and all the sites from the Sites table. 4. Export the GSM document to a Microsoft Access database (GSM.mdb). 5. Open GSM.mdb in Microsoft Access. 6. Delete the Sites table. 7. Open the UMTS document in Atoll 8. Export the UMTS document to a Microsoft Access database (UMTS.mdb). 9. Open GSM.mdb in Microsoft Access. 10. In Microsoft Access 2003 and earlier, select File > Get External Data > Link Tables. In Microsoft Access 2007 and later, select External Data > Access Database. 11. In Microsoft Access 2003 and earlier, the Link dialog box appears. Select UMTS.mdb. In Microsoft Access 2007 and later, the Get External Data - Access Database dialog box appears, specify UMTS.mdb as data source and select Link to data source by creating a linked table. 12. Click OK. The Link Tables dialog box appears. 13. Select the Sites table. 14. Click OK. Microsoft Access creates a Sites table in GSM.mdb which is linked to the Sites table in UMTS.mdb. The tables contain the same data. Once the linked Sites table has been created in the GSM database, you have to define the relations of this table with the other tables in the database. See the Data Structure Reference Guide for detailed information on database tables. • •
The UMTS Sites table has more fields than the GSM Sites table. Therefore, you should replace the GSM Sites table with the UMTS one. When you upgrade one by one the databases that share the Sites table, any triggers that you might have set on the Sites table of the database that is upgraded first might be overwritten by the triggers set on the Sites table of the database upgraded last. In order to avoid the triggers being overwritten, you can rename the triggers on the Sites table of the database upgraded first (by adding, for example, the database technology as prefix to the trigger names) before upgrading the other database(s).
Ensuring Database Consistency Between Linked Documents When users work with two Atoll documents and databases at the same time, it is important to have a protection mechanism against database inconsistencies. If a user archives the changes made in one document but forgets to archive the changes made in the other, this can create inconsistencies between the two networks.
74
AT332_AM_E0
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
To ensure database consistency, you can save or archive the linked documents at the same time, i.e., when a user saves or archives one document, Atoll automatically saves or archives the other. This can be done using a macro triggered by the save or archive operation.
75
Atoll 3.3.2 Administrator Manual Chapter 5: Managing Databases
76
© Forsk 2016
Chapter 6 Multi-user Environments This chapter covers the following topics: •
"Setting Up Multi-user Environments" on page 79
•
"Components of Multi-user Environments" on page 79
•
"Managing User Accounts and Access Rights in Oracle" on page 81
•
"Appendices" on page 87
Atoll 3.3.2 Administrator Manual © Forsk 2016
78
Atoll 3.3.2 Administrator Manual Chapter 6: Multi-user Environments
AT332_AM_E0
6 Multi-user Environments A multi-user environment is where more than one user work simultaneously on an Atoll project, sharing data over a network. In large, structured multi-user environments, groups of users can work on specific parts of a common, large-scale project. For example, different user groups can work on different regions of a country-wide network. In this chapter, the following are explained: • • •
"Setting Up Multi-user Environments" on page 79 "Components of Multi-user Environments" on page 79 "Managing User Accounts and Access Rights in Oracle" on page 81
6.1 Setting Up Multi-user Environments The general process of setting up a multi-user environment is described below. Each component is described in detail in "Components of Multi-user Environments" on page 79. 1. Create the master Atoll document with the required network data and geographic data. For more information, see "Master Atoll Document" on page 80 and "Shared Geographic Data" on page 80. 2. Export the master Atoll document to a new database and keep the document connected to the new database. For more information, see "Master Database" on page 80. 3. Create the private path loss matrices folder for the master Atoll document and calculate the private path loss matrices. For more information, see "Shared Path Loss Matrices" on page 81. 4. Create user Atoll documents from the master database. For more information, see "User Atoll Documents" on page 81. 5. In the user Atoll documents, add the required geographic data and set the master Atoll document’s private path loss matrices folder as the shared path loss matrices folder of the user documents. • •
The Atoll administrator should regularly update the shared path loss matrices. As the users work on the network and archive changes in the database, the Atoll administrator should regularly run data integrity checks on the master Atoll document after loading modified data from the master database. For more information, see "Appendix 1: Checking Data Integrity" on page 87.
6.2 Components of Multi-user Environments Figure 6.1 on page 79 shows the components of a multi-user environment.
Figure 6.1: Components of Multi-user Environments
79
Atoll 3.3.2 Administrator Manual Chapter 6: Multi-user Environments
© Forsk 2016
In this section, the following are explained: • • • • • •
"Master Atoll Document" on page 80 "Master Database" on page 80 "Shared Geographic Data" on page 80 "Shared Path Loss Matrices" on page 81 "Shared Microwave Link Profiles" on page 81 "User Atoll Documents" on page 81
6.2.1 Master Atoll Document It is the source Atoll document that contains the entire project’s network data. It is created and maintained by the Atoll administrator. This document is initially used to create the radio network database with which all the end-users work. The master Atoll document allows the administrator to globally manage all the data shared by the end-users. The master Atoll document is also used for calculating path loss matrices for the transmitters of the entire network and keeping the path loss matrices up to date with the user modifications to the radio network data. The document also contains the required geographic data for path loss calculations. Geographic data are usually located on file servers and linked to the document, not embedded in the ATL file. The private path loss matrices of this document are used as shared path loss matrices by the end-users. The shared path loss matrices folder is usually located on a file server accessible to all the users on the network. For exceptionally large networks, you can also work with more than one master Atoll document (for example, one master document per region). However, the multi-user environment set up remains the same. Master Atoll documents should not have redundant radio network data (same sites, for example), and should ideally cover different geographical regions. For more information on regionalisation, see "Appendix 2: Database Regionalisation" on page 87. If you wish to add custom fields in the Atoll document, you should first add the field in the database, and then update your Atoll document from the database. Custom fields added in an Atoll document connected to a Microsoft Access database are automatically added to the database. However, this is not the case with other RDBMS, such as Oracle.
6.2.2 Master Database The master database stores the radio network data shared by all the end-users. It can be created by exporting the radio network data in the master Atoll document to a database from Atoll (for more information, see "Creating a New Database Using Atoll" on page 57). An empty database can also be created using the Atoll Management Console, and populated with data later on (for more information, see "Creating a New Database Using the Atoll Management Console" on page 55). Only radio network data are stored in the database, i.e., sites, transmitters, antennas, etc. Parameters related to geographic data files, their paths, folder configurations, prediction definitions, zones, traffic maps, measurements can be stored in user configuration files (see "Configuration Files" on page 135 for details). For large networks, you can subdivide the network’s master database into regions. For more information on regionalisation, see "Appendix 2: Database Regionalisation" on page 87. For more information on database management, see "Managing Databases" on page 51. The recommended database server configuration is provided in "Recommended Hardware and Software" on page 18. The same database server can be used to store one or more master databases corresponding to different technologies. For example, a GSM database and a UMTS database can be stored on the same database server using the same RDBMS (Oracle, for example).
6.2.3 Shared Geographic Data Geographic data files are usually stored on a file server accessible to and shared by all the users working on the same network. User configuration files (CFG or GEO) are used to store the parameters related to geographic data. For more information, see "Configuration Files" on page 135. The administrator can set up different user configuration files (CFG) for separate user groups. User configuration files can be created so that only the geographic data required by a user are loaded. It is possible to load a user configuration file automatically when running Atoll. User configuration files can be shared and exchanged between users working on the same project. For more information, see "Atoll Command Line Parameters" on page 31. Geographic data files are usually large files, and it is recommended that these be stored externally and not embedded in Atoll documents. The recommended file server configuration is provided in "Recommended Hardware and Software" on page 18.
80
Atoll 3.3.2 Administrator Manual Chapter 6: Multi-user Environments
AT332_AM_E0
If users modify geographic data locally, for example edit clutter or traffic in their respective projects, they should store these modified geographic data locally so that the modifications do not impact other users.
6.2.4 Shared Path Loss Matrices Shared path loss matrices are usually stored on a file server accessible to and shared by all the users working on the same project. These path losses are calculated using the master Atoll document by the Atoll administrator. The private path loss matrices of the master Atoll document are used as shared path loss matrices by the end-users. The Atoll administrator is the owner of the shared path loss matrices, and must have read/write access to the shared path loss matrices folder. End-users should have read-only access to this folder. It is the administrator’s duty to regularly update the master Atoll document with the modifications made to the master database by the end-users, and to calculate the shared path loss matrices using the master Atoll document on a routine basis. This task can be carried out using a macro. For more information, see "Appendix 3: Calculating Path Loss Matrices" on page 88. Shared path loss matrices are available for use in calculations to all the end-users. However, end-users are not allowed to modify the shared path loss matrices. The shared path loss matrices must be unlocked in order for users to be able to work with them. You can check whether path loss matrices are unlocked in the Propagation tab of the Transmitters folder’s properties dialog box.
6.2.5 Shared Microwave Link Profiles Shared microwave link profiles are usually stored on a file server accessible to and shared by all the users working on the same project. These profiles are calculated using the master Atoll document by the Atoll administrator. The private profile data of the master Atoll document is used as shared profile data by the end-users. The Atoll administrator is the owner of the shared profiles, and must have read/write access to the shared profiles folder. Endusers should have read-only access to this folder. It is the administrator’s duty to regularly update the master Atoll document with the modifications made to the master database by the end-users, and to calculate the shared profile extraction using the master Atoll document on a routine basis. This task can be carried out using a macro.
6.2.6 User Atoll Documents User Atoll documents are created from the master database. These can contain the entire project network data or only a part of it. User documents are the working documents of the Atoll end-users connected to the master database, the geographic data, and the shared path loss matrices folder. You should load data from the master database in each user Atoll document and save it before setting the shared path loss matrices folder for the document. For any modifications made by end-users in their Atoll documents that render some shared path losses invalid, Atoll calculates the invalid path loss matrices locally for the end-users and stores them in their private path loss matrices location. Shared path loss matrices are only used in calculations if valid private path loss matrices are not available. Therefore, in order to use shared path loss matrices, you must delete the corresponding private path loss matrices. If users are going to work on regions of a network, the regionalisation should be set up before creating the user documents. For more information on regionalisation, see "Appendix 2: Database Regionalisation" on page 87. If you wish to add custom fields in the Atoll document, you should first add the field in the database, and then update your Atoll document from the database. Custom fields added in an Atoll document connected to a Microsoft Access database are automatically added to the database. However, this is not the case with other RDBMS, such as Oracle.
6.3 Managing User Accounts and Access Rights in Oracle The Atoll Management Console enables you to create and delete database user accounts, edit user account information, and define user access rights to different components of a project such as database tables, and radio data and parameters in Atoll. In order to be able to manage user accounts and access rights using the Atoll Management Console, you first have to make the database compatible with the user management tool. This is done automatically when the user management tool is run
81
Atoll 3.3.2 Administrator Manual Chapter 6: Multi-user Environments
© Forsk 2016
on a database for the first time. The database has to be of the same version as the Atoll Management Console being used to manage user accounts and access rights. To make your database compatible with the user management tool: 1. In the Atoll Management Console window, right-click the database whose user accounts you wish to manage. 2. Select Manage Users. The User Management dialog box appears. 3. Click Yes when asked whether you want to make your database compatible with the user management tool. The Atoll Management Console adds a GUIUserRights table in the database with the following structure: Field
Type
Description
ATOLL_USER
Text (50)
Name of the user account
RIGHTS
Memo
Semi-colon separated set of interface access rights
Each user’s interface access rights are stored in a unique record in the GUIUserRights table. The contents of the RIGHTS field have the following syntax: RADIOPARAMS;CALCPARAMS;PROPAGMODELS;PASSWORD The syntax is explained in detail in "Defining Database and Interface Access Rights" on page 82. If interface access rights are not defined for a database, i.e., the GUIUserRights table does not exist, all the users have unrestricted access to the Atoll interface. If interface access rights are defined for a database, and a user creates a document from the database or opens a document connected to the database, Atoll retrieves the interface access rights for the user when he enters his user name and password to access the database. If the database is not reachable, the user is not listed in the GUIUserRights table, or if the password is not correct, the user’s interface access rights are set to read-only by default (for more information, see "Defining Database and Interface Access Rights" on page 82). If the user is listed in the GUIUserRights table, his interface access rights are read and applied to the Atoll interface (table grids and properties dialog boxes). A message is displayed in the Event Viewer window to inform the user of his interface access rights. It is possible to remove interface access restrictions by disconnecting the document from the database. However, a disconnected document cannot be reconnected to the database. The GUIUserRights table is also stored in the Atoll document, and is updated when the document is saved. Hence, users can work on their documents without actually being connected to the database, and still have their usual interface access rights applied in the document. Atoll does not ask for the user name and password when a document is opened using the API. The interface access rights stored in the document are used.
When database connection properties are modified for a document, for example, when a different user enters his user name and password in the connection properties, Atoll reads and applies the interface access rights defined for the new user.
6.3.1 Defining Database and Interface Access Rights For any existing user account, you can set the database and Atoll interface access rights using the Atoll Management Console. To manage database and Atoll interface access rights for an existing user account: 1. In the right-hand pane of the Atoll Management Console window, right-click a database. A context menu appears. 2. In the context menu, select Manage Users. The User Management dialog box appears.
82
Atoll 3.3.2 Administrator Manual Chapter 6: Multi-user Environments
AT332_AM_E0
Figure 6.2: Managing User Accounts and Access Rights 3. Under Atoll projects, select the project for which you want to manage user accounts. 4. Under List of users, select the user account whose database and interface access rights you want to set. Users who have database access rights in the selected database are marked with the green icon ( ). Users who do not have any database access rights in the selected database (Category = No Access) are marked with the red icon ( ). Locked (deactivated) user accounts are marked with a yellow lock icon ( ). For more information on locked user accounts, see "Creating and Managing User Accounts" on page 85. 5. You can set the Filter list to: •
All users: Users with access (
• • • •
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
), without access (
), or locked (
)
6. Under Database rights, you can select a database access Rights category: • • • •
No access: User without read and write access to the database. The database is not visible to these users and they are not allowed to create Atoll documents based on this database. Read only: Users allowed to create Atoll documents from the database but without write permissions to any table of the database, i.e., users cannot archive changes made in the Atoll document to the database. Standard: Users with read and write access to some tables of the database containing radio network data (see table below). Super-User: Users with read and write access to all the tables of the database.
Database access rights are stored in the user account properties in Oracle. If you are working with an RDBMS other than Oracle, you will not be able to set database access rights. You can, however, still set interface access rights as explained below. Technologies
Tracked Tables
GSM GPRS EDGE
Sites, SitesLists, SitesListsNames, Transmitters, TXLists, TXListsNames, TRGs, TRXs, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt, NeighboursConstraints, NeighboursConstraintsExt
UMTS HSPA
Sites, SitesLists, SitesListsNames, Transmitters, TXLists, TXListsNames, CDMACells, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt, NeighboursConstraints, NeighboursConstraintsExt
CDMA2000 1xRTT 1xEV-DO
Sites, SitesLists, SitesListsNames, Transmitters, TXLists, TXListsNames, CDMACells, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt, NeighboursConstraints, NeighboursConstraintsExt
83
Atoll 3.3.2 Administrator Manual Chapter 6: Multi-user Environments
© Forsk 2016
Technologies
Tracked Tables
LTE
Sites, SitesLists, SitesListsNames, Transmitters, TXLists, TXListsNames, T4GCells, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt, NeighboursConstraints, NeighboursConstraintsExt, lcagroups, lcagroupdefs, lcompsets, lcompsetdefs, lmbsfnareas, lmbsfnareadefs
WiMAX/Wi-Fi
Sites, SitesLists, SitesListsNames, Transmitters, TXLists, TXListsNames, WCells, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt, NeighboursConstraints, NeighboursConstraintsExt
3GPP
sites, siteslists, siteslistsnames, ltransmitters, utransmitters, gtransmitters, ltxlists, ltxlistsnames, utxlists, utxlistsnames, gtxlists, gtxlistsnames, lcells, ucells, gtrgs, gtrxs, lrepeaters, urepeaters, grepeaters, lsecondaryantennas, usecondaryantennas, gsecondaryantennas, lneighbours, uneighbours, gneighbours, lneighext, uneighext, gneighext, guneighbours, ugneighbours, glneighbours, lgneighbours, ulneighbours, luneighbours, lneighextconstraints, uneighextconstraints, gneighextconstraints, lcagroups, lcagroupdefs, lcompsets, lcompsetdefs, lmbsfnareas, lmbsfnareadefs
3GPP2
sites, siteslists, siteslistsnames, ltransmitters, ctransmitters, ltxlists, ltxlistsnames, ctxlists, ctxlistsnames, lcells, ccells, lrepeaters, crepeaters, lsecondaryantennas, csecondaryantennas, lneighbours, cneighbours, lneighext, cneighext, lcneighbours, clneighbours, lneighextconstraints, cneighextconstraints, lcagroups, lcagroupdefs, lcompsets, lcompsetdefs, lmbsfnareas, lmbsfnareadefs
Microwave Radio Links/Backhaul
Sites, SitesLists, SitesListsNames, MWLinks, MWHubs, MWPmp, MWMultiHops, MWMultiHopsLinks, MWRepeaters, MWOTLinks, MWPorts, BHNodes, BHSegments, BHSegmentsMedia
7. Under Interface rights, you can select interface access rights for: •
Access to radio data: • Full: (RADIOPARAMS = ALL) Users with read and write access to all the tables and properties dialog boxes. • Standard: (RADIOPARAMS = STD) Users with read and write access to radio network data tables and properties dialog boxes including sites, transmitters, cells, carrier aggregation groups, carrier aggregation group definitions, CoMP sets, CoMP set definitions, MBSFN areas, MBSFN area definitions, subcells, repeaters, remote antennas, secondary antennas, intra- and inter-technology neighbours and exceptional pairs, site and transmitter lists, microwave point-to-point, point-to-multipoint, and multi-hop links, microwave repeaters, microwave hubs. • Read only: (RADIOPARAMS = NONE) Users with read-only access to tables and properties dialog boxes, i.e., users are not allowed to modify radio network data and parameters. •
•
Database access rights and access rights to radio data in Atoll can be set independently. For example, a user can have full access rights in the interface but not be allowed to archive changes to the database. However, access rights in the interface should only be granted if the user has at least read-only access to the database.
•
Access to calculation parameters: • All: (CALCPARAMS = ALL) Users with read and write access to all coverage predictions, their calculation settings, and to microwave calculation settings (Models, Objectives, and Clutter Categories tabs of the Properties dialog box of the Microwave Radio Links folder). • Standard: (CALCPARAMS = STD) Users with access to customised coverage predictions only, and allowed to modify coverage conditions and display settings. These users do not have access to the microwave calculation settings mentioned above. • Customised only: (CALCPARAMS = NONE) Users with access to customised coverage predictions only, but not allowed to modify coverage conditions and display settings. These users do not have access to the microwave calculation settings mentioned above.
•
Access to propagation models: • Full: (PROPAGMODELS = ALL) Users with read and write access to all propagation models and their properties. • Read only: (PROPAGMODELS = NONE) Users with read-only access to the properties of all the propagation models. Adding and deleting propagation models is also not allowed.
•
Password confirmation: • Yes: (PASSWORD = STD) Atoll will ask users for password when opening a document connected to this database or creating a new document from this database. • No: (PASSWORD = NONE) Atoll will not ask users for password when opening a document connected to this database or creating a new document from this database.
8. Click OK. The database and interface access rights of the selected user are saved in the database.
84
Atoll 3.3.2 Administrator Manual Chapter 6: Multi-user Environments
AT332_AM_E0
6.3.2 Creating and Managing User Accounts You can create and edit user accounts using the Atoll Management Console. To create a new user account: 1. In the right-hand pane of the Atoll Management Console window, right-click a database. A context menu appears. 2. In the context menu, select Manage Users. The User Management dialog box appears (see Figure 6.2 on page 83). 3. Under Users, click Create. The User Creation/Edition dialog box appears.
Figure 6.3: User Creation/Edition dialog box 4. Under Identification: •
Enter a User name, a Password, and Confirm your password.
•
Select a Tablespace, a Temporary tablespace, and a Profile.
5. Under Advanced: •
Select Use operating system authentication if you want to use OS authentication prefix with the user name.
•
Select "Unlimited tablespace" privilege if you want to assign this system privilege to the user or specify a Quota in megabytes.
6. Click OK. The new user account is created. To edit a user account: 1. In the right-hand pane of the Atoll Management Console window, right-click a database. A context menu appears. 2. In the context menu, select Manage Users. The User Management dialog box appears (see Figure 6.2 on page 83). 3. Under List of users, select the user account whose information you want to edit. 4. Under Users, click Edit. The Create/Edit User dialog box appears (Figure 6.3 on page 85). 5. Under Identification, modify the user’s Password and the assigned Tablespace, Temporary tablespace, and Profile. 6. Under Advanced: •
Select Use operating system authentication if you want to use OS authentication prefix with the user name.
•
Select "Unlimited tablespace" privilege if you want to assign this system privilege to the user or specify a Quota in megabytes.
7. Click OK. The new account information is saved. To deactivate (lock) a user account: 1. In the right-hand pane of the Atoll Management Console window, right-click a database. A context menu appears. 2. In the context menu, select Manage Users. The User Management dialog box appears (see Figure 6.2 on page 83). 3. Under List of users, select the user account you want to deactivate. 4. Under Users, click Edit. The Create/Edit User dialog box appears (Figure 6.3 on page 85).
85
Atoll 3.3.2 Administrator Manual Chapter 6: Multi-user Environments
© Forsk 2016
5. Under Advanced, select the Account locked check box. 6. Click OK. The user account is deactivated and can no longer be used. To delete a user account: 1. In the right-hand pane of the Atoll Management Console window, right-click a database. A context menu appears. 2. In the context menu, select Manage Users. The User Management dialog box appears (see Figure 6.2 on page 83). 3. Under List of users, select the user account you want to deactivate. 4. Under Users, click Delete. The user account is deleted.
6.3.3 Resetting User Database Permissions The permissions reset feature in the Atoll Management Console enables you to rebuild user database permissions while keeping existing role assignments. It is particularly useful after a major Atoll upgrade or after tables were added as a result of a project customization, and for all unforeseen reasons which can require fixing user database permissions. The reset process does not remove any object privileges assigned prior to rebuilding the database. It just looks for new objects and assigns permissions based on existing user profiles ("Administrator", "Standard", "Read-only", "Super-user"). To reset user permissions: 1. In the right-hand pane of the Atoll Management Console window, right-click a database. A context menu appears. 2. In the context menu, select Manage Users. The User Management dialog box appears (see Figure 6.2 on page 83). 3. Under Database rights, click Reset. 4. Acknowledge the message informing you about the rebuilding process duration. The duration of the database rebuilding process depends on the number of users and on the database processing speed.
86
Atoll 3.3.2 Administrator Manual Chapter 6: Multi-user Environments
AT332_AM_E0
6.4 Appendices The following appendices provide additional information on: • • • •
"Appendix 1: Checking Data Integrity" on page 87 "Appendix 2: Database Regionalisation" on page 87 "Appendix 3: Calculating Path Loss Matrices" on page 88 "Appendix 4: Path Loss Matrices From Different Sources" on page 88
6.4.1 Appendix 1: Checking Data Integrity Atoll includes data consistency and integrity checking tools that allow you to check data consistency between the different Atoll tables (Sites, Transmitters, etc.). It is recommended that the Atoll administrator runs data integrity checks regularly on the master Atoll document after it is updated with data modifications in the master database. To perform data integrity check: •
In Atoll, select Document > Data Audit > Integrity Check. Atoll searches for records with integrity problems which can occur with objects that have foreign keys. Integrity problems occur when records refer records that do not exist. For example, transmitters located on sites that do not exist in the Sites table, transmitters referring to an antenna that does not exist in the Antennas table, etc.). Records with integrity problems can be deleted when found.
To perform undefined record check: •
In Atoll, select Document > Data Audit > Undefined Record Check. Atoll searches for undefined records such as sites without transmitters, transmitters without subcells, TRXs, and neighbours in GSM, transmitters without cells, and cells without neighbours in UMTS, CDMA2000, TD-SCDMA, LTE, WiMAX, and Wi-Fi. Atoll lists all the undefined records found in the Event Viewer.
To perform duplicate record check: •
In Atoll, select Document > Data Audit > Duplicate Record Check. Atoll searches for records that have the same identifier. For example, sites with the same name, transmitters with the same name, etc. Atoll lists all the duplicate records in the Event Viewer.
To perform microwave data check: 1. In Atoll, select Document > Data Audit > Microwave Data Check. The Microwave Data Check dialog box appears. 2. In the Microwave Data Check dialog box, select the data to check. 3. Select List all the checks to list all the checks in the Event Viewer. 4. Click OK. Atoll searches the microwave links tables for problems related to the selected checks. Atoll lists the problems found in the Event Viewer. If you fix any problems in the Atoll document, you must archive the changes in the database in order to fix the problems for all the users working with that database.
6.4.2 Appendix 2: Database Regionalisation You can subdivide the network into regions in the following ways: •
Static regionalisation using multi-level databases Static regionalisation can be based on site lists, SQL filters, or geographic zones in the form of filtering polygons. Static regionalisation is carried out by creating project databases from the master database, i.e., multi-level databases as explained in "Working With Multi-level Databases Using Oracle" on page 61. Static regionalisation requires manual synchronisation between the master database and the regional project databases using the Atoll Management Console. In a multi-level database environment, end-users work with project databases, refreshing and archiving data as they continue to work on their respective regions of the network. Data archive and refresh between the project databases and the master database are performed by the administrator alone.
87
Atoll 3.3.2 Administrator Manual Chapter 6: Multi-user Environments
• • •
© Forsk 2016
Advantage: High performance. Disadvantage: Manual Synchronisation between the master and the project databases.
Dynamic regionalisation using Oracle Spatial or Oracle Locator Dynamic regionalisation can be based on Oracle Spatial, which does not create separate regional databases from the master database, but rather lets the different users work with the master database directly while managing their access privileges according to their user connection properties. In an Atoll multi-user environment, you can create such regionalisation without installing Oracle Spatial. You can implement this solution using Oracle Locator, which is provided in the standard Oracle installation. Specific documents explaining how to set up this regionalisation, using Oracle, in any Atoll master database are available on demand from Forsk. These documents provide scripts for creating different types of users, e.g., the administrator, advanced user, read-only user, etc., and give examples of how to set up regions in the network and how to assign user rights to each region. • •
Advantage: Once set up, does not require administrator intervention. Disadvantage: Slow performance (archiving data in the database takes a long time).
6.4.3 Appendix 3: Calculating Path Loss Matrices You can calculate only the invalid path loss matrices or all the path loss matrices in Atoll or using a macro. You should only calculate the shared path loss matrices when they are not being accessed by users.
To calculate invalid path loss matrices only: 1. Right-click the Transmitters folder. The context menu appears. 2. Select Calculations > Calculate Path Loss Matrices. Atoll calculates path loss matrices for all active transmitters in the folder or subfolder. Only invalid and nonexistent matrices are calculated. To calculate all the path loss matrices (valid and invalid): 1. Right-click the Transmitters folder. The context menu appears. 2. Select Calculations > Force Path Loss Matrix Calculation. Atoll calculates all the path loss matrices for all active transmitters in the folder or subfolder. You can write a script or macro to update path loss matrices automatically at regular intervals. The script or macro should: 1. Start Atoll (Start). 2. Open the master Atoll document (Open). 3. Refresh the contents of the document with data from the database (Refresh). 4. Calculate path loss matrices (Calculate). 5. Save the master Atoll document (Save). 6. Close Atoll (Exit). A path loss update macro is available from Forsk on demand. You should also make regular backups of the master Atoll document. The above macro could also create a backup ATL file of the master Atoll document on a regular basis. This file can be overwritten daily, whenever path losses are calculated.
6.4.4 Appendix 4: Path Loss Matrices From Different Sources Atoll calculates path loss matrices and creates path loss matrix storage files using the propagation models assigned to transmitters. Atoll can also work with path loss matrices calculated by other tools. To use path loss matrices from different sources, make sure that the path loss matrices are: • • •
88
Available in a format compatible with Atoll. File formats are described in "Path Loss Matrix File Format" on page 108. Stored at the location set in the Atoll document. Valid. If the path loss matrices are not valid, Atoll will automatically calculate them the next time they are used.
AT332_AM_E0
Atoll 3.3.2 Administrator Manual Chapter 6: Multi-user Environments
Path loss matrices calculated by other tools should include antenna pattern attenuation (i.e., should be masked) in order to be consistent with the path loss matrices calculated by Atoll. The shared path loss matrices architecture can contain path loss matrices from different sources. The Pathloss.dbf file provides the means to manage several sources of path loss matrices. This file stores, among other information, the validity status and the location (path) of the path loss matrix files for each transmitter. Let us assume that users of group A wish to work with the path loss matrices generated by Atoll only, and users of group B wish to work with path loss matrices generated by a different tool for a part of the network and with path loss matrices generated by Atoll where the matrices from the other tool are not available. Let us assume that the shared path loss matrices folder where Atoll stores the generated path loss matrices files is C:\Path_Loss_Internal, and the folder where the other tool stores its path loss matrices is C:\Path_Loss_External. The Pathloss.dbf file in the Path_Loss_Internal folder will store the path to the LOS files for each transmitter in the network. This folder can be set as the shared path loss matrices folder in the ATL files of group A users. To set up the shared path loss matrices folder for group B users, you must create a new folder with a Pathloss.dbf file in it. This folder can be called C:\Path_Loss_Mixed. The Pathloss.dbf file in this folder can be a copy of the Pathloss.dbf file in the Path_Loss_Internal folder with the paths to the LOS files modified. For example, if the path loss matrices generated by the other tool include Transmitter_1, the Pathloss.dbf file in the Path_Loss_Mixed folder will have all the same entries as Pathloss.dbf file in the Path_Loss_Internal folder except for the path for the Transmitter_1 path loss matrices file. Figure 6.4 on page 89 explains this concept.
Figure 6.4: Path Loss Architecture for Multiple Source Path Loss Matrices Once the Pathloss.dbf file in the Path_Loss_Mixed folder is updated with the correct paths corresponding to the different transmitters, the Path_Loss_Mixed folder can be set as the shared path loss matrices folder in the ATL files of group B users. If a group B user changes some parameters which make some path loss matrices invalid, Atoll will recalculate the private path loss matrices with the propagation models assigned to the transmitters. The external path loss matrix will no longer be used.
89
Atoll 3.3.2 Administrator Manual Chapter 6: Multi-user Environments
90
© Forsk 2016
Chapter 7 Coordinate Systems and Units This chapter covers the following topics: •
"Coordinate Systems" on page 93
•
"Units" on page 99
•
"BSIC Format" on page 100
Atoll 3.3.2 Administrator Manual © Forsk 2016
92
Atoll 3.3.2 Administrator Manual Chapter 7: Coordinate Systems and Units
AT332_AM_E0
7 Coordinate Systems and Units 7.1 Coordinate Systems A map or a geo-spatial database is a flat representation of data collected over a curved surface. Projection is a means of producing all or part of a spheroid on a flat surface, which cannot be done without distortion. It is up to the cartographer to choose the characteristic (distance, direction, scale, area, or shape) that he wants to produce accurately on a flat surface at the expense of the other characteristics, or to make a compromise on several characteristics. The projected zones are referenced using cartographic coordinates (metre, yard, etc.). Two projection methods are widely used: •
•
The Lambert Conformal-Conic Method: A portion of the earth is projected on a cone conceptually secant at one or two standard parallels. This projection method is useful for representing countries or regions that have a predominant east-west expanse. The Universal Transverse Mercator (UTM) Method: A portion of the earth is projected on a cylinder tangent to a meridian (which is transverse or crosswise to the equator). This projection method is useful for mapping large areas that are oriented north-south.
A geographic system is not a projection, but a representation of a location on the surface of the earth in geographic coordinates (degree-minute-second, gradient) with the latitude and longitude with respect to a meridian (e.g., Paris for NTF system and Greenwich for ED50 system). Locations in a geographic system can be converted into other projections. References: 1. Snyder, John. P., Map Projections Used by the US Geological Survey, 2nd Edition, United States Government Printing Office, Washington, D.C., 313 pages, 1982. 2. http://www.colorado.edu/geography/gcraft/notes/gps/gps_f.html 3. http://www.epsg.org/Geodetic.html 4. http://geodesie.ign.fr/contenu/fichiers/documentation/pedagogiques/ transfo.pdf (French)
7.1.1 Definition of a Coordinate System A geographic coordinate system is a latitude and longitude coordinate system. The latitude and longitude are related to an ellipsoid, a geodetic datum, and a prime meridian. The geodetic datum provides the position and orientation of the ellipsoid relative to the earth. Cartographic coordinate systems are obtained by transforming each (latitude, longitude) value into an (easting, northing) value. A projection coordinate system is obtained by transforming each (latitude, longitude) value into an (easting, northing) value. Projection coordinate systems are geographic coordinate systems that provide longitude and latitude, and the transformation method characterised by a set of parameters. Different methods might require different sets of parameters. For example, the parameters required for Transverse Mercator coordinate systems are: • • • • •
The longitude of the natural origin (central meridian) The latitude of the natural origin The False Easting value The False Northing value A scaling factor at the natural origin (central meridian)
Basic definitions are presented below. Geographic Coordinate System The geographic coordinate system is a datum and a meridian. Atoll enables you to choose the most suitable geographic coordinate system for your geographic data. Datum The datum consists of the ellipsoid and its position relative to the WGS84 ellipsoid. In addition to the ellipsoid, translation, rotation, and distortion parameters define the datum. Meridian The standard meridian is Greenwich, but some geographic coordinate systems are based on other meridians. These meridians are defined by the longitude with respect to Greenwich.
93
Atoll 3.3.2 Administrator Manual Chapter 7: Coordinate Systems and Units
© Forsk 2016
Ellipsoid The ellipsoid is the pattern used to model the earth. It is defined by its geometric parameters. Projection The projection is the transformation applied to project the ellipsoid of the earth on to a plane. There are different projection methods that use specific sets of parameters. Projection Coordinate System The projection coordinate system is the result of the application of a projection to a geographic coordinate system. It associates a geographic coordinate system and a projection. Atoll enables you to choose the projection coordinate system matching your geographic data.
7.1.2 Types of Coordinate Systems in Atoll Depending on the working environment, there can be either two or four coordinate systems used in Atoll. If you are working with stand-alone documents, i.e., documents not connected to databases, there are two coordinate systems used in Atoll: • •
Projection coordinate system Display coordinate system
If you are working in a multi-user environment, Atoll uses four coordinate systems: • • • •
Projection coordinate system for the Atoll document Display coordinate system for the Atoll document Internal projection coordinate system for the database Internal display coordinate system for the database
Projection Coordinate System The projection coordinate system is the coordinate system of the available raster geographic data files. You should set the projection coordinate system of your Atoll document so that it corresponds to the coordinate system of the available raster geographic data. You can set the projection coordinate system of your document in the Options dialog. All the raster geographic data files that you want to import and use in an Atoll document must have the same coordinate system. You cannot work with raster geographic data files with different coordinate systems in the same document. If you import vector geographic data (e.g., traffic, measurements, etc.) with different coordinate systems, it is possible to convert the coordinate systems of these data into the projection coordinate system of your Atoll document. The projection coordinate system is used to keep the coordinates of sites (radio network data) consistent with the geographic data. When you import a raster geographic data file, Atoll reads the geo-referencing information from the file (or from its header file, depending on the geographic data file format), i.e., its Northwest pixel, to determine the coordinates of each pixel. Atoll does not use any coordinate system during the import process. However, the geo-referencing information of geographic data files are considered to be provided in the projection coordinate system of the document. Display Coordinate System The display coordinate system is the coordinate system used for the display, e.g., in dialogs, in the Map window rulers, in the status bar, etc. The coordinates of each pixel of geographic data are converted to the display coordinate system from the projection coordinate system for display. The display coordinate system is also used for sites (radio network data). You can set the display coordinate system of your document in the Options dialog. If you import sites data, the coordinate system of the sites must correspond to the display coordinate system of your Atoll document. If you change the display coordinate system in a document which is not connected to a database, the coordinates of all the sites are converted to the new display system. If the coordinate systems of all your geographic data files and sites (radio network data) are the same, you do not have to define the projection and display coordinate systems separately. By default, the two coordinate systems are the same.
94
Atoll 3.3.2 Administrator Manual Chapter 7: Coordinate Systems and Units
AT332_AM_E0
Internal Coordinate Systems The internal coordinate systems are the projection and the display coordinate systems stored in a database. The projection and display coordinate systems set by the administrator in the central Atoll project are stored in the database when the database is created, and cannot be modified by users. Only the administrator can modify the internal coordinate systems manually by editing the entries in the CoordSys and the Units tables. All Atoll documents opened from a database will have the internal coordinate systems of the database as their default projection and display coordinate systems. When exporting an Atoll project to a database, the currently chosen display coordinate system becomes the internal display coordinate system for the database, and the currently chosen projection coordinate system becomes the internal projection coordinate system for the database. Although Atoll stores both the coordinate systems in the database, i.e., the projection and the display coordinate systems, the only relevant coordinate system for the database is the internal display coordinate system because this coordinate system is the one used for the coordinates of sites (radio network data). Users working on documents connected to a database can modify the coordinate systems in their documents locally, and save these changes in their documents, but they cannot modify the coordinate systems stored in the database. If you change the display coordinate system in a document which is not connected to a database, the coordinates of all the sites are converted to the new display system. If you change the display coordinate system in a document which is connected to a database, the coordinates of all the sites are converted to the new coordinate system in the Atoll document locally but not in the database because the internal coordinate systems cannot be changed. Atoll uses the internal coordinates systems in order to keep the site coordinates consistent in the database which is usually accessed by a large number of users in a multi-user environment.
7.1.3 Coordinate Systems File Format The Coordsystems folder located in the Atoll installation directory contains all the coordinate systems, both geographic and cartographic, offered in the tool. Coordinate systems are grouped by regions. A catalogue per region and a "Favourites" catalogue are available in Atoll. The Favourites catalogue is initially empty and can be filled by the user by adding coordinate systems to it. Each catalogue is described by an ASCII text file with .cs extension. In a .cs file, each coordinate system is described in one line. The line syntax for describing a coordinate system is: Code = "Name of the system"; Unit Code; Datum Code; Projection Method Code, Projection Parameters; "Comments" Examples: 4230 = "ED50"; 101; 230; 1; "Europe - west" 32045 = "NAD27 / Vermont"; 2; 267; 6, -72.5, 42.5, 500000, 0, 0.9999643; "United States - Vermont" You should keep the following points in mind when editing or creating .cs files: • •
The identification code enables Atoll to differentiate coordinates systems. In case you create a new coordinate system, its code must be an integer value higher than 32767. When describing a new datum, you must enter the ellipsoid code and parameters instead of the datum code in brackets. There can be 3 to 7 parameters defined in the following order: Dx, Dy, Dz, Rx, Ry, Rz, S. The syntax of the line in the .cs file will be:
Code = "Name of the system"; Unit Code; {Ellipsoid Code, Dx, Dy, Dz, Rx, Ry, Rz, S}; Projection Method Code, Projection Parameters; "Comments" •
• •
There can be up to seven projection parameters. These parameters must be ordered according to the parameter index (see "Projection Parameter Indices" on page 98). Parameter with index 0 is the first one. Projection parameters are delimited by commas. For UTM projections, you must provide positive UTM zone numbers for north UTM zones and negative numbers for south UTM zones. You can add all other information as comments (such as usage or region).
Codes of units, data, projection methods, and ellipsoids, and projection parameter indices are listed in the tables below.
95
Atoll 3.3.2 Administrator Manual Chapter 7: Coordinate Systems and Units
© Forsk 2016
Unit Codes Code
Cartographic Units
Code
Geographic Units
0
Metre
100
Radian
1
Kilometre
101
Degree
2
Foot
102
Grad
3
Link
103
ArcMinute
4
Chain
104
ArcSecond
5
Yard
-1
Unspecified
6
Nautical mile
Code
Datum
7
Mile
-1
Unspecified
Datum Codes
96
Code
Datum
121
Greek Geodetic Reference System 1987
260
Manoca
125
Samboja
261
Merchich
126
Lithuania 1994
262
Massawa
130
Moznet (ITRF94)
263
Minna
131
Indian 1960
265
Monte Mario
171
RGF93
266
M'poraloko
181
Luxembourg 1930
267
North American Datum 1927
201
Adindan
268
NAD Michigan
202
Australian Geodetic Datum 1966
269
North American Datum 1983
203
Australian Geodetic Datum 1984
270
Nahrwan 1967
204
Ain el Abd 1970
271
Naparima 1972
205
Afgooye
272
New Zealand Geodetic Datum 1949
206
Agadez
273
NGO 1948
207
Lisbon
274
Datum 73
208
Aratu
275
Nouvelle Triangulation Francaise
209
Arc 1950
276
NSWC 9Z-2
210
Arc 1960
277
OSGB 1936
211
Batavia
278
OSGB 1970 (SN)
212
Barbados
279
OS (SN) 1980
213
Beduaram
280
Padang 1884
214
Beijing 1954
281
Palestine 1923
215
Reseau National Belge 1950
282
Pointe Noire
216
Bermuda 1957
283
Geocentric Datum of Australia 1994
217
Bern 1898
284
Pulkovo 1942
218
Bogota
285
Qatar
219
Bukit Rimpah
286
Qatar 1948
221
Campo Inchauspe
287
Qornoq
222
Cape
288
Loma Quintana
223
Carthage
289
Amersfoort
224
Chua
290
RT38
225
Corrego Alegre
291
South American Datum 1969
226
Cote d'Ivoire
292
Sapper Hill 1943
227
Deir ez Zor
293
Schwarzeck
228
Douala
294
Segora
Atoll 3.3.2 Administrator Manual Chapter 7: Coordinate Systems and Units
AT332_AM_E0
Code
Datum
Code
Datum
229
Egypt 1907
295
Serindung
230
European Datum 1950
296
Sudan
231
European Datum 1987
297
Tananarive 1925
232
Fahud
298
Timbalai 1948
233
Gandajika 1970
299
TM65
234
Garoua
300
TM75
235
Guyane Francaise
301
Tokyo
236
Hu Tzu Shan
302
Trinidad 1903
237
Hungarian Datum 1972
303
Trucial Coast 1948
238
Indonesian Datum 1974
304
Voirol 1875
239
Indian 1954
305
Voirol Unifie 1960
240
Indian 1975
306
Bern 1938
241
Jamaica 1875
307
Nord Sahara 1959
242
Jamaica 1969
308
Stockholm 1938
243
Kalianpur
309
Yacare
244
Kandawala
310
Yoff
245
Kertau
311
Zanderij
247
La Canoa
312
Militar-Geographische Institut
248
Provisional South American Datum 1956
313
Reseau National Belge 1972
249
Lake
314
Deutsche Hauptdreiecksnetz
250
Leigon
315
Conakry 1905
251
Liberia 1964
322
WGS 72
252
Lome
326
WGS 84
253
Luzon 1911
611
Hong Kong 1980
254
Hito XVIII 1963
674
SIRGAS 2000
255
Herat North
901
Ancienne Triangulation Francaise
256
Mahe 1971
902
Nord de Guerre
257
Makassar
903
NAD 1927 Guatemala/Honduras/Salvador (Panama Zone)
258
European Reference System 1989
1026
Taiwan Datum 1997
Projection Method Codes Code
Projection Method
Code
Projection Method
0
Undefined
9
New Zealand Map Grid
1
No projection: Longitude / Latitude
10
Hotine Oblique Mercator
2
Lambert Conformal Conical 1SP
11
Laborde Oblique Mercator
3
Lambert Conformal Conical 2SP
12
Swiss Oblique Cylindrical
4
Mercator
13
Oblique Mercator
5
Cassini-Soldner
14
UTM Projection
6
Transverse Mercator
15
Albers Equal Area Conic
7
Transverse Mercator South Oriented
16
American Polyconic
8
Oblique Stereographic
Ellipsoid Codes Code
Name
Major Axis
Minor Axis
1
Airy 1830
6377563.396
6356256.90890985
2
Airy Modified 1849
6377340.189
6356034.44761111
3
Australian National Spheroid
6378160
6356774.71919531
97
Atoll 3.3.2 Administrator Manual Chapter 7: Coordinate Systems and Units
© Forsk 2016
Code
Name
Major Axis
Minor Axis
4
Bessel 1841
6377397.155
6356078.96261866
5
Bessel Modified
6377492.018
6356173.50851316
6
Bessel Namibia
6377483.865
6356165.38276679
7
Clarke 1858
6378293.63924683
6356617.98173817
8
Clarke 1866
6378206.4
6356583.8
9
Clarke 1866 Michigan
6378693.7040359
6357069.45104614
10
Clarke 1880 (Benoit)
6378300.79
6356566.43
11
Clarke 1880 (IGN)
6378249.2
6356515
12
Clarke 1880 (RGS)
6378249.145
6356514.86954978
13
Clarke 1880 (Arc)
6378249.145
6356514.96656909
14
Clarke 1880 (SGA 1922)
6378249.2
6356514.99694178
15
Everest 1830 (1937 Adjustment)
6377276.345
6356075.41314024
16
Everest 1830 (1967 Definition)
6377298.556
6356097.5503009
17
Everest 1830 (1975 Definition)
6377301.243
6356100.231
18
Everest 1830 Modified
6377304.063
6356103.03899315
19
GRS 1980
6378137
6356752.31398972
20
Helmert 1906
6378200
6356818.16962789
21
Indonesian National Spheroid
6378160
6356774.50408554
22
International 1924
6378388
6356911.94612795
23
International 1967
6378160
6356774.71919530
24
Krassowsky 1940
6378245
6356863.01877305
25
NWL 9D
6378145
6356759.76948868
26
NWL 10D
6378135
6356750.52001609
27
Plessis 1817
6376523
6355862.93325557
28
Struve 1860
6378297
6356655.84708038
29
War Office
6378300.583
6356752.27021959
30
WGS 84
6378137
6356752.31398972
31
GEM 10C
6378137
6356752.31398972
32
OSU86F
6378136.2
6356751.51667196
33
OSU91A
6378136.3
6356751.61633668
34
Clarke 1880
6378249.13884613
6356514.96026256
35
Sphere
6371000
6371000
Projection Parameter Indices Index
Projection Parameter
Index
Projection Parameter
0
UTM zone number
4
Scale factor at origin
0
Longitude of origin
4
Latitude of 1st parallel
1
Latitude of origin
5
Azimuth of central line
2
False Easting
5
Latitude of 2nd parallel
3
False Northing
6
Angle from rectified to skewed grid
7.1.4 Creating a Coordinate System in Atoll Atoll provides a large default catalogue of coordinate systems. However, it is possible to add new geographic and cartographic coordinate systems. New coordinate systems can be created from scratch or initialised based on existing ones. To create a new coordinate system from scratch: 1. Select Document > Properties. The Properties dialogue opens. 2. Select the Coordinates tab.
98
Atoll 3.3.2 Administrator Manual Chapter 7: Coordinate Systems and Units
AT332_AM_E0
3. Click the Browse button (
) to the right of Projection. The Coordinate Systems dialogue appears.
4. Click New. The Coordinate System dialogue appears. 5. In the Coordinate System dialogue: a. Select the coordinate systems catalogue to which you want to add the new coordinate system. b. Under General, enter a Name for the new coordinate system and select a Unit. In Use, you can enter comments about its usage. Atoll assigns the code automatically. c. Under Category, select the Type of coordinate system. Enter the longitude and latitude for a geographic coordinate system, or the type of projection and its set of associated parameters for a cartographic coordinate system (false easting and northing, and the first and second parallels). d. Under Geo, specify the meridian and choose a Datum for the coordinate system. The associated ellipsoid is automatically selected. You can also describe a geodetic datum by selecting "" in the Datum list. In this case, you must select an Ellipsoid and enter parameters (Dx, Dy, Dz, Rx, Ry, Rz, and S) needed for the transformation of the datum into WGS84. 6. Click OK. The new coordinate system is added to the selected coordinate system catalogue. To create a new coordinate system based on an existing system, select a coordinate system in the Coordinate Systems dialogue before clicking New in step 4. The new coordinate system is initialised with the values of the selected coordinate system.
7.2 Units In the Atoll documents, you can define measurement units for reception, transmission, antenna gain, distance, height and offset, and temperature. You can accept the default measurement units, or you can change them using the document properties dialogue. Transmission and Reception Power Units Depending on the working environment, Atoll can use either one or two measurement units for the transmission/reception power. If you are working with stand-alone documents, i.e., documents not connected to databases, there is only one measurement unit used in Atoll for display. It corresponds to the transmission/reception power unit defined in the Atoll document. If you are working in a multi-user environment, Atoll uses two measurement units: •
•
A measurement unit for display in the Atoll document. It corresponds to the transmission/reception power unit defined in the current Atoll document. It is used for the display in the dialogues and in the tables, e.g., reception thresholds (coverage prediction properties, microwave link properties, etc.), and received signal levels (measurements, point analysis, coverage predictions, microwave link properties, etc.). An internal measurement unit for the database. The internal unit is the transmission/reception power unit stored in the database. It corresponds to the transmission/reception power unit used in the master Atoll document when the database is created. Users working in documents connected to a database can modify the transmission/reception power unit and save this change in their documents locally, but they cannot modify the internal power unit stored in the database. Only the administrator can modify it manually by editing the entry in the Units tables.
Antenna Gain Units Depending on the working environment, Atoll can use either one or two measurement units for the antenna gain. If you are working with stand-alone documents, i.e., documents not connected to databases, there is only one measurement unit used in Atoll for display. It corresponds to the antenna gain unit defined in the Atoll document. If you are working in a multi-user environment, Atoll uses two measurement units: • •
A measurement unit for display in the Atoll document. It corresponds to the antenna gain unit defined in the current Atoll document and it is used for the display in the dialogues and in the tables. An internal measurement unit for the database. The internal unit is the antenna gain unit stored in the database. It corresponds to the antenna gain unit used in the master Atoll document when the database is created. Users working in documents connected to a database can modify the antenna gain unit and save this change in their documents locally, but they cannot modify the antenna gain unit stored in the database. Only the administrator can modify it manually by editing the entry in the Units tables.
Distance Units Atoll uses the distance unit defined in the current Atoll document as display unit of the distances in the dialogues, in the tables, and in the status bar.
99
Atoll 3.3.2 Administrator Manual Chapter 7: Coordinate Systems and Units
© Forsk 2016
Metre is used as the internal measurement unit for the distance in all Atoll documents whether they are connected to databases or not. The internal measurement unit is not stored in the database and cannot be changed. Height and Offset Units Atoll uses the height and offset unit defined in the current Atoll document as display unit of the heights and the offsets in the dialogues, in the tables, and in the status bar. Metre is used as the internal measurement unit for the heights and offsets in all Atoll documents whether they are connected to databases or not. The internal measurement unit is not stored in the database and cannot be changed. Temperature Units Atoll uses the temperature unit defined in the current Atoll document as display unit of the temperatures in the dialogues and in the tables. Degree Celsius is used as the internal measurement unit for the temperature in all Atoll documents whether they are connected to databases or not. The internal measurement unit is not stored in the database and cannot be changed.
7.3 BSIC Format Depending on the working environment, there can be either one or two types of BSIC formats. If you are working with standalone documents, i.e., documents not connected to databases, there is only one BSIC format: •
Display BSIC format
If you are working in a multi-user environment, Atoll uses two types of formats: • •
Display BSIC format for the Atoll document Internal BSIC format for the database
The display format is used for the display in dialogs and tables. You can set the display format for your document from the Transmitters folder’s context menu. The internal format is the BSIC format stored in a database. The BSIC format set by the administrator in the central Atoll project is stored in the database when the database is created, and cannot be modified by users. Only the administrator can modify the internal format manually by editing the corresponding entry in the Units tables. All Atoll documents opened from a database will have the internal format of the database as their default BSIC format. Users working on documents connected to a database can modify the format in their documents locally, and save this change in their documents, but they cannot modify the format stored in the database. Atoll expects the BSIC format in the database to be the octal format. If that is not the case, do the following: • •
100
In the Atoll database, update the setting of UNITS.BSIC_FORMAT to 1. In your ATL project (and in any ATL project created from the previous database configuration), go to the Parameters tab, select GSM Network Settings > BSICs > Format > Octal and save the ATL file.
Chapter 8 Atoll File Formats This chapter covers the following topics: •
"Geographic Data Files" on page 103
•
"Path Loss Matrix File Format" on page 108
•
"Path Loss Tuning File Format" on page 111
•
"Interference Matrix File Formats" on page 112
•
""Per Transmitter" Prediction File Format" on page 118
Atoll 3.3.2 Administrator Manual © Forsk 2016
102
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
AT332_AM_E0
8 Atoll File Formats Radio network data in Atoll includes the following, depending on the technology used in the network being planned: • • • •
• • • • • • • •
Site: The geographic location of transmitters (sectors, installed antennas, other equipment). A site can have one or more transmitters. Antenna: The radiation patterns and gains for antennas installed at transmitters. Transmitter: A group of radio devices installed at a site with there transmission/reception characteristics (antennas, feeders, TMAs, other equipment). A transmitter can have one or more cells or subcells. Cell: An RF carrier available at a transmitter in UMTS, CDMA2000, TD-SCDMA, LTE, WiMAX, and Wi-Fi networks. A cell is fully defined by the "transmitter-carrier" pair. Each cell in these networks is independent, i.e., has its own identifier, power levels, performance characteristics. TRX: An RF carrier available at a transmitter in GSM networks. A transceiver (TRX) can carry one ARFCN which can correspond to the BCCH (7 traffic timeslots) or TCH (8 traffic timeslots). Subcell: A subcell is a group of TRXs with the same radio characteristics. A subcell is fully defined by the "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.
This section covers the following file types that are used by Atoll: • • • • •
"Geographic Data Files" on page 103 "Path Loss Matrix File Format" on page 108 "Path Loss Tuning File Format" on page 111 "Interference Matrix File Formats" on page 112 ""Per Transmitter" Prediction File Format" on page 118
8.1 Geographic Data Files Atoll supports multiple types of geographic data, including DTM (Digital Terrain Model), clutter, scanned images, vector data, traffic maps, population, and custom geographic data. Atoll offers import/export filters for the most commonly used geographic data formats. The following tables summarise the supported vector/raster formats. "Raster and Vector" Formats
File Format
Import Export
Atoll Geo Data (AGD)
Both
Planet
Both
Geographic Data Types DTM
Clutter Classes
Clutter Heights
Traffic Maps
Raster Images
User profile densities Sector traffic maps
16-bit
16-bit
16-bit
DTM
Clutter Classes
Clutter Heights
User profile density Sector traffic maps User profile raster (16-bit) User density raster (16-bit)
Population
Web Map Services
Vector
Georeferencing (World File) Embedded
1, 4, 8, 24bit
Index file
"Vector" Formats
File Format
Import Export
SHP
Both
MapInfo (MIF, TAB)
Both
Geographic Data Types Traffic Maps User profile density Sector traffic maps User profile density Sector traffic maps
Raster Images
Population
Web Map Services
Georeferencing (World File)
Vector
Vector
103
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
© Forsk 2016
"Raster" Formats Geographic Data Types
File Format
Import Export
DTM
Clutter Classes
BIL
Both
8, 16, 32-bit
8-bit
TIFF
Both
8, 16-bit
8-bit
BMP
Both
8-bit
8-bit
DXF
Import
Erdas Imagine (IMG)
Import
8, 16, 32-bit
8-bit
ArcView ASCII Grid (TXT)
Export
ASCII
ASCII
ASCII
Vertical Mapper (GRD, GRC)
Both
GRD
GRC
GRD
ECW
Import
24-bit
PNG
Both
All
Yes
PGW file
JPEG
Both
All
Yes
JGW file
Clutter Heights
Web Map Services
Population
User profile raster (8-bit) 8, 16, 32-bit User density raster (16, 32bit)
1, 4, 8, 24bit
8, 16, 32-bit
8, 16-bit
User profile raster (8-bit), User density raster (16, 32bit)
1, 4, 8, 24bit
8, 16, 32-bit
Yes
TFW file
8-bit
User profile raster (8-bit) User density raster (16, 32bit)
1, 4, 8, 24bit
8, 32-bit
Yes
BPW or BMW file
HDR file
User profile density Sector traffic maps
• • • •
Georeferencing (World File)
Raster Images
Traffic Maps
User profile raster (8-bit) 8, 16, 32-bit User density raster (16, 32bit)
Embedded 1, 4, 8, 24bit
8, 16, 32-bit
Embedded
ASCII
ASCII
ASCII
Embedded
User profile raster User density raster
Raster Images
Vector
Embedded ERS file
World files (e.g. TFW, BPW) are header files used for the georeferencing of raster files. See next sections for more information on World file types generated by Atoll. The smallest supported resolution for raster files is 1 m. There is no restriction on the resolution of images. DTM, clutter classes, and clutter height maps must have an integer resolution. All the raster maps you want to import in an ATL document must be represented in the same projection system.
Specific header files are used to describe how data is organised within any of these geographic data file formats. This section describes the following header file formats: • • • • •
"HDR Header File for BIL Files" on page 104 "TFW Header File for TIFF Files" on page 106 "BPW/BMW Header Files for BMP Files" on page 107 "PGW Header File for PNG Files" on page 107 "JGW Header File for JPG Files" on page 107
8.1.1 HDR Header File for BIL Files 8.1.1.1 HDR Header File The HDR file is a text file that contains meta-data describing the organisation of the BIL file. The header file is made of rows, each row having the following format: keyword
value
where ‘keyword’ corresponds to an attribute type, and ‘value’ defines the attribute value. Keywords required by Atoll are described below. Other keywords are ignored.
104
ulxmap
x coordinate of the centre of the upper-left pixel.
ulymap
y coordinate of the centre of the upper-left pixel.
xdim
x size in metre of a pixel.
ydim
y size in metre of a pixel.
ncols
Number of columns in the image.
nrows
Number of rows in the image.
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
AT332_AM_E0
nbits
Number of bits per pixel per band: 16 ou 32 for DTMs or clutter heights (altitude in metres). 8 for clutter classes file (clutter code). 16 for path loss matrices (path loss in dB). 32 for calculation results (field value in dBm, dBµV and DBµV/m).
nbands
Number of spectral bands in the image: 1 for DTM, clutter heights, clutter classes, etc. 1 for any picture using a colour table. 3 for RGB pictures.
byteorder Byte order in which image pixel values are stored. Accepted values are M (Motorola byte order) or I (Intel byte order). layout
Must be ‘bil’.
bandrowbytes
Number of bytes per band per row.
totalrowbytes
Total number of bytes of data per row.
skipbytes Byte to be skipped in the image file in order to reach the beginning of the image data. Default value is 0. Four additional keywords can optionally be managed. pixeltype Type of data read (in addition to the length) This can be: SIGNEDINT
Signed integer
8, 16, or 32 bits
FLOAT
Real
32 or 64 bits
If no pixeltype parameter is available, then the default value is UNSIGNEDINT (8, 16, or 32 bits).
In some cases, this keyword can be replaced by datatype defined as follows: datatype
Type of data read (in addition to the length).
This can be: Unumber
Undefined
number of bits (8, 16, or 32 bits)
Inumber
Integer
number of bits (8, 16, or 32 bits)
Rnumber
Real
number of bits (32 or 64 bits)
The other optional keywords are: valueoffset, valuescale, and nodatavalue. By default, integer data types are chosen with respect to the pixel length (nbits). valueoffset
Real value to be added to the read value (Vread).
valuescale
Scaling factor to be applied to the read value.
So, we have V = Vread valuescale + valueoffset nodatavalue
Value corresponding to “NO DATA”.
DTM Sample Here, the data is 20 m. nrows
1500
ncols
1500
nbands
1
nbits
8 or 16
byteorder M layout
bil
105
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
© Forsk 2016
skipbytes 0 ulxmap
975000
ulymap
1891000
xdim
20.00
ydim
20.00
Clutter Classes Sample nrows
1500
ncols
1500
nbands
1
nbits
8
byteorder M layout
bil
skipbytes 0 ulxmap
975000
ulymap
1891000
xdim
20.00
ydim
20.00
8.1.1.2 Additional PRJ Projection File When you export BIL files, Atoll will generate an additional PRJ projection file if the lines below are included in the Atoll.ini file: [RasterExport] ExportBILAsESRI = 1 #default=0 Sample PRJ Projection File 984_UTM_Zone_31N", GEOGCS["GCS_WGS_1984", DATUM["D_WGS_1984", SPHEROID["WGS_1984",6378137,298.257223563]], PRIMEM["Greenwich",0], UNIT["Degree",0.017453292519943295]], PROJECTION["Transverse_Mercator"], PARAMETER["latitude_of_origin",0], PARAMETER["central_meridian",3], PARAMETER["scale_factor",0.9996], PARAMETER["false_easting",500000], PARAMETER["false_northing",0], UNIT["Meter",1]]
8.1.2 TFW Header File for TIFF Files TFW files contain the spatial reference data of associated TIFF files. The TFW file structure is simple; it is an ASCII text file that contains six lines. You can open a TFW file using any ASCII text editor. The TFW file structure is as follows:
a.
106
Line
Description
1
x dimension of a pixel in map units
2a
amount of translation
3
amount of rotation
4
negative of the y dimension of a pixel in map units
5
x-axis map coordinate of the centre of the upper-left pixel
6
y-axis map coordinate of the centre of the upper-left pixel
Atoll does not use the lines 2 and 3 when importing a TIFF format geographic file.
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
AT332_AM_E0
Clutter Classes Sample 100.00 0.00 0.00 -100.00 60000.00 2679900.00
8.1.3 BPW/BMW Header Files for BMP Files The header file is a text file that describes how organised in the BMP file. The header file is made of rows, each row having the following description: Line
Description
1
x dimension of a pixel in map units
2
amount of translation
3
amount of rotation
4
negative of the y dimension of a pixel in map units
5
x-axis map coordinate of the centre of the upper-left pixel
6
y-axis map coordinate of the centre of the upper-left pixel
Atoll supports BPW and BMW header file extensions for Import, but exports headers with BPW file extensions. Clutter Classes Sample 100.00 0.00 0.00 -100.00 60000.00 2679900.00
8.1.4 PGW Header File for PNG Files A PNG world file (PGW file) is a plain text file used by geographic information systems (GIS) to provide georeferencing information for raster map images in PNG format. The world file parameters are: Line
Description
1
x dimension of a pixel in map units
2
amount of translation
3
amount of rotation
4
negative of the y dimension of a pixel in map units
5
x-axis map coordinate of the centre of the upper-left pixel
6
y-axis map coordinate of the centre of the upper-left pixel
8.1.5 JGW Header File for JPG Files A JPEG world file (JGW file) is a plain text file used by geographic information systems (GIS) to provide georeferencing information for raster map images in JPEG format. The world file parameters are: Line
Description
1
x dimension of a pixel in map units
2
amount of translation
3
amount of rotation
107
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
© Forsk 2016
Line
Description
4
negative of the y dimension of a pixel in map units
5
x-axis map coordinate of the centre of the upper-left pixel
6
y-axis map coordinate of the centre of the upper-left pixel
8.2 Path Loss Matrix File Format When path loss matrices are stored externally, i.e., outside the ATL file, the path loss matrices folder contains a ‘pathloss.dbf’ file containing the calculation parameters of the transmitters and one LOS (path loss results) file per calculated transmitter. The path loss matrices folder also contains a LowRes folder with another pathloss.dbf file and one LOS (path loss results) file per transmitter that has an extended path loss matrix. The formats of the pathloss.dbf and LOS files are described here.
8.2.1 Pathloss.dbf File Format The pathloss.dbf file has a standard DBF (dBase III) format. The file can be opened in Microsoft Access, but it should not be modified without consulting the Forsk customer support. For general information, the format of DBF files in any Xbase language is as follows: Notations used in the following tables: FS = FlagShip; D3 = dBaseIII+; Fb = FoxBase; D4 = dBaseIV; Fp = FoxPro; D5 = dBaseV; CL = Clipper
DBF Structure Byte
Description
Remarks
0...n
DBF header (see next part for size, byte 8)
n+1
1st record of fixed length (see next parts); 2nd record (see next part for size, byte10) …; last record
last
optional: 0x1a (eof byte)
If .dbf is not empty
DBF Header The DBF header size is variable and depends on the field count.
108
Byte
Size
Contents
Description
Applies to
00
1
0x03
plain .dbf
FS, D3, D4, D5, Fb, Fp, CL
0x04
plain .dbf
D4, D5 (FS)
0x05
plain .dbf
D5, Fp (FS)
0x43
with .dbv memo var size
FS
0xB3
with .dbv and .dbt memo
FS
0x83
with .dbt memo
FS, D3, D4, D5, Fb, Fp, CL
0x8B
with .dbt memo in D4 format
D4, D5
0x8E
with SQL table
D4, D5
0xF5
with .fmp memo
Fp
01
3
YYMMDD
Last update digits
All
04
4
ulong
Number of records in file
All
08
2
ushort
Header size in bytes
All
10
2
ushort
Record size in bytes
All
12
2
0,0
Reserved
All
14
1
0x01
Begin transaction
D4, D5
0x00
End Transaction
D4, D5
0x00
ignored
FS, D3, Fb, Fp, CL
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
AT332_AM_E0
Byte
Size
Contents
Description
Applies to
15
1
0x01
Encrypted
D4, D5
0x00
normal visible
All
16
12
0 (1)
multi-user environment use
D4,D5
28
1
0x01
production index exists
Fp, D4, D5
0x00
index upon demand
All
29
1
n
language driver ID
D4, D5
0x01
codepage437 DOS USA
Fp
0x02
codepage850 DOS Multi ling
Fp
30
2
32
n*32
+1
1
0x03
codepage1251 Windows ANSI
Fp
0xC8
codepage1250 Windows EE
Fp
0x00
ignored
FS, D3, Fb, Fp, CL
0,0
reserved
All
0x0D
Field Descriptor (see next paragraph)
all
Header Record Terminator
all
Field descriptor array in the DBF header (32 bytes for each field): Byte
Size
Contents
Description
Applies to
0
11
ASCI
field name, 0x00 termin
all
11
1
ASCI
field type (see next paragraph)
all
12
4
n,n,n,n
Fld address in memory
D3
n,n,0,0
offset from record begin
Fp
0,0,0,0
ignored
FS, D4, D5, Fb, CL
16
1
byte
Field length, bin (see next paragraph)
all \ FS,CL: for C field type
17
1
byte
decimal count, bin
all / both used for fld lng
18
2
0,0
reserved
all
20
1
byte
Work area ID
D4, D5
0x00
unused
FS, D3, Fb, Fp, CL
21
2
n,n
multi-user dBase
D3, D4, D5
0,0
ignored
FS, Fb, Fp, CL
0x01
Set Fields
D3, D4, D5
23
1
0x00
ignored
FS, Fb, Fp, CL
24
7
0...0
reserved
all
31
1
0x01
Field is in .mdx index
D4, D5
0x00
ignored
FS, D3, Fb, Fp, CL
Field type and size in the DBF header, field descriptor (1 byte): Size
Type
Description/Storage
Applies to
C 1...n
Char
ASCII (OEM code page chars) rest= space, not \0 term.
all
n = 1...64kb (using deci count)
FS
n = 1...32kb (using deci count)
Fp, CL
n = 1...254
all
D8
Date
8 ASCII digits (0...9) in the YYYYMMDD format
all
F 1...n
Numeric
ASCII digits (-.0123456789) variable pos. of float.point n = 1...20
FS, D4, D5, Fp
N 1...n
Numeric
ASCII digits (-.0123456789) fix posit/no float.point
all
109
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
© Forsk 2016
Size
Type
Description/Storage
Applies to
n = 1...20
FS, Fp, CL
n = 1...18
D3, D4, D5, Fb
ASCII chars (YyNnTtFf space)
FS, D3, Fb, Fp, CL
ASCII chars (YyNnTtFf?)
D4, D5 (FS)
Memo
10 digits repres. the start block posit. in .dbt file, or 10 spaces if no entry in memo
all
V 10
Variable
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
FS
P 10
Picture
binary data in .ftp structure like M
Fp
B 10
Binary
binary data in .dbt structure like M
D5
G 10
General
OLE objects structure like M
D5, Fp
22
short int
binary int max +/- 32767
FS
44
long int
binary int max +/- 2147483647
FS
88
double
binary signed double IEEE
FS
L1
Logical
M 10
Each DBF record (fixed length): Byte
Size
Description
Applies to
0
1
deleted flag "*" or not deleted " "
All
1…n
1…
x-times contents of fields, fixed length, unterminated. For n, see (2) byte 10…11
All
8.2.2 Pathloss.dbf File Contents The DBF file provides information that is needed to check validity of each path loss matrix.
110
Field
Type
Description
TX_NAME
Text
Name of the transmitter
FILE_NAME
Text
Name (and optionally, path) of .los file
MODEL_NAME
Text
Name of propagation model used to calculate path loss
MODEL_SIG
Text
Signature (identity number) of model used in calculations. You can check it in the propagation model properties (General tab). The Model_SIG is used for the purpose of validity. A unique Model_SIG is assigned to each propagation model. When model parameters are modified, the associated model ID changes. This enables Atoll to detect path loss matrix invalidity. In the same way, two identical propagation models in different projects do not have the same model IDa.
ULXMAP
Float
X-coordinate of the top-left corner of the path loss matrix upper-left pixel
ULYMAP
Float
Y-coordinate of the top-left corner of the path loss matrix upper-left pixel
RESOLUTION
Float
Resolution of path loss matrix in metre
NROWS
Float
Number of rows in path loss matrix
NCOLS
Float
Number of columns in path loss matrix
FREQUENCY
Float
Frequency band
TILT
Float
Transmitter antenna mechanical tilt
AZIMUTH
Float
Transmitter antenna azimuth
TX_HEIGHT
Float
Transmitter height in metre
TX_POSX
Float
X-coordinate of the transmitter
TX_POSY
Float
Y-coordinate of the transmitter
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
AT332_AM_E0
Field
Type
Description
ALTITUDE
Float
Ground height above sea level at the transmitter in metre
RX_HEIGHT
Float
Receiver height in metre
ANTENNA_SI
Float
Logical number referring to antenna pattern. Antennas with the same pattern will have the same number.
MAX_LOS
Float
Maximum path loss stated in 1/16 dB. This information is used, when no calculation radius is set, to check the matrix validity.
CAREA_XMIN
Float
Lowest x-coordinate of centre pixel located on the calculation radiusb
CAREA_XMAX
Float
Highest x-coordinate of centre pixel located on the calculation radius
CAREA_YMIN
Float
Lowest y-coordinate of centre pixel located on the calculation radius
CAREA_YMAX
Float
Highest y-coordinate of centre pixel located on the calculation radius
WAREA_XMIN
Float
Lowest x-coordinate of centre pixel located in the computation zonec
WAREA_XMAX
Float
Highest x-coordinate of centre pixel located in the computation zone
WAREA_YMIN
Float
Lowest y-coordinate of centre pixel located in the computation zone
WAREA_YMAX
Float
Highest y-coordinate of centre pixel located in the computation zone
LOCKED
Boolean
Locking status 0: path loss matrix is not locked 1: path loss matrix is locked.
Boolean
Atoll indicates if losses due to the antenna pattern are taken into account in the path loss matrix. 0: antenna losses not taken into account 1: antenna losses included
INC_ANT
a.
b. c.
In order to benefit from the calculation sharing feature, users must retrieve the propagation models from the same central database. This can be done using the Open from database command for a new document or the Refresh command for an existing one. Otherwise, Atoll generates different model_ID (even if same parameters are applied on the same kind of model) and calculation sharing become unavailable due to inconsistency. These coordinates enable Atoll to determine the area of calculation for each transmitter. These coordinates enable Atoll to determine the rectangle including the computation zone.
8.2.3 LOS File Format The LOS (path loss results) files are binary files with a standard row-column structure. Data are stored starting from the southwest to the northeast corner of the area. The file contains 16-bit signed integer values in the range [-32768; +32767] with a 1/16 dB precision. "No data" values are represented by +32767.
8.3 Path Loss Tuning File Format Atoll can tune path losses calculated by propagation models using CW measurements or drive test Data. Path losses are tuned by merging measurement data with propagation results on pixels corresponding to the measurement points and the pixels in the vicinity. Path losses surrounding the measurement points are smoothed for homogeneity. Measuremment paths that are used for path loss tuning are stored as a catalogue in a folder containing a pathloss.dbf file and one PTS (path loss tuning) file per transmitter. A tuning file can contain several measurement paths. For more information on the path loss tuning algorithm, see the Technical Reference Guide.
8.3.1 Pathloss.dbf File Format See "Pathloss.dbf File Format" on page 108.
8.3.2 Pathloss.dbf File Contents The DBF file provides information about the measured transmitters involved in the tuning. Field
Type
Description
TX_NAME
Text
Name of the transmitter
FILE_NAME
Text
Name (and optionally, path) of .pts file
111
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
© Forsk 2016
Field
Type
Description
AREA_XMIN
Float
Not used
AREA_XMAX
Float
Not used
AREA_YMIN
Float
Not used
AREA_YMAX
Float
Not used
8.3.3 PTS File Format The PTS (path loss tuning) files contain a header and the list of measurement points. Header: • • • • • • • • • • • • •
4 bytes: version 4 bytes: flag (can be used to manage flags like active flag) 50 bytes: GUID 4 bytes: number of points 255 bytes: original measurement name (with prefix "Num" for drive test data and "CW" for CW measurements) 256 bytes: comments 4 bytes: X_RADIUS 4 bytes: Y_RADIUS 4 bytes: gain = measurement gain - losses 4 bytes: global error 4 bytes: rx height 4 bytes: frequency 8 bytes: tx Position
List of measurement points: • • • •
4 bytes: X 4 bytes: Y 4 bytes: measurement value 4 bytes: incidence angle.
8.4 Interference Matrix File Formats Interference matrices are used by GSM, LTE, and WiMAX AFPs (automatic frequency planning tools). Interference matrices can be imported and exported using the following formats: • •
GSM: CLC, IM0, IM1, IM2 LTE and WiMAX: IM2, TXT, CSV
Interference matrix files must contain interference probability values between 0 and 1, and not in precentage (between 0 and 100%). When interference matrix files are imported, Atoll does not check their validity and imports interference probability values for loaded transmitters only. In the following format descriptions and samples, lines starting with the "#" are considered as comments.
In GSM interference matrices: •
• •
112
The interferer TRX type is not specified and is always considered to be BCCH. Subcells have different powers defined as offsets with respect to the BCCH. For subcells other than the BCCH, if the power offset of a subcell is X dB, then its interference histogram will be shifted by X dB with respect to the BCCH interference histogram. If no power offset is defined on the interfered TRX type, it is possible to set "All". For each interfered subcell-interferer subcell pair, Atoll saves probabilities for several C/I values (6 to 24 values), including five fixed ones: –9, 1, 8, 14, and 22 dB. Between two fixed C/I value, there can be up to three additional values (this number depends on the probability variation between the fixed values). The C/I values have 0.5 dB accuracy and probability values are calculated and stored with an accuracy of 0.002 for probabilities between 1 and 0.05, and with an accuracy of 0.0001 for probabilities lower than 0.05.
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
AT332_AM_E0
8.4.1 CLC Format (One Value per Line) The CLC format uses wo ASCII text files: a CLC file and a DCT file. Interference matrices are imported by selecting the CLC file to import. Atoll looks for the associated DCT file in the same directory and uses it to decode transmitter identifiers. If no DCT file is available, Atoll assumes that the transmitter identifiers are the transmitter names, and the columns 1 and 2 of the CLC file must contain the names of the interfered and interfering transmitters instead of their identification numbers.
8.4.1.1 CLC File Format The CLC file consists of two parts. The first part is a header used for format identification. It must start with and contain the following lines: # Calculation Results Data File. # Version 1.1, Tab separated format. Commented lines start with #. The second part details interference histogram of each interfered subcell-interfering subcell pair. The lines after the header are considered as comments if they start with "#". If not, they must have the following format:
The 5 tab-separated columns are defined in the table below: Column
Name
Description
Column1
Interfered transmitter
Identification number of the interfered transmitter. If the column is empty, its value is identical to the one of the line above.
Column2
Interfering transmitter
Identification number of the interferer transmitter. If the column is null, its value is identical to the one of the line above.
Column3
Interfered TRX type
Interfered subcell. If the column is null, its value is identical to the one of the line above. In order to save storage, all subcells with no power offset are not duplicated (e.g. BCCH, TCH).
Column4
C/I threshold
C/I value. This column cannot be null.
Column5
Probability C/I > Threshold
Probability to have C/I the value specified in column 4 (C/I threshold). This field must not be empty.
The columns 1, 2, and 3 must be defined only in the first line of each histogram. Sample # Calculation Results Data File. # Version 1.1, # Remark:
Tab separated format. Commented lines start with #.
C/I results do not incorporate power offset values.
# Fields are: ##------------#------------#------------#-----------#------------------# #| Interfered | Interfering| Interfered | C/I #| Transmitter| Transmitter| Trx type
| Probability
|
| Threshold | C/I >= Threshold |
##------------#------------#------------#-----------#------------------# # # Warning, The parameter settings of this header can be wrong if # the "export" is performed following an "import". They # are correct when the "export" follows a "calculate". # # Service Zone Type is "Best signal level of the highest priority HCS layer". # Margin is 5. # Cell edge coverage probability 75%. # Traffic spreading was Uniform ##---------------------------------------------------------------------# 1
2
TCH_INNER
8 9
1 0.944
113
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
1
© Forsk 2016
BCCH,TCHa
2
a.
10
0.904
11
0.892
14
0.844
15
0.832
16
0.812
17
0.752
22
0.316
25
0.292
8
1
9
0.944
10
.904
13
0.872
14
0.84
17
0.772
If the TCH and BCCH histograms are the same, they are not repeated. A single record indicates that the histograms belong to TCH and BCCH both.
8.4.1.2 DCT File Format The .dct file is divided into two parts. The first part is a header used for format identification. It must start with and contain the following lines: # Calculation Results Dictionary File. # Version 1.1, Tab separated format. Commented lines start with #. The second part provides information about transmitters taken into account in AFP. The lines after the header are considered as comments if they start with "#". If not, they must have the following format:
Column
Name
Type
Description
Column1
Transmitter name
Text
Name of the transmitter
Column2
Transmitter Identifier
Integer
Identification number of the transmitter
Column3
BCCH during calculation
Integer
BCCH used in calculations
Column4
BSIC during calculation
Integer
BSIC used in calculations
Column5
% of vic’ coverage
Float
Percentage of overlap of the victim service area
Column6
% of int’ coverage
Float
Percentage of overlap of the interferer service area
The last four columns describe the interference matrix scope. One transmitter per line is described separated with a tab character. Sample # Calculation Results Dictionary File. # Version 2.1,
Tab separated format. Commented lines start with #.
# Fields are: ##-----------#-----------#-----------#-----------#---------#---------# #|Transmitter|Transmitter|BCCH during|BSIC during|% of vic'|% of int'| #|Name
|Identifier |calculation|calculation|coverage |coverage |
##-----------#-----------#-----------#-----------#---------#---------# # # Warning, The parameter settings of this header can be wrong if # the "export" is performed following an "import". They # are correct when the "export" follows a "calculate".
114
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
AT332_AM_E0
# # Service Zone Type is "Best signal level per HCS layer". # Margin is 5. # Cell edge coverage probability is 75%. # Traffic spreading was Uniform (percentage of interfered area) ##---------------------------# Site0_0
1
-1
-1
100
100
Site0_1
2
-1
-1
100
100
Site0_2
3
-1
-1
100
100
Site1_0
4
-1
-1
100
100
Site1_1
5
-1
-1
100
100
Site1_2
6
-1
-1
100
100
Site2_0
7
-1
-1
100
100
Site2_1
8
-1
-1
100
100
8.4.2 IM0 Format (One Histogram per Line) This file contains one histogram per line for each interfered/interfering subcell pair. The histogram is a list of C/I values with associated probabilities. The .im0 file consists of two parts. The first part is a header used for format identification. It must start with and contain the following lines: # Calculation Results Data File. # Version 1.1, Tab separated format. Commented lines start with #. The second part details interference histogram of each interfered subcell-interferer subcell pair. The lines after the header are considered as comments if they start with "#". If not, they must have the following format:
The 4 tab-separated columns are defined in the table below: Column
Name
Description
Column1
Interfered transmitter
Name of the interfered transmitter.
Column2
Interfering transmitter
Name of the interferer transmitter.
Column3
Interfered TRX type
Interfered subcell. In order to save storage, all subcells with no power offset are not duplicated (e.g. BCCH, TCH).
Column4
C/I probability
C/I value and the probability associated to this value separated by a space character. This entry cannot be null.
Sample # Calculation Results Data File. # Version 1.1, Tab separated format. Commented lines start with #. # Remark:
C/I results do not incorporate power offset values.
# Fields are: #-----------------------------------------------------------------------#Transmitter
Interferer
TRX type
{C/I Probability} values
#-----------------------------------------------------------------------# # Warning, The parameter settings of this header can be wrong if # the "export" is performed following an "import". They # are correct when the "export" follows a "calculate". #
115
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
© Forsk 2016
# Service Zone Type is "Best signal level of the highest priority HCS layer". # Margin is 5. # Cell edge coverage probability 75%. # Traffic spreading was Uniform ##---------------------------------------------------------------------# # Site0_2
Site0_1
BCCH,TCH-10 1 -9 0.996 -6 0.976 -4 0.964 -1 0.936 0 0.932 1 0.924 4 0.896 7 0.864 8 0.848 9 0.832 10 0.824 11 0.804 14 0.712 17 0.66
Site0_2
Site0_3
BCCH,TCH-10 1 -9 0.996 -6 0.976 -4 0.972 -1 0.948 0 0.94 1 0.928 4 0.896 7 0.856 8 0.84 11 0.772 13 0.688 14 0.636 15 0.608 18 0.556
Site0_3
Site0_1
BCCH,TCH-10 1 -9 0.996 -6 0.98 -3 0.948 0 0.932 1 0.924 4 0.892 7 0.852 8 0.832 9 0.816 10 0.784 11 0.764 14 0.644 15 0.616 18 0.564
Site0_3
Site0_2
BCCH,TCH-9 1 -6 0.972 -3 0.964 -2 0.96 0 0.94 1 0.932 4 0.904 7 0.876 8 0.86 9 0.844 11 0.804 13 0.744 14 0.716 15 0.692 18 0.644
8.4.3 IM1 Format (One Value per Line, TX Name Repeated) This file contains one C/I threshold and probability pair value per line for each interfered/interfering subcell pair. The histogram is a list of C/I values with associated probabilities. The .im1 file consists of two parts. The first part is a header used for format identification. It must start with and contain the following lines: # Calculation Results Data File. # Version 1.1, Tab separated format. Commented lines start with #. The second part details interference histogram of each interfered subcell-interferer subcell pair. The lines after the header are considered as comments if they start with "#". If not, they must have the following format:
The 5 tab-separated columns are defined in the table below: Column
Name
Description
Column1
Interfered transmitter
Name of the interfered transmitter.
Column2
Interfering transmitter
Name of the interferer transmitter.
Column3
Interfered TRX type
Interfered subcell. In order to save storage, all subcells with no power offset are not duplicated (e.g. BCCH, TCH).
Column4
C/I threshold
C/I value. This column cannot be null.
Probability C/I > Threshold
Probability to have C/I the value specified in column 4 (C/I threshold). This field must not be empty.
Column5 Sample
# Calculation Results Data File. # Version 1.1, Tab separated format. Commented lines start with #. # Remark:
C/I results do not incorporate power offset values.
# Fields are: #-----------------------------------------------------------------------#Transmitter
Interferer
TRX type
C/I
Probability
#------------------------------------------------------------------------
116
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
AT332_AM_E0
# # Warning, The parameter settings of this header can be wrong if # the "export" is performed following an "import". They # are correct when the "export" follows a "calculate". # # Service Zone Type is "Best signal level of the highest priority HCS layer". # Margin is 5. # Cell edge coverage probability 75%. # Traffic spreading was Uniform ##---------------------------------------------------------------------# Site0_2
Site0_1
BCCH,TCH
-10
1
Site0_2
Site0_1
BCCH,TCH
-9
0.996
Site0_2
Site0_1
BCCH,TCH
-6
0.976
Site0_2
Site0_1
BCCH,TCH
-4
0.964
Site0_2
Site0_1
BCCH,TCH
-1
0.936
Site0_2
Site0_1
BCCH,TCH
0
0.932
Site0_2
Site0_1
BCCH,TCH
1
0.924
Site0_2
Site0_1
BCCH,TCH
4
0.896
Site0_2
Site0_1
BCCH,TCH
7
0.864
Site0_2
Site0_1
BCCH,TCH
8
0.848
Site0_2
Site0_1
BCCH,TCH
9
0.832
Site0_2
Site0_1
BCCH,TCH
10
0.824
...
8.4.4 IM2 Format (Co- and Adjacent-channel Probabilities) IM2 files contain co-channel and adjacent-channel interference probabilities for each interfered transmitter – interfering transmitter pair. In GSM, there is only one set of values for all the subcells of the interfered transmitter. Each line must have the following format:
Where the separator () can either be a tab or a semicolon. The four columns are defined in the table below: Column
Name
Description
Column1
Interfered transmitter
Name of the interfered transmitter
Column2
Interfering transmitter
Name of the interferer transmitter
Column3
Co-channel probability
Co-channel interference probability
Column4
Adjacent-channel probability
Adjacent channel interference probability
Sample # Calculation Results Data File. # Version 1.1, Tab separated format. Commented lines start with #. # Remark:
C/I results do not incorporate power offset values.
# Fields are: #-----------------------------------------------------------------------#Transmitter
Interferer
Co-channel
Adjacent channel
#-----------------------------------------------------------------------# # Warning, The parameter settings of this header can be wrong if
117
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
© Forsk 2016
# the "export" is performed following an "import". They # are correct when the "export" follows a "calculate". # # Service Zone Type is "Best signal level of the highest priority HCS layer". # Margin is 5. # Cell edge coverage probability 75%. # Traffic spreading was Uniform ##---------------------------------------------------------------------# Site0_2
Site0_1
0.226667
0.024
Site0_2
Site0_3
0.27
0.024
Site0_3
Site0_1
0.276
0.02
Site0_3
Site0_2
0.226
0.028
The columns in the sample above are separated with a tab. These columns can also be separated with a semilcolon: Site0_2;Site0_1;0.226667;0.024 Site0_2;Site0_3;0.27;0.024 Site0_3;Site0_1;0.276;0.02 Site0_3;Site0_2;0.226;0.028
8.4.5 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 as the clutter or traffic file. It has the same structure as the menu file used in the Planet format. Field
Type
Description
Class code
Integer (>0)
Identification code for the clutter (or traffic) class
Class name
Text (50)
Name of the clutter (or traffic) class. It can 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
none
1
open
2
sea
3
inland_water
4
residential
5
meanurban
8.5 "Per Transmitter" Prediction File Format When a coverage prediction is calculated by value intervals it is stored externally, i.e., outside the ATL file. A corresponding ’\{}’ folder is actually created where the ATL document is located, as soon as the latter is saved. The calculation of the coverage prediction is either global or "per transmitter". •
When the calculation is global, the results are stored in two files for the entire prediction: one HDR file and one BIL file (both identified by the prediction name).
•
When a calculation is "per transmitter", one HDR file and one BIL file are created for each transmitter in the prediction (both identified by the transmitter’s name). In some "per transmitter" predictions, an additional DBF file is created for the entire prediction (identified by the prediction name). The DBF file contains information on each transmitter and a pointer to each transmitter’s specific HDR and BIL files.
118
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
AT332_AM_E0
In LTE, when a Cell Identifier Collision Zones (DL) prediction is calculated by value intervals with the display type set "No. of interferers per cell", the HDR file and the BIL file are created for each cell in the prediction (both identified by the cell’s name). The format and the content of the DBF file is described here. In both cases, an XML file describing the prediction is also created in the corresponding ’\{}’ folder.
8.5.1 .dbf File Format The format of ‘.dbf’ files is identical to the format described in "Pathloss.dbf File Format" on page 108.
8.5.2 .dbf File Contents The ‘.dbf’ files generated in specific ’{}’ folders provide information that is needed to check the validity of each "per transmitter" prediction> calculated by value intervals. Field
Type
Description
TX_NAME
Text
Name of the transmitter
FILE_NAME
Text
Name of the transmitter’s BIL result file
RESOLUTION
Float
Resolution of the calculation, same as ’xdim’ and ’ydim’ in the HDR file
AREA_XMIN
Float
Same as ’ulxmap’ in the HDR file
AREA_XMAX
Float
Same as ’ulxmap’ + ’xdim’ * ’ncols’ in the HDR file
AREA_YMIN
Float
Same as ’ulymap’ in the HDR file
AREA_YMAX
Float
Same as ’ulymap’ + ’ydim’ * ’nrows’ in the HDR file
NBITS
Float
Same as ’nbits’ in the HDR file
NBANDS
Float
Same as ’nbands’ in the HDR file
BYTE_ORDER
Float
Same as ’byteorder’ in the HDR file
BAND_ROW_BYTES
Float
Same as ’bandrowbytes’ in the HDR file
TOTAL_ROW_BYTES
Float
Same as ’totalrowbytes’ in the HDR file
SKIP_BYTES
Float
Same as ’skipbytes’ in the HDR file
DATA_TYPE
Text
NO_DATA_VALUE
Same as ’datatype’ in the HDR file Same as ’nodatavalue’ in the HDR file
119
Atoll 3.3.2 Administrator Manual Chapter 8: Atoll File Formats
120
© Forsk 2016
Chapter 9 Administration and Usage Recommendations
This chapter covers the following topics: •
"Geographic Data" on page 123
•
"Path Loss Matrices" on page 124
•
"Atoll Documents" on page 125
•
"Databases" on page 125
•
"Calculation Server" on page 126
•
"Atoll Administration Files" on page 126
•
"Process Memory" on page 127
•
"Printing" on page 127
•
"Coverage Prediction Calculations" on page 128
•
"CW Measurements and Drive Test Data" on page 128
•
"Antenna Patterns and Import" on page 128
•
"Traffic Maps" on page 128
•
"Atoll API" on page 129
•
"Performance and Memory" on page 129
Atoll 3.3.2 Administrator Manual © Forsk 2016
122
Atoll 3.3.2 Administrator Manual Chapter 9: Administration and Usage Recommendations
AT332_AM_E0
9 Administration and Usage Recommendations This chapter lists various technical recommendations for optimising your work with Atoll.
9.1 Geographic Data Location of the Geographic Data • • •
In multi-user environments, it is recommended to place all the geographic data on a file server accessible to all the users. This approach avoids the need to replicate the geographic data on all the workstations. Geographic data should either be located on each server or accessible through a fast network connection, e.g., 1 Gbps. You can restrict access to the geographic data locations by assigning read/write access rights to administrators and read-only rights to end-users.
Link or Embed • •
Only embed geographic data in ATL files if you wish to make a portable document. In all other cases, it is recommended to link geographic data files to the Atoll documents. It is recommended to set the paths to linked geographic data files using the Universal Naming Convention (UNC). Following the UNC, an absolute path, such as "C:\Program Files\Forsk\Geo Data\...", is represented as "\\Computer\C\Program Files\Forsk\Geo Data\...", where "Computer" is the computer name, and "C" is the share name of disk C. Example: Absolute Path
C:\Program Files\Forsk\Geo Data\...
Relative Path
\Program Files\Forsk\Geo Data\...
UNC Path
\\Computer\C\Program Files\Forsk\Geo Data\...
If you define paths to geographic data files using the UNC, Atoll will be able to keep track of the linked files even if the Atoll document is moved to another computer. Size of Tiles •
•
Some network planning tools require geographic data to be available in small tiles in order to work more efficiently. For a country-wide project, this can lead to hundreds of files describing the geographic data. Atoll is designed to optimise memory consumption, which enables it to perform efficiently with regional tiles (1 tile/file per region). In Atoll, Merging small tiles to build a regional tile can improve performance greatly. To note as well: • • •
Recommended file size: 100 to 200 MB Erdas Imagine Pyramids files can be bigger. ECW files can be of any size (no limitations).
Recommended Formats •
In order to improve performance, it is recommended to use uncompressed DTM and clutter files, for example, BIL files. Using compressed geographic data files, for example, compressed TIF or Erdas Imagine, can cause performance reduction due to decompression of these files in real time. If you are using compressed geographic data files, it is strongly recommended to: • •
•
Either, hide the status bar that displays geographic data information in real time. You can hide the status bar from the View menu. Or, disable the display of some of the information contained in the status bar, such as altitude, clutter class, and clutter height using an option in the Atoll.ini file, see "Hiding Information Displayed in the Status Bar" on page 186.
The following table shows the recommended file formats for different geographic data: Geographic data type
Recommended file format
Scanned maps
ECW
Vectors
SHP
123
Atoll 3.3.2 Administrator Manual Chapter 9: Administration and Usage Recommendations
© Forsk 2016
9.2 Path Loss Matrices Shared Path Loss Matrices •
•
Shared path loss matrices should be accessible through a fast network connection, e.g., 1 Gbps. These results are accessed by Atoll during calculations, and should be available to the users through a fast network connection, i.e., 30 Mbps at least per user. You can restrict access to the shared path loss matrices folder by assigning read/write access rights to administrators and read-only rights to end-users.
Private Path Loss Matrices •
Atoll synchronises the private path loss matrices with the shared path loss matrices. If private path loss matrices are invalid, and the corresponding shared path loss matrices are valid, Atoll deletes the invalid private path loss matrices and uses the shared ones. You can make Atoll verify and remove private path loss matrices, valid or invalid, whose corresponding shared path loss matrices are valid. This can be useful for disk space management. For more information, see "Synchronising Private and Shared Path Loss Matrices" on page 178.
Link or Embed •
Only embed path loss matrices in ATL files if you wish to make a portable document. In all other cases, it is recommended to link path loss matrices to the Atoll documents. Externalising path loss matrices to shared or private path loss folders will keep the ATL file size reasonable, which will result in less fragmentation. Externalising path loss matrices does not reduce the performance of display and calculations in Atoll.
•
It is recommended to set the paths to the private and shared path loss matrices folders using the Universal Naming Convention (UNC). Following the UNC, an absolute path, such as "C:\Program Files\Forsk\PathLosses\...", is represented as "\\Computer\C\Program Files\Forsk\PathLosses\...", where "Computer" is the computer name, and "C" is the share name of disk C. Example: Absolute Path
C:\Program Files\Forsk\PathLosses\...
Relative Path
\Program Files\Forsk\PathLosses\...
UNC Path
\\Computer\C\Program Files\Forsk\PathLosses\...
If you define paths to the private and shared path loss matrices folders using the UNC, Atoll will be able to keep track of the linked files even if the Atoll document is moved to another computer. Calculating Path Loss Matrices in Multi-RAT Documents •
When the path loss matrices in multi-RAT documents using the RunPathloss API function, the path loss matrices of each technology are calculated simultaneously using the same number of threads. For example, if 4 threads are used to calculate path loss matrices, and there are 3 technologies (GSM, UMTS, and LTE), a total of 12 threads will be used to calculate the path loss matrices at the same time. This can lead to the following problems: • • •
•
Insufficient CPU resources Insufficient memory Insufficient licenses if external propagation models are used.
To avoid these problems when using the RunPathloss API function to calculate path loss matrices in multi-RAT documents, use the following work-arounds: • • •
Use the Distributed Calculation Server, even locally. In your script or macro, deactivate the transmitters of the technologies for which you do not want to calculate the path loss matrices and reactivate them afterwards. Repeat it for all technologies. Lower the number of threads using the NumberOfThreadsPathloss option in RemoteCalculation section in Atoll.ini. For example, you can set the option to 2 to use a maximum of 6 threads (3*2) during path loss calculation using the RunPathloss function. •
124
Resource saturation during the calculation of path loss matrices for multi-RAT documents only occurs when using the RunPathloss API function in a macro or script. When calculating path loss matrices for a multi-RAT document using Atoll, this does not occur.
Atoll 3.3.2 Administrator Manual Chapter 9: Administration and Usage Recommendations
AT332_AM_E0
•
Atoll synchronises the private path loss matrices with the shared path loss matrices. If private path loss matrices are invalid, and the corresponding shared path loss matrices are valid, Atoll deletes the invalid private path loss matrices and uses the shared ones. You can make Atoll verify and remove private path loss matrices, valid or invalid, whose corresponding shared path loss matrices are valid. This can be useful for disk space management. For more information, see "Synchronising Private and Shared Path Loss Matrices" on page 178.
9.3 Atoll Documents General • •
It is recommended to define a rule for making backups of your Atoll documents at regular intervals. Do not skip a major Atoll version. For example, if you are currently using Atoll 2.8.x, you should first upgrade the document to Atoll 3.1.x before upgrading to Atoll 3.2.x. Upgrading your document will be simpler if you do not skip a major version. If you skip or have skipped an intermediate major version, you should upgrade your document twice in order to make it compatible with the new version.
9.4 Databases General • • • •
In order to use Atoll with Oracle, you must create Oracle users and schema with names in uppercase. Create backups of the database before upgrading. It is recommended to define a rule for making backups of the database at regular intervals. Do not skip a major Atoll version. For example, if you are currently using Atoll 2.7.x, you should first upgrade the database to Atoll 2.8.x before upgrading to Atoll 3.1.x. Upgrading your database will be simpler if you do not skip a major version. If you skip or have skipped an intermediate major version, you must upgrade your database twice in order to make it compatible with the new version.
Tables and Fields • •
Table and field names are case sensitive. Table and field names should be not more than 20 characters long. Oracle databases allow a maximum length of 30 characters for field and table names. However, for use in Atoll, you must not create tables and fields with names longer than 20 characters. This is because Atoll adds some characters to the table and field names for certain operations: creating associated triggers, creating project databases, etc. Limiting the length of table and field names to 20 characters will help avoid database connection and consistency problems.
• • • • • •
• •
Table and field names should only use alphanumeric characters (A-Z, a-z, 0-9) and underscores (_). Table and field names must not start with a numeric character (0-9). Table and field names must not contain an SQL or RDBMS-specific keyword, such as ORDER, DATE, etc. Table and field names must not contain spaces or special characters, such as periods (.), exclamation marks (!), colons (:), semi-colons (;), interrogation marks (?), parentheses (()), brackets ({}), square brackets ([]), etc. Boolean fields, system or user-defined, should always have default values assigned. The CustomFields table enables you to define default values, choice lists, and read/write access for any field in any table in Atoll, including user-defined fields that you add to the Atoll tables. The values defined in this table have priority over the internal predefined default values. If you define floating point default values, make sure that all the users have the same decimal separator. If you wish to add custom fields in the Atoll document, you should first add the field in the database, and then update your Atoll document from the database. When setting up your database for the first time, try to anticipate user requirements in terms of custom fields in Atoll tables. Some requirements of the different user groups can be satisfied if a few general-purpose user-defined fields are added in Atoll tables when setting up the database. For example, if you add three user-defined fields (one of type integer, float, and text (limited size)) to the Sites and Transmitters tables, users will be able to use these for sorting, filtering, grouping, or other purposes. This approach can help the database function a long time before users require the addition of other custom fields.
• •
•
To improve performance, if your projects allow it, reduce the size of the fields corresponding to the sites and transmitters’ names. To improve performance, unless absolutely necessary, do not add user-defined fields of Text type. Rather, use numeric field types, which allow sorting and other functions. If you must add Text fields, allocate them the appropriate size that would suffice. For example, a 255-character long Text type field would, for the most part, occupy disk space for no purpose. To improve performance, you should avoid adding custom fields to the neighbour management tables.
125
Atoll 3.3.2 Administrator Manual Chapter 9: Administration and Usage Recommendations
© Forsk 2016
9.5 Calculation Server Computation Server Stability and Resource Management In certain conditions, as described below, Atoll users might experience a decrease in server performance and stability in a multi-user Citrix environment. The principal difference observed might be the inability to run multiple Atoll sessions on the server without getting error messages, general application failures, or server crashes. Such problems can occur when the number of Atoll sessions on the server, carrying out calculations, increases to more than four. Causes of Instability and Loss of Performance This general instability and low performance of the servers is due to: • • •
Insufficient memory resources: globally and per process (Atoll session) Insufficient CPU resources Network congestion
Atoll can process four simultaneous path loss matrices calculations, which means high CPU and RAM resource consumption, and as path loss calculations share the amount of memory allocated to the Atoll session, the total memory requirement can exceed the Microsoft Windows’ (32-bit editions) limit of 2 GB per process. This is especially the case with large Atoll documents and propagation models that require considerable memory. Troubleshooting and Solution As the cause of this problem is resource saturation on the server, resource consumption should be controlled in order to avoid memory and CPU overloading as follows: •
To reduce the impact of a large number of simultaneous path loss calculations, a Distributed Calculation Server should be set up. Using the Distributed Calculation Server, path loss calculations can be performed outside Atoll. Using the Distribution Calculation Server has the following advantages: • Path loss calculations are limited to four parallel instances regardless of the number of Atoll sessions running on the server. This notably improves the memory and CPU consumption. • A queuing system, integrated in the Distributed Calculation Server, manages the calculation requests from different Atoll sessions. • A failover mechanism automatically switches and hands over the path loss calculations back to Atoll in case a problem occurs. • Path loss calculations are carried out by a separate process (AtollSvr), which has its own memory allocation apart from Atoll, i.e., the amount of memory needed for calculations does not impacts the Atoll memory allocation.
This set up can introduce considerable improvements in both the number of Atoll sessions per server and the calculations. A server with four processors (eight threads with hyper-threading) can accommodate four simultaneous path loss calculations and use the other four threads for Atoll sessions. Atoll’s interface will also be more efficient and the overall processing time for various tasks will be improved. In order to prevent users from deactivating the use of the Distributed Calculation Server, and hence bypassing the resource control procedure established above, the Atoll.ini file should be set made read-only for end-users. Apart from the above setup, you can also make some other system improvements: •
To avoid error messages caused by requesting a large number of files over the network, the following Microsoft Windows registry parameter can be modified in order to dedicate more resources to network read/write operations: IRQSTACKSIZE should be set to 30 instead of 11, for example.
•
•
To avoid ‘out of memory’ problems, the Pagefile size should be increased so that the server does not run out of global memory when supporting more than 10 Atoll sessions simultaneously. This is different from the 2 GB per process limit. Virtual memory can be increased from 8 GB to 16 GB, for example. For 32-bit Windows operating systems, you can also increase the default Windows memory allocation limit from 2 GB to 3 GB as explained in "Process Memory" on page 127.
9.6 Atoll Administration Files There is no specific order in which configuration and initialisation files should be created or installed on Atoll workstations and servers. It is sufficient to have these files created and placed in the right locations before running Atoll to have the predefined configuration of all workstations and servers. If you have already configured these files for one server, and you are setting up another server, you can copy these files to their respective locations on the new server to have the exact configuration and set-up as the first. If you do not copy these
126
Atoll 3.3.2 Administrator Manual Chapter 9: Administration and Usage Recommendations
AT332_AM_E0
files, or create them, you will not have the same configuration of the new server, but apart from that you will be able to work with Atoll normally. These files are optional, not obligatory. Initialisation File (INI) • •
It is highly recommended that the Atoll initialisation file be created and modified only by the administrator. If you are using Windows 2000 Server, state the actual number of processors in the INI file.
User Configuration File (CFG) • • •
Use Atoll to create these files and avoid modifying these files manually as human errors can create problems. Uncheck image visibility to avoid loading unnecessary data in the memory. You can set up your configuration files in the following manner: • •
•
A common configuration file that points to the geographic data, macros, and other common parameters in your Atoll documents. Separate configuration files created for your 2G and 3G projects, which would store their respective coverage prediction studies parameters, traffic information, neighbour allocation parameters, and other technologyspecific parameters. Separate configuration files based on, and for, different groups of users. These groups of users can be, for example, groups of users working on different regions, groups of users working on different technologies, groups of users focusing on certain operations (i.e., performing certain types of coverage predictions, performing the AFP, etc.).
Custom Predictions File •
Coverage prediction studies can easily be duplicated within Atoll. Before creating study templates, and the XML studies file, make sure that this study template is aimed at serving a number of users. This means, avoid creating study templates unless these will be needed for a long time by a number of users. You can use the configuration files to store your created coverage prediction studies locally. And, you can also use the study duplicate feature to create copies of existing coverage prediction studies.
9.7 Process Memory 32-bit Operating Systems Atoll can support 3 GB address space on a properly configured 32-bit system. For more information, please refer to the following URL: http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx (/3GB section in “Memory Support and Windows Operating Systems”). The following link provides information on how you can setup your Windows Server 2003 systems to activate the 3 GB switch at startup: http://technet.microsoft.com/en-us/library/bb124810.aspx. 64-Bit Operating Systems The 64-bit editions of Microsoft Windows provide 4 GB of memory per process.
9.8 Printing You should place different layers of geographic and radio data in a definite order when printing a project or a section of the project. The following order should be followed: 1. Visible objects of the Data tab All the visible objects of the Data tab are displayed above those in the Geo tab. However, it is strongly recommended to place vector layers on the top of coverage prediction plots. You can do this by transferring these vector layers to the Data tab using the context menu. For performance reasons, it is advised to place vector layers on top of raster layers before printing a project. Sites and Transmitters must be on the very top, above all other layers. You should place sites and sectors on the top, then vector layers, and then raster layers. 2. Unidimensional vectors (points) 3. Open polygonal vectors (lines, i.e., roads and other linear items, etc.) 4. Closed polygonal vectors (surfaces, i.e., zones and areas, etc.) 5. Multi-format maps (vector or raster maps, i.e., population, rain, generic maps, traffic, etc.) 6. Transparent raster maps (clutter class maps, etc.) 7. Non-transparent maps (images, DTM, clutter height maps, etc.)
127
Atoll 3.3.2 Administrator Manual Chapter 9: Administration and Usage Recommendations
© Forsk 2016
9.9 Coverage Prediction Calculations •
•
If you do not want Atoll to calculate the shadowing margin during a coverage prediction, it is advised to clear the Shadowing taken into account check box. This approach is more efficient in terms of performance than selecting this option and setting the Cell edge coverage probability to 50%. To improve memory consumption and optimise the calculation times, you should set the display resolutions of coverage predictions according to the precision required. The following table lists the levels of precision that are usually sufficient: Size of the coverage prediction
Display resolution
City Center
5m
City
20 m
County
50 m
State
100 m
Country
According to the size
9.10 CW Measurements and Drive Test Data •
•
It is recommended to use Fast Display in order to increase display speed. This option is available in the Display tab of the Properties dialogues for CW Measurements and Drive Test Data folders. Although this approach only displays measurement points as small squares, it can have a significant impact on performance depending on the number of measurement points in the Atoll document. When performing a CW measurements drive test campaign, please follow the recommended procedure described in the Measurements and Model Calibration Guide.
9.11 Antenna Patterns and Import •
•
•
Antenna names used in some tools, such as NetAct, can be different from those used in their corresponding antenna files. To solve this issue, you can create a new file, named "Index", containing the list of antenna names, which would in fact be the pattern (antenna file) names. You should place this file at the same location as the antenna patterns (files). This will replace the antenna names with the new antenna names. Some Kathrein antenna pattern files might have names different from the antenna pattern names present inside the file. You will have to replace the name of the pattern inside the file by the name of the pattern file itself, in order to import these antennas correctly. A Planet Index file contains the path to and the name of each antenna file available. Creating such an Index file when there are hundreds of antenna patterns available can be a difficult task. You can easily create the index file from the Microsoft Windows command prompt. You can open the Command Prompt window by selecting Start > Run, entering "cmd" and pressing ENTER. In the Command Prompt window, navigate to the directory containing the antenna pattern files, enter the following command and press ENTER: dir /b > Index This will create a file called "Index" in the same directory as the antenna patter files containing a list of all the antenna pattern file names, with one name per line. The file will also contain a line with its own name, so, before importing this file into Atoll, you should use a text editor to remove the line containing the file name "Index."
•
The electrical tilt, which can be defined in the antenna properties dialogues in Atoll, is an additional electrical downtilt. It might be redundant to define an additional electrical downtilt for antennas whose patterns already include electrical tilt. Users should verify whether the antenna patterns of the antennas in their projects, do not already include the effect of an electrical tilt.
9.12 Traffic Maps • • •
128
User profile environment-based traffic maps should only be used for a precision on traffic that is of the same level as the statistical clutter available in a project. For higher precision on traffic data, you should use sector traffic maps or user density traffic maps. User density traffic maps provide you with a means to define a density for each set of service, terminal type, and mobility type. Sector traffic maps are best suited for traffic data issued by the OMC.
Atoll 3.3.2 Administrator Manual Chapter 9: Administration and Usage Recommendations
AT332_AM_E0
9.13 Atoll API Correct functioning of Atoll when using Atoll through the API is guaranteed during interactive user sessions only. Atoll is an application that requires creating tool bars, creating menus, reading user profile options from the Windows’ registry, accessing printers, etc., even when it is accessed through the API. The same is true for add-ins working with Atoll. Even though it is possible to load and use Atoll when there is no user session open on a computer, its correct functioning is not guaranteed. Unexpected errors can occur. Particularly, creating objects through CreateObject or CoCreateInstance might fail. Therefore, the correct functioning of Atoll requires an open user session on the computer.
9.14 Performance and Memory Memory Refresh •
You can avoid memory fragmentation while working with Atoll documents by saving the Atoll document from time to time, closing and restarting Atoll, and reopening the document. This advice is applicable to any application running under Microsoft Windows because many common DLL files are accessed by applications, and unloading and reloading these DLL files refreshes the memory allocation.
• •
If you are working in a Citrix XenApp environment, you should restart your Citrix server every week or fortnight. The exact time should be determined by the administrator depending on the state of the network (LAN). In certain cases, it might be more appropriate to start working on a completely fresh ATL file. If you have been working on your existing ATL file for a long time, it might become unnecessarily large and might contain some useless remains from your earlier operations, e.g., traces of records that no longer exist in the database, etc. You can completely refresh your project by following these steps: a. Open the existing ATL file in Atoll that you want to replace. b. Create a CFG file from your existing ATL file with all the required information, e.g., geographic data set, coverage prediction parameters, neighbour allocation parameters, etc. For more information, refer to "Configuration Files" on page 135. c. Close the old ATL file. d. Create a new ATL from the database to create a fresh ATL file. e. Import the CFG file in the new ATL file. You now have a clean ATL file to work with, which has all the same information as the old ATL file, and takes up less space on the hard disk, has less fragmented data, and improved performance.
Memory Allocation •
•
If you have to open several large ATL files simultaneously on the same computer, it is better to open each in a separate Atoll session rather than to open them all in the same Atoll window. Each Atoll session on the same computer has its own memory space allocated by the operating system. Each computer consumes a single license token independent of the number of Atoll sessions opened simultaneously. For 32-bit Windows operating systems, you can also increase the default Windows memory allocation limit from 2 GB to 3 GB as explained in "Process Memory" on page 127.
File Size •
Coverage predictions calculated over large areas require more memory. If you are working on an Atoll document covering a large area, with coverage predictions calculated over the entire network, this document will require more memory for loading all the coverage predictions. You can reduce memory consumption by making copies of your Atoll document, and keeping a few coverage predictions in each copy. These ATL files will be faster to load and work with compared to a single ATL file with all the coverage predictions. Large coverage predictions can take up a considerable amount of memory even if they are not displayed on the map.
•
Externalise DTM, clutter, path loss matrices, and any other data that can be externalised, so that the ATL file size does not become unnecessarily large.
Path Loss Calculation •
Before starting path loss calculation, verify that the calculation radii and resolutions assigned to the different types of transmitters are consistent. For example, calculating path loss matrices of picocells over large calculation radii would only waste memory and disk space.
129
Atoll 3.3.2 Administrator Manual Chapter 9: Administration and Usage Recommendations
•
© Forsk 2016
For calculating path loss matrices over large areas, you should use the dual resolution feature in Atoll. Define short calculation radii and fine resolutions for the main path loss matrices, and large calculation radii and low resolutions for extended path loss matrices. This approach decreases the calculation time significantly compared to calculating just one matrix per transmitter using a fine resolution. The main path loss matrices should be calculated using the same resolution as the resolution of the geographic data available. The extended path loss matrices can be calculated using a lower resolution, e.g., twice the resolution of the geographic data.
Regionalisation •
Use database regionalisation or site lists if you are working on smaller parts of a large network. Atoll loads only the data necessary for your working area. If you load a large network, Atoll will load a lot of data that might not be necessary all the time, such as the neighbour relation data.
Performance and Memory Issues in Large GSM Projects Memory problems might be experienced in the C/I coverage prediction studies, interference matrices calculations, and the AFP while working on large GSM networks. Large network projects are more susceptible to these problems. If the network is large but homogeneous, these problems might only appear if the number of transmitters is over 15,000 or so. But, if there are large city centres involved, with each pixel having many overlapping path loss matrices, then this size limit might decrease to around 5,000 transmitters or so. Also, if the Atoll session has been open for a long time, memory problems can even appear while working on smaller networks. This is because the process memory space (memory space allocated to Atoll by the operating system) becomes fragmented. Following is a list of advice which you can follow in order to avoid such problems: •
•
•
•
Use regionalisation or site lists: If you load a large network, Atoll will be required to load a lot of data that might not be necessary all of the time. For example, in a typical large GSM network, you might have around 10,000 transmitter records, 20,000 subcell records, 50,000 TRX records, and up to 150,000 neighbour records. Externalise embedded interference matrices: You can store interference matrices listed in the Interference Matrices folder in external files. Atoll loads interference matrices from the external files to the memory only when needed. You will also reduce the ATL file size by externalising the interference matrices. Adapt calculation radii to the cell type and the EIRP: Before calculating path loss matrices, take care to correctly associate calculation radii and resolutions to different types of cells. If you calculate path loss matrices for all types of cells over a large calculation radius, it will unnecessarily burden the C/I and interference matrices computations. Properly configure the interference thresholds: These thresholds indicate the level after which an interferer can be ignored. The default value for this threshold (-130 dBm), defined in the Predictions tab of the Predictions folder’s Properties dialogue, means that the computations will take into account all the interferers. However, if you set it too high, you might lose important interference information. The proper value for this threshold depends on the Reception Thresholds and the C/I Thresholds defined in the Subcells table. The optimum value would be Min AllSubcells RT i – CIT i – M . Which means the minimum value of the factor RT i – CIT i – M computed for all subcells, i. Where, RTi is the reception threshold of the subcell i, CITi the C/I threshold of this subcell, and M is a safety margin. Since this interference threshold is used both in interference matrices calculation and in interference predictions, it is important to have at least a 3-dB margin for the interference energy aggregation in C/I studies. We recommend a safety margin of 5 dB, which can be reduced if any problem is encountered.
•
•
•
Do not define very high C/I quality thresholds (Default values: 12 dB for BCCH and 9 dB for TCH). If you want a certain TRX type to carry GPRS/EDGE traffic, you can add 1 or 2 dB to this value for that TRX type, and use the option of safety margin in the AFP module’s Cost tab. The 12 dB and 9 dB default values already include safety margins. If you increment these values too much, it will unnecessarily load the interference matrix generation and the AFP. Do not start an AFP session if the interference matrices report indicates problems: All the transmitters should have interferers and very few of them (not more than 20%) should have more than 70 interferers. If there are too many or too few entries in your interference matrices, the AFP plan will not be optimal. If the memory-critical task is interference matrices generation: You can generate interference matrices in a piecewise manner. This means that you can generate nation-wide interference matrices with low resolutions based on the percentage of interfered area (to improve computation time), with a cell edge coverage probability of 50% (which means no access to clutter for reading standard deviation values), and an interference threshold of -112 dBm. This will provide rough global interference matrices which can be locally improved. These interference matrices will be less memoryconsuming. Then, use polygon or site list filters to focus on each important location, and calculate local interference matrices with higher resolutions and reliabilities. Make sure that the computation zone in your project completely encompasses the filtering zones that you define.
•
130
If the memory-critical task is the AFP session: Try to make the document lighter, e.g., remove coverage prediction studies, exit and restart Atoll, and try to generate interference matrices with fewer entries.
Atoll 3.3.2 Administrator Manual Chapter 9: Administration and Usage Recommendations
AT332_AM_E0
•
If the memory-critical task is the traffic capture: You can use traffic load field of the Subcells table to provide traffic loads directly to the AFP, and possibly skip this step.
Performance and Memory Issues in UMTS/CDMA Simulations •
In order to optimise memory usage during simulations, you can set the "Information to retain" option to "Only the Average Simulation and Statistics". With this option Atoll uses much less memory because it only keeps limited information in memory during the simulation process. Simulation results are detailed enough to be used in generating coverage prediction studies.
Performance and Memory Issues in Co-planning Projects Co-planning with Atoll requires that both technology documents be open in the same Atoll window at the same time. However, loading, for example, a GSM and a UMTS document can cause memory saturation especially if the documents contain large, country-wide networks. To decrease the amount of memory used by Atoll in such cases, you can: • •
Load vector layers in main document only. Loading vectors in the linked document is not necessary and only consumes more memory. Avoid loading neighbours and custom fields which are not required. This can be performed by creating views in the database. For more information, see "Appendix 2: Setting Up Databases for Co-planning" on page 73.
131
Atoll 3.3.2 Administrator Manual Chapter 9: Administration and Usage Recommendations
132
© Forsk 2016
Chapter 10 Configuration Files This chapter covers the following topics: •
"Contents of User Configuration Files" on page 136
•
"Contents of Additional Configuration Files" on page 159
•
"Content of the Custom Predictions File" on page 164
•
"Content of the "Value Intervals" Predictions Files" on page 164
Atoll 3.3.2 Administrator Manual © Forsk 2016
134
Atoll 3.3.2 Administrator Manual Chapter 10: Configuration Files
AT332_AM_E0
10 Configuration Files Configuration files can be used to store parameter and display settings. These files are optional, not required for working with Atoll, but are useful means for making work easier. This chapter describes the formats of these files in detail: •
User configuration files (UTF-8 encoded XML-format GEO or CFG files) A user configuration file containing only the geographic data settings can be saved with a GEO extension. A user configuration file containing the geographic data settings and other parameter settings can be saved with a CFG extension. User configuration files must be created using Atoll to ensure correct syntax and structure. It is possible to edit the contents of these files in an XML editor and make changes if required (for example, to update the paths to geographic data files). For more information on how to create and load user configuration files in Atoll, see the User Manual. These files can store: • • • • • • • • • • • •
Geographic data settings Filtering, focus, computation, printing, and geographic export zones Map centre and zoom level Folder configurations List of coverage predictions in the Predictions folder and their settings Automatic neighbour allocation parameters Automatic frequency planning parameters (GSM GPRS EDGE documents) Automatic scrambling code allocation parameters (UMTS HSPA and TD-SCDMA documents) Automatic PN offset allocation parameters (CDMA2000 documents) Automatic OFDM resource allocation parameters (LTE, WiMAX, Wi-Fi) Microwave link parameters Full paths to macro files • •
Projection and display coordinate systems are stored in the database, not in user configuration files. Simulation settings are not stored in user configuration files.
For more information on the contents of user configuration files, see "Contents of User Configuration Files" on page 136. A user configuration file can be automatically loaded when Atoll is run if: a. The file is identified in the command line parameter -Cfg "cfgfilename" (see "Atoll Command Line Parameters" on page 31 for more information), or b. The file is named "Atoll.cfg" and is located in the Atoll installation folder. This file will be ignored if a user configuration file is loaded through the command line parameter. •
Additional configuration files (UTF-8 encoded XML-format CFG files or plain text INI files) The following parameter settings can be stored in additional configuration files with a CFG extension: • • •
Print setup configuration Table import/export configuration Coverage prediction report configuration
The following parameter settings can be stored in specific INI files: • •
CW measurement import configuration Drive test data import configuration
For more information on the contents of additional configuration files, see "Contents of Additional Configuration Files" on page 159. •
Custom predictions file (UTF-8 encoded XML files) This file (one for all customised predictions) contains the list and parameter settings of customised coverage predictions. By default, t
135
Atoll 3.3.2 Administrator Manual Chapter 10: Configuration Files
© Forsk 2016
A studies.xml file can be automatically loaded when Atoll is run if: a. The file is identified in the command line parameter -Stu "studiesfilename" (see "Atoll Command Line Parameters" on page 31 for more information), or b. The file is named "Studies.xml" and is located in the Atoll installation folder. This file will be ignored if a user configuration file is loaded through the command line parameter. The custom predictions file must be created using Atoll to ensure correct syntax and structure. It is possible to edit the contents of this file in an XML editor and make changes if required. For more information on working with customised predictions in Atoll, see the User Manual. For more information on the contents of the custom predictions file, see "Content of the Custom Predictions File" on page 164. •
Predictions files calculated by Value Intervals (UTF-8 encoded XML files) These files (one per prediction) contain the parameter settings of the coverage predictions calculated with the display type (on the General tab of the Properties dialog box) set to "Value intervals". By default, these files are named ".XML" and are located in "C:\\.studies\{}".
10.1 Contents of User Configuration Files The descriptions and examples provided below for each parameter set can help understand the format and function of the user configuration files. The following details are available: • • • • • • • • • • •
"Geographic Data Set" on page 136 "Map Centre and Zoom Level" on page 140 "Zones" on page 140 "Folder Configuration" on page 140 "Coverage Predictions" on page 147 "Automatic Neighbour Allocation Parameters" on page 149 "Automatic Frequency Planning Parameters" on page 151 "Automatic Scrambling Code Allocation Parameters" on page 152 "Automatic PN Offset Allocation Parameters" on page 154 "Microwave Radio Links Parameters" on page 156 "Macros" on page 159.
10.1.1 Geographic Data Set The following parameters are saved for various geographic data types:
136
•
: Format used to display degrees, minutes, and seconds for geographic coordinate systems
•
Population, geoclimatic parameters, vector traffic maps, and other vector layers: • : Name of the folder • : (Different combinations of the following parameters exist in different display settings.) • Display type , selected field , field description containing (same as ) and , visibility flag , and visibility range between and
• properties, such as: font name , font size , font colour , background colour , and font style
137
Atoll 3.3.2 Administrator Manual Chapter 10: Configuration Files
MS Shell Dlg -83 0 0 0 255 255 255
900. 1000. 900