Professional Documents
Culture Documents
v e r s i o n 3.1.0
AT310_AM_E2
sales@forsk.com +33 (0) 562 747 210 +33 (0) 562 747 211
support_us@forsk.com +1 888 GoAtoll (+1 888 462 8655) 8.00 am to 8.00 pm (EST) Monday - Friday
support@forsk.com +33 (0) 562 747 225 9.00 am to 6.00 pm (CET) Monday - Friday
www.forsk.com
Forsk 2011
Atoll 3.1.0 Administrator Manual Release AT310_AM_E2 Copyright 1997 - 2011 by Forsk The software described in this document is provided under a licence agreement. The software may only be used/copied under the terms and conditions of the licence agreement. No part of this document may be copied, reproduced or distributed in any form without prior authorisation from Forsk. The product or brand names mentioned in this document are trademarks or registered trademarks of their respective registering parties. The Atoll Administrator Manual contains administrator-level information and instructions. It is divided into three parts. The first part of the Administrator Manual provides information on installing Atoll and setting up and working with databases in multi-user environments. The second part contains recommendations and information on Atoll configuration and initialisation files. And, the third part describes the database structures of the technology modules.
AT310_AM_E2
Table of Contents
1
1.1 1.2 1.3 1.4 1.5 1.5.1 1.5.2 1.5.3 1.5.4 1.5.5 1.6
2
2.1 2.2 2.3 2.4 2.5 2.6 2.7
3
3.1 3.2 3.3
4
4.1 4.1.1 4.1.2 4.1.3 4.2 4.2.1 4.2.2
5
5.1 5.2 5.3 5.3.1 5.3.2 5.4 5.5 5.5.1 5.5.2 5.5.3 5.6 5.7 5.7.1 5.7.2 5.7.3 5.7.4 5.8 5.9 5.9.1
Forsk 2011
5.9.2
6
6.1 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.2.5 6.3 6.3.1 6.3.2 6.4 6.4.1 6.4.2 6.4.3 6.4.4
Multi-user Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Setting Up Multi-user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Components of Multi-user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Master Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Master Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Shared Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 Shared Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 User Atoll Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Managing User Accounts and Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Defining Database and Interface Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68 Creating and Editing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 Appendix 1: Checking Data Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 Appendix 2: Database Regionalisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 Appendix 3: Calculating Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 Appendix 4: Path Loss Matrices From Different Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
7
7.1 7.1.1 7.1.2 7.1.3 7.1.4 7.2 7.3
8
8.1 8.2 8.3 8.4 8.5 8.6 8.7 8.8 8.9 8.9.1 8.9.1.1 8.9.2 8.9.2.1 8.9.3 8.9.3.1 8.9.3.2 8.9.3.3 8.9.3.4 8.9.4 8.9.4.1 8.9.5 8.9.6 8.9.7 8.9.8 8.9.9 8.9.10 8.9.11 8.9.12 8.9.13 8.9.14 8.9.15 8.9.15.1 8.9.15.2 8.9.15.3 8.9.15.4 8.9.15.5
Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Digital Terrain Model (DTM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85 Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 Clutter Heights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 Vector Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Population Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Custom Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Geographic Data File Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 BIL Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 HDR Header File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 TIFF Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 TFW Header File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 BMP Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 BMP File Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 BMP Raster Data Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 Raster Data Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 BPW/BMW Header File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 PNG Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 PGW Header File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 DXF Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 SHP Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 MIF Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 TAB Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 ECW Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 Erdas Imagine Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 Planet EV/Vertical Mapper Geographic Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 ArcView Grid Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 Other File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 Generic Raster Header File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 Planet Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 DTM Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 Clutter Class Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 Vector Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 Image Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Text Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
AT310_AM_E2
8.9.15.6
9
9.1 9.1.1 9.1.2 9.2 9.3 9.4 9.5 9.5.1 9.5.2 9.6 9.6.1 9.7 9.7.1 9.7.2 9.7.3 9.8 9.8.1 9.8.2 9.8.3 9.9 9.9.1 9.9.1.1 9.9.1.2 9.9.2 9.9.3 9.9.4
10
10.1 10.2 10.3 10.4 10.5 10.6 10.7 10.8 10.9 10.10 10.11 10.12 10.13 10.14 10.14.1 10.14.2
11
11.1 11.1.1 11.1.2 11.1.3 11.1.4 11.1.5 11.1.6 11.1.7 11.1.8 11.1.9 11.1.10 11.2 11.2.1 11.2.2 11.2.3 11.2.4
Forsk 2011
11.2.5 11.3
Drive Test Data Import Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Contents of the Custom Predictions File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
12
12.1 12.1.1 12.1.1.1 12.1.1.2 12.1.1.3 12.1.1.4 12.1.1.5 12.1.1.6 12.1.1.7 12.1.1.8 12.1.1.9 12.1.1.10 12.1.1.11 12.1.1.12 12.1.1.13 12.1.1.14 12.1.1.15 12.1.1.16 12.1.1.17 12.1.1.18 12.1.1.19 12.1.1.20 12.1.1.21 12.1.1.22 12.1.1.23 12.1.1.24 12.1.1.25 12.1.1.26 12.1.1.27 12.1.1.28 12.1.1.29 12.1.1.30 12.1.1.31 12.1.1.32 12.1.1.33 12.1.1.34 12.1.1.35 12.1.1.36 12.1.1.37 12.1.2 12.1.2.1 12.1.2.2 12.1.2.3 12.1.2.4 12.1.2.5 12.1.2.6 12.1.2.7 12.1.2.8 12.1.2.9 12.1.2.10 12.1.2.11 12.1.2.12 12.1.3 12.1.3.1 12.1.3.2 12.1.3.3 12.1.4 12.1.4.1 12.1.4.2 12.1.4.3 12.1.4.4
AT310_AM_E2
12.1.5 12.1.5.1 12.1.6 12.1.6.1 12.1.6.2 12.1.6.3 12.1.6.4 12.1.6.5 12.1.6.6 12.1.6.7 12.1.6.8 12.1.7 12.1.7.1 12.1.7.2 12.1.7.3 12.1.7.4 12.1.7.5 12.1.7.6 12.1.7.7 12.1.7.8 12.1.7.9 12.1.7.10 12.1.7.11 12.1.7.12 12.1.7.13 12.1.7.14 12.1.7.15 12.1.7.16 12.1.7.17 12.1.7.18 12.1.7.19 12.1.7.20 12.1.7.21 12.1.7.22 12.1.7.23 12.1.7.24 12.1.7.25 12.1.7.26 12.1.8 12.1.8.1 12.1.8.2 12.1.8.3 12.1.8.4 12.1.8.5 12.1.8.6 12.1.8.7 12.1.8.8 12.1.8.9 12.1.8.10 12.1.8.11 12.1.8.12 12.1.8.13 12.1.8.14 12.1.8.15 12.1.9 12.1.9.1 12.1.9.2 12.1.9.3 12.1.9.4 12.1.9.5 12.1.9.6 12.1.9.7 12.1.9.8 12.1.9.9 12.1.9.10 12.1.9.11 12.1.9.12
ACP Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Specifying the Location of the Acp.ini File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Database Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Checking Data Integrity After Database Upgrade and Data Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Setting an Automatic Database Integrity Check at Open or Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Modifying the Default Database Connection Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Making Atoll Case-Sensitive for Database Import From Planet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Setting the Sign for KClutter When Importing Data From Planet EV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Enabling/Disabling Password Prompt at Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Archiving Data to Databases Using Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Enabling Partial Refresh from Recently Upgraded Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Common Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Setting the Antenna Patterns Modelling Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Disabling Automatic Locking of Coverage Predictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Enabling Shadowing Margin in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Setting a Default Value for the Cell Edge Coverage Probability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Enabling Indoor Coverage in Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Modifying the Resolution for the LOS Area Calculation Around a Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Disabling the Temporary Local Storage of Path Loss Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Embedding Path Losses in New Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Stopping Calculations on Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Warning About Prediction Vailidity When Display Options are Modified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Reading Exact Altitudes From the DTM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Setting a Common Display Resolution For All Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Allocating Neighbours Based on Distance Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Setting the Priorities for GUI and Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Setting the Number of Parallel Processors and Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Disabling Parallel Calculation of Monte Carlo Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Performing Calculations in Read-Only Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Identifying Transmitter, Repeater, and Remote Antenna Coverage Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Changing the Rounding Method Used for Profile Extraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Estimating Required and Used Memory Size for UMTS Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Disabling Calculations Over NoData Values for DTM and Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Co-Planning: Calculating Predictions in the Current Document Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Co-Planning: Calculating Predictions in Serial or in Parallel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Forcing Neighbour Symmetry Only Inside Focus Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Using Poisson Distribution in Monte-Carlo Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Calculating EIRP from Max Power in Signal Level Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 GSM GPRS EDGE Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Considering Overlapping Zones for IM Calculation Based on Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Setting the Default BSIC Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Selecting the Interference Matrices Used During the AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Checking Database Consistency Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Disabling the Maximum Range Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Enabling the Support for Multi-band Transmitters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 Setting the Best Server Calculation Method in Same Priority HCS Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Hiding Advanced AFP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Making Redundant Fields in the Transmitters Table Read-only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Setting the Transmission Diversity Gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 Adding Grouped HCS Servers Option in Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Deactivating Frequency Band Filtering in IM Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Starting TRX Indexes at 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Hiding the TRX Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Extending the Allowed Value Range for C/I and Reception Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 UMTS HSPA, CDMA2000, and TD-SCDMA Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Suppressing Cell Name Carrier Suffixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Disabling Macro-diversity (SHO) Gains in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Calculating and Displaying Peak or Instantaneous HSDPA Throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Setting the Power to Use for Intra-cell Interference in HSDPA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Enabling Coverage Predictions of Connection Probabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Setting the Calculation Method for HS-PDSCH CQI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Enabling Orthogonality Factor in Pilot EC/NT Calcaultion in HSDPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Setting the Maximum Number of Rejections for Mobiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Setting the Maximum Number of Rejections for HSDPA Mobiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Defining an Offset With Respect to The Thermal Noise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Setting Precision of the Rasterization Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Defining the Number of Iterations Before Downgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Forsk 2011
12.1.9.13 Adjusting the Working of the Proportional Fair Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.9.14 Displaying Ec/I0 of Rejected Mobiles in Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.9.15 Switching Back to the Old Best Server Determination Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.9.16 Displaying Automatic Allocation Cost Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.9.17 Selecting SC and PN Offset Allocation Strategies Available in the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.9.18 Defining a Fixed Interval Between Scrambling Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.9.19 Compressed Mode: Restricting Inter-carrier and Inter-technology Neighbour Allocation . . . . . . . . . . . . . . . . . . . . . . . 12.1.9.20 Setting the Maximum AS Size for SC Interference Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.9.21 Displaying Uplink Total Losses in Coverage by Signal Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.9.22 Setting the Maximum UL Reuse Factor for HSUPA Users Noise Rise Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10 WiMAX and LTE Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10.1 Blocking Access to IEEE Parameters in WiMAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10.2 Using Only Bearers Common Between the Terminals and Cells Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10.3 Disabling Multi-antenna Interference Calculation in LTE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10.4 Enabling Display of Signals per Subcarrier Point Analysis in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10.5 Enabling Multi-antenna Interference Calculation in WiMAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10.6 Including Cyclic Prefix Energy in LTE Signal Level Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10.7 Excluding Cyclic Prefix Energy in WiMAX Signal Level Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10.8 Ignoring Inter-Neighbour Preamble Index Collision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10.9 Ignoring Inter-Neighbour Physical Cell ID Collision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10.10 Renaming OPUSC Zone to PUSC UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10.11 Deactivating Uniform Distribution of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10.12 Activating Basic Preamble Index/Physical Cell ID Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10.13 Taking Second Order Neighbours into Account in the AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.10.14 Setting PDCCH to 100% Loaded in LTE Interference Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.11 Microwave Radio Links Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.11.1 Excluding Near-field Interference from Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.11.2 Excluding Standby Channels from Interference Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.11.3 Updating A>>B and B>>A Profiles in Real-time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.11.4 Disabling Sheilding Factor on Wanted Signal at Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.11.5 Using Old Min C/I Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.11.6 Defining Channel Number Prefix and Suffix for Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.12 Measurement Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.12.1 Displaying Additional Information in Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.12.2 Setting the Number of Transmitters per Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.12.3 Recalculating Distances of Points From There Serving Cells at Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.12.4 Defining the BCCH and BSIC Columns for FMT Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1.12.5 Importing Drive Test Data with Scrambling Codes as Integers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 ACP Initialisation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1 Managing Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2 GUI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.1 Default Values on the Optimisation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.2 Automatically Creating Custom Zones on the Optimisation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.3 Default Values on the Objectives Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.4 Default Values on the Reconfiguration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.5 Default Values for EMF Exposure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.6 Default Values on the Antennas Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.7 Defining the Functionality of the ACP - Automatic Cell Planning Properties Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.7.1 Defining the Antenna Masking Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.8 Defining Reconfiguration Values in Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.8.1 Defining Reconfiguration Values for Transmitters and Repeaters Using Custom Atoll Fields. . . . . . . . . . . . . . . . . . . 12.2.2.8.2 Defining Reconfiguration Values for Cells Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.8.3 Defining Reconfiguration Values for Sites Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.8.4 Defining Reconfiguration Values for Antennas Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.9 Defining Site Class Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.9.1 Defining Automatic Site Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.9.2 Automatically Assigning Site Classes in the ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.10 Defining the Appearance of the Optimisation Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.10.1 Defining the Colours in the Quality Analysis Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.10.2 Other Components of the Optimisation Dialogue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.11 Defining the Appearance of New Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.12 Defining the Functionality of the Commit Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.13 Defining the Appearance of the Overlay Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.14 Defining the Appearance of the Graph Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.15 Defining the Default Font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.16 Exporting Optimisation Results in XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
198 198 198 199 199 199 199 199 200 200 200 200 200 201 201 201 201 201 202 202 202 202 202 203 203 203 203 203 203 203 204 204 204 204 204 204 205 205 205 205 206 206 206 207 211 213 214 214 214 215 215 216 217 217 218 218 219 219 219 220 221 221 221 221 221 222
10
AT310_AM_E2
12.2.3 12.2.3.1 12.2.3.2 12.2.3.3 12.2.3.4 12.2.3.4.1 12.2.3.4.2 12.2.3.5 12.2.3.6 12.2.3.7 12.2.3.8 12.2.3.9 12.2.3.10 12.2.3.11 12.2.3.12 12.2.3.13 12.2.3.14 12.2.3.15 12.2.4 12.2.5 12.2.5.1
ACP Core Engine Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Log File Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Calculation Thread Pool Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Memory Management Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Signal Level and Macro Diversity Gain Calculation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Signal Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Macro Diversity Gain (UMTS Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Determining Transmitter Altitude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Balancing Speed, Memory Use, and Accuracy in Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Accessing Raster Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Accessing Path Loss Matrices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Preamble Segmentation (WiMAX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Multi-antenna Interference Calculation (LTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Multi-antenna Interference Calculation (WiMAX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Cyclic Prefix Energy in Signal Level Calculation (LTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Cyclic Prefix Energy in Signal Level Calculation (WiMAX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Fixed Ratio Between Pilot Power and Max Power (UMTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Enabling Multi-technology Optimisation Including WiMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 EMF Exposure Core Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Other Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 Validity of Coverage Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
13
13.1 13.1.1 13.1.2 13.2 13.3 13.4 13.5 13.6 13.7 13.8 13.9 13.10 13.11 13.12 13.13 13.14 13.15 13.16 13.17 13.18 13.19 13.20 13.21 13.22 13.23 13.24 13.25 13.26 13.27 13.28 13.29 13.30 13.31 13.32 13.33 13.34 13.35 13.36 13.37 13.38 13.39 13.40 13.41
11
Forsk 2011
13.42 13.43 13.44 13.45 13.46 13.47 13.48 13.49 13.50 13.51 13.52 13.53 13.54 13.55 13.56 13.57 13.58 13.59 13.60 13.61 13.62 13.63
Receivers Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RepeaterEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Repeaters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SecondaryAntennas Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SeparationRules Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Separations Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sites Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SitesLists Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SitesListsNames Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TMAEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TplTransmitters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmitters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRGConfigurations Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRGs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRXEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRXs Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRXTypes Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSConfigurationNames Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSConfigurations Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TxsLists Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TxsListsNames Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Units Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
249 249 250 250 251 251 251 252 252 252 252 254 256 257 259 259 260 260 260 261 261 261
14
14.1 14.1.1 14.1.2 14.2 14.3 14.4 14.5 14.6 14.7 14.8 14.9 14.10 14.11 14.12 14.13 14.14 14.15 14.16 14.17 14.18 14.19 14.20 14.21 14.22 14.23 14.24 14.25 14.26 14.27 14.28 14.29 14.30 14.31 14.32 14.33 14.34 14.35 14.36 14.37 14.38 14.39 14.40
12
AT310_AM_E2
14.41 14.42 14.43 14.44 14.45 14.46 14.47 14.48 14.49 14.50 14.51 14.52 14.53 14.54 14.55 14.56
TMAEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 TplTransmitters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 Transmitters Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 TxsLists Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 TxsListsNames Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 UECategories Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 UERxEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 UMTSEnvironmentDefs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 UMTSMobility Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 UMTSServices Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 UMTSServicesQuality Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291 UMTSServicesUsage Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 UMTSTerminals Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 UMTSTraficEnvironments Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 UMTSUserProfiles Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Units Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
15
15.1 15.1.1 15.1.2 15.2 15.3 15.4 15.5 15.6 15.7 15.8 15.9 15.10 15.11 15.12 15.13 15.14 15.15 15.16 15.17 15.18 15.19 15.20 15.21 15.22 15.23 15.24 15.25 15.26 15.27 15.28 15.29 15.30 15.31 15.32 15.33 15.34 15.35 15.36 15.37 15.38 15.39 15.40 15.41 15.42 15.43 15.44 15.45 15.46
13
Forsk 2011
16
16.1 16.2 16.3 16.4 16.5
17
17.1 17.1.1 17.1.2 17.2 17.3 17.4 17.5 17.6 17.7 17.8 17.9 17.10 17.11 17.12 17.13 17.14 17.15 17.16 17.17 17.18 17.19 17.20 17.21 17.22 17.23 17.24 17.25 17.26 17.27 17.28 17.29 17.30 17.31 17.32 17.33 17.34 17.35 17.36 17.37 17.38 17.39 17.40 17.41 17.42 17.43 17.44 17.45 17.46 17.47 17.48 17.49 17.50 17.51 17.52
14
AT310_AM_E2
18
18.1 18.1.1 18.1.2 18.2 18.3 18.4 18.5 18.6 18.7 18.8 18.9 18.10 18.11 18.12 18.13 18.14 18.15 18.16 18.17 18.18 18.19 18.20 18.21 18.22 18.23 18.24 18.25 18.26 18.27 18.28 18.29 18.30 18.31 18.32 18.33 18.34 18.35 18.36 18.37 18.38 18.39 18.40 18.41 18.42 18.43 18.44 18.45 18.46 18.47 18.48 18.49 18.50 18.51 18.52 18.53 18.54 18.55 18.56 18.57 18.58 18.59 18.60
15
Forsk 2011
19
19.1 19.1.1 19.1.2 19.2 19.3 19.4 19.5 19.6 19.7 19.8 19.9 19.10 19.11 19.12 19.13 19.14 19.15 19.16 19.17 19.18 19.19 19.20 19.21 19.22 19.23 19.24 19.25 19.26 19.27 19.28 19.29 19.30 19.31 19.32 19.33 19.34 19.35 19.36 19.37 19.38 19.39 19.40 19.41 19.42 19.43 19.44 19.45 19.46 19.47 19.48 19.49
20
20.1 20.1.1 20.1.2 20.1.3 20.1.4 20.2 20.3 20.4 20.5 20.6 20.7 20.8
16
AT310_AM_E2
20.9 20.10 20.11 20.12 20.13 20.14 20.15 20.16 20.17 20.18 20.19 20.20 20.21 20.22 20.23 20.24 20.25 20.26 20.27 20.28 20.29 20.30 20.31 20.32 20.33 20.34 20.35 20.36 20.37 20.38
MWCompatibilitiesGuides Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 MWDefaultsCurves Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 MWEPO Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 MWEPOLinkClass Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 MWEquipments Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 MWFamilies Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 MWFamilyBands Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 MWFamilyBrConfigs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 MWFamilyChSpacings Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 MWFamilyModulations Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 MWGuides Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 MWHubs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 MWIrfs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 MWLinks Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 MWLinkTypes Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 MWManufacturers Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 MWModulations Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 MWMultiHops Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 MWMultiHopsLinks Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 MWPMP Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 MWPorts Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 MWRepeaters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 MWSubbands Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 MWTplLinks Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 Networks Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452 PropagationModels Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 Sites Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 SitesLists Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 SitesListsNames Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 Units Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
17
Forsk 2011
18
Part 1
Getting Started
This part of the administrator manual provides the information to install and set up Atoll and its components, and to manage databases and multi-user environments. In this part, the following are explained: "Getting Started" on page 21 "Installing Atoll and Components" on page 25 "Setting Up Distributed Calculation Server" on page 35 "Managing Licences" on page 39 "Managing Databases" on page 45 "Multi-user Environments" on page 65
AT310_AM_E2
1 Getting Started
Atoll is an open, scalable, and flexible multi-technology network design and optimisation platform that supports wireless operators throughout the network lifecycle, from initial design to densification and optimisation. Atoll supports a wide range of implementation scenarios, from standalone to enterprise-wide server-based configurations using distributed and multithreaded computing. This manual explains how to install, configure, and deploy Atoll and how to set up back-end databases and manage users in a multiuser environment. Database structures of the different technology modules are also provided for reference. In this chapter, the following are explained: "Supported Technologies" on page 21 "Supported Operating Systems" on page 21 "Supported Database Management Systems" on page 21 "Supported Installation Configurations" on page 22 "Recommended Hardware and Software" on page 22 "Recommended Computer Network Architecture" on page 23.
The physical location of databases varies according to the type of the database. The following table shows where the database must be installed:
21
Forsk 2011
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.
Depends on the size of the locally stored geographic data and path loss matrices, if any.
If you are working with an Oracle database, you must install Oracle client on the user computers as well. The Oracle client version must correspond to the Oracle database installed on the database server.
22
AT310_AM_E2
120 GB or morea Microsoft Windows 2003 Server / Microsoft Windows 2008 Server / Unix / Linux Oracle 10g or 11g / Microsoft SQL Server 2005 / Sybase Adaptive Server 12.5.0
The recommended bandwidth between Citrix servers and Citrix clients for satisfactory performance is 300 Kbps per user.
In order to simulate the average activity of Atoll users, each user is assumed to carry out a "Routine Operation" 5 times during a three-hour working period. The "Routine Operation" consists in modifying parameters for 40 cells in 30 minutes, recalculating path loss matrices for these 40 cells, and calculating a best server coverage prediction.
23
Forsk 2011
Although a best server coverage prediction does not require a lot of computer resources for calculations, it requires Atoll to load all the path loss matrices in memory. When the path loss matrices are stored on a file server, as recommended, this operation creates a considerable data transfer activity over the network. The benchmark tests have been based on this simulated data transfer activity. Computer Network Architecture A centralised network architecture is the most widely used network architecture by Atoll users. The figure below shows the recommended architecture along with a per-user network bandwidth requirement between different network components.
Figure 1.1: Recommended Network Architecture and Bandwidth Requirements Citrix MetaFrame is used to centralise data and balance user loads between servers. A network based on such an architecture with Citrix servers must provide high speed connections between the Citrix servers and the file servers. The required number of Citrix servers depends on the number of users. On the average, one processor per 2 to 3 users is recommended. Thus, the required number of Citrix servers depends on the number of processors and the number of endusers. Computer Network Dimensioning You should set up your network according to the number of Atoll users, which is related to the size of the planning project. A country-wide project would have larger network dimensions than a project that covers a city. Link From End-user Citrix server To Citrix server File server Recommended Bandwidth 300 kbps per user 30 Mbps per user performing calculations
24
AT310_AM_E2
You need administrator rights for installing Atoll and its components.
To disable UAC: a. Go to Control Panel > User Accounts. b. Select Change User Account Control settings. The User Account Control Settings dialogue appears. c. Choose Never notify. d. Click OK. 1. Run the Atoll 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.
Figure 2.1: Atoll Setup Wizard 2. Click Next. The Select Destination Location dialogue appears. 3. Select the destination folder for the installation. The default installation folder for Atoll is C:\Program Files\Forsk\Atoll in the 32-bit versions of Microsoft Windows, and C:\Program Files (x86)\Forsk\Atoll in the 64-bit versions. You can select a different location by clicking Browse.
25
Forsk 2011
Figure 2.2: Select Destination Location Dialogue 4. Click Next. The Select Components dialogue appears. 5. 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.3: Select Components Dialogue 6. Click Next. If you selected the Distributed Calculation Server component for installation, the Logon Information dialogue appears. If you did not select this component, the Select Start Menu Folder dialogue appears. In which case, proceed to step 7.
Figure 2.4: Select Components Dialogue a. Enter the Domain name, Username, and Password. This information will be used to run the distributed calculation service on the computer, and allow other users of the domain to access this service. b. Click Next. The Select Start Menu Folder dialogue appears 7. 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.
26
AT310_AM_E2
Figure 2.5: Select Start Menu Folder Dialogue 8. Click Next. The Ready to Install dialogue appears. 9. Review the installation parameters.
Figure 2.6: Ready to Install Dialogue 10. Click Install. Atoll and its selected components are installed on the computer. If you work with fixed licences and you installed the Driver for Fixed Licence Keys, restart the computer. Restarting the computer is necessary for the driver to work. If you work with fixed licences, plug in the fixed licence key. On the versions of Microsoft Windows that support UAC (disabled before the installation), run Atoll once using an administrator account and with UAC disabled when the installation is complete. If the following files do not already exist in the installation folder, empty ones are created by the setup: [Atoll installation folder]\Atoll.ini [Atoll installation folder]\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 access 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
Forsk 2011
Microsoft Windows Vista Microsoft Windows 7 Microsoft Windows 2008 Server Microsoft Windows 2008 Server R2
To disable UAC: a. Go to Control Panel > User Accounts. b. Select Change User Account Control settings. The User Account Control Settings dialogue appears. c. Choose Never notify. d. Click OK. 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.
Figure 2.7: Atoll C++ Development Kit Setup Wizard 2. Click Next. The Select Destination Location dialogue appears. 3. Select the destination folder for the installation. The default installation folder for Atoll C++ Development Kit is C:\Program Files\Forsk\Atoll in the 32-bit versions of Microsoft Windows, and C:\Program Files (x86)\Forsk\Atoll in the 64-bit versions. You can select a different location by clicking Browse.
Figure 2.8: Select Destination Location Dialogue 4. Click Next. The Ready to Install dialogue appears. 5. Review the installation parameters.
28
AT310_AM_E2
Figure 2.9: Ready to Install Dialogue 6. Click Install. Atoll C++ Development Kit is installed on the computer.
29
Forsk 2011
Password for installing the distributed calculation server. /TYPE=type name Overrides the default setup type. The setup type names are: Full installation: full Compact installation: compact Custom installation: custom
For full and compact setup types, the /COMPONENTS parameters are ignored. /COMPONENTS="comma separated list of component names" Overrides the default component settings. Using this command line parameter causes the setup to automatically select a custom installation type. Only the specified components will be selected. Component names are: Atoll: Atoll Export to Google Earth add-in: "Addins\GoogleEarth" Best signal export add-in: "Addins\SignalsExport" Driver for fixed licence keys: RainbowDongle Distributed calculation server: Atoll_Server Atoll Management Console: AMC
Example: To install Atoll, the distributed calculation server, and the driver for fixed licence keys: /COMPONENTS="Atoll,Atoll_Server,RainbowDongle"
30
AT310_AM_E2
Add-ins installed by the Atoll setup are uninstalled when Atoll is uninstalled. To uninstall any other add-in by unregistering its DLL: 1. Close Atoll. 2. Right-click the DLL file in Windows Explorer. The context menu appears. 3. Select Unregister. The DLL is unregistered. You can also unregister the DLL from the command prompt using regsrv32.exe /u.
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 142. To remove a macro from Atoll: 1. In Atoll, select Tools > Add-ins and Macros. The Add-ins and Macros dialogue appears (see Figure 2.10 on page 30). 2. In the list of available macros, select the macro you wish to remove. 3. Click Delete. Other commands available in the Add-ins and Macros dialogue are: Edit: Edit the selected macro in the default text editor. Run: Execute the selected macro. Icon: Assign an icon to the selected macro. Icons assigned to macros appear in the Macros toolbar. Refresh: To reload the selected macro file.
31
Forsk 2011
Instructs Atoll to use the mentioned providername to access the database server (Microsoft Access: Microsoft.Jet.OLEDB.4.0, or Oracle: MSDAORA.1). -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.
Fixed licence keys Fixed licence keys cannot be used with "Server"-type operating systems. Therefore, you should not install the driver for fixed licence keys on: Microsoft Windows 2003 Server Microsoft Windows 2008 Server Microsoft Windows 2008 Server R2
Citrix
The current version of the driver for fixed licence keys (Sentinel SuperPro driver) installed with Atoll is the 7.6.1. If Atoll is unable to access the fixed licence key, even after a clean installation, try reinstalling the Sentinel SuperPro driver manually. The drivers setup program (SPI761.exe) is copied to the Sentinel subfolder in the Atoll installation folder by the setup if you selected the Driver for Fixed Licence Keys component during the installation. You can also download the driver from http://www.safenet-inc.com. Restart the computer when asked by the setup. Restarting the computer is necessary for the driver for fixed licence keys to work. If you get a protection key error message, verify that the fixed licence key correctly plugged in and that the licence has not expired. In case the fixed or the floating licence key becomes unavailable, Atoll will ask the users currently accessing the key to save their open documents before Atoll closes. If the key becomes available again, Atoll will let the users continue working. Do not change the computers date.
If you have installed Atoll on a Citrix MetaFrame server, you must published it to make it available to the users.
Atoll version and build You can get information about Atoll (version, build, type of licence and remaining time before expiration, etc.) by selecting Help > About Atoll in the main menu in Atoll.
32
AT310_AM_E2
Atoll file version and technology ATL file properties store the Atoll version and build number in which the file was last saved, and the technologies contained in the file. To access the ATL file properties: 1. Right-click the ATL file in the Windows Explorer. The context menu appears. 2. Select Properties from the context menu. The file properties dialogue appears. 3. In Windows XP, click the Summary tab and then the Advanced button. In Windows Vista and 7, 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 Forsks 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 Forsks support website. The support website also offers you: A problem report template, Documentation,
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.
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 Control Panel. To uninstall Atoll: In Windows XP or Windows 2003 Server: 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, or Windows 2008 Server: 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. Add-ins installed by the Atoll setup are uninstalled when Atoll is uninstalled.
33
Forsk 2011
34
AT310_AM_E2
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.
35
Forsk 2011
Running More Than One Instance of the Service By default, a single instance of the distributed calculation service is run. You can, however, run up to 9 additional distributed calculation services (a total of 10 including the first one) manually. To manually run additional distributed calculation services, double-click the AtollSvr.exe file located in the Atoll installation folder. For each new instance of the service, a command prompt window opens. To stop an additional, manually run service, close the command prompt window corresponding to it. Atoll can detect a total of 10 instances of the distributed calculation service. If you run more than 9 additional distributed calculation services, they will not be detected by Atoll and can cause the operating system to stop responding. Stopping and Starting the Distributed Calculation Server To stop the distributed calculation service: 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. 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 "<Atoll Installation Path>\AtollSvr.exe /UnregServer". <Atoll Installation Path> is the path to the Atoll installation folder. c. Click Run. This will remove the distributed calculation service from the computer.
36
AT310_AM_E2
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 may also be on a file server, not necessarily on the users computer that requested the calculations). 7. Atoll user may then request the path loss matrices from the file server if they are needed for coverage predictions.
37
Forsk 2011
38
AT310_AM_E2
4 Managing Licences
Atoll can be used on: Computers with fixed licence keys plugged in to USB slots on the computers themselves, or Computers connected to a licence server with a floating licence key plugged in to a USB port on the server. The driver for fixed licence keys can be installed at the same time as Atoll. For more information, see "Installing Atoll and Components" on page 25. The software for managing floating licence keys must be installed on a server accessible to the computers on which Atoll is going to be used. For more information, see "Working with Floating Licences" on page 39. For information on the Atoll licence management utility, see "Using the Atoll Licence Manager" on page 41.
39
Forsk 2011
Do not plug the floating licence key in the server before installing the device drivers. Wait for the HASP licence manager setup to indicate when to plug in the key. If the floating licence server is protected by a firewall, port 475 must be open when using the UDP or TCP protocols. Once the HASP licence manager has been installed, the floating licence key must always remain plugged in. In case the fixed or the floating licence key becomes unavailable, Atoll will ask the users currently accessing the key to save their open documents before Atoll closes. If the key becomes available again, Atoll will let the users continue working. The floating licence key may become unavailable and a key protection error message appears in Atoll if the licence management server is heavily loaded. Check if there is any application running on the server that might be causing the problem. If this is the case, remove any such application from memory. If this is not possible, try changing the latency associated to the HASP licence manager in accessing the key.
Installation and Startup The HASP licence manager, the HASP device driver, and the floating licence key must be installed on the server. The following options should be selected when installing the HASP licence manager: Choose "Service" as the type of installation. This means that the licence manager will run as a service, and will be accessible even if there is no user logged on. You may choose to install it as an application, but in that case you will have to run the licence manager manually every time you log on to the server and you will have to stay logged on for the licence server to be available to the Atoll users. Accept automatic driver installation. This will install the HASP device driver required by the HASP licence manager. Once the device driver is successfully installed, plug in the floating licence key. Once installed, start the HASP licence manager. If you selected "Service" as the type of installation, the licence manager will start in service mode. An icon will be available in the task bar. You can access the network communication protocols by double-clicking this icon. The HASP licence manager window displays a list of supported protocols which can be modified through the Load and Remove menus. Closing this window does not stop the licence manager. The icon remains available in the taskbar as long as the service is running. To stop the HASP licence manager: a. Go to Control Panel > Administrative Tools > Services. b. In the list of services, right-click the HASP Loader service, and select Stop from the context menu. You may also copy (from the installation CD) or create the nhsrv.ini file on the floating licence server (in the HASP licence manager installation folder). The HASP licence manager settings in this file can be modified according to the your requirements. For more information on the contents of the nhsrv.ini file, see "nhsrv.ini File" on page 40. To restrict access to the HASP licence manager installation folder, you can assign read/ write access rights to this folder to administrators and read-only rights to end-users.
HASP Monitor (Optional) You can install the HASP monitor on the floating licence server, or on one or several other computers, to monitor the token allocation and retrieval activity. The HASP monitor displays the list of computers using tokens available on the floating licence key.
40
AT310_AM_E2
File Contents The following is a sample of the nhsrv.ini file that shows how to set a list of computers allowed access to the floating licence server. Complete syntax may be found on the HASP installation CD or on the Aladdin website. [NHS_SERVER] ;NHS_IP_LIMIT = <IpAddr0>[,<IpAddr1>,<IpAddr2>,...] ;Specifies the IP addresses of computers served by the licence manager ;Example: 10.1.1.1, 10.1.1.* ;For use, remove the semi-colon before NHS_IP_LIMIT
A nethasp.ini file located in the Atoll installation folder has priority over any nethasp.ini file located in the Windows folder, which in turn has priority over any nethasp.ini file located in a folder listed in the system path variable. Storing the nethasp.ini file in the Windows folder instead of the Atoll installation folder may be useful if you have more than one version of Atoll installed, and you wish to access the same floating licence server. This avoids making a copy of the file in each Atoll installation folder. File Contents The following is a sample of the nethasp.ini file with the minimum required information. Complete syntax may be found on the HASP installation CD or on the Aladdin website. [NH_COMMON] NH_IPX = Disabled NH_NETBIOS = Disabled NH_TCPIP = Enabled [NH_TCPIP] NH_SERVER_ADDR = 3CT000J NH_TCPIP_METHOD = UDP NH_USE_BROADCAST = Disabled a. ;(a)IP address of the floating licence server ;(b)Send TCP or UDP packets ;Use TCP/IP broadcast - Enabled or Disabled ;Use the IPX protocol - Enabled or Disabled ;Use the NETBIOS protocol - Enabled or Disabled ;Use the TCP/IP protocol - Enabled or Disabled
b.
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. For HASP Licence Manager 8.20 and later, Aladdin recommends UDP as the default TCP/IP method.
Remove the NH_SESSION and NH_SEND_RCV entries from the nethasp.ini file if these exist. These fields define the timeout delays depending to the network. They may be useful in slow networks and should be set only if required.
41
Forsk 2011
Figure 4.1: Atoll Licence Manager 4. Under Available licences, select a licence 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 licence key. Type: The type of key, Fixed licence or Floating licence. Reference: Unique floating licence key reference provided by Forsk. This number must be communicated to Forsk, when requested, for reprogramming the licence key. This reference is also printed on the sticker on the key. Location (server): Name of the floating licence management server on which the floating licence key is plugged. Under Modules and licences, all the Atoll modules available on the selected key are listed along with the numbers of licence tokens of each. Under Number of licences, the Modify buttons are reserved for Forsk use only. Under Dates and durations, the following dates and durations are available: Licence start Licence end Duration of validity Time bomb
42
AT310_AM_E2
A purchased Atoll licence corresponds to a particular Atollversion. There is no time limit on using this version. However, yearly maintenance must be purchased in order to access newer versions with updates and bug fixes. When you purchase maintenance, Forsk reprograms your licence keys to allow access to new versions. The Time bomb date is the end date for maintenance. When the time bomb date passes, the licence key stops working. You may then choose to either purchase maintenance for the next year, and benefit from the new features and bug fixes, or have the licence key reprogrammed without maintenance for the next year, in which case users can continue working with the existing version. Atoll can inform you about the approaching time bomb date 30 days in advance. This alert can be configured through the Atoll.ini file. Do not attempt to modify the Time bomb settings on the fixed licence key. Contact Forsks customer support. Do not change the computers 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.
To update a licence key: 1. Close Atoll. 2. Go to the Atoll installation folder. 3. Run Lic.exe. The licence manager opens (see Figure 4.1 on page 42). 4. Under Available licences, select the key to update. If the key does not appear in the available licences list, check that it is plugged in to your computer. 5. Under Key programming, click Load. The Open dialogue appears. 6. Select the ALIC file provided by Forsk. 7. Click Open. The key is updated.
43
Forsk 2011
44
AT310_AM_E2
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 radio planning and optimisation engineers. Atoll enables you create databases, upgrade them to newer versions, archive and refresh data with databases, manage and resolve data conflicts, and create and work with multi-level databases. A database server can store one or more database. 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 45 "Atoll Management Console" on page 46 "Creating New Databases" on page 48 "Upgrading Existing Databases" on page 50 "Working With Multi-level Databases" on page 52 "Setting Database Access Privileges" on page 57 "Managing Data Modifications History" on page 57 "Using Oracle With Atoll" on page 60
The relationships in the database schema figures are represented by arrows. These unidirectional arrows should be read as: = n or 1 In the tables, primary keys are listed in bold and italic characters. In the database schema figures, primary keys are in bold and underlined characters, and required fields are in bold characters. If you export the content of an ATL document which is already connected to a database, to a another RDBMS (for example, if you export a document connected to an Oracle database to Sybase or Microsoft Access), some field types will be converted according to the above table but this conversion does not have an impact on the document in Atoll.
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:
45
Forsk 2011
Atoll Field Type Float Double Integer Short Boolean Text Memo Binary Length 4 8 4 2 2 Variable* Variable Variable
Oracle Equivalent Field Type FLOAT FLOAT NUMBER NUMBER NUMBER VARCHAR2 VARCHAR2 LONG RAW Length 32 64 11 6 1 Variable* 2000
Microsoft SQL Server Equivalent Field Type real float int tinyint bit varchar varchar image Length 4 8 4 1 1 Variable* 4000 16
Sybase Equivalent Field Type real float int tinyint bit varchar text image 16 Length 4 8 4 1 1 Variable*
Microsoft Access Equivalent Single Double Long Integer Integer Yes/No Text* Memo OLE Object
* Lengths for these fields are specified in parentheses in the database structure tables. 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 46 and "Upgrading Existing Databases" on page 50, respectively.
The Atoll Management Console can be installed with Atoll. For more information, see "Installing Atoll and Components" on page 25. You can run the Atoll Management Console from the Windows Start menu program group or by double-clicking Atollmgmt.msc in the Atoll installation folder. The Atoll Management Console runs using the Microsoft Management Console environment. When the Atoll Management Console is run for the first time, you must register your database server in order to have the databases installed on the server to be available in the Atoll Management Console. To register a database server: 1. In the Atoll Management Console window, in the left pane, right-click the Database item under the Administration Atoll. The context menu appears. 2. Select Register a New Server. The Data Link Properties dialogue appears. 3. Click the Provider tab. On the Provider tab, select the provider for your database server depending on whether it is Oracle or SQL Server.
46
AT310_AM_E2
Figure 5.1: Data Link Properties dialogue - Provider Tab 4. Click Next. On the Connection tab, enter the server name, and the user name and password required to access the database server. You can check to see if the entered information is correct by clicking the Test Connection button. 5. Click OK. The selected database server is registered and available in the Atoll Management Console (see Figure 5.2 on page 47). You now have access to the features offered by the Atoll Management Console.
Figure 5.2: Atoll Management Console The tree in the left pane lists the registered database servers. Registered database servers may 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 may be the owner of one of the listed databases. The user name of the owner of a database appears in parentheses in the title bar. One Oracle user can create and own one database. For each new database, you must create a new user owner of the database. The following details are available for databases created or upgraded using the Atoll Management Console: Whether the database corresponds to the current Atoll version ( the current version. The type of the database: master or project. ) or a previous version ( ), not yet upgraded to
A master database may 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" on page 52. The technology of the network modelled by the database. The path of the shared path loss folder.
To view details of a database: 1. In the right pane, right-click the database in the list. The context menu appears. 2. Select Properties. The database Properties dialogue appears. 3. The Properties dialogue contains two tabs: General tab: The General tab displays the Name, Description, Owner, Type, and Version of the database. Statistics tab: The Statistics tab displays the number of records in each table of the database.
47
Forsk 2011
To create a new database: 1. In the Atoll Management Console window, in the left pane, right-click the database server on which you want to create a new database. The context menu appears. 2. Select New > Database. The New Database Wizard dialogue appears.
48
AT310_AM_E2
3. Click Next. The Specify the database owner page appears. 4. Select Use the current connection if you wish 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. 5. Click Next. The Name the database and specify a network type page appears. 6. Enter a Name for the new database and select the Network type. The Network type can be one of the database templates installed with Atoll. Atoll and the Atoll Management Console must have the same version. This means that the Atoll Management Console can create databases based on the database templates installed with Atoll of the same version. 7. Click Next. The Specify units and coordinate systems page appears. 8. Select a Transmission power unit and a Reception threshold unit. 9. Under Coordinate systems, select a Cartographic projection system and the System to be used in the database. 10. Click Next. The Ready to create database page appears. This page provides a summary of the selected parameters. 11. Click Execute. The Atoll Management Console creates the new database with the defined parameters on the selected database server. A database created using the Atoll Management Console contains an ATOLL_ADMIN table with the following structure: Field NAME DESCRIPTION ATOLL_VERSION ATOLL_BUILD ATOLL_DBTYPE ATOLL_TEMPLATE DBSCHEMA Type Text (50) Text (255) Text (10) Integer Text (10) Text (50) Memo Description The name of the database Description of the database The current version of Atoll Current build of Atoll Type of Atoll database (i.e., Master or Project) Atoll database template used to create the database 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 may 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 50. 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.
49
Forsk 2011
Description The name of the database The current version of Atoll 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. You can use the ODBC interface (used by Sybase as well) to access all databases that accept UDL files and the ODBC interface.
In order to be able to archive to and refresh data from a Sybase 12.5.0 database using the ODBC driver: 1. Open the Windows registry using regedit.exe. 2. Add a "string" called "WorkArounds2" in: HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Sybase Where "Sybase" represents the logical name used for the ODBC connection. 3. Assign the value "152" to "WorkArounds2", i.e., WorkArounds2 = 152.
The Microwave Radio Links template now supports Radio Series. Similar microwave radios belong to the same radio series. In order to organise the microwave radios (microwave equipment) in radio series before the database upgrade: 1. In Atoll 2.8.x, add a custom field named FAMILY of type Text (50) to the MWEquipments table. 2. Enter the radio series names in this field for each radio, i.e., group the radios of the same series under the same radio series name in the FAMILY field. Without this manual organisation of the microwave radios into radio series, the database upgrade will create one radio series for each microwave radio. To upgrade a database using the Atoll Management Console: 1. In the Atoll Management Console window, in the right pane, right-click the database that you want to upgrade. The context menu appears. 2. Select Upgrade Database. The Database Update Wizard dialogue appears. The Database Upgrade Wizard displays the current database version and the version to which the database will be upgraded.
50
AT310_AM_E2
3. Click Next. The Name the database page appears. 4. Enter a Name and description for the database. 5. Click Next. The Database Upgrade Wizard reads the database to determine the Atoll database template using which it was created. If there is more than one template corresponding to the network, select the template to be used for the upgrade and click Next. The Atoll Management Console upgrades the database. If some of the tables in a database have been replaced by views, the Database Upgrade Wizard asks to select the views to upgrade. Select the views that you want the Atoll Management Console to upgrade and click Execute. If, for example, the definition of a view is given by the condition: Select Field1, Field2 from Table1 where (Condition1); The wizard first upgrades the schema of Table1 and then upgrades the definition of the view. The upgraded definition will take the newly added fields into account. 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 Consoles 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 57. 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. Notes on Document Data Structure Upgrade The data structure of an Atoll document not connected to any database is automatically upgraded to the new Atoll version when the document is opened and saved in the new version. Once saved, it is not possible to open the document in an earlier Atoll version. The data structure of an Atoll document connected to a database not yet upgraded to the new version can be upgraded by: Either opening the document in the new Atoll version, disconnecting it from the database, and saving it in the new version, or Upgrading the database to the new version and then opening and saving the document in the new Atoll version. Once disconnected from its database, it is not possible to reconnect the document to any database. Obsolete fields in the data structure of a document not connected to any database are automatically deleted by Atoll when the document is saved in the new version. If the database has been upgraded to the new version but an Atoll document connected to the database has not yet been upgraded, it is possible to open the document in the previous Atoll version as read-only. It is also not possible to interact with the upgraded database (archive, refresh, etc., are not allowed). To make the document write-accessible in the previous Atoll version, it must be disconnected from the upgraded database.
It is possible to upgrade an existing database manually (not recommended) by adding and deleting tables and fields as required by the new version. However, due to the complex nature of the upgrade process, it is highly recommended to use the Atoll Management Console for upgrading existing databases. For information on manually upgrading a database, see "Upgrading Databases Manually" on page 52.
51
Forsk 2011
Upgrading Databases for the First Time If you want to upgrade a database which was neither created nor already upgraded (at least once) using the Atoll Management Console, you must first upgrade the database to the same version as the current version of the database. This is required so that the Atoll Management console adds the required information to the database to make it upgradable to newer versions. To upgrade the database: 1. Before installing the new version of Atoll, install the Atoll Management Console (if not already installed) compatible with the existing version of Atoll. 2. Upgrade the database (as described in "Upgrading Existing Databases" on page 50) 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 48. 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 50), 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 registery 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 recognize 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 recognize obsolete or deleted fields in the following upgrades. Upgrading Databases Manually This procedure is for information only. It should used if and only if, for some reason, automatic upgrade of the database using the Atoll Management Console is not possible. Using the previous Atoll version: a. Create a new document from the database. b. Disconnect the document from the database. c. Save and close the document. Using the new Atoll version: d. Open the disconnected document of the previous Atoll version. e. Atoll upgrades the document data structure to make it compatible with the new version. f. Create a new database as explained in "Creating a New Database Using Atoll" on page 49. If you are upgrading your database using a script based on the data structure modifications listed in Part 3 of the Administrator Manual, you must also 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 48.
52
AT310_AM_E2
For example, you may have a country-wide master database and more than one regional project databases. End-users can here work with their local regions project database, and would not have to unnecessarily load country-wide data.
Figure 5.4: 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.5: 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 may be created with copies of the entire master database or a part of the master database corresponding to a given physical location or region. 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 countrys database to be loaded.
Project databases may be created using filters on sites, thus allowing users to work with regional databases. A possible scenario is depicted in the figure below:
53
Forsk 2011
Figure 5.6: Multiple Project Databases From a Single Master Database Multi-level databases may be set up using the Atoll Management Console with Oracle. In this section, the following are explained: "Creating Project Databases" on page 54 "Archiving Project Databases to Master Databases" on page 56 "Refreshing Project Databases from Master Databases" on page 57
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 wish to create a project database. The context menu appears. 2. Select Create a Project Database. The Project Database Creation Wizard dialogue appears. 3. Click Next. The Specify the server and the owner of the project database page appears. 4. Select the Destination server for the project database. 5. Under Owner, select Current user if you wish to create the new project database using the current user, or select Create a new user and enter a User name and Password to create a new user that will be owner of the new project database. Some versions of Oracle let you create a new user through this dialogue but the new user is not assigned DBA rights, which makes the new user unable to create the project database. Therefore, it is recommended to create the new user with DBA rights directly in the database before create the project database using the Atoll Management Console using the new user account. 6. Click Next. The Name the database page appears. 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
54
AT310_AM_E2
Select this option if you wish to create a project database that contains all the data of the master database. Include a site list contained in the master database Select this option if you wish 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 wish 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 wish 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.7: 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: Field NAME MASTER_CONNECTION MASTER_DBSCHEMA SEL_METHOD SEL_PARAM SEL_PGON Type Text (50) Text (255) Text (50) Short Text (255) Memo Description The name of the project database Connection parameters to the master database The name of the original schema of the master database Data extraction method used to select the sites to include in the project database Site selection method parameters (the SQL condition, if any) Site selection polygon (if used)
55
Forsk 2011
You can view the details stored in the ATOLL_ADMIN_PRJ table in the project database properties. To view the above details of a project database: 1. In the right pane, right-click the project database in the list. The context menu appears. 2. Select Properties. The database Properties dialogue appears. 3. The Properties dialogue contains three tabs: General tab: The General tab displays the Name, Description, Owner, Type, and Version of the database. Project Database tab: Under Source master database, the Project Database tab displays the Connection settings to and the Owner of the master database. Under Site selection, this tab displays the site filtering Method and Settings used for creating the project database. Statistics tab: The Statistics tab displays the number of records in each table of the project database.
The project database contains a copy of all the original tables of the master database. The names of the original tables are prefixed with "O_". For example, the ANTENNAS table of the master database is stored in the project database under the name O_ANTENNAS. The COORDSYS and UNITS are not copied to the project database because their contents cannot be different from those of the master database. All the tables in a project database contain a non-modifiable, integer O_RECORD_ID field and a Boolean O_CHANGED field. The O_RECORD_ID field is used to locate records in the master database. Modified records are archived in master database using the O_RECORD_ID of the project database and DB_RECORD_ID of the master database. The O_CHANGED field is set to TRUE for records modified in the project database.
56
AT310_AM_E2
Under Errors, Atoll Management Console displays errors that occurred during archive. 4. Once archive is complete, click Close.
1. Click OK. The project database is refreshed with data from the master database.
57
Forsk 2011
Tracked Tables Sites, Transmitters, CDMACells, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt Sites, Transmitters, WCells, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt Sites, MWLinks, MWHubs, MWPMP, MWMultiHops, MWMultiHopsLinks, MWRepeaters
You can, however, enable or disable history management for table as required (see "Enabling/Disabling Data Modifications History Management" on page 59 for more information). If you wish, you can also purge old data modifications history (see "Purging Old Data Modifications History" on page 60 for more information). The history management tool is available for Oracle databases. The following section describes how to set up the history management tool for an Oracle database using the Atoll Management Console.
The above fields are also added to all the tracked tables in order to store information about the latest modification. Therefore, opening any tracked table, you can see when a record was last modified, by whom, and the type of modification. To set up data modifications history management for a database: 1. In the Atoll Management Console window, in the right pane, right-click the database for which you wish to set up data modifications history management. The context menu appears. 2. Select Manage Data Modifications History. The Data Modifications History Management dialogue appears. 3. Click Yes when asked whether you wish 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 dialogue (Figure 5.9 on page 59). This dialogue lists all the tables for which the data modifications history management has been enabled, the total numbers of records in these tables, and the status of the history management. All the modifications made in the tables listed in "Managing Data Modifications History" on page 57 are stored in the history tables added to the database. If you wish, you can disable the data modifications history management for any table. For more information, see "Enabling/ Disabling Data Modifications History Management" on page 59.
58
AT310_AM_E2
59
Forsk 2011
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.
Figure 5.10: Record Purge Dialogue 5. Under Purge data modifications recorded before, move the slider to select from which date onwards you wish to keep the data modification history records. All the data modification history records before this date will be deleted. Number of records shows the number of records that will be left after the purge. Data size shows the size of the records that will be left after the purge. 6. Under Options, select the Keep creation and deletion records check box if you wish to keep the records of creation and deletion. 7. Click Purge. All the history records before the selected date are deleted from the history table. If you selected the Keep creation and deletion records check box, creation and deletion records before the selected date are not deleted.
60
AT310_AM_E2
4. Create a tablespace called "Atoll". 5. Create a project account. To create a project account: a. Run DBA Studio on the database server (or a client computer with Oracle administration tools). b. Open the Add Database to Tree dialogue. c. In the Add Database To Tree dialogue, select Add selected databases from your local tnsnames.ora file. d. Select the "AtollDB" service. e. Open the connection dialogue for the "AtollDB" service. f. Enter Username = "system" and Password = "manager".
g. To create a new user, right-click the User folder in the Security folder and select Create. h. Create a new user (project account) with administrator rights and privileges. i. Specify "Atoll" as the default tablespace and choose DBA for its privileges.
This account will be used to create Atoll document tables and will be the owner of these tables. It is usually helpful to assign a name to the project account that indicates the type of project that you want to store (GSM, UMTS, etc.).
6. Create database tables in the empty database "AtollDB" using the project account created in step 5.. For more information, see "Creating a New Database Using Atoll" on page 49. 7. Create user accounts. To create a project account: a. Run DBA Studio on the database server (or a client computer with Oracle administration tools). b. Open the Add Database to Tree dialogue. c. In the Add Database To Tree dialogue, select Add selected databases from your local tnsnames.ora file. d. Select the "AtollDB" service. e. Open the connection dialogue for the "AtollDB" service. f. Log on with the project account.
g. To create a new user, right-click the User folder in the Security folder and select Create. h. Create new user accounts with appropriate rights and privileges. These user accounts do not own tables, but only specify the access rights to the tables owned by the project account. i. Specify "Atoll" as the default tablespace for the new user accounts.
The database will be accessible through any of the user accounts from any client computer. In some cases, Atoll displays too many decimal values for fields of type "Float" in documents connected to Oracle databases. This type of display is not due to any error in Atoll. You can fix this problem by: In Atoll, setting the display precision of floating point values the Atoll.ini option described in "Setting the Display Precision of Floating Point Values" on page 175. In Oracle, If the database is new and the fields are empty, changing the field type from Float to Number and fix the number of decimal values for it in Oracle. If the database fields contain data, updating the field data by rounding the values stored in them: UPDATE TABLE_NAME SET FIELD_NAME = ROUND(FIELD_NAME,2);
Once this is done, you have to refresh document data from the database in order to fix the display problem in Atoll.
61
Forsk 2011
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.
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.
62
AT310_AM_E2
SQL > rename SITES to PRIVATE_SITES; 3. Create a POSTCODETABLE table to link users and postcodes (one user may 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.
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, SQL Server, or Sybase: 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.
63
Forsk 2011
4. Export the GSM document to the database by entering the user name and password for GSMUser. 5. Log in as GSMUser to the database. 6. Delete the Sites table. 7. Open the UMTS document in Atoll. 8. Export the UMTS document to the database by entering the user name and password for UMTSUser. 9. Log in as UMTSUser to the database. 10. Right-click the Sites table and select Create a View from the context menu. The Create View dialogue appears. a. Enter Sites as the view name. b. Enter GSMUser as the name of the schema which will contain the view. c. Select Table as object type. d. Enter UMTSUser as the name of the schema you want to use. e. Select Sites as the object used to model the view. 11. Click Create. The view of the Sites table from UMTSUser is created in GSMUser. The GSMUser Sites table is now the same as UMTSUser Sites table. 12. Set up user privileges for the Sites view in GSMUser to allow each user to Import, Update, Delete, and Select. To set up a shared Sites table for a GSM-UMTS co-planning project in Microsoft Access: 1. Make backups of the GSM and UMTS documents. 2. Open the GSM document in Atoll. 3. Delete all the transmitters from the Transmitters table and all the sites from the Sites table. 4. Export the GSM document to a Microsoft Access database (GSM.mdb). 5. Open GSM.mdb in Microsoft Access. 6. Delete the Sites table. 7. Open the UMTS document in Atoll 8. Export the UMTS document to a Microsoft Access database (UMTS.mdb). 9. Open GSM.mdb in Microsoft Access. 10. In Microsoft Access 2003 and earlier, select File > Get External Data > Link Tables. In Microsoft Access 2007 and later, select External Data > Access Database. 11. In Microsoft Access 2003 and earlier, the Link dialogue appears. Select UMTS.mdb. In Microsoft Access 2007 and later, the Get External Data - Access Database dialogue appears, specify UMTS.mdb as data source and select Link to data source by creating a linked table. 12. Click OK. The Link Tables dialogue appears. 13. Select the Sites table. 14. Click OK. Microsoft Access creates a Sites table in GSM.mdb which is linked to the Sites table in UMTS.mdb. The tables contain the same data. Once the linked Sites table has been created in the GSM database, you have to define the relations of this table with the other tables in the database. Figure 13.1 on page 231 shows the relations of the Sites table with other tables in a GSM database. The UMTS Sites table has more fields compared to the GSM Sites table. Therefore, we propose to replace the GSM Sites table with the UMTS one.
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 may create inconsistencies between the two networks. To ensure database consistency, you may 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.
64
AT310_AM_E2
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 may work on specific parts of a common, large-scale project. For example, different user groups may work on different regions of a country-wide network. In this chapter, the following are explained: "Setting Up Multi-user Environments" on page 65 "Components of Multi-user Environments" on page 65 "Managing User Accounts and Access Rights" on page 67
65
Forsk 2011
In this section, the following are explained: "Master Atoll Document" on page 66 "Master Database" on page 66 "Shared Geographic Data" on page 66 "Shared Path Loss Matrices" on page 67 "User Atoll Documents" on page 67
66
AT310_AM_E2
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.
67
Forsk 2011
Field RIGHTS
Type Memo
Each users 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 68. 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 users interface access rights are set to read-only by default (for more information, see "Defining Database and Interface Access Rights" on page 68). If the user is listed in the GUIUserRights table, his interface access rights are read and applied to the Atoll interface (table grids and properties dialogues). A message is displayed in the Event Viewer window to inform the user of his interface access rights. It is possible to remove interface access restrictions by disconnecting the document from the database. However, a disconnected document cannot be reconnected to the database. The GUIUserRights table is also stored in the Atoll document, and is updated when the document is saved. Hence, users can work on their documents without actually being connected to the database, and still have their usual interface access rights applied in the document. Atoll does not ask for the user name and password when a document is opened using the API. The interface access rights stored in the document are used.
When database connection properties are modified for a document, for example, when a different user enters his user name and password in the connection properties, Atoll reads and applies the interface access rights defined for the new user.
Figure 6.2: User Account and Access Rights Management Dialogue 3. Under Atoll projects, select the project for which you want to manage user accounts. 4. Under List of users, select the user account whose database and interface access rights you want to set.
68
AT310_AM_E2
Users who have database access rights in the selected database are marked with the green icon ( ). Users who do not have any database access rights in the selected database (Category = No Access) are marked with the red icon ( ). Locked (deactivated) user accounts are marked with a yellow lock icon ( ). For more information on locked user accounts, see "Creating and Editing User Accounts" on page 69. You can use the Filter list to display: All users: Users with access ( ), without access ( ), or locked ( )
Users with access ( ) Administrators: Users with administrator rights among the users with access Standard users: Users with standard rights among the user with access Read-only users: Users with read-only access rights among the users with access
5. Under Database rights, you can select a database access Rights category: No access: User without read and write access to the database. The database is not visible to these users and they are not allowed to create Atoll documents based on this database. Read-only: Users allowed to create Atoll documents from the database but without write permissions to any table of the database, i.e., users cannot archive changes made in the Atoll document to the database. Standard: Users with read and write access to some tables of the database. These tables include radio network data tables including sites, transmitters, cells, subcells, repeaters, remote antennas, secondary antennas, intraand inter-technology neighbours and exceptional pairs, site and transmitter lists, microwave point-to-point, pointto-multipoint, and multi-hop links, microwave repeaters, microwave hubs. Administrator: Users with read and write access to all the tables of the database.
Database access rights are stored in the user account properties in Oracle. If you are working with an RDBMS other than Oracle, you will not be able to set database access rights. You can, however, still set interface access rights as explained below. 6. Under Interface rights, you can select interface access rights for: Access to radio data: Full: (RADIOPARAMS = ALL) Users with read and write access to all the tables and properties dialogues. Standard: (RADIOPARAMS = STD) Users with read and write access to radio network data tables and properties dialogues including sites, transmitters, cells, subcells, repeaters, remote antennas, secondary antennas, intra- and inter-technology neighbours and exceptional pairs, site and transmitter lists, microwave point-to-point, point-to-multipoint, and multi-hop links, microwave repeaters, microwave hubs. Read-only: (RADIOPARAMS = NONE) Users with read-only access to tables and properties dialogues, i.e., users are not allowed to modify radio network data and parameters. Database access rights and access rights to radio data in Atoll can be set independently. For example, a user may have full access rights in the interface but not 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 predictions: All: (CALCPARAMS = ALL) Users with read and write access to all coverage predictions and their properties. Standard: (CALCPARAMS = STD) Users with access to customised coverage predictions only, and allowed to modify coverage conditions and display settings. Customised only: (CALCPARAMS = NONE) Users with access to customised coverage predictions only, but not allowed to modify coverage conditions and display settings. 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.
7. Click OK. The database and interface access rights of the selected user are saved in the database.
69
Forsk 2011
To manage user accounts: 1. In the Atoll Management Console window, right-click the database whose user accounts you want to manage. 2. Select Manage Users. The User Management dialogue appears (see Figure 6.2 on page 68). 3. To create a new user account: a. Under Users, click Create. The Create/Edit User dialogue appears (Figure 6.3 on page 70). b. Under Identification, enter a User name (in block letters) and Password, and select a Tablespace for the new user account. c. Under Advanced, select Use operating system authentication if you want to use OS authentication prefix with the user name, and Unlimited tablespace privilege if you want to assign this system privilege to the user. d. Click OK. The new user account is created. 4. To edit a user account: a. Under List of users, select the user account whose information you want to edit. b. Under Users, click Edit. The Create/Edit User dialogue appears (Figure 6.3 on page 70). c. Under Identification, modify the users Password or assigned Tablespace. d. Under Advanced, select Use operating system authentication if you want to use OS authentication prefix with the user name, and Unlimited tablespace privilege if you want to assign this system privilege to the user. e. Click OK. The modified user account information is saved. 5. To deactivate (lock) a user account: a. Under List of users, select the user account you want to deactivate. b. Under Users, click Edit. The Create/Edit User dialogue appears (Figure 6.3 on page 70). c. Under Advanced, select Account locked check box. d. Click OK. The user account is deactivated and can no longer be used. 6. To delete a user account: a. Under List of users, select the user account you want to delete. b. Under Users, click Delete. The user account is deleted.
6.4 Appendices
The following appendices provide additional information on: "Appendix 1: Checking Data Integrity" on page 71 "Appendix 2: Database Regionalisation" on page 71 "Appendix 1: Checking Data Integrity" on page 71
70
AT310_AM_E2
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
71
Forsk 2011
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).
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.
72
AT310_AM_E2
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 73 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.
73
Forsk 2011
74
Part 2
Reference
This part of the administrator manual provides recommendations and information on Atoll configuration and initialisation files. In this part, the following are explained: "Administration and Usage Recommendations" on page 129 "Configuration Files" on page 141 "Initialisation Files" on page 169
AT310_AM_E2
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)
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.
77
Forsk 2011
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.
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.
78
AT310_AM_E2
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.
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 82). 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.
79
Forsk 2011
Unit Codes Code 0 1 2 3 4 5 6 7 -1 Datum Codes Code 121 125 126 130 131 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 221 222 223 224 225 226 227 228 229 230 Datum Greek Geodetic Reference System 1987 Samboja Lithuania 1994 Moznet (ITRF94) Indian 1960 Adindan Australian Geodetic Datum 1966 Australian Geodetic Datum 1984 Ain el Abd 1970 Afgooye Agadez Lisbon Aratu Arc 1950 Arc 1960 Batavia Barbados Beduaram Beijing 1954 Reseau National Belge 1950 Bermuda 1957 Bern 1898 Bogota Bukit Rimpah Campo Inchauspe Cape Carthage Chua Corrego Alegre Cote d'Ivoire Deir ez Zor Douala Egypt 1907 European Datum 1950 Code 260 261 262 263 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 Datum Manoca Merchich Massawa Minna Monte Mario M'poraloko North American Datum 1927 NAD Michigan North American Datum 1983 Nahrwan 1967 Naparima 1972 New Zealand Geodetic Datum 1949 NGO 1948 Datum 73 Nouvelle Triangulation Franaise NSWC 9Z-2 OSGB 1936 OSGB 1970 (SN) OS (SN) 1980 Padang 1884 Palestine 1923 Pointe Noire Geocentric Datum of Australia 1994 Pulkovo 1942 Qatar Qatar 1948 Qornoq Loma Quintana Amersfoort RT38 South American Datum 1969 Sapper Hill 1943 Schwarzeck Segora Cartographic Units Metre Kilometre Foot Link Chain Yard Nautical mile Mile Unspecified -1 Unspecified Code 100 101 102 103 104 Geographic Units Radian Degree Grad ArcMinute ArcSecond
80
AT310_AM_E2
Code 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 247 248 249 250 251 252 253 254 255 256 257 258
Datum European Datum 1987 Fahud Gandajika 1970 Garoua Guyane Francaise Hu Tzu Shan Hungarian Datum 1972 Indonesian Datum 1974 Indian 1954 Indian 1975 Jamaica 1875 Jamaica 1969 Kalianpur Kandawala Kertau La Canoa Provisional South American Datum 1956 Lake Leigon Liberia 1964 Lome Luzon 1911 Hito XVIII 1963 Herat North Mahe 1971 Makassar European Reference System 1989
Code 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 322 326 901 902 903
Datum Serindung Sudan Tananarive 1925 Timbalai 1948 TM65 TM75 Tokyo Trinidad 1903 Trucial Coast 1948 Voirol 1875 Voirol Unifie 1960 Bern 1938 Nord Sahara 1959 Stockholm 1938 Yacare Yoff Zanderij Militar-Geographische Institut Reseau National Belge 1972 Deutsche Hauptdreiecksnetz Conakry 1905 WGS 72 WGS 84 Ancienne Triangulation Franaise Nord de Guerre NAD 1927 Guatemala/Honduras/Salvador (Panama Zone)
Projection Method Codes Code 0 1 2 3 4 5 6 7 Ellipsoid Codes Code 1 2 3 4 5 6 Name Airy 1830 Airy Modified 1849 Australian National Spheroid Bessel 1841 Bessel Modified Bessel Namibia Major Axis 6377563.396 6377340.189 6378160 6377397.155 6377492.018 6377483.865 Minor Axis 6356256.90890985 6356034.44761111 6356774.71919531 6356078.96261866 6356173.50851316 6356165.38276679 Projection Method Undefined No projection > Longitude / Latitude Lambert Conformal Conical 1SP Lambert Conformal Conical 2SP Mercator Cassini-Soldner Transverse Mercator Transverse Mercator South Oriented Code 8 9 10 11 12 13 14 Projection Method Oblique Stereographic New Zealand Map Grid Hotine Oblique Mercator Laborde Oblique Mercator Swiss Oblique Cylindrical Oblique Mercator UTM Projection
81
Forsk 2011
Name Clarke 1858 Clarke 1866 Clarke 1866 Michigan Clarke 1880 (Benoit) Clarke 1880 (IGN) Clarke 1880 (RGS) Clarke 1880 (Arc) Clarke 1880 (SGA 1922) Everest 1830 (1937 Adjustment) Everest 1830 (1967 Definition) Everest 1830 (1975 Definition) Everest 1830 Modified GRS 1980 Helmert 1906 Indonesian National Spheroid International 1924 International 1967 Krassowsky 1940 NWL 9D NWL 10D Plessis 1817 Struve 1860 War Office WGS 84 GEM 10C OSU86F OSU91A Clarke 1880 Sphere
Major Axis 6378293.63924683 6378206.4 6378693.7040359 6378300.79 6378249.2 6378249.145 6378249.145 6378249.2 6377276.345 6377298.556 6377301.243 6377304.063 6378137 6378200 6378160 6378388 6378160 6378245 6378145 6378135 6376523 6378297 6378300.583 6378137 6378137 6378136.2 6378136.3 6378249.13884613 6371000
Minor Axis 6356617.98173817 6356583.8 6357069.45104614 6356566.43 6356515 6356514.86954978 6356514.96656909 6356514.99694178 6356075.41314024 6356097.5503009 6356100.231 6356103.03899315 6356752.31398972 6356818.16962789 6356774.50408554 6356911.94612795 6356774.71919530 6356863.01877305 6356759.76948868 6356750.52001609 6355862.93325557 6356655.84708038 6356752.27021959 6356752.31398972 6356752.31398972 6356751.51667196 6356751.61633668 6356514.96026256 6371000
Projection Parameter UTM zone number Longitude of origin Latitude of origin False Easting False Northing
Index 4 4 5 5 6
Projection Parameter Scale factor at origin Latitude of 1st parallel Azimuth of central line Latitude of 2nd parallel Angle from rectified to skewed grid
82
AT310_AM_E2
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 "<Customized>" in the Datum list. In this case, you must select an Ellipsoid and enter parameters (Dx, Dy, Dz, Rx, Ry, Rz, and S) needed for the transformation of the datum into WGS84. 6. Click OK. The new coordinate system is added to the selected coordinate system catalogue. To create a new coordinate system based on an existing system, select a coordinate system in the Coordinate Systems dialogue before clicking New in step 4. The new coordinate system is initialised with the values of the selected coordinate system.
7.2 Units
In the Atoll documents, you can define measurement units for reception, transmission, antenna gain, distance, height and offset, and temperature. You can accept the default measurement units, or you can change them using the document properties dialogue. Transmission and Reception Power Units Depending on the working environment, Atoll can use either one or two measurement units for the transmission/reception power. If you are working with stand-alone documents, i.e., documents not connected to databases, there is only one measurement unit used in Atoll for display. It corresponds to the transmission/reception power unit defined in the Atoll document. If you are working in a multi-user environment, Atoll uses two measurement units: A measurement unit for display in the Atoll document. It corresponds to the transmission/reception power unit defined in the current Atoll document. It is used for the display in the dialogues and in the tables, e.g., reception thresholds (coverage prediction properties, microwave link properties, etc.), and received signal levels (measurements, point analysis, coverage predictions, microwave link properties, etc.). An internal measurement unit for the database. The internal unit is the transmission/reception power unit stored in the database. It corresponds to the transmission/reception power unit used in the master Atoll document when the database is created. Users working in documents connected to a database can modify the transmission/reception power unit and save this change in their documents locally, but they cannot modify the internal power unit stored in the database. Only the administrator can modify it manually by editing the entry in the Units tables.
Antenna Gain Units Depending on the working environment, Atoll can use either one or two measurement units for the antenna gain. If you are working with stand-alone documents, i.e., documents not connected to databases, there is only one measurement unit used in Atoll for display. It corresponds to the antenna gain unit defined in the Atoll document. If you are working in a multi-user environment, Atoll uses two measurement units: A measurement unit for display in the Atoll document. It corresponds to the antenna gain unit defined in the current Atoll document and it is used for the display in the dialogues and in the tables. An internal measurement unit for the database. The internal unit is the antenna gain unit stored in the database. It corresponds to the antenna gain unit used in the master Atoll document when the database is created. Users working in documents connected to a database can modify the antenna gain unit and save this change in their documents locally, but they cannot modify the antenna gain unit stored in the database. Only the administrator can modify it manually by editing the entry in the Units tables.
Distance Units Atoll uses the distance unit defined in the current Atoll document as display unit of the distances in the dialogues, in the tables, and in the status bar. Metre is used as the internal measurement unit for the distance in all Atoll documents whether they are connected to databases or not. The internal measurement unit is not stored in the database and cannot be changed.
83
Forsk 2011
Height and Offset Units Atoll uses the height and offset unit defined in the current Atoll document as display unit of the heights and the offsets in the dialogues, 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.
If you are working in a multi-user environment, Atoll uses two type of formats: Display BSIC format for the Atoll document Internal BSIC format for the database
The display format is used for the display in dialogs and tables. You can set the display format for your document from the Transmitters folders 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.
84
AT310_AM_E2
8 Geographic Data
Atoll supports several geographic data types; DTM (Digital Terrain Model), clutter, scanned images, vector data, traffic maps, population, and custom geographic data. Atoll offers import/export filters for the most commonly used geographic data formats. The different filters are: File Format BIL TIFF Planet BMP DXF SHP MapInfo (MIF, TAB) Erdas Imagine (IMG) ArcView Grid (TXT) Atoll Geo Data (AGD) Vertical Mapper (GRD, GRC) ECW Import and Export in Atoll Both Both Both Both Import Both Both Import Export Both Both Import Geographic Data DTM, clutter classes, clutter heights, traffic maps, images, population, other DTM, clutter classes, clutter heights, traffic maps, images, population, other DTM, clutter classes, images, vector data DTM, clutter classes, clutter heights, traffic maps, images, population, other Vector data, vector traffic maps Vector data, vector traffic maps, population, other Vector data, vector traffic maps, population, other DTM, clutter classes, clutter heights, traffic maps, images, population, other DTM, clutter classes, clutter heights, traffic maps, images, population, other Vector data, vector traffic maps, population, other DTM, clutter classes, clutter heights, traffic maps, images, population, other Images Georeferencing Yes (via HDRfiles) Yes (via TFW files) Yes (via index files) Yes (via BPW or BMW files) Yes Yes Yes Yes Yes (embedded in the data file) Yes (embedded in the data file) Yes (embedded in the data file) Yes (via ERS files)
WLD files may be used for georeferencing for any type of binary raster file. 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.
85
Forsk 2011
Four points (hence, four altitude values) are necessary to describe a bin; these points are bin vertices. Therefore, a DTM file that contains N x N bins requires N2 points (altitude values).
Figure 8.2: Schematic view of a DTM file DTM file formats supported by Atoll are: BIL (32-bits integer and real, 16-bits integer, 8-bits integer) TIFF (16-bits integer, 8-bits integer) BMP (8-bits) Erdas Imagine (32-bits integer and real, 16-bits integer, 8-bits integer) Vertical Mapper (GRD, GRC) Planet (16-bits integer) Altitudes may differ within a bin. The method used to calculate altitudes in Atoll is described in the Technical Reference Guide. To display a DTM map, Atoll takes the altitude of the southwest point of each bin to assign a colour. In Atoll, DEM (Digital Elevation Model) is the same as Digital Terrain Model (DTM). In litterature, DEM and DTM may not have the same meaning. By definition, DEM refers to the altitude above sea level including ground and clutter, while DTM refers to the ground altitude above sea level alone.
Figure 8.3: Clutter Classes Atoll supports a maximum of 255 clutter classes (8 bits/pixel). A clutter classes file file that contains N x N bins requires N2 code values.
86
AT310_AM_E2
Clutter classes file formats supported by Atoll are: BIL (8-bits) TIFF (8-bits) BMP (8-bit) Erdas Imagine (8-bits) Vertical Mapper (GRD, GRC) Planet (16-bits) The clutter code is the same inside a bin.
User profile traffic maps based on user profile environments (raster traffic maps) support the following formats: BIL (8-bits) TIFF (8-bits) BMP (8-bits) Erdas Imagine (8-bits) Vertical Mapper (GRD, GRC) Planet (16-bits)
User density traffic maps (raster traffic maps) support the following formats: BIL (32-bits, 16-bits) TIFF (32-bits, 16-bits) BMP (32-bits, 16-bits) Erdas Imagine (32-bits, 16-bits) Vertical Mapper (GRD, GRC) Planet (16-bits integer)
87
Forsk 2011
8.6 Images
Images include air and satellite images. Images can be imported in Atoll for display and to provide information about the geographic environment. Image file formats supported by Atoll are: BIL (1, 4, 8, 24-bits) TIFF (1, 4, 8, 24-bits) BMP (1 to 24-bits) Erdas Imagine (1, 4, 8, 24-bits) Vertical Mapper (GRD, GRC) ECW (Enhanced Compressed Wavelet) (24 bits) Planet (1, 4, 8, 24-bits)
Population data vector file formats supported by Atoll are: MIF/TAB SHP Vertical Mapper (GRD, GRC) AGD
88
AT310_AM_E2
where keyword corresponds to an attribute type, and value defines the attribute value. Keywords required by Atoll are described below. Other keywords are ignored. nrows ncols nbands nbits Number of rows in the image. Number of columns in the image. Number of spectral bands in the image, (1 for DTM and 8 bit pictures). Number of bits per pixel per band; 8 or 16 for DTMs or Clutter heights (altitude in metres), 8 for clutter classes file (clutter code), 16 for path loss matrices (path loss in dB, field value in dBm, dBV and DBV/m).
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.
skipbytes Byte to be skipped in the image file in order to reach the beginning of the image data. Default value is 0. ulxmap ulymap xdim ydim x coordinate of the centre of the upper-left pixel. y coordinate of the centre of the upper-left pixel. x size in metre of a pixel. y size in metre of a pixel.
Four additional keywords may be optionally managed. pixeltype Type of data read (in addition to the length) This can be: UNSIGNDINT SIGNEDINT FLOAT Undefined Integer Real 8, 16, 24 or 32 bits 16 or 32 bits 32 or 64 bits
In some cases, this keyword can be replaced by datatype defined as follows: datatype This can be: Type of data read (in addition to the length)
89
Forsk 2011
Un In Rn RGB24
n bits (8, 16, 24 or 32 bits) n bits (16 or 32 bits) n bits (32 or 64 bits) 3 colour components on 24 bits
The other optional keywords are: valueoffset, valuescale, and nodatavalue. By default, integer data types are chosen with respect to the pixel length (nbits). valueoffset valuescale Real value to be added to the read value (Vread) Scaling factor to be applied to the read value
So, we have V = V read valuescale + valueoffset nodatavalue DTM Sample Here, the data is 20 m. nrows ncols nbands nbits 1500 1500 1 8 or 16 Value corresponding to NO DATA
90
AT310_AM_E2
Tiled TIFF format is not supported. You can modify the colour palette convention used by Atoll when exporting TIFF files. For more information, see "Setting the TIFF Colour Convention" on page 170. It is possible to import Packbit, FAX-CCITT3, and LZW compressed TIFF files. However, in case of DTM and clutter, it is recommended to use uncompressed files for better performance. Large uncompressed files can be split into smaller ones. If you are using compressed TIFF files, performance may be improved by either hiding the Status Bar or by hiding some of the information displayed in the Status Bar (altitude, clutter class, or clutter height). For more information, see "Hiding Information Displayed in the Status Bar" on page 179. Compressed TIFF files can be exported to uncompressed TIFF files using Atoll.
Atoll does not use the lines 2 and 3 when importing a TIFF format geographic file.
The following tables give exact information about the data structures. The Start-value is the position of the byte in the file at which the explained data element of the structure starts, the Size-value contains the number of bytes used by this data element, the Name column contains both generic name and the name assigned to this data element by the Microsoft API documentation, and the Description column gives a short explanation of the purpose of this data element. BITMAPFILEHEADER (Header - 14 bytes):
91
Forsk 2011
Start 1 3 7 9 11 Start 15 19 23 27
Size 2 4 2 2 4
Name Generic Signature FileSize Reserved1 Reserved2 DataOffset MS API bfType bfSize bfReserved1 bfReserved2 bfOffBits
Description Must always be set to 'BM' to declare that this is a BMP file Specifies the size of the file in bytes. Not used. Must be set to zero. Not used. Must be set to zero. Specifies the offset from the beginning of the file to the bitmap raster data.
BITMAPINFOHEADER (InfoHeader - 40 bytes): Size 4 4 4 2 Name Generic Size Width Height Planes MS API biSize biWidth biHeight biPlanes Description Specifies the size of the BITMAPINFOHEADER structure, in bytes (= 40 bytes). Specifies the width of the image, in pixels. Specifies the height of the image, in pixels. Specifies the number of planes of the target device, must be set to zero or 1. Specifies the number of bits per pixel. 1 = monochrome pallete. # of colours = 1 4 = 4-bit palletized. # of colours = 16 8 = 8-bit palletized. # of colours = 256 16 = 16-bit palletized. # of colours = 65536 24 = 24-bit palletized. # of colours = 16M Specifies the type of compression, usually set to zero. 0 = BI_RGB no compression 1 = BI_RLE8 8-bit RLE encoding 2 = BI_RLE4 4-bit RLE encoding Specifies the size of the image data, in bytes. If there is no compression, it is valid to set this element to zero. Specifies the the horizontal pixels per meter. Specifies the the vertical pixels per meter. Specifies the number of colours actually used in the bitmap. If set to zero the number of colours is calculated using the biBitCount element. Specifies the number of colour that are 'important' for the bitmap. If set to zero, all colours are considered important.
29
BitCount
biBitCount
31
Compression
biCompression
35 39 43 47 51 Start 1 2 3 4
4 4 4 4 4
RGBQUAD array (ColorTable): Size 1 1 1 1 Name Generic Blue Green Red Reserved MS API rgbBlue rgbGreen rgbRed rgbReserved Description Specifies the blue part of the colour Specifies the green part of the colour Specifies the red part of the colour Must always be set to zero
In a colour table (RGBQUAD), the specification for a colour starts with the blue byte, while in a palette a colour always starts with the red byte.
Pixel data: The interpretation of the pixel data depends on the BITMAPINFOHEADER structure. It is important to know that the rows of a BMP are stored upside down meaning that the uppermost row which appears on the screen is actually the
92
AT310_AM_E2
lowermost row stored in the bitmap. Another important thing is that the number of bytes in one row must always be adjusted by appending zero bytes to fit into the border of a multiple of four (16-bit or 32-bit rows).
Encoding type
4-bit 16 colour images 8-bit 256 colour images 16-bit High colour images 24-bit True colour images
16
24
The following table provides the description of the raster data compression for 8-bit, 256 colour images:
93
Forsk 2011
Description n pixels of colour number c End-of-line End-of-Bitmap Delta. The following 2 bytes define an unsigned offset in x and y direction (y being up). The skipped pixels should get a colour zero. The following c bytes will be read as single pixel colours just as in uncompressed files. A zero follows, if c is odd, putting the file/memory pointer on a 16-bit boundary again.
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
94
AT310_AM_E2
You can find more information at http://www.mapinfo.com. You can define mappings between the coordinate system used for the MapInfo vector files, defined in the corresponding MIF files, and Atoll. In this way, when you import a vector file, Atoll can detect the correct coordinate system automatically. For more information about defining the mapping between coordinate systems, see "Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Files" on page 172. TAB files are also supported as georeference information files for raster files (BMP and TIFF). The TAB file must have the following format: !table !version 300 !charset WindowsLatin1 Definition Table File "raster.bmp" Type "RASTER"
95
Forsk 2011
(ulxmap,ulymap) (0,0) Label "Pt 1", (llxmap,llymap) (0,nrows) Label "Pt 2", (lrxmap,lrymap) (ncols,nrows) Label "Pt 3", (urxmap,urymap) (ncols,0) Label "Pt 4" The fields in bold are described below: Field File "raster.bmp" ulxmap ulymap llxmap llymap lrxmap lrymap urxmap urymap nrows ncols Description Name of the raster file (e.g., raster.bmp) x coordinate of the centre of the upper-left pixel in metres y coordinate of the centre of the upper-left pixel in metres x coordinate of the centre of the lower-left pixel in metres y coordinate of the centre of the lower-left pixel in metres x coordinate of the centre of the lower-right pixel in metres y coordinate of the centre of the lower-right pixel in metres x coordinate of the centre of the upper-right pixel in metres y coordinate of the centre of the upper-right pixel in metres Number of rows in the image Number of columns in the image
For image files, the number of supported bands is either 1 (colour palette is defined separately) or 3 (no colour palette but direct RGB information for each pixel). In case of 3 bands, only 8 bit per pixel format is supported. Therefore, 8-bit images, containing RGB information (three bands are provided: the first band is for Blue, the second one is for Green and the third for Red), can be considered as 24 bit per pixel files. 32 bit per pixel files are not supported. If you are using compressed Erdas Imagine files, performance may be improved by either hiding the Status Bar or by hiding some of the information displayed in the Status Bar (altitude, clutter class, or clutter height). For more information, see "Hiding Information Displayed in the Status Bar" on page 179. Compressed files can be exported to uncompressed files using Atoll.
96
AT310_AM_E2
Classified grids, which contain alphanumeric (characters) information, and are stored in files with the GRC extension.
Atoll is capable of supporting the Vertical Mapper Classified Grid (GRC) and Vertical Mapper Continuous Grid (GRD) file formats in order to import and export: GRD: DTM, image, population, traffic density, and other data types. GRC: DTM, clutter classes, clutter heights, environment traffic, image, population, and other data types.
It is also possible to export coverage predictions in GRD and GRC formats. This is the geographic data format used by Planet EV. So, it is possible to directly import geographic data from Planet EV to Atoll using this format.
nodata_value XXXOptional value corresponding to no data (no information). //Row 1 Top of the raster. Description of the first row. Syntax: ncols number of values separated by spaces. : : //Row N Sample ncols 303 nrows 321 xllcorner 585300.000000 yllcorner 5615700.000000 cellsize 100.000000 nodata_value 0 ... Bottom of the raster.
97
Forsk 2011
Line 1 2 3 4 5 6 Clutter Classes File Sample 100.00 0.00 0.00 -100.00 60000.00 2679900.00
Description x dimension of a pixel in map units amount of translation amount of rotation negative of the y dimension of a pixel in map units x-axis map coordinate of the centre of the upper-left pixel y-axis map coordinate of the centre of the upper-left pixel
The projection file provides information about the projection system used. This file is optional. It is an ASCII text file with four lines maximum. Line Spheroid Zone Description
Projection Central meridian Latitude and longitude of projection central meridian and equivalent x and y coordinates in meters (optional)
In the associated binary file, the value -9999 corresponds to No data which is supported by Atoll.
Sample Index file associated with height file (DTM data): sydney1 303900 343900 6227900 6267900 50
98
AT310_AM_E2
Projection file associated with height file (DTM data): Australian-1965 56 UTM 0 153 500000 10000000
The index file gives clutter spatial references. The structure of clutter index file is the same as the structure of DTM index file. In the associated binary file, the value -9999 corresponds to No data which is supported by Atoll.
Sample Menu file associated with the clutter file: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 open sea inlandwater residential meanurban denseurban buildings village industrial openinurban forest parks denseurbanhigh blockbuildings denseblockbuild rural mixedsuburban
99
Forsk 2011
The fields are separated by space character. The index file, an ASCII text file, lists the vector files and associates each vector file with one vector type, and optionally with one attribute file. The index file consists of one or more records with the following structure: Field Vector file name Attribute file name Dimensions Type Text (32) Text (32) Description Name of the vector file Name of attribute file associated with the vector file (optional) eastmin: minimum x-axis coordinate of all vector path points in the vector file eastmax: maximum x-axis coordinate of all vector path points in the vector file northmin: minimum y-axis coordinate of all vector path points in the vector file northmax: maximum y-axis coordinate of all vector path points Name of the vector type with which the vector file is associated. This one must match exactly a vector type name field in the menu file.
Real
Text (32)
The fields are separated by spaces. Sample Index file associated with the vector files sydney1.airport 313440 333021 6239426 6244784 airport sydney1.riverlake 303900 342704 6227900 6267900 riverlake sydney1.coastline 322837 343900 6227900 6267900 coastline sydney1.railways 303900 336113 6227900 6267900 railways sydney1.highways 303900 325155 6240936 6267900 highways sydney1.majstreets 303900 342770 6227900 6267900 majstreets sydney1.majorroads 303900 342615 6227900 6267900 majorroads The attribute file stores the height and description properties of vector paths. This file is optional.
Airport 637111.188 3094774.00 Airport 628642.688 3081806.25 Each file contains a line of text followed by easting and northing of that text, etc. The index file, an ASCII text file, stores the position of each text file. It consists of one or more records with the following structure: Field File name East Min East Max Type Text (32) Real Real Description File name of the text data file Minimum x-axis coordinate of all points listed in the text data file Maximum x-axis coordinate of all points listed in the text data file
100
AT310_AM_E2
Description Minimum y-axis coordinate of all points listed in the text data file Maximum y-axis coordinate of all points listed in the text data file This field is omitted in case no menu file is available.
The fields are separated by spaces. railwayp.txt -260079 693937 2709348 3528665 Railway_Station airport.txt -307727 771663 2547275 3554675 Airport ferryport.txt 303922 493521 2667405 3241297 Ferryport 1 2 3 The menu file, an ASCII text file, contains the text features. This file is optional. Airport Ferryport Railway_Station
Either space or tab can be used as the separator. Clutter Classes Sample An MNU file associated to a clutter classes file: 0 1 2 3 4 5 none open sea inland_water residential meanurban
101
Forsk 2011
102
AT310_AM_E2
When XML files are imported to a document, the table and field definitions are not modified, i.e., the Networks and CustomFields tables are exported to XML file but are not imported. The following sections describe the structures of the XML files created at export.
The index file also contains the mapping between the tables exported from Atoll and the XML files corresponding to each table. This list is sorted in the order in which tables must be imported in Atoll. The list is composed of <XML_Table.../> tags with the following attributes: Attribute XML_File Atoll_Table Description Corresponds to the exported XML file name (e.g., "Sites.xml") Corresponds to the exported Atoll table name (e.g., "Sites")
103
Forsk 2011
<Atoll_XML_Config Atoll_File_System="UMTS" Atoll_File_Technology="CDMA" Atoll_File_Version="3.x.x build xxxx"> <XML_Table XML_File="CustomFields.xml" Atoll_Table="CustomFields" /> <XML_Table XML_File="CoordSys.xml" Atoll_Table="CoordSys" /> ... </Atoll_XML_Config> Note that no closing tag </XML_Table> is required.
104
AT310_AM_E2
<s:AttributeType name='ALTITUDE' rs:number='4' rs:nullable='true' rs:maydefer='true' rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='ALTITUDE'> <s:datatype dt:type='r4' dt:maxLength='4' rs:precision='7' rs:fixedlength='true'/> </s:AttributeType> <s:AttributeType name='COMMENT_' rs:number='5' rs:nullable='true' rs:maydefer='true' rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='COMMENT_'> <s:datatype dt:type='string' dt:maxLength='255'/> </s:AttributeType> <s:extends type='rs:rowbase'/> </s:ElementType> </s:Schema> <rs:data> <rs:insert> <z:row NAME='Site0' LONGITUDE='8301' LATITUDE='-9756'/> </rs:insert> </rs:data> </xml>
The format of 2D antenna patterns containing co-polar and cross-polar diagrams can be understood from Figure 9.2 on page 106.
105
Forsk 2011
Pattern Discriptor 1
Pattern Discriptor 2
Pattern Discriptor 3
Pattern Discriptor 4
You may use a 3rd party software or develop a tool to to convert the contents of the DIAGRAM field into binary. In binary, each antenna is described by a header and a list of value pairs. The header is defined as follows: flag: (Integer, 32 bits) -1 for omni diagrams, 0 for directional num: (Short integer, 16 bits) Number of diagrams (0, 1, 2, 3, 4) siz0: (Short integer, 16 bits) Size of the first diagram (horizontal co-polar section, elevation = 0) siz1: (Short integer, 16 bits) Size of the second diagram (vertical co-polar section, azimuth = 0) siz2: (Short integer, 16 bits) Size of the third diagram (horizontal cross-polar) siz3: (Short integer, 16 bits) Size of the fourth diagram (vertical cross-polar) prec: (Short integer, 16 bits) Precision of the following angle values (100)
Then follows the content of each of the defined diagrams, i.e., the diagrams whose sizes (siz0, siz1, siz2, siz3) are not zero. Each diagram consists of a list of value pairs. The number of value pairs in a list depends on the value of the siz0, siz1, siz2, and siz3 parameters. For example, siz2 = 5 means there are five value pairs in the third diagram. The value pairs in each list are: ang: (Short integer, 16 bits) The first component of the value pair is the angle in degrees multiplied by 100. For example, 577 means 5.77 degrees. loss: (Short integer, 16 bits) The second component of the value pair is the loss in dB for the given angle ang.
106
AT310_AM_E2
Pattern Discriptor 3
Pattern Discriptor 4
Pattern Discriptor 5
Pattern Discriptor 6
Pattern Discriptor 7
Pattern Discriptor 8
4 0 1 0 360 0 0 1 0.5 ... 0 0 0 360 0 0 1 0.5 ... 1 1 0 360 0 0 1 0.5 ... 1 0 0 360 0 0 1 0.5 ... 4 0 1 0 360 0 0 1 0.5 ... 0 0 0 360 0 0 1 0.5 ... 1 1 0 360 0 0 1 0.5 ... 1 0 0 360 0 0 1 0.5 ...
Figure 9.3: 2D Microwave Antenna Pattern Format The contents of the PATTERN field are formatted as follows: Pattern Descriptor 1: Space-separated list of parameters. First entry: The number of co-polar diagrams. For example, 4. Second and third entries: First co-polar diagram type = 0 1, for H-V diagram. Fourth entry: The elevation angle of the azimuth diagram. Fifth entry: The number of angle-attenuation pairs in the first co-polar diagram. For example, 360. Co-polar H-V Diagram: Co-polar H-V diagram (the second and third entries in the preceding descriptor are 0 1). The format is space-separated angle attenuation pairs. For example, 0 0 1 0.5.... Pattern Descriptor 2: Space-separated list of parameters. First and second entries: Second co-polar diagram type = 0 0, for H-H diagram. Third entry: The azimuth angle of the elevation diagram.
107
Forsk 2011
Fourth entry: The number of angle-attenuation pairs in the second co-polar diagram. For example, 360.
Co-polar H-H Diagram: Co-polar H-H diagram (the first and second entries in the preceding descriptor are 0 0). The format is space-separated angle attenuation pairs. For example, 0 0 1 0.5.... Pattern Descriptor 3: Space-separated list of parameters. First and second entries: Third co-polar diagram type = 1 1, for V-V diagram. Third entry: The elevation angle of the azimuth diagram. Fourth entry: The number of angle-attenuation pairs in the third co-polar diagram. For example, 360. Co-polar V-V Diagram: Co-polar V-V diagram (the first and second entries in the preceding descriptor are 1 1). The format is space-separated angle attenuation pairs. For example, 0 0 1 0.5.... Pattern Descriptor 4: Space-separated list of parameters. First and second entries: Fourth co-polar diagram type = 1 0, for V-H diagram. Third entry: The azimuth angle of the elevation diagram. Fourth entry: The number of angle-attenuation pairs in the fourth co-polar diagram. For example, 360. Co-polar V-H Diagram: Co-polar V-H diagram (the first and second entries in the preceding descriptor are 1 0). The format is space-separated angle attenuation pairs. For example, 0 0 1 0.5.... Pattern Descriptor 5: Space-separated list of parameters. First entry: The number of cross-polar diagrams. For example, 4. Second and third entries: First cross-polar diagram type = 0 1, for H-V diagram. Fourth entry: The elevation angle of the azimuth diagram. Fifth entry: The number of angle-attenuation pairs in the first cross-polar diagram. For example, 360. Cross-polar H-V Diagram: Cross-polar H-V diagram (the second and third entries in the preceding descriptor are 0 1). The format is space-separated angle attenuation pairs. For example, 0 0 1 0.5.... Pattern Descriptor 6: Space-separated list of parameters. First and second entries: Second cross-polar diagram type = 0 0, for H-H diagram. Third entry: The azimuth angle of the elevation diagram. Fourth entry: The number of angle-attenuation pairs in the second cross-polar diagram. For example, 360. Cross-polar H-H Diagram: Cross-polar H-H diagram (the first and second entries in the preceding descriptor are 0 0). The format is space-separated angle attenuation pairs. For example, 0 0 1 0.5.... Pattern Descriptor 7: Space-separated list of parameters. First and second entries: Third cross-polar diagram type = 1 1, for V-V diagram. Third entry: The elevation angle of the azimuth diagram. Fourth entry: The number of angle-attenuation pairs in the third cross-polar diagram. For example, 360. Cross-polar V-V Diagram: Cross-polar V-V diagram (the first and second entries in the preceding descriptor are 1 1). The format is space-separated angle attenuation pairs. For example, 0 0 1 0.5.... Pattern Descriptor 8: Space-separated list of parameters. First and second entries: Fourth cross-polar diagram type = 1 0, for V-H diagram. Third entry: The azimuth angle of the elevation diagram. Fourth entry: The number of angle-attenuation pairs in the fourth cross-polar diagram. For example, 360. Cross-polar V-H Diagram: Cross-polar V-H diagram (the first and second entries in the preceding descriptor are 1 0). The format is space-separated angle attenuation pairs. For example, 0 0 1 0.5....
108
AT310_AM_E2
Field Date of data Manufacturer ID Number Frequency range Mid-band gain Half-power beam width
Length (Char) 16 16 16 16 16
Description Date referenced on the published pattern Reference number assigned by the antenna manufacturer. This is to identify the full frequency range for which this pattern is valid and agrees with the range as specified in the printed pattern. The frequency is in Megahertz. Gain of the antenna at mid-band (dBi) This is the included angle centered on the main beam of the antenna and defines the angle where the antenna response falls -3 dB The data is preceded by an indication of the polarization the data. The commonly accepted polarization designators for linear polarization are to be used: HH: Horizontal polarized port response to a horizontally polarized signal in the horizontal direction. HV: Horizontal polarized port response to a vertically polarized signal in the horizontal direction. VV: Vertical polarized port response to a vertically polarized signal in the horizontal direction VH: Vertical polarized port response to a horizontally polarized signal in the horizontal direction ELHH: Horizontal polarized port response to a horizontally polarized signal in the vertical direction ELHV: Horizontal polarized port response to a vertically polarized signal in the vertical direction ELVV: Vertical polarized port response to a vertically polarized signal in the vertical direction ELVH: Vertical polarized port response to a horizontally polarized signal in the vertical direction The data count will be the number of data points to follow. All eight responses should be included. If different polarizations have identical responses, they are to be duplicated in order that a full set of data be listed. Full compliment of data will show the antenna response in the horizontal direction for a 'horizontal cut' and in the vertical direction for a 'vertical cut'. The data is presented in two columns. The angle of observation is listed first followed by the antenna response. For the horizontal direction, the angle of observation starts from -180 degrees (defined as the left side of the antenna) and decrease in angle to the main beam , 0 degrees, and then increase to +180 degrees. The full data will cover the 360 degrees of the antenna. For the vertical direction, the angle of observation starts from -5 (-90) degrees (defined as the antenna response below the main beam) and decrease in angle to the main beam, 0 degrees, and then increase to +5 (+90) degrees. The full data will cover the 10 (180) degrees centered about the main beam. The antenna response is listed as dB down from the main lobe response and is shown as negative.
7 7
7 7
Sample MARK ANTENNA PRODUCTS Inc. MHP-100A120D (none) M15028 M15027 11-25-85 NONE 10700-11700 MHZ 48.4 dB 0.6 Deg HH 39
109
Forsk 2011
-180 -88 -160 -88 -150 -90 -97 -90 -66 -70 ... 160 -88 180 -88 HV 33 -180 -89 -170 -89 ... 180 -89 VV 39 -180 -88 -160 -88 ... 150 -90 160 -88 180 -88 VH 33 -180 -89 -170 -89 -160 -90 ... 180 -89 ELHH 7 -4 -36 -1.7 -30 ... 4 -36 ELHV 11 -4.5 -63.4 ... 4.5 -63.4 ELVV 7 -4 -36 ... 4 -36 ELVH 11 -4.5 -63.4 ... 4.5 -63.4
110
AT310_AM_E2
Field Revision Number Revision Date Comment1 Comment2 Antenna Manufacturer Model Number Pattern ID Number
Length (Char) 42 16 80 80 42 42 42
Description Version of this standard to which the pattern conforms Date of the current revision of the standard Field for comments on the current revision Field for comments on the current revision Name of the antenna manufacturer Full model number as used when the data was taken NSMA ID number Used when more than one file is associated with a specific antenna model number. This field will contain the particular file number and the total number of files associated with that model number. An example of such a case would be a dual band antenna with two pattern files associated with it. Orientation of the feed hook when looking from the back of the antenna in the direction of the mechanical boresite Used to describe the antenna and its characteristics Used to describe the antenna and its characteristics Used to describe the antenna and its characteristics Used to describe the antenna and its characteristics Used to describe the antenna and its characteristics Date the pattern data was taken Lower frequency of the operating bandwidth of the antenna (MHertz). If the antenna can be operated in two distinct frequency bands, then the performance of the antenna in each band shall be described in separate files. Upper frequency of the operating bandwidth of the antenna (MHertz). If the antenna can be operated in two distinct frequency bands, then the performance of the antenna in each band shall be described in separate files Gain unit Gain of the antenna at the low frequency of the frequency band. The gain is in units described in GUNITS Gain of the antenna at the mid frequency of the frequency band and may include a full bandwidth tolerance. The gain is in units described in GUNITS Gain of the antenna at high frequency of the frequency band. The gain is in units described in GUNITS Nominal total width of the main beam at the -3 dB points in the azimuth plane. This is a mid-band measurement expressed in degrees and may include a full bandwidth tolerance Nominal total width of the main beam at the -3 dB points in the elevation plane. This is a mid-band measurement expressed in degrees and may include a full bandwidth tolerance Description of the antenna connector type Worst case limit of the antennas VSWR over the operating bandwidth Worst case power level in dB between the main lobe peak and the peak of the antennas back lobe. The back lobe peak does not necessarily point 180 degrees behind the main lobe. Amount that the main beam peak of the antenna (electrical boresite) is dowtilted below the mechanical boresite of the antenna. This is a midband measurement and may include a tolerance. This measurement is expressed in degrees.
13
FILNUM
Feed Orientation Description1 Description2 Description3 Description4 Description5 Date of data Low Frequency (MHz)
13 80 80 80 80 80 16 21
21
HGHFRQ
15 12
GUNITS LWGAIN
16 12
MDGAIN HGGAIN
Mid-band Az Bmwdth
16
AZWIDT
16 80 13 10
16
ELTILT
111
Forsk 2011
Length (Char) 13
Description Height of the center of the radiating aperture above the mechanical bottom of the antenna (m). It is not necessarily the phase center of the antenna. Measurement made on dual polarization antennas. It is the maximum amount of power over the antennas operating bandwidth that is coupled between ports. It is the power ratio (dB) between a reference signal injected into one port and the amount of coupled power returned back out of the other port. Maximum amount of average RF input power which can be applied to each of the antennas input ports in the antennas operating frequency range (Watts). Mechanical length of the antenna (m). This does not include the antenna mount. For a circularly symmetric parabolic antenna this would be the diameter. Mechanical width of the antenna (m). This does not include the antenna mount. For a circularly symmetric parabolic antenna this would be the diameter. Mechanical depth antenna (m). This does not include the antenna mount. weight of the antenna in kg. This includes the antenna mount.
12
POTOPO
17
MAXPOW
14
ANTLEN
Antenna Width (m) Antenna Depth (m) Antenna Weight (kg) Future Field Future Field Future Field Future Field Future Field Pattern Type # Freq this file Pattern Freq (Mhz) # Pattern cuts Pattern Cut Polarization
14 14 16 80 80 80 80 80 16 10 21 11 11 15
ANTWID ANTDEP ANTWGT FIELD1 FIELD2 FIELD3 FIELD4 FIELD5 PATTYP NOFREQ PATFRE NUMCUT PATCUT POLARI
Pattern type, either typical or envelope. The number of pattern frequencies which comprise the full data set. Frequency of the pattern data for a typical pattern (MHz). Number of pattern cuts which comprise the full data set. Geometry of a particular pattern cut. Particular polarization of a pattern cut. The first polarization is the polarization of the antenna-under-test and the second the polarization of the illuminating source. The two polarizations are separated by a /. The number of data points in a particular pattern cut data set. The first and last angle (in degrees) of the antenna pattern data. Pattern data shall be expressed monotonically, with respect to angle. Azimuths shall be stated as either 180 to +180 or 0 to 360 degrees. A verbal description of the physical orientation of the x-axis on the antenna. A verbal description of the physical orientation of the y-axis on the antenna. A verbal description of the physical orientation of the z-axis on the antenna. The data is presented in three columns. The angle of observation is listed first followed by the antenna magnitude response and phase response. In most cases the phase response will not be included in the data set. S designates the sign of the number. The antenna power magnitude is listed in the units specified in the antenna units field (GUNITS). The angle and phase data are expressed in units of degrees.
13 25
NUPOIN FSTLST
53 53 53
28/point
End of file
11
ENDFIL
This field designates the end of the file with the characters EOF
112
AT310_AM_E2
Sample REVNUM:,NSMA WG16.99.050 REVDAT:,19990520 ANTMAN:,RADIO WAVES INC MODNUM:,HP4-64 DESCR1:,4 FT LOW SIDELOBE ANTENNA PATNUM:,9005 DTDATA:,20030807 LOWFRQ:,6425 HGHFRQ:,7125 GUNITS:,DBI/DBR LWGAIN:,35.5 MDGAIN:,35.9 HGGAIN:,36.3 AZWIDT:,2.8 ELWIDT:,2.8 ELTILT:,0 ANTLEN:,1.2, PATTYP:,ENVELOPE, NOFREQ:,NA, PATFRE:,NA, NUMCUT:,4, PATCUT:,AZ, POLARI:,H/H, NUPOIN:,29, FSTLST:,-180,180 -180,-60,
-100,-60,
-51,-42.3, ... PATCUT:,AZ, POLARI:,H/V, NUPOIN:,11, FSTLST:,-180,180 -180,-60, -22,-60, ... PATCUT:,AZ, POLARI:,V/V, NUPOIN:,33, FSTLST:,-180,180 -180,-60, ... PATCUT:,AZ, POLARI:,V/H, NUPOIN:,11, FSTLST:,-180,180 -180,-60,
113
Forsk 2011
... ENDFIL:,EOF,
114
AT310_AM_E2
Row "BRANCHING", Configuration, Transmitter loss, Main receiver loss, Protect receiver loss "MAX_RSL", Overflow threshold for 10-6 BER, Overflow threshold for 10-3 BER "DFM", DFM for 10-6 BER, DFM for 10-3 BER "TX_SPECTRUM", Number of points "CURVE_POINT", Frequency shift in MHz, Response in dBm/4Hz "TX_FILTER", "FCC_BANDWIDTH", FCC bandwidth "99%_BANDWIDTH", 99%power bandwidth "3DB_BANDWIDTH", 3dB bandwidth
Description System configuration and branching losses in dB Configuration may be:NP = not protected; MHSB = monitored hot standby; MHSD = monitored hot space diversity; FD = frequency diversity diversity; 1:M = multiline Maximum receive level in dBm (overflow threshold) Dispersive fade margin (dB) at the specified BER (digital radio only) Not used by Atoll Number of points used to define the transmitter mask graph Data points of the transmitter mask graph Not used by Atoll FCC channel bandwidth in MHz used to calculate the FCC spectrum mask - Not used by Atoll Bandwidth occupied by the transmitter in MHz (including 99% of the transmitted power) Bandwidth occupied by the transmitter in MHz (between the 3dB points) - Not used by Atoll
"T/T_FREQ_SEP", Same Antenna&Polarization, Same Minimum required frequency separation between two transmitters Antenna & Different Polarization, Different Antenna in MHz - Not used by Atoll & Polarization "T/R_FREQ_SEP", Same Antenna&Polarization, Same Antenna & Different Polarization, Different Antenna & Polarization "T/R_FIXED", T/R spacing #1, T/R spacing #2, etc., Minimum required frequency separation between the closest transmitter and receiver in MHz - Not used by Atoll Some radios only allow fixed transmit-receive frequency separations. If applicable, show all allowable frequency separations in MHz - Not used by Atoll Number of points used to define the Threshold-to-Interference (T/I) graph. The interfering transmitter and victim receiver are the same type of radio, using the same modulation and data rate. Data points of the T/I graph Number of points used to define the Threshold-to-Interference (T/I) graph. The interfering transmitter is a CW tone and the victim receiver is a digital radio. This T/I curve is used to model FM transmitters interfering into digital receivers - Not used by Atoll Data points of the T/I graph - Not used by Atoll Other capacity radio into specified radio RADIO_ID refers to the Radio Identification of the interfering transmitter. Interferor Bandwidth shall correspond to the FCC or ITU emission bandwidth of the interferor, specified as a real number in MHz. Data points of the T/I graph Baseband frequency range in kHz (analog radio only) - Not used by Atoll Number of points used to define the receiver mask graph Data points of the receiver mask graph Not used by Atoll Not used by Atoll Not used by Atoll Not used by Atoll
"T/I_LIKE", Number of points "CURVE_POINT", Frequency shift in MHz, Response in dB "T/I_CW", Number of points
"CURVE_POINT", Frequency shift in MHz, Response in dB "T/I_OTHER", RADIO_ID, Interferor Bandwidth, Number of points
"CURVE_POINT", Frequency shift in MHz, Response in dB "BB_FREQ", Low frequency, High frequency "RX_RF_FILTER", Number of points "CURVE_POINT", Frequency shift in MHz, Response in dB "RX_IF_FILTER", Number of points "CURVE_POINT", Frequency shift in MHz, Response in dB "IF_FILTER_EXT", Switch-on point, Number of points "CURVE_POINT", Frequency shift in MHz, Response in dB
115
Forsk 2011
Row "RX_BB_FILTER", Number of points "CURVE_POINT", Frequency shift in MHz, Response in dB "COM_COUNT", Number of comments "COMMENT", Description #1 "COMMENT", Description #2 "COMMENT", Description #n "$TLR", File type, "$"
Description Not used by Atoll Not used by Atoll Number of comments Comment Comment Comment File trailer. The file type indicates the data contained, the format and the version of the format. For version 1.0 of the Equipment format, this value must be EQUIP1.0.
Sample "$HDR", "EQUIP1.0", "$" "EQUIP_MFG", "Alcatel USA" "MFG_MODEL", "MDR-6706-8" "REV_NUM", "Version 1.0" "REV_DATE", "03-01-1999" "RADIO_ID", "JF6-9406" "FCC_CODE", "EQ_DATE", "02-24-1999" "EMISSION", "2M50D7W" "MAX_LOADING", 192 "DATA_RATE", 12.4 "RADIO_CAP", 8, "DS1" "MODULATION", "128 TCM" "DEVIATION", "FREQ_RANGE", 5850, 7125 "POWER_OPTION", 15, 29, 31 "POWER_RANGE" "STABILITY", 0.001 "ATPC_POWER", 10 "ATPC_STEP", 1 "ATPC_TRIG", -65 "THRESH_DIG", -79, -81 "THRESH_ANA" "BRANCHING", "Non-Protected", 0, 0 "BRANCHING", "Monitored Hot-Standby", 0, 0.5, 10 "MAX_RSL", -10, -8 "DFM", 68, 70 "TX_SPECTRUM", 25 "CURVE_POINT", -3.12, -85.65 ... "CURVE_POINT", 3.12, -85.51 "TX_FILTER", 0 "FCC_BANDWIDTH", 2.5 "99%_BANDWIDTH", 2.48 "3DB_BANDWIDTH", 2.08 "T/T_FREQ_SEP", 49, 2.5, 28 "T/R_FREQ_SEP", 132, 105, 33
116
AT310_AM_E2
"T/R_FIXED" "T/I_LIKE", 171 "CURVE_POINT", -125.000, -130.7 ... "CURVE_POINT", 125.000, -133.0 "T/I_CW", 171 "CURVE_POINT", -125.000, -152.9 ... "CURVE_POINT", 125.000, -143.0 "T/I_OTHER", "", 0, 0 "BB_FREQ" "RX_RF_FILTER", 68 "CURVE_POINT", -125, -113.7 ... "CURVE_POINT", 125, -110.5 "RX_IF_FILTER", 0 "IF_FILTER_EXT", 0 "RX_BB_FILTER", 0 "COM_COUNT", 1 "COMMENT", "T/I Data for 6.425-7.125 GHz band" "$TLR", "EQUIP1.0", "$"
DBF Structure Byte 0...n n+1 last DBF Header The DBF header size is variable and depends on the field count. Description DBF header (see next part for size, byte 8) 1st record of fixed length (see next parts); 2nd record (see next part for size, byte10) ; last record optional: 0x1a (eof byte) If .dbf is not empty Remarks
117
Forsk 2011
Byte 00
Size 1
Contents 0x03 0x04 0x05 0x43 0xB3 0x83 0x8B 0x8E 0xF5
Description plain .dbf plain .dbf plain .dbf with .dbv memo var size with .dbv and .dbt memo with .dbt memo with .dbt memo in D4 format with SQL table with .fmp memo Last update digits Number of records in file Header size in bytes Record size in bytes Reserved Begin transaction End Transaction ignored Encrypted normal visible multi-user environment use production index exists index upon demand language driver ID codepage437 DOS USA codepage850 DOS Multi ling codepage1251 Windows ANSI codepage1250 Windows EE ignored reserved Field Descriptor (see next paragraph) Header Record Terminator
Applies to FS, D3, D4, D5, Fb, Fp, CL D4, D5 (FS) D5, Fp (FS) FS FS FS, D3, D4, D5, Fb, Fp, CL D4, D5 D4, D5 Fp All All All All All D4, D5 D4, D5 FS, D3, Fb, Fp, CL D4, D5 All D4,D5 Fp, D4, D5 All D4, D5 Fp Fp Fp Fp FS, D3, Fb, Fp, CL All all all
01 04 08 10 12 14
3 4 2 2 2 1
15 16 28 29
1 12 1 1
0x01 0x00 0 (1) 0x01 0x00 n 0x01 0x02 0x03 0xC8 0x00
30 32 +1
2 n*32 1
0,0 0x0D
Field descriptor array in the DBF header (32 bytes for each field): Byte 0 11 12 Size 11 1 4 Contents ASCI ASCI n,n,n,n n,n,0,0 0,0,0,0 16 17 18 20 21 23 1 1 2 1 2 1 byte byte 0,0 byte 0x00 n,n 0,0 0x01 Description field name, 0x00 termin field type (see next paragraph) Fld address in memory offset from record begin ignored Field length, bin (see next paragraph) decimal count, bin reserved Work area ID unused multi-user dBase ignored Set Fields Applies to all all D3 Fp FS, D4, D5, Fb, CL all \ FS,CL: for C field type all / both used for fld lng all D4, D5 FS, D3, Fb, Fp, CL D3, D4, D5 FS, Fb, Fp, CL D3, D4, D5
118
AT310_AM_E2
Byte 24 31
Size 7 1
Applies to FS, Fb, Fp, CL all D4, D5 FS, D3, Fb, Fp, CL
Field type and size in the DBF header, field descriptor (1 byte): Size C 1...n Type Char Description/Storage ASCII (OEM code page chars) rest= space, not \0 term. n = 1...64kb (using deci count) n = 1...32kb (using deci count) n = 1...254 D8 F 1...n N 1...n Date Numeric Numeric 8 ASCII digits (0...9) in the YYYYMMDD format ASCII digits (-.0123456789) variable pos. of float.point n = 1...20 ASCII digits (-.0123456789) fix posit/no float.point n = 1...20 n = 1...18 L1 Logical ASCII chars (YyNnTtFf space) ASCII chars (YyNnTtFf?) M 10 Memo 10 digits repres. the start block posit. in .dbt file, or 10 spaces if no entry in memo Variable, bin/asc data in .dbv 4bytes bin= start pos in memo 4bytes bin= block size 1byte = subtype 1byte = reserved (0x1a) 10 spaces if no entry in .dbv binary data in .ftp structure like M binary data in .dbt structure like M OLE objects structure like M binary int max +/- 32767 binary int max +/- 2147483647 binary signed double IEEE Applies to all FS Fp, CL all all FS, D4, D5, Fp
all FS, Fp, CL D3, D4, D5, Fb FS, D3, Fb, Fp, CL D4, D5 (FS) all
V 10
Variable
FS
P 10 B 10 G 10 22 44 88
Fp D5 D5, Fp FS FS FS
Each DBF record (fixed length): Byte 0 1n Size 1 1 Description deleted flag "*" or not deleted " " x-times contents of fields, fixed length, unterminated. For n, see (2) byte 1011 Applies to All All
119
Forsk 2011
Field MODEL_NAME
Type Text
Description Name of propagation model used to calculate path loss Signature (identity number) of model used in calculations. You may check it in the propagation model properties (General tab). The 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. X-coordinate of the top-left corner of the path loss matrix upper-left pixel Y-coordinate of the top-left corner of the path loss matrix upper-left pixel Resolution of path loss matrix in metre Number of rows in path loss matrix Number of columns in path loss matrix Frequency band Transmitter antenna mechanical tilt Transmitter antenna azimuth Transmitter height in metre X-coordinate of the transmitter Y-coordinate of the transmitter Ground height above sea level at the transmitter in metre Receiver height in metre Logical number referring to antenna pattern. Antennas with the same pattern will have the same number. Maximum path loss stated in 1/16 dB. This information is used, when no calculation radius is set, to check the matrix validity. Lowest x-coordinate of centre pixel located on the calculation radiusb Highest x-coordinate of centre pixel located on the calculation radius Lowest y-coordinate of centre pixel located on the calculation radius Highest y-coordinate of centre pixel located on the calculation radius Lowest x-coordinate of centre pixel located in the computation zonec Highest x-coordinate of centre pixel located in the computation zone Lowest y-coordinate of centre pixel located in the computation zone Highest y-coordinate of centre pixel located in the computation zone Locking status 0: path loss matrix is not locked 1: path loss matrix is locked. 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
MODEL_SIG
Text
ULXMAP ULYMAP RESOLUTION NROWS NCOLS FREQUENCY TILT AZIMUTH TX_HEIGHT TX_POSX TX_POSY ALTITUDE RX_HEIGHT ANTENNA_SI MAX_LOS CAREA_XMIN CAREA_XMAX CAREA_YMIN CAREA_YMAX WAREA_XMIN WAREA_XMAX WAREA_YMIN WAREA_YMAX LOCKED
Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Float Boolean
INC_ANT
Boolean
a.
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.
120
AT310_AM_E2
List of measurement points: 4 bytes: X 4 bytes: Y 4 bytes: measurement value 4 bytes: incidence angle.
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.
121
Forsk 2011
In the following format descriptions and samples, lines starting with the "#" are considered as comments.
In GSM interference matrices: The interferer TRX type is not specified and is always considered to be BCCH. Subcells have different powers defined as offsets with respect to the BCCH. For subcells other than the BCCH, if the power offset of a subcell is X dB, then its interference histogram will be shifted by X dB with respect to the BCCH interference histogram. If no power offset is defined on the interfered TRX type, it is possible to set "All". For each interfered subcell-interferer subcell pair, Atoll saves probabilities for several C/I values (6 to 24 values), including five fixed ones: 9, 1, 8, 14, and 22 dB. Between two fixed C/I value, there can be up to three additional values (this number depends on the probability variation between the fixed values). The C/I values have 0.5 dB accuracy and probability values are calculated and stored with an accuracy of 0.002 for probabilities between 1 and 0.05, and with an accuracy of 0.0001 for probabilities lower than 0.05.
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 #.
122
AT310_AM_E2
| Probability
##------------#------------#------------#-----------#------------------# # # 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 9 10 11 14 15 16 17 22 25 1 2 BCCH,TCHa 8 9 10 13 14 17 a. 1 0.944 .904 0.872 0.84 0.772 8 1 0.944 0.904 0.892 0.844 0.832 0.812 0.752 0.316 0.292
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.
123
Forsk 2011
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, # Fields are: ##-----------#-----------#-----------#-----------#---------#---------# #|Transmitter|Transmitter|BCCH during|BSIC during|% of vic'|% of int'| #|Name |Identifier |calculation|calculation|coverage |coverage | Tab separated format. Commented lines start with #.
##-----------#-----------#-----------#-----------#---------#---------# # # 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 per HCS layer". # Margin is 5. # Cell edge coverage probability is 75%. # Traffic spreading was Uniform (percentage of interfered area) ##---------------------------# Site0_0 Site0_1 Site0_2 Site1_0 Site1_1 Site1_2 Site2_0 Site2_1 1 2 3 4 5 6 7 8 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100
124
AT310_AM_E2
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.
#-----------------------------------------------------------------------# # 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 -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
125
Forsk 2011
Name Interfered TRX type C/I threshold Probability C/I > Threshold
Description Interfered subcell. In order to save storage, all subcells with no power offset are not duplicated (e.g. BCCH, TCH). C/I value. This column cannot be null. Probability to have C/I the value specified in column 4 (C/I threshold). This field must not be empty.
# Calculation Results Data File. # Version 1.1, Tab separated format. Commented lines start with #. # Remark: C/I results do not incorporate power offset 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". # # 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_2 Site0_2 Site0_2 Site0_2 Site0_2 Site0_2 Site0_2 Site0_2 Site0_2 Site0_2 Site0_2 ... Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 Site0_1 BCCH,TCH BCCH,TCH BCCH,TCH BCCH,TCH BCCH,TCH BCCH,TCH BCCH,TCH BCCH,TCH BCCH,TCH BCCH,TCH BCCH,TCH BCCH,TCH -10 -9 -6 -4 -1 0 1 4 7 8 9 10 1 0.996 0.976 0.964 0.936 0.932 0.924 0.896 0.864 0.848 0.832 0.824
126
AT310_AM_E2
Description Name of the interfered transmitter Name of the interferer transmitter Co-channel interference probability Adjacent channel interference probability
# Calculation Results Data File. # Version 1.1, Tab separated format. Commented lines start with #. # Remark: C/I results do not incorporate power offset 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". # # 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_2 Site0_3 Site0_3 Site0_1 Site0_3 Site0_1 Site0_2 0.226667 0.27 0.276 0.226 0.024 0.024 0.02 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
127
Forsk 2011
128
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 10: Administration and Usage Recommendations
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 Relative Path UNC Path C:\Program Files\Forsk\Geo Data\... \Program Files\Forsk\Geo Data\... \\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 may 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 179.
The following table shows the recommended file formats for different geographic data: Geographic data type Scanned maps Vectors Recommended file format ECW SHP
129
Atoll 3.1.0 Administrator Manual Chapter 10: Administration and Usage Recommendations
Forsk 2011
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 177.
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 Relative Path UNC Path C:\Program Files\Forsk\PathLosses\... \Program Files\Forsk\PathLosses\... \\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.
10.3 Databases
Database Upgrade 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). 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.
130
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 10: Administration and Usage Recommendations
Table and field names must not contain spaces or special characters, such as periods (.), exclamation marks (!), 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 and choice lists 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 may 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 may help the database function a long time before users require the addition of other custom fields.
To improver performance, if your projects allow it, reduce the size of the fields corresponding to the sites and transmitters names. To improver 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 improver performance, you should avoid adding custom fields to the neighbour management tables.
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 may 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. Atolls interface will also be more efficient and the overall processing time for various tasks will be improved.
131
Atoll 3.1.0 Administrator Manual Chapter 10: Administration and Usage Recommendations
Forsk 2011
In order to prevent users from deactivating the use of the Distributed Calculation Server, 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 132.
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 may 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.
132
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 10: Administration and Usage Recommendations
64-Bit Operating Systems The 64-bit editions of Microsoft Windows provide 4 GB of memory per process.
10.7 Printing
You should place different layers of geographic and radio data in a definite order when printing a project or a section of the project. 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.)
133
Atoll 3.1.0 Administrator Manual Chapter 10: Administration and Usage Recommendations
Forsk 2011
A Planet Index file contains the path to and the name of each antenna file available. 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.
134
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 10: Administration and Usage Recommendations
Memory Allocation If you have to open several large ATL files simultaneously on the same computer, it is better to open each in a separate Atoll session rather than to open them all in the same Atoll window. Each Atoll session on the same computer has its own memory space allocated by the operating system. Each computer consumes a single licence token independent of the number of Atoll sessions opened simultaneously. For 32-bit Windows operating systems, you can also increase the default Windows memory allocation limit from 2 GB to 3 GB as explained in "Process Memory" on page 132.
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. 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 may 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 may 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 folders 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
135
Atoll 3.1.0 Administrator Manual Chapter 10: Administration and Usage Recommendations
Forsk 2011
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 modules 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. 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. 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 63.
136
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 10: Administration and Usage Recommendations
determined by the size of the planning area. In networks with a large number of sites, transmitters and cells, it is the number of these network entities that governs this requirement. Pixel size plays an equally important role in all cases. Network-Wide Input The file sizes for raster maps (DTM, clutter heights, clutter classes, traffic density or environments, images, etc.) does not depend on the number of cells, but only on the size of the planning area in pixels. The following information can provide you with an estimate of disk usage for different geographic data: Clutter class maps require 1 byte per pixel (2 bytes for Planet format). Background images require from 1 to 3 bytes per pixel. Traffic maps require 1 byte per pixel (2 bytes for Planet format). DTM or clutter height maps require 2 bytes per pixel. Population maps or other generic maps require from 1 to 4 bytes per pixel.
For one clutter map, one DTM map, one traffic map, and one background image, you may estimate 6 bytes per pixel of the input area. This data can be shared between different planning alternatives of the same network. If an embedded geographic data file is deleted from the project, Atoll automatically compresses the ATL file to avoid file fragmentation.
Cell-Specific Results For a project with a large number of cells, it is important to consider the disk space required by the propagation prediction results of each cell. Here, the cell calculation area and the calculation resolution are important factors. Cell-specific results require 2 bytes per pixel. For example, the propagation results for a sector with a calculation area of 1024 x 1024 pixels will require 2 MB disk space. If there are different ATL files for planning the same part of the network in different ways, each ATL file will require the same amount of disk space. The same rule applies to extended path loss matrices as well. If embedded path loss matrices are externalised, Atoll automatically compresses the ATL file to avoid file fragmentation.
Network-Wide Output Network-wide output (raster results) mainly depends on: The size of the planning area The pixel size The number of coverage predictions The types of coverage predictions
Coverage predictions may have a number of layers depending on the calculation criteria. There can be a single layer for the entire network or a layer per transmitter, sector, or subcell. The resulting size depends on the number of layers and the number of colours and thresholds. Therefore, Atoll coverage predictions may require between 1 bit and 2 bytes per pixel of the calculation area.
Atoll can compress the coverage prediction results when saving a ATL file to avoid file fragmentation. You can consider 14 bytes per pixel as a rough estimate to determine the disk space required for each individual ATL file.
Temporary Disk Space Atoll requires some disk space to temporarily store intermediate results during calculations. A file is created in the systems temporary directory whose size depends on the calculations. This file is described in the section on RAM requirements. Likewise, a temporary file is created when using the "Save As" command. These files are erased after the calculations or once the storage has finished.
137
Atoll 3.1.0 Administrator Manual Chapter 10: Administration and Usage Recommendations
Forsk 2011
Other Disk Space Requirements Other objects in a ATL file that require disk space can easily be neglected in real-life scenarios since the required disk space depending on the size of the planning area and the number of transmitters is much higher. ATL files store database tables and calculation results. An empty ATL file requires around 500 KB. Each additional site requires between 1 and 2 KB, which is negligible compared to the size of the propagation results. Furthermore, the size of vector files is negligible compared to that of other geographic data, as their size is usually much smaller than the DTM, clutter height, and clutter class maps. When saving an ATL file, Atoll estimates the size of unused spaces in the file due to fragmentation. If the amount of unused spaces is more than half of the useful space, Atoll proposes compressing the file.
Most of these parameters have minor influences and the actual requirements are mostly governed by the number of cells and the number of mobiles generated. Assuming that there are three carriers used and the number of transmitters and mobiles is high enough so that the other input can be ignored, the required memory can be roughly approximated by:
R = 14.0 t + 3.25 m R = 14.0 t + 4.3 m
with R: peak RAM requirement in KBytes t: number of transmitters affecting the computation zone m: number of mobiles generated by the UMTS simulation Example: To calculate for 500 sites (or 1500 transmitters) and 2400 mobiles, around 28 MB of RAM are required for a normal simulation and 30 MB if detailed results are to be stored as well. Please note that this is the peak requirement. Less memory will be required once the calculations are terminated. This approximation also considers effects due to the operating system, such as memory over-allocation due to fragmentation. It is a conservative approximation and in most cases the actual RAM requirement will be below these calculated figures. A more accurate estimation of the used and required memory for UMTS simulations is available in the Source Traffic tab of the new simulation group dialogue. To activate the memory estimation feature, you must add an option in the Atoll.ini file. For more information, see "Estimating Required and Used Memory Size for UMTS Simulations" on page 190.
138
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 10: Administration and Usage Recommendations
Coverage Predictions RAM required during coverage prediction calculations (network-wide raster result) is the same as the required additional disk space, i.e., between 1 bit and 2 bytes per pixel of the calculation area. Apart from this, temporary memory is required for calculations like "Coverage by transmitter" and "Coverage by signal level". For these, Atoll temporarily allocates an average of 4 bytes more per pixel (8 bytes, if the best server margin is not zero) of the calculation area. Example: The Paris region has a size of around 10 x 13 km. For a calculation resolution of 25 m, this equals 5.2 million pixels. If a coverage prediction calculates the signal strength of the UMTS pilot in less than 16 colours, it would require a memory of 4 bits per pixel, or a total of 2.6 MB. During the calculation, Atoll would also require 4 more bytes per pixel, which equals 20.8 MB more apart from the 2.6 MB. For large networks, to avoid loading the entire computation zone in memory, Atoll divides the coverage prediction computations into smaller tiles, and carries out the computations on them successively. This subdivision is invisible to the user.
139
Atoll 3.1.0 Administrator Manual Chapter 10: Administration and Usage Recommendations
Forsk 2011
140
AT310_AM_E2
11 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 may store: Geographic data settings Filtering, focus, computation, printing, and geographic export zones Folder configurations List of coverage predictions in the Predictions folder and their settings Automatic neighbour allocation parameters Automatic frequency planning parameters (GSM GPRS EDGE documents) Automatic scrambling code allocation parameters (UMTS HSPA and TD-SCDMA documents) Automatic PN offset allocation parameters (CDMA2000 documents) Microwave link parameters Full paths to macro files Projection and display coordinate systems are stored in the database, 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 142. A user configuration file may 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 164. Custom predictions file (UTF-8 encoded XML files) This file contains the list and parameter settings of customised coverage predictions. By default, this file is named "Studies.xml" and is located in the Atoll installation folder. The custom predictions file must be created using Atoll to ensure correct syntax and structure. It is possible to edit the contents of this file in an XML editor and make changes if required. For more information on working with customised predictions in Atoll, see the User Manual. For more information on the contents of the custom predictions file, see "Contents of the Custom Predictions File" on page 168.
141
Forsk 2011
142
AT310_AM_E2
Sample
<Display>: (Different combinations of the following parameters exist in different display settings.) Displate type <type>, selected field <FieldSelector>, transparency level <opacity>, visibility flag <visible>, and visibility range between <minZoom> and <maxZoom> <Items> properties, such as for each item: <Value>, <Min>, <Max>, <Legend>, <MainColor>, <SecondaryColor>, <LineStyle>, <LineWidth>, and <FillStyle> <AddToLegend>: Add to legend option checked or not <File>: <Format> and <Path> to linked files, if any
Sample with display set to value intervals. <?xml version="1.0" encoding="UTF-8"?> <Atoll> <Geodataset version="2"> <DegreeFormat>0</DegreeFormat> <Population> // or <GeoClimaticParams> or <Vectors> <Name>Population</Name> // or <Name>Geoclimatic Parameters</Name> or <Name>Vectors</Name> <Display> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> <Type>ByIntervals</Type> <FieldSelector>80000001</FieldSelector> <SymbolFont> <Name>Wingdings</Name> <Size>-120</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </SymbolFont> <LabelFont> <Name>MS Shell Dlg</Name> <Size>-83</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </LabelFont> <Items> <Item> <Min>900.</Min> <Max>1000.</Max> <Legend>900 <=Population(Density) <1 000</Legend> <MainColor>255 96 0</MainColor> <SecondaryColor>255 0 0</SecondaryColor> </Item> </Items> </Display> <AddToLegend>0</AddToLegend> <Type> <Name>Population</Name> <Formats>15</Formats>
143
Forsk 2011
<Type>800</Type> <Integrable>1</Integrable> </Type> <Files/> </Population> // or </GeoClimaticParams> or </Vectors> <ClassifiedClutter UseOnlyDefault="0"> <Display> <Type>ByIntervals</Type> <FieldSelector>3</FieldSelector> <Opacity>50</Opacity> <Items> <Item> <Min>54.</Min> <Max>56.</Max> <Legend>54 <=Height (m) <56</Legend> <MainColor>255 38 0</MainColor> <SecondaryColor>255 38 0</SecondaryColor> <LineStyle>5</LineStyle> <LineWidth>10</LineWidth> <FillStyle>1</FillStyle> </Item> </Items> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> </Display> <Attributes> <fields> <field length="1" type="uint" name="CODE"/> <field length="4" type="int" name="COLOR"/> <field length="50" type="text" name="NAME"/> <field length="4" type="real" name="HEIGHT"/> </fields> <records/> </Attributes> <Name>Clutter Classes</Name> <AddToLegend>0</AddToLegend> <DefaultValues> </DefaultValues> </ClassifiedClutter> <Altitudes> // or <BuildingHeights> <Name>Digital Terrain Model</Name> // or <Name>Clutter Heights</Name> <Display> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> <Type>ByIntervals</Type> <FieldSelector>0</FieldSelector> <Opacity>50</Opacity>
144
AT310_AM_E2
<Items> <Item> <Min>900.</Min> <Max>1000.</Max> <Legend>900 <=Altitude <1 000</Legend> <MainColor>255 96 0</MainColor> <SecondaryColor>255 96 0</SecondaryColor> <LineStyle>5</LineStyle> <LineWidth>10</LineWidth> <FillStyle>1</FillStyle> </Item> </Items> </Display> <AddToLegend>0</AddToLegend> </Altitudes> // or </BuildingHeights> </Geodataset> </Atoll>
11.1.2 Zones
The user configuration files store the coordinates of the vertices of the filtering, focus, computation, printing, and geographic export zone polygons, i.e., the points forming these polygons. The first and the last points have the same coordinates. Sample The following sample has rectangular computation and focus zones of the same size. <?xml version="1.0" encoding="UTF-8"?> <Atoll> <CalculationZone> <Point>35950.000000 -15445.000000</Point> <Point>33.000000 -15445.000000</Point> <Point>33.000000 -33.000000</Point> <Point>35950.000000 -33.000000</Point> <Point>35950.000000 -15445.000000</Point> </CalculationZone> <FocusZone> <Point>35950.000000 -15445.000000</Point> <Point>33.000000 -15445.000000</Point> <Point>33.000000 -33.000000</Point> <Point>35950.000000 -33.000000</Point> <Point>35950.000000 -15445.000000</Point> </FocusZone> <Atoll>
145
Forsk 2011
<SymbolFont> properties, such as font name <Name>, font size <Size>, font colour <Color>, background colour <BackColor>, and font style <Style> <LabelFont> properties, such as label font name <Name>, label font size <Size>, label font colour <Color>, label font background colour <BackColor>, and label font style <Style> <Items> properties, such as for each <Item>: <Value>, <Legend>, <MainColor>, <SecondaryColor>, <Symbol>, and <SymbolSize> <DataTips>: List of <items> displayed in tip texts <Labels>: List of <items> displayed in labels <AddToLegend>: Add to legend option checked or not <DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration <Filter>, <Groups>, and <Sort> criteria <Configuration>: If any configuration exists for the folder, this tag contains the configuration <Name> and the <Filter>, <Groups>, and <Sort> criteria
Antennas folder: <Name>: Name of the folder <DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration <Filter>, <Groups>, and <Sort> criteria <Configuration>: If any configuration exists for the folder, this tag contains the configuration <Name> and the <Filter>, <Groups>, and <Sort> criteria Transmitters, Multi-Hops, and Point to Multipoint folders: <Name>: Name of the folder <Display>: Displate type <Type>, selected field <FieldSelector>, visibility flag <Visible>, and visibility range between <MinZoom> and <MaxZoom> <LabelFont> properties, such as label font name <Name>, label font size <Size>, label font colour <Color>, label font background colour <BackColor>, and label font style <Style> <Items> properties, such as for each <Item>: <Value>, <Legend>, <MainColor>, <SecondaryColor>, <Symbol>, and <SymbolSize> <DataTips>: List of <items> displayed in tip texts <Labels>: List of <items> displayed in labels <AddToLegend>: Add to legend option checked or not <DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration <Filter>, <Groups>, and <Sort> criteria <Configuration>: If any configuration exists for the folder, this tag contains the configuration <Name> and the <Filter>, <Groups>, and <Sort> criteria Links folder: <Name>: Name of the folder <Display>: Contains visibility flag <visible>, and visibility range between <minZoom> and <maxZoom> <AddToLegend>: Add to legend option checked or not <DefaultConfiguration>: The default configuration for the folder <LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>, label font background colour <BackColor>, and label font style <Style> <SiteDisplay> properties, such as: <SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, background colour <BackColor>, and font style <Style> <LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>, label font background colour <BackColor>, and label font style <Style> <Symbol>: Symbol used for microwave links <ShowText>: Caption for microwave links shown or not <RepeaterDisplay> properties, such as: <SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, background colour <BackColor>, and font style <Style> CW Measurements folder: <DefaultConfiguration>: The default configuration for the folder <Distance>: The minimum <Min> and maximum <Max> distance for measurement filtering <DistanceUnit>: The distance unit <Measure>: The minimum <Min> and maximum <Max> measured level for filtering <MeasureUnit>: The measurement unit <Angle>: The minimum <Min> and maximum <Max> angle for measurement filtering <Relative>: Whether the angle is relative to each transmitters azimuth or an absolute value <Clutter>: For each <Class>, its <Code> and whether it is in the <Filter> or not <Advanced>: Any advanced filter used for filtering <PathLosses>: Path loss tuing parameters, i.e., <ParallelAxisRadius>, <PerpendicularAxisRadius>, <GlobalMargin>, <LocalMargin>, and <Threshold> <Display>:
146
AT310_AM_E2
Displate type <Type>, selected field <FieldSelector>, visibility flag <Visible>, and visibility range between <MinZoom> and <MaxZoom> <SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, background colour <BackColor>, and font style <Style> <LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>, label font background colour <BackColor>, and label font style <Style> <Items> properties, such as for each <Item>: <Legend>, <MainColor>, <SecondaryColor>, <Symbol>, and <SymbolSize> <DataTips>: List of <items> displayed in tip texts <Labels>: List of <items> displayed in labels <AddToLegend>: Add to legend option checked or not
Drive Test Data folder: <Techno>: Name of the technology (if exported from a 3GPP Multi-RAT document. <DefaultConfiguration>: The default configuration for the folder <Clutter>: For each <Class>, its <Code> and whether it is in the <Filter> or not <Advanced>: Any advanced filter used for filtering <PathLosses>: Path loss tuing parameters, i.e., <ParallelAxisRadius>, <PerpendicularAxisRadius>, <GlobalMargin>, <LocalMargin>, and <Threshold> <Display>: Displate type <Type>, selected field <FieldSelector>, visibility flag <Visible>, and visibility range between <MinZoom> and <MaxZoom> <SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, background colour <BackColor>, and font style <Style> <LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>, label font background colour <BackColor>, and label font style <Style> <Items> properties, such as for each <Item>: <Legend>, <MainColor>, <SecondaryColor>, <Symbol>, and <SymbolSize> <DataTips>: List of <items> displayed in tip texts <Labels>: List of <items> displayed in labels <AddToLegend>: Add to legend option checked or not Propagation Models and Smart Antenna Models folders: <Name>: Name of the folder <DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration <Filter>, <Groups>, and <Sort> criteria
Sample <?xml version="1.0" encoding="UTF-8"?> <Atoll> <FoldersConfigurations> <Sites> <Name>Sites</Name> <Display> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> <Type>ByValues</Type> <FieldSelector>8</FieldSelector> <SymbolFont> <Name>Wingdings</Name> <Size>-120</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>32</Style> </SymbolFont> <LabelFont> <Name>MS Shell Dlg</Name> <Size>-80</Size>
147
Forsk 2011
<Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>33</Style> </LabelFont> <Items> <Item> <Value>Vendor</Value> <Legend>Vendor</Legend> <MainColor>255 0 0</MainColor> <SecondaryColor>255 255 255</SecondaryColor> <Symbol>164</Symbol> <SymbolSize>120</SymbolSize> </Item> </Items> <DataTips> <Item>0</Item> </DataTips> <Labels> <Item>0</Item> </Labels> </Display> <AddToLegend>1</AddToLegend> <DefaultConfiguration> <Groups>Type</Groups> </DefaultConfiguration> </Sites> <Antennas> <Name>Antennas</Name> <DefaultConfiguration> <Filter>([CONSTRUCTOR]= Kathrein)</Filter> </DefaultConfiguration> <Configuration> <Name>Conf</Name> <Filter>([CONSTRUCTOR]= Kathrein)</Filter> </Configuration> </Antennas> <Transmitters> // or <MWMultiHops> // or <MWHubs> <Name>Transmitters</Name> // or <Name>Multi-Hops</Name> // or <Name>Point to Multipoint</Name> <Display> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> <Type>ByValues</Type> <FieldSelector>0</FieldSelector> <Items> </Items> <DataTips> <Item>0</Item>
148
AT310_AM_E2
</DataTips> </Display> <AddToLegend>1</AddToLegend> <DefaultConfiguration/> </Transmitters> // or </MWMultiHops> // or </MWHubs> <MWLinks> <Name>Links</Name> <Display> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> </Display> <AddToLegend>0</AddToLegend> <DefaultConfiguration/> <LabelFont> <Name>MS Shell Dlg</Name> <Size>-83</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </LabelFont> <SiteDisplay> <SymbolFont> <Name>Wingdings</Name> <Size>80</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </SymbolFont> <LabelFont> <Name>MS Shell Dlg</Name> <Size>-80</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </LabelFont> </SiteDisplay> <Symbol>65444</Symbol> <ShowText>0</ShowText> <RepeaterDisplay> <SymbolFont> <Name>Wingdings</Name> <Size>80</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </SymbolFont> </RepeaterDisplay> </MWLinks>
149
Forsk 2011
<CWMeasurements> <DefaultConfiguration> <Distance> <Min>0.</Min> <Max>1000.</Max> </Distance> <DistanceUnit>0</DistanceUnit> <Measure> <Min>-105.</Min> <Max>-90.</Max> </Measure> <MeasureUnit>0</MeasureUnit> <Angle> <Min>-180.</Min> <Max>180.</Max> </Angle> <Relative>Yes</Relative> <Clutter> <Class> <Code>1</Code> <Filter>Yes</Filter> </Class> </Clutter> <Advanced>([DIST]> 500)</Advanced> </DefaultConfiguration> <PathLosses> <ParallelAxisRadius>200.</ParallelAxisRadius> <PerpendicularAxisRadius>100.</PerpendicularAxisRadius> <GlobalMargin>30.</GlobalMargin> <LocalMargin>30.</LocalMargin> <Threshold>-130.</Threshold> </PathLosses> <Display> <Type>ByIntervals</Type> <FieldSelector>Error (P-M) (dB)</FieldSelector> <SymbolFont> <Name>Wingdings</Name> <Size>-120</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </SymbolFont> <LabelFont> <Name>MS Shell Dlg</Name> <Size>-83</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </LabelFont>
150
AT310_AM_E2
<Items> <Item> <Min>-20.</Min> <Legend>Error (P-M) (dB) >=-20</Legend> <MainColor>255 0 0</MainColor> <SecondaryColor>0 0 0</SecondaryColor> <Symbol>167</Symbol> <SymbolSize>100</SymbolSize> </Item> </Items> <DataTips> <Item>M (dBm)</Item> </DataTips> <Labels> <Item>M (dBm)</Item> </Labels> </Display> </CWMeasurements> <TestMobileData> <Techno>GSM</Techno> <DefaultConfiguration> <Clutter> <Class> <Code>1</Code> <Filter>Yes</Filter> </Class> </Clutter> <Advanced></Advanced> </DefaultConfiguration> <PathLosses> <ParallelAxisRadius>200.</ParallelAxisRadius> <PerpendicularAxisRadius>100.</PerpendicularAxisRadius> <GlobalMargin>30.</GlobalMargin> <LocalMargin>30.</LocalMargin> <Threshold>-130.</Threshold> </PathLosses> <Display> <Type>ByIntervals</Type> <FieldSelector>Ec_I0</FieldSelector> <SymbolFont> <Name>Wingdings</Name> <Size>-120</Size> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </SymbolFont> <LabelFont> <Name>MS Shell Dlg</Name> <Size>-83</Size>
151
Forsk 2011
<Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>0</Style> </LabelFont> <Items> <Item> <Min>-60.</Min> <Legend>Ec_I0 >=-60</Legend> <MainColor>255 0 0</MainColor> <SecondaryColor>0 0 0</SecondaryColor> <Symbol>167</Symbol> <SymbolSize>100</SymbolSize> </Item> </Items> </Display> </TestMobileData> <PropagationModels> // or <SmartAntennasModels> <Name>Propagation Models</Name> // or <Name>Smart Antenna Models</Name> <DefaultConfiguration/> </PropagationModels> // or </SmartAntennasModels> </FoldersConfigurations> </Atoll>
Sample GSM coverage by signal level <?xml version="1.0" encoding="UTF-8"?> <Atoll> <Studies> <CoverageTRXStudy> <Techno>GSM</Techno> <Name>GSM: Coverage by Signal Level 0</Name>
152
AT310_AM_E2
<Display> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> <Type>ByIntervals</Type> <FieldSelector>80000008</FieldSelector> <Opacity>50</Opacity> <Items> <Item> <Min>-75.</Min> <Legend>Best Signal Level (dBm) >=-75</Legend> <MainColor>255 147 0</MainColor> <SecondaryColor>0 0 0</SecondaryColor> <LineStyle>5</LineStyle> <LineWidth>15</LineWidth> <FillStyle>1</FillStyle> </Item> <Item> <Min>-85.</Min> <Legend>Best Signal Level (dBm) >=-85</Legend> <MainColor>70 255 0</MainColor> <SecondaryColor>0 0 0</SecondaryColor> <LineStyle>5</LineStyle> <LineWidth>15</LineWidth> <FillStyle>1</FillStyle> </Item> <Item> <Min>-95.</Min> <Legend>Best Signal Level (dBm) >=-95</Legend> <MainColor>0 255 217</MainColor> <SecondaryColor>0 0 0</SecondaryColor> <LineStyle>5</LineStyle> <LineWidth>15</LineWidth> <FillStyle>1</FillStyle> </Item> <Item> <Min>-105.</Min> <Legend>Best Signal Level (dBm) >=-105</Legend> <MainColor>0 0 255</MainColor> <SecondaryColor>0 0 0</SecondaryColor> <LineStyle>5</LineStyle> <LineWidth>15</LineWidth> <FillStyle>1</FillStyle> </Item> </Items> <DataTips> <Item>c0000000</Item> <Item>c0000001</Item> </DataTips>
153
Forsk 2011
</Display> <AddToLegend>1</AddToLegend> <Resolution>50</Resolution> <LockedStudy>0</LockedStudy> <ComputeHisto>1</ComputeHisto> <HistoPerTx>0</HistoPerTx> <HistoLabel></HistoLabel> <Conditions> <FieldDbm> <Min>-105.</Min> </FieldDbm> <Reliability>0.75</Reliability> <TRXType>BCCH</TRXType> <DefTrgThreshold>1</DefTrgThreshold> <Indoor>0</Indoor> <WithShadowing>0</WithShadowing> </Conditions> </CoverageTRXStudy> </Studies> </Atoll>
154
AT310_AM_E2
<UseGlobalThreshold>: Coverage conditions for WiMAX and LTE: Whether to use a global minimum preamble C/ N or RSRP, or per-cell values
Parameters specific to GSM GPRS EDGE: <minField>: Coverage conditions: Minimum BCCH signal level <margin>: Coverage conditions: Margin for the minimum signal level (Handover start) <traffic>: Coverage conditions: Take traffic into account or not <deltaMax>: Coverage conditions: Handover end Parameters specific to UMTS HSPA, TD-SCDMA, and CDMA2000 1xRTT 1xEV-DO: <minField>: Coverage conditions: Minimum pilot signal level <margin>: Coverage conditions: Margin for the minimum signal level (Ec/I0 margin) <traffic>: Coverage conditions: Take traffic into account or not <deltaMax>: Coverage conditions: Handover end <EcIoMin>: Coverage conditions: Minimum Ec/I0 <usePmax>: Coverage conditions: Use maximum power or not <PerCentMaxPower>: Coverage conditions: Percentage of maximum power to consider in calculations <EcIoMax>: Coverage conditions: Maximum Ec/I0 <useEcIoMax>: Coverage conditions: Use maximum Ec/I0 or not <TDrop>: TDrop value (TD-SCDMA documents, intra-technology neighbour allocation only) Parameters specific to WiMAX 802.16e and LTE: <HOStart>: The handover start margin (intra-technology neighbour allocation only) <HOEnd>: The handover end margin (intra-technology neighbour allocation only) <BSmargin>: RSRP margin from the best server (inter-technology neighbour allocation only)
Sample UMTS HSPA inter-technology, intra-carrier neighbour allocation parameters: <?xml version="1.0" encoding="UTF-8"?> <Atoll> <ANP_options> <Techno>UMTS</Techno> <numMax>16</numMax> <resolution>-1</resolution> <minField>-10500</minField> <margin>500</margin> <useCoSite>1</useCoSite> <useAdjacent>1</useAdjacent> <traffic>0</traffic> <symetric>0</symetric> <keepNeighbs>0</keepNeighbs> <MaxDist>10000</MaxDist> <PercentCoverage>1000</PercentCoverage> <UseShadowing>0</UseShadowing> <reliability>7500</reliability> <UseIndoor>0</UseIndoor> <deltaMax>1200</deltaMax> <applyConstraints>0</applyConstraints> <covBased>1</covBased> <minDistImportance>100</minDistImportance> <maxDistImportance>1000</maxDistImportance> <minCov>1000</minCov> <maxCov>3000</maxCov> <minAdj>3000</minAdj> <maxAdj>6000</maxAdj> <minCos>6000</minCos>
155
Forsk 2011
156
AT310_AM_E2
<dtxVocalFactor>70</dtxVocalFactor> <AfpBasedOnInterference>1</AfpBasedOnInterference> <AfpBasedOnSeparations>1</AfpBasedOnSeparations> <IM_calculate__WithTraffic>0</IM_calculate__WithTraffic> <IM_calculate__BestServerZoneMargin>5</IM_calculate__BestServerZoneMargin> <IM_calculate__ServiceZoneType>1</IM_calculate__ServiceZoneType> <IM_calculate__reliability_X_10000>7500</IM_calculate__reliability_X_10000> <TakeTfFromCapt>1</TakeTfFromCapt> <preferedSenario></preferedSenario> </AFP_options> </Atoll>
157
Forsk 2011
<margin>500.</margin> <reliability>5000.</reliability> <DistanceMin>200000.</DistanceMin> <Strategy0>1</Strategy0> <Strategy1>1</Strategy1> <Strategy2>1</Strategy2> <Strategy3>1</Strategy3> <Strategy>0</Strategy> <FromScratch>1</FromScratch> <UseCurrentNghbs>1</UseCurrentNghbs> <NghbOrder>1</NghbOrder> <ComputeNghbs>0</ComputeNghbs> <UseMaxCodes>1</UseMaxCodes> <UseShadowing>1</UseShadowing> <SameCodeForCarriers>0</SameCodeForCarriers> <NbClusterPerSite>3</NbClusterPerSite> <ClustNghbs>0</ClustNghbs> <Clust2ndNghbs>0</Clust2ndNghbs> <NbCodesPerCluster>8</NbCodesPerCluster> <UseDistance>1</UseDistance> <UseExcepPairs>1</UseExcepPairs> <minField>-10500</minField> <usePmax>0</usePmax> <PerCentMaxPower>5000</PerCentMaxPower> <Max1stNghbCost>100</Max1stNghbCost> <Max2ndNghbCost>50</Max2ndNghbCost> <Max3rdNghbCost>5</Max3rdNghbCost> <CoplanCost>100</CoplanCost> <MaxCoClusterCost>50</MaxCoClusterCost> <MaxDistCost>100</MaxDistCost> <ExcepPairCost>100</ExcepPairCost> <UseIndoor>0</UseIndoor> <UseCloseNghbs>1</UseCloseNghbs> <CloseDistance>80000.</CloseDistance> <CloseImportance>3000.</CloseImportance> <MaxCloseCost>100</MaxCloseCost> </SCP_options> </Atoll>
158
AT310_AM_E2
Sample
<UseCurrentNghbs>: Use existing neighbours or not <NghbOrder>: The order of neigbours to take into account, i.e., 1st, 2nd, or 3rd <ComputeNghbs>: Calculate neighbours using the addition Ec/I0 conditions or not <UseShadowing>: Shadowing taken into account or not <SameCodeForCarriers>: Allocate same PN offset to cells of the same transmitter or not <PilotIncr>: Value for the PILOT_INC <PNClusterSize>: Number of PN offsets per cluster <UseDistance>: Take the minimum reuse distance into account or not <UseExcepPairs>: Take exceptional pairs into account or not <UseMaxCodes>: Use a maximum of codes or not <minField>: Minimum pilot signal level constraint <usePmax>: Use the maximum downlink transmission power or not <PerCentMaxPower>: The percentage of the maximum downlink power is <usePmax> is set to 0 <Max1stNghbCost>: The maximum cost of 1st order neighbours <Max2ndNghbCost>: The maximum cost of 2nd order neighbours <Max3rdNghbCost>: The maximum cost of 3rd order neighbours <CoplanCost>: The cost for inter-technology neighbours <MaxDistCost>: The maximum cost for a minimum reuse distance constraint violation <ExcepPairCost>: The cost for exceptional pair constraint violation <UseIndoor>: Coverage conditions: Use indoor losses defined per clutter class or not
<?xml version="1.0" encoding="UTF-8"?> <Atoll> <PNO_options> <DistanceMin>200000.</DistanceMin> <Strategy0>1</Strategy0> <Strategy1>1</Strategy1> <Strategy2>1</Strategy2> <Strategy>2</Strategy> <FromScratch>1</FromScratch> <UseCurrentNghbs>1</UseCurrentNghbs> <NghbOrder>1</NghbOrder> <ComputeNghbs>1</ComputeNghbs> <SameCodeForCarriers>0</SameCodeForCarriers> <PilotIncr>4</PilotIncr> <PNClusterSize>3</PNClusterSize> <UseDistance>1</UseDistance> <UseExcepPairs>1</UseExcepPairs> <UseMaxCodes>1</UseMaxCodes> <MinEcI0>-1600.</MinEcI0> <TDrop>-1800.</TDrop> <reliability>6000.</reliability> <UseShadowing>0</UseShadowing> <minField>-10500</minField> <usePmax>0</usePmax> <PerCentMaxPower>5000</PerCentMaxPower> <Max1stNghbCost>100</Max1stNghbCost> <Max2ndNghbCost>50</Max2ndNghbCost> <Max3rdNghbCost>5</Max3rdNghbCost> <CoplanCost>100</CoplanCost> <MaxDistCost>100</MaxDistCost> <ExcepPairCost>100</ExcepPairCost> <UseIndoor>0</UseIndoor>
159
Forsk 2011
</PNO_options> </Atoll>
160
AT310_AM_E2
<maxZoom>20000000</maxZoom> <visible>Yes</visible> </Display> <AddToLegend>0</AddToLegend> <QualityModel>6</QualityModel> <QualityObjective0>3</QualityObjective0> <QualityObjective1>4</QualityObjective1> <QualityObjective2>2</QualityObjective2> <QualityObjective3>1</QualityObjective3> <AvailabilityObjective0>3</AvailabilityObjective0> <AvailabilityObjective1>2</AvailabilityObjective1> <AvailabilityObjective2>1</AvailabilityObjective2> <RainModel>5</RainModel> <RBER>1.e-012</RBER> <ALFA1>10</ALFA1> <ALFA2>1</ALFA2> <RefDelayM>6.30000019</RefDelayM> <refDelayNM>6.30000019</refDelayNM> <EquipPercent>33.</EquipPercent> <RainPercent>33.</RainPercent> <kMoy>1.33</kMoy> <kMin>0.88</kMin> <UseAtpc>0</UseAtpc> <P0Method>1</P0Method> <IgnoreXPD>1</IgnoreXPD> <IgnorePR>0</IgnorePR> <WhichBER>5</WhichBER> <BER1>1.e-003</BER1> <BER2>1.e-006</BER2> <Rec838>1</Rec838> <UseK1Global>1</UseK1Global> <UseK2Global>1</UseK2Global> <CALC_LINK_PORTS>selected</CALC_LINK_PORTS> <MultilineShared>0</MultilineShared> <NoAcm>1</NoAcm> <InterferenceDistanceMax>50000.</InterferenceDistanceMax> <InterferenceDropMin>1.</InterferenceDropMin> <InterferenceDropMinGlobal>3.</InterferenceDropMinGlobal> <InterferenceCalcGo>1</InterferenceCalcGo> <InterferenceCalcReturn>1</InterferenceCalcReturn> <InterferenceCalcUplink>0</InterferenceCalcUplink> <InterferenceCalcDownlink>0</InterferenceCalcDownlink> <InterferenceRainSurfCorrelation>100.</InterferenceRainSurfCorrelation> <InterferenceAutoWeight>0</InterferenceAutoWeight> <InterferenceUseAtpc>0</InterferenceUseAtpc> <InterferenceWidth>250</InterferenceWidth> <InterferenceOverShoot>0</InterferenceOverShoot> <CochannelOnly>0</CochannelOnly> <IgnoreIntraLinkInterference>1</IgnoreIntraLinkInterference>
161
Forsk 2011
<Resolution>50</Resolution> <INTERF_DETAIL>both</INTERF_DETAIL> <ClutterCategory0>0</ClutterCategory0> <ClutterDryCategory0>B</ClutterDryCategory0> <ClutterCategory1>1</ClutterCategory1> <ClutterDryCategory1>B</ClutterDryCategory1> <ClutterCategory2>1</ClutterCategory2> <ClutterDryCategory2>B</ClutterDryCategory2> <ClutterCategory3>1</ClutterCategory3> <ClutterDryCategory3>B</ClutterDryCategory3> <ClutterCategory4>0</ClutterCategory4> <ClutterDryCategory4>B</ClutterDryCategory4> <ClutterCategory5>1</ClutterCategory5> <ClutterDryCategory5>B</ClutterDryCategory5> <ClutterCategory6>2</ClutterCategory6> <ClutterDryCategory6>B</ClutterDryCategory6> <ClutterCategory7>2</ClutterCategory7> <ClutterDryCategory7>B</ClutterDryCategory7> <ClutterCategory8>2</ClutterCategory8> <ClutterDryCategory8>B</ClutterDryCategory8> <ClutterCategory9>4</ClutterCategory9> <ClutterDryCategory9>B</ClutterDryCategory9> <ClutterCategory10>2</ClutterCategory10> <ClutterDryCategory10>B</ClutterDryCategory10> <ClutterCategory11>2</ClutterCategory11> <ClutterDryCategory11>B</ClutterDryCategory11> <ClutterCategory12>2</ClutterCategory12> <ClutterDryCategory12>B</ClutterDryCategory12> <ClutterCategory13>2</ClutterCategory13> <ClutterDryCategory13>B</ClutterDryCategory13> <ClutterCategory14>2</ClutterCategory14> <ClutterDryCategory14>B</ClutterDryCategory14> <ClutterCategory15>1</ClutterCategory15> <ClutterDryCategory15>E</ClutterDryCategory15> <ClutterCategory16>1</ClutterCategory16> <ClutterDryCategory16>E</ClutterDryCategory16> <ClutterCategory17>0</ClutterCategory17> <ClutterDryCategory17>E</ClutterDryCategory17> <ClutterCategory18>1</ClutterCategory18> <ClutterDryCategory18>E</ClutterDryCategory18> <ClutterCategory19>1</ClutterCategory19> <ClutterDryCategory19>E</ClutterDryCategory19> <ClutterCategory20>1</ClutterCategory20> <ClutterDryCategory20>E</ClutterDryCategory20> <ClutterCategory21>1</ClutterCategory21> <ClutterDryCategory21>E</ClutterDryCategory21> <ClutterCategory22>1</ClutterCategory22> <ClutterDryCategory22>E</ClutterDryCategory22> <ClutterCategory23>1</ClutterCategory23>
162
AT310_AM_E2
<ClutterDryCategory23>E</ClutterDryCategory23> <ClutterCategory24>1</ClutterCategory24> <ClutterDryCategory24>E</ClutterDryCategory24> <ClutterCategory25>1</ClutterCategory25> <ClutterDryCategory25>E</ClutterDryCategory25> <ClutterCategory26>1</ClutterCategory26> <ClutterDryCategory26>A</ClutterDryCategory26> <ClutterCategory27>1</ClutterCategory27> <ClutterDryCategory27>A</ClutterDryCategory27> <ClutterCategory28>1</ClutterCategory28> <ClutterDryCategory28>A</ClutterDryCategory28> <ClutterCategory29>1</ClutterCategory29> <ClutterDryCategory29>A</ClutterDryCategory29> <ClutterCategory30>1</ClutterCategory30> <ClutterDryCategory30>A</ClutterDryCategory30> <ClutterCategory31>1</ClutterCategory31> <ClutterDryCategory31>E</ClutterDryCategory31> <ClutterCategory32>1</ClutterCategory32> <ClutterDryCategory32>E</ClutterDryCategory32> <ClutterCategory33>1</ClutterCategory33> <ClutterDryCategory33>E</ClutterDryCategory33> <ClutterCategory34>1</ClutterCategory34> <ClutterDryCategory34>E</ClutterDryCategory34> <ClutterCategory35>1</ClutterCategory35> <ClutterDryCategory35>E</ClutterDryCategory35> <ClutterCategory36>1</ClutterCategory36> <ClutterDryCategory36>E</ClutterDryCategory36> </Microwave> </Atoll>
11.1.10 Macros
The following parameters are saved for macros: Sample <?xml version="1.0" encoding="UTF-8"?> <Atoll> <Macros> <File> <Path>C:\TestsAddin\testEvents.vbs</Path> <Language>VBScript</Language> <Timeout>3600</Timeout> </File> </Macros> </Atoll> <Path>: Full path to the macro file <Language>: Language in which the macro is written <Timeout>: The target time allocated to macro execution
163
Forsk 2011
Sample <?xml version="1.0" encoding="UTF-8"?> <PrintConfiguration version="1"> <Page> <Paper size="" orientation="1"/> <Margins right="2000" left="2000" bottom="2000" top="2000"/> <Scale fitToPage="1">12 495</Scale> </Page> <Map insideFZonly="1" rulers="1"/> <Legend> <LegendPos enable="0" majorPos="3" minorPos="0" insideMap="0"/> </Legend> <Comments> <Position vPos="1" enable="0" hPos="1" insideMap="0"/> <text></text> <font height="14" weight="400" charset="1" face="MS Shell Dlg" italic="0"/> </Comments> <Logo> <Position vPos="0" enable="1" hPos="0" insideMap="0"/> <bitmap></bitmap> <Dimensions width="46" height="18"/> </Logo> <Title> <Position vPos="0" enable="0" hPos="1" insideMap="0"/>
164
AT310_AM_E2
<text></text> <font height="14" weight="400" charset="1" face="MS Shell Dlg" italic="0"/> </Title> <LogoBottom> <Position vPos="1" enable="0" hPos="0" insideMap="0"/> <bitmap></bitmap> <Dimensions width="46" height="18"/> </LogoBottom> <Footer> <Position vPos="1" enable="0" hPos="1" insideMap="0"/> <text></text> <font height="14" weight="400" charset="1" face="MS Shell Dlg" italic="0"/> </Footer> </PrintConfiguration>
165
Forsk 2011
The column type indexes are as follows: Type Text Integer Real Date <Ignore> Sample [ConfigurationName] Header=2 Separator=tab DecimalSeparator=. Pattern=*.txt Xindex=1 Yindex=2 MeasIndex=4 Unit=0 Frequency=2110 Height=1.5 Gain=0 Losses=0 NbCol=23 Col0=1 Col3=4 Index 0 1 2 3 4
166
AT310_AM_E2
Col5=0 ...
The column type indexes are as follows: Type Text Integer Long Integer Single Double Date <Ignore> Sample [ConfigurationName] Header=2 Separator=tab DecimalSeparator=. Pattern=*.* Xindex=1 Yindex=2 Unit=0 Height=1.5 Gain=0 Losses=0 GenericNameIdOne= GenericNameIdTwo=BSID IdFormat=Decimal Techno=IEEE 802.16e NbCol=21 Col0=1 Col3=1 Index 0 1 2 3 4 5 6
167
Forsk 2011
Col4=4 ...
168
AT310_AM_E2
12 Initialisation Files
Initialisation files can be used to store operational and working environment settings. These files are optional, not required for working with Atoll, but are useful means for selecting required calculation methods and other settings. This chapter describes the formats of these files in detail: Atoll initialisation file (INI files) This file contains conventions, calculation settings, and other options. For more information on these options, see "Atoll Initialisation File" on page 169. The Atoll initialisation file may be automatically loaded when Atoll is run if: a. The file is identified in the command line parameter -Ini "inifilename" (see "Atoll Command Line Parameters" on page 31 for more information), or b. The file is named "Atoll.ini" and is located in the Atoll installation folder. This file will be ignored if an initialisation file is loaded through the command line parameter. You can open the Atoll.ini file in the Atoll installation folder for editing by pressing CTRL+SHIFT+i. If no Atoll.ini file exists, a blank Atoll.ini file is created. You have to restart Atoll in order to take into account any modifications in the Atoll.ini file.
ACP initialisation file (INI files) This file contains calculation settings and other options for the ACP module. For more information on these options, see "ACP Initialisation File" on page 205.
169
Forsk 2011
Prefix = "newprefix" Each new transmitter will be named newprefixN instead of Sitename_X (Sitename is the name of the site where the transmitter is located and X is the transmitter sector number on this site). Not adding the above lines, or setting the prefix to <Auto> (Prefix = "<AUTO>"), will instruct Atoll to keep the conventional naming method, i.e., each transmitter will be named Sitename_X. Furthermore, it is also possible to remove the underscore character "_" from the transmitters name, i.e., the transmitter can be named SitenameX instead of Sitename_X. To do this, add the following line in the [Transmitter] section of the Atoll.ini file: Underscore = 0 or 1 Setting this value to 0 means the underscore character will not be used when naming transmitters. The default value is 1. You can also define whether the suffix X in the transmitters name should be a number or a letter. The following two lines define this option in the Atoll.ini file: SuffixIsNum = 0 or 1 FirstCharSuffix = "A" When SuffixIsNum = 1, the default, the suffix X in the transmitter name Sitename_X will be a number. When it is set to 0, this suffix will be a letter. The starting suffix in this case will be A by default but can be changed to any other character through the second line. If you are using number suffixes, you can also initialise the number suffix at any other number than 1. To do this, you can add the following lines under the [Transmitter] section of the Atoll.ini file: First = X Where, X is a number.
170
AT310_AM_E2
You can also start Atoll, specifying a log file, by starting it with "Atoll.exe -log LogFile.log", either from the command line, or by modifying the shortcut parameters. If you have a log file defined in the Atoll.ini file, and run Atoll with the -log option in the command line, the command line log file will have priority over the one mentioned in the Atoll.ini file. The option available in Atoll.ini is more suitable for running Atoll using macros. Apart from these options, you also have the possibility to save the messages in the Event Viewer to a log file during an Atoll session (through the Event Viewer context menu).
12.1.1.7 Restricting the List of Predictions for Creating Sector Traffic Maps
When you create a sector traffic map, i.e., traffic map based on cell coverage areas, Atoll uses an existing best server coverage prediction in order to be able to distribute the live traffic data geographically. Atoll lets you select the best server coverage prediction on which the traffic map will be based. In the list of available best server coverage predictions, Atoll lists all the best server coverage prediction available in the Predictions folder, whether they were created using a margin or without. If you want Atoll to list only the best server coverage predictions that were created without a margin, i.e., with 0 dB margin, you can add the following lines to the Atoll.ini file: [Studies] SelectNullMarginOnly = 1 SelectNullMarginOnly is set to 0 by default, which means that Atoll lists all the best server coverage predictions available.
171
Forsk 2011
172
AT310_AM_E2
Enabling this option influences the export feature for all exportable vector fomats (MIF, TAB, AGD, SHP, TXT). When this option is enabled, only the largest polygon is exported for coverage layers having more than one polygon. You can enable this feature by adding the following lines in the Atoll.ini file: [Studies] EnableLBS = 1 Setting EnableLBS to 1 adds a new coverage prediction export format "LBS Polygon Files (*.txt)" to Atoll. The polygons are exported in a comma separated values format.
173
Forsk 2011
12.1.1.14 Setting the Precision for the Antenna Pattern Verification at Import
Atoll checks whether the vertical and horizontal patterns are correctly aligned at the extremities. The antenna patterns are correctly aligned when: the horizontal pattern attenuation at 0 is the same as the vertical pattern attenuation at the pattern electrical tilt angle, and the horizontal pattern attenuation at 180 is the same as the vertical pattern attenuation at the 180 less the pattern electrical tilt angle.
By default, the option is inactive, i.e., the pattern attenuations are considered the same if they differ less than 100 dB. If you want to change this default precision, add the following lines in the Atoll.ini file: [Antenna] PrecisionTimes10 = X Where X is the required precision in dB multiplied by 10. For example, if you want to set the precision to 0.5 dB, X will be 0.5 10 = 5 .
174
AT310_AM_E2
12.1.1.23 Exporting BMP, TIF, and PNG Files with a TAB Reference File
When exporting BMP, TIF, and PNG files, Atoll can export the georeference information in a TAB file instead of the default respective World files (BPW or BMW for BMP, TFW for TIF, and PGW for PNG). If you want Atoll to export the georeference information in a TAB file when you export in BMP, TIF, and PNG formats, add the following lines in the Atoll.ini file: [RasterExport] GeorefWithTAB = 1 GeorefWithTAB is set to 0 by default.
175
Forsk 2011
12.1.1.26 Adding the Duplicate Site to the Original Sites Site List
When you duplicate a site, you can choose to add the duplicate site to the site list (if any) of the original site by adding the following lines in the Atoll.ini file: [Site] AddToSiteListOnDuplicate = 1 AddToSiteListOnDuplicate is set to 0 by default.
176
AT310_AM_E2
12.1.1.32 Filtering Predictions by Technology When Reading the XML Studies File
In the XML studies file, some common CDMA coverage predictions may be available for both CDMA2000 and UMTS, or some common OFDMA coverage predictions may be available for both WiMAX and LTE. If you wish to filter the customized predictions stored in the XML studies file by their technology, e.g., separate the WiMAX and LTE coverage predictions, and only load the predictions specific to the technology of the current active Atoll document, add the following lines in the Atoll.ini file: [Studies] CustomStudiesFilteredByTechno = 1 CustomStudiesFilteredByTechno is set to 0 by default. This option is only relevant for reading the XML studies file. Atoll always writes the technology type in the XML studies file when customized coverage predictions are saved in it.
177
Forsk 2011
If you set ReportResolution to a very precise (low) value, the performance (calculation speed) can be considerably decreased depending on the size of the population maps in the document. It is recommended to set this parameter to an optimum value, i.e., just precise enough to get the required accuracy.
ExportOnlyVisibleLevels is set to 0 by default, which means that when any coverage prediction is exported, Atoll exports all its levels, visible or not. Atoll exports only visible coverage predictions. If a coverage prediction consists of only one level, the visibility check box of that level also controls the visibility check box of the prediction itself. This means that if the visibility check box of the only level of such a prediction is cleared, the prediction will itself be hidden and will not be exported.
178
AT310_AM_E2
Color = Colour of the symbol The default sites symbol is used when a new document is created in Atoll. To know the name of the font to use, and to set the symbol, you can use the Windows Character Map tool. You can use the copy/paste features to set the symbol in the Atoll.ini file. Example: [SitesSymbol] FontName = Wingdings Symbol = Size = 12 Color = 0
179
Forsk 2011
[StatusBar] DisplayZ = 0 DisplayClutterClass = 0 DisplayClutterHeight = 0 DisplayZ, DisplayClutterClass and DisplayClutterHeight respectively refer to the display of altitude, clutter class, and clutter height.
12.1.2.8 Setting the Maximum Number of Lines in Coverage Prediction Tool Tips
If you have more than one coverage prediction displayed on the map, the tool tips display the tip text for all the coverage predictions available at a pixel up to 30 lines by default. You can change this default number of tool tip text lines through the following option in the Atoll.ini file: [Studies] MultiplePlotsTipTextLines = X X is the number of lines to display in the tool tips. By default, MultiplePlotsTipTextLines is set to 30. If you set it to a very large value, however, the tool tip might not display correctly.
180
AT310_AM_E2
Where X is the number of digits that the CELL_IDENTITY field should contain. For example, CellIDNbDigits = 5 means that Atoll will display at least five digits in the CELL_IDENTITY field by adding leading zeros where required. This means that Atoll will display "00678" in the above example. However, if the CELL_IDENTITY field contains a number that has more than X digits, all the digits will still be displayed. For example, all seven digits in "9376562" will still be displayed even if CellIDNbDigits is set to 5.
This option works for both, application and service, modes of the distributed calculation server. The distributed calculation server (AtollSvr.exe) must be restarted in order to take into account the new value for the AtollSvrPriority option. The Realtime priority mode has not been implemented for reasons of stability.
181
Forsk 2011
[RemoteCalculation] DetectTimeOut = 5000 In this example, the detection time-out is set to 5000 ms.
You can also block access to GSM, UMTS, or LTE radio access technologies in 3GPP Multi-RAT documents using these options.
182
AT310_AM_E2
ACP_GSM = 0 ACP_UMTS = 0 ACP_WiMAX = 0 ACP_LTE = 0 GSM_AFP = 0 WiMAX_AFP = 0 LTE_AFP = 0 In order to carry out a combined GSM and UMTS optimisation using the ACP module, you must have access to both ACP module licences, i.e., ACP_GSM and ACP_UMTS both must not be set to 0.
183
Forsk 2011
12.1.6.5 Setting the Sign for KClutter When Importing Data From Planet EV
Planet EV uses the opposite sign for the Kclutter parameter with respect to Planet DMS. If you are importing data from Planet EV, you might have to change the sign of this parameter. You can instruct Atoll to change the sign for Kclutter when importing data from Planet EV by adding the following lines to the Atoll.ini file: [PlanetImport] ChangeKclutterSign = 1 ChangeKclutterSign is set to 0 by default.
184
AT310_AM_E2
Username and password are stored in the ATL file in an encrypted form. This option is only appropriate if the database connection string contains a password.
185
Forsk 2011
[Studies] AutoLock = 0 This setting is read by Atoll without Atoll having to be restarted.
12.1.7.4 Setting a Default Value for the Cell Edge Coverage Probability
The default value of the cell edge coverage probability can be configured in the Atoll.ini file. If you enter the following lines in the Atoll.ini file, Atoll will consider the value of the cell edge coverage probability defined in the Atoll.ini file as the default value, and will take it into account when performing point analysis, in the shadowing margins calculator, and will propose it as the default value for coverage prediction studies. [Shadowing] Reliability = 60 Reliability = 60 means 60 % cell edge coverage probability. The value of cell edge coverage probability used for automatic neighbour allocation and interference matrices calculation is stored in user configuration files (CFG).
12.1.7.6 Modifying the Resolution for the LOS Area Calculation Around a Site
The calculation of line of sight area around a given site uses the resolution of the geographic data as the default calculation resolution. These calculations can be time-consuming if the geographic data is available with a very high resolution. You can set the calculation resolution to a multiple of the resolution of the geographic data by adding the following lines in the Atoll.ini file:
186
AT310_AM_E2
[LOSArea] ResolutionMultFactor = X Where X is an integer. Therefore, setting ResolutionMultFactor to 2 will double the calculation resolution and decrease the time required for the calculation by half.
Use this option only if you are critically short of hard disk space. However, note that disabling temporary local copies might decrease the performance as it adds file access delays over the network.
12.1.7.10 Warning About Prediction Vailidity When Display Options are Modified
Coverage predictions have to be recalculated if you modify their display options. Atoll displays a warning message when you modify the display options for coverage predictions. To deactivate this warning message, add the following lines in the Atoll.ini file: [Studies] RecomputationWarning = 0 RecomputationWarning is set to 1 by default.
187
Forsk 2011
[Calculations] UseSiteAltitude = 0 UseSiteAltitude is set to 1 by default, which means that the altitude used in calculations will be the one which is either read from the Sites table or from the DTM at the sites coordinates, if the user-defined altitude is not available in the Sites table. Setting UseSiteAltitude to 0 means that, during calculations, Atoll will read the altitudes from the DTM at the exact coordinates of each transmitter considering the values entered for the DX and DY parameters. The above option is also valid for microwave links. In this case, setting UseSiteAltitude to 0 means that, during calculations, Atoll will read the altitudes from the DTM at the exact coordinates of each microwave link considering the values entered for the DX_A, DY_A, DX_B, and DY_B parameters. With UseSiteAltitude = 0, if DX and DY are 0, i.e., for transmitters and microwave links located at the site coordinates, Atoll will still use the altitudes defined per site, if any, or the altitudes from the DTM otherwise
188
AT310_AM_E2
Maximum number of calculation threads: NumberOfThreadsPathloss is the maximum number of threads that can be used for path loss calculations (4 by default, 8 maximum) NumberOfThreadsSimulation is the maximum number of threads that can be used for Monte Carlo simulation calculations (4 by default, 8 maximum) NumberOfThreadsStudy is the maximum number of threads that can be used for the calculation of coverage predictions (4 by default, 8 maximum) NumberOfThreadsStudyTile is the maximum number of threads that can be used per coverage prediction calculation (0 by default, 8 maximum). If you set this option to 0, Atoll will use actual number of available threads. NumberOfThreadsNeighbour is the maximum number of threads that can be used for automatic neighbour allocation (4 by default, 8 maximum) NumberOfThreadsMicrowave is the maximum number of threads that can be used for microwave link calculations (4 by default, 8 maximum)
All these options are upper limits per computer. Atoll supports a maximum of 64 parallel threads.
The parallel calculation of Monte Carlo simulations in TD-SCDMA, WiMAX 802.16d, WiMAX 802.16e, and LTE documents is disabled by default. It shoud not be enabled in TD-SCDMA documents.
189
Forsk 2011
In order to make this coverage prediction available in Atoll, add the following lines in the Atoll.ini file: [Studies] AerialStudy = 1
12.1.7.20 Estimating Required and Used Memory Size for UMTS Simulations
Atoll can estimate the required and used memory sizes for UMTS simulations and display the estimates in the Source Traffic tab of the new simulation group dialogue. Estimated memory size within the green region means low consumption, within the yellow region means medium consumption, within the orange region means high consumption, and within the red region means very high consumption, in which case the simulations might generate an out of memory error and not complete. To activate the memory estimation feature, add the following lines in the Atoll.ini file: [CDMA] PredictSimuMemorySize = 1 PredictSimuMemorySize is set to 0 by default which means the feature is not active.
12.1.7.21 Disabling Calculations Over NoData Values for DTM and Clutter Classes
If you dont want Atoll to calculate path losses on the pixels located over nodata values defined in the DTM and clutter classes files, add the following lines in the Atoll.ini file: [FskPropagModels] OptimOnNoData = 1 By default, OptimOnNoData is set to 0. This option only works with the propagation models available with Atoll by default.
190
AT310_AM_E2
If you set LinkedPredictionsComputationMode to any other value, the calculations are performed in parallel but without being managed by a task list. Calculations are carried out starting with the current document in the order of the coverage predictions in the Predictions folder.
191
Forsk 2011
The First Value method was the default method in earlier versions of Atoll which allowed multiple interference matrix import.
192
AT310_AM_E2
[Studies] RemoveBadMultiCells = 0 RemoveBadMultiCells is set to 1 by default. If you are not working with multi-band transmitters, i.e., MultiBandManagement is set to 0, Atoll does not automatically delete such records. If you want Atoll to automatically delete such records when opening the document from a database, you have to sett the following option in the Atoll.ini file: [Studies] CleanMultiCellManagement = 1 CleanMultiCellManagement is set to 0 by default.
12.1.8.7 Setting the Best Server Calculation Method in Same Priority HCS Layers
Atoll can calculate serving transmitters according to HCS layer priorities in coverage predictions. The signal level received from the serving transmitter must be higher than the minimum reception threshold ( T Rec ) for its HSC layer. If there are two HCS layers with different priorities: The serving transmitter is the one that belongs to the HCS layer with the highest priority.
HCS
2nd strategy: The serving transmitter is the one which has the highest received signal level.
The default strategy is the 1st one. You can use the 2nd strategy by adding the following lines in the Atoll.ini file: [Studies] UseThresholdForSameLayerPriorities = 0 UseThresholdForSameLayerPriorities is set to 1 by default.
193
Forsk 2011
12.1.8.15 Extending the Allowed Value Range for C/I and Reception Thresholds
Currently the subcell C/I threshold allows values from 0 to 24 dB and the rception threshold allows values from -116 to 50 dBm. If you wish to extend this range to 30 dB and -134 dBm for the C/I and reception thresholds respectively, add the following lines in the Atoll.ini file: [GSM] WideRangeSubcellThresholds = 1 WideRangeSubcellThresholds is set to 0 by default, which corresponds to the default value ranges.
194
AT310_AM_E2
This is set to 0 by default, which means that cell names will follow the normal convention of Atoll, SiteN_X(C). If there is only one carrier, meaning that C is unique, then this option can be set to 1. This will result in cell names which will be same as the transmitter names, SiteN_X.
If you choose to display the instantaneous HSDPA throughputs, Atoll will: Display the number of simultaneous HSDPA users in the simulation results. Place a certain part of HSDPA users in a waiting queue during simulations. Display the instantaneous gross and instantaneous application level throughputs per mobile and per cell in the simulation results. Display the instantaneous throughput per site in the Sites tab of the simulation results.
If you choose to display the peak HSDPA throughputs, Atoll will: Not display the number of simultaneous HSDPA users in the simulation results. Display the peak gross and peak application level throughputs per mobile and per cell in the simulation results. Display the MUG table in the cell properties. Input from this are used to calculate the peak gross throughput per cell when the scheduling algorithm is "Proportional Fair". Display the average HSDPA throughput per user in the Cells tab of the simulation results.
HSDPA resource scheduling will not be carried out. The HSDPA throughput for each user will be calculated by taking into account the MUG corresponding to the current number of connected HSDPA users. In Average Simulation results, the average HSDPA throughput per user can be calculated excluding the simulations where no HSDPA users were served. To do this, enter the following lines in the Atoll.ini file: [CDMA] HSDPAAvgSimuResults = 1 HSDPAAvgSimuResults = 0 by default.
195
Forsk 2011
0: Intra-cell interference calculation based on total power (Default) 1: Intra-cell interference calculation based on maximum power
If you set CQIDeltaWithPower to 1, the HS-PDSCH CQI will be calculated using the formula:
( CQI ) HS PDSCH = ( CQI ) pilot P pilot + P HS PDSCH
The above equations are in dB. Refer to the Technical Reference Guide for more details.
196
AT310_AM_E2
Where X is the number of times an HSDPA mobile should be rejected to be considered permanently rejected for the simulation.
Figure 12.1: Rasterization Process The primitive libraries, which perform the conversion from vector to raster, deal in terms of float values for the x and y coordinates of the vector polygons. Since these are float values, you will have to create vector polygons with the exact (accurate to all the decimal places) size of a pixel (or multiples of a pixel) in order to get raster pixels with the exact same surface area as the vector polygons. If the coordinates of the vector polygons are not accurate, it is possible that the raster pixel found from the vector polygon will be shifted 1 bin to the right or to the left. Such a rasterization means that the number of users in the vector remains correct, but the density might be different since the surface area has changed (Number of users = User Density x Area). If you want Atoll to increase the precision of the rasterization process for hotspots in your network. You can add the following lines in the Atoll.ini file: [Rasterization] Improve = 0 or 1 Precision = 1 SurfRatio = 20 MaximumSurf = 2500 The options are: Improve = 1 (by default) means that Atoll will use the accurate rasterization method for small polygons. Improve = 0 means that the normal rasterization method will be used for all polygons. Setting this option to 1 implies that this algorithm will not be used globally for all polygons, but only for small polygons which are defined by the options SurfRatio or MaximumSurf. Precision = 1 (by default) means that the rasterization resolution (step) used by the algorithm for small polygons is 1 metre. You can set it to a higher value if you observe performance degradation. The step of rasterization means the size of the bin used to approximate the vector shape with bins.
197
Forsk 2011
If you set Precision = 1, the performance (calculation speed) can be considerably decreased depending on the size of your network. It is recommended to set a higher value for the Precision option. SurfRatio = 20 (by default) means that the accurate algorithm will be used only for polygons whose size is smaller than 20 times the size of the normal raster bin. The normal raster bin size in an Atoll document is the finest resolution among the geographic data available in the document. If your Atoll document contains two geographic data files, one with a 20 m resolution and the other with a 5 m resolution, and you remove the 5 m one from your document, Atoll will still keep 5 m as the normal raster bin size. MaximumSurf = 2500 (by default) means that a polygon will be considered small only if its surface area is less than or equal to 2500 sq. m.
So, a polygon will be considered small, and will be rasterized using the accurate algorithm, if either the ratio of its surface area to the surface area of the normal raster bin is equal to or less than SurfRatio, or if its surface area is less than MaximumSurf. If you want to use just the MaximumSurf option, you can set the SurfRatio to 0.
198
AT310_AM_E2
199
Forsk 2011
[Studies] SCActivesetMaxSize = X Where X is the maximum number of transmitters in the active set. If you set SCActivesetMaxSize = 10, you will get the same results in the coverage prediction as the SC Interference tab in the point analysis.
12.1.9.22 Setting the Maximum UL Reuse Factor for HSUPA Users Noise Rise Estimation
In UMTS HSPA simulations, Atoll assumes a constant uplink reuse factor for estimating the maximum available noise rise per HSUPA user. This may cause unnecessary rejection of some HSUPA users in very low traffic cases. You can set an upper limit for the uplink reuse factor by adding the following lines in the Atoll.ini file: [UMTSSimus] MaxReuseFactor = X MaxReuseFactor is set to 5 by default.
802.16e:
12.1.10.2 Using Only Bearers Common Between the Terminals and Cells Equipment
If you want Atoll to perform an intersection over the bearers supported by the cell equipment and by the terminal equipment, add the following lines in the Atoll.ini file: [OFDM]
200
AT310_AM_E2
UseCommonBearersOnly = 1 UseCommonBearersOnly is set to 0 by default. When UseCommonBearersOnly is set to 1, Atoll only uses the bearers for which selection thresholds are defined in both the terminals and the cells equipment for both downlink and uplink bearer selection.
DisplaySignalsPerSCInPtA is set to 0 by default. When the DisplaySignalsPerSCInPtA option is set to "0" or is absent, SS & PBCH per subcarrier and PDCCH & PDSCH per subcarrier are not available options in a point analysis.
201
Forsk 2011
202
AT310_AM_E2
Basic_LTE_AFP = 1
203
Forsk 2011
ShieldingFactorOnWantedSignal = 0 ShieldingFactorOnWantedSignal is set to 1 by default, which means that the sheilding factor is taken into account at the receiver when calculating interference. On the transmitter side, the sheilding factor is always taken into account when calculating interference.
You have to add the following lines in the Atoll.ini file to display this information: [TestMobileData] ShowCoupleInfo = 1 Setting ShowCoupleInfo to 0 hides this information.
12.1.12.2 Setting the Number of Transmitters per Drive Test Data Path
By default, Atoll can import information about one serving transmitter (or cell in CDMA documents) and six neighbour transmitters (or cells in CDMA documents) for drive test data paths. You can change the number of transmitters per drive test data path by adding the following lines in the Atoll.ini file: [TestMobileData] NumberOfTestMobileTransmitters = X Where X is the number of transmitters per drive test data path. The default value of NumberOfTestMobileTransmitters is 7.
204
AT310_AM_E2
[TestMobileData] RecalcDist = 1 or 0 The default value of RecalcDist is 1, which means that Atoll will calculate the distance for each measurement point. The nearest serving cell is the one closest to the measurement point which has the same (Scrambling Code, SC Group), (BSIC, BCCH), or (PN Offset, PN Offset Group) pair as the point.
12.1.12.4 Defining the BCCH and BSIC Columns for FMT Import
The .fmt files generated by the TEMS Investigation GSM tool contain a number of columns. To define which of these columns should be imported as the BCCH column and which one as the BSIC column in Atoll, you can add the following lines in the Atoll.ini file: [TestMobileDataImportFmt] BCCHColumn = Column1 BSICColumn = Column2 Where, Column1 and Column2 are the titles of the two columns in the .fmt file corresponding to the BCCH and the BSIC columns respectively.
In order for the ACP initialisation file to be used by Atoll, you should place the acp.ini file in the Atoll installation directory. You can define a different location for the acp.ini file by setting the following option in the atoll.ini file: [ACP] iniFile = /path/to/the/ACP.ini The following sections describe the options available in the acp.ini file.
205
Forsk 2011
The local settings, defined using the ACP - Automatic Cell Planning Properties dialogue, take precedence over the same settings defined in the global acp.ini file. The settings in the acp.ini file are read when you start a new project to initialise the settings of the ACP. When using the acp.ini file to define options, instead of using the ACP Automatic Cell Planning Properties dialogue, you can also define any other settings even if they can not be set using the ACP - Automatic Cell Planning Properties dialogue. These settings redefined locally have precedence over the global settings.
206
AT310_AM_E2
zone.1.name=MyVectorZone2 # The name of the zone (in this case from SHP) zone.1.file=c:\path\to\file.shp # Absolute path to the SHP file.
207
Forsk 2011
param.lte.overlap.minRxLevel=-105 param.lte.coverage.autoPrediction=yes param.lte.coverage.isShadowing=no param.lte.coverage.cellEdgeCov=0.75 param.lte.cinr.autoPrediction=yes param.lte.cnir.isShadowing=no param.lte.cnir.cellEdgeCov=0.75 param.lte.cnir.useFreqBand=1 param.lte.cnir.useSegmentation=1 The following options are used to define the default threshold for each objective rule: quality.gsm.bcch.threshold=-85 quality.gsm.overlap.threshold=4 quality.umts.rscp.threshold=-85 quality.umts.ecio.threshold=-13 quality.umts.overlap.threshold=4 quality.cdma.rscp.threshold=-85 quality.cdma.ecio.threshold=-13 quality.cdma.overlap.threshold=4 quality.wimax.coverage.threshold=-85 quality.wimax.c.threshold=-85 quality.wimax.cn.threshold=20 quality.wimax.cinr.threshold=10 quality.wimax.overlap.threshold=5 quality.lte.coverage.threshold=-85 quality.lte.c.threshold=-85 quality.lte.cn.threshold=20 quality.lte.rsrp.threshold=-105 quality.lte.cinr.threshold=10 quality.lte.rsrq.threshold=-12 quality.lte.overlap.threshold=5 The following options are used to define the default objectives proposed by the ACP. All objectives defined with the option "auto=yes" are automatically created during a new setup. Others are available on the context menu used for creating new objectives. For the setting "objective.X.conditions.X.operande," a value of "0" means "<" (less than) and "1" means ">" (greater than).
objective.count=14 # The total number of objectives to be defined. objective.0.name=GSM Coverage # Name of objective "0" defined. objective.0.conditions.count=1 objective.0.conditions.0.layer=gsm objective.0.conditions.0.quality=bcch objective.0.conditions.0.threshold=-85 objective.0.conditions.operande=OR objective.0.auto=true objective.0.weight=1 objective.0.targetZone=-1 # -2=compZone, -1=focusZone, or other zone idx
objective.0.target.isAbsoluteCoverage=yes
208
AT310_AM_E2
objective.0.target.absoluteCoverage=90 objective.0.filter.count=0 ;; The following objective should be defined separately for each layer objective.1.name=GSM Cell Dominance # Name of objective "1" defined. objective.1.conditions.operande=AND objective.1.conditions.count=2 objective.1.conditions.0.layer=gsm objective.1.conditions.0.quality=overlap objective.1.conditions.0.operande=1 # "1" means ">" (greater than). objective.1.conditions.0.threshold=0 objective.1.conditions.1.layer=gsm objective.1.conditions.1.quality=overlap objective.1.conditions.1.operande=0 # "0" means "<" (less than) objective.1.conditions.1.threshold=4 objective.1.target.isAbsoluteCoverage=yes objective.1.target.absoluteCoverage=100 objective.2.name=UMTS RSCP Coverage # Name of objective "2" defined. objective.2.conditions.count=1 objective.2.conditions.0.layer=umts objective.2.conditions.0.quality=rscp objective.2.conditions.0.threshold=-85 objective.2.conditions.operande=OR objective.3.name=UMTS EcIo # Name of objective "3" defined. objective.3.conditions.count=1 objective.3.conditions.0.layer=umts objective.3.conditions.0.quality=ecio objective.3.conditions.0.threshold=-13 objective.3.conditions.operande=OR objective.3.target.isAbsoluteCoverage=yes objective.3.target.absoluteCoverage=100 objective.4.name=UMTS Pilot Pollution # Name of objective "4" defined. objective.4.auto=false objective.4.conditions.count=1 objective.4.conditions.0.layer=umts objective.4.conditions.0.quality=overlap objective.4.conditions.0.operande=0 # "0" means "<" (less than) objective.4.conditions.0.threshold=4 objective.4.conditions.operande=AND objective.4.target.isAbsoluteCoverage=yes objective.4.target.absoluteCoverage=100 objective.5.name=UMTS Soft Handover # Name of objective "5" defined. objective.5.auto=false objective.5.conditions.count=2 objective.5.conditions.0.layer=umts objective.5.conditions.0.quality=overlap
209
Forsk 2011
objective.5.conditions.0.operande=1 # "1" means ">" (greater than) objective.5.conditions.0.threshold=1 objective.5.conditions.1.layer=umts objective.5.conditions.1.quality=overlap objective.5.conditions.1.operande=0 # "0" means "<" (less than) objective.5.conditions.1.threshold=4 objective.5.conditions.operande=AND objective.5.filters.count=1 objective.5.filters.0.layer=umts objective.5.filters.0.quality=rscp objective.5.filters.0.operande=0 objective.5.filters.0.threshold=-95 objective.6.name=WiMAX Preamble Coverage # Name of objective "6" defined. objective.6.conditions.count=1 objective.6.conditions.0.layer=wimax objective.6.conditions.0.quality=coverage objective.6.conditions.0.threshold=-85 objective.6.conditions.operande=OR objective.7.name=WiMAX Preamble CINR # Name of objective "7" defined. objective.7.conditions.count=1 objective.7.conditions.0.layer=wimax objective.7.conditions.0.quality=cinr objective.7.conditions.0.operande=1 # "1" means ">" (greater than) objective.7.conditions.0.threshold=10 objective.7.conditions.operande=OR objective.7.target.isAbsoluteCoverage=yes objective.7.target.absoluteCoverage=100 objective.8.name=LTE RS Coverage # Name of objective "8" defined. objective.8.conditions.count=1 objective.8.conditions.0.layer=lte objective.8.conditions.0.quality=coverage objective.8.conditions.0.threshold=-85 objective.8.conditions.operande=OR objective.9.name=LTE RS CINR # Name of objective "9" defined. objective.9.conditions.count=1 objective.9.conditions.0.layer=lte objective.9.conditions.0.quality=cinr objective.9.conditions.0.threshold=10 objective.9.conditions.operande=OR objective.9.target.isAbsoluteCoverage=yes objective.9.target.absoluteCoverage=100 objective.10.name=CDMA Coverage # Name of objective "10" defined. objective.10.conditions.count=1 objective.10.conditions.0.layer=cdma objective.10.conditions.0.quality=coverage
210
AT310_AM_E2
objective.10.conditions.0.threshold=-85 objective.10.conditions.operande=OR objective.11.name=CDMA EcIo # Name of objective "11" defined. objective.11.conditions.count=1 objective.11.conditions.0.layer=cdma objective.11.conditions.0.quality=ecio objective.11.conditions.0.threshold=-13 objective.11.conditions.operande=OR objective.11.target.isAbsoluteCoverage=yes objective.11.target.absoluteCoverage=100 objective.12.name=CDMA Pilot Pollution # Name of objective "12" defined. objective.12.auto=false objective.12.conditions.count=1 objective.12.conditions.0.layer=cdma objective.12.conditions.0.quality=overlap objective.12.conditions.0.operande=0 # "0" means "<" (less than) objective.12.conditions.0.threshold=4 objective.12.conditions.0.threshold=4 objective.12.conditions.operande=AND objective.12.target.isAbsoluteCoverage=yes objective.12.target.absoluteCoverage=100 objective.13.name=CDMA Soft Handover # Name of objective "13" defined. objective.13.auto=false objective.13.conditions.count=2 objective.13.conditions.0.layer=cdma objective.13.conditions.0.quality=overlap objective.13.conditions.0.operande=1 # "0" means "<" (less than) objective.13.conditions.0.threshold=1 objective.13.conditions.1.layer=cdma objective.13.conditions.1.quality=overlap objective.13.conditions.1.operande=0 # "0" means "<" (less than objective.13.conditions.1.threshold=4 objective.13.conditions.operande=AND objective.13.filters.count=1 objective.13.filters.0.layer=cdma objective.13.filters.0.quality=coverage objective.13.filters.0.operande=0 objective.13.filters.0.threshold=-95
211
Forsk 2011
[ACPTplReconfPage] umts.disablePilotPowerOptimisation=1 umts.disableMaxPowerOptimisation=1 umts.SyncMultiCellPower=1 umts.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm # around actual value. If 0, use fixed value 37-46 cdma.1xrtt.SyncMultiCellPower=1 cdma.1xevdo.SyncMultiCellPower=1 cdma.1xrtt.disablePilotPowerOptimisation=1 cdma.1xrtt.disableMaxPowerOptimisation=1 cdma.1xevdo.disableMaxPowerOptimisation=1 cdma.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm # around actual value. If 0, use fixed value 37-46 gsm.disablePowerOptimisation=1 gsm.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm # around actual value. If 0, use fixed value 37-46 wimax.disablePreamblePowerOptimisation=1 wimax.SyncMultiCellPower=1 wimax.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm # around actual value. If 0, use fixed value 37-46 lte.disablePowerOptimisation=1 lte.SyncMultiCellPower=1 lte.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm # around actual value. If 0, use fixed value 37-46
The following options are used to define the default reconfiguration that will be done on transmitters and sites: disableAntennaOptimization=1 disableETiltOptimization=1 disableAzimuthOptimization=1 disableMechTiltOptimization=1 disableSiteSelection=1 The following options are used to specify default values for the reconfiguration ranges: defaultTxAzimuthVariation=20 defaultTxAzimuthStep=5 defaultTxAzimuthMinInterSector=0 defaultTxTiltMin=0 defaultTxTiltMax=5 defaultTxTiltStep=1 defaultTxETiltMin=0 defaultTxETiltMax=10 defaultTxHeightMin=0 defaultTxHeightMax=10 defaultTxHeightStep=5 defaultTxHeightMin.feet=0 defaultTxHeightMax.feet=30 defaultTxHeightStep.feet=15
212
AT310_AM_E2
umts.disablePilotPowerOptimization=0 umts.disableMaxPowerOptimization=0
213
Forsk 2011
The following options enable you to map clutter classes to propagation classes. Each mapping is defined on two lines: the first line defines the clutter class (by its code from the Description tab of the Clutter Classes Properties dialogue); the second line defines the propagation class (by its ID under Propagation on the Optimisation tab of the ACP Setup dialogue). The default propagation classes in the ACP are "Open" (ID "0"), "Vegetation" (ID "1"), and "Building" (ID "2"). Any additional propagation classes will have an ID assigned when they are created. clutterMapping.count=3 clutterMapping.0.clutterCode=10 clutterMapping.0.classCode=0 clutterMapping.1.clutterCode=4 clutterMapping.1.classCode=1 clutterMapping.2.clutterCode=6 clutterMapping.2.classCode=2 clutterMapping.3.clutterCode=7 clutterMapping.3.classCode=2 The following options define the default threshold and weight for the EMF exposure objective: [ACPEMFage] isPropClassesExtendable=1 # "1" enables user to create propagation classes.
12.2.2.7 Defining the Functionality of the ACP - Automatic Cell Planning Properties Dialogue
You can set options in the ACP.ini file to define the functionality of the ACP - Automatic Cell Planning Properties dialogue.
12.2.2.7.1
214
AT310_AM_E2
implements the appropriate methods of Atolls API). Delegating calculation to the propagation model provides more accurate tx.etilt.optimize=acp_etilt_use results but might take longer. Additionally, it will use disk space to store the calculation results. tx.etilt.min=acp_etilt_min [ACPAntMaskModelPage] tx.etilt.max=acp_etilt_max advancedUI=1 # The default tx.tilt.optimize=acp_tilt_use is "0"; the "Delegate Calculation to Model" # feature is disabled. tx.tilt.min=acp_tilt_min tx.tilt.max=acp_tilt_max to allow "Optimised" propagation models (i.e., propagation models that use the "Optimised" The following option can be used mode) to use "Full Path Loss" mode: tx.tilt.step=acp_tilt_step tx.azimuth.optimize=acp_azim_use # default is "0"; the feature is disabled. nativeAllowFullPathLoss=1 # The relative values from current azimuth tx.azimuth.deltamin=acp_azim_deltamin
12.2.2.8.1 tx.height.min=acp_height_min # absolute value for height values Defining Reconfiguration Values for Transmitters and Repeaters Using Custom Atoll Fields
tx.height.max=acp_height_max In the [ACPCustomFieldExtraction] section, you can set options that will enable ACP to extract data from custom fields from tx.height.step=acp_height_step the Atoll database. The custom columns in the Transmitters or Repeaters tables the Transmitters and Repeaters tables in must match the column name defined in the acp.ini file. tx.gsm.power.optimize=acp_gsmpower_use By default, the ACP does not extract custom fields. tx.gsm.power.min=acp_gsmpower_min [ACPCustomFieldExtraction] tx.gsm.power.max=acp_gsmpower_max in Transmitters and Repeaters table use to # The name of the custom column # initialize the reconfiguration parameter for each transmitter or repeater. tx.antenna.optimize=acp_ant_use tx.antenna.group=acp_ant_group # Best to define this column as a Boolean
215
Forsk 2011
tx.etilt.optimize=acp_etilt_use tx.etilt.min=acp_etilt_min tx.etilt.max=acp_etilt_max tx.tilt.optimize=acp_tilt_use tx.tilt.min=acp_tilt_min tx.tilt.max=acp_tilt_max tx.tilt.step=acp_tilt_step tx.azimuth.optimize=acp_azim_use # relative values from current azimuth tx.azimuth.deltamin=acp_azim_deltamin tx.azimuth.deltamax=acp_azim_deltamax tx.azimuth.min=acp_azim_min # absolute value for azimuth angle tx.azimuth.max=acp_azim_max tx.azimuth.step=acp_azim_step tx.azimuth.minInterSector=acp_azim_inter tx.height.optimize=acp_height_use tx.height.deltamin=acp_height_deltamin # relative values from current height tx.height.deltamax=acp_height_deltamax tx.height.min=acp_height_min # absolute value for height values tx.height.max=acp_height_max tx.height.step=acp_height_step tx.gsm.power.optimize=acp_gsmpower_use tx.gsm.power.min=acp_gsmpower_min tx.gsm.power.max=acp_gsmpower_max
12.2.2.8.2
216
AT310_AM_E2
wcell.power.max=acp_power_max wcell.power.step=acp_power_step The following options can be used to define the custom columns in the T4GCells table. These will be used for default reconfiguration options for LTE cells. By default, the value of each is undefined; therefore the field will not be extracted. [ACPCustomFieldExtraction] lcell.power.optimize=acp_power_use lcell.power.min=acp_power_min lcell.power.max=acp_power_max lcell.power.step=acp_power_step
12.2.2.8.3
[ACPCustomFieldExtraction] site.status=ACP_STATUS # Name of the custom column in Sites table. # Default value is 'ACP_STATUS'. site.status.candidate=candidate # Name used to define a candidate site. The following options can be used to define custom columns in the Sites table. These will be used for default reconfiguration options for each site. [ACPCustomFieldExtraction] site.locked=acp_site_locked site.removeable=acp_site_removable site.cellsRemoveable=acp_site_cellsRemovable site.azimLocked=acp_site_azimLocked site.heightLocked=acp_site_heightLocked
12.2.2.8.4
217
Forsk 2011
The following option can be used to name the custom columns in the Antennas table to automatically define the AEDT options. To optimise AEDT, you must set the "enableAedt" option to "1" first, in order to activate it.
[ACPCustomFieldExtraction] # The name of the custom column in ANTENNA table of type 'bool' used to # automatically generate patterns from the given aedt range antenna.aedtUse=ACP_AEDT_USE # The name of the custom column in ANTENNA table of type 'int', that defines the # aedt range antenna.aedtMin=ACP_AEDT_MIN # The name of the custom column in ANTENNA table of type 'int', that defines the # aedt range antenna.aedtMax=ACP_AEDT_MAX
12.2.2.9.1
The following is an example of the keys for the first site class (numbered "0") called "Planned" in this example. cost.classes.0.name=Planned cost.classes.0.azimuth.cost=1
218
AT310_AM_E2
cost.classes.0.azimuth.isSiteVisit=true cost.classes.0.tilt.cost=1 cost.classes.0.tilt.isSiteVisit=true cost.classes.0.antenna.cost=1 cost.classes.0.antenna.isSiteVisit=true cost.classes.0.etilt.cost=0.1 cost.classes.0.etilt.isSiteVisit=false cost.classes.0.height.cost=1 cost.classes.0.height.isSiteVisit=true cost.classes.0.power.cost=0.1 cost.classes.0.power.isSiteVisit=false cost.classes.0.siteVisitCost=2 cost.classes.0.upgradeSiteCost=5 cost.classes.0.newSiteCost=10 cost.classes.0.removeSiteCost=-5
12.2.2.9.2
[ACPCustomFieldExtraction] site.costClass=[name of custom field in Site table] The site class defined in the Sites table will be assigned automatically when an ACP optimisation is defined. For new candidate sites which are located on an existing site, the site class is the same as the site on which the new candidate is located. For new candidate sites which are not co-located on an existing site, the site class is set to "Default" and can be changed manually. By defining the costs of each site class as explained in "Defining Automatic Site Classes" on page 218, the cost structure is automatically defined as well.
12.2.2.10.1
219
Forsk 2011
There are two possible formats for defining the range of colours on maps: 1. Detailed format: The detailed format enables you to set a non-uniform range. The number of ranges is defined and, for each range, the minimum and maximum value of the range followed by its RGB color representation. colormap.<techno>.<quality>.nbRange=8 # Number of ranges to be defined colormap.<techno>.<quality>.range.0=[-99999.000000 -15.000000] RGB(0 0 255) colormap.<techno>.<quality>.range.1=[-15.000000 -13.000000] RGB(0 128 255) colormap.<techno>.<quality>.range.2=[-13.000000 -11.000000] RGB(0 196 196) colormap.<techno>.<quality>.range.3=[-11.000000 -9.000000] RGB(0 224 0) colormap.<techno>.<quality>.range.4=[-9.000000 -7.000000] RGB(128 255 0) colormap.<techno>.<quality>.range.5=[-7.000000 -5.000000] RGB(255 224 0) colormap.<techno>.<quality>.range.6=[-5.000000 -3.000000] RGB(255 128 0) colormap.<techno>.<quality>.range.7=[-3.000000 99999.000000] RGB(255 0 0) 2. Uniform format description: A uniform format description using a range and step: [firstBreak startcolor] [lastBreak endColor] interval: colormap.<techno>.<quality>.rangeDefinition=[-5 RGB(255 0 0)] [-20 RGB(0 0 255)] -5 These colormap descriptions are used for default colormap and can easily be changed by the user. The settings are the same for the various quality indicator of the various technologies, where you replace: <techno> with umts, gsm, lte, wimax, cdma <quality> with: In UMTS: ecio, ec, ecgain, eciogain In GSM: sl, slgain, In WiMAX: sl, slC, slCN, cinr, slgain, cinrgain In LTE: sl, slC, slCN, rsrp, cinr, rsrq, slgain, cinrgain
In addition a number of other colormaps can be defined for other type of maps: colormap.overlap and colormap.overlapgain for overlap maps colormap.objective and colormap.objective.gain for objective status maps and a few others for change maps, emf maps, etc. The default acp.ini file installed with the ACP has a complete list.
12.2.2.10.2
The following options define the pixel size used in the maps on the Quality Maps tab. You can let ACP automatically define the pixel size or you can define the pixel size: config.isAutoPixel=1 # Automatically calculate point size from coverage surface config.pixelSize=1 # If autopixel is not set, use this number of pixels for each point config.pixelCoverage=50 # If autopixel is set, calculate the pixel size of a point to try to cover the set percentage of the used surface config.maxPixelSize=6 # If autopixel is set, limit the pixel size to the set maximum. The following options define the size of the map title on the Quality Maps tab: config.titleHeight=16 # Title height in pixels config.titleFontSize=16 # Size of title font in points The following option defines the width of the margin in pixels on the Quality Maps tab: config.margin=2
220
AT310_AM_E2
The following options define the appearance of the map legend on the Quality Maps tab: config.showLegend=1 # Defines whether the legend is displayed. config.legendWidth=40 # Defines the width of the legend in pixels. config.legendFontSize=11 # Defines the font used in points. config.legendForeground=0 # RGB code as integer: here black The following option defines whether the axis is displayed on the Quality Maps tab: config.showAxis=1 The following options define the appearance of the histogram on the Quality Maps tab: config.showHistogram=1 # Defines whether the histogram is displayed. config.histogramHeight=60 # Defines the width of the histogram in pixels. The following options define the appearance of the focus zone on the Quality Maps tab: config.showFocusZone=1 # Defines whether the focus zone is displayed. config.focusLighterPercent=30 # Defines how much lighter the area outside the focus zone is displayed.
221
Forsk 2011
# define the font used by grid, graph component and map component DefaultFont=MS UI Gothic # for grid only, define the used font size. 0 mean default size DefaultGridFontSize=0
defaultStylesheetName=.acpReport.xslt # name of the default stylesheet file. set it empty to disable stylesheet processing instruction
222
AT310_AM_E2
memLimitMemory: Memory use is determined to be excessive when the estimated memory use in Mb, as defined in "memLimitMemory" is reached during a calculation. Setting "memLimitMemory" to "-1" deactivates this option. memLimitUseableMemory: Memory use is determined to be excessive when the estimated memory use exceeds the percentage of the total memory available for Atoll, as defined in "memLimitUseableMemory." Setting "memLimitUseableMemory" to "-1" deactivates this option.
If all three options are deactivated, ACP does not check excessive memory usage. The "abortIfMemLimitReach" option defines how ACP reacts if the defined maximum memory use is reached. By default (with "abortIfMemLimitReach" set to "0"), ACP will attempt to allocate memory. If unable to successfully allocate memory, ACP displays a message and the calculation is stopped. When using the option "abortIfMemLimitReach", then ACP will not start if the message indicating excessive memory use is displayed. By default, excessive memory use is considered an estimate of 80% of the memory available to the process; ACP is not prevented running even when 80% is exceeded. When ACP estimates actual memory use (i.e., using either "memLimitMemory" or "memLimitUseableMemory"), the memory estimate is only a rough estimate. Depending on the project, actual memory usage can be quite different.
memLimitNumPos=-1 # A setting of "-1" deactivates this option. memLimitMemory=-1 # A setting of "-1" deactivates this option. memLimitUseableMemory=80 # A setting of "-1" deactivates this option. abortIfMemLimitReach=0
12.2.3.4.1
Signal Level
You can define how ACP measures the signal level (UMTS RSCP, GSM BCCH Power, WiMAX Preamble Power, LTE Reference signal Power, CDMA pilot power) using the "linkMode" option. The "linkMode" option can have one of the following values: 0: When "linkMode" is set to "0," ACP considers the signal level on the downlink and transmission losses are taken into account. This is the default setting. 1: When "linkMode" is set to "1," ACP considers the signal level on the uplink and reception losses are taken into account. 2: When "linkMode" is set to "2," ACP does not take reception or transmission losses into account.
12.2.3.4.2
223
Forsk 2011
Any change you make here must match a corresponding change in the atoll.ini file. When "useSiteAltitude" is set to "1," the ACP results will only match the results in Atoll if the following setting is made in the atoll.ini file: useSiteAltitude=1 useSiteAltitude=1 # The default
The options described below are those used for the default operation mode The acp.ini options that define how the selected mode works are described below: maxMonitorCell: The "maxMonitorCell" defines the maximum number of cells monitored. This option affects memory use and accuracy. The analogous options for the high speed mode and the high precision mode are "maxMonitorCellSpeed" and "maxMonitorCellPrec", respectively. threshLevelMonitorCell: The "threshLevelMonitorCell" defines the best server signal threshold (dB) in order to be monitored. This option affects memory and accuracy. The analogous options for the high speed mode and the high precision mode are "threshLevelMonitorCellSpeed" and "threshLevelMonitorCellPrec", respectively.
The following options define the values ACP uses for default mode: maxMonitorCell=32 threshLevelMonitorCell = 35 The following options define the values ACP uses for high speed mode: maxMonitorCellSpeed=30 threshLevelMonitorCellSpeed = 30 The following options define the values ACP uses for high precision mode: maxMonitorCellPrec=35 threshLevelMonitorCellPrec = 40 Other options in the acp.ini file can be used to define additional offsets that will be used by the specific technology that ACP is optimising: threshLevelOffUmts=0 maxMonitorOffUmts=0 threshLevelOffGsm=0 maxMonitorOffGsm=0 threshLevelOffWimax=5 maxMonitorOffWimax=5 threshLevelOffLte=10 maxMonitorOffLte=10
224
AT310_AM_E2
gisDataTechnoShared=0 Atoll ACP loads raster data with block-based processing to reduce memory usage. The maximum memory (in Mb) allowed for this block processing in Mb is controlled with the following setting: gisDataCacheMemMax=256 You can reduce this number if you experience issues with ACP failure due to memory allocation.
pathlossAccessMode=2
wimaxPreambleSegmented=2
lteMultiAntennaInterference=2
wimaxMultiAntennaInterference=2
225
Forsk 2011
This option has the possible values: 0: Included. 1: Excluded. 2: ACP automatically detects the version of Atoll used, and hence the value used by Atoll for this option. This is the default value.
lteExcludeCPFromUsefulPower=2
wimaxExcludeCPFromUsefulPower=2
12.2.3.14 Fixed Ratio Between Pilot Power and Max Power (UMTS)
When optimising the maximum cell power in UMTS, the ACP forces the ratio between pilot power and maximum power to stay constant. You can remove this constraint using the following option: umtsPilotPowerRatioFixed=0
226
AT310_AM_E2
227
Forsk 2011
228
Part 3
Data Structures
This part of the administrator manual provides information on the data structures of the Atoll technology modules. In this part, the following are explained: "GSM GPRS EDGE Data Structure" on page 231 "UMTS HSPA Data Structure" on page 263 "LTE Data Structure" on page 295 "3GPP Multi-RAT Data Structure" on page 325 "CDMA2000 Data Structure" on page 335 "TD-SCDMA Data Structure" on page 365 "WiMAX Data Structure" on page 399 "Microwave Links Data Structure" on page 429
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
231
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
232
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
CodecModeAdaptations Table Field MAL_LENGTH Type Integer Description MAL length Attributes Null column allowed: Yes Default value:
233
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
CodecQualityTables Table Field MAL_LENGTH Type Integer Description MAL length Attributes Null column allowed: Yes Default value:
CustomFields Table Field CHOICE_TYPE Type Integer Description 0: Choice List is optional; 1: Choice List is mandatory Attributes Null column allowed: Yes Default value: 0
EGPRSQuality Table Field MAL_LENGTH Type Integer Description MAL length Attributes Null column allowed: Yes Default value:
EGPRSServices Table Field DL_ACTIVITY DL_MBR REQ_AVERAGE_DL_RATE REQ_AVERAGE_UL_RATE UL_ACTIVITY UL_MBR Type Float Float Float Float Float Float Description Activity factor for voice services on the downlink DL Maximum Throughput Requested Average Downlink Rate (kbps) Requested Average Uplink Rate (kbps) Activity factor for voice services on the uplink UL Maximum Throughput Attributes Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0
EGPRSTerminals Table Field DTX Type Boolean TplTransmitters Table Field COMMENT_ SHAREDMAST Type Text (255) Text (50) Description Comments Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Description DTX capability of terminal Attributes Null column allowed: No Default value: True
Transmitters Table Field SHAREDMAST Type Text (50) Description Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value:
TRGConfigurations Table Field TX_DIVERSITY_MODE_DL Type Short Description If more than one antenna are used (TX_DIVERSITY_NBANT), this field indicates if they are used 0- simultaneously (TXDiv) or 1- alternatively (antenna hopping) Attributes Null column allowed: Yes Default value: 0
234
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
TRGs Table Field BLOCKING_PROBA DTX_GAIN_DL TX_DIVERSITY_MODE_DL UL_TRAFFIC_LOAD Type Float Float Short Float Description Blocking probability (%) Downlink Gain due to DTX (dB) If more than one antenna are used (TX_DIVERSITY_NBANT), this field indicates if they are used 0- simultaneously (TXDiv) or 1- alternatively (antenna hopping) Subcells Uplink Traffic load Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1
235
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
Field TYPE
The format of the binary field, DIAGRAM, is described in "RF 2D Antenna Pattern Format" on page 105.
FIRST
236
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Description Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Unique key. Name of a resource group Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST.
Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 1
The FIRST and LAST fields of this table are of type Integer in the template (.mdb) and in a database (if connected to one). But these fields are of type Text when accessed or retrieved from an add-in.
237
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
Description Reference quality indicator name used for ideal link adaptation Name of Codec equipment Receiver reference noise
Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: -113
238
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Type Text (50) Text (50) Text (20) Short Integer Text (50) Text (20)
Description Codec equipment name Codec mode Frequency Band (empty = all bands) Frequency hopping 1=NH; 2= ideal FH; empty = all hopping modes MAL length Mobility (empty = all mobilities) Quality indicator name
Attributes Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value:
239
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
Description Decimal degrees Decimal degrees UTM, Undefined, NoProjection, Lambert1SP, Lambert2SP, Mercator, CassiniSoldner, TransMercator, TransMercatorSO, ObliqueStereographic, NewZealandMapGrid, HotineOM, LabordeOM, SwissObliqueCylindical
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
PROJ_METHOD
Short
Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.
240
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Reference noise of the equipment which has been used to produce the Null column allowed: Yes curves Default value: -113 GSM, GPRS or GPRS/EDGE. To allocate traffic to compatible transmitter Null column allowed: Yes mobile pair. Default value: GPRS
241
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
Hopping mode corresponding to the curves ( 1=NH; 2= ideal FH; empty = Null column allowed: Yes all hopping modes) Default value: MAL length Mobility (empty = all mobilities) Null column allowed: Yes Default value: Null column allowed: Yes Default value:
Maximum probability that a packet is blocked (delayed), GoS for circuit Null column allowed: Yes switched services Default value: 2 Maximum delay allowed for the service Null column allowed: Yes Default value: 1
242
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Field MAX_TS_SUPPORT MIN_THROUGHPUT MIN_THROUGHPUT_RATIO NAME REQ_AVERAGE_DL_RATE REQ_AVERAGE_UL_RATE TH_OFFSET TH_SCALE_FACTOR TYPE UL_ACTIVITY UL_MBR
Type Integer Float Float Text (50) Float Float Float Float Short Float Float
Description Maximum number of timeslots supported by the service Minimum user throughput requested for the service Dimensioning target of the % of surface where minimum throughput is reached Service Name Requested Average Downlink Rate (kbps) Requested Average Uplink Rate (kbps) Offset which should be added to the scale factor Percentage of end user throughput compared to MAC throughput Type of service (0: circuit; 1: packet; 2: circuit over packet) Activity factor for voice services on the uplink UL Maximum Throughput
Attributes Null column allowed: Yes Default value: 4 Null column allowed: Yes Default value: 15 Null column allowed: Yes Default value: 95 Null column allowed: No Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 95 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0
243
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
Field EGPRS_EQUIPMENT MAX_CS MAX_MCS NAME NOISE_FIGURE PMAX PRIMARY_BAND SAIC SECONDARY_BAND TECHNOLOGY
Type Text (50) Short Short Text (50) Float Float Text (50) Boolean Text (50) Text (15)
Description Associated GPRS/EDGE equipment (for PS services) Highest coding scheme (CS) available for GPRS Highest coding scheme (MCS) available for EDGE Terminal name Noise figure of the terminal Max power that can be used in UL (for UL calculations) Frequency band the mobile terminal is compatible with Terminal capability for Single Antenna Interference Cancellation (for future use) Frequency band the mobile terminal is compatible with (for dual-band mobile terminals) Technology supported by the mobile terminal
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 4 Null column allowed: Yes Default value: 12 Null column allowed: No Default value: Null column allowed: Yes Default value: 8 Null column allowed: Yes Default value: 33 Null column allowed: No Default value: Null column allowed: No Default value: False Null column allowed: Yes Default value: Null column allowed: Yes Default value:
244
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
List of frequencies to be excluded from the series defined by FIRST, LAST Null column allowed: Yes and STEP (separated with commas) Default value: Frequencies to be added. It is forbidden for EXTRA and EXLUDED to have Null column allowed: Yes common numbers Default value: Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Unique key. Name of a Resource Group Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 1
LAST
Integer
NAME
Text (50)
STEP
Integer
245
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
LAST
Integer
NAME
Text (50)
STEP
Integer
246
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Field PRIORITY
Type Short
Description Priority of the layer (largest value has the highest priority)
REASON
Integer
TRANSMITTER TYPE
TRANSMITTER
Text (50)
Text (50) Second part of the unique key. List of neighbours from another project. Integer Text (50) Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. Choice list: 0=Forced; 1=Forbidden; First part of the unique key. Transmitters or cells
247
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
Type Float
Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 (Manual) Null column allowed: No Default value: Null column allowed: Yes Default value:
Text (50) Second part of the unique key. List of neighbours from another project Integer Reason of the neighbourhood Choice list: 0=Manual; 1=Forced; 2=Co-site; 3=Adjacent; 4=Symmetric; 5=Distance; 6=Coverage; First part of the unique key. Transmitters or cells Type of the neighbourhood (handover, measurement)
TRANSMITTER TYPE
248
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Description Flag which indicates if this indicator is used in CS services Name of the measured figure used for this QI determination Choice list: 1=C; 2=CIR; Name of the managed quality indicator Flag which indicates if this indicator is used for PS services Flag which indicates if this QI must be interpolated or not
Attributes Null column allowed: No Default value: True Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: No Default value: True Null column allowed: No Default value: True
249
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
Repeater properties are saved in two tables: the donor-side parameters are in the Repeaters table and the coverage-side parameters in the Transmitters table. The repeater EIRP taken into account in calculations is stored in the Repeaters table (the EIRP column of the Transmitters table is not used).
250
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Field TX_ID
251
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
A text field pointing to ResourceGroups.NAME. It limits the BSIC domain Null column allowed: Yes of the site. Default value: Name of the BTS equipment Calculation radius used to define each transmitter calculation area Unit: m Extended calculation radius Unit: m Calculation resolution Extended calculation resolution Cell reselection offset Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
252
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Field CELL_SIZE
Type Float
CELL_TYPE
Text (50)
This field marks a set of records in the TRGConfigurations tables (all the Null column allowed: Yes records for which TRG_CONFIG has the same value.) Each of these Default value: records specifies a TRG that should exist in this transmitter. Associated Codec equipment (for voice services) The number of coding schemes supported by the GPRS/EDGE transmitters Comments Name of the equipment assigned to the GPRS/EDGE station Transmitters effective isotropic radiated power 'Yes' enables you to consider the transmitter as a GPRS/EDGE station Name of the feeder equipment Length of downlink feeder Unit: m Length of uplink feeder Unit: m Frame number offset Antenna height above the ground Unit: m Name of the Hierarchical Cell Structure layer If filled-in, takes precedence on the threshold value defined in the HCSLayers table Losses due to transmitter radio equipment Unit: dB Maximum number of inter-technology neighbours for the cell or the transmitter Maximum number of neighbours for the cell or the transmitter Maximum range (m) of coverage (for extended cells) Minimum range (m) of coverage (for extended cells) Miscellaneous downlink losses Miscellaneous uplink losses Template name Number of sectors Cell reselection offset for GPRS cells with PBCCH in use (For future use) Packet Broadcast Control Channel used or not (For future use) Reception threshold value for GPRS cells with PBCCH in use (For future use) Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 3 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value:
CODEC_EQUIPMENT CODING_SCHEME_NUMBER COMMENT_ EGPRS_EQUIPMENT EIRP ENABLE_EGPRS FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL FN_OFFSET HEIGHT LAYER LAYER_RECEPTION_THRESH OLD LOSSES MAX_EXT_NEIGHB_NUMBER MAX_NEIGHB_NUMBER MAX_RANGE MIN_RANGE MISCDLL MISCULL NAME NUM_SECTORS PBCCH_CELL_RESELECT_OFF SET PBCCH_IN_USE PBCCH_RECEPTION_THRESH OLD
Text (50) Short Text (255) Text (255) Float Boolean Text (50) Float Float Integer Float Text (50) Float Float Short Short Integer Integer Float Float Text (50) Integer Integer Boolean Float
253
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
Field POWER PROPAG_MODEL PROPAG_MODEL2 REDT REQ_CHANNELS SHAREDMAST TILT TMA_NAME TRX_MAX_NUMBER TX_TYPE
Type Float Text (255) Text (255) Float Integer Text (50) Float Text (50) Short Short
Description Transmitter power Name of the propagation model used to calculate predictions Name of the propagation model used to calculate extended prediction Remote Electrical tilt Number of required physical channels Shared mast name: enables antenna sharing between transmitters Mechanical downtilt of the main antenna Name of the Tower Mounted Amplifier equipment Maximum number of TRX that can be allocated by TRX dimensionning Type of transmitter (0 = Normal; 1 = Interferer only)
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
254
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Field CELL_TYPE CHANNELS CODEC_EQUIPMENT CODING_SCHEME_NUMBER COMMENT_ CONTROL_CHANNEL COST_FACTOR DX DY EGPRS_EQUIPMENT EIRP ENABLE_EGPRS FBAND FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL FN_OFFSET FROZEN HEIGHT HEXAGON_GROUP HOP_MODE HSN_FROZEN LAYER LAYER_RECEPTION_THRESH OLD LOSSES MAX_EXT_NEIGHB_NUMBER MAX_NEIGHB_NUMBER
Type
Description
Attributes
This field identifies a set of records in the TRGConfigurations tables (all Null column allowed: Yes Text (50) the records that point to this cell-type) each of these records specifies a Default value: TRG that should exist in this transmitter. DCS1800_N_Normal Text (255) Text (50) Integer Text (255) Integer Double Float Float Text (50) Float Boolean Text (20) Text (50) Float Float Integer Boolean Float Text (50) Text (25) Boolean Text (50) Float Float Integer Integer Physical channels allocated to the transmitter Associated Codec equipment (for voice services) The number of coding schemes supported by the GPRS/EDGE transmitters Additional information about the transmitter Physical channel used as Broadcast Control Channel (BCCH) Used by the AFP assign priorities to transmitters X coordinate relative to the site location Y coordinate relative to the site location Name of the equipment assigned to the GPRS/EDGE station Transmitters effective isotropic radiated power 'Yes' enables you to consider the transmitter as a GPRS/EDGE station Name of the frequency band Name of the feeder equipment Length of feeder in DL Length of feeder in UL Frame Number offset Only TRXs that are not frozen and belong to non-frozen cells can be assigned frequencies by the AFP. Antenna height above the ground Unit: m Group of hexagons used to create this transmitter The hopping mode of the default traffic TRG in this transmitter. Only TRGs belonging to non-HSN-frozen cells, and which have non_HSN_frozen configurations, can be assigned HSNs by the AFP. Name of the Hierarchical Cell Structure layer If filled-in, takes precedence on the threshold value defined in the HCSLayers table Losses due to transmitter radio equipment Unit: dB Maximum number of inter-technology neighbours for the transmitter Maximum number of neighbours for the transmitter Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 43 Null column allowed: No Default value: False Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: False Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: False Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value:
255
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
Description Maximum range (m) of coverage (for extended cells) Minimum range (m) of coverage (for extended cells) Miscellaneous DL loss Miscellaneous UL loss The total number of TRXs in this transmitter. In the cases of no or Base band hopping, it must correspond to the number of channels in the CHANNELS field. Cell reselection offset for GPRS cells with PBCCH in use (For future use) Packet Broadcast Control Channel used or not (For future use) Reception threshold value for GPRS cells with PBCCH in use (For future use) Transmitter power Name of the propagation model used to calculate prediction Name of the propagation model used to calculate extended prediction Remote Electrical tilt Number of required TRXs Shared mast name: enables antenna sharing between transmitters Name of the site on which the transmitter is located (from the Sites table) Mechanical downtilt of the first antenna Name of the TMA equipment Maximum number of TRX that can be allocated by TRX dimensionning Transmitter name Type of transmitter (0 = Normal; 1 = Interferer only)
Attributes Null column allowed: Yes Default value: 35000 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: False Null column allowed: Yes Default value: -102 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Default model Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 16 Null column allowed: No Default value: Null column allowed: Yes Default value: 0
NUM_TRX PBCCH_CELL_RESELECT_OFF SET PBCCH_IN_USE PBCCH_RECEPTION_THRESH OLD POWER PROPAG_MODEL PROPAG_MODEL2 REDT REQ_CHANNELS SHAREDMAST SITE_NAME TILT TMA_NAME TRX_MAX_NUMBER TX_ID TX_TYPE
Float
Integer Boolean Float Float Text (255) Text (255) Float Integer Text (50) Text (50) Float Text (50) Short Text (50) Short
256
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Description Minimum C/I First part of unique key. By default, 1. The cost factor will be used to increase or decrease the importance of subcells of this configuration. This is a default value of a subcell specific parameter. It is set to true if the TRXs of the subcell use Discontinuous transmission This is a default value of a subcell specific parameter. Hopping mode can be Non Hopping, Base Band Hopping, or Synthesized Hopping. This is a default value of a subcell specific parameter. It denotes the minimum received power required to be served by this subcell. This is a default value of a subcell specific parameter: the average power offset with respect to the BCCH channel. Default TRX equipment of TRXs belonging to this subcell All frequencies assigned to TRXs of this configuration must belong to this domain. Domains contain grouping info as well. Percentage of Half Rate voice traffic in the subcell. All HSNs assigned to subcells of this configuration must belong to this domain. Only subcells that point to non-hsn_frozen configurations in nonhsn_frozen cells can by be assigned HSNs by the AFP. Limitation on length of the MAL (Mobile allocation list). Average value of DL power control The percentage of traffic that is considered to overflow from the subcell. Second part of unique key Timeslot configuration If more than one antenna are used (TX_DIVERSITY_NBANT), this field indicates if they are used 0- simultaneously (TXDiv) or 1- alternatively (antenna hopping) TX diversity Choice list: 1=No TX diversity; 2=TX diversity with 2 antennas;
Attributes Null column allowed: No Default value: 12 Null column allowed: No Default value: Null column allowed: No Default value: 1 Null column allowed: No Default value: True Null column allowed: No Default value: Non Hopping Null column allowed: No Default value: -102 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 40 Null column allowed: No Default value: Null column allowed: No Default value: False Null column allowed: No Default value: 48 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1
DEF_HOP_MODE
Text (25)
DEF_MIN_RECEPTION DEF_POWER_OFFSET DEF_TRX_EQUIPMENT FREQUENCY_DOMAIN HR_RATIO HSN_DOMAIN HSN_FROZEN MAXIMAL_MAL MEAN_POWER_CONTROL TRAFFIC_OVERFLOW_TARGE T TRX_TYPE TS_CONFIGURATION_NAME
Float Float Text (25) Text (50) Float Text (50) Boolean Integer Float Float Text (15) Text (50)
TX_DIVERSITY_MODE_DL
Short
TX_DIVERSITY_NBANT
Short
257
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
Field AFP_FREEZE_DIM AFP_SEP_COST ASSIGN_MODE BAD_QUAL_UB BLOCKING_PROBA C_OVER_I_MIN COST_FACTOR CS_ERLANGS DEF_TRX_EQUIPMENT DTX DTX_GAIN_DL EFFECTIVE_TRAFFIC_OVERFL OW EXCLUDED FREQUENCY_DOMAIN HOP_MODE
Type Boolean Float Text (25) Float Float Float Float Float Text (25) Boolean Float Float Text (250) Text (50) Text (25)
Description Permit the AFP to not always respect the number of required TRXs Secondary AFP quality indicator One of the two options: Free or Group constrained.
Attributes Null column allowed: No Default value: False Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Free
Additional constraints on subcell quality (considered in AFP): maximum Null column allowed: Yes probability to have C/I lower than C_OVER_I_MIN. Default value: 1 Blocking probability (%) Minimum C/I By default, 1. The cost factor is used to increase or decrease the importance of subcells of this configuration. Circuit switched demand in Erlangs Default TRX equipment of TRXs belonging to this subcell It is set to true if the TRXs of the subcell use Discontinuous transmission. Downlink Gain due to DTX (dB) Effective traffic overflow List of frequencies which should not be used by TRX of the current subcell. Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 12 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: True Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value:
All frequencies assigned to TRXs of this configuration must belong to this Null column allowed: Yes domain. Domains contain grouping info as well. Default value: The hopping mode of a subcell can be Non Hopping, Base Band Hopping, or Synthesized Hopping. Percentage of Half rate traffic in the subcell. Assigned HSN. All HSNs assigned to subcells of this configuration must belong to this domain. Only subcells that point to non-hsn_frozen configurations in nonhsn_frozen cells can be assigned HSNs by the AFP. Limitation on length of the MAL (Mobile allocation list). Average value of DL power control Minimum reception power required to be served by this subcell. The average power offset with respect to the BCCH channel. Frequency group which should be used if possible Packet switched demand in data Erlangs (equivalent to avaraged used time slots) Number of required channels. Defines synchronization sets. Null column allowed: Yes Default value: Non Hopping Null column allowed: Yes Default value: 40 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: False Null column allowed: Yes Default value: 48 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: -102 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value:
HR_RATIO HSN HSN_DOMAIN HSN_FROZEN MAXIMAL_MAL MEAN_POWER_CONTROL MIN_RECEPTION POWER_OFFSET PREFERRED_FREQ_GROUP PS_DATA_ERLANGS REQ_CHANNELS SYNCHRO_NAME
Float Integer Text (50) Boolean Integer Float Float Float Text (50) Float Integer Text (50)
258
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Description TRAFFIC_LOAD = (Traffic in Erlangs) / (NUM_TRX * Multyplexing_factor ) (Where, Multiplexing_factor = 8). The percentage of traffic that is considered to overflow from one subcell. Second part of a unique key. Points to the TRX type table. Timeslot configuration If more than one antenna are used (TX_DIVERSITY_NBANT), this field indicates if they are used 0- simultaneously (TXDiv) or 1- alternatively (antenna hopping) TX diversity Choice list: 1=No TX diversity; 2=TX diversity with 2 antennas; First part of a unique key. It is the transmitter to which this subcell belongs. (The cell type can be retrieved by following this link). Subcells Uplink Traffic load
Attributes Null column allowed: No Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 1
TX_DIVERSITY_MODE_DL
Short
259
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
Description An order on TRXs in the same subcell. It is the second part of a unique key. The couple TX_ID, TRG_TYPE is the key of the TRGs table to which this TRX belongs First part of a unique key. It points to Transmitters. The value of the field CELL_TYPE in the Transmitters table can therefore be retrieved and can serve in order to access relevant information in the TRGConfigurations table. Inter-network uplink noise rise Uplink noise rise
Attributes Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
TX_ID
Text (50)
Float Float
260
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
261
Atoll 3.1.0 Administrator Manual Chapter 13: GSM GPRS EDGE Data Structure
Forsk 2011
262
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
263
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
264
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
265
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
CustomFields Table Field CHOICE_TYPE Type Integer Description 0=Choice list is optional; 1=Choice list is mandatory; Attributes Null column allowed: Yes Default value: 0
HSUPAUECategories Field UE_CATEGORY_NAME Type Text (50) Description Name of the HSUPA UE category Attributes Null column allowed: Yes Default value:
TplTransmitters Field COMMENT_ MC_HSDPA_MUG MC_HSDPA_SCHED_ALGO MULTI_CARRIER SHAREDMAST Transmitters Field MC_HSDPA_MUG MC_HSDPA_SCHED_ALGO MULTI_CARRIER SHAREDMAST Type Memo Short Short Text (50) Description Multi-carrier HSDPA multi user gain MUG=f(#users) Scheduling algo used for HSDPA multi-carrier users. 0=MAXC/I (MAx C/ I), 1=RR (Round Robin), 2=PF (Proportional Fair) Multi-carrier mode: 0=None; 1=Dual-cell; Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 2 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Type Text (255) Memo Short Short Text (50) Description Comments Multi-carrier HSDPA multi user gain MUG=f(#users) Scheduling algo used for HSDPA multi-carrier users. 0=MAXC/I (MAx C/ I); 1=RR (Round Robin); 2=PF (Proportional Fair); Multi-carrier mode: 0=None; 1=Dual-cell; Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
266
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
UECategories Field MULTI_CARRIER UE_CATEGORY_NAME Type Short Text (50) Description Multi-carrier mode: 0=None; 1=Dual-cell; Name of the HSDPA UE category Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value:
UMTSServices Field ADPCH_ACTIVITY CARRIER_LIST CARRIER_SUPPORT CPC_SUPPORT DL_GBR DL_MBR EDPCH_ACTIVITY UL_GBR UL_MBR Type Float Text (50) Integer Short Float Float Float Float Float Description Activity Factor for HSDPA users List of preferred carrier numbers Carrier support type: 0=Prefered; 1=Allowed; Continuous packet connectivity support: None; DL DRX / UL DTX; HSSCCH Less operation; HS-FACH; Guaranted downlink bit rate (kbps) Maximum downlink bit rate (kbps) Activity Factor for HSUPA users Guaranted uplink bit rate (kbps) Maximum uplink bit rate (kbps) Attributes Null column allowed: Yes Default value: 0.1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0.1 Null column allowed: Yes Default value: Null column allowed: Yes Default value:
UMTSTerminals Field CPC_SUPPORT Type Short Description Continuous packet connectivity support: None; DL DRX / UL DTX; HSSCCH Less operation; HS-FACH Attributes Null column allowed: Yes Default value: 0
267
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
The format of the binary field, DIAGRAM, is described in the "RF 2D Antenna Pattern Format" on page 105.
268
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Description Uplink losses due to the configuration of the BTS (duplexer and/or combiner) Name of Base Station Equipment Noise figure of Base Station Rho factor to model self generated interference (100%=ideal)
Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 100
269
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
Field LOCKED_SC MAX_DL_LOAD MAX_EXT_NEIGHB_NUMBER MAX_INTERCAR_NEIGHB_NB MAX_NEIGHB_NUMBER MAX_R99BEARER_DL_RATE MAX_R99BEARER_UL_RATE MAX_UL_LOAD MIMO_SUPPORT NUM_HS_SCCH NUM_HSDPA_USERS NUM_HSUPA_USERS OTHERS_CCH_POWER PILOT_POWER POWER_MAX PWR_HEADROOM REUSE_DIST SC_DOMAIN_NAME SCH_POWER SCRAMBLING_CODE TOTAL_POWER TX_ID UL_LOAD UL_REUSE_FACTOR UPLINK_EXTERNAL_NOISE_R ISE
Type Boolean Float Integer Integer Integer Float Float Float Short Short Short Short Float Float Float Float Float Text (50) Float Integer Float Text (50) Float Float Float
Description Field used to freeze allocated SC of the cell during automatic allocation
Maximum downlink load allowed (percentage of max power used). Used Null column allowed: Yes in power control simulation Default value: 50 Maximum number of inter-technology neighbours for the cell Maximum number of inter-carrier neighbours for this cell Maximum number of neighbours for the cell Max bearer rate available in DL (kbps) Max bearer rate available in UL (kbps) Maximum uplink load allowed (percentage). Used in power control simulation MIMO features supported: 0=None; 1=Transmit Diversity; 2=SU-MIMO; Number of HS-SCCH channels Number of served HSDPA users in the cell: calculated by the WCDMA simulation algorithm Number of served HSUPA users in the cell: calculated by the WCDMA simulation algorithm Power of other common channels except SCH Power of the pilot channel Maximum power supported by the transmitter Power Control Headroom (dB) for DCH (used in WCDMA simulation algorithm) Minimum reuse distance for scrambling codes Scrambling code domain name. Power of the synchronisation (SCH) channel Scrambling code. Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm Name of the transmitter Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm Uplink (I intra+ I extra)/ I intra: calculated by the WCDMA simulation algorithm Inter-network uplink noise rise Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1000 Null column allowed: Yes Default value: 1000 Null column allowed: Yes Default value: 75 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 30 Null column allowed: Yes Default value: 33 Null column allowed: Yes Default value: 43 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 21 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0
270
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Description Cell identity Inter-network downlink noise rise Name of the site equipment Inter-network uplink noise rise
Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 15
271
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
Field SERVICE
PROJ_METHOD
Short
PROJ_SCALE_FACTOR PROJ_SECOND_PARALLEL
Double Double
272
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Field PROJ_ZONE_NUMBER
Type Integer
See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.
273
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
Field SPREADING_WIDTH
Type Double
274
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Type Float Short Memo Short Short Text (50) Text (50)
Description Downlink diversity gain (D-TxAA) HSDPA Bearer index Maximum spatial multiplexing capacity gain graphs Number of reception antennas used for MIMO Number of transmission antennas used for MIMO UE mobility Type of receiver of the User Equipment
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: No Default value: Standard
275
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
276
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Description Inter-network channel protection = f( MHz) Interfering bandwidth (kHz) Interfering technology Victim bandwidth (kHz)
Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: 0
TRANSMITTER
Text (50)
Text (50) Second part of the unique key. List of neighbours from another project.
277
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
Description Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. Choice list: 0=Forced; 1=Forbidden; First part of the unique key. Transmitters or cells
Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value:
Text (50) Second part of the unique key. List of neighbours from another project Reason of the neighbourhood Choice list: 0=Manual; 1=Forced; 2=Co-site; 3=Adjacent; 4=Symmetric; 5=Distance; 6=Coverage; First part of the unique key. Transmitters or cells Type of the neighbourhood (handover, measurement)
REASON
Integer
TRANSMITTER TYPE
278
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Field IOISNTOT NAME NTISNTOT POWERS_RELATIVE_TO_PILO T PTOT_RELATIVE_TO_PMAX RSCP_COMPRESSED_THRESH OLD SHARED_RESULTS_FOLDER SPREADING_WIDTH SYSTEM_ TECHNOLOGY
Type Boolean Text (50) Boolean Boolean Boolean Float Text (255) Float Text (50) Text (10)
Attributes Null column allowed: No Default value: True Null column allowed: No Default value:
Nt includes pilot signal or not Cell paging and Synchro powers, Service Allowed DL min and max TCH powers are absolute values or relative to cell pilot power Cell total power is absolute value (dBm) or relative to Cell maximum power (%) RSCP threshold for compressed mode activation (for future use) Shared results storage folder Spreading width (MHz) Name of the system Name of the technology
Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: No Default value: -100 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 3.84 Null column allowed: No Default value: UMTS Null column allowed: No Default value: CDMA
MEAS_PARAM
Short
279
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
For DL part of Bearer: Minimum transmitter power on traffic channel for Null column allowed: Yes the bearer not to exceed Default value: -20 Bearer type (0: Empty, 1: Interactive, 2: Conversational, 3: Background ,4: Streaming) Bearer nominal rate in uplink Unit: kbps Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 9.6
280
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Description Maximum uplink output power (dBm) Minimum gain of the amplifier (dB) Name of the repeater equipment Repeater noise Figure (dB) Step of amplifier gain (dB) Time delay in the equipment (microseconds)
Attributes Null column allowed: Yes Default value: 12 Null column allowed: Yes Default value: 50 Null column allowed: No Default value: Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 5
Repeater properties are saved in two tables: the donor-side parameters are in the Repeaters table and the coverage-side parameters in the Transmitters table.
281
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
LAST
Integer
NAME
Text (50)
STEP
Integer
282
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Field TX_ID_OTHER
Description Second part of the unique key. Second cell name in a symmetric relation
283
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
Description First part of the unique key. Name of the list Second part of the unique key. Name of the site
Attributes Null column allowed: No Default value: Null column allowed: No Default value:
284
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Field CDMA_EQUIPMENT CELL_SIZE CELLS_POWER_SHARING CHANNEL_ELEMENTS_DL CHANNEL_ELEMENTS_UL COMMENT_ DOWNLINK_EXTERNAL_NOIS E_RISE DYN_HS_SCCH_POWER_ALL OC DYN_HSDPA_POWER_ALLOC FBAND FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL HEIGHT HS_SCCH_POWER HSDPA_MAX_CODES HSDPA_MAX_USERS HSDPA_MIN_CODES HSDPA_MUG_TABLE HSDPA_PWR HSDPA_SCHEDULER_ALGO HSPA_SUPPORT HSUPA_DLPOWER HSUPA_MAX_USERS HSUPA_UL_LOAD MAX_DL_LOAD MAX_EXT_NEIGHB_NUMBER
Type Text (50) Float Boolean Integer Integer Text (255) Float Boolean Boolean Text (50) Text (50) Float Float Float Float Short Short Short Memo Float Short Short Float Short Float Float Short
Description CDMA equipment Hexagon radius Unit: m If true, cells' powers are shared for HSDPA users Number of channel elements for downlink Number of channel elements for uplink Comments Inter-network downlink noise rise Allocation of power for HS-SCCH (True=Dynamic, False=Static) Allocation of power for HSDPA (True=Dynamic, False=Static) Frequency band Name of the feeder equipment Length of downlink feeder Unit: m Length of uplink feeder Unit: m Antenna height above the ground Unit: m Value of power dedicated to a HS-SCCH channel. In case of dynamic allocation, it is the maximum available power. Maximum number of HS-PDSCH codes Max number of HSDPA users managed simultaneously by the scheduler Minimum Number of HS-PDSCH codes Lookup table giving MUG=f(#users) Amount of power (dBm) dedicated to HSDPA Scheduling algo used for HSDPA users. 0=MAXC/I (MAx C/I), 1=RR (Round Robin), 2=PF (Proportional Fair) HSPA features supported: 0: None; 1: HSDPA; 2: HSPA; 3: HSPA+ Amount of power (dBm) dedicated to HSUPA DL chanels (E-AGCH, ERGCH, E-HICH Max number of HSUPA users managed simultaneously by the scheduler Uplink transmitter load factor due to HSUPA users: calculated by the WCDMA simulation algorithm
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
Maximum downlink load allowed (percentage of max power used). Used Null column allowed: Yes in power control simulation Default value: Maximum number of inter-technology neighbours for the cell or the transmitter Null column allowed: Yes Default value:
285
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
Field MAX_INTERCAR_NEIGHB_NB MAX_IUB_RATE_DL MAX_IUB_RATE_UL MAX_NEIGHB_NUMBER MAX_R99BEARER_DL_RATE MAX_R99BEARER_UL_RATE MAX_UL_LOAD MC_HSDPA_MUG MC_HSDPA_SCHED_ALGO MISCDLL MISCULL MULTI_CARRIER NAME NOISE_FIGURE NUM_HS_SCCH NUM_HSDPA_USERS NUM_HSUPA_USERS NUM_RX_ANTENNAS NUM_SECTORS NUM_TX_ANTENNAS OTHERS_CCH_POWER PILOT_POWER POWER_MAX PROPAG_MODEL PROPAG_MODEL2 PWR_HEADROOM REDT
Type Integer Float Float Short Float Float Float Memo Short Float Float Short Text (50) Float Short Short Short Short Integer Short Float Float Float Text (255) Text (255) Float Float
Description Maximum number of inter-carrier neighbours for this cell Max Iub Backhaul rate for downlink Max Iub Backhaul rate for uplink Maximum number of neighbours for the cell or the transmitter Max bearer rate available in DL (kbps) Max bearer rate available in UL (kbps) Maximum uplink load allowed (percentage). Used in power control simulation Multi-carrier HSDPA multi user gain MUG=f(#users) Scheduling algo used for HSDPA multi-carrier users. 0=MAXC/I (MAx C/ I); 1=RR (Round Robin); 2=PF (Proportional Fair); Miscellaneous downlink losses Miscellaneous uplink losses Multi-carrier mode: 0=None; 1=Dual-cell; Template name Noise figure used to determine the thermal noise at the transmitter Number of HS_SCCH channels Number of served HSDPA users in the cell: calculated by the WCDMA simulation algorithm Number of served HSUPA users in the cell: calculated by the WCDMA simulation algorithm Number of transmission antenna ports available at the transmitter Number of sectors Number of reception antenna ports available at the transmitter Power of common channels (except SCH) Power of the pilot channel Maximum power supported by the transmitter Name of the propagation model used to calculate predictions Name of the propagation model used to calculate extended prediction Power Control Headroom (dB) for DCH (used in WCDMA simulation algorithm) Remote Electrical tilt
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 3 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
286
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Field REUSE_DIST RXLOSSES SC_DOMAIN_NAME SCH_POWER SHAREDMAST TILT TMA_NAME TOTAL_POWER TX_DIVERSITY_CFG TX_MAX_POWER TXLOSSES UL_LOAD UL_REUSE_FACTOR UPLINK_EXTERNAL_NOISE_R ISE
Type Float Float Text (50) Float Text (50) Float Text (50) Float Integer Float Float Float Float Float
Description Minimum reuse distance for scrambling codes Losses in the uplink due to transmitter radio equipment Unit: dB Scrambling code domain name Power of the synchronisation (SCH) channel Shared mast name: enables antenna sharing between transmitters Mechanical downtilt of the main antenna Name of the Tower Mounted Amplifier equipment Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm TX diversity configuration 1- No TX diversity 2- TX div. open loop 3- TX div. closed loop Maximum power sharable between sectors. Losses in the downlink due to transmitter radio equipment Unit: dB Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm Uplink (I intra+ I extra)/ I intra: calculated by the WCDMA simulation algorithm Inter-network uplink noise rise
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
287
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
Field CELLS_POWER_SHARING COMMENT_ DX DY FBAND FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL HEIGHT HEXAGON_GROUP MC_HSDPA_MUG MC_HSDPA_SCHED_ALGO MISCDLL MISCULL MULTI_CARRIER NOISE_FIGURE NUM_RX_ANTENNAS NUM_TX_ANTENNAS
Type Boolean Text (255) Float Float Text (50) Text (50) Float Float Float Text (50) Memo Short Float Float Short Float Short Short Text (255) Text (255) Float Float Text (50) Text (50) Float Text (50) Short
Description If true, cells' powers are shared for HSDPA users Additional information about the transmitter X coordinate relative to the site location Y coordinate relative to the site location Frequency band Name of the feeder equipment Length of feeder in DL Length of feeder in UL Antenna height above the ground Unit: m Group of hexagons used to create this transmitter Multi-carrier HSDPA multi user gain MUG=f(#users) Scheduling algo used for HSDPA multi-carrier users. 0=MAXC/I (Max C/ I); 1=RR (Round Robin); 2=PF (Proportional Fair); Miscellaneous DL loss Miscellaneous UL loss Multi-carrier mode: 0=None; 1=Dual-cell; Noise figure used to determine the thermal noise at the transmitter Number of transmission antenna ports available at the transmitter Number of reception antenna ports available at the transmitter
Attributes Null column allowed: No Default value: False Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 2 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 5 Null column allowed: No Default value: 1 Null column allowed: No Default value: 1 Null column allowed: Yes Default value: Default model Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value:
PROPAG_MODEL
Name of the propagation model used to calculate extended prediction Remote Electrical tilt Losses in the uplink due to transmitter radio equipment Shared mast name: enables antenna sharing between transmitters Name of the site on which the transmitter is located (from the Sites table) Mechanical downtilt of the first antenna Name of the TMA equipment
TX diversity configuration: 1=No TX diversity; 2=TX div. open loop; 3=TX Null column allowed: Yes div. closed loop; Default value: 0
288
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Description Transmitter name Maximum power sharable between sectors Losses in the downlink due to transmitter radio equipment
Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: 43 Null column allowed: Yes Default value: 0
289
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
290
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Field DL_PACKET_EFFICIENCY DL_SP DL_SPC_MAX DL_SPC_MIN EDPCH_ACTIVITY ENABLE_DOWNGRADING NAME PRIORITY R99BEARER REQ_AVERAGE_DL_RATE REQ_AVERAGE_UL_RATE TH_OFFSET TH_SCALE_FACTOR TYPE UL_ACTIVITY UL_DP UL_DPC UL_GBR UL_MBR UL_NPC UL_PACKET_EFFICIENCY UL_SP UL_SPC_MAX UL_SPC_MIN USE_HANDOFF
Type Float Integer Float Float Float Boolean Text (50) Integer Text (50) Float Float Float Float Short Float Float Float Float Float Integer Float Integer Float Float Boolean
Description Packet efficiency factor on the downlink Packet size (Bytes) on the downlink Downlink max Packet call size (kBytes) Downlink min Packet call size (kBytes) Activity Factor for HSUPA users Service supports lower bearer than nominal bearer Service name Priority level of the service: parameter used in the WCDMA simulation Name of the R99 Bearer Requested Average Downlink Rate (kbps) Requested Average Uplink Rate (kbps) Offset to add to the above ratio Ratio between application throughput and RLC layer throughput Type of service: 0=circuit; 1=packet; 2=circuit over packet; Activity factor for circuit switched service on the uplink Packet inter arrival time (ms) on the uplink Reading time (distance) between two packet calls (ms) on the uplink Guaranted uplink bit rate (kbps) Maximum uplink bit rate (kbps) Number of packet calls during a session on the uplink Packet efficiency factor on the uplink Packet size (Bytes) on the uplink Uplink max Packet call size (kBytes) Uplink min Packet call size (kBytes) 'Yes' if the service supports soft handoff
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1500 Null column allowed: Yes Default value: 2000 Null column allowed: Yes Default value: 4 Null column allowed: Yes Default value: 0.1 Null column allowed: No Default value: True Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 95 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1500 Null column allowed: Yes Default value: 2000 Null column allowed: Yes Default value: 4 Null column allowed: No Default value: False
291
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
Description Eb/Nt target on the downlink for a type of mobility Eb/Nt target on downlink in case of TX diversity closed loop Eb/Nt target on downlink in case of TX diversity open loop Second part of the unique key. Type of mobility
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: Standard Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
Type of receiver First part of the unique key. Name of the R99 Bearer Eb/Nt target on the uplink for a type of mobility Eb/Nt target on uplink in case of 2RX diversity Eb/Nt target on uplink in case of 4RX diversity
292
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Field HSPA_SUPPORT HSUPA_UE_CATEGORY LOSS MUD_FACTOR NAME NOISE_FACTOR NOISE_FACTOR_SEC NUM_RX_ANTENNAS PMAX PMIN PRIMARY_BAND RAKE_EFFICIENCY RHO_FACTOR RX_EQUIP SECONDARY_BAND UE_CATEGORY
Type Short Short Float Float Text (50) Float Float Short Float Float Text (50) Float Short Text (50) Text (50) Short
Description HSPA features supported: 0=None; 1=HSDPA; 2=HSPA; Category of the User Equipment for HSUPA Receiver antenna loss
Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0
Advanced Receiver Factor to model intra-cell interference reduction for Null column allowed: Yes HSDPA terminals only Default value: 0 Terminal name Noise figure used to determine the thermal noise at the receiver Null column allowed: No Default value: Null column allowed: Yes Default value: 8
Noise figure used to determine the thermal noise at the receiver (for the Null column allowed: Yes secondary frequency band) Default value: 8 Number of reception antenna ports available at the terminal Maximum receiver power on traffic channel Minimum receiver power on traffic channels Primary frequency band Efficiency of the rake receiver. Used for combination of Active Set member contributions Rho factor to model self generated interference Type of the User Equipment Receiver Secondary frequency band Category of the User Equipment for HSDPA Null column allowed: No Default value: 1 Null column allowed: Yes Default value: 21 Null column allowed: Yes Default value: -20 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: No Default value: 100 Null column allowed: Yes Default value: Standard Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1
293
Atoll 3.1.0 Administrator Manual Chapter 14: UMTS HSPA Data Structure
Forsk 2011
Description Display coordinate system when creating database Unit used for gains (dBd or dBi) Choice list: 0=dBd; 1=dBi; Projected coordinate system for geo data Reception unit when creating database Choice list: 0=dBm; 1=dbV; 2=dbV/m; Transmission unit when creating database Choice list: 0=dBm; 1=Watts; 2=kWatts;
Attributes Null column allowed: Yes Default value: -1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: -1 Null column allowed: No Default value: 0 Null column allowed: No Default value: 0
294
AT310_AM_E2
295
Forsk 2011
296
AT310_AM_E2
CustomFields Table Field CHOICE_TYPE Type Integer Description 0=Choice list is optional; 1=Choice list is mandatory Attributes Null column allowed: Yes Default value: 0
FrequencyBands Table Field GUARD_BAND Type Float Description Guard band between carriers (MHz) Attributes Null column allowed: Yes Default value: 0
297
Forsk 2011
lframeconfigs Table (New) Field N_RB_GROUP0 N_RB_GROUP1 N_RB_GROUP2 N_RB_TOTAL NAME Type Text (255) Text (255) Text (255) Short Text (50) lpcidomains Table (New) Field DOMAIN_NAME Type Text (50) Description Name of the physical cell ID domain Attributes Null column allowed: No Default value: Description Frequency blocks belonging to the first group (PSS ID 0) Frequency blocks belonging to the second group (PSS ID 1) Frequency blocks belonging to the third group (PSS ID 2) Number of frequency blocks for which the configuration is defined Name of the ICIC frame configuration Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value:
lpcigroups Table (New) Field DOMAIN_NAME EXCLUDED EXTRA FIRST Type Text (50) Text (225) Text (225) Integer Description Name of the physical cell ID domain List of IDs to be excluded from the series defined by FIRST, LAST and STEP (separated by blank characters) IDs to be added. It is forbidden for EXTRA and EXLUDED to have common numbers. Separator must be a blank character. Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Name of the physical cell ID group in the domain Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Attributes Null column allowed: Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 1
LAST
Integer
NAME STEP
Neighbours Table Field RELATION_TYPE Type Short Description Type of the neighbour relation: 0=Intra-carrier; 1=Inter-carrier Attributes Null column allowed: Yes Default value: 0
Networks Table Field BS_SELECTION SSF_CONFIG Type Short Short Description Best server selection method: 0=RS C; 1=RSRP; TDD: Special subframe configuration (0; 1; 2; 3; 4; 5; 6; 7; 8;) Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
298
AT310_AM_E2
RepeaterEquipments Table (New) Field COMMENT_ MANUFACTURER MAX_AMPLIFIER_GAIN MAX_OUTPUT_DL MAX_OUTPUT_UL MIN_AMPLIFIER_GAIN NAME NOISE_FIGURE STEP_AMPLIFIER_GAIN TIME_DELAY Type Text (255) Text (50) Float Float Float Float Text (50) Float Float Float Description Comments Manufacturer of the repeater equipment Maximum gain of the amplifier (dB) Maximum downlink output power (dBm) Maximum uplink output power (dBm) Minimum gain of the amplifier (dB) Name of the repeater equipment Repeater noise Figure (dB) Step of amplifier gain (dB) Time delay in the equipment (microseconds) Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 90 Null column allowed: Yes Default value: 30 Null column allowed: Yes Default value: 12 Null column allowed: Yes Default value: 50 Null column allowed: No Default value: Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 5
Repeaters Table (New) Field AMPLIFIER_GAIN AZIMUT DONOR_CELLID DONOR_LINK_LOSS DONOR_LINK_TYPE DONOR_PROPAG_MODEL DOWNTILT EQUIPMENT_NAME FEEDER_NAME FEEDERLENGTH HEIGHT REC_ANTENNA REC_FEEDERLENGTH_UL TOTAL_GAIN TOTAL_GAIN_UL Type Float Float Text (50) Float Short Text (50) Float Text (50) Text (50) Float Float Text (50) Float Float Float Description Gain of the amplifier Azimuth of the donor side antenna Name of the donor cell Loss (dB) between donor and donor side of the repeater 1- Off air 2- Microwave 3- Fibre Name of the propagation model used to calculate prediction between donor and repeater Downtilt of the donor side antenna If no equipment, the repeater is a passive component Name of the donor side feeder Length of donor side feeder Height of the donor side antenna Name of the donor side antenna Length of donor side uplink feeder Total gain to be applied to donor cell pilot power Uplink total gain to be applied to mobile output power Attributes Null column allowed: Yes Default value: 80 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
299
Forsk 2011
Field TX_ID
Description Name of the transmitter (and of the transmitter used for coverage)
Description Angular distributions of downlink power Percentage of downlink traffic load carried by the smart antenna Name of the ICIC frame configuration Number of DL connected users for the cell Number of DL connected users for the cell Name of the physical cell ID domain
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value:
T4GServices Table Field DL_LOWEST_BEARER UL_LOWEST_BEARER Type Short Short Description The lowest bearer allowed to be used for this service in DL The lowest bearer allowed to be used for this service in UL Attributes Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1
T4GTerminals Table Field UE_CATEGORY Type Text (50) Description UE category Attributes Null column allowed: Yes Default value:
T4GUECategories Table (New) Field BEST_MODULATION DL_TBS_MAX MAX_MIMO_RX_ANTENNAS NAME UL_TBS_MAX Type Short Float Short Text (50) Float Description Highest supported modulation in uplink Choice list: 0=BPSK; 1=QPSK; 2=16QAM; 3=64QAM; Maximum number of transport block bits per TTI in downlink Maximum number of reception antenna ports UE category name Maximum number of transport block bits per TTI in uplink Attributes Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 0
TplTransmitters Table Field COMMENT_ FRAME_CONFIG PCI_DOMAIN_NAME Type Text (255) Text (50) Text (50) Description Comments ICIC frame configuration Name of the physical cell ID domain Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
300
AT310_AM_E2
Description Name of the smart antenna equipment Shared mast name: enables antenna sharing between transmitters
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value:
Transmitters Table Field SA_NAME SHAREDMAST Type Text (50) Text (50) Description Name of the smart antenna equipment Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value:
301
Forsk 2011
Field PHYSICAL_ANTENNA
The format of the binary field, DIAGRAM, is described in "RF 2D Antenna Pattern Format" on page 105.
302
AT310_AM_E2
Description Decimal degrees Meters Meters Decimal degrees Decimal degrees Decimal degrees UTM, Undefined, NoProjection, Lambert1SP, Lambert2SP, Mercator, CassiniSoldner, TransMercator, TransMercatorSO, ObliqueStereographic, NewZealandMapGrid, HotineOM, LabordeOM, SwissObliqueCylindical
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
PROJ_METHOD
Short
Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.
303
Forsk 2011
Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value:
304
AT310_AM_E2
Type Text (255) Text (255) Text (255) Short Text (50)
Description Frequency blocks belonging to the first group (PSS ID 0) Frequency blocks belonging to the second group (PSS ID 1) Frequency blocks belonging to the third group (PSS ID 2) Number of frequency blocks for which the configuration is defined Name of the ICIC frame configuration
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value:
LAST
Integer
NAME STEP
305
Forsk 2011
REASON
Integer
306
AT310_AM_E2
Field REASON
Type Integer
Description Reason of the neighbourhood Choice list: 0=Manual; 1=Forced; 2=Co-site; 3=Adjacent; 4=Symmetric; 5=Distance; 6=Coverage; Reference cell Type of the neighbourhood (handover, measurement)
Attributes Null column allowed: Yes Default value: 0 (Manual) Null column allowed: No Default value: Null column allowed: Yes Default value:
TRANSMITTER TYPE
DEFAULT_MODEL DEFAULT_RESOLUTION DMAX INTERFERERS_RX_THRESH NAME PDCCH_SYMBOLS POWER_CONTROL_MARGIN PUCCH_AVG_NRB RS_EPRE_DEFINITION SHARED_RESULTS_FOLDER SP_PERIODICITY SSF_CONFIG SYSTEM_ TECHNOLOGY THERMAL_NOISE
Text (50) Float Float Float Text (50) Short Float Float Short Text (255) Short Short Text (50) Text (10) Float
307
Forsk 2011
308
AT310_AM_E2
Description Maximum downlink output power (dBm) Maximum uplink output power (dBm) Minimum gain of the amplifier (dB) Name of the repeater equipment Repeater noise Figure (dB) Step of amplifier gain (dB) Time delay in the equipment (microseconds)
Attributes Null column allowed: Yes Default value: 30 Null column allowed: Yes Default value: 12 Null column allowed: Yes Default value: 50 Null column allowed: No Default value: Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 5
309
Forsk 2011
Repeater properties are saved in two tables: the donor-side parameters are in the Repeaters table and the coverage-side parameters in the Transmitters table.
0 = Peak RLC Throughput; 1 = Effective RLC Throughput; 2 = Application Null column allowed: Yes Throughput Default value: 0 0 = Peak RLC Throughput; 1 = Effective RLC Throughput; 2 = Application Null column allowed: Yes Throughput Default value: 0 UL Bandwidth Allocation Target: 0 Full Bandwidth; 1 Maintain Connection; 2 Best Bearer Null column allowed: Yes Default value: 2
310
AT310_AM_E2
Description Height of the pylon at site The nature of site. This field is for information only
Attributes Null column allowed: Yes Default value: 50 Null column allowed: Yes Default value: 0
311
Forsk 2011
312
AT310_AM_E2
Field CELL_ID CHANNEL CHANNEL_STATUS COMMENT_ DIVERSITY_SUPPORT DIVERSITY_SUPPORT_UL DL_FFR_USAGE DL_LOAD DOWNLINK_EXTERNAL_NOIS E_RISE FBAND FRAME_CONFIG ICIC_DELTAPL_TH ICIC_SUPPORT ID_REUSE_MIN_DIST ID_STATUS MAX_DL_LOAD MAX_EXT_NEIGHB_NUMBER MAX_NEIGHB_NUMBER MAX_NUMBER_OF_USERS MAX_UL_LOAD NOISE_RISE_ICIC_UL NOISE_RISE_UL NUM_DL_USERS NUM_UL_USERS PBCH_POWER_OFFSET PCI_DOMAIN_NAME PDCCH_POWER_OFFSET
Type Text (50) Integer Short Text (255) Short Short Float Float Float Text (50) Text (50) Float Short Float Short Float Integer Integer Integer Float Float Float Float Float Float Text (50) Float
Description Name of the cell Channel number Channel allocation status (0 = Not allocated, 1 = Allocated, 2 = Locked) Additional information about the cell The type of antenna diversity supported by the cell in downlink The type of antenna diversity supported by the cell in uplink Percentage of the downlink traffic load carried by the ICIC part of the cell Downlink cell traffic load Inter-network downlink noise rise Frequency band of the cell Name of the ICIC frame configuration Maximum difference in dB between the best server path loss and second best Server path loss to be considered in ICIC zone Inter -Cell Interference Coordination Support 0=None; 1=Static DL; 2=Static UL The minimum reuse distance for the AFP and physical cell ID allocation Physical cell ID status (0 = Not allocated, 1 = Allocated, 2 = Locked) Maximum traffic load allowed on downlink Maximum number of inter-technology neighbours for this cell Maximum number of intra-technology neighbours for this cell Max supported number of users for the cell Maximum traffic load allowed on uplink Noise rise received by cell edge traffic Uplink noise rise (dB). Manually specified by the user or calculated during simulations. Number of DL connected users for the cell Number of UL connected users for the cell EPRE offset for PBCH with respect to RS EPRE Name of the physical cell ID domain EPRE offset for PDCCH with respect to RS EPRE
Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 100 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 100 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0
313
Forsk 2011
Field PDSCH_POWER_OFFSET PHY_CELL_ID POWER RANK RS_EPRE RSRQ_THRES RX_EQUIPMENT SCH_POWER_OFFSET SCHEDULER SF_CONFIG TX_ID UL_FPC_CINR_MAX UL_FPC_FACTOR UL_FPC_NR_MAX UL_LOAD UL_MU_SM_GAIN UPLINK_EXTERNAL_NOISE_R ISE
Type Float Integer Float Short Float Float Text (50) Float Text (50) Short Text (50) Float Float Float Float Float Float
Description EPRE offset for PDSCH with respect to RS EPRE Physical cell ID Maximum output power Unit: dBm Zero based order used by scheduler for sequential cell selection Energy per resource Element of reference signals Required RSRP for coverage Reception equipment installed at the cell EPRE offset for SS with respect to RS EPRE Scheduler used by the cell Subframe configuration used by the cell in case of TDD frequency band Name of the transmitter to which the cell belongs Target PUSCH C/(I+N) provides Po_pusch and is driven by noise rise limitations of neighbouring cells. This field will be output from simulation. Factor enabling reduction of transmission powers of cell-edge users FPC Off;0; 0.4;0.5;0.6;0.7;0.8;0.9;1 Maximum uplink noise rise Uplink cell traffic load Multi-user (collaborative) MIMO gain in uplink Inter-network uplink noise rise
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 43 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: -140 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 20 Null column allowed: No Default value: 1 Null column allowed: Yes Default value: 6 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
314
AT310_AM_E2
Field NAME
315
Forsk 2011
Field DL_MBR DL_NPC DL_SP DL_SPC_MAX DL_SPC_MIN NAME PRIORITY REQ_AVERAGE_DL_RATE REQ_AVERAGE_UL_RATE TH_OFFSET TH_SCALE_FACTOR TYPE UL_ACTIVITY UL_DP UL_DPC UL_GBR UL_HIGHEST_BEARER UL_LOWEST_BEARER UL_MBR UL_NPC UL_SP UL_SPC_MAX UL_SPC_MIN
Type Float Integer Integer Float Float Text (50) Short Float Float Float Float Short Float Float Float Float Float Short Float Integer Integer Float Float
Description Maximum sustained trasmission rate in DL (Maximum Bit Rate) Number of packet calls during a session in downlink Packet size (Bytes) in downlink Downlink maximum packet call size (kBytes) Downlink minimum packet call size (kBytes) Service name Service priority (0: lowest) Requested Average Downlink Rate (kbps) Requested Average Uplink Rate (kbps) Offset to add to TH_SCALE_FACTOR Ratio between application level throughput and RLC layer throughput Service type Choice list: 0=Voice; 1=Data; Activity factor for voice services on the uplink Packet inter-arrival time (ms) in uplink Reading time (distance) between two packet calls (ms) in uplink Minimum required transmission rate in UL (Guaranteed Bit Rate) The highest bearer allowed to be used for this service in UL The lowest bearer allowed to be used for this service in UL Maximum sustained trasmission rate in UL (Maximum Bit Rate) Number of packet calls during a session in uplink Packet size (Bytes) in uplink Uplink maximum packet call size (kBytes) Uplink minimum packet call size (kBytes)
Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1500 Null column allowed: Yes Default value: 2000 Null column allowed: Yes Default value: 4 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: 95 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 15 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1500 Null column allowed: Yes Default value: 2000 Null column allowed: Yes Default value: 4
316
AT310_AM_E2
Type Float Float Text (50) Text (50) Float Text (50)
Description Average number of calls per hour for circuit switched services or average number of sessions per hour for packet switched services Volume transferred on the downlink during a session (for packet switched services) Unit: Kbyte Service (from the Service table) that the subscriber may request Type of terminal (from the Terminal table) used by the subscriber for the service Volume transferred on the uplink during a session (for packet switched services) Unit: Kbyte User profile name
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: No Default value:
RX_EQUIP
Text (50)
UE_CATEGORY
Text (50)
UE category
317
Forsk 2011
Calculation radius used to define each transmitter calculation area Unit: Null column allowed: Yes m Default value: Second calculation radius Unit: m Null column allowed: Yes Default value:
318
AT310_AM_E2
Field CALC_RESOLUTION CALC_RESOLUTION2 CELL_SIZE CHANNEL_LIST COMMENT_ DIVERSITY_SUPPORT DIVERSITY_SUPPORT_UL DL_FFR_USAGE DL_LOAD DOWNLINK_EXTERNAL_NOIS E_RISE FBAND FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL FRAME_CONFIG HEIGHT ICIC_DELTAPL_TH ICIC_SUPPORT ID_REUSE_MIN_DIST MAX_DL_LOAD MAX_EXT_NEIGHB_NUMBER MAX_NEIGHB_NUMBER MAX_NUMBER_OF_USERS MAX_UL_LOAD MISCDLL MISCULL NAME
Type Integer Integer Float Text(255) Text (255) Short Short Float Float Float Text (50) Text (50) Float Float Text (50) Float Float Short Float Float Integer Integer Integer Float Float Float Text (50)
Description Calculation resolution Second calculation resolution Radius of the cell (schematically represented by an hexagon) Unit: m Channel numbers used by transmitters Comments Type of diversity support used in downlink 0=None, 1=Diversity, 2=SU-MIMO, 3=AMS Type of diversity support used in uplink 0=None, 1=Diversity, 2=SU-MIMO, 3=AMS, 4=MU-MIMO Percentage of the downlink traffic load carried by the ICIC part of the cell Downlink traffic load Inter-network downlink noise rise Frequency band of the cell Name of the feeder equipment Length of downlink feeder Unit: m Length of uplink feeder Unit: m ICIC frame configuration Antenna height above the ground Unit: m Maximum difference in dB between the best server path loss and second best Server path loss to be considered in ICIC zone Inter -Cell Interference Coordination Support 0=None; 1=Static DL; 2=Static UL The minimum reuse distance for the AFP and physical cell ID allocation Maximum traffic load allowed on downlink Maximum number of inter-technology neighbours Maximum number of intra-technology neighbours Max supported number of users for the cell Maximum traffic load allowed on uplink Miscellaneous downlink loss Miscellaneous uplink loss Template name
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value:
319
Forsk 2011
Field NOISE_FIGURE NOISE_RISE_ICIC_UL NOISE_RISE_UL NUM_SECTORS PBCH_POWER_OFFSET PCI_DOMAIN_NAME PDCCH_POWER_OFFSET PDSCH_POWER_OFFSET PHY_CELLID_LIST POWER PROPAG_MODEL PROPAG_MODEL2 REDT RS_EPRE RSRQ_THRES RX_ANTENNAS_PORTS RX_EQUIPMENT RXLOSSES SA_NAME SCH_POWER_OFFSET SCHEDULER SF_CONFIG SHAREDMAST TILT TMA_NAME TX_ANTENNAS_PORTS TX_TYPE
Type Float Float Float Integer Float Text (50) Float Float Text(255) Float Text (255) Text (255) Float Float Float Short Text (50) Float Text (50) Float Text (30) Short Text (50) Float Text (50) Short Short
Description Total Noise figure used to determine the thermal noise at the transmitter (Temp) Noise rise received by cell edge traffic Uplink interference noise rise (dB) Number of sectors EPRE offset for PBCH with respect to RS EPRE Name of the physical cell ID domain EPRE offset for PDCCH with respect to RS EPRE EPRE offset for PDSCH with respect to RS EPRE Physical cell IDs used by transmitters Maximum cell output power (dBm) Name of the propagation model used to calculate prediction Name of the second propagation model used to calculate prediction Remote Electrical tilt Energy per resource Element of reference signals Required RSRP for coverage Number of reception antenna ports Reception equipment Losses on the uplink due to transmitter radio equipment Unit: dB Name of the smart antenna equipment EPRE offset for SS with respect to RS EPRE Scheduler used by the cell Subframe configuration used by the cell in case of TDD frequency band Shared mast name: enables antenna sharing between transmitters Mechanical downtilt of the main antenna Name of theTower Mounted Amplifier equipment Number of transmission antenna ports Type of transmitter (0 = Normal; 1 = Interferer only)
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
320
AT310_AM_E2
Field TXLOSSES
Type Float
Description Losses on the downlink due to transmitter radio equipment Unit: dB Target PUSCH C/(I+N) provides Po_pusch and is driven by noise rise limitations of neighbouring cells. This field will be output from simulation. Factor enabling reduction of transmission powers of cell-edge users 0;0.4;0.5;0.6;0.7;0.8;0.9;1 Maximum uplink noise rise Uplink traffic load Multi-user (collaborative) MIMO gain in uplink Inter-network uplink noise rise
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
UL_FPC_CINR_MAX
Float
321
Forsk 2011
Field MISCDLL MISCULL NOISE_FIGURE POLARIZATION PROPAG_MODEL PROPAG_MODEL2 REDT RX_ANTENNAS_PORTS RXLOSSES SA_NAME SHAREDMAST SITE_NAME TILT TMA_NAME TX_ANTENNAS_PORTS TX_ID TX_TYPE TXLOSSES
Type Float Float Float Text (1) Text (50) Text (50) Float Short Float Text (50) Text (50) Text (50) Float Text (50) Short Text (50) Short Float
Description Miscellaneous downlink loss Miscellaneous uplink loss Total Noise figure used to determine the thermal noise at the transmitter Polarization of the antennas installed at the transmitter Name of the propagation model used to calculate prediction Name of the second propagation model used to calculate prediction Remote electrical tilt of the main antenna Number of antenna ports in reception Losses on the uplink due to transmitter radio equipment Name of the smart antenna equipment Shared mast name: enables antenna sharing between transmitters Name of the site at which the transmitter is located (from the Sites table) Mechanical downtilt of the first antenna Name of theTower Mounted Amplifier equipment Number of antenna ports in transmission Transmitter name Type of transmitter (0 = Normal; 1 = Interferer only) Losses on the downlink due to transmitter radio equipment
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: "V" Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
322
AT310_AM_E2
323
Forsk 2011
324
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure
325
Atoll 3.1.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure
Forsk 2011
326
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure
Field PUCCH_AVG_NRB RS_EPRE_DEFINITION RSCP_COMPRESSED_THRESH OLD SHARED_RESULTS_FOLDER SP_PERIODICITY SPREADING_WIDTH SSF_CONFIG SYSTEM_ TECHNOLOGY THERMAL_NOISE
Type Float Short Float Text (255) Short Float Short Text (50) Text (10) Float
Description Average number of overhead resource blocks for PUCCH RS EPRE Definition Method 0 - Calculated from Max Power, 1 - User Defined RSCP threshold for compressed mode activation Shared results storage folder Switching point periodicity (TDD) Choice list: 0=Half Frame; 1=Frame; Spreading width (MHz) TDD: Special subframe configuration (0; 1; 2; 3; 4; 5; 6; 7; 8;) Name of the system Name of the technlogy Thermal noise
Attributes Null column allowed: No Default value: 2 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: -100 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 3.84 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: -121
The networks table contains one record for each technology in the document. In each record, only parameters relevant for the rows technology are used. receivers Table The final structure is the same as the GSM Receivers table (see "Receivers Table" on page 249). sites Table The final structure is the same as the UMTS Sites table (see "Sites Table" on page 283). units Table The final structure is the same as the GSM Units table (see "Units Table" on page 261).
327
Atoll 3.1.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure
Forsk 2011
3GPP Multi-RAT Table ghsndomains ghsngroups glayers gneighbours gneighconstraints gneighext gneighextconstraints gqualityindicators grepeaters gsecondaryantennas gseparationrules gseparations gservicequality gtpltransmitters gtransmitters gtrgconfigs gtrgs gtrxequipments gtrxs gtrxtypes gtsconfignames gtsconfigs gtxslists gtxslistsnames UMTS Technology Tables 3GPP Multi-RAT Table ucells uceuse uequipments ufrequencybands uhsdpabearers uhsdpabearerselect uhsdpaqualtables uhspamimoconfigs uhsupabearers uhsupabearerselect uhsupaqualtables uhsuparessuse uhsupauecategories uinterfreducfactors uneighbours uneighconstraints uneighext uneighextconstraints upscdomains upscforbidpairs upscgroups
Equivalent GSM Table HSNDomains Table HSNGroups Table Layers Table Neighbours Table NeighboursConstraints Table NeighboursExt Table NeighboursConstraintsExt Table QualityIndicators Table Repeaters Table SecondaryAntennas Table SeparationRules Table Separations Table EGPRSServiceQuality Table TplTransmitters Table Transmitters Table TRGConfigurations Table TRGs Table TRXEquipments Table TRXs Table TRXTypes Table TSConfigurationNames Table TSConfigurations Table TxsLists Table TxsListsNames Table
Equivalent UMTS Table CDMACells Table CDMAEquipmentsCEsUse Table CDMAEquipments Table FrequencyBands Table HSDPABearers Table HSDPABearerSelectTables Table HSDPAQualityTables Table HSPAMIMOConfigs Table HSUPABearers Table HSUPABearerSelection Table HSUPAQualityTables Table CdmaEqptsHSUPARssUse Table HSUPAUECategories Table InterfReductionFactors Table Neighbours Table NeighboursConstraints Table NeighboursExt Table NeighboursConstraintsExt Table ScramblingCodesDomains Table Separations Table ScramblingCodesGroups Table
328
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure
3GPP Multi-RAT Table uqualityindicators ur99bearers urepeaters usecondaryantennas uservicequaltables uservicesquality utpltransmitters utransmitters utxslists utxslistsnames uuecategories uuerxequipments LTE Technology Tables 3GPP Multi-RAT Table lbearerqualitycurves lbearers lbearersrequiredci lcells lequipments lframeconfigs lfrequencybands lmimoconfigs lmugtables lneighbours lneighconstraints lneighext lneighextconstraints lpcidomains lpcigroups lqualityindicators lrepeaters lschedulers lsecondaryantennas lsmartantennas ltpltransmitters ltransmitters ltxslists ltxslistsnames luecategories
Equivalent UMTS Table QualityIndicators Table R99Bearers Table Repeaters Table SecondaryAntennas Table ServiceQualityTables Table UMTSServicesQuality Table TplTransmitters Table Transmitters Table TxsLists Table TxsListsNames Table UECategories Table UERxEquipments Table
Equivalent LTE Table T4GBearerQualityCurves Table T4GBearers Table T4GBearersRequiredCI Table T4GCells Table T4GEquipments Table lframeconfigs Table FrequencyBands Table T4GMimoConfigs Table MUGTables Table Neighbours Table NeighboursConstraints Table NeighboursExt Table NeighboursConstraintsExt Table lpcidomains Table lpcigroups Table QualityIndicators Table Repeaters Table Schedulers Table SecondaryAntennas Table SmartAntennas Table TplTransmitters Table Transmitters Table TxsLists Table TxsListsNames Table T4GUECategories Table
329
Atoll 3.1.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure
Forsk 2011
3GPP Multi-RAT Table glneighconstraints ugneighbours ugneighconstraints ulneighbours ulneighconstraints lgneighbours lgneighconstraints luneighbours luneighconstraints Structure of the neighbour relations tables: Field IMPORTANCE NEIGHBOUR Type Float Text (50) Description Handover importance Second part of the unique key. List of neighbours
Descritpion Constraints on LTE neighbours of GSM transmitters GSM neighbours of UMTS cells Constraints on GSM neighbours of UMTS cells LTE neighbours of UMTS cells Constraints on LTE neighbours of UMTS cells GSM neighbours of LTE cells Constraints on GSM neighbours of LTE cells UMTS neighbours of LTE cells Constraints on UMTS neighbours of LTE cells
Attributes Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 (Manual) Null column allowed: No Default value: Null column allowed: Yes Default value:
REASON
Integer
Reason of the neighbourhood Choice list: 0=Manual; 1=Forced; 2=Co-site; 3=Adjacent; 4=Symmetric; 5=Distance; 6=Coverage; First part of the unique key. Transmitters or cells Type of the neighbourhood (handover, measurement)
TRANSMITTER TYPE
Structure of the neighbour constraints tables: Field IMPORTANCE NEIGHBOUR STATUS Type Float Text (50) Integer Description Handover importance Second part of the unique key. List of neighbours Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. Choice list: 0=Forced; 1=Forbidden; First part of the unique key. Transmitters or cells. Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value:
TRANSMITTER
Text (50)
330
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure
Figure 16.13GPP Services Model Common multi-RAT service parameters are stored in the following table: Field DL_ACTIVITY NAME REQ_AVERAGE_DL_RATE REQ_AVERAGE_UL_RATE TECHNO_PRIORITY UL_ACTIVITY services Table Type Float Text (50) Float Float Text (50) Float Description Activity factor for voice services on the downlink Service Name Requested Average Downlink Rate (kbps) Requested Average Uplink Rate (kbps) List of supported technologies in the order of priority Activity factor for voice services on the uplink Attributes Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1
Per-technology service parameters are stored in the following tables: gservices Table Same structure as the services table in GSM, except the DL_ACTIVITY, REQ_AVERAGE_DL_RATE, REQ_AVERAGE_UL_RATE, and UL_ACTIVITY fields. See "EGPRSServices Table" on page 242. uservices Table Same structure as the services table in UMTS, except the DL_ACTIVITY, REQ_AVERAGE_DL_RATE, REQ_AVERAGE_UL_RATE, and UL_ACTIVITY fields. See "UMTSServices Table" on page 290. lservices Table Same structure as the services table in LTE, except the DL_ACTIVITY, REQ_AVERAGE_DL_RATE, REQ_AVERAGE_UL_RATE, and UL_ACTIVITY fields. See "T4GServices Table" on page 315.
331
Atoll 3.1.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure
Forsk 2011
Terminal Tables
Figure 16.23GPP Terminals Model Common multi-RAT service parameters are stored in the following table: Field NAME terminals Table Type Text (50) Description Name of terminal Attributes Null column allowed: No Default value:
Per-technology service parameters are stored in the following tables: gterminals Table Same structure as the terminals table in GSM. See "EGPRSTerminals Table" on page 243. uterminals Table Same structure as the terminals table in UMTS. See "UMTSTerminals Table" on page 292. lterminals Table Same structure as the terminals table in LTE. See "T4GTerminals Table" on page 317. Mobility Tables
Figure 16.33GPP Services Model Common multi-RAT service parameters are stored in the following table: Field NAME MEAN_SPEED mobility Table Type Text (50) Float Description Name of mobility type Average speed (km/h) Attributes Null column allowed: No Default value: Null column allowed: No Default value:
Per-technology service parameters are stored in the following table: umobility Table
332
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure
Same structure as the mobilities table in UMTS, except the MEAN_SPEED field. See "UMTSMobility Table" on page 290. servicesusage Table Same structure as services usage tables in all three technologies. See, for example, "EGPRSServicesUsage Table" on page 243. environmentdefs Table Same structure as environment definition tables in all three technologies. See, for example, "EGPRSEnvironmentDefs Table" on page 241. trafficenvs Table Same structure as traffic environment tables in all three technologies. See, for example, "EGPRSTrafficEnvironments Table" on page 244. userprofiles Table Same structure as user profiles tables in all three technologies. See, for example, "EGPRSUserProfiles Table" on page 244.
333
Atoll 3.1.0 Administrator Manual Chapter 16: 3GPP Multi-RAT Data Structure
Forsk 2011
334
AT310_AM_E2
335
Forsk 2011
336
AT310_AM_E2
337
Forsk 2011
CdmaCells Table Field LOCKED_PNO Type Boolean Description Field used to freeze allocated PNO of the cell during automatic allocation Attributes Null column allowed: No Default value: False
CustomFields Table Field CHOICE_TYPE Type Integer Description 0=Choice list is optional; 1=Choice list is mandatory Attributes Null column allowed: Yes Default value: 0
DLBearersSelection Table Field MODULATION Type Short Description 0=QPSK; 1=8PSK; 2=16QAM; 3=64QAM Attributes Null column allowed: No Default value: 0
TplTransmitters Table Field COMMENT_ MC_MODE_MUG MC_MODE_UL_ECNT_MIN MULTI_CARRIER SHAREDMAST Type Text (255) Memo Float Short Text (50) Description Comments Multi-user gain graph used in multi-carrier mode Required Ec/Nt for multi-carrier mode in the uplink 0=None; 1=Multi-Carrier Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
Transmitters Table Field MC_MODE_MUG MC_MODE_UL_ECNT_MIN MULTI_CARRIER SHAREDMAST Type Memo Float Short Text (50) Description Multi-user gain graph used in multi-carrier mode Required Ec/Nt for multi-carrier mode in the uplink 0=None; 1=Multi-Carrier Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value:
338
AT310_AM_E2
ULBearersSelection Table Field MODULATION Type Short Description 0=QPSK; 1=8PSK; 2=16QAM; 3=64QAM Attributes Null column allowed: No Default value: 0
UMTSServices Table Field MIN_RATE_DL MIN_RATE_UL Type Float Float Description Downlink guaranteed bit rate (kbps) Uplink guaranteed bit rate (kbps) Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
UMTSTerminals Table Field HANDOFF_TYPE MODULATION NUM_CARRIERS_MAX Type Short Short Short Description 0=Locked HO; 1=Unlocked HO 0=QPSK; 1=8PSK; 2=16QAM; 3=64QAM Maximum number of carriers supported in multi-carrier mode Attributes Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 3
339
Forsk 2011
The format of the binary field, DIAGRAM, is described in "RF 2D Antenna Pattern Format" on page 105.
340
AT310_AM_E2
Maximum downlink load allowed (percentage of max power used). Used Null column allowed: Yes in power control simulation Default value: 50 Maximum number of EV-DO users Maximum number of inter-technology neighbours for the cell Maximum number of inter-carrier neighbours for this cell Maximum number of neighbours for the cell Maximum uplink load allowed (percentage). Used in power control simulation Set of values used to generate the graph MUG=f(number of users) Power of other common channels except SCH Power of the pilot channel PN Offset domain name. PN Offset. Amount of power which can be borrowed in the BTS power pool (dB) Maximum power supported by the transmitter Null column allowed: No Default value: 256 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 75 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 30 Null column allowed: Yes Default value: 33 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 1 Null column allowed: Yes Default value: 43
341
Forsk 2011
Field REUSE_DIST ROT_RANGE ROT_TARGET SYNCHRO_POWER TADD TDROP TOTAL_POWER TX_ID UL_LOAD UPLINK_EXTERNAL_NOISE_R ISE
Type Float Float Float Float Float Float Float Text (50) Float Float
Description Minimum reuse distance for PN Offsets Delta of acceptable noise rise (dB) Receiver Noise Rise Over Thermal target (dB) Power of the synchronisation (SCH) channel Minimum Ec/Io for best server selection Ec/Io threshold for active set rejection Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm Name of the transmitter Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm Inter-network uplink noise rise
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 4 Null column allowed: Yes Default value: 23 Null column allowed: Yes Default value: -14 Null column allowed: Yes Default value: -17 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0
342
AT310_AM_E2
Description Number of channel elements used for uplink First part of the unique key. Name of equipment Second part of the unique key. Terminal name.
Attributes Null column allowed: No Default value: 1 Null column allowed: No Default value: Null column allowed: No Default value:
PROJ_METHOD
Short
343
Forsk 2011
Description
Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.
344
AT310_AM_E2
Description EV-DO bearer index RLC bearer rate Transport block size (Bits)
Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
345
Forsk 2011
Description Feeder connector losses in uplink Feeder loss per meter Name of Feeder
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value:
346
AT310_AM_E2
Description Force Handover type to hard handover in case of intra-carriers neighbours Handover importance (for AFP use) Second part of the unique key. List of neighbours Reason of the neighbourhood Choice list: 0=Manual; 1=Forced; 2=Co-site; 3=Adjacent; 4=Symmetric; 5=Distance; 6=Coverage; First part of the unique key. Transmitters or cells Type of the neighbourhood (handover, measurement)
Attributes Null column allowed: No Default value: False Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 (Manual) Null column allowed: No Default value: Null column allowed: Yes Default value:
TRANSMITTER TYPE
Text (50) Second part of the unique key. List of neighbours from another project. Integer Text (50) Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. Choice list: 0=Forced; 1=Forbidden; First part of the unique key. Transmitters or cells
Text (50) Second part of the unique key. List of neighbours from another project
347
Forsk 2011
Description Reason of the neighbourhood Choice list: 0=Manual; 1=Forced; 2=Co-site; 3=Adjacent; 4=Symmetric; 5=Distance; 6=Coverage; First part of the unique key. Transmitters or cells Type of the neighbourhood (handover, measurement)
Attributes Null column allowed: Yes Default value: 0 (Manual) Null column allowed: No Default value: Null column allowed: Yes Default value:
348
AT310_AM_E2
Field DOMAIN_NAME
LAST
Integer
NAME STEP
NAME PS_QI
349
Forsk 2011
Field USE_INTERPOLATION
Type Boolean
350
AT310_AM_E2
Field DONOR_CELLID DONOR_LINK_LOSS DONOR_LINK_TYPE DONOR_PROPAG_MODEL DOWNTILT EQUIPMENT_NAME FEEDER_NAME FEEDERLENGTH HEIGHT REC_ANTENNA REC_FEEDERLENGTH_UL TOTAL_GAIN TOTAL_GAIN_UL TX_ID
Type Text (50) Float Short Text (50) Float Text (50) Text (50) Float Float Text (50) Float Float Float Text (50)
Description Name of the donor cell Loss (dB) between donor and donor side of the repeater 1- Off air 2- Microwave 3- Fibre Name of the propagation model used to calculate prediction between donor and repeater Downtilt of the donor side antenna If no equipment, the repeater is a passive component Name of the donor side feeder Length of donor side feeder Height of the donor side antenna Name of the donor side antenna Length of donor side uplink feeder Total gain to be applied to donor cell pilot power Uplink total gain to be applied to mobile output power Name of the transmitter (and of the transmitter used for coverage)
Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value:
Repeater properties are saved in two tables: the donor-side parameters are in the Repeaters table and the coverage-side parameters in the Transmitters table.
351
Forsk 2011
Description First part of the unique key. First cell name in a symmetric relation Second part of the unique key. Second cell name in a symmetric relation
Attributes Null column allowed: No Default value: Null column allowed: No Default value:
352
AT310_AM_E2
Description First part of the unique key. Name of the list Second part of the unique key. Name of the site
Attributes Null column allowed: No Default value: Null column allowed: No Default value:
353
Forsk 2011
Field CARRIERS CCH_TS_PCT CDMA_EQUIPMENT CELL_SIZE CHANNEL_ELEMENTS_DL CHANNEL_ELEMENTS_UL COMMENT_ DOWNLINK_EXTERNAL_NOIS E_RISE DRC_ER_RATE EVDO_CES FBAND FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL HEIGHT IDLE_POWER_GAIN MAX_DL_LOAD MAX_EVDO_USERS MAX_EXT_NEIGHB_NUMBER MAX_INTERCAR_NEIGHB_NB MAX_NEIGHB_NUMBER MAX_UL_LOAD MC_MODE_MUG MC_MODE_UL_ECNT_MIN MISCDLL MISCULL MUG_TABLE
Type Text (50) Float Text (50) Float Integer Integer Text (255) Float Float Integer Text (50) Text (50) Float Float Float Float Float Integer Short Integer Short Float Memo Float Float Float Memo
Description Carriers used by the transmitter % of time slots dedicated to Common Control Channels CDMA equipment Hexagon radius Unit: m Number of channel elements for downlink Number of channel elements for uplink Comments Inter-network downlink noise rise DRC Erasure Rate (ie % of time DRC values are in error) Number of EVDO channel elements per carrier Frequency band Name of the feeder equipment Length of downlink feeder Unit: m Length of uplink feeder Unit: m Antenna height above the ground Unit: m Gain dedicated to transmitted power in idle state
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
Maximum downlink load allowed (percentage of max power used). Used Null column allowed: Yes in power control simulation Default value: Maximum number of EV-DO users Maximum number of inter-technology neighbours for the cell or the transmitter Maximum number of inter-carrier neighbours for this cell Maximum number of neighbours for the cell or the transmitter Maximum uplink load allowed (percentage). Used in power control simulation Multi-user gain graph used in multi-carrier mode Required Ec/Nt for multi-carrier mode in the uplink Miscellaneous downlink losses Miscellaneous uplink losses Set of values used to generate the graph MUG=f(num users) Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
354
AT310_AM_E2
Field MULTI_CARRIER NAME NOISE_FIGURE NUM_SECTORS PAGING_POWER PILOT_POWER PN_DOMAIN_NAME POOLED_PWR POWER_MAX PROPAG_MODEL PROPAG_MODEL2 REDT REUSE_DIST ROT_RANGE ROT_TARGET RXLOSSES SHAREDMAST SYNCHRO_POWER TADD TDROP TILT TMA_NAME TOTAL_POWER TXLOSSES UL_LOAD UPLINK_EXTERNAL_NOISE_R ISE
Type Short Text (50) Float Integer Float Float Text (50) Float Float Text (255) Text (255) Float Float Float Float Float Text (50) Float Float Float Float Text (50) Float Float Float Float
Description 0=None; 1=Multi-Carrier Template name Noise figure used to determine the thermal noise at the transmitter Number of sectors Power of the paging channel Power of the pilot channel PN Offset code domain name Amount of power which can be borrowed in the BTS power pool (dB) Maximum power supported by the transmitter Name of the propagation model used to calculate predictions Name of the propagation model used to calculate extended prediction Remote Electrical tilt Minimum reuse distance for PN offsets Delta of acceptable noise rise (dB) Receiver Noise Rise Over Thermal target (dB) Losses in the uplink due to transmitter radio equipment Unit: dB Shared mast name: enables antenna sharing between transmitters Power of the synchronisation (SCH) channel Minimum Ec/Io for best server selection Ec/Io threshold for active set rejection Mechanical downtilt of the main antenna Name of the Tower Mounted Amplifier equipment Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm Losses in the downlink due to transmitter radio equipment Unit: dB Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm Inter-network uplink noise rise
Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 3 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
355
Forsk 2011
356
AT310_AM_E2
Field PROPAG_MODEL PROPAG_MODEL2 REDT RXLOSSES SHAREDMAST SITE_NAME TILT TMA_NAME TX_ID TXLOSSES
Type Text (255) Text (255) Float Float Text (50) Text (50) Float Text (50) Text (50) Float
Description Name of the propagation model used to calculate prediction Name of the propagation model used to calculate extended prediction Remote Electrical tilt Losses in the uplink due to transmitter radio equipment Shared mast name: enables antenna sharing between transmitters Name of the site on which the transmitter is located (from the Sites table) Mechanical downtilt of the first antenna Name of the TMA equipment Transmitter name Losses in the downlink due to transmitter radio equipment
Attributes Null column allowed: Yes Default value: Default model Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0
357
Forsk 2011
Type Memo Float Float Text (50) Short Integer Text (50)
Description Tables of Probabilities of Earlier Termination=f(REPEAT_NUM) Required Pilot Ec/Nt for High Capacity services Required Pilot Ec/Nt for Low Latency services UE mobility 0=QPSK; 1=8PSK; 2=16QAM; 3=64QAM Number of retransmissions to ensure a correct transmission Type of receiver of the User Equipment
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: "Standard"
COVERI_THROUGHPUTS
Memo
Delta (dB) to be added to the T_ADD defined in cells structure Delta (dB) to be added to the T_DROP defined in cells structure Type of mobility Minimum uplink Ec/Nt (EV-DO)
358
AT310_AM_E2
Field CARRIER DLFCH_ACTIVITYFACTOR DLRATE_16 DLRATE_2 DLRATE_4 DLRATE_8 DOWN_153K6_76K8 DOWN_19K2_9K6 DOWN_38K4_19K2 DOWN_76K8_38K4 ENABLE_DOWNGRADING EVDO_ULRATE_1 MIN_RATE_DL MIN_RATE_UL NAME PRIORITY QOS_CLASS
Type Integer Float Float Float Float Float Float Float Float Float Boolean Float Float Float Text (50) Integer Short
Description Carrier supporting the service. -1 means that all carriers can be used. Occupancy time of the fundamental channel on the downlink Probability to transmit sixteen times the nominal rate on the supplementary channel (SCH) on the downlink Probability to transmit twice the nominal rate on the supplementary channel (SCH) on the downlink Probability to transmit four times the nominal rate on the supplementary channel (SCH) on the downlink Probability to transmit eight times the nominal rate on the supplementary channel (SCH) on the downlink EV-DO Rev.0 Downgrading probability (153.6 -> 76.8) (Unit 1/255) EV-DO Rev.0 Downgrading probability (19.2 -> 9.6) (Unit 1/255) EV-DO Rev.0 Downgrading probability (38.4 -> 19.2) (Unit 1/255) EV-DO Rev.0 Downgrading probability (76.8 -> 38.4) (Unit 1/255) True if downgrading is enabled for the service Probability to transmit at 9.6 kbps for an EVDO service Downlink guaranteed bit rate (kbps) Uplink guaranteed bit rate (kbps) Service name Priority level of the service: parameter used in the WCDMA simulation 0="Best Effort" 1="Guaranteed Bit Rate" Table of Reverse Link throughputs=f(Forward Link application layer throughput)
Attributes Null column allowed: No Default value: -1 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: True Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: '0 0 300 10 600 20 900 30 1200 40 1500 50 1800 60 2400 80' Null column allowed: No Default value: False Null column allowed: No Default value: 0 Null column allowed: No Default value: 95 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
TCP_ACK_CURVE
Memo
True if the user application is using TCP Offset to add to the above ratio Ratio between application throughput and RLC layer throughput '0'=Speech,1=Data 1xRTT 2=EVDO 0="High Capacity" 1="Low Latency"
Either occupancy time of the fundamental channel on the uplink for Null column allowed: Yes 1xRTT, or probability to transmit the nominal rate on the supplementary Default value: 1 channel (SCH) on the uplink in case of 1xEVDO. Probability to transmit sixteen times the nominal rate on the supplementary channel (SCH) on the uplink Probability to transmit twice the nominal rate on the supplementary channel (SCH) on the uplink Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
ULRATE_16 ULRATE_2
Float Float
359
Forsk 2011
Description Probability to transmit four times the nominal rate on the supplementary channel (SCH) on the uplink Probability to transmit height times the nominal rate on the supplementary channel (SCH) on the uplink EV-DO Rev.0 Upgrading probability (19.2 -> 38.4) (Unit 1/255) EV-DO Rev.0 Upgrading probability (38.4 -> 76.8) (Unit 1/255) EV-DO Rev.0 Upgrading probability (76.8 -> 153.6) (Unit 1/255) EV-DO Rev.0 Upgrading probability (9.6 -> 19.2) (Unit 1/255) 'Yes' if the service supports soft handoff
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: False
FCH power to Pilot power gain. Used if global flag UL_PWC_ON_PILOT is Null column allowed: Yes set to True Default value: 0 UE mobility Maximum transmitter power on fundamental traffic channel for the service Minimum transmitter power on fundamental traffic channel for the service Type of receiver SCH Rate factor (0 -> 16) Null column allowed: Yes Default value: Null column allowed: Yes Default value: 34 Null column allowed: Yes Default value: 14 Null column allowed: No Default value: Standard Null column allowed: No Default value: 0
SCH power to Pilot power gain. Used if global flag UL_PWC_ON_PILOT is Null column allowed: Yes set to True Default value: 0 First part of the unique key. Name of the service Second part of the unique key. Type of terminal Pilots Ec/Nt target. Used if global flag UL_PWC_ON_PILOT is set to True Eb/Nt target on the uplink for each type of (mobility, SCH rate) pair Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value:
360
AT310_AM_E2
Description Service that the subscriber may request Type of terminal used by the subscriber for the service User profile name
Attributes Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value:
Maximum number of transmitters possibly connected with the receiver Null column allowed: Yes for the fundamental channel (FCH) Default value: 6 DRC gain (No handoff case) DRC gain (No handoff case) for 1xEvDo Rev A DRC gain (any kind of soft handoff) DRC gain (any kind of soft handoff) for 1xEvDo Rev A DRC gain (only softer handoff) DRC gain (only softer handoff) for 1xEvDo Rev A Downlink nominal rate supported by the receiver on the fundamental channel Receiver antenna gain 0=Locked HO; 1=Unlocked HO Receiver antenna loss 0=QPSK; 1=8PSK; 2=16QAM; 3=64QAM Terminal name Noise figure used to determine the thermal noise at the receiver Noise figure used to determine the thermal noise at the receiver (for secondary frequency band) Maximum number of carriers supported in multi-carrier mode Percentage of maximum power dedicated to the UL pilot channel Maximum receiver power on traffic channel Minimum receiver power on traffic channels Null column allowed: Yes Default value: -1 Null column allowed: No Default value: -1 Null column allowed: Yes Default value: -3 Null column allowed: No Default value: -3 Null column allowed: Yes Default value: -1 Null column allowed: No Default value: -1 Null column allowed: No Default value: 9.6 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 8 Null column allowed: Yes Default value: 8 Null column allowed: Yes Default value: 3 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 23 Null column allowed: Yes Default value: -50
361
Forsk 2011
Field PRIMARY_BAND RAKE_EFFICIENCY RAKE_NUM_FINGERS REV_BASEDATARATE RHO_FACTOR RRI_GAIN_DORA RX_EQUIP SCH_AS_SIZE SECONDARY_BAND SUPPORTED_TECHNO TRAFFIC_GAIN_153_6 TRAFFIC_GAIN_19_2 TRAFFIC_GAIN_38_4 TRAFFIC_GAIN_76_8 TRAFFIC_GAIN_9_6
Type Text (50) Float Short Float Short Float Text (50) Short Text (50) Short Float Float Float Float Float
Description Primary frequency band Efficiency of the rake receiver. Used for combination of Active Set member contributions Number of links of the active set that will be combined Uplink nominal rate supported by the receiver on the fundamental channel Rho factor to model self generated interference RRI gain for 1xEvDo Rev A Type of the User Equipment Receiver
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 3 Null column allowed: No Default value: 9.6 Null column allowed: No Default value: 94 Null column allowed: No Default value: -6 Null column allowed: No Default value: Standard
Maximum number of transmitters possibly connected with the receiver Null column allowed: Yes for the supplementary channel (SCH) Default value: 3 Secondary frequency band 0:Speech, 1:1xRTT_Data, 2:1xEvDo_Rel0, 3:1xEvDo_RelA Traffic gain (153.6 kbps) Traffic gain (19.2 kbps) Traffic gain (38.4 kbps) Traffic gain (76.8 kbps) Traffic gain (9.2 kbps) Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 18 Null column allowed: Yes Default value: 7 Null column allowed: Yes Default value: 10 Null column allowed: Yes Default value: 13 Null column allowed: Yes Default value: 4
362
AT310_AM_E2
Description Display coordinate system when creating database Unit used for gains (dBd or dBi) Choice list: 0=dBd; 1=dBi; Projected coordinate system for geo data Reception unit when creating database Choice list: 0=dBm; 1=dbV; 2=dbV/m; Transmission unit when creating database Choice list: 0=dBm; 1=Watts; 2=kWatts;
Attributes Null column allowed: Yes Default value: -1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: -1 Null column allowed: No Default value: 0 Null column allowed: No Default value: 0
363
Forsk 2011
364
AT310_AM_E2
365
Forsk 2011
366
AT310_AM_E2
367
Forsk 2011
Number of served HSDPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes simulation algorithm Default value: Number of served HSUPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes simulation algorithm Default value:
HSDPABearers Field MODULATION Type Short Description Modulation: 0=QPSK; 1=16QAM; Attributes Null column allowed: No Default value: 0
HSUPABearers (New) Field BEARER_INDEX Type Short Description Index of the bearer Attributes Null column allowed: No Default value:
368
AT310_AM_E2
Description Number of E-PUCH codes used Modulation: 0=QPSK; 1=16QAM; Peak RLC throughput (without BLER) Transport Block Size (bits) Number of time slots used per subframe Associated UE category
Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1
HSUPABearerSelection (New) Field BEARER_INDEX EARLY_TERM_TABLE EPUCH_ECNT_REQ MAX_NUM_REP MOBILITY RX_EQUIP UL_CRT_MARGIN Type Short Memo Float Integer Text (50) Text (50) Float Description Index of the selected bearer Tables of probabilities of earlier termination=f(REPEAT_NUM) Required E-PUCH Ec/Nt Number of retransmissions to ensure a correct transmission Users mobility Reception equipment of the terminal Uplink control margin for E-PUCH Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
HSUPAUECategories (New) Field MAX_BLOCK_SIZE MAX_EPUCH_CODES MAX_EPUCH_TS MODULATION UE_CATEGORY UE_CATEGORY_NAME Type Integer Short Integer Short Short Text (50) Description Maximum transport block size supported for TTI=10ms (bits) Maximum number of E-DPDCH codes for HSUPA Smallest Spreading Factor supported Modulation (0: QPSK; 1: 16QAM) UE category for HSUPA Name of the HSUPA UE category Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value:
TplTransmitters Field COMMENT_ DYN_EDCH_DL_POWER_ALL OC EDCH_DL_POWER Type Text (255) Boolean Float Description Comments Allocation of power for HSUPA DL power (E-AGCH, E-HICH): True=Dynamic; False=Static; Value of power dedicated to E-AGCH and E-HICH channel per timeslot. In case of dynamic allocation, it is the maximum available power. Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value:
369
Forsk 2011
Field HSPA_SUPPORT HSUPA_MAX_USERS MAX_R99BEARER_DL_RATE MAX_R99BEARER_UL_RATE NUM_HSDPA_USERS NUM_HSUPA_USERS SHAREDMAST Transmitters Field SHAREDMAST
Description HSPA features supported: 0=None; 1=HSDPA; 2=HSPA; Max number of HSUPA users managed simultaneously by the scheduler Max bearer rate available in DL (kbps) Max bearer rate available in UL (kbps)
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
Number of served HSDPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes simulation algorithm Default value: Number of served HSUPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes simulation algorithm Default value: Shared mast name: enables antenna sharing between transmitters Null column allowed: Yes Default value:
UECategories Field MODULATION UE_CATEGORY_NAME Type Short Text (50) Description Modulation (0: QPSK; 1: 16QAM) Name of the HSDPA UE category Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value:
UMTSMobility Field EDCH_DL_ECNT UMTSServices Field ADPCH_ACTIVITY CARRIER_LIST CARRIER_SUPPORT EDPCH_ACTIVITY Type Float Text (50) Integer Float Description Activity Factor for HSDPA users List of preferred carrier numbers Carrier support type: 0=Prefered; 1=Allowed; Activity Factor for HSUPA users Attributes Null column allowed: Yes Default value: 0.1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0.1 Type Float Description E-DCH Ec/Nt target for HSUPA DL power (E-AGCH, E-HICH) Attributes Null column allowed: Yes Default value: -12
UMTSTerminals Field HSPA_SUPPORT HSUPA_UE_CATEGORY Type Short Short Description HSPA features supported: 0=None; 1=HSDPA; 2=HSPA HSUPA UE category Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1
370
AT310_AM_E2
TplTransmitters Table CHANNEL_ELEMENTS_DL CHANNEL_ELEMENTS_UL COV_PROBA ENABLE_HSDPA MAX_DL_LOAD MAX_UL_LOAD PWC_LIMIT SCH_POWER TOTAL_POWER UL_LOAD
371
Forsk 2011
The format of the binary field, DIAGRAM, is described in "RF 2D Antenna Pattern Format" on page 105.
372
AT310_AM_E2
Description Downlink losses due to the configuration of the BTS (duplexer and/or combiner) Uplink losses due to the configuration of the BTS (duplexer and/or combiner) Name of Base Station Equipment Noise figure of Base Station Rho factor to model self generated interference (100%=ideal)
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 100
Scheduling algo used for HSDPA users. 0 = MAX C/I, 1 = Round Robin, 2 = Null column allowed: Yes Proportional Fair. Default value: 2
373
Forsk 2011
Field HSPA_SUPPORT HSUPA_MAX_USERS LOCKED_SC MAX_EXT_NEIGHB_NUMBER MAX_NEIGHB_NUMBER MAX_R99BEARER_DL_RATE MAX_R99BEARER_UL_RATE NUM_HS_SCCH NUM_HS_SICH NUM_HSDPA_USERS NUM_HSUPA_USERS OTHERS_CCH_POWER PILOT_POWER POWER_MAX PWR_HEADROOM REQ_DL_RUS REQ_UL_RUS REUSE_DIST RSCP_COMP SC_DOMAIN_NAME SCRAMBLING_CODE
Type Short Integer Boolean Integer Integer Float Float Short Short Integer Integer Float Float Float Float Short Short Float Float Text (50) Integer
Description HSPA features supported: 0=None; 1=HSDPA; 2=HSPA; Max number of HSUPA users managed simultaneously by the scheduler Field used to freeze allocated SC of the cell during automatic allocation Maximum number of inter-technology neighbours for the cell Maximum number of neighbours for the cell Max bearer rate available in DL (kbps) Max bearer rate available in UL (kbps) Number of HS-SCCH channels Number of HS-SICH channels per cell
Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 15 Null column allowed: No Default value: False Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1000 Null column allowed: Yes Default value: 1000 Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: 5
Number of served HSDPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes simulation algorithm Default value: Number of served HSUPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes simulation algorithm Default value: Power on the other common channels for TS0 (S-CCPCH, FPACH, PICH) Power of the pilot channel Maximum power supported by the transmitter Power Control Headroom (dB) for DCH (used in WCDMA simulation algorithm) Required resource units in downlink Required resource units in uplink Minimum reuse distance for scrambling codes P-CCPCH RSCP margin to trigger Baton Handover Scrambling code domain name. Scrambling code. Timeslot configuration (1-DUDDDDD; 2-DUUDDDD; 3-DUUUDDD; 4-DUUUUDD; 5-DUUUUUD; 6-DUUUUUU;) Name of the transmitter Inter-network uplink noise rise Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 33 Null column allowed: Yes Default value: 43 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 3 Null column allowed: No Default value: Null column allowed: Yes Default value: 0
TS_CONFIG
Integer
374
AT310_AM_E2
375
Forsk 2011
Description Number of channel elements used for downlink Number of channel elements used for uplink First part of the unique key. Name of equipment Second part of the unique key. Service name.
Attributes Null column allowed: No Default value: 1 Null column allowed: No Default value: 1 Null column allowed: No Default value: Null column allowed: No Default value:
376
AT310_AM_E2
Description Meters Decimal degrees Decimal degrees Decimal degrees UTM, Undefined, NoProjection, Lambert1SP, Lambert2SP, Mercator, CassiniSoldner, TransMercator, TransMercatorSO, ObliqueStereographic, NewZealandMapGrid, HotineOM, LabordeOM, SwissObliqueCylindical
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
PROJ_METHOD
Short
Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.
377
Forsk 2011
18.17 HSUPABearers
For HSUPA bearers.
378
AT310_AM_E2
Description Index of the bearer Number of E-PUCH codes used Modulation: 0=QPSK; 1=16QAM; Peak RLC throughput (without BLER) Transport Block Size (bits) Number of time slots used per subframe Associated UE category
Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1
18.18 HSUPABearerSelection
For HSUPA bearer selection graphs. Field BEARER_INDEX EARLY_TERM_TABLE EPUCH_ECNT_REQ MAX_NUM_REP MOBILITY RX_EQUIP UL_CRT_MARGIN Type Short Memo Float Integer Text (50) Text (50) Float Description Index of the selected bearer Tables of probabilities of earlier termination=f(REPEAT_NUM) Required E-PUCH Ec/Nt Number of retransmissions to ensure a correct transmission Users mobility Reception equipment of the terminal Uplink control margin for E-PUCH Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
18.19 HSUPAUECategories
For HSUPA UE categories. Field MAX_BLOCK_SIZE MAX_EPUCH_CODES MAX_EPUCH_TS MODULATION UE_CATEGORY UE_CATEGORY_NAME Type Integer Short Integer Short Short Text (50) Description Maximum transport block size supported for TTI=10ms (bits) Maximum number of E-DPDCH codes for HSUPA Smallest Spreading Factor supported Modulation (0: QPSK; 1: 16QAM) UE category for HSUPA Name of the HSUPA UE category Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value:
379
Forsk 2011
380
AT310_AM_E2
Description Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. Choice list: 0=Forced; 1=Forbidden; First part of the unique key. Transmitters or cells.
Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value:
Text (50) Second part of the unique key. List of neighbours from another project. Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. Choice list: 0=Forced; 1=Forbidden; First part of the unique key. Transmitters or cells
STATUS
Integer
TRANSMITTER
Text (50)
Text (50) Second part of the unique key. List of neighbours from another project Reason of the neighbourhood Choice list: 0=Manual; 1=Forced; 2=Co-site; 3=Adjacent; 4=Symmetric; 5=Distance; 6=Coverage; First part of the unique key. Transmitters or cells Type of the neighbourhood (handover, measurement)
REASON
Integer
TRANSMITTER TYPE
381
Forsk 2011
Field GUARD_PERIOD_CHIPS_NU MBER HSDPA_NTISNTOT INTERFERERS_RX_THRESH MIDAMBLE_CHIPS_NUMBER NAME NTISNTOT PILOT_PROCESSING_GAIN POWERS_RELATIVE_TO_PILO T PTS_GUARD_PERIOD_CHIPS_ NUMBER SHARED_RESULTS_FOLDER SPREADING_FACTOR_MAX SPREADING_FACTOR_MIN SPREADING_WIDTH SUBFRAME_TIME SYSTEM_ TECHNOLOGY TS_DATA_CHIPS_NUMBER TS_NUMBER UPPTS_CHIPS_NUMBER
Type Float Boolean Float Float Text (50) Boolean Float Boolean Integer Text (255) Integer Integer Float Short Text (50) Text (10) Float Integer Integer
Description Number of chips in guard period HSDPA only: Nt includes or not pilot's signal for HS-SCCH, HS-PDSCH and CPICH for CQI determination Interferers' reception threshold Number of chips in midamble
Attributes Null column allowed: Yes Default value: 16 Null column allowed: No Default value: False Null column allowed: Yes Default value: -130 Null column allowed: Yes Default value: 144 Null column allowed: No Default value:
Nt includes pilot signal or not P-CCPCH Processing Gain Cell Paging and Synchro powers, Service Allowed DL min and max TCH powers are absolute values (False) or relative to cell pilot power (True) Number of chips in the PTS guard period Shared results storage folder Maximum spreading factor Minimum spreading factor Spreading width (MHz) Duration of a subframe in ms Name of the system Name of the technology Number of data chips in a TS Number of TS in a subframe UpPTS (TS dedicated to the pilot)
Null column allowed: No Default value: False Null column allowed: Yes Default value: 13.8 Null column allowed: No Default value: Null column allowed: Yes Default value: 96 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 16 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1.28 Null column allowed: Yes Default value: 5 Null column allowed: No Default value: TDSCDMA Null column allowed: No Default value: CDMA Null column allowed: Yes Default value: 704 Null column allowed: Yes Default value: 7 Null column allowed: Yes Default value: 160
382
AT310_AM_E2
383
Forsk 2011
Field NAME
384
AT310_AM_E2
Description Height of the donor side antenna Name of the donor side antenna Length of donor side uplink feeder Total gain to be applied to donor cell pilot power Uplink total gain to be applied to mobile output power Name of the transmitter (and of the transmitter used for coverage)
Attributes Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value:
Repeater properties are saved in two tables: the donor-side parameters are in the Repeaters table and the coverage-side parameters in the Transmitters table.
FIRST
LAST
Integer
385
Forsk 2011
Field NAME
Description First part of the unique key. Name of the scrambling code group Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST.
Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: 1
STEP
Integer
386
AT310_AM_E2
Type Short Short Short Short Short Short Text (50) Short
Description Uplink or downlink Choice list: 1=DL; 2=UL; Number of SF1 codes allocated for DL Number of SF16 codes allocated for DL Number of SF2 codes allocated for DL Number of SF4 codes allocated for DL Number of SF8 codes allocated for DL Service name Rank for TS allocation in Monte Carlo simulations
Attributes Null column allowed: No Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: 1
387
Forsk 2011
Field NAME
Modelling Type: 0- Dedicated Model, 1- Ideal Beam Steering, 2- Grid Of Null column allowed: Yes Beams, 3- Statistical Default value: 0 Name of the Smart Antenna Probability of having more than used C/I gain External Model used to model the smart antenna Null column allowed: No Default value: Null column allowed: Yes Default value: 50 Null column allowed: Yes Default value:
388
AT310_AM_E2
Description Downlink losses of Tower Mounted Amplifier Name of Tower Mounted Amplifier Noise figure of Tower Mounted Amplifier Uplink gain of Tower Mounted Amplifier
Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
389
Forsk 2011
Field FBAND FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL HEIGHT HS_SCCH_POWER HSDPA_MAX_CODES HSDPA_MAX_USERS HSDPA_MIN_CODES HSDPA_PWR HSDPA_SCHEDULER_ALGO HSPA_SUPPORT HSUPA_MAX_USERS MAX_EXT_NEIGHB_NUMBER MAX_NEIGHB_NUMBER MAX_R99BEARER_DL_RATE MAX_R99BEARER_UL_RATE MAX_RANGE MIN_RANGE MISCDLL MISCULL N_FREQUENCY NAME NOISE_FIGURE NUM_HS_SCCH NUM_HS_SICH NUM_HSDPA_USERS
Type Text (50) Text (50) Float Float Float Float Short Short Short Float Short Short Integer Short Short Float Float Integer Integer Float Float Boolean Text (50) Float Short Short Integer
Description Frequency band Name of the feeder equipment Length of downlink feeder Unit: m Length of uplink feeder Unit: m Antenna height above the ground Unit: m Value of power dedicated to a HS_SCCH channel. In case of dynamic allocation, it is the maximum available power. Maximum number of HS-PDSCH codes Max number of HSDPA users managed simultaneously by the scheduler Minimum Number of HS-PDSCH codes Amount of power (dBm) dedicated to HSDPA Scheduling algo used for HSDPA users. 0=MAXC/I (MAx C/I), 1=RR (Round Robin), 2=PF (Proportional Fair) HSPA features supported: 0=None; 1=HSDPA; 2=HSPA; Max number of HSUPA users managed simultaneously by the scheduler Maximum number of inter-technology neighbours for the cell or the transmitter Maximum number of neighbours for the cell or the transmitter Max bearer rate available in DL (kbps) Max bearer rate available in UL (kbps) Maximum range (m) of coverage (for extended cells) Minimum range (m) of coverage (for extended cells) Miscellaneous downlink losses Miscellaneous uplink losses N-frequency mode. 'Yes' means that the transmitter has one master carrier and slaves carriers; otherwise all its carriers are standalone Template name Noise figure used to determine the thermal noise at the transmitter Number of HS_SCCH channels Number of HS-SICH channels per cell
Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
Number of served HSDPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes simulation algorithm Default value:
390
AT310_AM_E2
Field NUM_HSUPA_USERS NUM_RX_ANTENNAS NUM_SECTORS NUM_TX_ANTENNAS OTHERS_CCH_POWER PILOT_POWER POWER_MAX PROPAG_MODEL PROPAG_MODEL2 PWR_HEADROOM REDT REQ_DL_RUS REQ_UL_RUS REUSE_DIST RXLOSSES SA_NAME SC_DOMAIN_NAME SHAREDMAST TILT TMA_NAME TS_CONFIG TX_DIVERSITY_CFG TXLOSSES UPLINK_EXTERNAL_NOISE_R ISE
Type Integer Short Integer Short Float Float Float Text (255) Text (255) Float Float Integer Integer Float Float Text (50) Text (50) Text (50) Float Text (50) Float Integer Float Float
Description
Attributes
Number of served HSUPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes simulation algorithm Default value: Number of transmission antenna ports available at the transmitter Number of sectors Number of reception antenna ports available at the transmitter Power of common channels (except SCH) Power of the pilot channel Maximum power supported by the transmitter Name of the propagation model used to calculate predictions Name of the propagation model used to calculate extended prediction Power Control Headroom (dB) for DCH (used in WCDMA simulation algorithm) Remote Electrical tilt Required resource units in downlink Required resource units in uplink Minimum reuse distance for scrambling codes Losses in the uplink due to transmitter radio equipment Unit: dB Null column allowed: Yes Default value: Null column allowed: Yes Default value: 3 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
Name of the associated smart antenna (if empty, the standard antenna Null column allowed: Yes is used) Default value: Scrambling code domain name Shared mast name: enables antenna sharing between transmitters Mechanical downtilt of the main antenna Name of the Tower Mounted Amplifier equipment Timeslot configuration (1-DUDDDDD 2-DUUDDDD 3-DUUUDDD 4DUUUUDD 5-DUUUUUD 6-DUUUUUU) TX diversity configuration 0=No TX diversity; 1=TX div. open loop; 2=TX div. closed loop Losses in the downlink due to transmitter radio equipment Unit: dB Inter-network uplink noise rise Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
391
Forsk 2011
Field ACTIVE ANTDIVGAIN ANTENNA_NAME AZIMUT BTS_NAME CALC_RADIUS CALC_RADIUS2 CALC_RESOLUTION CALC_RESOLUTION2 CELL_SIZE COMMENT_ DX DY FBAND FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL HEIGHT HEXAGON_GROUP MAX_RANGE MIN_RANGE MISCDLL MISCULL N_FREQUENCY NOISE_FIGURE NUM_RX_ANTENNAS NUM_TX_ANTENNAS
Type Boolean Float Text (50) Float Text (50) Integer Integer Integer Integer Float Text (255) Float Float Text (50) Text (50) Float Float Float Text (50) Integer Integer Float Float Boolean Float Short Short
Description Transmitter activity: 'Yes' means that the transmitter is active Antenna diversity gain Name of the main antenna installed on the transmitter Azimuth of the main antenna Name of the BTS equipment Calculation radius used to define the calculation area Unit: m Extended calculation radius Calculation resolution Extended calculation resolution Hexagon radius Unit: m Additional information about the transmitter X coordinate relative to the site location Y coordinate relative to the site location Frequency band Name of the feeder equipment Length of feeder in DL Length of feeder in UL Antenna height above the ground Unit: m Group of hexagons used to create this transmitter Maximum range (m) of coverage (for extended cells) Minimum range (m) of coverage (for extended cells) Miscellaneous DL loss Miscellaneous UL loss N-frequency mode. 'Yes' means that the transmitter has one master carrier and slaves carriers; otherwise all its carriers are standalone Noise figure used to determine the thermal noise at the transmitter Number of transmission antenna ports available at the transmitter Number of reception antenna ports available at the transmitter
Attributes Null column allowed: No Default value: True Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 4000 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 50 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 2000 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 35000 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: False Null column allowed: Yes Default value: 5 Null column allowed: No Default value: 1 Null column allowed: No Default value: 1
392
AT310_AM_E2
Field PROPAG_MODEL PROPAG_MODEL2 REDT RXLOSSES SA_NAME SHAREDMAST SITE_NAME TILT TMA_NAME TX_DIVERSITY_CFG TX_ID TXLOSSES
Type Text (255) Text (255) Float Float Text (50) Text (50) Text (50) Float Text (50) Short Text (50) Float
Description Name of the propagation model used to calculate prediction Name of the propagation model used to calculate extended prediction Remote Electrical tilt Losses in the uplink due to transmitter radio equipment
Attributes Null column allowed: Yes Default value: Default model Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
Name of the associated smart antenna (if empty, the standard antenna Null column allowed: Yes is used) Default value: Shared mast name: enables antenna sharing between transmitters Name of the site on which the transmitter is located (from the Sites table) Mechanical downtilt of the first antenna Name of the TMA equipment TX diversity configuration. 1 = No TX diversity 2 = TX div. open loop 3 = TX div. closed loop Transmitter name Losses in the downlink due to transmitter radio equipment Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0
393
Forsk 2011
Description Modulation (0: QPSK; 1: 16QAM) UE category for HSDPA Name of the HSDPA UE category
Attributes Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value:
394
AT310_AM_E2
Field UPPCH_RSCP
Type Float
395
Forsk 2011
Description Activity factor for circuit switched service on the uplink Packet inter arrival time (ms) on the uplink Reading time (distance) between two packet calls (ms) on the uplink Number of packet calls during a session on the uplink Packet efficiency factor on the uplink Packet size (Bytes) on the uplink Uplink max Packet call size (kBytes) Uplink min Packet call size (kBytes)
Attributes Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1500 Null column allowed: Yes Default value: 2000 Null column allowed: Yes Default value: 4
396
AT310_AM_E2
Description Data volume transferred on the downlink during a session (for packet switched services) Unit: Kbyte Service that the subscriber may request Type of terminal used by the subscriber for the service Data volume transferred on the uplink during a session (for packet switched services) Unit: Kbyte User profile name
Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: No Default value:
UL_VOLUME
Float
USER_PROFILE
Text (50)
Advanced Receiver Factor to model intra-cell interference reduction for Null column allowed: Yes HSDPA terminals only Default value: 0 Terminal name Noise figure used to determine the thermal noise at the receiver Maximum receiver power on traffic channel Minimum receiver power on traffic channels Rho factor to model self generated interference Type of the User Equipment Receiver Category of the User Equipment for HSDPA Power on the UpPTS timeslot Null column allowed: No Default value: Null column allowed: Yes Default value: 8 Null column allowed: Yes Default value: 21 Null column allowed: Yes Default value: -50 Null column allowed: No Default value: 100 Null column allowed: Yes Default value: Standard Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: -50
397
Forsk 2011
Field NAME
398
AT310_AM_E2
399
Forsk 2011
400
AT310_AM_E2
CustomFields Table Field CHOICE_TYPE Type Integer Description 0=Choice list is optional; 1=Choice list is mandatory Attributes Null column allowed: Yes Default value: 0
FrameConfigurations Table Field UL_SEGMENTATION Type Boolean Description If true, the first UL PUSC zone is segmented Attributes Null column allowed: No Default value: False
401
Forsk 2011
FrequencyBands Table Field GUARD_BAND Type Float Description Guard band between carriers (MHz) Attributes Null column allowed: Yes Default value: 0
MUGTables Table (New) Field MAX_CINR MOBILITY MUG_TABLE SCHEDULER_NAME Type Float Text (50) Memo Text (30) Description C/(I+N) above which no MUG will be applied. Mobility type for which the MUG table is defined. Multi-user diversity gain table Name of the scheduler for which the MUG table is defined. Attributes Null column allowed: No Default value: 16.8 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: No Default value:
Neighbours Table Field RELATION_TYPE Type Short Description Type of the neighbour relation: 0=Intra-carrier; 1=Inter-carrier Attributes Null column allowed: Yes Default value: 0
Networks Table Field BS_SELECTION Type Short Description Best server selection method: 0=Preamble signal level; 1=Preamble C/N; Attributes Null column allowed: Yes Default value: 0
PermutationZones Table Field ULSC_GROUPS_SEG0 ULSC_GROUPS_SEG1 ULSC_GROUPS_SEG2 Type Text (255) Text (255) Text (255) Description Uplink subchannels belonging to segment 0 of the cell Uplink subchannels belonging to segment 1 of the cell Uplink subchannels belonging to segment 2 of the cell Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
RepeaterEquipments Table (New) Field COMMENT_ MANUFACTURER MAX_AMPLIFIER_GAIN MAX_OUTPUT_DL MAX_OUTPUT_UL MIN_AMPLIFIER_GAIN NAME NOISE_FIGURE Type Text (255) Text (50) Float Float Float Float Text (50) Float Description Comments Manufacturer of the repeater equipment Maximum gain of the amplifier (dB) Maximum downlink output power (dBm) Maximum uplink output power (dBm) Minimum gain of the amplifier (dB) Name of the repeater equipment Repeater noise Figure (dB) Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 90 Null column allowed: Yes Default value: 30 Null column allowed: Yes Default value: 12 Null column allowed: Yes Default value: 50 Null column allowed: No Default value: Null column allowed: Yes Default value: 5
402
AT310_AM_E2
Description Step of amplifier gain (dB) Time delay in the equipment (microseconds)
Attributes Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 5
Repeaters Table (New) Field AMPLIFIER_GAIN AZIMUT DONOR_CELLID DONOR_LINK_LOSS DONOR_LINK_TYPE DONOR_PROPAG_MODEL DOWNTILT EQUIPMENT_NAME FEEDER_NAME FEEDERLENGTH HEIGHT REC_ANTENNA REC_FEEDERLENGTH_UL TOTAL_GAIN TOTAL_GAIN_UL TX_ID Type Float Float Text (50) Float Short Text (50) Float Text (50) Text (50) Float Float Text (50) Float Float Float Text (50) TplTransmitters Table Field COMMENT_ NOISE_RISE_UL_SEG PI_DOMAIN_NAME SHAREDMAST Type Text (255) Float Text (50) Text (50) Description Comments Uplink noise rise for the segmented permutation zone Name of the preamble index domain Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Description Gain of the amplifier Azimuth of the donor side antenna Name of the donor cell Loss (dB) between donor and donor side of the repeater 1- Off air 2- Microwave 3- Fibre Name of the propagation model used to calculate prediction between donor and repeater Downtilt of the donor side antenna If no equipment, the repeater is a passive component Name of the donor side feeder Length of donor side feeder Height of the donor side antenna Name of the donor side antenna Length of donor side uplink feeder Total gain to be applied to donor cell pilot power Uplink total gain to be applied to mobile output power Name of the transmitter (and of the transmitter used for coverage) Attributes Null column allowed: Yes Default value: 80 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value:
403
Forsk 2011
Transmitters Table Field SHAREDMAST Type Text (50) Description Shared mast name: enables antenna sharing between transmitters Attributes Null column allowed: Yes Default value:
WCells Table Field DL_ZONE_PB DL_ZONE_PB_STATUS LOCKED_SEGMENT NOISE_RISE_UL_SEG PI_DOMAIN_NAME UL_ZONE_PB UL_ZONE_PB_STATUS Type Integer Short Short Float Text (50) Integer Short Description Downlink zone permbase Downlink zone permbase allocation status: 0=Not allocated; 1=Allocated;2=Locked; Segment locked for automatic allocation or not: 0=Unlocked; 1=Locked; Uplink noise rise for the segmented permutation zone Name of the preamble index domain Uplink zone permbase Uplink zone permbase allocation status: 0=Not allocated; 1=Allocated;2=Locked Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0
WPIDomains Table (New) Field DOMAIN_NAME Type Text (50) Description Name of the preamble index domain Attributes Null column allowed: No Default value:
WPIGroups Table (New) Field DOMAIN_NAME EXCLUDED EXTRA FIRST Type Text (50) Text (225) Text (225) Integer Description Name of the preamble index domain Attributes Null column allowed: Default value:
List of indexes to be excluded from the series defined by FIRST, LAST and Null column allowed: Yes STEP (separated by blank characters) Default value: Indexes to be added. It is forbidden for EXTRA and EXLUDED to have common numbers. Separator must be a blank character. Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Name of the preamble index group in the domain Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 1
LAST
Integer
NAME
Text (50)
STEP
Integer
WServices Table Field DL_LOWEST_BEARER UL_LOWEST_BEARER Type Short Short Description The lowest bearer allowed to be used for this service in DL The lowest bearer allowed to be used for this service in UL Attributes Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1
404
AT310_AM_E2
The format of the binary field, DIAGRAM, is described in "RF 2D Antenna Pattern Format" on page 105.
405
Forsk 2011
Description Downlink losses due to the configuration of the BTS (duplexer and/or combiner) Uplink losses due to the configuration of the BTS (duplexer and/or combiner) Name of Base Station Equipment Noise figure of Base Station Rho factor (not used)
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 100
406
AT310_AM_E2
Field
Type
Description UTM, Undefined, NoProjection, Lambert1SP, Lambert2SP, Mercator, CassiniSoldner, TransMercator, TransMercatorSO, ObliqueStereographic, NewZealandMapGrid, HotineOM, LabordeOM, SwissObliqueCylindical
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
PROJ_METHOD
Short
Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.
407
Forsk 2011
Description Name of the frame configuration The number of subcarriers used for the preamble If true, the first DL PUSC zone is segmented If true, the first UL PUSC zone is segmented
Attributes Null column allowed: No Default value: "Default Frame" Null column allowed: No Default value: Null column allowed: No Default value: False Null column allowed: No Default value: False
408
AT310_AM_E2
Description C/(I+N) above which no MUG will be applied. Mobility type for which the MUG table is defined. Multi-user diversity gain table Name of the scheduler for which the MUG table is defined.
Attributes Null column allowed: No Default value: 16.8 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: No Default value:
409
Forsk 2011
REASON
Integer
TRANSMITTER TYPE
FRAME_DURATION
Short
INTERFERERS_RX_THRESH
Float
410
AT310_AM_E2
Field N_DATA N_FFT N_SUBCHANNELS_CH N_USED NAME POWER_CONTROL_MARGIN PZ_SEL_CRITERION SHARED_RESULTS_FOLDER SYSTEM_ TECHNOLOGY THERMAL_NOISE UL_SYM_DURATIONS_NB VARIABLE_DL_OVERHEAD VARIABLE_UL_OVERHEAD
Type Short Short Short Short Text (50) Float Short Text (255) Text (50) Text (10) Float Short Float Float
Description Number of subcarriers per channel used for data transfer (N_USED - pilot subcarriers) Total number of subcarriers per channel Number of subchannels per channel Number of used subcarriers per channel (N_FFT - guard subcarriers) Type of network Margin Over Max Bearer Threshold defining C/I Target (dB) Permutation zone selection criterion (0 - Preamble C/N; 1 - Preamble C/(I+N)) Shared results storage folder Name of the system Name of the technlogy Thermal noise Number of symbol durations in the uplink subframe DL overhead expressed in trame percentage UL overhead expressed in trame percentage
Attributes Null column allowed: Yes Default value: 192 Null column allowed: Yes Default value: 256 Null column allowed: Yes Default value: 16 Null column allowed: Yes Default value: 200 Null column allowed: No Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: IEEE 802.16e Null column allowed: No Default value: OFDM Null column allowed: Yes Default value: -121 Null column allowed: Yes Default value: 15 Null column allowed: No Default value: 0 Null column allowed: No Default value: 0
411
Forsk 2011
Field SC_GROUPS_SEG0 SC_GROUPS_SEG1 SC_GROUPS_SEG2 SUBCHANNEL_ALLOC_MODE SUBFRAME ULSC_GROUPS_SEG0 ULSC_GROUPS_SEG1 ULSC_GROUPS_SEG2 USED_SC_GROUPS ZONE_ID
Type Short Short Short Short Short Text (255) Text (255) Text (255) Short Short
Description Subchannel groups used by segment 0 Subchannel groups used by segment 1 Subchannel groups used by segment 2
Attributes Null column allowed: Yes Default value: 3 Null column allowed: Yes Default value: 12 Null column allowed: Yes Default value: 48
Name of the subchannel allocation mode Null column allowed: Yes Choice list: 0=PUSC DL; 1=FUSC; 2=OFUSC; 3=AMC; 4=TUSC 1; 5=TUSC 2; Default value: 0 6=PUSC UL; 7=OPUSC; Downlink Subframe or Uplink Subframe Choice list: 0=DL; 1=UL; Uplink subchannels belonging to segment 0 of the cell Uplink subchannels belonging to segment 1 of the cell Uplink subchannels belonging to segment 2 of the cell Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
The secondary subchannel groups used by the segmented DL PUSC zone Null column allowed: Yes (Obsolete) Default value: Zone identifier Choice list: 0 to 7 for DL; 0 to 2 for UL; Null column allowed: No Default value: 0
412
AT310_AM_E2
413
Forsk 2011
Field DONOR_PROPAG_MODEL DOWNTILT EQUIPMENT_NAME FEEDER_NAME FEEDERLENGTH HEIGHT REC_ANTENNA REC_FEEDERLENGTH_UL TOTAL_GAIN TOTAL_GAIN_UL TX_ID
Type Text (50) Float Text (50) Text (50) Float Float Text (50) Float Float Float Text (50)
Description Name of the propagation model used to calculate prediction between donor and repeater Downtilt of the donor side antenna If no equipment, the repeater is a passive component Name of the donor side feeder Length of donor side feeder Height of the donor side antenna Name of the donor side antenna Length of donor side uplink feeder Total gain to be applied to donor cell pilot power Uplink total gain to be applied to mobile output power Name of the transmitter (and of the transmitter used for coverage)
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 25 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value:
Repeater properties are saved in two tables: the donor-side parameters are in the Repeaters table and the coverage-side parameters in the Transmitters table.
0 = Proportional Fair; 1 = Proportional Demand; 2 = Biased (QoS Class); 3 Null column allowed: Yes = Max Aggregate Throughput Default value: 0 0 = Peak MAC Throughput; 1 = Effective MAC Throughput; 2 = Application Throughput 0 = Peak MAC Throughput; 1 = Effective MAC Throughput; 2 = Application Throughput UL Bandwidth Allocation Target: 0 Full Bandwidth; 1 Maintain Connection; 2 Best Bearer Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 2
414
AT310_AM_E2
Description Azimuth of the antenna Percentage of power dedicated to the secondary antenna Remote Electrical tilt of the secondary antenna Mechanical downtilt of the secondary antenna Transmitter name
Attributes Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value:
415
Forsk 2011
416
AT310_AM_E2
Field BTS_NAME CALC_RADIUS CALC_RADIUS2 CALC_RESOLUTION CALC_RESOLUTION2 CELL_SIZE CHANNEL_LIST COMMENT_ DL_LOAD DOWNLINK_EXTERNAL_NOIS E_RISE FBAND FEEDER_NAME FEEDERLENGTH_DL FEEDERLENGTH_UL FRAME_CONFIG HEIGHT IDLE_PILOT_POWER_OFFSET MAX_DL_LOAD MAX_EXT_NEIGHB_NUMBER MAX_NEIGHB_NUMBER MAX_NUMBER_OF_USERS MAX_UL_LOAD MIMO_RX_ANTENNAS MIMO_TX_ANTENNAS MISCDLL MISCULL NAME
Type Text (50) Integer Integer Integer Integer Float Text(255) Text (255) Float Float Text (50) Text (50) Float Float Text (50) Float Float Float Integer Integer Integer Float Short Short Float Float Text (50)
Calculation radius used to define each transmitter calculation area Unit: Null column allowed: Yes m Default value: Second calculation radius Unit: m Calculation resolution Second calculation resolution Radius of the cell (schematically represented by an hexagon) Unit: m Channel numbers used by transmitters Comments Downlink traffic load Inter-network downlink noise rise Frequency band of the cell Name of the feeder equipment Length of downlink feeder Unit: m Length of uplink feeder Unit: m Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
Defines the subchannel, subcarrier, and permutation zone configuration Null column allowed: Yes used at the cell Default value: Antenna height above the ground Unit: m Pilot power offset = Preamble power - Idle Pilot power (dB) Maximum traffic load allowed on downlink Maximum number of inter-technology neighbours Maximum number of intra-technology neighbours Max supported number of users for the cell Maximum traffic load allowed on uplink Number of reception antennas used for MIMO Number of transmission antennas used for MIMO Miscellaneous downlink loss Miscellaneous uplink loss Template name Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value:
417
Forsk 2011
Field NOISE_FIGURE NOISE_RISE_UL NOISE_RISE_UL_SEG NUM_SECTORS PI_DOMAIN_NAME PI_LIST PI_REUSE_MIN_DIST PILOT_POWER_OFFSET POWER PREAMBLE_QUALITY_THRES PROPAG_MODEL PROPAG_MODEL2 REDT RXLOSSES SA_NAME SCHEDULER SEGMENTATION_USAGE SHAREDMAST TILT TMA_NAME TRAFFIC_POWER_OFFSET TX_TYPE TXLOSSES UL_LOAD UL_MU_SM_GAIN UPLINK_EXTERNAL_NOISE_R ISE WEQUIPMENT
Type Float Float Float Integer Text (50) Text(255) Float Float Float Float Text (255) Text (255) Float Float Text (50) Text (30) Float Text (50) Float Text (50) Float Short Float Float Float Float Text (50)
Description Total Noise figure used to determine the thermal noise at the transmitter (Temp) Uplink interference noise rise (dB) Uplink noise rise for the segmented permutation zone Number of sectors Name of the preamble index domain Preamble indexes used by transmitters The minimum reuse distance for the AFP and preamble index allocation Pilot power offset = Preamble power - Pilot power (dB) Cell output power (dBm) Required CNR quality for the preamble signal Name of the propagation model used to calculate prediction Name of the second propagation model used to calculate prediction Remote Electrical tilt Losses on the uplink due to transmitter radio equipment Unit: dB Name of the associated smart antenna Scheduler used by the cell Segmentation usage ratio Shared mast name: enables antenna sharing between transmitters Mechanical downtilt of the main antenna Name of theTower Mounted Amplifier equipment Traffic power offset = Preamble power - traffic power (dB) Type of transmitter (0 = Normal; 1 = Interferer only) Losses on the downlink due to transmitter radio equipment Unit: dB Uplink traffic load Multi-user (collaborative) MIMO gain in uplink Inter-network uplink noise rise Cell equipment
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
418
AT310_AM_E2
419
Forsk 2011
Field REDT RXLOSSES SA_NAME SHAREDMAST SITE_NAME TILT TMA_NAME TX_ID TX_TYPE TXLOSSES
Type Float Float Text (50) Text (50) Text (50) Float Text (50) Text (50) Short Float
Description Remote electrical tilt of the main antenna Losses on the uplink due to transmitter radio equipment Name of the smart antenna assigned to the transmitter Shared mast name: enables antenna sharing between transmitters Name of the site at which the transmitter is located (from the Sites table) Mechanical downtilt of the first antenna Name of theTower Mounted Amplifier equipment Transmitter name Type of transmitter (0 = Normal; 1 = Interferer only) Losses on the downlink due to transmitter radio equipment
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
420
AT310_AM_E2
421
Forsk 2011
Field BSID CELL_ID CHANNEL CHANNEL_STATUS COMMENT_ DL_LOAD DL_ZONE_PB DL_ZONE_PB_STATUS DOWNLINK_EXTERNAL_NOIS E_RISE FBAND FRAME_CONFIG IDLE_PILOT_POWER_OFFSET LOCKED_SEGMENT MAX_DL_LOAD MAX_EXT_NEIGHB_NUMBER MAX_NEIGHB_NUMBER MAX_NUMBER_OF_USERS MAX_UL_LOAD NOISE_RISE_UL NOISE_RISE_UL_SEG PI_DOMAIN_NAME PI_REUSE_MIN_DIST PI_STATUS PILOT_POWER_OFFSET POWER PREAMBLE_INDEX PREAMBLE_QUALITY_THRES
Type Text (50) Text (50) Integer Short Text (255) Float Integer Short Float Text (50) Text (50) Float Short Float Integer Integer Integer Float Float Float Text (50) Float Short Float Float Integer Float
Description Cell connexion identifier Name of the cell Channel number Channel allocation status (0 = Not allocated, 1 = Allocated, 2 = Locked) Additional information about the cell Downlink cell traffic load Downlink zone permbase Downlink zone permbase allocation status: 0=Not allocated; 1=Allocated;2=Locked; Inter-network downlink noise rise Frequency band of the cell
Attributes Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value:
Defines the subchannel, subcarrier, and permutation zone configuration Null column allowed: Yes used at the cell Default value: Offset (in dB) with respect to the preamble power for determining the pilot power during the empty part of the frame Segment locked for automatic allocation or not: 0=Unlocked; 1=Locked; Maximum traffic load allowed on downlink Maximum number of inter-technology neighbours for this cell Maximum number of intra-technology neighbours for this cell Max supported number of users for the cell Maximum traffic load allowed on uplink Uplink noise rise (dB). Manually specified by the user or calculated during simulations. Uplink noise rise for the segmented permutation zone Name of the preamble index domain The minimum reuse distance for the AFP and preamble index allocation Preamble index status (0 = Not allocated, 1 = Allocated, 2 = Locked) Offset (in dB) with respect to the preamble power for determining the pilot power during the loaded part of the frame Output PowerUnit: dBm Preamble index of the cell Required CNR quality for the preamble signal Null column allowed: Yes Default value: 10 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 100 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 100 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 43 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: -4
422
AT310_AM_E2
Field RANK SCHEDULER SEGMENTATION_USAGE TRAFFIC_POWER_OFFSET TX_ID UL_LOAD UL_MU_SM_GAIN UL_ZONE_PB UL_ZONE_PB_STATUS UPLINK_EXTERNAL_NOISE_R ISE WEQUIPMENT
Type Short Text (30) Float Float Text (50) Float Float Integer Short Float Text (50)
Description Zero based order used by scheduler for sequential cell selection Scheduler used by the cell Percentation of downlink traffic load dedicated to the segmented zone Offset (in dB) with respect to the preamble power for determining the traffic power Name of the transmitter to which the cell belongs Uplink cell traffic load Multi-user (collaborative) MIMO gain in uplink Uplink zone permbase Uplink zone permbase allocation status: 0=Not allocated; 1=Allocated;2=Locked Inter-network uplink noise rise WiMAX equipment installed at the cell
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 50 Null column allowed: Yes Default value: 3 Null column allowed: No Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 2 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value:
423
Forsk 2011
Type Memo Short Short Text (50) Float Short Text (50)
Description Graph of maximum MIMO gains vs. C/(I+N) Number of MIMO antennas used for reception Number of MIMO antennas used for transmission User mobility Gain that will be applied to the CINR in STTD mode (dB) Subchannel allocation mode Name of the equipment to which the MIMO gains correspond
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 8 Null column allowed: No Default value:
List of indexes to be excluded from the series defined by FIRST, LAST and Null column allowed: Yes STEP (separated by blank characters) Default value: Indexes to be added. It is forbidden for EXTRA and EXLUDED to have common numbers. Separator must be a blank character. Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Name of the preamble index group in the domain Group elements are: FIRST, FIRST+STEP, FIRST+2*STEP, , FIRST+n*STEP. n is the greatest positive integer so that FIRST+n*STEP LAST. Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 1
LAST
Integer
NAME STEP
424
AT310_AM_E2
QOS_CLASS
Short
425
Forsk 2011
Field UL_HIGHEST_BEARER UL_LOWEST_BEARER UL_MAXIMUM_LATENCY UL_MRTR UL_MSTR UL_NPC UL_SP UL_SPC_MAX UL_SPC_MIN
Type Float Short Float Float Float Integer Integer Float Float
Description The highest bearer to allowed to be used for this service in UL The lowest bearer allowed to be used for this service in UL Maximum latency in UL (ms) Minimum required transmission rate in UL (Committed Information Rate) Maximum sustained trasmission rate in UL (Maximum Information Rate) Number of packet calls during a session in uplink Packet size (Bytes) in uplink Uplink maximum packet call size (kBytes) Uplink minimum packet call size (kBytes)
Attributes Null column allowed: Yes Default value: 4 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1500 Null column allowed: Yes Default value: 2000 Null column allowed: Yes Default value: 4
426
AT310_AM_E2
Description Number of MIMO antennas used for transmission Terminal name Noise figure used to determine the thermal noise at the receiver (dB) Maximum terminal power on traffic channel (dBm) Minimum terminal power on traffic channel (dBm) Name of the WiMAX equipment available at the terminal
Attributes Null column allowed: Yes Default value: 1 Null column allowed: No Default value: Null column allowed: Yes Default value: 8 Null column allowed: Yes Default value: 23 Null column allowed: Yes Default value: -22 Null column allowed: Yes Default value:
427
Forsk 2011
428
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
MWAntennas Table Field RADOME_LOSS Type Float Description Radome loss to take into account when radomes are used on links Attributes Null column allowed: Yes Default value: 0
MWBranchingConfigs Table (New) Field FREQ_DIVERSITY HSB NAME SPACE_DIVERSITY SYSTEM_CONFIG_M SYSTEM_CONFIG_N XPIC Type Boolean Boolean Text (50) Boolean Short Short Boolean Description Flag to check if this configuration supports frequency diversity Flag to check if this configuration supports hot standby Branching configuration name Flag to check if this configuration supports space diversity Maximum number of standby channels which can be branched Maximum number of main channels which can be branched Flag to check if this configuration supports cross polar cancellation Attributes Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: No Default value: Null column allowed: No Default value: False Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: False
MWCapacities Table (New) Field AIR_LINK_RATE NAME Type Float Text (50) MWEPO Table Field COMMENT_ MAXIMUM_LENGTH MINIMUM_LENGTH Type Text (255) Double Double Description Comments Maximum length of link related to an objective (km) Maximum length of link related to an objective (km) Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Description Data rate Capacity name Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value:
429
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Forsk 2011
MWEquipments Table Field ACM_MODE CHANNEL_SPACING DFM EMISSION_DESIGNATOR FAMILY MIN_PHASE_SIG_DEPTH Type Short Text (50) Memo Text (20) Text (50) Memo Description Optimisation mode: 0=None; 1=Max system gain; 2=Max throughput gain; Channel spacing defined by the manufacturer for this capactiy/ modulation Dispersive fade margin curve Normalized designator Family name Minimum signature depth Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: '1e-6 30 1e-3 30' Null column allowed: Yes Default value: '1e-6 10 1e-3 10' Null column allowed: Yes Default value: '1e-6 30 1e-3 30' Null column allowed: Yes Default value: '1e-6 10 1e-3 10' Null column allowed: Yes Default value: '1e-6 -25 1e-3 -20' Null column allowed: No Default value: False
Memo
Memo
Memo
Memo Boolean
Curve which defines the thresholds max value for any value of BER Used to calculate Kn
MWFamilies Table (New) Field COMMENT_ MANUFACTURER NAME Type Text (255) Text (50) Text (50) MWFamilyBands Table (New) Field ACM_MODE FAMILY FREQ_BAND Type Integer Text (50) Text (50) Description Optimisation mode: 0=None; 1=Max system gain; 2=Max throughput gain; Family name Frequency band Attributes Null column allowed: No Default value: 0 Null column allowed: No Default value: Null column allowed: No Default value: Description Comments Manufacturer name Family name Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value:
MWFamilyBrConfigs Table (New) Field BRANCHING_CONFIG FAMILY Type Text (50) Text (50) Description Branching configuration name Family name Attributes Null column allowed: No Default value: Null column allowed: No Default value:
430
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Description Frequency band Main channel reception loss Standby channel reception loss Transmission loss
Attributes Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
MWFamilyChSpacings Table (New) Field CHANNEL_SPACING FAMILY FREQ_BAND XS Type Text (50) Text (50) Text (50) Double MWFamilyModulations Table (New) Field ACM_MODE ATPC_MAX ATPC_STEP DISCRETE_POWERS FAMILY FREQ_BAND MAX_POWER MODULATION STD_POWER Type Short Float Float Text (255) Text (50) Text (50) Float Text (20) Float Description Optimisation mode: 0=None; 1=Max system gain; 2=Max throughput gain; Maximum supported ATPC value ATPC interval Allowed power values Family name Frequency bands Maximum power Modulation Standard power Attributes Null column allowed: No Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 30 Null column allowed: No Default value: Null column allowed: Yes Default value: Description Channel spacing name Family name Frequency band Channel spacing in MHz Attributes Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 7
MWLinks Table Field ACTIVE_MODULATIONS_A ACTIVE_MODULATIONS_B BRANCHING_CONFIG_A BRANCHING_CONFIG_B RADOME_ON_A Type Text (100) Text (100) Text (50) Text (50) Boolean Description List of modulations used at A List of modulations used at B Branching configuration at A Branching configuration at B Radome used on the first antenna at A Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: False
431
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Forsk 2011
Description Radome used on the first antenna at B Radome used on the second antenna at A Radome used on the second antenna at B Rain zone N-units /km Terrain type (Vigants) Type of power at A: True=Standard (low) or False= Maximum (high) Type of power at B: True=Standard (low) or False= Maximum (high)
Attributes Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: Yes Default value: 4 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: False Null column allowed: No Default value: False
MWLinkTypes Table Field TYPE Type Short MWModulations Table (New) Field EB_N0 FULL_NAME NAME NSTATES Type Memo Text (255) Text (20) Integer Description Eb/No graph Comments Modulation Number of modulation states Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 16 Description Trunk type: 0=PDH; 1=SDH/SONET; 2=IP; Attributes Null column allowed: Yes Default value: 0
MWTplLinks Table Field BRANCHING_CONFIG_A BRANCHING_CONFIG_B RAIN_ZONE REFRACTIVITY_KE TERRAIN_TYPE Type Text (50) Text (50) Short Float Integer Description Branching configuration at A Branching configuration at B Rain zone N-units /km Terrain type (Vigants) Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 4 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0
432
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
MWEquipments Table ATPC_MAX BM BNM EQ_TYPE HSB INCR_PORT_RX_LOSS INCR_PORT_TX_LOSS MANUF_CHANNEL_SPACING MANUFACTURER POWER SYSTEM_CONFIG_M SYSTEM_CONFIG_N THRESHOLD_MAX WM WNM
EQ_TYPE
CAPACITY
MODULATION
No change
433
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Forsk 2011
Remarks FAMILY field of the MWEquipments table points to a record in the MWFamilies table which is linked to the FAMILY field of the MWFamilyModulations table whose MAX_POWER is now used instead of POWER of the MWEquipments table. FAMILY field of the MWEquipments table points to a record in the MWFamilies table which is linked to the FAMILY field of the MWFamilyModulations table whose ATPC_MAX is now used instead of ATPC_MAX of the MWEquipments table. THRESHOLD_MAX of type Double is replaced by RX_OVERFLOW field of type Memo in order to store graphs instead of a simple value. RX_OVERFLOW contains THRESHOLD_MAX value (X) by default: 1e-6 X 1e-3 X. WM of type Double is replaced by MIN_PHASE_SIG_WIDTH field of type Memo in order to store graphs instead of a simple value. MIN_PHASE_SIG_WIDTH contains WM value (X) by default: 1e-6 X 1e-3 X.
ATPC_MAX
ATPC_MAX field of the MWFamilyModulations table RX_OVERFLOW field of the MWEquipments table MIN_PHASE_SIG_WIDTH field of the MWEquipments table
THRESHOLD_MAX
WM
WNM
WNM of type Double is replaced by NON_MIN_PHASE_SIG_WIDTH field of type NON_MIN_PHASE_SIG_WID Memo in order to store graphs instead of a simple value. TH field of the NON_MIN_PHASE_SIG_WIDTH contains WNM value (X) by default: 1e-6 X 1e-3 MWEquipments table X. MIN_PHASE_SIG_DEPTH field of the MWEquipments table BM of type Double is replaced by MIN_PHASE_SIG_DEPTH field of type Memo in order to store graphs instead of a simple value. MIN_PHASE_SIG_DEPTH contains BM value (X) by default: 1e-6 X 1e-3 X.
BM
BNM
BNM of type Double is replaced by NON_MIN_PHASE_SIG_DEPTH field of type NON_MIN_PHASE_SIG_DEPT Memo in order to store graphs instead of a simple value. H field of the NON_MIN_PHASE_SIG_DEPTH contains BNM value (X) by default: 1e-6 X 1e-3 MWEquipments table X. SYSTEM_CONFIG_N field of the MWBranchingConfigs table FAMILY field of the MWEquipments table points to a record in the MWFamilies table which is linked to the FAMILY field of the MWFamilyBrConfigs table. BRANCHING_CONFIG field of the MWFamilyBrConfigs table points to a record in the MWBranchingConfigs table whose SYSTEM_CONFIG_N is now used instead of SYSTEM_CONFIG_N of the MWEquipments table.
SYSTEM_CONFIG_N
SYSTEM_CONFIG_M
FAMILY field of the MWEquipments table points to a record in the MWFamilies SYSTEM_CONFIG_M field of table which is linked to the FAMILY field of the MWFamilyBrConfigs table. the MWBranchingConfigs BRANCHING_CONFIG field of the MWFamilyBrConfigs table points to a record in table the MWBranchingConfigs table whose SYSTEM_CONFIG_M is now used instead of SYSTEM_CONFIG_M of the MWEquipments table. No change No change No change CHANNEL_SPACING field of the MWEquipments table Obsolete Obsolete Obsolete MANUF_CHANNEL_SPACING of type Float is replaced by CHANNEL_SPACING field of type Text.
MWLinks Table Atoll 2.8 Field DIVERSITY_A Atoll 3.1 Field SPACE_DIVERSITY field of the MWBranchingConfigs table SPACE_DIVERSITY field of the MWBranchingConfigs table XPIC field of the MWBranchingConfigs table XPIC field of the MWBranchingConfigs table Remarks BRANCHING_CONFIG_A field of the MWLinks table points to a record in the MWBranchingConfigs table whose SPACE_DIVERSITY is now used instead of DIVERSITY_A of the MWLinks table BRANCHING_CONFIG_B field of the MWLinks table points to a record in the MWBranchingConfigs table whose SPACE_DIVERSITY is now used instead of DIVERSITY_B of the MWLinks table BRANCHING_CONFIG_A field of the MWLinks table points to a record in the MWBranchingConfigs table whose XPIC is now used instead of XPIC of the MWLinks table BRANCHING_CONFIG_B field of the MWLinks table points to a record in the MWBranchingConfigs table whose XPIC is now used instead of XPIC_B of the MWLinks table
DIVERSITY_B
XPIC
XPIC_B
434
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
MWLinkTypes Table Atoll 2.8 Field SDH Atoll 3.1 Field TYPE field of the MWLinkTypes table Remarks The TYPE field replaces the SDH field in order to have more than two possible values. SDH False = TYPE 0 (PDH); SDH True = TYPE 1 (SDH); TYPE 2 (IP);
PROJ_METHOD
Short
PROJ_SCALE_FACTOR
Double
435
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Forsk 2011
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.
The format of the binary field, PATTERN, is described in "Microwave 2D Antenna Pattern Format" on page 107.
436
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
437
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Forsk 2011
438
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Description Maximum length of link related to an objective (km) EPO name Maximum bit rate (Mbps) Minimum bit rate (Mbps) ITU Recommendations
Attributes Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1
439
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Forsk 2011
Attributes Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: '1e-6 30 1e-3 30' Null column allowed: Yes Default value: '1e-6 10 1e-3 10' Null column allowed: No Default value: 16-QAM Null column allowed: Yes Default value: 1000000 Null column allowed: No Default value: Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value: '1e-6 30 1e-3 30' Null column allowed: Yes Default value: '1e-6 10 1e-3 10' Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: '1e-6 -25 1e-3 -20' Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1e-6 -82 1e-3 -90 Null column allowed: Yes Default value:
Minimum signature width Modulation type Mean Time Before Failure Name of the equipment Noise Figure of the equipment Non minimum signature depth
Memo Float
RX_OVERFLOW RX_PORT_1 RX_PORT_2 RX_PORT_3 RX_PORT_4 RX_PORT_5 RX_PORT_6 RX_PORT_7 RX_PORT_8 RX_PORT_9 RX_PORT_10 RX_SELECTIVITY
Memo Float Float Float Float Float Float Float Float Float Float Memo
Curve which defines the thresholds max value for any value of BER Receiving loss on port number 1 Receiving loss on port number 2 Receiving loss on port number 3 Receiving loss on port number 4 Receiving loss on port number 5 Receiving loss on port number 16 Receiving loss on port number 7 Receiving loss on port number 8 Receiving loss on port number 9 Receiving loss on port number 10 Receiver filter selectivity
RX_SENSITIVITY TI_CURVE
Memo Memo
440
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Field TX_LOSS_PHYS TX_MASK TX_PORT_1 TX_PORT_2 TX_PORT_3 TX_PORT_4 TX_PORT_5 TX_PORT_6 TX_PORT_7 TX_PORT_8 TX_PORT_9 TX_PORT_10 WITH_EQUALIZER XPIF
Type Float Memo Float Float Float Float Float Float Float Float Float Float Boolean Float
Description Physical transmitter loss Transmitter spectrum mask Transmission loss on port number 1 Transmission loss on port number 2 Transmission loss on port number 3 Transmission loss on port number 4 Transmission loss on port number 5 Transmission loss on port number 6 Transmission loss on port number 7 Transmission loss on port number 8 Transmission loss on port number 9 Transmission loss on port number 10 Used to calculate Kn Crosspolar Interference Factor
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: False Null column allowed: Yes Default value: 20
441
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Forsk 2011
442
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
The IRF field represents a list of pairs of values. Each pair consists of: float deltaF: spacing in frequency float protection: protection applied to this frequency
443
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Forsk 2011
444
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Field DX_A DX_B DY_A DY_B ENVTYPE EPO_CLASS EQUIPMENT_A EQUIPMENT_B FREQ_A FREQ_B FREQ_BAND FREQ_SUBBAND FREQ_SUBBAND_B GEOCLIM_FACTOR GUIDE_LG1 GUIDE_LG2 GUIDE_LG3 GUIDE_LG4 GUIDE_USE1 GUIDE_USE2 GUIDE_USE3 GUIDE_USE4 GUIDE1 GUIDE2 GUIDE3 GUIDE4 HEIGHT_A
Type Float Float Float Float Integer Text (50) Text (50) Text (50) Double Double Text (50) Text (50) Text (50) Double Float Float Float Float Integer Integer Integer Integer Text (50) Text (50) Text (50) Text (50) Float
Description X coordinate relative to the site A position X coordinate relative to the site B position Y coordinate relative to the site A position Y coordinate relative to the site B position Type of environment EPO Class for the link Equipment at site A Equipment at site B Frequency at site A Frequency at site B Frequency band of the link Frequency subband of the link (site A) Frequency subband of the link (site B)
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: -1 Null column allowed: Yes Default value: -1 Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
Length of GUIDE1 Length of GUIDE2 Length of GUIDE3 Length of GUIDE4 Use of Guide 1 on site A Use of Guide 2 on site B Use of Guide 1 on site B Use of Guide 2 on site A Waveguide when A transmitting Waveguide when B receiving Waveguide when B transmitting Waveguide when A receiving Height at site A
Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0
445
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Forsk 2011
Field HEIGHT_B KQ_FACTOR MTTR NAME PARITY_A PARITY_B PL POLARIZATION_A POLARIZATION_B PROFILE PROPAG_IMODEL PROPAG_MODEL R001 RADOME_ON_A RADOME_ON_B RADOME2_ON_A RADOME2_ON_B RAIN_HEIGHT RAIN_ZONE REFRACTIVITY REFRACTIVITY_KE REPEATER1 REPEATER2 RXLOSS_ATT_A RXLOSS_ATT_B SEPARATION_A SEPARATION_B
Type Float Float Float Text (120) Integer Integer Float Text (1) Text (1) Binary Text (50) Text (50) Float Boolean Boolean Boolean Boolean Float Short Float Float Text (50) Text (50) Float Float Float Float
Description Height at site B KQ reliability method: KQ Factor Minimum Time To Repair Name of the microwave link Parity of site A Parity of site B
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 10
Polarization at site A Polarization at site B Link profile Propagation model used for interference calculation Propagation model Rain intensity exceeded for 0.01% of time (mm/hr) Radome used on the first antenna at A Radome used on the first antenna at B Radome used on the second antenna at A Radome used on the second antenna at B
Null column allowed: Yes Default value: V Null column allowed: Yes Default value: V Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: Yes Default value:
Rain zone
Null column allowed: Yes Default value: 4 Null column allowed: Yes Default value:
N-units /km First repeater (P) Second repeater (Q) Reception losses due to attenuators at A Reception losses due to attenuators at B Diversity separation at site A Diversity separation at site B
Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0
446
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Field SHIELDING_FACTOR_A SHIELDING_FACTOR_B SITE_A SITE_B TEMPERATURE TERRAIN_TYPE TXLOSS_ATT_A TXLOSS_ATT_B TXLOSS_BRANCHING_A TXLOSS_BRANCHING_B USE_STD_POWER_A USE_STD_POWER_B VAPOR
Type Float Float Text (50) Text (50) Float Integer Float Float Float Float Boolean Boolean Float
Description
Attributes
Additional loss due to a natural or artificial obstacle in the vicinity of the Null column allowed: Yes antenna A Default value: 0 Additional loss due to a natural or artificial obstacle in the vicinity of the Null column allowed: Yes antenna B Default value: 0 Site of departure (A) Site of arrival (B) Temperature Terrain type (Vigants) Transmission losses due to attenuators at A Transmission losses due to attenuators at B Transmission losses due to connectors and branching at A Transmission losses due to connectors and branching at B Type of power at A: True=Standard (low) or False= Maximum (high) Type of power at B: True=Standard (low) or False= Maximum (high) Vapour density (g/cu. m) Null column allowed: No Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: False Null column allowed: No Default value: False Null column allowed: Yes Default value:
447
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Forsk 2011
448
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Description Signal polarization of this channel Rx attenuation loss for this channel Number of the port on the RX equipment where the channel is connected Status of the microwave port (0 = main,1 = standby, or 2 = diversity) Tx attenuation loss for this channel Number of the port on the TX equipment where the channel is connected Way of the link AB or BA
Attributes Null column allowed: No Default value: H Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: No Default value: 0
449
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Forsk 2011
Height of the repeater Height (pointed to B) Guide length Name of the repeater
Null column allowed: Yes Default value: 30 Null column allowed: Yes Default value: 30 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 0 (Reflector) Null column allowed: No Default value: False Null column allowed: No Default value: Null column allowed: Yes Default value: 5 Null column allowed: Yes Default value:
Type of the repeater (Reflector or Back-to-back antennas) If true, tx polarization from P to B is not the same as from A to P (and resp, B->P is different to P->A) Name of the repeaters site Repeater surface area (sq. m) Tilt of the repeater antenna in the direction of A
450
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Field ANTENNA_A ANTENNA_B ATMOS_PRESSURE BER BER2 BRANCHING_CONFIG_A BRANCHING_CONFIG_B C_FACTOR CLIMATE_ZONE ENVTYPE EPO_CLASS EQUIPMENT_A EQUIPMENT_B FREQ_BAND GUIDE_LG1 GUIDE_LG2 GUIDE_LG3 GUIDE_LG4 GUIDE_USE1 GUIDE_USE2 GUIDE_USE3 GUIDE_USE4 GUIDE1 GUIDE2 GUIDE3 GUIDE4 HEIGHT_A
Type Text (50) Text (50) Float Double Double Text (50) Text (50) Float Short Integer Text (50) Text (50) Text (50) Text (50) Float Float Float Float Integer Integer Integer Integer Text (50) Text (50) Text (50) Text (50) Float
Description Main antenna at site A Main antenna at site B Atmospheric pressure in mbar Bit Error Rate Second Bit Error Ratio (i.e. 1e-6) Branching configuration at A Branching configuration at B Vigants-Barnett method: C factor Rain Climate Zone Type of environment EPO Class for the link Equipment at site A Equipment at site B Frequency band of the link Length of GUIDE1 Length of GUIDE2 Length of GUIDE3 Length of GUIDE4 Use of Guide 1 on site A Use of Guide 2 on site B Use of Guide 1 on site B Use of Guide 2 on site A Waveguide when A transmitting Waveguide when B receiving Waveguide when B transmitting Waveguide when A receiving Height at site A
Attributes Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1e-3 Null column allowed: Yes Default value: 1e-6 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 4 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: No Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 1 Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0
451
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Forsk 2011
Field HEIGHT_B KQ_FACTOR MTTR NAME PL POLARIZATION_A POLARIZATION_B PROPAG_IMODEL PROPAG_MODEL R001 RAIN_HEIGHT RAIN_ZONE REFRACTIVITY REFRACTIVITY_KE RXLOSS_ATT_A RXLOSS_ATT_B TEMPERATURE TERRAIN_TYPE TXLOSS_ATT_A TXLOSS_ATT_B TXLOSS_BRANCHING_A TXLOSS_BRANCHING_B VAPOR
Type Float Float Float Text (120) Float Text (1) Text (1) Text (50) Text (50) Float Float Short Float Float Float Float Float Integer Float Float Float Float Float
Description Height at site B KQ reliability method: KQ Factor Minimum Time To Repair Name of the microwave link template
Attributes Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: No Default value: Null column allowed: Yes Default value: 10
Polarisation of the descending link 'siteA - site B' (the site A and site B are respectively transmitter and receiver) Polarisation of the ascending link 'siteA-site B' (the site A and site B are respectively receiver and transmitter) Propagation model used for interference calculation Propagation model Rain intensity exceeded for 0.01% of time (mm/hr)
Null column allowed: Yes Default value: V Null column allowed: Yes Default value: V Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value: Null column allowed: Yes Default value:
Rain zone
Null column allowed: Yes Default value: 4 Null column allowed: Yes Default value:
N-units /km Reception losses due to attenuators at A Reception losses due to attenuators at B Temperature Terrain type (Vigants) Transmission losses due to attenuators at A Transmission losses due to attenuators at B Transmission losses due to connectors and branching at A Transmission losses due to connectors and branching at B Vapour density (g/cu. m)
Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value: 0 Null column allowed: Yes Default value:
452
AT310_AM_E2
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Type Float Float Text (50) Text (255) Text (50) Text (10)
Attributes Null column allowed: Yes Default value: 50 Null column allowed: Yes Default value: -1 Null column allowed: No Default value:
Shared results storage folder Name of the system Name of the technology
Null column allowed: Yes Default value: Null column allowed: No Default value: MW Null column allowed: No Default value: FWA
453
Atoll 3.1.0 Administrator Manual Chapter 20: Microwave Links Data Structure
Forsk 2011
Description First part of the unique key. Name of the list Second part of the unique key. Name of the site
Attributes Null column allowed: No Default value: Null column allowed: No Default value:
454
AT310_AM_E2
455
Administrator Manual
version 3.1.0
AT310_AM_E2 12 July 2011
Head Office
7, rue des Briquetiers 31700 Blagnac - France Tel: +33 562 747 210 Fax: +33 562 747 211
US Office
200 South Wacker Drive - Suite 3100 Chicago, IL 60606 - USA Tel: +1 312 674 4800 Fax: +1 312 674 4847
China Office
Suite 302, 3/F, West Tower, Jiadu Commercial Building, No. 66 Jianzhong Road, Tianhe Hi-Tech Industrial Zone, Guangzhou, 510665, P. R. of China Tel: +86 20 8553 8938 Fax: +86 20 8553 8285
www.forsk.com