Atoll 2[1].8.1 Administrator Manual E1

Atoll RF Planning & Optimisation Software Administrator Manual v e r s i o n 2.8.1 AT281_AM_E1 Administrator Manual Contact Information Forsk (Head Office) 7 rue des Briquetiers 31700 Blagnac France      Forsk (USA Office) 200 South Wacker Drive Suite 3100 Chicago, IL 60606 USA     Forsk (China Office) Suite 302, 3/F, West Tower, Jiadu Commercial Building, No.66 Jianzhong Road, Tianhe Hi-Tech Industrial Zone, Guangzhou, 510665, People’s Republic of China     www.forsk.com sales@forsk.com helpdesk@forsk.com +33 (0) 562 74 72 10 +33 (0) 562 74 72 25 +33 (0) 562 74 72 11 Web Sales and pricing information Technical support General Technical support Fax sales_us@forsk.com support_us@forsk.com +1 312 674 4846 +1 888 GoAtoll (+1 888 462 8655) +1 312 674 4847 Sales and pricing information Technical support General Technical support Fax www.forsk.com.cn enquiries@forsk.com.cn +86 20 8553 8938 +86 20 8553 8285 +86 10 6513 4559 Web Information and enquiries Telephone Fax (Guangzhou) Fax (Beijing) Atoll 2.8.1 Administrator Manual Release AT281_AM_E1 © Copyright 1997 - 2009 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. About Administrator Manual This manual is written for the system and database administrator in charge of installing, configuring, or tuning Atoll. This document covers topics related to various tasks an Atoll administrator might have to perform, namely, Atoll installation, licence server installation, database setup, network data administration, etc. The contents of this manual primarily explain the architecture, installation procedure, database structure, database related operations, administration files, and technical recommendations for optimum usage of Atoll in various environments. This document begins with an installation guide explaining how to install Atoll and the associated utilities. This manual contains detailed information about database administration and specific Atoll administration files. It also describes the features and functions of the Atoll Management Console and a user-manual approach to their operation and handling. It also contains details of specific and new concepts introduced by the Atoll Management Console and its approach to Atoll database manipulations. Lastly, it cites an exhaustive list of recommendations, i.e., recommended hardware and software configurations, necessary and recommended software patches, and recommendations on procedures. This document also lists the modifications and additions in the data structure of the current version with respect to the earlier. It also contains more information on the database upgrading from previous to current version. © Forsk 2009 AT281_AM_E1 3 Administrator Manual 4 AT281_AM_E1 © Forsk 2009 Table of Contents Table of Contents 1 1.1 1.1.1 1.2 1.2.1 1.2.1.1 1.2.1.2 1.2.2 1.2.3 1.2.4 1.2.5 1.2.6 1.3 1.3.1 1.3.2 1.3.2.1 1.3.2.2 1.3.2.3 1.3.2.4 1.3.3 1.4 1.4.1 1.4.2 1.5 2 2.1 2.1.1 2.2 2.2.1 2.2.2 2.2.2.1 2.2.2.2 2.2.2.3 2.2.2.3.1 2.2.3 2.2.3.1 2.2.4 2.2.4.1 2.2.4.1.1 2.2.4.2 2.2.5 2.2.5.1 2.2.5.1.1 2.2.5.1.2 2.2.5.2 2.2.5.3 2.3 2.3.1 2.3.2 2.3.2.1 2.3.2.2 2.3.2.3 2.3.2.4 2.3.2.4.1 2.3.2.4.2 2.3.2.4.3 2.3.2.5 2.4 © Forsk 2009 Installation Guide ............................................................................ 23 Introduction ............................................................................................................................................ 23 Technical Support ............................................................................................................................ 23 Atoll Installation ...................................................................................................................................... 24 Installation Procedures ..................................................................................................................... 24 Interactive Installation ................................................................................................................. 24 Command Line Installation ......................................................................................................... 26 What's Installed With Atoll ................................................................................................................ 27 Installation Troubleshooting ............................................................................................................. 27 Getting Help in Atoll.......................................................................................................................... 28 Atoll C++ Development Kit Installation ............................................................................................. 28 Uninstalling Atoll............................................................................................................................... 29 Floating License Manager Installation.................................................................................................... 29 Requirements ................................................................................................................................... 30 Installation Procedure....................................................................................................................... 30 NetHASP License Manager........................................................................................................ 30 nhsrv.ini File................................................................................................................................ 33 NetHASP Monitor ....................................................................................................................... 33 NetHASP.ini File ......................................................................................................................... 33 License Management Using Lic.exe ................................................................................................ 34 Distributed Calculation Server................................................................................................................ 36 Installing the Distributed Calculation Server..................................................................................... 37 Uninstalling the Distributed Calculation Server ................................................................................ 38 Add-in and Macro Installation................................................................................................................. 38 Multi-user Environments and Databases ........................................ 43 Components of Multi-user Environments ............................................................................................... 43 Supported RDBMS ........................................................................................................................... 44 Setting Up Multi-user Environments....................................................................................................... 44 Master Atoll Document ..................................................................................................................... 45 Shared Path Loss Matrices .............................................................................................................. 45 Setting Up Shared Path Loss Matrices....................................................................................... 45 Calculating Path Loss Matrices Only .......................................................................................... 46 Working With Path Loss Matrices From Different Sources......................................................... 47 Managing Several Sources for Path Loss Matrices .............................................................. 47 Shared Geographic Data and User Configurations .......................................................................... 48 Loading a User Configuration File Automatically........................................................................ 48 Master Database .............................................................................................................................. 48 Creating the Master Database.................................................................................................... 49 Exporting the Master Atoll Document to a Database ............................................................ 49 Setting Database Access Privileges ........................................................................................... 51 User Atoll Documents....................................................................................................................... 51 Regionalising the Master Database............................................................................................ 51 Static Regionalisation ........................................................................................................... 51 Dynamic Regionalisation....................................................................................................... 52 Creating or Opening an Atoll Document from a Database ......................................................... 52 Opening a Project From a Database Automatically.................................................................... 52 Working in Multi-user Environments ...................................................................................................... 53 Data Exchange Summary ................................................................................................................ 53 Common Database Operations ........................................................................................................ 53 Checking Database Connection Properties................................................................................ 53 Loading Data From a Database.................................................................................................. 54 Archiving Data in a Database ..................................................................................................... 54 Resolving Database Conflicts..................................................................................................... 56 Resolving a Conflict on a Modified Record ........................................................................... 56 Resolving a Conflict on a Deleted Record ............................................................................ 58 Resolving All the Conflicts Simultaneously ........................................................................... 58 Checking Database Consistency................................................................................................ 58 Using Oracle With Atoll .......................................................................................................................... 59 AT281_AM_E1 5 Administrator Manual 2.4.1 2.4.2 2.4.3 2.4.4 2.4.5 2.4.5.1 2.4.5.2 2.5 2.5.1 2.5.2 2.5.3 2.5.3.1 3 3.1 3.1.1 3.1.1.1 3.1.2 3.1.2.1 3.1.2.2 3.1.3 3.1.4 3.1.4.1 3.1.4.2 3.1.4.3 3.1.4.4 3.1.4.5 3.1.4.6 3.1.4.7 3.1.4.8 3.1.4.9 3.1.4.10 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.3 3.3.1 3.3.1.1 3.3.1.2 3.3.1.3 3.3.1.4 3.3.1.5 3.3.1.6 3.3.1.7 3.3.1.8 3.3.1.9 3.3.1.10 3.3.1.11 3.3.1.12 3.3.1.13 3.3.1.14 3.3.1.15 3.3.1.16 3.3.1.17 3.3.1.18 3.3.1.19 3.3.2 3.3.2.1 3.3.2.2 3.3.2.3 3.3.2.4 3.3.2.5 3.3.2.6 3.3.2.7 3.3.2.8 6 Setting Up an Oracle Database for Atoll ...........................................................................................59 Creating a Project Account ...............................................................................................................59 Creating Tables.................................................................................................................................60 Creating Other User Accounts ..........................................................................................................60 Appendices .......................................................................................................................................60 Appendix 1: Advanced Customisation.........................................................................................60 Appendix 2: Oracle Architecture..................................................................................................62 Setting Up Databases for Co-Planning...................................................................................................64 Sharing Tables in Oracle, SQL Server, or Sybase............................................................................64 Sharing Tables Microsoft Access......................................................................................................64 Setting Up Shared Antenna Parameter Synchronisation ..................................................................65 Ensuring Database Consistency for Shared Antenna Parameters .............................................65 Administration Files .........................................................................69 User Configuration File (.cfg)..................................................................................................................69 Creating a User Configuration File....................................................................................................70 Exporting User Configurations to User Configuration Files .........................................................70 Loading User Configuration Files......................................................................................................70 Loading User Configuration Files With Atoll................................................................................70 Importing User Configurations From User Configuration Files....................................................71 Setting Up Configuration Files for Co-Planning ................................................................................71 User Configuration File Contents ......................................................................................................71 Geographic Data Set ...................................................................................................................71 Folder Configuration....................................................................................................................74 Computation and Focus Zones ...................................................................................................81 Coverage Prediction Study List ...................................................................................................81 Automatic Neighbour Allocation Parameters...............................................................................81 Automatic Frequency Planning Parameters ................................................................................83 Automatic Scrambling Code Allocation Parameters....................................................................84 Automatic PN Offset Allocation Parameters................................................................................85 Microwave Radio Links Parameters ............................................................................................86 Macros.........................................................................................................................................88 Other Configuration Files........................................................................................................................88 Print Setup Configuration ..................................................................................................................89 Table Import/Export Configuration ....................................................................................................90 Coverage Prediction Report Configuration .......................................................................................90 CW Measurement Import Configuration............................................................................................91 Drive Test Data Import Configuration................................................................................................91 Atoll Initialisation File ..............................................................................................................................92 General Options ................................................................................................................................93 Modifying the Default Formats of Site and Transmitter Names...................................................93 Disabling Automatic Renaming of Transmitters and Cells ..........................................................94 Setting the TIF Colour Convention ..............................................................................................94 Creating an Event Viewer Log File ..............................................................................................94 Increasing the Maximum Printing Resolution ..............................................................................94 Duplicating External Path Loss Matrices with "Save As".............................................................94 Restricting the List of Predictions for Creating Sector Traffic Maps ............................................95 Displaying Path Loss Calculation Details in the Event Viewer ....................................................95 Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Files ..........................................95 Exporting Coverage Prediction Polygons in Text Format............................................................96 Defining Web Map Services Servers...........................................................................................96 Improving Point Analysis Performance .......................................................................................96 Loading Vector Files Dynamically ...............................................................................................97 Setting the Precision for the Antenna Pattern Verification at Import ...........................................97 Disabling Opening of Exported XLS Files Automatically in MS Excel.........................................97 Disallowing Creation of New Documents from Templates ..........................................................97 Blocking Access to Macros and Add-ins .....................................................................................97 Enabling Notification for Donor Transmitter Parameter Modifications.........................................97 Setting the Display Precision of Floating Point Values................................................................98 Calculation Options ...........................................................................................................................98 Setting the Antenna Patterns Modelling Method .........................................................................98 Disabling Automatic Locking of Coverage Predictions ................................................................98 Enabling Shadowing Margin in Calculations ...............................................................................98 Setting a Default Value for the Cell Edge Coverage Probability .................................................99 Enabling Indoor Coverage in Calculations ..................................................................................99 Modifying the Resolution for the LOS Area Calculation Around a Site .......................................99 Disabling the Temporary Local Storage of Path Loss Files ........................................................99 Embedding Path Losses in New Documents ..............................................................................99 AT281_AM_E1 © Forsk 2009 Table of Contents 3.3.2.9 3.3.2.10 3.3.2.11 3.3.2.12 3.3.2.13 3.3.2.14 3.3.2.15 3.3.2.16 3.3.2.17 3.3.2.18 3.3.2.19 3.3.2.20 3.3.2.21 3.3.2.22 3.3.2.23 3.3.2.24 3.3.2.25 3.3.3 3.3.3.1 3.3.3.2 3.3.3.3 3.3.3.4 3.3.3.5 3.3.3.6 3.3.3.7 3.3.3.8 3.3.4 3.3.4.1 3.3.4.2 3.3.4.3 3.3.5 3.3.5.1 3.3.5.2 3.3.5.3 3.3.6 3.3.6.1 3.3.6.2 3.3.6.3 3.3.6.4 3.3.6.5 3.3.6.6 3.3.6.7 3.3.6.8 3.3.7 3.3.7.1 3.3.7.2 3.3.7.3 3.3.7.4 3.3.7.5 3.3.7.6 3.3.7.7 3.3.7.8 3.3.7.9 3.3.7.10 3.3.7.11 3.3.8 3.3.8.1 3.3.8.2 3.3.8.3 3.3.8.4 3.3.8.5 3.3.8.6 3.3.8.7 3.3.8.8 3.3.8.9 3.3.8.10 3.3.8.11 3.3.8.12 © Forsk 2009 Stopping Calculations on Error ................................................................................................. 100 Warning About Prediction Vailidity When Display Options are Modified .................................. 100 Reading Exact Transmitter Altitudes From the DTM ................................................................ 100 Setting a Common Display Resolution For All Coverage Predictions ...................................... 100 Setting Coverage Prediction Report Resolution For Population Maps ..................................... 101 Deleting Private Path Losses When Shared Path Losses are Valid......................................... 101 Calculating Neighbour Importance Based on Distance ............................................................ 101 Setting the Priorities for GUI and Calculations ......................................................................... 101 Setting the Number of Parallel Processors and Threads.......................................................... 101 Disabling Parallel Calculation of Monte Carlo Simulations ....................................................... 102 Performing Calculations in Read-Only Documents .................................................................. 102 Identifying Transmitter, Repeater, and Remote Antenna Coverage Areas .............................. 102 Changing the Rounding Method Used for Profile Extraction .................................................... 103 Estimating Required and Used Memory Size for UMTS Simulations ....................................... 103 Co-Planning: Calculating Predictions in the Current Document Only....................................... 103 Co-Planning: Calculating Predictions in Serial or in Parallel .................................................... 103 Co-Planning: Linking the Sites Folder ...................................................................................... 103 GUI Options.................................................................................................................................... 104 Defining the Parameters for the Default Sites Symbol ............................................................. 104 Refreshing the Display Automatically When a New Station is Dropped ................................... 104 Hiding Information Displayed in the Status Bar ........................................................................ 104 Displaying Date and Time in the Event Viewer......................................................................... 104 Disabling Automatic Resizing of Windows................................................................................ 104 Setting the Maximum Number of Lines in Coverage Prediction Tool Tips ............................... 105 Changing the Display for Downlink Smart Antenna Results..................................................... 105 Displaying Coverage Prediction Comments in the Legend Window......................................... 105 Distributed Calculation Server Options .......................................................................................... 105 Detecting and Listing Distributed Calculation Servers.............................................................. 105 Setting the Distributed Calculation Server Priority.................................................................... 105 Modifying the Default Detection Time-Out................................................................................ 106 License Management Options........................................................................................................ 106 Setting an Alarm for the License End Date............................................................................... 106 Blocking Access to Certain Modules ........................................................................................ 106 Changing the NetHASP License Manager Idle Time Setting ................................................... 107 Database Options........................................................................................................................... 107 Running the Database Integrity Checking After Refresh .......................................................... 107 Setting an Automatic Database Integrity Check at Open or Refresh........................................ 108 Modifying the Default Database Connection Timeout .............................................................. 108 Making Atoll Case-Sensitive for Database Import From Planet................................................ 108 Setting the Sign for KClutter When Importing Data From Planet EV........................................ 108 Removing Database Modifications History ............................................................................... 108 Enabling/Disabling Password Prompt at Archive...................................................................... 108 Archiving Data to Databases Using Transactions .................................................................... 109 GSM Options.................................................................................................................................. 109 Considering Overlapping Zones for IM Calculation Based on Traffic ....................................... 109 Setting the Default BSIC Format .............................................................................................. 109 Selecting the Interference Matrices Used During the AFP ....................................................... 109 Checking Database Consistency Automatically ....................................................................... 110 Disabling the Maximum Range Parameter ............................................................................... 110 Enabling the Support for Multi-band Transmitters .................................................................... 110 Setting the Best Server Calculation Method in Same Priority HCS Layers .............................. 110 Hiding Advanced AFP Parameters ........................................................................................... 111 Making Redundant Fields in the Transmitters Table Read-only............................................... 111 Setting the Transmission Diversity Gain................................................................................... 111 Adding Grouped HCS Servers Option in Calculations.............................................................. 111 UMTS and CDMA2000 Options ..................................................................................................... 111 Suppressing Cell Name Carrier Suffixes .................................................................................. 111 Enabling Shadowing Margin Calculation for Ec/I0.................................................................... 112 Using Poisson Distribution in Monte-Carlo Simulations............................................................ 112 Calculating and Displaying Peak or Instantaneous HSDPA Throughput.................................. 112 Setting the Power to Use for Intra-cell Interference in HSDPA................................................. 112 Enabling Coverage Predictions of Connection Probabilities..................................................... 113 Setting the Calculation Method for HS-PDSCH CQI ................................................................ 113 Enabling Orthogonality Factor in Pilot EC/NT Calcaultion in HSDPA....................................... 113 Setting the Maximum Number of Rejections for Mobiles.......................................................... 113 Setting the Maximum Number of Rejections for HSDPA Mobiles ............................................ 113 Defining an Offset With Respect to The Thermal Noise ........................................................... 113 Setting Precision of the Rasterization Process......................................................................... 114 AT281_AM_E1 7 Administrator Manual 3.3.8.13 3.3.8.14 3.3.8.15 3.3.8.16 3.3.8.17 3.3.8.18 3.3.8.19 3.3.8.20 3.3.8.21 3.3.9 3.3.9.1 3.3.9.2 3.3.9.3 3.3.9.4 3.3.10 3.3.10.1 3.3.10.2 3.3.10.3 3.3.10.4 3.3.10.5 3.3.11 3.3.11.1 3.3.11.2 3.4 3.4.1 3.4.2 3.4.2.1 3.4.2.2 3.4.2.3 3.4.2.4 3.4.2.5 3.4.2.6 3.4.2.7 3.4.2.7.1 3.4.2.7.2 3.4.2.8 3.4.2.9 3.4.2.10 3.4.2.11 3.4.3 3.4.3.1 3.4.3.2 3.4.3.3 3.4.3.4 3.4.3.5 3.4.3.5.1 3.4.3.5.2 3.4.3.6 3.4.3.7 3.4.3.8 3.4.3.9 3.4.3.10 3.4.3.11 3.4.4 3.4.4.1 3.5 3.5.1 3.5.2 3.5.3 4 4.1 4.2 4.2.1 4.2.2 4.2.3 4.3 4.3.1 8 Defining the Number of Iterations Before Downgrading ............................................................115 Adjusting the Working of the Proportional Fair Scheduler.........................................................115 Displaying Ec/I0 of Rejected Mobiles in Simulation Results .....................................................115 Switching Back to the Old Best Server Determination Method .................................................115 Displaying Automatic Allocation Cost Values ............................................................................115 Selecting SC and PN Offset Allocation Strategies Available in the GUI ...................................115 Defining a Fixed Interval Between Scrambling Codes ..............................................................116 Compressed Mode: Restricting Inter-carrier and Inter-technology Neighbour Allocation .........116 Setting the Maximum AS Size for SC Interference Prediction ..................................................116 WiMAX and LTE Options ................................................................................................................116 Blocking Access to IEEE Parameters in WiMAX.......................................................................116 Using Only Bearers Common Between the Terminal’s and Cell’s Equipment ..........................117 Ignoring Inter-Neighbour Preamble Index Collision...................................................................117 Ignoring Inter-Neighbour Physical Cell ID Collision...................................................................117 Measurement Options.....................................................................................................................117 Displaying Additional Information in Drive Test Data ................................................................117 Setting the Number of Transmitters per Drive Test Data Path ..................................................118 Recalculating Distances of Points From There Serving Cells at Import ....................................118 Defining the BCCH and BSIC Columns for FMT Import............................................................118 Importing Drive Test Data with Scrambling Codes as Integers .................................................118 Other Options..................................................................................................................................118 Best Signals Export for Active Transmitters Only......................................................................118 Best Signals Export for Transmitters, Repeaters, and Remote Antennas ................................119 The ACP Initialisation File.....................................................................................................................119 Managing Preferences ....................................................................................................................119 GUI-Related Preferences................................................................................................................119 Default Values on the General Tab ...........................................................................................119 Default Values on the Objectives Tab .......................................................................................120 Default Values on the Reconfiguration Tab...............................................................................121 Activating Support for Volcano Propagation Models .................................................................122 Default Values on the Antennas Tab.........................................................................................122 Displaying Custom Site and Antenna Fields .............................................................................122 Defining the Appearance of the Optimisation Dialogue.............................................................123 Defining the Colours in the Quality Analysis Maps ..............................................................123 Other Components of the Optimisation Dialogue ................................................................124 Defining the Appearance of New Maps .....................................................................................125 Defining the Functionality of the Commit Tab ...........................................................................125 Defining the Appearance of the Overlay Window......................................................................125 Exporting Optimisation Results in XML .....................................................................................125 The Core ACP Engine Settings.......................................................................................................126 Log File Settings........................................................................................................................126 Configuration File Settings ........................................................................................................126 Calculation Thread Pool Settings ..............................................................................................126 Memory Management Settings .................................................................................................126 RSCP and Macro Diversity Gain Calculation Options ...............................................................127 Signal Level .........................................................................................................................127 Macro Diversity Gain (UMTS Only) .....................................................................................127 Determining Transmitter Altitude...............................................................................................127 Balancing Speed, Memory Use, and Accuracy in Calculations.................................................127 Extracted Traffic Settings ..........................................................................................................128 Accessing Raster Data..............................................................................................................129 Accessing Path Loss Matrices ..................................................................................................129 Specific WiMAX Parameters .....................................................................................................129 Miscellaneous Configuration Settings .............................................................................................129 Validity of Coverage Predictions ...............................................................................................129 XML Studies File...................................................................................................................................130 Creating an XML Studies file...........................................................................................................130 Using an XML Studies file ...............................................................................................................130 XML Studies File Example ..............................................................................................................130 Atoll Management Console............................................................135 Introduction ...........................................................................................................................................135 Atoll Management Console Installation ................................................................................................135 Installation Requirements................................................................................................................135 Installation Procedure .....................................................................................................................135 Uninstalling the Atoll Management Console ...................................................................................137 Working With the Atoll Management Console ......................................................................................137 Running the Atoll Management Console.........................................................................................137 AT281_AM_E1 © Forsk 2009 Table of Contents 4.3.2 4.3.3 4.3.3.1 4.3.3.2 4.3.4 4.3.4.1 4.3.4.2 4.3.4.3 4.3.5 4.3.6 4.3.7 4.3.7.1 4.3.7.2 4.3.8 4.3.8.1 4.3.8.2 4.3.8.3 4.3.8.4 5 5.1 5.1.1 5.1.1.1 5.1.1.2 5.1.1.3 5.1.1.3.1 5.1.1.3.2 5.1.1.3.3 5.1.1.4 5.1.1.5 5.1.1.6 5.1.1.7 5.1.1.8 5.1.1.9 5.1.2 5.1.2.1 5.1.2.2 6 6.1 6.1.1 6.1.2 6.1.3 6.1.3.1 6.1.3.2 6.1.3.3 6.1.3.4 6.1.3.5 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.3.3 6.4 6.4.1 6.4.2 6.4.3 6.5 6.6 6.6.1 6.6.2 6.6.3 © Forsk 2009 Atoll Management Console Environment ....................................................................................... 138 Working With Master Databases.................................................................................................... 139 Creating New Master Databases.............................................................................................. 139 Archiving Changes in Master Databases.................................................................................. 141 Working With Project Databases.................................................................................................... 142 Project Databases .................................................................................................................... 142 Creating Project Databases...................................................................................................... 143 Refreshing Project Databases .................................................................................................. 145 Upgrading Databases..................................................................................................................... 146 Managing Administration File Paths ............................................................................................... 147 Managing User Accounts and Access Rights ................................................................................ 151 Defining Database and Interface Access Rights ...................................................................... 152 Creating and Editing User Accounts......................................................................................... 153 Managing the History of Data Modifications ................................................................................... 154 Setting Up the History Management......................................................................................... 154 Enabling and Disabling History Management for Tables.......................................................... 155 Repairing After a Database Structure Modification or Upgrade................................................ 155 Purging Old History Information................................................................................................ 155 Radio Data Import ......................................................................... 159 Migration From Planet 2.8 Databases.................................................................................................. 159 Prerequisites for Data Import From Planet ..................................................................................... 159 Geographic and Text Data........................................................................................................ 159 Radio Antennas ........................................................................................................................ 159 Microwave Antennas ................................................................................................................ 160 Description of Planet Microwave Antennas......................................................................... 160 Description of Atoll Microwave Antennas............................................................................ 160 Conversion From Planet to Atoll ......................................................................................... 160 Sites and Transmitters.............................................................................................................. 161 Carriers ..................................................................................................................................... 161 Neighbours ............................................................................................................................... 161 Propagation Models.................................................................................................................. 161 Path Loss Matrices ................................................................................................................... 162 CW Measurements ................................................................................................................... 162 Importing Data From a Planet Database........................................................................................ 162 Importing CW Measurements From a Planet Database ........................................................... 163 Importing Microwave Antennas From a Planet Database ........................................................ 163 Administration and Usage Recommendations .............................. 167 Recommendations on Network Architecture........................................................................................ 167 Network Architecture ...................................................................................................................... 167 Network Dimensioning ................................................................................................................... 168 System Dimensioning..................................................................................................................... 168 Recommended File Server Configuration................................................................................. 168 Recommended Floating Licence Server Configuration ............................................................ 168 Recommended Citrix Server Configuration .............................................................................. 168 Recommended Database Server Configuration ....................................................................... 168 Recommended Workstation Configuration ............................................................................... 169 Recommendations on Installation ........................................................................................................ 169 Microsoft Windows Updates........................................................................................................... 169 Citrix MetaFrame Installation.......................................................................................................... 169 Atoll Installation .............................................................................................................................. 169 Licence Manager Installation.......................................................................................................... 170 Distributed Calculation Server Installation...................................................................................... 170 Recommendations on Geographic Data .............................................................................................. 170 Location of the Geographic Data.................................................................................................... 170 Size of Tiles.................................................................................................................................... 171 Recommended Formats ................................................................................................................. 171 Recommendations on Path Loss Management ................................................................................... 171 Shared and Private Path Loss Matrices ......................................................................................... 171 Link or Embed ................................................................................................................................ 171 Setting Up Efficient Shared Path Loss Matrices Folders................................................................ 172 Recommendation on Defining Paths to Linked Files ........................................................................... 173 Recommendations on Database Usage .............................................................................................. 174 Database Upgrades ....................................................................................................................... 174 Import From Planet......................................................................................................................... 174 Oracle Client Version ..................................................................................................................... 174 AT281_AM_E1 9 Administrator Manual 6.6.4 6.6.4.1 6.6.5 6.7 6.7.1 6.7.1.1 6.7.1.2 6.8 6.9 6.9.1 6.9.1.1 6.9.1.2 6.9.1.3 6.9.2 6.9.3 6.9.4 6.9.5 6.9.6 6.9.7 6.9.8 6.10 6.10.1 6.11 6.11.1 6.11.1.1 6.11.1.2 6.11.1.3 6.11.1.4 6.11.1.5 6.11.2 6.11.2.1 6.11.2.2 6.11.3 7 7.1 7.1.1 7.1.2 7.1.2.1 7.1.2.2 7.1.3 7.1.3.1 7.1.3.2 7.1.3.3 7.2 7.2.1 7.2.1.1 7.2.1.2 7.2.1.3 7.2.1.4 7.2.1.5 7.2.1.6 7.2.2 7.2.2.1 7.2.2.2 7.2.2.3 7.2.2.4 7.2.2.5 7.2.2.6 7.2.2.7 7.2.2.8 7.2.2.9 7.2.2.10 7.2.2.11 7.2.3 7.2.3.1 7.2.3.2 7.2.3.3 10 Tables and Fields............................................................................................................................174 User-Defined Fields and Default Values ...................................................................................174 Regionalisation................................................................................................................................174 Recommendations on Calculation Management ..................................................................................175 Computation Server Stability and Resource Management .............................................................175 Causes of Instability and Loss of Performance .........................................................................175 Troubleshooting and Solution....................................................................................................175 Recommendations on Atoll Administration Files ..................................................................................176 Recommendations on Atoll Usage .......................................................................................................177 Performance and Memory Issues ...................................................................................................177 Performance and Memory Issues in Large GSM Projects ........................................................178 Performance and Memory Issues in UMTS/CDMA Simulations ...............................................179 Performance and Memory Issues in Co-planning Projects .......................................................179 Printing ............................................................................................................................................179 Coverage Predictions......................................................................................................................179 CW Measurements and Drive Test Data ........................................................................................179 Path Loss Matrices..........................................................................................................................180 Antenna Patterns and Electrical Downtilts ......................................................................................180 Antenna Import................................................................................................................................180 Traffic Maps ....................................................................................................................................180 Recommendations on the Atoll API ......................................................................................................180 Using Atoll Through the API............................................................................................................180 Appendix: Memory Requirements ........................................................................................................180 Disk Space Requirements...............................................................................................................181 Network-Wide Input ...................................................................................................................181 Cell-Specific Results .................................................................................................................181 Network-Wide Output ................................................................................................................181 Temporary Disk Space..............................................................................................................181 Other Disk Space Requirements ...............................................................................................182 RAM Requirements.........................................................................................................................182 UMTS Simulations.....................................................................................................................182 Coverage Predictions ................................................................................................................183 Process Memory .............................................................................................................................183 Compatibility Between Versions 2.7 and 2.8 .................................187 Upgrading From 2.7 to 2.8....................................................................................................................187 Important Information ......................................................................................................................187 Upgrading 2.7 Databases to 2.8 .....................................................................................................187 Recommendations ....................................................................................................................187 Manual Database Upgrade Procedure ......................................................................................188 Upgrading 2.7.x Documents to 2.8..................................................................................................188 Upgrading Disconnected Documents ........................................................................................188 Upgrading Documents Connected to 2.7 Databases ................................................................188 Upgrading Documents Connected to Upgraded Databases .....................................................188 Changes in the Data Structure .............................................................................................................189 Changes in Microwave Radio Links Documents.............................................................................189 MWDefaultsCurves Table .........................................................................................................189 MWEquipments Table ...............................................................................................................189 MWLinks Table..........................................................................................................................189 MWRepeaters Table .................................................................................................................189 MWTplLinks Table.....................................................................................................................190 Other Changes ..........................................................................................................................190 Changes in GSM GPRS EGPRS Documents.................................................................................190 FrequencyBands Table .............................................................................................................190 Transmitters Table ....................................................................................................................190 TplTransmitters Table ...............................................................................................................190 TRGs Table ...............................................................................................................................190 TRXs Table ...............................................................................................................................191 EGPRSCodingSchemes Table .................................................................................................191 EGPRSQuality Table.................................................................................................................191 EGPRSServices Table ..............................................................................................................191 EGPRSTerminals Table ............................................................................................................191 InterNetChProtect Table............................................................................................................192 Other Changes ..........................................................................................................................192 Changes in UMTS HSPA Documents.............................................................................................192 Networks Table .........................................................................................................................192 Sites Table ................................................................................................................................192 Transmitters Table ....................................................................................................................192 AT281_AM_E1 © Forsk 2009 Table of Contents 7.2.3.4 7.2.3.5 7.2.3.6 7.2.3.7 7.2.3.8 7.2.3.9 7.2.3.10 7.2.3.11 7.2.3.12 7.2.3.13 7.2.3.14 7.2.3.15 7.2.3.16 7.2.3.17 7.2.4 7.2.4.1 7.2.4.2 7.2.4.3 7.2.4.4 7.2.4.5 7.2.4.6 7.2.4.7 7.2.5 7.2.5.1 7.2.5.2 7.2.5.3 7.2.5.4 7.2.5.5 7.2.5.6 7.2.5.7 7.2.5.8 7.2.6 7.2.6.1 7.2.6.2 7.2.6.3 7.2.6.4 7.2.6.5 7.2.6.6 7.2.6.7 7.3 7.3.1 7.3.1.1 7.3.1.1.1 7.3.1.1.2 7.3.1.2 7.3.1.2.1 7.3.1.3 7.3.1.3.1 7.3.2 7.3.2.1 7.3.2.1.1 7.3.2.1.2 7.3.2.2 7.3.2.2.1 7.3.3 7.3.3.1 7.3.3.1.1 7.3.4 7.3.4.1 7.3.4.1.1 7.3.4.1.2 7.3.4.2 7.3.4.2.1 8 8.1 8.2 8.2.1 © Forsk 2009 TplTransmitters Table............................................................................................................... 192 CDMACells Table ..................................................................................................................... 193 CDMAEquipments Table .......................................................................................................... 193 CDMAEquipmentsCEsUse Table ............................................................................................. 193 CDMAEqptsHSUPARssUse Table ........................................................................................... 193 UMTSServices Table................................................................................................................ 193 HSDPABearers Table............................................................................................................... 194 HSUPABearers Table............................................................................................................... 194 UMTSTerminals Table.............................................................................................................. 194 UECategories Table ................................................................................................................. 194 HSUPAUECategories Table ..................................................................................................... 194 HSPAMIMOConfigs Table ........................................................................................................ 194 InterNetChProtect Table ........................................................................................................... 195 Other Changes ......................................................................................................................... 195 Changes in CDMA2000 1xRTT 1xEV-DO Documents .................................................................. 195 Networks Table......................................................................................................................... 195 TplTransmitters Table............................................................................................................... 195 CDMACells Table ..................................................................................................................... 195 UMTSServicesQuality Table..................................................................................................... 195 UMTSTerminals Table.............................................................................................................. 196 InterNetChProtect Table ........................................................................................................... 196 Other Changes ......................................................................................................................... 196 Changes in TD-SCDMA Documents .............................................................................................. 196 Transmitters Table.................................................................................................................... 196 TplTransmitters Table............................................................................................................... 196 CDMACells Table ..................................................................................................................... 196 CDMAEquipments Table .......................................................................................................... 197 CodesRelativityClusters Table.................................................................................................. 197 UMTSServices Table................................................................................................................ 197 InterNetChProtect Table ........................................................................................................... 197 Other Changes ......................................................................................................................... 197 Changes in WiMAX BWA Documents............................................................................................ 197 Networks Table......................................................................................................................... 197 Schedulers Table...................................................................................................................... 198 TplTransmitters Table............................................................................................................... 198 WCells Table ............................................................................................................................ 198 WMimoConfigs Table ............................................................................................................... 198 InterNetChProtect Table ........................................................................................................... 199 Other Changes ......................................................................................................................... 199 Data Structure Changes for Activating Optional Features ................................................................... 199 Optional Features in GSM GPRS EGPRS Documents.................................................................. 199 Intermodulation Interference Modelling .................................................................................... 199 Transmitters Table .............................................................................................................. 199 Networks Table ................................................................................................................... 200 Frequency Diversity Gain Modelling ......................................................................................... 200 CodecQualityTables and EGPRSQuality Tables ................................................................ 200 Additional Indoor Loss Modelling.............................................................................................. 200 FrequencyBands Table ....................................................................................................... 200 Optional Features in UMTS HSPA Documents .............................................................................. 200 MBMS Modelling....................................................................................................................... 200 CDMACells and TplTransmitters Tables............................................................................. 200 UMTSMobility Table............................................................................................................ 200 Additional Indoor Loss Modelling.............................................................................................. 201 FrequencyBands Table ....................................................................................................... 201 Optional Features in CDMA2000 1xRTT 1xEV-DO Documents .................................................... 201 Additional Indoor Loss Modelling.............................................................................................. 201 FrequencyBands Table ....................................................................................................... 201 Optional Features in TD-SCDMA Documents ................................................................................ 201 MBMS Modelling....................................................................................................................... 201 CDMACells and TplTransmitters Tables............................................................................. 201 UMTSMobility Table............................................................................................................ 202 Additional Indoor Loss Modelling.............................................................................................. 202 FrequencyBands Table ....................................................................................................... 202 Database Structure ....................................................................... 205 Overview .............................................................................................................................................. 205 Microwave Radio Links Template ........................................................................................................ 206 Microwave Radio Links Tables....................................................................................................... 207 AT281_AM_E1 11 Administrator Manual 8.2.1.1 8.2.1.2 8.2.1.3 8.2.1.4 8.2.1.5 8.2.1.6 8.2.1.7 8.2.1.7.1 8.2.1.7.2 8.2.1.8 8.2.1.9 8.2.1.10 8.2.1.11 8.2.1.12 8.2.1.13 8.2.1.14 8.2.1.15 8.2.1.16 8.2.1.17 8.2.1.18 8.2.1.19 8.2.1.20 8.2.1.21 8.2.1.22 8.2.1.23 8.2.1.24 8.2.1.25 8.2.1.26 8.2.1.27 8.2.1.28 8.2.1.29 8.3 8.3.1 8.3.1.1 8.3.1.2 8.3.1.3 8.3.1.4 8.3.1.5 8.3.1.6 8.3.1.7 8.3.1.7.1 8.3.1.7.2 8.3.1.8 8.3.1.8.1 8.3.1.8.2 8.3.1.9 8.3.1.10 8.3.1.11 8.3.1.12 8.3.1.13 8.3.1.14 8.3.1.15 8.3.1.16 8.3.1.16.1 8.3.1.16.2 8.3.1.16.3 8.3.1.17 8.3.1.17.1 8.3.1.17.2 8.3.1.17.3 8.3.1.17.4 8.3.1.18 8.3.1.19 8.3.1.20 8.3.1.21 8.3.1.22 8.3.1.22.1 8.3.1.22.2 12 PropagationModels Table .........................................................................................................207 CustomFields Table ..................................................................................................................207 CoordSys Table.........................................................................................................................207 Units Table ................................................................................................................................208 Networks Table .........................................................................................................................208 Sites Table ................................................................................................................................209 Site List Management Tables ....................................................................................................209 SitesListsNames Table ........................................................................................................209 SitesLists Table ...................................................................................................................209 MWAntennas Table...................................................................................................................209 MWBands Table........................................................................................................................210 MWBERCurves Table ...............................................................................................................210 MWCompatibilities Table...........................................................................................................210 MWCompatibilitiesGuides Table ...............................................................................................210 MWDefaultsCurves Table .........................................................................................................210 MWEPO Table ..........................................................................................................................211 MWEPOLinkClass Table ...........................................................................................................211 MWEquipments Table ...............................................................................................................211 MWGuides Table.......................................................................................................................213 MWIrfs Table .............................................................................................................................213 MWLinks Table..........................................................................................................................214 MWLinksTypes Table................................................................................................................217 MWManufacturers Table ...........................................................................................................217 MWMultiHops Table ..................................................................................................................217 MWMultiHopsLinks Table..........................................................................................................217 MWRepeaters Table .................................................................................................................217 MWSubbands Table ..................................................................................................................218 MWTplLinks Table.....................................................................................................................218 MWHubs Table..........................................................................................................................220 MWPMP Table ..........................................................................................................................220 MWPorts Table..........................................................................................................................221 GSM GPRS EGPRS Template.............................................................................................................222 GSM GPRS EGPRS Tables ...........................................................................................................225 PropagationModels Table .........................................................................................................225 CustomFields Table ..................................................................................................................225 CoordSys Table.........................................................................................................................225 Units Table ................................................................................................................................226 Networks Table .........................................................................................................................226 Sites Table ................................................................................................................................227 Site List Management Tables ....................................................................................................227 SitesListsNames Table ........................................................................................................227 SitesLists Table ...................................................................................................................227 Transmitter List Management Tables ........................................................................................227 TxsListsNames Table ..........................................................................................................227 TxsLists Table......................................................................................................................227 Antennas Table .........................................................................................................................228 SecondaryAntennas Table ........................................................................................................228 Antenna List Management Tables.............................................................................................229 AntennasListsNames Table ......................................................................................................229 AntennasLists Table ..................................................................................................................229 FrequencyBands Table .............................................................................................................229 Receivers Table ........................................................................................................................229 Equipment Management Tables ...............................................................................................229 TMAEquipments Table ........................................................................................................229 FeederEquipments Table ....................................................................................................230 BTSEquipments Table.........................................................................................................230 Neighbour Management Tables ................................................................................................230 Neighbours Table ................................................................................................................230 NeighboursExt Table ...........................................................................................................230 NeighboursConstraints Table ..............................................................................................231 NeighboursConstraintsExt Table .........................................................................................231 Transmitters Table ....................................................................................................................231 TplTransmitters Table ...............................................................................................................234 Repeaters Table........................................................................................................................235 RepeaterEquipments Table.......................................................................................................235 Resource Management Tables .................................................................................................236 FrequencyDomains Table....................................................................................................236 FrequencyGroups Table ......................................................................................................236 AT281_AM_E1 © Forsk 2009 Table of Contents 8.3.1.22.3 8.3.1.22.4 8.3.1.22.5 8.3.1.22.6 8.3.1.23 8.3.1.24 8.3.1.25 8.3.1.26 8.3.1.27 8.3.1.28 8.3.1.29 8.3.1.30 8.3.1.31 8.3.1.32 8.3.1.33 8.3.1.34 8.3.1.35 8.3.1.36 8.3.1.37 8.3.1.38 8.3.1.39 8.3.1.40 8.3.1.40.1 8.3.1.40.2 8.3.1.40.3 8.3.1.40.4 8.3.1.40.5 8.3.1.40.6 8.3.1.40.7 8.3.1.41 8.3.1.42 8.3.1.42.1 8.3.1.42.2 8.3.1.42.3 8.3.1.43 8.3.1.44 8.3.1.45 8.4 8.4.1 8.4.1.1 8.4.1.2 8.4.1.3 8.4.1.4 8.4.1.5 8.4.1.6 8.4.1.7 8.4.1.7.1 8.4.1.7.2 8.4.1.8 8.4.1.8.1 8.4.1.8.2 8.4.1.9 8.4.1.10 8.4.1.11 8.4.1.11.1 8.4.1.11.2 8.4.1.12 8.4.1.13 8.4.1.14 8.4.1.14.1 8.4.1.14.2 8.4.1.14.3 8.4.1.15 8.4.1.15.1 8.4.1.15.2 8.4.1.15.3 8.4.1.15.4 8.4.1.16 © Forsk 2009 BSICDomains Table ........................................................................................................... 236 BSICGroups Table .............................................................................................................. 237 HSNDomains Table ............................................................................................................ 237 HSNGroups Table............................................................................................................... 237 Layers Table ............................................................................................................................. 237 TRXTypes Table....................................................................................................................... 238 TRXEquipments Table.............................................................................................................. 238 CellTypes Table........................................................................................................................ 238 TRGConfigurations Table ......................................................................................................... 238 TRGs Table .............................................................................................................................. 239 TRXs Table............................................................................................................................... 240 Separations Table..................................................................................................................... 241 SeparationRules Table ............................................................................................................. 241 TSConfigurationNames Table .................................................................................................. 241 TSConfigurations Table ............................................................................................................ 241 EGPRSCodingSchemes Table................................................................................................. 242 EGPRSEquipments Table ........................................................................................................ 242 EGPRSQuality Table ................................................................................................................ 242 EGPRSDimensioningModel Table............................................................................................ 243 EGPRSServiceQuality Table .................................................................................................... 243 QualityIndicators Table ............................................................................................................. 243 Multi-Service Traffic Management Tables ................................................................................ 243 EGPRSEnvironmentDefs Table .......................................................................................... 243 EGPRSMobility Table ......................................................................................................... 244 EGPRSServices Table........................................................................................................ 244 EGPRSServicesUsage Table ............................................................................................. 244 EGPRSTerminals Table...................................................................................................... 244 EGPRSTrafficEnvironments Table...................................................................................... 245 EGPRSUserProfiles Table .................................................................................................. 245 CodecModes Table................................................................................................................... 245 CodecEquipments, CodecModeAdaptations and CodecQualityTables Tables........................ 245 CodecEquipments Table..................................................................................................... 245 CodecModeAdaptations Table............................................................................................ 246 CodecQualityTables Table.................................................................................................. 246 ChannelModels Table............................................................................................................... 246 AfpModels Table....................................................................................................................... 246 InterNetChProtect Table ........................................................................................................... 247 UMTS HSPA Template ........................................................................................................................ 248 UMTS HSPA Tables....................................................................................................................... 250 PropagationModels Table......................................................................................................... 250 CustomFields Table.................................................................................................................. 251 CoordSys Table ........................................................................................................................ 251 Units Table................................................................................................................................ 252 Networks Table......................................................................................................................... 252 Sites Table................................................................................................................................ 253 Site List Management Tables ................................................................................................... 254 SitesListsNames Table ....................................................................................................... 254 SitesLists Table................................................................................................................... 254 Transmitter List Management Tables ....................................................................................... 254 TxsListsNames Table.......................................................................................................... 254 TxsLists Table ..................................................................................................................... 254 Antennas Table......................................................................................................................... 254 SecondaryAntennas Table ....................................................................................................... 255 Antenna List Management Tables ............................................................................................ 255 AntennasListsNames Table ................................................................................................ 255 AntennasLists Table ........................................................................................................... 255 FrequencyBands Table............................................................................................................. 255 Receivers Table........................................................................................................................ 256 Equipment Management Tables............................................................................................... 256 TMAEquipments Table ....................................................................................................... 256 FeederEquipments Table.................................................................................................... 256 BTSEquipments Table ........................................................................................................ 256 Neighbour Management Tables ............................................................................................... 257 Neighbours Table................................................................................................................ 257 NeighboursExt Table .......................................................................................................... 257 NeighboursConstraints Table.............................................................................................. 257 NeighboursConstraintsExt Table ........................................................................................ 258 Transmitters Table.................................................................................................................... 258 AT281_AM_E1 13 Administrator Manual 8.4.1.17 8.4.1.18 8.4.1.19 8.4.1.20 8.4.1.20.1 8.4.1.20.2 8.4.1.20.3 8.4.1.21 8.4.1.22 8.4.1.23 8.4.1.24 8.4.1.25 8.4.1.25.1 8.4.1.25.2 8.4.1.25.3 8.4.1.25.4 8.4.1.25.5 8.4.1.25.6 8.4.1.25.7 8.4.1.25.8 8.4.1.25.9 8.4.1.25.10 8.4.1.25.11 8.4.1.26 8.4.1.27 8.4.1.28 8.4.1.29 8.4.1.30 8.4.1.31 8.4.1.32 8.4.1.33 8.5 8.5.1 8.5.1.1 8.5.1.2 8.5.1.3 8.5.1.4 8.5.1.5 8.5.1.6 8.5.1.7 8.5.1.7.1 8.5.1.7.2 8.5.1.8 8.5.1.8.1 8.5.1.8.2 8.5.1.9 8.5.1.10 8.5.1.11 8.5.1.11.1 8.5.1.11.2 8.5.1.12 8.5.1.13 8.5.1.14 8.5.1.14.1 8.5.1.14.2 8.5.1.14.3 8.5.1.15 8.5.1.15.1 8.5.1.15.2 8.5.1.15.3 8.5.1.15.4 8.5.1.16 8.5.1.17 8.5.1.18 8.5.1.19 8.5.1.20 8.5.1.20.1 8.5.1.20.2 14 TplTransmitters Table ...............................................................................................................259 Repeaters Table........................................................................................................................261 RepeaterEquipments Table.......................................................................................................262 Scrambling Code Management Tables .....................................................................................262 ScramblingCodesDomains Table ........................................................................................262 ScramblingCodesGroups Table...........................................................................................262 Separations Table................................................................................................................263 CDMACells Table ......................................................................................................................263 CDMAEquipments Table ...........................................................................................................264 CDMAEquipmentsCEsUse Table..............................................................................................265 CdmaEqptsHSUPARssUse Table.............................................................................................265 Multi-Service Traffic Management.............................................................................................265 UMTSEnvironmentDefs Table .............................................................................................265 UMTSMobility Table ............................................................................................................266 UMTSServicesQuality Table................................................................................................266 UMTSServicesUsage Table ................................................................................................266 UMTSServices Table...........................................................................................................266 R99Bearers Table................................................................................................................267 HSDPA Bearers Modelling Tables.......................................................................................268 HSUPA Bearers Modelling Tables.......................................................................................269 UMTSTerminals Table.........................................................................................................269 UMTSTraficEnvironments Table..........................................................................................270 UMTSUserProfiles Table .....................................................................................................270 ServiceQualityTables Table ......................................................................................................270 QualityIndicators Table..............................................................................................................271 UERxEquipments Table ............................................................................................................271 UECategories Table ..................................................................................................................271 HSUPAUECategories Table......................................................................................................271 InterfReductionFactors Table ....................................................................................................272 HSPAMIMOConfigs Table.........................................................................................................272 InterNetChProtect Table............................................................................................................272 CDMA2000 1xRTT 1xEV-DO Template ...............................................................................................273 CDMA2000 1xRTT 1xEV-DO Tables..............................................................................................276 PropagationModels Table .........................................................................................................276 CustomFields Table ..................................................................................................................276 CoordSys Table.........................................................................................................................276 Units Table ................................................................................................................................277 Networks Table .........................................................................................................................277 Sites Table ................................................................................................................................278 Site List Management Tables ....................................................................................................278 SitesListsNames Table ........................................................................................................278 SitesLists Table ...................................................................................................................279 Transmitter List Management Tables ........................................................................................279 TxsListsNames Table ..........................................................................................................279 TxsLists Table......................................................................................................................279 Antennas Table .........................................................................................................................279 SecondaryAntennas Table ........................................................................................................280 Antenna List Management Tables.............................................................................................280 AntennasListsNames Table.................................................................................................280 AntennasLists Table ............................................................................................................280 FrequencyBands Table .............................................................................................................280 Receivers Table ........................................................................................................................280 Equipment Management Tables ...............................................................................................281 TMAEquipments Table ........................................................................................................281 FeederEquipments Table ....................................................................................................281 BTSEquipments Table.........................................................................................................281 Neighbour Management Tables ................................................................................................281 Neighbours Table ................................................................................................................281 NeighboursExt Table ...........................................................................................................282 NeighboursConstraints Table ..............................................................................................282 NeighboursConstraintsExt Table .........................................................................................282 Transmitters Table ....................................................................................................................283 TplTransmitters Table ...............................................................................................................284 Repeaters Table........................................................................................................................285 RepeaterEquipments Table.......................................................................................................286 PN Offset Management Tables .................................................................................................286 PnCodesDomains Table......................................................................................................286 PnCodesGroups Table ........................................................................................................286 AT281_AM_E1 © Forsk 2009 Table of Contents 8.5.1.20.3 8.5.1.21 8.5.1.22 8.5.1.23 8.5.1.24 8.5.1.25 8.5.1.25.1 8.5.1.25.2 8.5.1.25.3 8.5.1.25.4 8.5.1.25.5 8.5.1.25.6 8.5.1.25.7 8.5.1.25.8 8.5.1.25.9 8.5.1.26 8.5.1.27 8.5.1.28 8.5.1.29 8.5.1.30 8.6 8.6.1 8.6.1.1 8.6.1.2 8.6.1.3 8.6.1.4 8.6.1.5 8.6.1.6 8.6.1.7 8.6.1.7.1 8.6.1.7.2 8.6.1.8 8.6.1.8.1 8.6.1.8.2 8.6.1.9 8.6.1.10 8.6.1.11 8.6.1.12 8.6.1.13 8.6.1.14 8.6.1.14.1 8.6.1.14.2 8.6.1.15 8.6.1.16 8.6.1.17 8.6.1.17.1 8.6.1.17.2 8.6.1.17.3 8.6.1.18 8.6.1.18.1 8.6.1.18.2 8.6.1.18.3 8.6.1.18.4 8.6.1.19 8.6.1.20 8.6.1.21 8.6.1.22 8.6.1.23 8.6.1.23.1 8.6.1.23.2 8.6.1.23.3 8.6.1.23.4 8.6.1.24 8.6.1.25 8.6.1.26 8.6.1.27 8.6.1.28 8.6.1.28.1 © Forsk 2009 Separations Table ............................................................................................................... 287 CDMACells Table ..................................................................................................................... 287 CDMAEquipments Table .......................................................................................................... 288 CDMAEquipmentsCEsUse Table ............................................................................................. 289 CarriersType Table ................................................................................................................... 289 Multi-Service Traffic Management ............................................................................................ 289 UMTSEnvironmentDefs Table ............................................................................................ 289 UMTSMobility Table............................................................................................................ 289 UMTSServicesQuality Table ............................................................................................... 289 UMTSServicesUsage Table................................................................................................ 290 UMTSServices Table .......................................................................................................... 290 UMTSTerminals Table ........................................................................................................ 291 1xEV-DO Release A Bearers Modelling Tables.................................................................. 292 UMTSTraficEnvironments Table ......................................................................................... 294 UMTSUserProfiles Table .................................................................................................... 294 ServiceQualityTables Table...................................................................................................... 294 QualityIndicators Table ............................................................................................................. 294 UERxEquipments Table ........................................................................................................... 295 InterfReductionFactors Table ................................................................................................... 295 InterNetChProtect Table ........................................................................................................... 295 TD-SCDMA Template .......................................................................................................................... 296 TD-SCDMA Tables......................................................................................................................... 299 PropagationModels Table......................................................................................................... 299 CustomFields Table.................................................................................................................. 299 CoordSys Table ........................................................................................................................ 299 Units Table................................................................................................................................ 300 Networks Table......................................................................................................................... 300 Sites Table................................................................................................................................ 301 Site List Management Tables ................................................................................................... 302 SitesListsNames Table ....................................................................................................... 302 SitesLists Table................................................................................................................... 302 Transmitter List Management Tables ....................................................................................... 302 TxsListsNames Table.......................................................................................................... 302 TxsLists Table ..................................................................................................................... 302 Antennas Table......................................................................................................................... 302 SecondaryAntennas Table ....................................................................................................... 303 SmartAntennas Table ............................................................................................................... 303 SmartAntennasModels Table ................................................................................................... 304 SACIGainCDF Table ................................................................................................................ 304 Antenna List Management Tables ............................................................................................ 304 AntennasListsNames Table ................................................................................................ 304 AntennasLists Table ........................................................................................................... 304 FrequencyBands Table............................................................................................................. 304 Receivers Table........................................................................................................................ 305 Equipment Management Tables............................................................................................... 305 TMAEquipments Table ....................................................................................................... 305 FeederEquipments Table.................................................................................................... 305 BTSEquipments Table ........................................................................................................ 305 Neighbour Management Tables ............................................................................................... 306 Neighbours Table................................................................................................................ 306 NeighboursExt Table .......................................................................................................... 306 NeighboursConstraints Table.............................................................................................. 306 NeighboursConstraintsExt Table ........................................................................................ 307 Transmitters Table.................................................................................................................... 307 TplTransmitters Table............................................................................................................... 308 Repeaters Table ....................................................................................................................... 310 RepeaterEquipments Table ...................................................................................................... 311 Scrambling Code Management Tables .................................................................................... 311 ScramblingCodesDomains Table........................................................................................ 311 ScramblingCodesGroups Table .......................................................................................... 311 Separations Table ............................................................................................................... 312 CodesRelativityClusters Table ............................................................................................ 312 CDMACells Table ..................................................................................................................... 312 CDMACellsTS Table................................................................................................................. 313 CDMAEquipments Table .......................................................................................................... 314 CDMAEquipmentsCEsUse Table ............................................................................................. 314 Multi-Service Traffic Management ............................................................................................ 314 UMTSEnvironmentDefs Table ............................................................................................ 314 AT281_AM_E1 15 Administrator Manual 8.6.1.28.2 8.6.1.28.3 8.6.1.28.4 8.6.1.28.5 8.6.1.28.6 8.6.1.28.7 8.6.1.28.8 8.6.1.28.9 8.6.1.28.10 8.6.1.29 8.6.1.30 8.6.1.31 8.6.1.32 8.6.1.33 8.6.1.34 8.6.1.35 8.7 8.7.1 8.7.1.1 8.7.1.2 8.7.1.3 8.7.1.4 8.7.1.5 8.7.1.6 8.7.1.7 8.7.1.7.1 8.7.1.7.2 8.7.1.8 8.7.1.8.1 8.7.1.8.2 8.7.1.9 8.7.1.10 8.7.1.11 8.7.1.12 8.7.1.13 8.7.1.14 8.7.1.15 8.7.1.16 8.7.1.17 8.7.1.18 8.7.1.18.1 8.7.1.18.2 8.7.1.18.3 8.7.1.19 8.7.1.19.1 8.7.1.19.2 8.7.1.19.3 8.7.1.19.4 8.7.1.20 8.7.1.21 8.7.1.22 8.7.1.23 8.7.1.24 8.7.1.25 8.7.1.26 8.7.1.26.1 8.7.1.26.2 8.7.1.26.3 8.7.1.26.4 8.7.1.26.5 8.7.1.26.6 8.7.1.26.7 8.7.1.26.8 8.7.1.27 8.7.1.28 8.7.1.29 8.8 8.8.1 16 UMTSMobility Table ............................................................................................................314 UMTSServicesQuality Table................................................................................................315 UMTSServicesUsage Table ................................................................................................315 UMTSServices Table...........................................................................................................316 R99Bearers Table................................................................................................................317 HSDPA Bearers Modelling Tables.......................................................................................317 UMTSTerminals Table.........................................................................................................318 UMTSTraficEnvironments Table..........................................................................................318 UMTSUserProfiles Table .....................................................................................................318 ServiceQualityTables Table ......................................................................................................318 ServiceRUsUse Table ...............................................................................................................319 QualityIndicators Table..............................................................................................................319 UERxEquipments Table ............................................................................................................319 UECategories Table ..................................................................................................................319 InterfReductionFactors Table ....................................................................................................320 InterNetChProtect Table............................................................................................................320 WiMAX BWA Template.........................................................................................................................321 WiMAX BWA Tables .......................................................................................................................324 PropagationModels Table .........................................................................................................324 CustomFields Table ..................................................................................................................324 CoordSys Table.........................................................................................................................324 Units Table ................................................................................................................................325 Networks Table .........................................................................................................................325 Sites Table ................................................................................................................................326 Site List Management Tables ....................................................................................................327 SitesListsNames Table ........................................................................................................327 SitesLists Table ...................................................................................................................327 Transmitter List Management Tables ........................................................................................327 TxsListsNames Table ..........................................................................................................327 TxsLists Table......................................................................................................................327 Antennas Table .........................................................................................................................327 SecondaryAntennas Table ........................................................................................................328 SmartAntennas Table................................................................................................................328 SmartAntennasModels Table ....................................................................................................328 FrequencyBands Table .............................................................................................................329 FrameConfigurations Table (WiMAX 802.16e) .........................................................................329 PermutationZones Table (WiMAX 802.16e)..............................................................................329 Schedulers Table ......................................................................................................................330 Receivers Table ........................................................................................................................330 Equipment Management Tables ...............................................................................................331 TMAEquipments Table ........................................................................................................331 FeederEquipments Table ....................................................................................................331 BTSEquipments Table.........................................................................................................331 Neighbour Management Tables (WiMAX 802.16e)...................................................................331 Neighbours Table ................................................................................................................331 NeighboursExt Table ...........................................................................................................332 NeighboursConstraints Table ..............................................................................................332 NeighboursConstraintsExt Table .........................................................................................332 Transmitters Table ....................................................................................................................333 TplTransmitters Table ...............................................................................................................334 WCells Table .............................................................................................................................335 WEquipments Table ..................................................................................................................336 WBearerQualityCurves Table....................................................................................................337 WBearersRequiredCI Table ......................................................................................................337 Multi-Service Traffic Management.............................................................................................337 WEnvironmentDefs Table....................................................................................................337 WMobility Table ...................................................................................................................337 WServicesUsage Table .......................................................................................................337 WServices Table..................................................................................................................338 WBearers Table...................................................................................................................339 WTerminals Table................................................................................................................339 WTraficEnvironments Table ................................................................................................340 WUserProfiles Table............................................................................................................340 QualityIndicators Table..............................................................................................................340 WMimoConfigs Table ................................................................................................................340 InterNetChProtect Table............................................................................................................340 LTE Template .......................................................................................................................................342 LTE Tables......................................................................................................................................345 AT281_AM_E1 © Forsk 2009 Table of Contents 8.8.1.1 8.8.1.2 8.8.1.3 8.8.1.4 8.8.1.5 8.8.1.6 8.8.1.7 8.8.1.7.1 8.8.1.7.2 8.8.1.8 8.8.1.8.1 8.8.1.8.2 8.8.1.9 8.8.1.10 8.8.1.11 8.8.1.12 8.8.1.13 8.8.1.14 8.8.1.15 8.8.1.16 8.8.1.16.1 8.8.1.16.2 8.8.1.16.3 8.8.1.17 8.8.1.17.1 8.8.1.17.2 8.8.1.17.3 8.8.1.17.4 8.8.1.18 8.8.1.19 8.8.1.20 8.8.1.21 8.8.1.22 8.8.1.23 8.8.1.24 8.8.1.24.1 8.8.1.24.2 8.8.1.24.3 8.8.1.24.4 8.8.1.24.5 8.8.1.24.6 8.8.1.24.7 8.8.1.24.8 8.8.1.25 8.8.1.26 8.8.1.27 © Forsk 2009 PropagationModels Table......................................................................................................... 345 CustomFields Table.................................................................................................................. 345 CoordSys Table ........................................................................................................................ 345 Units Table................................................................................................................................ 346 Networks Table......................................................................................................................... 346 Sites Table................................................................................................................................ 347 Site List Management Tables ................................................................................................... 347 SitesListsNames Table ....................................................................................................... 347 SitesLists Table................................................................................................................... 347 Transmitter List Management Tables ....................................................................................... 348 TxsListsNames Table.......................................................................................................... 348 TxsLists Table ..................................................................................................................... 348 Antennas Table......................................................................................................................... 348 SecondaryAntennas Table ....................................................................................................... 349 SmartAntennas Table ............................................................................................................... 349 SmartAntennasModels Table ................................................................................................... 349 FrequencyBands Table............................................................................................................. 349 Schedulers Table...................................................................................................................... 350 Receivers Table........................................................................................................................ 350 Equipment Management Tables............................................................................................... 350 TMAEquipments Table ....................................................................................................... 350 FeederEquipments Table.................................................................................................... 351 BTSEquipments Table ........................................................................................................ 351 Neighbour Management Tables ............................................................................................... 351 Neighbours Table................................................................................................................ 351 NeighboursExt Table .......................................................................................................... 351 NeighboursConstraints Table.............................................................................................. 352 NeighboursConstraintsExt Table ........................................................................................ 352 Transmitters Table.................................................................................................................... 352 TplTransmitters Table............................................................................................................... 353 T4GCells Table......................................................................................................................... 355 T4GEquipments Table.............................................................................................................. 356 T4GBearerQualityCurves Table ............................................................................................... 356 T4GBearersRequiredCI Table .................................................................................................. 356 Multi-Service Traffic Management ............................................................................................ 357 T4GEnvironmentDefs Table................................................................................................ 357 T4GMobility Table ............................................................................................................... 357 T4GServicesUsage Table ................................................................................................... 357 T4GServices Table ............................................................................................................. 357 T4GBearers Table .............................................................................................................. 358 T4GTerminals Table ........................................................................................................... 359 T4GTraficEnvironments Table ............................................................................................ 359 T4GUserProfiles Table........................................................................................................ 359 QualityIndicators Table ............................................................................................................. 359 T4GMimoConfigs Table............................................................................................................ 359 InterNetChProtect Table ........................................................................................................... 360 AT281_AM_E1 17 Administrator Manual 18 AT281_AM_E1 © Forsk 2009 List of Figures List of Figures Figure 1.1: Figure 1.2: Figure 1.3: Figure 1.4: Figure 1.5: Figure 1.6: Figure 1.7: Figure 1.8: Figure 1.9: Figure 1.10: Figure 1.11: Figure 1.12: Figure 1.13: Figure 1.14: Figure 1.15: Figure 1.16: Figure 1.17: Figure 1.18: Figure 1.19: Figure 2.1: Figure 2.2: Figure 2.3: Figure 2.4: Figure 2.5: Figure 2.6: Figure 2.7: Figure 2.8: Figure 2.9: Figure 2.10: Figure 2.11: Figure 2.12: Figure 2.13: Figure 2.14: Figure 2.15: Figure 2.16: Figure 2.17: Figure 2.18: Figure 2.19: Figure 2.20: Figure 2.21: Figure 2.22: Figure 2.23: Figure 2.24: Figure 2.25: Figure 3.1: Figure 4.1: Figure 4.2: Figure 4.3: Figure 4.4: Figure 4.5: Figure 4.6: Figure 4.7: Figure 4.8: Figure 4.9: Figure 4.10: © Forsk 2009 Atoll Setup Wizard ..................................................................................................................................... 24 Select Destination Directory Dialogue ....................................................................................................... 24 Select Components Dialogue .................................................................................................................... 25 Atoll Setup Wizard ..................................................................................................................................... 26 Atoll C++ Development Kit Setup Wizard .................................................................................................. 28 Atoll C++ Development Kit Setup Wizard .................................................................................................. 29 Atoll C++ Development Kit Setup Wizard .................................................................................................. 29 Installation Type......................................................................................................................................... 31 Installation Folder and Program Group Selection...................................................................................... 31 Firewall Settings ........................................................................................................................................ 31 Device Driver Installation ........................................................................................................................... 31 Starting NetHASP License Manager ......................................................................................................... 32 NetHASP License Manager window.......................................................................................................... 32 Aladdin NetHASP Monitor ......................................................................................................................... 33 Lic.exe Window.......................................................................................................................................... 35 Reprogramming a License Dongle ............................................................................................................ 35 Test Key Dialogue ..................................................................................................................................... 36 Login Information Dialogue........................................................................................................................ 37 Add-ins and Macros Dialogue.................................................................................................................... 39 Components of Multi-user Environments................................................................................................... 43 Path Loss Architecture for Multiple Source Path Loss Matrices ................................................................ 48 Exporting an Atoll Document to a Database.............................................................................................. 50 Connecting to an Oracle Database............................................................................................................ 50 SQL Server Login Dialogue ....................................................................................................................... 50 ODBC Data Source Dialogue .................................................................................................................... 50 Connection Between an Existing Database and a New Atoll Document ................................................... 53 Export Data From a Current Atoll Document to a Database...................................................................... 53 Archive in the Database............................................................................................................................. 53 Refresh From the Database ...................................................................................................................... 53 Archiving Data in a Database .................................................................................................................... 55 Differences Dialogue ................................................................................................................................. 55 Microsoft Access Database - Transmitters Table Modified by Another User ............................................ 56 Atoll Document - Modified Transmitters Table........................................................................................... 56 Conflict Warning Message......................................................................................................................... 56 Differences Dialogue ................................................................................................................................. 57 Resolving Database Conflicts.................................................................................................................... 57 Selecting Conflicting Data to Consider ...................................................................................................... 57 Updated Microsoft Access Database After Conflict Resolution ................................................................. 57 Archiving a Conflicting Record in the Database or Deleting it From the Atoll Document .......................... 58 Resolving All the Conflicts Simultaneously................................................................................................ 58 Basic Architecture of Oracle ...................................................................................................................... 62 Data Dictionary .......................................................................................................................................... 62 Objects Manipulated by Oracle.................................................................................................................. 63 Databases and Tablespaces ..................................................................................................................... 64 Rasterization Process.............................................................................................................................. 114 Atoll Management Console Setup ........................................................................................................... 135 Atoll Management Console Setup - Installation Directory Selection........................................................ 136 Atoll Management Console Setup - Start Menu Folder Selection ........................................................... 136 Atoll Management Console Setup - Finalising Installation....................................................................... 136 Database Context Menu .......................................................................................................................... 137 Data Link Properties Dialogue - Provider Tab ......................................................................................... 137 Data Link Properties Dialogue - Connection Tab .................................................................................... 138 Atoll Management Console Environment - Current Connected User and Associated Database ............ 138 Creating a New Master Database............................................................................................................ 139 New Database Wizard ............................................................................................................................. 140 AT281_AM_E1 19 Administrator Manual Figure 4.11: Figure 4.12: Figure 4.13: Figure 4.14: Figure 4.15: Figure 4.16: Figure 4.17: Figure 4.18: Figure 4.19: Figure 4.20: Figure 4.21: Figure 4.22: Figure 4.23: Figure 4.24: Figure 4.25: Figure 4.26: Figure 4.27: Figure 4.28: Figure 4.29: Figure 4.30: Figure 4.31: Figure 4.32: Figure 5.1: Figure 6.1: Figure 6.2: Figure 8.1: Figure 8.2: Figure 8.3: Figure 8.4: Figure 8.5: Figure 8.6: Figure 8.7: Figure 8.8: Figure 8.9: Figure 8.10: Figure 8.11: Figure 8.12: Figure 8.13: Figure 8.14: Figure 8.15: Figure 8.16: Figure 8.17: Figure 8.18: Figure 8.19: 20 Steps to Creating a New Master Database .............................................................................................. Steps to Creating a New Master Database .............................................................................................. Archiving Changes in Master Databases ................................................................................................. Working With a Single Level Database .................................................................................................... Working With Project Databases.............................................................................................................. Multiple Project Databases From a Single Master Database ................................................................... Project Database Creation Wizard .......................................................................................................... Creating a New Project Database ............................................................................................................ Refreshing Project Databases.................................................................................................................. Database Upgrade Wizard ....................................................................................................................... Add/Remove Snap-in ............................................................................................................................... Adding Standalone Snap-in - Step 1 ........................................................................................................ Adding Standalone Snap-in - Step 2 ........................................................................................................ Selecting Group Policy Object.................................................................................................................. Group Policies .......................................................................................................................................... Administrative Templates ......................................................................................................................... Defining File Paths for User Groups - Step 1 ........................................................................................... Defining File Paths for User Groups - Step 2 ........................................................................................... User Account and Access Rights Management Dialogue ........................................................................ Creating or Editing a User Account .......................................................................................................... Changes History Management Dialogue.................................................................................................. Record Purge Dialogue ............................................................................................................................ Planet Database Import Dialogue ............................................................................................................ Recommended Network Architecture and Bandwidth Requirements ...................................................... Setting Up Efficient Shared Path Loss Matrices Folders.......................................................................... Microwave Radio Links Template ............................................................................................................ GSM GPRS EGPRS Template - 1 ........................................................................................................... GSM GPRS EGPRS Template - 2 ........................................................................................................... GSM GPRS EGPRS Template - 3 ........................................................................................................... UMTS HSPA Template - 1 ....................................................................................................................... UMTS HSPA Template - 2 ....................................................................................................................... UMTS HSPA Template - 3 ....................................................................................................................... CDMA2000 1xRTT 1xEV-DO Template - 1.............................................................................................. CDMA2000 1xRTT 1xEV-DO Template - 2.............................................................................................. CDMA2000 1xRTT 1xEV-DO Templates - 3 ............................................................................................ TD-SCDMA Template - 1 ......................................................................................................................... TD-SCDMA Template - 2 ......................................................................................................................... TD-SCDMA Template - 3 ......................................................................................................................... WiMAX BWA Template - 1 ....................................................................................................................... WiMAX BWA Template - 2 ....................................................................................................................... WiMAX BWA Template - 3 ....................................................................................................................... LTE Template - 1...................................................................................................................................... LTE Template - 2...................................................................................................................................... LTE Template - 3...................................................................................................................................... AT281_AM_E1 140 140 141 142 143 143 144 144 145 146 148 148 149 149 149 150 150 151 152 153 155 156 162 167 173 206 222 223 224 248 249 250 273 274 275 296 297 298 321 322 323 342 343 344 © Forsk 2009 Chapter 1 Installation Guide This chapter describes installation procedures for Atoll and its components, and the floating license server. Atoll RF Planning & Optimisation Software Administrator Manual 22 AT281_AM_E1 © Forsk 2009 Chapter 1: Installation Guide 1 Installation Guide 1.1 Introduction Atoll is a comprehensive multi-technology and user-friendly radio-planning environment that runs on Microsoft Windows operating systems1. Atoll supports wireless telecom operators throughout their network planning and optimisation cycle, from initial design to densification and optimisation. More than an engineering tool, Atoll is an open, scalable, and flexible technical information system that interfaces smoothly and easily with other IT systems, increases productivity, and shortens lead times. Atoll supports a full range of implementation scenarios, from stand-alone to enterprise-wide server-based configurations using distributed and parallel computing. Some prominent features of Atoll are: • • • • Advanced network design features: - A high-performance propagation calculation engine. - Multi-layered and hierarchical network support. - Traffic modelling. - Automatic frequency and code planning and network optimisation. - Full support of GSM/GPRS/EDGE, UMTS HSPA, CDMA2000, TD-SCDMA, WiMAX BWA, and LTE technologies. - Planning of integrated multi-technology networks (2G/2.5G, 2G/3G, etc.). Open and flexible architecture: - Multi-user environment support through an innovative database architecture providing data sharing, data integrity management, and easy integration with other IT systems. - Integration of 3rd party or proprietary modules (propagation models, AFP, ACP, etc.) through dedicated APIs. - Integration of add-ins and macros. Distributed and parallel computing: - Atoll can distribute computations over multiple workstations and supports parallel computing on multi-processor systems, which dramatically reduces the required time for coverage predictions and simulations, and helps you use your hardware resources to the maximum. State-of-the-art GIS features: - Atoll supports multi-format and multi-resolution geographic data and integration with GIS tools. You can work with large, dense and country-wide databases and interactively manage their display in various layers, including engineering and coverage prediction studies. - Atoll includes an integrated raster and vector editor. Atoll comprises a platform module, which incorporates the basic functions, and optional technology modules, which run on the platform. These technology modules include: • • • • • • • • • 1.1.1 GSM GPRS EGPRS module UMTS HSPA module CDMA2000 1xRTT 1xEV-DO module TD-SCDMA module WiMAX BWA module LTE module Automatic Frequency and Cell Planning modules for different technologies Measurements module (CW measurements and drive test data) Microwave Radio Links module Technical Support For technical queries you can contact the Forsk Technical Support Team, available from Monday through Friday. Contact details for the support teams world-wide are available in "Contact Information" on page 3. You can also consult the support section of Forsk’s website: www.forsk.com. Here, you can download: • • • The latest available version Manuals and technical documents Sample geographic data You can report any problem that you might have encountered using the "Problem Report Template" available on the site. You can also get the latest information about: • • • • Issues fixed in the available versions Already known issues in the phase of being corrected The schedule for the upcoming versions Upcoming holidays 1. The following versions of Microsoft Windows operating systems are fully supported: Microsoft Windows 2000, XP (32-bit and 64-bit), Vista (32-bit), 2000 Server, and 2003 Server. © Forsk 2009 AT281_AM_E1 23 Administrator Manual 1.2 Atoll Installation The following sections describe the installation procedures for Atoll and the floating license manager. Atoll can be installed in the following two ways: 1. On workstations equipped with SuperPro hardware keys. 2. On workstations connected to a single floating license managing server. A floating license management system is installed on this server and a NetHASP hardware key plugged in. This hardware key and the floating license management system control the number of possible Atoll users. There is a defined maximum number of tokens in a floating license system. This is the maximum number of simultaneous Atoll instances that can be launched. Each workstation consumes one token even if more than one Atoll session is running. This approach provides more flexibility. The floating license server can be one of the workstations on which Atoll is installed. Note: • Before proceeding with the installation, see "Administration and Usage Recommendations" on page 167 for information about the hardware requirements for installing and setting up Atoll. 1.2.1 Installation Procedures 1.2.1.1 Interactive Installation You need administrator rights to the computer on which you want to install Atoll. The Atoll setup wizard is simple and lets you configure the installation according to your requirements. Follow the instructions below to install Atoll successfully. 1. Close all programs. 2. Insert the Atoll installation CD ROM in the workstation CD drive. This will launch the Autorun program. If the Autorun does not launch, you can open the contents of the CD in Explorer and run the setup program manually. You can install Atoll in either French or English. 3. Click the Install Atoll command in the Autorun program to launch the Atoll installation. This will run the Atoll setup wizard, which will guide you through the setup process. Figure 1.1: Atoll Setup Wizard 4. Select the destination directory for the installation. Figure 1.2: Select Destination Directory Dialogue The default installation directory for Atoll is C:\Program Files\Forsk\Atoll (or the last directory in which it was installed). You can define a different path during the installation. 24 AT281_AM_E1 © Forsk 2009 Chapter 1: Installation Guide Important note for 64-bit operating systems: • If you are using the 64-bit edition of Microsoft Windows XP, the default installation directory for 32-bit applications is C:\Program Files (x86)\. The Atoll setup program proposes the directory C:\Program Files (x86)\Forsk\Atoll for installation. However, if you install Atoll in this folder, you will not be able to use Atoll with Oracle databases due to a problem in Oracle. It is recommended to install Atoll in a different directory whose name does not contain parantheses. 5. Select the components to install with the application. - Full: Atoll, Atoll calculation server, and the dongle driver for a fixed license. Compact: Atoll only. Custom: Any combination of available components. To install the distributed calculation server, select the Atoll Calculation Server option in the Select Components dialogue. This application is installed as a service on the local computer and runs as long as the workstation is running, even if there isn’t a user logged in. You can access this service’s properties through the Administrative tools in the Control Panel. Distributed calculation server on a given workstation will only be visible to other workstations if the service “Atoll server” is running on this workstation. You can deactivate this service through the Administrative tools in the Control Panel. For more information, see "Distributed Calculation Server" on page 36. Figure 1.3: Select Components Dialogue Notes: • In the case where geographic data is centralised on a file server, make sure that this service is installed on the workstation through a user account that has enough rights to access the geographic data needed for calculations. This might not be the case by default. You can assign a user account to the distributed calculation service through Control Panel > Administrative Tools > Services > Atoll Server properties > Log On tab. • Fixed license dongles cannot be used with Server-type operating systems. • The driver for fixed licenses has been upgraded in the 2.8.1. The new version of the Sentinel SuperPro driver installed with Atoll 2.8.1 is the 7.5.0. • If you work with a fixed license and are about to install Atoll 2.8.1, you must: - Unplug the fixed license key. - In the Atoll 2.8.1 setup, select the Dongle Driver for Fixed Licence check box. - Choose to restart the computer after the installation when the setup proposes the option. - Plug in the fixed license key again. If even after a clean installation Atoll 2.8.1 is unable to access the fixed license key, you must install the Sentinel SuperPro dirver manually. The driver’s setup program (SPI750.exe) is located in the Sentinel folder created by the Atoll 2.8.1 setup in the Atoll installation folder. 6. Select the Start menu folder for Atoll. 7. Verify the installation information. 8. Click the Install button to install the selected components. © Forsk 2009 AT281_AM_E1 25 Administrator Manual Figure 1.4: Atoll Setup Wizard Notes: 1.2.1.2 • You can also download the latest versions available on the Forsk’s Support website by logging on using the user name and password provided by Forsk. • You can click the Back button to go back and modify any of the options during the installation process. • You can click the Cancel button at any time during the installation to cancel the installation. • The setup wizard will ask to restart the computer if you have installed the dongle driver for a fixed license. This driver will become active after the computer has been restarted. • The Atoll User Manual and other documents can also be installed from the installation CD. These documents are also available for download on the Forsk’s support website. • If you have installed Atoll on a Citrix MetaFrame server, it must be published in order for all the users to have access to it. Command Line Installation You can also install Atoll from the command line. This non-interactive mode may be useful for automating Atoll installation using batch files. The Atoll setup program accepts optional command line parameters, which can be useful for administrators, and to other applications calling the setup program. The following table lists the command line parameters accepted by the Atoll setup program. 26 • /SP: Disables the setup’s startup prompt, i.e., the first page with the text "This will install...". • /SILENT or /VERYSILENT: Instructs the setup to be silent or very silent. When setup is silent, the wizard window are not displayed but the installation progress window is. When setup is very silent, even the installation progress window is not displayed. Everything else is normal. So, for example, error messages during installation are displayed, and also the startup prompt (if you have not disabled it with the /SP command line option explained above). If the setup is silent, and it requires a restart, but the /NORESTART option isn't used (see below), it will display the message box asking whether you want to restart your system now or plan to do it later. But, if the setup is very silent, it will restart the computer without asking. • /NOCANCEL: Prevents the user from cancelling during the installation process by disabling the Cancel button and ignoring clicks on the close button. • /NORESTART: When combined with /SILENT or /VERYSILENT, it instructs the setup not to restart the computer even if it is required. • /SAVEINF="filename": Instructs the setup to save the installation settings to the specified file. Don't forget to use quotes if the file name contains spaces. • /LOADINF="filename": Instructs the setup to load the settings from the specified file after having checked the command line. This file can be created using the /SAVEINF option as explained above. Don't forget to use quotes if AT281_AM_E1 © Forsk 2009 Chapter 1: Installation Guide the file name contains spaces. • /DIR="x:\dirname": Overrides the default directory path displayed in the Select Destination Directory wizard page. • /GROUP="folder name": Overrides the default Start menu folder name displayed in the Select Start Menu Folder wizard page. • /COMPONENTS="comma separated list of component names": Overrides the default components setting. Using this command line parameter causes the setup to automatically select a custom installation type.Component names for Atoll are: Atoll, Atoll_Server (for Atoll Calculation Server), RainbowDongle (for Dongle Driver for Fixed License). • /svraccount=username: User name for installing the Atoll Calculation Server. Must be provided if you are installing the Atoll Calculation Server. • /svrpasswd=password: Password for installing the Atoll Calculation Server. Must be provided if you are installing the Atoll Calculation Server. Note: • 1.2.2 The Atoll setup program is based on a freeware setup application called Inno Setup. You can also visit Inno Setup’s website for further information: http://www.jrsoftware.org/ isinfo.php. What's Installed With Atoll Some other components required by Atoll may also be installed during Atoll installation. Atoll requires an appropriate version of Microsoft Data Access Components (MDAC) in order to work with databases. The minimum MDAC version is 2.7, which can be installed from the installation CD or downloaded from the Forsk’s support website if needed. Help files are automatically installed with Atoll. You can also install Adobe Acrobat® Reader from the installation CD. 1.2.3 Installation Troubleshooting If you have trouble installing Atoll, make sure that you are logged on with a user account that has administrator rights on the computer. Once you have successfully installed Atoll, you must restart the computer and log on again with a user account that has administrator rights on the computer. This is necessary for completing the installation of the libraries that were in use during the installation. These libraries may include the Microsoft Data Access Components (MDAC) library and the sentinel driver. Also verify that you have installed Atoll in a valid folder. The default Atoll installation folder is named "Atoll". Make sure that modifying it during the setup and installing Atoll to a folder with another name has not changed it to, for example, "C:\Program Files\Forsk\XYZ\Atoll\", where XYZ is the name of the installation folder where you wanted to install Atoll. If the version of the Microsoft Data Access Components (MDAC) installed on your computer is older than 2.7, you will have to install a newer version. You can install the newer version from the Atoll installation CD or download it from the Microsoft website: http://msdn.microsoft.com/data/mdac/default.aspx. The minimum required MDAC version is 2.7. Microsoft Windows XP, 2003 Server, and later versions install these components automatically, so you will not have to install them yourself. If you get a "Protection key error" message, please verify that there is a hardware key correctly plugged in and that it is valid. If you are using a SuperPro hardware key, try restarting your computer after the installation using a user account with administrator rights, and reinstalling the Sentinel SuperPro driver. Atoll installation CD contains the Sentinel SuperPro driver version 5.41. You can also download and install the latest Sentinel SuperPro driver from http://www.safenetinc.com/support/tech/sentinel.asp. In case the fixed or the floating license key suddenly becomes unavailable for any reason, Atoll will ask the users currently accessing the key whether they want to save their open documents before quitting the application. If, in the mean time, you have made the key available again, Atoll will let you reconnect and continue working. Notes: • You can download and install either the latest version of the driver from the Sentinel website, or install the version 5.41 available on the Atoll installation CD. • Atoll setup program installs the version 5.41 of the Sentinel SuperPro driver. You can also set a command line parameter for Atoll to keep a log file for each Atoll session. Messages listed in the Events tab will then be saved in a .log file. You can activate this feature for some or all users by using the following command line syntax: "C:\Program Files\ForskTools\Atoll\Atoll.exe" -log "C:\...\events.log" If any problem persists after verifying all these points, do not hesitate to contact the Forsk Technical Support Team (see "Contact Information" on page 3). © Forsk 2009 AT281_AM_E1 27 Administrator Manual Important: • It is recommended to switch off your computer before unplugging or plugging in the hardware key. • Do not change the computer’s date. • With a temporary SuperPro hardware key: - Do not reprogram it even if you plug it into another computer. - Do not modify the time bomb settings before contacting the Forsk Technical Support Team. 1.2.4 Getting Help in Atoll Once you have successfully installed Atoll, you can access the online help at any time by, • • Selecting the Help Topic command in the Help menu, or Pressing F1. You can browse and search through the help topics in different ways: • • • Through the Contents tab: This tab lets you scroll through the table of contents in order to find the information you need. Through the Index tab: This tab lets you browse through the index in order to find the information you need. Through the Find tab: This tab lets you enter a keyword and launch a search query in order to list all the help topics that contain the specified keyword. For explanations of items present in dialogue boxes in Atoll, you can click the What's this button , located at the upperright corner of each dialogue, and click the item about which you want more information. You can get descriptions of toolbar buttons in the form of tool-tip balloons, and of menu commands in the status bar by placing the cursor above them. You can get information about Atoll (version, build, type of license, days remaining before the license expires, etc.) by clicking the About button in the toolbar or the About Atoll command in the Help menu. Atoll version and build number are saved in the document properties of each .atl file. You can know the version and build with which any .atl file was last saved by opening the 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. Select the Summary tab and click the Advanced button. The Atoll version and build number are stored in the Revision Number property. 1.2.5 Atoll C++ Development Kit Installation You need administrator rights to the computer on which you want to install the Atoll C++ Development Kit. Follow the instructions below to install the development kit successfully. 1. Close all programs. 2. Insert the Atoll installation CD ROM in the workstation CD drive. This will launch the Autorun program. If the Autorun does not launch, you can open the contents of the CD in Explorer and run the setup program manually. 3. Click the Install Atoll C++ Development Kit command in the Autorun program to launch the installation. This will run the Atoll C++ Development Kit setup wizard, which will guide you through the setup process. Figure 1.5: Atoll C++ Development Kit Setup Wizard 4. Select the destination directory for the installation. The default installation directory is C:\Program Files\Forsk\Atoll (or the last directory in which it was installed). You can define a different path during the installation. 28 AT281_AM_E1 © Forsk 2009 Chapter 1: Installation Guide 5. Verify that all the installation information is correct. Figure 1.6: Atoll C++ Development Kit Setup Wizard 6. Click the Install button to install the develpment kit. Figure 1.7: Atoll C++ Development Kit Setup Wizard Notes: 1.2.6 • You can click the Back button to go back and modify any of the options during the installation process. • You can click the Cancel button at any time during the installation to cancel the installation. Uninstalling Atoll To uninstall Atoll: 1. Close all programs. 2. Open the Control Panel. 3. Open Add or Remove Programs. 4. Select Atoll in the list of installed programs listed under the Install/Uninstall tab. 5. Click Remove. 6. Follow the instructions in the uninstall wizard. 1.3 Floating License Manager Installation A floating license manager is installed on a floating license server in order to work in a network environment with floating licenses. A floating license server is a computer where the floating license management system is installed and with a NetHASP hardware key plugged in. This hardware key and the floating license management system control the number of possible Atoll users. There is a defined maximum number of tokens in a floating license system. This number corresponds to the maximum number of simultaneous Atoll instances that can be launched. Each workstation consumes one token even if more than one Atoll session is running. The floating license managing server can be one of the workstations on which Atoll is installed. The floating license management system, called NetHASP, is manufactured by Aladdin. This system includes: • A NetHASP key: Depending on the number of potential users, keys may be programmed with a variable number of tokens. Important: • © Forsk 2009 One workstation consumes one token even if more than one Atoll session is running. AT281_AM_E1 29 Administrator Manual • • • • The NetHASP license manager: This application communicates with Atoll and NetHASP. The HASP device driver: This device driver is an interface between the NetHASP license manager and the NetHASP key. The NetHASP monitor: This monitor enables you to check the number of consumed tokens. The nethasp.ini and nhsrv.ini files: The nethasp.ini file is installed on each workstation to facilitate access to the license server. The nhsrv.ini file is installed on the server in order to authorise workstations to consume tokens. The workstation and the NetHASP license server read and use the information in these files if they exist. Otherwise, default values are used. Notes: 1.3.1 • Check for latest updates of the NetHASP License Manager, the HASP Device Driver and the NetHASP Monitor software at http://www.aladdin.com/support/hasp/hasp4/ enduser.asp. There might be newer versions available than those provided on the CD that you can download and install. • In case a workstation is connected to a server with a license manager and a NetHASP hardware key, and is also equipped with a SuperPro hardware key at the same time, the SuperPro hardware key has priority over the NetHASP hardware key. • In case a SuperPro hardware key is plugged into a workstation where the license manager is installed (the server), the SuperPro hardware key is ignored. • SuperPro hardware key cannot be used with a Server-type operating system. Requirements The following are the minimum requirements for a computer that will run the floating license management server: • • Operating system: Microsoft Windows 2000 or 2000 Server. Available parallel or USB port to plug in the NetHASP hardware key. The following requirement must be fulfilled for a network protected by a firewall: • If the floating license management server is behind the firewall, port 475 must be open when using the UDP or TCP protocol. 1.3.2 Installation Procedure 1.3.2.1 NetHASP License Manager Important: • Do not plug the NetHASP hardware key (dongle) in the server before installing the device drivers. Otherwise, Microsoft Windows will try to find the best suited device driver for the hardware key and automatically install it. Wait for the License Manager setup to indicate when to plug in the hardware key. The NetHASP License Manager counts the tokens being consumed by different workstations and manages their allocation and retrieval. The NetHASP device driver communicates with the NetHASP hardware key. The NetHASP License Manager, the HASP Device Driver and the NetHASP Key must be installed on the server. You may also copy or create the nhsrv.ini file on the server. The NetHASP License Manager settings in the file can later be modified according to the your requirements. To install the NetHASP License Manager and the HASP Device Driver: 1. Run LMsetup.exe. You can find this file on the HASP installation CD under the folder "\servers\win32-ver8.31\", or download it from the Aladdin website: http://www.aladdin.com/support/hasp/hasp4/enduser.asp, under the section "The Latest NetHASP License Manager (LM) Downloads". 2. Choose "Service" as the type of installation. This means that the license manager runs as a service on this server as long as it is running, even if there is no user logged on. You can install is as an application but, in that case, you will have to launch the application manually every time you log on to the server. 30 AT281_AM_E1 © Forsk 2009 Chapter 1: Installation Guide Figure 1.8: Installation Type 3. Specify a destination directory. The default installation folder is “C:\Program Files\Aladdin\HASP LM”. Figure 1.9: Installation Folder and Program Group Selection 4. Choose whether you would like the setup program to modify your firewall settings or whether you would prefer doing that manually later on. Figure 1.10: Firewall Settings 5. Accept the following dialogues until NetHASP License Manager is installed. 6. Accept automatic driver installation. Figure 1.11: Device Driver Installation This device driver enables the NetHASP License Manager to communicate with the hardware key. © Forsk 2009 AT281_AM_E1 31 Administrator Manual 7. Once the device driver is successfully installed, plug the NetHASP hardware key in the server’s parallel or USB port. Figure 1.12: Starting NetHASP License Manager 8. Start the NetHASP License Manager. The license manager is started in Service mode. A small icon is visible in the task bar at the lower right of the screen. You can access the network communication protocols by double-clicking this icon. Load and Remove commands in the menu bar enable you to modify these protocols. To close the window without stopping the license manager, select Exit in the menu bar. 9. Search for file nhsrv.ini on the CD and copy it to the directory where the NetHASP License Manager is located. The nhsrv.ini file can be later customised as required. See "nhsrv.ini File" on page 33 for more information. You can now run Atoll sessions on as many workstations connected to this NetHASP license server as the number of tokens available on the NetHASP hardware key plugged in the server. The NetHASP License Manager setup automatically installs the HASP device drivers. If you need to install the HASP device drivers separately, you can download the latest version from the Aladdin website: http://www.aladdin.com/support/ hasp/hasp4/enduser.asp, under the section "HASP Device Driver Downloads". The correct (recommended) version of the device driver setup to download is the one that works with "HASP4 API v8.x or Envelope 12.x". There is usually a relevant note on the web page that points to this setup file. The NetHASP License Manager window displays a list of supported protocols which can be modified through the Load and Remove menus. Closing this window through the Exit menu or through the window’s Close command only minimises the NetHASP License Manager. It neither stops the service from running in the background nor closes the application. The NetHASP License Manager is available in the taskbar as long as the service is running. To close the NetHASP License Manager or to stop the HASP Loader service, 1. Select Control Panel -> Administrative tools -> Services to access the Services management console. 2. Right-click the HASP Loader service and choose Stop from the context menu. Figure 1.13: NetHASP License Manager window Important: • The NetHASP hardware key must always stay plugged in to the server once you have successfully installed the NetHASP License Manager. Notes: 32 • NetHASP hardware key is supported by Windows 2000 Server and Windows 2003 Server with NetHASP License Manager 8.20 or above. • When downloading the setup files from the Aladdin website, keep in mind that you should download setup files for HASP4 and not HASP HL. AT281_AM_E1 © Forsk 2009 Chapter 1: Installation Guide 1.3.2.2 nhsrv.ini File The nhsrv.ini file must be located in the same directory as the NetHASP License Manager. In the context of Atoll and NetHASP License Management system, the nhsrv.ini file can be used to define and restrict the users who will be allowed tokens from the NetHASP hardware key connected to a given server. The following sample nhsrv.ini file shows how: ;NetHASP License Manager configuration file syntax. ;Note: All text lines are commented. Remove comments in the lines you want to use. [NHS_SERVER] ;NHS_IP_LIMIT = < IpAddr0> [, <IpAddr1>...];Specify the range of stations the License Manager serves. Examples: 10.1.1.1, 10.1.1.* Complete syntax of the nhsrv.ini file can be found on the HASP installation CD as well as on the Aladdin website. 1.3.2.3 NetHASP Monitor You can install the NetHASP Monitor on the server, or on one or several workstations, to keep track of the number of tokens being consumed. You can find the setup file (askmon32.exe) on the HASP installation CD, or download the latest version from the Aladdin website: http://www.aladdin.com/support/hasp/hasp4/enduser.asp, under the section "DiagnostiX and Support Tools". To install the NetHASP Monitor: 1. Run askmon32.exe. 2. Specify a destination directory. The default installation folder is “C:\Program Files\Aladdin\Monitor”. 3. Accept the following dialogues until the NetHASP Monitor is installed. The NetHASP Monitor displays the list of workstations using tokens available on the NetHASP hardware key that is connected to the NetHASP License Management Server. Figure 1.14: Aladdin NetHASP Monitor 1.3.2.4 NetHASP.ini File It is recommended to keep a nethasp.ini file on each client workstation in the Atoll installation directory. This file lets Atoll identify the NetHASP license server where it can find the NetHASP License Manager and request tokens from the NetHASP hardware key. The following is a sample of the nethasp.ini file with the minimum required information. Complete syntax of the nethasp.ini file can be found on the HASP installation CD as well as on the Aladdin website. [NH_COMMON] NH_IPX= Disabled ;Use the IPX protocol - Enabled or Disabled NH_NETBIOS= Disabled ;Use the NETBIOS protocol - Enabled or Disabled NH_TCPIP= Enabled ;Use the TCP/IP protocol - Enabled or Disabled [NH_TCPIP] © Forsk 2009 AT281_AM_E1 33 Administrator Manual NH_SERVER_ADDR= 3CT000J ;IP addresses of the NetHASP license server NH_TCPIP_METHOD= UDP ;Send a TCP packet or UDP packet NH_USE_BROADCAST= Disabled ;Use TCP/IP Broadcast mechanism - Enabled or Disabled Notes: 1.3.3 • It is recommended to specify the server name in the domain (NetBios name) in the nethasp.ini file. • If the full server name is Server1.company.com, enter just Server1, and do not enter Server1.company.com. • Only one server name is supported in the nethasp.ini configuration file. • For NetHASP License Manager 8.20 or later, Aladdin recommends UDP as the default TCP/IP method. You should modify the NH_TCPIP_METHOD entry in the [NH_TCPIP] section accordingly. • Remove the NH_SESSION and NH_SEND_RCV entries from your nethasp.ini file if these exist. You should adjust these fields in your nethasp.ini file only if required. These fields set the timeout delays according to the network and are usually of interest if the network is particularly slow. License Management Using Lic.exe Lic.exe (Atoll License Manager) is a utility installed with Atoll which enables you to monitor, troubleshoot, and update license dongles. The most important function of the Atoll License Manager is to let Atoll administrators update their license keys by loading new key programming instructions from a .alic file provided by Forsk. Important: • You should not modify the programming, and the existing information available in the License Management interface, without consulting Forsk Technical Support first. Modifying the information unnecessarily might damage your fixed or floating licenses and may block users working with Atoll. To access the license management utility: 1. Run Lic.exe installed in the Atoll installation folder. The License Management window opens. Figure 1.15: on page 35 shows the License Management interface. 2. Under Available Licenses, select a key in order to display the information related to it. The Clear All button is reserved for use by Forsk. Under Selected Key the following information and options related to the selected key are available: - - - Number: Unique key number given by the key provider. This number must be communicated to Forsk upon request whenever you require the key to be reprogrammed. Type: The type of dongle, Fixed License or Floating License. Reference: Unique floating license dongle reference provided by Forsk. This reference must be communicated to Forsk upon request whenever you require the key to be reprogrammed. This reference is also printed on the sticker on the dongle. Location (Server): Name of the license management server on which the floating license dongle is physically plugged. Under Modules and Licenses, all the Atoll modules accessible and available for users using the selected key are listed along with the numbers of licenses of each for each module. Under Number of Licenses, the Modify buttons should not be touched. These buttons are reserved for use by Forsk. Under Dates and Durations, the following dates and durations are available: - License Start License End Duration of validity Time Bomb Each Atoll license purchased by any customer corresponds to a given version. There is no time limit for using this particular version. But, if customers want access to newer versions and updates, containing new features and problem fixes, they also have to purchase yearly maintenance. In this case, Forsk reprograms the keys to support new versions. The Time Bomb date generally conforms to the end date for maintenance. To ensure better license management, licenses are programmed with an annual time bomb date. When the time bomb date passes, the key stops working. The user can either purchase maintenance for the next year, and benefit from the new features and bug fixes, or the key can be simply reprogrammed without maintenance for the next year, and the user can continue working with the version he has. Atoll can be instructed to inform the user 30 days before the maintenance expiry date that the license will end in 30 days. This time can be configured through the Atoll.ini file. 34 AT281_AM_E1 © Forsk 2009 Chapter 1: Installation Guide Figure 1.15: Lic.exe Window - Under Key Programming, the buttons allow you to reprogram the selected key or test it. To reprogram a key, you must have a reprogramming instructions file (.alic) sent by Forsk. To reprogram a key: i. Verify that the dongle is physically connected to your computer and is listed under Available Licenses. ii. Under Available Licenses, select the key to reprogram. iii. Under Key Programming, click the Load button. The Open dialogue appears. iv. Browse for the .alic file and open it. The key is reprogrammed. Figure 1.16: Reprogramming a License Dongle To test a key: i. Under Available Licenses, select the key to test. ii. Under Key Programming, click the Test button. The Key test dialogue appears. iii. Under Modules, select the module that you want to test iv. Click the Test button. The test shows whether the selected module is authorised on the key or not. © Forsk 2009 AT281_AM_E1 35 Administrator Manual Caution: • Testing a module by entering a future date can decrease the time left for using that license. Therefore, you should not test any module at a future date. Figure 1.17: Test Key Dialogue - Under Profile Signature, the PID (profile signature or ID) is available, which 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. 3. Click Close. The License Management window closes. 1.4 Distributed Calculation Server Due to limitations of Microsoft Windows operating systems, each Atoll session can only use a maximum of 2 to 3 GB of memory. This memory limit can be breached when an Atoll session is performing calculations over large (country-wide) networks. If multiple sessions use large amounts of memory then the server can become unresponsive and processes may appear to have crashed. Atoll includes an optional distributed calculation feature that enables you to use a number of computers to perform propagation path loss matrix calculations. The distributing calculation service has a lower memory requirement than Atoll because it has no GUI. It is is suited for memory intensive processes. The distributed calculation service is a Windows service, and is installed as part of the standard installation. It uses the standard Atoll API to exchange data with the path loss calculator and the Atoll session. When an Atoll session requests a calculation, the request is passed to the distributed calculation service using the Atoll API. If the distributed calculation server has a spare thread, it starts performing calculations using that thread. Otherwise, the request is placed in a queue. When a thread finishes a calculation, it passes the results back to the Atoll session. In order to control the number of data fluxes, calculations are done in the following manner: 1. User’s workstation sends the request for calculating path loss matrices to distributed calculation servers. 2. Distributed calculation servers calculate the path loss matrices and send the results directly to the storage location (the file server where path loss matrices are stored). User’s workstation can request the path loss matrices from the file server if they are needed for coverage predictions. If an error occurs on any of the distributed calculation servers, Atoll starts to calculate the path loss matrices on the local computer. In this case, Atoll only uses one thread on the local computer and calculates the path loss matrices one by one. The local computer does not try to create as many threads as set for the distributed calculation servers in order to avoid memory saturation. Any error or warning messages generated are passed back to the Atoll session and displayed in the Event Viewer. A computer on which the distributed calculation service is installed and running is called a distributed calculation server. This computer, the distributed calculation server, is visible to all the workstations connected to it through Atoll sessions. You can have as many distributed calculation servers installed as required. By default, a single instance of the distributed calculation service is run when the computer (server) starts. You can, however, run up to 9 additional distributer 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 line prompt window is opened. To stop an additional manually run service, close the command prompt window corresponding to it. Note: • Atoll can detect a total of 10 distributed calculation services. 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. Compatibility Between Atoll and the Distibuted Calculation Server Any version of Atoll supports the distributed calculation server of the same and any later version. Consequently, a version of the distributed calculation server supports the same and earlier versions of Atoll (to a certain limit). 36 AT281_AM_E1 © Forsk 2009 Chapter 1: Installation Guide Setting Distributed Calculation Server Options The Atoll application on the server can be configured to use the distributed calculation server through a set of entries in the Atoll.ini file. Each entry lists a server where this service is running and which could be used for computations. By default, the Atoll distributed computation server (AtollSvr.exe) runs with a normal priority on the computers on which it is installed. However, you can modify its process priority on the system by defining the priority parameter in the Atoll.ini file. This option works for the service as well as the application mode of the distributed calculation server. The AtollSvr calculation server application supports dual-processor configurations, and both processors on a multi-processor station can be used. In other words, the service is capable of managing four threads to perform calculations. For more information, see "Setting the Number of Parallel Processors and Threads" on page 101. 1.4.1 Installing the Distributed Calculation Server The calculation server application (AtollSvr), is included in the Atoll platform. This server application can be installed on workstations or servers and can be used by Atoll sessions running on other connected workstations. The distributed calculation server application can be installed on any workstation or server where Atoll is installed. You can opt to install this application by checking the "Atoll Calculation Server" check box in the Select Components dialogue of the Atoll setup wizard. The application is automatically selected for installation if you have chosen Full Installation. You must log on with a user account with administrator rights on the computer when installing Atoll and the distributed calculation server. Figure 1.18: Login Information Dialogue The application is installed as a service on the local computer. This means that this service will be available to other workstations running Atoll as long as this distributed calculation server is running, even if there is no user logged on. During the installation, the Atoll setup wizard will ask for the login information of the user with administrator rights on the computer in order to start the server application once the installation is complete. You can access the properties and manage the service properties through Control Panel -> Administrative tools -> Services. From the Log On tab of the service properties, you can modify the user name, password, and domain name, and restart the service to free up the server for other calculations. Note: • © Forsk 2009 In the case where geographic data is centralised on a file server, make sure that this service is installed on the workstation through a user account that has enough rights to access the geographic data needed for calculations. This might not be the case by default. You can assign a user account to the distributed calculation service through Control Panel > Administrative Tools > Services > Atoll Server properties > Log On tab. AT281_AM_E1 37 Administrator Manual 1.4.2 Uninstalling the Distributed Calculation Server The distributed calculation server is installed as a service on workstations (or servers) and runs as long as the computer is running and the service has not been manually stopped by the administrator of the computer. To uninstall this service, you must be logged on to the computer with a user account with administrator rights. The service can be uninstalled in two steps: 1. Stopping the service. 2. Unregistering the service. To stop the AtollSvr service, 1. Access the Services Management Console through Control Panel -> Administrative tools -> Services. 2. Right-click the Atoll Server service and choose Stop from the context menu. You can also stop the service by double-clicking it and clicking the Stop button in the General tab of its properties dialogue. Once the service is stopped, you can unregister the service as described below: 1. Open the Run dialogue from the Start menu. 2. Enter "<Atoll Installation Path>\AtollSvr.exe /UnregServer" and click Run. This will remove the distributed calculation service from the computer. The <Atoll Installation Path> is the path to the Atoll installation directory (typically C:\Program Files\Forsk\Atoll\). 1.5 Add-in and Macro Installation Add-ins are usually compiled .dll files which can be placed in any designated folder on the local computer and activated by registering them in the Windows’ registery. Once the add-ins have been registered, a new Atoll session will automatically load them in the list of add-ins available in Atoll. You can choose to activate or deactivate them from within Atoll. Macros are of two types: those which can be executed from Atoll, and those which can be executed independently. Atoll can load and execute macros written in VBScript, Javascript, or plain text files. It is possible to access and work with add-ins and macros when there is no .atl file open in Atoll. There can be two different ways to install an add-in: • • If the add-in has an executable setup file: Run the setup program, it will automatically place the .dll file in an appropriate folder and register it. If the add-in is simply a .dll file: Place it in any appropriate folder, and register it. Once loaded, the add-in will be accessible through Atoll and listed in the list of available add-ins in the Add-ins and Macros dialogue. You can select which add-ins will be available to the users by checking the corresponding check boxes. 38 AT281_AM_E1 © Forsk 2009 Chapter 1: Installation Guide Figure 1.19: Add-ins and Macros Dialogue To uninstall an add-in: 1. Close any open Atoll session. 2. Unregister the add-in’s .dll file. You can add, edit, refresh, run, and delete macros from Atoll through the Add-ins and Macros dialogue. • • • • • • To add a new macro to Atoll: Click the Add button and select the file containing the macro (.vbs, .js, and .txt). To delete a macro from Atoll: Select the macro to delete in the list of macros, and click the Delete button. To edit an existing macro: Select the macro to edit in the list of macros, and click the Edit button. To execute a macro from Atoll: Select the macro in the list of macros, and click the Run button. To assign an icon to a macro: Select a macro in the list of macros, click the Icon button, and select a file containing the icon. To refresh an edited macro: Select the macro that has been edited in the list of macros, and click Refresh. You can use .cfg files to save the list of macros available in Atoll. You can also use .cfg files or the Atoll Management Console to automatically load macros for different groups of users. For example, you can load an OMC interface macro for the group of users working on the OMC interfacing. For more information, refer to "User Configuration File (.cfg)" on page 69 and "Managing Administration File Paths" on page 147. © Forsk 2009 AT281_AM_E1 39 Administrator Manual 40 AT281_AM_E1 © Forsk 2009 Chapter 2 Multi-user Environments and Databases Atoll RF Planning & Optimisation Software Administrator Manual 42 AT281_AM_E1 © Forsk 2009 Chapter 2: Multi-user Environments and Databases 2 Multi-user Environments and Databases A multi-user environment is where a number of users, or groups of users, work simultaneously on given parts of a single large (may be nation-wide) network. Different user groups may be working on regional or smaller sections of the network. This section describes the different components of multi-user environments and outlines their purpose. The next section describes the process of setting up such environments. Figure 2.1: Components of Multi-user Environments 2.1 Components of Multi-user Environments A multi-user environment is made up of: 1. A master Atoll document which can only be accessed, modified and updated by the Atoll administrator. Through this master Atoll document, the Atoll administrator can globally manage all the data shared by all the individual Atoll users or groups of users. 2. The shared data which is initially set up using the master Atoll document by the administrator, and is then accessed, modified, worked upon and updated by the Atoll users and the administrator. The shared data is mainly of the following three types: - The shared path loss matrices The path loss matrices are calculated through the master Atoll document by the administrator and can be updated by the administrator only. A calculation administrator can be a different individual than the administrator who created the master Atoll document. Each individual user can access these path loss data in a read-only manner. If users modify their Atoll documents so that their modifications make the path loss data invalid, any path loss matrices calculated by these users are stored locally, either embedded in the .atl file or externalised, and don not modify the shared path loss data. Shared path loss matrices are updated when the calculation administrator performs an update by taking into account the modifications made by other users which have been stored and updated in the master database. Shared path loss matrices enable a number of users to work with a centralised path loss matrices folder, containing path loss matrices corresponding to the master Atoll document, shared by several users. - The shared geographic data Shared geographic data files are usually stored on a common file server with a fast access connection. The recommended file server configuration is provided in "Recommended File Server Configuration" on page 168. Since the geographic data usually comprises large files, it is usually stored outside any .atl file, i.e., it is externalised, so as to minimise the .atl file size. Once the common, shared geographic data is stored at the required location, it is rarely modified or updated. Often, users who modify geographic data locally, such as edit clutter or traffic in their respective projects, store these modifications locally, since these modifications rarely impact other users. © Forsk 2009 AT281_AM_E1 43 Administrator Manual User configuration files (.cfg or .geo) are used to store the characteristics or properties related to geographic data in each user’s Atoll document. For more information, refer to "User Configuration File (.cfg)" on page 69. The administrator can set up different user configuration files (.cfg) for separate user groups, and use the Atoll management console to assign these .cfg files to each group of users. It is also possible to set a .cfg file to be automatically loaded by Atoll when a user project is loaded. User configuration files can be shared and exchanged between users working on the same project. - The master database The master database stores all the radio data of all the Atoll user projects. It is initiated through the master Atoll document by the administrator, and is then subdivided into sections on which users or groups of users can work simultaneously. Once the database is in place, users can modify their projects, refresh their projects from the data stored in the database, and archive their modifications in the database. Moreover, potential data conflicts due to modifications from other users, modified or deleted records, for example, can be detected and resolved. Atoll documents memorise their database connection properties and allow the users to manage data consistency in deferred processing. Furthermore, Atoll can be configured to automatically load projects from databases by providing the required connection parameters in the command line. The same database server can be used to store one or more master databases corresponding to different technologies. For example, a GSM database, a UMTS database, and a microwave links database can be stored on the same database server using the same RDBMS (Oracle, for example). 3. User projects which are initialised by the administrator but are later worked upon and managed by each individual user. User projects are .atl files which are connected to the master database, load only the required part of the geographic data (as defined by the .cfg file, for example), and have access to the shared path loss matrices folder. However, these projects only impact parts of the master database depending on their access rights. 2.1.1 Supported RDBMS Working with databases allows several users to share data without the risk of data inconsistency. In a multi-user configuration, all the users are connected to a master database. Atoll supports the following RDBMS: • • • • Microsoft SQL Server Microsoft Access Oracle via the OLE DB interface Sybase through the ODBC interface Other databases that accept .udl files and support the ODBC interface can also be accessed. The physical location of databases varies according to the type of the database. The following table shows where the database must be installed: Database Server Workstation Microsoft Access No Yesa Microsoft SQL server Yes No Oracle Yes Yes (Oracle client) Sybase Yes Yes a. It is possible to work with an Atoll document connected to a Microsoft Access database even if Microsoft Access is not installed on the computer. Atoll allows you to interactively create your database when possible. Some databases, Microsoft SQL Server for example, cannot be created in this manner and must be set up by the administrator. Each database has its specific connection parameters and access dialogues. 2.2 Setting Up Multi-user Environments A multi-user environment can be set up by the administrator by following the process described below. The general process for creating multi-user environments remains the same, but the details may vary depending on each network and operator’s requirements. 1. Create the master Atoll document, which covers the entire network. 2. Import and link the geographic data in this project. 3. Import or create the radio network data in the project. 4. Export the radio network data to a database in order to create the master database. 5. Create a private path loss matrices folder for this project. 6. Perform path loss computation over the entire network. 7. Define user groups (if required) and create user configuration files for geographic data, and site lists or filtering polygons for radio data. 8. Create project databases using the Atoll Management Console for the different user groups (if you opt for site lists or filtering polygons). Or, use Oracle Locator or Oracle Spatial to define each user’s effective working region. 44 AT281_AM_E1 © Forsk 2009 Chapter 2: Multi-user Environments and Databases 9. Create user Atoll documents (using the Open from Database command), assign the shared path loss matrices folder to each project, and the relevant user configuration (either by importing the .cfg file or by using the Atoll Management Console to assign the .cfg file for a user group). 2.2.1 Master Atoll Document The master Atoll document should encompass the entire network. It should contain all the radio network data and all the geographic data corresponding to the entire network. You can also have many master Atoll documents that do not overlap. For example, for a large country-wide network, you may choose to divide the entire network into 4 regions, e.g., north, south, east and west markets, and create a master Atoll document for each of the four markets. However, the concept of the master Atoll document remains the same. Once you have determined the scope of your master Atoll document(s), you can create it by following the steps below: 1. Place the geographic data corresponding to the master Atoll document on the file server. 2. Start Atoll and create a new .atl file. 3. Set the Projection and Display coordinate systems, and the transmission, reception, and other units as required. 4. Import the geographic data into the .atl file. Remember that it is always recommended to link large geographic data files rather than embedding them in the .atl file. 5. Either create a preliminary network on which each individual user will work, or import the radio network data from an existing database into the master Atoll document. 6. Create a Computation Zone that covers the entire network. Once you have correctly created or imported the required radio network data to start with, you are ready to create your master database and to create the initial shared path loss matrices folder as well. 2.2.2 Shared Path Loss Matrices The shared path loss matrices folder, in a multi-user environment, is only write-accessible for the administrator. The initial results, in the form of .los files, stored in this folder may correspond to the preliminary radio network data. As individual users continue to work on their specific Atoll documents, they update the master database from time to time in order to store their more precise parameters for the network data and modified radio network data. The administrator updates the master Atoll document with the data updated by other users in the master database, and performs the path loss calculations from time to time. When the administrator launches the path loss matrices computation, Atoll verifies whether the existing path loss matrices have been invalidated by the updates made by other users in the master database. If there have been updates in the master database which require recalculation of path loss matrices, Atoll recalculates them and updates the relevant .los files. 2.2.2.1 Setting Up Shared Path Loss Matrices Path loss matrices can be externalised in .los format files placed in a separate folder. It is possible to share these path loss matrices between a number of users. Externalising path loss results, i.e., creating .los files for each path loss matrix and storing them in a folder and not inside the .atl project file, has many advantages, such as: • • • You can limit the .atl file size by storing the related path loss matrices at a separate location. By storing the path loss matrices on another computer, such as a file server, accessible through a fast network connection, you can also gain local disk space. By setting up a shared path loss folder, you can easily manage a centralised path loss file server, accessible by all the users working on the same Atoll document. This feature enables the users to optimise calculation times and to minimise disk usage on their workstations. Note: • One .los file contains one path loss matrix. Therefore, a single transmitter can have up to two .los files associated with it. Master Atoll Document: A specific configuration which is easy to set up and maintain is required to use this feature. It requires that all the users be connected with a master database and that the master project must be managed by the administrator, who also manages the centralised path loss results through the master Atoll document, also connected to the same database. Important: • The shared path loss matrices folder should be "Read/Write" accessible for the administrator, but "Read-only" for other users. The master Atoll document should encompass the Atoll documents of all the other users. For example, if the Atoll documents of all the users in a region cover sections of that region, the master Atoll document should cover the entire region, so that the administrator can manage the path loss results for all the users working on that region. The private external path loss matrices folder of the master Atoll document will serve as the shared external path loss matrices folder for all the other user projects. So, in order to set up the shared path loss matrices folder, the administrator must initiate the Atoll document covering the entire region. He must then create a private external path loss matrices folder © Forsk 2009 AT281_AM_E1 45 Administrator Manual on a suitable computer, e.g., a file server (refer to "Recommendations on Path Loss Management" on page 171 for more information). And, then, he must associate this folder with his Atoll document as follows: 1. Open the Prediction folder’s properties by right-clicking the Predictions folder (Explorer Window’s Data tab) to open its context menu. 2. Either specify the complete path to the private path loss matrices folder in the Private Directory field, or click the button, select Browse, and indicate the Pathloss.dbf file corresponding to the private folder. 3. Click OK. Once this path loss matrices folder has been set up, the administrator should perform the entire path loss matrix calculation for the master Atoll document, in order for the users to be able to access these results. Only the administrator can update the shared matrices by refreshing (loading again) the master Atoll document with the data stored in the master database, and recalculating all the path loss matrices. In this way, the path loss matrices for all the new transmitters added by the users, and the path loss matrices invalidated by modifications made by the users, will all be recalculated. Caution: • • The shared path loss matrices must be unlocked for other users to be able to work with them. The administrator can check whether the shared path loss matrices are unlocked or not in the Propagation tab of the Transmitters folder’s properties dialogue. The administrator must update the shared path loss matrices only when they are not being accessed by other users. User Documents: Important: • It is advised to refresh data from the database in each user’s Atoll document and save it before setting up the shared path loss matrices folder. To use shared path loss matrices: 1. Open the Prediction folder’s properties by right-clicking the Predictions folder (Explorer Window’s Data tab) to open its context menu. 2. Either specify the complete path to the shared path loss matrices folder in the Shared Directory field, or click the button and indicate the Pathloss.dbf file corresponding to the shared folder. 3. Click OK. Note: • It is not mandatory to store private path loss matrices in an external folder in order to access public path loss matrices. Therefore, you may specify a shared folder to be used even if private path loss matrices are embedded in your .atl file. Atoll uses the shared path loss matrices only when it does not find the corresponding matrices in user’s private external folder (or embedded in the .atl file). Therefore, if you want to perform coverage prediction studies based exclusively on the shared path loss matrices, you must delete the matrices stored in the private path loss folder (or embedded in the .atl file). To delete the private path loss matrices from the external folder or from the .atl file: 1. Open the Prediction folder’s context menu by right-clicking on the folder. 2. Select the Result Storage command to open the Result Storage Management dialogue. 3. Select the path loss matrices that you want to delete in the available grid. 4. Delete the selected path loss matrices using the Delete command in the button menu. Atoll accesses the shared path loss matrices in a read-only mode. If some parameters are modified in a user’s local Atoll document, Atoll automatically detects which matrices have been invalidated and recalculates them. Once you save and close your Atoll document, Atoll stores only the recalculated matrices in either the private external path loss matrices folder or embedded in the .atl file. Therefore, for example, if you change the height of the antenna at a transmitter and carry out coverage predictions, Atoll recalculates only the path loss matrices related to this transmitter and saves these in the private external folder associated with the .atl file or embed them in the file itself. The coverage prediction studies will be based on the locally recalculated matrices and other matrices read from the shared path loss folder corresponding to the other transmitters in the project. This feature is very useful when several users working on the same project want to perform coverage predictions on different areas. They can plan the network over the concerned area and store the associated path loss matrices in their private path loss matrices folder. Note: • 2.2.2.2 The pathloss.dbf and .los file formats are explained in the Technical Reference Guide. Calculating Path Loss Matrices Only This is a useful feature for the calculation administrator, in charge of keeping the shared path loss matrices up to date. It can be used by the calculation administrator for setting up the shared path loss matrices folder. 46 AT281_AM_E1 © Forsk 2009 Chapter 2: Multi-user Environments and Databases Path loss matrices can be calculated independently of coverage prediction studies. To perform path loss matrix calculation: 1. Right-click the Transmitters folder (or any of its sub-folders). 2. Select Calculations > Calculate path loss matrices from the context menu. This feature enables you to calculate path loss matrices for all active transmitters in a group. Only invalid matrices or nonexistent matrices are calculated. The Computation Zone does not influence the calculated transmitters, and path loss matrices size. Computation is performed for the entire transmitter calculation radius. To recalculate all the path loss matrices (valid or invalid): 1. Right-click the Transmitters folder (or any of its sub-folders). 2. Select Calculations > Force path loss matrix calculation from the context menu. These features are also available in the context menu of a single transmitter. It might be helpful for the calculation administrator to set up a macro to update path loss matrices automatically. Macros can enable the calculation administrator to automatically generate or update path loss matrices, based on synchronised database content. The macro could perform the following steps during its execution: 1. Start an Atoll session (Start). 2. Open the calculation administrator’s Atoll document (Open). 3. Synchronise the contents of this project with the database (Refresh). 4. Calculate path loss matrices (Calculate). 5. Save the updated Atoll document (Save). 6. Close the Atoll session (Exit). The calculation administrator can also automate a daily backup of his Atoll document. You can add a few instructions in the above macro to create a backup .atl file of the Atoll document on a daily basis. This file can be overwritten daily, whenever a new calculation is performed. A path loss update macro is available from Forsk on demand. 2.2.2.3 Working With Path Loss Matrices From Different Sources Atoll calculates path loss matrices and creates path loss matrix storage files using the propagation models assigned to transmitters. Atoll can also work with path loss matrices calculated by other tools than Atoll itself. You can use path loss matrices from other sources than Atoll in your projects. To use path loss matrices from different sources, make sure that the path loss matrices are: • • • Available in a format compatible with Atoll. File formats are described in the Technical Reference Guide. Stored at the location set in the .atl document. Valid. If the path loss matrices are not valid, Atoll will automatically start recalculating them the next time they are used. The shared path loss matrices architecture can contain path loss matrices from different sources. Caution: • 2.2.2.3.1 Path loss matrices calculated by other tools should include antenna pattern attenuation in order to be consistent with the path loss matrices calculated by Atoll. Managing Several Sources for Path Loss Matrices The Pathloss.dbf file provides the means to manage several sources of path loss matrices. This file stores, among other information, the validity status and the location (path) of the path loss matrices (.los) files for each transmitter. If a tool other than Atoll is able to provide path loss results for a part of the network under study, some users might want to work with these path loss matrices where available, and use the path loss matrices from Atoll if others are not available. © Forsk 2009 AT281_AM_E1 47 Administrator Manual Figure 2.2: Path Loss Architecture for Multiple Source Path Loss Matrices Let us assume two groups of users, where group A wants to work with the path loss matrices generated by Atoll only while group B wants to work with path loss matrices generated by a different tool for a part of the network and with path loss matrices generated by Atoll where the matrices from the other tool are not available. Let us assume that the shared path loss matrices folder where Atoll stores the generated path loss matrice 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 directly 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, the administrator will have to 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 2.2: on page 48 explains this concept. 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. 2.2.3 Shared Geographic Data and User Configurations The geographic data corresponding to the master Atoll document should be stored at a location accessible to all users. However, since all users do not need to access the same regions of the geographic data, user configuration files can be created for different groups of users and then set to be loaded by Atoll either automatically through the command line (see "Loading a User Configuration File Automatically" on page 48), or through the Atoll Management Console’s feature of user groups (see "Managing Administration File Paths" on page 147). A detailed description of user configuration files (.cfg and .geo files) is available in "User Configuration File (.cfg)" on page 69. When you create each individual user Atoll document, you can define the geographic data that needs to be accessible for each given user. Then, you can export the geographic data configuration to a .cfg file, and have Atoll load that .cfg file every time a session is launched. 2.2.3.1 Loading a User Configuration File Automatically A .cfg file present in the Atoll installation folder will be automatically read and loaded each time an Atoll session starts. You can also have Atoll load a user configuration file by adding the full path of the user configuration file to the command line following this syntax: "C:\Program Files\ForskTools\Atoll\Atoll.exe" -cfg "C:\...\configuration.cfg" 2.2.4 Master Database A master database is initially created by the administrator by exporting the contents of the master Atoll document to a database. Only the radio network data are stored in the database, i.e., sites, transmitters, antennas, station templates, micro- 48 AT281_AM_E1 © Forsk 2009 Chapter 2: Multi-user Environments and Databases wave links, propagation models, frequency bands, technology-specific parameters, inter- and intra technology neighbours, custom fields, units, coordinate systems, etc. Parameters related to geographic data files, their paths, folder configurations, study definitions, computation and focus zones, traffic maps, measurements, path loss results (matrices) and coverage areas are not stored in databases. These data can be stored in user configuration files in order to be shared between several users (see "User Configuration File (.cfg)" on page 69 for details). Traffic maps, measurements and coverage areas can be exported to external files. Finally, path loss results can be shared between users using a centralised shared path loss matrix folder. These files can also be exported to external files in order to be used in other applications. The following sections describe how to create the master database, how to create user Atoll documents from the master database, and how to perform other tasks in projects connected to a master database. Important: • • 2.2.4.1 If you are working with Oracle, go through "Using Oracle With Atoll" on page 59 before continuing. We recommend that you also familiarise yourself with the Atoll Management Console, its concepts and features described in "Atoll Management Console" on page 135. The same database server can be used to store one or more master databases corresponding to different technologies. For example, a GSM database, a UMTS database, and a microwave links database can be stored on the same database server using the same RDBMS (Oracle, for example). Creating the Master Database This procedure enables you to create the master database which will be shared between several users. An empty master database can be created by creating a new project in Atoll, defining the units, the projection and display coordinate systems to use, and then exporting this project to a database. To create a master database: 1. Open the Atoll document from which you want to create the master database. 2. Select File > Database > Export the Document to a New Database to to export this project to database. 3. In the Export to a Database dialogue, select the appropriate database type (Microsoft Access, Microsoft SQL Server, Oracle or Sybase). 4. If required, enter the user name and password of the owner of the tables. 5. When asked whether Atoll should connect the document to the new database after the export, you can either keep the new connection by selecting Yes, or keep the document disconnected, or connected to the current database, by selecting No. Atoll exports the current project to the specified database, creating all the tables automatically. Important: 2.2.4.1.1 • Before exporting the project to a database, which will create the table structure, you should make sure that all the custom fields you need are already properly defined in this project. • If you have to add an additional column in a table once you have created the database, you must do this by altering the database structure directly, and not through Atoll. Modifying the database structure in this way will enable all the users to access the modified project with the new custom fields when they open a new Atoll document from the database, or refresh an existing one. Exporting the Master Atoll Document to a Database To export a currently open Atoll document to a database: 1. Select File > Database > Export the Document to a New Database. The Export in a Database dialogue opens. 2. Select a database format for the export. 3. Choose a name and path for the database to export. © Forsk 2009 AT281_AM_E1 49 Administrator Manual Figure 2.3: Exporting an Atoll Document to a Database 4. In the user connection dialogue, enter the information required to connect to the database, such as system account, server, user name and password. Oracle, Microsoft SQL server and Sybase present their respective user verification dialogues as shown below. Figure 2.4: Connecting to an Oracle Database Figure 2.5: SQL Server Login Dialogue Figure 2.6: ODBC Data Source Dialogue 50 AT281_AM_E1 © Forsk 2009 Chapter 2: Multi-user Environments and Databases You can use the ODBC interface (used by Sybase as well) to access all databases that accept .udl files and the ODBC interface. Important: • Use the following workaround in order to be able to archive to and refresh data from a Sybase 12.5 database: 1. Open the Windows registry using regedit.exe. 2. Add a "string" called "WorkArounds2" under: 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. 5. Click Save to export the Atoll document to the database selected. 6. Click Yes when asked whether you want to connect the document to the new database. The master database is created and the master Atoll document is connected to the master database. 2.2.4.2 Setting Database Access Privileges You can assign different levels of privileges to different users for accessing (reading/writing) the various tables and views of a database in a multi-user environment. You can grant user privileges for Project, Table, Column and Row levels keeping in mind the following: • • • • Project Level: - Users trying to open a project from a database in Atoll are prompted with a list of different accessible projects. This list can be adjusted based on the user connection properties (log in) used to connect to the database. Table Level: - For consistency reasons, all the tables available in an Atoll database/project must be readable by all the users. However, Write access (INSERT, DELETE and UPDATE) can be granted on a limited number of tables. Column Level: - Similar to table level, all the columns of all the tables in an Atoll database/project must be readable/selectable by all the users. Different Write permissions can be granted or revoked for each column of all the tables. Custom columns - fields added by users in addition to the columns available in Atoll by default - can be assigned read/write permissions freely. Row Level: - Row level permissions can be set by defining custom views on Atoll tables. Access to these views can be based on user connection properties (log in), on external table references, or on the geographic locations of sites (e.g., through polygons) when using the spatial features of databases. All of these permissions can be set as regular SELECT, INSERT, UPDATE and DELETE previleges on database objects. Triggers can also be used to prevent users making certain actions on the database. Different permissions for different users can be granted directly or through database roles. Database roles enable you to define permission templates, which can then be assigned to existing or new users of the database. You can use the Atoll Management Console for defining user access rights to categories of database tables and features in the Atoll GUI. For more information on the user access rights you can manage and how to define these access rights, see "Managing User Accounts and Access Rights" on page 151. 2.2.5 User Atoll Documents User Atoll documents can be created by creating a new Atoll document from a database, as shown in the next section, loading a relevant user configuration file, and setting up the shared path loss matrices folder. If users are going to work on regions of an entire network, it is a good idea to set up those regions before creating the user projects. Once you have regionalised your radio network database, you can open Atoll documents based on the regionalised databases in order to create the user projects corresponding to those regions. 2.2.5.1 Regionalising the Master Database Regionalisation can be performed in any of the following ways: 1. Static regionalisation - Using site lists Using SQL filters Using filtering zones 2. Dynamic regionalisation - 2.2.5.1.1 Using Oracle Spatial or Oracle Locator Static Regionalisation The first 3 methods are static approaches to regionalisation. These methods require synchronisation between the master database and the created regional databases using the Atoll Management Console. In these methods, the administrator creates regional databases from the master database, based on the filters defined by the sites list, SQL, or the filtering zone. Once you have the required sites list or filtering polygon created, you can use the Atoll Management Console to © Forsk 2009 AT281_AM_E1 51 Administrator Manual create project databases corresponding to the different user groups or regions defined by the sites list, filtering zone or the SQL filter selected in the Project Database Creation wizard. For more information, see "Creating Project Databases" on page 143. Currently, these approaches are only available for Oracle databases. They will be extended to other databases in future versions of Atoll. For further information on how to create, manage, and work with sites lists and filtering zones, refer to the User Manual. SQL filters can be defined directly in the Project Database Creation wizard of the Atoll Management Console. Once you have created project databases for the different user groups, the users can work with these regional databases. They can refresh data from the regional databases, and archive their modifications in the regional databases. But, only the administrator can update the master database with the data modified by the users in the regional databases. 2.2.5.1.2 Dynamic Regionalisation This is a dynamic approach 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 while managing their access privileges according to their user connection properties. In an Atoll multi-user environment, you can create such regionalisation without having to install Oracle Spatial. You can implement this solution using Oracle Locator, which is provided in the standard Oracle installation. Specific documents explaining how to set up this regionalisation, using Oracle, in any Atoll master database are available on demand from Forsk. These documents provide scripts for creating different types of users, e.g., the administrator, advanced user, read-only user, etc., and give examples of how to set up regions in the network, and how to assign user rights to each region. So you can define access rights to each Atoll user who could be allowed to modify only the data corresponding to his region of responsibility. 2.2.5.2 Creating or Opening an Atoll Document from a Database The connection between an existing database and a new Atoll document is established when creating the project. Once connected, Atoll loads the database in your new Atoll document and disconnects it from the database. This connection to the reference database is reactivated only when necessary, thus ensuring access to the database by other users. To create or open an Atoll document based on data from an existing database: 1. Select File > New > From an Existing Database. 2. Select the type of database (Microsoft Access, Microsoft SQL Server, Oracle, Sybase, or Microsoft Data Link files .udl) and the reference database from the Open dialogue. 3. In the user connection dialogue, enter the information required to connect to the database, such as system account, server, user name, and password. 4. Click Open. The Data to Load dialogue appears. 5. Select the data to load in the dialogue and click OK to open the Atoll document from the selected database. When you create a new document from a database, you can select the data to be loaded from the database to create the document in the Data to load dialogue. You can select which Project, Site List, Custom Fields Groups, and neighbour lists to load. If you load the intra-technology or the inter-technology neighbour list, Atoll will also load the associated exceptional pairs table. Notes: 2.2.5.3 • The user connection dialogues are similar to the dialogues shown in "Exporting the Master Atoll Document to a Database" on page 49. • You should verify the paths to geographic data locations (clutter, traffic, etc.); they may no longer be valid. Opening a Project From a Database Automatically It is possible to open a project stored in a Microsoft Access or Oracle database by entering the database connection parameters (user/password/server) as command line parameters when starting Atoll. To do this, adapt the path defined in your Atoll desktop shortcut according to the following syntax: • For Oracle databases: "C:\Program Files\Forsk\Atoll\Atoll.exe" -Provider <Provider name> -Password <User password> -UserId <User account> -DataSource <server> -Project <Project account> [-cfg "C:\...\configuration.cfg"] • For Microsoft Access databases: "C:\Program Files\Forsk\Atoll\Atoll.exe" -Provider <Provider name> -DataSource "C:\...\database.mdb" [-cfg "C:\...\configuration.cfg"] 52 AT281_AM_E1 © Forsk 2009 Chapter 2: Multi-user Environments and Databases Notes: • The provider names for Microsoft Access and Oracle databases are Microsoft.Jet.OLEDB.4.0 and MSDAORA.1, respectively. You can verify the provider names through the Connection Properties dialogue. Refer to "Checking Database Connection Properties" on page 53 for information on the Connection Properties dialogue. • The brackets in "[-cfg "C:\...\configuration.cfg"]" mean that this part of the command line is optional. You can add this in order to load a user configuration file from the command line. Caution: • Provider, Password, UserId, DataSource, and Project are case sensitive in the above instructions. 2.3 Working in Multi-user Environments 2.3.1 Data Exchange Summary The following figures depict the various data exchanges that occur between the master Atoll document and the user Atoll documents and the master database. Figure 2.7: Connection Between an Existing Database and a New Atoll Document Figure 2.8: Export Data From a Current Atoll Document to a Database Figure 2.9: Archive in the Database Figure 2.10: Refresh From the Database You start your network planning process by creating the master database from the master Atoll document, and then create user Atoll documents from this master database. Users and the administrator can archive modifications in their projects to the master database from within Atoll sessions, and refresh these projects with the data from the master database. 2.3.2 Common Database Operations 2.3.2.1 Checking Database Connection Properties To check and modify the connection between your Atoll document and its reference database: • © Forsk 2009 Select File > Database > Connection Properties to open the Database Connection dialogue. AT281_AM_E1 53 Administrator Manual If the current Atoll document is connected to a database, the Database Connection dialogue informs you about the current connection properties. You can modify these connection properties and eventually connect your current Atoll document to a different database, or disconnect it completely to work in a stand-alone environment. You can also change the Read/Write access rights to the database for the current user from this dialogue. Note: • 2.3.2.2 You can use this feature to switch from one user or project account to another. If you have switched user accounts through this feature, be sure to refresh your project to update your privileges and rights related to the current connection. Loading Data From a Database You can refresh the data in your Atoll document from the database when a database connection between your Atoll document and the reference database already exists. In this way, you can take into account the modifications made by other users to the database in your Atoll document. To refresh data from the database: 1. Select File > Database > Refresh From the Database. The Refresh dialogue appears. 2. In the dialogue, you can choose to do one of the following if you have modified your document but have not yet saved those changes in the database: - - Archive your changes in the database: This option allows you to archive your changes to the server instead of refreshing your document from the server. Atoll opens the Archive assistant dialogue to help you archive the changes that you want in the database. "Archiving Data in a Database" on page 54 describes the archive procedure. Refresh unmodified data only: This option lets you keep the current modifications in your Atoll document and load the data from the database that does not impact these modifications. Cancel your changes and reload database: This option performs a complete refresh by overwriting any changes that you might have made in your Atoll document with the data from the database. 3. Under Take into account, you can select the neighbour lists, Intra-technology Neighbours and Inter-technology Neighbours, to refresh. 4. Under Modifications since the last refresh, you can choose to generate a report for the refresh process. 5. Click OK. The document is refreshed according to the selected options. If you selected to generate a report, Atoll creates a text file in CSV (Comma Separated Values) format in the temporary files system folder, and opens it. You can then rename and save the file as and where you wish. The report lists all the modifications (deletions, additions, and updates) that were stored in the database since the last time you refreshed or opened your document. Notes: 2.3.2.3 • After refreshing your document, you can run a database audit to ensure data consistency in your document. • You can instruct Atoll to automatically perform a data integrity check after you refresh data from the database. If this option is selected, Atoll will ask you whether you want to perform the integrity check after every refresh or not. For more information, see "Checking Database Consistency" on page 58. This option can be selected by adding the option described in "Running the Database Integrity Checking After Refresh" on page 107 in the Atoll.ini file. • Atoll automatically performs a primary consistency check to avoid incompatibility between redundant fields in GSM GPRS EGPRS documents. When opening a document from a database or refreshing a document from a database, Atoll updates the values of the fields "Number of TRXs" and "Channels" of the Transmitters table, with the values from the TRGs and the TRXs tables respectively. Archiving Data in a Database You can archive the modifications you have made in your Atoll document to the database with which the Atoll document is connected. Atoll’s Archive assistant offers a user-friendly interface for accurately selecting the data you want to transfer to the database. To open the Archive dialogue: • Select File > Database > Archive to the Database. The Archive dialogue lists all the modified tables and the number of modifications in each table in parentheses. Modifications can be of three types: • • • Updated: The value of a field modified in the Atoll document. Deleted: A record completely deleted from a table. Inserted: A new record added to a table. Atoll groups each of these types of modifications under the table name and shows the number of each type of modifications in parentheses. It also lists the modified fields for "Update". 54 AT281_AM_E1 © Forsk 2009 Chapter 2: Multi-user Environments and Databases Figure 2.11: Archiving Data in a Database When you select a table in the left pane, the Pending Changes pane lists all the modifications to that table. You can also select a type of modification under the table in the left pane to list all the modifications of that type only in the Pending Changes pane. Furthermore, if you select the name of the field in the left pane, the Pending Changes pane shows you the new value (from the Atoll document) and the original value (in the database) of the field. You can perform the following operations in the Archive dialogue: 1. Click Run All to archive all the changes made in the Atoll document to the database. 2. Click Run to archive only the selected pending changes in the Pending Changes pane. 3. Select an updated field in the Pending Changes pane and click the Differences button to open a dialogue showing all the fields of that record, with the modified fields highlighted. This dialogue also lists the current (in the Atoll document) and original (in the database) values for the updated fields. Figure 2.12: Differences Dialogue 4. Select a table, a modification type or a modified field in the left pane and click the Undo button to cancel any of the changes made in the Atoll document. The Archive assistant lets you accurately select the modifications to be archived in the database. Atoll displays a warning message if there are conflicts when archiving the data in the database. It is possible to resolve these conflicts using the Resolve or the Resolve All buttons. Notes: © Forsk 2009 • The Archive dialogue is only available if a record or value has been modified after the last archive or refresh. • The Archive command covers all the pending changes, including changes in the items outside the current filter. Therefore, an filtered object, which is not visible, may have its modifications archived in the database. • It is also possible to access the Archive dialogue through the context menu of the Sites folder (or its subfolders). In this case, this dialogue will only take into account sites and their dependencies (transmitters, cells, etc.). • In the case of databases which require a password (Oracle, Sybase and Microsoft SQL Server), Atoll asks for this password before the first archive. • If you want to add a new custom field in your Atoll document, you should first add the field in the database, and then update your Atoll document from the database using the Refresh feature. • If you create a custom field in an Atoll document connected to a Microsoft Access database, it will be automatically added to the connected database. This procedure does not work with other RDBMS, such as Oracle. AT281_AM_E1 55 Administrator Manual 2.3.2.4 Resolving Database Conflicts Conflicts occur when: • Two users have modified the same record. Such a conflict is caused only by differences in the same field of the same record between the database and the current Atoll document. • One user has modified a record which has been deleted by another. The following sections elaborate how these conflicts can be resolved one by one, and simultaneously as a group. 2.3.2.4.1 Resolving a Conflict on a Modified Record Let us assume that you are connected to a Microsoft Access database whose Transmitters table has been modified by another user since you last refreshed data from the database. The other user has increased the antenna height for Tx34 from 30 to 35 m. Figure 2.13: Microsoft Access Database - Transmitters Table Modified by Another User While you have also increased this height from 30 to 33 m in your project. Figure 2.14: Atoll Document - Modified Transmitters Table If you try to archive this change in the database, Atoll will detect this conflict and display a warning message. Figure 2.15: Conflict Warning Message If you click Ignore, Atoll will ignore all the conflicting records in the current table, archive the records without conflicts, and go to the next table. If you click Ignore all, Atoll will ignore all the conflicting records in all the tables and archive the records without conflicts. In the Archive dialogue, selecting an updated field in the Pending Changes pane and clicking the Differences button opens a dialogue that shows all the fields of that record, with the modified fields highlighted. It also lists the current (Atoll document) and original (database) values for the updated fields. The original values correspond to values of fields in the Atoll document at the time of the last refresh/update from the linked database. 56 AT281_AM_E1 © Forsk 2009 Chapter 2: Multi-user Environments and Databases Figure 2.16: Differences Dialogue To resolve this conflict, select the conflicting data in the Pending Changes pane of the Archive dialogue and click Resolve. Figure 2.17: Resolving Database Conflicts A dialogue opens, summarising the conflict, with highlighted rows representing the fields with conflicting data. You can select the conflicting fields whose values you want to archive by selecting the check box on the left. The database is then updated with data corresponding to the selected fields from your Atoll document. For the unchecked fields, data is loaded from the linked database. Figure 2.18: Selecting Conflicting Data to Consider Figure 2.19: Updated Microsoft Access Database After Conflict Resolution © Forsk 2009 AT281_AM_E1 57 Administrator Manual You can then verify whether the archive was successful or not by checking the database. 2.3.2.4.2 Resolving a Conflict on a Deleted Record In this case, the record you modified in your Atoll document, and are trying to update (archive) in the database, has been deleted from the linked database by another user. If you try to archive such a record, Atoll will detect this conflict and display a warning message. When you click the Resolve button to resolve this conflict, Atoll will ask you whether you want to create this deleted record in the database again or delete it from your Atoll document as well. Figure 2.20: Archiving a Conflicting Record in the Database or Deleting it From the Atoll Document Clicking Yes will create the deleted record in the database again, and clicking No will permanently delete it from your Atoll document as well. 2.3.2.4.3 Resolving All the Conflicts Simultaneously You can also resolve all the conflicts simultaneously by clicking the Resolve All button instead of the Resolve button. Resolving all the conflicts simultaneously means that you are either going to accept all the modifications made by other users in the database and update your document with values from the database, or you are going to overwrite the modifications made by other users in the database with the values from your document. When you click the Resolve All button, Atoll asks you whether you want to overwrite the values in the database with values from your document, or overwrite values in your document with values from the database. Figure 2.21: Resolving All the Conflicts Simultaneously You should only use the Resolve All feature when you are fully certain about the modifications. 2.3.2.5 Checking Database Consistency The Database Consistency tool or the Database Audit tool enables you to check data consistency between the different Atoll tables (Sites, Transmitters, etc.). This tool is useful when working either with Atoll documents linked to a master database, or with Atoll documents created from a master database but then disconnected. In these cases, the Atoll documents may contain some inconsistencies originating in the master database. To perform an audit on the database: • Select Tools > Data Audit > Integrity Check, Undefined Record Check, or Duplicate Record Check. • Integrity Check This command finds all the objects with consistency problems. Integrity problems may occur with objects that have foreign keys. Integrity problems occur with records that refer to other objects that do not exist. For example, transmitters located on sites that do not exist in the Sites table, transmitters referring to an antenna that does not exist in the Antennas table, etc.). If Atoll finds any integrity problems, it will ask if you want to delete them. Important: • • Integrity problems are corrected in the Atoll document but not in the database. You must archive your modifications in the database linked to your Atoll document to correct them in the master database. Undefined Record Check This command finds: - Sites without transmitters Transmitters without subcells, TRXs and neighbours in GSM GPRS EGPRS projects Transmitters without cells, and cells without neighbours in UMTS HSPA, CDMA2000 1xRTT 1xEV-DO projects Atoll lists all the undefined records found in the Event viewer. 58 AT281_AM_E1 © Forsk 2009 Chapter 2: Multi-user Environments and Databases • Duplicate Record Check This command finds objects that have the same identifier. For example, sites with the same name, transmitters with the same name, etc. Atoll lists all the duplicated records in the Event viewer. 2.4 Using Oracle With Atoll The following sections provide further information about using Oracle databases with Atoll. The first few sections describe some aspects of working with an Oracle database with Atoll. Then, the first appendix shows how SQL can be used to perform database customisation, and the second appendix provides a basic introduction to the Oracle architecture and concepts. Note: • 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 using either of the following two methods: i. Set the display precision of floating point values in Atoll using the Atoll.ini option described in "Setting the Display Precision of Floating Point Values" on page 98. ii. Change the field type from Float to Number and fix the number of decimal values for it in Oracle. Once this has been done, you have to refresh document data from the database in order to fix the display problem in Atoll. 2.4.1 Setting Up an Oracle Database for Atoll Atoll supports Oracle version 8.1.7 and above. This section refers to the computer where the database is stored as a server. You will perform all administration operations described in this section on the server. This section also assumes that: • • • • Oracle has already been installed on the server and clients. An empty database where data will be stored has been created, with the name "AtollDB" and the specific SID "AtollDB". An entry has been added in the tnsnames.ora file enabling communication with the Atoll database, i.e., the service name AtollDB has been defined. A tablespace called Atoll has been created. Note: • The service name, AtollDB, must be specified to: - Export an Atoll document to an Oracle database (Server = Service name) - Open an Atoll document from an AtollDB database (Server = Service name) - Use Oracle tools to manage the AtollDB database (Host name = Service name) 2.4.2 Creating a Project Account To create a project account, you must be connected to the server and must use DBA Studio. DBA Studio may be started from the server or any client on which administration tools have been installed. To create a project account: 1. Select Start > Programs > Oracle > Database Administration > DBA Studio. DBA Studio starts. 2. Select File > Add Database To Tree to view the different databases you can access. Note: • The Add Database To Tree dialogue appears automatically when you start DBA Studio for the first time. It is also available from the File menu. 3. Select the option ‘Add selected databases from your local tnsnames.ora file’ in the Add Database To Tree dialogue. 4. Choose the AtollDB service and click OK. 5. Double-click the AtollDB service name in the left pane of DBA Studio to open the connection dialogue. 6. Enter: Username: system Password: manager 7. Expand the Security subfolder, right-click the User subfolder and select Create from the context menu to create a new user. 8. Create a project account (new user) with all the administrator rights and privileges. © Forsk 2009 AT281_AM_E1 59 Administrator Manual This account will be used to store Atoll document tables. It will be the owner of these tables. Tip: It might be helpful to assign a name to this project account that indicates the type of project that you want to store (GSM GPRS EGPRS, UMTS HSPA etc.). 9. Specify Atoll as the default tablespace and choose DBA for its privileges. 2.4.3 Creating Tables Once the project account is set up, Atoll can automatically create the required tables. 1. Start Atoll. 2. Create a new project and define the units, the projection and display coordinate systems to use. 3. Select File > Database > Export the Document to a New Database to export this new project to the Oracle database. 4. In the Export to a Database dialogue, select Oracle Database as the type of database. 5. Enter the user name and password of the owner of the tables, i.e., the user name and password defined when creating the project account, and the service name defined in the tnsnames.ora file, i.e., AtollDB. Atoll exports the newly created project to the Oracle database creating all the tables automatically. 2.4.4 Creating Other User Accounts To create other user accounts, you must be connected to the server and must use DBA Studio. DBA Studio may be started from the server or any client on which administration tools have been installed. To create a user account: 1. Select Start > Programs > Oracle > Database Administration > DBA Studio. DBA Studio starts. 2. Select File > Add Database To Tree to view the different databases you can access. Note: • The Add Database To Tree dialogue appears automatically when you start DBA Studio for the first time. It is also available from the File menu. 3. Select the option ‘Add selected databases from your local tnsnames.ora file’ in the Add Database To Tree dialogue. 4. Choose the AtollDB service and click OK. 5. Double-click the AtollDB service name in the left pane of DBA Studio to open the connection dialogue. 6. Log on as the owner of the tables in order to grant privileges to other users. 7. Expand the Security subfolder, right-click the User subfolder and select Create from the context menu to create a new user. 8. Create user accounts (new user) with restricted rights and privileges. For example, you may create an account for an Atoll database administrator, with all the rights and privileges to the tables, and other user accounts with restricted rights to the tables of the project. These user accounts do not contain any tables, but only specify the access rights to the tables of the project account. 9. For each user account, enter a name and a password, specify Atoll as the default tablespace and specify user privileges. Any user can connect to the project account by providing the respective user name and password. This set-up is sufficient to use Oracle from any client computer using one of the declared user accounts and the service created on this computer. 2.4.5 Appendices 2.4.5.1 Appendix 1: Advanced Customisation You can use SQL in order to manage access to and share the Sites table (example 1), or to restrict the connection to a set of transmitters for some users (example 2). To implement the following two examples, you must log on as the owner of the tables through SQL Plus 8. Example 1: Managing Site Sharing Assumptions: • • 60 Connection string = AtollDB GSM Project account = AtollADMINGSM, password = ADMINGSM AT281_AM_E1 © Forsk 2009 Chapter 2: Multi-user Environments and Databases • • UMTS Project account = AtollADMINUMTS, password = ADMINUMTS Common Project account = AtollADMIN, password = ADMIN 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 Postcode The following example elaborates a basic concept. A much more exhaustive script, specific to the requirements of each different client, might be needed to implement the function in a comprehensive manner. Please contact Forsk for further information about this function. 1. Add a ‘POSTCODE’ field to the SITES table. SQL > alter table SITES add (POSTCODE number); 2. Rename the SITES table to be able to hide it by a view. SQL > rename SITES to PRIVATE_SITES; 3. Create a POSTCODETABLE table to link users and postcodes (one user 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; © Forsk 2009 AT281_AM_E1 61 Administrator Manual Note: • "With check option" is very important because it specifies that insert and update operations performed through the view must result in rows which the view query can select. 5. Hide the TRANSMITTERS table. SQL > rename TRANSMITTERS to PRIVATE_TRANSMITTERS; SQL > create view TRANSMITTERS as select * from PRIVATE_TRANSMITTERS where SITE_NAME in (select NAME from SITES); Note: • It is also important to hide the TRANSMITTERS table because Atoll must not select transmitters whose associated sites are not present in the SITES view. 6. Commit. SQL > commit; Caution: • 2.4.5.2 The error message “ORA-01402: view WITH CHECK OPTION - clause violation” is triggered if you try to archive a record which does not match the project. Appendix 2: Oracle Architecture Oracle can be viewed as having a nested architecture as shown in Figure 2.22: on page 62. Figure 2.22: Basic Architecture of Oracle Kernel The Kernel is the internal code that communicates with the database, and handles all the facilities of DBMS: retrieval, recovery, etc. It also optimises request execution to be more efficient, and deals with the accelerators and physical data storage exploiting the facilities of the host operating system. Data Dictionary The Data Dictionary describes the Oracle objects in detail. It is used for the documentation and management of these objects. It contains the schema of the tables and views. The description of database objects is often called metadata (data about data). The dictionary is a set of tables and views manipulated through SQL. Users can look at the content of the tables through a series of views. Only the database administrator can actually manipulate the dictionary directly (see Figure 2.23: on page 62). Figure 2.23: Data Dictionary 62 AT281_AM_E1 © Forsk 2009 Chapter 2: Multi-user Environments and Databases SQL Layer The SQL Layer serves as the interface between the kernel and the tools of the external layer. Every data access operation is expressed in SQL. SQL commands include: • • • Data Definition commands to define the schema Data Manipulation commands to manipulate the contents of the schema Data Control commands to grant users privileges and access rights External Layer The external layer is aset of tools that enable all the facilities provided by the three basic underlying layers to be used easily. It is basically an applications development environment. This is the interactive interface to SQL, so you can put SQL commands directly to the database. Oracle Objects Oracle manipulates many objects, of which the most important are: • • • • • Tables Views Integrity constraints Users and their privileges Accelerators on tables (indexes, clusters) – these are data structures that provide fast access paths to tables, like an index in a book. Figure 2.24: Objects Manipulated by Oracle In Oracle, a user cannot explicitly define an object called a database. A user’s database is the set of tables and views that a user has access privileges to. Users may access tables and views other than those created by themselves by prefixing them with the name of that user, provided they have been granted the privilege of doing so. In Figure 2.24: on page 63, user1 has created two tables, table1 and table2, and a view view1. The two tables are grouped in the same cluster, which means that they are stored internally close together on the disk because they are often accessed together. This same user can access table table3 via view view2. User3 has created the table table3, which uses an index (a data structure which makes accessing data in it faster), and two views view2 and view3 on this table. Finally, user2 has created no table or view, but has the privilege of accessing table table2 by prefixing it with the name of user1. User Privileges Users are defined by a name (unique), a password and a set of privileges. All users can create views and organize which users have permission to use the views. You can build tables for your databases as follows: 1. 2. 3. 4. Design your tables. User A creates the tables. User A grants permission to another user B to access the tables using the SQL GRANT statement. User B will have to use user A’s tables by prefixing the table name with user A’s Oracle user name. Databases and Tablespaces There can be only one database, managed by the database administrator. It is divided into Tablespaces. Tablespaces are partitions where Oracle objects are stored. Tablespace SYSTEM is where the Data Dictionary is held (Figure 2.25: on page 64). © Forsk 2009 AT281_AM_E1 63 Administrator Manual Figure 2.25: Databases and Tablespaces 2.5 Setting Up Databases for Co-Planning Atoll uses different data structures for its different technology modules. When you use Atoll with a database, Oracle for example, you create and use separate data structures for each technology. In this section, the example given is a UMTS network being co-planned with a GSM network. This procedure can be adapted to work with other technology modules as well. The Sites table must be shared between GSM and UMTS databases before starting to work on the co-planning project. This means that the sites bearing both GSM and UMTS sectors should be defined only once in a shared Sites table. Therefore, the Sites tables in the GSM and UMTS databases must be views of a common Sites table. 2.5.1 Sharing Tables in Oracle, SQL Server, or Sybase If you have a GSM-UMTS co-planning project, and have separate Atoll documents for your GSM and UMTS networks, you can create views to share tables that have common structures. Such tables include the Sites and Antennas tables. We assume that the sites in the GSM and in the UMTS documents are identical. We also assume that two users, named GSMUser and UMTSUser in this example, have been created in the database. To set up a single Sites table for your GSM-UMTS co-planning project: 1. Open the GSM document in Atoll. 2. Delete all the transmitters from the Transmitters table 3. Delete all the sites from the Sites table. 4. Export the GSM document to the database by entering the user name and password for GSMUser. 5. Log in as GSMUser to the database. 6. Delete the Sites table. 7. Open the UMTS document in Atoll. 8. Export the UMTS document to the database by entering the user name and password for UMTSUser. 9. Log in as UMTSUser to the database. 10. Right-click the Sites table and select Create a View from the context menu. The Create View dialogue appears. a. Enter Sites as the view name. b. Enter GSMUser as the name of the schema which will contain the view. c. Select Table as object type. d. Enter UMTSUser as the name of the schema you want to use. e. Select Sites as the object used to model the view. 11. Click Create. The view of the Sites table from UMTSUser is created in GSMUser. The GSMUser Sites table is now the same as UMTSUser Sites table. You have to set user privileges for the Sites view in GSMUser, to allow each user to Import, Update, Delete, and Select. 2.5.2 Sharing Tables Microsoft Access If you have a GSM-UMTS co-planning project, and have separate Atoll documents for your GSM and UMTS networks, you can export these documents to Microsoft Access databases, create a link between the databases, and share the tables that have common structures. Such tables include the Sites and Antennas tables. To set up a single Sites table for your GSM-UMTS co-planning project: 1. Open the GSM document in Atoll. 2. Delete all the transmitters from the Transmitters table and sites from the Sites table. 3. Export the GSM document to an Microsoft Access the database (GSM.mdb). 4. Open GSM.mdb in Microsoft Access. 5. Delete the Sites table. 64 AT281_AM_E1 © Forsk 2009 Chapter 2: Multi-user Environments and Databases 6. Open the UMTS document in Atoll 7. Export the UMTS document to an Microsoft Access database (UMTS.mdb). 8. Open GSM.mdb in Microsoft Access. 9. Select File > Get External Data > Link Tables. 10. Select UMTS.mdb in the Link dialogue. 11. Click the Link button. 12. Select the Sites table in the Link tables dialogue. 13. 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 information. 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 8.2: on page 222 shows the relations of the Sites table with other tables in a GSM database. Important: • 2.5.3 Make sure that you use the UMTS Sites table and not the GSM Sites table. The Sites table in UMTS documents contains additional information compared to the Sites table in GSM documents. Therefore, you delete the Sites table from the GSM database rather than from the UMTS database. Setting Up Shared Antenna Parameter Synchronisation You can set up a synchronisation mechanism for updating the shared antenna parameters in the main/linked document when changes to these are made in the linked/main document. The shared antenna parameters include the site location (X and Y coordinates), the antenna’s position relative to the site (Dx and Dy), antenna height, azimuth, and mechanical tilt. This synchronisation is optional and works when an optional field named SharedMast has been added in the Transmitters tables of both the main and the linked documents. The SharedMast field should be a Text field with length (recommended) not more than 10 to 15 characters. Transmitters of the main and the linked documents that have the same site locations (X and Y coordinates) and have the same contents in the SharedMast field are considered by Atoll to share antennas. For such transmitters, modifications made in one document are automatically propagated to the other document. The SharedMast field should be left blank for transmitters that do not share antennas. 2.5.3.1 Ensuring Database Consistency for Shared Antenna Parameters 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 document, it may create inconsistencies between the shared antenna parameters in both networks. There can be two ways to ensure database consistency: 1. Automatically save or archive both documents together: This means that if a user archives the UMTS document, or saves the UMTS document, Atoll automatically archives the GSM document, or saves the GSM document, as well, and vice-versa. This can be done using a macro with Atoll which runs in the background and is triggered by the archive or the save operations. This will ensure that the GSM and UMTS documents have consistent databases. However, this solution is based on the assumption that a clear process has been set up to avoid unwanted archive and save operations. 2. Add a synchronisation trigger in the databases: To avoid inconsistency, you can add a synchronisation trigger in the database which automatically updates the shared antenna parameters in the GSM document when the UMTS document is archived, and vice versa. Use a global variable to avoid a repetitive loop. If a global variable is not used, the recursive process may initiate an infinite loop that keeps updating the shared antenna parameters in the two databases. An example of a synchronisation trigger is provided below. Sample Macro: Example of Synchronisation Trigger --AS GLOBAL-connect GLOBAL/N@ATOLL9I; CREATE or replace PACKAGE mutation_prevention AS fire_trigger varchar2(5) := 'YES'; END mutation_prevention; / grant execute on mutation_prevention to gsm with grant option; grant execute on mutation_prevention to umts with grant option; --AS GSM-- © Forsk 2009 AT281_AM_E1 65 Administrator Manual connect GSM/N@ATOLL9I; GRANT SELECT, DELETE, UPDATE, INSERT ON TRANSMITTERS TO UMTS WITH GRANT OPTION; ALTER TABLE TRANSMITTERS ADD (SHAREDMAST VARCHAR2(50)); ALTER TABLE TRANSMITTERS ADD CONSTRAINT UNIQUE_SHAREDMAST UNIQUE (SHAREDMAST); --AS UMTS-connect UMTS/N@ATOLL9I; GRANT SELECT, DELETE, UPDATE, INSERT ON TRANSMITTERS TO GSM WITH GRANT OPTION; ALTER TABLE TRANSMITTERS ADD (SHAREDMAST VARCHAR2(50)); ALTER TABLE TRANSMITTERS ADD CONSTRAINT UNIQUE_SHAREDMAST UNIQUE (SHAREDMAST); --AS GSM-connect GSM/N@ATOLL9I; CREATE OR REPLACE TRIGGER SYN_TRANSMITTERS BEFORE UPDATE OF DX,DY,HEIGHT,AZIMUT,TILT ON TRANSMITTERS FOR EACH ROW BEGIN IF (GLOBAL.mutation_prevention.fire_trigger = 'YES') THEN GLOBAL.mutation_prevention.fire_trigger := 'NO'; UPDATE UMTS.TRANSMITTERS T SET T.DX = :NEW.DX, T.DY = :NEW.DY, T.HEIGHT = :NEW.HEIGHT, T.AZIMUT = :NEW.AZIMUT, T.TILT = :NEW.TILT WHERE T.SHAREDMAST=:NEW.SHAREDMAST AND :NEW.SHAREDMAST IS NOT NULL; GLOBAL.mutation_prevention.fire_trigger := 'YES'; END IF; END; / --AS UMTS-connect UMTS/N@ATOLL9I; CREATE OR REPLACE TRIGGER SYN_TRANSMITTERS BEFORE UPDATE OF DX,DY,HEIGHT,AZIMUT,TILT ON TRANSMITTERS FOR EACH ROW BEGIN IF (GLOBAL.mutation_prevention.fire_trigger = 'YES') THEN GLOBAL.mutation_prevention.fire_trigger := 'NO'; UPDATE GSM.TRANSMITTERS T SET T.DX = :NEW.DX, T.DY = :NEW.DY, T.HEIGHT = :NEW.HEIGHT, T.AZIMUT = :NEW.AZIMUT, T.TILT = :NEW.TILT WHERE T.SHAREDMAST=:NEW.SHAREDMAST AND :NEW.SHAREDMAST IS NOT NULL; GLOBAL.mutation_prevention.fire_trigger := 'YES'; END IF; END; / 66 AT281_AM_E1 © Forsk 2009 Chapter 3 Administration Files This chapter details the configuration, initialisation and other standard administration files that can be used with Atoll to customise the operation and working according to the user’s requirements. Atoll RF Planning & Optimisation Software Administrator Manual 68 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files 3 Administration Files Three files can be used by the administrator to manage various aspects of Atoll’s operation and working environment. This chapter describes these administration files in detail. These administration files are: • Configuration files (.cfg) These files include: - • The user configuration files which can contain paths and description of geographic data, computation zone definition, filter/sort/group criteria applied to folders, display settings of objects, prediction study list, customized studies, path to access macros, and AFP settings. Other configuration files which can contain print setup settings, table import/export settings, coverage prediction report settings, CW measurement import settings, and drive test data import settings. The Atoll initialisation file (.ini) This file can contain site and transmitter naming conventions, calculation settings (modelling method of antenna patterns) and other options (list of calculation servers, etc.). • An .xml study file This file (default name : Studies.xml) describes prediction studies with customized settings. Several users can share a common working environment using these files. The administrator can set up different administration files and configure access to these files for different groups of users through the Atoll Management Console. "Managing Administration File Paths" on page 147 describes how to do this. These files are not necessary to work with Atoll. They are additional tools that can be used to customise and administer Atoll’s environment and function. 3.1 User Configuration File (.cfg) The user configuration file can be used to store parameters. It is a UTF-8 encoded XML (eXtensible Markup Language) file with either a .cfg or a .geo extension. This file can contain the following information: • Geographic data set: - Paths to imported geographic data (including vectors, traffic maps, clutter maps, DEM, images, and any other geographic data) - Display settings for geographic data maps (display type, visibility scale, transparency, tips text, etc.) - Descriptions of clutter classes (code, name, colour, height, standard deviations, indoor losses, orthogonality factor, % Pilot Finger of each clutter class, and the default standard deviations and indoor losses) - Descriptions of traffic maps (raster maps, vector maps, sector maps, etc.) - Other types and formats of geographic data (customer density, etc.) • Definitions of the computation and focus zones • Folder configurations: - Sort/group/filter criteria (as saved by the user as well as currently applied sort/group/filter configurations) and display settings of Sites, Antennas, Transmitters, propagation models, and other folders - Filtering zone and display settings of radio data folders (including measurement display) • List of coverage prediction studies: - List of prediction studies available in the Predictions folder and their settings, such as general information (name, comments, group, sort order, and filters), study conditions, and display settings (display type, visibility scale, add to legend option, tips text, transparency level, etc.) • Automatic neighbour allocation parameters: - Settings specified when starting a automatic neighbour allocation • AFP configuration (GSM GPRS EGPRS projects): - Settings specified when starting an AFP session as well as calculation parameters used for interference histograms • Automatic scrambling code allocation parameters (UMTS HSPA and TD-SCDMA projects): - Settings specified when starting an automatic scrambling code allocation • Automatic PN offset allocation parameters (CDMA2000 1xRTT 1xEV-DO projects): - Settings specified when starting an automatic PN offset allocation • Microwave Radio Links parameters • Paths to files containing macros User configuration files containing information about macros can be loaded even when there is no .atl file open in Atoll. Once a macro is loaded in Atoll, it remains active throughout the Atoll session. You can open and close .atl files and still keep the macro loaded in Atoll. You can unload macros through the specific Add-ins and Macros dialogue available by selecting Add-ins and Macros command from the Tools menu. All of the parameters and settings mentioned above are not stored in the database. Therefore, the user configuration files provide an efficient means of sharing these settings. You can create a user configuration file with the required information, which can later be shared by a number of users who can simply import it in their Atoll documents to benefit from these pre- © Forsk 2009 AT281_AM_E1 69 Administrator Manual defined settings. Moreover, users can carry out any modifications in their respective Atoll documents without changing the reference user configuration for the others. 3.1.1 Creating a User Configuration File A user configuration file is a UTF-8 encoded XML file that can be viewed in any XML-ready application, such as Internet Explorer or XMLSpy. It is recommended to create user configuration files in Atoll to ensure that they have the correct structure and can be later opened and read again by Atoll. However, it is possible to modify the contents of these files in an XML editor in order to make specific changes, such as updating the paths to geographic data. You can create user configuration files from Atoll by exporting user configurations to files as explained below. 3.1.1.1 Exporting User Configurations to User Configuration Files User configurations can be saved and shared between users through user configuration files. Once a user configuration is exported to a user configuration file, the user configuration file can be loaded by a number of users who are working on the same project under similar conditions. Before exporting a user configuration to a user configuration file, make sure that you have correctly defined and set up the required settings and information in your Atoll document. To export a user configuration to a user configuration file: 1. Select Tools > User Configuration > Export to open the User Configuration Export dialogue. 2. Select the options you want to export to the user configuration file in this dialogue and click OK. 3. Specify a file name for the user configuration file and choose a location to save it. 4. Click Save to save the user configuration file. Notes: • Atoll can store the path of any imported geographic data with any of the supported formats. Make sure that vectors have the same coordinate system as the raster maps. • Projection and display coordinate systems are stored in the database and not in the user configuration file. • Atoll proposes a .geo file extension when exporting a user configuration containing only a geographic data set and computation and focus zones. If other information is also selected to be exported to the user configuration file, Atoll proposes the .cfg extension. • Macros can be exported to user configuration files even when there is no Atoll document open, since a macro is linked to an Atoll session and not to a specific Atoll document. • Simulation settings, such as parameters entered when creating simulations or simulation display properties, are not stored in user configuration files. • It is also possible to save the display configuration of a single CW measurement path or a single drive test data path in a user configuration file in order to apply it to other paths. This can be done directly from the measurement path properties dialogue. 3.1.2 Loading User Configuration Files 3.1.2.1 Loading User Configuration Files With Atoll Three methods can be used to automatically load a user configuration file when users create a new Atoll document (by selecting File > New > From a Document Template or File > New > From an Existing Database): 1. Use “C:\Program Files\Forsk\Atoll\Atoll.exe -cfg <configuration_file>” as the application path for Atoll’s desktop shortcut. Note: • You can replace "C:\Program Files\Forsk\Atoll\" with your specific path to the location of Atoll.exe. 2. Name the user configuration file to be loaded automatically "Atoll.cfg" and place it in the Atoll installation directory. Note: • This method will not work if Atoll is started with a "-cfg" option loading an alternate user configuration file. 3. Use the Atoll Management Console to specify the user configuration file to be loaded for each user. This depends on the user connection properties. For more information, see "Managing Administration File Paths" on page 147. 70 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files 3.1.2.2 Importing User Configurations From User Configuration Files User configuration files can be used to share data between users who import the same user configuration. To import a user configuration from a user configuration file: 1. Select Tools > User Configuration > Import to open the User Configuration Import dialogue. 2. Select the user configuration file (.cfg or .geo) you want to import and click Open. 3. In the User Configuration dialogue, select the items you want to import from the user configuration file to your Atoll document. 4. Click OK to import the user configuration. If you are importing a user configuration file that contains a geographic data set, a coverage prediction study list, or customized study defintions, Atoll checks if any geographic data maps, or prediction studies are available in the Atoll document. If it finds a geographic data map or coverage prediction study in the project, Atoll asks the user whether to "Reset Existing Geo Data", or "Reset the Existing Prediction List". You can opt to remove or keep the existing geographic maps or the coverage prediction studies in the Atoll document when loading the geographic data set or the coverage prediction study list from the user configuration file. If you are importing a user configuration file that contains a folder configuration, Atoll checks if folder configurations already exist in the Atoll document. If folder configurations already exist, Atoll adds the folder configurations from the user configuration file to the Atoll document. It also applies the configurations defined in the user configuration file to folders. You can only import a user configuration file in this manner if Atoll’s desktop shortcut does not point to another user configuration file through “-cfg <configuration_file>”. If a configuration file called Atoll.cfg is located in the Atoll installation directory, it is automatically loaded when users create a new Atoll document (by selecting File > New > From a Document Template or File > New > From an Existing Database). Notes: 3.1.3 • You can import macros in user configuration files only when no Atoll document is open, because a macro is linked to an Atoll session and not to an Atoll document. • If you import a user configuration file containing a macro when no Atoll document is open, only the macro is imported; all user configuration information is ignored. • If you import a user configuration file containing a macro into an open Atoll document, only user configuration information is imported; the macro will not be imported. Setting Up Configuration Files for Co-Planning You can set up user configuration files for your co-planning project, i.e., two different technology documents, with, for example, a pre-defined transmitter symbol, colours, symbol sizes on the map, tool tip text, and labels, etc. This will facilitate the work of the end-users by providing them with pre-defined display parameters. 1. Set display parameters for both technology documents. 2. Export a user configuration files for each technology document. 3. Using the Atoll Management Console, assign the user configuration files to the group of users working on the coplanning project. For more information on managing Atoll administration file paths using the Atoll Management Console, see "Managing Administration File Paths" on page 147. 3.1.4 User Configuration File Contents The examples provided below for each parameter set can help understand the format and function of the user configuration files. 3.1.4.1 Geographic Data Set The following parameters are saved in the .geo or .cfg files for various geographic data types: © Forsk 2009 • <DegreeFormat>: Format used to display degrees, minutes, and seconds for geographic coordinate systems • Population, Rain, Vector Traffic Maps, Other Vector Layers: - <Name>: Name of the folder - <Display>: (Different combinations of the following parameters exist in different display settings.) - Display type <type>, selected field <FieldSelector>, transparency level <opacity> (not applicable for vectors), 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: <Min>, <Max>, <Legend>, <MainColor>, <SecondaryColor>, <LineStyle>, <LineWidth>, and <FillStyle> - <AddToLegend>: Add to legend option checked or not - <Type>: Data type properties, such as <Name>, <Formats>, <Type>, and <Integrable> - <File>: Contains the file format, path, coordinate system information. AT281_AM_E1 71 Administrator Manual - <Format> of and <Path> to linked files, if any Coordinate system information for vector format data including: <CoordinateSystemName>, <CoordinateSystemCode>, <EllipsoidCode>, <EllipsoidMajorRadius>, <EllipsoidMinorRadius>, <DatumCode>, <DatumShiftX>, <DatumShiftY>, <DatumShiftZ>, <DatumRotationX>, <DatumRotationY>, <DatumRotationZ>, <DatumScaleFactor>, <ProjectionMethod>, <ProjectionZone>, <ProjectionLongitudeOrigin>, <ProjectionLatitudeOrigin>, <ProjectionFalseEasting>, <ProjectionFalseNorthing>, <ProjectionScaleFactor>, <ProjectionFirstParallel>, <ProjectionSecondParallel>, and <ProjectionAngle> • Clutter Classes: - <Name>: Name of the folder - <Display>: (Different combinations of the following parameters exist in different display settings.) - Displate type <type>, selected field <FieldSelector>, transparency level <Opacity>, visibility flag <visible>, and visibility range between <minZoom> and <maxZoom> - <Items> properties, such as for each item: <Min>, <Max>, <Legend>, <MainColor>, <SecondaryColor>, <LineStyle>, <LineWidth>, and <FillStyle> - <AddToLegend>: Add to legend option checked or not - <Attributes>, such as: <records> and <fields>, which are, - GSM GPRS EGPRS: CODE, COLOR, NAME, HEIGHT, STDDEV, COVERI_STDDEV, INDOOR, TX_DIV_GAIN - UMTS HSPA: CODE, COLOR, NAME, HEIGHT, STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, INDOOR, ALPHA, FORTHO - CDMA2000 1xRTT 1xEV-DO: CODE, COLOR, NAME, HEIGHT, STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, INDOOR, ALPHA, FORTHO - TD-SCDMA: CODE, COLOR, NAME, HEIGHT, STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, INDOOR, FORTHO_UL, FORTHO_DL - WiMAX 802.16d and WiMAX 802.16e: CODE, COLOR, NAME, HEIGHT, STDDEV, COVERI_STDDEV, INDOOR, MIMO_GAIN_FACTOR, STTD_OFFSET_DL, STTD_OFFSET_UL - LTE: CODE, COLOR, NAME, HEIGHT, STDDEV, COVERI_STDDEV, INDOOR, MIMO_GAIN_FACTOR, DIV_GAIN_OFFSET_DL, DIV_GAIN_OFFSET_UL - Microwave Radio Links: CODE, COLOR, NAME, HEIGHT, STDDEV, COVERI_STDDEV, INDOOR - <DefaultValues>, for the fields stated above. • Clutter Heights and Digital Terrain Models: - <Name>: Name of the folder - <Display>: (Different combinations of the following parameters exist in different display settings.) - Displate type <type>, selected field <FieldSelector>, transparency level <opacity>, visibility flag <visible>, and visibility range between <minZoom> and <maxZoom> - <Items> properties, such as for each item: <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 <RainDensity> or <Vectors> <Name>Population</Name> // or <Name>Rain</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> 72 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files <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> <Type>800</Type> <Integrable>1</Integrable> </Type> <Files/> </Population> // or </RainDensity> 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"/> © Forsk 2009 AT281_AM_E1 73 Administrator Manual <field length="4" type="real" name="STDDEV"/> <field length="4" type="real" name="COVERI_STDDEV"/> <field length="4" type="real" name="INDOOR"/> </fields> <records/> </Attributes> <Name>Clutter Classes</Name> <AddToLegend>0</AddToLegend> <DefaultValues> <STDDEV> <DefaultValue></DefaultValue> </STDDEV> <COVERI_STDDEV> <DefaultValue></DefaultValue> </COVERI_STDDEV> <INDOOR> <DefaultValue></DefaultValue> </INDOOR> </DefaultValues> </ClassifiedClutter> <Altitudes> // or <BuildingHeights> <Name>Digital Terrain Model</Name> // or <Name>Clutter Height</Name> <Display> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> <Type>ByIntervals</Type> <FieldSelector>0</FieldSelector> <Opacity>50</Opacity> <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> 3.1.4.2 Folder Configuration The folder configurations for the following folders are stored in the .cfg files: • 74 Sites folder: AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files - - © Forsk 2009 <Name>: Name of the folder <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>: <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 transmitter’s azimuth or an absolute value - <Clutter>: For each <Class>, its <Code> and whether it is in the <Filter> or not - <Advanced>: Any advanced filter used for filtering - <PathLosses>: Path loss tuing parameters, i.e., <ParallelAxisRadius> and <PerpendicularAxisRadius> - <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> AT281_AM_E1 75 Administrator Manual - <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 folders: - <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> and <PerpendicularAxisRadius> - <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> <Color>0 0 0</Color> <BackColor>255 255 255</BackColor> <Style>33</Style> </LabelFont> <Items> <Item> <Value>Vendor</Value> <Legend>Vendor</Legend> 76 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files <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> </DataTips> </Display> <AddToLegend>1</AddToLegend> <DefaultConfiguration/> </Transmitters> // or </MWMultiHops> // or </MWHubs> <MWLinks> <Name>Links</Name> <Display> <minZoom>500</minZoom> © Forsk 2009 AT281_AM_E1 77 Administrator Manual <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> <CWMeasurements> <DefaultConfiguration> <Distance> <Min>0.</Min> <Max>1000.</Max> </Distance> <DistanceUnit>0</DistanceUnit> <Measure> <Min>-105.</Min> <Max>-90.</Max> 78 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files </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> </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> <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> © Forsk 2009 AT281_AM_E1 79 Administrator Manual <Item>M (dBm)</Item> </Labels> </Display> </CWMeasurements> <TestMobileData> <DefaultConfiguration> <Clutter> <Class> <Code>1</Code> <Filter>Yes</Filter> </Class> </Clutter> <Advanced></Advanced> </DefaultConfiguration> <PathLosses> <ParallelAxisRadius>200.</ParallelAxisRadius> <PerpendicularAxisRadius>100.</PerpendicularAxisRadius> </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> <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/> 80 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files </PropagationModels> // or </SmartAntennasModels> </FoldersConfigurations> </Atoll> 3.1.4.3 Computation and Focus Zones The .cfg files store the coordinates of the vertices of the computation and focus zone polygons, i.e., the points forming these polygons. The first and the last points have the same coordinates. The following sample has rectangular zones of the exact same size. Sample: <?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> 3.1.4.4 Coverage Prediction Study List The .cfg files can store the parameters used for calculating the coverage prediction studies available in an .atl file, i.e., all the coverage prediction studies available under the Predictions folder. The Atoll administrator can create a .cfg file with the most common coverage prediction studies. These coverage prediction studies can be different depending upon different user groups working on Atoll. Each user group can be assigned a different .cfg file with different coverage prediction study lists using the Atoll Management Console as described in "Managing Administration File Paths" on page 147. In this way, whenever users will open their Atoll sessions, they will have the predefined coverage prediction studies already available and configured under the Predictions folder. 3.1.4.5 Automatic Neighbour Allocation Parameters There are two or three kinds of neighbours, depending on the technology. For example, in GSM GPRS EGPRS, WiMAX 802.16e, and LTE projects, there are intra-technology neighbours (within the same .atl file) and inter-technology neighbours (between two different .atl files, which can be of the same technology or any other technology, such as UMTS HSPA or CDMA2000). In UMTS HSPA, TD-SCDMA, and CDMA2000 1xRTT 1xEV-DO projects, there are inter-carrier neighbours (neighbouring transmitters using different carriers within the same .atl file), intra-technology neighbours (within the same .atl file), and inter-technology neighbours (between two different .atl files, which can be of the same technology or any other technology, such as GSM GPRS EGPRS). The .cfg files store the automatic allocation parameters for all kinds of neighbour allocations. These parameters are stored under three different sections: • • • <ANP_options>: Intra-technology neighbour allocation parameters <ANP_IT_options>: Inter-technology neighbour allocation parameters <ANP_IL_options>: Inter-carrier (or inter-layer) neighbour allocation parameters The stored parameters are: • © Forsk 2009 Parameters common to all technologies: - <numMax>: Maximum number of neighbours to allocate - <useCoSite>: Force co-site transmitters/cells as neighbours or not - <useAdjacent>: Force adjacent transmitters/cells as neighbours or not - <symetric>: Force symmetry between neighbours or not - <keepNeighbs>: Reset existing neighbours or keep them AT281_AM_E1 81 Administrator Manual - <MaxDist>: Maximum distance between sites <PercentCoverage>: Coverage conditions: Minimum percentage of covered area <UseShadowing>: Coverage conditions: Take shadowing into account or not <reliability>: Coverage conditions: Cell edge coverage probability <applyConstraints>: Force exceptional pairs as neighbours or not <covBased>: Not implemented yet <minCov>: Neighbour importance: minimum factor for coverage <maxCov>: Neighbour importance: maximum factor for coverage <minAdj>: Neighbour importance: minimum factor for adjacency <maxAdj>: Neighbour importance: maximum factor for adjacency <minCos>: Neighbour importance: minimum factor for co-site <maxCos>: Neighbour importance: maximum factor for co-site <resolution>: Resolution used for coverage calculation for overlapping (-1 means the default resolution defined in the properties of the Predictions folder is used) <UseIndoor>: Coverage conditions: Use indoor losses defined per clutter class or not • Parameters specific to GSM GPRS EGPRS: - <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 Note: • • The parameters <EcIoMin>, <usePmax>, and <PerCentMaxPower> are not saved in the <ANP_IL_options> section of the cfg files created from CDMA2000 1xRTT 1xEV-DO projects. Parameters specific to WiMAX 802.16e and LTE: - <HOStart>: The handover start margin - <HOEnd>: The handover end margin Sample: <?xml version="1.0" encoding="UTF-8"?> <Atoll> <ANP_options> // or <ANP_IT_options> or <ANP_IL_options> <HOStart>0</HOStart> <HOEnd>500</HOEnd> <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>1</UseIndoor> <deltaMax>1200</deltaMax> <applyConstraints>0</applyConstraints> 82 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files <covBased>1</covBased> <minCov>100</minCov> <maxCov>3000</maxCov> <minAdj>3000</minAdj> <maxAdj>6000</maxAdj> <minCos>6000</minCos> <maxCos>10000</maxCos> <EcIoMin>-1400</EcIoMin> <usePmax>0</usePmax> <PerCentMaxPower>5000</PerCentMaxPower> <EcIoMax>-700</EcIoMax> <useEcIoMax>0</useEcIoMax> </ANP_options> // or </ANP_IT_options> or </ANP_IL_options> </Atoll> 3.1.4.6 Automatic Frequency Planning Parameters The following automatic frequency planning options (GSM GPRS EGPRS documents) can be stored in the .cfg file: • • • • • • • • • • • • • • • • • • • • • <defSeparations__CONF_CO_SITE_BB>: Default co-site separation rule for two BCCH type TRXs. <defSeparations__CONF_CO_CELL_BB>: Default co-transmitter separation rule for two BCCH type TRXs. <defSeparations__CONF_NEIGH_BOUR_BB>: Default neighbour separation rule for two BCCH type TRXs. <defSeparations__CONF_CO_SITE_BT>: Default co-site separation rule for a BCCH and a TCH type TRX. <defSeparations__CONF_CO_CELL_BT>: Default co-transmitter separation rule for a BCCH and a TCH type TRX. <defSeparations__CONF_NEIGH_BOUR_BT>: Default neighbour separation rule a for BCCH and a TCH type TRX. <defSeparations__CONF_CO_SITE_TT>: Default co-site separation rule for two TCH type TRXs. <defSeparations__CONF_CO_CELL_TT>: Default co-transmitter separation rule for two TCH type TRXs. <defSeparations__CONF_NEIGH_BOUR_TT>: Default neighbour separation rule for two TCH type TRXs. <allocType>: The parameters/resources to be allocated (memorised from the last AFP session) <freezeState>: Last minute resource freezing options available in the AFP launch wizard <numMinutes>: Target time alloted to the AFP <useDTX>: Consider the effect of discontinuous transmission or not <dtxVocalFactor>: Voice activity factor for discontinuous transmission <AfpBasedOnInterference>: Load all potential interferers or not <AfpBasedOnSeparations>: Load all the subcells potentially involved in separation constraints or not <IM_calculate__WithTraffic>: Whether traffic spreading is uniform or based on the maps used in the default traffic capture (for interference matrices calculation) <IM_calculate__BestServerZoneMargin>: Margin in case of Best signal level per HCS layer (for interference matrices calculation) <IM_calculate__ServiceZoneType>: All or Best signal level per HCS layer (for interference matrices calculation) <IM_calculate__reliability_X_10000>: Cell edge coverage probability (for interference matrices calculation) <TakeTfFromCapt>: Whether traffic loads are read from the default traffic capture or from the Subcells table Sample: <?xml version="1.0" encoding="UTF-8"?> <Atoll> <AFP_options> <defSeparations__CONF_CO_SITE_BB>2</defSeparations__CONF_CO_SITE_BB> <defSeparations__CONF_CO_CELL_BB>3</defSeparations__CONF_CO_CELL_BB> <defSeparations__CONF_NEIGH_BOUR_BB>2</defSeparations__CONF_NEIGH_BOUR_BB> <defSeparations__CONF_CO_SITE_BT>2</defSeparations__CONF_CO_SITE_BT> <defSeparations__CONF_CO_CELL_BT>3</defSeparations__CONF_CO_CELL_BT> <defSeparations__CONF_NEIGH_BOUR_BT>1</defSeparations__CONF_NEIGH_BOUR_BT> <defSeparations__CONF_CO_SITE_TT>1</defSeparations__CONF_CO_SITE_TT> <defSeparations__CONF_CO_CELL_TT>2</defSeparations__CONF_CO_CELL_TT> <defSeparations__CONF_NEIGH_BOUR_TT>1</defSeparations__CONF_NEIGH_BOUR_TT> <allocType>315</allocType> <freezeState>0</freezeState> <numMinutes>1000</numMinutes> © Forsk 2009 AT281_AM_E1 83 Administrator Manual <useDTX>0</useDTX> <dtxVocalFactor>70</dtxVocalFactor> <AfpBasedOnInterference>1</AfpBasedOnInterference> <AfpBasedOnSeparations>1</AfpBasedOnSeparations> <IM_calculate__WithTraffic>0</IM_calculate__WithTraffic> <IM_calculate__BestServerZoneMargin>5</IM_calculate__BestServerZoneMargin> <IM_calculate__ServiceZoneType>1</IM_calculate__ServiceZoneType> <IM_calculate__reliability_X_10000>7500</IM_calculate__reliability_X_10000> <TakeTfFromCapt>1</TakeTfFromCapt> </AFP_options> </Atoll> 3.1.4.7 Automatic Scrambling Code Allocation Parameters The automatic scrambling code allocation parameters (UMTS HSPA and TD-SCDMA documents) that can be stored in the .cfg files are: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • <MinEcI0>: Minimum Ec/I0 constraint (not used in TD-SCDMA) <margin>: Ec/I0 margin (not used in TD-SCDMA) <reliability>: Cell edge coverage probability (not used in TD-SCDMA) <DistanceMin>: Default re-use distance <Strategy0>: Clustered strategy available or not <Strategy1>: Distributed per Cell strategy available or not <Strategy2>: One Cluster/SYNC_DL Code per Site strategy available or not <Strategy3>: Distributed per Site strategy available or not <Strategy>: Scrambling code allocation strategy <FromScratch>: Reset all already allocated codes or not <UseCurrentNghbs>: Use existing first-order neighbours or not <NghbOrder>: The order of neigbours to take into account, i.e., 1st, 2nd, or 3rd <ComputeNghbs>: Calculate neighbours using the addition Ec/I0 conditions or not <UseMaxCodes>: Use a maximum of codes or not <UseShadowing>: Shadowing taken into account or not (not used in TD-SCDMA) <SameCodeForCarriers>: Allocate carriers identically or not <NbClusterPerSite>: Number of transmitters per site among which a cluster should be distributed <ClustNghbs>: Additional constraint of taking into account the first-order neighbours in other clusters <Clust2ndNghbs>: Additional constraint of taking into account the second-order neighbours in other clusters <NbCodesPerCluster>: The number of scrambling codes in one cluster/SYNC_DL <UseDistance>: Take the minimum reuse distance into account or not <UseExcepPairs>: Take exceptional pairs into account or not <minField>: Minimum pilot signal level constraint (not used in TD-SCDMA) <usePmax>: Use the maximum downlink transmission power or not (not used in TD-SCDMA) <PerCentMaxPower>: The percentage of the maximum downlink power is <usePmax> is set to 0 (not used in TDSCDMA) <Max1stNghbCost>: The maximum cost of 1st order neighbours <Max2ndNghbCost>: The maximum cost of 2nd order neighbours <Max3rdNghbCost>: The maximum cost of 3rd order neighbours <CoplanCost>: The cost for inter-technology neighbours <MaxCoClusterCost>: The maximum cost for same-cluster/SYNC_DL neighbours <MaxDistCost>: The maximum cost for a minimum reuse distance constraint violation <ExcepPairCost>: The cost for exceptional pair constraint violation <UseIndoor>: Coverage conditions: Use indoor losses defined per clutter class or not <UseCloseNghbs>: Take the Close Neighbours constraint into account or not (not used in UMTS) <CloseDistance>: Maximum distance within which close neighbours are located (not used in UMTS) <CloseImportance>: Minimum importance value of close neighbour (not used in UMTS) <MaxCloseCost>: Maximum cost of a close neighbour relation (not used in UMTS) Sample: <?xml version="1.0" encoding="UTF-8"?> <Atoll> <SCP_options> <MinEcI0>-1500.</MinEcI0> <margin>500.</margin> <reliability>5000.</reliability> <DistanceMin>200000.</DistanceMin> <Strategy0>1</Strategy0> 84 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files <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> 3.1.4.8 Automatic PN Offset Allocation Parameters The automatic PN offset allocation parameters (CDMA2000 1xRTT 1xEV-DO documents) that can be stored in the .cfg files are: • • • • • • • • • • • • • • • • • • © Forsk 2009 <MinEcI0>: Minimum Ec/I0 constraint <TDrop>: Value for the TDrop <reliability>: Cell edge coverage probability <DistanceMin>: Default re-use distance <Strategy0>: PN Offset per Cell strategy available or not <Strategy1>: Adjacent PN-Cluster per Site strategy available or not <Strategy2>: Distributed PN-Cluster per Site strategy available or not <Strategy>: PN offset allocation strategy <FromScratch>: Reset all already allocated codes or not <UseCurrentNghbs>: Use existing neighbours or not <NghbOrder>: The order of neigbours to take into account, i.e., 1st, 2nd, or 3rd <ComputeNghbs>: Calculate neighbours using the addition Ec/I0 conditions or not <UseShadowing>: Shadowing taken into account or not <SameCodeForCarriers>: Allocate same PN offset to cells of the same transmitter or not <PilotIncr>: Value for the PILOT_INC <PNClusterSize>: Number of PN offsets per cluster <UseDistance>: Take the minimum reuse distance into account or not <UseExcepPairs>: Take exceptional pairs into account or not AT281_AM_E1 85 Administrator Manual • • • • • • • • • • • <UseMaxCodes>: Use a maximum of codes or not <minField>: Minimum pilot signal level constraint <usePmax>: Use the maximum downlink transmission power or not <PerCentMaxPower>: The percentage of the maximum downlink power is <usePmax> is set to 0 <Max1stNghbCost>: The maximum cost of 1st order neighbours <Max2ndNghbCost>: The maximum cost of 2nd order neighbours <Max3rdNghbCost>: The maximum cost of 3rd order neighbours <CoplanCost>: The cost for inter-technology neighbours <MaxDistCost>: The maximum cost for a minimum reuse distance constraint violation <ExcepPairCost>: The cost for exceptional pair constraint violation <UseIndoor>: Coverage conditions: Use indoor losses defined per clutter class or not Sample: <?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> </PNO_options> </Atoll> 3.1.4.9 Microwave Radio Links Parameters The microwave radio links parameters that can be stored in the .cfg files are: • • • • • • 86 <Name>: Name of the Microwave Radio Links folder <Display>: Display parameters for the microwave links, such as <minZoom>, <maxZoom>, and <visible> <AddToLegend>: Add microwave links to legend window or not <Interference>: Interference calculation <QualityModel>: Quality model used for calculations <QualityObjective0>, <QualityObjective1>, <QualityObjective2>, <QualityObjective3>: Quality objectives AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • <AvailabilityObjective0>, <AvailabilityObjective1>, <AvailabilityObjective2>, <AvailabilityObjective3>: Availability objectives <RainModel>: Rain model used <RBER>: Residual BER <ALFA1>: Value of alpha 1 <ALFA2>: Value of alpha 2 <RefDelayM>: Reference delay for minimum phase <refDelayNM>: Reference delay for non-minimum phase <EquipPercent>: Availability objectives ratio for equipment <RainPercent>: Availability objectives ratio for rain <kMoy>: Average value of k <kMin>: Minimum value of k <UseAtpc>: Use automatice power control or not <Rec530Simple>: Use simplified method for multipath occurence using ITU-R P.530 <IgnoreXPD>: Ignore cross-polar discrimination <IgnorePR>: Ignore passive repeaters <OneBER>: Use same BER for all links <BER1>: Value of BER 1 <BER2>: Value of BER 2 <CALC_LINK_PORTS>: Calculate for given link ports <InterferenceDistanceMax>: Maximum distance for interference filtering <InterferenceDropMin>: Minimum threshold reduction for interference result filtering <InterferenceCalcGo>: Interference calculation in the direction from site A to site B <InterferenceCalcReturn>: Interference calculation in the direction from site B to site A <InterferenceCalcUplink>: Interference calculation in the uplink <InterferenceCalcDownlink>: Interference calculation in the downlink <InterferenceRainSurfCorrelation>: Interference correlation surface area <InterferenceAutoWeight>: Automatic interference weighting <InterferenceUseAtpc>: Power control for interference calculation <InterferenceWidth>: Interfered wanted bandwidth <InterferenceOverShoot>: Interference over shoot calculation <INTERF_DETAIL>: Interference calculation details Sample: <?xml version="1.0" encoding="UTF-8"?> <Atoll> <Microwave> <Name>Microwave Radio Links</Name> <Display> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> </Display> <AddToLegend>0</AddToLegend> <Interference>0</Interference> <QualityModel>1</QualityModel> <QualityObjective0>0</QualityObjective0> <AvailabilityObjective0>0</AvailabilityObjective0> <QualityObjective1>1</QualityObjective1> <AvailabilityObjective1>1</AvailabilityObjective1> <QualityObjective2>2</QualityObjective2> <AvailabilityObjective2>2</AvailabilityObjective2> <QualityObjective3>3</QualityObjective3> <AvailabilityObjective3>3</AvailabilityObjective3> <RainModel>1</RainModel> <RBER>1.e-012</RBER> <ALFA1>10</ALFA1> <ALFA2>1</ALFA2> <RefDelayM>6.30000019</RefDelayM> <refDelayNM>6.30000019</refDelayNM> <EquipPercent>33.</EquipPercent> © Forsk 2009 AT281_AM_E1 87 Administrator Manual <RainPercent>33.</RainPercent> <kMoy>1.33</kMoy> <kMin>0.</kMin> <UseAtpc>0</UseAtpc> <Rec530Simple>1</Rec530Simple> <IgnoreXPD>0</IgnoreXPD> <IgnorePR>0</IgnorePR> <OneBER>0</OneBER> <BER1>1.e-003</BER1> <BER2>1.e-006</BER2> <CALC_LINK_PORTS>selected</CALC_LINK_PORTS> <InterferenceDistanceMax>50000.</InterferenceDistanceMax> <InterferenceDropMin>0.3</InterferenceDropMin> <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> <INTERF_DETAIL>both</INTERF_DETAIL> </Microwave> <Atoll> 3.1.4.10 Macros The .cfg files can store the following information about macros: • • • <Path>: Complete path to the macro file <Language>: Language in which the macro is written <Timeout>: The target time allocated to macro execution Sample: <?xml version="1.0" encoding="UTF-8"?> <Atoll> <Macros> <File> <Path>C:\TestsAddin\testEvents.vbs</Path> <Language>VBScript</Language> <Timeout>60</Timeout> </File> </Macros> </Atoll> 3.2 Other Configuration Files These configuration files include the following UTF-8 encoded XML (eXtensible Markup Language) files with a .cfg extension: • • • 88 Print setup configuration file Table import/export configuration file Coverage prediction report configuration file AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files Other configuration files, which are not XML-based, include: • • CW measurement import configuration file Drive test data import configuration file The examples provided below for each configuration file can help understand their formats and functions. 3.2.1 Print Setup Configuration The following print setup parameters are saved in the .cfg files: • • • Page tab <Page>: - Paper size and orientation <Paper size="" orientation=""/>, margins <Margins right="" left="" bottom="" top="">, scaling with the fit to page option <Scale fitToPage=""> Components tab: - Rulers and area inside focus zone only <Map>: <Map insideFZonly="" rulers=""/> - Legend <Legend>: Legend flag, outer and inner position, and inside map flag <LegendPos enable="" majorPos="" minorPos="" insideMap=""/> - Comments <Comments>: Comments flag, vertical and horizontal position, and the inside map flag <Position vPos="" enable="" hPos="" insideMap=""/>, comment text <text>, and font details <font height="" weight="" charset="" face="" italic=""/> Header/Footer tab: - Header logo <Logo>: Logo flag, vertical and horizontal position, and the inside map flag <Position vPos="" enable="" hPos="" insideMap=""/>, logo image <bitmap>, and logo width and height in pixels <Dimensions width="" height=""/> - Header title <Title>: Header flag, vertical and horizontal position, and the inside map flag <Position vPos="" enable="" hPos="" insideMap=""/>, title text <text>, and font details <font height="" weight="" charset="" face="" italic=""/> - Footer logo <LogoBottom>: Logo flag, vertical and horizontal position, and the inside map flag <Position vPos="" enable="" hPos="" insideMap=""/>, logo image <bitmap>, and logo width and height in pixels <Dimensions width="" height=""/> - Footer text <Footer>: Footer flag, vertical and horizontal position, and the inside map flag <Position vPos="" enable="" hPos="" insideMap=""/>, footer text <text>, and font details <font height="" weight="" charset="" face="" italic=""/> Sample: <?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"/> <text></text> <font height="14" weight="400" charset="1" face="MS Shell Dlg" italic="0"/> </Title> © Forsk 2009 AT281_AM_E1 89 Administrator Manual <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> 3.2.2 Table Import/Export Configuration The following table import/export parameters are saved in the .cfg files: • • • • • Header flag <TITRE> Field separator <FLD_SEPARATOR> Decimal symbol <DEC_SEPARATOR> Fields available in the table (field legends) <FIELDS> Fields selected for import/export (field legends) <CHOOSEN_FIELDS> Sample: <?xml version="1.0" encoding="UTF-8"?> <TITRE>1</TITRE> <FLD_SEPARATOR><tab></FLD_SEPARATOR> <DEC_SEPARATOR>.</DEC_SEPARATOR> <FIELDS> Site Transmitter ... </FIELDS> <CHOOSEN_FIELDS> Site Transmitter ... </CHOOSEN_FIELDS> 3.2.3 Coverage Prediction Report Configuration The following coverage prediction report parameters are saved in the .cfg files: • Columns selected in the Columns to be displayed dialogue <SelectedFields> including the field titles <Field> <Title> Sample: <?xml version="1.0" encoding="UTF-8"?> <ReportConfiguration> <SelectedFields> <Field> <Title>Surface (km²)</Title> </Field> <Field> <Title>% of Covered Area</Title> </Field> ... 90 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files </SelectedFields> </ReportConfiguration> 3.2.4 CW Measurement Import Configuration Many CW measurement import configurations can be saved in a single MeasImport.ini file. For each saved configuration, the following parameters are stored: • • • • • • • • • • • • • • • Configuration name in square brackets First measurement row (Header) Separator (Separator) Decimal symbol (DecimalSeparator) Type of files for which the configuration has been defined (Pattern) Column containing the X coordinates (Xindex) Column containing the Y coordinates (Yindex) Column containing the measurement values (MeasIndex) Unit of the measurement values (Unit) Frequency of the measurements (Frequency) Height of the receiver used for measurements (Height) Gain of the receiver used for measurements (Gain) Losses of the receiver used for measurements (Losses) Total number of columns in measurement files (NbCol) Column types (Col0 to ColNbCol) The column type indexes are as follows: Type Index Text 0 Integer 1 Real 2 Date 3 <Ignore> 4 Sample: [ConfigurationName] Header=2 Separator=tab DecimalSeparator=. Pattern=*.txt Xindex=1 Yindex=2 MeasIndex=4 Unit=0 Frequency=2110 Height=1.5 Gain=0 Losses=0 NbCol=23 Col0=1 Col3=4 Col5=0 Col6=1 Col7=2 ... 3.2.5 Drive Test Data Import Configuration Many drive test data import configurations can be saved in a single NumMeasINIFile.ini file. For each saved configuration, the following parameters are stored: • © Forsk 2009 Configuration name in square brackets AT281_AM_E1 91 Administrator Manual • • • • • • • • • • • • • • • • First measurement row (Header) Separator (Separator) Decimal symbol (DecimalSeparator) Type of files for which the configuration has been defined (Pattern) Column containing the X coordinates (Xindex) Column containing the Y coordinates (Yindex) Unit of the measurement values (Unit) Height of the receiver used for measurements (Height) Gain of the receiver used for measurements (Gain) Losses of the receiver used for measurements (Losses) First identifier (GenericNameIdOne) Second identifier (GenericNameIdTwo) Format of the second identifier (IdFormat) Wireless technology (Techno) Total number of columns in measurement files (NbCol) Column types (Col0 to ColNbCol) The column type indexes are as follows: Type Index Text 0 Integer 1 Long Integer 2 Single 3 Double 4 Date 5 <Ignore> 6 Sample: [ConfigurationName] Header=2 Separator=tab DecimalSeparator=. Pattern=*.* Xindex=1 Yindex=2 Unit=0 Height=1.5 Gain=0 Losses=0 GenericNameIdOne= GenericNameIdTwo=BSID IdFormat=Decimal Techno=IEEE 802.16e NbCol=21 Col0=1 Col3=1 Col4=4 ... 3.3 Atoll Initialisation File The Atoll initialisation file is used to inform Atoll of the preferred settings to be used during Atoll sessions. It can be used to adjust the behaviour and algorithms used in Atoll. Caution: • 92 The Atoll initialisation file is a powerful tool. You should not modify any option in the Atoll.ini file until and unless you are absolutely sure of what you are doing. AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files In order for the Atoll initialisation file to be used by Atoll, you may: 1. Place the Atoll.ini file in the Atoll installation directory 2. Use the Atoll Management Console to specify the Atoll.ini file to be loaded for each user as described in "Managing Administration File Paths" on page 147. This depends on the user connection properties. 3. Declare the .ini file to be loaded in the command line, as shown below. C:\Program Files\Forsk\Atoll\atoll.exe -ini C:\Work\Atoll.ini By default, the Atoll initialisation file is named "Atoll.ini." It is possible to rename the initialisation file or load an initialisation file with a different name. If you rename the .ini file you must specify the name (with the complete path, if the .ini file is not in the same directory as the Atoll executable) when starting Atoll: C:\Program Files\Forsk\Atoll\atoll.exe -ini myini.ini or C:\Program Files\Forsk\Atoll\atoll.exe -ini C:\Work\myini.ini This feature is useful when several users work on the same workstation or a user works on different projects that require different settings. Notes: • If an Atoll.ini file exists in the Atoll installation folder, you can open it for editing from Atoll by pressing CTRL+SHIFT+i. • You have to restart Atoll in order to take into account any modifications in the Atoll.ini file. • An .ini file defined in the command line has priority over the .ini file configured using the Atoll Management Console. The following sections describe the options available in the Atoll.ini file. 3.3.1 General Options 3.3.1.1 Modifying the Default Formats of Site and Transmitter Names Through the Atoll.ini file, it is possible to specify prefixes to be used for naming sites and transmitters. In case of sites, you must add these lines: [Site] Prefix = "newprefix" Each new site will then be named “newprefixN” instead of “SiteN”, where N is the site number or index. For transmitters, you can define a prefix by adding these lines: [Transmitter] 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 transmitter’s name, i.e., the transmitter can be named SitenameX instead of Sitename_X. To do this, add the following line in the [Transmitter] section of the .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 transmitter’s 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: © Forsk 2009 AT281_AM_E1 93 Administrator Manual First = X Where, X is a number. 3.3.1.2 Disabling Automatic Renaming of Transmitters and Cells When the name of any site is modified, Atoll automatically renames the transmitters and cells related to the site according to the new site name. Similarly, renaming a transmitter renames the corresponding cells automatically. Automatic renaming according to site names is enabled by default. However, it may be disabled by adding the following lines in the Atoll.ini file: [AutoRename] Transmitters = 0 3GCells = 0 • • 3.3.1.3 "Transmitters" refers to transmitter renaming when the site name is changed. "3Gcells" refers to cell renaming when the transmitter name is changed. Setting the TIF Colour Convention You may export .tif files with a palette containing the background colour at index 0 along with other colour indices representing the foreground. To do so, the Atoll.ini file must contain these lines: [TiffExport] PaletteConvention = Gis 3.3.1.4 Creating an Event Viewer Log File You can define a log file path and file name in Atoll.ini in order to save all the warning, error and information messages displayed in the Event Viewer window to a log file. To do this, add the following lines to Atoll.ini: [EventsObserver] LogPath = FullPath\LogFile.log The path should be the full path to the log file, which can be, for example, "\\Server\Drive\Root\Folder\Atoll\" or "C:\Program Files\Forsk\Atoll\" (without quotation marks). "LogFile.log" will be created by Atoll as an ASCII text file, and can have any file name and extension. Atoll will overwrite any already existing log file with the same name. If Atoll is unable to overwrite the existing log file, it will not create any log. You can also start Atoll, specifying a log file, by starting it with "Atoll.exe -log LogFile.log", either from the command line, or by modifying the shortcut parameters. If you have a log file defined in the Atoll.ini file, and run Atoll with the -log option in the command line, the command line log file will have priority over the one mentioned in the Atoll.ini file. The option available in Atoll.ini is more suitable for running Atoll using macros. Apart from these options, you also have the possibility to save the messages in the Event Viewer to a log file during an Atoll session (through the Event Viewer context menu). 3.3.1.5 Increasing the Maximum Printing Resolution By default, Atoll limits the printing resolution to 150 dpi (dots per inch) to improve performance and consume less memory when printing. If you want Atoll to print your maps in a higher resolution than 150 dpi, you can add the following lines to the Atoll.ini file: [Print] MaxDPI = 300 300 dpi is given as an example only. 3.3.1.6 Duplicating External Path Loss Matrices with "Save As" When you save a file (filename.atl, for example) under a new name using the Save As command, Atoll creates the new file (newfilename.atl) and the corresponding external path loss matrices folder (newfilename.losses\), where it copies the existing path loss matrices from the external path loss matrices folder (filename.losses\) of the original document. There can be a large number of .los files, and copying these files could take a lot of time and use a lot of disk space. If you want Atoll not to make copies of the external path loss matrices, you can add the following lines to the Atoll.ini file: [Perfos] StoreExternPrivLosFilesOnCopy = 0 StoreExternPrivLosFilesOnCopy is set to 1 by default, which means that Atoll makes copies of the external path loss matrices. If you set StoreExternPrivLosFilesOnCopy to 0, Atoll does not create the external path loss matrices folder for the new file, and the external path loss matrices of the original .atl file are used for the new .atl file as well. 94 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files A file open in Atoll has exclusive access rights to its private path loss matrices. If you simultaneously open two files in Atoll that point to the same private path loss matrices, only the file open first will have access rights while the second will not be allowed to access the path loss matrices. You will be able to open the second file, but it will no longer point to any private path loss matrices folder. Therefore, if you have more than one file that points to the same private path loss matrices folder, you should not open them at the same time. 3.3.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. 3.3.1.8 Displaying Path Loss Calculation Details in the Event Viewer During path loss calculations, Atoll displays details about these calculations in the Tasks tab of the Event Viewer. These details cannot be copied or saved. If you want access to these details, or to a summary of these details, once the calculations have finished, you can add the following lines in the Atoll.ini file: [Pathlosses] DisplayInvalidityCause = 1 DisplayIndividualSuccessOrFailure = 1 DisplayOverallSuccessOrFailure = 1 Setting the DisplayInvalidityCause option to 1 will display the cause for which path losses were calculated for each transmitter, setting DisplayIndividualSuccessOrFailure to 1 will display whether the path loss calculation succeeded or failed for each transmitter, and setting DisplayOverallSuccessOrFailure to 1 will display the total number of path loss matrices calculated, the number of path loss matrices calculated successfully, and the number of calculations that failed. These details are listed in the Events tab of the Event Viewer. 3.3.1.9 Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Files It is now possible to define a mapping between the coordinate systems in Atoll and the coordinate systems defined in the header files of MapInfo (.mif) and ESRI (.prj) vector files that you want to import. You can defne a mapping between the two coordinate systems by adding the following lines in the Atoll.ini file: [MITAB] Coordinate system definition in the header file = Coordinate system code in Atoll In this way, Atoll is able to exactly detect the coordinate system used by the vector file being imported. In .mif files, the CoordSys clause defines the coordinate systems, datum, unit, and other information. The coordinate system definition is different in the .prj files. The syntax used in Atoll.ini follows the syntax of the CoordSys clause in .mif files. Using the same syntax for .mif and .prj files, Atoll is able to read the detect the coordinate systems for both MapInfo and ESRI vector files. The coordinate system codes in Atoll are stored in the .cs files in the coordsystems folder. To access the coordinate system codes through Atoll: 1. Select Tools > Options. The Options dialogue opens. 2. On the Coordinates tab, click the browse button (...) to the left of the Projection field. The Coordinate Systems dialogue opens. 3. Select a coordinate system in the pane. 4. Click the Properties button. The Coordinate System properties dialogue opens. The coordinate system code is available in the properties dialogue. A few examples of such mapping are given below. [MITAB] ; NTF Earth Projection 1, 107 = 4275 ; Tokyo © Forsk 2009 AT281_AM_E1 95 Administrator Manual Earth Projection 1, 97 = 4301 ; WGS 84 / UTM zone 31N Earth Projection 8, 104, "m", 3, 0, 1, 500000, 0 = 32631 ; WGS 84 / UTM zone 53N Earth Projection 8, 104, "m", 135, 0, 0.9996, 500000, 0 = 32653 ; WGS 84 / UTM zone 54N Earth Projection 8, 104, "m", 141, 0, 0.9996, 500000, 0 = 32654 ; NTF (Paris) / France II étendue Earth Projection 3, 1002, "m", 0, 46.8, 45.8989188889, 47.69601444, 600000, 2200000 = 27595 3.3.1.10 Exporting Coverage Prediction Polygons in Text Format You can export coverage predictions in the form of polygons to text format files. Caution: • 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. 3.3.1.11 Defining Web Map Services Servers Web Map Services allow you to directly import geographic data from specialised servers into Atoll. The list of WMS servers can be defined in the Atoll.ini file as follows: [WMS] S1 = Server1 S2 = Server2 ... SN = ServerN You can define any number of servers by incrementing the index N. These servers will be available in the WMS data import dialogue in Atoll. 3.3.1.12 Improving Point Analysis Performance You can improve the performance, i.e., calculation speed, of the Point Analysis tool by restricting the number of transmitters for which the received signal levels are calculated. To restrict the number of transmitters considered in the Point Analysis tool, add the following lines in the Atoll.ini file: [Perfos] PtAnalysisNbServersMax = X PtAnalysisMargin = Y The option PtAnalysisNbServersMax lets to define the maximum number of transmitters (servers) to consider for the calculation of the received signal levels. X is the maximum number of transmitters. The option PtAnalysisMargin lets you define the margin with respect to the best server signal level. Atoll calculates the signal levels from all the transmitters within Y dB margin from the best server signal level. The default value for PtAnalysisMargin is 30 dB. In addition to the above, you can also set the number of transmitters for which arrows are displayed from the pointer location in the map window. For setting this number, add the following lines in the Atoll.ini file: [ReceptionTab] NumberOfTransmitterDisplayed = Z Z is the number of transmitters for which arrows generated from the pointer location will be displayed in the map window. 96 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files 3.3.1.13 Loading Vector Files Dynamically Vector geo data from files imported in an Atoll document are loaded in the memory when the document is open. Atoll can dynamically load the data from .shp and .tab vector files when the following option is set in the Atoll.ini file: [Import] LoadVectors = 1 LoadVectors is set to 0 by default, which means that the data from imported vector files are loaded in memory. When you set LoadVectors to 1, Atoll reads the data from the vector files directly. From the point of view of performance, this option is only advisable when working with large vector data files. 3.3.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 . 3.3.1.15 Disabling Opening of Exported XLS Files Automatically in MS Excel When you export an entire data table, or selected columns, to an MS Excel file, Atoll automatically runs MS Excel once the export is complete and opens the XLS file created by the export in MS Excel. To disable this feature, add the following option in the Atoll.ini file: [Export] AutoOpenWithExcel = 0 AutoOpenWithExcel is set to 1 by default, which means that MS Excel is automatically run once the export is complete and the XLS file created by the export opened in it. If you set AutoOpenWithExcel to 0, Atoll will not run MS Excel after the export. 3.3.1.16 Disallowing Creation of New Documents from Templates You can disallow the creation of new Atoll documents from templates by adding the following lines in the Atoll.ini file: [GUIUserRights] EnableNewDocFromTemplate = 0 EnableNewDocFromTemplate is set to 1 by default. 3.3.1.17 Blocking Access to Macros and Add-ins You can block access to the Add-ins and Macros dialogue by adding the following lines in the Atoll.ini file: [GUIUserRights] EnableMacrosAddins = 0 EnableMacrosAddins is set to 1 by default. 3.3.1.18 Enabling Notification for Donor Transmitter Parameter Modifications Atoll can notify you whenever a donor transmitter parameter, which has an impact on a repeater, is modified. To activate the notification, add the following lines in the Atoll.ini file: [Transmitter] CheckImpactOnRepeaters = 1 CheckImpactOnRepeaters is set to 0 by default, which means that no notifications are displayed. © Forsk 2009 AT281_AM_E1 97 Administrator Manual 3.3.1.19 Setting the Display Precision of Floating Point Values You can set the display precision for floating point values in Atoll dialogues and tables. For example, in order to display two digits after the decimal point, you can add the following lines in the Atoll.ini file: [Grids] NbDecimals = 2 This option applies to all floating point parameters in Atoll except geographic coordinates. NbDecimals is set to -1 by default. This corresponds to maximum precision, i.e., all the digits after the decimal point available in the database are displayed. 3.3.2 Calculation Options 3.3.2.1 Setting the Antenna Patterns Modelling Method In order to set the modelling method for antenna patterns, the Atoll.ini file may contain following information: [Antenna] AngleCalculation = 2000 or 3000 Catalog Vertical Diagram Orientation = 0 or angle value InterpolatePatternEventIfOnlyOneDiagram = 0 or 1 The values 2000 and 3000 are only valid for Forsk’s propagation model library, i.e., the propagation models available with Atoll by default. Setting AngleCalculation = 2000 makes the propagation models calculate "unmasked" path losses, i.e., path losses without considering the transmitter antenna patterns. Setting AngleCalculation = 3000 makes the propagation models calculate the angles of incidence to each pixel instead of path loss. Catalog Vertical Diagram Orientation is only a display option. It enables representing the antenna’s vertical diagram with a certain orientation. Adjusting Catalog Vertical Diagram Orientation= 90, for example, will rotate the vertical diagram by 90° in clock-wise direction. 0 corresponds to the default display. The InterpolatePatternEventIfOnlyOneDiagram can be used to change the way Atoll interpolates antenna attenuation patterns for antennas with only one diagramme available, vertical or horizontal. With InterpolatePatternEventIfOnlyOneDiagram = 0 (default, new method), Atoll uses the one available diagramme for both vertical and horizontal planes. With InterpolatePatternEventIfOnlyOneDiagram = 1 (previous method), Atoll uses the available diagramme for the plane to which it corresponds, vertical or horizontal, and an isotropic attenuation diagramme (a 0 dB circular attenuation pattern) for the plane for which no diagramme is available. 3.3.2.2 Disabling Automatic Locking of Coverage Predictions By default, Atoll automatically locks a coverage prediction study once it is calculated. To instruct Atoll not to lock prediction studies automatically, these lines have to be included in the Atoll.ini file: [Studies] AutoLock = 0 This setting is read by Atoll without Atoll having to be restarted. 3.3.2.3 Enabling Shadowing Margin in Calculations An average value of shadowing margin is calculated by Atoll and applied to the signal level and interference levels during coverage predictions and other calculations such as point analysis, automatic neighbour allocation, automatic scrambling code and PN offset allocation, and interference matrices calculation. This average value depends on the cell edge coverage probabilities and the standard deviations defined per clutter class. In the dialogues of all the above-mentioned calculations, the Shadowing taken into account check box is not selected by default. Not selecting this check box implies that the shadowing margin is neither calculated nor used in the calculations. If you want to select the Shadowing taken into account check box by default in all the above-mentioned dialogues, you have to enter the following lines in the Atoll.ini file: [Shadowing] UseShadowing = 1 UseShadowing is set to 0 by default. 98 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files Note: • 3.3.2.4 This option does not affect the shadowing margin calculation during Monte Carlo simulations. Monte Carlo simulations do not use an average value of the shadowing margin depending on the cell edge coverage probability. During Monte Carlo simulations, random shadowing margin values are calculated based only on the standard deviations defined per clutter class. 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. Note: • 3.3.2.5 The value of cell edge coverage probability used for automatic neighbour allocation and interference matrices calculation is stored in user configuration files (.cfg). Enabling Indoor Coverage in Calculations Indoor losses are taken into account in calculations when the Indoor Coverage check box is selected. This check box is not selected by default. If you want to select the check box by default in the properties dialogues of all the calculations, you have to enter the following lines in the Atoll.ini file: [ClutterParams] IndoorActivity = 1 IndoorActivity is set to 0 by default. 3.3.2.6 Modifying the Resolution for the LOS Area Calculation Around a Site The calculation of line of sight area around a given site uses the resolution of the geographic data as the default calculation resolution. These calculations can be time-consuming if the geographic data is available with a very high resolution. You can set the calculation resolution to a multiple of the resolution of the geographic data by adding the following lines in the Atoll.ini file: [LOSArea] ResolutionMultFactor = X Where X is an integer. Therefore, setting ResolutionMultFactor to 2 will double the calculation resolution and decrease the time required for the calculation by half. 3.3.2.7 Disabling the Temporary Local Storage of Path Loss Files If you are working with a shared path loss folder, Atoll automatically copies the path loss files that it needs during calculations to the local computer for improving performance. This feature improves the performance many times if the shared path loss folder is located across a network because accessing a local hard disk is much faster than accessing a file over the network. However, you can instruct Atoll not to store these temporary copies of the path loss results in the system’s temporary files folder by adding the following lines in the Atoll.ini file: [PathLosses] PrivateCopies = 0 • • 0: Temporary copies disabled 1: Temporary copies enabled (default) Use this option only if you are critically short of hard disk space. However, note that disabling temporary local copies might decrease the performance as it adds file access delays over the network. 3.3.2.8 Embedding Path Losses in New Documents If you calculate path loss matrices for a new document that has not been saved yet, Atoll asks if you would like to save the document and externalise the path loss matrices or if you would like to keep the path loss matrices embedded in the document and save it later. You can suppress this message by adding the following lines in the Atoll.ini file: © Forsk 2009 AT281_AM_E1 99 Administrator Manual [PathLosses] EmbeddedByDefault = 1 EmbeddedByDefault is set to 0 by default. 3.3.2.9 Stopping Calculations on Error If a problem occurs in calculating one or more path loss matrices while calculating a coverage prediction, Atoll continues performing the remaining calculations, and provides results even if they are not complete. If you want Atoll to stop the calculations if there is an error, you can add the following lines in the Atoll.ini file: [Studies] ContinueOnError = 0 ContinueOnError = 1 by default. This means that by default Atoll does not stop the calculations on error. 3.3.2.10 Warning About Prediction Vailidity When Display Options are Modified Coverage predictions have to be recalculated if you modify their display options. You can instruct Atoll to display a warning message when you modify the display options for coverage predictions. To display the warning message every time the display options for coverage predictions are modified, add the following lines in the Atoll.ini file: [Studies] RecomputationWarning = 1 RecomputationWarning is set to 0 by default. 3.3.2.11 Reading Exact Transmitter Altitudes From the DTM Atoll uses either the user-defined site altitudes from the Sites table or, if they are not defined, the site altitudes read from the DTM for the site coordinates defined in the Sites table. However, transmitters can be located at certain distances from the site coordinates. You can set these distances of transmitters from their sites in the Transmitters table under DX and DY. If you want Atoll to consider the exact transmitter coordinates, i.e., including DX and DY, during calculations for determining the transmitter height, which will be read from the DTM at the exact transmitter coordinates, you must add the following lines in the Atoll.ini file: [Calculations] UseSiteAltitude = 0 UseSiteAltitude is set to 1 by default, which means that the altitude considered in calculations for any transmitter is the one which is either read from the Sites table or from the DTM at the site’s coordinates, if the user-defined altitude is not available in the Sites table. Setting UseSiteAltitude to 0 means that, during calculations, Atoll will read the altitudes from the DTM at the exact coordinates of each transmitter considering the values entered for the DX and DY parameters. The above option is also valid for microwave links. In this case, setting UseSiteAltitude to 0 means that, during calculations, Atoll will read the altitudes from the DTM at the exact coordinates of each microwave link considering the values entered for the DX_A, DY_A, DX_B, and DY_B parameters. 3.3.2.12 Setting a Common Display Resolution For All Coverage Predictions You can set a display resolution for each coverage prediction individually as well as a default display resolution for all coverage predictions that you create, in the Predictions tab of the Predictions folder’s properties dialogue. If you create a new coverage prediction, Atoll reads the default resolution from the Predictions folder’s properties and sets that as the display resolution for the new coverage prediction. Then, if you delete this resolution from the coverage prediction properties, and do not enter any resolution, Atoll resets the resolution to the default value. In this way, each coverage prediction has a display resolution defined. However, it is possible to manage a common display resolution for all coverage predictions, new or existing, that do not have a resolution defined for them. You can switch to this option by adding the following lines in the Atoll.ini file: [Studies] SpecifyResolutionAfterComputation = 0 Once SpecifyResolutionAfterComputation is set to 0, Atoll no longer resets the resolution to the default value for coverage predictions that do not have a resolution defined. Atoll allows you to leave the field empty in the coverage prediction properties, and directly reads the default resolution defined in the Predictions folder’s properties. In this way, when you create coverage predictions without defining resolutions for them, you can modify the default resolution of the Predictions folder’s properties and, therefore, change the display resolution for all the coverage predictions, new or existing. To return to the normal working, you can either remove the lines from the Atoll.ini file, or set SpecifyResolutionAfterComputation to 1. 100 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files 3.3.2.13 Setting Coverage Prediction Report Resolution For Population Maps Atoll uses the default resolution, defined in the Predictions folder’s properties dialogue, for rasterization of the population maps. In order to use a different resolution for higher or lower precision, you can add the following lines in the Atoll.ini file: [Population] ReportResolution = X Where X is the resolution for the conversion of population map vectors into raster. Important: • 3.3.2.14 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 optiimum value, i.e., just precise enough to get the required accuracy. Deleting Private Path Losses When Shared Path Losses are Valid Atoll verifies whether the shared and private path loss matrices are valid before starting any calcualtion. If the shared path loss matrices are valid, Atoll deletes the corresponding invalid private path loss matrices and uses the shared ones for the calculation. If you want Atoll to delete all the private path loss matrices, invalid as well as valid, corresponding to the valid shared path loss matrices, add the following lines to the Atoll.ini file: [Pathlosses] FullResyncPrivShared = 1 FullResyncPrivShared is set to 0 by default. Important: • 3.3.2.15 If you have tuned locally stored path loss matrices using measurement data, enabling this option will make Atoll automatically delete them when calculations are made. You should disable this option while tuning local path loss matrices, which are stored in the private path loss matrices folder. Calculating Neighbour Importance Based on Distance During the automatic neighbour allocation process, Atoll calculates the neighbour importance values (ranks) based on coverage overlapping, adjacency, and co-site factors as described in the Technical Reference Guide. If you want Atoll to consider the distance between the reference transmitter/cell and its candidate neighbours in the calculation of importance, add the following lines in the Atoll.ini file: [Neighbours] CoefDistance = n Where n is any whole number. By default, n is equal to 0. Atoll calculates and applies a distance factor to the overlapping factor. The distance factor is calculated as follows: d n D = 1 –  ------------  d Max The distance factor is linear if n = 1. With higher values of n, the distance factor varies geometrically. The above formula uses real distances between transmitters/cells. d is the distance from the reference transmitter/cell to a candidate neighbour and d Max is the distance from the reference transmitter/cell to its farthest candidate neighbour. 3.3.2.16 Setting the Priorities for GUI and Calculations You can set the priorities for user interface and calculations through the following option in the Atoll.ini file: [RemoteCalculation] Priority = 0, 1, or 2 Priority enables you to set the priority between calculations and user interface. • • • 3.3.2.17 0: User interface has the highest priority. 1 (default): User interface has a higher priority than calculations. 2: User interface and calculations have the same priority. Setting the Number of Parallel Processors and Threads You can manage the number of processors and threads through the Atoll.ini file. The file should contain the following options: © Forsk 2009 AT281_AM_E1 101 Administrator Manual [RemoteCalculation] NumberOfProcessors = X NumberOfThreads = 1, 2, ..., or 8 NumberOfThreadsPathloss = 1, 2, ..., or 8 NumberOfThreadsSimulation = 1, 2, ..., or 8 NumberOfThreadsStudy = 1, 2, ..., or 8 NumberOfThreadsNeighbour = 1, 2, ..., or 8 NumberOfThreadsMicrowave = 1, 2, ..., or 8 Maximum number of processors: • NumberOfProcessors is the maximum number of processors that can be used for calculations. If you set this option to 0, Atoll will use actual number of available processors. Maximum number of calculation threads: • • • • • • NumberOfThreads is the maximum number of threads that can be used for any calculation (8 by default, 8 maximum). 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 coverage prediction study calculations (4 by default, 8 maximum) 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. 3.3.2.18 Disabling Parallel Calculation of Monte Carlo Simulations For UMTS HSPA and CDMA2000 1xRTT 1xEV-DO documents, Atoll can perform multi-thread calculations of Monte Carlo simulations. If you want to disable the parallel calculation, add the following lines to the Atoll.ini file: [CDMA] ParallelSimulations = 0 ParallelSimulations is set to 1 by default. Important: • The Generator Initialisation must be set to 0 in order for the simulations to be calculated parallely. The parallel calculation of Monte Carlo simulations in TD-SCDMA, WiMAX 802.16d, WiMAX 802.16e, and LTE documents is disabled by default. It shoud not be enabled in TD-SCDMA documents. 3.3.2.19 Performing Calculations in Read-Only Documents By default, when you open a read-only Atoll document, it is not possible to run calculations in it. If you want to run calculations in read-only documents, you will have to add the following lines in the Atoll.ini file: [Studies] ComputeEvenIfReadOnly = 1 If you open a document that is already open in another Atoll session, Atoll lets you open the document as read-only. 3.3.2.20 Identifying Transmitter, Repeater, and Remote Antenna Coverage Areas In GSM GPRS EGPRS and UMTS HSPA documents, you can create a "Coverage by Aerial" signal level coverage prediction for differentiating the coverage areas of transmitters, and their repeaters and remote antennas. In order to make this coverage prediction available in Atoll, add the following lines in the Atoll.ini file: [Studies] AerialStudy = 1 102 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files 3.3.2.21 Changing the Rounding Method Used for Profile Extraction Before Atoll 2.8.0, real values for altitudes read from the DTM files were rounded down to their integer values. However, from Atoll 2.8.0 onwards, real values are rounded up or down to their nearest integer values. For example, using the previous method, 98.8 m was rounded to 98 m, but with the new method, it is rounded to 99 m. If you want to switch back to the previous method, add the following lines in the Atoll.ini file: [Calculations] RoundAltitudes = 0 RoundAltitudes is set to 1 by default. 3.3.2.22 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. 3.3.2.23 Co-Planning: Calculating Predictions in the Current Document Only Atoll calculates all the unlocked coverage predictions in the Predictions folder of the current document and the unlocked coverage predictions in the linked Predictions folder from another document when you click the Calculate button, press F7, or select the command from a context menu in the current document. If you want Atoll to calculate only the unlocked coverage predictions in the Predictions folder of the current document, and not in the linked Predictions folder from another document, add the following lines in the Atoll.ini file: [CoPlanning] ComputeLinkedPredictions = 0 ComputeLinkedPredictions is set to 1 by default. 3.3.2.24 Co-Planning: Calculating Predictions in Serial or in Parallel If you want Atoll to calculate in parallel the invalid or unavailable path loss matrices and unlocked coverage predictions in the Predictions folder of the current document and the linked Predictions folder from another document, add the following lines in the Atoll.ini file: [CoPlanning] LinkedPredictionsComputationMode = Parallelized LinkedPredictionsComputationMode is set to Serialized by default, which means the path loss matrices and unlocked coverage predictions in the current and linked documents are calculated in serial. If you set LinkedPredictionsComputationMode to any other value, the calculations are performed in parallel but without being managed by a task list. Calculations are carried out starting with the current document in the order of the coverage predictions in the Predictions folder. 3.3.2.25 Co-Planning: Linking the Sites Folder You can link the Sites folder, in addition to the Transmitters and Predictions folders, of a document to another (main) document using the File > Link With command by adding the following lines in the Atoll.ini file: [CoPlanning] LinkSites = 1 LinkSites is set to 0 by default. © Forsk 2009 AT281_AM_E1 103 Administrator Manual 3.3.3 GUI Options 3.3.3.1 Defining the Parameters for the Default Sites Symbol You can define the parameters of the default symbol used for displaying sites on the map through the Atoll.ini file. You can define the parametes as follows: [SitesSymbol] FontName = Name of the font Symbol = Character used for the site symbol from the character set of the font Size = Character size in number of pts 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 3.3.3.2 Refreshing the Display Automatically When a New Station is Dropped You can have Atoll refresh the display automatically each time a new station or a group of stations is dropped on the map by adding the following lines in the Atoll.ini file: [Transmitter] AutoSynchronizeDisplay = 1 AutosynchroniseDisplay is set to 0 by default. 3.3.3.3 Hiding Information Displayed in the Status Bar It is possible to hide altitude, clutter class, or clutter height information in the status bar. To hide the previously mentioned information, add the following lines to the Atoll.ini: [StatusBar] DisplayZ = 0 DisplayClutterClass = 0 DisplayClutterHeight = 0 DisplayZ, DisplayClutterClass and DisplayClutterHeight respectively refer to the display of altitude, clutter class, and clutter height. 3.3.3.4 Displaying Date and Time in the Event Viewer You can instruct Atoll to display the date, and time with milliseconds in the Event viewer. To display this information, add the following lines to the Atoll.ini file: [EventsObserver] milliseconds = 1 date = 1 3.3.3.5 Disabling Automatic Resizing of Windows When you open a new workspace window (map window or a table) while another workspace window is maximized, Atoll restores all the windows to their normal sizes. If you want Atoll to open all new windows as maximized when you are viewing workspace windows as maximized, add the following lines to the Atoll.ini file: [Display] MaximizeWindows = 1 104 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files MaximizeWindows is set to 0 by default. 3.3.3.6 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. 3.3.3.7 Changing the Display for Downlink Smart Antenna Results The downlink smart antenna simulation results, i.e, the angular distributions of downlink transmitted power density, calculated during Monte Carlo simulations using the Optimum Beamformer and Conventional Beamformer can be displayed in two different ways. By default, these diagrams represent the average array correlation matrices and are symmetric about the x-axis (same on the front and back). If you want to display these diagrams taking into account the antenna pattern of the single antenna element, add the following option in the Atoll.ini file: [SAModel] DrawSingleElementPattern = 1 H DrawSingleElementPattern is set to 0 by default, in which case the displayed diagram is S   R Avg  S  . When you set H DrawSingleElementPattern to 1, the diagram displayed will represent g n     S   R Avg  S  . 3.3.3.8 Displaying Coverage Prediction Comments in the Legend Window You can display the contents of the Comments box of coverage prediction properties in the Legend window by adding the following lines in the Atoll.ini file: [Studies] CommentsInLegend = 1 The comments are displayed between the name of the coverage prediction and the thresholds. CommentsInLegend is set to 0 by default. 3.3.4 Distributed Calculation Server Options 3.3.4.1 Detecting and Listing Distributed Calculation Servers You can use Atoll to detect distributed calculation servers and list them in the Atoll.ini file. A computer, serving as a distributed calculation server, can run up to 10 instances of Atollsvr, the distributed calculation application. The distributed calculation server names can be listed in the Atoll.ini file in the following format: [RemoteCalculation] NumberedServers = Server1NameN; Server2NameN; ... Here Server1Name and Server2Name refer to the names of the computers being used as calculation servers, and N is a number from 0 to 9. This means, for example, that Server1 can run up to 10 instances of the distributed calculation application, and all these instances can be listed in the NumberedServers option (Server1Name0; Server1Name1; Server1Name2; ...). Using this option, you can assign distributed calculation servers to different groups of users working with two different Atoll.ini files. For example, user group 1 can use Server1Name0 to Server1Name4, and group 2 can use Server1Name5 to Server1Name9. If an error occurs on any of the distributed calculation servers, Atoll starts to calculate the path loss matrices on the local computer. In this case, Atoll only uses one thread on the local computer and calculates the path loss matrices one by one. The local computer does not try to create as many threads as set for the distributed calculation servers in order to avoid memory saturation. Any error or warning messages generated are passed back to the Atoll session and displayed in the Event Viewer. 3.3.4.2 Setting the Distributed Calculation Server Priority By default, the Atoll distributed calculation server (AtollSvr.exe) runs with a normal process priority. However, it is possible to modify its priority, in both service and application modes, and set it higher or lower. You can do this by adding the following lines in the Atoll.ini file: [RemoteCalculation] © Forsk 2009 AT281_AM_E1 105 Administrator Manual AtollSvrPriority = -1, 0, 1 or 2 You can choose between 4 possible priority levels: • • • • -1: Below Normal priority 0: Normal priority 1: Above Normal priority 2: High priority This option works for both, application and service, modes of the distributed calculation server. Important: 3.3.4.3 • 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. Modifying the Default Detection Time-Out The default time-out (2 seconds) for locating calculation servers within the network might be too short in certain cases. You can increase this time-out by adding the following lines to the Atoll.ini file: [RemoteCalculation] DetectTimeOut = 5000 In this example, the detection time-out is set to 5000 ms. 3.3.5 License Management Options 3.3.5.1 Setting an Alarm for the License End Date You can set a warning message about the license end date to appear a certain number of days before this date. The Atoll.ini file should contain the following lines: [License] TimeBombNotice = X X is the number of days prior to the temporary license end date you want Atoll to warn you. When no information is given in the Atoll.ini file, Atoll warns the user 30 days before the license end. 3.3.5.2 Blocking Access to Certain Modules This option is useful when working with a floating license management system where a floating license server manages and distributes tokens between several Atoll users. When a user starts an Atoll session and opens either a GSM or a UMTS Atoll document, Atoll consumes one Atoll Platform license, one GSM license or one UMTS license and, in addition, one Measurements license and one Microwave Radio Links license, even if the project does not contain any measurements or microwave links. You can block access to the Measurements and Microwave Radio Links license consumption by adding the following lines in the Atoll.ini file: [License] Measures = 0 MW = 0 Where, Measures and MW respectively refer to the Measurements and Microwave Radio Links module licenses. Setting these options to 0 means that if you open a GSM or a UMTS Atoll document with measurements or microwave links, you will not have access to the Measurements or the Microwave Radio Links modules. This option is particularly useful in giving different license rights to users. For example, you could have a group of users working on cellular radio technologies, GSM or UMTS, that uses measurements data, and another group of users working on microwave links projects. In this case, you could create two Atoll.ini files, the first not allowing the first group to use the Microwave Radio Links license, and the second not allowing the second group to use the Measurements module. Then, use the Atoll Management Console to specify the Atoll.ini file to be loaded for each group as described in "Managing Administration File Paths" on page 147. This way, the first group of users can work on GSM and UMTS Atoll documents with measurements without consuming Microwave Radio Links licenses which will be reserved to the second group. You can also block access to the radio technology licences for users or user groups working on microwave links only. To block access to the different mobile technology modules, add the corresponding lines to the [License] section of the Atoll.ini file: 2G = 0 3G = 0 TD-SCDMA = 0 106 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files WiMAX = 0 LTE = 0 You can also block access to the ACP and AFP licences for users or user groups. To block access to ACP or AFP modules, add the corresponding lines to the [License] section of the Atoll.ini file: ACP_GSM = 0 ACP_UMTS = 0 ACP_WiMAX = 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. 3.3.5.3 To block access to Add GSM GPRS EGPRS 2G = 0 UMTS HSPA or CDMA2000 1xRTT 1xEV-DO 3G = 0 TD-SCDMA TD-SCDMA = 0 WiMAX 802.16d and WiMAX 802.16e WiMAX = 0 LTE LTE = 0 Microwave Radio Links MW = 0 Measurements Measures = 0 GSM ACP ACP_GSM = 0 UMTS ACP ACP_UMTS = 0 WiMAX ACP ACP_WiMAX = 0 WiMAX AFP WiMAX_AFP = 0 LTE AFP LTE_AFP = 0 Changing the NetHASP License Manager Idle Time Setting The floating license manager has an idle time parameter with 10 minutes as default value. Atoll sessions consuming floating licenses from a license manager server reset this idle time parameter to its initial value every minute. If you are performing time-consuming calculations on Atoll connected to a floating license server, and consuming a license, it might occur that Atoll does not get the chance to reset the idle time value to its initial value. In this case, a new Atoll session can steal the license actually allocated to an already running session. This might cause problems in the case where all the licenses are used, the Atoll session performing heavy calculations does not get the chance to initialise the idle time parameter for its license, and a new Atoll session is launched on another computer. In such a situation, the floating license manager considers that the already running session has been inactive or closed, and the license allocated to the already running Atoll session is allocated to the new session. You can modify the default idle time parameter value to a higher value to avoid this effect. To set a different default value for the idle time parameter, add the following lines to the Atoll.ini file: [License] IdleTime = X Where X is the time in minutes. The idle time can be set to infinity by defining IdleTime = 0. 3.3.6 Database Options 3.3.6.1 Running the Database Integrity Checking After Refresh It is advised to perform a database consistency check after you have refreshed the Atoll document contents with the data in your database. You can also add the following optional lines in the Atoll.ini file so that Atoll will ask you if you want to perform a database integrity check after you have refreshed your Atoll document data from the database. [Refresh] ControlIntegrity = 1 When you refresh data in your Atoll document with the data from the database, Atoll will not propose the data integrity check, if you have set ControlIntegrity to 0. If you set ControlIntegrity to 1, Atoll will display a dialogue box asking whether you want to perform the data integrity check or not. © Forsk 2009 AT281_AM_E1 107 Administrator Manual 3.3.6.2 Setting an Automatic Database Integrity Check at Open or Refresh This option automatically performs a data integrity check when opening a document from a database or refreshing data from a database. To turn this feature on, you have to add the following line in the Atoll.ini file: [Database] IntegrityChecker = 1 If this option is set to 1, Atoll performs SELECT filters in the database to guarnatee data integrity.This feature enables selection directly in the database in order to avoid integrity problems in the future. 3.3.6.3 Modifying the Default Database Connection Timeout The ODBC driver has a default command timeout value which could be too short in some cases, such as slow networks. You can change this default timeout value and set a higher value if you encounter problems, during execution of commands on the database, which might be related to timeout. To change the value of the command timeout parameter of the ODBC driver, add the following lines in the Atoll.ini file: [Database] CommandTimeout = X Where X is the timeout value in an integer number of seconds. After X seconds, the command is considered too long to execute. If you set CommandTimeout = 0, there will be no time limit for the execution of the command. 3.3.6.4 Making Atoll Case-Sensitive for Database Import From Planet The network data import from a Planet database into Atoll is not case sensitive by default. You can set this import to case sensitive by adding the following lines in the Atoll.ini file: [PlanetImport] SensitiveCase = 1 Case sensitive means that "Site0" will be considered different from "site0" during import. 3.3.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. 3.3.6.6 Removing Database Modifications History All Atoll documents connected to a database store a history of all the modifications made in the table records. If you delete records from your database, for regionalisation, for example, this does not necessarily decrease the memory consumption due to the modifications history stored in the document. You can have this modifications history erased from your document if you disconnect the document from the database and if you have the following option set in your Atoll.ini file: [Database] RemoveHistoricalRecords = 1 3.3.6.7 Enabling/Disabling Password Prompt at Archive You can instruct Atoll to prompt the user for password before archiving data in a database. If you want Atoll to ask the user to enter the username and password once per Atoll session, add the following lines in the Atoll.ini file: [Database] PromptOnArchive = 1 PromptOnArchive = 1 is the default setting used if this option is not provided in the Atoll.ini file. The user will be prompted for password when he tries to archive data in the database for the first time during an Atoll session. If you want Atoll to ask the user to enter the username and password for every refresh and archive, set: PromptOnArchive = 2 108 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files If you want to disable the prompt for password, set: PromptOnArchive = 0 Notes: 3.3.6.8 • 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. Archiving Data to Databases Using Transactions Atoll supports transactions for archiving data to databases. This approach ensures that users always get consistent data when refreshing their documents with data from the database, even when another user is archiving his modifications at the same time. By default, Atoll uses transactions for archiving data, however you can disable the transaction mode for Atoll by adding the following lines to the Atoll.ini file: [Database] UseTransaction = 0 UseTransaction is set to 1 by default. Caution: • Before modifying this option, make sure that the database server is correctly configured for transactions. 3.3.7 GSM Options 3.3.7.1 Considering Overlapping Zones for IM Calculation Based on Traffic When calculating interference matrices based on traffic, overlapping between coverage areas of different transmitters is taken into account when the option "Best Server" is selected and a positive margin is defined. For interference matrices calculation based on "All" the servers (not Best Server), Atoll does not consider the overlapping to improve performance. However, you can instruct Atoll to consider the overlapping during these calculations as well by adding the following lines in the Atoll.ini file: [Features] IM_TRAFFIC_OVERLAP = 1 3.3.7.2 Setting the Default BSIC Format You can set the default BSIC format to be used by Atoll by adding these lines in the Atoll.ini file: [BsicFormat] DefaultValue = 1 for Octal or 0 for Decimal format DefaultValue enables you to change the default BSIC format (Octal by default) when you create a new Atoll document. 3.3.7.3 Selecting the Interference Matrices Used During the AFP All active interference matrices are taken into account during an AFP session according to the method defined in the Atoll.ini file: [AFP] WorstCaseIM_FskAfp = 0 or 1 This option is valid for Forsk’s AFP. 1 refers to the default method, which is the worst case one. Setting this value to 0 will instruct the AFP to use the second method. • • Worst Case Method: For each interference matrix relationship, the worst case value in all the active interference matrices is taken into consideration. First Value Method: For each interference matrix relationship, the first value found in any active interference matrix is taken into consideration. The order in which the interference matrices are scanned to find the first value is the order of the interference matrices in the Interference Matrices folder in the Explorer window, i.e. the first IM is the one at the top. The First Value method was the default method in earlier versions of Atoll which allowed multiple interference matrix import. © Forsk 2009 AT281_AM_E1 109 Administrator Manual 3.3.7.4 Checking Database Consistency Automatically If you want Atoll to automatically perform a basic data consistency check to avoid incompatibility between redundant fields in GSM GPRS EGPRS documents, add the following lines to the Atoll.ini file: [Refresh] TRXIntegrity = 1 By default, this option is considered to be set to 0, which improves Atoll’s performance. If this option is set to 1, Atoll updates the values of the fields "Number of TRXs" and "Channels" of the Transmitters table, with the values from the TRGs and the TRXs tables respectively, when a document is opened from a database or refreshed. Note: • 3.3.7.5 It is not advised to use this option with a Sybase database. Disabling the Maximum Range Parameter The maximum cell range parameter (System tab of the Predictions folder’s properties dialogue) in GSM GPRS EGPRS documents is used by default and set to 35 km. You can disable this option by adding the following lines in the Atoll.ini file: [Perfos] MaxRangeApplied = No If you set this option to anything other than "No", Atoll will use the maximum range parameter and set it to the default value of 35 km. 3.3.7.6 Enabling the Support for Multi-band Transmitters Atoll is capable of modelling transmitters with subcells (TRX groups) belonging to different frequency domains. To turn on the multi-band modelling feature, add the following lines in the Atoll.ini file: [Studies] MultiBandManagement = 1 MultiBandManagement is set to 0 by default. Enabling multi-band management allows the users to access the multi-band management features through the Frequency Band Propagation button under the Subcells section of the TRXs tab of a transmitter’s properties dialogue, and through the Subcells > Multi-Band Propagation Parameters command in the context menu of the Transmitters folder. In the Multi-Band Propagation Parameters table and in the database, Atoll uses the "@" character to identify the multiband transmitters. Therefore, if you are working on a document with multi-band transmitters, and you have the "@" character in the names of repeaters, remote antennas, or subcells without a donor/main transmitter, Atoll deletes these records with opening the document from a database. If you do not want Atoll to automatically delete such records when opening the document from a database, you have to sett the following option in the Atoll.ini file: [Studies] RemoveBadMultiCells = 0 RemoveBadMultiCells is set to 1 by default. If you are not working with multi-band transmitters, i.e., MultiBandManagement is set to 0, Atoll does not automatically delete such records. If you want Atoll to automatically delete such records when opening the document from a database, you have to sett the following option in the Atoll.ini file: [Studies] CleanMultiCellManagement = 1 CleanMultiCellManagement is set to 0 by default. 3.3.7.7 Setting the Best Server Calculation Method in Same Priority HCS Layers Atoll can calculate serving transmitters according to HCS layer priorities in coverage predictions. The signal level received HCS 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. If there are two HCS layers with the same priority: 110 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files • 1st strategy: The serving transmitter is the one for which the difference between the received signal level and HCS HCS T Rec is the highest. Where, T Rec is the minimum reception threshold for the HSC layer of each respective trans• mitter. 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. 3.3.7.8 Hiding Advanced AFP Parameters You can hide the advanced parameters from the Atoll AFP properties dialogue by adding the following lines in the Atoll.ini file: [AFP] SimpleUserGUI = 1 SimpleUserGUI is set to 0 by default. Setting SimpleUserGUI to 1 hides the Interference Matrices, MAIO, and Advanced tabs. 3.3.7.9 Making Redundant Fields in the Transmitters Table Read-only Some of the fields in the Transmitters table are redundant with other fields in the Subcells table. Modifying values in one table might cause inconsistencies between the two tables in some cases. You can make these redundant fields uneditable in the Transmitters table by adding the following lines in the Atoll.ini file: [GSM] CanEditTRXInfoAtTXLevel = 0 The redundant fields in the Transmitters table are the BCCH and the Number of TRXs fields. CanEditTRXInfoAtTXLevel is set to 1 by default, which means that the fields are editable. 3.3.7.10 Setting the Transmission Diversity Gain If a subcell is using transmission diversity, the air-combining gain of 3 dB is applied to all the received signal levels, wanted (C) as well as interfering (I), during calculations. You can modify the default value of 3 dB by adding the following lines in the Atoll.ini file: [Studies] 2GTxDiversityGain = X Where X is the value of the air-combining gain in dB. 3.3.7.11 Adding Grouped HCS Servers Option in Calculations By default, the Grouped HCS Servers option is not available in the list of choices for Server in coverage predictions, traffic capture, and interference matrix calculations. To make this option available, add the following lines in the atollu-net.ini file: [TMP] ExtraServZone = 1 3.3.8 UMTS and CDMA2000 Options 3.3.8.1 Suppressing Cell Name Carrier Suffixes It is only possible to suppress the carrier suffix in a 3G cell name in the case of a single carrier scenario, i.e., the first carrier is also the last carrier in the global parameters. To do this, add the following lines in the Atoll.ini file: [3GCells] NoSuffixIfUniqueCarrier = 0 or 1 This is set to 0 by default, which means that cell names will follow the normal convention of Atoll, SiteN_X(C). If there is only one carrier, meaning that C is unique, then this option can be set to 1. This will result in cell names which will be same as the transmitter names, SiteN_X. © Forsk 2009 AT281_AM_E1 111 Administrator Manual 3.3.8.2 Enabling Shadowing Margin Calculation for Ec/I0 In order to take the DL SHO gain into account in the Ec/I0 calculations, the Atoll.ini file must contain the following lines: [CDMA] AddPilotSHOGain = 1 Setting AddPilotSHOGain to 0 means that the DL SHO gain is neither calculated nor taken into account. Setting it to 1 means that it will be taken into account in the Ec/I0 calculations. When this parameter is not defined in the Atoll.ini file, Atoll considers the DL SHO gain, i.e., the default value is 1. 3.3.8.3 Using Poisson Distribution in Monte-Carlo Simulations By default in UMTS and CDMA technologies, a number of mobiles are generated in each simulation of a group following a Poisson distribution. This means that there are small variations in the number of randomly distributed mobiles from one simulation to another. To disable this type of distribution, i.e., to have the same number of mobiles generated in each simulation of a group, these lines have to be included in the Atoll.ini file: [CDMA] RandomTotalUsers = 0 Setting RandomTotalUsers to 0 instructs Atoll to use a constant total number of users attempting a connection in all simulations. By default, this option is considered to be set to 1, which means that Atoll will determine a random total number of users attempting a connection in each simulation following a Poisson distribution. 3.3.8.4 Calculating and Displaying Peak or Instantaneous HSDPA Throughput In UMTS HSPA documents, you can choose to display and work with either peak values or instantaneous values of the HSDPA throughputs per mobile, cell, and site in simulation results. To do this, you can add the following lines in the Atoll.ini file: [CDMA] HSDPAThroughputPeak = 0 or 1 • • 0: Instantaneous throughput (Default) 1: Peak throughput If you choose to display the instantaneous HSDPA throughputs, Atoll will: • • • • Display the number of simultaneous HSDPA users in the simulation results. Place a certain part of HSDPA users in a waiting queue during simulations. Display the instantaneous gross and instantaneous application level throughputs per mobile and per cell in the simulation results. Display the instantaneous throughput per site in the Sites tab of the simulation results. If you choose to display the peak HSDPA throughputs, Atoll will: • • • • Not display the number of simultaneous HSDPA users in the simulation results. Display the peak gross and peak application level throughputs per mobile and per cell in the simulation results. Display the MUG table 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. 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. 3.3.8.5 Setting the Power to Use for Intra-cell Interference in HSDPA In HSDPA prediction studies, you can choose whether to perform intra-cell interference calculations based on total cell power (Ptot) or maximum cell power (Pmax). By default, Atoll performs this calculation based on the total power. You can instruct Atoll to use maximum power in stead by adding the following lines in the Atoll.ini file: [CDMA] PmaxInIntraItf = 1 • • 112 0: Intra-cell interference calculation based on total power (Default) 1: Intra-cell interference calculation based on maximum power AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files 3.3.8.6 Enabling Coverage Predictions of Connection Probabilities You can perform coverage prediction studies for connection probabilities in UMTS HSPA documents by adding the following lines in the Atoll.ini file: [CDMA] UseStudyCnxProba = 1 MinUsersPerBin = X This coverage prediction study is available in the list of prediction studies if UseStudyCnxProba is set to 1. Otherwise, it will not be available. MinUsersPerBin is the minimum number of users per pixel required for that pixel to be taken into account in the coverage prediction. 3.3.8.7 Setting the Calculation Method for HS-PDSCH CQI If you choose the “CQI based on CPICH quality” option in Global Parameters, you can select the formula used for calculating HS-PDSCH CQI in Atoll by adding the following lines in the Atoll.ini file: [CDMA] CQIDeltaWithPower = 0 or 1 CQIDeltaWithPower is set to 1 by default. If you set CQIDeltaWithPower to 0, the HS-PDSCH CQI will be calculated using the formula: EC EC  CQI  HS – PDSCH =  CQI  pilot –  ------- +  -------  N T pilot  N T HS – PDSCH 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. 3.3.8.8 Enabling Orthogonality Factor in Pilot EC/NT Calcaultion in HSDPA %Pilot Finger and the Orthogonality Factor model two different effects on the CPICH quality. %Pilot Finger is related to the CPICH physical channel only and models the loss of energy in the CPICH signal due to multipath. The Orthogonality Factor is related to the correlation between the CPICH physical channel and other intra-cell physical channels. You can instruct Atoll to use the Orthogonality Factor in the calculation of pilot EC/NT in HSDPA instead of %Pilot Finger by adding the following lines in the Atoll.ini file: [CDMA] OrthoInCPICH = 1 3.3.8.9 Setting the Maximum Number of Rejections for Mobiles You can define a maximum number of rejections for mobiles during simulations by adding the following lines in the Atoll.ini file: [CDMA] MaxRejections = X If a mobile is rejected X number of times, it will no longer be considered in the next iterations. 3.3.8.10 Setting the Maximum Number of Rejections for HSDPA Mobiles You can set the number of times an HSDPA mobile should be rejected (or placed in a queue) before it is considered permanently rejected (or permanently placed in the queue). The default value of this option is 5. To modify the default value, enter the following lines in the Atoll.ini file: [CDMA] HSDPAMaxRejections = X Where X is the number of times an HSDPA mobile should be rejected to be considered permanently rejected for the simulation. 3.3.8.11 Defining an Offset With Respect to The Thermal Noise You can define an offset with respect to the thermal noise by adding the following lines in the Atoll.ini file: [CDMA] © Forsk 2009 AT281_AM_E1 113 Administrator Manual CutOffSimu = X Where, X is the offset value in dBs. During Monte Carlo simulations, calculations performed on each mobile only take into account the cells whose received power, at the mobile location, is greater than the thermal noise minus this offset. You should set CutOffSimu to 20 dB for optimum performance without losing a lot of interference. 3.3.8.12 Setting Precision of the Rasterization Process During Monte Carlo simulations, Atoll internally converts vector traffic maps to raster traffic maps in order to perform a distribution of users according to the traffic densities and the connection probabilities. The accuracy of this conversion from vectors to raster is high enough for most, nearly all, cases. However, this accuracy might not be enough for highly precise vector polygons defining traffic hotspots. The figure below depicts this effect for a vector polygon which is just slightly larger than 1 raster pixel. The vector polygon and the raster bin have the same traffic density in the following figure. Figure 3.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. Important: • • 114 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. AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files Note: • • 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. 3.3.8.13 Defining the Number of Iterations Before Downgrading You can set the number of iterations that Atoll should carry out before starting the downgrading. The default value of this option is 30. To modify the default value, enter the following lines in the Atoll.ini file: [CDMA] IterBeforeDown = X Where X is the integer number of iterations. 3.3.8.14 Adjusting the Working of the Proportional Fair Scheduler In UMTS HSPA documents, you can adjust how the proportional fair scheduler functions by adding the following lines in the Atoll.ini file: [CDMA] PFSchedulerCQIFactor = X Where X is a number between 0 and 100, which represents the proportional fair scheduler weight. PFSchedulerCQIFactor = 50 by default. If you set PFSchedulerCQIFactor = 0, the proportional fair scheduler functions like the Round Robin scheduler. If you set PFSchedulerCQIFactor = 100, the proportional fair scheduler functions like the Max C/I scheduler. 3.3.8.15 Displaying Ec/I0 of Rejected Mobiles in Simulation Results In UMTS and CDMA simulation results, the Ec/I0 AS1 column in the Mobiles tab may list the Ec/I0 values from the best server for all the mobiles, connected or rejected. To display the Ec/I0 from the best server for the rejected mobiles, add the following lines in the Atoll.ini file: [CDMA] DisplayEcIoOfRejected = 1 DisplayEcIoOfRejected is set to 0 by default. 3.3.8.16 Switching Back to the Old Best Server Determination Method Before Atoll 2.8.0, best server determination in UMTS and CDMA networks used to be performed by selecting the best carrier within transmitters according to the selected method (site equipment) and then the best transmitter using the best carrier. To switch back to this best server determination method, add the following lines in the Atoll.ini file: [CDMA] MultiBandSimu = 0 MultiBandSimu is set to 1 by default. 3.3.8.17 Displaying Automatic Allocation Cost Values You can display the cost values calculated by Atoll for different relations when allocating scrambling codes and PN offsets. To display cost values, add the following lines in the Atoll.ini file: [PSC] DisplayCostValues = 1 DisplayCostValues is set to 0 by default. 3.3.8.18 Selecting SC and PN Offset Allocation Strategies Available in the GUI In the Atoll.ini file, you can select the scrambling code (UMTS and TD-SCDMA) and PN offset (CDMA2000) allocation strategies that will be available to the user in the automatic allocation dialogue. To select the allocation strategies, add the following lines in the Atoll.ini file: © Forsk 2009 AT281_AM_E1 115 Administrator Manual [CDMA] CodeStrategies = 1, 2, 3, 4 The allocation strategies 1, 2, 3, and 4 correspond to the following: 3.3.8.19 • In UMTS: - 1: Clustered - 2: Distributed per Cell - 3: One Cluster per Site - 4: Distributed per Site • In TD-SCDMA: - 1: Clustered - 2: Distributed per Cell - 3: One SYNC_DL Code per Site - 4: Distributed per Site • In CDMA2000: - 1: PN Offset per Cell - 2: Adjacent PN-Clusters per Site - 3: Distributed PN-Clusters per Site Defining a Fixed Interval Between Scrambling Codes You can define a fixed interval between scrambling codes assigned to cells on a same site when the allocation is based on a distributed strategy (Distributed per Cell or Distributed per Site). To apply the defined interval, add the following lines in the Atoll.ini file: [PSC] ConstantStep = 1 ConstantStep is set to 0 by default. 3.3.8.20 Compressed Mode: Restricting Inter-carrier and Inter-technology Neighbour Allocation You can prevent Atoll from allocating inter-carrier and inter-technology neighbours to cells located on sites whose equipment does not support compressed mode, by adding the following lines in the Atoll.ini file: [Neighbours] CompressModeEval = 1 CompressModeEval is set to 0 by default. 3.3.8.21 Setting the Maximum AS Size for SC Interference Prediction You can set the maximum active set size to a fixed number of transmitters for the scrambling code interference coverage prediction by adding the following lines in the Atoll.ini file: [Studies] SCActivesetMaxSize = X Where X is the maximum number of transmitters in the active set. If you set SCActivesetMaxSize = 10, you will get the same results in the coverage prediction as the SC Interference tab in the point analysis. 3.3.9 WiMAX and LTE Options 3.3.9.1 Blocking Access to IEEE Parameters in WiMAX You can disallow modification of the parameters that come from the IEEE specifications, and are not supposed to be changed, by adding the following lines in the Atoll.ini file: [WiMAX] ModifiableIEEEParams = 0 By default, ModifiableIEEEParams is set to 1, which means that all the parameters are modifiable. When you set ModifiableIEEEParams to 0, it means that the following parameters will be unmodifiable in the GUI: • 116 802.16d: AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files • 802.16e: - 3.3.9.2 Under Channel Configuration in the Global Parameters tab of the Transmitters folder’s properties dialogue: Number of Subchannels per Channel and Number of Subcarriers per Channel, i.e. Total, Used, and Data. In the Permutation Zones table: Number of Used Subcarriers, Number of Data Subcarriers, and Number of Subchannels per Channel. In the Frame Configurations table and in the General tab of the properties dialogue of the frame configurations: Number of Preamble Subcarriers. In the Frame Configurations table, the Total Number of Subcarriers changes into a combo box with the following five values: 128, 256, 512, 1024, 2048. Using Only Bearers Common Between the Terminal’s and Cell’s Equipment If you want Atoll to perform an intersection over the bearers supported by the cell equipment and by the terminal equipment, add the following lines in the Atoll.ini file: [OFDM] UseCommonBearersOnly = 1 UseCommonBearersOnly is set to 0 by default. When UseCommonBearersOnly is set to 1, Atoll only uses the bearers for which selection thresholds are defined in both the terminal’s and the cell’s equipment for both downlink and uplink bearer selection. 3.3.9.3 Ignoring Inter-Neighbour Preamble Index Collision The automatic preamble index allocation algorithm in Atoll takes into account the possible collision of preamble indexes assigned to neighbours of a cell. This means that Atoll tries to not allocate the same preamble index to two neighbours of a cell. If you want to disable this constraint, i.e., allow Atoll to allocate the same preamble index to two neighbours of a cell, add the following lines in the Atoll.ini file: [WiMAX] InterNeighbourPICollisions = 0 InterNeighbourPICollisions is set to 1 by default. The preamble index audit based on neighbours also takes this option into account. With InterNeighbourPICollisions = 1, the audit lists the cell pairs that are neighbours of a cell and are allocated the same preamble index. When InterNeighbourPICollisions = 0, the preamble index collision is not verified between neighbours of a cell. 3.3.9.4 Ignoring Inter-Neighbour Physical Cell ID Collision The automatic physical cell ID allocation algorithm in Atoll takes into account the possible collision of physical cell IDs assigned to neighbours of a cell. This means that Atoll tries to not allocate the same physical cell ID to two neighbours of a cell. If you want to disable this constraint, i.e., allow Atoll to allocate the same physical cell ID to two neighbours of a cell, add the following lines in the Atoll.ini file: [LTE] InterNeighbourIDCollisions = 0 InterNeighbourIDCollisions is set to 1 by default. The physical cell ID audit based on neighbours also takes this option into account. With InterNeighbourIDCollisions = 1, the audit lists the cell pairs that are neighbours of a cell and are allocated the same physical cell ID. When InterNeighbourIDCollisions = 0, the physical cell ID collision is not verified between neighbours of a cell. 3.3.10 Measurement Options 3.3.10.1 Displaying Additional Information in Drive Test Data It is possible to display the following additional information in the columns of serving and neighbour cells: • • • BCCH - BSIC pair (GSM GPRS EDGE documents) Scrambling Code - Scrambling Code Group pair (UMTS HSPA documents) PN Offset - PN Offset Group pair (CDMA2000 1xRTT 1xEV-DO documents) You have to add the following lines in the Atoll.ini file to display this information: [TestMobileData] ShowCoupleInfo = 1 Setting ShowCoupleInfo to 0 hides this information. © Forsk 2009 AT281_AM_E1 117 Administrator Manual 3.3.10.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. 3.3.10.3 Recalculating Distances of Points From There Serving Cells at Import If you want Atoll to calculate the distance of each measurement point from its nearest serving cell, you can add the following lines in the Atoll.ini file: [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. 3.3.10.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. 3.3.10.5 Importing Drive Test Data with Scrambling Codes as Integers You can force the conversion of scrambling codes to integer values when importing drive test data by adding the following option in the Atoll.ini file: [TestMobileData] FloatingPointScramblingCodeSupport = 1 FloatingPointScramblingCodeSupport is set to 0 by default, and the scrambling codes are imported according to the numeric data type selected for the scrambling code column in the import dialogue. 3.3.11 Other Options These options concern the Best Signals Export add-in which is available from Forsk on demand. 3.3.11.1 Best Signals Export for Active Transmitters Only The Best Signal Export add-in offers an option to calculate the path loss matrices for transmitters whose current path loss matrices are either invalid or do not exist. As calculating path loss matrices can be a time-consuming task, it is important to filter out the transmitters that do not have any influence on the results of the add-in. These transmitters might be the ones that have missing or invalid path loss matrices, and are inactive. The default option in the current version of the addin only considers transmitters that are active. If you want to instruct the add-in to consider all active and inactive transmitters, add the following lines in the Atoll.ini file (not the BestSignalsExport.ini file): [Transmitter] GetSortedSignalsActiveOnly = 0 For further information about the add-in and its features, please refer to the Best Signals Export User Manual available on Forsk’s support website. 118 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files 3.3.11.2 Best Signals Export for Transmitters, Repeaters, and Remote Antennas By default, the add-in exports the best signals for a transmitter, its remote antennas, and its repeaters combined. If you want the add-in to export separate coverages for transmitters, remote antennas, and repeaters, add the following lines in the Atoll.ini file (not the BestSignalsExport.ini file): [Transmitter] GetSortedSignalsCombineTxRepAndRa = 0 If you want the add-in to export separate coverages for remote antennas and repeaters and not export any coverage for their transmitters, add the following lines in the Atoll.ini file (not the BestSignalsExport.ini file): [Transmitter] GetSortedSignalsRepeatersOnly = 1 3.4 The ACP Initialisation File The ACP initialisation file is used to inform Atoll of the preferred settings when the ACP is used for automatic cell planning during Atoll sessions. It can be used to adjust the behaviour of the ACP. You can comment out any option in the acp.ini by preceding the line with a semi-colon (";") or with a hash mark ("#"). Caution: • The ACP initialisation file is a powerful tool. You should not modify any option in the acp.ini file until and unless you are absolutely sure of what you are doing. In order for the ACP initialisation file to be used by Atoll, you should place the acp.ini file in the Atoll installation directory. The following sections describe the options available in the acp.ini file. 3.4.1 Managing Preferences For any setting in the acp.ini file can be overridden by creating an equivalent setting in the Windows registry. For example, to override a setting called KEY_NAME in the acp.ini section called SECTION_NAME, you must the following Windows registry entry of the type REG_SZ: HKEY_CURRENT_USER\Software\Forsk\acp\SECTION_NAME\KEY_NAME In the [ACPSettingManagement] section, the following setting defines what will be loaded first: the settings from the acp.ini file or the user-specific settings of the Windows registry. By loading user settings first, you can override the user-specific settings with the settings in the acp.ini file. The default is to load acp.ini first. [ACPSettingManagement] isUserSettingFirst=0 3.4.2 GUI-Related Preferences In this section are the settings defining default values and defining certain aspects of the GUI configuration. 3.4.2.1 Default Values on the General Tab In the [ACPGeneralPage] section, you can find the options used to set default values for the General tab. The following options can be used to set default values for the number of interations and resolution: [ACPGeneralPage] nbIteration=100 resolution=50 Other options can be used to define the default values for calculating cost: cost.type=0 # 0=off, 1=limt_to_max, 2=apply_cost_to_change_plan cost.maxCost=50 cost.azimuth.cost=1 cost.azimuth.isSiteVisit=true cost.tilt.cost=1 cost.tilt.isSiteVisit=true cost.antenna.cost=1 © Forsk 2009 AT281_AM_E1 119 Administrator Manual cost.antenna.isSiteVisit=true cost.etilt.cost=0.1 cost.etilt.isSiteVisit=false cost.power.cost=0.1 cost.power.isSiteVisit=false cost.siteVisitCost=2 cost.upgradeSiteCost=5 cost.newSiteCost=10 cost.removeSiteCost=-5 3.4.2.2 Default Values on the Objectives Tab In the [ACPObjectivePage] section are the settings defining default values for the Objectives tab. The following options are used to define the default values for UMTS Ec/Io: [ACPObjectivePage] umts.ecIoThreshold=-13 umts.ecIoCoverage=90 umts.ecIoCoverageType=2 # 0=absoluteValue, 1=relativeValue, 2=noCoverage umts.ecIoDeltaCoverage=5 umts.isEcioTrafficWeight=1 The following options are used to define the default values for UMTS RSCP: umts.ecThreshold=-85 umts.ecCoverage=90 umts.ecCoverageType=0 # 0=absoluteValue, 1=relativeValue, 2=noCoverage umts.ecDeltaCoverage=5 umts.isEcTrafficWeight=0 The following option is used to define the default value for the minimisation of interference: umts.interferenceWeight=1 # 0=none, 1=low, 2=high The following option is used to define the default respective weights given to RSCP and Ec/Io: umts.rscpEcioWeight=2 # 0=rscpOnly, 1=rscpPrefered, 2=normal, 3=ecIoPrefered, 4=ecIoOnly The following options are used to define the default value for the overlap margin in UMTS and WiMAX: umts.overlapMargin=5 wimax.overlapThreshold=5 The following options are used to define the default values for reception levels in GSM: gsm.slThreshold=-85 gsm.slCoverage=90 gsm.slCoverageType=0 # 0=absoluteValue, 1=relativeValue, 2=noCoverage gsm.slDeltaCoverage=5 gsm.isSlTrafficWeight=0 gsm-imported.slCoverageType=1 # 0=absoluteValue, 1=relativeValue, 2=noCoverage gsm-imported.slDeltaCoverage=0 The following options are used to define the default values GSM cell dominance: gsm.cdNbServer=3 gsm.cdThreshold=10 gsm.cdCoverage=90 gsm.cdCoverageType=2 # 0=absoluteValue, 1=relativeValue, 2=noCoverage 120 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files gsm.cdDeltaCoverage=5 gsm.isCdTrafficWeight=0 gsm-imported.cdCoverageType=1 # 0=absoluteValue, 1=relativeValue, 2=noCoverage gsm-imported.cdDeltaCoverage=0 The following option is used to define the default respective weights given to GSM reception level and GSM cell dominance: gsm.slCdWeight=2 4=DomOnly # 0=rxlevOnly, 1=rxlevPrefered, 2=normal, 3=DomPrefered, The following options are used to define the default values for reception levels in WiMAX: wimax.slThreshold=-85 wimax.slCoverage=90 wimax.slCoverageType=0 # 0=absoluteValue, 1=relativeValue, 2=noCoverage wimax.slDeltaCoverage=5 wimax.isSlTrafficWeight=0 The following options are used to define the default values for WiMAX CINR: wimax.cinrNbServer=3 wimax.cinrThreshold=10 wimax.cinrCoverage=90 wimax.cinrCoverageType=2 # 0=absoluteValue, 1=relativeValue, 2=noCoverage wimax.cinrDeltaCoverage=5 wimax.iscinrTrafficWeight=0 The following options are used to define the default calculation method for WiMAX CINR: wimax.cinrMethod=0 # 0=use frequency plan, 1=ignore frequency plan wimax.cinrUseSegmentation=1 The following option is used to define the default respective weights given to WiMAX reception level and WiMAX CINR: wimax.slCdWeight=2 # 0=rxlevOnly, 1=rxlevPrefered, 2=normal, 3=CinrPrefered, 4=CinrOnly The following options are used to define whether shadowing is used and, if so, what the cell edge probability should be set at (as a percentage): param.shadowingMargin=false param.cellEdgeCoverage=75 The following option defines whether or not indoor coverage is used. By default, when this option is set to "true," all pixels will be considered to be indoors. Note: • On the Advanced tab of ACP Setup dialogue, you can define which individual clutter classes are to be considered as indoors. For more information, see the User Manual. param.indoorCov=false 3.4.2.3 Default Values on the Reconfiguration Tab In the [ACPReconfPage] section are the settings defining default values for the Reconfiguration tab. The following options enable you to define the default reconfiguration that will be done: pilot power, antenna, azimuth, and mechanical tilt optimisation. Note: • The options in this section do not select the default reconfiguration options when set to "1", instead they disable those reconfiguration options. ; [ACPReconfPage] umts.disablePilotPowerOptimization=0 © Forsk 2009 AT281_AM_E1 121 Administrator Manual wimax.disablePreamblePowerOptimization=0 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 defaultTxTiltMin=0 defaultTxTiltMax=5 defaultTxTiltStep=1 defaultTxETiltMin=0 defaultTxETiltMax=10 The following option is used if the precalculated path loss matrix module is available and used. Note: • This option should be set to "0" if all of the propagation models used are natively supported by the ACP and you do not need the precalculated path loss matrix module. allowPrecalcMatricesModule=1 3.4.2.4 Activating Support for Volcano Propagation Models If you want to activate support for Volcano propagation models, you can add a section called [VolcanoPM] and enter the following option: enable=1 # ACP support for Volcano propagation models are activated. If "enable" is set to "0," or if the option is not in the acp.ini file, access to Volcano propagation models is not supported by ACP. 3.4.2.5 Default Values on the Antennas Tab In the [ACPAntennaPage] section are the settings defining default values for the Antennas tab. The following options enable you to define default regex pattern that will is used to automatically calculating antenna groups: [ACPAntennaPage] autoGroupPattern=(.*)_ autoGroupPattern_ant=(.*)_ autoGroupPattern_group=(.*)_ By setting the following option to "1" (default), ACP will automatically apply the default antenna configuration each time a new setup is created (i.e., the configuration which have have been backed up by a user): autoRestoreDefaultConfig=1 3.4.2.6 Displaying Custom Site and Antenna Fields In the [ACPCustomFieldExtraction] section, you can set options that will enable ACP to extract data from custom fields in the SITE and ANTENNA tables of the Atoll database. ACP can use the information in the custom fields to extract the status (candidate or existing) of sites for site selection or to group antennas. The custom columns in the SITE and ANTENNA tables must match the column names defined in the "site.status" and "antenna.model" options of the acp.ini file, respectively: • • 122 Status of sites: By using the "site.status" option to define the name of the custom status column in the SITE table, you can extract the status (candidate or existing) of sites for site selection. All sites in the SITE table with the label set to the one defined by the "site.status.candidate" option will be automatically set as candidate sites. Any sites with a label other than the one defined by the "site.status.candidate" option will be considered as existing sites. By default, all active sites are considered as existing sites. Grouping antenna patterns: You can group antenna patterns into groups of physical antennas (i.e., all patterns related to the same physical antenna) and group the physical antennas at different frequencies into radomes by AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files using the "antenna.model" option. Using the "antenna.model" enables you to form a multi-band antenna. [ACPCustomFieldExtraction] site.status=acp_status # Name of the custom column in SITE table. Default value is 'acp_status'. site.status.candidate=candidate # Name used to define a candidate site. Default value is 'candidate'. antenna.model=acp_model # Name of the custom column in ANTENNA table. Default is 'acp_model'. 3.4.2.7 Defining the Appearance of the Optimisation Dialogue In the [ACPMapPage] section are the settings defining the appearance of the Optimisation dialogue that appears when running an optimisation. Some options refer to the Graphs tab and some to the Quality Maps tab. 3.4.2.7.1 Defining the Colours in the Quality Analysis Maps The following settings in the [ACPMapPage] section are used to define the colours used in the quality analysis maps on the Quality Maps tab. The settings are the same for a series of keys: • • • • • • • • • • • • • • • • • • • • • • • • • colormap.obj1: This key is used on the result/quality map window for UMTS 'RSCP', GSM 'BCCH SigLev', WiMAX 'Preamble SigLev'. colormap.obj2: This key is used on the result/quality map window for UMTS 'EcIo'. colormap.slCn: This key is used on the result/quality map window for WiMAX 'C/N' and CINR. colormap.gain1: This key is used on the result/quality map window for 'RSCP Gain', 'BCCH SigLev' gain, 'Preamble SigLev' gain. colormap.gain2: This key is used on the result/quality map window for 'EcIo Gain'. colormap.gain: This key is used on the overlay map that appears during a run. colormap.cellOverlapGain: This key is used on the result/quality map window for gain in overlapping areas. colormap.cellOverlap: This key is used on the result/quality map window for overlapping areas and GSM Cell Dominance. colormap.ececioCoverage: This key is used on the result/quality map window for Ec and Ec/Io. colormap.imprCoverage: This key is used on the result/quality map window for improved coverage. colormap.changeImpr: This key is used on the result/quality map window for the amount of improvement. colormap.changeCost: This key is used on the result/quality map window for a change of cost. colormap.changeType: This key is used on the result/quality map window for a change of antenna type. colormap.changeSelectionType: This key is used on the result/quality map window for a change of selection type. colormap.changeTilt: This key is used on the result/quality map window for a change of mechanical tilt. colormap.changeAzimuth: This key is used on the result/quality map window for a change of azimuth. colormap.changePilot: This key is used on the result/quality map window for a change in pilot power. colormap.changeEtilt: This key is used on the result/quality map window for a change in electrical tilt. colormap.bestcellEtilt: This key is used on the result/quality map window for the electrical tilt in the best serving cell. colormap.bestcellSector: This key is used on the result/quality map window for the serving sector of the best serving cell. colormap.bestcellEc: This key is used on the result/quality map window for Ec of the best cell. colormap.bestcellEcio: This key is used on the result/quality map window for Ec/Io of the best cell colormap.overlapRatio: This key is used on the result/quality map window for the percentage of overlap. colormap.diff: This key is used on the result/quality map window colormap.userWeighting: This key is used on the result/quality map window for the defined user weighting. Each key has a series of options. The first option, "nbRange," defines the number of steps in the total range of possible values. Then, for each step, the first and last value is defined along with the RGB values of the colour that is used to display it on the map. The following is an example of the first keys. The remaining keys can be defined in the same manner. [ACPMapPage] colormap.obj1.nbRange=10 colormap.obj1.range.0=[-99999.000000 -105.000000] RGB(0 0 255) colormap.obj1.range.1=[-105.000000 -100.000000] RGB(0 128 255) colormap.obj1.range.2=[-100.000000 -95.000000] RGB(0 196 196) colormap.obj1.range.3=[-95.000000 -90.000000] RGB(0 224 128) colormap.obj1.range.4=[-90.000000 -85.000000] RGB(0 224 0) colormap.obj1.range.5=[-85.000000 -80.000000] RGB(64 255 0) colormap.obj1.range.6=[-80.000000 -75.000000] RGB(196 255 0) colormap.obj1.range.7=[-75.000000 -70.000000] RGB(255 224 0) colormap.obj1.range.8=[-70.000000 -65.000000] RGB(255 128 0) colormap.obj1.range.9=[-65.000000 99999.000000] RGB(255 0 0) © Forsk 2009 AT281_AM_E1 123 Administrator Manual colormap.obj2.nbRange=8 colormap.obj2.range.0=[-99999.000000 -15.000000] RGB(0 0 255) colormap.obj2.range.1=[-15.000000 -13.000000] RGB(0 128 255) colormap.obj2.range.2=[-13.000000 -11.000000] RGB(0 196 196) colormap.obj2.range.3=[-11.000000 -9.000000] RGB(0 224 0) colormap.obj2.range.4=[-9.000000 -7.000000] RGB(128 255 0) colormap.obj2.range.5=[-7.000000 -5.000000] RGB(255 224 0) colormap.obj2.range.6=[-5.000000 -3.000000] RGB(255 128 0) colormap.obj2.range.7=[-3.000000 99999.000000] RGB(255 0 0) colormap.gain1.nbRange=8 colormap.gain1.range.0=[-99999.000000 -9.000000] RGB(0 0 255) colormap.gain1.range.1=[-9.000000 -6.000000] RGB(0 128 255) colormap.gain1.range.2=[-6.000000 -3.000000] RGB(0 196 212) colormap.gain1.range.3=[-3.000000 0.000000] RGB(0 224 196) colormap.gain1.range.4=[0.000000 3.000000] RGB(0 255 0) colormap.gain1.range.5=[3.000000 6.000000] RGB(255 255 0) colormap.gain1.range.6=[6.000000 9.000000] RGB(255 128 0) colormap.gain1.range.7=[9.000000 99999.000000] RGB(255 0 0) colormap.gain2.nbRange=8 colormap.gain2.range.0=[-99999.000000 -3.000000] RGB(0 0 255) colormap.gain2.range.1=[-3.000000 -2.000000] RGB(0 128 255) colormap.gain2.range.2=[-2.000000 -1.000000] RGB(0 196 212) colormap.gain2.range.3=[-1.000000 0.000000] RGB(0 224 196) colormap.gain2.range.4=[0.000000 1.000000] RGB(0 255 0) colormap.gain2.range.5=[1.000000 2.000000] RGB(255 255 0) colormap.gain2.range.6=[2.000000 3.000000] RGB(255 128 0) colormap.gain2.range.7=[3.000000 99999.000000] RGB(255 0 0) colormap.gain.nbRange=10 colormap.gain.range.0=[-99999.000000 -4.000000] RGB(0 0 255) colormap.gain.range.1=[-4.000000 -2.000000] RGB(0 128 255) colormap.gain.range.2=[-2.000000 -1.000000] RGB(0 196 196) colormap.gain.range.3=[-1.000000 0.000000] RGB(0 224 128) colormap.gain.range.4=[0.000000 1.000000] RGB(0 224 0) colormap.gain.range.5=[1.000000 2.000000] RGB(64 255 0) colormap.gain.range.6=[2.000000 3.000000] RGB(196 255 0) colormap.gain.range.7=[3.000000 4.000000] RGB(255 224 0) colormap.gain.range.8=[4.000000 5.000000] RGB(255 128 0) colormap.gain.range.9=[5.000000 99999.000000] RGB(255 0 0) 3.4.2.7.2 Other Components of the Optimisation Dialogue The following settings in the [ACPMapPage] section are used to define other components of the Optimisation dialogue that appears when running an optimisation. Some options refer to the Graphs tab and some to the Quality Maps tab. The following options define the background and foreground colours of the Quality Maps tab, with the RGB code as an integer: config.background=0 # RGB code as integer: here black config.foreground=16843008 # RGB code as integer(R*2^16+G*256+B): here white 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 124 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files 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 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. 3.4.2.8 Defining the Appearance of New Maps In the [ACPMapDefault] section is the option for defining the appearance of new maps created from optimisation results. The following option defines the transparency of new maps: transparency=50 3.4.2.9 Defining the Functionality of the Commit Tab In the [ACPCommitPage] section is the option for defining whether the user can only edit the set of changes to be committed Change Details tab (default). Setting "allowUserChangeForCommit" to "true" allows the user to edit the set of changes on the Commit tab; this setting is not recommended. allowUserChangeForCommit=false 3.4.2.10 Defining the Appearance of the Overlay Window In the [ACPOverlayDialog] section is the option for defining whether the user can only edit the set of changes to be committed Change Details tab (default). Setting "allowUserChangeForCommit" to "true" allows the user to edit the set of changes on the Commit tab; this setting is not recommended. allowUserChangeForCommit=false 3.4.2.11 Exporting Optimisation Results in XML In the [ACPXmlReport] section are the options for defining the contents and appearance of an XML report generated from the Statistics tab of the optimisation Properties dialogue. enableXmlExport=1 #enable the xml report from the ResultStatPage generateXmlSection=-1 # bit combination of following: 1=metadata, 2=setup, 4=resultSummary, 8=resultSectors, 16=resultIterations, 32=resulstChangeset, 64=resultMaps., -1=all © Forsk 2009 AT281_AM_E1 125 Administrator Manual encoding=UTF-8 saveDefaultStylesheet=1 #save a default styleshhet if none exist defaultStylesheetName=.acpReport.xslt # name of the default stylesheet file. set it empty to disable stylesheet processing instruction 3.4.3 The Core ACP Engine Settings The settings in the [ACPCore] section are used to define how the ACP engine functions. 3.4.3.1 Log File Settings ACP enables you to set up a log file as well as create a crash report in case of an application crash. The following option defines whether ACP generates a log file (with the name ATL_NAME_optim.log): generateLogFile=0 # The default is "0"; no log file. The following option defines the crash reporter will run in case of an application crash. useCrashReport=1 When the crash reporter is enabled, if the application crashes, ACP provides the possibility of sending information by e-mail that can be used to help determine the reason the application crashed. No sensitive project-related information is sent. By default the support e-mail is set to Forsk support. You can change this by editing the following option in the XCrashReport.ini file: [Email] Adress=support@theoperator.com Name=Support_name 3.4.3.2 Configuration File Settings You can save default setup options in a general configuration file using the ACP - Automatic Cell Planning Properties dialogue. For information on using the properties dialogue, refer to the technology-specific chapter of the User Manual. The following option defines the general configuration file to be used: generalCfgFile=c:\myConfig\myDefaultPrj.cfg # complete path to cfg file Note: • 3.4.3.3 Any settings in the general configuration file will overwrite any option which can also be defined either in the acp. Calculation Thread Pool Settings The following options define how the calculation thread pool will be managed. If "useComputationThreadPool" is set to "false," ACP uses only one thread. If "useComputationThreadPool" is set to "true," ACP uses the number of threads specified by the "computationThreadPoolSize" option. The default setting for "computationThreadPoolSize" is "-1" and means that ACP will use one thread per processor core available. useComputationThreadPool=true computationThreadPoolSize=-1 3.4.3.4 Memory Management Settings The following options define how the ACP manages memory during calculations. The ACP tries to estimate the worst-case scenario in memory use, and indicates to the user when memory use seems too high. Using one of the following options, you can define the method ACP uses to indicate excessive memory use: • • • memLimitNumPos: Memory use is determined to be excessive when the maximum number of pixels, as defined in "memLimitNumPos" is reached during a calculation. Setting "memLimitNumPos" to "-1" deactivates this option. memLimitMemory: Memory use is determined to be excessive when the estimated memory use in Mb, as defined in "memLimitMemory" is reached during a calculation. Setting "memLimitMemory" to "-1" deactivates this option. memLimitUseableMemory: Memory use is determined to be excessive when the estimated memory use exceeds 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. 126 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files 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 "memLimitNumPos", 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. Note: • 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 3.4.3.5 RSCP and Macro Diversity Gain Calculation Options The following options determine how ACP calculates the signal level and the macro diversity gain mode. 3.4.3.5.1 Signal Level You can define how ACP measures the signal level (UMTS RSCP, GSM BCCH Power, WiMAX Preamble 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. linkMode = 0 # The default 3.4.3.5.2 Macro Diversity Gain (UMTS Only) The following option defines whether ACP takes macro diversity gain into account in UMTS. "addPilotSHOGain" can have the following values: • • 0: When "addPilotSHOGain" is set to "0," ACP does not take macro diversity gain into account. 1: When "addPilotSHOGain" is set to "1," ACP takes macro diversity gain into account. This is the default value. Warning: Any changes you make here must match corresponding changes in the atoll.ini file. When "addPilotSHOGain" is set to "0," the ACP results will only match the results in Atoll if the following settings are made in the [CDMA] section of the atoll.ini file: AddPilotSHOGain=0 SHOGainAdvanced=0 addPilotSHOGain=1 # The default 3.4.3.6 Determining Transmitter Altitude The following option defines how ACP determines the transmitter altitude when no site altitude is defined in Atoll. "addPilotSHOGain" can have the following values: • • 0: When "useSiteAltitude" is set to "0," ACP uses the exact transmitter coordinates, including dx and dy offset. 1: When "useSiteAltitude" is set to "1," ACP uses only the coordinates of the site. This is the default value. Warning: 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 3.4.3.7 Balancing Speed, Memory Use, and Accuracy in Calculations On the User Preferences tab of the ACP - Automatic Cell Planning Properties dialogue, ACP enables you to select a mode of operation that balances balance speed, memory use, and accuracy. By defining the settings of the options in the acp.ini file that each mode uses, you can fine-tune how ACP will operate in the selected mode: © Forsk 2009 AT281_AM_E1 127 Administrator Manual • • • High Speed: Using the highest speed also uses the least memory although the final results are slightly less accurate. Default: When no changes are made to the acp.ini file, ACP uses the default settings. The default settings can be overridden by changing the settings in this section. High Precision: When the settings in this section are defined to give the results of the highest precision, calculating the results will take the longest time and will use more memory. The options descibed 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 analagous 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 analagous options for the high speed mode and the high precision mode are "threshLevelMonitorCellSpeed" and "threshLevelMonitorCellPrec", respectively. threshLevelCalcCell: The "threshLevelCalcCell" defines the best server signal threshold (dB) in order to be used when calculating interference. The analagous options for the high speed mode and the high precision mode are "threshLevelCalcCellSpeed" and "threshLevelCalcCellPrec", respectively. The following options define the values ACP uses for default mode: maxMonitorCell=32 threshLevelMonitorCell = 35 threshLevelCalcCell = 27 The following options define the values ACP uses for high speed mode: maxMonitorCellSpeed=30 threshLevelMonitorCellSpeed = 30 threshLevelCalcCellSpeed = 25 The following options define the values ACP uses for high precision mode: maxMonitorCellPrec=35 threshLevelMonitorCellPrec = 40 threshLevelCalcCellPrec = 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 3.4.3.8 Extracted Traffic Settings The ACP extracts traffic directly from Atoll using randomly generated users for the selected maps. Because the traffic is generated randomly (as opposed to accessing traffic density directly), many more positions than there are pixels are requested during the extraction of traffic. Internal density maps are then built from these random traffic snapshots. The accuracy of this process depends both on the resolution of the extracted traffic defined during the setup process and the selected ACP mode of operation for (high speed, default, or high precision, see "Balancing Speed, Memory Use, and Accuracy in Calculations" on page 127). For example, using the default settings, ACP requests ten times more random users than the number of pixels derived from the resolution of the extracted traffic. You can increase the precision (but also the traffic extraction time) with which ACP extracts traffic from traffic maps by increasing the values of the following options: noUniformTrafficLowFactor=5 # Using high speed settings noUniformTrafficNormFactor=10 # Using default settings 128 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files noUniformTrafficHighFactor=20 # Using high precision settings 3.4.3.9 Accessing Raster Data By default, ACP accesses all raster files (DEM, clutter class files, clutter height files) using the Atoll API. When using external, as opposed to embedded, raster files, you can increase how quickly ACP loads the raster data by allowing ACP to access the files directly instead of through Atoll. You can enable ACP to access the files directly using the following option: useExternalGisDataFile=1 Notes: • • • When you set "useExternalGisDataFile" to "1," enabling ACP to access raster files directly, a new tab, the Parameters tab, appears on the ACP Setup dialogue. You must define the each raster file ACP will use on the Parameters tab. If the same raster files are used for each Atoll session, you should identify the raster files in the configuration file, so that it is no longer necessary to enter the data each time. When ACP accesses raster files directly, only single-layer raster files are supported. The raster files must be in either BIL or TIFF format. When ACP accesses raster files directly, you can define the georeferencing mode for raster files in BIL format: • • • 0: Edge: The upper North-East coordinate of the BIL raster file corresponds to the edge of the raster file. 1: Centre: The upper North East coordinate of the BIL raster file corresponds to the center of the first pixel of the raster file. 2: Auto: ACP detects automatically the correct georeferencing mode for the BIL raster file The default setting is "2," which enables ACP to automatically select the correct mode and is the recommended setting. bilGeoMode=2 # The default is 2 (auto) 3.4.3.10 Accessing Path Loss Matrices You can define how ACP accesses path loss matrices using the "pathlossAccessMode" option. This option has two possible values: • • • 0: If this option is set to "0," ACP will access path loss matrices through Atoll. 1: If this option is set to "1," ACP will access path loss matrices directly. With this setting, the path loss matrices must be stored externally; they can not be embedded. 2: If this option is set to "2," ACP will access path loss matrices directly if they are external, otherwise through Atoll if they are embedded. This is the default value. pathlossAccessMode=2 3.4.3.11 Specific WiMAX Parameters You can define how ACP takes segmentation into account using the "wimaxPreambleSegmented" option. This option enables you to take into account the change in change in calculation methods from version 2.7.1 to version 2.8.0 of Atoll. In version 2.7.1, the preamble was not considered as segmented unless the frame configuration used by the cell was flagged as segmented. In version 2.8.0, the preamble is considered by default to be segmented. This option has the possible values: • • • 0: This value is intended for versions of Atoll up to and including version 2.7.1. If this option is set to "0," ACP will only take preamble segmentation into account if the segmentation flag of cell frame configuration is set to ON. 1: This value is intended for versions of Atoll of 2.8.0 and up. If this option is set to "1," ACP always takes preamble segmentation into account. 2: If this option is set to "2," ACP automatically detects the version of Atoll used. This is the default value. wimaxPreambleSegmented=2 3.4.4 Miscellaneous Configuration Settings In the [ACPMisc] section are several additional ACP configuration options. 3.4.4.1 Validity of Coverage Predictions You can use the following option to enable or disable the automatic verification of the validity of coverage predictions before running an optimisation setup. autoCheckPredictionValidity=1 © Forsk 2009 AT281_AM_E1 129 Administrator Manual If "autoCheckPredictionValidity" is set to "1," thereby enabling the verification of the validity of coverage predictions, you can have ACP automatically recalculate the invalid coverage predictions using the following option. If it is set to "0," ACP will not automatically recalculate predictions. autoPathlossRecomputation=0 3.5 XML Studies File The .xml file can be created if you want to share customized coverage prediction studies. It contains descriptions of coverage prediction studies, including: • • • General parameters: name of study template, comments, group, sort, and filter criteria. Study conditions: study criterion, lower and upper thresholds, servers to be studied, margin, carrier, etc. Display settings: display type, visibility scale, add to legend option, tips text, transparency level, etc. This file can be created in any folder in order to be imported from a specific path according to the user type. All the studies described in these .xml files can be used as study templates available for users in their Atoll documents. 3.5.1 Creating an XML Studies file An .xml study file is a UTF-8 encoded XML file that can be viewed in any XML-ready application, such as Internet Explorer or XMLSpy. It is recommended to create this .xml file in Atoll to ensure that it has the correct structure and can be later opened and read again by Atoll. However, it is possible to modify the contents of this file in an XML editor in order to make specific changes. You can create this file from Atoll by saving a coverage prediction study as a template. To save a coverage prediction study as a template in a specific .xml file: 1. Expand the Predictions folder of the Explorer window. 2. Right-click the coverage prediction study that you want to save as a template. 3. Select "Save as a template" from the context menu. You can save the additional customized study in an existing .xml study file. In that case, this file, which already contains a list of customized study definition is completed with this last study. If you indicate a new .xml study file, this one is created with a single customized study in it. 3.5.2 Using an XML Studies file It is possible to import a specific .xml study file in order to place a list of customized studies with predefined settings in the prediction creation dialogue. The interest of browsing an .xml study file is to have a specific list of customized studies for a particular type of user. To use an existing .xml study file: 1. Right-click the Predictions folder of the Explorer window. 2. Select "New" from the context menu. 3. Click the Browse button in order to locate the appropriate file. 4. When found, click OK to import the customized study list contained in it. The customized study list new appears in the bottom part of the prediction creation dialogue. 3.5.3 XML Studies File Example <?xml version="1.0" encoding="UTF-8"?> <CoverageTRXStudy> <Name>Coverage by Signal Level</Name> <Display> <minZoom>500</minZoom> <maxZoom>20000000</maxZoom> <visible>Yes</visible> <Type>ByIntervals</Type> <FieldSelector>80000008</FieldSelector> <Opacity>50</Opacity> <Items> <Item> <Min>-70.</Min> 130 AT281_AM_E1 © Forsk 2009 Chapter 3: Administration Files <Legend>Best signal level (dBm) >=-70</Legend> <MainColor>255 0 0</MainColor> <SecondaryColor>0 0 0</SecondaryColor> <LineStyle>5</LineStyle> <LineWidth>15</LineWidth> <FillStyle>1</FillStyle> </Item> ... <Item> <Min>-100.</Min> <Legend>Best signal level (dBm) >=-100</Legend> <MainColor>0 147 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> </Display> <AddToLegend>1</AddToLegend> <Resolution>100</Resolution> <LockedStudy>0</LockedStudy> <ComputeHisto>1</ComputeHisto> <HistoPerTx>0</HistoPerTx> <HistoLabel>Best signal level (dBm)</HistoLabel> <Conditions> <FieldDbm> <Min>-100.</Min> </FieldDbm> <Reliability>0.75</Reliability> <TRXType>BCCH</TRXType> <DefTrgThreshold>1</DefTrgThreshold> <Indoor>0</Indoor> <WithShadowing>1</WithShadowing> </Conditions> </CoverageTRXStudy> © Forsk 2009 AT281_AM_E1 131 Administrator Manual 132 AT281_AM_E1 © Forsk 2009 Chapter 4 Atoll Management Console This chapter describes the Atoll Management Console’s concepts, features and functions and how to access and perform the tasks it offers. Atoll RF Planning & Optimisation Software Administrator Manual 134 AT281_AM_E1 © Forsk 2009 Chapter 4: Atoll Management Console 4 Atoll Management Console 4.1 Introduction The Atoll Management Console facilitates creating and upgrading Atoll databases2. The Atoll Management Console provides the database administrator the possibility of globally managing the database with the easy-to-use step-by-step procedures which use wizard interfaces. The Atoll Management Console comprises the following management tools: • • • • • • • 4.2 Creating a master database Upgrading a master database Creating project databases Refreshing the project databases Managing shared Atoll administration file paths for user groups Managing user accounts and access rights Managing a history of data modifications in databases Atoll Management Console Installation Following sections list the requirements for installing and the installation procedure for installing the Atoll Management Console. 4.2.1 Installation Requirements You can install the Atoll Management Console once you have installed Atoll. Atoll Management Console supports Oracle, and Microsoft SQL Server. 4.2.2 Installation Procedure You need administrator rights to the computer on which you want to install the Atoll Management Console. The setup wizard is simple and lets you configure your installation according to your requirements. Follow the instructions below, in order to install the Atoll Management Console successfully. 1. Close all programs. 2. Insert the Atoll installation CD ROM in the workstation CD drive. This will launch the Autorun program. If the Autorun does not launch automatically, you can open the contents of the CD in Explorer and run the setup program manually. 3. Click the Install Atoll Management Console command in the Autorun program to launch the installation. This will run the Atoll Management Console setup wizard, which will guide you through the setup process. Figure 4.1: Atoll Management Console Setup 4. Select the destination directory for the installation. 2. In this chapter, Atoll databases refer to the RDBMS consisting of Atoll’s tables containing their respective fields and values, which can be used with Atoll Management Console, i.e., Oracle and Microsoft SQL Server. © Forsk 2009 AT281_AM_E1 135 Administrator Manual Figure 4.2: Atoll Management Console Setup - Installation Directory Selection The installation directory proposed by the setup program may be different from the Atoll installation directory. Make sure that you install the Atoll Management Console in the same directory as Atoll. The Atoll Management Console follows the same version and build format as Atoll. Therefore, you should ensure that you install compatible versions of Atoll and the Atoll Management Console. 5. Select the Start menu folder for the Atoll Management Console. Figure 4.3: Atoll Management Console Setup - Start Menu Folder Selection 6. Click the Next button to install the Atoll Management Console. Figure 4.4: Atoll Management Console Setup - Finalising Installation Notes: 136 • You can also download the latest versions available on the Forsk’s Support website by logging on using the user name and password provided by Forsk. • You can click the Back button to go back and modify any of the options during the installation process. • You can click the Cancel button at any time during the installation to cancel the installation. • The Atoll User Manual and other documents can also be installed from the installation CD. These documents are also available for download on the Forsk’s support website. AT281_AM_E1 © Forsk 2009 Chapter 4: Atoll Management Console 4.2.3 Uninstalling the Atoll Management Console To uninstall the Atoll Management Console: 1. Close all programs. 2. Open the Control Panel. 3. Open Add or Remove Programs. 4. Select Atoll Management Console in the list of installed programs listed under the Install/Uninstall tab. 5. Click Remove. 6. Follow the instructions in the uninstall wizard. 4.3 Working With the Atoll Management Console This section explains the tools available in the Atoll Management Console and the procedures to follow. The Atoll Management Console consists of wizards that facilitate the procedure for each function proposing, a step-by-step approach. 4.3.1 Running the Atoll Management Console To launch the Atoll Management Console: 1. Select Start > Run from the Windows taskbar. 2. Type mmc in the Open field of the Run dialogue to run the Microsoft Management Console (mmc.exe). 3. Select Open from the Console menu. 4. Open the Atollmgmt.msc file from the Atoll installation folder. When the Atoll Management Console is run for the first time, there will be no database registered to manage. To register a new database: 1. Right click the Database item in the left pane under the Atoll Administration section to open its context menu. 2. Select Register a new server… to open the Data Link Properties dialogue. Figure 4.5: Database Context Menu 3. On the Provider tab, select the appropriate driver for your database, i.e., Oracle or SQL Server. Figure 4.6: Data Link Properties Dialogue - Provider Tab 4. On the Connection tab, enter the server name, and the user name and password to access the database server. You can check to see if the entered information is correct by clicking the Test Connection button. © Forsk 2009 AT281_AM_E1 137 Administrator Manual Oracle Databases SQL Server Figure 4.7: Data Link Properties Dialogue - Connection Tab 5. Click OK to connect to the selected database server. Once a database server is added in the Atoll Management Console, you have access to all the features offered by the console on the database server. 4.3.2 Atoll Management Console Environment The figure below depicts the working environment of the Atoll Management Console. The Tree in the left pane lists all the available database servers. The database server to which the current user is connected is marked with the icon and the disconnected database servers are represented with a icon. The other pane displays the list of all the databases available on the connected database server. The current user can be the owner of one of the listed databases. The user name of the owner of a database is mentioned with the database name in parentheses, i.e., [Administration Atoll \Database\Server_Name(User_Name)]. One Oracle user can create and own only one database. Details for the databases that have been upgraded, worked upon or created using the Atoll Management Console are available in the window. Databases which are up to date are represented with the ent version than that of currently installed Atoll are marked with the icon while those which have a differ- icon. Note: • A single user cannot own more than one database. You must create a new user in order to create a new master database or project database. Figure 4.8: Atoll Management Console Environment - Current Connected User and Associated Database 138 AT281_AM_E1 © Forsk 2009 Chapter 4: Atoll Management Console The displayed details of the databases which have been managed with the Atoll Management Console include the version and type of database, and the Atoll template used to create this database. Note: • A master database is one from which project databases can be created. To view the details of a master database or a project database: 1. Right-click the master database or the project database in the list. 2. Select Properties from the context menu. The Properties dialogue displays: • • • • • Name and description of the database, User name, Database type (Master or Project), Version, and Statistics on the database containing basic information such as the number of records in each table, etc. There is a second tab in the Properties dialogue for project databases. This tab displays: • • • The name of the master database, Connection parameters to the master database, and The sites filtering method used when creating this project database. The four main functions of the Atoll Management Console are accessible either through the context menu of the databases, or through the Actions menu in the menu bar. The following sections describe how the functions of the Atoll Management Console can be performed. 4.3.3 Working With Master Databases 4.3.3.1 Creating New Master Databases You can create new master databases in Oracle and SQL Server using the Atoll Management Console by providing the required information to the New Database wizard. You have to specify the type of network template (GSM GPRS EGPRS, UMTS HSPA, CDMA2000 1xRTT 1xEV-DO, etc.) on which the new master database is to be based, and follow the instructions in the New Database wizard. Atoll and the Atoll Management Console have the same versions. This means that the Atoll Management Console can create master databases based on the modules installed with the matching version of Atoll. Note: • You must have administrator rights to the database and to the server for creating master databases. To create a new master database: 1. Select the server in the server list in the left pane. 2. Select Action > New > Database. Figure 4.9: Creating a New Master Database The New Database Wizard dialogue will appear. Note: • © Forsk 2009 You can also create a new master database by selecting New > Database from the context menu of the server item in the left pane. AT281_AM_E1 139 Administrator Manual Figure 4.10: New Database Wizard 3. Follow the step-by-step procedure, providing the information required and clicking Next. The wizard will ask for the following information to create the master database: - The user who will be assigned owner rights to the master database. It can either be the current user or you can create a new user. The base Atoll template (GSM GPRS EGPRS, UMTS HSPA, etc.) to be used to create the master database. Name and description for the master database. The units and coordinate systems for the new master database. Figure 4.11: Steps to Creating a New Master Database Figure 4.12: Steps to Creating a New Master Database 4. The last window of the wizard lists the parameters you have selected. 5. Click Execute to create the master database. The newly created master database is stored on the server on which it was created. This master database contains additional fields in the table ATOLL_ADMIN. Furthermore, every table in the master database (except COODSYS and UNITS) contains an extra field called DB_RECORD_ID. The purpose of this field is to store the record ID for each record in the table. The information in this field cannot be modified. The ATOLL_ADMIN table contains the following fields: 140 Field Type Description NAME Text (50) The name of the master database as provided by the user DESCRIPTION Text (255) Description of the master database as provided by the user ATOLL_VERSION Text (10) The current version of Atoll AT281_AM_E1 © Forsk 2009 Chapter 4: Atoll Management Console ATOLL_BUILD Integer Current build of Atoll (added by Atoll Management Console) ATOLL_DBTYPE Text (10) Type of Atoll database (i.e., Master or Project) (added by Atoll Management Console) ATOLL_TEMPLATE Text (50) Base Atoll template used to create the master database (added by Atoll Management Console) DBSCHEMA Memo An image of the schema of the original database (added by Atoll Management Console) The ATOLL_ADMIN table is used to improve the performance of the upgrade feature. If a database has never been managed using the Atoll Management Console and this table contains only the first three fields, the Database Upgrade wizard has to search for all the data required for the upgrade in the entire database. This decreases the performance of the Database Upgrade wizard. Therefore, this table is used to store the required information so that the future upgrades are quicker. All the data required by the Database Upgrade wizard for the upgrade process is stored in this table. 4.3.3.2 Archiving Changes in Master Databases Modifications made in project databases while working on it in Atoll can be archived in the master database using the Atoll Management Console. You can archive any changes or modifications from a project database to the master database using the Archive dialogue. The Archive dialogue lets you select changes to archive at multiple levels. To archive the changes from a project database: 1. Select the project database to archive in the list of databases. 2. Select Actions > Archive to open the Archive dialogue. Note: • You can also archive the changes by selecting Archive from the context menu of the project database. Atoll Management Console compares the project database and the master database for differences and list all the differences found in the Archive dialogue. Figure 4.13: Archiving Changes in Master Databases a. Select a Site List from the Filter by Site List if you want to archive the changes made to sites of a specific site list only. If you select a site list, the Atoll Management console filters the modifications listed below to include only the modifications corresponding to sites in the selected site list. b. Click Archive All if you want to archive all the modifications. c. Select the check boxes to the left of the modified records that you want to archive and click Archive Sel. to archive only the changes those modifications. You can select the check boxes of more than one record simultaneously by selecting more than the records, and clicking the check box corresponding to any one of the selected records. d. You can also undo the last archive of all or selected changes. e. Select the Check conflicts check box to see whether there have been conflicts during the archive. A conflict occurs when a user or project database, having rights over the same item, has already archived a modification since your last refresh from the master database. In this case you will have a different value for a field stored in your project database, which you now want to modify, while the master database will have an already modified value. This feature helps avoiding conflicts of this sort that can arise in certain situations. © Forsk 2009 AT281_AM_E1 141 Administrator Manual f. The Errors table lists any errors that might occur during the archive process. It lists the table and the record on which the error occurs and the action that generated the error along with any error message that would have been generated. 3. Click Close to finish archiving. Note: • 4.3.4 During the archive, the Atoll Management Console verifies the state of the O_CHANGED fields in all the tables. If the O_CHANGED field is true for a record, the record will be listed in the records to be archived in the master database. Working With Project Databases You can use Atoll’s project database feature with Oracle. The following sections describe the features available for working with project databases. 4.3.4.1 Project Databases Project databases improve performance, facilitate usage, and ensure data security and reliability. Instead of all the users working directly with the master database, you can create one or many project databases from of your master database. A project database can either be a copy of the entire master database or a copy of a part of the master database corresponding to a given physical location or surface area. For example, you can have a country-wide master database either copied in a country-wide project database or many project databases corresponding to different regions of the country. The database administrator can manage the connection, i.e., upgrade, archive, refresh etc., between the project database(s) and the master database. The master database is not directly accessible to other users. A project database is an intermediary database created from a master database. A project database contains the master database that remains hidden from the end-users, and contains a copy of the master database that behaves as the currently accessed database. When a user modifies the value of a field in any table of the database, he modifies this value in the copy of that table stored in the project database. The value stored in the original table in the master database remains unchanged until the database administrator archives all the modifications from the project databases to the master database. Figure 4.14: Working With a Single Level Database 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 it is only the database administrator who can archive modifications from project databases to the master database. All the users have access to project databases, but only the administrator or advanced users can access and modify the master database directly. 142 AT281_AM_E1 © Forsk 2009 Chapter 4: Atoll Management Console Figure 4.15: Working With Project Databases If a country-wide network database is stored at a single location, and all the users of all the sub-regions have access to this master database at the same time: • • • • 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 as well. As the entire network is loaded every time a user accesses the database, and this too for each user working on any part of the network, performance is hampered greatly. A user working on only one city does not require knowledge of the entire country’s network for most of his tasks. All these drawbacks can be countered by using project databases. Local project databases can be created using different filters on sites thus allowing users to work on specific regions at a time. A possible scenario is depicted in the figure below: Figure 4.16: Multiple Project Databases From a Single Master Database 4.3.4.2 Creating Project Databases You can create project databases using the Atoll Management Console. Project databases facilitate the interaction of users within a database, and provide flexibility and security. A project database is a copy of the master database with which all the users of the master database can work simultaneously. A project database is an additional layer between the users © Forsk 2009 AT281_AM_E1 143 Administrator Manual and the master database, and provides added security for the master database. Project databases also help in avoiding conflicts between the modifications of different users working on the same database. To create a project database from a master databases: 1. Select the master database to from which you want to create a project database in the list of databases. 2. Select Actions > Create a Project Database to open the Project Database Creation Wizard dialogue. Figure 4.17: Project Database Creation Wizard Note: • You can also create a new project database by selecting Create a Project Database from the context menu of a master database. 3. Follow the step-by-step procedure, providing the information required and clicking Next. The wizard asks for the following information to create the project database: - Name of the server where the project database will be saved. The user who will be the owner of the project database. It can either be the current user or you can create a new user. Note: • - Certain versions of Oracle (and possibly other RDBMS) let you create a new user through this dialogue, but the new user is not assigned DBA rights, and is unable to create the associated project database. If such an error occurs in your case, it is recommended to create the new user beforehand in the database, assign him DBA rights, and then create the project database using the Atoll Management Console through the new user’s account. Name and description of the project database. The data that you want to be extracted from the master database into the project database. Here you have four possibilities: - Include all the sites in the master database. - Include all the sites in a sitelist (disabled if no sitelist exists). - Select the sites to include using an SQL condition. - Include the sites contained inside a polygon filter. Figure 4.18: Creating a New Project Database An SQL condition can be used to select sites that have a certain field in common (a Flag, for example). If a polygon filter is used, the user is asked the location of the vector file that contains the polygon. The project database will have PROJECT mentioned in the details of the Atoll Management Console window. A project database contains a table named ATOLL_ADMIN_PRJ in addition to the table ATOLL_ADMIN. This table contains the following information about the project database: 144 AT281_AM_E1 © Forsk 2009 Chapter 4: Atoll Management Console Field Type Description NAME Text (50) The name of the project database provided by the user MASTER_CONNECTION Text (255) Connection parameters to the master database MASTER_DBSCHEMA Text (50) The name of the original schema of the master database SEL_METHOD Short Data extraction method that was used to select the sites to include in the project. SEL_PARAM Text (255) Parameters, if any, for the selection method SEL_PGON Memo The filter polygon, if used, of the selection method This information can also be seen in the Project tab of the properties dialogue of the project database by right-clicking the project database and selecting Properties. If the data extraction method used requires a parameter, such as an SQL condition, the condition is stored in the SEL_PARAM field. To prevent the Atoll Management Console from searching the filter polygon each time, the polygon is stored in the SEL_PGON field, if used. Apart from these tables, a project database contains a copy of all the original tables of the master database. The nomenclature adapted for this storage is O_TABLENAME. For example, the ANTENNAS table of the master database is stored in the project database under the name O_ANTENNAS. UNITS and COORDSYS tables are not stored in this manner. They are not stored since they are not modified. Furthermore, each table in the project database has two additional fields; O_RECORD_ID and O_CHANGED. These two fields are used to verify whether any record has been modified with respect to the original values in the master database. The O_CHANGED field shows whether the record has been changed or not. The O_RECORD_ID field never changes. It is used to locate the position of the record in the master database. In case the record has been modified, it can be archived in its correct location in master database using the O_RECORD_ID and DB_RECORD_ID fields. Field Type Description O_RECORD_ID Integer Contains the value of the corresponding DB_RECORD_ID field in the master database O_CHANGED Boolean Flag to show whether the record has been modified or not Note: • 4.3.4.3 The creation of project databases require that the user have enough rights to be able to create new tables in the master database schema. Refreshing Project Databases You can refresh the contents of project databases using the Atoll Management Console. Refreshing the contents of a project database with the contents from the master database will discard changes made to the project database and reset all the tables with data from the master database. To refresh a project database: 1. Select the project database to refresh in the list of databases. 2. Select Actions > Refresh to refresh the project database. Atoll Management Console asks whether you want to: - Refresh unmodified data only This option keeps your current modifications to the project database and updates the project database with other data from the master database. - Refresh all and cancel any modifications This option erases all the current modifications that you made in the project database and replaces all the data with values from the master database. Figure 4.19: Refreshing Project Databases Note: • © Forsk 2009 You can also refresh a project database by selecting Refresh from the context menu of a project database. AT281_AM_E1 145 Administrator Manual During the refresh process, the Atoll Management Console verifies the state of the O_CHANGED fields in all the tables. If the O_CHANGED field is true for a record, the record will be refreshed from the master database. 4.3.5 Upgrading Databases Every major version of Atoll brings some changes in the structure of Atoll databases. Therefore, it is necessary for the correct functioning of Atoll that the databases be up to date and compatible with the new version. Problems may arise if the older database structures are not upgraded to the new one. You can upgrade Oracle and SQL Server databases using the Atoll Management Console. Important: • If you are upgrading a database which was neither created nor already upgraded (at least once) using the Atoll Management Console, see "Upgrading Databases for the First Time" on page 147 first. To upgrade a database (master or project database) using the Atoll Management Console: 1. Select the database to upgrade in the list of databases. 2. Select Actions > Upgrade Database to open the Database Upgrade Wizard dialogue. The Database Upgrade wizard displays the current database version and the version to which the database will be upgraded. Figure 4.20: Database Upgrade Wizard Note: • You can also upgrade a database by selecting Upgrade Database from the context menu of a database. 3. Follow the step-by-step procedure, providing the information required and clicking Next. The wizard will ask for a name and description for upgrading the database. The Database Upgrade wizard studies the database to upgrade in order to determine the original Atoll template (GSM GPRS EGPRS, UMTS HSPA, etc.) on which this database was based. If there is more than one template available for the same type of network, the wizard asks the user to choose the most appropriate one for the upgrade. Once the base template is selected, the wizard applies the modifications to the database according to the base template. Important: • If you use the Atoll Management Console’s Changes History Management tool, you must repair the upgraded database in order to continue using this tool. For more information, see "Managing the History of Data Modifications" on page 154. Fields are added to the ATOLL_ADMIN table when the database is upgraded for the first time using the Atoll Management Console. This table contains the following fields: 146 Field Type Description NAME Text (50) The name of the database as provided by the user DESCRIPTION Text (255) Description of the database as provided by the user ATOLL_VERSION Text (10) The current version of Atoll ATOLL_BUILD Integer Current build of Atoll (added by Atoll Management Console) ATOLL_DBTYPE Text (10) Type of Atoll database (i.e., Master or Project) (added by Atoll Management Console) ATOLL_TEMPLATE Text (50) Base Atoll template used to create the database (added by Atoll Management Console) AT281_AM_E1 © Forsk 2009 Chapter 4: Atoll Management Console DBSCHEMA Memo An image of the schema of the original database (added by Atoll Management Console) The ATOLL_ADMIN table is used to improve the performance of the upgrade feature. If a database has never been managed using the Atoll Management Console and this table contains only the first three fields, the Database Upgrade wizard has to search for all the data required for the upgrade in the entire database. This decreases the performance of the Database Upgrade wizard. Therefore, this table is used to store the required information so that the future upgrades are quicker. All the data required by the wizard for the upgrade process is stored in this table. The Atoll Management Console also adds a DB_RECORD_ID field in all the tables of the database (except COODSYS and UNITS). The purpose of this field is to store the record ID for each record in the table. The information in this field cannot be modified. If some of the tables in a database have been replaced by views, the Database Upgrade wizard analyses the definitions of these views when performing the upgrade. 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 accordingly. The upgraded definition will take the newly added fields into account. Note: • DB_RECORD_ID field is not added to Microsoft Access databases. • 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 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 will first have to upgrade the database to the same version as the current version of the database. To upgrade the database: 1. Before installing the new version of Atoll, install the Atoll Management Console (if not already installed) compatible with the version of Atoll currently in use. 2. Access and upgrade the database (as described in "Upgrading Databases" on page 146) using the Atoll Management Console to the version of Atoll currently in use. The Atoll Management Console adds additional fields to the ATOLL_ADMIN table and DB_RECORD_ID fields in all the tables, as described in "Upgrading Databases" on page 146. Once the Atoll Management Console has performed the necessary modifications, you can now upgrade the database to the new version. 3. Install the new version of Atoll and the Atoll Management Console. 4. Access and upgrade the database (as described in "Upgrading Databases" on page 146), using the new version of the Atoll Management Console, to the new version of Atoll. A database that has never been processed by the Atoll Management Console must be first upgraded to the current version, using the current version of the Atoll Management Console. This is necessary so that the Atoll Management console can add the required information to the database, and be able to upgrade it later on to newer versions. It is necessary to upgrade such a database (that has never been processed by the Atoll Management Console) to the current version before installing the new version of Atoll and the Atoll Management Console. This is because once you install the new version of the Atoll Management Console, the Windows registery key that stores the information about the .dll file of the Atoll Management Console is overwritten, and you cannot use the previous version of the Atoll Management Console unless you manually register the older .dll again (regsvr32 filename.dll). If you have already installed the new version of the Atoll Management Console, you will have to register the older .dll again, upgrade the database to the older version using the older Atoll Management Console, register the new .dll, and upgrade the database to the new version using the new Atoll Management Console. 4.3.6 Managing Administration File Paths Atoll Management Console enables you to specify the locations of administration (.cfg and .ini) and project template files (.mdb) which can be accessed by a number of users and user groups. This feature is useful for network planning teams working simultaneously on different parts of a large network. You can specify paths to the following Atoll administration files and network templates for different user groups: • • • © Forsk 2009 .cfg files .ini files (Atoll.ini, MeasImport.ini, and NumMeasImport.ini) .mdb files AT281_AM_E1 147 Administrator Manual Atoll sessions launched by a user of a certain user group will automatically load the .cfg and the .ini files specified for that user group. Therefore, the user’s Atoll sessions will load the geographical region on which the user is working, and the parameters set in the initialisation file. You can also define the paths to network project templates relevant to each user group. For example, for a group of users working on a network-specific variant of a GSM GPRS EGPRS project, containing modifications specific to their network, it is not necessary for each user to keep an upgraded copy of the project template, and for each modification to be carried out by all the users on their templates separately. It is possible to keep a single project template that is shared and accessed by all the users in the group. Modifications can be carried out by the administrator so that all the users who access this project template always work on an up-to-date version. This can also avoid inconsistencies that may occur when a number of users of a user group modify their respective project templates separately. The Atoll Management Console uses the Group Policy feature of Microsoft Windows and extends it to implement the file path management feature. To gain access to this feature: 1. Select Console > Add/Remove Snap-in… to open the Add/Remove Snap-in dialogue. Figure 4.21: Add/Remove Snap-in 2. Select the Atoll administration item in dialogue. 3. Click the Add button to open the Add Standalone Snap-in dialogue. Figure 4.22: Adding Standalone Snap-in - Step 1 4. Select Group Policy snap-in and click the Add button. 148 AT281_AM_E1 © Forsk 2009 Chapter 4: Atoll Management Console Figure 4.23: Adding Standalone Snap-in - Step 2 5. Click Browse in the Select Group Policy Object dialogue. 6. Select your group policy object from the Browse window. Figure 4.24: Selecting Group Policy Object Figure 4.25: Group Policies 7. Once the Group Policy snap-in is added to the console, right-click the Administrative Templates folder in the User Configuration item of the Group Policy tree. 8. Select the Add/Remove Templates… command from the context menu. 9. Click the Add button in the Add/Remove Templates dialogue. 10. Browse for the ‘AtollGroupPolicies.adm’ template file and add it. This will add a subfolder named Atoll in the Administrative Templates folder of the Group Policy tree. © Forsk 2009 AT281_AM_E1 149 Administrator Manual Figure 4.26: Administrative Templates Now the administrator has access to the feature of defining file paths for user groups. Note: • You can save the changes in the Atoll Management Console so that you do not have to go through this process every time you run the Atoll Management Console. To define paths to administration and template files for user groups: 1. Click the Atoll subfolder in the Administrative Templates folder of the Group Policy tree. 2. Double-click the Admin paths policy to open its properties dialogue. 3. Select Enabled and define the paths to the .cfg, .ini, and .mdb files to be shared by a user group. 4. Click OK. Note: • In addition to the Atoll.ini file, the .ini files directory also refers to the MeasImport.ini file which serves as the configuration file for importing CW measurements. Figure 4.27: Defining File Paths for User Groups - Step 1 150 AT281_AM_E1 © Forsk 2009 Chapter 4: Atoll Management Console Figure 4.28: Defining File Paths for User Groups - Step 2 Once a Group Policy has been defined containing the specific Atoll administrative template, it has to be assigned by the administrator to a user group using the Microsoft Windows Administrative Tools. 4.3.7 Managing User Accounts and Access Rights Atoll Management Console enables you to create and delete database user accounts, edit user account information, and define user access rights to different components of a project such as database tables, and radio data and parameters in Atoll. The following sections describe how user acounts and access rights are managed using the Atoll Management Console. In order to be able to manage user accounts and access rights using the Atoll Management Console, you first have to make your database compatible with the User Management tool. This is done automatically when the User Management tool is run on a database for the first time. The database has to be of the same version as the Atoll Management Console being used to manage user accounts and access rights. To make your database compatible with the User Management tool: 1. In the Atoll Management Console window, select the database whose user accounts you want to manage. 2. Select Actions > Manage Users to open the User Management dialogue. 3. Click Yes when the Atoll Management Console asks you whether you want to make your database compatible with the User Management tool. The Atoll Management Console adds a GUIUsersRights table in the database with the following structure: Field Type Description ATOLL_USER Text (50) Name of the user account RIGHTS Memo Semi-colon separated set of interface access rights Each user’s interface access rights are stored in a unique record in the GUIUsersRights table. The contents of the RIGHTS field have the following syntax: RADIOPARAMS=X;CALCPARAMS=Y;PROPAGMODELS=Z The syntax is explained in detail in "Defining Database and Interface Access Rights" on page 152. If interface access rights are not defined for a database, i.e., the GUIUserRights table does not exist, all the users have no interface access limitations. If interface access rights are defined for a database, and a user creates a document from the database or opens a document connected to the database, Atoll retrieves the interface access rights for the user when he enters his user name and password to access the database. If the database is not reachable, the user is not listed in the GUIUserRights table, or if the password is not correct, the user’s interface access rights are set to read-only by default (see "Defining Database and Interface Access Rights" on page 152 for more details). 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 any interface access restrictions by disconnecting the document from the database. However, a disconnected document cannot be connected to the database again. 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. Note: • © Forsk 2009 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. AT281_AM_E1 151 Administrator Manual 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. 4.3.7.1 Defining Database and Interface Access Rights For any existing user account, you can set the database and Atoll interface access rights using the Atoll Management Console. To manage database and Atoll interface access rights for an existing user account: 1. In the Atoll Management Console window, select the database whose user accounts you want to manage. 2. Select Actions > Manage Users to open the User Management dialogue (see Figure 4.29: on page 152). Figure 4.29: User Account and Access Rights Management Dialogue 3. Under Atoll Projects, you can 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. Under List of Users, 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 153. ). If you want to see only the user accounts who currently have database access rights in the selected database, select the Hide users without rights in this project check box. Only the user accounts that have database access rights in the selected database ( ) are displayed in the List of Users. 5. Under Database Rights, you can select a database access Rights Category: - - - No Access: The user has neither read nor write access to the database. The database is not visible to the user and he is not allowed to create an Atoll document based on this database. Read Only: The user is allowed to create Atoll documents from the database. However, the user does not have write permissions to any table of the database, i.e., he cannot archive the modifications he makes in the Atoll document to the database. Standard: The user has read and write access to some tables of the database. These tables include radio network data tables including sites, transmitters, cells, subcells, repeaters, remote antennas, secondary antennas, intra- and inter-technology neighbours and exceptional pairs, site and transmitter lists, microwave point-to-point, point-to-multipoint, and multi-hop links, microwave repeaters, microwave hubs. Administrator: The user has 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: - 152 Access to Radio Data: RADIOPARAMS=X - Full: (X = ALL) The user has read and write access to all the data tables and the related properties dialogues. - Standard: (X = STD) The user has 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 pointto-point, point-to-multipoint, and multi-hop links, microwave repeaters, microwave hubs. AT281_AM_E1 © Forsk 2009 Chapter 4: Atoll Management Console - Read Only: (X = NONE) The user has read-only access to radio network data tables and related properties dialogues, i.e., the user is not allowed to modify radio network data and parameters. Note: • - - Database and Atoll radio data are independent. For example, a user may have full access rights in the interface but not allowed to archive his 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 Prediction Parameters: CALCPARAMS=Y - Full: (Y = ALL) The user has read and write access to all the coverage predictions and their parameters. - Templates Only: (Y = NONE) The user has access to customized coverage prediction studies list only. The user is not allowed to modify coverage conditions and display settings. Access to Propagation Models: PROPAGMODELS=Z - Full: (Z = ALL) The user has read and write access to all propagation models and their properties. - Limited: (Z = NONE) The user has read-only access to the properties of all the propagation models in the Propagation Models folder. 7. Click OK or Apply to store the database and interface access rights for the selected user. 4.3.7.2 Creating and Editing User Accounts You can create user accounts and edit existing user account information using the Atoll Management Console. To manage user accounts: 1. In the Atoll Management Console window, select the database whose user accounts you want to manage. 2. Select Actions > Manage Users to open the User Management dialogue (see Figure 4.29: on page 152). 3. To create a new user account: a. Under Users, click Create. The Create/Edit User dialogue appears (Figure 4.30: on page 153). b. Under Identification, enter a user name and password for the new user account. If you want to use the same password as the one used for authentication by the operating system, select Use Operating System Authentication under Advanced. c. 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 4.30: on page 153). c. Under Identification, modify the user’s password. If you want to use the same password as the one used for authentication by the operating system, select Use Operating System Authentication under Advanced. d. Click OK. The password for the user account is updated. 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 4.30: on page 153). c. Under Advanced, select Account Locked check box. d. Click OK. The user account is deactivated and is no longer in use. 6. To delete a user account: a. Under List of Users, select the user account you want to delete. b. Under Users, click Delete. The user account is deleted. Figure 4.30: Creating or Editing a User Account © Forsk 2009 AT281_AM_E1 153 Administrator Manual 4.3.8 Managing the History of Data Modifications The Atoll Management Console allows you to keep and manage a history of all the modifications made in the network data tables by different users. The history management tool keeps track of all the modifications made in the following Atoll tables: Technology Tracked Tables GSM GPRS EGPRS Sites, Transmitters, TRGs, TRXs, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt UMTS HSPA Sites, Transmitters, CDMACells, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt CDMA2000 1xRTT 1xEV-DO Sites, Transmitters, CDMACells, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt TD-SCDMA Sites, Transmitters, CDMACells, Repeaters, SecondaryAntennas, Neighbours, NeighboursExt WiMAX 802.16d Sites, Transmitters, WCells, SecondaryAntennas WiMAX 802.16e Sites, Transmitters, WCells, SecondaryAntennas, Neighbours, NeighboursExt LTE Sites, Transmitters, T4GCells, SecondaryAntennas, Neighbours, NeighboursExt Microwave Radio Links Sites, MWLinks, MWHubs, MWPMP, MWMultiHops, MWMultiHopsLinks, MWRepeaters You can, however, disable the history management for any table (see "Enabling and Disabling History Management for Tables" on page 155 for more information). If you wish, you can also purge old history information (see "Purging Old History Information" on page 155 for more information). The history management tool is available for all the technologies supported by Atoll, and for Oracle databases. The following section describes how to set up the history management tool for an Oracle database via the Atoll Management Console. 4.3.8.1 Setting Up the History Management When you set up the history management tool for any database, the Atoll Management Console adds new tables to the database structure. For each tracked table, it adds a corresponding history table that has the same name as the tracked table with a suffix "_H". Each history table has the same structure as the corresponding tracked table, but with the following four additional fields. These fields enable the Atoll Management Console to store all the modifications made by users to each tracked table: Field Type Description HISTORY_ID Integer A unique ID of the modification history record MODIFIED_BY Text (50) The user who made the modification MODIFIED_DATE Date The date when the modification was made HISTORY_STATUS Text (10) Status of the modification history record The above fields are also added to all the tracked tables in order to store information about the most recent modification. For example, simply looking at a record in a tracked table will provide you the information about the user who last modified the record, when it was modified, and what was the modification type. To set up the history management tool for a database: 1. In the Atoll Management Console window, select the database for which you want to manage the changes history. 2. Select Actions > Manage Changes History to open the Changes History Management dialogue. 3. Click Yes when the Atoll Management Console asks you whether you want to make your database compatible with the history management tool. The Atoll Management Console updates the database structure to make it compatible with the history management tool. Once finished, it opens the Changes History Management dialogue (Figure 4.31: on page 155). This dialogue lists all the tables for which the history management has been enabled, the total numbers of records in these tables, and the status of the history management. The history management is now enabled for this database. All the modifications made by users in the tables listed in "Managing the History of Data Modifications" on page 154 will now be stored in the history tables added in the database by the tool. If you wish, you can disable the history management for any table. For more information, see "Enabling and Disabling History Management for Tables" on page 155. 154 AT281_AM_E1 © Forsk 2009 Chapter 4: Atoll Management Console Figure 4.31: Changes History Management Dialogue 4.3.8.2 Enabling and Disabling History Management for Tables You can enable or disable history management for each individual table. To enable history management for a table: 1. In the Atoll Management Console window, select the database for which you want to manage the changes history. 2. Select Actions > Manage Changes History to open the Changes History Management dialogue. 3. In the Changes History Management dialogue, right-click the table for which you want to enable history management. The context menu appears. 4. Select Enable in the context menu. History management is now enabled for this table. The Status in the Changes History Management dialogue is set to OK for this table. To disable history management for a table: 1. In the Atoll Management Console window, select the database for which you want to manage the changes history. 2. Select Actions > Manage Changes History to open the Changes History Management dialogue. 3. In the Changes History Management dialogue, right-click the table for which you want to disable history management. The context menu appears. 4. Select Disable in the context menu. History management is now disabled for this table. The Status in the Changes History Management dialogue is set to Deactivated for this table. 4.3.8.3 Repairing After a Database Structure Modification or Upgrade When you modify the structure of a tracked database table (for which changes history is recorded), either automatically upgrading your database using the Atoll Management Console, or manually by adding or removing a field, or by modifiying a field type, the corresponding history management table becomes invalid and has to be upgraded as well to match the new structure of the tracked table. The Status column of the Changes History Management dialogue shows an error for the tracked table whose history management table does not match its structure. To repair a history management table: 1. In the Atoll Management Console window, select the database for which you want to manage the changes history. 2. Select Actions > Manage Changes History to open the Changes History Management dialogue. 3. In the Changes History Management dialogue, right-click the table whose Status shows an error and whose history management table you wish to repair. The context menu appears. 4. Select Install/Repair in the context menu. The Atoll Management Console repairs the data structure of the history management table to match the structure of the corresponding tracked table. 4.3.8.4 Purging Old History Information All the modifications made by all the users are stored in the history management tables. Therefore, these tables may quickly become very large and may require a lot of disk space. You can, if you wish, purge old history information (records) from these tables in order to gain space. To purge old history records from a history management table: 1. In the Atoll Management Console window, select the database for which you want to manage the changes history. 2. Select Actions > Manage Changes History to open the Changes History Management dialogue. © Forsk 2009 AT281_AM_E1 155 Administrator Manual 3. In the Changes History Management dialogue, right-click the table whose old history records you wish to purge. The context menu appears. 4. Select Purge in the context menu. The Record Purge dialogue appears (Figure 4.32: on page 156). Figure 4.32: Record Purge Dialogue 5. Under Purge changes history recorded before, move the slider to select the date from which onwards you want to keep the history records. All the changes history records before this date will be deleted. 6. Under Number of records, the number of records that will be left after the purge are available. 7. Under Data size, the size of the records that will be left after the purge is available. 8. Under Options, select the Keep creation and deleteion records check box if you want to purge the history records except the records of creation and deletion. 9. 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, all the creation and deletion records before the selected date are not purged. 156 AT281_AM_E1 © Forsk 2009 Chapter 5 Radio Data Import Atoll RF Planning & Optimisation Software Administrator Manual 158 AT281_AM_E1 © Forsk 2009 Chapter 5: Radio Data Import 5 Radio Data Import 5.1 Migration From Planet 2.8 Databases Atoll can import the following data from a Planet 2.8 database: • • • • • • Geographic data (DTM, clutter, vectors, and images) Network data (radio antennas, microwave antennas, sites and transmitters, carriers) Neighbours Propagation models (and path loss matrices) Text data files CW measurements Atoll imports the Planet database even if problems or inconsistencies are encountered in the files being imported. Atoll imports all the objects, except those with incorrect description or syntax, and those which depend on other objects that do not exist in the database being imported or in the Atoll document. For example, a station located on a site which does not exist in the database or in the Atoll document will not be imported. Errors and warnings related to the problems encountered during the import are listed in the Event viewer window. Notes: • The import feature is available in all types of Atoll documents. • The various Planet data file formats are detailed in the Technical Reference Guide. • Existing records in an Atoll document, which you might have imported earlier, are erased and replaced by new records every time you import the same entity. For example, if you have already imported a list of 10 antennas from a Planet database, and are now importing a list of 5, the new import process will erase all the existing 10 antennas from the Atoll document and replace them with the newly imported 5 antennas. Important: • If you import a Planet database and encounter problems, it is strongly advised to correct those problems in your Planet database and try the next import in to a fresh Atoll document. Continuously deleting the problematic records in the same .atl file and reimporting from the Planet database after correction may cause problems and database inconsistency issues. 5.1.1 Prerequisites for Data Import From Planet 5.1.1.1 Geographic and Text Data Following are some important points to keep in mind while importing geographic data from Planet: • • • 5.1.1.2 You should take care in checking or modifying the projection coordinate system related to the geographic data being imported. If you are importing an index file, Atoll considers it to be a Planet data file (index) by default. You do not need to explicitly select this option in the Files of type list. Atoll considers all the files whose names start with the character string "index" or "INDEX" as Planet index files. For example: index, Index2, INDEX.new, etc. Radio Antennas Standard fields that are defined in Atoll data structure are directly imported. Other Planet fields are imported and considered as information-only fields. These fields are available in the Other Properties tab of the Properties dialogue of the imported data. In all RDBMS other than Microsoft Access, you must create the following fields in the database before importing. For the antenna import, the fields to be created are: • • • • • FREQUENCY H_WIDTH V_WIDTH FRONT_TO_BACK TILT The design frequency of the antenna The azimuth beamwidth The elevation beamwidth The ratio of forward antenna gain at 0 and 180 degree elevation Indicates whether the antenna is to be electrically or mechanically tilted Other fields available in the Planet antenna files that you wish to import in Atoll can also be created in the database before importing. Atoll imports all the custom fields as long as the field data in the antenna file matches the field type in the database. Notes: • © Forsk 2009 Values from the H_WIDTH field are automatically copied to the Beamwidth field of the Antennas table. You can display transmitter symbols on the map according to the values in this field. AT281_AM_E1 159 Administrator Manual • If the Planet antenna files contain electrical downtilts, these values are automatically copied to the Additional Electrical Downtilt field of the Antennas table. • If the Planet antenna files do not specify any unit of antenna gain, or provide the gain in dB, Atoll will ask you to specify a gain unit (dBi or dBd) to be applied on all the antennas being imported which have no gain unit specified. The antennas whose gain units are defined in their respective Planet format files will be imported with the defined unit. • The index file is a text file listing a Planet format antenna file per row. 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." 5.1.1.3 Microwave Antennas 5.1.1.3.1 Description of Planet Microwave Antennas Planet Microwave Tool generates ASCII files that contain the description of microwave antennas. There are separate files for each antenna radiation pattern and an index file that contains the names of these antenna files. The syntax is the same for radio and microwave antennas, although the two antenna types do not have the same definition. A microwave antenna is defined by 4 radiation patterns divided between the 2 antenna files: • • 5.1.1.3.2 Antenna: Parallel pattern VV (or HH) is the response of a vertically (or horizontally) polarised port to a vertically (or horizontally) polarised signal. The Antenna pattern defines parallel polarisation (HH and VV). Antenna_CROSS: Cross pattern VH (or HV) is the response of a vertically (or horizontally) polarised port to a horizontally (or vertically) polarised signal. The Antenna_CROSS pattern defines cross polarisation (HV and VH). Description of Atoll Microwave Antennas Atoll’s microwave antennas table (MWAntennas) is linked to the frequency bands (MWBands) and the manufacturers (MWManufacturers) tables. A microwave antenna is described by 8 radiation patterns: Horizontal polarization - Horizontal plane: 1. Co-polar section: Horizontal polarised port response to a horizontally polarised signal in the horizontal plane. 2. Cross-polar section: Horizontal polarised port response to a vertically polarised signal in the horizontal plane. Horizontal polarization - Vertical plane: 3. Co-polar section: Horizontal polarised port response to a horizontally polarised signal in the vertical plane. 4. Cross-polar section: Horizontal polarised port response to a vertically polarised signal in the vertical plane. Vertical polarization - Horizontal plane: 5. Co-polar section: Vertical polarised port response to a vertically polarised signal in the horizontal plane. 6. Cross-polar section: Vertical polarised port response to a horizontally polarised signal in the horizontal plane. Vertical polarization - Vertical plane: 7. Co-polar section: Vertical polarised port response to a vertically polarised signal in the vertical plane. 8. Cross-polar section: Vertical polarised port response to a horizontally polarised signal in the vertical plane. 5.1.1.3.3 Conversion From Planet to Atoll When Planet microwave antennas are being imported, Atoll looks for existing records in the frequency bands table and in the manufacturers table which correspond to the antennas being imported. If no such records exist, new frequency bands records have to be created. The FREQUENCY field in Planet files indicates the design frequency of the antenna in MHz, and the MAKE field indicates the name of the antenna manufacturer. If no frequency band in Atoll includes the design frequency of the antenna being imported, then Atoll creates a new band with Fmin = FREQUENCY - 1 GHz and Fmax = FREQUENCY + 1 GHz. The name of this new frequency band is set to *Fmin-Fmax*. If the manufacturer does not exist in the manufacturers table, Atoll will create a new manufacturer with Name = MAKE. The 4 patterns in Planet format are converted to the eight patterns used by Atoll. Planet patterns are given for horizontal planes. Pattern 1 160 Planet File Pattern Antenna Parallel pattern HH AT281_AM_E1 Atoll HH in horizontal plane © Forsk 2009 Chapter 5: Radio Data Import 2 5.1.1.4 Antenna_CROSS Cross pattern HV HV in horizontal plane 3 Antenna Parallel pattern VV truncated to 5° HH in vertical plane 4 Antenna_CROSS Cross pattern VH truncated to 5° HV in vertical plane 5 Antenna Parallel pattern VV VV in horizontal plane 6 Antenna_CROSS Cross pattern VH VH in horizontal plane 7 Antenna Parallel pattern HH truncated to 5° VV in vertical plane 8 Antenna_CROSS Cross pattern HV truncated to 5° VH in vertical plane Sites and Transmitters Network data (only sites, or sites and transmitters) can be imported to Atoll from Planet 2.8. You have to select an ASCII sites database file and a Flag type file (optional) for the import. Planet sites databases contain 5 flags. If you have selected a Flag type file, Atoll will import flag names instead of flag values. Make sure that the database being imported and the data in the Flag type file are consistent. Standard fields defined in the Atoll data structure are directly imported. Other Planet fields are imported and considered as information-only fields. These fields are available in the Other Properties tab of the Properties dialogue of the imported data. In all RDBMS other than Microsoft Access, you will have to create the following fields in the database before importing. For the sites, the information fields to be created are: • • FLAG_1 to FLAG5 LAYER Site status flags (numbers, or names if a Flag types file exists) MACRO for macrocell, MICRO for microcell, or empty Important: 5.1.1.5 • Transmitters whose main antennas do not already exist in the Atoll document will not be imported. Before importing network data, make sure that all the antenna types referenced by transmitters already exist in the current project. If not, you must first import the appropriate antennas database. • Planet uses the EIRP property for transmitters. This field is not available in Atoll 3G projects. Therefore, a pilot power has to be defined. Atoll calculates the pilot power from the EIRP available in the Planet database during import. Pilot Power = EIRP – Transmitter Antenna Gain + Transmission Losses Carriers Carrier data from Planet 2.8 can be imported in GSM GPRS EGPRS projects. Standard fields defined in Atoll data structure are directly imported. Other Planet fields are imported and considered as information-only fields. These fields are available in the Other Properties tab of the Properties dialogue of the imported data. In all RDBMS other than Microsoft Access, you must create the following fields in database before importing. For the carrier import, the fields to be created are: • • • • • LAC CELLID MOB_COUNTRY_CODE BSC MSC Location Area Code Alphanumeric Cell Identity Mobile Country Code Base Station Controller Mobile Services Switching Centre Before importing carriers, make sure that the transmitters already exist in the Atoll document, or import them if required. 5.1.1.6 Neighbours Importing neighbours database requires that the transmitters database in the Atoll document contain consistent values. This database could have been imported from a Planet database. You can import neighbours to GSM GPRS EGPRS, UMTS HSPA, and CDMA2000 1xRTT 1xEV-DO projects. 5.1.1.7 Propagation Models Atoll can automatically import propagation models, K1 to K6 parameter values for SPM, calculation methods, and clutter management parameters from Planet. Therefore, you do not have to perform any conversion for propagation models manually. It is important to keep in mind that Planet works in terms of gains while Atoll in terms of losses. Planet considers losses as negative values. Therefore, clutter management parameters, and K1 through K6, except K4, parameter values for SPM in Atoll are opposite to those in Planet. K4 (diffraction parameter) is considered a loss. For example: • • © Forsk 2009 A clutter class having a -10 dB gain in a Planet project will be assigned a 10 dB loss (positive value) in an Atoll document. A clutter class that introduces an increase of signal, e.g., 5 dB, in a Planet project, will be considered to have a negative loss (-5 dB) in Atoll. AT281_AM_E1 161 Administrator Manual 5.1.1.8 Path Loss Matrices Path loss matrices imported in to Atoll from Planet (.sig files) are listed in the Result Storage window, available from the Prediction folders context menu. The imported path loss matrices are locked, and any new coverage prediction study performed in Atoll will be based on the imported results, without recalculating path loss matrices. During the path loss matrices import, Atoll uses the signal level and EIRP available in each binary .sig file to calculate the path loss (EIRP-signal level). This path loss can then be used by Atoll as any other path loss result. Note: • 5.1.1.9 If you change some parameters, such as the grid resolution, Atoll will display a warning informing you that the path loss calculations will be unlocked. Atoll will then recalculate the path loss matrices using the default model to perform coverage prediction studies. CW Measurements Following are some important points to keep in mind while importing CW measurement data from Planet: • • 5.1.2 Importing Planet CW measurements to an Atoll UMTS HSPA project requires that the reference transmitter be already available in the project, i.e., site, antenna, transmitter, and cell. You should also ensure the consistency between the cell pilot power in the Atoll UMTS HSPA project and the EIRP value defined in the Planet project: Cell Pilot Power = EIRP – Transmitter Antenna Gain + Transmission Losses Importing Data From a Planet Database Importing data from Planet databases consists in importing index files in the following manner: 1. Select File > Import to open the file import dialogue. 2. Choose Planet® database in the Files of type list. This will open the Planet database import dialogue. Figure 5.1: Planet Database Import Dialogue 3. Click the check boxes for the data to be imported and define the path to the associated index file(s). You can also click the button, and look for the index files by browsing. 4. Click OK to import the data once you have identified all the index files related to all the types of data to be imported from the Planet database. 162 AT281_AM_E1 © Forsk 2009 Chapter 5: Radio Data Import Notes: 5.1.2.1 • You can also import Planet data files by selecting Planet® data files (index) in the Files of type list. Once you open the index file from the Open dialogue, Atoll will ask you to choose the type of data this file contains, and whether you want Atoll to embed this imported data in your .atl file or not. • If the currently open .atl file (Atoll document) does not have access to the microwave links module, i.e., it does not include the tables relating to the microwave links module, the Microwave Antennas option in the above dialogue will be disabled. • You can also import Planet antenna files directly through the context menu of the Antennas folder. Importing CW Measurements From a Planet Database The import method described in "Importing Data From a Planet Database" on page 162 is applicable to all types of Planet data except CW measurements. To import CW measurements from a Planet file to Atoll: 1. Right-click the CW Measurements folder in the Data tab of the Explorer window to open its context menu. 2. Select Import from the context menu to Open the CW Measurements import dialogue. 3. Choose Survey Files Planet (*.hd) in the Files of type list. 4. Browse for the file to import and click Open. The CW measurements are directly imported to the Atoll document, and data values are copied to their corresponding Atoll internal fields. 5. Click OK to finish the import. Note: • 5.1.2.2 You can also import CW Measurements from Planet files by dragging the file to the Atoll window and dropping it on the appropriate Atoll document. Importing Microwave Antennas From a Planet Database You can also import microwave antennas in the form of Planet files through the Import command of the Links folder context menu. This is an additional user interface option, which performs exactly the same import as the import procedure described in "Importing Data From a Planet Database" on page 162. To import microwave antennas from a Planet file into Atoll: 1. Expand the Microwave Radio Links folder in the Data tab of the Explorer window. 2. Right-click the Links folder to open its context menu. 3. Select Import from the Antennas menu to open the Microwave Antenna Import dialogue. 4. Select whether you want to import a single file or an entire folder, and click the - button. If you are importing a single file, choose Planet® files (index) in the Files of type list. Browse for the file to import and click Open. If you are importing an entire folder, choose the folder in the open dialogue and click OK. 5. Click Import in the Microwave Antenna Import dialogue to import the file or folder. The microwave antennas are directly imported to the Atoll document, and the required conversion between the Planet and Atoll formats is automatically carried out. Data values are copied to their corresponding Atoll internal fields. Note: • © Forsk 2009 You can also import microwave antennas from Planet files by dragging the file to the Atoll window and dropping it on the appropriate Atoll document. AT281_AM_E1 163 Administrator Manual 164 AT281_AM_E1 © Forsk 2009 Chapter 6 Administration and Usage Recommendations Atoll RF Planning & Optimisation Software Administrator Manual 166 AT281_AM_E1 © Forsk 2009 Chapter 6: Administration and Usage Recommendations 6 Administration and Usage Recommendations This chapter deals with various technical recommendations that you can follow to optimise your work with Atoll. It includes system dimensioning, and hardware and software requirements, as well as guidelines to help you set up your working environment. It also lists some recommended approaches for working with Atoll that can help you get the most out of your hardware and avoid potential problems while working with Atoll. 6.1 Recommendations on Network Architecture These recommendations are based on the results of benchmark tests carried out on the network of an average-sized operator, with around 40 to 60 Atoll licences. The results show the requirements in terms of network, hardware, and software per user. Based on these recommendations, you can setup your network working environment for any number of users. The benchmark tests were based on the following scenario: • Number of end-users: 40 • Each user working on the following Atoll document: - 1660 sites, i.e., around 5000 cells Calculation area comprising 300 sites (900 cells) Calculation radius = 20 km, i.e., matrices of 40 km x 40 km each Calculation resolution = 50 m In order to simulate the average activity of Atoll users, each user is assumed to carry out a "Routine Operation" 5 times during a three-hour working period. The "Routine Operation" consists in modifying parameters for 40 cells in 30 minutes, recalculating path loss matrices for these 40 cells, and calculating a best server coverage prediction. Although a best server coverage prediction does not require a lot of computer resources in terms of calculation, it requires Atoll to load all the path loss matrices in memory. If the path loss matrices are stored on a file server, as recommended below, this operation will create a considerable data transfer activity over the network. The benchmark tests have been based on this simulated data transfer activity. 6.1.1 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 6.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 or 3 users is recommended. Thus, the required number of Citrix servers depends on the number of processors and the number of end-users. © Forsk 2009 AT281_AM_E1 167 Administrator Manual 6.1.2 Network Dimensioning You should setup your network according to the number of Atoll users, which in turn depends upon the size of your project. A country-wide project would have larger network dimensions than a project that covers a city. Link 6.1.3 Recommended Bandwidth From To End-user Citrix server 300 kbps per user Citrix server File server 30 Mbps per user performing calculations System Dimensioning This section provides guidelines for dimensioning your network servers for optimum performance with Atoll. 6.1.3.1 Recommended File Server Configuration • • • • 6.1.3.2 Recommended Floating Licence Server Configuration • • • • • 6.1.3.3 This server should be accessible to all the Citrix servers on the network in order to provide licence tokens for Atoll sessions to the users. There should be a reliable network connection between this server and all the Citrix servers. The floating licence server can be one of the Citrix servers. It should have the NetHasp License Manager correctly installed and running. The installation process is described in "Floating License Manager Installation" on page 29. The NetHasp hardware key should be correctly plugged in the parallel or USB port. Recommended Citrix Server Configuration • • • 6.1.3.4 The file servers store geographic data, path loss matrices, configuration and administration files, and user projects. The required hard disk space can be determined from the sizes of the above-mentioned data. Geographic data and shared path loss matrices should be stored on file servers so that the calculation processes accessing these data do not affect Atoll’s usage and unnecessarily slow down the GUI. Required disk space should be calculated according to the size of geographic data files and path loss matrix files. Refer to "Disk Space Requirements" on page 181 for more information. A bandwidth of 30 Mbps is recommended per user performing calculations between the Citrix servers and the file servers. This is because data is exchanged extensively between Atoll servers and the file servers during calculations. The Citrix servers are intended for installing and running Atoll, defining user rights, etc. Users connected to these servers can work with Atoll through Citrix MetaFrame. The recommended bandwidth between Citrix servers and remote Citrix clients for satisfactory performance is 300 Kbps per user. Hardware/Software Recommended Processor 1 dual-core processor per 2 to 3 users (1 quad-core per 4 to 6, and so on) RAM 1 GB per user Hard disk space 150 to 200 GB Operating system Microsoft® Windows® 2003 Server Application server Citrix MetaFrame Presentation Server 4.0 or later Recommended Database Server Configuration The following hardware and software recommendations are provided for Oracle release 9i or 10g. The same configuration can be considered valid for other database types as well. 168 Hardware/Software Recommended Processor 3 GHz dual-core RAM 1 GB system + 2 GB for the database Hard disk space 200 GB or more (Tablespace of around 100 MB per 10,000 transmitters) Operating system Microsoft® Windows® 2003 Server / Unix / Linux RDBMS Oracle 9i, 10g, or 11g, or Microsoft SQL Server 2005, or Sybase Adaptive Server 12.5 AT281_AM_E1 © Forsk 2009 Chapter 6: Administration and Usage Recommendations 6.1.3.5 Recommended Workstation Configuration The following table lists the minimum and recommended requirements for workstations intended for working with Atoll. Hardware/Software Recommended Processor 3 GHz dual-core or better RAM 2 GB or more Free hard disk space At least 10 GB (depending on local geographic data and local path loss matrices, if any) Graphics 1280 x 1024 with True or High Colours or better Operating system Microsoft® Windows XP Professional SP2 Additional software Microsoft® Office 2000 or XP Professional Citrix Client Citrix client 9.0 or later Other requirements - Fixed licence: 1 USB port required to plug-in the SuperPro hardware key - Floating licence: nethasp.ini file placed in the Atoll installation folder You should also have the Oracle client installed on the workstations if you are working with an Oracle database. The Oracle client should be the same version Oracle installed on the Oracle server. Note: • Optimal CPU usage can be achieved through running Atoll using an application server with Citrix metaframe. However, the amount of RAM required per user remains the same. So, in case of an application server dedicated to n users, each user will require at least 256 MB of RAM, i.e., a total of n  256 MB. 6.2 Recommendations on Installation 6.2.1 Microsoft Windows Updates It is recommended to keep your operating system up to date using the Microsoft Windows Update tool. It is, however, also recommended to go through the description of each update patch that Microsoft offers in order to see whether it might have a negative effect on your system or network. Pay special attention to updates and patches related to networking. It is also recommended to keep the uninstall directories, named "$NtUninstall...", under the Windows installation directory, in case you require to uninstall a certain patch. Furthermore, some of the update patches require uninstall folders of older patches to be available for their own installation. 6.2.2 Citrix MetaFrame Installation If you are using Microsoft Windows Server 2003, you must install Citrix MetaFrame XP 1.0 FR3 or above. You also have to install a version of Citrix Program Neighborhood. It is recommended to install Citrix Program Neighborhood 8.0. Important: 6.2.3 • Citrix Program Neighborhood 6.3 and above work correctly with Atoll, but it is highly recommended to use Citrix Program Neighborhood 8.0. • Citrix has announced that they will stop supporting the MetaFrame XP product line by the end of year 2006. Therefore, they recommend to start migrating from these products to Citrix Presentation Server 4.0. However, since Citrix Presentation Server 4.0 has not yet been tested at Forsk, we are unable to provide specific information about it at the moment. Atoll Installation Following are a few important elements about installing Atoll. • • • • © Forsk 2009 If you have trouble installing Atoll, make sure that you are logged on with a user account that has administrator rights on the computer. If the version of the Microsoft Data Access Components (MDAC) installed on your computer is older than 2.7, you will have to install a newer version. You can install the newer version from the Atoll installation CD or download it from the Microsoft website: http://msdn.microsoft.com/data/mdac/default.aspx. The minimum required MDAC version is 2.7. Microsoft Windows XP, 2003 Server, and later versions install these components automatically, so you will not have to install them yourself. It might be helpful in certain cases to assign user access rights to the Atoll installation folder. - Administrators: Read & Write - Users: Read only If you have installed Atoll on a Citrix MetaFrame server, it must be published in order for all the users to have access to it. AT281_AM_E1 169 Administrator Manual Detailed recommendations for, during, and after the Atoll installation are provided in "Atoll Installation" on page 24. 6.2.4 Licence Manager Installation Following are a few important points about installing the Licence Management Server. • It might be helpful in some cases to assign user access rights to the installation folders of the NetHASP Licence Manager and the HASP Monitor. - Administrators: Read & Write Users: Read only Important: • It is recommended to switch off your computer before unplugging or plugging in the hardware key. • Do not change the computer’s date. • With a temporary SuperPro hardware key: - Do not reprogram it even if you plug it into another computer. - Do not modify the time bomb settings before contacting the Forsk Technical Support Team. • • NetHASP hardware key is supported by Windows 2000 Server and Windows 2003 Server with NetHASP License Manager 8.20 or above. In some networks, and under some circumstances, it might occur that the network key may not be accessible and a key protection error message encountered by Atoll users. This can most likely be due to a heavily loaded Licence Management Server. There might be an application running on the server, in parallel to the Licence Manager, which might be causing this problem. The best solution would be to remove any such application from memory. If this approach is not possible, try changing the latency associated to the Licence Manager software, in accessing the key. This might help in resolving this issue. Detailed recommendations for, during, and after the Licence Manager installation are provided in "Floating License Manager Installation" on page 29. 6.2.5 Distributed Calculation Server Installation Following are a few important points about installing the Distributed Calculation Server. • • You must log on with a user account with administrator rights on the computer when installing Atoll and the distributed calculation server. In the case where geographic data is centralised on a file server, make sure that this service is installed on the workstation through a user account that has enough rights to access the geographic data needed for calculations. This might not be the case by default. You can assign a user account to the distributed calculation service through Control Panel > Administrative Tools > Services > Atoll Server properties > Log On tab. Detailed recommendations for, during, and after the Distributed Calculation Server installation are provided in "Distributed Calculation Server" on page 36. 6.3 Recommendations on Geographic Data 6.3.1 Location of the Geographic Data Following are a few recommendations on the location of geographic data files. • • • Geographic data should either be located on each server or accessible through a fast network connection, e.g., 1 Gbps. It might be helpful in some cases to assign user access rights to the folders or disks containing the geographic data files. - Administrators: Read & Write - Users: Read only Link or embed: - Usually, in a multi-user environment, it is more suitable to place all of the geographic data on a central geographic data server so that it is accessible by all the users. This approach also avoids the need to replicate the geographic data on all the workstations. - - 170 Geographic data located on workstations can also be linked to the Atoll document. Linking geographic data to Atoll documents, rather than embedding, is advised in order to not exceed the 2 GB file size limit of Microsoft Windows (32-bit editions). Embedding geographic data in .atl files may be useful for the purpose of portability of these files. Otherwise, it is always advisable to link these data to, rather than embed them in, Atoll documents. AT281_AM_E1 © Forsk 2009 Chapter 6: Administration and Usage Recommendations 6.3.2 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 leads to hundreds of files describing just the geographic data. Atoll is designed to optimise memory consumption, which enables it to perform efficiently with regional tiles (1 tile/file per region). • • • Recommended file size: between 100 to 200 MB Erdas Imagine Pyramids files can be bigger, though not larger than the 2 GB limit. ECW files can be of any size (no limitations). Merging small tiles to build a regional tile can improve performance greatly. 6.3.3 Recommended Formats In order to improve performance, it is recommended to use uncompressed DTM and clutter files, for example, files in .bil format. Using compressed geographic data files, for example, compressed .tif or Erdas Imagine, can cause unnecessary decrease in performance due to decompression in real time. If you are using compressed geographic data files, it is strongly recommended to: • • Either, hide the status bar, which 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 104. The following table shows the recommended file formats for different geographic data: Geographic data type Recommended file format Scanned maps ECW Vectors SHP 6.4 Recommendations on Path Loss Management 6.4.1 Shared and Private Path Loss Matrices Following are a few recommendations on the management of shared path loss matrices. • • Shared path loss results should be accessible to Atoll through a fast network connection, e.g., 1 Gbps. These results are accessed by Atoll when calculating a coverage prediction study, and should be available to the users through a fast network connection, i.e., 30 Mbps at least per user. It might be helpful in some cases to assign user access rights to the folders/disks containing the shared path loss matrices files. - Administrators: Read & Write Users: Read only Following are a few recommendations on the management of private path loss matrices. • 6.4.2 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 can be useful for disk space management. For more information, see "Deleting Private Path Losses When Shared Path Losses are Valid" on page 101. Link or Embed It is always recommended to have path loss matrices files linked to your Atoll documents rather than embedding the path loss results in the .atl file. Path loss results should only be embedded in .atl files if there is a need of document portability, for example. Externalising your path loss matrices to shared or private path loss folders will help you in keeping your .atl file size within limits. This means less fragmentation and not exceeding the Windows’ (32-bit editions) limit of 2 GB file size. Externalising path loss results, i.e., to create .los files for each path loss matrix and to store them in a folder and not inside the .atl project file, has many advantages, such as: • • • You can limit the .atl file size by storing the related path loss matrices at a separate location. By storing the path loss matrices on another computer, accessible through a fast network connection, you can also gain local disk space. By setting up a shared path loss folder, you can easily manage a centralised path loss file server, accessible by all the users working on the same Atoll document. Note: • © Forsk 2009 There is no significant difference in terms of performance if you have embedded path loss matrices or linked matrices files in local path loss matrices folder. Therefore, even when working locally, it is advised to store the path loss matrices externally. AT281_AM_E1 171 Administrator Manual 6.4.3 Setting Up Efficient Shared Path Loss Matrices Folders The .losses folder associated with an Atoll document contains all the path loss matrix files corresponding to the project. A LowRes subfolder also exists within the main .losses folder, if there are extended path loss matrices as well. Note: • You can have two path loss matrices per transmitter (sector) in Atoll. These path loss matrices can have different calculation radii (area) and calculation resolutions (pixel size). Usually, the main path loss matrices are used for calculating fine path loss results (smaller calculation area, higher resolution) near the transmitter, and the extended path loss matrices are used for calculating rough path loss results (larger calculation area, lower resolution) far from the transmitter. Atoll places all the .los files corresponding to the main path loss matrices of all the transmitters in the .losses folder, and all the .los files corresponding to the extended path loss matrices of all the transmitters in the LowRes subfolder. This default approach is efficient enough for most (nearly all) of the working environments. Although, .los file access over the network and file search within the shared path loss matrices folder might take too long for Atoll documents with a large number of sectors. It might be interesting, for operators planning large networks, to set up the shared path loss folder in the manner described below. This loss in performance is due to the fact that Microsoft Windows takes a long time to search a file in a folder if there is a large number of files present in that folder. The following method, or workaround, can be used to decrease the number of .los files in a folder in order to gain performance. Important: • Some of our clients have reported improvements in overall system performance by adapting the architecture explained below, while test benches conducted at Forsk have not shown considerable improvements. So, it is recommended that you carry out some tests internally to determine whether your network (LAN) and system require such implementation or not. And, you might or might not need to implement this architecture. • Microsoft’s TechNet page mentions some limits of the NTFS file system, mainly the maximum number of files per folder and a recommendation. It says, "Some guidelines to consider when designing a folder structure include: Avoid putting a large number of files into a folder if you use programs that create, delete, open, or close files quickly or frequently. The better solution is to logically separate the files into folders to distribute the workload on multiple folders at the same time." See: http://www.microsoft.com/technet/prodtechnol/winxppro/reskit/c13621675.mspx. If there is a single shared path loss matrices folder containing all the .los files, e.g., 50,000, and an Atoll user launches a coverage prediction study, Microsoft Windows can take a long time searching for the needed .los files required in the coverage prediction. On the other hand, if there are subfolders containing, for example, 500 path loss matrix files each, instead of 50,000, it might take much less time to search for the required path loss matrices. If the calculation administrator has a large region to manage whose shared path loss matrices folder contains a large number of .los files, he can implement the following approach to reduce the number of files in a single folder. This approach can considerably decrease the file access time experienced by Atoll users. In the following example, let us assume that: • • • A region contains 50,000 transmitters (sectors) This region can be divided in to 10 states Each state can be subdivided in to 10 counties Therefore, each county will have around 500 transmitters. To set up county-level path loss matrices folders: 1. First of all, create the region-level Atoll document called, for example, Regional_Atoll_Project.atl. In this step, you must set up a region-level .atl file with all the geographic data and radio network data correctly linked to the file. 2. Once you have all the sites placed and their parameters adjusted (if you are doing this at the beginning of a network planning process, this might be a rough placement and a rough adjustment), create a private external path loss matrices folder. This folder will serve as the shared path loss matrices folder for all the users working on this region. Refer to "Setting Up Shared Path Loss Matrices" on page 45 for more information. Atoll will create the .losses folders and the associated pathloss.dbf files. 3. Create state and county subfolders. For example, if your region-level .atl file is placed in a folder named "C:\Regional_Atoll_Project\", you can create state and county subfolders as: - "C:\Regional_Atoll_Project\State_1\County_1" through "C:\Regional_Atoll_Project\State_10\County_10" Note: • In this example, the state-level subfolders do not contain any .atl files. They only have 10 subfolders, one for each county in that state. 4. Now, in your region-level Atoll document, create subdivisions of sites for counties, using the filtering features in Atoll. Export the sites and all the radio data corresponding to each county to a separate .atl file called, for example, State_M_County_N.atl. These .atl files will contain only the subsets of sites from the region-level .atl file, but can be linked to the entire geographic data. This means that you do not have to divide the geographic data in to counties for these .atl files. 172 AT281_AM_E1 © Forsk 2009 Chapter 6: Administration and Usage Recommendations 5. Place these county-level .atl files in their respective subfolders. 6. Create external private path loss matrices folders for each of these county-level Atoll documents. This will create the .losses folder and the related pathloss.dbf files. 7. Run path loss matrix calculation on all of these county-level Atoll documents. In this way you will have 500 path loss matrix files in each county-level subfolder with a corresponding pathloss.dbf file. 8. Pathloss.dbf file is a dBase III format file. Write a macro which reads the file name and path from each of the county-level path loss matrix files and writes this information to the region-level pathloss.dbf file. This macro, - Reads the FILE_NAME field of the pathloss.dbf file in the county-level path loss matrices subfolders, for example, "C:\Regional_Atoll_Project\State_1\County_1\State_1_County_1.losses\". Let us assume that this pathloss.dbf contains the entry "Site42_0.los". And, replaces the existing contents of FILE_NAME field in the pathloss.dbf file of the region-level path loss matrices folder (available in "C:\Regional_Atoll_Project\Regional_Atoll_Project.losses\") by: "C:\Regional_Atoll_Project\State_1\County_1\State_1_County_1.losses\Site42_0.los" - Once this macro finishes its task, the main pathloss.dbf file, in the region-level path loss matrices folder ("C:\Regional_Atoll_Project\Regional_Atoll_Project.losses\"), will contain full paths for all the .los files in the project. Now, there will be a single pathloss.dbf, which all the users can access through their projects. The region-level path loss matrices folder will contain only this file, and not any path loss matrices. The path loss matrices will be placed in the countylevel path loss matrices subfolders. These subfolders will contain 500 path loss matrices, instead of a single region-level path loss matrices folder containing all the 50,000 path loss matrices. Once set up, this pathloss.dbf file will have to be managed by the calculation administrator through the region-level Atoll document. You can somewhat improve your overall system performance by this means. Important: • The shared path loss matrices folder should be "Read/Write" accessible for the administrator, but "Read-only" for other users. Note: • A macro is available from Forsk on demand which, for all county-level .atl files, runs Atoll, opens the .atl file, refreshes data from the database, runs path loss calculations, saves file, and exits. Figure 6.2: Setting Up Efficient Shared Path Loss Matrices Folders 6.5 Recommendation on Defining Paths to Linked Files The recommended method of defining paths to geographic data or path loss files is 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: © Forsk 2009 Absolute Path C:\Program Files\Forsk\Geo Data\... Relative Path \Program Files\Forsk\Geo Data\... UNC Path \\Computer\C\Program Files\Forsk\Geo Data\... AT281_AM_E1 173 Administrator Manual If you define paths to geographic data and path loss files using the UNC in your Atoll document, it will be able to keep track of all the linked files even if it is moved to another computer. 6.6 Recommendations on Database Usage 6.6.1 Database Upgrades The Atoll database administrator should set up a backup policy for creating backups of the database at suitable intervals. You should try not to skip any major version of Atoll if you are working with databases. For example, if you are currently using Atoll 2.N, you should not skip Atoll 2.N+1 and directly install Atoll 2.N+2. Upgrading your database will be simpler if you donot skip a major version. If you skip or have skipped an intermediate major version, you will have to upgrade your database twice in order to make it compatible with the new version. 6.6.2 Import From Planet If you import a Planet database and encounter problems, it is strongly advised to correct those problems in your Planet database and try the next import in to a fresh Atoll document. Continuously deleting the problematic records in the same .atl file and reimporting from the Planet database after correction may cause problems and database inconsistency issues. 6.6.3 Oracle Client Version Oracle Client version 9.2.0.1.0 or later should be installed when working with Microsoft Windows Server 2003. 6.6.4 Tables and Fields These rules can help you improve the performance of your database and gain disk space: • • • • If your projects allow it, it is highly recommended to reduce the size of the field corresponding to the transmitters’ names. This modification concerns the NAME field in the Transmitters table and TX_ID Field in most of the other tables, such as tables concerning neighbours, cells and subcells, etc. You can also do the same, and gain more disk space, with the fields corresponding to site names. Avoid creating new user-defined (custom) fields of Text type. Rather, use numeric field types, which allow sorting and other actions. If you have to add Text fields, try to allocate just the field length that would suffice. For example, a 255-character long Text type field would, for the most part, occupy disk space for no purpose. You should restrict the number of user-defined fields introduced in neighbour management tables. Also keep in mind that: • • • • Boolean fields, system or user-defined, should always have default values assigned. If you want to add a new custom field in your Atoll document, you should first add the field in the database, and then update your Atoll document from the database using the Refresh feature. You must not add fields and tables whose names start with a number or contain an SQL or RDBMS-specifc keywords, such as ORDER, DATE, etc. Oracle databases allow a maximum length of 30 characters for field and table names. You should not create tables and fields with names more than 20 characters long. This is because Atoll adds some more characters to the table and field names for creating associated triggers, and when creating project databases. Limiting the number of characters in the field and table names that you create to 20 will avoid database connection and consistency problems. When setting up your database for the first time, it might be helpful to anticipate a few general-purpose user-defined fields in a few tables beforehand. You should analyse the needs of each group of users to assess if they would require additional fields in Atoll tables during their work. For example, you can add three user-defined fields of type integer, float, and text (limited size), to the Sites and the Transmitters tables. Users will have access to these three fields in both of these tables from the start, and they will be able to use them for any purpose. This approach might be helpful in setting up a functioning database, which will last a long time before requiring the addition of customised fields to tables. 6.6.4.1 User-Defined Fields and Default Values The CustomFields table enables you to define default values and choice lists for all the fields of all the tables in Atoll, including user-defined fields added to different tables. For each custom field, you must indicate the table in which it should be available, and you can assign a default value and a choice list. The values defined in this table have priority over the internal predefined default values. In order for Atoll to correctly consider the new default values, note that: • • 6.6.5 If you use floating point values, ensure that all the users have the same decimal separator (comma or point). The field names are case sensitive. Regionalisation You can carry out regionalisation of your Oracle database in the following two manners: 174 AT281_AM_E1 © Forsk 2009 Chapter 6: Administration and Usage Recommendations • Through regional databases This is a static approach that requires synchronisation between the master and the regional databases through the Atoll Management Console. In this approach, the database administrator creates regional databases from the master database. This regionalisation can be performed through site lists, SQL filters, and filtering polygons as described in "Creating Project Databases" on page 143. Currently, this approach is only available for Oracle databases. It will be extended to other databases in future versions of Atoll. Here are the advantages and the disadvantages of this approach: - Advantages: This approach is very efficient in terms of performance. - Disadvantages: This approach requires synchronisation between the master and the regional databases, i.e., the database administrator must update the master database with the contents from the regional databases using the Atoll Management Console. • Directly through the master database This is a dynamic approach based on Oracle Spatial and user connection properties. To implement the regionalisation approach based on Oracle Spatial, you do not have to buy Oracle Spatial. You can implement this solution using Oracle Locator, which is provided in the standard Oracle installation. - Advantages: This approach creates dynamic regions, which do not require administrator intervention to upgrade the master database. - Disadvantages: This approach is less efficient in terms of performance. Archiving data in the database takes the longest time among the various operations performed with the database. You can choose either of the two approaches depending on your needs and considering the advantages and the disadvantages of both. 6.7 Recommendations on Calculation Management 6.7.1 Computation Server Stability and Resource Management In certain conditions, as described below, Atoll users might experience a decrease in server performance and stability in a multi-user Citrix environment. The principal difference observed might be the inability to run multiple Atoll sessions on the server without getting error messages, general application failures, or server crashes. Such problems may occur when the number of Atoll sessions on the server, carrying out calculations, increases to more than four. 6.7.1.1 Causes of Instability and Loss of Performance This general instability and low performance of the servers is due to: • • • Insufficient memory resources: globally and per process (Atoll session) Insufficient CPU resources Network congestion Atoll can process four simultaneous path loss matrices calculations, which means high CPU and RAM resource consumption, and as the 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. 6.7.1.2 Troubleshooting and Solution Go through the following check list in order to resolve the above problems: • 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 dedicated Computation Server (Atoll Distributed Computation Server) should be set up on the server. Through the distributed calculation server feature of Atoll, the path loss calculations can be performed outside Atoll. This means that a distributed computation server on a computer, which is a separate process from Atoll, performs the computations rather than Atoll itself. Note: • - © Forsk 2009 This Distribution Computation Server can also be used to transfer the path loss calculations to a different computer. Enabling the Computation Server offers several advantages: AT281_AM_E1 175 Administrator Manual - Path loss calculations are limited to four parallel instances regardless of the number of Atoll sessions running on the server. A queuing system, integrated in the Distributed Computation 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 there is a computation server failure. Path loss calculations are carried out by a separate process (AtollSvr), which has its own memory allocation apart from Atoll. - This computation environment can introduce considerable improvements in both the number of Atoll sessions per server and the computations. After this implementation, the same servers should be able to work as previously or even better. These improvements are due to: - Path loss calculations are controlled and limited to four parallel threads instead of potentially 4 x number of active Atoll sessions. This notably improves the memory and CPU consumption. Path loss calculations have their own process and memory environment, i.e., the amount of memory necessary for those computations no longer impacts the Atoll sessions’ 2 GB limit. With this architecture, a server equipped with four processors (eight threads with hyper-threading) can accommodate four simultaneous path loss computations, and fully use the remaining four threads for other Atoll operations. Atoll’s interface will also be more efficient and the overall processing time for various tasks will be improved. Note: • • 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: - - 6.8 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. - • In order to prevent users from deactivating the use of the Computation Server and bypassing the resource control procedure established above, the Atoll.ini file should be set to read-only for users other than the administrator. Virtual memory can be increased from 8 GB to 16 GB, for example. You can also increase the default Windows memory allocation limit from 2 GB to 3 GB as explained in "Process Memory" on page 183. Recommendations on Atoll Administration Files There are three types of administration files for Atoll described in "Administration Files" on page 69. There is no specific order in which these files should be created or installed on Atoll workstations and servers. It is sufficient to have these files created and placed in the right locations before running Atoll to have the predefined configuration of all workstations and servers. If you have already configured these files for one server, and you are setting up another server, you can copy these files to their respective locations on the new server to have the exact configuration and set-up as the first. If you do not copy these files, or create them, you will not have the same configuration of the new server, but apart from that you will be able to work with Atoll normally. These files are optional, not obligatory. • Initialisation File (.ini) - • 176 It is highly recommended that the Atoll initialisation file be created or modified only by the administrator. The Atoll initialisation file is used to set the preferred settings to be used during Atoll sessions. It can be used to adjust the behaviour and algorithms used in Atoll. If you are using Windows 2000 Server, state the actual number of processors in the .ini file. The location of Atoll.ini, MeasImport.ini (which serves as the configuration file when importing CW measurements), and other .ini files can be managed through the Atoll Management Console as described in "Managing Administration File Paths" on page 147. Configuration File (.cfg) - Use Atoll to create these files. Modifying these files manually is not recommended as human error can introduce problems. - Uncheck image visibility to avoid loading unnecessary data in the memory. - You can store the information regarding geographic data only in .geo files. - You can set up your configuration files in the following manner: - A common configuration file that points to the geographic data, macros, and other common parameters in your Atoll documents. - Separate configuration files created for your 2G and 3G projects, which would store their respective coverage prediction studies parameters, traffic information, neighbour allocation parameters, and other technology-specific parameters. - Separate configuration files based on, and for, different groups of users. These groups of users may be, for example, groups of users working on different regions, groups of users working on different technolo- AT281_AM_E1 © Forsk 2009 Chapter 6: Administration and Usage Recommendations gies, groups of users focusing on certain operations (i.e., performing certain types of coverage predictions, performing the AFP, etc.). • XML Studies 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. 6.9 Recommendations on Atoll Usage 6.9.1 Performance and Memory Issues Following are a few recommendations on performance and memory usage. Memory Refresh • You can avoid memory fragmentation while working with Atoll documents by saving the Atoll document from time to time, closing and restarting Atoll, and reopening the document. This advice is applicable to any application running under Microsoft Windows because many common .dll files are accessed by applications, and unloading and reloading these .dll files refreshes their memory allocation. • If you are working in a Citrix MetaFrame environment, you should restart your Citrix server every week or fortnight. The exact time should be determined by the administrator depending on the state of the network (LAN). • In certain cases, it might be more appropriate to start working on a completely fresh .atl file. If you have been working on your existing .atl file for a long time, it might have attained a large size and might contain some useless remains from your earlier operations, e.g., traces of records that no longer exist in the database, etc. You can completely refresh your project by following these steps: - - Open the existing .atl file in Atoll that you want to replace. Create a personal, or local, .cfg file, from your existing .atl file with all the required information, e.g., geographic data information, coverage prediction studies parameters, neighbour allocation parameters, calculation and focus zones, etc. For more information, refer to "User Configuration File (.cfg)" on page 69. Close the old .atl file. Select Open from Database to create a fresh .atl file. Import the personal, or local, .cfg file in the new .atl file. You now have a clean .atl file to work with, which has all the same information as the old .atl file, and takes up less space on the hard disk, has less fragmented data, and shows improved performance. Memory Allocation • If you have to open several large .atl files simultaneously on the same computer, it is better to open each in a separate Atoll session rather than to open them all in the same Atoll window. Each Atoll session on the same computer has its own 2 GB memory space allocated by the operating system. If you open a number of large .atl files in the same Atoll session, it might reach its 2 GB memory allocation limit. This will not be the case if you open .atl files in different Atoll sessions. If you are working on a co-planning proect, you have to open linked .atl files in the same Atoll session. Moreover, each computer consumes a single licence independent of the number of Atoll sessions open simultaneously. File Size • Coverage prediction studies 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 prediction studies can take up a considerable amount of memory even if they are not displayed on the map. • Externalise DTM, clutter, path loss results, and any other data that can be externalised, so that the .atl file size does not become unnecessarily large. Path Loss Calculation © Forsk 2009 • 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 pico cells 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 AT281_AM_E1 177 Administrator Manual 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 • 6.9.1.1 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 centers 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 folder’s Properties dialogue, means that the computations will take into account all the interferers. However, if you set it too high, you might lose important interference information. The proper value for this threshold depends on the Reception Thresholds and the C/I Thresholds defined in the Subcells table. The optimum value would be Min AllSubcells  RT i – CIT i – M  . Which means the minimum value of the factor RT i – CIT i – M computed for all subcells, i. Where, RTi is the reception threshold of the subcell i, CITi the C/I threshold of this subcell, and M is a safety margin. Since this interference threshold is used both in interference matrices calculation and in interference predictions, it is important to have at least a 3-dB margin for the interference energy aggregation in C/I studies. We recommend a safety margin of 5 dB, which can be reduced if any problem is encountered. • Do not define very high C/I quality thresholds (Default values: 12 dB for BCCH and 9 dB for TCH). If you want a certain TRX type to carry GPRS/EDGE traffic, you can add 1 or 2 dB to this value for that TRX type, and use the option of safety margin in the AFP module’s Cost tab. The 12 dB and 9 dB default values already include safety margins. If you increment these values too much, it will unnecessarily load the interference matrix generation and the AFP. • Do not start an AFP session if the interference matrices report indicates problems: All the transmitters should have interferers and very few of them (not more than 20%) should have more than 70 interferers. If there are too many or too few entries in your interference matrices, the AFP plan will not be optimal. • If the memory-critical task is interference matrices generation: You can generate interference matrices in a piecewise manner. This means that you can generate nation-wide interference matrices with low resolutions based on the percentage of interfered area (to improve computation time), with a cell edge coverage probability of 50% (which means no access to clutter for reading standard deviation values), and an interference threshold of -112 dBm. This will provide rough global interference matrices which can be locally improved. These interference matrices will be less memory-consuming. Then, use polygon or site list filters to focus on each important location, and calculate local interference matrices with higher resolutions and reliabilities. Make sure that the computation zone in your project completely encompasses the filtering zones that you define. 178 • 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. AT281_AM_E1 © Forsk 2009 Chapter 6: Administration and Usage Recommendations 6.9.1.2 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. 6.9.1.3 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: 6.9.2 • 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 "Setting Up Databases" on page 183. 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.) 6.9.3 Coverage Predictions Following are a few recommendations on performing coverage prediction studies. • If you do not want Atoll to calculate the shadowing margin during a coverage prediction, it is advised to clear the "Shadowing taken into account" check box. This approach is more efficient in terms of performance than selecting this option and setting the Cell Edge Coverage Probability to 50%. • To improve memory consumption and optimise the calculation times, you should set the display resolutions of coverage predictions according to the precision required. The following table lists the levels of precision that are usually sufficient: Size of the coverage prediction • 6.9.4 Display resolution City Center 5m City 20 m County 50 m State 100 m Country According to the size Atoll provides you with the possibility of setting different resolutions for coverage predictions independently of the resolutions of the geographic data in your documents. If your geographic data has a 50 m resolution, it is possible to set the resolutions of your coverage predictions to 100 m. CW Measurements and Drive Test Data Following are a few recommendations on working with CW measurements and drive test data. • © Forsk 2009 It is recommended to use Fast Display in order to increase display speed. This option is available in the Display tab of the Properties dialogues for CW Measurements and Drive Test Data folders. Although this approach only AT281_AM_E1 179 Administrator Manual displays measurement points as small squares, it may have a significant impact on performance depending on the number of measurement points in the Atoll document. • 6.9.5 When performing a CW measurements drive test campaign, please follow the recommended procedure described in the SPM Calibration Guide. Path Loss Matrices Refer to "Link or Embed" on page 171. 6.9.6 Antenna Patterns and Electrical Downtilts 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. 6.9.7 Antenna Import Following are a few recommendations on antenna import. • Antenna names used in some tools, such as NetAct, can be different from those used in their corresponding antenna files. To solve this issue, you can create a new file, named "Index", containing the list of antenna names, which would in fact be the pattern (antenna file) names. You should place this file at the same location as the antenna patterns (files). This will replace the antenna names with the new antenna names. • Some Kathrein antenna pattern files might have names different from the antenna pattern names present inside the file. You will have to replace the name of the pattern inside the file by the name of the pattern file itself, in order to import these antennas correctly. • A Planet Index file contains the path to and the name of each antenna file available. Creating such an Index file when there are hundreds of antenna patterns available can be a difficult task. You can easily create the index file from the Microsoft Windows command prompt. You can open the Command Prompt window by selecting Start > Run, entering "cmd" and pressing ENTER. In the Command Prompt window, navigate to the directory containing the antenna pattern files, enter the following command and press ENTER: dir /b > Index This will create a file called "Index" in the same directory as the antenna patter files containing a list of all the antenna pattern file names, with one name per line. The file will also contain a line with its own name, so, before importing this file into Atoll, you should use a text editor to remove the line containing the file name "Index." 6.9.8 Traffic Maps Following are a few recommendations on working with traffic maps. • • • User profile environment-based traffic maps should only be used for a precision on traffic that is of the same level as the statistical clutter available in a project. For higher precision on traffic data, you should use sector traffic maps or user density traffic maps. User density traffic maps provide you with a means to define a density for each set of service, terminal type, and mobility type. Sector traffic maps are best suited for traffic data issued by the OMC. 6.10 Recommendations on the Atoll API 6.10.1 Using Atoll Through the API Correct functioning of Atoll when using Atoll through the API is guaranteed during interactive user sessions only. Atoll is an application that requires creating tool bars, creating menus, reading user profile options from the Windows’ registry, accessing printers, etc., even when it is accessed through the API. The same is true for add-ins working with Atoll. Even though it is possible to load and use Atoll when there is no user session open on a computer, its correct functioning is not guaranteed. Unexpected errors can occur. Particularly, creating objects through CreateObject or CoCreateInstance may fail. Therefore, the correct functioning of Atoll requires an open user session on the computer. 6.11 Appendix: Memory Requirements This part gives some aspects of memory requirements (both RAM and hard disk space) for Atoll depending on the network to be planned. Atoll is capable of performing computations in pixel sizes different from those of the raster maps in a project. It is recommended to perform detailed planning with smaller pixel sizes in high density areas, and country-wide (or region-wide, 180 AT281_AM_E1 © Forsk 2009 Chapter 6: Administration and Usage Recommendations depending on the size) coverage predictions and other calculations using larger pixel sizes. This approach will provide overall satisfactory results, and will considerably improve the disk space requirements, RAM allocation and calculation time. Please note that the figures mentioned in the following sections are approximate, and though actual figures may vary, their deviation from the approximate values will be negligible. These approximate values are computed through simplified formulas. These formulas do not consider all the input parameters, but only the input parameters that have a considerable impact on memory requirements. 6.11.1 Disk Space Requirements The amount of disk space required for data varies from project to project. It depends mainly on the size of the planning area, the pixel size, and the number of cells. In networks with only a few cells, the amount of disk space required is chiefly 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. 6.11.1.1 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. Note: • 6.11.1.2 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. Note: • 6.11.1.3 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. Notes: 6.11.1.4 • 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 system’s temporary directory whose size depends on the calculations. This file is described in the section on RAM requirements. © Forsk 2009 AT281_AM_E1 181 Administrator Manual 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. 6.11.1.5 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. Note: • 6.11.2 When saving a .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. RAM Requirements Usually, 512 MB of RAM in a workstation is sufficient for all operations with Atoll, provided that there are no other applications being used in parallel that consume large amounts of memory. Starting Atoll without loading a project requires around 20 MB of RAM (as monitored with the Windows Task Manager). Loading a project with 500 sites, a few predictions, and some simulations may increase the consumed memory to around 50 to 100 MB. 6.11.2.1 UMTS Simulations UMTS Monte-Carlo simulations are calculations that consume large amounts of memory. The memory requirement of these calculations is a function of the following: • • • • • • • • • • The number of sites involved The number of transmitters involved The number of cells involved The number of mobiles generated by the UMTS simulation The number of transmitters covering a pixel The number of services simulated The number of neighbours per cell The "Detailed Results" and "Limit Active Set to Neighbours" flags The number of links per mobile The number of channel elements per site Most of these parameters have minor influences and the actual requirements are mostly governed by the number of cells and the number of mobiles generated. 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 for normal simulations R = 14.0  t + 4.3  m using the "detailed results" option with R: peak RAM requirement in KBytes t: number of transmitters affecting the computation zone m: number of mobiles generated by the UMTS simulation Example: To calculate for 500 sites (or 1500 transmitters) and 2400 mobiles, around 28 MB of RAM are required for a normal simulation and 30 MB if detailed results are to be stored as well. Notes: 182 • 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 103. AT281_AM_E1 © Forsk 2009 Chapter 6: Administration and Usage Recommendations 6.11.2.2 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. Note: • 6.11.3 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. Process Memory 32-bit Operating Systems Atoll can support 3 GB address space on a properly configured 32-bit system. For more information, please refer to the following URL: http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx (/3GB section in “Memory Support and Windows Operating Systems”). The following link provides information on how you can setup your Windows 2000 Advanced Server, Windows 2000 Datacenter Server, or any Windows 2003 Server systems to activate the 3 GB switch at startup: http://technet.microsoft.com/ en-us/library/bb124810.aspx. Important: • The above article from Microsoft also states that the /3GB switch should not be used on Windows 2000 Server because it is not supported and can cause application or operating system crashes. 64-Bit Operating Systems The 64-bit edition of Microsoft Windows XP provides 4 GB of memory per process. © Forsk 2009 AT281_AM_E1 183 Administrator Manual 184 AT281_AM_E1 © Forsk 2009 Chapter 7 Data Structure Compatibility This chapter describes the modifications in the data structures of Atoll templates in Atoll 2.8 compared to Atoll 2.7 and how to upgrade any version 2.7 document to 2.8. Atoll RF Planning & Optimisation Software Administrator Manual 186 AT281_AM_E1 © Forsk 2009 Chapter 7: Compatibility Between Versions 2.7 and 2.8 7 Compatibility Between Versions 2.7 and 2.8 The database structure modifications in version 2.8 provide support for the new features implemented in 2.8. This chapter presents the differences in the data structures of versions 2.7 and 2.8. In order to upgrade from a 2.7 database structure to a 2.8 database structure, it is strongly advised that you use the Atoll Management Console. Database structures are only modified between two major versions. Therefore, databases are referred to as 2.7 and 2.8 databases, while Atoll documents are referred to as 2.7.x and 2.8.x documents. The following table lists the types of fields used in Atoll templates with their corresponding lengths, and also presents the equivalent fields and lengths in different databases: Microsoft SQL Server Equivalent Field Type Length Field Type Length Field Type Length Field Type Length Microsoft Access Equivalent Float 4 FLOAT 32 real 4 real 4 Single Double 8 FLOAT 64 float 8 float 8 Double Integer 4 NUMBER 11 int 4 int 4 Long Integer Atoll Oracle Equivalent Sybase Equivalent Short 2 NUMBER 6 tinyint 1 tinyint 1 Integer Boolean 2 NUMBER 1 bit 1 bit 1 Yes/No Variable* Text Variable* VARCHAR2 Variable* varchar Variable* varchar Memo Variable VARCHAR2 2000 varchar 4000 text Binary Variable LONG RAW image 16 image Text* Memo 16 OLE Object * Lengths for these fields are specified in parentheses in the database structure tables. Note: • In the tables listed below, primary keys are listed in bold and italic characters. 7.1 Upgrading From 2.7 to 2.8 7.1.1 Important Information Automatic upgrade using the Atoll Management Console allows upgrading data from any previous version to 2.8. It is highly recommended to use the Atoll Management Console for carrying out the upgrades. In version 2.8, some fields which are no longer used by Atoll have been removed from the data structures. Automatic upgrade using the Atoll Management Console will automatically remove them. Upgrading documents not connected to any database will also remove them automatically. In order for the Atoll Management Console to recognize obsolete or deleted fields from database tables, it is imperative that the ATOLL_ADMIN table exist, with its full definition as described in "Working With Master Databases" on page 139, 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. When the Atoll Management Console has been used to upgrade a database once, it will be able to recognize obsolete or deleted fields in the following upgrades. This is because the Atoll Management Console cannot distinguish between obsolete fields and custom fields added by the user when it is used to upgrade a database for the first time. Manual upgrade procedure described below allows upgrading data from version 2.7 to version 2.8. Users working with versions older than version 2.7 have to upgrade to version 2.7 first. Please refer to Administrator Manuals of previous versions or contact our support team if this is your case. If you use the Atoll Management Console’s Changes History Management feature, you must repair the upgraded database in order to continue using this feature. For more information, see "Managing the History of Data Modifications" on page 154. 7.1.2 Upgrading 2.7 Databases to 2.8 7.1.2.1 Recommendations It is highly recommended to upgrade your database using the Atoll Management Console. For more information on upgrading databases using the Atoll Management Console, see "Upgrading Databases" on page 146. If you are working with a centralised database, it is strongly advised to: • • • © Forsk 2009 Upgrade your database structure to 2.8 either automatically (see "Upgrading Databases" on page 146) or manually (see "Manual Database Upgrade Procedure" on page 188), Deploy Atoll version 2.8.x, Ask all the users accessing this database to refresh data in their documents from the database. AT281_AM_E1 187 Administrator Manual When users open their documents in Atoll 2.8.x, they are asked whether they want to upgrade the documents to the same structure as the database or to disconnect them from the database. If they choose to upgrade, Atoll automatically upgrades the data structure in their documents. 7.1.2.2 Manual Database Upgrade Procedure The procedure provided in this section is for information only. It should only be used if the database cannot be upgraded automatically using the Atoll Management Console for some reason. You can create a new 2.8 database using the contents of a disconnected 2.7.x document. To create a new 2.8 document based on the contents of a disconnected 2.7.x document: 1. Upgrade the disconnected 2.7.x document to a disconnected 2.8 document by following the procedure described in "Upgrading Disconnected Documents" on page 188. 2. Create a new 2.8 database using the disconnected 2.8 document by following the procedures described in "Creating the Master Database" on page 49 and "Using Oracle With Atoll" on page 59. Important: • If you are upgrading your database using a script based on the information provided in section "Changes in the Data Structure" on page 189, you must also add the ATOLL_ADMIN table whose complete description is available in "Working With Master Databases" on page 139. 7.1.3 Upgrading 2.7.x Documents to 2.8 7.1.3.1 Upgrading Disconnected Documents When you open a disconnected document last saved using any previous Atoll version in Atoll 2.8, it’s data structure is automatically upgraded to 2.8 when the document is saved using Atoll 2.8. To upgrade a document that is not connected to a database, and that was last saved using any previous version of Atoll, to 2.8: 1. Start Atoll 2.8. 2. Open the document that you want to upgrade in Atoll 2.8. 3. Save the document. The document is upgraded to Atoll 2.8. Note: • 7.1.3.2 It is not possible to open a 2.8 document in an earlier version. Upgrading Documents Connected to 2.7 Databases A 2.7.x document connected to a 2.7 database will have to be disconnected from the database in order to be upgraded to 2.8. A document once disconnected cannot be connected to the database again. To upgrade a 2.7.x document to 2.8 by disconnecting it from the database: 1. Start Atoll 2.8. 2. Open the 2.7.x document in Atoll 2.8. A dialogue appears asking you to disconnect the document from the database if you want to upgrade it to 2.8 and open in Atoll 2.8. 3. Click OK. The document is disconnected from the database. 4. Save the document. The document is upgraded to Atoll 2.8. However, it is no longer connected to the database. 7.1.3.3 Upgrading Documents Connected to Upgraded Databases If a 2.7.x document is connected to a database that has already been upgraded to 2.8, the document can be upgraded to 2.8 as well with the following procedure. Important: • You can open a 2.7.x document connected to a 2.8 database, i.e., a database already upgraded, in Atoll 2.7.x, but it is not possible to save any modifications in the document. It is also not allowed to interact with the database (archive, refresh, etc., are not allowed). To upgrade a 2.7.x document to 2.8 keeping the connection with the database: 1. Start Atoll 2.8. 2. Open the 2.7.x document in Atoll 2.8. A dialogue appears asking whether you want to: - 188 Keep the document connected to the upgraded database and refresh data from the database, or Disconnect the document from the database. AT281_AM_E1 © Forsk 2009 Chapter 7: Compatibility Between Versions 2.7 and 2.8 3. Select Refresh From the Database if you want to upgrade the document and keep the connection with the database. 4. Select the Refresh Unmodified Data Only check box if you want to keep the current modifications in the document and load the data from the database that does not impact these modifications. 5. Select Disconnect From the Database if you want to disconnect the document from the database and upgrade it. Note: • A document once disconnected cannot be connected to the database again. 6. Click OK. Either the data is refreshed from the database or the document is disconnected from the database, depending on the selected option. 7. Save the document. The document is upgraded to 2.8 and is either connected to the upgraded 2.8 database or disconnected, depending on the selected option. 7.2 Changes in the Data Structure The following changes have been made in the data structure of the version 2.8 compared to the version 2.7.1. Note: • Field names in bold characters correspond to primary keys. 7.2.1 Changes in Microwave Radio Links Documents 7.2.1.1 MWDefaultsCurves Table The following field should be added to the MWDefaultsCurves table: Field Type INTERFERED 7.2.1.2 Description Attributes Null column allowed: Yes Default value: Text (50) MWEquipments Table The following field should be added to the MWEquipments table: Field Type MANUF_CHANNEL_SPACIN G Float 7.2.1.3 Description Attributes Null column allowed: Yes Default value: MWLinks Table The following fields should be added to the MWLinks table: Field Type Description Attributes Atmospheric pressure in mbar Null column allowed: Yes Default value: 1013 ATMOS_PRESSURE Float GEOCLIM_FACTOR Double Null column allowed: Yes Default value: RAIN_HEIGHT Float Null column allowed: Yes Default value: REFRACTIVITY Float Null column allowed: Yes Default value: PROPAG_IMODEL Text (50) 7.2.1.4 Propagation model used for interference calculation Null column allowed: Yes Default value: MWRepeaters Table The following fields should be added to the MWRepeaters table: © Forsk 2009 Field Type Description Attributes TILT_A Float Tilt of the repeater antenna in the direction of A Null column allowed: Yes Default value: TILT_B Float Tilt of the repeater antenna in the direction of B Null column allowed: Yes Default value: AT281_AM_E1 189 Administrator Manual 7.2.1.5 MWTplLinks Table The following fields should be added to the MWTplLinks table: Field Type Description Attributes Atmospheric pressure in mbar Null column allowed: Yes Default value: 1013 ATMOS_PRESSURE Float RAIN_HEIGHT Float Null column allowed: Yes Default value: REFRACTIVITY Float Null column allowed: Yes Default value: PROPAG_IMODEL Text (50) 7.2.1.6 Propagation model used for interference calculation Null column allowed: Yes Default value: Other Changes The Types for the following fields have changed: • • Integer to Float for VAPOR and TEMPERATURE in the MWLinks table. Integer to Float for VAPOR and TEMPERATURE in the MWTplLinks table. The following fields should be removed: • • LOSS_USE1, LOSS_USE2, LOSS_USE3, LOSS_USE5, LOSS_USE6, LOSS_USE7, FRQ_SEP, and HSB_ON from the MWLinks table. LOSS_USE1, LOSS_USE2, LOSS_USE3, LOSS_USE5, LOSS_USE6, LOSS_USE7, and HSB_ON from the MWTplLinks table. 7.2.2 Changes in GSM GPRS EGPRS Documents 7.2.2.1 FrequencyBands Table The following field should be added to the FrequencyBands table: Field MAX_CHANNEL_NUM 7.2.2.2 Type Integer Description Attributes Extended Channel Offset (used for band E-GSM) Null column allowed: Yes Default value: Transmitters Table The following fields should be added to the Transmitters table: Field Type Description Attributes CELL_IDENTITY Integer Cell identity Null column allowed: Yes Default value: TX_TYPE Short Type of transmitter (0 = Normal; 1 = Interferer only) Null column allowed: Yes Default value: 0 7.2.2.3 TplTransmitters Table The following field should be added to the TplTransmitters table: Field Type Description Attributes TX_TYPE Short Type of transmitter (0 = Normal; 1 = Interferer only) Null column allowed: Yes 7.2.2.4 TRGs Table The following fields should be added to the TRGs table: Field Type Description Attributes AFP_BLOCKED_COST Float Secondary AFP quality indicator Null column allowed: Yes Default value: 0 AFP_CONGESTION Float Secondary AFP indicator depicting the spectral congestion state Null column allowed: Yes Default value: 0 AFP_COST Float Main AFP quality indicator Null column allowed: Yes Default value: 0 AFP_FREEZE_DIM Boolean Permit the AFP to not always respect the number of required TRXs Null column allowed: No Default value: False 190 AT281_AM_E1 © Forsk 2009 Chapter 7: Compatibility Between Versions 2.7 and 2.8 AFP_SEP_COST Float Secondary AFP quality indicator Null column allowed: Yes Default value: 0 CS_ERLANGS Float Circuit switched demand in Erlangs Null column allowed: Yes Default value: 0 PS_DATA_ERLANGS Float Packet switched demand in data Erlangs (equivalent to avaraged used time slots) Null column allowed: Yes Default value: 0 7.2.2.5 TRXs Table The following fields should be added to the TRXs table: Field Type Description Attributes DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes Default value: 0 UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes Default value: 0 UPLINK_NOISE_RISE Float Uplink noise rise Null column allowed: Yes Default value: 0 7.2.2.6 EGPRSCodingSchemes Table A new EGPRSCodingSchemes table should be added with the following structure: Field Type Description Attributes CS_NUMBER Short Coding scheme number Null column allowed: No Default value: 1 DATA_CODING Short Type of FEC coding (0: Convolutional, 1: Turbo) Null column allowed: No Default value: 0 MAX_THROUGHPUT Float Maximum rate obtained when there is no data transmission error Unit: kbps Null column allowed: No Default value: 1 MODULATION Short Modulation (0: GMSK,1: 8-PSK, 2: QPSK,3: 16QAM, 4: 32QAM) Null column allowed: No Default value: 0 NAME Text (50) Name of the coding scheme Null column allowed: No Default value: TECHNOLOGY Text (15) Technology ("GPRS", "GPRS/EDGE", "EGPRS2") Null column allowed: No Default value: ’GPRS’ 7.2.2.7 EGPRSQuality Table The following field should be added to the EGPRSQuality table: Field Type Description Attributes CS_NAME Text (10) Coding scheme name Null column allowed: Yes Default value: 7.2.2.8 EGPRSServices Table The following field should be added to the EGPRSServices table: Field TYPE 7.2.2.9 Type Short Description Attributes Type of service (0: circuit; 1: packet; 2: circuit over packet) Null column allowed: No Default value: 0 EGPRSTerminals Table The following fields should be added to the EGPRSTerminals table: Field Type Description Attributes DL_AVAIL_CARRIERS Short Number of simultaneous carriers Null column allowed: Yes Default value: 1 PMAX Float Max power that can be used in UL (for UL calculations) Null column allowed: Yes Default value: 33 © Forsk 2009 AT281_AM_E1 191 Administrator Manual 7.2.2.10 InterNetChProtect Table A new InterNetChProtect table should be added with the following structure: Field Type Description Attributes ICP Memo Inter-network channel protection = f(  MHz) Null column allowed: Yes Default value: ITF_BW Double Interfering bandwidth (kHz) Null column allowed: No Default value: 0 ITF_TECHNO Text (50) Interfering technology Null column allowed: No Default value: V_BW Double Victim bandwidth (kHz) Null column allowed: No Default value: 0 7.2.2.11 Other Changes The following fields should be removed: • • • • • • CODING_SCHEME, EDGE, MAX_THROUGHPUT, and MODULATION from the EGPRSQuality table. PACKET_SWITCHED and VOICE from the EGPRSServices table. DEF_CIRCUIT_TS, DEF_PACKET_TS, and DEF_COMPOSITE_TS from the TRGConfigurations table. CIRCUIT_TS, COMPOSITE_TS, PACKET_TS, REQ_CIRCUIT_TS, REQ_COMPOSITE_TS, REQ_PACKET_TS from the TRGs table. CODING_SCHEME_NUMBER from the EGPRSEquipments table. NUM_SECOND_ANTENNAS from the TplTransmitters table. 7.2.3 Changes in UMTS HSPA Documents 7.2.3.1 Networks Table and The following field should be added to the Networks table: Field Type Description Attributes PTOT_RELATIVE_TO_PMAX Boolean Cell total power is absolute value (dBm) or relative to Cell maximum power (%) Null column allowed: No Default value: False 7.2.3.2 Sites Table The following fields should be added to the Sites table: Field Type Description Attributes MAX_IUB_RATE_UL Float Max Iub Backhaul rate for uplink Null column allowed: Yes Default value: 12288 MAX_IUB_RATE_DL Float Max Iub Backhaul rate for downlink Null column allowed: Yes Default value: 12288 7.2.3.3 Transmitters Table The following fields should be added to the Transmitters table: Field Type Description Attributes NUM_RX_ANTENNAS Short Number of transmission antenna ports available at the transmitter Null column allowed: No Default value: 1 NUM_TX_ANTENNAS Short Number of reception antenna ports available at the transmitter Null column allowed: No Default value: 1 7.2.3.4 TplTransmitters Table The following fields should be added to the TplTransmitters table: Field Type Description Attributes HSPA_SUPPORT Short HSPA features supported: 0: None; 1: HSDPA; 2: HSPA; 3: HSPA+ (Transmit Diversity); 4: HSPA+ (Spatial Multiplexing) Null column allowed: Yes NUM_RX_ANTENNAS Short Number of transmission antenna ports available at the transmitter Null column allowed: Yes NUM_TX_ANTENNAS Short Number of reception antenna ports available at the transmitter Null column allowed: Yes MAX_IUB_RATE_UL Float Max Iub Backhaul rate for uplink Null column allowed: Yes MAX_IUB_RATE_DL Float Max Iub Backhaul rate for downlink Null column allowed: Yes 192 AT281_AM_E1 © Forsk 2009 Chapter 7: Compatibility Between Versions 2.7 and 2.8 DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes 7.2.3.5 CDMACells Table The following fields should be added to the CdmaCells table: Field Type Description Attributes CELL_IDENTITY Integer Cell identity Null column allowed: Yes Default value: DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes Default value: 0 HSPA_SUPPORT Short HSPA features supported: 0: None; 1: HSDPA; 2: HSPA; 3: HSPA+ (Transmit Diversity); 4: HSPA+ (Spatial Multiplexing) Null column allowed: Yes Default value: 0 UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes Default value: 0 7.2.3.6 CDMAEquipments Table The following fields should be added to the CdmaEquipments table: Field Type Description Attributes IUB_E1_RATE Float Supported rate per E1 line (kps) Null column allowed: Yes Default value: 2048 IUB_HSDPA_PERCENT Short Iub HSDPA Backhaul Overhead (%) Null column allowed: Yes Default value: 20 IUB_OVERHEAD_DL Float Iub Common Transport Channel Backhaul Overhead per cell (rate in kps) Null column allowed: Yes Default value: 40 7.2.3.7 CDMAEquipmentsCEsUse Table The following fields should be added to the CdmaEquipmentsCEsUse table: Field Type Description Attributes IUB_RATE_DL Float Iub backaul rate for downlink (kbps) Null column allowed: Yes Default value: 15 IUB_RATE_UL Float Iub backaul rate for uplink (kbps) Null column allowed: Yes Default value: 15 7.2.3.8 CDMAEqptsHSUPARssUse Table A new CdmaEqptsHSUPARssUse table should be added with the following structure: Field Type Description Attributes BEARER_INDEX Short Cell identity Null column allowed: No Default value: CHANNEL_ELTS_UL Integer Inter-network downlink noise rise Null column allowed: Yes Default value: 1 EQUIPMENT Text (50) Name of the site equipment Null column allowed: No Default value: IUB_RATE_UL Float Inter-network uplink noise rise Null column allowed: Yes Default value: 15 7.2.3.9 UMTSServices Table The following field should be added to the UMTSServices table: © Forsk 2009 Field Type Description Attributes TYPE Short Type of service (0: circuit; 1: packet; 2: circuit over packet) Null column allowed: No Default value: 0 AT281_AM_E1 193 Administrator Manual 7.2.3.10 HSDPABearers Table The following field should be added to the HSDPABearers table: Field Type MODULATION 7.2.3.11 Short Description Attributes Modulation (0: QPSK; 1: 16QAM; 2: 64QAM) Null column allowed: No Default value: 0 HSUPABearers Table The following field should be added to the HSUPABearers table: Field Type Description Attributes MODULATION Short Modulation (0: QPSK; 1: 16QAM) Null column allowed: No Default value: 0 7.2.3.12 UMTSTerminals Table The following fields should be added to the UMTSTerminals table: Field Type Description Attributes HSPA_SUPPORT Short HSPA features supported: 0: None; 1: HSDPA; 2: HSPA Null column allowed: No Default value: 0 NUM_RX_ANTENNAS Short Number of reception antenna ports available at the terminal Null column allowed: No Default value: 1 HSUPA_DTX_SUPPORT Boolean Whether the terminal supports discontinuous DPCCH transmission or not Null column allowed: No Default value: False 7.2.3.13 UECategories Table The following fields should be added to the UECategories table: Field Type Description Attributes MIMO_SUPPORT Short MIMO support (0: None; 1: MIMO) Null column allowed: No Default value: 0 MODULATION Short Modulation (0: QPSK; 1: 16QAM; 2: 64QAM) Null column allowed: No Default value: 0 7.2.3.14 HSUPAUECategories Table The following field should be added to the HSUPAUECategories table: Field Type MODULATION 7.2.3.15 Short Description Attributes Modulation (0: QPSK; 1: 16QAM) Null column allowed: No Default value: 0 HSPAMIMOConfigs Table A new HSPAMIMOConfigs table should be added with the following structure: Field Type Description Attributes DL_DIVERSITY_GAIN Float Downlink diversity gain (D-TxAA) Null column allowed: Yes Default value: 0 HSDPA_BEARER_INDEX Short HSDPA Bearer index Null column allowed: Yes Default value: 0 MAX_MIMO_GAIN_TABLE Memo Maximum spatial multiplexing capacity gain graphs Null column allowed: Yes Default value: MIMO_RX_ANTENNAS Short Number of reception antennas used for MIMO Null column allowed: Yes Default value: 1 MIMO_TX_ANTENNAS Short Number of transmission antennas used for MIMO Null column allowed: Yes Default value: 1 MOBILITY Text (50) UE mobility Null column allowed: Yes Default value: RX_EQUIP Text (50) Type of receiver of the User Equipment Null column allowed: No Default value: ’Standard’ 194 AT281_AM_E1 © Forsk 2009 Chapter 7: Compatibility Between Versions 2.7 and 2.8 7.2.3.16 InterNetChProtect Table A new InterNetChProtect table should be added with the following structure: Field Type Description Attributes ICP Memo Inter-network channel protection = f(  MHz) Null column allowed: Yes Default value: ITF_BW Double Interfering bandwidth (kHz) Null column allowed: No Default value: 0 ITF_TECHNO Text (50) Interfering technology Null column allowed: No Default value: V_BW Double Victim bandwidth (kHz) Null column allowed: No Default value: 0 7.2.3.17 Other Changes The following fields should be removed: • • • • • • • ENABLE_HSDPA and ENABLE_HSUPA from the CDMACells table. USE_16QAM from the HSDPABearers table. NUM_SECOND_ANTENNAS, ENABLE_HSDPA, ENABLE_HSUPA, and RX_DIVERSITY_CFG from the TplTransmitters table. RX_DIVERSITY_CFG from the Transmitters table. ENABLE_16QAM from the UECategories table. PACKET_SWITCHED from the UMTSServices table. ENABLE_HSDPA and ENABLE_HSUPA from the UMTSTerminals table. 7.2.4 Changes in CDMA2000 1xRTT 1xEV-DO Documents 7.2.4.1 Networks Table The following field should be added to the Networks table: Field PTOT_RELATIVE_TO_PMAX 7.2.4.2 Type Description Attributes Boolean Cell total power is absolute value (dBm) or relative to Cell maximum power (%) Null column allowed: No Default value: False TplTransmitters Table The following fields should be added to the TplTransmitters table: Field Type Description Attributes DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes 7.2.4.3 CDMACells Table The following fields should be added to the CdmaCells table: Field Type Description Attributes CELL_IDENTITY Integer Cell identity Null column allowed: Yes Default value: DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes Default value: 0 UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes Default value: 0 7.2.4.4 UMTSServicesQuality Table The following field should be added to the UMTSServicesQuality table: Field Type Description Attributes MOBILITY Text (50) UE mobility Null column allowed: Yes Default value: © Forsk 2009 AT281_AM_E1 195 Administrator Manual 7.2.4.5 UMTSTerminals Table The following field should be added to the UMTSTerminals table: Field Type Description Attributes NOISE_FACTOR_SEC Float Noise figure used to determine the thermal noise at the receiver (for secondary frequency band) Null column allowed: Yes Default value: 8 PRIMARY_BAND Text (50) Primary frequency band Null column allowed: Yes Default value: SECONDARY_BAND Text (50) Secondary frequency band Null column allowed: Yes Default value: 0 7.2.4.6 InterNetChProtect Table A new InterNetChProtect table should be added with the following structure: Field Type Description Attributes ICP Memo Inter-network channel protection = f(  MHz) Null column allowed: Yes Default value: ITF_BW Double Interfering bandwidth (kHz) Null column allowed: No Default value: 0 ITF_TECHNO Text (50) Interfering technology Null column allowed: No Default value: V_BW Double Victim bandwidth (kHz) Null column allowed: No Default value: 0 7.2.4.7 Other Changes The following fields should be removed: • NUM_SECOND_ANTENNAS from the TplTransmitters table. 7.2.5 Changes in TD-SCDMA Documents 7.2.5.1 Transmitters Table The following fields should be added to the Transmitters table: Field Type Description Attributes NUM_RX_ANTENNAS Short Number of transmission antenna ports available at the transmitter Null column allowed: No Default value: 1 NUM_TX_ANTENNAS Short Number of reception antenna ports available at the transmitter Null column allowed: No Default value: 1 7.2.5.2 TplTransmitters Table The following fields should be added to the TplTransmitters table: Field Type Description Attributes NUM_RX_ANTENNAS Short Number of transmission antenna ports available at the transmitter Null column allowed: Yes NUM_TX_ANTENNAS Short Number of reception antenna ports available at the transmitter Null column allowed: Yes DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes REQ_UL_RUS Integer Required resource units in uplink Null column allowed: Yes REQ_DL_RUS Integer Required resource units in downlink Null column allowed: Yes 7.2.5.3 CDMACells Table The following field should be added to the CdmaCells table: Field CELL_IDENTITY 196 Type Integer Description Attributes Cell identity Null column allowed: Yes Default value: AT281_AM_E1 © Forsk 2009 Chapter 7: Compatibility Between Versions 2.7 and 2.8 DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes Default value: 0 UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes Default value: 0 7.2.5.4 CDMAEquipments Table The following field should be added to the CdmaCells table: Field Type Description Attributes MCJD_FACTOR Float Multi cell joint detection factor for extra cell UL interference cancellation Null column allowed: No Default value: 0 7.2.5.5 CodesRelativityClusters Table A new CodesRelativityClusters table should be added with the following structure: Field Type Description Attributes NAME Text (50) Name of the cluster of scrambling codes Null column allowed: No Default value: CODES_LIST Text (255) Coma separated list of codes belonging to the cluster Null column allowed: No Default value: 7.2.5.6 UMTSServices Table The following field should be added to the UMTSServices table: Field Type Description Attributes TYPE Short Type of service (0: circuit; 1: packet; 2: circuit over packet) Null column allowed: No Default value: 0 7.2.5.7 InterNetChProtect Table A new InterNetChProtect table should be added with the following structure: Field Type Description Attributes ICP Memo Inter-network channel protection = f(  MHz) Null column allowed: Yes Default value: ITF_BW Double Interfering bandwidth (kHz) Null column allowed: No Default value: 0 ITF_TECHNO Text (50) Interfering technology Null column allowed: No Default value: V_BW Double Victim bandwidth (kHz) Null column allowed: No Default value: 0 7.2.5.8 Other Changes The following fields should be removed: • • • • • BEST_BEARER_TABLE and CQI_TABLE from the HSDPABearerSelectTables table. CES_OVERHEAD_DL and CES_OVERHEAD_UL from the CDMAEquipments table. PACKET_SWITCHED from the UMTSServices table. RX_DIVERSITY_CFG from the Transmitters table. RX_DIVERSITY_CFG and NUM_SECOND_ANTENNAS from the TplTransmitters table. Remove the HSDPAQualityTables table. 7.2.6 Changes in WiMAX BWA Documents 7.2.6.1 Networks Table The following fields should be added to the Networks table in WiMAX 802.16e: Field Type Description Attributes DL_RATIO_FORMAT Short Format of the DL ratio parameter (0: Percentage; 1: Fraction) Null column allowed: Yes Default value: 0 DL_SYM_DURATIONS_NB Short Number of symbol durations in the downlink subframe (including the symbol duration used for the Preamble) Null column allowed: Yes Default value: 32 © Forsk 2009 AT281_AM_E1 197 Administrator Manual UL_SYM_DURATIONS_NB Short Number of symbol durations in the uplink subframe Null column allowed: Yes Default value: 15 CELL_SELECTION Short Serving cell selection method (0 = Min DL Load, 1 = Min UL Load, 2 = Random, 3 = Sequential) Null column allowed: Yes Default value: 2 PZ_SEL_CRITERION Short Permutation zone selection criterion (0 - Preamble C/N; 1 - Preamble C/(I+N)) Null column allowed: Yes Default value: 0 AMS_SEL_CRITERION Short AMS criterion (0 - Preamble C/N; 1 - Preamble C/(I+N)) Null column allowed: Yes Default value: 0 7.2.6.2 Schedulers Table The following fields should be added to the Schedulers table: Field Type Description Attributes BEARER_SELECTION Short Bearer Selection Criterion: 0 – Bearer Index; 1 – Peak MAC Throughput; 2 – Effective MAC Throughput Null column allowed: Yes Default value: 0 UL_BW_ALLOCATION Short UL Bandwidth Allocation Target: 0 – Full Bandwidth; 1 – Maintain Connection; 2 – Best Bearer Null column allowed: Yes Default value: 2 7.2.6.3 TplTransmitters Table The following fields should be added to the TplTransmitters table: Field Type Description Attributes CHANNEL_STATUS Short Channel allocation status (0 = Not allocated, 1 = Allocated, 2 = Locked) Null column allowed: Yes PI_STATUS Short Preamble index status (0 = unassigned; 1 = assigned; 2= Fixed) Null column allowed: Yes TX_TYPE Short Type of transmitter (0 = Normal; 1 = Interferer only) Null column allowed: Yes MAX_DL_LOAD Float Maximum traffic load allowed on downlink Null column allowed: Yes MAX_UL_LOAD Float Maximum traffic load allowed on uplink Null column allowed: Yes UL_MU_SM_GAIN Float Multi-user (collaborative) MIMO gain in uplink Null column allowed: Yes DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes CHANNEL_LIST Text(255) Channel numbers used by transmitters Null column allowed: Yes PI_LIST Text(255) Preamble indexes used by transmitters Null column allowed: Yes 7.2.6.4 WCells Table The following fields should be added to the WCells table: Field Type Description Attributes MAX_DL_LOAD Float Maximum traffic load allowed on downlink Null column allowed: Yes Default value: 100 MAX_UL_LOAD Float Maximum traffic load allowed on uplink Null column allowed: Yes Default value: 100 UL_MU_SM_GAIN Float Multi-user (collaborative) MIMO gain in uplink Null column allowed: Yes Default value: 2 DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes Default value: 0 UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes Default value: 0 RANK Short Zero based order used by scheduler for sequential cell selection Null column allowed: Yes Default value: 7.2.6.5 WMimoConfigs Table The following fields should be added to the WMIMOConfigs table: Field 198 Type Description Attributes BEARER_INDEX Short Index of the WiMAX bearer Null column allowed: Yes Default value: 1 MAX_BLER Float Maximum value of BLER for which the gains are applicable Null column allowed: Yes Default value: 1 AT281_AM_E1 © Forsk 2009 Chapter 7: Compatibility Between Versions 2.7 and 2.8 STTD_GAIN Float Gain that will be applied to the CINR in STTD mode (dB) Null column allowed: Yes Default value: 0 SUBCHANNEL_ALLOC_MO DE Short Subchannel allocation mode for WiMAX 802.16e only Null column allowed: Yes Default value: 8 WEQUIPMENT Text (50) Name of the equipment to which the MIMO gains correspond Null column allowed: No Default value: 7.2.6.6 InterNetChProtect Table A new InterNetChProtect table should be added with the following structure: Field Type Description Attributes ICP Memo Inter-network channel protection = f(  MHz) Null column allowed: Yes Default value: ITF_BW Double Interfering bandwidth (kHz) Null column allowed: No Default value: 0 ITF_TECHNO Text (50) Interfering technology Null column allowed: No Default value: V_BW Double Victim bandwidth (kHz) Null column allowed: No Default value: 0 7.2.6.7 Other Changes The following fields should be removed: • • 7.3 NAME, STTD_GAIN_DL, and STTD_GAIN_UL from the WMimoConfigs table. NUM_SECOND_ANTENNAS from the TplTransmitters table. Data Structure Changes for Activating Optional Features Some optional features require that a few data structure changes be made manually in the database. Atoll makes the optional features available to the user when it detects that the data structure has been correspondingly modified. Note: • If you use the Atoll Management Console to upgrade your 2.7 database to the version 2.8, and you have some data structure modifications in the 2.7 database which make some optional features available, these modofications will be erased during the upgrade. In order to keep the modifications, you have to make these changes in the 2.8 MS Access template (.mdb file) as well that the Atoll Management Console will use as reference for the upgrade. The following data structure changes have to be made in order to make the corresponding optional features available: 7.3.1 Optional Features in GSM GPRS EGPRS Documents 7.3.1.1 Intermodulation Interference Modelling 7.3.1.1.1 Transmitters Table The following fields should be added to the Transmitters table: Field Type Description Attributes I3_MSACTIVE Boolean Take into Account 3rd Order Intermodulation Generated by Mobiles Null column allowed: Yes Default value: True I3_LOSS Float Loss at the Base Station due to 3rd Order Intermodulation (dB) Null column allowed: Yes Default value: 80 I3_BSACTIVE Boolean Take into Account 3rd Order Intermodulation Generated by the Base Station Null column allowed: Yes Default value: True SPURIOUS_POWER Float Transmission Power for Spurious Emissions (dBm) Null column allowed: Yes Default value: -46 SPURIOUS_ACTIVE Boolean Take Spurious Emissions into Account Null column allowed: Yes Default value: True © Forsk 2009 AT281_AM_E1 199 Administrator Manual 7.3.1.1.2 Networks Table The following field should be added to the Networks table: Field I3_PROTECTION Type Float Description Attributes Protection Level Against 3rd Order Intermodulation at Mobiles (dB) Null column allowed: Yes Default value: -18 7.3.1.2 Frequency Diversity Gain Modelling 7.3.1.2.1 CodecQualityTables and EGPRSQuality Tables The following field should be added to the CodecQualityTables and EGPRSQuality tables: Field Type Description Attributes MAL_LENGTH Integer Mobile Allocation List Length Null column allowed: Yes Default value: 7.3.1.3 Additional Indoor Loss Modelling 7.3.1.3.1 FrequencyBands Table The following field should be added to the FrequencyBands table: Field Type Description Attributes ADD_INDOOR_LOSS Float Additional indoor loss per frequency band Total indoor loss = Clutter class indoor loss + ADD_INDOOR_LOSS Null column allowed: Yes Default value: 7.3.2 Optional Features in UMTS HSPA Documents 7.3.2.1 MBMS Modelling 7.3.2.1.1 CDMACells and TplTransmitters Tables The following fields should be added to the CDMACells and TplTransmitters tables: Field Type Description Attributes MBMS1_PWR Float Power dedicated to the 1st MBMS channel (1st SCCPCH used for MBMS) Null column allowed: Yes Default value: 33 MBMS2_PWR Float Power dedicated to the 2nd MBMS channel (2nd SCCPCH used for MBMS) Null column allowed: Yes Default value: 30 MBMS3_PWR Float Power dedicated to the 3rd MBMS channel (3rd SCCPCH used for MBMS) Null column allowed: Yes Default value: 27 MBMS4_PWR Float Power dedicated to the 4th MBMS channel (4th SCCPCH used for MBMS) Null column allowed: Yes Default value: MBMS5_PWR Float Power dedicated to the 5th MBMS channel (5th SCCPCH used for MBMS) Null column allowed: Yes Default value: MBMS6_PWR Float Power dedicated to the 6th MBMS channel (6th SCCPCH used for MBMS) Null column allowed: Yes Default value: MBMS1_RATE Float Data rate of the 1st MBMS channel (1st SCCPCH used for MBMS) Null column allowed: Yes Default value: 100 MBMS2_RATE Float Data rate of the 2nd MBMS channel (2nd SCCPCH used for MBMS) Null column allowed: Yes Default value: 64 MBMS3_RATE Float Data rate of the 3rd MBMS channel (3rd SCCPCH used for MBMS) Null column allowed: Yes Default value: 12.2 MBMS4_RATE Float Data rate of the 4th MBMS channel (4th SCCPCH used for MBMS) Null column allowed: Yes Default value: MBMS5_RATE Float Data rate of the 5th MBMS channel (5th SCCPCH used for MBMS) Null column allowed: Yes Default value: MBMS6_RATE Float Data rate of the 6th MBMS channel (6th SCCPCH used for MBMS) Null column allowed: Yes Default value: 7.3.2.1.2 UMTSMobility Table The following field should be added to the UMTSMobility table: 200 AT281_AM_E1 © Forsk 2009 Chapter 7: Compatibility Between Versions 2.7 and 2.8 Field MBMS_RATE Type Memo Description Attributes Set of values used to generate the quality threshold = f(rate) graph Null column allowed: Yes Default value: 12 6 64 6.5 100 7 150 7.5 200 7.8 384 8 7.3.2.2 Additional Indoor Loss Modelling 7.3.2.2.1 FrequencyBands Table The following field should be added to the FrequencyBands table: Field Type Description Attributes ADD_INDOOR_LOSS Float Additional indoor loss per frequency band Total indoor loss = Clutter class indoor loss + ADD_INDOOR_LOSS Null column allowed: Yes Default value: 7.3.3 Optional Features in CDMA2000 1xRTT 1xEV-DO Documents 7.3.3.1 Additional Indoor Loss Modelling 7.3.3.1.1 FrequencyBands Table The following field should be added to the FrequencyBands table: Field ADD_INDOOR_LOSS Type Description Attributes Float Additional indoor loss per frequency band Total indoor loss = Clutter class indoor loss + ADD_INDOOR_LOSS Null column allowed: Yes Default value: 7.3.4 Optional Features in TD-SCDMA Documents 7.3.4.1 MBMS Modelling 7.3.4.1.1 CDMACells and TplTransmitters Tables The following fields should be added to the CDMACells and TplTransmitters tables: Field Type Description Attributes MBMS1_PWR Float Power dedicated to the 1st MBMS channel (1st SCCPCH used for MBMS) Null column allowed: Yes Default value: 33 MBMS2_PWR Float Power dedicated to the 2nd MBMS channel (2nd SCCPCH used for MBMS) Null column allowed: Yes Default value: 30 MBMS3_PWR Float Power dedicated to the 3rd MBMS channel (3rd SCCPCH used for MBMS) Null column allowed: Yes Default value: 27 MBMS4_PWR Float Power dedicated to the 4th MBMS channel (4th SCCPCH used for MBMS) Null column allowed: Yes Default value: MBMS5_PWR Float Power dedicated to the 5th MBMS channel (5th SCCPCH used for MBMS) Null column allowed: Yes Default value: MBMS6_PWR Float Power dedicated to the 6th MBMS channel (6th SCCPCH used for MBMS) Null column allowed: Yes Default value: MBMS1_RATE Float Data rate of the 1st MBMS channel (1st SCCPCH used for MBMS) Null column allowed: Yes Default value: 100 MBMS2_RATE Float Data rate of the 2nd MBMS channel (2nd SCCPCH used for MBMS) Null column allowed: Yes Default value: 64 MBMS3_RATE Float Data rate of the 3rd MBMS channel (3rd SCCPCH used for MBMS) Null column allowed: Yes Default value: 12.2 MBMS4_RATE Float Data rate of the 4th MBMS channel (4th SCCPCH used for MBMS) Null column allowed: Yes Default value: MBMS5_RATE Float Data rate of the 5th MBMS channel (5th SCCPCH used for MBMS) Null column allowed: Yes Default value: MBMS6_RATE Float Data rate of the 6th MBMS channel (6th SCCPCH used for MBMS) Null column allowed: Yes Default value: MBMS1_TS Float Timeslot allocated to the 1st MBMS channel (1st SCCPCH used for MBMS) Null column allowed: Yes Default value: 4 © Forsk 2009 AT281_AM_E1 201 Administrator Manual MBMS2_TS Float Timeslot allocated to the 2nd MBMS channel (2nd SCCPCH used for MBMS) Null column allowed: Yes Default value: 5 MBMS3_TS Float Timeslot allocated to the 3rd MBMS channel (3rd SCCPCH used for MBMS) Null column allowed: Yes Default value: 6 MBMS4_TS Float Timeslot allocated to the 4th MBMS channel (4th SCCPCH used for MBMS) Null column allowed: Yes Default value: MBMS5_TS Float Timeslot allocated to the 5th MBMS channel (5th SCCPCH used for MBMS) Null column allowed: Yes Default value: MBMS6_TS Float Timeslot allocated to the 6th MBMS channel (6th SCCPCH used for MBMS) Null column allowed: Yes Default value: 7.3.4.1.2 UMTSMobility Table The following field should be added to the UMTSMobility table: Field Type Description Attributes MBMS_RATE Memo Set of values used to generate the quality threshold = f(rate) graph Null column allowed: Yes Default value: 12 6 64 6.5 100 7 150 7.5 200 7.8 384 8 7.3.4.2 Additional Indoor Loss Modelling 7.3.4.2.1 FrequencyBands Table The following field should be added to the FrequencyBands table: Field ADD_INDOOR_LOSS 202 Type Description Attributes Float Additional indoor loss per frequency band Total indoor loss = Clutter class indoor loss + ADD_INDOOR_LOSS Null column allowed: Yes Default value: AT281_AM_E1 © Forsk 2009 Chapter 8 Database Structure This chapter contains complete description of Atoll database structures for all types of Atoll documents. Atoll RF Planning & Optimisation Software Administrator Manual 204 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8 Database Structure 8.1 Overview All the technology modules available in Atoll (CDMA2000 1xRTT 1xEV-DO, UMTS HSPA, GSM GPRS EGPRS, TDSCDMA, WiMAX BWA, LTE, and Microwave Radio Links) are based on database templates. In order to be used, these templates can be located: • • Either in the Templates folder in the Atoll installation directory, or In any directory whose location path is defined using the Atoll Management Console for each group of users. Refer to "Managing Administration File Paths" on page 147 for details. Each template is an .mdb file and consists of a set of tables that model the radio network data structure. This chapter focuses on the structure of the tables composing the document templates and the relationships between these tables. The following table lists the types of fields used in Atoll templates and their corresponding lengths, and also presents the equivalent fields and lengths in different databases: Atoll Field Type Microsoft SQL Server Equivalent Oracle Equivalent Length Field Type Length Field Type Length Sybase Equivalent Field Type Length Microsoft Access Equivalent Float 4 FLOAT 32 real 4 real 4 Single Double 8 FLOAT 64 float 8 float 8 Double Integer 4 NUMBER 11 int 4 int 4 Long Integer Short 2 NUMBER 6 tinyint 1 tinyint 1 Integer Boolean 2 NUMBER 1 bit 1 bit 1 Yes/No Text Variable* VARCHAR2 Variable* varchar Variable* varchar Variable* Text* Memo Variable VARCHAR2 2000 varchar 4000 text Binary Variable LONG RAW image 16 image 16 OLE Object Memo * Lengths for these fields are specified in parentheses in the database structure tables. Notes: • The relationships in the database schema figures, presented in this chapter, are represented by arrows. These unidirectional arrows should be read as: = • In the tables listed below, primary keys are listed in bold and italic characters. • In the relationship diagrams, primary keys are in bold and underlined characters, and required fields are in bold characters. n or  1 Important: • © Forsk 2009 If you export the content of a .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. AT281_AM_E1 205 Administrator Manual 8.2 Microwave Radio Links Template Figure 8.1: on page 206 depicts the Microwave Radio Links database structure. Figure 8.1: Microwave Radio Links Template 206 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.2.1 Microwave Radio Links Tables The Microwave Radio Links project template has the following data structure. 8.2.1.1 PropagationModels Table This table contains propagation model description, formulas, and parameters. Field Type Description Attributes Data Binary Model specific parameters Null column allowed: Yes Description Text (255) User defined Null column allowed: Yes Name Text (50) Name of the propagation model Null column allowed: No Signature Text (40) Unique Global ID of last model update Null column allowed: No Type Text (50) ProgID of the model Null column allowed: No 8.2.1.2 CustomFields Table This table enables you to define default values for all the fields of all the tables in Atoll, including user-defined fields added to different tables. It also enables you to define choice lists, a caption, and a group name for user-defined fields. Field Type Description Attributes CHOICE_LIST Memo Choice list for the field Null column allowed: Yes COLUMN_NAME Text (50) Second part of the unique key. Field name Null column allowed: No DEFAULT_VALUE Text (50) Default value for the field Null column allowed: Yes TABLE_NAME Text (50) First part of the unique key. Table name Null column allowed: No CAPTION Text (50) Caption of the field (displayed instead of the name) Null column allowed: Yes GROUP_NAME Text (50) Name of the group to which that field belongs Null column allowed: Yes The default values defined in this table have priority over the internal predefined default values (hard-coded in Atoll or defined in the database table structure). In order for Atoll to correctly consider the new default values, note that: • • 8.2.1.3 If you use floating point values, ensure that all the users have the same decimal separator (comma or point). The field names are case sensitive. CoordSys Table This table stores descriptions of the projection coordinate system and database’s internal coordinate system (the display coordinate system used when creating a database). Field Type Description Attributes CODE Integer Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768) Null column allowed: No Default value: 0 DATUM_CODE Double DATUM_ROTX Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_ROTY Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_ROTZ Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_SCALE Double Parts per million (ppm) Null column allowed: Yes Default value: 0 DATUM_SHIFTX Double Meters Null column allowed: Yes Default value: 0 DATUM_SHIFTY Double Meters Null column allowed: Yes Default value: 0 DATUM_SHIFTZ Double Meters Null column allowed: Yes Default value: 0 ELLIPS_CODE Integer ELLIPS_RMAJOR Double © Forsk 2009 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Meters AT281_AM_E1 Null column allowed: Yes Default value: 0 207 Administrator Manual ELLIPS_RMINOR Double Meters Null column allowed: Yes Default value: 0 NAME Text (50) Coordinate system name Null column allowed: No Default value: PROJ_ANGLE Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_FALSE_EASTING Double Meters Null column allowed: Yes Default value: 0 PROJ_FALSE_NORTHING Double Meters Null column allowed: Yes Default value: 0 PROJ_FIRST_PARALLEL Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_LATITUDE_ORIGIN Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_LONGITUDE_ORIGIN Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_METHOD Short Undefined, NoProjection, Lambert1SP, Lambert2SP, Mercator, CassiniSoldner, TransMercator, TransMercatorSO, ObliqueStereographic, NewZealandMapGrid, HotineOM, LabordeOM, SwissObliqueCylindical, UTM Null column allowed: Yes Default value: 0 PROJ_SCALE_FACTOR Double PROJ_SECOND_PARALLEL Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_ZONE_NUMBER Integer Used with UTM Null column allowed: Yes Default value: 0 8.2.1.4 Null column allowed: Yes Default value: 0 Units Table This table stores the identification numbers of reception and transmission units, projection coordinate system specified in the .atl document and the database internal coordinate system. Field Type Description Attributes COORD_SYSTEM Integer Display coordinate system when creating database Null column allowed: Yes Default value: -1 PROJECTION Integer Projected coordinate system for geo data Null column allowed: Yes Default value: -1 Reception unit when creating database Null column allowed: No Default value: 0 Choice list: 0=dBm, 1=dbµV, 2=dbµV/m RECEPTION_UNIT Integer TRANSMISSION_UNIT Integer Transmission unit when creating database Null column allowed: No Default value: 0 Choice list: 0=dBm, 1=Watts, 2=kWatts GAIN_UNIT Integer Unit used for gains (dBd or dBi) Null column allowed: Yes Default value: 0 Choice list: 0= dBd, 1= dBi 8.2.1.5 Networks Table This table contains network-level properties and network-specific data. Field Type Description Attributes Null column allowed: No Default value: NAME Text (50) TECHNOLOGY Text (10) Name of the technology Null column allowed: No Default value: ‘FWA’ SYSTEM_ Text (50) Name of the system Null column allowed: No Default value: ‘MW’ DEFAULT_RESOLUTION Float Default calculation resolution Null column allowed: Yes Default value: 50 DEFAULT_MODEL Text (50) Default propagation model Null column allowed: Yes Default value: ‘Cost-Hata’ 208 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure SHARED_RESULTS_FOLDE Text (255) R DMAX 8.2.1.6 Float Shared results storage folder Null column allowed: Yes Default value: Maximum radius for a cell Null column allowed: Yes Default value: -1 Sites Table This table contains the physical properties of sites. Field Type Description Attributes ALTITUDE Float Real altitude Unit: m Null column allowed: Yes Default value: 0 COMMENT_ Text (255) Additional information on the site Null column allowed: Yes Default value: 0 LATITUDE Double Y coordinate Null column allowed: No Default value: 0 LONGITUDE Double X coordinate Null column allowed: No Default value: 0 NAME Text (50) Site name Null column allowed: No Default value: PYLON_HEIGHT Float Height of the pylon at site Null column allowed: Yes Default value: 50 SUPPORT_NATURE Short The nature of site. This field is for information only Null column allowed: Yes Default value: 0 8.2.1.7 Site List Management Tables This table manage site lists used to filter groups of sites and transmitters. 8.2.1.7.1 SitesListsNames Table Field Type Description Attributes NAME Text (50) Name of the list Null column allowed: No 8.2.1.7.2 SitesLists Table Field Type Description Attributes LIST_NAME Text (50) First part of the unique key. Name of the list Null column allowed: No SITE_NAME Text (50) Second part of the unique key. Name of the site Null column allowed: No 8.2.1.8 MWAntennas Table This table contains properties of Microwave antennas. Field Type Description Attributes NAME Text (50) Name of the antenna Null column allowed: No Default value: FREQ_BAND Text (50) Frequency band of the antenna Null column allowed: No Default value: MANUFACTURER Text (50) Manufacturer of the antenna Null column allowed: Yes Default value: COMMENT_ Text (255) Comments Null column allowed: Yes Default value: PATTERN Binary Antenna pattern diagrams Null column allowed: Yes Default value: GAIN Float Antenna gain Null column allowed: Yes Default value: 10 DIAMETER Float Diameter of the antenna Null column allowed: Yes Default value: 5 © Forsk 2009 AT281_AM_E1 209 Administrator Manual 8.2.1.9 MWBands Table This table describes the microwave frequency bands. Field Type Description Attributes NAME Text (50) Name of the frequency band Null column allowed: No Default value: FMIN Double Minimum frequency Null column allowed: Yes Default value: 100 FMAX Double Maximum frequency Null column allowed: Yes Default value: 200 COMMENT_ Text (255) Comments Null column allowed: Yes Default value: 8.2.1.10 MWBERCurves Table This table contains the bit error rate graphs used in microwave links computations. Field Type Description Attributes NAME Text (50) Name of the BER graph Null column allowed: No Default value: MODULATION Text (10) Modulation type Null column allowed: No Default value: “4-QAM” BER_CURVE Memo BER graph for the given modulation type Null column allowed: Yes Default value: ‘1’ 8.2.1.11 MWCompatibilities Table This table describes the compatibilities between equipment and antennas. Field Type Description Attributes ANTENNA Text (50) Name of the antenna Null column allowed: No Default value: EQUIPMENT Text (50) Name of the equipment Null column allowed: No Default value: COMMENT_ Text (255) Comments Null column allowed: Yes Default value: 8.2.1.12 MWCompatibilitiesGuides Table This table describes the compatibilities between wave guides and antennas. Field Type Description Attributes ANTENNA Text (50) Name of the antenna Null column allowed: No Default value: GUIDE Text (50) Name of the wave guide Null column allowed: No Default value: COMMENT_ Text (255) Comments Null column allowed: Yes Default value: 8.2.1.13 MWDefaultsCurves Table This table stores the default graphs of transmission, reception masks, etc. Field 210 Type Description Attributes CURVE_TYPE Short The type of curve Null column allowed: Yes Default value: 0 Choice list: 0: TX_MASK, 1: RX_MASK, 2: TtoI FREQ_BAND Text (50) Frequency band Null column allowed: No Default value: MANUFACTURER Text (50) Manufacturer Null column allowed: Yes Default value: MODULATION Text (15) Modulation used Null column allowed: Yes Default value: AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure NAME Text (50) Name of the curve Null column allowed: No Default value: RATE Float Rate (Mbps) Null column allowed: Yes Default value: 1 VALUES_ Memo Curve values Null column allowed: Yes Default value: BANDWIDTH Float Channel bandwidth Null column allowed: Yes Default value: 0 INTERFERED Text (50) 8.2.1.14 Null column allowed: Yes Default value: MWEPO Table This table contains the description of quality and availability performance objectives. Field Type Description Attributes NAME Text (50) EPO name Null column allowed: No Default value: EPO_TYPE Text (1) Performance objective type (Availability or Quality) Null column allowed: No Default value: REC_UIT Float ITU Recommendations Null column allowed: Yes Default value: 1 EPO_PARAM Text (5) Performance objective parameter (SESR, BBER, or ESR) Null column allowed: No Default value: LINK_CLASS Text (50) EPO Link class Null column allowed: No Default value: RATE_MIN Float Minimum bit rate (Mbps) Null column allowed: Yes Default value: RATE_MAX Float Maximum bit rate (Mbps) Null column allowed: Yes Default value: A Double Parameter used to calculate the EPO required: EPO = A * L+B Null column allowed: No Default value: 0 B Double Parameter used to calculate the EPO required: EPO = A * L+B Null column allowed: No Default value: 0 8.2.1.15 MWEPOLinkClass Table This table describes the EPO link classes. Field Type Description Attributes NAME Text (50) Name of the EPO class Null column allowed: No Default value: LINK_CLASS Text (5) Type of EPO link class Null column allowed: No Default value: LINK_SUBCLASS Text (5) Type of EPO link subclass Null column allowed: Yes Default value: LMIN Float Minimum length of the link for the EPO class Null column allowed: Yes Default value: LMAX Float Maximum length of the link for the EPO class Null column allowed: Yes Default value: COMMENT_ Text (255) Comments Null column allowed: Yes Default value: 8.2.1.16 MWEquipments Table This table contains the information related to microwave equipment. Field Type Description Attributes NAME Text (50) Name of the equipment Null column allowed: No Default value: FREQ_BAND Text (50) Frequency band of the equipment Null column allowed: No Default value: MANUFACTURER Text (50) Equipment manufacturer Null column allowed: Yes Default value: © Forsk 2009 AT281_AM_E1 211 Administrator Manual EQ_TYPE Text (50) Trunk type Null column allowed: Yes Default value: MODULATION Text (10) Modulation type Null column allowed: No Default value: “4-QAM” CAPACITY Integer Equipment capacity Null column allowed: No Default value: 1 POWER Float Power Null column allowed: Yes Default value: 30 ATPC_MAX Float Maximum ATPC Null column allowed: Yes Default value: 30 THRESHOLD_MAX Float Overflow threshold for the equipment Null column allowed: Yes Default value: -20 NF Float Noise Figure of the equipment Null column allowed: Yes Default value: 5 KN Float Kn parameter Null column allowed: Yes Default value: 0 WM Float Width minimum Null column allowed: Yes Default value: 10 WNM Float Width non-minimum Null column allowed: Yes Default value: 10 BM Float Depth minimum Null column allowed: Yes Default value: 30 BNM Float Depth non-minimum Null column allowed: Yes Default value: 30 XPIF Float Crosspolar Interference Factor Null column allowed: Yes Default value: 20 TX_LOSS_PHYS Float Physical transmitter loss Null column allowed: Yes Default value: 0 RX_LOSS_PHYS Float Physical receiver loss Null column allowed: Yes Default value: 0 MTBF Float Mean Time Before Failure Null column allowed: Yes Default value: 1000000 HSB_DELAY Float Hot Standby commutation delay time Null column allowed: Yes Default value: 0 RX_SENSITIVITY Memo BER - Sensitivity tables Null column allowed: Yes Default value: HSB Boolean True if the equipment supports hot stand by channels configuration. Null column allowed: No Default value: False INCR_PORT_RX_LOSS Float Incremental RX branching loss per port. Null column allowed: Yes Default value: 0 INCR_PORT_TX_LOSS Float Incremental TX branching loss per port Null column allowed: Yes Default value: 0 SYSTEM_CONFIG_M Short Second part of the system configuration which is like "n+m" Null column allowed: Yes Default value: 0 SYSTEM_CONFIG_N Short First part of a system configuration which is like "n+m" Null column allowed: Yes Default value: 1 RX_PORT_1 Float Receiving loss on port number 1 Null column allowed: Yes Default value: 0 RX_PORT_2 Float Receiving loss on port number 2 Null column allowed: Yes Default value: 0 RX_PORT_3 Float Receiving loss on port number 3 Null column allowed: Yes Default value: 0 RX_PORT_4 Float Receiving loss on port number 4 Null column allowed: Yes Default value: 0 RX_PORT_5 Float Receiving loss on port number 5 Null column allowed: Yes Default value: 0 RX_PORT_6 Float Receiving loss on port number 16 Null column allowed: Yes Default value: 0 RX_PORT_7 Float Receiving loss on port number 7 Null column allowed: Yes Default value: 0 RX_PORT_8 Float Receiving loss on port number 8 Null column allowed: Yes Default value: 0 212 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure RX_PORT_9 Float Receiving loss on port number 9 Null column allowed: Yes Default value: 0 RX_PORT_10 Float Receiving loss on port number 10 Null column allowed: Yes Default value: 0 RX_SELECTIVITY Memo Receiver filter selectivity Null column allowed: Yes Default value: TI_CURVE Memo T/I curve Null column allowed: Yes Default value: TX_MASK Memo Transmitter spectrum mask Null column allowed: Yes Default value: TX_PORT_1 Float Transmission loss on port number 1 Null column allowed: Yes Default value: 0 TX_PORT_2 Float Transmission loss on port number 2 Null column allowed: Yes Default value: 0 TX_PORT_3 Float Transmission loss on port number 3 Null column allowed: Yes Default value: 0 TX_PORT_4 Float Transmission loss on port number 4 Null column allowed: Yes Default value: 0 TX_PORT_5 Float Transmission loss on port number 5 Null column allowed: Yes Default value: 0 TX_PORT_6 Float Transmission loss on port number 6 Null column allowed: Yes Default value: 0 TX_PORT_7 Float Transmission loss on port number 7 Null column allowed: Yes Default value: 0 TX_PORT_8 Float Transmission loss on port number 8 Null column allowed: Yes Default value: 0 TX_PORT_9 Float Transmission loss on port number 9 Null column allowed: Yes Default value: 0 TX_PORT_10 Float Transmission loss on port number 10 Null column allowed: Yes Default value: 0 CI_MIN_BER3 Float Minimum C/I for BER = 1e-3 Null column allowed: Yes Default value: CI_MIN_BER6 Float Minimum C/I for BER = 1e-6 Null column allowed: Yes Default value: IFM Float Margin against interference Null column allowed: Yes Default value: 1 MANUF_CHANNEL_SPACIN G Float 8.2.1.17 Null column allowed: Yes Default value: MWGuides Table This table contains the description of microwave guides. Field Type Description Attributes NAME Text (50) Name of the guide Null column allowed: No Default value: FREQ_BAND Text (50) Frequency band of the guide Null column allowed: No Default value: GUIDE_TYPE Integer Type of guide Null column allowed: Yes Default value: 0 LOSS_PER_METER Float Linear loss Null column allowed: Yes Default value: 7 MANUFACTURER Text (50) Guide manufacturer Null column allowed: Yes Default value: 8.2.1.18 MWIrfs Table This table describes the IRFs for pairs of interferer and victim equipment. Field INTERFERED © Forsk 2009 Type Text (50) Description Attributes Interfered equipment Null column allowed: No Default value: AT281_AM_E1 213 Administrator Manual INTERFERER Text (50) Interferer equipment Null column allowed: No Default value: IRF Memo List of interference filtering protections Null column allowed: Yes Default value: Note: • The binary field, IRF, represents a list of pairs of values. Each pair consists of: - float deltaF: spacing in frequency - float protection: protection applied to this frequency 8.2.1.19 MWLinks Table This table contains the descriptions of microwave links. Field Type Description Attributes NAME Text (255) Name of the microwave link Null column allowed: No Default value: ACTIVE Boolean Link active or not Null column allowed: No Default value: True FREQ_BAND Text (50) Frequency band of the link Null column allowed: No Default value: FREQ_SUBBAND Text (50) Frequency subband of the link (site A) Null column allowed: Yes Default value: REPEATER1 Text (50) First repeater (P) Null column allowed: Yes Default value: REPEATER2 Text (50) Second repeater (Q) Null column allowed: Yes Default value: COMMENT_ Text (255) Comments Null column allowed: Yes Default value: PROFILE Binary Link profile Null column allowed: Yes Default value: SITE_A Text (50) Site of departure (A) Null column allowed: No Default value: EQUIPMENT_A Text (50) Equipment at site A Null column allowed: Yes Default value: ANTENNA_A Text (50) Main antenna at site A Null column allowed: Yes Default value: ANTENNA2_A Text (50) Secondary antenna at site A Null column allowed: Yes Default value: HEIGHT_A Float Height at site A Null column allowed: Yes Default value: 0 DOWNTILT_A Float Downtilt at site A Null column allowed: Yes Default value: 0 AZIMUTH_A Float Azimuth at site A Null column allowed: Yes Default value: 0 POLARIZATION_A Text (1) Polarization at site A Null column allowed: Yes Default value: ‘V’ DELTA_POW_A Float Gain or loss to maximum transmitter power at A Null column allowed: Yes Default value: 0 ATPC_A Float ATPC at site A Null column allowed: Yes Default value: 0 TXLOSS_ATT_A Float Transmission losses due to attenuators at A Null column allowed: Yes Default value: 0 TXLOSS_BRANCHING_A Float Transmission losses due to connectors and branching at A Null column allowed: Yes Default value: 0 RXLOSS_ATT_A Float Reception losses due to attenuators at A Null column allowed: Yes Default value: 0 CHANNELS_A Text (50) Channels used at site A Null column allowed: Yes Default value: PARITY_A Integer Parity of site A Null column allowed: Yes Default value: 0 214 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure DIVERSITY_A Boolean Diversity at site A Null column allowed: No Default value: False SEPARATION_A Float Diversity separation at site A Null column allowed: Yes Default value: 0 FREQ_A Double Frequency at site A Null column allowed: Yes Default value: -1 SITE_B Text (50) Site of arrival (B) Null column allowed: No Default value: EQUIPMENT_B Text (50) Equipment at site B Null column allowed: Yes Default value: ANTENNA_B Text (50) Main antenna at site B Null column allowed: Yes Default value: ANTENNA2_B Text (50) Secondary antenna at site B Null column allowed: Yes Default value: HEIGHT_B Float Height at site B Null column allowed: Yes Default value: 0 DOWNTILT_B Float Downtilt at site B Null column allowed: Yes Default value: 0 AZIMUTH_B Float Azimuth at site B Null column allowed: Yes Default value: 0 POLARIZATION_B Text (1) Polarization at site B Null column allowed: Yes Default value: ‘V’ DELTA_POW_B Float Gain or loss to maximum transmitter power at B Null column allowed: Yes Default value: 0 ATPC_B Float ATPC at site B Null column allowed: Yes Default value: 0 TXLOSS_ATT_B Float Transmission losses due to attenuators at B Null column allowed: Yes Default value: 0 TXLOSS_BRANCHING_B Float Transmission losses due to connectors and branching at B Null column allowed: Yes Default value: 0 RXLOSS_ATT_B Float Reception losses due to attenuators at B Null column allowed: Yes Default value: 0 CHANNELS_B Text (50) Channels used at site B Null column allowed: Yes Default value: PARITY_B Integer Parity of site B Null column allowed: Yes Default value: 0 DIVERSITY_B Boolean Diversity at site B Null column allowed: No Default value: False SEPARATION_B Float Diversity separation at site B Null column allowed: Yes Default value: 0 FREQ_B Double Frequency at site B Null column allowed: Yes Default value: -1 GUIDE1 Text (50) Waveguide when A transmitting Null column allowed: Yes Default value: GUIDE2 Text (50) Waveguide when B receiving Null column allowed: Yes Default value: GUIDE3 Text (50) Waveguide when B transmitting Null column allowed: Yes Default value: GUIDE4 Text (50) Waveguide when A receiving Null column allowed: Yes Default value: GUIDE_LG1 Float Length of GUIDE1 Null column allowed: Yes Default value: 0 GUIDE_LG2 Float Length of GUIDE2 Null column allowed: Yes Default value: 0 GUIDE_LG3 Float Length of GUIDE3 Null column allowed: Yes Default value: 0 GUIDE_LG4 Float Length of GUIDE4 Null column allowed: Yes Default value: 0 PROPAG_MODEL Text (50) Propagation model Null column allowed: Yes Default value: PL Float © Forsk 2009 Null column allowed: Yes Default value: 10 AT281_AM_E1 215 Administrator Manual VAPOR Float Vapour density (g/cu. m) Null column allowed: Yes Default value: 10 TEMPERATURE Float Temperature Null column allowed: Yes Default value: ENVTYPE Integer Type of environment Null column allowed: Yes Default value: 0 R001 Float Rain intensity exceeded for 0.01% of time (mm/hr) Null column allowed: Yes Default value: 22 XPIC Boolean Crosspolar Interference Compensation (site A) Null column allowed: No Default value: False EPO_CLASS Text (50) EPO Class for the link Null column allowed: Yes Default value: BER Double Bit Error Rate Null column allowed: Yes Default value: 1e-3 MTTR Float Minimum Time To Repair Null column allowed: Yes Default value: 0 BER2 Double Second Bit Error Ratio (i.e. 1e-6) Null column allowed: Yes Default value: 1e-6 C_FACTOR Float Vigants-Barnett method: C factor Null column allowed: Yes Default value: 1 CLIMATE_ZONE Short Rain Climate Zone Null column allowed: Yes Default value: 4 DX_A Float X coordinate relative to the site A position Null column allowed: Yes Default value: 0 DX_B Float X coordinate relative to the site B position Null column allowed: Yes Default value: 0 DY_A Float Y coordinate relative to the site A position Null column allowed: Yes Default value: 0 DY_B Float Y coordinate relative to the site B position Null column allowed: Yes Default value: 0 KQ_FACTOR Float KQ reliability method: KQ Factor Null column allowed: Yes Default value: SHIELDING_FACTOR_A Float Additional loss due to a natural or artificial obstacle in the vicinity of the antenna A Null column allowed: Yes Default value: 0 SHIELDING_FACTOR_B Float Additional loss due to a natural or artificial obstacle in the vicinity of the antenna B Null column allowed: Yes Default value: 0 GUIDE_USE1 Integer Use of Guide 1 on site A Null column allowed: Yes Default value: 0 GUIDE_USE2 Integer Use of Guide 2 on site B Null column allowed: Yes Default value: 1 GUIDE_USE3 Integer Use of Guide 1 on site B Null column allowed: Yes Default value: 0 GUIDE_USE4 Integer Use of Guide 2 on site A Null column allowed: Yes Default value: 1 FREQ_SUBBAND_B Text (50) Frequency subband of the link (site B) Null column allowed: Yes Default value: XPIC_B Boolean Crosspolar Interference Compensation (site B) Null column allowed: No Default value: False ATMOS_PRESSURE Float Atmospheric pressure in mbar Null column allowed: Yes Default value: 1013 GEOCLIM_FACTOR Double Null column allowed: Yes Default value: RAIN_HEIGHT Float Null column allowed: Yes Default value: REFRACTIVITY Float Null column allowed: Yes Default value: PROPAG_IMODEL Text (50) 216 Propagation model used for interference calculation AT281_AM_E1 Null column allowed: Yes Default value: © Forsk 2009 Chapter 8: Database Structure 8.2.1.20 MWLinksTypes Table This table describes the types of microwave links trunks. Field Type Description Attributes NAME Text (50) Name of the link type Null column allowed: No Default value: SDH Boolean Type of digital Hierarchy (SDH or PDH) Null column allowed: No Default value: True (=SDH) RATE Float Maximum bit rate (Mbps) Null column allowed: Yes Default value: 2 SUP_RATE Float Supported bit rate (Mbps) Null column allowed: Yes Default value: 2 BLOCK_SIZE Integer Size of transmitted blocks (number of bits per block) Null column allowed: Yes Default value: 2000 BER_SES Double BERses Null column allowed: Yes Default value: 0 8.2.1.21 MWManufacturers Table This table contains the list of microwave equipment manufacturers. Field Type Description Attributes NAME Text (50) Name of the manufacturer Null column allowed: No Default value: COMMENT_ Text (255) Comments Null column allowed: Yes Default value: 8.2.1.22 MWMultiHops Table This table contains the description of multihop links. Field Type Description Attributes NAME Text (50) Name of the multihop link Null column allowed: No Default value: COMMENT_ Text (255) Comments Null column allowed: Yes Default value: EPO_CLASS Text (50) Name of the EPO class Null column allowed: Yes Default value: 8.2.1.23 MWMultiHopsLinks Table This table describes the mapping and order of the links belonging to different multihops. Field Type Description Attributes MULTI_HOP Text (50) Name of the multihop link Null column allowed: No Default value: LINK Text (255) Name of the link belonging to the multihop Null column allowed: No Default value: ORDER_ Short Order of the links in the multihop Null column allowed: Yes Default value: 0 8.2.1.24 MWRepeaters Table This table models microwave repeaters and stores their properties. Field Type Description Attributes NAME Text (50) Name of the repeater Null column allowed: No Default value: FREQ_BAND Text (50) Frequency band of the repeater Null column allowed: No Default value: SITE Text (50) Name of the repeater’s site Null column allowed: No Default value: HEIGHT Float Height of the repeater Null column allowed: Yes Default value: 30 © Forsk 2009 AT281_AM_E1 217 Administrator Manual AZIMUTH_A Float Azimuth of the repeater in the direction of A Null column allowed: Yes Default value: 0 AZIMUTH_B Float Azimuth of the repeater in the direction of B Null column allowed: Yes Default value: 0 REPEATER_TYPE Short Type of the repeater (Reflector or Back-to-back antennas) Null column allowed: Yes Default value: 0 (Reflector) SURFACE Float Repeater surface area (sq. m) Null column allowed: Yes Default value: 5 ANTENNA Text (50) Repeater antenna Null column allowed: Yes Default value: DX Float X coordinate relative to site position Null column allowed: Yes Default value: 0 DY Float Y coordinate relative to site position Null column allowed: Yes Default value: 0 ANTENNA_2 Text (50) Used if type is Back to Back Antenna (from the antenna table) (point to B) Null column allowed: Yes Default value: GUIDE Text (50) Used if type is Back to Back Antenna (from the guide table) Null column allowed: Yes Default value: HEIGHT_2 Float Height (pointed to B) Null column allowed: Yes Default value: 30 LG_GUIDE Float Guide length Null column allowed: Yes Default value: 0 REVERSE_POLAR Boolean 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) Null column allowed: No Default value: False TILT_A Float Tilt of the repeater antenna in the direction of A Null column allowed: Yes Default value: TILT_B Float Tilt of the repeater antenna in the direction of B Null column allowed: Yes Default value: 8.2.1.25 MWSubbands Table This table models frequency subbands. Field Type Description Attributes NAME Text (50) Name of the subband Null column allowed: No Default value: FREQ_BAND Text (50) Frequency band Null column allowed: Yes Default value: F0 Double Central frequency Null column allowed: Yes Default value: 4700 KL Double Lower half-band shift Null column allowed: Yes Default value: -310 KU Double Upper half-band shift Null column allowed: Yes Default value: 2 XS Double Inter-channel space Null column allowed: Yes Default value: 28 N_MIN Integer First channel number Null column allowed: Yes Default value: 1 N_MAX Integer Last channel number Null column allowed: Yes Default value: 10 STEP Integer Step size between first and last channel number Null column allowed: Yes Default value: 1 EXCLUDE_L Text (250) Excluded channels in the lower half-band Null column allowed: Yes Default value: EXCLUDE_U Text (250) Excluded channels in the upper half-band Null column allowed: Yes Default value: REC_UIT Text (255) ITU Recommendations Null column allowed: Yes Default value: 8.2.1.26 MWTplLinks Table This table contains the microwave links templates. 218 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure Field Type Description Attributes NAME Text (120) Name of the microwave link template Null column allowed: No Default value: FREQ_BAND Text (50) Frequency band of the link Null column allowed: No Default value: EQUIPMENT_A Text (50) Equipment at site A Null column allowed: Yes Default value: ANTENNA_A Text (50) Main antenna at site A Null column allowed: Yes Default value: HEIGHT_A Float Height at site A Null column allowed: Yes Default value: 0 TXLOSS_ATT_A Float Transmission losses due to attenuators at A Null column allowed: Yes Default value: 0 TXLOSS_BRANCHING_A Float Transmission losses due to connectors and branching at A Null column allowed: Yes Default value: 0 RXLOSS_ATT_A Float Reception losses due to attenuators at A Null column allowed: Yes Default value: 0 EQUIPMENT_B Text (50) Equipment at site B Null column allowed: Yes Default value: ANTENNA_B Text (50) Main antenna at site B Null column allowed: Yes Default value: HEIGHT_B Float Height at site B Null column allowed: Yes Default value: 0 TXLOSS_ATT_B Float Transmission losses due to attenuators at B Null column allowed: Yes Default value: 0 TXLOSS_BRANCHING_B Float Transmission losses due to connectors and branching at B Null column allowed: Yes Default value: 0 RXLOSS_ATT_B Float Reception losses due to attenuators at B Null column allowed: Yes Default value: 0 GUIDE1 Text (50) Waveguide when A transmitting Null column allowed: Yes Default value: GUIDE2 Text (50) Waveguide when B receiving Null column allowed: Yes Default value: GUIDE3 Text (50) Waveguide when B transmitting Null column allowed: Yes Default value: GUIDE4 Text (50) Waveguide when A receiving Null column allowed: Yes Default value: GUIDE_LG1 Float Length of GUIDE1 Null column allowed: Yes Default value: 0 GUIDE_LG2 Float Length of GUIDE2 Null column allowed: Yes Default value: 0 GUIDE_LG3 Float Length of GUIDE3 Null column allowed: Yes Default value: 0 GUIDE_LG4 Float Length of GUIDE4 Null column allowed: Yes Default value: 0 PL Float VAPOR Float Vapour density (g/cu. m) Null column allowed: Yes Default value: 10 TEMPERATURE Float Temperature Null column allowed: Yes Default value: ENVTYPE Integer Type of environment Null column allowed: Yes Default value: 0 R001 Float Rain intensity exceeded for 0.01% of time (mm/hr) Null column allowed: Yes Default value: 22 EPO_CLASS Text (50) EPO Class for the link Null column allowed: Yes Default value: BER Double Bit Error Rate Null column allowed: Yes Default value: 1e-3 MTTR Float Minimum Time To Repair Null column allowed: Yes Default value: 0 © Forsk 2009 Null column allowed: Yes Default value: 10 AT281_AM_E1 219 Administrator Manual PROPAG_MODEL Text (50) Propagation model Null column allowed: Yes Default value: BER2 Double Second Bit Error Ratio (i.e. 1e-6) Null column allowed: Yes Default value: 1e-6 C_FACTOR Float Vigants-Barnett method: C factor Null column allowed: Yes Default value: 1 CLIMATE_ZONE Short Rain Climate Zone Null column allowed: Yes Default value: 4 KQ_FACTOR Float KQ reliability method: KQ Factor Null column allowed: Yes Default value: POLARIZATION_A Text (1) Polarisation of the descending link 'siteA - site B' (the site A and site B are respectively transmitter and receiver) Null column allowed: Yes Default value: ‘V’ POLARIZATION_B Text (1) Polarisation of the ascending link 'siteA-site B' (the site A and site B are respectively receiver and transmitter) Null column allowed: Yes Default value: ‘V’ GUIDE_USE1 Integer Use of Guide 1 on site A Null column allowed: Yes Default value: 0 GUIDE_USE2 Integer Use of Guide 2 on site B Null column allowed: Yes Default value: 1 GUIDE_USE3 Integer Use of Guide 1 on site B Null column allowed: Yes Default value: 0 GUIDE_USE4 Integer Use of Guide 2 on site A Null column allowed: Yes Default value: 1 ATMOS_PRESSURE Float Atmospheric pressure in mbar Null column allowed: Yes Default value: 1013 RAIN_HEIGHT Float Null column allowed: Yes Default value: REFRACTIVITY Float Null column allowed: Yes Default value: PROPAG_IMODEL Text (50) 8.2.1.27 Propagation model used for interference calculation Null column allowed: Yes Default value: MWHubs Table This table contains the properties modelling microwave link hubs. Field Type Description Attributes ANTENNA Text (50) Name of the (shared) Antenna Null column allowed: Yes Default value: AZIMUTH Float Azimuth of the Antenna Null column allowed: Yes Default value: 0 COMMENT_ Text (255) Comments Null column allowed: Yes Default value: DOWNTILT Float Tilt of the Antenna Null column allowed: Yes Default value: 0 FREQ_BAND Text (50) Name of the frequency band Null column allowed: No Default value: HEIGHT Float Height of the Antenna Null column allowed: Yes Default value: 30 NAME Text (50) Name of the Hub Null column allowed: No Default value: PMP_TYPE Short Type of the PMP: TDA or FDA Null column allowed: Yes Default value: 0 SITE Text (50) Name of the site Null column allowed: No Default value: 8.2.1.28 MWPMP Table This table stores the relations between hubs and microwave links in a point-to-multipoint network. Field 220 Type Description Attributes HUB Text (50) Name of the hub Null column allowed: No Default value: LINK Text (100) Name of the link Null column allowed: No Default value: AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.2.1.29 MWPorts Table This table contains the properties of microwave ports. Field Type Description Attributes CHANNEL Short Channel Number Null column allowed: No Default value: 0 HSB Boolean Flag to set a channel as a hot standby channel Null column allowed: No Default value: LINK Text (255) Name of the link Null column allowed: No Default value: POLARIZATION Text (1) Signal polarization of this channel Null column allowed: No Default value: ‘H’ RX_ATTENUATION Float Rx attenuation loss for this channel Null column allowed: Yes Default value: 1 RX_PORT Short Number of the port on the RX equipment where the channel is connected Null column allowed: Yes Default value: 1 TX_ATTENUATION Float Tx attenuation loss for this channel Null column allowed: Yes Default value: 0 TX_PORT Short Number of the port on the TX equipment where the channel is connected Null column allowed: Yes Default value: 1 WAY Short Way of the link AB or BA Null column allowed: No Default value: 0 STATUS Short Status of the microwave port (0 = main,1 = standby, or 2 = diversity) Null column allowed: No Default value: 0 © Forsk 2009 AT281_AM_E1 221 Administrator Manual 8.3 GSM GPRS EGPRS Template Figure 8.2: on page 222, Figure 8.3: on page 223, and Figure 8.4: on page 224 depict the GSM GPRS EGPRS database structure. Figure 8.2: GSM GPRS EGPRS Template - 1 222 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure Figure 8.3: GSM GPRS EGPRS Template - 2 © Forsk 2009 AT281_AM_E1 223 Administrator Manual Figure 8.4: GSM GPRS EGPRS Template - 3 224 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.3.1 GSM GPRS EGPRS Tables The GSM GPRS EGPRS project template has the following data structure. 8.3.1.1 PropagationModels Table This table contains propagation model description, formulas, and parameters. Field Type Description Attributes Data Binary Model specific parameters Null column allowed: Yes Description Text (255) User defined Null column allowed: Yes Name Text (50) Name of the propagation model Null column allowed: No Signature Text (40) Unique Global ID of last model update Null column allowed: No Type Text (50) ProgID of the model Null column allowed: No 8.3.1.2 CustomFields Table This table enables you to define default values for all the fields of all the tables in Atoll, including user-defined fields added to different tables. It also enables you to define choice lists, a caption, and a group name for user-defined fields. Field Type Description Attributes CHOICE_LIST Memo Choice list for the field Null column allowed: Yes COLUMN_NAME Text (50) Second part of the unique key. Field name Null column allowed: No DEFAULT_VALUE Text (50) Default value for the field Null column allowed: Yes TABLE_NAME Text (50) First part of the unique key. Table name Null column allowed: No CAPTION Text (50) Caption of the field (displayed instead of the name) Null column allowed: Yes GROUP_NAME Text (50) Name of the group to which that field belongs Null column allowed: Yes The default values defined in this table have priority over the internal predefined default values (hard-coded in Atoll or defined in the database table structure). In order for Atoll to correctly consider the new default values, note that: • • 8.3.1.3 If you use floating point values, ensure that all the users have the same decimal separator (comma or point). The field names are case sensitive. CoordSys Table This table stores descriptions of the projection coordinate system and database’s internal coordinate system (the display coordinate system used when creating a database). Field Type Description Attributes CODE Integer Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768) Null column allowed: No Default value: 0 DATUM_CODE Double DATUM_ROTX Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_ROTY Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_ROTZ Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_SCALE Double Parts per million (ppm) Null column allowed: Yes Default value: 0 DATUM_SHIFTX Double Meters Null column allowed: Yes Default value: 0 DATUM_SHIFTY Double Meters Null column allowed: Yes Default value: 0 DATUM_SHIFTZ Double Meters Null column allowed: Yes Default value: 0 ELLIPS_CODE Integer ELLIPS_RMAJOR Double © Forsk 2009 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Meters AT281_AM_E1 Null column allowed: Yes Default value: 0 225 Administrator Manual ELLIPS_RMINOR Double Meters Null column allowed: Yes Default value: 0 NAME Text (50) Coordinate system name Null column allowed: No Default value: PROJ_ANGLE Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_FALSE_EASTING Double Meters Null column allowed: Yes Default value: 0 PROJ_FALSE_NORTHING Double Meters Null column allowed: Yes Default value: 0 PROJ_FIRST_PARALLEL Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_LATITUDE_ORIGIN Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_LONGITUDE_ORIGIN Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_METHOD Short Undefined, NoProjection, Lambert1SP, Lambert2SP, Mercator, CassiniSoldner, TransMercator, TransMercatorSO, ObliqueStereographic, NewZealandMapGrid, HotineOM, LabordeOM, SwissObliqueCylindical, UTM Null column allowed: Yes Default value: 0 PROJ_SCALE_FACTOR Double PROJ_SECOND_PARALLEL Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_ZONE_NUMBER Integer Used with UTM Null column allowed: Yes Default value: 0 8.3.1.4 Null column allowed: Yes Default value: 0 Units Table This table stores the identification numbers of reception and transmission units, projection coordinate system specified in the .atl document and the database internal coordinate system, and internal BSIC format. Field Type Description Attributes COORD_SYSTEM Integer Display coordinate system when creating database Null column allowed: Yes Default value: -1 PROJECTION Integer Projected coordinate system for geo data Null column allowed: Yes Default value: -1 Reception unit when creating database Null column allowed: No Default value: 0 Choice list: 0=dBm, 1=dbµV, 2=dbµV/m Transmission unit when creating database Null column allowed: No Default value: 0 Choice list: 0=dBm, 1=Watts, 2=kWatts RECEPTION_UNIT TRANSMISSION_UNIT Integer Integer BSIC_FORMAT Integer BSIC format Null column allowed: Yes Default value: 1 Choice list: 0=Decimal, 1=Octal GAIN_UNIT Integer Unit used for gains (dBd or dBi) Null column allowed: Yes Default value: 0 Choice list: 0= dBd, 1= dBi 8.3.1.5 Networks Table This table contains network-level properties and network-specific data. Field 226 Type Description Attributes Null column allowed: No Default value: NAME Text (50) TECHNOLOGY Text (10) Name of the technology Null column allowed: No Default value: ‘TDMA’ SYSTEM_ Text (50) Name of the system Null column allowed: No Default value: ‘GSM’ AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure DEFAULT_RESOLUTION Float Default calculation resolution Null column allowed: No Default value: 50 DEFAULT_MODEL Text (50) Default propagation model Null column allowed: No Default value: Shared results storage folder Null column allowed: Yes Default value: SHARED_RESULTS_FOLDE Text (255) R DMAX Float Maximum radius for a cell Null column allowed: No Default value: -1 INTERFERERS_RX_THRES H Float Interferers' reception threshold Null column allowed: Yes Default value: -130 THERMAL_NOISE Float Thermal noise Null column allowed: Yes Default value: -121 8.3.1.6 Sites Table This table contains the physical properties of sites. Field Type Description Attributes ALTITUDE Float Real altitude Unit: m Null column allowed: Yes Default value: COMMENT_ Text (255) Additional information on the site Null column allowed: Yes Default value: LATITUDE Double Y coordinate Null column allowed: No Default value: 0 LONGITUDE Double X coordinate Null column allowed: No Default value: 0 NAME Text (50) Site name Null column allowed: No Default value: PYLON_HEIGHT Float Height of the pylon at site Null column allowed: Yes Default value: 50 SUPPORT_NATURE Short The nature of site. This field is for information only Null column allowed: Yes Default value: 0 8.3.1.7 Site List Management Tables These tables manage site lists used to filter groups of sites and transmitters. 8.3.1.7.1 SitesListsNames Table Field Type Description Attributes NAME Text (50) Name of the list Null column allowed: No 8.3.1.7.2 SitesLists Table Field Type Description Attributes LIST_NAME Text (50) First part of the unique key. Name of the list Null column allowed: No SITE_NAME Text (50) Second part of the unique key. Name of the site Null column allowed: No 8.3.1.8 Transmitter List Management Tables These tables manage transmitter lists used to filter groups of transmitters. 8.3.1.8.1 TxsListsNames Table Field Type Description Attributes NAME Text (50) Name of the transmitter list Null column allowed: No Description Attributes 8.3.1.8.2 TxsLists Table Field Type LIST_NAME Text (50) First part of the unique key. Name of the list. Null column allowed: No TX_NAME Text (50) Second part of the unique key. Name of the transmitter. Null column allowed: No © Forsk 2009 AT281_AM_E1 227 Administrator Manual 8.3.1.9 Antennas Table This table contains the description of antennas. Field Type Description Attributes Beamwidth Float Antenna beamwidth Null column allowed: Yes Default value: COMMENT_ Text (255) Additional information about antenna Null column allowed: Yes Default value: CONSTRUCTOR Text (50) Antenna manufacturer name Null column allowed: Yes Default value: DIAGRAM Binary Antenna horizontal and vertical patterns Null column allowed: Yes Default value: ELECTRICAL_TILT Float Antenna electrical tilt (for information) Null column allowed: Yes Default value: FMax Double Maximum operating frequency of the antennas Unit: MHz Null column allowed: Yes Default value: FMin Double Minimum operating frequency of the antenna Unit: MHz Null column allowed: Yes Default value: GAIN Float Antenna isotropic gain Unit: dBi Null column allowed: No Default value: 0 NAME Text (50) Name of antenna Null column allowed: No Default value: Note: • An antenna pattern described in a text format may be converted to a binary format using a converter. The format of the binary field, DIAGRAM, is detailed below. Each antenna is described by a header and a list of value pairs. - The header is defined as follows: int (32 bits) flag = 0 for omni diagrams, 1 for non-omni short (16 bits) num = number of diagrams (0,1,2,3,4) short (16 bits) siz0 = size of the first diagram (horizontal copolar section (elevation=0°)) short (16 bits) siz1 = size of second (vertical copolar section (azimuth=0°)) short (16 bits) siz2 = size of third (horizontal contrapolar) short (16 bits) siz3 = size of fourth (vertical contrapolar) short (16 bits) prec = precision of the following angle values (=100) - Then follows the content of each of the defined diagrams ("sizx" with a value not equal to zero). - One diagram consists of a list of value pairs: one unsigned short value, the angle in degrees (multiplied by 100), so 577 means 5 degrees 77 hundredths of a degree. one short value representing the loss in dB for the given angle. - if siz2 = 5, there will be 5 pairs of values describing the third diagram. - All the lists of pairs are concatenated without a separator. 8.3.1.10 SecondaryAntennas Table This table is used to model additional antennas installed on transmitters. Field 228 Type Description Attributes ANTENNA Text (50) Name of the antenna installed on the transmitter Null column allowed: No Default value: AZIMUT Float Second part of the unique key. Azimuth of the antenna Null column allowed: No Default value: 0 REDT Float Remote electrical tilt for secondary antenna Null column allowed: Yes Default value: 0 PERCENT_POWER Float Percentage of power dedicated to the secondary antenna Null column allowed: No Default value: 0 TILT Float Mechanical downtilt of the secondary antenna Null column allowed: No Default value: 0 TX_ID Text (50) First part of the unique key. Transmitter name Null column allowed: No Default value: AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.3.1.11 Antenna List Management Tables These tables manage antenna lists. 8.3.1.12 AntennasListsNames Table Field Type Description Attributes NAME Text (50) Name of the list Null column allowed: No 8.3.1.13 AntennasLists Table Field Type Description Attributes ANTENNA_NAME Text (50) First part of the unique key. Name of the list. Null column allowed: No LIST_NAME Text (50) Second part of the unique key. Name of the antenna. Null column allowed: No 8.3.1.14 FrequencyBands Table This table contains the description of frequency band(s). Field Type Description Attributes NAME Text (20) Name of the frequency band Null column allowed: No Default value: CHANNEL_WIDTH Double Width of each physical channel composing the frequency band Unit: kHz Null column allowed: No Default value: 1 EXCLUDED_CHANNELS Text (255) Physical channels you do not want to allocate Null column allowed: Yes Default value: FIRST_CHANNEL Integer Number of the first physical channel available in the network Null column allowed: No Default value: 0 FREQUENCY Double Frequency of the downlink carrier Unit: MHz Null column allowed: No Default value: 1000 LAST_CHANNEL Integer Number of the last physical channel available in the network Null column allowed: No Default value: 0 MULTIPLEX_FACTOR Integer Number of logical channels composing a physical channel Null column allowed: No Default value: 1 MAX_CHANNEL_NUM Integer Extended Channel Offset (used for band E-GSM) Null column allowed: Yes Default value: 8.3.1.15 Receivers Table This table models the receiver used for raster coverage predictions. Field Type Description Attributes ADJ_CHANNEL_PROT Float Protection against interfering signals from adjacent channels. Null column allowed: No Default value: 18 ANTENNA Text (50) Receiver antenna name (if empty an omni antenna is used) Null column allowed: Yes Default value: HEIGHT Float Height of the receiver Null column allowed: No Default value: 2 LOSS Float Losses due to receiver radio equipment (up and downlink) Null column allowed: No Default value: 0 NAME Text (50) Receiver name Null column allowed: No Default value: 8.3.1.16 Equipment Management Tables These tables model TMA, feeders, and BTS equipment properties. 8.3.1.16.1 TMAEquipments Table Field DL_LOSSES © Forsk 2009 Type Float Description Attributes Downlink losses of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 AT281_AM_E1 229 Administrator Manual NAME Text (50) Name of Tower Mounted Amplifier Null column allowed: No Default value: NOISE_FIGURE Float Noise figure of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 UL_GAIN Float Uplink gain of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 8.3.1.16.2 FeederEquipments Table Field Type Description Attributes CONNECTOR_LOSSES_UL Float Feeder connector losses in uplink Null column allowed: Yes Default value: 0 CONNECTOR_LOSSES_DL Float Feeder connector losses in downlink Null column allowed: Yes Default value: 0 LOSS_PER_METER Float Feeder loss per meter Null column allowed: Yes Default value: 0 NAME Text (50) Name of Feeder Null column allowed: No Default value: 8.3.1.16.3 BTSEquipments Table Field Type Description Attributes NAME Text (50) Name of Base Station Equipment Null column allowed: No Default value: NOISE_FIGURE Float Noise figure of Base Station Null column allowed: Yes Default value: 0 CONFIG_DL_LOSSES Float Downlink losses due to the configuration of the BTS (duplexer and/or combiner) Null column allowed: Yes Default value: 0 CONFIG_UL_LOSSES Float Uplink losses due to the configuration of the BTS (duplexer and/or combiner) Null column allowed: Yes Default value: 0 RHO_FACTOR Short Rho factor to model self generated interference (100%=ideal) Null column allowed: Yes Default value: 100 8.3.1.17 Neighbour Management Tables 8.3.1.17.1 Neighbours Table This table stores neighbourhood relationships between transmitters of the same .atl document (intra-technology neighbours). Field Type Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: 1 NEIGHBOUR Text (50) Second part of the unique key. List of neighbours Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: REASON Integer Reason of the neighbourhood Null column allowed: Yes Default value: 0 (Manual) Choice list: Manual, Forced, Co-site, Adjacent, Symmetric, Distance, Coverage TRANSMITTER Text (50) First part of the unique key. Transmitters or cells Null column allowed: No Default value: TYPE Text (50) Type of the neighbourhood (handover, measurement…) Null column allowed: Yes Default value: 8.3.1.17.2 NeighboursExt Table This table stores neighbourhood relationships between transmitters/cells of different .atl documents (inter-technology neighbours). Field IMPORTANCE 230 Type Float Description Attributes Handover importance (for AFP use) Null column allowed: Yes Default value: AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure NEIGHBOUR Text (50) Second part of the unique key. List of neighbours from another project Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: REASON Integer Reason of the neighbourhood Null column allowed: Yes Default value: 0 (Manual) Choice list: Manual, Forced, Co-site, Adjacent, Symmetric, Distance, Coverage TRANSMITTER Text (50) First part of the unique key. Transmitters or cells Null column allowed: No Default value: TYPE Text (50) Type of the neighbourhood (handover, measurement…) Null column allowed: Yes Default value: 8.3.1.17.3 NeighboursConstraints Table This table enables you to set handover relationships between transmitters. These constraints are used as input for the automatic neighbour allocation. Field Type Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: NEIGHBOUR Text (50) Second part of the unique key. List of neighbours Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: STATUS Integer Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. Null column allowed: Yes Default value: 0 Choice list: 0=Forced, 1=Forbidden TRANSMITTER Text (50) First part of the unique key. Transmitters or cells. Null column allowed: No Default value: 8.3.1.17.4 NeighboursConstraintsExt Table This table enables you to set external handover relationships (with transmitters/cells of another project). These constraints are used as input for the automatic neighbour allocation. Field Type Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: NEIGHBOUR Text (50) Second part of the unique key. List of neighbours from another project. Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: STATUS Integer Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. Null column allowed: Yes Default value: 0 Choice list: 0=Forced, 1=Forbidden TRANSMITTER Text (50) First part of the unique key. Transmitters or cells Null column allowed: No Default value: 8.3.1.18 Transmitters Table This table stores the transmitters and their properties. Field Type Description Attributes ACTIVE Boolean Transmitter activity: 'Yes' means that the transmitter is active Null column allowed: No Default value: True ANTDIVGAIN Float Antenna diversity gain Null column allowed: Yes Default value: 0 ANTENNA_NAME Text (50) Name of the main antenna installed on the transmitter Null column allowed: Yes Default value: AZIMUT Float Azimuth of the main antenna Null column allowed: Yes Default value: 0 © Forsk 2009 AT281_AM_E1 231 Administrator Manual BTS_NAME Text (50) Name of the BTS equipment Null column allowed: Yes Default value: CALC_RADIUS Integer Calculation radius used to define the calculation area Unit: m Null column allowed: Yes Default value: 4000 CALC_RADIUS2 Integer Extended calculation radius Null column allowed: Yes Default value: CALC_RESOLUTION Integer Calculation resolution Null column allowed: Yes Default value: 50 CALC_RESOLUTION2 Integer Extended calculation resolution Null column allowed: Yes Default value: CELL_SIZE Float Hexagon radius Unit: m Null column allowed: Yes Default value: 2000 COMMENT_ Text (255) Additional information about the transmitter Null column allowed: Yes Default value: DX Float X coordinate relative to the site location Null column allowed: Yes Default value: 0 DY Float Y coordinate relative to the site location Null column allowed: Yes Default value: 0 FEEDER_NAME Text (50) Name of the feeder equipment Null column allowed: Yes Default value: FEEDERLENGTH_DL Float Length of feeder in DL Null column allowed: Yes Default value: 0 FEEDERLENGTH_UL Float Length of feeder in UL Null column allowed: Yes Default value: 0 HEIGHT Float Antenna height above the ground Unit: m Null column allowed: Yes Default value: 25 HEXAGON_GROUP Text (50) Group of hexagons used to create this transmitter Null column allowed: Yes Default value: MISCDLL Float Miscellaneous DL loss Null column allowed: Yes Default value: 0 MISCULL Float Miscellaneous UL loss Null column allowed: Yes Default value: 0 PROPAG_MODEL Text (255) Name of the propagation model used to calculate prediction Null column allowed: Yes Default value: ’Default model’ PROPAG_MODEL2 Text (255) Name of the propagation model used to calculate extended prediction Null column allowed: Yes Default value: SITE_NAME Text (50) Name of the site on which the transmitter is located (from the site table of Atoll) Null column allowed: No Default value: TILT Float Mechanical downtilt of the first antenna Null column allowed: Yes Default value: 0 TMA_NAME Text (50) Name of the TMA equipment Null column allowed: Yes Default value: TX_ID Text (50) Transmitter name Null column allowed: No Default value: AVERAGE_8PSK_POWER_ BACKOFF Float Average power reduction for EGPRS transmitters due to 8PSK modulation in EDGE Null column allowed: Yes Default value: 3 BSIC Text (10) BSIC colour code (Base Station Identity Code) assigned to the station Null column allowed: Yes Default value: BSIC_DOMAIN Text (50) A text field pointing at the BSIC domain. Null column allowed: Yes Default value: BSIC_FROZEN Boolean AFP not allowed to modify BSIC. Null column allowed: No Default value: False CELL_TYPE Text (50) This field identifies a set of records in the TRGConfigurations tables (all the records that point to this cell-type) each of these records specifies a TRG that should exist in this transmitter. Null column allowed: Yes Default value: DCS1800_N_Normal CHANNELS Text (255) Physical channels allocated to the transmitter Null column allowed: Yes Default value: CODING_SCHEME_NUMBE R Integer The number of coding schemes supported by the EGPRS transmitter Null column allowed: Yes Default value: CONTROL_CHANNEL Integer Physical channel used as Broadcast Control Channel (BCCH) Null column allowed: Yes Default value: 232 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure COST_FACTOR Double Used by the AFP assign priorities to transmitters Null column allowed: Yes Default value: 1 EGPRS_EQUIPMENT Text (50) Name of the equipment assigned to the E-GPRS station Null column allowed: Yes Default value: EIRP Float Transmitter’s effective isotropic radiated power Null column allowed: Yes Default value: 43 ENABLE_EGPRS Boolean 'Yes' enables you to consider the transmitter as a E-GPRS station Null column allowed: No Default value: False FBAND Text (20) Name of the frequency band Null column allowed: No Default value: FROZEN Boolean Only TRXs that are not frozen and belong to non-frozen cells can be assigned frequencies by the AFP. Null column allowed: No Default value: False HOP_MODE Text (25) The hopping mode of the default traffic TRG in this transmitter. Null column allowed: Yes Default value: HSN_FROZEN Boolean Only TRGs belonging to non-HSN-frozen cells, and which have non_HSN_frozen configurations, can be assigned HSNs by the AFP. Null column allowed: No Default value: False LAYER Text (50) Name of the Hierarchical Cell Structure layer Null column allowed: Yes Default value: LOSSES Float Losses due to transmitter radio equipment Unit: dB Null column allowed: Yes Default value: 0 MAX_NEIGHB_NUMBER Integer Maximum number of neighbours for the transmitter Null column allowed: Yes Default value: MAX_EXT_NEIGHB_NUMBE R Integer Maximum number of inter-technology neighbours for the transmitter Null column allowed: Yes Default value: NUM_TRX Float 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. Null column allowed: Yes Default value: 0 POWER Float Transmitter power Null column allowed: Yes Default value: REQ_CHANNELS Integer Number of required TRXs Null column allowed: Yes Default value: 1 COV_PROBA Short Cell edge Coverage probability per Transmitter Null column allowed: Yes Default value: 75 MAX_RANGE Integer Maximum range (m) of coverage (for extended cells) Null column allowed: Yes Default value: 35000 MIN_RANGE Integer Minimum range (m) of coverage (for extended cells) Null column allowed: Yes Default value: 0 REDT Float Remote Electrical tilt Null column allowed: Yes Default value: 0 CODEC_EQUIPMENT Text (50) Associated Codec equipment (for voice services) Null column allowed: Yes Default value: TRX_MAX_NUMBER Short Maximum number of TRX that can be allocated by TRX dimensionning Null column allowed: Yes Default value: 16 FN_OFFSET Integer Frame Number offset Null column allowed: Yes Default value: 0 CELL_RESELECT_OFFSET Integer Cell reselection offset Null column allowed: Yes Default value: 0 LAYER_RECEPTION_THRE SHOLD Float If filled-in, takes precedence on the threshold value defined in the HCSLayers table Null column allowed: Yes Default value: PBCCH_CELL_RESELECT_ OFFSET Integer Cell reselection offset for GPRS cells with PBCCH in use (For future use) Null column allowed: Yes Default value: 0 PBCCH_IN_USE Boolean Packet Broadcast Control Channel used or not (For future use) Null column allowed: No Default value: False PBCCH_RECEPTION_THRE SHOLD Float Reception threshold value for GPRS cells with PBCCH in use (For future use) Null column allowed: Yes Default value: -102 CELL_IDENTITY Integer Cell identity Null column allowed: Yes Default value: TX_TYPE Short Type of transmitter (0 = Normal; 1 = Interferer only) Null column allowed: Yes Default value: 0 © Forsk 2009 AT281_AM_E1 233 Administrator Manual 8.3.1.19 TplTransmitters Table This table is used to store station templates and their properties. Field Type Description Attributes ACTIVE Boolean Transmitter activity: 'Yes' means that the transmitter is active Null column allowed: No ANTDIVGAIN Float Antenna diversity gain Unit: dB Null column allowed: Yes ANTENNA_NAME Text (50) Name of the main antenna installed on the transmitter Null column allowed: Yes AZIMUT Float Azimuth of the first antenna Null column allowed: Yes BTS_NAME Text (50) Name of the BTS equipment Null column allowed: Yes CALC_RADIUS Integer Calculation radius used to define each transmitter calculation area Unit: m Null column allowed: Yes CALC_RADIUS2 Integer Extended calculation radius Unit: m Null column allowed: Yes CALC_RESOLUTION Integer Calculation resolution Null column allowed: Yes CALC_RESOLUTION2 Integer Extended calculation resolution Null column allowed: Yes CELL_SIZE Float Hexagon radius Unit: m Null column allowed: Yes FEEDER_NAME Text (50) Name of the feeder equipment Null column allowed: Yes FEEDERLENGTH_DL Float Length of downlink feeder Unit: m Null column allowed: Yes FEEDERLENGTH_UL Float Length of uplink feeder Unit: m Null column allowed: Yes HEIGHT Float Antenna height above the ground Unit: m Null column allowed: Yes MAX_NEIGHB_NUMBER Short Maximum number of neighbours for the cell or the transmitter Null column allowed: Yes MAX_EXT_NEIGHB_NUMBE R Short Maximum number of inter-technology neighbours for the cell or the transmitter Null column allowed: Yes MISCDLL Float Miscellaneous downlink losses Null column allowed: Yes MISCULL Float Miscellaneous uplink losses Null column allowed: Yes NAME Text (50) Template name Null column allowed: No NUM_SECTORS Integer Number of sectors Null column allowed: Yes PROPAG_MODEL Text (255) Name of the propagation model used to calculate predictions Null column allowed: Yes PROPAG_MODEL2 Text (255) Name of the propagation model used to calculate extended prediction Null column allowed: Yes TILT Float Mechanical downtilt of the main antenna Null column allowed: Yes TMA_NAME Text (50) Name of the Tower Mounted Amplifier equipment Null column allowed: Yes AVERAGE_8PSK_POWER_ BACKOFF Float Average power reduction for EGPRS transmitters due to 8PSK modulation in EDGE Null column allowed: Yes BSIC_DOMAIN Text (50) A text field pointing to ResourceGroups.NAME. It limits the BSIC domain of the site. Null column allowed: Yes CELL_TYPE Text (50) This field marks a set of records in the TRGConfigurations tables (all the records for which TRG_CONFIG has the same value.) Each of these records specifies a TRG that should exist in this transmitter. Null column allowed: Yes CODING_SCHEME_NUMBE R Short The number of coding schemes supported by the EGPRS transmitter Null column allowed: Yes EGPRS_EQUIPMENT Text (255) Name of the equipment assigned to the E-GPRS station Null column allowed: Yes EIRP Float Transmitter’s effective isotropic radiated power Null column allowed: Yes ENABLE_EGPRS Boolean 'Yes' enables you to consider the transmitter as a E-GPRS station Null column allowed: No LAYER Text (50) Name of the Hierarchical Cell Structure layer Null column allowed: Yes LOSSES Float Losses due to transmitter radio equipment Unit: dB Null column allowed: Yes 234 POWER Float Transmitter power Null column allowed: Yes REQ_CHANNELS Integer Number of required physical channels Null column allowed: Yes COV_PROBA Short Cell edge Coverage probability per Transmitter Null column allowed: Yes MAX_RANGE Integer Maximum range (m) of coverage (for extended cells) Null column allowed: Yes MIN_RANGE Integer Minimum range (m) of coverage (for extended cells) Null column allowed: Yes REDT Float Remote Electrical tilt Null column allowed: Yes AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure CODEC_EQUIPMENT Text (50) Associated Codec equipment (for voice services) Null column allowed: Yes TRX_MAX_NUMBER Short Maximum number of TRX that can be allocated by TRX dimensionning Null column allowed: Yes FN_OFFSET Integer Frame number offset Null column allowed: Yes CELL_RESELECT_OFFSET Integer Cell reselection offset Null column allowed: Yes LAYER_RECEPTION_THRE SHOLD Float If filled-in, takes precedence on the threshold value defined in the HCSLayers table Null column allowed: Yes PBCCH_CELL_RESELECT_ OFFSET Integer Cell reselection offset for GPRS cells with PBCCH in use (For future use) Null column allowed: Yes PBCCH_IN_USE Boolean Packet Broadcast Control Channel used or not (For future use) Null column allowed: No PBCCH_RECEPTION_THRE SHOLD Float Reception threshold value for GPRS cells with PBCCH in use (For future use) Null column allowed: Yes TX_TYPE Short Type of transmitter (0 = Normal; 1 = Interferer only) Null column allowed: Yes 8.3.1.20 Repeaters Table This table manages repeaters and repeater properties. Field Type Description Attributes AMPLIFIER_GAIN Float Gain of the amplifier Null column allowed: Yes Default value: 80 AZIMUT Float Azimuth of the donor side antenna Null column allowed: Yes Default value: 0 DONOR_CELLID Text (50) Name of the donor transmitter Null column allowed: No Default value: DOWNTILT Float Downtilt of the donor side antenna Null column allowed: Yes Default value: 0 FEEDER_NAME Text (50) Name of the donor side feeder Null column allowed: Yes Default value: FEEDERLENGTH Float Length of donor side feeder Null column allowed: Yes Default value: 0 EIRP Float EIRP of the repeater Null column allowed: Yes Default value: 0 HEIGHT Float Height of the donor side antenna Null column allowed: Yes Default value: 25 REC_ANTENNA Text (50) Name of the donor side antenna Null column allowed: Yes Default value: TX_ID Text (50) Name of the transmitter (and of the transmitter used for coverage) Null column allowed: No Default value: DONOR_LINK_TYPE Short 1- Off air 2- Microwave 3- Fibre Null column allowed: No Default value: 1 DONOR_LINK_LOSS Float Loss (dB) between donor and donor side of the repeater Null column allowed: Yes Default value: 0 EQUIPMENT_NAME Text (50) If no equipment, the repeater is a passive component Null column allowed: Yes Default value: REC_FEEDERLENGTH_UL Float Length of donor side uplink feeder Null column allowed: Yes Default value: 0 DONOR_PROPAG_MODEL Text (50) Name of the propagation model used to calculate prediction between donor and repeater Null column allowed: Yes Default value: Notes: 8.3.1.21 • 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). RepeaterEquipments Table This table models the equipment used by repeaters. © Forsk 2009 AT281_AM_E1 235 Administrator Manual Field Type Description Attributes NAME Text (50) Name of the repeater equipment Null column allowed: No Default value: MANUFACTURER Text (50) Manufacturer of the repeater equipment Null column allowed: Yes Default value: NOISE_FIGURE Float Repeater noise Figure (dB) Null column allowed: Yes Default value: 5 MIN_AMPLIFIER_GAIN Float Minimum gain of the amplifier (dB) Null column allowed: Yes Default value: 50 MAX_AMPLIFIER_GAIN Float Maximum gain of the amplifier (dB) Null column allowed: Yes Default value: 90 STEP_AMPLIFIER_GAIN Float Step of amplifier gain (dB) Null column allowed: Yes Default value: 1 MAX_OUTPUT_UL Float Maximum uplink output power (dBm) Null column allowed: Yes Default value: 12 MAX_OUTPUT_DL Float Maximum downlink output power (dBm) Null column allowed: Yes Default value: 30 TIME_DELAY Float Time delay in the equipment (microseconds) Null column allowed: Yes Default value: 5 COMMENT_ Text (255) Comments Null column allowed: Yes Default value: 8.3.1.22 Resource Management Tables These tables manage resources such as frequencies, BSICs, and HSNs. You may define domains and groups of resources (a domain being a set of groups of resources). 8.3.1.22.1 FrequencyDomains Table Field Type Description Attributes FREQUENCY_BAND_NAME Text (50) Name of the frequency band on which domain is based Null column allowed: No Default value: NAME Text (50) Name of domain Null column allowed: No Default value: 8.3.1.22.2 FrequencyGroups Table Field Description Attributes DOMAIN_NAME Text (50) Called grouping scheme. Set of resource groups. Null column allowed: No Default value: EXCLUDED Text (255) List of frequencies to be excluded from the series defined by FIRST, LAST and STEP (separated with commas) Null column allowed: Yes Default value: EXTRA Text (225) Frequencies to be added. It is forbidden for EXTRA and EXLUDED to have common numbers Null column allowed: Yes Default value: FIRST Integer 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 LAST Integer 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 NAME Text (50) Unique key. Name of a Resource Group Null column allowed: No Default value: STEP Integer 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: 1 8.3.1.22.3 BSICDomains Table Field NAME 236 Type Type Text (50) Description Attributes Name of the domain Null column allowed: No Default value: AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.3.1.22.4 BSICGroups Table Field Type Description Attributes DOMAIN_NAME Text (50) Called grouping scheme. Set of resource groups. Null column allowed: No Default value: EXCLUDED Text (225) List of BSICs to be excluded from the series defined by FIRST, LAST and STEP (separated with commas) Null column allowed: Yes Default value: EXTRA Text (225) BSIC to be added. It is forbidden for EXTRA and EXLUDED to have common numbers Null column allowed: Yes Default value: FIRST Integer 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 LAST Integer 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 NAME Text (50) Unique key. Name of a resource group Null column allowed: No Default value: STEP Integer 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: 1 Note: • 8.3.1.22.5 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. HSNDomains Table Field Type NAME 8.3.1.22.6 Text (50) Description Attributes Name of HSN (Hopping Sequence Number) domain. Null column allowed: No Default value: HSNGroups Table Field Type Description Attributes DOMAIN_NAME Text (50) Called grouping scheme. Set of resource groups. Null column allowed: No Default value: EXCLUDED Text (225) List of HSNs to be excluded from the series defined by FIRST, LAST and STEP (separated with commas) Null column allowed: Yes Default value: EXTRA Text (225) HSNs to be added. It is forbidden for EXTRA and EXLUDED to have common numbers Null column allowed: Yes Default value: FIRST Integer 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 LAST Integer 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 NAME Text (50) Unique key. name of a Resource Group Null column allowed: No Default value: STEP Integer 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: 1 8.3.1.23 Layers Table This table is used to manage HCS layers. Field Type Description Attributes NAME Text (50) Name of the hierarchical cell structure layer Null column allowed: No Default value: MAX_SPEED Float Threshold speed for a mobile considered eligible to reside on a layer Null column allowed: Yes Default value: 300 PRIORITY Short Priority of the layer (largest value has the highest priority) Null column allowed: No Default value: 1 MIN_PRIORITY_POWER Float Minimum power value for the HCS layer Null column allowed: Yes Default value: -130 © Forsk 2009 AT281_AM_E1 237 Administrator Manual 8.3.1.24 TRXTypes Table This table contains a list of TRX types. By default this table contains three types of TRXs: BCCH, TCH, and TCH_INNER. Field Type Description Attributes IS_BCCH Boolean Indicates that a TRG_TYPE is the Common Broadcast carrier. Tests in the code will verify that only one type carries the broadcast. Null column allowed: No Default value: False IS_TCH_DEF Boolean Indicates that a TRG_TYPE is the default traffic carrier (the OUTER zone). Tests in the code will verify that only one type is the default TCH. Null column allowed: No Default value: False NAME Text (15) Type of TRX Null column allowed: No Default value: PRIORITY Short Priority of a certain type of TRX to carry traffic (largest value has the highest priority) Null column allowed: Yes Default value: 0 TRAFFIC_POOL Short All TRXs of the same pool can exchange traffic if they need to balance their loads. If they are in different pools, the load balancing might fail. Null column allowed: Yes Default value: 1 8.3.1.25 TRXEquipments Table This table models equipment used in Subcells and TRXs tables. Field Type Description Attributes NAME Text (25) Name of TRX equipment Null column allowed: No Default value: GMSK_POWER Float Nominal output power in GMSK modulation Null column allowed: Yes Default value: 47 _8PSK_POWER Float Nominal output power in 8PSK modulation Null column allowed: Yes Default value: 44 MAX_CS Short Highest coding scheme (CS) available for GPRS Null column allowed: No Default value: 4 MAX_MCS Short Highest coding scheme (MCS) available for EDGE Null column allowed: No Default value: 12 COMMENT_ Text (100) Comments Null column allowed: Yes Default value: 8.3.1.26 CellTypes Table This table contains a list of cell types. Field Type Description Attributes NAME Text (50) Defines the list of TRXs of the station and associated parameters. Null column allowed: No Default value: 8.3.1.27 TRGConfigurations Table This table stores cell types parameters. Field Type Description Attributes ASSIGN_MODE Text (25) One of the two options: «Free» or «Group constrained». Null column allowed: No Default value: ‘Free’ BAD_QUAL_UB Float Additional constraints on subcell quality (considered in AFP): maximum probability to have C/I lower than C_OVER_I_MIN. Null column allowed: No Default value: 1 C_OVER_I_MIN Float Minimum C/I Null column allowed: No Default value: 12 CELL_TYPE Text (50) First part of unique key. Null column allowed: No Default value: COST_FACTOR Float By default, 1. The cost factor will be used to increase or decrease the importance of subcells of this configuration. Null column allowed: No Default value: 1 DEF_DTX Boolean This is a default value of a subcell specific parameter. It is set to true if the TRXs of the subcell use Discontinuous transmission Null column allowed: No Default value: True DEF_HOP_MODE Text (25) This is a default value of a subcell specific parameter. Hopping mode can be “Non Hopping”, “Base Band Hopping”, or “Synthesized Hopping”. Null column allowed: No Default value: ‘Non Hopping’ DEF_MIN_RECEPTION Float This is a default value of a subcell specific parameter. It denotes the minimum received power required to be served by this subcell. Null column allowed: No Default value: -102 238 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure DEF_POWER_OFFSET Float This is a default value of a subcell specific parameter: the average power offset with respect to the BCCH channel. Null column allowed: No Default value: 0 FREQUENCY_DOMAIN Text (50) All frequencies assigned to TRXs of this configuration must belong to this domain. Domains contain grouping info as well. Null column allowed: No Default value: HR_RATIO Float Percentage of Half Rate voice traffic in the subcell. Null column allowed: Yes Default value: 40 HSN_DOMAIN Text (50) All HSNs assigned to subcells of this configuration must belong to this domain. Null column allowed: No Default value: HSN_FROZEN Boolean Only subcells that point to non-hsn_frozen configurations in nonhsn_frozen cells can by be assigned HSNs by the AFP. Null column allowed: No Default value: False MAXIMAL_MAL Integer Limitation on length of the MAL (Mobile allocation list). Null column allowed: No Default value: 48 TRX_TYPE Text (15) Second part of unique key Null column allowed: No Default value: TRAFFIC_OVERFLOW_TAR GET Float The percentage of traffic that is considered to overflow from the subcell. Null column allowed: Yes Default value: 0 TS_CONFIGURATION_NAM E Text (50) Timeslot configuration Null column allowed: Yes Default value: MEAN_POWER_CONTROL Float Average value of DL power control Null column allowed: Yes Default value: 0 DEF_TRX_EQUIPMENT Text (25) Default TRX equipment of TRXs belonging to this subcell Null column allowed: Yes Default value: _8PSK_PWBCKFF Float Reduction of power due to 8PSK modulation Null column allowed: Yes Default value: 3 TX diversity Null column allowed: Yes Default value: 1 Choice list: . 1= no TX diversity, 2= TX diversity with 2 antennas TX_DIVERSITY_NBANT 8.3.1.28 Short TRGs Table This table stores subcell parameters. Field Type Description Attributes ASSIGN_MODE Text (25) One of the two options: “Free” or “Group constrained”. Null column allowed: Yes Default value: ‘Free’ BAD_QUAL_UB Float Additional constraints on subcell quality (considered in AFP): maximum probability to have C/I lower than C_OVER_I_MIN. Null column allowed: Yes Default value: 1 COST_FACTOR Float By default, 1. The cost factor is used to increase or decrease the importance of subcells of this configuration. Null column allowed: Yes Default value: 1 C_OVER_I_MIN Float Minimum C/I Null column allowed: Yes Default value: 12 DTX Boolean It is set to true if the TRXs of the subcell use Discontinuous transmission. Null column allowed: No Default value: True EFFECTIVE_TRAFFIC_OVE RFLOW Float Effective traffic overflow Null column allowed: Yes Default value: FREQUENCY_DOMAIN Text (50) All frequencies assigned to TRXs of this configuration must belong to this domain. Domains contain grouping info as well. Null column allowed: Yes Default value: EXCLUDED Text (250) List of frequencies which should not be used by TRX of the current subcell. Null column allowed: Yes Default value: HOP_MODE Text (25) The hopping mode of a subcell can be “Non Hopping”, “Base Band Hopping”, or “Synthesized Hopping”. Null column allowed: Yes Default value: ‘Non Hopping’ HR_RATIO Float Percentage of Half rate traffic in the subcell. Null column allowed: Yes Default value: 40 HSN Integer Assigned HSN. Null column allowed: Yes Default value: HSN_DOMAIN Text (50) All HSNs assigned to subcells of this configuration must belong to this domain. Null column allowed: Yes Default value: HSN_FROZEN Boolean Only subcells that point to non-hsn_frozen configurations in nonhsn_frozen cells can be assigned HSNs by the AFP. Null column allowed: No Default value: False MAXIMAL_MAL Integer Limitation on length of the MAL (Mobile allocation list). Null column allowed: Yes Default value: 48 © Forsk 2009 AT281_AM_E1 239 Administrator Manual MIN_RECEPTION Float Minimum reception power required to be served by this subcell. Null column allowed: No Default value: -102 POWER_OFFSET Float The average power offset with respect to the BCCH channel. Null column allowed: No Default value: 0 REQ_CHANNELS Integer Number of required channels. Null column allowed: No Default value: 0 SYNCHRO_NAME Text (50) Defines synchronization sets. Null column allowed: Yes Default value: TRAFFIC_LOAD Float TRAFFIC_LOAD = (Traffic in Erlangs) / (NUM_TRX * Multyplexing_factor ) (Where, Multiplexing_factor = 8). Null column allowed: No Default value: 1 TRAFFIC_OVERFLOW_TAR GET Float The percentage of traffic that is considered to overflow from one subcell. Null column allowed: Yes Default value: 0 TRX_TYPE Text (15) Second part of a unique key. Points to the TRX type table. Null column allowed: No Default value: TS_CONFIGURATION_NAM E Text (50) Timeslot configuration Null column allowed: Yes Default value: TX_ID Text (50) 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). Null column allowed: No Default value: MEAN_POWER_CONTROL Float Average value of DL power control Null column allowed: Yes Default value: 0 DEF_TRX_EQUIPMENT Text (25) Default TRX equipment of TRXs belonging to this subcell Null column allowed: Yes Default value: _8PSK_PWBCKFF Float Power reduction due to 8PSK modulation Null column allowed: Yes Default value: 3 PREFERRED_FREQ_GROU P Text (50) Frequency group which should be used if possible Null column allowed: Yes Default value: TX_DIVERSITY_NBANT Short TX diversity Null column allowed: Yes Default value: 1 Choice list: . 1= no TX diversity, 2= TX diversity with 2 antennas AFP_BLOCKED_COST Float Secondary AFP quality indicator Null column allowed: Yes Default value: 0 AFP_CONGESTION Float Secondary AFP indicator depicting the spectral congestion state Null column allowed: Yes Default value: 0 AFP_COST Float Main AFP quality indicator Null column allowed: Yes Default value: 0 AFP_FREEZE_DIM Boolean Permit the AFP to not always respect the number of required TRXs Null column allowed: No Default value: False AFP_SEP_COST Float Secondary AFP quality indicator Null column allowed: Yes Default value: 0 CS_ERLANGS Float Circuit switched demand in Erlangs Null column allowed: Yes Default value: 0 PS_DATA_ERLANGS Float Packet switched demand in data Erlangs (equivalent to avaraged used time slots) Null column allowed: Yes Default value: 0 8.3.1.29 TRXs Table This table store the TRXs of transmitters. Field 240 Type Description Attributes CN_LIST Text (255) List of all frequencies assigned to a TRX. (separated with spaces) Null column allowed: Yes Default value: FROZEN Boolean Allows/disallows changing parameters of this TRX. Null column allowed: No Default value: False MAIO Integer Assigned MAIO (Mobile Allocation Index Offset). Null column allowed: Yes Default value: TRX_NUMBER Integer An order on TRXs in the same subcell. It is the second part of a unique key. Null column allowed: No Default value: TRX_TYPE Text (15) The couple TX_ID, TRG_TYPE is the key of the TRGs table to which this TRX belongs Null column allowed: No Default value: AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure TX_ID Text (50) 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. TRX_EQUIPMENT Text (25) TRX equipment of this TRX Null column allowed: Yes Default value: _8PSK_PWBCKFF Float Reduction of power due to 8PSK modulation Null column allowed: Yes Default value: 3 AFP_RANK Short Rank of this TRX according to the AFP Null column allowed: Yes Default value: 0 DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes Default value: 0 UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes Default value: 0 UPLINK_NOISE_RISE Float Uplink noise rise Null column allowed: Yes Default value: 0 8.3.1.30 Null column allowed: No Default value: Separations Table This table contains separation requirements for some pairs of subcells or pairs of transmitters. It is used as an input for the AFP. Field Type Description Attributes MIN_SEP Integer Minimum separation requirement. Null column allowed: No Default value: 1 TRX_TYPE Text (15) First transmitter subcell or All Null column allowed: No Default value: “All” TRX_TYPE_OTHER Text (15) Second transmitter subcell or All Null column allowed: No Default value: “All” TX_ID Text (50) First transmitter name in a symmetric relation. Null column allowed: No Default value: TX_ID_OTHER Text (50) Second transmitter name in a symmetric relation. Null column allowed: No Default value: 8.3.1.31 SeparationRules Table This table is used to define default separations for each kind of subcell or cell relationships. It is used as an input for the AFP. Field Type Description Attributes RELATION_TYPE Short Type of the relation : 1=Co-Subcell; 2=Co-Cell; 3=Co-Site; 4=Neighbour Null column allowed: No Default value: 1 TRX_TYPE Text (15) Type of TRX or All Null column allowed: No Default value: ’All’ TRX_TYPE_OTHER Text (15) Type of TRX or All Null column allowed: No Default value: ’All’ DEFAULT_MIN_SEP Short Minimum separation requirement Null column allowed: No Default value: 1 8.3.1.32 TSConfigurationNames Table This table contains a list of timeslot configurations. Field NAME 8.3.1.33 Type Text (50) Description Attributes Name of the configuration Null column allowed: No Default value: TSConfigurations Table This table stores timeslot configuration parameters. Field Type Description Attributes NAME Text (50) Name of the configuration Null column allowed: No Default value: TRX_NUMBER Integer Zero based index of TRX Null column allowed: No Default value: 1 © Forsk 2009 AT281_AM_E1 241 Administrator Manual COMPOSITE_TS Integer Number of timeslots that support circuit and packet switched traffic Null column allowed: No Default value: 8 CIRCUIT_TS Integer Number of timeslots that support circuit switched traffic Null column allowed: No Default value: 0 PACKET_TS Integer Number of timeslots that support packet switched traffic Null column allowed: No Default value: 0 8.3.1.34 EGPRSCodingSchemes Table This table manges GPRS, EGPRS, and EGPRS2 coding schemes: Field Type Description Attributes CS_NUMBER Short Coding scheme number Null column allowed: No Default value: 1 DATA_CODING Short Type of FEC coding (0: Convolutional, 1: Turbo) Null column allowed: No Default value: 0 MAX_THROUGHPUT Float Maximum rate obtained when there is no data transmission error Unit: kbps Null column allowed: No Default value: 1 MODULATION Short Modulation (0: GMSK,1: 8-PSK, 2: QPSK,3: 16QAM, 4: 32QAM) Null column allowed: No Default value: 0 NAME Text (50) Name of the coding scheme Null column allowed: No Default value: TECHNOLOGY Text (15) Technology ("GPRS", "GPRS/EDGE", "EGPRS2") Null column allowed: No Default value: ’GPRS’ 8.3.1.35 EGPRSEquipments Table This table manages GPRS and EGPRS equipment. Field Type Description Attributes NAME Text (50) Equipment name Null column allowed: No Default value: TECHNOLOGY Text (15) GSM, GPRS or GPRS/EDGE. To allocate traffic to compatible transmitter mobile pair. Null column allowed: Yes Default value: GPRS REFERENCE_NOISE Float Reference noise of the equipment which has been used to produce the curves Null column allowed: Yes Default value: -113 8.3.1.36 EGPRSQuality Table This table stores the properties of GPRS and EGPRS equipment. Field Type Description Attributes C_THRESHOLD Float Minimum power (C) required at the receiver in order for a coding scheme to be used Null column allowed: Yes Default value: 1 C_THROUGHPUTS Memo Set of values used to generate throughput=f(C) graph Null column allowed: Yes Default value: COVERI_THRESHOLD Float Minimum carrier to interference ratio (C/I) required at the receiver in order for a coding scheme to be used Null column allowed: Yes Default value: 1 COVERI_THROUGHPUTS Memo Set of values used to generate the throughput=f(C/I) graph Null column allowed: Yes Default value: ’0’ EQUIPMENT Text (50) Type of equipment Null column allowed: No Default value: FREQUENCY_BAND Text (20) Frequency Band (empty = all bands) Null column allowed: Yes Default value: HOPPING Short Hopping mode corresponding to the curves ( 1=NH; 2= ideal FH; empty = all hopping modes) Null column allowed: Yes Default value: MOBILITY Text (50) Mobility (empty = all mobilities) Null column allowed: Yes Default value: CS_NAME Text (10) Coding scheme name Null column allowed: Yes Default value: 242 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.3.1.37 EGPRSDimensioningModel Table This table stores network dimensioning models and parameters. Field Type Description Attributes NAME Text (50) Service Name Null column allowed: No Default value: QUEUING_MODEL Text (50) Queuing model: Erlang B , Erlang C Null column allowed: Yes Default value: ’Erlang B’ MAX_CHANNELS Text (4) Maximum number of TRXs that can be allocated Null column allowed: No Default value: ’16’ MIN_DEDICATED_PDCH Integer Minimum dedicated timeslots number for packet switched traffic Null column allowed: No Default value: 0 MAX_TRXS_TO_ADD_FOR_ PACKET Integer Maximum allowed number of TRXs to add in order to reach required quality for packet switched services Null column allowed: Yes Default value: 100 PDCH_THROUGHPUT_MIN_ KPI Boolean Minimum throughput KPI Null column allowed: No Default value: True PDCH_BLOCKING_PROBA_ KPI Boolean Blocking probability KPI Null column allowed: No Default value: False PDCH_DELAY_KPI Boolean Service delay KPI Null column allowed: No Default value: False 8.3.1.38 EGPRSServiceQuality Table This table stores quality graphs used for the packet-switched traffic dimensioning. Field Type Description Attributes DIMENSIONING_MODEL Text (50) Name of the dimensioning model Null column allowed: No Default value: AVAIL_CONNECTIONS Float Number of available connections Null column allowed: Yes Default value: 1 LOAD_RF Memo Set of values used to generate the chart throughput reduction factor=f(Load) Null column allowed: Yes Default value: ’1’ LOAD_DELAY Memo Set of values used to generate the chart Delay=f(Load) Null column allowed: Yes Default value: ’1’ LOAD_BLOCKING_PROBA Memo Set of values used to generate the chart Blocking=f(Load) Null column allowed: Yes Default value: ’1’ 8.3.1.39 QualityIndicators Table This table used by Quality Indicator (FER, BER, BLER, etc.) coverage predictions. Field Type Description Attributes NAME Text (20) Name of the managed quality indicator Null column allowed: No Default value: PS_QI Boolean Flag which indicates if this indicator is used for PS services Null column allowed: No Default value: True CS_QI Boolean Flag which indicates if this indicator is used in CS services Null column allowed: No Default value: True MEAS_PARAM Short Name of the measured figure used for this QI determination Null column allowed: Yes Default value: 1 Choice list: 1 = C, 2 = CIR USE_INTERPOLATION Boolean Flag which indicates if this QI must be interpolated or not Null column allowed: No Default value: True 8.3.1.40 Multi-Service Traffic Management Tables This tables contain descriptions of multi-service traffic data, i.e., services, mobility types, terminals, user profiles, and environments. 8.3.1.40.1 EGPRSEnvironmentDefs Table Field Type Description Attributes ENVIRONMENT Text (50) Environment name Null column allowed: No Default value: © Forsk 2009 AT281_AM_E1 243 Administrator Manual USER_PROFILE Text (255) User profile Null column allowed: No Default value: MOBILITY Text (50) Type of mobility Null column allowed: No Default value: DENSITY Float Number of subscribers per km2 Null column allowed: Yes Default value: 0 8.3.1.40.2 EGPRSMobility Table Field Type Description Attributes NAME Text (50) Name of mobility type Null column allowed: No Default value: SPEED Float Average speed (km/h) Null column allowed: No Default value: 8.3.1.40.3 EGPRSServices Table Field Type Description Attributes NAME Text (50) Service Name Null column allowed: No Default value: ’1’ MIN_THROUGHPUT Float Minimum user throughput requested for the service Null column allowed: Yes Default value: 15 MIN_THROUGHPUT_RATIO Float Dimensioning target of the % of surface where minimum throughput is reached Null column allowed: Yes Default value: 95 MAX_DELAY Float Maximum delay allowed for the service Null column allowed: Yes Default value: 1 MAX_BLOCKING_RATE Float Maximum probability that a packet is blocked (delayed), GoS for circuit switched services Null column allowed: Yes Default value: 2 MAX_TS_SUPPORT Integer Maximum number of timeslots supported by the service Null column allowed: Yes Default value: 4 TH_SCALE_FACTOR Float Percentage of end user throughput compared to MAC throughput Null column allowed: Yes Default value: 95 TH_OFFSET Float Offset which should be added to the scale factor Null column allowed: Yes Default value: 0 TYPE Short Type of service (0: circuit; 1: packet; 2: circuit over packet) Null column allowed: No Default value: 0 8.3.1.40.4 EGPRSServicesUsage Table Field Type Description Attributes USER_PROFILE Text (255) User profile name Null column allowed: No Default value: SERVICE Text (50) Service that the subscriber may request Null column allowed: No Default value: TERMINAL Text (50) Type of terminal used by the subscriber for the service Null column allowed: No Default value: CALL_NUMBER Float Average number of calls per hour for circuit switched services or average number of sessions per hour for packet switched services Null column allowed: Yes Default value: 0 CALL_DURATION Float Average duration of a call (for circuit switched services) Null column allowed: Yes Default value: DL_VOLUME Float Volume transferred on the downlink during a session (for packet switched services) Null column allowed: Yes Default value: 8.3.1.40.5 EGPRSTerminals Table Field Type Description Attributes NAME Text (50) Terminal name Null column allowed: No Default value: DL_AVAIL_TIME_SLOT Float Number of timeslots the mobile terminal can multiplex in downlink Null column allowed: Yes Default value: 1 PRIMARY_BAND Text (50) Frequency band the mobile terminal is compatible with Null column allowed: No Default value: SECONDARY_BAND Text (50) Frequency band the mobile terminal is compatible with (for dual-band mobile terminals) Null column allowed: Yes Default value: 244 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure TECHNOLOGY Text (15) Technology supported by the mobile terminal Null column allowed: Yes Default value: EGPRS_EQUIPMENT Text (50) Associated EGPRS equipment (for PS services) Null column allowed: Yes Default value: CODEC_EQUIPMENT Text (50) Associated Codec Equipment (for voice services) Null column allowed: Yes Default value: MAX_CS Short Highest coding scheme (CS) available for GPRS Null column allowed: Yes Default value: 4 MAX_MCS Short Highest coding scheme (MCS) available for EDGE Null column allowed: Yes Default value: 12 NOISE_FIGURE Float Noise figure of the terminal Null column allowed: Yes Default value: 8 SAIC Boolean Terminal capability for Single Antenna Interference Cancellation (for future use) Null column allowed: No Default value: False DL_AVAIL_CARRIERS Short Number of simultaneous carriers Null column allowed: Yes Default value: 1 PMAX Float Max power that can be used in UL (for UL calculations) Null column allowed: Yes Default value: 33 8.3.1.40.6 EGPRSTrafficEnvironments Table Field Type Description Attributes NAME Text (50) Name of the created environment Null column allowed: No Default value: CLUTTER_WEIGHTS Binary Internal binary format describing weights assigned to each clutter class Null column allowed: Yes Default value: 8.3.1.40.7 EGPRSUserProfiles Table Field Type NAME 8.3.1.41 Text (50) Description Attributes Name of the created user profile Null column allowed: No Default value: CodecModes Table This table defines a list of codec types and modes. Field Type Description Attributes NAME Text (50) Name of the codec mode Null column allowed: No Default value: CODEC_TYPE Text (50) Name of codec type Null column allowed: No Default value: HR Boolean Half rate support Null column allowed: No Default value: False _8PSK_MODULATION Boolean Modulation is 8PSK Null column allowed: No Default value: False MAX_RATE Float Maximum supported rate for this mode (kbps) Null column allowed: No Default value: 0 SELECTION_PRIORITY Short Priority value used to select the best possible mode Null column allowed: No Default value: 0 8.3.1.42 CodecEquipments, CodecModeAdaptations and CodecQualityTables Tables These tables model codec equipment used in the EGPRSTerminals and Transmitters tables. 8.3.1.42.1 CodecEquipments Table Field Type Description Attributes NAME Text (50) Name of Codec equipment Null column allowed: No Default value: IDEAL_LINK_ADAPTATION Boolean Automatic mode selection providing the best quality Null column allowed: No Default value: True © Forsk 2009 AT281_AM_E1 245 Administrator Manual IDEAL_QI_NAME Text (20) Reference quality indicator name used for ideal link adaptation Null column allowed: Yes Default value: REFERENCE_NOISE Float Receiver reference noise Null column allowed: No Default value: -113 8.3.1.42.2 CodecModeAdaptations Table Field Type Description Attributes CODEC_EQT Text (50) Codec equipment name Null column allowed: No Default value: CODEC_MODE Text (50) Codec mode Null column allowed: No Default value: FREQUENCY_BAND Text (20) Frequency Band (empty = all bands) Null column allowed: Yes Default value: HOPPING Short Frequency hopping 1=NH; 2= ideal FH; empty = all hopping modes Null column allowed: Yes Default value: MOBILITY Text (50) Mobility (empty = all mobilities) Null column allowed: Yes Default value: MIN_CIR Float C/(I+N) quality threshold for selecting this mode when there is no ideal link adaptation Null column allowed: Yes Default value: 0 8.3.1.42.3 CodecQualityTables Table Field Type Description Attributes CODEC_EQT Text (50) Codec equipment name Null column allowed: No Default value: QI_NAME Text (20) Quality indicator name Null column allowed: No Default value: CODEC_MODE Text (50) Codec mode Null column allowed: No Default value: FREQUENCY_BAND Text (20) Frequency Band (empty = all bands) Null column allowed: Yes Default value: HOPPING Short Frequency hopping 1=NH; 2= ideal FH; empty = all hopping modes Null column allowed: Yes Default value: MOBILITY Text (50) Mobility (empty = all mobilities) Null column allowed: Yes Default value: C_I_TABLE Memo QI = f(C/I) table Null column allowed: Yes Default value: C_N_TABLE Memo QI = f(C/N) table Null column allowed: Yes Default value: 8.3.1.43 ChannelModels Table This table stores the transmitter antenna diversity gains for different clutter classes. Field Type Description Attributes NAME Text (50) Name of the channel model Null column allowed: No TX_DIV_GAIN Float Gain applied for subcells using TX diversity Null column allowed: No Default value: 0 8.3.1.44 AfpModels Table This table contains AFP model description, settings, and state. 246 Field Type Description Attributes Data Binary Model specific parameters Null column allowed: Yes Description Text (255) User defined Null column allowed: Yes Name Text (50) Name of the AFP model Null column allowed: No Signature Text (40) Unique Global ID of last model update Null column allowed: No Type Text (50) ProgID of the model Null column allowed: No AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.3.1.45 InterNetChProtect Table This table stores the inter-network channel protection graphs. Field Type Description Attributes ICP Memo Inter-network channel protection = f(  MHz) Null column allowed: Yes Default value: ITF_BW Double Interfering bandwidth (kHz) Null column allowed: No Default value: 0 ITF_TECHNO Text (50) Interfering technology Null column allowed: No Default value: V_BW Double Victim bandwidth (kHz) Null column allowed: No Default value: 0 © Forsk 2009 AT281_AM_E1 247 Administrator Manual 8.4 UMTS HSPA Template Figure 8.5: on page 248, Figure 8.6: on page 249, and Figure 8.7: on page 250 depict the UMTS HSPA database structure. Figure 8.5: UMTS HSPA Template - 1 248 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure Figure 8.6: UMTS HSPA Template - 2 © Forsk 2009 AT281_AM_E1 249 Administrator Manual Figure 8.7: UMTS HSPA Template - 3 8.4.1 UMTS HSPA Tables The UMTS HSPA project template has the following data structure. 8.4.1.1 PropagationModels Table This table contains propagation model description, formulas, and parameters. Field 250 Type Description Attributes Data Binary Model specific parameters Null column allowed: Yes Description Text (255) User defined Null column allowed: Yes Name Text (50) Name of the propagation model Null column allowed: No AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure Signature Text (40) Unique Global ID of last model update Null column allowed: No Type Text (50) ProgID of the model Null column allowed: No 8.4.1.2 CustomFields Table This table enables you to define default values for all the fields of all the tables in Atoll, including user-defined fields added to different tables. It also enables you to define choice lists, a caption, and a group name for user-defined fields. Field Type Description Attributes CHOICE_LIST Memo Choice list for the field Null column allowed: Yes COLUMN_NAME Text (50) Second part of the unique key. Field name Null column allowed: No DEFAULT_VALUE Text (50) Default value for the field Null column allowed: Yes TABLE_NAME Text (50) First part of the unique key. Table name Null column allowed: No CAPTION Text (50) Caption of the field (displayed instead of the name) Null column allowed: Yes GROUP_NAME Text (50) Name of the group to which that field belongs Null column allowed: Yes The default values defined in this table have priority over the internal predefined default values (hard-coded in Atoll or defined in the database table structure). In order for Atoll to correctly consider the new default values, note that: • • 8.4.1.3 If you use floating point values, ensure that all the users have the same decimal separator (comma or point). The field names are case sensitive. CoordSys Table This table stores descriptions of the projection coordinate system and database’s internal coordinate system (the display coordinate system used when creating a database). Field Type Description Attributes CODE Integer Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768) Null column allowed: No Default value: 0 DATUM_CODE Double DATUM_ROTX Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_ROTY Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_ROTZ Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_SCALE Double Parts per million (ppm) Null column allowed: Yes Default value: 0 DATUM_SHIFTX Double Meters Null column allowed: Yes Default value: 0 DATUM_SHIFTY Double Meters Null column allowed: Yes Default value: 0 DATUM_SHIFTZ Double Meters Null column allowed: Yes Default value: 0 ELLIPS_CODE Integer ELLIPS_RMAJOR Double Meters Null column allowed: Yes Default value: 0 ELLIPS_RMINOR Double Meters Null column allowed: Yes Default value: 0 NAME Text (50) Coordinate system name Null column allowed: No Default value: PROJ_ANGLE Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_FALSE_EASTING Double Meters Null column allowed: Yes Default value: 0 PROJ_FALSE_NORTHING Double Meters Null column allowed: Yes Default value: 0 PROJ_FIRST_PARALLEL Double Decimal degrees Null column allowed: Yes Default value: 0 © Forsk 2009 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 AT281_AM_E1 251 Administrator Manual PROJ_LATITUDE_ORIGIN Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_LONGITUDE_ORIGIN Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_METHOD Short Undefined, NoProjection, Lambert1SP, Lambert2SP, Mercator, CassiniSoldner, TransMercator, TransMercatorSO, ObliqueStereographic, NewZealandMapGrid, HotineOM, LabordeOM, SwissObliqueCylindical, UTM Null column allowed: Yes Default value: 0 PROJ_SCALE_FACTOR Double PROJ_SECOND_PARALLEL Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_ZONE_NUMBER Integer Used with UTM Null column allowed: Yes Default value: 0 8.4.1.4 Null column allowed: Yes Default value: 0 Units Table This table stores the identification numbers of reception and transmission units, projection coordinate system specified in the .atl document and the database internal coordinate system. Field Type Description Attributes COORD_SYSTEM Integer Display coordinate system when creating database Null column allowed: Yes Default value: -1 PROJECTION Integer Projected coordinate system for geo data Null column allowed: Yes Default value: -1 Reception unit when creating database Null column allowed: No Default value: 0 Choice list: 0=dBm, 1=dbµV, 2=dbµV/m RECEPTION_UNIT Integer TRANSMISSION_UNIT Integer Transmission unit when creating database Null column allowed: No Default value: 0 Choice list: 0=dBm, 1=Watts, 2=kWatts GAIN_UNIT Integer Unit used for gains (dBd or dBi) Null column allowed: Yes Default value: 0 Choice list: 0= dBd, 1= dBi 8.4.1.5 Networks Table This table contains network-level properties and network-specific data. Field Type Description Attributes Null column allowed: No Default value: NAME Text (50) TECHNOLOGY Text (10) Name of the technology Null column allowed: No Default value: ‘CDMA’ SYSTEM_ Text (50) Name of the system Null column allowed: No Default value: ‘UMTS’ DEFAULT_RESOLUTION Float Default calculation resolution Null column allowed: No Default value: 50 DEFAULT_MODEL Text (50) Default propagation model Null column allowed: Yes Default value: ‘Cost-Hata’ Shared results storage folder Null column allowed: Yes Default value: SHARED_RESULTS_FOLDE Text (255) R DMAX Float Maximum radius for a cell Null column allowed: No Default value: -1 DEFAULT_ORTHO_FACTOR Float Default orthogonality factor Null column allowed: No Default value: 0 DEFAULT_HOGAIN_UL Float Default soft handoff gain uplink Null column allowed: No Default value: 0 ADD_MRC_SOFTERSOFT Boolean If true, gain due to MRC is taken into account for softer/soft cases Null column allowed: No Default value: False IOISNTOT Boolean Io includes pilot signal or not Null column allowed: No Default value: True 252 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure NTISNTOT Boolean Nt includes pilot signal or not Null column allowed: No Default value: False COMPRESSED_THRESHOL D Float Ec/Io threshold for compressed mode activation Null column allowed: No Default value: -13 COMPRESSED_DELTA_UL_ QUAL Float Eb/Nt UL target overhead due to compressed mode activated Null column allowed: No Default value: 1 COMPRESSED_DELTA_DL_ QUAL Float Eb/Nt DL target overhead due to compressed mode activated Null column allowed: No Default value: 1 HSDPA_NTISNTOT Boolean Nt includes or not pilot's signal for HS-SCCH, HS-PDSCH and CPICH for CQI determination Null column allowed: No Default value: False CQI_CPICH_BASED Boolean CQI determination ids based on CPICH quality (true) or on HS-PDSCH quality (false) Null column allowed: No Default value: True POWERS_RELATIVE_TO_PI LOT Boolean Cell paging and Synchro powers, Service Allowed DL min and max TCH powers are absolute values or relative to cell pilot power Null column allowed: No Default value: False COMPRESSED_ON_ECIO Boolean Compressed mode activated on Ec/Io threshold (for future use) Null column allowed: No Default value: True COMPRESSED_ON_RSCP Boolean Compressed mode activated on RSCP threshold (for future use) Null column allowed: No Default value: False RSCP_COMPRESSED_THR ESHOLD Float RSCP threshold for compressed mode activation (for future use) Null column allowed: No Default value: -100 INTERFERERS_RX_THRES H Float Interferers' reception threshold Null column allowed: Yes Default value: -130 SPREADING_WIDTH Float Spreading width (MHz) Null column allowed: Yes Default value: 3.84 PTOT_RELATIVE_TO_PMAX Boolean Cell total power is absolute value (dBm) or relative to Cell maximum power (%) Null column allowed: No Default value: False 8.4.1.6 Sites Table This table contains the physical properties of sites. Field Type Description Attributes ALTITUDE Float Real altitude Unit: m Null column allowed: Yes Default value: COMMENT_ Text (255) Additional information on the site Null column allowed: Yes Default value: LATITUDE Double Y coordinate Null column allowed: No Default value: 0 LONGITUDE Double X coordinate Null column allowed: No Default value: 0 NAME Text (50) Site name Null column allowed: No Default value: CDMA_EQUIPMENT Text (50) Equipment associated with the site Null column allowed: Yes Default value: CHANNEL_ELEMENTS_DL Integer Number of available channel elements for downlink Null column allowed: No Default value: 256 CHANNEL_ELEMENTS_UL Integer Number of available channel elements for uplink Null column allowed: No Default value: 256 PYLON_HEIGHT Float Height of the pylon at site Null column allowed: Yes Default value: 50 SUPPORT_NATURE Short The nature of site. This field is for information only Null column allowed: Yes Default value: 0 MAX_IUB_RATE_UL Float Max Iub Backhaul rate for uplink Null column allowed: Yes Default value: 12288 MAX_IUB_RATE_DL Float Max Iub Backhaul rate for downlink Null column allowed: Yes Default value: 12288 © Forsk 2009 AT281_AM_E1 253 Administrator Manual 8.4.1.7 Site List Management Tables These tables manage site lists used to filter groups of sites and transmitters. 8.4.1.7.1 SitesListsNames Table Field Type Description Attributes NAME Text (50) Name of the list Null column allowed: No 8.4.1.7.2 SitesLists Table Field Type Description Attributes LIST_NAME Text (50) First part of the unique key. Name of the list Null column allowed: No SITE_NAME Text (50) Second part of the unique key. Name of the site Null column allowed: No 8.4.1.8 Transmitter List Management Tables These tables manage transmitter lists used to filter groups of transmitters. 8.4.1.8.1 TxsListsNames Table Field Type Description Attributes NAME Text (50) Name of the transmitter list Null column allowed: No 8.4.1.8.2 TxsLists Table Field Type Description Attributes LIST_NAME Text (50) First part of the unique key. Name of the list. Null column allowed: No TX_NAME Text (50) Second part of the unique key. Name of the transmitter. Null column allowed: No 8.4.1.9 Antennas Table This table contains the description of antennas. Field Type Description Attributes Beamwidth Float Antenna beamwidth Null column allowed: Yes Default value: COMMENT_ Text (255) Additional information about antenna Null column allowed: Yes Default value: CONSTRUCTOR Text (50) Antenna manufacturer name Null column allowed: Yes Default value: DIAGRAM Binary Antenna horizontal and vertical patterns Null column allowed: Yes Default value: ELECTRICAL_TILT Float Antenna electrical tilt (for information) Null column allowed: Yes Default value: FMax Double Maximum operating frequency of the antennas Unit: MHz Null column allowed: Yes Default value: FMin Double Minimum operating frequency of the antenna Unit: MHz Null column allowed: Yes Default value: GAIN Float Antenna isotropic gain Unit: dBi Null column allowed: No Default value: 0 NAME Text (50) Name of antenna Null column allowed: No Default value: Note: • An antenna pattern described in a text format may be converted to a binary format using a converter. The format of the binary field, DIAGRAM, is detailed below. Each antenna is described by a header and a list of value pairs. - The header is defined as follows: int (32 bits) flag = 0 for omni diagrams, 1 for non-omni short (16 bits) num = number of diagrams (0,1,2,3,4) short (16 bits) siz0 = size of the first diagram (horizontal copolar section (elevation=0°)) short (16 bits) siz1 = size of second (vertical copolar section (azimuth=0°)) short (16 bits) siz2 = size of third (horizontal contrapolar) 254 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure short (16 bits) siz3 = size of fourth (vertical contrapolar) short (16 bits) prec = precision of the following angle values (=100) - Then follows the content of each of the defined diagrams ("sizx" with a value not equal to zero). - One diagram consists of a list of value pairs: one unsigned short value, the angle in degrees (multiplied by 100), so 577 means 5 degrees 77 hundredths of a degree. one short value representing the loss in dB for the given angle. - if siz2 = 5, there will be 5 pairs of values describing the third diagram. - All the lists of pairs are concatenated without a separator. 8.4.1.10 SecondaryAntennas Table This table is used to model additional antennas installed on transmitters. Field Type Description Attributes ANTENNA Text (50) Name of the antenna installed on the transmitter Null column allowed: No Default value: AZIMUT Float Second part of the unique key. Azimuth of the antenna Null column allowed: No Default value: 0 REDT Float Remote electrical tilt for secondary antenna Null column allowed: Yes Default value: 0 PERCENT_POWER Float Percentage of power dedicated to the secondary antenna Null column allowed: No Default value: 0 TILT Float Mechanical downtilt of the secondary antenna Null column allowed: No Default value: 0 TX_ID Text (50) First part of the unique key. Transmitter name Null column allowed: No Default value: 8.4.1.11 Antenna List Management Tables These tables manage antenna lists. 8.4.1.11.1 AntennasListsNames Table Field Type Description Attributes NAME Text (50) Name of the list Null column allowed: No Description Attributes 8.4.1.11.2 AntennasLists Table Field Type LIST_NAME Text (50) First part of the unique key. Name of the list Null column allowed: No SITE_NAME Text (50) Second part of the unique key. Name of the site Null column allowed: No 8.4.1.12 FrequencyBands Table This table contains the description of frequency band(s). Field Type Description Attributes NAME Text (50) Name of the frequency band Null column allowed: No Default value: FIRST_CARRIER Integer Number of the first carrier available on the network Null column allowed: Yes Default value: 0 FREQUENCY Double Average frequency of carriers Unit: MHz Null column allowed: Yes Default value: 2110 LAST_CARRIER Integer Number of the last carrier available on the network Null column allowed: Yes Default value: 0 SPREADING_WIDTH Double Spreading bandwidth definition Null column allowed: Yes Default value: 3.84 BAND_WIDTH Double Bandwidth (MHz) Null column allowed: Yes Default value: 5 © Forsk 2009 AT281_AM_E1 255 Administrator Manual 8.4.1.13 Receivers Table This table models the receiver used for raster coverage predictions. Field Type Description Attributes ADJ_CHANNEL_PROT Float Protection against interfering signals from adjacent channels. Null column allowed: No Default value: 18 ANTENNA Text (50) Receiver antenna name (if empty an omni antenna is used) Null column allowed: Yes Default value: HEIGHT Float Height of the receiver Null column allowed: No Default value: 2 LOSS Float Losses due to receiver radio equipment (up and downlink) Null column allowed: No Default value: 0 NAME Text (50) Receiver name Null column allowed: No Default value: 8.4.1.14 Equipment Management Tables These tables model TMA, feeders, and BTS equipment properties. 8.4.1.14.1 TMAEquipments Table Field Type Description Attributes DL_LOSSES Float Downlink losses of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 NAME Text (50) Name of Tower Mounted Amplifier Null column allowed: No Default value: NOISE_FIGURE Float Noise figure of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 UL_GAIN Float Uplink gain of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 8.4.1.14.2 FeederEquipments Table Field Type Description Attributes CONNECTOR_LOSSES_UL Float Feeder connector losses in uplink Null column allowed: Yes Default value: 0 CONNECTOR_LOSSES_DL Float Feeder connector losses in downlink Null column allowed: Yes Default value: 0 LOSS_PER_METER Float Feeder loss per meter Null column allowed: Yes Default value: 0 NAME Text (50) Name of Feeder Null column allowed: No Default value: 8.4.1.14.3 BTSEquipments Table Field Type Description Attributes NAME Text (50) Name of Base Station Equipment Null column allowed: No Default value: NOISE_FIGURE Float Noise figure of Base Station Null column allowed: Yes Default value: 0 CONFIG_DL_LOSSES Float Downlink losses due to the configuration of the BTS (duplexer and/or combiner) Null column allowed: Yes Default value: 0 CONFIG_UL_LOSSES Float Uplink losses due to the configuration of the BTS (duplexer and/or combiner) Null column allowed: Yes Default value: 0 RHO_FACTOR Short Rho factor to model self generated interference (100%=ideal) Null column allowed: Yes Default value: 100 256 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.4.1.15 Neighbour Management Tables 8.4.1.15.1 Neighbours Table This table stores neighbourhood relationships between cells of the same .atl document (intra-technology neighbours). Field Type Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: 1 NEIGHBOUR Text (50) Second part of the unique key. List of neighbours Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: REASON Integer Reason of the neighbourhood Null column allowed: Yes Default value: 0 (Manual) Choice list: Manual, Forced, Co-site, Adjacent, Symmetric, Distance, Coverage TRANSMITTER Text (50) First part of the unique key. Transmitters or cells Null column allowed: No Default value: TYPE Text (50) Type of the neighbourhood (handover, measurement…) Null column allowed: Yes Default value: FORCE_HHO Boolean Force Handover type to hard handover in case of intra-carriers neighbours Null column allowed: No Default value: False 8.4.1.15.2 NeighboursExt Table This table stores neighbourhood relationships between transmitters/cells of different .atl documents (inter-technology neighbours). Field Type Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: NEIGHBOUR Text (50) Second part of the unique key. List of neighbours from another project Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: REASON Integer Reason of the neighbourhood Null column allowed: Yes Default value: 0 (Manual) Choice list: Manual, Forced, Co-site, Adjacent, Symmetric, Distance, Coverage TRANSMITTER Text (50) First part of the unique key. Transmitters or cells Null column allowed: No Default value: TYPE Text (50) Type of the neighbourhood (handover, measurement…) Null column allowed: Yes Default value: 8.4.1.15.3 NeighboursConstraints Table This table enables you set handover relationships between cells. These constraints are used as input for the automatic neighbour allocation. Field Type Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: NEIGHBOUR Text (50) Second part of the unique key. List of neighbours Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: Integer Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. Null column allowed: Yes Default value: 0 Choice list: 0=Forced, 1=Forbidden STATUS © Forsk 2009 AT281_AM_E1 257 Administrator Manual TRANSMITTER Text (50) First part of the unique key. Transmitters or cells. Null column allowed: No Default value: FORCE_HHO Boolean Force Handover type to hard handover in case of intra-carriers neighbours Null column allowed: No Default value: False 8.4.1.15.4 NeighboursConstraintsExt Table This table enables you to set external handover relationships (with transmitters/cells of another project). These constraints are used as input for automatic neighbour allocation. Field Type Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: NEIGHBOUR Text (50) Second part of the unique key. List of neighbours from another project. Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: STATUS Integer Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. Null column allowed: Yes Default value: 0 Choice list: 0=Forced, 1=Forbidden TRANSMITTER Text (50) First part of the unique key. Transmitters or cells Null column allowed: No Default value: 8.4.1.16 Transmitters Table This table stores the transmitters and their properties. Field Type Description Attributes ACTIVE Boolean Transmitter activity: 'Yes' means that the transmitter is active Null column allowed: No Default value: True ANTDIVGAIN Float Antenna diversity gain Null column allowed: Yes Default value: 0 ANTENNA_NAME Text (50) Name of the main antenna installed on the transmitter Null column allowed: Yes Default value: AZIMUT Float Azimuth of the main antenna Null column allowed: Yes Default value: 0 BTS_NAME Text (50) Name of the BTS equipment Null column allowed: Yes Default value: CALC_RADIUS Integer Calculation radius used to define the calculation area Unit: m Null column allowed: Yes Default value: 4000 CALC_RADIUS2 Integer Extended calculation radius Null column allowed: Yes Default value: CALC_RESOLUTION Integer Calculation resolution Null column allowed: Yes Default value: 50 CALC_RESOLUTION2 Integer Extended calculation resolution Null column allowed: Yes Default value: CELL_SIZE Float Hexagon radius Unit: m Null column allowed: Yes Default value: 2000 COMMENT_ Text (255) Additional information about the transmitter Null column allowed: Yes Default value: DX Float X coordinate relative to the site location Null column allowed: Yes Default value: 0 DY Float Y coordinate relative to the site location Null column allowed: Yes Default value: 0 FEEDER_NAME Text (50) Name of the feeder equipment Null column allowed: Yes Default value: FEEDERLENGTH_DL Float Length of feeder in DL Null column allowed: Yes Default value: 0 FEEDERLENGTH_UL Float Length of feeder in UL Null column allowed: Yes Default value: 0 HEIGHT Float Antenna height above the ground Unit: m Null column allowed: Yes Default value: 25 HEXAGON_GROUP Text (50) Group of hexagons used to create this transmitter Null column allowed: Yes Default value: 258 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure MISCDLL Float Miscellaneous DL loss Null column allowed: Yes Default value: 0 MISCULL Float Miscellaneous UL loss Null column allowed: Yes Default value: 0 PROPAG_MODEL Text (255) Name of the propagation model used to calculate prediction Null column allowed: Yes Default value: ’Default model’ PROPAG_MODEL2 Text (255) Name of the propagation model used to calculate extended prediction Null column allowed: Yes Default value: SITE_NAME Text (50) Name of the site on which the transmitter is located (from the site table of Atoll) Null column allowed: No Default value: TILT Float Mechanical downtilt of the first antenna Null column allowed: Yes Default value: 0 TMA_NAME Text (50) Name of the TMA equipment Null column allowed: Yes Default value: TX_ID Text (50) Transmitter name Null column allowed: No Default value: FBAND Text (50) Frequency band Null column allowed: No Default value: NOISE_FIGURE Float Noise figure used to determine the thermal noise at the transmitter Null column allowed: Yes Default value: 5 RXLOSSES Float Losses in the uplink due to transmitter radio equipment Null column allowed: Yes Default value: 0 TXLOSSES Float Losses in the downlink due to transmitter radio equipment Null column allowed: Yes Default value: 0 COV_PROBA Short Cell edge Coverage probability per Transmitter Null column allowed: Yes Default value: 75 REDT Float Remote Electrical tilt Null column allowed: Yes Default value: 0 TX_DIVERSITY_CFG Short TX diversity configuration 1- No TX diversity 2- TX div. open loop 3- TX div. closed loop Null column allowed: Yes Default value: 0 CELLS_POWER_SHARING Boolean If true, cells' powers are shared for HSDPA users Null column allowed: No Default value: False TX_MAX_POWER Float Maximum power sharable between sectors Null column allowed: Yes Default value: 43 NUM_RX_ANTENNAS Short Number of transmission antenna ports available at the transmitter Null column allowed: No Default value: 1 NUM_TX_ANTENNAS Short Number of reception antenna ports available at the transmitter Null column allowed: No Default value: 1 8.4.1.17 TplTransmitters Table This table is used to store station templates and their properties. Field Type Description Attributes ACTIVE Boolean Transmitter activity: 'Yes' means that the transmitter is active Null column allowed: No ANTDIVGAIN Float Antenna diversity gain Unit: dB Null column allowed: Yes ANTENNA_NAME Text (50) Name of the main antenna installed on the transmitter Null column allowed: Yes AZIMUT Float Azimuth of the first antenna Null column allowed: Yes BTS_NAME Text (50) Name of the BTS equipment Null column allowed: Yes CALC_RADIUS Integer Calculation radius used to define each transmitter calculation area Unit: m Null column allowed: Yes CALC_RADIUS2 Integer Extended calculation radius Unit: m Null column allowed: Yes CALC_RESOLUTION Integer Calculation resolution Null column allowed: Yes CALC_RESOLUTION2 Integer Extended calculation resolution Null column allowed: Yes CELL_SIZE Float Hexagon radius Unit: m Null column allowed: Yes FEEDER_NAME Text (50) Name of the feeder equipment Null column allowed: Yes FEEDERLENGTH_DL Float Length of downlink feeder Unit: m Null column allowed: Yes © Forsk 2009 AT281_AM_E1 259 Administrator Manual FEEDERLENGTH_UL Float Length of uplink feeder Unit: m Null column allowed: Yes HEIGHT Float Antenna height above the ground Unit: m Null column allowed: Yes MAX_NEIGHB_NUMBER Short Maximum number of neighbours for the cell or the transmitter Null column allowed: Yes MAX_EXT_NEIGHB_NUMBE R Short Maximum number of inter-technology neighbours for the cell or the transmitter Null column allowed: Yes MISCDLL Float Miscellaneous downlink losses Null column allowed: Yes MISCULL Float Miscellaneous uplink losses Null column allowed: Yes NAME Text (50) Template name Null column allowed: No NUM_SECTORS Integer Number of sectors Null column allowed: Yes PROPAG_MODEL Text (255) Name of the propagation model used to calculate predictions Null column allowed: Yes PROPAG_MODEL2 Text (255) Name of the propagation model used to calculate extended prediction Null column allowed: Yes TILT Float Mechanical downtilt of the main antenna Null column allowed: Yes TMA_NAME Text (50) Name of the Tower Mounted Amplifier equipment Null column allowed: Yes CARRIERS Text (50) Carriers used by the transmitter Null column allowed: Yes FBAND Text (50) Frequency band Null column allowed: No NOISE_FIGURE Float Noise figure used to determine the thermal noise at the transmitter Null column allowed: Yes PILOT_POWER Float Power of the pilot channel Null column allowed: Yes POWER_MAX Float Maximum power supported by the transmitter Null column allowed: Yes RXLOSSES Float Losses in the uplink due to transmitter radio equipment Unit: dB Null column allowed: Yes TOTAL_POWER Float Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm Null column allowed: Yes TXLOSSES Float Losses in the downlink due to transmitter radio equipment Unit: dB Null column allowed: Yes UL_LOAD Float Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm Null column allowed: Yes CHANNEL_ELEMENTS_DL Integer Number of channel elements for downlink Null column allowed: Yes CHANNEL_ELEMENTS_UL Integer Number of channel elements for uplink Null column allowed: Yes CDMA_EQUIPMENT Text (50) CDMA equipment Null column allowed: Yes REUSE_DIST Float Minimum reuse distance for scrambling codes Null column allowed: Yes AS_THRESHOLD Float Max allowed difference with the best-server to enter the Active Set (dB) Null column allowed: Yes OTHERS_CCH_POWER Float Power of common channels (except SCH) Null column allowed: Yes SC_DOMAIN_NAME Text (50) Scrambling code domain name Null column allowed: Yes SCH_POWER Float Power of the synchronisation (SCH) channel Null column allowed: Yes COV_PROBA Short Cell edge Coverage probability per Transmitter Null column allowed: Yes REDT Float Remote Electrical tilt Null column allowed: Yes TX_DIVERSITY_CFG Integer TX diversity configuration 1- No TX diversity 2- TX div. open loop 3- TX div. closed loop Null column allowed: Yes MAX_UL_LOAD Float Maximum uplink load allowed (percentage). Used in power control simulation Null column allowed: Yes MAX_DL_LOAD Float Maximum downlink load allowed (percentage of max power used). Used in power control simulation Null column allowed: Yes HSDPA_PWR Float Amount of power (dBm) dedicated to HSDPA Null column allowed: Yes PWR_HEADROOM Float Power Control Headroom (dB) for DCH (used in WCDMA simulation algorithm) Null column allowed: Yes HSDPA_MAX_CODES Short Maximum number of HS-PDSCH codes Null column allowed: Yes MAX_INTERCAR_NEIGHB_ NB Integer Maximum number of inter-carrier neighbours for this cell Null column allowed: Yes DYN_HS_SCCH_POWER_A LLOC Boolean Allocation of power for HS-SCCH (True=Dynamic, False=Static) Null column allowed: No DYN_HSDPA_POWER_ALL OC Boolean Allocation of power for HSDPA (True=Dynamic, False=Static) Null column allowed: No HS_SCCH_POWER Float Value of power dedicated to a HS-SCCH channel. In case of dynamic allocation, it is the maximum available power. Null column allowed: Yes HSDPA_MAX_USERS Short Max number of HSDPA users managed simultaneously by the scheduler Null column allowed: Yes 260 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure HSDPA_MIN_CODES Short HSDPA_MUG_TABLE Minimum Number of HS-PDSCH codes Null column allowed: Yes Memo Lookup table giving MUG=f(#users) Null column allowed: Yes HSDPA_SCHEDULER_ALG O Short Scheduling algo used for HSDPA users. 0=MAXC/I (MAx C/I), 1=RR (Round Robin), 2=PF (Proportional Fair) Null column allowed: Yes MAX_R99BEARER_DL_RAT E Float Max bearer rate available in DL (kbps) Null column allowed: Yes MAX_R99BEARER_UL_RAT E Float Max bearer rate available in UL (kbps) Null column allowed: Yes NUM_HS_SCCH Short Number of HS_SCCH channels Null column allowed: Yes CELLS_POWER_SHARING Boolean If true, cells' powers are shared for HSDPA users Null column allowed: No HSUPA_DLPOWER Float Amount of power (dBm) dedicated to HSUPA DL chanels (E-AGCH, ERGCH, E-HICH Null column allowed: Yes HSUPA_MAX_USERS Short Max number of HSUPA users managed simultaneously by the scheduler Null column allowed: Yes NUM_HSDPA_USERS Short Number of served HSDPA users in the cell: calculated by the WCDMA simulation algorithm Null column allowed: Yes NUM_HSUPA_USERS Short Number of served HSUPA users in the cell: calculated by the WCDMA simulation algorithm Null column allowed: Yes HSUPA_UL_LOAD Float Uplink transmitter load factor due to HSUPA users: calculated by the WCDMA simulation algorithm Null column allowed: Yes TX_MAX_POWER Float Maximum power sharable between sectors. Null column allowed: Yes UL_REUSE_FACTOR Float Uplink (I intra+ I extra)/ I intra: calculated by the WCDMA simulation algorithm Null column allowed: Yes HSPA_SUPPORT Short HSPA features supported: 0: None; 1: HSDPA; 2: HSPA; 3: HSPA+ (Transmit Diversity); 4: HSPA+ (Spatial Multiplexing) Null column allowed: Yes NUM_RX_ANTENNAS Short Number of transmission antenna ports available at the transmitter Null column allowed: Yes NUM_TX_ANTENNAS Short Number of reception antenna ports available at the transmitter Null column allowed: Yes MAX_IUB_RATE_UL Float Max Iub Backhaul rate for uplink Null column allowed: Yes MAX_IUB_RATE_DL Float Max Iub Backhaul rate for downlink Null column allowed: Yes DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes 8.4.1.18 Repeaters Table This table manages repeaters and repeater properties. Field Type Description Attributes AMPLIFIER_GAIN Float Gain of the amplifier Null column allowed: Yes Default value: 80 AZIMUT Float Azimuth of the donor side antenna Null column allowed: Yes Default value: 0 DONOR_CELLID Text (50) Name of the donor cell Null column allowed: No Default value: DOWNTILT Float Downtilt of the donor side antenna Null column allowed: Yes Default value: 0 FEEDER_NAME Text (50) Name of the donor side feeder Null column allowed: Yes Default value: FEEDERLENGTH Float Length of donor side feeder Null column allowed: Yes Default value: 0 HEIGHT Float Height of the donor side antenna Null column allowed: Yes Default value: 25 REC_ANTENNA Text (50) Name of the donor side antenna Null column allowed: Yes Default value: TX_ID Text (50) Name of the transmitter (and of the transmitter used for coverage) Null column allowed: No Default value: TOTAL_GAIN Float Total gain to be applied to donor cell pilot power Null column allowed: Yes Default value: 0 DONOR_LINK_TYPE Short 1- Off air 2- Microwave 3- Fibre Null column allowed: No Default value: 1 © Forsk 2009 AT281_AM_E1 261 Administrator Manual DONOR_LINK_LOSS Float Loss (dB) between donor and donor side of the repeater Null column allowed: Yes Default value: 0 EQUIPMENT_NAME Text (50) If no equipment, the repeater is a passive component Null column allowed: Yes Default value: REC_FEEDERLENGTH_UL Float Length of donor side uplink feeder Null column allowed: Yes Default value: 0 TOTAL_GAIN_UL Float Uplink total gain to be applied to mobile output power Null column allowed: Yes Default value: 0 DONOR_PROPAG_MODEL Text (50) Name of the propagation model used to calculate prediction between donor and repeater Null column allowed: Yes Default value: Note: • 8.4.1.19 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. RepeaterEquipments Table This table models the equipment used by repeaters. Field Type Description Attributes NAME Text (50) Name of the repeater equipment Null column allowed: No Default value: MANUFACTURER Text (50) Manufacturer of the repeater equipment Null column allowed: Yes Default value: NOISE_FIGURE Float Repeater noise Figure (dB) Null column allowed: Yes Default value: 5 MIN_AMPLIFIER_GAIN Float Minimum gain of the amplifier (dB) Null column allowed: Yes Default value: 50 MAX_AMPLIFIER_GAIN Float Maximum gain of the amplifier (dB) Null column allowed: Yes Default value: 90 STEP_AMPLIFIER_GAIN Float Step of amplifier gain (dB) Null column allowed: Yes Default value: 1 MAX_OUTPUT_UL Float Maximum uplink output power (dBm) Null column allowed: Yes Default value: 12 MAX_OUTPUT_DL Float Maximum downlink output power (dBm) Null column allowed: Yes Default value: 30 TIME_DELAY Float Time delay in the equipment (microseconds) Null column allowed: Yes Default value: 5 COMMENT_ Text (255) Comments Null column allowed: Yes Default value: 8.4.1.20 Scrambling Code Management Tables These tables store constraints (the range of available scrambling codes, pairs of cells which cannot be assigned the same scrambling codes) used as input for automatic scrambling code allocation. 8.4.1.20.1 ScramblingCodesDomains Table Field Type Description Attributes DOMAIN_NAME Text (50) Resource domain name Null column allowed: No Default value: 8.4.1.20.2 ScramblingCodesGroups Table Field 262 Type Description Attributes DOMAIN_NAME Text (50) Second part of the unique key. Called grouping scheme. Set of scrambling code groups. Null column allowed: No Default value: EXCLUDED Text (225) List of codes to be excluded from the series defined by FIRST, LAST and STEP (separated by blank characters) Null column allowed: Yes Default value: EXTRA Text (225) Codes to be added. It is forbidden for EXTRA and EXLUDED to have common numbers. Separator must be a blank character. Null column allowed: Yes Default value: FIRST Integer 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 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure LAST Integer 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 NAME Text (50) First part of the unique key. Name of the scrambling code group Null column allowed: No Default value: STEP Integer 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: 1 8.4.1.20.3 Separations Table Field Type Description Attributes TX_ID Text (50) First part of the unique key. First cell name in a symmetric relation Null column allowed: No Default value: TX_ID_OTHER Text (50) Second part of the unique key. Second cell name in a symmetric relation Null column allowed: No Default value: 8.4.1.21 CDMACells Table This table stores cells and their properties. Field Type Description Attributes CARRIER Integer Carrier number Null column allowed: Yes Default value: 0 CELL_ID Text (50) Name of the cell Null column allowed: No Default value: COMMENT_ Text (255) Additional information about the cell Null column allowed: Yes Default value: MAX_NEIGHB_NUMBER Integer Maximum number of neighbours for the cell Null column allowed: Yes Default value: MAX_EXT_NEIGHB_NUMBE R Integer Maximum number of inter-technology neighbours for the cell Null column allowed: Yes Default value: PILOT_POWER Float Power of the pilot channel Null column allowed: Yes Default value: 33 POWER_MAX Float Maximum power supported by the transmitter Null column allowed: Yes Default value: 43 REUSE_DIST Float Minimum reuse distance for scrambling codes Null column allowed: Yes Default value: TOTAL_POWER Float Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm Null column allowed: Yes Default value: TX_ID Text (50) Name of the transmitter Null column allowed: No Default value: UL_LOAD Float Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm Null column allowed: Yes Default value: AS_THRESHOLD Float Maximum difference with the best-server to enter active Set (dB) Null column allowed: Yes Default value: 5 OTHERS_CCH_POWER Float Power of other common channels except SCH Null column allowed: Yes Default value: 30 SC_DOMAIN_NAME Text (50) Scrambling code domain name. Null column allowed: Yes Default value: SCH_POWER Float Power of the synchronisation (SCH) channel Null column allowed: Yes Default value: 21 SCRAMBLING_CODE Integer Scrambling code. Null column allowed: Yes Default value: MAX_UL_LOAD Float Maximum uplink load allowed (percentage). Used in power control simulation Null column allowed: Yes Default value: 75 MAX_DL_LOAD Float Maximum downlink load allowed (percentage of max power used). Used in power control simulation Null column allowed: Yes Default value: 50 HSDPA_PWR Float Amount of power (dBm) dedicated to HSDPA Null column allowed: Yes Default value: PWR_HEADROOM Float Power Control Headroom (dB) for DCH (used in WCDMA simulation algorithm) Null column allowed: Yes Default value: 0 HSDPA_MAX_CODES Short Maximum number of HS-PDSCH codes Null column allowed: Yes Default value: 16 © Forsk 2009 AT281_AM_E1 263 Administrator Manual MAX_INTERCAR_NEIGHB_ NB Integer Maximum number of inter-carrier neighbours for this cell Null column allowed: Yes Default value: DYN_HS_SCCH_POWER_A LLOC Boolean Allocation of power for HS-SCCH (True=Dynamic, False=Static) Null column allowed: No Default value: True DYN_HSDPA_POWER_ALL OC Boolean Allocation of power for HSDPA (True=Dynamic, False=Static) Null column allowed: No Default value: False HS_SCCH_POWER Float Value of power dedicated to a HS-SCCH channel. In case of dynamic allocation, it is the maximum available power. Null column allowed: Yes Default value: HSDPA_MAX_USERS Short Max number of HSDPA users managed simultaneously by the scheduler Null column allowed: Yes Default value: 64 HSDPA_MIN_CODES Short Minimum Number of HS-PDSCH codes Null column allowed: Yes Default value: 1 HSDPA_MUG_TABLE Memo Lookup table giving MUG=f(#users) Null column allowed: Yes Default value: HSDPA_SCHEDULER_ALG O Short Scheduling algo used for HSDPA users. 0=MAXC/I (MAx C/I), 1=RR (Round Robin), 2=PF (Proportional Fair) Null column allowed: Yes Default value: 2 MAX_R99BEARER_DL_RAT E Float Max bearer rate available in DL (kbps) Null column allowed: Yes Default value: 1000 MAX_R99BEARER_UL_RAT E Float Max bearer rate available in UL (kbps) Null column allowed: Yes Default value: 1000 NUM_HS_SCCH Short Number of HS-SCCH channels Null column allowed: Yes Default value: 1 ACTIVE Boolean Cell's activity: 'Yes' means that the cell is active Null column allowed: No Default value: True HSUPA_DLPOWER Float Amount of power (dBm) dedicated to HSUPA DL channels (E-AGCH, ERGCH, E-HICH) Null column allowed: Yes Default value: HSUPA_MAX_USERS Short Max number of HSUPA users managed simultaneously by the scheduler Null column allowed: Yes Default value: 15 HSUPA_UL_LOAD Float Uplink cell load factor due to HSUPA users: calculated by the WCDMA simulation algorithm Null column allowed: Yes Default value: NUM_HSDPA_USERS Short Number of served HSDPA users in the cell: calculated by the WCDMA simulation algorithm Null column allowed: Yes Default value: NUM_HSUPA_USERS Short Number of served HSUPA users in the cell: calculated by the WCDMA simulation algorithm Null column allowed: Yes Default value: UL_REUSE_FACTOR Float Uplink (I intra+ I extra)/ I intra: calculated by the WCDMA simulation algorithm Null column allowed: Yes Default value: CELL_IDENTITY Integer Cell identity Null column allowed: Yes Default value: DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes Default value: 0 HSPA_SUPPORT Short HSPA features supported: 0: None; 1: HSDPA; 2: HSPA; 3: HSPA+ (Transmit Diversity); 4: HSPA+ (Spatial Multiplexing) Null column allowed: Yes Default value: 0 UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes Default value: 0 8.4.1.22 CDMAEquipments Table This table models equipment that performs radio resource management at site level. Field Type Description Attributes CARRIER_SELECTION Short Carrier selection mode Null column allowed: No Default value: 0 Choice list: 0="min UL noise" 1= "min DL power" 2="random" CES_OVERHEAD_DL Integer Number of channel elements used for DL overhead channels (pilot, synchro, ...) Null column allowed: No Default value: 0 CES_OVERHEAD_UL Integer Number of channel elements used for UL overhead channels (pilot, synchro, ...) Null column allowed: No Default value: 0 MANUFACTURER Text (50) Name of the manufacturer Null column allowed: Yes Default value: MUD_FACTOR Float MUD factor for UL interference cancellation Null column allowed: No Default value: 0 264 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure NAME Text (50) Equipment name Null column allowed: No Default value: RAKE_EFFICIENCY Float Efficiency of the rake receiver. Used for combination of AS member contributions Null column allowed: No Default value: 1 USE_NEIGHBOURS Boolean If true, selection of AS members is limited to the neighbours of the selected transmitter Null column allowed: No Default value: False ENABLE_COMPRESSED_M ODE Boolean If true, NodeBs of the site can manage compressed mode Null column allowed: No Default value: False IUB_E1_RATE Float Supported rate per E1 line (kps) Null column allowed: Yes Default value: 2048 IUB_HSDPA_PERCENT Short Iub HSDPA Backhaul Overhead (%) Null column allowed: Yes Default value: 20 IUB_OVERHEAD_DL Float Iub Common Transport Channel Backhaul Overhead per cell (rate in kps) Null column allowed: Yes Default value: 40 8.4.1.23 CDMAEquipmentsCEsUse Table This table contains information about the consumption of channel elements. Field Type Description Attributes CHANNEL_ELTS_DL Integer Number of channel elements used for downlink Null column allowed: No Default value: 1 CHANNEL_ELTS_UL Integer Number of channel elements used for uplink Null column allowed: No Default value: 1 EQUIPMENT Text (50) First part of the unique key. Name of equipment Null column allowed: No Default value: SERVICE Text (50) Second part of the unique key. Service name. Null column allowed: No Default value: IUB_RATE_DL Float Iub backaul rate for downlink (kbps) Null column allowed: Yes Default value: 15 IUB_RATE_UL Float Iub backaul rate for uplink (kbps) Null column allowed: Yes Default value: 15 8.4.1.24 CdmaEqptsHSUPARssUse Table This table contains information about the consumption of HSUPA resources. Field Type Description Attributes BEARER_INDEX Short Cell identity Null column allowed: No Default value: CHANNEL_ELTS_UL Integer Inter-network downlink noise rise Null column allowed: Yes Default value: 1 EQUIPMENT Text (50) Name of the site equipment Null column allowed: No Default value: IUB_RATE_UL Float Inter-network uplink noise rise Null column allowed: Yes Default value: 15 8.4.1.25 Multi-Service Traffic Management These tables contain descriptions of multi-service traffic data, i.e., services, mobility types, terminals, user profiles, and environments. 8.4.1.25.1 UMTSEnvironmentDefs Table Field Type Description Attributes DENSITY Float Number of subscribers per km2 Null column allowed: Yes Default value: 0 ENVIRONMENT Text (50) Environment name Null column allowed: No Default value: MOBILITY Text (50) Type of mobility Null column allowed: No Default value: USER_PROFILE Text (255) Type of user profile Null column allowed: No Default value: © Forsk 2009 AT281_AM_E1 265 Administrator Manual 8.4.1.25.2 UMTSMobility Table Field Type Description Attributes NAME Text (50) Type of mobility Null column allowed: No Default value: TADD Float Minimum Ec/Io for best server selection Null column allowed: No Default value: MEAN_SPEED Float Mean mobile speed (km/h) used for HSDPA Null column allowed: Yes Default value: 0 HSSCCH_ECNT Float HS-SCCH Ec/Nt target for HSDPA Null column allowed: Yes Default value: -12 8.4.1.25.3 UMTSServicesQuality Table Field Type Description Attributes MOBILITY Text (50) Second part of the unique key. Type of mobility Null column allowed: No Default value: SERVICE Text (50) First part of the unique key. Name of the R99 Bearer Null column allowed: No Default value: DL_TARGET_QUAL Float Eb/Nt target on the downlink for a type of mobility Null column allowed: Yes Default value: 0 UL_TARGET_QUAL Float Eb/Nt target on the uplink for a type of mobility Null column allowed: Yes Default value: 0 UL_TGT_QUAL_DIV2RX Float Eb/Nt target on uplink in case of 2RX diversity Null column allowed: Yes Default value: 0 UL_TGT_QUAL_DIV4RX Float Eb/Nt target on uplink in case of 4RX diversity Null column allowed: Yes Default value: 0 DL_TGT_QUAL_DIVOPEN Float Eb/Nt target on downlink in case of TX diversity open loop Null column allowed: Yes Default value: 0 DL_TGT_QUAL_DIVCLOSE D Float Eb/Nt target on downlink in case of TX diversity closed loop Null column allowed: Yes Default value: 0 RX_EQUIP Text (50) Type of receiver Null column allowed: No Default value: “Standard” 8.4.1.25.4 UMTSServicesUsage Table Field Type Description Attributes CALL_DURATION Float Average duration of a call (for circuit switched services) Unit: s Null column allowed: Yes Default value: CALL_NUMBER Float Average number of calls per hour for circuit switched services or average number of sessions per hour for packet switched services Null column allowed: Yes Default value: 0 SERVICE Text (50) Service that the subscriber may request Null column allowed: No Default value: TERMINAL Text (50) Type of terminal used by the subscriber for the service Null column allowed: No Default value: USER_PROFILE Text (255) User profile name Null column allowed: No Default value: DL_VOLUME Float Data volume transferred on the downlink during a session (for packet switched services) Unit: Kbyte Null column allowed: Yes Default value: UL_VOLUME Float Data volume transferred on the uplink during a session (for packet switched services) Unit: Kbyte Null column allowed: Yes Default value: 8.4.1.25.5 UMTSServices Table Field 266 Type Description Attributes BODY_LOSS Float Body loss Null column allowed: No Default value: 0 NAME Text (50) Service name Null column allowed: No Default value: PRIORITY Integer Priority level of the service: parameter used in the WCDMA simulation Null column allowed: Yes Default value: 0 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure USE_HANDOFF Boolean 'Yes' if the service supports soft handoff Null column allowed: No Default value: False DL_ACTIVITY Float Activity factor for circuit switched service on the downlink Null column allowed: Yes Default value: DL_PACKET_EFFICIENCY Float Packet efficiency factor on the downlink Null column allowed: Yes Default value: UL_ACTIVITY Float Activity factor for circuit switched service on the uplink Null column allowed: Yes Default value: UL_PACKET_EFFICIENCY Float Packet efficiency factor on the uplink Null column allowed: Yes Default value: CARRIER Integer Carrier supporting the service. -1 means that all carriers can be used. Null column allowed: No Default value: -1 TH_SCALE_FACTOR Float Ratio between application throughput and RLC layer throughput Null column allowed: No Default value: 95 TH_OFFSET Float Offset to add to the above ratio Null column allowed: No Default value: 0 ENABLE_HSDPA Boolean Service can use HSDPA channels Null column allowed: No Default value: False UL_NPC Integer Number of packet calls during a session on the uplink Null column allowed: Yes Default value: 1 UL_DPC Float Reading time (distance) between two packet calls (ms) on the uplink Null column allowed: Yes Default value: 0 UL_DP Float Packet inter arrival time (ms) on the uplink Null column allowed: Yes Default value: 0 UL_SP Integer Packet size (Bytes) on the uplink Null column allowed: Yes Default value: 1500 UL_SPC_MIN Float Uplink min Packet call size (kBytes) Null column allowed: Yes Default value: 4 UL_SPC_MAX Float Uplink max Packet call size (kBytes) Null column allowed: Yes Default value: 2000 DL_NPC Integer Number of packet calls during a session on the downlink Null column allowed: Yes Default value: 1 DL_DPC Float Reading time (distance) between two packet calls (ms) on the downlink Null column allowed: Yes Default value: 0 DL_DP Float Packet inter arrival time (ms) on the downlink Null column allowed: Yes Default value: 0 DL_SP Integer Packet size (Bytes) on the downlink Null column allowed: Yes Default value: 1500 DL_SPC_MIN Float Downlink min Packet call size (kBytes) Null column allowed: Yes Default value: 4 DL_SPC_MAX Float Downlink max Packet call size (kBytes) Null column allowed: Yes Default value: 2000 R99BEARER Text (50) Name of the R99 Bearer Null column allowed: Yes Default value: REQ_AVERAGE_DL_RATE Float Requested Average Downlink Rate (kbps) Null column allowed: Yes Default value: REQ_AVERAGE_UL_RATE Float Requested Average Uplink Rate (kbps) Null column allowed: Yes Default value: ENABLE_HSUPA Boolean If trure, the service can use HSUPA channels Null column allowed: No Default value: False ENABLE_DOWNGRADING Boolean Service supports lower bearer than nominal bearer Null column allowed: No Default value: True TYPE Short Type of service (0: circuit; 1: packet; 2: circuit over packet) Null column allowed: No Default value: 0 8.4.1.25.6 R99Bearers Table Field Type Description Attributes DL_CODING_FACTOR Float Coding Factor downlink Null column allowed: Yes Default value: 1 DL_NOMINAL_BIT_RATE Float Bearer nominal rate in downlink Unit: kbps Null column allowed: Yes Default value: 9.6 © Forsk 2009 AT281_AM_E1 267 Administrator Manual DPCCH_DPCH_RATIO_DL Float Ratio between DPCCH and DPCH powers in DL Null column allowed: Yes Default value: 0 DPCCH_DPCH_RATIO_UL Float Ratio between DPCCH and DPCH powers in UL Null column allowed: Yes Default value: 0 NAME Text (50) Bearer name Null column allowed: No Default value: PTCH_MAX Float For DL part of Bearer: Maximum transmitter power on traffic channel for the bearer not to exceed Null column allowed: Yes Default value: 21 PTCH_MIN Float For DL part of Bearer: Minimum transmitter power on traffic channel for the bearer not to exceed Null column allowed: Yes Default value: -20 TYPE Short Bearer type (0: Empty, 1: Interactive, 2: Conversational, 3: Background ,4: Streaming) Null column allowed: Yes Default value: 0 UL_CODING_FACTOR Float Coding Factor in uplink Null column allowed: Yes Default value: 1 UL_NOMINAL_BIT_RATE Float Bearer nominal rate in uplink Unit: kbps Null column allowed: Yes Default value: 9.6 ACTIVE_SPREADING_FACT OR_DL Integer DL Spreading Factor for active users Null column allowed: Yes Default value: 256 INACTIVE_SPREADING_FA CTOR_DL Integer DL Spreading Factor for inactive users Null column allowed: Yes Default value: 256 8.4.1.25.7 HSDPA Bearers Modelling Tables These tables model HSDPA service bearers. HSDPABearers Table Field Type Description Attributes BEARER_INDEX Short Unique key to address bearer Null column allowed: No Default value: 1 TRANSPORT_BL_SIZE Integer Transport Block Size (bits) Null column allowed: Yes Default value: 0 HSPDSCH_NUM Short Number of HS_PDSCH channels used Null column allowed: Yes Default value: 5 RLC_PEAK_THROUGHPUT Float Peak RLC throughput (without BLER consideration) Null column allowed: Yes Default value: 0 MODULATION Short Modulation (0: QPSK; 1: 16QAM; 2: 64QAM) Null column allowed: No Default value: 0 HSDPABearerSelectTables Table Field Type Description Attributes MOBILITY Text (50) UE mobility Null column allowed: Yes Default value: RX_EQUIP Text (50) Type of receiver of the User Equipment Null column allowed: Yes Default value: “Standard” CQI_TABLE Memo Tables CQI=f(Quality) , Quality defined by CQI_CPICH_BASED in Networks table Null column allowed: Yes Default value: BEST_BEARER_TABLE Memo Tables BEST_BEARER_INDEX=f(CQI_HSPDSCH) Null column allowed: Yes Default value: HSDPAQualityTables Table Field 268 Type Description Attributes BEARER_INDEX Short Bearer index Null column allowed: No Default value: 0 QI_NAME Text (50) Name of the Quality Indicator Null column allowed: No Default value: RX_EQUIP Text (50) Type of receiver of the User Equipment Null column allowed: No Default value: “Standard” AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure MOBILITY Text (50) UE mobility Null column allowed: Yes Default value: DL_QI_TABLE Memo QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table Null column allowed: Yes Default value: 8.4.1.25.8 HSUPA Bearers Modelling Tables These tables model HSUPA service bearers. HSUPABearers Table Field Type Description Attributes BEARER_INDEX Short Index of the bearer Null column allowed: No Default value: EDPDCH_NUM Short Number of E-DPDCH codes used Null column allowed: Yes Default value: MIN_SF Integer Smallest Spreading Factor Null column allowed: Yes Default value: RLC_PEAK_RATE Float Peak RLC throughput (without BLER) Null column allowed: Yes Default value: TRANSPORT_BL_SIZE Integer Transport Block Size (bits) Null column allowed: Yes Default value: TTI_LENGTH Float Duration of TTI (ms) Null column allowed: Yes Default value: MODULATION Short Modulation (0: QPSK; 1: 16QAM) Null column allowed: No Default value: 0 HSUPABearerSelection Table Field Type Description Attributes BEARER_INDEX Short Index of the selected bearer Null column allowed: Yes Default value: 0 EARLY_TERM_TABLE Memo Tables of probabilities of earlier termination=f(REPEAT_NUM) Null column allowed: Yes Default value: EC_NT_REQ Float Required E-DPDCH Ec/Nt Null column allowed: Yes Default value: MOBILITY Text (50) User’s mobility Null column allowed: Yes Default value: REPEAT_NUM Integer Number of retransmissions to ensure a correct transmission Null column allowed: Yes Default value: 1 RX_EQUIP Text (50) Reception equipment of the terminal Null column allowed: Yes Default value: "Standard" HSUPAQualityTables Table Field Type Description Attributes BEARER_INDEX Short Bearer index Null column allowed: No Default value: 0 MOBILITY Text (50) User’s mobility Null column allowed: Yes Default value: QI_NAME Text (50) Name of the Quality Indicator Null column allowed: No Default value: REPEAT_NUM Integer Number of retransmissions to ensure a correct transmission Null column allowed: Yes Default value: 1 RX_EQUIP Text (50) Reception equipment of the terminal Null column allowed: No Default value: "Standard" UL_QI_TABLE Memo QI=f(MEAS_PARAM), where MEAS_PARAM is read from the QualityIndicators table Null column allowed: Yes Default value: 8.4.1.25.9 © Forsk 2009 UMTSTerminals Table Field Type Description Attributes GAIN Float Receiver antenna gain Null column allowed: Yes Default value: 0 AT281_AM_E1 269 Administrator Manual LOSS Float Receiver antenna loss Null column allowed: Yes Default value: 0 NAME Text (50) Terminal name Null column allowed: No Default value: NOISE_FACTOR Float Noise figure used to determine the thermal noise at the receiver Null column allowed: Yes Default value: 8 PMAX Float Maximum receiver power on traffic channel Null column allowed: Yes Default value: 21 PMIN Float Minimum receiver power on traffic channels Null column allowed: Yes Default value: -20 RAKE_EFFICIENCY Float Efficiency of the rake receiver. Used for combination of Active Set member contributions Null column allowed: Yes Default value: 1 ACTIVE_SET_SIZE Short Maximum number of transmitters possibly connected to the receiver Null column allowed: No Default value: 3 ENABLE_COMPRESSED_M ODE Boolean If true, the mobile connected to a compressed-mode-capable NodeB is able to manage compressed mode when necessary Null column allowed: No Default value: False RHO_FACTOR Short Rho factor to model self generated interference Null column allowed: No Default value: 100 UE_CATEGORY Short Category of the User Equipment for HSDPA Null column allowed: Yes Default value: 1 RX_EQUIP Text (50) Type of the User Equipment Receiver Null column allowed: Yes Default value: “Standard” MUD_FACTOR Float Advanced Receiver Factor to model intra-cell interference reduction for HSDPA terminals only Null column allowed: Yes Default value: 0 HSUPA_UE_CATEGORY Short Category of the User Equipment for HSUPA Null column allowed: Yes Default value: 1 PRIMARY_BAND Text (50) Primary frequency band Null column allowed: Yes Default value: SECONDARY_BAND Text (50) Secondary frequency band Null column allowed: Yes Default value: NOISE_FACTOR_SEC Float Noise figure used to determine the thermal noise at the receiver (for the secondary frequency band) Null column allowed: Yes Default value: 8 HSPA_SUPPORT Short HSPA features supported: 0: None; 1: HSDPA; 2: HSPA Null column allowed: No Default value: 0 NUM_RX_ANTENNAS Short Number of reception antenna ports available at the terminal Null column allowed: No Default value: 1 HSUPA_DTX_SUPPORT Boolean Whether the terminal supports discontinuous DPCCH transmission or not Null column allowed: No Default value: False 8.4.1.25.10 UMTSTraficEnvironments Table Field Type Description Attributes CLUTTER_WEIGHTS Binary Internal binary format describing weights assigned to each clutter class Null column allowed: Yes Default value: Yes NAME Text (50) Name of the created environment Null column allowed: No Default value: 8.4.1.25.11 Field NAME 8.4.1.26 UMTSUserProfiles Table Type Text (50) Description Attributes Name of the created user profile Null column allowed: No Default value: ServiceQualityTables Table This table stores the quality graphs used for different reception equipment and quality indicators. 270 Field Type Description Attributes SERVICE Text (50) Name of the service (can be null for some QI) Null column allowed: No Default value: QI_NAME Text (50) Name of the Quality Indicator Null column allowed: No Default value: RX_EQUIP Text (50) Type of receiver of the User Equipment Null column allowed: No Default value: “Standard” AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure MOBILITY Text (50) UE mobility Null column allowed: Yes Default value: DL_QI_TABLE Memo QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table Null column allowed: Yes Default value: UL_QI_TABLE Memo QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table Null column allowed: Yes Default value: 8.4.1.27 QualityIndicators Table This table is used by Quality Indicator (FER, BER, BLER, etc.) coverage predictions. Field Type Description Attributes NAME Text (20) Name of the managed quality indicator Null column allowed: No Default value: PS_QI Boolean Flag which indicates if this indicator is used for PS services Null column allowed: No Default value: True CS_QI Boolean Flag which indicates if this indicator is used in CS services Null column allowed: No Default value: True MEAS_PARAM Short Name of the measured figure used for this QI determination Null column allowed: Yes Default value: 1 Choice list: CPICH_ECIO=1, CPICH_CI=2, CPICH_ECNT=3, DCH_EBNT=4, HSPDSCH_ECNT=5 USE_INTERPOLATION Boolean Flag which indicates if this QI must be interpolated or not Null column allowed: No Default value: True 8.4.1.28 UERxEquipments Table This table contains a list of UE reception equipment. Field Type Description Attributes NAME Text (50) Name of the type of receiver in the UE Null column allowed: No Default value: 8.4.1.29 UECategories Table This table models HSDPA UE categories. Field Type Description Attributes UE_CATEGORY Short UE category for HSDPA Null column allowed: No Default value: MAX_HSPDSCH_NUM Short Maximum number of HS-PDSCH channels for HSDPA Null column allowed: Yes Default value: 5 MIN_INTERTTI_NUM Short Minimum number of TTI between two TTI used Null column allowed: Yes Default value: 1 MAX_BLOCK_SIZE Integer Maximum transport block size supported (bits) Null column allowed: Yes Default value: 26000 MIMO_SUPPORT Short MIMO support (0: None; 1: MIMO) Null column allowed: No Default value: 0 MODULATION Short Modulation (0: QPSK; 1: 16QAM; 2:64QAM) Null column allowed: No Default value: 0 8.4.1.30 HSUPAUECategories Table This table models HSUPA UE categories. Field Type Description Attributes MAX_BLOCK_SIZE_10MS Integer Maximum transport block size supported for TTI=10ms (bits) Null column allowed: Yes Default value: MAX_BLOCK_SIZE_2MS Integer Maximum transport block size supported for TTI=2ms (bits) Null column allowed: Yes Default value: MAX_EDPDCH_NUM Short Maximum number of E-DPDCH codes for HSUPA Null column allowed: Yes Default value: © Forsk 2009 AT281_AM_E1 271 Administrator Manual MIN_SF Integer Smallest Spreading Factor supported Null column allowed: Yes Default value: TTI_2MS Boolean True if TTI=2ms is supported Null column allowed: No Default value: False UE_CATEGORY Short UE category for HSUPA Null column allowed: No Default value: MODULATION Short Modulation (0: QPSK; 1: 16QAM) Null column allowed: No Default value: 0 8.4.1.31 InterfReductionFactors Table This table stores the interference reduction factors between carriers. Field Type Description Attributes CARRIER1 Integer First carrier Null column allowed: No Default value: 0 CARRIER2 Integer Second carrier Null column allowed: No Default value: 0 FACTOR Double Interference reduction factor Null column allowed: No Default value: 200 8.4.1.32 HSPAMIMOConfigs Table This table contains the HSPA MIMO gains for different reception equipment. Field Type Description Attributes DL_DIVERSITY_GAIN Float Downlink diversity gain (D-TxAA) Null column allowed: Yes Default value: 0 HSDPA_BEARER_INDEX Short HSDPA Bearer index Null column allowed: Yes Default value: 0 MAX_MIMO_GAIN_TABLE Memo Maximum spatial multiplexing capacity gain graphs Null column allowed: Yes Default value: MIMO_RX_ANTENNAS Short Number of reception antennas used for MIMO Null column allowed: Yes Default value: 1 MIMO_TX_ANTENNAS Short Number of transmission antennas used for MIMO Null column allowed: Yes Default value: 1 MOBILITY Text (50) UE mobility Null column allowed: Yes Default value: RX_EQUIP Text (50) Type of receiver of the User Equipment Null column allowed: No Default value: ’Standard’ 8.4.1.33 InterNetChProtect Table This table stores the inter-network channel protection graphs. 272 Field Type Description Attributes ICP Memo Inter-network channel protection = f(  MHz) Null column allowed: Yes Default value: ITF_BW Double Interfering bandwidth (kHz) Null column allowed: No Default value: 0 ITF_TECHNO Text (50) Interfering technology Null column allowed: No Default value: V_BW Double Victim bandwidth (kHz) Null column allowed: No Default value: 0 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.5 CDMA2000 1xRTT 1xEV-DO Template Figure 8.8: on page 273, Figure 8.9: on page 274, and Figure 8.10: on page 275 depict the CDMA2000 1xRTT 1xEV-DO database structure. Figure 8.8: CDMA2000 1xRTT 1xEV-DO Template - 1 © Forsk 2009 AT281_AM_E1 273 Administrator Manual Figure 8.9: CDMA2000 1xRTT 1xEV-DO Template - 2 274 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure Figure 8.10: CDMA2000 1xRTT 1xEV-DO Templates - 3 © Forsk 2009 AT281_AM_E1 275 Administrator Manual 8.5.1 CDMA2000 1xRTT 1xEV-DO Tables The CDMA2000 1xRTT 1xEV-DO project template has the following data structure. 8.5.1.1 PropagationModels Table This table contains propagation model description, formulas, and parameters. Field Type Description Attributes Data Binary Model specific parameters Null column allowed: Yes Description Text (255) User defined Null column allowed: Yes Name Text (50) Name of the propagation model Null column allowed: No Signature Text (40) Unique Global ID of last model update Null column allowed: No Type Text (50) ProgID of the model Null column allowed: No 8.5.1.2 CustomFields Table This table enables you to define default values for all the fields of all the tables in Atoll, including user-defined fields added to different tables. It also enables you to define choice lists, a caption, and a group name for user-defined fields. Field Type Description Attributes CHOICE_LIST Memo Choice list for the field Null column allowed: Yes COLUMN_NAME Text (50) Second part of the unique key. Field name Null column allowed: No DEFAULT_VALUE Text (50) Default value for the field Null column allowed: Yes TABLE_NAME Text (50) First part of the unique key. Table name Null column allowed: No CAPTION Text (50) Caption of the field (displayed instead of the name) Null column allowed: Yes GROUP_NAME Text (50) Name of the group to which that field belongs Null column allowed: Yes The default values defined in this table have priority over the internal predefined default values (hard-coded in Atoll or defined in the database table structure). In order for Atoll to correctly consider the new default values, note that: • • 8.5.1.3 If you use floating point values, ensure that all the users have the same decimal separator (comma or point). The field names are case sensitive. CoordSys Table This table stores descriptions of the projection coordinate system and database’s internal coordinate system (the display coordinate system used when creating database). Field 276 Type Description Attributes CODE Integer Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768) Null column allowed: No Default value: 0 DATUM_CODE Double DATUM_ROTX Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_ROTY Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_ROTZ Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_SCALE Double Parts per million (ppm) Null column allowed: Yes Default value: 0 DATUM_SHIFTX Double Meters Null column allowed: Yes Default value: 0 DATUM_SHIFTY Double Meters Null column allowed: Yes Default value: 0 DATUM_SHIFTZ Double Meters Null column allowed: Yes Default value: 0 ELLIPS_CODE Integer ELLIPS_RMAJOR Double Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Meters AT281_AM_E1 Null column allowed: Yes Default value: 0 © Forsk 2009 Chapter 8: Database Structure ELLIPS_RMINOR Double Meters Null column allowed: Yes Default value: 0 NAME Text (50) Coordinate system name Null column allowed: No Default value: PROJ_ANGLE Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_FALSE_EASTING Double Meters Null column allowed: Yes Default value: 0 PROJ_FALSE_NORTHING Double Meters Null column allowed: Yes Default value: 0 PROJ_FIRST_PARALLEL Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_LATITUDE_ORIGIN Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_LONGITUDE_ORIGIN Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_METHOD Short Undefined, NoProjection, Lambert1SP, Lambert2SP, Mercator, CassiniSoldner, TransMercator, TransMercatorSO, ObliqueStereographic, NewZealandMapGrid, HotineOM, LabordeOM, SwissObliqueCylindical, UTM Null column allowed: Yes Default value: 0 PROJ_SCALE_FACTOR Double PROJ_SECOND_PARALLEL Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_ZONE_NUMBER Integer Used with UTM Null column allowed: Yes Default value: 0 8.5.1.4 Null column allowed: Yes Default value: 0 Units Table This table stores the identification numbers of reception and transmission units, projection coordinate system specified in the .atl document and the database internal coordinate system. Field Type Description Attributes COORD_SYSTEM Integer Display coordinate system when creating database Null column allowed: Yes Default value: -1 PROJECTION Integer Projected coordinate system for geo data Null column allowed: Yes Default value: -1 Reception unit when creating database Null column allowed: No Default value: 0 Choice list: 0=dBm, 1=dbµV, 2=dbµV/m RECEPTION_UNIT Integer TRANSMISSION_UNIT Integer Transmission unit when creating database Null column allowed: No Default value: 0 Choice list: 0=dBm, 1=Watts, 2=kWatts GAIN_UNIT Integer Unit used for gains (dBd or dBi) Null column allowed: Yes Default value: 0 Choice list: 0= dBd, 1= dBi 8.5.1.5 Networks Table This table contains network-level properties and network-specific data. Field Type Description Attributes Null column allowed: No Default value: NAME Text (50) TECHNOLOGY Text (10) Name of the technology Null column allowed: No Default value: ‘CDMA’ SYSTEM_ Text (50) Name of the system Null column allowed: No Default value: ‘1xRTT’ DEFAULT_RESOLUTION Float Default calculation resolution Null column allowed: No Default value: 50 DEFAULT_MODEL Text (50) Default propagation model Null column allowed: Yes Default value: ‘Cost-Hata’ © Forsk 2009 AT281_AM_E1 277 Administrator Manual SHARED_RESULTS_FOLDE Text (255) R Shared results storage folder Null column allowed: Yes Default value: DMAX Float Maximum radius for a cell Null column allowed: No Default value: -1 DEFAULT_ORTHO_FACTOR Float Default orthogonality factor Null column allowed: No Default value: 0 DEFAULT_HOGAIN_UL Float Default soft handoff gain uplink Null column allowed: No Default value: 0 ADD_MRC_SOFTERSOFT Boolean If true, gain due to MRC is taken into account for softer/soft cases Null column allowed: No Default value: False IOISNTOT Boolean Io includes pilot signal or not Null column allowed: No Default value: True NTISNTOT Boolean Nt includes pilot signal or not Null column allowed: No Default value: False POWERS_RELATIVE_TO_PI LOT Boolean Cell paging and Synchro powers, Service Allowed DL min and max TCH powers are absolute values or relative to cell pilot power Null column allowed: No Default value: False UC_PWC_ON_PILOT Boolean True if uplink power control is based on pilot’s target Null column allowed: No Default value: False INTERFERERS_RX_THRES H Float Interferers' reception threshold Null column allowed: Yes Default value: -130 SPREADING_WIDTH Float Spreading width (MHz) Null column allowed: Yes Default value: 1.2288 PTOT_RELATIVE_TO_PMAX Boolean Cell total power is absolute value (dBm) or relative to Cell maximum power (%) Null column allowed: No Default value: False 8.5.1.6 Sites Table This table contains the physical properties of sites. Field Type Description Attributes ALTITUDE Float Real altitude Unit: m Null column allowed: Yes Default value: COMMENT_ Text (255) Additional information on the site Null column allowed: Yes Default value: LATITUDE Double Y coordinate Null column allowed: No Default value: 0 LONGITUDE Double X coordinate Null column allowed: No Default value: 0 NAME Text (50) Site name Null column allowed: No Default value: CDMA_EQUIPMENT Text (50) Equipment associated with the site Null column allowed: Yes Default value: CHANNEL_ELEMENTS_DL Integer Number of available channel elements for downlink Null column allowed: Yes Default value: 256 CHANNEL_ELEMENTS_UL Integer Number of available channel elements for uplink Null column allowed: Yes Default value: 256 EVDO_CES Integer Number of EVDO CEs per carrier Null column allowed: Yes Default value: 96 PYLON_HEIGHT Float Height of the pylon at site Null column allowed: Yes Default value: 50 SUPPORT_NATURE Short The nature of site. This field is for information only Null column allowed: Yes Default value: 0 8.5.1.7 Site List Management Tables These tables manage site lists used to filter groups of sites and transmitters. 8.5.1.7.1 278 SitesListsNames Table Field Type Description Attributes NAME Text (50) Name of the list Null column allowed: No AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.5.1.7.2 SitesLists Table Field Type Description Attributes LIST_NAME Text (50) First part of the unique key. Name of the list Null column allowed: No SITE_NAME Text (50) Second part of the unique key. Name of the site Null column allowed: No 8.5.1.8 Transmitter List Management Tables These tables manage transmitter lists used to filter groups of transmitters. 8.5.1.8.1 TxsListsNames Table Field Type Description Attributes NAME Text (50) Name of the transmitter list Null column allowed: No Description Attributes 8.5.1.8.2 TxsLists Table Field Type LIST_NAME Text (50) First part of the unique key. Name of the list. Null column allowed: No TX_NAME Text (50) Second part of the unique key. Name of the transmitter. Null column allowed: No 8.5.1.9 Antennas Table This table contains the description of antennas. Field Type Description Attributes Beamwidth Float Antenna beamwidth Null column allowed: Yes Default value: COMMENT_ Text (255) Additional information about antenna Null column allowed: Yes Default value: CONSTRUCTOR Text (50) Antenna manufacturer name Null column allowed: Yes Default value: DIAGRAM Binary Antenna horizontal and vertical patterns Null column allowed: Yes Default value: ELECTRICAL_TILT Float Antenna electrical tilt (for information) Null column allowed: Yes Default value: FMax Double Maximum operating frequency of the antennas Unit: MHz Null column allowed: Yes Default value: FMin Double Minimum operating frequency of the antenna Unit: MHz Null column allowed: Yes Default value: GAIN Float Antenna isotropic gain Unit: dBi Null column allowed: No Default value: 0 NAME Text (50) Name of antenna Null column allowed: No Default value: Note: • An antenna pattern described in a text format may be converted to a binary format using a converter. The format of the binary field, DIAGRAM, is detailed below. Each antenna is described by a header and a list of value pairs. - The header is defined as follows: int (32 bits) flag = 0 for omni diagrams, 1 for non-omni short (16 bits) num = number of diagrams (0,1,2,3,4) short (16 bits) siz0 = size of the first diagram (horizontal copolar section (elevation=0°)) short (16 bits) siz1 = size of second (vertical copolar section (azimuth=0°)) short (16 bits) siz2 = size of third (horizontal contrapolar) short (16 bits) siz3 = size of fourth (vertical contrapolar) short (16 bits) prec = precision of the following angle values (=100) - Then follows the content of each of the defined diagrams ("sizx" with a value not equal to zero). - One diagram consists of a list of value pairs: one unsigned short value, the angle in degrees (multiplied by 100), so 577 means 5 degrees 77 hundredths of a degree. one short value representing the loss in dB for the given angle. © Forsk 2009 AT281_AM_E1 279 Administrator Manual - if siz2 = 5, there will be 5 pairs of values describing the third diagram. - All the lists of pairs are concatenated without a separator. 8.5.1.10 SecondaryAntennas Table This table is used to model additional antennas installed on transmitters. Field Type Description Attributes ANTENNA Text (50) Name of the antenna installed on the transmitter Null column allowed: No Default value: AZIMUT Float Second part of the unique key. Azimuth of the antenna Null column allowed: No Default value: 0 REDT Float Remote electrical tilt for secondary antenna Null column allowed: Yes Default value: 0 PERCENT_POWER Float Percentage of power dedicated to the secondary antenna Null column allowed: No Default value: 0 TILT Float Mechanical downtilt of the secondary antenna Null column allowed: No Default value: 0 TX_ID Text (50) First part of the unique key. Transmitter name Null column allowed: No Default value: 8.5.1.11 Antenna List Management Tables These tables manage antenna lists. 8.5.1.11.1 AntennasListsNames Table Field Type Description Attributes NAME Text (50) Name of the list Null column allowed: No Description Attributes 8.5.1.11.2 AntennasLists Table Field Type LIST_NAME Text (50) First part of the unique key. Name of the list Null column allowed: No SITE_NAME Text (50) Second part of the unique key. Name of the site Null column allowed: No 8.5.1.12 FrequencyBands Table This table contains the description of frequency band(s). Field Type Description Attributes NAME Text (50) Name of the frequency band Null column allowed: No Default value: FIRST_CARRIER Integer Number of the first carrier available on the network Null column allowed: Yes Default value: 0 FREQUENCY Double Average frequency of carriers Unit: MHz Null column allowed: Yes Default value: 2110 LAST_CARRIER Integer Number of the last carrier available on the network Null column allowed: Yes Default value: 0 SPREADING_WIDTH Double Spreading bandwidth definition Null column allowed: Yes Default value: 1.2288 BAND_WIDTH Double Bandwidth (MHz) Null column allowed: Yes Default value: 5 8.5.1.13 Receivers Table This table models the receiver used for raster coverage predictions. Field Type Description Attributes ADJ_CHANNEL_PROT Float Protection against interfering signals from adjacent channels. Null column allowed: No Default value: 18 ANTENNA Text (50) Receiver antenna name (if empty an omni antenna is used) Null column allowed: Yes Default value: HEIGHT Float Height of the receiver Null column allowed: No Default value: 2 280 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure LOSS Float Losses due to receiver radio equipment (up and downlink) Null column allowed: No Default value: 0 NAME Text (50) Receiver name Null column allowed: No Default value: 8.5.1.14 Equipment Management Tables These tables model TMA, feeders, and BTS equipment properties. 8.5.1.14.1 TMAEquipments Table Field Type Description Attributes DL_LOSSES Float Downlink losses of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 NAME Text (50) Name of Tower Mounted Amplifier Null column allowed: No Default value: NOISE_FIGURE Float Noise figure of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 UL_GAIN Float Uplink gain of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 8.5.1.14.2 FeederEquipments Table Field Type Description Attributes CONNECTOR_LOSSES_UL Float Feeder connector losses in uplink Null column allowed: Yes Default value: 0 CONNECTOR_LOSSES_DL Float Feeder connector losses in downlink Null column allowed: Yes Default value: 0 LOSS_PER_METER Float Feeder loss per meter Null column allowed: Yes Default value: 0 NAME Text (50) Name of Feeder Null column allowed: No Default value: 8.5.1.14.3 BTSEquipments Table Field Type Description Attributes NAME Text (50) Name of Base Station Equipment Null column allowed: No Default value: NOISE_FIGURE Float Noise figure of Base Station Null column allowed: Yes Default value: 0 CONFIG_DL_LOSSES Float Downlink losses due to the configuration of the BTS (duplexer and/or combiner) Null column allowed: Yes Default value: 0 CONFIG_UL_LOSSES Float Uplink losses due to the configuration of the BTS (duplexer and/or combiner) Null column allowed: Yes Default value: 0 RHO_FACTOR Short Rho factor to model self generated interference (100%=ideal) Null column allowed: Yes Default value: 100 8.5.1.15 Neighbour Management Tables 8.5.1.15.1 Neighbours Table This table stores neighbourhood relationships between cells of the same .atl document (intra-technology neighbours). Field Type Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: 1 NEIGHBOUR Text (50) Second part of the unique key. List of neighbours Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: Reason of the neighbourhood Null column allowed: Yes Default value: 0 (Manual) Choice list: Manual, Forced, Co-site, Adjacent, Symmetric, Distance, Coverage REASON © Forsk 2009 Integer AT281_AM_E1 281 Administrator Manual TRANSMITTER Text (50) First part of the unique key. Transmitters or cells Null column allowed: No Default value: TYPE Text (50) Type of the neighbourhood (handover, measurement…) Null column allowed: Yes Default value: FORCE_HHO Boolean Force Handover type to hard handover in case of intra-carriers neighbours Null column allowed: No Default value: False 8.5.1.15.2 NeighboursExt Table This table stores neighbourhood relationships between transmitters/cells of different .atl documents (inter-technology neighbours). Field Type Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: NEIGHBOUR Text (50) Second part of the unique key. List of neighbours from another project Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: REASON Integer Reason of the neighbourhood Null column allowed: Yes Default value: 0 (Manual) Choice list: Manual, Forced, Co-site, Adjacent, Symmetric, Distance, Coverage TRANSMITTER Text (50) First part of the unique key. Transmitters or cells Null column allowed: No Default value: TYPE Text (50) Type of the neighbourhood (handover, measurement…) Null column allowed: Yes Default value: 8.5.1.15.3 NeighboursConstraints Table This table enables you set handover relationships between cells. These constraints are used as input for automatic neighbour allocation. Field Type Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: NEIGHBOUR Text (50) Second part of the unique key. List of neighbours Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: STATUS Integer Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. Null column allowed: Yes Default value: 0 Choice list: 0=Forced, 1=Forbidden TRANSMITTER Text (50) First part of the unique key. Transmitters or cells. Null column allowed: No Default value: FORCE_HHO Boolean Force Handover type to hard handover in case of intra-carriers neighbours Null column allowed: No Default value: False 8.5.1.15.4 NeighboursConstraintsExt Table This table enables you to set external handover relationships (with transmitters/cells of another project). These constraints are used as input for automatic neighbour allocation. Field 282 Type Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: NEIGHBOUR Text (50) Second part of the unique key. List of neighbours from another project. Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure STATUS Integer Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. TRANSMITTER Text (50) First part of the unique key. Transmitters or cells 8.5.1.16 Null column allowed: Yes Default value: 0 Choice list: 0=Forced, 1=Forbidden Null column allowed: No Default value: Transmitters Table This table stores all the transmitters and their properties. Field Type Description Attributes ACTIVE Boolean Transmitter activity: 'Yes' means that the transmitter is active Null column allowed: No Default value: True ANTDIVGAIN Float Antenna diversity gain Null column allowed: Yes Default value: 0 ANTENNA_NAME Text (50) Name of the main antenna installed on the transmitter Null column allowed: Yes Default value: AZIMUT Float Azimuth of the main antenna Null column allowed: Yes Default value: 0 BTS_NAME Text (50) Name of the BTS equipment Null column allowed: Yes Default value: CALC_RADIUS Integer Calculation radius used to define the calculation area Unit: m Null column allowed: Yes Default value: 4000 CALC_RADIUS2 Integer Extended calculation radius Null column allowed: Yes Default value: CALC_RESOLUTION Integer Calculation resolution Null column allowed: Yes Default value: 50 CALC_RESOLUTION2 Integer Extended calculation resolution Null column allowed: Yes Default value: CELL_SIZE Float Hexagon radius Unit: m Null column allowed: Yes Default value: 2000 COMMENT_ Text (255) Additional information about the transmitter Null column allowed: Yes Default value: DX Float X coordinate relative to the site location Null column allowed: Yes Default value: 0 DY Float Y coordinate relative to the site location Null column allowed: Yes Default value: 0 FEEDER_NAME Text (50) Name of the feeder equipment Null column allowed: Yes Default value: FEEDERLENGTH_DL Float Length of feeder in DL Null column allowed: Yes Default value: 0 FEEDERLENGTH_UL Float Length of feeder in UL Null column allowed: Yes Default value: 0 HEIGHT Float Antenna height above the ground Unit: m Null column allowed: Yes Default value: 25 HEXAGON_GROUP Text (50) Group of hexagons used to create this transmitter Null column allowed: Yes Default value: MISCDLL Float Miscellaneous DL loss Null column allowed: Yes Default value: 0 MISCULL Float Miscellaneous UL loss Null column allowed: Yes Default value: 0 PROPAG_MODEL Text (255) Name of the propagation model used to calculate prediction Null column allowed: Yes Default value: ’Default model’ PROPAG_MODEL2 Text (255) Name of the propagation model used to calculate extended prediction Null column allowed: Yes Default value: SITE_NAME Text (50) Name of the site on which the transmitter is located (from the site table of Atoll) Null column allowed: No Default value: TILT Float Mechanical downtilt of the first antenna Null column allowed: Yes Default value: 0 TMA_NAME Text (50) Name of the TMA equipment Null column allowed: Yes Default value: © Forsk 2009 AT281_AM_E1 283 Administrator Manual TX_ID Text (50) Transmitter name Null column allowed: No Default value: FBAND Text (50) Frequency band Null column allowed: No Default value: NOISE_FIGURE Float Noise figure used to determine the thermal noise at the transmitter Null column allowed: Yes Default value: 5 RXLOSSES Float Losses in the uplink due to transmitter radio equipment Null column allowed: Yes Default value: 0 TXLOSSES Float Losses in the downlink due to transmitter radio equipment Null column allowed: Yes Default value: 0 COV_PROBA Short Cell edge Coverage probability per Transmitter Null column allowed: Yes Default value: 75 REDT Float Remote Electrical tilt Null column allowed: Yes Default value: 0 8.5.1.17 TplTransmitters Table This table is used to store station templates and their properties. Field Type Description Attributes ACTIVE Boolean Transmitter activity: 'Yes' means that the transmitter is active Null column allowed: No ANTDIVGAIN Float Antenna diversity gain Unit: dB Null column allowed: Yes ANTENNA_NAME Text (50) Name of the main antenna installed on the transmitter Null column allowed: Yes AZIMUT Float Azimuth of the first antenna Null column allowed: Yes BTS_NAME Text (50) Name of the BTS equipment Null column allowed: Yes CALC_RADIUS Integer Calculation radius used to define each transmitter calculation area Unit: m Null column allowed: Yes CALC_RADIUS2 Integer Extended calculation radius Unit: m Null column allowed: Yes CALC_RESOLUTION Integer Calculation resolution Null column allowed: Yes CALC_RESOLUTION2 Integer Extended calculation resolution Null column allowed: Yes CELL_SIZE Float Hexagon radius Unit: m Null column allowed: Yes FEEDER_NAME Text (50) Name of the feeder equipment Null column allowed: Yes FEEDERLENGTH_DL Float Length of downlink feeder Unit: m Null column allowed: Yes FEEDERLENGTH_UL Float Length of uplink feeder Unit: m Null column allowed: Yes HEIGHT Float Antenna height above the ground Unit: m Null column allowed: Yes MAX_NEIGHB_NUMBER Short Maximum number of neighbours for the cell or the transmitter Null column allowed: Yes MAX_EXT_NEIGHB_NUMBE R Short Maximum number of inter-technology neighbours for the cell or the transmitter Null column allowed: Yes MISCDLL Float Miscellaneous downlink losses Null column allowed: Yes MISCULL Float Miscellaneous uplink losses Null column allowed: Yes NAME Text (50) Template name Null column allowed: No NUM_SECTORS Integer Number of sectors Null column allowed: Yes PROPAG_MODEL Text (255) Name of the propagation model used to calculate predictions Null column allowed: Yes PROPAG_MODEL2 Text (255) Name of the propagation model used to calculate extended prediction Null column allowed: Yes TILT Float Mechanical downtilt of the main antenna Null column allowed: Yes TMA_NAME Text (50) Name of the Tower Mounted Amplifier equipment Null column allowed: Yes CARRIERS Text (50) Carriers used by the transmitter Null column allowed: Yes FBAND Text (50) Frequency band Null column allowed: No NOISE_FIGURE Float Noise figure used to determine the thermal noise at the transmitter Null column allowed: Yes PILOT_POWER Float Power of the pilot channel Null column allowed: Yes POWER_MAX Float Maximum power supported by the transmitter Null column allowed: Yes Float Losses in the uplink due to transmitter radio equipment Unit: dB Null column allowed: Yes RXLOSSES 284 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure TOTAL_POWER Float Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm Null column allowed: Yes TXLOSSES Float Losses in the downlink due to transmitter radio equipment Unit: dB Null column allowed: Yes UL_LOAD Float Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm Null column allowed: Yes CHANNEL_ELEMENTS_DL Integer Number of channel elements for downlink Null column allowed: Yes CHANNEL_ELEMENTS_UL Integer Number of channel elements for uplink Null column allowed: Yes CDMA_EQUIPMENT Text (50) CDMA equipment Null column allowed: Yes REUSE_DIST Float Minimum reuse distance for PN offsets Null column allowed: Yes EVDO_CES Integer Number of EVDO channel elements per carrier Null column allowed: Yes IDLE_POWER_GAIN Float Gain dedicated to transmitted power in idle state Null column allowed: Yes MUG_TABLE Memo Set of values used to generate the graph MUG=f(num users) Null column allowed: Yes PAGING_POWER Float Power of the paging channel Null column allowed: Yes PN_DOMAIN_NAME Text (50) PN Offset code domain name Null column allowed: Yes SYNCHRO_POWER Float Power of the synchronisation (SCH) channel Null column allowed: Yes COV_PROBA Short Cell edge Coverage probability per Transmitter Null column allowed: Yes REDT Float Remote Electrical tilt Null column allowed: Yes MAX_UL_LOAD Float Maximum uplink load allowed (percentage). Used in power control simulation Null column allowed: Yes MAX_DL_LOAD Float Maximum downlink load allowed (percentage of max power used). Used in power control simulation Null column allowed: Yes ROT_TARGET Float Receiver Noise Rise Over Thermal target (dB) Null column allowed: Yes ROT_RANGE Float Delta of acceptable noise rise (dB) Null column allowed: Yes DRC_ER_RATE Float DRC Erasure Rate (ie % of time DRC values are in error) Null column allowed: Yes BCMCS_TS_PCT Float % of time slots dedicated to Broadcast/MultiCast services Null column allowed: Yes MAX_INTERCAR_NEIGHB_ NB Integer Maximum number of inter-carrier neighbours for this cell Null column allowed: Yes MAX_EVDO_USERS Integer Maximum number of EV-DO users Null column allowed: Yes POOLED_PWR Float Amount of power which can be borrowed in the BTS power pool (dB) Null column allowed: Yes TADD Float Minimum Ec/Io for best server selection Null column allowed: Yes TDROP Float Ec/Io threshold for active set rejection Null column allowed: Yes BCMCS_RATE Float BCMCS service rate Null column allowed: Yes CCH_TS_PCT Float % of time slots dedicated to Common Control Channels Null column allowed: Yes DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes 8.5.1.18 Repeaters Table This table manages repeaters and repeater properties. Field Type Description Attributes AMPLIFIER_GAIN Float Gain of the amplifier Null column allowed: Yes Default value: 80 AZIMUT Float Azimuth of the donor side antenna Null column allowed: Yes Default value: 0 DONOR_CELLID Text (50) Name of the donor cell Null column allowed: No Default value: DOWNTILT Float Downtilt of the donor side antenna Null column allowed: Yes Default value: 0 FEEDER_NAME Text (50) Name of the donor side feeder Null column allowed: Yes Default value: FEEDERLENGTH Float Length of donor side feeder Null column allowed: Yes Default value: 0 HEIGHT Float Height of the donor side antenna Null column allowed: Yes Default value: 25 © Forsk 2009 AT281_AM_E1 285 Administrator Manual REC_ANTENNA Text (50) Name of the donor side antenna Null column allowed: Yes Default value: TX_ID Text (50) Name of the transmitter (and of the transmitter used for coverage) Null column allowed: No Default value: TOTAL_GAIN Float Total gain to be applied to donor cell pilot power Null column allowed: Yes Default value: 0 DONOR_LINK_TYPE Short 1- Off air 2- Microwave 3- Fibre Null column allowed: No Default value: 1 DONOR_LINK_LOSS Float Loss (dB) between donor and donor side of the repeater Null column allowed: Yes Default value: 0 EQUIPMENT_NAME Text (50) If no equipment, the repeater is a passive component Null column allowed: Yes Default value: REC_FEEDERLENGTH_UL Float Length of donor side uplink feeder Null column allowed: Yes Default value: 0 TOTAL_GAIN_UL Float Uplink total gain to be applied to mobile output power Null column allowed: Yes Default value: 0 DONOR_PROPAG_MODEL Text (50) Name of the propagation model used to calculate prediction between donor and repeater Null column allowed: Yes Default value: Note: • 8.5.1.19 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. RepeaterEquipments Table This table models the equipment used by repeaters. Field Type Description Attributes NAME Text (50) Name of the repeater equipment Null column allowed: No Default value: MANUFACTURER Text (50) Manufacturer of the repeater equipment Null column allowed: Yes Default value: NOISE_FIGURE Float Repeater noise Figure (dB) Null column allowed: Yes Default value: 5 MIN_AMPLIFIER_GAIN Float Minimum gain of the amplifier (dB) Null column allowed: Yes Default value: 50 MAX_AMPLIFIER_GAIN Float Maximum gain of the amplifier (dB) Null column allowed: Yes Default value: 90 STEP_AMPLIFIER_GAIN Float Step of amplifier gain (dB) Null column allowed: Yes Default value: 1 MAX_OUTPUT_UL Float Maximum uplink output power (dBm) Null column allowed: Yes Default value: 12 MAX_OUTPUT_DL Float Maximum downlink output power (dBm) Null column allowed: Yes Default value: 30 TIME_DELAY Float Time delay in the equipment (microseconds) Null column allowed: Yes Default value: 5 COMMENT_ Text (255) Comments Null column allowed: Yes Default value: 8.5.1.20 PN Offset Management Tables These tables store constraints (the range of available PN offsets, pairs of cells which cannot be assigned the same PN offset) used as input for automatic PN offset allocation. 8.5.1.20.1 PnCodesDomains Table Field Type Description Attributes DOMAIN_NAME Text (50) Resource domain name Null column allowed: No Default value: 8.5.1.20.2 PnCodesGroups Table Field DOMAIN_NAME 286 Type Text (50) Description Attributes Second part of the unique key. Domain of the PN code group. Null column allowed: No Default value: AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure EXCLUDED Text (225) List of codes to be excluded from the series defined by FIRST, LAST and STEP (separated by blank character) Null column allowed: Yes Default value: EXTRA Text (225) Codes to be added. It is forbidden for EXTRA and EXLUDED to have common numbers. Separator must be a blank character. Null column allowed: Yes Default value: FIRST Integer 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 LAST Integer 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 NAME Text (50) First part of the unique key. Name of the PN code group Null column allowed: No Default value: STEP Integer 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: 1 8.5.1.20.3 Separations Table Field Type Description Attributes TX_ID Text (50) First part of the unique key. First cell name in a symmetric relation Null column allowed: No Default value: TX_ID_OTHER Text (50) Second part of the unique key. Second cell name in a symmetric relation Null column allowed: No Default value: 8.5.1.21 CDMACells Table This table stores cells and their properties. Field Type Description Attributes CARRIER Integer Carrier number Null column allowed: Yes Default value: 0 CELL_ID Text (50) Name of the cell Null column allowed: No Default value: COMMENT_ Text (255) Additional information about the cell Null column allowed: Yes Default value: MAX_NEIGHB_NUMBER Integer Maximum number of neighbours for the cell Null column allowed: Yes Default value: MAX_EXT_NEIGHB_NUMBE R Integer Maximum number of inter-technology neighbours for the cell Null column allowed: Yes Default value: PILOT_POWER Float Power of the pilot channel Null column allowed: Yes Default value: 33 POWER_MAX Float Maximum power supported by the transmitter Null column allowed: Yes Default value: 43 REUSE_DIST Float Minimum reuse distance for PN Offsets Null column allowed: Yes Default value: TOTAL_POWER Float Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm Null column allowed: Yes Default value: TX_ID Text (50) Name of the transmitter Null column allowed: No Default value: UL_LOAD Float Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm Null column allowed: Yes Default value: IDLE_POWER_GAIN Float Gain dedicated to transmitted power in idle state. Null column allowed: Yes Default value: -10 MUG_TABLE Memo Set of values used to generate the graph MUG=f(number of users) Null column allowed: Yes Default value: PN_DOMAIN_NAME Text (50) PN Offset domain name. Null column allowed: Yes Default value: PN_OFFSET Integer PN Offset. Null column allowed: Yes Default value: SYNCHRO_POWER Float Power of the synchronisation (SCH) channel Null column allowed: Yes Default value: 23 PAGING_POWER Float Power of other common channels except SCH Null column allowed: Yes Default value: 30 © Forsk 2009 AT281_AM_E1 287 Administrator Manual MAX_UL_LOAD Float Maximum uplink load allowed (percentage). Used in power control simulation Null column allowed: Yes Default value: 75 MAX_DL_LOAD Float Maximum downlink load allowed (percentage of max power used). Used in power control simulation Null column allowed: Yes Default value: 50 ROT_TARGET Float Receiver Noise Rise Over Thermal target (dB) Null column allowed: Yes Default value: 4 ROT_RANGE Float Delta of acceptable noise rise (dB) Null column allowed: Yes Default value: 1 DRC_ER_RATE Float DRC Erasure Rate (ie % of time DRC values are in error) Null column allowed: Yes Default value: 25 BCMCS_TS_PCT Float % of time slots dedicated to Broadcast/MultiCast services Null column allowed: Yes Default value: 5 MAX_INTERCAR_NEIGHB_ NB Integer Maximum number of inter-carrier neighbours for this cell Null column allowed: Yes Default value: BCMCS_RATE Float BCMCS service rate Null column allowed: Yes Default value: 204.8 CCH_TS_PCT Float % of time slots dedicated to Common Control Channels Null column allowed: Yes Default value: 3 ACTIVE Boolean Cell's activity: True means that the cell is active Null column allowed: No Default value: True MAX_EVDO_USERS Integer Maximum number of EV-DO users Null column allowed: No Default value: 256 POOLED_PWR Float Amount of power which can be borrowed in the BTS power pool (dB) Null column allowed: No Default value: 1 TADD Float Minimum Ec/Io for best server selection Null column allowed: No Default value: -14 TDROP Float Ec/Io threshold for active set rejection Null column allowed: Yes Default value: -17 CELL_IDENTITY Integer Cell identity Null column allowed: Yes Default value: DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes Default value: 0 UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes Default value: 0 8.5.1.22 CDMAEquipments Table This table models equipment that performs radio resource management at site level. Field Type Description Attributes CARRIER_SELECTION Short Carrier selection mode Null column allowed: No Default value: 0 Choice list: 0="min UL noise" 1= "min DL power" 2="random" CES_OVERHEAD_DL Integer Number of channel elements used for DL overhead channels (pilot, synchro, ...) Null column allowed: No Default value: 0 CES_OVERHEAD_UL Integer Number of channel elements used for UL overhead channels (pilot, synchro, ...) Null column allowed: No Default value: 0 MANUFACTURER Text (50) Name of the manufacturer Null column allowed: Yes Default value: MUD_FACTOR Float MUD factor for UL interference cancellation Null column allowed: No Default value: 0 NAME Text (50) Equipment name Null column allowed: No Default value: RAKE_EFFICIENCY Float Efficiency of the rake receiver. Used for combination of AS member contributions Null column allowed: No Default value: 1 USE_NEIGHBOURS Boolean If true, selection of AS members is limited to the neighbours of the selected transmitter Null column allowed: No Default value: False CE_SHARED_ALL_SECTOR S Boolean If true CE resources is shared between all sectors of the site Null column allowed: No Default value: False SPP Boolean (Sector Power Pooling) If True, sectors' powers available for TCH can be shared among all co-site sectors Null column allowed: No Default value: False 288 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.5.1.23 CDMAEquipmentsCEsUse Table This table contains information about consumption of channel elements. Field Type Description Attributes CHANNEL_ELTS_DL Float Number of channel elements used for downlink Null column allowed: No Default value: 1 CHANNEL_ELTS_UL Float Number of channel elements used for uplink Null column allowed: No Default value: 1 EQUIPMENT Text (50) First part of the unique key. Name of equipment Null column allowed: No Default value: TERMINAL Text (50) Second part of the unique key. Terminal name. Null column allowed: No Default value: 8.5.1.24 CarriersType Table This table lists different carrier types and defines whether the carrier is 1xEV-DO or 1xRTT based. Field Type Description Attributes CARRIER Integer Carrier number Null column allowed: No Default value: 0 TYPE Short Carrier type Null column allowed: Yes Default value: 0 Choice list: 0 = 1xRTT 1 = 1xEV-DO 8.5.1.25 Multi-Service Traffic Management This table contain descriptions of multi-service traffic data, i.e., services, mobility types, terminals, user profiles, and environments. 8.5.1.25.1 UMTSEnvironmentDefs Table Field Type Description Attributes DENSITY Float Number of subscribers per km2 Null column allowed: Yes Default value: 0 ENVIRONMENT Text (50) Environment name Null column allowed: No Default value: MOBILITY Text (50) Type of mobility Null column allowed: No Default value: USER_PROFILE Text (255) Type of user profile Null column allowed: No Default value: 8.5.1.25.2 UMTSMobility Table Field Type NAME Text (50) Description Attributes Type of mobility Null column allowed: No Default value: COVERI_THROUGHPUTS Memo Set of values used to generate the Rate=f(C/I) graph Null column allowed: Yes Default value: '38.4 -10.5 76.8 -7.5 153.6 -4.5 307.2 -2. 614.4 1 921.6 3.3 1228.8 5 1843.2 9.2 2457.6 11.5' DELTA_TADD Float Delta (dB) to be added to the T_ADD defined in cell’s structure Null column allowed: Yes Default value: 0 DELTA_TDROP Float Delta (dB) to be added to the T_DROP defined in cell’s structure Null column allowed: Yes Default value: 0 UL_ECNT_MIN Float Minimum uplink Ec/Nt (EV-DO) Null column allowed: Yes Default value: -22 8.5.1.25.3 UMTSServicesQuality Table Field Type Description Attributes SERVICE Text (50) First part of the unique key. Name of the service Null column allowed: No Default value: © Forsk 2009 AT281_AM_E1 289 Administrator Manual TERMINAL Text (50) Second part of the unique key. Type of terminal Null column allowed: No Default value: DL_TARGET_QUAL Float Eb/Nt target on the downlink for each type of (mobility, SCH rate) pair Null column allowed: Yes Default value: PTCH_MIN Float Minimum transmitter power on fundamental traffic channel for the service Null column allowed: Yes Default value: 14 PTCH_MAX Float Maximum transmitter power on fundamental traffic channel for the service Null column allowed: Yes Default value: 34 UL_TARGET_QUAL Float Eb/Nt target on the uplink for each type of (mobility, SCH rate) pair Null column allowed: Yes Default value: SCH_RATE Integer SCH Rate factor (0 -> 16) Null column allowed: No Default value: 0 RX_EQUIP Text (50) Type of receiver Null column allowed: No Default value: ’Standard’ FCH2PILOT Float FCH power to Pilot power gain. Used if global flag UL_PWC_ON_PILOT is set to True Null column allowed: Yes Default value: 0 SCH2PILOT Float SCH power to Pilot power gain. Used if global flag UL_PWC_ON_PILOT is set to True Null column allowed: Yes Default value: 0 UL_ECNT_MIN Float Pilot’s Ec/Nt target. Used if global flag UL_PWC_ON_PILOT is set to True Null column allowed: Yes Default value: 0 MOBILITY Text (50) UE mobility Null column allowed: Yes Default value: 8.5.1.25.4 UMTSServicesUsage Table Field Type Description Attributes CALL_DURATION Float Average duration of a call (for circuit switched services) Unit: s Null column allowed: Yes Default value: CALL_NUMBER Float Average number of calls per hour for circuit switched services or average number of sessions per hour for packet switched services Null column allowed: Yes Default value: 0 SERVICE Text (50) Service that the subscriber may request Null column allowed: No Default value: TERMINAL Text (50) Type of terminal used by the subscriber for the service Null column allowed: No Default value: USER_PROFILE Text (255) User profile name Null column allowed: No Default value: 8.5.1.25.5 UMTSServices Table Field Type Description Attributes BODY_LOSS Float Body loss Null column allowed: No Default value: 0 NAME Text (50) Service name Null column allowed: No Default value: PRIORITY Integer Priority level of the service: parameter used in the WCDMA simulation Null column allowed: Yes Default value: 0 USE_HANDOFF Boolean 'Yes' if the service supports soft handoff Null column allowed: No Default value: False DLFCH_ACTIVITYFACTOR Float Occupancy time of the fundamental channel on the downlink Null column allowed: Yes Default value: 1 DLRATE_2 Float Probability to transmit twice the nominal rate on the supplementary channel (SCH) on the downlink Null column allowed: Yes Default value: 0 DLRATE_4 Float Probability to transmit four times the nominal rate on the supplementary channel (SCH) on the downlink Null column allowed: Yes Default value: 0 DLRATE_8 Float Probability to transmit eight times the nominal rate on the supplementary channel (SCH) on the downlink Null column allowed: Yes Default value: 0 DLRATE_16 Float Probability to transmit sixteen times the nominal rate on the supplementary channel (SCH) on the downlink Null column allowed: Yes Default value: 0 TYPE Short '0'=’Speech’,’1’=’Data 1xRTT’ ‘2’=’EVDO’ Null column allowed: Yes Default value: 0 ULFCH_ACTIVITYFACTOR Float Either occupancy time of the fundamental channel on the uplink for 1xRTT, or probability to transmit the nominal rate on the supplementary channel (SCH) on the uplink in case of 1xEVDO. Null column allowed: Yes Default value: 1 290 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure ULRATE_2 Float Probability to transmit twice the nominal rate on the supplementary channel (SCH) on the uplink Null column allowed: Yes Default value: 0 ULRATE_4 Float Probability to transmit four times the nominal rate on the supplementary channel (SCH) on the uplink Null column allowed: Yes Default value: 0 ULRATE_8 Float Probability to transmit height times the nominal rate on the supplementary channel (SCH) on the uplink Null column allowed: Yes Default value: 0 ULRATE_16 Float Probability to transmit sixteen times the nominal rate on the supplementary channel (SCH) on the uplink Null column allowed: Yes Default value: 0 CARRIER Integer Carrier supporting the service. -1 means that all carriers can be used. Null column allowed: Yes Default value: -1 TH_SCALE_FACTOR Float Ratio between application throughput and RLC layer throughput Null column allowed: No Default value: 95 TH_OFFSET Float Offset to add to the above ratio Null column allowed: No Default value: 0 EVDO_ULRATE_1 Float Probability to transmit at 9.6 kbps for an EVDO service Null column allowed: Yes Default value: 0 TCP_SERVICE Boolean True if the user application is using TCP Null column allowed: No Default value: False TCP_ACK_CURVE Memo Table of Reverse Link throughputs=f(Forward Link application layer throughput) Null column allowed: Yes Default value: '0 0 300 10 600 20 900 30 1200 40 1500 50 1800 60 2400 80' DOWN_153K6_76K8 Float EV-DO Rev.0 Downgrading probability (153.6 -> 76.8) (Unit 1/255) Null column allowed: Yes Default value: 0 DOWN_19K2_9K6 Float EV-DO Rev.0 Downgrading probability (19.2 -> 9.6) (Unit 1/255) Null column allowed: Yes Default value: 0 DOWN_38K4_19K2 Float EV-DO Rev.0 Downgrading probability (38.4 -> 19.2) (Unit 1/255) Null column allowed: Yes Default value: 0 DOWN_76K8_38K4 Float EV-DO Rev.0 Downgrading probability (76.8 -> 38.4) (Unit 1/255) Null column allowed: Yes Default value: 0 ENABLE_DOWNGRADING Boolean True if downgrading is enabled for the service Null column allowed: No Default value: True QOS_CLASS Short 0="Best Effort" 1="Guaranteed Bit Rate" Null column allowed: Yes Default value: 0 UL_OPERATION_MODE Short 0="High Capacity" 1="Low Latency" Null column allowed: Yes Default value: 0 UP_19K2_38K4 Float EV-DO Rev.0 Upgrading probability (19.2 -> 38.4) (Unit 1/255) Null column allowed: Yes Default value: 0 UP_38K4_76K8 Float EV-DO Rev.0 Upgrading probability (38.4 -> 76.8) (Unit 1/255) Null column allowed: Yes Default value: 0 UP_76K8_153K6 Float EV-DO Rev.0 Upgrading probability (76.8 -> 153.6) (Unit 1/255) Null column allowed: Yes Default value: 0 UP_9K6_19K2 Float EV-DO Rev.0 Upgrading probability (9.6 -> 19.2) (Unit 1/255) Null column allowed: Yes Default value: 0 8.5.1.25.6 UMTSTerminals Table Field Type Description Attributes GAIN Float Receiver antenna gain Null column allowed: Yes Default value: 0 LOSS Float Receiver antenna loss Null column allowed: Yes Default value: 0 NAME Text (50) Terminal name Null column allowed: No Default value: NOISE_FACTOR Float Noise figure used to determine the thermal noise at the receiver Null column allowed: Yes Default value: 8 PMAX Float Maximum receiver power on traffic channel Null column allowed: Yes Default value: 23 PMIN Float Minimum receiver power on traffic channels Null column allowed: Yes Default value: -50 RAKE_EFFICIENCY Float Efficiency of the rake receiver. Used for combination of Active Set member contributions Null column allowed: Yes Default value: 1 © Forsk 2009 AT281_AM_E1 291 Administrator Manual ACTIVE_SET_SIZE Short Maximum number of transmitters possibly connected with the receiver for the fundamental channel (FCH) Null column allowed: Yes Default value: 6 SCH_AS_SIZE Short Maximum number of transmitters possibly connected with the receiver for the supplementary channel (SCH) Null column allowed: Yes Default value: 3 FWD_BASEDATARATE Float Downlink nominal rate supported by the receiver on the fundamental channel Null column allowed: No Default value: 9.6 RAKE_NUM_FINGERS Short Number of links of the active set that will be combined Null column allowed: Yes Default value: 3 REV_BASEDATARATE Float Uplink nominal rate supported by the receiver on the fundamental channel Null column allowed: No Default value: 9.6 PILOT_POWER_PCT Float Percentage of maximum power dedicated to the UL pilot channel Null column allowed: Yes Default value: 0 RHO_FACTOR Short Rho factor to model self generated interference Null column allowed: No Default value: 94 SUPPORTED_TECHNO Short 0:Speech, 1:1xRTT_Data, 2:1xEvDo_Rel0, 3:1xEvDo_RelA Null column allowed: No Default value: 0 RX_EQUIP Text (50) Type of the User Equipment Receiver Null column allowed: No Default value: ‘Standard’ ACK_GAIN Float ACK gain Null column allowed: Yes Default value: 4 ACK_GAIN_DORA Float ACK gain for 1xEvDo Rev A Null column allowed: No Default value: 3 RRI_GAIN_DORA Float RRI gain for 1xEvDo Rev A Null column allowed: No Default value: -6 DRC_GAIN_NOHO Float DRC gain (No handoff case) Null column allowed: Yes Default value: -1 DRC_GAIN_NOHO_DORA Float DRC gain (No handoff case) for 1xEvDo Rev A Null column allowed: No Default value: -1 DRC_GAIN_SOFT Float DRC gain (any kind of soft handoff) Null column allowed: Yes Default value: -3 DRC_GAIN_SOFT_DORA Float DRC gain (any kind of soft handoff) for 1xEvDo Rev A Null column allowed: No Default value: -3 DRC_GAIN_SOFTER Float DRC gain (only softer handoff) Null column allowed: Yes Default value: -1 DRC_GAIN_SOFTER_DORA Float DRC gain (only softer handoff) for 1xEvDo Rev A Null column allowed: No Default value: -1 TRAFFIC_GAIN_153_6 Float Traffic gain (153.6 kbps) Null column allowed: Yes Default value: 18 TRAFFIC_GAIN_19_2 Float Traffic gain (19.2 kbps) Null column allowed: Yes Default value: 7 TRAFFIC_GAIN_38_4 Float Traffic gain (38.4 kbps) Null column allowed: Yes Default value: 10 TRAFFIC_GAIN_76_8 Float Traffic gain (76.8 kbps) Null column allowed: Yes Default value: 13 TRAFFIC_GAIN_9_6 Float Traffic gain (9.2 kbps) Null column allowed: Yes Default value: 4 NOISE_FACTOR_SEC Float Noise figure used to determine the thermal noise at the receiver (for secondary frequency band) Null column allowed: Yes Default value: 8 PRIMARY_BAND Text (50) Primary frequency band Null column allowed: Yes Default value: SECONDARY_BAND Text (50) Secondary frequency band Null column allowed: Yes Default value: 0 8.5.1.25.7 1xEV-DO Release A Bearers Modelling Tables These tables model 1xEV-DO Release A service bearers. DORABearers Table Field BEARER_INDEX 292 Type Short Description Attributes EV-DO bearer index Null column allowed: No Default value: AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure RLC_PEAK_RATE Float RLC bearer rate Null column allowed: Yes Default value: 0 TRANSPORT_BLOCK_SIZE Integer Transport block size (Bits) Null column allowed: Yes Default value: 0 ULBearersSelection Table Field Type Description Attributes BEARER_INDEX Short Index of selected bearer Null column allowed: Yes Default value: 0 EARLY_TERM_TABLE Memo Tables of Probabilities of Earlier Termination=f(REPEAT_NUM) Null column allowed: Yes Default value: HC_ECNT_REQ Float Required Pilot Ec/Nt for High Capacity services Null column allowed: Yes Default value: LL_ECNT_REQ Float Required Pilot Ec/Nt for Low Latency services Null column allowed: Yes Default value: MOBILITY Text (50) UE mobility Null column allowed: Yes Default value: NUM_SUBFRAMES Integer Number of retransmissions to ensure a correct transmission Null column allowed: Yes Default value: 1 RX_EQUIP Text (50) Type of receiver of the User Equipment Null column allowed: Yes Default value: "Standard" DLDORABearers Table Field Type Description Attributes BEARER_INDEX Short EV-DO bearer index Null column allowed: No Default value: RLC_PEAK_RATE Float RLC bearer rate Null column allowed: Yes Default value: 0 TRANSPORT_BLOCK_SIZE Integer Transport block size (Bits) Null column allowed: Yes Default value: 0 DLBearersSelection Table Field Type Description Attributes BEARER_INDEX Short Index of selected bearer Null column allowed: Yes Default value: 0 CI_REQ Float Required Pilot C/I Null column allowed: Yes Default value: EARLY_TERM_TABLE Memo Tables of Probabilities of Earlier Termination=f(REPEAT_NUM) Null column allowed: Yes Default value: MOBILITY Text (50) UE mobility Null column allowed: Yes Default value: NUM_SLOTS Integer Number of retransmissions to ensure a correct transmission Null column allowed: Yes Default value: 1 RX_EQUIP Text (50) Type of receiver of the User Equipment Null column allowed: Yes Default value: "Standard" DORATerminalT2PRatios Table Field Type Description Attributes TERMINAL Text (50) Terminal name Null column allowed: No Default value: BEARER_INDEX Short EV-DO bearer index Null column allowed: No Default value: 0 AUX_PILOT_GAIN Float Auxiliary pilot gain Null column allowed: Yes Default value: HC_T2P_GAIN Float Traffic to pilot gain for High Capacity services Null column allowed: Yes Default value: LL_T2P_GAIN Float Traffic to pilot gain for Low Latency services Null column allowed: Yes Default value: © Forsk 2009 AT281_AM_E1 293 Administrator Manual DORABearersProba Table Field Type Description Attributes BEARER_INDEX Short EV-DO bearer index Null column allowed: No Default value: SERVICE Text (50) Name of the service Null column allowed: No Default value: PROBA Float Probability of using a bearer Null column allowed: No Default value: 0 8.5.1.25.8 UMTSTraficEnvironments Table Field Type Description Attributes CLUTTER_WEIGHTS Binary Internal binary format describing weights assigned to each clutter class Null column allowed: Yes Default value: Yes NAME Text (50) Name of the created environment Null column allowed: No Default value: 8.5.1.25.9 UMTSUserProfiles Table Field Type NAME 8.5.1.26 Text (50) Description Attributes Name of the created user profile Null column allowed: No Default value: ServiceQualityTables Table This table stores quality graphs used for different reception equipment and quality indicators. Field Type Description Attributes SERVICE Text (50) Name of the service (can be null for some QI) Null column allowed: No Default value: QI_NAME Text (50) Name of the Quality Indicator Null column allowed: No Default value: RX_EQUIP Text (50) Type of receiver of the User Equipment Null column allowed: No Default value: ’Standard’ MOBILITY Text (50) UE mobility Null column allowed: Yes Default value: DL_QI_TABLE Memo QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table Null column allowed: Yes Default value: UL_QI_TABLE Memo QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table Null column allowed: Yes Default value: 8.5.1.27 QualityIndicators Table This table is used by Quality Indicator (FER, BER, BLER, etc.) coverage predictions. Field Type Description Attributes NAME Text (20) Name of the managed quality indicator Null column allowed: No Default value: PS_QI Boolean Flag which indicates if this indicator is used for PS services Null column allowed: No Default value: True CS_QI Boolean Flag which indicates if this indicator is used in CS services Null column allowed: No Default value: True MEAS_PARAM Short Name of the measured figure used for this QI determination Null column allowed: Yes Default value: 1 Choice list: CPICH_ECIO=1, CPICH_CI=2, CPICH_ECNT=3, DCH_EBNT=4, HSPDSCH_ECNT= 5 USE_INTERPOLATION Boolean Flag which indicates if this QI must be interpolated or not Null column allowed: No Default value: True 294 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.5.1.28 UERxEquipments Table This table contains a list of UE reception equipment. Field NAME 8.5.1.29 Type Text (50) Description Attributes Name of the type of receiver in the UE Null column allowed: No Default value: InterfReductionFactors Table This table stores the interference reduction factors between carriers. Field Type Description Attributes CARRIER1 Integer First carrier Null column allowed: No Default value: 0 CARRIER2 Integer Second carrier Null column allowed: No Default value: 0 FACTOR Double Interference reduction factor Null column allowed: No Default value: 200 8.5.1.30 InterNetChProtect Table This table stores the inter-network channel protection graphs. Field Type Description Attributes ICP Memo Inter-network channel protection = f(  MHz) Null column allowed: Yes Default value: ITF_BW Double Interfering bandwidth (kHz) Null column allowed: No Default value: 0 ITF_TECHNO Text (50) Interfering technology Null column allowed: No Default value: V_BW Double Victim bandwidth (kHz) Null column allowed: No Default value: 0 © Forsk 2009 AT281_AM_E1 295 Administrator Manual 8.6 TD-SCDMA Template Figure 8.11: on page 296, Figure 8.12: on page 297, and Figure 8.13: on page 298 depict the TD-SCDMA database structure. Figure 8.11: TD-SCDMA Template - 1 296 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure Figure 8.12: TD-SCDMA Template - 2 © Forsk 2009 AT281_AM_E1 297 Administrator Manual Figure 8.13: TD-SCDMA Template - 3 298 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.6.1 TD-SCDMA Tables The TD-SCDMA project template has the following data structure. 8.6.1.1 PropagationModels Table This table contains propagation model description, formulas, and parameters. Field Type Description Attributes Data Binary Model specific parameters Null column allowed: Yes Description Text (255) User defined Null column allowed: Yes Name Text (50) Name of the propagation model Null column allowed: No Signature Text (40) Unique Global ID of last model update Null column allowed: No Type Text (50) ProgID of the model Null column allowed: No 8.6.1.2 CustomFields Table This table enables you to define default values for all the fields of all the tables in Atoll, including user-defined fields added to different tables. It also enables you to define choice lists, a caption, and a group name for user-defined fields. Field Type Description Attributes CHOICE_LIST Memo Choice list for the field Null column allowed: Yes COLUMN_NAME Text (50) Second part of the unique key. Field name Null column allowed: No DEFAULT_VALUE Text (50) Default value for the field Null column allowed: Yes TABLE_NAME Text (50) First part of the unique key. Table name Null column allowed: No CAPTION Text (50) Caption of the field (displayed instead of the name) Null column allowed: Yes GROUP_NAME Text (50) Name of the group to which that field belongs Null column allowed: Yes The default values defined in this table have priority over the internal predefined default values (hard-coded in Atoll or defined in the database table structure). In order for Atoll to correctly consider the new default values, note that: • • 8.6.1.3 If you use floating point values, ensure that all the users have the same decimal separator (comma or point). The field names are case sensitive. CoordSys Table This table stores descriptions of the projection coordinate system and database’s internal coordinate system (the display coordinate system used when creating database). Field Type Description Attributes CODE Integer Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768) Null column allowed: No Default value: 0 DATUM_CODE Double DATUM_ROTX Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_ROTY Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_ROTZ Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_SCALE Double Parts per million (ppm) Null column allowed: Yes Default value: 0 DATUM_SHIFTX Double Meters Null column allowed: Yes Default value: 0 DATUM_SHIFTY Double Meters Null column allowed: Yes Default value: 0 DATUM_SHIFTZ Double Meters Null column allowed: Yes Default value: 0 ELLIPS_CODE Integer ELLIPS_RMAJOR Double © Forsk 2009 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Meters AT281_AM_E1 Null column allowed: Yes Default value: 0 299 Administrator Manual ELLIPS_RMINOR Double Meters Null column allowed: Yes Default value: 0 NAME Text (50) Coordinate system name Null column allowed: No Default value: PROJ_ANGLE Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_FALSE_EASTING Double Meters Null column allowed: Yes Default value: 0 PROJ_FALSE_NORTHING Double Meters Null column allowed: Yes Default value: 0 PROJ_FIRST_PARALLEL Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_LATITUDE_ORIGIN Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_LONGITUDE_ORIGIN Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_METHOD Short Undefined, NoProjection, Lambert1SP, Lambert2SP, Mercator, CassiniSoldner, TransMercator, TransMercatorSO, ObliqueStereographic, NewZealandMapGrid, HotineOM, LabordeOM, SwissObliqueCylindical, UTM Null column allowed: Yes Default value: 0 PROJ_SCALE_FACTOR Double PROJ_SECOND_PARALLEL Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_ZONE_NUMBER Integer Used with UTM Null column allowed: Yes Default value: 0 8.6.1.4 Null column allowed: Yes Default value: 0 Units Table This table stores the identification numbers of reception and transmission units, projection coordinate system specified in the .atl document and the database internal coordinate system. Field Type Description Attributes COORD_SYSTEM Integer Display coordinate system when creating database Null column allowed: Yes Default value: -1 PROJECTION Integer Projected coordinate system for geo data Null column allowed: Yes Default value: -1 Reception unit when creating database Null column allowed: No Default value: 0 Choice list: 0=dBm, 1=dbµV, 2=dbµV/m RECEPTION_UNIT Integer TRANSMISSION_UNIT Integer Transmission unit when creating database Null column allowed: No Default value: 0 Choice list: 0=dBm, 1=Watts, 2=kWatts GAIN_UNIT Integer Unit used for gains (dBd or dBi) Null column allowed: Yes Default value: 0 Choice list: 0= dBd, 1= dBi 8.6.1.5 Networks Table This table contains network-level properties and network-specific data. Field Type Description Attributes Null column allowed: No Default value: NAME Text (50) TECHNOLOGY Text (10) Name of the technology Null column allowed: No Default value: ‘CDMA’ SYSTEM_ Text (50) Name of the system Null column allowed: No Default value: ‘TDSCDMA’ DEFAULT_RESOLUTION Float Default calculation resolution Null column allowed: Yes Default value: 50 DEFAULT_MODEL Text (50) Default propagation model Null column allowed: No Default value: ‘Cost-Hata’ 300 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure SHARED_RESULTS_FOLDE Text (255) R Shared results storage folder Null column allowed: Yes Default value: DMAX Float Maximum radius for a cell Null column allowed: No Default value: -1 NTISNTOT Boolean Nt includes pilot signal or not Null column allowed: No Default value: False SPREADING_FACTOR_MIN Integer Minimum spreading factor Null column allowed: Yes Default value: 1 SPREADING_FACTOR_MAX Integer Maximum spreading factor Null column allowed: Yes Default value: 16 FRAME_TIME Short Duration of a frame in ms Null column allowed: Yes Default value: 10 SUBFRAME_TIME Short Duration of a subframe in ms Null column allowed: Yes Default value: 5 TS_NUMBER Integer Number of TS in a subframe Null column allowed: Yes Default value: 7 TS_DATA_CHIPS_NUMBER Float Number of data chips in a TS Null column allowed: Yes Default value: 704 MIDAMBLE_CHIPS_NUMBE R Float Number of chips in midamble Null column allowed: Yes Default value: 144 PILOT_PROCESSING_GAIN Float P-CCPCH Processing Gain Null column allowed: Yes Default value: 13.8 GUARD_PERIOD_CHIPS_N UMBER Float Number of chips in guard period Null column allowed: Yes Default value: 16 CQI_CPICH_BASED Boolean HSDPA only: CQI determination ids based on CPICH quality (true) or on HS-PDSCH quality (false) Null column allowed: No Default value: True DWPTS_CHIPS_NUMBER Integer DwPTS (TS dedicated to the pilot) Null column allowed: Yes Default value: 96 HSDPA_NTISNTOT Boolean HSDPA only: Nt includes or not pilot's signal for HS-SCCH, HS-PDSCH and CPICH for CQI determination Null column allowed: No Default value: False POWERS_RELATIVE_TO_PI LOT Boolean Cell Paging and Synchro powers, Service Allowed DL min and max TCH powers are absolute values (False) or relative to cell pilot power (True) Null column allowed: No Default value: PTS_GUARD_PERIOD_CHI PS_NUMBER Integer Number of chips in the PTS guard period Null column allowed: Yes Default value: 96 UPPTS_CHIPS_NUMBER Integer UpPTS (TS dedicated to the pilot) Null column allowed: Yes Default value: 160 INTERFERERS_RX_THRES H Float Interferers' reception threshold Null column allowed: Yes Default value: -130 SPREADING_WIDTH Float Spreading width (MHz) Null column allowed: Yes Default value: 1.28 EBNT_QUALITY_TARGET Boolean Type of quality target. True = Eb/Nt, False = C/I Null column allowed: No Default value: True 8.6.1.6 Sites Table This table contains the physical properties of sites. Field Type Description Attributes ALTITUDE Float Real altitude Unit: m Null column allowed: Yes Default value: COMMENT_ Text (255) Additional information on the site Null column allowed: Yes Default value: LATITUDE Double Y coordinate Null column allowed: No Default value: 0 LONGITUDE Double X coordinate Null column allowed: No Default value: 0 NAME Text (50) Site name Null column allowed: No Default value: CDMA_EQUIPMENT Text (50) Equipment associated with the site Null column allowed: Yes Default value: CHANNEL_ELEMENTS_DL Integer Number of available channel elements for downlink Null column allowed: No Default value: 256 © Forsk 2009 AT281_AM_E1 301 Administrator Manual CHANNEL_ELEMENTS_UL Integer Number of available channel elements for uplink Null column allowed: No Default value: 256 PYLON_HEIGHT Float Height of the pylon at site Null column allowed: Yes Default value: 50 SUPPORT_NATURE Short The nature of site. This field is for information only Null column allowed: Yes Default value: 0 8.6.1.7 Site List Management Tables These tables manage site lists used to filter groups of sites and transmitters. 8.6.1.7.1 SitesListsNames Table Field Type Description Attributes NAME Text (50) Name of the list Null column allowed: No Description Attributes 8.6.1.7.2 SitesLists Table Field Type LIST_NAME Text (50) First part of the unique key. Name of the list Null column allowed: No SITE_NAME Text (50) Second part of the unique key. Name of the site Null column allowed: No 8.6.1.8 Transmitter List Management Tables These tables manage transmitter lists used to filter groups of transmitters. 8.6.1.8.1 TxsListsNames Table Field Type Description Attributes NAME Text (50) Name of the transmitter list Null column allowed: No 8.6.1.8.2 TxsLists Table Field Type Description Attributes LIST_NAME Text (50) First part of the unique key. Name of the list. Null column allowed: No TX_NAME Text (50) Second part of the unique key. Name of the transmitter. Null column allowed: No 8.6.1.9 Antennas Table This table contains the description of antennas. Field Type Description Attributes Beamwidth Float Antenna beamwidth Null column allowed: Yes Default value: COMMENT_ Text (255) Additional information about antenna Null column allowed: Yes Default value: CONSTRUCTOR Text (50) Antenna manufacturer name Null column allowed: Yes Default value: DIAGRAM Binary Antenna horizontal and vertical patterns Null column allowed: Yes Default value: ELECTRICAL_TILT Float Antenna electrical tilt (for information) Null column allowed: Yes Default value: FMax Double Maximum operating frequency of the antennas Unit: MHz Null column allowed: Yes Default value: FMin Double Minimum operating frequency of the antenna Unit: MHz Null column allowed: Yes Default value: GAIN Float Antenna isotropic gain Unit: dBi Null column allowed: No Default value: 0 NAME Text (50) Name of antenna Null column allowed: No Default value: Note: • 302 An antenna pattern described in a text format may be converted to a binary format using a converter. The format of the binary field, DIAGRAM, is detailed below. Each antenna is described by a header and a list of value pairs. AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure - The header is defined as follows: int (32 bits) flag = 0 for omni diagrams, 1 for non-omni short (16 bits) num = number of diagrams (0,1,2,3,4) short (16 bits) siz0 = size of the first diagram (horizontal copolar section (elevation=0°)) short (16 bits) siz1 = size of second (vertical copolar section (azimuth=0°)) short (16 bits) siz2 = size of third (horizontal contrapolar) short (16 bits) siz3 = size of fourth (vertical contrapolar) short (16 bits) prec = precision of the following angle values (=100) - Then follows the content of each of the defined diagrams ("sizx" with a value not equal to zero). - One diagram consists of a list of value pairs: one unsigned short value, the angle in degrees (multiplied by 100), so 577 means 5 degrees 77 hundredths of a degree. one short value representing the loss in dB for the given angle. - if siz2 = 5, there will be 5 pairs of values describing the third diagram. - All the lists of pairs are concatenated without a separator. 8.6.1.10 SecondaryAntennas Table This table is used to model additional antennas installed on transmitters. Field Type Description Attributes ANTENNA Text (50) Name of the antenna installed on the transmitter Null column allowed: No Default value: AZIMUT Float Second part of the unique key. Azimuth of the antenna Null column allowed: No Default value: 0 PERCENT_POWER Float Percentage of power dedicated to the secondary antenna Null column allowed: No Default value: 0 TILT Float Mechanical downtilt of the secondary antenna Null column allowed: No Default value: 0 TX_ID Text (50) First part of the unique key. Transmitter name Null column allowed: No Default value: REDT Float Additional electrical downtilt Null column allowed: Yes Default value: 0 8.6.1.11 SmartAntennas Table This table models smart antenna systems. Field Type Description Attributes NAME Text (50) Name of the Smart Antenna Null column allowed: No Default value: GEOMETRY_TYPE Integer Geometry 1- ULA 2- UCA Null column allowed: Yes Default value: 1 ELTS_NUMBER Integer Number of elements Null column allowed: Yes Default value: 4 INTER_ELTS_DIST Integer Distance between elements in % of the wavelength Null column allowed: Yes Default value: 50 PROBA_THRESHOLD Integer Probability of having more than used C/I gain Null column allowed: Yes Default value: 50 COMMENT_ Text (255) Algorithm used to the C/I gain curves Null column allowed: Yes Default value: ADAPTIVE_PATTERN_DL Text (50) Downlink pattern used to model an adaptative smart antenna Null column allowed: Yes Default value: ADAPTIVE_PATTERN_UL Text (50) Uplink pattern used to model an adaptative smart antenna Null column allowed: Yes Default value: GOB_PATTERN Text (50) Downlink grid of beams name Null column allowed: Yes Default value: GOB_PATTERN_UL Text (50) Uplink grid of beams name Null column allowed: Yes Default value: © Forsk 2009 AT281_AM_E1 303 Administrator Manual SA_MODEL Text (50) External Model used to model the smart antenna Null column allowed: Yes Default value: MODELLING_TYPE Short Modelling Type: 0- Dedicated Model, 1- Ideal Beam Steering, 2- Grid Of Beams, 3- Statistical Null column allowed: Yes Default value: 0 8.6.1.12 SmartAntennasModels Table This table is used to store the smart antenna model parameters. Field Type Description Attributes SA_NAME Text (50) Name of the smart antenna model Null column allowed: No Default value: SA_TYPE Text (50) Type of the smart antenna model Null column allowed: No Default value: SA_SIGNATURE Text (50) Signature of the smart antenna model Null column allowed: No Default value: SA_DATA Binary Smart antenna model data Null column allowed: Yes Default value: SA_DESCRIPTION Text (50) Description of the smart antenna model Null column allowed: Yes Default value: 8.6.1.13 SACIGainCDF Table This table stores the graphs of cumulative density function of C/I gain associated to various smart antenna systems. Field Type Description Attributes SA_NAME Text (50) Name of the Smart antenna Null column allowed: No Default value: ANGULAR_SPREAD Short Value of the average angular spread in dB Null column allowed: Yes Default value: 5 CIGAIN_CDF Memo CDF of C/I gain values (list of pairs: C/I, cumulated probability) Null column allowed: Yes Default value: 8.6.1.14 Antenna List Management Tables These tables manage antenna lists used to filter groups of antennas. 8.6.1.14.1 AntennasListsNames Table Field Type Description Attributes NAME Text (50) Name of the list Null column allowed: No 8.6.1.14.2 AntennasLists Table Field Type Description Attributes ANTENNA_NAME Text (50) First part of the unique key. Name of the list. Null column allowed: No LIST_NAME Text (50) Second part of the unique key. Name of the antenna. Null column allowed: No 8.6.1.15 FrequencyBands Table This table contains the description of frequency band(s). 304 Field Type Description Attributes NAME Text (50) Name of the frequency band Null column allowed: No Default value: FIRST_CARRIER Integer Number of the first carrier available on the network Null column allowed: Yes Default value: 0 FREQUENCY Double Average frequency of carriers Unit: MHz Null column allowed: Yes Default value: 2010 LAST_CARRIER Integer Number of the last carrier available on the network Null column allowed: Yes Default value: 0 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure SPREADING_WIDTH Double Spreading bandwidth definition Null column allowed: Yes Default value: 1.28 BAND_WIDTH Double Bandwidth (MHz) Null column allowed: Yes Default value: 1.6 8.6.1.16 Receivers Table This table models the receiver used for raster coverage predictions. Field Type Description Attributes ADJ_CHANNEL_PROT Float Protection against interfering signals from adjacent channels. Null column allowed: No Default value: 18 ANTENNA Text (50) Receiver antenna name (if empty an omni antenna is used) Null column allowed: Yes Default value: HEIGHT Float Height of the receiver Null column allowed: No Default value: 2 LOSS Float Losses due to receiver radio equipment (up and downlink) Null column allowed: No Default value: 0 NAME Text (50) Receiver name Null column allowed: No Default value: 8.6.1.17 Equipment Management Tables These tables Model TMA, feeders, and BTS equipment properties. 8.6.1.17.1 TMAEquipments Table Field Type Description Attributes DL_LOSSES Float Downlink losses of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 NAME Text (50) Name of Tower Mounted Amplifier Null column allowed: No Default value: NOISE_FIGURE Float Noise figure of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 UL_GAIN Float Uplink gain of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 8.6.1.17.2 FeederEquipments Table Field Type Description Attributes CONNECTOR_LOSSES_UL Float Feeder connector losses in uplink Null column allowed: Yes Default value: 0 CONNECTOR_LOSSES_DL Float Feeder connector losses in downlink Null column allowed: Yes Default value: 0 LOSS_PER_METER Float Feeder loss per meter Null column allowed: Yes Default value: 0 NAME Text (50) Name of Feeder Null column allowed: No Default value: 8.6.1.17.3 BTSEquipments Table Field Type Description Attributes NAME Text (50) Name of Base Station Equipment Null column allowed: No Default value: NOISE_FIGURE Float Noise figure of Base Station Null column allowed: Yes Default value: 0 CONFIG_DL_LOSSES Float Downlink losses due to the configuration of the BTS (duplexer and/or combiner) Null column allowed: Yes Default value: 0 CONFIG_UL_LOSSES Float Uplink losses due to the configuration of the BTS (duplexer and/or combiner) Null column allowed: Yes Default value: 0 RHO_FACTOR Short Rho factor to model self generated interference (100%=ideal) Null column allowed: Yes Default value: 100 © Forsk 2009 AT281_AM_E1 305 Administrator Manual 8.6.1.18 Neighbour Management Tables 8.6.1.18.1 Neighbours Table This table stores neighbourhood relationships between cells of the same .atl document (intra-technology neighbours). Field Type Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: 1 NEIGHBOUR Text (50) Second part of the unique key. List of neighbours Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: REASON Integer Reason of the neighbourhood Null column allowed: Yes Default value: 0 (Manual) Choice list: Manual, Forced, Co-site, Adjacent, Symmetric, Distance, Coverage TRANSMITTER Text (50) First part of the unique key. Transmitters or cells Null column allowed: No Default value: TYPE Text (50) Type of the neighbourhood (handover, measurement…) Null column allowed: Yes Default value: FORCE_HHO Boolean Force Handover type to hard handover in case of intra-carriers neighbours Null column allowed: No Default value: False 8.6.1.18.2 NeighboursExt Table This table stores neighbourhood relationships between transmitters/cells of different .atl documents (inter-technology neighbours). Field Type Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: NEIGHBOUR Text (50) Second part of the unique key. List of neighbours from another project Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: REASON Integer Reason of the neighbourhood Null column allowed: Yes Default value: 0 (Manual) Choice list: Manual, Forced, Co-site, Adjacent, Symmetric, Distance, Coverage TRANSMITTER Text (50) First part of the unique key. Transmitters or cells Null column allowed: No Default value: TYPE Text (50) Type of the neighbourhood (handover, measurement…) Null column allowed: Yes Default value: 8.6.1.18.3 NeighboursConstraints Table This table enables you set handover relationships between cells. These constraints are used as input for automatic neighbour allocation. Field Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: NEIGHBOUR Text (50) Second part of the unique key. List of neighbours Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: Integer Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. Null column allowed: Yes Default value: 0 Choice list: 0=Forced, 1=Forbidden STATUS 306 Type AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure TRANSMITTER Text (50) First part of the unique key. Transmitters or cells. Null column allowed: No Default value: FORCE_HHO Boolean Force Handover type to hard handover in case of intra-carriers neighbours Null column allowed: No Default value: False 8.6.1.18.4 NeighboursConstraintsExt Table This table enables you to set external handover relationships (with transmitters/cells of another project). These constraints are used as input for automatic neighbour allocation. Field Type Description Attributes IMPORTANCE Float Handover importance (for AFP use) Null column allowed: Yes Default value: NEIGHBOUR Text (50) Second part of the unique key. List of neighbours from another project. Null column allowed: No Default value: RANK Float Order of the neighbourhood (not strict order relation) Null column allowed: Yes Default value: STATUS Integer Type of constraint on the neighbourhood relationship. Constraint is used in automatic allocation. Null column allowed: Yes Default value: 0 Choice list: 0=Forced, 1=Forbidden TRANSMITTER Text (50) First part of the unique key. Transmitters or cells Null column allowed: No Default value: 8.6.1.19 Transmitters Table This table stores the transmitters and their properties. Field Type Description Attributes ACTIVE Boolean Transmitter activity: 'Yes' means that the transmitter is active Null column allowed: No Default value: True ANTDIVGAIN Float Antenna diversity gain Null column allowed: Yes Default value: 0 ANTENNA_NAME Text (50) Name of the main antenna installed on the transmitter Null column allowed: Yes Default value: AZIMUT Float Azimuth of the main antenna Null column allowed: Yes Default value: 0 BTS_NAME Text (50) Name of the BTS equipment Null column allowed: Yes Default value: CALC_RADIUS Integer Calculation radius used to define the calculation area Unit: m Null column allowed: Yes Default value: 4000 CALC_RADIUS2 Integer Extended calculation radius Null column allowed: Yes Default value: CALC_RESOLUTION Integer Calculation resolution Null column allowed: Yes Default value: 50 CALC_RESOLUTION2 Integer Extended calculation resolution Null column allowed: Yes Default value: CELL_SIZE Float Hexagon radius Unit: m Null column allowed: Yes Default value: 2000 COMMENT_ Text (255) Additional information about the transmitter Null column allowed: Yes Default value: DX Float X coordinate relative to the site location Null column allowed: Yes Default value: 0 DY Float Y coordinate relative to the site location Null column allowed: Yes Default value: 0 FEEDER_NAME Text (50) Name of the feeder equipment Null column allowed: Yes Default value: FEEDERLENGTH_DL Float Length of feeder in DL Null column allowed: Yes Default value: 0 FEEDERLENGTH_UL Float Length of feeder in UL Null column allowed: Yes Default value: 0 HEIGHT Float Antenna height above the ground Unit: m Null column allowed: Yes Default value: 25 HEXAGON_GROUP Text (50) Group of hexagons used to create this transmitter Null column allowed: Yes Default value: © Forsk 2009 AT281_AM_E1 307 Administrator Manual MISCDLL Float Miscellaneous DL loss Null column allowed: Yes Default value: 0 MISCULL Float Miscellaneous UL loss Null column allowed: Yes Default value: 0 PROPAG_MODEL Text (255) Name of the propagation model used to calculate prediction Null column allowed: Yes Default value: ’Default model’ PROPAG_MODEL2 Text (255) Name of the propagation model used to calculate extended prediction Null column allowed: Yes Default value: SITE_NAME Text (50) Name of the site on which the transmitter is located (from the site table of Atoll) Null column allowed: No Default value: TILT Float Mechanical downtilt of the first antenna Null column allowed: Yes Default value: 0 TMA_NAME Text (50) Name of the TMA equipment Null column allowed: Yes Default value: TX_ID Text (50) Transmitter name Null column allowed: No Default value: FBAND Text (50) Frequency band Null column allowed: No Default value: NOISE_FIGURE Float Noise figure used to determine the thermal noise at the transmitter Null column allowed: Yes Default value: 5 RXLOSSES Float Losses in the uplink due to transmitter radio equipment Null column allowed: Yes Default value: 0 TXLOSSES Float Losses in the downlink due to transmitter radio equipment Null column allowed: Yes Default value: 0 COV_PROBA Short Cell edge Coverage probability per Transmitter Null column allowed: Yes Default value: 75 MAX_RANGE Integer Maximum range (m) of coverage (for extended cells) Null column allowed: Yes Default value: 35000 MIN_RANGE Integer Minimum range (m) of coverage (for extended cells) Null column allowed: Yes Default value: 0 REDT Float Remote Electrical tilt Null column allowed: Yes Default value: 0 SA_NAME Text (50) Name of the associated smart antenna (if empty, the standard antenna is used) Null column allowed: Yes Default value: N_FREQUENCY Boolean N-frequency mode. 'Yes' means that the transmitter has one master carrier and slaves carriers; otherwise all its carriers are standalone Null column allowed: No Default value: False TX_DIVERSITY_CFG Short TX diversity configuration. 1 = No TX diversity 2 = TX div. open loop 3 = TX div. closed loop Null column allowed: Yes Default value: 0 NUM_RX_ANTENNAS Short Number of transmission antenna ports available at the transmitter Null column allowed: No Default value: 1 NUM_TX_ANTENNAS Short Number of reception antenna ports available at the transmitter Null column allowed: No Default value: 1 8.6.1.20 TplTransmitters Table This table is used to store station templates and their properties. Field Type Description Attributes ACTIVE Boolean Transmitter activity: 'Yes' means that the transmitter is active Null column allowed: No ANTDIVGAIN Float Antenna diversity gain Unit: dB Null column allowed: Yes ANTENNA_NAME Text (50) Name of the main antenna installed on the transmitter Null column allowed: Yes AZIMUT Float Azimuth of the first antenna Null column allowed: Yes BTS_NAME Text (50) Name of the BTS equipment Null column allowed: Yes CALC_RADIUS Integer Calculation radius used to define each transmitter calculation area Unit: m Null column allowed: Yes CALC_RADIUS2 Integer Extended calculation radius Unit: m Null column allowed: Yes CALC_RESOLUTION Integer Calculation resolution Null column allowed: Yes CALC_RESOLUTION2 Integer Extended calculation resolution Null column allowed: Yes 308 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure CELL_SIZE Float Hexagon radius Unit: m Null column allowed: Yes FEEDER_NAME Text (50) Name of the feeder equipment Null column allowed: Yes FEEDERLENGTH_DL Float Length of downlink feeder Unit: m Null column allowed: Yes FEEDERLENGTH_UL Float Length of uplink feeder Unit: m Null column allowed: Yes HEIGHT Float Antenna height above the ground Unit: m Null column allowed: Yes MAX_NEIGHB_NUMBER Short Maximum number of neighbours for the cell or the transmitter Null column allowed: Yes MAX_EXT_NEIGHB_NUMBE R Short Maximum number of inter-technology neighbours for the cell or the transmitter Null column allowed: Yes MISCDLL Float Miscellaneous downlink losses Null column allowed: Yes MISCULL Float Miscellaneous uplink losses Null column allowed: Yes NAME Text (50) Template name Null column allowed: No NUM_SECTORS Integer Number of sectors Null column allowed: Yes PROPAG_MODEL Text (255) Name of the propagation model used to calculate predictions Null column allowed: Yes PROPAG_MODEL2 Text (255) Name of the propagation model used to calculate extended prediction Null column allowed: Yes TILT Float Mechanical downtilt of the main antenna Null column allowed: Yes TMA_NAME Text (50) Name of the Tower Mounted Amplifier equipment Null column allowed: Yes CARRIERS Text (50) Carriers used by the transmitter Null column allowed: Yes FBAND Text (50) Frequency band Null column allowed: No NOISE_FIGURE Float Noise figure used to determine the thermal noise at the transmitter Null column allowed: Yes PILOT_POWER Float Power of the pilot channel Null column allowed: Yes POWER_MAX Float Maximum power supported by the transmitter Null column allowed: Yes RXLOSSES Float Losses in the uplink due to transmitter radio equipment Unit: dB Null column allowed: Yes TOTAL_POWER Float Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm Null column allowed: Yes TXLOSSES Float Losses in the downlink due to transmitter radio equipment Unit: dB Null column allowed: Yes UL_LOAD Float Uplink transmitter load factor: manually specified by the user or calculated by the WCDMA simulation algorithm Null column allowed: Yes CHANNEL_ELEMENTS_DL Integer Number of channel elements for downlink Null column allowed: Yes CHANNEL_ELEMENTS_UL Integer Number of channel elements for uplink Null column allowed: Yes CDMA_EQUIPMENT Text (50) CDMA equipment Null column allowed: Yes REUSE_DIST Float Minimum reuse distance for scrambling codes Null column allowed: Yes OTHERS_CCH_POWER Float Power of common channels (except SCH) Null column allowed: Yes SC_DOMAIN_NAME Text (50) Scrambling code domain name Null column allowed: Yes SCH_POWER Float Power of the synchronisation (SCH) channel Null column allowed: Yes COV_PROBA Short Cell edge Coverage probability per Transmitter Null column allowed: Yes MAX_RANGE Integer Maximum range (m) of coverage (for extended cells) Null column allowed: Yes MIN_RANGE Integer Minimum range (m) of coverage (for extended cells) Null column allowed: Yes REDT Float Remote Electrical tilt Null column allowed: Yes MAX_UL_LOAD Float Maximum uplink load allowed (percentage). Used in power control simulation Null column allowed: Yes MAX_DL_LOAD Float Maximum downlink load allowed (percentage of max power used). Used in power control simulation Null column allowed: Yes SA_NAME Text (50) Name of the associated smart antenna (if empty, the standard antenna is used) Null column allowed: Yes PWC_LIMIT Float Maximum difference between two DCH powers transmitted by a cell (dB) Null column allowed: Yes TS_CONFIG Float Timeslot configuration (1-DUDDDDD 2-DUUDDDD 3-DUUUDDD 4DUUUUDD 5-DUUUUUD 6-DUUUUUU) Null column allowed: Yes DWPCH_POWER Float Power on the DwPTS timeslot Null column allowed: Yes DYN_HS_SCCH_POWER_A LLOC Boolean Allocation of power for HS_SCCH (True=Dynamic, False=Static) Null column allowed: No © Forsk 2009 AT281_AM_E1 309 Administrator Manual DYN_HSDPA_POWER_ALL OC Boolean Allocation of power for HSDPA (True=Dynamic, False=Static) Null column allowed: No ENABLE_HSDPA Boolean Cell supports or not HSDPA channels Null column allowed: No HS_SCCH_POWER Float Value of power dedicated to a HS_SCCH channel. In case of dynamic allocation, it is the maximum available power. Null column allowed: Yes HSDPA_MAX_CODES Short Maximum number of HS-PDSCH codes Null column allowed: Yes HSDPA_MAX_USERS Short Max number of HSDPA users managed simultaneously by the scheduler Null column allowed: Yes HSDPA_MIN_CODES Short Minimum Number of HS-PDSCH codes Null column allowed: Yes HSDPA_PWR Float Amount of power (dBm) dedicated to HSDPA Null column allowed: Yes HSDPA_SCHEDULER_ALG O Short Scheduling algo used for HSDPA users. 0=MAXC/I (MAx C/I), 1=RR (Round Robin), 2=PF (Proportional Fair) Null column allowed: Yes NUM_HS_SCCH Short Number of HS_SCCH channels Null column allowed: Yes PWR_HEADROOM Float Power Control Headroom (dB) for DCH (used in WCDMA simulation algorithm) Null column allowed: Yes UPPCH_POWER Float Power on the UpPTS timeslot Null column allowed: Yes N_FREQUENCY Boolean N-frequency mode. 'Yes' means that the transmitter has one master carrier and slaves carriers; otherwise all its carriers are standalone Null column allowed: No DYN_HS_SICH_POWER_AL LOC Boolean Allocation of power for HS-SICH (True=Dynamic, False=Static) Null column allowed: No NUM_HS_SICH Short Number of HS-SICH channels per cell Null column allowed: Yes NUM_RX_ANTENNAS Short Number of transmission antenna ports available at the transmitter Null column allowed: Yes NUM_TX_ANTENNAS Short Number of reception antenna ports available at the transmitter Null column allowed: Yes DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes REQ_UL_RUS Integer Required resource units in uplink Null column allowed: Yes REQ_DL_RUS Integer Required resource units in downlink Null column allowed: Yes 8.6.1.21 Repeaters Table This table manages repeaters and repeater properties. 310 Field Type Description Attributes AMPLIFIER_GAIN Float Gain of the amplifier Null column allowed: Yes Default value: 80 AZIMUT Float Azimuth of the donor side antenna Null column allowed: Yes Default value: 0 DONOR_CELLID Text (50) Name of the donor cell Null column allowed: No Default value: DOWNTILT Float Downtilt of the donor side antenna Null column allowed: Yes Default value: 0 FEEDER_NAME Text (50) Name of the donor side feeder Null column allowed: Yes Default value: FEEDERLENGTH Float Length of donor side feeder Null column allowed: Yes Default value: 0 HEIGHT Float Height of the donor side antenna Null column allowed: Yes Default value: 25 REC_ANTENNA Text (50) Name of the donor side antenna Null column allowed: Yes Default value: TX_ID Text (50) Name of the transmitter (and of the transmitter used for coverage) Null column allowed: No Default value: TOTAL_GAIN Float Total gain to be applied to donor cell pilot power Null column allowed: Yes Default value: 0 DONOR_LINK_TYPE Short 1- Off air 2- Microwave 3- Fibre Null column allowed: No Default value: 1 DONOR_LINK_LOSS Float Loss (dB) between donor and donor side of the repeater Null column allowed: Yes Default value: 0 EQUIPMENT_NAME Text (50) If no equipment, the repeater is a passive component Null column allowed: Yes Default value: AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure REC_FEEDERLENGTH_UL Float Length of donor side uplink feeder Null column allowed: Yes Default value: 0 TOTAL_GAIN_UL Float Uplink total gain to be applied to mobile output power Null column allowed: Yes Default value: 0 DONOR_PROPAG_MODEL Text (50) Name of the propagation model used to calculate prediction between donor and repeater Null column allowed: Yes Default value: Note: • 8.6.1.22 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. RepeaterEquipments Table This table models the equipment used by repeaters. Field Type Description Attributes NAME Text (50) Name of the repeater equipment Null column allowed: No Default value: MANUFACTURER Text (50) Manufacturer of the repeater equipment Null column allowed: Yes Default value: NOISE_FIGURE Float Repeater noise Figure (dB) Null column allowed: Yes Default value: 5 MIN_AMPLIFIER_GAIN Float Minimum gain of the amplifier (dB) Null column allowed: Yes Default value: 50 MAX_AMPLIFIER_GAIN Float Maximum gain of the amplifier (dB) Null column allowed: Yes Default value: 90 STEP_AMPLIFIER_GAIN Float Step of amplifier gain (dB) Null column allowed: Yes Default value: 1 MAX_OUTPUT_UL Float Maximum uplink output power (dBm) Null column allowed: Yes Default value: 12 MAX_OUTPUT_DL Float Maximum downlink output power (dBm) Null column allowed: Yes Default value: 30 TIME_DELAY Float Time delay in the equipment (microseconds) Null column allowed: Yes Default value: 5 COMMENT_ Text (255) Comments Null column allowed: Yes Default value: 8.6.1.23 Scrambling Code Management Tables These tables store constraints (the range of available scrambling codes, pairs of cells which cannot be assigned the same scrambling codes) used as input for automatic scrambling code allocation. 8.6.1.23.1 ScramblingCodesDomains Table Field Type Description Attributes DOMAIN_NAME Text (50) Resource domain name Null column allowed: No Default value: 8.6.1.23.2 ScramblingCodesGroups Table Field Type Description Attributes DOMAIN_NAME Text (50) Second part of the unique key. Called grouping scheme. Set of scrambling code groups. Null column allowed: No Default value: EXCLUDED Text (225) List of codes to be excluded from the series defined by FIRST, LAST and STEP (separated by blank characters) Null column allowed: Yes Default value: EXTRA Text (225) Codes to be added. It is forbidden for EXTRA and EXLUDED to have common numbers. Separator must be a blank character. Null column allowed: Yes Default value: FIRST Integer 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 LAST Integer 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 © Forsk 2009 AT281_AM_E1 311 Administrator Manual NAME Text (50) First part of the unique key. Name of the scrambling code group Null column allowed: No Default value: STEP Integer 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: 1 8.6.1.23.3 Separations Table Field Type Description Attributes TX_ID Text (50) First part of the unique key. First cell name in a symmetric relation Null column allowed: No Default value: TX_ID_OTHER Text (50) Second part of the unique key. Second cell name in a symmetric relation Null column allowed: No Default value: 8.6.1.23.4 CodesRelativityClusters Table This table models scrambling code clusters. Field Type Description Attributes NAME Text (50) Name of the cluster of scrambling codes Null column allowed: No Default value: CODES_LIST Text (255) Coma separated list of codes belonging to the cluster Null column allowed: No Default value: 8.6.1.24 CDMACells Table This table stores cells and their properties. Field Type Description Attributes CARRIER Integer Carrier number Null column allowed: Yes Default value: 0 CELL_ID Text (50) Name of the cell Null column allowed: No Default value: COMMENT_ Text (255) Additional information about the cell Null column allowed: Yes Default value: MAX_NEIGHB_NUMBER Integer Maximum number of neighbours for the cell Null column allowed: Yes Default value: MAX_EXT_NEIGHB_NUMBE R Integer Maximum number of inter-technology neighbours for the cell Null column allowed: Yes Default value: PILOT_POWER Float Power of the pilot channel Null column allowed: Yes Default value: 33 POWER_MAX Float Maximum power supported by the transmitter Null column allowed: Yes Default value: 43 REUSE_DIST Float Minimum reuse distance for scrambling codes Null column allowed: Yes Default value: TX_ID Text (50) Name of the transmitter Null column allowed: No Default value: SC_DOMAIN_NAME Text (50) Scrambling code domain name. Null column allowed: Yes Default value: SCH_POWER Float Power of the synchronisation (SCH) channel Null column allowed: Yes Default value: 21 SCRAMBLING_CODE Integer Scrambling code. Null column allowed: Yes Default value: PWC_LIMIT Short Maximum difference between two DCH powers transmitted by a cell (dB) Null column allowed: Yes Default value: 20 TS_CONFIG Integer Timeslot configuration (1-DUDDDDD 2-DUUDDDD 3-DUUUDDD 4-DUUUUDD 5-DUUUUUD 6-DUUUUUU) Null column allowed: Yes Default value: 3 REQ_UL_RUS Short Required resource units in uplink Null column allowed: Yes Default value: 0 REQ_DL_RUS Short Required resource units in downlink Null column allowed: Yes Default value: 0 DWPCH_POWER Float Power on the DwPTS timeslot Null column allowed: Yes Default value: 36 312 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure DYN_HS_SCCH_POWER_A LLOC Boolean Allocation of power for HS_SCCH (True=Dynamic, False=Static) Null column allowed: No Default value: True DYN_HSDPA_POWER_ALL OC Boolean Allocation of power for HSDPA (True=Dynamic, False=Static) Null column allowed: No Default value: True ENABLE_HSDPA Boolean Cell supports or not HSDPA channels Null column allowed: No Default value: False HS_SCCH_POWER Float Value of power dedicated to a HS-SCCH channel. In case of dynamic allocation, it is the maximum available power. Null column allowed: Yes Default value: HSDPA_MAX_CODES Short Maximum number of HS-PDSCH codes Null column allowed: Yes Default value: 16 HSDPA_MAX_USERS Short Max number of HSDPA users managed simultaneously by the scheduler Null column allowed: Yes Default value: 64 HSDPA_MIN_CODES Short Minimum Number of HS-PDSCH codes Null column allowed: Yes Default value: 0 HSDPA_PWR Float Amount of power (dBm) dedicated to HSDPA Null column allowed: Yes Default value: HSDPA_SCHEDULER_ALG O Short Scheduling algo used for HSDPA users. 0 = MAX C/I, 1 = Round Robin, 2 = Proportional Fair. Null column allowed: Yes Default value: 2 NUM_HS_SCCH Short Number of HS-SCCH channels Null column allowed: Yes Default value: 5 PWR_HEADROOM Float Power Control Headroom (dB) for DCH (used in WCDMA simulation algorithm) Null column allowed: Yes Default value: 0 ACTIVE Boolean Cell's activity: 'Yes' means that the cell is active Null column allowed: No Default value: True MASTER Boolean If true, the cell is a master cell, if false it is a slave cell which does not have its own pilot and is considered as an extension of the master cell Null column allowed: No Default value: False OTHERS_CCH_POWER Float Power on the other common channels for TS0 (S-CCPCH, FPACH, PICH) Null column allowed: Yes Default value: 0 RSCP_COMP Float P-CCPCH RSCP margin to trigger Baton Handover Null column allowed: Yes Default value: 5 DYN_HS_SICH_POWER_AL LOC Boolean Allocation of power for HS-SICH (True=Dynamic, False=Static) Null column allowed: No Default value: True NUM_HS_SICH Short Number of HS-SICH channels per cell Null column allowed: Yes Default value: 5 CELL_IDENTITY Integer Cell identity Null column allowed: Yes Default value: DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes Default value: 0 UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes Default value: 0 8.6.1.25 CDMACellsTS Table This table stores cell parameter per timeslot. Field Type Description Attributes BLOCKED Boolean Allow to block the timeslot: 'Yes' means that the timeslot is blocked Null column allowed: No Default value: False CELL_ID Text (50) Name of the cell Null column allowed: No Default value: DL_ANGULAR_POWERS Binary Angular distribution of downlink transmitted power Null column allowed: Yes Default value: MAX_DL_LOAD Float Maximum downlink load allowed (percentage of max power used). Used in power control simulation Null column allowed: Yes Default value: 75 MAX_UL_LOAD Float Maximum uplink load allowed (percentage). Used in power control simulation Null column allowed: Yes Default value: 50 OTHERS_CCH_POWER Float Power on the other common channels Null column allowed: Yes Default value: -200 RU_OVERHEAD Short Overhead due to signalling channels Null column allowed: Yes Default value: 0 TIME_SLOT Short Time slot number Null column allowed: No Default value: © Forsk 2009 AT281_AM_E1 313 Administrator Manual TOTAL_POWER Float Total downlink power: manually specified by the user or calculated by the WCDMA simulation algorithm Null column allowed: Yes Default value: UL_ANGULAR_LOADS Memo Angular distribution of uplink interference Null column allowed: Yes Default value: UL_LOAD Float Uplink cellr load factor: manually specified by the user or calculated by the WCDMA simulation algorithm Null column allowed: Yes Default value: HSDPA_MAX_CODES Short Maximum number of HS-PDSCH codes Null column allowed: Yes Default value: HSDPA_MIN_CODES Short Minimum number of HS-PDSCH codes Null column allowed: Yes Default value: HSDPA_PWR Float Amount of power (dBm) dedicated to HSDPA Null column allowed: Yes Default value: TIME_SLOT_TYPE Short Type of timeslot (0 = R99, 1 = HSDPA, 2 = R99 + HSDPA) Null column allowed: Yes Default value: 0 8.6.1.26 CDMAEquipments Table This table models equipment that performs radio resource management at site level. Field Type Description Attributes MANUFACTURER Text (50) Name of the manufacturer Null column allowed: Yes Default value: MUD_FACTOR Float MUD factor for UL interference cancellation Null column allowed: No Default value: 0 NAME Text (50) Equipment name Null column allowed: No Default value: MCJD_FACTOR Float Multi cell joint detection factor for extra cell UL interference cancellation Null column allowed: No Default value: 0 8.6.1.27 CDMAEquipmentsCEsUse Table This table contains information about consumption of channel elements. Field Type Description Attributes CHANNEL_ELTS_DL Integer Number of channel elements used for downlink Null column allowed: No Default value: 1 CHANNEL_ELTS_UL Integer Number of channel elements used for uplink Null column allowed: No Default value: 1 EQUIPMENT Text (50) First part of the unique key. Name of equipment Null column allowed: No Default value: SERVICE Text (50) Second part of the unique key. Service name. Null column allowed: No Default value: 8.6.1.28 Multi-Service Traffic Management These tables contain descriptions of multi-service traffic data, i.e., services, mobility types, terminals, user profiles, and environments. 8.6.1.28.1 UMTSEnvironmentDefs Table Field Description Attributes DENSITY Float Number of subscribers per km2 Null column allowed: Yes Default value: 0 ENVIRONMENT Text (50) Environment name Null column allowed: No Default value: MOBILITY Text (50) Type of mobility Null column allowed: No Default value: USER_PROFILE Text (255) Type of user profile Null column allowed: No Default value: 8.6.1.28.2 314 Type UMTSMobility Table Field Type Description Attributes NAME Text (50) Type of mobility Null column allowed: No Default value: AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure TADD Float Minimum Ec/Io for best server selection Null column allowed: Yes Default value: 7 MEAN_SPEED Float Mean mobile speed (km/h) used for HSDPA Null column allowed: Yes Default value: 0 RSCP_MIN Short Minimum P-CCPCH RSCP for cell selection (dBm) Null column allowed: Yes Default value: -84 DWPCH_RSCP Float Minimum DwPCH RSCP (dBm) Null column allowed: Yes Default value: -100 HSSCCH_ECNT Float HS-SCCH Ec/Nt target for HSDPA Null column allowed: Yes Default value: -12 HSSICH_ECNT Float HS-SICH uplink Ec/Nt target for HSDPA Null column allowed: Yes Default value: -12 RSCP_DROP Float P-CCPCH RSCP for cell dropping (Baton Handover) Null column allowed: Yes Default value: -95 DWPCH_QUALITY Float Quality target for the DwPCH (dB) Null column allowed: Yes Default value: 2 UPPCH_RSCP Float Minimum UpPCH RSCP (dBm) Null column allowed: Yes Default value: -100 8.6.1.28.3 UMTSServicesQuality Table Field Type Description Attributes MOBILITY Text (50) Second part of the unique key. Type of mobility Null column allowed: No Default value: SERVICE Text (50) First part of the unique key. Name of the service Null column allowed: No Default value: DL_TARGET_QUAL Float Eb/Nt target on the downlink for a type of mobility Null column allowed: Yes Default value: 0 UL_TARGET_QUAL Float Eb/Nt target on the uplink for a type of mobility Null column allowed: Yes Default value: 0 RX_EQUIP Text (50) Type of receiver Null column allowed: No Default value: TCH_THRESHOLD_UL Short RSCP TCH target on uplink for a type of mobility Null column allowed: Yes Default value: 0 TCH_THRESHOLD_DL Short RSCP TCH target on downlink for a type of mobility Null column allowed: Yes Default value: 0 DL_TGT_QUAL_DIVCLOSE D Float Quality target on downlink in case of closed loop TX diversity Null column allowed: Yes Default value: 0 DL_TGT_QUAL_DIVOPEN Float Quality target on downlink in case of open loop TX diversity Null column allowed: Yes Default value: 0 UL_TGT_QUAL_DIV2RX Float Quality target on uplink in case of 2RX diversity Null column allowed: Yes Default value: 0 UL_TGT_QUAL_DIV4RX Float Quality target on uplink in case of 4RX diversity Null column allowed: Yes Default value: 0 8.6.1.28.4 UMTSServicesUsage Table Field Type Description Attributes CALL_DURATION Float Average duration of a call (for circuit switched services) Unit: s Null column allowed: Yes Default value: CALL_NUMBER Float Average number of calls per hour for circuit switched services or average number of sessions per hour for packet switched services Null column allowed: Yes Default value: 0 SERVICE Text (50) Service that the subscriber may request Null column allowed: No Default value: TERMINAL Text (50) Type of terminal used by the subscriber for the service Null column allowed: No Default value: USER_PROFILE Text (255) User profile name Null column allowed: No Default value: © Forsk 2009 AT281_AM_E1 315 Administrator Manual DL_VOLUME Float Data volume transferred on the downlink during a session (for packet switched services) Unit: Kbyte Null column allowed: Yes Default value: UL_VOLUME Float Data volume transferred on the uplink during a session (for packet switched services) Unit: Kbyte Null column allowed: Yes Default value: 8.6.1.28.5 UMTSServices Table Field Type Description Attributes BODY_LOSS Float Body loss Null column allowed: No Default value: 0 NAME Text (50) Service name Null column allowed: No Default value: PRIORITY Integer Priority level of the service: parameter used in the WCDMA simulation Null column allowed: Yes Default value: 0 DL_ACTIVITY Float Activity factor for circuit switched service on the downlink Null column allowed: Yes Default value: DL_PACKET_EFFICIENCY Float Packet efficiency factor on the downlink Null column allowed: Yes Default value: UL_ACTIVITY Float Activity factor for circuit switched service on the uplink Null column allowed: Yes Default value: UL_PACKET_EFFICIENCY Float Packet efficiency factor on the uplink Null column allowed: Yes Default value: CARRIER Integer Carrier supporting the service. -1 means that all carriers can be used. Null column allowed: No Default value: -1 TH_SCALE_FACTOR Float Ratio between application throughput and RLC layer throughput Null column allowed: No Default value: 95 TH_OFFSET Float Offset to add to the above ratio Null column allowed: No Default value: 0 UL_NPC Integer Number of packet calls during a session on the uplink Null column allowed: Yes Default value: 1 UL_DPC Float Reading time (distance) between two packet calls (ms) on the uplink Null column allowed: Yes Default value: 0 UL_DP Float Packet inter arrival time (ms) on the uplink Null column allowed: Yes Default value: 0 UL_SP Integer Packet size (Bytes) on the uplink Null column allowed: Yes Default value: 1500 UL_SPC_MIN Float Uplink min Packet call size (kBytes) Null column allowed: Yes Default value: 4 UL_SPC_MAX Float Uplink max Packet call size (kBytes) Null column allowed: Yes Default value: 2000 DL_NPC Integer Number of packet calls during a session on the downlink Null column allowed: Yes Default value: 1 DL_DPC Float Reading time (distance) between two packet calls (ms) on the downlink Null column allowed: Yes Default value: 0 DL_DP Float Packet inter arrival time (ms) on the downlink Null column allowed: Yes Default value: 0 DL_SP Integer Packet size (Bytes) on the downlink Null column allowed: Yes Default value: 1500 DL_SPC_MIN Float Downlink min Packet call size (kBytes) Null column allowed: Yes Default value: 4 DL_SPC_MAX Float Downlink max Packet call size (kBytes) Null column allowed: Yes Default value: 2000 ENABLE_HSDPA Boolean Service can use HSDPA channels Null column allowed: No Default value: False REQ_AVERAGE_DL_RATE Float Requested Average Downlink Rate (kbps) Null column allowed: Yes Default value: REQ_AVERAGE_UL_RATE Float Requested Average Uplink Rate (kbps) Null column allowed: Yes Default value: R99BEARER Text (50) Name of the R99 Bearer Null column allowed: Yes Default value: 316 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure REQ_MIN_DL_RATE Float Requested Minimum Downlink Rate (kbps) Null column allowed: Yes Default value: 0 REQ_MIN_UL_RATE Float Requested Minimum Uplink Rate (kbps) Null column allowed: Yes Default value: 0 TYPE Short Type of service (0: circuit; 1: packet; 2: circuit over packet) Null column allowed: No Default value: 0 8.6.1.28.6 R99Bearers Table Field Type Description Attributes NAME Text (50) R99 bearer name Null column allowed: No Default value: DL_NOMINAL_BIT_RATE Float Bearer nominal data rate on the downlink Unit: kbps Null column allowed: Yes Default value: 9.6 UL_NOMINAL_BIT_RATE Float Bearer nominal data rate on the uplink Unit: kbps Null column allowed: Yes Default value: 9.6 PTCH_MAX Float Maximum DL transmitter power on traffic channel for the bearer Null column allowed: Yes Default value: 21 PTCH_MIN Float Minimum DL transmitter power on traffic channel for the bearer Null column allowed: Yes Default value: -20 TS_UL Short Number of TS used for UL Null column allowed: Yes Default value: 1 TS_DL Short Number of TS used for DL Null column allowed: Yes Default value: 1 UL_PG Float Uplink processing gain Null column allowed: Yes Default value: 0 DL_PG Float Downlink processing gain Null column allowed: Yes Default value: 0 TYPE Short Bearer type (0: Empty, 1: Interactive, 2: Conversational, 3: Background ,4: Streaming) Null column allowed: Yes Default value: 0 8.6.1.28.7 HSDPA Bearers Modelling Tables These tables model HSDPA service bearers. HSDPABearers Table Field Type Description Attributes BEARER_INDEX Short Unique key to address bearer Null column allowed: No Default value: 1 TRANSPORT_BL_SIZE Integer Transport Block Size (bits) Null column allowed: Yes Default value: 0 HSPDSCH_NUM Short Number of HS_PDSCH channels used Null column allowed: Yes Default value: 5 USE_16QAM Boolean True if 16QAM modulation is enabled Null column allowed: No Default value: False RLC_PEAK_THROUGHPUT Float Peak RLC throughput (without BLER consideration) Null column allowed: Yes Default value: 0 TS_NUM Short Number of time slots used per subframe Null column allowed: Yes Default value: 1 UE_CATEGORY Short Associated UE category [1-15] Null column allowed: No Default value: 1 HSDPABearerSelectTables Table Field Type Description Attributes MOBILITY Text (50) UE mobility Null column allowed: Yes Default value: RX_EQUIP Text (50) Type of receiver of the User Equipment Null column allowed: Yes Default value: “Standard” BEARER_INDEX Short Bearer index Null column allowed: No Default value: 0 HSPDSCH_ECNT_REQ Float Requried HS-PDSCH Ec/Nt Null column allowed: Yes Default value: 5 © Forsk 2009 AT281_AM_E1 317 Administrator Manual 8.6.1.28.8 UMTSTerminals Table Field Type Description Attributes GAIN Float Receiver antenna gain Null column allowed: Yes Default value: 0 LOSS Float Receiver antenna loss Null column allowed: Yes Default value: 0 NAME Text (50) Terminal name Null column allowed: No Default value: NOISE_FACTOR Float Noise figure used to determine the thermal noise at the receiver Null column allowed: Yes Default value: 8 PMAX Float Maximum receiver power on traffic channel Null column allowed: Yes Default value: 21 PMIN Float Minimum receiver power on traffic channels Null column allowed: Yes Default value: -50 UPPCH_POWER Float Power on the UpPTS timeslot Null column allowed: Yes Default value: -50 RHO_FACTOR Short Rho factor to model self generated interference Null column allowed: No Default value: 100 RX_EQUIP Text (50) Type of the User Equipment Receiver Null column allowed: Yes Default value: ‘Standard’ MUD_FACTOR Float Advanced Receiver Factor to model intra-cell interference reduction for HSDPA terminals only Null column allowed: Yes Default value: 0 ENABLE_HSDPA Boolean Terminal supports HSDPA channels Null column allowed: No Default value: False UE_CATEGORY Float Category of the User Equipment for HSDPA Null column allowed: Yes Default value: 1 CARRIER_NUMBER Short Number of carriers supported by the terminal Null column allowed: Yes Default value: 1 HSSICH_POWER Float Maximum power on HS-SICH channels Null column allowed: Yes Default value: 21 8.6.1.28.9 UMTSTraficEnvironments Table Field Type Description Attributes CLUTTER_WEIGHTS Binary Internal binary format describing weights assigned to each clutter class Null column allowed: Yes Default value: Yes NAME Text (50) Name of the created environment Null column allowed: No Default value: 8.6.1.28.10 Field NAME 8.6.1.29 UMTSUserProfiles Table Type Text (50) Description Attributes Name of the created user profile Null column allowed: No Default value: ServiceQualityTables Table This table stores quality graphs used for different reception equipment and quality indicators. 318 Field Type Description Attributes SERVICE Text (50) Name of the service (can be null for some QI) Null column allowed: No Default value: QI_NAME Text (50) Name of the Quality Indicator Null column allowed: No Default value: RX_EQUIP Text (50) Type of receiver of the User Equipment Null column allowed: No Default value: ’Standard’ MOBILITY Text (50) UE mobility Null column allowed: Yes Default value: DL_QI_TABLE Memo QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table Null column allowed: Yes Default value: UL_QI_TABLE Memo QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table Null column allowed: Yes Default value: AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.6.1.30 ServiceRUsUse Table This table stores the usage of resource units for different services. Field Type Description Attributes DIRECTION Short Uplink or downlink Null column allowed: No Default value: 1 Choice list: 1= DL, 2= UL NB_SF1 Short Number of SF1 codes allocated for DL Null column allowed: Yes Default value: 0 NB_SF16 Short Number of SF16 codes allocated for DL Null column allowed: Yes Default value: 1 NB_SF2 Short Number of SF2 codes allocated for DL Null column allowed: Yes Default value: 0 NB_SF4 Short Number of SF4 codes allocated for DL Null column allowed: Yes Default value: 0 NB_SF8 Short Number of SF8 codes allocated for DL Null column allowed: Yes Default value: 0 SERVICE Text (50) Service name Null column allowed: No Default value: TS_RANK Short Rank for TS allocation in Monte Carlo simulations Null column allowed: No Default value: 1 8.6.1.31 QualityIndicators Table This table is used by Quality Indicator (FER, BER, BLER, etc.) coverage predictions. Field Type Description Attributes NAME Text (20) Name of the managed quality indicator Null column allowed: No Default value: PS_QI Boolean Flag which indicates if this indicator is used for PS services Null column allowed: No Default value: True CS_QI Boolean Flag which indicates if this indicator is used in CS services Null column allowed: No Default value: True MEAS_PARAM Short Name of the measured figure used for this QI determination Choice list: CPICH_ECIO=1, CPICH_CI=2, CPICH_ECNT=3, DCH_EBNT=4, HSPDSCH_ECNT= 5 Null column allowed: Yes Default value: 1 USE_INTERPOLATION Boolean Flag which indicates if this QI must be interpolated or not Null column allowed: No Default value: True 8.6.1.32 UERxEquipments Table This table contains a list of UE reception equipment. Field Type Description Attributes NAME Text (50) Name of the type of receiver in the UE Null column allowed: No Default value: 8.6.1.33 UECategories Table This table models HSDPA UE categories. Field Type Description Attributes UE_CATEGORY Short UE category for HSDPA Null column allowed: No Default value: MAX_HSPDSCH_NUM Short Maximum number of HS-PDSCH channels for HSDPA Null column allowed: Yes Default value: 5 MIN_INTERTTI_NUM Short Minimum number of TTI between two TTI used Null column allowed: Yes Default value: 1 MAX_BLOCK_SIZE Integer Maximum transport block size supported (bits) Null column allowed: Yes Default value: 26000 ENABLE_16QAM Boolean True if 16QAM modulation is enabled Null column allowed: No Default value: False MAX_HSPDSCH_TS Short Maximum number of HS-PDSCH time slots per TTI Null column allowed: Yes Default value: 2 © Forsk 2009 AT281_AM_E1 319 Administrator Manual 8.6.1.34 InterfReductionFactors Table This table stores the interference reduction factors between carriers. Field Type Description Attributes CARRIER1 Integer First carrier Null column allowed: No Default value: 0 CARRIER2 Integer Second carrier Null column allowed: No Default value: 0 FACTOR Double Interference reduction factor Null column allowed: No Default value: 200 8.6.1.35 InterNetChProtect Table This table stores the inter-network channel protection graphs. 320 Field Type Description Attributes ICP Memo Inter-network channel protection = f(  MHz) Null column allowed: Yes Default value: ITF_BW Double Interfering bandwidth (kHz) Null column allowed: No Default value: 0 ITF_TECHNO Text (50) Interfering technology Null column allowed: No Default value: V_BW Double Victim bandwidth (kHz) Null column allowed: No Default value: 0 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.7 WiMAX BWA Template Figure 8.14: on page 321, Figure 8.15: on page 322, and Figure 8.16: on page 323 depict the WiMAX BWA database structure. Figure 8.14: WiMAX BWA Template - 1 © Forsk 2009 AT281_AM_E1 321 Administrator Manual Figure 8.15: WiMAX BWA Template - 2 322 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure Figure 8.16: WiMAX BWA Template - 3 © Forsk 2009 AT281_AM_E1 323 Administrator Manual 8.7.1 WiMAX BWA Tables The WiMAX BWA project template has the following data structure. 8.7.1.1 PropagationModels Table This table contains propagation model description, formulas, and parameters. Field Type Description Attributes Data Binary Model specific parameters Null column allowed: Yes Description Text (255) User defined Null column allowed: Yes Name Text (50) Name of the propagation model Null column allowed: No Signature Text (40) Unique Global ID of last model update Null column allowed: No Type Text (50) ProgID of the model Null column allowed: No 8.7.1.2 CustomFields Table This table enables you to define default values for all the fields of all the tables in Atoll, including user-defined fields added to different tables. It also enables you to define choice lists, a caption, and a group name for user-defined fields. Field Type Description Attributes CHOICE_LIST Memo Choice list for the field Null column allowed: Yes COLUMN_NAME Text (50) Second part of the unique key. Field name Null column allowed: No DEFAULT_VALUE Text (50) Default value for the field Null column allowed: Yes TABLE_NAME Text (50) First part of the unique key. Table name Null column allowed: No CAPTION Text (50) Caption of the field (displayed instead of the name) Null column allowed: Yes GROUP_NAME Text (50) Name of the group to which that field belongs Null column allowed: Yes The default values defined in this table have priority over the internal predefined default values (hard-coded in Atoll or defined in the database table structure). In order for Atoll to correctly consider the new default values, note that: • • 8.7.1.3 If you use floating point values, ensure that all the users have the same decimal separator (comma or point). The field names are case sensitive. CoordSys Table This table stores descriptions of the projection coordinate system and database’s internal coordinate system (the display coordinate system used when creating a database). Field 324 Type Description Attributes CODE Integer Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768) Null column allowed: No Default value: 0 DATUM_CODE Double DATUM_ROTX Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_ROTY Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_ROTZ Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_SCALE Double Parts per million (ppm) Null column allowed: Yes Default value: 0 DATUM_SHIFTX Double Meters Null column allowed: Yes Default value: 0 DATUM_SHIFTY Double Meters Null column allowed: Yes Default value: 0 DATUM_SHIFTZ Double Meters Null column allowed: Yes Default value: 0 ELLIPS_CODE Integer ELLIPS_RMAJOR Double Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Meters AT281_AM_E1 Null column allowed: Yes Default value: 0 © Forsk 2009 Chapter 8: Database Structure ELLIPS_RMINOR Double Meters Null column allowed: Yes Default value: 0 NAME Text (50) Coordinate system name Null column allowed: No Default value: PROJ_ANGLE Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_FALSE_EASTING Double Meters Null column allowed: Yes Default value: 0 PROJ_FALSE_NORTHING Double Meters Null column allowed: Yes Default value: 0 PROJ_FIRST_PARALLEL Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_LATITUDE_ORIGIN Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_LONGITUDE_ORIGIN Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_METHOD Short Undefined, NoProjection, Lambert1SP, Lambert2SP, Mercator, CassiniSoldner, TransMercator, TransMercatorSO, ObliqueStereographic, NewZealandMapGrid, HotineOM, LabordeOM, SwissObliqueCylindical, UTM Null column allowed: Yes Default value: 0 PROJ_SCALE_FACTOR Double PROJ_SECOND_PARALLEL Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_ZONE_NUMBER Integer Used with UTM Null column allowed: Yes Default value: 0 8.7.1.4 Null column allowed: Yes Default value: 0 Units Table This table stores the identification numbers of reception and transmission units, projection coordinate system specified in the .atl document and the database internal coordinate system. Field Type Description Attributes COORD_SYSTEM Integer Display coordinate system when creating database Null column allowed: Yes Default value: -1 PROJECTION Integer Projected coordinate system for geo data Null column allowed: Yes Default value: -1 Reception unit when creating database Null column allowed: No Default value: 0 Choice list: 0=dBm, 1=dbµV, 2=dbµV/m RECEPTION_UNIT Integer TRANSMISSION_UNIT Integer Transmission unit when creating database Null column allowed: No Default value: 0 Choice list: 0=dBm, 1=Watts, 2=kWatts GAIN_UNIT Integer Unit used for gains (dBd or dBi) Null column allowed: Yes Default value: 0 Choice list: 0= dBd, 1= dBi 8.7.1.5 Networks Table This table contains network-level properties and network-specific data. Field Type Description Attributes CYCLIC_PREFIX Short Cyclic prefix ratio Null column allowed: No Default value: 1 Choice list: 0: 1/4, 1: 1/8, 2: 1/16, 4: 1/32 DEFAULT_MODEL Text (50) Default propagation model Null column allowed: Yes Default value: "Cost-Hata" DEFAULT_RESOLUTION Float Default calculation resolution Null column allowed: No Default value: 50 DEFAULT_RTG Float Receive Time Guard, RTG (TDD only) Unit: ms Null column allowed: No Default value: 0 © Forsk 2009 AT281_AM_E1 325 Administrator Manual DEFAULT_TTG Float Transmit Time Guard, TTG (TDD only) Unit: ms Null column allowed: No Default value: 0 DL_UL_RATIO Float DL subframe symbol number / UL subframe symbol number (TDD only) Unit: % Null column allowed: No Default value: 66.667 DMAX Float Maximum radius for a cell Null column allowed: No Default value: -1 FIX_DL_OVERHEAD Short DL overhead expressed in symbol durations Null column allowed: No Default value: 1 FIX_UL_OVERHEAD Integer UL overhead expressed in symbol durations Null column allowed: No Default value: 0 FRAME_DURATION Short The length of a frame Null column allowed: No Default value: 4 Choice list: 0: 20 ms, 1: 12.5 ms, 2: 10 ms, 3: 8 ms, 4: 5 ms, 5: 4 ms, 6: 2.5 ms 7: 2 ms INTERFERERS_RX_THRES H Float Interferers' reception threshold Null column allowed: Yes Default value: -130 N_DATA Short Number of subcarriers per channel used for data transfer (N_USED - pilot subcarriers) Null column allowed: Yes Default value: 192 N_FFT Short Total number of subcarriers per channel Null column allowed: Yes Default value: 256 N_SUBCHANNELS_CH Short Number of subchannels per channel Null column allowed: Yes Default value: 16 N_USED Short Number of used subcarriers per channel (N_FFT - guard subcarriers) Null column allowed: Yes Default value: 200 NAME Text (50) Type of network Null column allowed: No Default value: Shared results storage folder Null column allowed: Yes Default value: SHARED_RESULTS_FOLDE Text (255) R SYSTEM_ Text (50) Name of the system Null column allowed: No Default value: ‘IEEE 802.16d’ or ‘IEEE 802.16e’ TECHNOLOGY Text (10) Name of the technlogy Null column allowed: No Default value: ‘OFDM’ THERMAL_NOISE Float Thermal noise Null column allowed: Yes Default value: -121 VARIABLE_DL_OVERHEAD Float DL overhead expressed in trame percentage Null column allowed: No Default value: 0 VARIABLE_UL_OVERHEAD Float UL overhead expressed in trame percentage Null column allowed: No Default value: 0 POWER_CONTROL_MARGI N Float Margin Over Max Bearer Threshold defining C/I Target (dB) Null column allowed: Yes Default value: 1 DL_RATIO_FORMAT Short Format of the DL ratio parameter (0: Percentage; 1: Fraction) (WiMAX802.16e only) Null column allowed: Yes Default value: 0 DL_SYM_DURATIONS_NB Short Number of symbol durations in the downlink subframe (including the symbol duration used for the Preamble) (WiMAX802.16e only) Null column allowed: Yes Default value: 32 UL_SYM_DURATIONS_NB Short Number of symbol durations in the uplink subframe (WiMAX802.16e only) Null column allowed: Yes Default value: 15 CELL_SELECTION Short Serving cell selection method (0 = Min DL Load, 1 = Min UL Load, 2 = Random, 3 = Sequential) Null column allowed: Yes Default value: 2 PZ_SEL_CRITERION Short Permutation zone selection criterion (0 - Preamble C/N; 1 - Preamble C/(I+N)) Null column allowed: Yes Default value: 0 AMS_SEL_CRITERION Short AMS criterion (0 - Preamble C/N; 1 - Preamble C/(I+N)) Null column allowed: Yes Default value: 0 8.7.1.6 Sites Table This table contains the physical properties of sites. 326 Field Type Description Attributes ALTITUDE Float Real altitude (user-defined) Unit: m Null column allowed: Yes Default value: AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure COMMENT_ Text (255) Additional information about the site Null column allowed: Yes Default value: LATITUDE Double Y coordinate Null column allowed: No Default value: 0 LONGITUDE Double X coordinate Null column allowed: No Default value: 0 NAME Text (50) Site name Null column allowed: No Default value: PYLON_HEIGHT Float Height of the pylon at site Null column allowed: Yes Default value: 50 SUPPORT_NATURE Short The nature of site. This field is for information only Null column allowed: Yes Default value: 0 8.7.1.7 Site List Management Tables These tables manage site lists used to filter groups of sites and transmitters. 8.7.1.7.1 SitesListsNames Table Field Type Description Attributes NAME Text (50) Name of the list Null column allowed: No Description Attributes 8.7.1.7.2 SitesLists Table Field Type LIST_NAME Text (50) First part of the unique key. Name of the list Null column allowed: No SITE_NAME Text (50) Second part of the unique key. Name of the site Null column allowed: No 8.7.1.8 Transmitter List Management Tables These tables manage transmitter lists used to filter groups of transmitters. 8.7.1.8.1 TxsListsNames Table Field Type Description Attributes NAME Text (50) Name of the transmitter list Null column allowed: No 8.7.1.8.2 TxsLists Table Field Type Description Attributes LIST_NAME Text (50) First part of the unique key. Name of the list. Null column allowed: No TX_NAME Text (50) Second part of the unique key. Name of the transmitter. Null column allowed: No 8.7.1.9 Antennas Table This table contains the description of antennas. Field Type Description Attributes Beamwidth Float Antenna beamwidth Null column allowed: Yes Default value: COMMENT_ Text (255) Additional information about the antenna Null column allowed: Yes Default value: CONSTRUCTOR Text (255) Antenna manufacturer name Null column allowed: Yes Default value: DIAGRAM Binary Internal binary format containing the description of the antenna horizontal and vertical patterns Null column allowed: Yes Default value: ELECTRICAL_TILT Float Antenna electrical tilt Null column allowed: Yes Default value: FMax Double Maximum frequency of created antenna Unit: MHz Null column allowed: Yes Default value: FMin Double Minimum frequency of created antenna Unit: MHz Null column allowed: Yes Default value: GAIN Float Antenna isotropic gain Unit: dBi Null column allowed: No Default value: 0 © Forsk 2009 AT281_AM_E1 327 Administrator Manual NAME Text (50) Name of antenna created in the current project Null column allowed: No Default value: Note: • An antenna pattern described in a text format may be converted to a binary format using a converter. The format of the binary field, DIAGRAM, is detailed below. Each antenna is described by a header and a list of value pairs. - The header is defined as follows: int (32 bits) flag = 0 for omni diagrams, 1 for non-omni short (16 bits) num = number of diagrams (0,1,2,3,4) short (16 bits) siz0 = size of the first diagram (horizontal copolar section (elevation=0°)) short (16 bits) siz1 = size of second (vertical copolar section (azimuth=0°)) short (16 bits) siz2 = size of third (horizontal contrapolar) short (16 bits) siz3 = size of fourth (vertical contrapolar) short (16 bits) prec = precision of the following angle values (=100) - Then follows the content of each of the defined diagrams ("sizx" with a value not equal to zero). - One diagram consists of a list of value pairs: one unsigned short value, the angle in degrees (multiplied by 100), so 577 means 5 degrees 77 hundredths of a degree. one short value representing the loss in dB for the given angle. - if siz2 = 5, there will be 5 pairs of values describing the third diagram. - All the lists of pairs are concatenated without a separator. 8.7.1.10 SecondaryAntennas Table This table is used to model additional antennas installed on transmitters. Field Type Description Attributes ANTENNA Text (50) Name of the antenna installed on the transmitter (from the antenna table of Atoll) Null column allowed: No Default value: AZIMUT Float Azimuth of the antenna Null column allowed: No Default value: 0 PERCENT_POWER Float Percentage of power dedicated to the secondary antenna Null column allowed: No Default value: 0 REDT Float Remote Electrical tilt of the secondary antenna Null column allowed: Yes Default value: 0 TILT Float Mechanical downtilt of the secondary antenna Null column allowed: No Default value: 0 TX_ID Text (50) Transmitter name Null column allowed: No Default value: 8.7.1.11 SmartAntennas Table This table is used to model smart antennas. Field Type Description Attributes NAME Text (50) Name of the Smart Antenna Null column allowed: No Default value: SA_MODEL Text (50) Smart antenna model used Null column allowed: Yes Default value: COMMENT_ Text (255) Comments Null column allowed: Yes Default value: BROADCAST_ANTENNA Text (50) Broadcast (main) antenna model for the smart antenna Null column allowed: Yes Default value: 8.7.1.12 SmartAntennasModels Table This table is used to store the smart antenna model parameters. Field SA_NAME 328 Type Text (50) Description Attributes Name of the smart antenna model Null column allowed: No Default value: AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure SA_TYPE Text (50) Type of the smart antenna model Null column allowed: No Default value: SA_SIGNATURE Text (50) Signature of the smart antenna model Null column allowed: No Default value: SA_DATA Binary Smart antenna model data Null column allowed: Yes Default value: SA_DESCRIPTION Text (50) Description of the smart antenna model Null column allowed: Yes Default value: 8.7.1.13 FrequencyBands Table This table contains the description of frequency band(s). Field Type Description Attributes ADJ_CHANNEL_PROT Float Protection against interfering signals from adjacent channels Null column allowed: No Default value: 11 CHANNEL_WIDTH Double Width of each physical channel composing the frequency band Unit: MHz Null column allowed: Yes Default value: 1 DL_FREQUENCY Double DL frequency of the 1st channel Unit: MHz Null column allowed: Yes Default value: DUPLEXING_METHOD Short Duplexing method used in the frequency band Null column allowed: No Default value: 0 Choice list: 0: FDD, 1: TDD EXCLUDED_CHANNELS Text (255) Physical channels you do not want to allocate Null column allowed: Yes Default value: FIRST_CHANNEL Short Number of the first physical channel of the frequency band Null column allowed: Yes Default value: 0 LAST_CHANNEL Short Number of the last physical channel of the frequency band Null column allowed: Yes Default value: 9 NAME Text (50) Name of the frequency band Null column allowed: No Default value: SAMPLING_FACTOR Float Ratio between the channel bandwidth and its sampling frequency Null column allowed: No Default value: 1 UL_FREQUENCY Double UL frequency of the 1st channel Unit: MHz Null column allowed: Yes Default value: 8.7.1.14 FrameConfigurations Table (WiMAX 802.16e) This table contains the configurations of frames. Field Type Description Attributes N_FFT Short Total number of subcarriers per channel bandwidth for this frame configuration Null column allowed: Yes Default value: 256 NAME Text (50) Name of the frame configuration Null column allowed: No Default value: "Default Frame" SEGMENTATION Boolean If true, the first DL PUSC zone is segmented Null column allowed: No Default value: False PREAMBLE_N_USED Short The number of subcarriers used for the preamble Null column allowed: No Default value: 8.7.1.15 PermutationZones Table (WiMAX 802.16e) This table contains the permutation zones. Field Type Description Attributes FRAME_CONFIG Text (50) Name of the frame configuration (from the FrameConfigurations table) Null column allowed: No Default value: N_DATA Short Number of subcarriers per channel used for data transfer (N_USED - pilot subcarriers) Null column allowed: Yes Default value: 192 N_SUBCHANNELS_CH Short Number of subchannels per channel Null column allowed: Yes Default value: 16 N_USED Short Number of used subcarriers per channel (N_FFT - guard subcarriers - DC subcarrier) Null column allowed: Yes Default value: 200 © Forsk 2009 AT281_AM_E1 329 Administrator Manual SUBCHANNEL_ALLOC_MO DE Short Name of the subchannel allocation mode Null column allowed: Yes Default value: 0 Choice list: 0: PUSC DL, 1: FUSC, 2: OFUSC, 3: AMC, 4: TUSC 1, 5: TUSC 2, 6: PUSC UL, 7: OPUSC SUBFRAME Short Downlink Subframe or Uplink Subframe Null column allowed: No Default value: 0 Choice list: 0: DL, 1:UL ZONE_ID Short Zone identifier Null column allowed: No Default value: 0 Choice List: 0 to 7 for DL, 0 to 2 for UL MAX_SPEED Float Highest user speed that can use this permutation zone (km/h) Null column allowed: Yes Default value: 150 PRIORITY Short Permutation zone priority (0: lowest) Null column allowed: Yes Default value: 0 QUALITY_THRESHOLD Float Minimum signal quality required to use this zone (dB) Null column allowed: Yes Default value: -5 DIVERSITY_SUPPORT Short The type of antenna diversity supported by the permutation zone Null column allowed: Yes Default value: 1 MAX_DISTANCE Float Coverage limit for the zone in terms of maximum distance from the cell Null column allowed: Yes Default value: 500000 USED_SC_GROUPS Short The secondary subchannel groups used by the segmented DL PUSC zone (Obsolete) Null column allowed: Yes Default value: SC_GROUPS_SEG0 Short Subchannel groups used by segment 0 Null column allowed: Yes Default value: 3 SC_GROUPS_SEG1 Short Subchannel groups used by segment 1 Null column allowed: Yes Default value: 12 SC_GROUPS_SEG2 Short Subchannel groups used by segment 2 Null column allowed: Yes Default value: 48 AUTO_ACTIVATE Boolean If true, the permutation zone is activated for new cells Null column allowed: No Default value: False 8.7.1.16 Schedulers Table This table is used to model different schedulers. Field Type Description Attributes NAME Text (30) Name of the scheduler Null column allowed: No Default value: QOS_BIAS_FACTOR Float Weight ratio for better QoS (%) Null column allowed: No Default value: 0 SCHEDULING_METHOD Integer 0 = Proportional Fair; 1 = Proportional Demand; 2 = Biased (QoS Class); 3 = Max Aggregate Throughput Null column allowed: Yes Default value: 0 TARGET_THROUGHPUT_D ATA Integer 0 = Peak MAC Throughput; 1 = Effective MAC Throughput; 2 = Application Throughput Null column allowed: Yes Default value: 0 TARGET_THROUGHPUT_V OICE Integer 0 = Peak MAC Throughput; 1 = Effective MAC Throughput; 2 = Application Throughput Null column allowed: Yes Default value: 0 BEARER_SELECTION Short Bearer Selection Criterion: 0 – Bearer Index; 1 – Peak MAC Throughput; 2 – Effective MAC Throughput Null column allowed: Yes Default value: 0 UL_BW_ALLOCATION Short UL Bandwidth Allocation Target: 0 – Full Bandwidth; 1 – Maintain Connection; 2 – Best Bearer Null column allowed: Yes Default value: 2 8.7.1.17 Receivers Table This table models the receiver used for raster coverage predictions. 330 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure Field Type Description Attributes ANTENNA Text (50) Receiver's antenna name (if empty an omni antenna is used) Null column allowed: Yes Default value: HEIGHT Float Height of the receiver Unit: m Null column allowed: No Default value: 2 LOSS Float Losses due to receiver radio equipment (up and downlink) Unit: dB Null column allowed: No Default value: 0. NAME Text (50) Name of the receiver Null column allowed: No Default value: 8.7.1.18 Equipment Management Tables These tables model TMA, feeders, and BTS equipment properties. 8.7.1.18.1 TMAEquipments Table Field Type Description Attributes DL_LOSSES Float Downlink losses of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 NAME Text (50) Name of Tower Mounted Amplifier Null column allowed: No Default value: NOISE_FIGURE Float Noise figure of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 UL_GAIN Float Uplink gain of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 8.7.1.18.2 FeederEquipments Table Field Type Description Attributes CONNECTOR_LOSSES_UL Float Feeder connector losses in uplink Null column allowed: Yes Default value: 0 CONNECTOR_LOSSES_DL Float Feeder connector losses in downlink Null column allowed: Yes Default value: 0 LOSS_PER_METER Float Feeder loss per meter Null column allowed: Yes Default value: 0 NAME Text (50) Name of Feeder Null column allowed: No Default value: 8.7.1.18.3 BTSEquipments Table Field Type Description Attributes NAME Text (50) Name of Base Station Equipment Null column allowed: No Default value: NOISE_FIGURE Float Noise figure of Base Station Null column allowed: Yes Default value: 0 CONFIG_DL_LOSSES Float Downlink losses due to the configuration of the BTS (duplexer and/or combiner) Null column allowed: Yes Default value: 0 CONFIG_UL_LOSSES Float Uplink losses due to the configuration of the BTS (duplexer and/or combiner) Null column allowed: Yes Default value: 0 RHO_FACTOR Short Rho factor to model self generated interference (100%=ideal) Null column allowed: Yes Default value: 100 8.7.1.19 Neighbour Management Tables (WiMAX 802.16e) 8.7.1.19.1 Neighbours Table This table stores neighbourhood relationships between cells of the same .atl document (intra-technology neighbours). Field Type Description Attributes IMPORTANCE Float Handover importance Null column allowed: Yes Default value: 1 NEIGHBOUR Text (50) Neighbour cell Null column allowed: No Default value: © Forsk 2009 AT281_AM_E1 331 Administrator Manual REASON Integer Reason of the neighbourhood Null column allowed: Yes Default value: 0 (Manual) Choice list: Manual, Forced, Co-site, Adjacent, Symmetric, Distance, Coverage TRANSMITTER Text (50) Reference cell Null column allowed: No Default value: TYPE Text (50) Type of the neighbourhood (handover, measurement…) Null column allowed: Yes Default value: FORCE_HHO Boolean Force Handover type to hard handover in case of intra-carriers neighbours Null column allowed: No Default value: False 8.7.1.19.2 NeighboursExt Table This table stores neighbourhood relationships between transmitters/cells of different .atl documents (inter-technology neighbours). Field Type Description Attributes IMPORTANCE Float Handover importance Null column allowed: Yes Default value: 1 NEIGHBOUR Text (50) Neighbour cell Null column allowed: No Default value: REASON Integer Reason of the neighbourhood Null column allowed: Yes Default value: 0 (Manual) Choice list: Manual, Forced, Co-site, Adjacent, Symmetric, Distance, Coverage TRANSMITTER Text (50) Reference cell Null column allowed: No Default value: TYPE Text (50) Type of the neighbourhood (handover, measurement…) Null column allowed: Yes Default value: 8.7.1.19.3 NeighboursConstraints Table This table stores the exceptional pair relations between cells of the same .atl document (intra-technology exceptional pairs). Field Type Description Attributes IMPORTANCE Float Handover importance Null column allowed: Yes Default value: NEIGHBOUR Text (50) Neighbour cell Null column allowed: No Default value: TRANSMITTER Text (50) Reference cell Null column allowed: No Default value: STATUS Integer Constraint used in automatic allocation. 0 = Forced; 1 = Forbidden. Null column allowed: Yes Default value: 0 FORCE_HHO Boolean Force Handover type to hard handover in case of intra-carriers neighbours (not used) Null column allowed: No Default value: False 8.7.1.19.4 NeighboursConstraintsExt Table This table stores the exceptional pair relations between transmitters/cells of different .atl documents (inter-technology exceptional pairs). Field 332 Type Description Attributes IMPORTANCE Float Handover importance Null column allowed: Yes Default value: NEIGHBOUR Text (50) Neighbour cell or transmitter Null column allowed: No Default value: TRANSMITTER Text (50) Reference cell Null column allowed: No Default value: STATUS Integer Constraint used in automatic allocation. 0 = Forced; 1 = Forbidden. Null column allowed: Yes Default value: 0 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.7.1.20 Transmitters Table This table stores the transmitters and their properties. Field Type Description Attributes ACTIVE Boolean Transmitter activity: 'Yes' means that the transmitter is active Null column allowed: No Default value: True ANTDIVGAIN Float Antenna diversity gain (Temp) Unit: dB Null column allowed: Yes Default value: 0 ANTENNA_NAME Text (50) Name of the main antenna installed on the transmitter (from the Antennas table) Null column allowed: Yes Default value: AZIMUT Float Azimuth of the first antenna Null column allowed: Yes Default value: 0 BTS_NAME Text (50) Name of the BTS equipment Null column allowed: Yes Default value: CALC_RADIUS Integer Calculation radius used to define the calculation area Unit: m Null column allowed: Yes Default value: 4000 CALC_RADIUS2 Integer Second calculation radius Unit: m Null column allowed: Yes Default value: CALC_RESOLUTION Integer Calculation resolution Null column allowed: Yes Default value: 50 CALC_RESOLUTION2 Integer Second calculation resolution Null column allowed: Yes Default value: CELL_SIZE Float Radius of the cell (schematically represented by an hexagon) Null column allowed: Yes Default value: 2000 COMMENT_ Text (255) Additional information about the transmitter Null column allowed: Yes Default value: COV_PROBA Short Cell Edge Coverage Probability Null column allowed: Yes Default value: DX Float X coordinate relative to the site position Null column allowed: Yes Default value: 0 DY Float Y coordinate relative to the site position Null column allowed: Yes Default value: 0 FEEDER_NAME Text (50) Name of the feeder equipment Null column allowed: Yes Default value: FEEDERLENGTH_DL Float Length of downlink feeder Unit: m Null column allowed: Yes Default value: 0 FEEDERLENGTH_UL Float Length of uplink feeder Unit: m Null column allowed: Yes Default value: 0 HEIGHT Float Antenna height above the ground Unit: m Null column allowed: Yes Default value: 25 HEXAGON_GROUP Text (50) Group of hexagons which contains this transmitter Null column allowed: Yes Default value: MISCDLL Float Miscellaneous downlink loss Null column allowed: Yes Default value: 0 MISCULL Float Miscellaneous uplink loss Null column allowed: Yes Default value: 0 NOISE_FIGURE Float Total Noise figure used to determine the thermal noise at the transmitter Null column allowed: Yes Default value: 5 POLARIZATION Text (1) Polarization of the antennas installed at the transmitter Null column allowed: Yes Default value: "V" PROPAG_MODEL Text (50) Name of the propagation model used to calculate prediction Null column allowed: Yes Default value: PROPAG_MODEL2 Text (50) Name of the second propagation model used to calculate prediction Null column allowed: Yes Default value: REDT Float Remote electrical tilt of the main antenna Null column allowed: Yes Default value: 0 RXLOSSES Float Losses on the uplink due to transmitter radio equipment Null column allowed: Yes Default value: 0 SITE_NAME Text (50) Name of the site at which the transmitter is located (from the Sites table) Null column allowed: No Default value: TILT Float Mechanical downtilt of the first antenna Null column allowed: Yes Default value: 0 © Forsk 2009 AT281_AM_E1 333 Administrator Manual TMA_NAME Text (50) Name of theTower Mounted Amplifier equipment Null column allowed: Yes Default value: TX_ID Text (50) Transmitter name Null column allowed: No Default value: TXLOSSES Float Losses on the downlink due to transmitter radio equipment Null column allowed: Yes Default value: 0 SA_NAME Text (50) Name of the smart antenna assigned to the transmitter Null column allowed: Yes Default value: MIMO_TX_ANTENNAS Short Number of MIMO antennas used for transmission Null column allowed: Yes Default value: 1 MIMO_RX_ANTENNAS Short Number of MIMO antennas used for reception Null column allowed: Yes Default value: 1 TX_TYPE Short Type of transmitter (0 = Normal; 1 = Interferer only) Null column allowed: Yes Default value: 0 8.7.1.21 TplTransmitters Table This table is used to store station templates and their properties. Field Type Description Attributes ACTIVE Boolean Transmitter activity: 'Yes' means that the transmitter is active Null column allowed: No ANTDIVGAIN Float Antenna diversity gain (Temp) Unit: dB Null column allowed: Yes ANTENNA_NAME Text (50) Name of the main antenna installed on the transmitter (from the Antennas table) Null column allowed: Yes AZIMUT Float Azimuth of the main antenna Null column allowed: Yes BTS_NAME Text (50) Name of the BTS equipment Null column allowed: Yes CALC_RADIUS Integer Calculation radius used to define each transmitter calculation area Unit: m Null column allowed: Yes CALC_RADIUS2 Integer Second calculation radius Unit: m Null column allowed: Yes CALC_RESOLUTION Integer Calculation resolution Null column allowed: Yes CALC_RESOLUTION2 Integer Second calculation resolution Null column allowed: Yes 334 CELL_SIZE Float Radius of the cell (schematically represented by an hexagon) Unit: m Null column allowed: Yes COV_PROBA Short Cell Edge Coverage Probability Null column allowed: Yes FBAND Text (50) Frequency band of the cell Null column allowed: Yes FEEDER_NAME Text (50) Name of the feeder equipment Null column allowed: Yes FEEDERLENGTH_DL Float Length of downlink feeder Unit: m Null column allowed: Yes FEEDERLENGTH_UL Float Length of uplink feeder Unit: m Null column allowed: Yes HEIGHT Float Antenna height above the ground Unit: m Null column allowed: Yes MISCDLL Float Miscellaneous downlink loss Null column allowed: Yes MISCULL Float Miscellaneous uplink loss Null column allowed: Yes NAME Text (50) Template name Null column allowed: No NOISE_FIGURE Float Total Noise figure used to determine the thermal noise at the transmitter (Temp) Null column allowed: Yes NUM_SECTORS Integer Number of sectors Null column allowed: Yes POWER Float Cell output power (dBm) Null column allowed: Yes PROPAG_MODEL Text (255) Name of the propagation model used to calculate prediction Null column allowed: Yes PROPAG_MODEL2 Text (255) Name of the second propagation model used to calculate prediction Null column allowed: Yes REDT Float Remote Electrical tilt Null column allowed: Yes RXLOSSES Float Losses on the uplink due to transmitter radio equipment Unit: dB Null column allowed: Yes TILT Float Mechanical downtilt of the main antenna Null column allowed: Yes TMA_NAME Text (50) Name of theTower Mounted Amplifier equipment Null column allowed: Yes TXLOSSES Float Losses on the downlink due to transmitter radio equipment Unit: dB Null column allowed: Yes WEQUIPMENT Text (50) Cell equipment Null column allowed: Yes AAS_USAGE Float AAS usage ratio Null column allowed: Yes AMS_THRESHOLD Float CINR threshold in dB to switch from SM to STTD/MRC Null column allowed: Yes CHANNEL Integer Channel number Null column allowed: Yes DL_LOAD Float Downlink traffic load Null column allowed: Yes AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure IDLE_PILOT_POWER_OFFS ET Float Pilot power offset = Preamble power - Idle Pilot power (dB) Null column allowed: Yes MAX_NUMBER_OF_USERS Integer Max supported number of users for the cell Null column allowed: Yes MIMO_RX_ANTENNAS Short Number of reception antennas used for MIMO Null column allowed: Yes MIMO_TX_ANTENNAS Short Number of transmission antennas used for MIMO Null column allowed: Yes NOISE_RISE_UL Float Uplink interference noise rise (dB) Null column allowed: Yes PILOT_POWER_OFFSET Float Pilot power offset = Preamble power - Pilot power (dB) Null column allowed: Yes SA_NAME Text (50) Name of the associated smart antenna Null column allowed: Yes TRAFFIC_POWER_OFFSET Float Traffic power offset = Preamble power - traffic power (dB) Null column allowed: Yes UL_LOAD Float Uplink traffic load Null column allowed: Yes DIVERSITY_SUPPORT Short Type of diversity support used in downlink (WiMAX 802.16d) 0=None, 1=AAS, 2=STTD/MRC, 3=SU-MIMO, 4=AMS Null column allowed: Yes MAX_EXT_NEIGHB_NUMBE R Integer Maximum number of inter-technology neighbours (WiMAX 802.16e) Null column allowed: Yes MAX_NEIGHB_NUMBER Integer Maximum number of intra-technology neighbours (WiMAX 802.16e) Null column allowed: Yes FRAME_CONFIG Text (50) Defines the subchannel, subcarrier, and permutation zone configuration used at the cell (WiMAX 802.16e) Null column allowed: Yes PREAMBLE_INDEX Short Preamble Index (WiMAX 802.16e) Null column allowed: Yes SEGMENTATION_USAGE Float Segmentation usage ratio (WiMAX 802.16e) Null column allowed: Yes SCHEDULER Text (30) Scheduler used by the cell Null column allowed: Yes PREAMBLE_QUALITY_THR ES Float Required CNR quality for the preamble signal Null column allowed: Yes PI_REUSE_MIN_DIST Float The minimum reuse distance for the AFP and preamble index allocation Null column allowed: Yes CHANNEL_STATUS Short Channel allocation status (0 = Not allocated, 1 = Allocated, 2 = Locked) Null column allowed: Yes PI_STATUS Short Preamble index status (0 = unassigned; 1 = assigned; 2= Fixed) Null column allowed: Yes TX_TYPE Short Type of transmitter (0 = Normal; 1 = Interferer only) Null column allowed: Yes MAX_DL_LOAD Float Maximum traffic load allowed on downlink Null column allowed: Yes MAX_UL_LOAD Float Maximum traffic load allowed on uplink Null column allowed: Yes UL_MU_SM_GAIN Float Multi-user (collaborative) MIMO gain in uplink Null column allowed: Yes DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes CHANNEL_LIST Text(255) Channel numbers used by transmitters Null column allowed: Yes PI_LIST Text(255) Preamble indexes used by transmitters Null column allowed: Yes DIVERSITY_SUPPORT_UL Short Type of diversity support used in uplink (WiMAX 802.16d) 0=None, 1=AAS, 2=STTD/MRC, 3=SU-MIMO, 4=AMS, 5=MU-MIMO Null column allowed: Yes 8.7.1.22 WCells Table This table stores cells and their properties. Field Type Description Attributes BSID Text (50) Cell connexion identifier Null column allowed: Yes Default value: CELL_ID Text (50) Name of the cell Null column allowed: No Default value: CHANNEL Integer Channel number Null column allowed: Yes Default value: 0 COMMENT_ Text (255) Additional information about the cell Null column allowed: Yes Default value: DL_LOAD Float Downlink cell traffic load Null column allowed: Yes Default value: 1 FBAND Text (50) Frequency band of the cell Null column allowed: No Default value: FRAME_CONFIG Text (50) Defines the subchannel, subcarrier, and permutation zone configuration used at the cell (WiMAX 802.16e) Null column allowed: Yes Default value: MAX_NUMBER_OF_USERS Integer Max supported number of users for the cell Null column allowed: Yes Default value: © Forsk 2009 AT281_AM_E1 335 Administrator Manual POWER Float Output PowerUnit: dBm Null column allowed: Yes Default value: 43 TX_ID Text (50) Name of the transmitter to which the cell belongs Null column allowed: No Default value: UL_LOAD Float Uplink cell traffic load Null column allowed: Yes Default value: 1 WEQUIPMENT Text (50) WiMAX equipment installed at the cell Null column allowed: Yes Default value: NOISE_RISE_UL Float Uplink noise rise (dB). Manually specified by the user or calculated during simulations. Null column allowed: Yes Default value: 0 PREAMBLE_INDEX Integer Preamble index of the cell Null column allowed: Yes Default value: 0 ACTIVE Boolean Cell's activity. Cell is active if true. Null column allowed: No Default value: True SEGMENTATION_USAGE Float Percentation of downlink traffic load dedicated to the segmented zone Null column allowed: Yes Default value: 50 AAS_RESULTS Binary Uplink and downlink AAS results from simulations Null column allowed: Yes Default value: MAX_NEIGHB_NUMBER Integer Maximum number of intra-technology neighbours for this cell Null column allowed: Yes Default value: MAX_EXT_NEIGHB_NUMBE R Integer Maximum number of inter-technology neighbours for this cell Null column allowed: Yes Default value: AAS_USAGE Float Percentation of downlink traffic load supported by the smart antenna equipment Null column allowed: Yes Default value: 50 AMS_THRESHOLD Float C/(I+N) threshold for switching from SM to STTD/MRC Null column allowed: Yes Default value: PILOT_POWER_OFFSET Float Offset (in dB) with respect to the preamble power for determining the pilot power during the loaded part of the frame Null column allowed: Yes Default value: 0 TRAFFIC_POWER_OFFSET Float Offset (in dB) with respect to the preamble power for determining the traffic power Null column allowed: Yes Default value: 3 IDLE_PILOT_POWER_OFFS ET Float Offset (in dB) with respect to the preamble power for determining the pilot power during the empty part of the frame Null column allowed: Yes Default value: 10 DIVERSITY_SUPPORT Short The type of antenna diversity supported by the cell (WiMAX 802.16d) Null column allowed: Yes Default value: 1 SCHEDULER Text (30) Scheduler used by the cell Null column allowed: Yes Default value: PREAMBLE_QUALITY_THR ES Float Required CNR quality for the preamble signal Null column allowed: Yes Default value: -4 PI_REUSE_MIN_DIST Float The minimum reuse distance for the AFP and preamble index allocation Null column allowed: Yes Default value: PI_STATUS Short Preamble index status (0 = Not allocated, 1 = Allocated, 2 = Locked) Null column allowed: Yes Default value: 0 CHANNEL_STATUS Short Channel allocation status (0 = Not allocated, 1 = Allocated, 2 = Locked) Null column allowed: Yes Default value: 0 MAX_DL_LOAD Float Maximum traffic load allowed on downlink Null column allowed: Yes Default value: 100 MAX_UL_LOAD Float Maximum traffic load allowed on uplink Null column allowed: Yes Default value: 100 UL_MU_SM_GAIN Float Multi-user (collaborative) MIMO gain in uplink Null column allowed: Yes Default value: 2 DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes Default value: 0 UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes Default value: 0 RANK Short Zero based order used by scheduler for sequential cell selection Null column allowed: Yes Default value: 8.7.1.23 WEquipments Table This table models equipment that performs radio resource management at site level. Field 336 Type Description AT281_AM_E1 Attributes © Forsk 2009 Chapter 8: Database Structure NAME 8.7.1.24 Text (50) Name of the WiMAX equipment Null column allowed: No Default value: WBearerQualityCurves Table This table contains the quality graphs of the different quality indicators for the different bearers. Field Type Description Attributes BEARER_INDEX Short Bearer index Null column allowed: No Default value: 0 MOBILITY Text (50) Mobility type Null column allowed: Yes Default value: QI_CURVE Memo DL Quality QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table Null column allowed: Yes Default value: QI_NAME Text (50) Name of the Quality Indicator Null column allowed: No Default value: RX_EQUIP Text (50) Name of the WiMAX equipment Null column allowed: No Default value: 8.7.1.25 WBearersRequiredCI Table This table contains the bearer selection C/(I+N) thresholds for the different bearers. Type Description Attributes BEARERS_REQUIRED_COV ERI Field Memo C/I required in DL for selecting a WiMAX bearer C/I_Req = f(Best(BEARER_INDEX)) Null column allowed: Yes Default value: MOBILITY Text (50) CPE mobility Null column allowed: Yes Default value: RX_EQUIP Text (50) Name of the WiMAX equipment Null column allowed: No Default value: 8.7.1.26 Multi-Service Traffic Management These tables contain descriptions of multi-service traffic data, i.e., services, mobility types, terminals, user profiles, and environments. 8.7.1.26.1 WEnvironmentDefs Table Field Type Description Attributes DENSITY Float Number of subscribers per km2 Null column allowed: Yes Default value: 0 ENVIRONMENT Text (50) Environment name Null column allowed: No Default value: MOBILITY Text (50) Type of mobility Null column allowed: No Default value: USER_PROFILE Text (255) Type of user profile Null column allowed: No Default value: 8.7.1.26.2 WMobility Table Field Type Description Attributes NAME Text (50) Type of mobility Null column allowed: No Default value: MEAN_SPEED Float Mean mobile speed (km/h) used for HSDPA Null column allowed: Yes Default value: 0 8.7.1.26.3 WServicesUsage Table Field Type Description Attributes CALL_DURATION Float Average duration of a call (for circuit switched services) Unit: s Null column allowed: Yes Default value: CALL_NUMBER Float Average number of calls per hour for circuit switched services or average number of sessions per hour for packet switched services Null column allowed: Yes Default value: 0 DL_VOLUME Float Volume transferred on the downlink during a session (for packet switched services) Unit: Kbyte Null column allowed: Yes Default value: © Forsk 2009 AT281_AM_E1 337 Administrator Manual SERVICE Text (50) Service (from the Service table) that the subscriber may request Null column allowed: No Default value: TERMINAL Text (50) Type of terminal (from the Terminal table) used by the subscriber for the service Null column allowed: No Default value: UL_VOLUME Float Volume transferred on the uplink during a session (for packet switched services) Unit: Kbyte Null column allowed: Yes Default value: USER_PROFILE Text (255) User profile name Null column allowed: No Default value: 8.7.1.26.4 WServices Table Field Type Description Attributes BODY_LOSS Float Losses due to the users body (dB) Null column allowed: No Default value: 0 DL_ACTIVITY Float Activity factor for voice services on the downlink Null column allowed: Yes Default value: 1 DL_DP Float Packet inter-arrival time (ms) in downlink Null column allowed: Yes Default value: 0 DL_DPC Float Reading time (distance) between two packet calls (ms) in downlink Null column allowed: Yes Default value: 0 DL_HIGHEST_BEARER Float The highest bearer to allowed to be used for this service in DL Null column allowed: Yes Default value: 8 DL_MAXIMUM_LATENCY Float Maximum latency in DL (ms) Null column allowed: No Default value: 0 DL_MRTR Float Minimum required transmission rate in DL (Committed Information Rate) Null column allowed: No Default value: 0 DL_MSTR Float Maximum sustained trasmission rate in DL (Maximum Information Rate) Null column allowed: No Default value: 0 DL_NPC Integer Number of packet calls during a session in downlink Null column allowed: Yes Default value: 1 DL_SP Integer Packet size (Bytes) in downlink Null column allowed: Yes Default value: 1500 DL_SPC_MAX Float Downlink maximum packet call size (kBytes) Null column allowed: Yes Default value: 2000 DL_SPC_MIN Float Downlink minimum packet call size (kBytes) Null column allowed: Yes Default value: 4 MAXIMUM_BLOCKING_PRO BA Integer Maximum probability of blocking (or delay) (%) Null column allowed: Yes Default value: 0 NAME Text (50) Service name Null column allowed: No Default value: PRIORITY Short Service priority (0: lowest) Null column allowed: Yes Default value: 0 QOS_CLASS Short Quality of Service class (In order of priority defined by the IEEE 802.16 standard) Null column allowed: Yes Default value: 0 Choice list:0: UGs, 1: rtPs, 2: ErtPs, 3: nrtPs, 4: Best Effort REQ_AVERAGE_DL_RATE Float Requested Average Downlink Rate (kbps) Null column allowed: Yes Default value: REQ_AVERAGE_UL_RATE Float Requested Average Uplink Rate (kbps) Null column allowed: Yes Default value: TH_OFFSET Float Offset to add to TH_SCALE_FACTOR Null column allowed: No Default value: 0 TH_SCALE_FACTOR Float Ratio between application level throughput and MAC layer throughput Null column allowed: No Default value: 95 338 TYPE Short Service type Null column allowed: Yes Default value: 0 Choice list: 0: Voice, 1: Data UL_ACTIVITY Float Activity factor for voice services on the uplink Null column allowed: Yes Default value: 1 UL_DP Float Packet inter-arrival time (ms) in uplink Null column allowed: Yes Default value: 0 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure UL_DPC Float Reading time (distance) between two packet calls (ms) in uplink Null column allowed: Yes Default value: 0 UL_HIGHEST_BEARER Float The highest bearer to allowed to be used for this service in UL Null column allowed: Yes Default value: 4 UL_MAXIMUM_LATENCY Float Maximum latency in UL (ms) Null column allowed: No Default value: 0 UL_MRTR Float Minimum required transmission rate in UL (Committed Information Rate) Null column allowed: No Default value: 0 UL_MSTR Float Maximum sustained trasmission rate in UL (Maximum Information Rate) Null column allowed: No Default value: 0 UL_NPC Integer Number of packet calls during a session in uplink Null column allowed: Yes Default value: 1 UL_SP Integer Packet size (Bytes) in uplink Null column allowed: Yes Default value: 1500 UL_SPC_MAX Float Uplink maximum packet call size (kBytes) Null column allowed: Yes Default value: 2000 UL_SPC_MIN Float Uplink minimum packet call size (kBytes) Null column allowed: Yes Default value: 4 8.7.1.26.5 WBearers Table Field Type Description Attributes BEARER_INDEX Short Modulation and coding scheme number Null column allowed: No Default value: 1 CODING_RATE Float Coding rate Null column allowed: Yes Default value: 1 MODULATION Short Modulation type Null column allowed: No Default value: 1 Choice list: 0: BPSK, 1: QPSK, 2: 16QAM 3: 64QAM NAME Text (50) Name of the WiMAX radio bearer Null column allowed: No Default value: SPECTRAL_EFFICIENCY Float Spectral efficiency = Peak MAC Throughput per Hz Unit: bps/Hz Null column allowed: Yes Default value: 0 8.7.1.26.6 WTerminals Table Field Type Description Attributes ANTENNA Text (50) Receiver's antenna name (if empty an omni antenna is used) Null column allowed: Yes Default value: GAIN Float Terminal antenna gain (dB) Null column allowed: Yes Default value: 0 LOSS Float Terminal antenna loss (dB) Null column allowed: Yes Default value: 0 NAME Text (50) Terminal name Null column allowed: No Default value: NOISE_FACTOR Float Noise figure used to determine the thermal noise at the receiver (dB) Null column allowed: Yes Default value: 8 PMAX Float Maximum terminal power on traffic channel (dBm) Null column allowed: Yes Default value: 23 PMIN Float Minimum terminal power on traffic channel (dBm) Null column allowed: Yes Default value: -22 RX_EQUIP Text (50) Name of the WiMAX equipment available at the terminal Null column allowed: Yes Default value: DIVERSITY_SUPPORT Short Antenna diversity support (0 = None, 1 = AAS, 2 = MIMO, 3 = AAS+MIMO) Null column allowed: Yes Default value: 1 MIMO_TX_ANTENNAS Short Number of MIMO antennas used for transmission Null column allowed: Yes Default value: 1 MIMO_RX_ANTENNAS Short Number of MIMO antennas used for reception Null column allowed: Yes Default value: 1 © Forsk 2009 AT281_AM_E1 339 Administrator Manual 8.7.1.26.7 WTraficEnvironments Table Field Type Description Attributes CLUTTER_WEIGHTS Binary Internal binary format describing weights assigned to each clutter class Null column allowed: Yes Default value: NAME Text (50) Name of the created environment Null column allowed: No Default value: 8.7.1.26.8 WUserProfiles Table Field Type Description Attributes NAME Text (50) Name of the created user profile Null column allowed: No Default value: 8.7.1.27 QualityIndicators Table This table is used by Quality Indicator (FER, BER, BLER, etc.) coverage predictions. Field Type Description Attributes CS_QI Boolean Flag indicating whether the Quality Indicator is used for Voice (CS) services Null column allowed: No Default value: True MEAS_PARAM Short Name of the measured figure used for this QI determination Null column allowed: Yes Default value: 0 Choice list: 0 = C, 1 = CIR NAME Text (50) Name of the Quality Indicator Null column allowed: No Default value: PS_QI Boolean Flag indicating whether the Quality Indicator is used for Data (PS) services Null column allowed: No Default value: True USE_INTERPOLATION Boolean Flag indicating whether the Quality Indicator must be interpolated or not Null column allowed: No Default value: True 8.7.1.28 WMimoConfigs Table This table stores the maximum MIMO gain graphs for different numbers of transmission and reception antennas. Field Type Description Attributes MOBILITY Text (50) User mobility Null column allowed: Yes Default value: MIMO_TX_ANTENNAS Short Number of MIMO antennas used for transmission Null column allowed: Yes Default value: 1 MIMO_RX_ANTENNAS Short Number of MIMO antennas used for reception Null column allowed: Yes Default value: 1 MAX_MIMO_GAIN Memo Graph of maximum MIMO gains vs. C/(I+N) Null column allowed: Yes Default value: BEARER_INDEX Short Index of the WiMAX bearer Null column allowed: Yes Default value: 1 MAX_BLER Float Maximum value of BLER for which the gains are applicable Null column allowed: Yes Default value: 1 STTD_GAIN Float Gain that will be applied to the CINR in STTD mode (dB) Null column allowed: Yes Default value: 0 SUBCHANNEL_ALLOC_MO DE Short Subchannel allocation mode for WiMAX 802.16e only Null column allowed: Yes Default value: 8 WEQUIPMENT Text (50) Name of the equipment to which the MIMO gains correspond Null column allowed: No Default value: 8.7.1.29 InterNetChProtect Table This table stores the inter-network channel protection graphs. 340 Field Type Description Attributes ICP Memo Inter-network channel protection = f(  MHz) Null column allowed: Yes Default value: ITF_BW Double Interfering bandwidth (kHz) Null column allowed: No Default value: 0 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure ITF_TECHNO Text (50) Interfering technology Null column allowed: No Default value: V_BW Double Victim bandwidth (kHz) Null column allowed: No Default value: 0 © Forsk 2009 AT281_AM_E1 341 Administrator Manual 8.8 LTE Template Figure 8.17: on page 342, Figure 8.18: on page 343, and Figure 8.19: on page 344 depict the LTE database structure. Figure 8.17: LTE Template - 1 342 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure Figure 8.18: LTE Template - 2 © Forsk 2009 AT281_AM_E1 343 Administrator Manual Figure 8.19: LTE Template - 3 344 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.8.1 LTE Tables The LTE project template has the following data structure. 8.8.1.1 PropagationModels Table This table contains propagation model description, formulas, and parameters. Field Type Description Attributes Data Binary Model specific parameters Null column allowed: Yes Description Text (255) User defined Null column allowed: Yes Name Text (50) Name of the propagation model Null column allowed: No Signature Text (40) Unique Global ID of last model update Null column allowed: No Type Text (50) ProgID of the model Null column allowed: No 8.8.1.2 CustomFields Table This table enables you to define default values for all the fields of all the tables in Atoll, including user-defined fields added to different tables. It also enables you to define choice lists, a caption, and a group name for user-defined fields. Field Type Description Attributes CHOICE_LIST Memo Choice list for the field Null column allowed: Yes COLUMN_NAME Text (50) Second part of the unique key. Field name Null column allowed: No DEFAULT_VALUE Text (50) Default value for the field Null column allowed: Yes TABLE_NAME Text (50) First part of the unique key. Table name Null column allowed: No CAPTION Text (50) Caption of the field (displayed instead of the name) Null column allowed: Yes GROUP_NAME Text (50) Name of the group to which that field belongs Null column allowed: Yes The default values defined in this table have priority over the internal predefined default values (hard-coded in Atoll or defined in the database table structure). In order for Atoll to correctly consider the new default values, note that: • • 8.8.1.3 If you use floating point values, ensure that all the users have the same decimal separator (comma or point). The field names are case sensitive. CoordSys Table This table stores descriptions of the projection coordinate system and database’s internal coordinate system (the display coordinate system used when creating a database). Field Type Description Attributes CODE Integer Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768) Null column allowed: No Default value: 0 DATUM_CODE Double DATUM_ROTX Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_ROTY Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_ROTZ Double Arc-seconds Null column allowed: Yes Default value: 0 DATUM_SCALE Double Parts per million (ppm) Null column allowed: Yes Default value: 0 DATUM_SHIFTX Double Meters Null column allowed: Yes Default value: 0 DATUM_SHIFTY Double Meters Null column allowed: Yes Default value: 0 DATUM_SHIFTZ Double Meters Null column allowed: Yes Default value: 0 ELLIPS_CODE Integer ELLIPS_RMAJOR Double © Forsk 2009 Null column allowed: Yes Default value: 0 Null column allowed: No Default value: 0 Meters AT281_AM_E1 Null column allowed: Yes Default value: 0 345 Administrator Manual ELLIPS_RMINOR Double Meters Null column allowed: Yes Default value: 0 NAME Text (50) Coordinate system name Null column allowed: No Default value: PROJ_ANGLE Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_FALSE_EASTING Double Meters Null column allowed: Yes Default value: 0 PROJ_FALSE_NORTHING Double Meters Null column allowed: Yes Default value: 0 PROJ_FIRST_PARALLEL Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_LATITUDE_ORIGIN Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_LONGITUDE_ORIGIN Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_METHOD Short Undefined, NoProjection, Lambert1SP, Lambert2SP, Mercator, CassiniSoldner, TransMercator, TransMercatorSO, ObliqueStereographic, NewZealandMapGrid, HotineOM, LabordeOM, SwissObliqueCylindical, UTM Null column allowed: Yes Default value: 0 PROJ_SCALE_FACTOR Double PROJ_SECOND_PARALLEL Double Decimal degrees Null column allowed: Yes Default value: 0 PROJ_ZONE_NUMBER Integer Used with UTM Null column allowed: Yes Default value: 0 8.8.1.4 Null column allowed: Yes Default value: 0 Units Table This table stores the identification numbers of reception and transmission units, projection coordinate system specified in the .atl document and the database internal coordinate system. Field Type Description Attributes COORD_SYSTEM Integer Display coordinate system when creating database Null column allowed: Yes Default value: -1 PROJECTION Integer Projected coordinate system for geo data Null column allowed: Yes Default value: -1 Reception unit when creating database Null column allowed: No Default value: 0 Choice list: 0=dBm, 1=dbµV, 2=dbµV/m RECEPTION_UNIT Integer TRANSMISSION_UNIT Integer Transmission unit when creating database Null column allowed: No Default value: 0 Choice list: 0=dBm, 1=Watts, 2=kWatts GAIN_UNIT Integer Unit used for gains (dBd or dBi) Null column allowed: Yes Default value: 0 Choice list: 0= dBd, 1= dBi 8.8.1.5 Networks Table This table contains network-level properties and network-specific data. Field DEFAULT_CP Type Short Description Attributes Default cyclic prefix Null column allowed: Yes Default value: 0 Choice list: 0: Normal, 1: Extended SP_PERIODICITY Short Switching point periodicity (TDD) Null column allowed: Yes Default value: 0 Choice list: 0: Half Frame, 1: Frame DEFAULT_MODEL Text (50) Default propagation model Null column allowed: Yes Default value: "Cost-Hata" DEFAULT_RESOLUTION Float Default calculation resolution Null column allowed: No Default value: 50 346 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure DMAX Float Maximum radius for a cell Null column allowed: No Default value: -1 PDCCH_SYMBOLS Short Number of symbol durations per subframe for PDCCH overhead Null column allowed: No Default value: 1 PUCCH_AVG_NRB Float Average number of overhead resource blocks for PUCCH Null column allowed: No Default value: 2 INTERFERERS_RX_THRES H Float Interferers' reception threshold Null column allowed: Yes Default value: -130 NAME Text (50) Type of network Null column allowed: No Default value: Shared results storage folder Null column allowed: Yes Default value: SHARED_RESULTS_FOLDE Text (255) R SYSTEM_ Text (50) Name of the system Null column allowed: No Default value: ‘LTE’ TECHNOLOGY Text (10) Name of the technlogy Null column allowed: No Default value: ‘OFDM’ THERMAL_NOISE Float Thermal noise Null column allowed: Yes Default value: -121 POWER_CONTROL_MARGI N Float Margin Over Max Bearer Threshold defining C/I Target (dB) Null column allowed: Yes Default value: 1 CELL_SELECTION Short Serving cell selection method (0 = Min DL Load, 1 = Min UL Load, 2 = Random, 3 = Sequential) Null column allowed: Yes Default value: 2 AMS_SEL_CRITERION Short AMS criterion (0 - Reference signal C/N; 1 - Reference signal C/(I+N)) Null column allowed: Yes Default value: 0 8.8.1.6 Sites Table This table contains the physical properties of sites. Field Type Description Attributes ALTITUDE Float Real altitude (user-defined) Unit: m Null column allowed: Yes Default value: COMMENT_ Text (255) Additional information about the site Null column allowed: Yes Default value: LATITUDE Double Y coordinate Null column allowed: No Default value: 0 LONGITUDE Double X coordinate Null column allowed: No Default value: 0 NAME Text (50) Site name Null column allowed: No Default value: PYLON_HEIGHT Float Height of the pylon at site Null column allowed: Yes Default value: 50 SUPPORT_NATURE Short The nature of site. This field is for information only Null column allowed: Yes Default value: 0 8.8.1.7 Site List Management Tables These tables manage site lists used to filter groups of sites and transmitters. 8.8.1.7.1 SitesListsNames Table Field Type Description Attributes NAME Text (50) Name of the list Null column allowed: No 8.8.1.7.2 SitesLists Table Field Type Description Attributes LIST_NAME Text (50) First part of the unique key. Name of the list Null column allowed: No SITE_NAME Text (50) Second part of the unique key. Name of the site Null column allowed: No © Forsk 2009 AT281_AM_E1 347 Administrator Manual 8.8.1.8 Transmitter List Management Tables These tables manage transmitter lists used to filter groups of transmitters. 8.8.1.8.1 TxsListsNames Table Field Type Description Attributes NAME Text (50) Name of the transmitter list Null column allowed: No 8.8.1.8.2 TxsLists Table Field Type Description Attributes LIST_NAME Text (50) First part of the unique key. Name of the list. Null column allowed: No TX_NAME Text (50) Second part of the unique key. Name of the transmitter. Null column allowed: No 8.8.1.9 Antennas Table This table contains the description of antennas. Field Type Description Attributes Beamwidth Float Antenna beamwidth Null column allowed: Yes Default value: COMMENT_ Text (255) Additional information about the antenna Null column allowed: Yes Default value: CONSTRUCTOR Text (255) Antenna manufacturer name Null column allowed: Yes Default value: DIAGRAM Binary Internal binary format containing the description of the antenna horizontal and vertical patterns Null column allowed: Yes Default value: ELECTRICAL_TILT Float Antenna electrical tilt Null column allowed: Yes Default value: FMax Double Maximum frequency of created antenna Unit: MHz Null column allowed: Yes Default value: FMin Double Minimum frequency of created antenna Unit: MHz Null column allowed: Yes Default value: GAIN Float Antenna isotropic gain Unit: dBi Null column allowed: No Default value: 0 NAME Text (50) Name of antenna created in the current project Null column allowed: No Default value: Note: • An antenna pattern described in a text format may be converted to a binary format using a converter. The format of the binary field, DIAGRAM, is detailed below. Each antenna is described by a header and a list of value pairs. - The header is defined as follows: int (32 bits) flag = 0 for omni diagrams, 1 for non-omni short (16 bits) num = number of diagrams (0,1,2,3,4) short (16 bits) siz0 = size of the first diagram (horizontal copolar section (elevation=0°)) short (16 bits) siz1 = size of second (vertical copolar section (azimuth=0°)) short (16 bits) siz2 = size of third (horizontal contrapolar) short (16 bits) siz3 = size of fourth (vertical contrapolar) short (16 bits) prec = precision of the following angle values (=100) - Then follows the content of each of the defined diagrams ("sizx" with a value not equal to zero). - One diagram consists of a list of value pairs: one unsigned short value, the angle in degrees (multiplied by 100), so 577 means 5 degrees 77 hundredths of a degree. one short value representing the loss in dB for the given angle. - if siz2 = 5, there will be 5 pairs of values describing the third diagram. - All the lists of pairs are concatenated without a separator. 348 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.8.1.10 SecondaryAntennas Table This table is used to model additional antennas installed on transmitters. Field Type Description Attributes ANTENNA Text (50) Name of the antenna installed on the transmitter (from the antenna table of Atoll) Null column allowed: No Default value: AZIMUT Float Azimuth of the antenna Null column allowed: No Default value: 0 PERCENT_POWER Float Percentage of power dedicated to the secondary antenna Null column allowed: No Default value: 0 REDT Float Remote Electrical tilt of the secondary antenna Null column allowed: Yes Default value: 0 TILT Float Mechanical downtilt of the secondary antenna Null column allowed: No Default value: 0 TX_ID Text (50) Transmitter name Null column allowed: No Default value: 8.8.1.11 SmartAntennas Table This table is used to model smart antennas. Field Type Description Attributes NAME Text (50) Name of the Smart Antenna Null column allowed: No Default value: SA_MODEL Text (50) Smart antenna model used Null column allowed: Yes Default value: COMMENT_ Text (255) Comments Null column allowed: Yes Default value: BROADCAST_ANTENNA Text (50) Broadcast (main) antenna model for the smart antenna Null column allowed: Yes Default value: 8.8.1.12 SmartAntennasModels Table This table is used to store the smart antenna model parameters. Field Type Description Attributes SA_NAME Text (50) Name of the smart antenna model Null column allowed: No Default value: SA_TYPE Text (50) Type of the smart antenna model Null column allowed: No Default value: SA_SIGNATURE Text (50) Signature of the smart antenna model Null column allowed: No Default value: SA_DATA Binary Smart antenna model data Null column allowed: Yes Default value: SA_DESCRIPTION Text (50) Description of the smart antenna model Null column allowed: Yes Default value: 8.8.1.13 FrequencyBands Table This table contains the description of frequency band(s). Field Type Description Attributes ADJ_CHANNEL_PROT Float Protection against interfering signals from adjacent channels Null column allowed: No Default value: 28 CHANNEL_WIDTH Double Width of each physical channel composing the frequency band Unit: MHz Null column allowed: Yes Default value: 5 DL_FREQUENCY Double DL frequency of the 1st channel Unit: MHz Null column allowed: Yes Default value: 2110 DUPLEXING_METHOD Short Duplexing method used in the frequency band Null column allowed: No Default value: 0 Choice list: 0: FDD, 1: TDD EXCLUDED_CHANNELS Text (255) Physical channels you do not want to allocate Null column allowed: Yes Default value: © Forsk 2009 AT281_AM_E1 349 Administrator Manual FIRST_CHANNEL Short Number of the first physical channel of the frequency band Null column allowed: Yes Default value: 0 LAST_CHANNEL Short Number of the last physical channel of the frequency band Null column allowed: Yes Default value: 0 NAME Text (50) Name of the frequency band Null column allowed: No Default value: SAMPLING_FREQUENCY Float Sampling frequency Unit: MHz Null column allowed: No Default value: 7.68 N_RB Short Number of resource blocks per channel Null column allowed: Yes Default value: 25 UL_FREQUENCY Double UL frequency of the 1st channel Unit: MHz Null column allowed: Yes Default value: 8.8.1.14 Schedulers Table This table is used to model different schedulers. Field Type Description Attributes NAME Text (30) Name of the scheduler Null column allowed: No Default value: SCHEDULING_METHOD Integer 0 = Proportional Fair; 1 = Proportional Demand; 3 = Max Aggregate Throughput Null column allowed: Yes Default value: 0 TARGET_THROUGHPUT_D ATA Integer 0 = Peak RLC Throughput; 1 = Effective RLC Throughput; 2 = Application Throughput Null column allowed: Yes Default value: 0 TARGET_THROUGHPUT_V OICE Integer 0 = Peak RLC Throughput; 1 = Effective RLC Throughput; 2 = Application Throughput Null column allowed: Yes Default value: 0 BEARER_SELECTION Short Bearer Selection Criterion: 0 – Bearer Index; 1 – Peak RLC Throughput; 2 – Effective RLC Throughput Null column allowed: Yes Default value: 0 UL_BW_ALLOCATION Short UL Bandwidth Allocation Target: 0 – Full Bandwidth; 1 – Maintain Connection; 2 – Best Bearer Null column allowed: Yes Default value: 2 8.8.1.15 Receivers Table This table models the receiver used for raster coverage predictions. Field Type Description Attributes ANTENNA Text (50) Receiver's antenna name (if empty an omni antenna is used) Null column allowed: Yes Default value: HEIGHT Float Height of the receiver Unit: m Null column allowed: No Default value: 2 LOSS Float Losses due to receiver radio equipment (up and downlink) Unit: dB Null column allowed: No Default value: 0. NAME Text (50) Name of the receiver Null column allowed: No Default value: 8.8.1.16 Equipment Management Tables These tables model TMA, feeders, and BTS equipment properties. 8.8.1.16.1 350 TMAEquipments Table Field Type Description Attributes DL_LOSSES Float Downlink losses of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 NAME Text (50) Name of Tower Mounted Amplifier Null column allowed: No Default value: NOISE_FIGURE Float Noise figure of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 UL_GAIN Float Uplink gain of Tower Mounted Amplifier Null column allowed: Yes Default value: 0 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.8.1.16.2 FeederEquipments Table Field Type Description Attributes CONNECTOR_LOSSES_UL Float Feeder connector losses in uplink Null column allowed: Yes Default value: 0 CONNECTOR_LOSSES_DL Float Feeder connector losses in downlink Null column allowed: Yes Default value: 0 LOSS_PER_METER Float Feeder loss per meter Null column allowed: Yes Default value: 0 NAME Text (50) Name of Feeder Null column allowed: No Default value: 8.8.1.16.3 BTSEquipments Table Field Type Description Attributes NAME Text (50) Name of Base Station Equipment Null column allowed: No Default value: NOISE_FIGURE Float Noise figure of Base Station Null column allowed: Yes Default value: 0 CONFIG_DL_LOSSES Float Downlink losses due to the configuration of the BTS (duplexer and/or combiner) Null column allowed: Yes Default value: 0 CONFIG_UL_LOSSES Float Uplink losses due to the configuration of the BTS (duplexer and/or combiner) Null column allowed: Yes Default value: 0 8.8.1.17 Neighbour Management Tables 8.8.1.17.1 Neighbours Table This table stores neighbourhood relationships between cells of the same .atl document (intra-technology neighbours). Field Type Description Attributes IMPORTANCE Float Handover importance Null column allowed: Yes Default value: 1 NEIGHBOUR Text (50) Neighbour cell Null column allowed: No Default value: REASON Integer Reason of the neighbourhood Null column allowed: Yes Default value: 0 (Manual) Choice list: Manual, Forced, Co-site, Adjacent, Symmetric, Distance, Coverage TRANSMITTER Text (50) Reference cell Null column allowed: No Default value: TYPE Text (50) Type of the neighbourhood (handover, measurement…) Null column allowed: Yes Default value: FORCE_HHO Boolean Force Handover type to hard handover in case of intra-carriers neighbours Null column allowed: No Default value: False 8.8.1.17.2 NeighboursExt Table This table stores neighbourhood relationships between transmitters/cells of different .atl documents (inter-technology neighbours). Field Type Description Attributes IMPORTANCE Float Handover importance Null column allowed: Yes Default value: 1 NEIGHBOUR Text (50) Neighbour cell Null column allowed: No Default value: Reason of the neighbourhood Null column allowed: Yes Default value: 0 (Manual) Choice list: Manual, Forced, Co-site, Adjacent, Symmetric, Distance, Coverage REASON © Forsk 2009 Integer AT281_AM_E1 351 Administrator Manual TRANSMITTER Text (50) Reference cell Null column allowed: No Default value: TYPE Text (50) Type of the neighbourhood (handover, measurement…) Null column allowed: Yes Default value: 8.8.1.17.3 NeighboursConstraints Table This table stores the exceptional pair relations between cells of the same .atl document (intra-technology exceptional pairs). Field Type Description Attributes IMPORTANCE Float Handover importance Null column allowed: Yes Default value: NEIGHBOUR Text (50) Neighbour cell Null column allowed: No Default value: TRANSMITTER Text (50) Reference cell Null column allowed: No Default value: STATUS Integer Constraint used in automatic allocation. 0 = Forced; 1 = Forbidden. Null column allowed: Yes Default value: 0 FORCE_HHO Boolean Force Handover type to hard handover in case of intra-carriers neighbours (not used) Null column allowed: No Default value: False 8.8.1.17.4 NeighboursConstraintsExt Table This table stores the exceptional pair relations between transmitters/cells of different .atl documents (inter-technology exceptional pairs). Field Type Description Attributes IMPORTANCE Float Handover importance Null column allowed: Yes Default value: NEIGHBOUR Text (50) Neighbour cell or transmitter Null column allowed: No Default value: TRANSMITTER Text (50) Reference cell Null column allowed: No Default value: STATUS Integer Constraint used in automatic allocation. 0 = Forced; 1 = Forbidden. Null column allowed: Yes Default value: 0 8.8.1.18 Transmitters Table This table stores the transmitters and their properties. Field Type Description Attributes ACTIVE Boolean Transmitter activity: 'Yes' means that the transmitter is active Null column allowed: No Default value: True ANTDIVGAIN Float Antenna diversity gain (Temp) Unit: dB Null column allowed: Yes Default value: 0 ANTENNA_NAME Text (50) Name of the main antenna installed on the transmitter (from the Antennas table) Null column allowed: Yes Default value: AZIMUT Float Azimuth of the first antenna Null column allowed: Yes Default value: 0 BTS_NAME Text (50) Name of the BTS equipment Null column allowed: Yes Default value: CALC_RADIUS Integer Calculation radius used to define the calculation area Unit: m Null column allowed: Yes Default value: 4000 CALC_RADIUS2 Integer Second calculation radius Unit: m Null column allowed: Yes Default value: CALC_RESOLUTION Integer Calculation resolution Null column allowed: Yes Default value: 50 CALC_RESOLUTION2 Integer Second calculation resolution Null column allowed: Yes Default value: CELL_SIZE Float Radius of the cell (schematically represented by an hexagon) Null column allowed: Yes Default value: 2000 COMMENT_ Text (255) Additional information about the transmitter Null column allowed: Yes Default value: DX Float X coordinate relative to the site position Null column allowed: Yes Default value: 0 352 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure DY Float Y coordinate relative to the site position Null column allowed: Yes Default value: 0 FEEDER_NAME Text (50) Name of the feeder equipment Null column allowed: Yes Default value: FEEDERLENGTH_DL Float Length of downlink feeder Unit: m Null column allowed: Yes Default value: 0 FEEDERLENGTH_UL Float Length of uplink feeder Unit: m Null column allowed: Yes Default value: 0 HEIGHT Float Antenna height above the ground Unit: m Null column allowed: Yes Default value: 25 HEXAGON_GROUP Text (50) Group of hexagons which contains this transmitter Null column allowed: Yes Default value: MISCDLL Float Miscellaneous downlink loss Null column allowed: Yes Default value: 0 MISCULL Float Miscellaneous uplink loss Null column allowed: Yes Default value: 0 NOISE_FIGURE Float Total Noise figure used to determine the thermal noise at the transmitter Null column allowed: Yes Default value: 5 POLARIZATION Text (1) Polarization of the antennas installed at the transmitter Null column allowed: Yes Default value: "V" PROPAG_MODEL Text (50) Name of the propagation model used to calculate prediction Null column allowed: Yes Default value: PROPAG_MODEL2 Text (50) Name of the second propagation model used to calculate prediction Null column allowed: Yes Default value: REDT Float Remote electrical tilt of the main antenna Null column allowed: Yes Default value: 0 RXLOSSES Float Losses on the uplink due to transmitter radio equipment Null column allowed: Yes Default value: 0 SITE_NAME Text (50) Name of the site at which the transmitter is located (from the Sites table) Null column allowed: No Default value: TILT Float Mechanical downtilt of the first antenna Null column allowed: Yes Default value: 0 TMA_NAME Text (50) Name of theTower Mounted Amplifier equipment Null column allowed: Yes Default value: TX_ID Text (50) Transmitter name Null column allowed: No Default value: TXLOSSES Float Losses on the downlink due to transmitter radio equipment Null column allowed: Yes Default value: 0 TX_ANTENNAS_PORTS Short Number of antenna ports in transmission Null column allowed: Yes Default value: 1 RX_ANTENNAS_PORTS Short Number of antenna ports in reception Null column allowed: Yes Default value: 1 TX_TYPE Short Type of transmitter (0 = Normal; 1 = Interferer only) Null column allowed: Yes Default value: 0 8.8.1.19 TplTransmitters Table This table is used to store station templates and their properties. Field Type Description Attributes ACTIVE Boolean Transmitter activity: 'Yes' means that the transmitter is active Null column allowed: No ANTDIVGAIN Float Antenna diversity gain (Temp) Unit: dB Null column allowed: Yes ANTENNA_NAME Text (50) Name of the main antenna installed on the transmitter (from the Antennas table) Null column allowed: Yes AZIMUT Float Azimuth of the main antenna Null column allowed: Yes BTS_NAME Text (50) Name of the BTS equipment Null column allowed: Yes CALC_RADIUS Integer Calculation radius used to define each transmitter calculation area Unit: m Null column allowed: Yes CALC_RADIUS2 Integer Second calculation radius Unit: m Null column allowed: Yes CALC_RESOLUTION Integer Calculation resolution Null column allowed: Yes CALC_RESOLUTION2 Integer Second calculation resolution Null column allowed: Yes © Forsk 2009 AT281_AM_E1 353 Administrator Manual CELL_SIZE Float Radius of the cell (schematically represented by an hexagon) Unit: m Null column allowed: Yes FBAND Text (50) Frequency band of the cell Null column allowed: Yes FEEDER_NAME Text (50) Name of the feeder equipment Null column allowed: Yes FEEDERLENGTH_DL Float Length of downlink feeder Unit: m Null column allowed: Yes FEEDERLENGTH_UL Float Length of uplink feeder Unit: m Null column allowed: Yes HEIGHT Float Antenna height above the ground Unit: m Null column allowed: Yes MISCDLL Float Miscellaneous downlink loss Null column allowed: Yes MISCULL Float Miscellaneous uplink loss Null column allowed: Yes NAME Text (50) Template name Null column allowed: No NOISE_FIGURE Float Total Noise figure used to determine the thermal noise at the transmitter (Temp) Null column allowed: Yes NUM_SECTORS Integer Number of sectors Null column allowed: Yes POWER Float Maximum cell output power (dBm) Null column allowed: Yes PROPAG_MODEL Text (255) Name of the propagation model used to calculate prediction Null column allowed: Yes PROPAG_MODEL2 Text (255) Name of the second propagation model used to calculate prediction Null column allowed: Yes REDT Float Remote Electrical tilt Null column allowed: Yes RXLOSSES Float Losses on the uplink due to transmitter radio equipment Unit: dB Null column allowed: Yes TILT Float Mechanical downtilt of the main antenna Null column allowed: Yes TMA_NAME Text (50) Name of theTower Mounted Amplifier equipment Null column allowed: Yes TXLOSSES Float Losses on the downlink due to transmitter radio equipment Unit: dB Null column allowed: Yes RX_EQUIPMENT Text (50) Reception equipment Null column allowed: Yes AMS_THRESHOLD Float CINR threshold in dB to switch from SM to STTD Null column allowed: Yes CHANNEL Integer Channel number Null column allowed: Yes DL_LOAD Float Downlink traffic load Null column allowed: Yes MAX_NUMBER_OF_USERS Integer Max supported number of users for the cell Null column allowed: Yes RX_ANTENNAS_PORTS Short Number of reception antenna ports Null column allowed: Yes TX_ANTENNAS_PORTS Short Number of transmission antenna ports Null column allowed: Yes NOISE_RISE_UL Float Uplink interference noise rise (dB) Null column allowed: Yes UL_LOAD Float Uplink traffic load Null column allowed: Yes DIVERSITY_SUPPORT Short Type of diversity support used in downlink 0=None, 1=Diversity, 2=SU-MIMO, 3=AMS Null column allowed: Yes MAX_EXT_NEIGHB_NUMBE R Integer Maximum number of inter-technology neighbours Null column allowed: Yes MAX_NEIGHB_NUMBER Integer Maximum number of intra-technology neighbours Null column allowed: Yes SCHEDULER Text (30) Scheduler used by the cell Null column allowed: Yes RSRQ_THRES Float Required reference signal CNR quality for the best server signal Null column allowed: Yes SF_CONFIG Short Subframe configuration used by the cell in case of TDD frequency band Null column allowed: Yes ID_REUSE_MIN_DIST Float The minimum reuse distance for the AFP and physical cell ID allocation Null column allowed: Yes CHANNEL_STATUS Short Channel allocation status (0 = Not allocated, 1 = Allocated, 2 = Locked) Null column allowed: Yes ID_STATUS Short Physical cell ID status (0 = unassigned; 1 = assigned; 2= Fixed) Null column allowed: Yes TX_TYPE Short Type of transmitter (0 = Normal; 1 = Interferer only) Null column allowed: Yes MAX_DL_LOAD Float Maximum traffic load allowed on downlink Null column allowed: Yes MAX_UL_LOAD Float Maximum traffic load allowed on uplink Null column allowed: Yes UL_MU_SM_GAIN Float Multi-user (collaborative) MIMO gain in uplink Null column allowed: Yes DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes CHANNEL_LIST Text(255) Channel numbers used by transmitters Null column allowed: Yes PHY_CELLID_LIST Text(255) Physical cell IDs used by transmitters Null column allowed: Yes SCH_POWER_OFFSET Float SCH/PBCH EPRE offset (dB) Null column allowed: Yes PDSCH_POWER_OFFSET Float PDSCH/PDCCH EPRE offset (dB) Null column allowed: Yes PHY_CELL_ID Short Physical cell ID Null column allowed: Yes DIVERSITY_SUPPORT_UL Short Type of diversity support used in uplink 0=None, 1=Diversity, 2=SU-MIMO, 3=AMS, 4=MU-MIMO Null column allowed: Yes 354 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure ICIC_SUPPORT Short Inter -Cell Interference Coordination Support 0=None; 1=Static DL; 2=Static UL Null column allowed: Yes DL_FFR_USAGE Float Percentage of the downlink traffic load carried by the ICIC part of the cell Null column allowed: Yes ICIC_DELTAPL_TH Float Maximum difference in dB between the best server path loss and second best Server path loss to be considered in ICIC zone Null column allowed: Yes UL_FPC_FACTOR Float Factor enabling reduction of transmission powers of cell-edge users 0; 0.4;0.5;0.6;0.7;0.8;0.9;1 Null column allowed: Yes UL_FPC_NR_MAX Float Maximum uplink noise rise Null column allowed: Yes UL_FPC_CINR_MAX Float 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. Null column allowed: Yes NOISE_RISE_ICIC_UL Float Noise rise received by cell edge traffic Null column allowed: Yes 8.8.1.20 T4GCells Table This table stores cells and their properties. Field Type Description Attributes CELL_ID Text (50) Name of the cell Null column allowed: No Default value: CHANNEL Integer Channel number Null column allowed: Yes Default value: 0 COMMENT_ Text (255) Additional information about the cell Null column allowed: Yes Default value: DL_LOAD Float Downlink cell traffic load Null column allowed: Yes Default value: 1 FBAND Text (50) Frequency band of the cell Null column allowed: No Default value: MAX_NUMBER_OF_USERS Integer Max supported number of users for the cell Null column allowed: Yes Default value: POWER Float Maximum output power Unit: dBm Null column allowed: Yes Default value: 43 TX_ID Text (50) Name of the transmitter to which the cell belongs Null column allowed: No Default value: UL_LOAD Float Uplink cell traffic load Null column allowed: Yes Default value: 1 RX_EQUIPMENT Text (50) Reception equipment installed at the cell Null column allowed: Yes Default value: NOISE_RISE_UL Float Uplink noise rise (dB). Manually specified by the user or calculated during simulations. Null column allowed: Yes Default value: 0 ACTIVE Boolean Cell's activity. Cell is active if true. Null column allowed: No Default value: True MAX_NEIGHB_NUMBER Integer Maximum number of intra-technology neighbours for this cell Null column allowed: Yes Default value: MAX_EXT_NEIGHB_NUMBE R Integer Maximum number of inter-technology neighbours for this cell Null column allowed: Yes Default value: AMS_THRESHOLD Float C/(I+N) threshold for switching from spatial multiplexing to space-time transmit diversity Null column allowed: Yes Default value: DIVERSITY_SUPPORT Short The type of antenna diversity supported by the cell in downlink Null column allowed: Yes Default value: 1 SCHEDULER Text (50) Scheduler used by the cell Null column allowed: Yes Default value: SF_CONFIG Short Subframe configuration used by the cell in case of TDD frequency band Null column allowed: Yes Default value: 1 RSRQ_THRES Float Required reference signal CNR quality for the best server signal Null column allowed: Yes Default value: 0 PHY_CELL_ID Integer Physical cell ID Null column allowed: Yes Default value: 0 SCH_POWER_OFFSET Float SCH/PBCH EPRE offset Null column allowed: Yes Default value: 0 PDSCH_POWER_OFFSET Float PDSCH/PDCCH EPRE offset Null column allowed: Yes Default value: 0 © Forsk 2009 AT281_AM_E1 355 Administrator Manual DIVERSITY_SUPPORT_UL Short The type of antenna diversity supported by the cell in uplink Null column allowed: Yes Default value: 1 ID_REUSE_MIN_DIST Float The minimum reuse distance for the AFP and physical cell ID allocation Null column allowed: Yes Default value: ID_STATUS Short Physical cell ID status (0 = Not allocated, 1 = Allocated, 2 = Locked) Null column allowed: Yes Default value: 0 CHANNEL_STATUS Short Channel allocation status (0 = Not allocated, 1 = Allocated, 2 = Locked) Null column allowed: Yes Default value: 0 MAX_DL_LOAD Float Maximum traffic load allowed on downlink Null column allowed: Yes Default value: 100 MAX_UL_LOAD Float Maximum traffic load allowed on uplink Null column allowed: Yes Default value: 100 UL_MU_SM_GAIN Float Multi-user (collaborative) MIMO gain in uplink Null column allowed: Yes Default value: 2 DOWNLINK_EXTERNAL_NO ISE_RISE Float Inter-network downlink noise rise Null column allowed: Yes Default value: 0 UPLINK_EXTERNAL_NOISE _RISE Float Inter-network uplink noise rise Null column allowed: Yes Default value: 0 RANK Short Zero based order used by scheduler for sequential cell selection Null column allowed: Yes Default value: ICIC_SUPPORT Short Inter -Cell Interference Coordination Support 0=None; 1=Static DL; 2=Static UL Null column allowed: Yes Default value: 0 DL_FFR_USAGE Float Percentage of the downlink traffic load carried by the ICIC part of the cell Null column allowed: Yes Default value: 0 ICIC_DELTAPL_TH Float Maximum difference in dB between the best server path loss and second best Server path loss to be considered in ICIC zone Null column allowed: Yes Default value: 0 UL_FPC_FACTOR Float Factor enabling reduction of transmission powers of cell-edge users 0; 0.4;0.5;0.6;0.7;0.8;0.9;1 Null column allowed: Yes Default value: 1 UL_FPC_NR_MAX Float Maximum uplink noise rise Null column allowed: Yes Default value: 6 UL_FPC_CINR_MAX Float 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. Null column allowed: Yes Default value: 20 NOISE_RISE_ICIC_UL Float Noise rise received by cell edge traffic Null column allowed: Yes Default value: 0 8.8.1.21 T4GEquipments Table This table models equipment that performs radio resource management. Field Type Description Attributes NAME Text (50) Name of the reception equipment Null column allowed: No Default value: 8.8.1.22 T4GBearerQualityCurves Table This table contains the quality graphs of the different quality indicators for the different bearers. Field Type Description Attributes BEARER_INDEX Short Bearer index Null column allowed: No Default value: 0 MOBILITY Text (50) Mobility type Null column allowed: Yes Default value: QI_CURVE Memo DL Quality QI=f(MEAS_PARAM) MEAS_PARAM from QualityIndicators table Null column allowed: Yes Default value: QI_NAME Text (50) Name of the Quality Indicator Null column allowed: No Default value: RX_EQUIP Text (50) Name of the reception equipment Null column allowed: No Default value: 8.8.1.23 T4GBearersRequiredCI Table This table contains the bearer selection C/(I+N) thresholds for the different bearers. Field 356 Type Description AT281_AM_E1 Attributes © Forsk 2009 Chapter 8: Database Structure BEARERS_REQUIRED_COV ERI Memo C/I required in DL for selecting a LTE bearer C/I_Req = f(Best(BEARER_INDEX)) Null column allowed: Yes Default value: MOBILITY Text (50) CPE mobility Null column allowed: Yes Default value: RX_EQUIP Text (50) Name of the reception equipment Null column allowed: No Default value: 8.8.1.24 Multi-Service Traffic Management These tables contain descriptions of multi-service traffic data, i.e., services, mobility types, terminals, user profiles, and environments. 8.8.1.24.1 T4GEnvironmentDefs Table Field Type Description Attributes DENSITY Float Number of subscribers per km2 Null column allowed: Yes Default value: 0 ENVIRONMENT Text (50) Environment name Null column allowed: No Default value: MOBILITY Text (50) Type of mobility Null column allowed: No Default value: USER_PROFILE Text (255) Type of user profile Null column allowed: No Default value: 8.8.1.24.2 T4GMobility Table Field Type Description Attributes NAME Text (50) Type of mobility Null column allowed: No Default value: MEAN_SPEED Float Mean mobile speed (km/h) used for HSDPA Null column allowed: Yes Default value: 0 8.8.1.24.3 T4GServicesUsage Table Field Type Description Attributes CALL_DURATION Float Average duration of a call (for circuit switched services) Unit: s Null column allowed: Yes Default value: CALL_NUMBER Float Average number of calls per hour for circuit switched services or average number of sessions per hour for packet switched services Null column allowed: Yes Default value: 0 DL_VOLUME Float Volume transferred on the downlink during a session (for packet switched services) Unit: Kbyte Null column allowed: Yes Default value: SERVICE Text (50) Service (from the Service table) that the subscriber may request Null column allowed: No Default value: TERMINAL Text (50) Type of terminal (from the Terminal table) used by the subscriber for the service Null column allowed: No Default value: UL_VOLUME Float Volume transferred on the uplink during a session (for packet switched services) Unit: Kbyte Null column allowed: Yes Default value: USER_PROFILE Text (255) User profile name Null column allowed: No Default value: 8.8.1.24.4 T4GServices Table Field Type Description Attributes BODY_LOSS Float Losses due to the users body (dB) Null column allowed: No Default value: 0 DL_ACTIVITY Float Activity factor for voice services on the downlink Null column allowed: Yes Default value: 1 DL_DP Float Packet inter-arrival time (ms) in downlink Null column allowed: Yes Default value: 0 DL_DPC Float Reading time (distance) between two packet calls (ms) in downlink Null column allowed: Yes Default value: 0 DL_HIGHEST_BEARER Float The highest bearer to allowed to be used for this service in DL Null column allowed: Yes Default value: 15 DL_GBR Float Minimum required transmission rate in DL (Guaranteed Bit Rate) Null column allowed: No Default value: 0 © Forsk 2009 AT281_AM_E1 357 Administrator Manual DL_MBR Float Maximum sustained trasmission rate in DL (Maximum Bit Rate) Null column allowed: No Default value: 0 DL_NPC Integer Number of packet calls during a session in downlink Null column allowed: Yes Default value: 1 DL_SP Integer Packet size (Bytes) in downlink Null column allowed: Yes Default value: 1500 DL_SPC_MAX Float Downlink maximum packet call size (kBytes) Null column allowed: Yes Default value: 2000 DL_SPC_MIN Float Downlink minimum packet call size (kBytes) Null column allowed: Yes Default value: 4 NAME Text (50) Service name Null column allowed: No Default value: PRIORITY Short Service priority (0: lowest) Null column allowed: Yes Default value: 0 REQ_AVERAGE_DL_RATE Float Requested Average Downlink Rate (kbps) Null column allowed: Yes Default value: REQ_AVERAGE_UL_RATE Float Requested Average Uplink Rate (kbps) Null column allowed: Yes Default value: TH_OFFSET Float Offset to add to TH_SCALE_FACTOR Null column allowed: No Default value: 0 TH_SCALE_FACTOR Float Ratio between application level throughput and RLC layer throughput Null column allowed: No Default value: 95 TYPE Short Service type Null column allowed: Yes Default value: 0 Choice list: 0: Voice, 1: Data UL_ACTIVITY Float Activity factor for voice services on the uplink Null column allowed: Yes Default value: 1 UL_DP Float Packet inter-arrival time (ms) in uplink Null column allowed: Yes Default value: 0 UL_DPC Float Reading time (distance) between two packet calls (ms) in uplink Null column allowed: Yes Default value: 0 UL_HIGHEST_BEARER Float The highest bearer to allowed to be used for this service in UL Null column allowed: Yes Default value: 15 UL_GBR Float Minimum required transmission rate in UL (Guaranteed Bit Rate) Null column allowed: No Default value: 0 UL_MBR Float Maximum sustained trasmission rate in UL (Maximum Bit Rate) Null column allowed: No Default value: 0 UL_NPC Integer Number of packet calls during a session in uplink Null column allowed: Yes Default value: 1 UL_SP Integer Packet size (Bytes) in uplink Null column allowed: Yes Default value: 1500 UL_SPC_MAX Float Uplink maximum packet call size (kBytes) Null column allowed: Yes Default value: 2000 UL_SPC_MIN Float Uplink minimum packet call size (kBytes) Null column allowed: Yes Default value: 4 8.8.1.24.5 T4GBearers Table Field Type Description Attributes BEARER_INDEX Short Modulation and coding scheme number Null column allowed: No Default value: 1 CODING_RATE Float Coding rate Null column allowed: Yes Default value: 1 MODULATION Short Modulation type Null column allowed: No Default value: 1 Choice list: 0: BPSK, 1: QPSK, 2: 16QAM 3: 64QAM NAME Text (50) Name of the LTE radio bearer Null column allowed: No Default value: SPECTRAL_EFFICIENCY Float Spectral efficiency = Peak RLC Throughput per Hz Unit: bps/Hz Null column allowed: Yes Default value: 0 358 AT281_AM_E1 © Forsk 2009 Chapter 8: Database Structure 8.8.1.24.6 T4GTerminals Table Field Type Description Attributes ANTENNA Text (50) Receiver's antenna name (if empty an omni antenna is used) Null column allowed: Yes Default value: GAIN Float Terminal antenna gain (dB) Null column allowed: Yes Default value: 0 LOSS Float Terminal antenna loss (dB) Null column allowed: Yes Default value: 0 NAME Text (50) Terminal name Null column allowed: No Default value: NOISE_FACTOR Float Noise figure used to determine the thermal noise at the receiver (dB) Null column allowed: Yes Default value: 8 PMAX Float Maximum terminal power on traffic channel (dBm) Null column allowed: Yes Default value: 23 PMIN Float Minimum terminal power on traffic channel (dBm) Null column allowed: Yes Default value: -40 RX_EQUIP Text (50) Name of the reception equipment available at the terminal Null column allowed: Yes Default value: "Default CPE Reception Equipment" DIVERSITY_SUPPORT Short Antenna diversity support (0 = None, 1 = MIMO) Null column allowed: Yes Default value: 1 MIMO_TX_ANTENNAS Short Number of MIMO antennas used for transmission Null column allowed: Yes Default value: 1 MIMO_RX_ANTENNAS Short Number of MIMO antennas used for reception Null column allowed: Yes Default value: 1 8.8.1.24.7 T4GTraficEnvironments Table Field Type Description Attributes CLUTTER_WEIGHTS Binary Internal binary format describing weights assigned to each clutter class Null column allowed: Yes Default value: NAME Text (50) Name of the created environment Null column allowed: No Default value: 8.8.1.24.8 T4GUserProfiles Table Field Type NAME 8.8.1.25 Text (50) Description Attributes Name of the created user profile Null column allowed: No Default value: QualityIndicators Table This table is used by Quality Indicator (FER, BER, BLER, etc.) coverage predictions. Field Type Description Attributes CS_QI Boolean Flag indicating whether the Quality Indicator is used for Voice (CS) services Null column allowed: No Default value: True MEAS_PARAM Short Name of the measured figure used for this QI determination Null column allowed: Yes Default value: 0 Choice list: 0 = C, 1 = CIR NAME Text (50) Name of the Quality Indicator Null column allowed: No Default value: PS_QI Boolean Flag indicating whether the Quality Indicator is used for Data (PS) services Null column allowed: No Default value: True USE_INTERPOLATION Boolean Flag indicating whether the Quality Indicator must be interpolated or not Null column allowed: No Default value: True 8.8.1.26 T4GMimoConfigs Table This table stores the maximum MIMO gain graphs for different numbers of transmission and reception antennas. Field Type Description Attributes MOBILITY Text(50) User mobility Null column allowed: Yes Default value: © Forsk 2009 AT281_AM_E1 359 Administrator Manual MIMO_TX_ANTENNAS Short Number of MIMO antennas used for transmission Null column allowed: Yes Default value: 1 MIMO_RX_ANTENNAS Short Number of MIMO antennas used for reception Null column allowed: Yes Default value: 1 MAX_MIMO_GAIN Memo Graph of maximum MIMO gains vs. C/(I+N) Null column allowed: Yes Default value: STTD_GAIN Float Diversity gain that will be applied to the CINR (dB) Null column allowed: Yes Default value: 0 BEARER_INDEX Short Index of the LTE bearer Null column allowed: Yes Default value: 1 MAX_BLER Float Maximum value of BLER for which the gains are applicable Null column allowed: Yes Default value: 1 EQUIPMENT Text (50) Name of the equipment to which the MIMO gains correspond Null column allowed: No Default value: 8.8.1.27 InterNetChProtect Table This table stores the inter-network channel protection graphs. 360 Field Type Description Attributes ICP Memo Inter-network channel protection = f(  MHz) Null column allowed: Yes Default value: ITF_BW Double Interfering bandwidth (kHz) Null column allowed: No Default value: 0 ITF_TECHNO Text (50) Interfering technology Null column allowed: No Default value: V_BW Double Victim bandwidth (kHz) Null column allowed: No Default value: 0 AT281_AM_E1 © Forsk 2009 Administrator Manual © Forsk 2009 AT281_AM_E1 361 Administrator Manual version 2.8.1 AT281_AM_E1 October 2009  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 4846 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

Atoll 2[1].8.1 Administrator Manual E1

Related documents

Products

Support

Atoll 2[1].8.1 Administrator Manual E1

Related documents

Add this document to collection(s)

Add this document to saved

Suggest us how to improve StudyLib