Atoll 3.2.1 Administrator Manual

Version3.2.
AdministratorManual
AT321_AM_E1
Atoll3.2.1AdministratorManual
Release:AT321_AM_E1(February2014)
Copyright19972014Forsk.AllRightsReserved.
Publishedby:
Forsk
7ruedesBriquetiers
31700Blagnac,France
Tel:+33562747210
Fax:+33562747211
Thesoftwaredescribedinthisdocumentisprovidedunderalicenceagreement.Thesoftwaremayonlybeusedorcopiedunderthetermsandconditionsofthelicenceagreement.
Nopartofthecontentsofthisdocumentmaybereproducedortransmittedinanyformorbyanymeanswithoutwrittenpermissionfromthepublisher.
Theproductorbrandnamesmentionedinthisdocumentaretrademarksorregisteredtrademarksoftheirrespectiveregisteringparties.
Thepublisherhastakencareinthepreparationofthisdocument,butmakesnoexpressedorimpliedwarrantyofanykindandassumesnoresponsibilityforerrorsoromissions.No
liabilityisassumedforincidentalorconsequentialdamagesinconnectionwithorarisingoutoftheuseoftheinformationcontainedherein.
Atoll 3.2.1 Administrator Manual
Forsk 2014
TableofContents
AT321_AM_E1
TableofContents
1
1.1
1.2
1.3
1.4
1.5
1.5.1
1.5.2
1.5.3
1.5.4
1.5.5
1.6
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
3
3.1
3.2
3.3
4
4.1
4.1.1
4.1.2
4.1.3
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.2.4.1
4.2.4.2
4.2.4.3
5
5.1
5.2
5.3
5.4
5.4.1
5.4.2
5.5
5.6
5.6.1
5.6.2
5.6.3
5.7
5.8
GettingStarted.....................................................13
SupportedTechnologies ................................................................................. 13
SupportedOperatingSystems............................................................................ 13
SupportedDatabaseManagementSystems ................................................................. 14
SupportedInstallationConfigurations...................................................................... 14
RecommendedHardwareandSoftware .................................................................... 14
UserComputers...................................................................................... 14
DatabaseServers..................................................................................... 15
ApplicationServers ................................................................................... 15
FloatingLicenceServers ............................................................................... 15
FileServers.......................................................................................... 15
RecommendedComputerNetworkArchitecture............................................................. 16
InstallingAtollandComponents ......................................17
InstallingAtollUsingtheSetupWizard..................................................................... 17
InstallingaLanguagePackUsingtheSetupWizard........................................................... 19
InstallingAtollC++DevelopmentKit ....................................................................... 20
SetupCommandLineParameters......................................................................... 21
InstallingandUninstallingAddins......................................................................... 22
InstallingandUninstallingMacros ......................................................................... 23
AtollCommandLineParameters.......................................................................... 24
TroubleshootingandOtherInformation .................................................................... 25
SettingUpDistributedCalculationServer ...............................27
SettingUpServers ...................................................................................... 27
SettingUpAtolltoAccesstheServers...................................................................... 28
DistributedCalculationProcess........................................................................... 28
ManagingLicences..................................................31
WorkingwithFloatingLicences........................................................................... 31
HASPLicenceManagerandDeviceDriver ................................................................. 31
nhsrv.iniFile......................................................................................... 32
nethasp.iniFile ....................................................................................... 33
UsingtheAtollLicenceManager.......................................................................... 33
LicenceManagerInterface ............................................................................. 34
UpdatingLicenceKeys ................................................................................. 35
TestingLicenceKeys................................................................................... 35
ReducingtheNumberofModuleTokensinALICFiles ....................................................... 36
ActivatingtheOptionintheLicenceManager ............................................................ 36
ReducingtheNumberofModuleTokens ................................................................ 36
ProgrammingaBlankLicenceKeyUsingtheRestrictedALICFile ............................................ 37
ManagingDatabases ................................................39
AtollDatabaseTemplates ................................................................................ 39
CustomisingAtollDatabaseStructures..................................................................... 40
AtollManagementConsole .............................................................................. 42
CreatingNewDatabases................................................................................. 43
CreatingaNewDatabaseUsingtheAtollManagementConsole .............................................. 43
CreatingaNewDatabaseUsingAtoll ..................................................................... 45
UpgradingExistingDatabases ............................................................................ 45
WorkingWithaMultilevelDatabases ..................................................................... 49
CreatingProjectDatabases ............................................................................. 50
ArchivingProjectDatabasestoMasterDatabases.......................................................... 52
RefreshingProjectDatabasesfromMasterDatabases....................................................... 53
SettingDatabaseAccessPrivileges ........................................................................ 53
ManagingDataModificationsHistory ...................................................................... 54
TableofContents
5.8.1
5.8.2
5.8.3
5.8.4
5.8.4.1
5.8.4.2
5.9
5.9.1
5.9.2
6
6.1
6.2
6.2.1
6.2.2
6.2.3
6.2.4
6.2.5
6.3
6.3.1
6.3.2
6.3.3
6.4
6.4.1
6.4.2
6.4.3
6.4.4
7
7.1
7.1.1
7.1.2
7.1.3
7.1.4
7.2
7.3
8
8.1
8.1.1
8.1.2
8.1.3
8.1.4
8.1.5
8.1.6
9
9.1
9.1.1
9.1.2
9.2
9.3
9.4
9.5
9.5.1
9.5.2
9.5.3
9.6
9.6.1
9.6.2
9.6.3
9.7
9.7.1
9.7.1.1
9.7.1.2
Forsk2014
SettingUpDataModificationsHistoryManagement........................................................54
Enabling/DisablingDataModificationsHistoryManagement .................................................55
UpdatingAfterDataStructureUpgrade ...................................................................55
PurgingOldDataModificationRecords...................................................................56
PurgingOldDataModificationRecordsofaTable.........................................................56
PurgingOldDataModificationRecordsofaDatabase .....................................................57
Appendices ............................................................................................58
Appendix1:AdvancedCustomisation ....................................................................58
Appendix2:SettingUpDatabasesforCoplanning ..........................................................60
MultiuserEnvironments............................................ 63
SettingUpMultiuserEnvironments .......................................................................63
ComponentsofMultiuserEnvironments...................................................................63
MasterAtollDocument ................................................................................64
MasterDatabase......................................................................................64
SharedGeographicData ...............................................................................64
SharedPathLossMatrices ..............................................................................65
UserAtollDocuments..................................................................................65
ManagingUserAccountsandAccessRightsinOracle.........................................................65
DefiningDatabaseandInterfaceAccessRights .............................................................66
CreatingandEditingUserAccounts ......................................................................68
ResettingUserDatabasePermissions.....................................................................68
Appendices ............................................................................................69
Appendix1:CheckingDataIntegrity......................................................................69
Appendix2:DatabaseRegionalisation....................................................................70
Appendix3:CalculatingPathLossMatrices ................................................................70
Appendix4:PathLossMatricesFromDifferentSources .....................................................71
CoordinateSystemsandUnits....................................... 73
CoordinateSystems .....................................................................................73
DefinitionofaCoordinateSystem .......................................................................73
TypesofCoordinateSystemsinAtoll.....................................................................74
CoordinateSystemsFileFormat.........................................................................75
CreatingaCoordinateSysteminAtoll ....................................................................78
Units .................................................................................................79
BSICFormat ...........................................................................................80
GeographicData .................................................. 81
GeographicHeaderFileFormats ..........................................................................82
HDRHeaderFileforBILFiles............................................................................82
TFWHeaderFileforTIFFFiles...........................................................................83
BPW/BMWHeaderFilesforBMPFiles ....................................................................84
PGWHeaderFileforPNGFiles ..........................................................................84
JGWHeaderFileforJPGFiles ...........................................................................84
GenericRasterHeaderFile .............................................................................85
RadioDataFormats ................................................ 87
XMLImport/ExportFormat...............................................................................87
Index.xmlFileFormat ..................................................................................87
XMLFileFormat ......................................................................................88
RF2DAntennaPatternFormat............................................................................89
ImportFormatof3DAntennaPatternTextFiles .............................................................91
Microwave2DAntennaPatternFormat ....................................................................91
PathLossMatrixFileFormat..............................................................................92
Pathloss.dbfFileFormat................................................................................92
Pathloss.dbfFileContents..............................................................................95
LOSFileFormat .......................................................................................96
PathLossTuningFileFormat .............................................................................96
Pathloss.dbfFileFormat................................................................................96
Pathloss.dbfFileContents..............................................................................96
PTSFileFormat .......................................................................................96
InterferenceMatrixFileFormats ..........................................................................97
CLCFormat(OneValueperLine) ........................................................................97
CLCFileFormat .....................................................................................97
DCTFileFormat .....................................................................................98
AT321_AM_E1
9.7.2
9.7.3
9.7.4
9.8
9.8.1
9.8.2
10
10.1
10.2
10.3
10.4
10.5
10.6
10.7
10.8
10.9
10.10
10.11
10.12
10.13
10.14
10.15
10.15.1
10.15.2
11
11.1
11.1.1
11.1.2
11.1.3
11.1.4
11.1.5
11.1.6
11.1.7
11.1.8
11.1.9
11.1.10
11.1.11
11.1.12
11.2
11.2.1
11.2.2
11.2.3
11.2.4
11.2.5
11.3
11.4
12
12.1
12.1.1
12.1.1.1
12.1.1.2
12.1.1.3
12.1.1.4
12.1.1.5
12.1.1.6
12.1.1.7
12.1.1.8
12.1.1.9
12.1.1.10
12.1.1.11
12.1.1.12
12.1.1.13
TableofContents
IM0Format(OneHistogramperLine) .................................................................... 99
IM1Format(OneValueperLine,TXNameRepeated)...................................................... 100
IM2Format(CoandAdjacentchannelProbabilities)...................................................... 102
"PerTransmitter"PredictionFileFormat .................................................................. 102
<per_transmitter_prediction>.dbfFileFormat ............................................................ 103
<per_transmitter_prediction>.dbfFileContents .......................................................... 103
AdministrationandUsageRecommendations..........................105
GeographicData ...................................................................................... 105
PathLossMatrices..................................................................................... 106
AtollDocuments ...................................................................................... 107
Databases............................................................................................ 107
CalculationServer..................................................................................... 108
AtollAdministrationFiles............................................................................... 108
ProcessMemory ...................................................................................... 109
Printing .............................................................................................. 109
CoveragePredictionCalculations......................................................................... 110
CWMeasurementsandDriveTestData................................................................... 110
AntennaPatternsandImport............................................................................ 110
TrafficMaps .......................................................................................... 110
AtollAPI ............................................................................................. 111
PerformanceandMemory.............................................................................. 111
Appendix:MemoryRequirements........................................................................ 113
DiskSpaceRequirements ............................................................................. 113
RAMRequirements .................................................................................. 114
ConfigurationFiles.................................................117
ContentsofUserConfigurationFiles ...................................................................... 118
GeographicDataSet ................................................................................. 118
Zones .............................................................................................. 121
MapCentreandZoomLevel ........................................................................... 122
FolderConfiguration ................................................................................. 122
CoveragePredictions ................................................................................. 129
AutomaticNeighbourAllocationParameters ............................................................. 131
AutomaticFrequencyPlanningParameters .............................................................. 133
AutomaticScramblingCodeAllocationParameters ........................................................ 134
AutomaticPNOffsetAllocationParameters.............................................................. 136
AutomaticOFDMResourceAllocationParameters ........................................................ 137
MicrowaveRadioLinksParameters..................................................................... 138
Macros ............................................................................................ 141
ContentsofAdditionalConfigurationFiles................................................................. 141
PrintSetupConfiguration ............................................................................. 141
TableImport/ExportConfiguration ..................................................................... 143
CoveragePredictionReportConfiguration ............................................................... 143
CWMeasurementImportConfiguration ................................................................. 144
DriveTestDataImportConfiguration ................................................................... 144
ContentoftheCustomPredictionsFile.................................................................... 145
Contentofthe"ValueIntervals"PredictionsFiles........................................................... 146
InitialisationFiles ..................................................147
AtollInitialisationFile.................................................................................. 147
GeneralOptions ..................................................................................... 147
ModifyingtheDefaultFormatsofSiteandTransmitterNames............................................. 147
DisablingAutomaticRenamingofTransmittersandCells.................................................. 148
SettingtheTIFFColourConvention.................................................................... 148
CreatinganEventViewerLogFile ..................................................................... 148
DisplayingInsufficientPermissionMessagesintheEventViewer ........................................... 149
IncreasingtheMaximumPrintingResolution ........................................................... 149
DuplicatingLinkedPathLossMatricesonSaveAs........................................................ 149
DisablingExternalStorageofNumericalResultsFilesforPredictions ........................................ 150
RestrictingtheListofPredictionsforCreatingSectorTrafficMaps .......................................... 150
DisplayingPathLossCalculationDetailsintheEventViewer ............................................... 150
MappingAtollCoordinateSystemswithMapInfo/ESRIVectorFiles......................................... 150
ExportingCoveragePredictionPolygonsinTextFormat................................................... 151
DefiningWebMapServicesServers................................................................... 151
TableofContents
12.1.1.14
12.1.1.15
12.1.1.16
12.1.1.17
12.1.1.18
12.1.1.19
12.1.1.20
12.1.1.21
12.1.1.22
12.1.1.23
12.1.1.24
12.1.1.25
12.1.1.26
12.1.1.27
12.1.1.28
12.1.1.29
12.1.1.30
12.1.1.31
12.1.1.32
12.1.1.33
12.1.1.34
12.1.1.35
12.1.1.36
12.1.1.37
12.1.1.38
12.1.1.39
12.1.1.40
12.1.1.41
12.1.1.42
12.1.1.43
12.1.1.44
12.1.1.45
12.1.1.46
12.1.1.47
12.1.1.48
12.1.1.49
12.1.2
12.1.2.1
12.1.2.2
12.1.2.3
12.1.2.4
12.1.2.5
12.1.2.6
12.1.2.7
12.1.2.8
12.1.2.9
12.1.2.10
12.1.2.11
12.1.2.12
12.1.2.13
12.1.2.14
12.1.2.15
12.1.2.16
12.1.2.17
12.1.3
12.1.3.1
12.1.3.2
12.1.3.3
12.1.4
12.1.4.1
12.1.4.2
12.1.4.3
12.1.4.4
12.1.5
12.1.5.1
12.1.5.2
Forsk2014
ImprovingPointAnalysisPerformance................................................................ 152
LoadingVectorFilesDynamically..................................................................... 152
ExcludingVectorsfromImportedKML/KMZFiles ....................................................... 152
SettingthePrecisionfortheAntennaPatternVerificationatImport ....................................... 152
OpeningExportedXLSFilesAutomaticallyinMSExcel................................................... 153
DisablingCreationofNewDocumentsfromTemplates .................................................. 153
BlockingAccesstoMacrosandAddins................................................................ 153
DisablingSavingandOpeningZIPFiles................................................................ 153
EnablingNotificationforDonorTransmitterParameterModifications ...................................... 153
SettingtheDisplayPrecisionofFloatingPointValues .................................................... 153
ChangingthePathtoLinkedGeoDataFiles ............................................................ 154
Exporting/ImportingVectorDatawithaDisplayConfigurationFile......................................... 154
UsingOnlyVisibleGeoDatainPredictionReports....................................................... 154
ExportingBMP,TIF,andPNGFileswithaTABReferenceFile.............................................. 154
CoPlanning:LinkingtheSitesFolder.................................................................. 154
DisablingNormalisationofMIF/TABVectorFiles ........................................................ 155
AddingtheDuplicateSitetotheOriginalSitesSiteList .................................................. 155
UsingOnlyVisibleClutterClassesinInterferencePredictionReports....................................... 155
Displaying%ofCoveredClutterClassesw.r.t.theFocusZoneinReports ................................... 155
Displaying%ofCoveredTrafficClassesw.r.t.theFocusZoneinReports ................................... 155
SynchronisingPrivateandSharedPathLossMatrices .................................................... 155
SelectingtheLogo2CheckBoxbyDefaultinPrintSetup................................................. 156
FilteringPredictionsbyTechnologyWhenReadingtheXMLStudiesFile .................................... 156
EnablingEventViewerMessagesforMapInfoFileImport/Export .......................................... 156
SettingtheResolutionofPopulationMapsinCoveragePredictionReports .................................. 156
SettingthePrecisioninCoveragePredictionReports .................................................... 157
IncludingPixelfreeRangesinCoveragePredictionReports ............................................... 157
ChangingHotSpotReferenceSurfaceinPredictionReports .............................................. 157
ExportingOnlyVisibleValueIntervalLayersofCoveragePredictions....................................... 157
AvoidingOverlappingPixelsinBestServerCoveragePrediction ........................................... 157
SettingtheMinimumATLFileSizeRequiringCompression ............................................... 158
Loading,Activating,andSettingAddinsasVisible ...................................................... 158
DefiningOnlineMapURLs .......................................................................... 158
ChangingtheDefaultCacheLocationfortheLoadedMapTiles............................................ 158
ManagingCarriageReturnsinImportedTXT/CSVFiles ................................................... 159
DeletingtheFilteringZoneonRemovingFiltersFromTables .............................................. 159
GUIOptions ........................................................................................ 159
DefiningtheParametersfortheDefaultSitesSymbol.................................................... 159
UsingaUniqueSymbolforRemoteAntennas .......................................................... 159
KeepingTransmitterSymbolsFromChangingonSearch ................................................. 160
DisplayingFilledSymbolsforInactiveTransmittersontheMap ........................................... 160
RefreshingtheDisplayAutomaticallyWhenaNewStationisDropped...................................... 160
HidingInformationDisplayedintheStatusBar ......................................................... 160
DisplayingDateandTimeintheEventViewer .......................................................... 160
SettingtheMaximumNumberofLinesinCoveragePredictionToolTips .................................... 160
ChangingtheDisplayforDownlinkSmartAntennaResults ............................................... 161
AddingExposureAnalysistotheListofMultiRATCoveragePredictions(Hiddenen3.2.0.02,cesinfossontdansTN013)
161
DisplayingCoveragePredictionCommentsintheLegendWindow ......................................... 161
DisplayingLeadingZerosintheCELL_IDENTITYField .................................................... 161
MakingtheAntennaAdditionalElectricalDowntiltAccessible............................................. 161
IncreasingtheWidthoftheClutterDescriptionPaneintheStatusBar...................................... 162
HidingtheTechnologyNameintheTitleBar........................................................... 162
DisplayingObjectsDiscreteValueswithUserdefinedColours............................................ 162
DisplayingVerticalBeamwidthinProfileAnalysis ....................................................... 162
DistributedCalculationServerOptions.................................................................. 163
DetectingandListingDistributedCalculationServers.................................................... 163
SettingtheDistributedCalculationServerPriority....................................................... 163
ModifyingtheDefaultDetectionTimeout ............................................................. 163
LicenceManagementOptions ......................................................................... 164
SettinganAlarmfortheLicenceEndDate............................................................. 164
BlockingAccesstoTechnologyModules ............................................................... 164
BlockingAccesstoACPandAFPModules .............................................................. 164
ChangingtheNetHASPLicenceManagerIdleTimeSetting................................................ 164
DatabaseOptions................................................................................... 165
CheckingDataIntegrityAfterDatabaseUpgradeandDataRefresh......................................... 165
AutomaticallyRunningaDatabaseIntegrityCheckatOpenorRefresh...................................... 165
AT321_AM_E1
12.1.5.3
12.1.5.4
12.1.5.5
12.1.5.6
12.1.5.7
12.1.5.8
12.1.5.9
12.1.5.10
12.1.5.11
12.1.5.12
12.1.6
12.1.6.1
12.1.6.2
12.1.6.3
12.1.6.4
12.1.6.5
12.1.6.6
12.1.6.7
12.1.6.8
12.1.6.9
12.1.6.10
12.1.6.11
12.1.6.12
12.1.6.13
12.1.6.14
12.1.6.15
12.1.6.16
12.1.6.17
12.1.6.18
12.1.6.19
12.1.6.20
12.1.6.21
12.1.6.22
12.1.6.23
12.1.6.24
12.1.6.25
12.1.6.26
12.1.6.27
12.1.6.28
12.1.6.29
12.1.6.30
12.1.6.31
12.1.6.32
12.1.7
12.1.7.1
12.1.7.2
12.1.7.3
12.1.7.4
12.1.7.5
12.1.7.6
12.1.7.7
12.1.7.8
12.1.7.9
12.1.7.10
12.1.7.11
12.1.7.12
12.1.7.13
12.1.7.14
12.1.7.15
12.1.7.16
12.1.7.17
12.1.7.18
12.1.7.19
12.1.7.20
12.1.7.21
12.1.8
12.1.8.1
TableofContents
AllowingNullEntriesinNonnullableCustomFields ...................................................... 165

AutomaticallyRunningGSMSubcellAuditatOpenorRefresh ............................................. 165
ModifyingtheDefaultDatabaseConnectionTimeout.................................................... 166
MakingAtollCaseSensitiveforDatabaseImportFromPlanet ............................................. 166
SettingtheSignforKClutterWhenImportingDataFromPlanetEV......................................... 166
Enabling/DisablingPasswordPromptatArchive ......................................................... 166
ArchivingDatatoDatabasesUsingTransactions ......................................................... 167
KeepingSeparateWorkandMasterPathLossDirectories ................................................. 167
EnablingPartialRefreshfromRecentlyUpgradedDatabases .............................................. 167
SettingtheTypeofDatabaseBeingUsed............................................................... 167
CommonCalculationOptions .......................................................................... 168
SettingtheAntennaPatternsModellingMethod........................................................ 168
DisablingAutomaticLockingofCoveragePredictions..................................................... 168
EnablingShadowingMargininCalculations ............................................................. 168
SettingaDefaultValuefortheCellEdgeCoverageProbability............................................. 169
EnablingIndoorCoverageinCalculations............................................................... 169
ModifyingtheResolutionfortheLOSAreaCalculationAroundaSite ....................................... 169
EmbeddingPathLossesinNewDocuments............................................................. 169
StoppingCalculationsonError ....................................................................... 169
WarningAboutPredictionValidityWhenDisplayOptionsareModified ..................................... 170
ReadingExactAltitudesFromtheDTM ................................................................ 170
SettingaCommonDisplayResolutionForAllCoveragePredictions......................................... 170
SettingthePrioritiesforGUIandCalculations ........................................................... 170
SettingtheNumberofParallelProcessorsandThreads ................................................... 171
DisablingParallelCalculationofMonteCarloSimulations................................................. 171
PerformingCalculationsinReadOnlyDocuments ....................................................... 171
IdentifyingTransmitter,Repeater,andRemoteAntennaCoverageAreas.................................... 172
ChangingtheRoundingMethodUsedforProfileExtraction ............................................... 172
EstimatingRequiredandUsedMemorySizeforUMTSSimulations......................................... 172
DisablingCalculationsOverNoDataValuesforDTMandClutterClasses..................................... 172
Coplanning:CalculatingPredictionsintheCurrentDocumentOnly......................................... 172
Coplanning:CalculatingPredictionsinSerialorinParallel ................................................ 172
ForcingNeighbourSymmetryOnlyInsideFocusZone .................................................... 173
UsingPoissonDistributioninMonteCarloSimulations ................................................... 173
CalculatingEIRPfromMaxPowerinSignalLevelPredictions .............................................. 173
ExcludingFilteredTransmittersfromtheListofNeighbours............................................... 173
ChangingtheWeightingFactoroftheEffectiveIntertransmitterDistance ................................... 173
ExtendingtheMaximumIntersiteDistancetoRepeatersandRemoteAntennas.............................. 174
ForcingtheRealIntersiteDistanceThreshold .......................................................... 174
PrioritisingIndividualIntersiteDistancesinNeighbourImportanceCalculation............................... 174
KeepingtheAssignedNeighbourswhicharenotSymmetrisedwiththeReferenceTransmitter .................. 174
EnablingandDisablingPersitePathLossMatrixCalculations .............................................. 174
DefiningaGlobalMaximumPathLossCalculationRadius................................................. 175
GSMGPRSEDGEOptions ............................................................................. 175
ConsideringIntertechnologyInterference ............................................................. 175
ConsideringOverlappingZonesforIMCalculationBasedonTraffic......................................... 175
SettingtheDefaultBSICFormat ...................................................................... 175
CheckingDatabaseConsistencyAutomatically .......................................................... 175
DisablingtheMaximumRangeParameter .............................................................. 175
EnablingtheSupportforMultibandTransmitters....................................................... 176
SettingtheBestServerCalculationMethodinSamePriorityHCSLayers ..................................... 176
HidingAdvancedAFPParameters ..................................................................... 176
ModifyingtheThresholdsforImportantViolationsinAFP................................................. 177
HidingViolationsBetweenLowImportanceGSMNeighboursinAFPResults ................................. 177
HidingViolationsBetweenNonsynchronisedMALsMAIOsinAFPResults................................... 177
SelectingtheInterferenceMatricesUsedDuringtheAFP ................................................. 177
DefiningtheMaximumNumberofTransmittersforReuseDistance ........................................ 178
MakingRedundantFieldsintheTransmittersTableReadonly ............................................. 178
SettingtheTransmissionDiversityGain................................................................ 178
AddingGroupedHCSServersOptioninCalculations...................................................... 178
DeactivatingFrequencyBandFilteringinIMCalculation.................................................. 178
StartingTRXIndexesat1............................................................................ 179
HidingtheTRXIndex................................................................................ 179
ExtendingtheAllowedValueRangeforC/IandReceptionThresholds....................................... 179
AutomaticallyCorrectingOutofrangeSubcellValues .................................................... 179
UMTSHSPA,CDMA2000,andTDSCDMAOptions ......................................................... 180
SuppressingCellNameCarrierSuffixes ................................................................ 180
TableofContents
12.1.8.2
12.1.8.3
12.1.8.4
12.1.8.5
12.1.8.6
12.1.8.7
12.1.8.8
12.1.8.9
12.1.8.10
12.1.8.11
12.1.8.12
12.1.8.13
12.1.8.14
12.1.8.15
12.1.8.16
12.1.8.17
12.1.8.18
12.1.8.19
12.1.8.20
12.1.8.21
12.1.8.22
12.1.9
12.1.9.1
12.1.9.2
12.1.9.3
12.1.9.4
12.1.9.5
12.1.9.6
12.1.9.7
12.1.9.8
12.1.9.9
12.1.9.10
12.1.9.11
12.1.9.12
12.1.9.13
12.1.9.14
12.1.9.15
12.1.9.16
12.1.9.17
12.1.9.18
12.1.9.19
12.1.9.20
12.1.9.21
12.1.9.22
12.1.9.23
12.1.10
12.1.10.1
12.1.11
12.1.11.1
12.1.11.2
12.1.11.3
12.1.11.4
12.1.11.5
12.1.11.6
12.1.11.7
12.1.11.8
12.1.11.9
12.1.11.10
12.1.12
12.1.12.1
12.1.12.2
12.1.12.3
12.1.12.4
12.1.12.5
12.1.12.6
12.1.13
12.1.13.1
10
Forsk2014
DisablingMacrodiversity(SHO)GainsinCalculations ................................................... 180

CalculatingandDisplayingPeakorInstantaneousHSDPAThroughput...................................... 180
SettingthePowertoUseforIntracellInterferenceinHSDPA ............................................. 181
EnablingCoveragePredictionsofConnectionProbabilities ............................................... 181
SettingtheCalculationMethodforHSPDSCHCQI ...................................................... 181
EnablingOrthogonalityFactorinPilotEC/NTCalculationinHSDPA......................................... 181
SettingtheMaximumNumberofRejectionsforMobiles ................................................. 181
SettingtheMaximumNumberofRejectionsforHSDPAMobiles........................................... 182
DefininganOffsetWithRespecttoTheThermalNoise................................................... 182
SettingPrecisionoftheRasterisationProcess .......................................................... 182
DefiningtheNumberofIterationsBeforeDowngrading.................................................. 183
AdjustingtheWorkingoftheProportionalFairScheduler ................................................ 183
DisplayingEc/I0ofRejectedMobilesinSimulationResults ............................................... 183
SwitchingBacktotheOldBestServerDeterminationMethod ............................................ 184
DisplayingAutomaticAllocationCostValues........................................................... 184
SelectingSCandPNOffsetAllocationStrategiesAvailableintheGUI ....................................... 184
DefiningaFixedIntervalBetweenScramblingCodes .................................................... 184
CompressedMode:RestrictingIntercarrierandIntertechnologyNeighbourAllocation....................... 184
SettingtheMaximumASSizeforSCInterferencePrediction .............................................. 185
DisplayingUplinkTotalLossesinCoveragebySignalLevel ................................................ 185
SettingtheMaximumULReuseFactorforHSUPAUsersNoiseRiseEstimation.............................. 185
LTE,WiMAX,andWiFiOptions........................................................................ 185
BlockingAccesstoIEEEParametersinWiMAX.......................................................... 185
UsingOnlyBearersCommonBetweentheTerminalsandCellsEquipment................................. 186
EnablingDisplayofSignalsperSubcarrierPointAnalysisinLTE ............................................ 186
IncludingCyclicPrefixEnergyinLTESignalLevelCalculation.............................................. 186
ExcludingCyclicPrefixEnergyinWiMAXandWiFiSignalLevelCalculation.................................. 186
IgnoringInterNeighbourPreambleIndexCollisioninWiMAX ............................................. 186
IgnoringInterNeighbourPhysicalCellIDCollisioninLTE................................................. 187
ApplyingTransmitDiversityGainstoReferenceSignals .................................................. 187
RenamingOPUSCZonetoPUSCULinWiMAX.......................................................... 187
DeactivatingUniformDistributionofResources ........................................................ 187
TakingSecondOrderNeighboursintoAccountintheAFP................................................ 187
ExcludingtheAdjacentChannelOverlapfromtheAFPCostFunctions ...................................... 188
SwitchingBetweenSynchronisedandUnsynchronisedInterferenceCalculationMethods...................... 188
SettingPDCCHto100%LoadedinLTEInterferenceCalculations ........................................... 188
CalculatingEIRPfromRSEPREinLTESignalLevelPredictions ............................................. 188
AveragingtheUplinkNoiseRiseindB ................................................................. 189
DeactivatingServiceMaxThroughputDemandDowngradinginLTE........................................ 189
DisplayingPixelswithZeroThroughputinCoveragePredictions ........................................... 189
SettingUplinkNoiseRiseControlParametersinLTE ..................................................... 189
UsingtheABSPatternsThroughoutaCellinLTE ........................................................ 190
ApplyingtheABSCollisionProbabilityonInterferencefromRS ............................................ 190
EnablingMultieNodeBCarrierAggregation........................................................... 190
SwitchingBetweenCarrierAggregationSchedulingMethods ............................................. 190
3GPPMultiRATOptions ............................................................................. 190
BSIC,SC,andPCIAllocationwithIntertechnologyNeighbourConstraints ................................... 190
MicrowaveRadioLinksOptions ....................................................................... 191
UpdatingA>>BandB>>AProfilesinRealtime.......................................................... 191
DisablingShieldingFactoronWantedSignalatReceiver ................................................. 191
MakingtheITURP.5305MethodAvailable ........................................................... 191
DecreasingCalculationTimeofPathProfiles........................................................... 191
UsingOldMinC/IValues ........................................................................... 191
SolvingAlignmentIssueinGeneratedReports.......................................................... 192
UsingDefaultMethodforCalculatingUnavailability ..................................................... 192
DefiningDefaultConfigurationFilesforLinkBudgetsReports............................................. 192
DefiningaDefaultConfigurationFilefortheChannelArrangementDisplay.................................. 192
DefiningaDefaultTemplateforMicrowaveLinksCustomReports ......................................... 193
MeasurementOptions ............................................................................... 193
DisplayingAdditionalInformationinDriveTestData .................................................... 193
SettingtheNumberofTransmittersperDriveTestDataPath............................................. 193
RecalculatingDistancesofPointsFromThereServingCellsatImport....................................... 193
DefiningtheBCCHandBSICColumnsforFMTImport.................................................... 193
ImportingDriveTestDatawithScramblingCodesasIntegers............................................. 194
ImportingDriveTestDataforActiveandFilteredTransmittersOnly........................................ 194
ACPOptions........................................................................................ 194
SpecifyingtheLocationoftheAcp.iniFile.............................................................. 194
AT321_AM_E1
TableofContents
12.2
ACPInitialisationFile................................................................................... 194
12.2.1
ManagingPreferences ................................................................................ 194
12.2.2
GUIOptions ........................................................................................ 195
12.2.2.1
DefaultValuesontheOptimisationTab ................................................................ 195
12.2.2.2
DisplayingAdvancedCostOptions .................................................................... 195
12.2.2.3
AutomaticallyCreatingCustomZonesontheOptimisationTab ............................................ 196
12.2.2.4
DefaultValuesontheObjectivesTab .................................................................. 196
12.2.2.5
DefaultValuesontheReconfigurationpage............................................................ 203
12.2.2.6
DefaultValuesonSitestabofReconfigurationpage...................................................... 205
12.2.2.7
CustomColumnsonSitestabofReconfigurationpage.................................................... 205
12.2.2.8
DefaultValuesontheTransmittersTaboftheReconfigurationPage ........................................ 205
12.2.2.9
CustomColumnsonTransmitters/RemotestabsofReconfigurationpage.................................... 206
12.2.2.10
DefaultValuesonthePatternstaboftheAntennaTab................................................... 206
12.2.2.11
DefaultValuesforEMFExposure ..................................................................... 206
12.2.2.12
ControllingAntennaPatternSmoothing................................................................ 207
12.2.2.13
DefaultValuesontheAntennasTab................................................................... 208
12.2.2.14
DefiningtheAntennaMaskingModel ................................................................. 208
12.2.2.15
DefiningMultiStoreyOptions ........................................................................ 208
12.2.2.16
DefiningReconfigurationValuesinCustomAtollFields................................................... 208
12.2.2.16.1
DefiningReconfigurationValuesforTransmittersandRepeatersUsingCustomAtollFields ................... 209
12.2.2.16.2
DefiningReconfigurationValuesforSecondaryAntennasUsingCustomAtollFields ......................... 210
12.2.2.16.3
DefiningReconfigurationValuesforCellsUsingCustomAtollFields ....................................... 210
12.2.2.16.4
DefiningReconfigurationValuesforSitesUsingCustomAtollFields ....................................... 211
12.2.2.16.5
DefiningReconfigurationValuesforAntennasUsingCustomAtollFields ................................... 212
12.2.2.17
DefiningSiteClassOptions........................................................................... 213
12.2.2.17.1
DefiningAutomaticSiteClasses ..................................................................... 213
12.2.2.17.2
AutomaticAssignmentofSiteClassesintheACP....................................................... 214
12.2.2.18
DefiningtheAppearanceoftheOptimisationDialogBoxDuringaRun...................................... 214
12.2.2.18.1
DefiningtheColoursintheAnalysisMapsontheQualityTab............................................ 214
12.2.2.18.2
OtherComponentsoftheOptimisationDialogBox ..................................................... 215
12.2.2.19
DefiningtheAppearanceofPredictions ................................................................ 215
12.2.2.20
DefiningNewPredictions............................................................................ 216
12.2.2.21
DefiningtheFunctionalityoftheCommitTab ........................................................... 216
12.2.2.22
DefiningtheAppearanceoftheOverlayWindow ........................................................ 217
12.2.2.23
DefiningtheAppearanceoftheGraphTab ............................................................. 217
12.2.2.24
DefiningtheDefaultFont............................................................................ 217
12.2.2.25
ExportingOptimisationResultsinXML................................................................. 217
12.2.2.26
ChangingtheColourLegendfortheOptimisationGraph .................................................. 217
12.2.3
ACPCoreEngineOptions.............................................................................. 218
12.2.3.1
LogFileSettings ................................................................................... 218
12.2.3.2
CalculationThreadPoolSettings ...................................................................... 218
12.2.3.3
NumberofThreadsUsedforPropagationModelCalculations ............................................. 218
12.2.3.4
MemoryManagementSettings ....................................................................... 219
12.2.3.5
SignalLevelandMacroDiversityGainCalculationOptions ................................................ 219
12.2.3.5.1
SignalLevel...................................................................................... 219
12.2.3.5.2
MacroDiversityGain(UMTSOnly) .................................................................. 219
12.2.3.6
DeterminingTransmitterAltitude ..................................................................... 220
12.2.3.7
AutomaticCandidatePositioningOptions.............................................................. 220
12.2.3.8
BalancingSpeed,MemoryUse,andAccuracyinCalculations .............................................. 220
12.2.3.9
AccessingRasterData............................................................................... 221
12.2.3.10
AccessingPathLossMatrices......................................................................... 221
12.2.3.11
FilteringClutterClassLayers ......................................................................... 221
12.2.3.12
PreambleSegmentation(WiMAX) .................................................................... 222
12.2.3.13
MultiantennaInterferenceCalculation(LTE) ........................................................... 222
12.2.3.14
MultiantennaInterferenceCalculation(WiMAX) ........................................................ 222
12.2.3.15
CyclicPrefixEnergyinSignalLevelCalculation(LTE) ...................................................... 222
12.2.3.16
CyclicPrefixEnergyinSignalLevelCalculation(WiMAX) .................................................. 223
12.2.3.17
ApplyingTransmitDiversityGainstoReferenceSignals(LTE) .............................................. 223
12.2.3.18
FixedRatioBetweenPilotPowerandMaxPower(UMTS) ................................................. 223
12.2.3.19
ShowingInitial/Final"TotalPower"or"DLLoad"onSectorsTab(UMTS) ..................................... 223
12.2.3.20
EnablingMultitechnologyOptimisationIncludingWiMAX................................................ 223
12.2.4
EMFExposureCoreOptions........................................................................... 223
12.2.5
OtherOptions....................................................................................... 224
12.2.5.1
ValidityofCoveragePredictions...................................................................... 224
11
TableofContents
12
Forsk2014
Chapter1:GettingStarted
AT321_AM_E1
1 GettingStarted
Atollisanopen,scalable,andflexiblemultitechnologynetworkdesignandoptimisationplatformthatsupportswireless
operatorsthroughoutthenetworklifecycle,frominitialdesigntodensificationandoptimisation.Atollsupportsawiderange
ofimplementationscenarios,fromstandalonetoenterprisewideserverbasedconfigurationsusingdistributedandmulti
threadedcomputing.
Thismanualexplainshowtoinstall,configure,anddeployAtollandhowtosetupbackenddatabasesandmanageusersin
amultiuserenvironment.
Inthischapter,thefollowingareexplained:
"SupportedTechnologies"onpage 13
"SupportedOperatingSystems"onpage 13
"SupportedDatabaseManagementSystems"onpage 14
"SupportedInstallationConfigurations"onpage 14
"RecommendedHardwareandSoftware"onpage 14
"RecommendedComputerNetworkArchitecture"onpage 16.
1.1 SupportedTechnologies
Atollsupportsthefollowingradiotechnologies:GSMGPRSEDGE,UMTSHSPA,CDMA20001xRTTEVDO,LTE,TDSCDMA,
WiMAX, and WiFi. It also supports 3GPP MultiRAT (combined GSM, UMTS, and LTE) and 3GPP2 MultiRAT (combined
CDMA2000andLTE).AtollMicrowavesupportsdetaileddesignandanalysisofmicrowavelinknetworks.
1.2 SupportedOperatingSystems
AtollsupportsthefollowingversionsofMicrosoftWindowsoperatingsystems.AtollalsosupportsVMWareESXi4.xand5.1
virtualisationplatforms.
SupportedOperatingSystemsforAtoll32bit
MicrosoftWindowsXPProfessionalSP3(32bitand64bit)
MicrosoftWindowsVistaSP2(32bitand64bit)
MicrosoftWindows7(32bitand64bit)
MicrosoftWindows8ProfessionalandEnterprise(32bitand64bit)
MicrosoftWindowsServer2003
MicrosoftWindowsServer2008(32bitand64bit)
MicrosoftWindowsServer2008R2SP1
SupportedOperatingSystemsforAtoll64bit
MicrosoftWindows7(64bit)
MicrosoftWindows8ProfessionalandEnterprise(64bit)
MicrosoftWindowsServer2008SP2(64bit)
MicrosoftWindowsServer2008R2SP1
Among other Microsoft Windows components, Atoll 64bit uses Microsoft Access
DatabaseEngine64bit.MicrosoftAccessDatabaseEngine64bitisincludedinMicrosoft
Office 64bit, and is also available as a free redistributable Microsoft Windows
componentfromtheForsksupportwebsite.
If the computer on which you wish to install and run Atoll 64bit already has
MicrosoftOfficeinstalled,youmustupgradeittoMicrosoftOffice64bit(version
2010SP1ornewer).
IfyoudonothaveMicrosoftOfficeinstalled,youcandownloadandinstallthe
Microsoft Access Database Engine 64bit redistributable (version 2010 SP1)
neededbyAtoll64bitfromtheForsksupportwebsite.
Note:InstallingMicrosoftOffice64bitortheMicrosoftAccessDatabaseEngine64bit
requiresuninstallingany32bitMicrosoftOfficecomponentsthatmaybeinstalledon
thecomputer.
13
Forsk2014
1.3 SupportedDatabaseManagementSystems
Inamultiuserenvironment,databasesallowseveraluserstosharedatawithouttheriskofdatainconsistency.Inamultiuser
environment,userdocumentsareconnectedtoacentraldatabase,inwhichusersstoretheirworkonacommonproject.
AtollsupportsthefollowingRDBMS:
Oracle10gand11g.Oracleclientversion10.0.2.3orlatershouldbeused.
MicrosoftSQLServer2005and2008
MicrosoftAccess2003andlater
Thephysicallocationofdatabasesvariesaccordingtothetypeofthedatabase.Thefollowingtableshowswherethedatabase
mustbeinstalled:
a.
Database
Server
Clientcomputer
MicrosoftAccess
No
Yesa
MicrosoftSQLserver
Yes
No
Oracle
Yes
Yes(Oracleclient)
ItispossibletoworkwithanAtolldocumentconnectedtoaMicrosoftAccessdatabaseevenifMicrosoftAccessisnot
installedonthecomputer.
1.4 SupportedInstallationConfigurations
Dependingonyourrequirements,Atollcanbeinstalledina:
Standaloneconfiguration:
Atollinstalledoneachindividualusercomputerwithafixedlicencekeypluggedineachcomputer.
Workstationbasedmultiuserconfiguration:
Atoll installed on each individual user computer on a network with a floating licence management server that
allocateslicencetokenstoAtollsessionsrunbyusersontheircomputers.
Serverbasedmultiuserconfiguration:
Atollinstalledonserversconnectedtousercomputersandafloatinglicencemanagementserveronanetwork.The
floatinglicencemanagementserverallocateslicencetokenstoAtollsessionsrunbytheusersontheservers.The
serverscanbeCitrixbased,whereusersrunAtollsessionsontheserversthroughtheCitrixinterface.
1.5 RecommendedHardwareandSoftware
Thissectionprovidesguidelinesfordimensioningclientcomputersandserversonyournetworkforoptimumperformance
withAtoll.Thissectionliststherecommendedhardwareandsoftwarefor:
"UserComputers"onpage 14
"DatabaseServers"onpage 15
"ApplicationServers"onpage 15
"FloatingLicenceServers"onpage 15
"FileServers"onpage 15.
1.5.1 UserComputers
Thefollowingtableliststherequiredandrecommendedhardwareandsoftwareforusercomputers(clients)intendedfor
runningwithAtoll.
a.
Processor
Corei7
RAM
8 GBormore
Storage
512 GBa(preferablySSD)
Operatingsystem
Windows7orWindows8ProfessionalorEnterprise
Dependsonthesizeofthelocallystoredgeographicdataandpathlossmatrices,ifany.
User computers must also have a USB port available for plugging in a fixed licence key, or the nethasp.ini file providing
informationonaccessingfloatinglicenceserver.
IfyouareworkingwithanOracledatabase,youmustinstallOracleclientontheusercomputersaswell.TheOracleclient
version10.0.2.3orlatershouldbeused.
14
AT321_AM_E1
1.5.2 DatabaseServers
ThefollowingtableliststherequiredandrecommendedhardwareandsoftwareforanOracledatabaseserver.Thesame
configurationcanbeconsideredvalidforotherdatabasesystemsaswell.
a.
Processor
XeonE3/E5familyorequivalent
RAM
8 GBormore
Storage
2x146 GB(RAID1)ormorea
Operatingsystem
Oracle:Windows/UNIX/Linux/Solaris
SQLServer:MicrosoftWindows
Connectivity
GigabitEthernetorbetter
RDBMS
Oracle10gor11g
MicrosoftSQLServer2005
Tablespaceofaround100 MBper10000transmitters.
1.5.3 ApplicationServers
ApplicationserversareintendedforinstallingandrunningAtoll,defininguserrights,etc.UserscanworkwithAtollinstalled
ontheseserversthroughthinclientssuchasRemoteDesktoporCitrix.
Thefollowingtableliststherequiredandrecommendedhardwareandsoftwareforapplicationserversintendedforrunning
withAtoll.
Processor
1quadcorefor2to3users
RAM
4 GBperuser(minimum8GB)
Storage
2x146 GB(RAID1)
Connectivity
GigabitEthernetorbetter
Operatingsystem
WindowsServer2008R2SP1
WindowsServer2012
Thinclientconfiguration
RemoteDesktop
CitrixXenApp6.0orlater
Virtualisation
VMWareESXi4.xor5.1
Theminimumbandwidthbetweenapplicationserversandclientcomputersforsatisfactoryperformanceis300 kbpsperuser.
1.5.4 FloatingLicenceServers
Thefloatinglicencemanagementserver:
Mustbeaccessibletoalltheusercomputers/CitrixserversonthenetworkinordertoprovidelicencetokensforAtoll
sessions.
Musthaveasteadyandreliablenetworkconnectionwithusercomputers/Citrixservers.
Must have the HASP licence manager installed and running. For more information, see "Working with Floating
Licences"onpage 31.
Musthavethefloatinglicencekeypluggedin.
Canbeoneoftheapplicationservers.
1.5.5 FileServers
Fileserverscanstoregeographicdata,pathlossmatrices,Atollconfigurationandinitialisationfiles,anduserprojects.The
requiredharddiskspacehastobedeterminedfromthefilesizesofthesedata.
GigabitEthernetisrecommendedforconnectingusercomputers,applicationservers,andfileservers.Networkbandwidthis
requiredfordataexchangebetweenAtollsessionsandfileservers.
Geographicdataandsharedpathlossmatricesshouldbestoredonfileserverssothatthecalculationprocessesaccessing
thesedatadonotaffectAtollsusageandunnecessarilyslowdowntheGUI.
15
Forsk2014
1.6 RecommendedComputerNetworkArchitecture
The following network architecture recommendations are based on benchmark tests carried out on the network of an
averagesizeoperator,witharound40to60Atolllicences.Theresultsshowtherequirementsintermsofnetwork,hardware,
andsoftware.Basedonthesefollowing,youcansetupyournetworkenvironmentforanynumberofusers.
Thebenchmarktestswerebasedonthefollowingscenario:
Numberofendusers:40
EachuserworkingonanAtolldocumentwith:
Totalnumberofsites:
Numberofsitesinthecalculationarea:
Persectorpathlosscalculationradius:
Pathlosscalculationresolution:
1660sites(around5000cells)
300sites(900cells)
20km(i.e.,matricesof40kmx40kmeach)
50m
InordertosimulatetheaverageactivityofAtollusers,eachuserisassumedtocarryouta"RoutineOperation"5timesduring
a threehour working period. The "Routine Operation" consists in modifying parameters for 40 cells in 30 minutes,
recalculatingpathlossmatricesforthese40cells,andcalculatingabestservercoverageprediction.
Althoughabestservercoveragepredictiondoesnotrequirealotofcomputerresourcesforcalculations,itrequiresAtollto
loadallthepathlossmatricesinmemory.Whenthepathlossmatricesarestoredonafileserver,asrecommended,this
operation creates a considerable data transfer activity over the network. The benchmark tests have been based on this
simulateddatatransferactivity.
ComputerNetworkArchitecture
AcentralisednetworkarchitectureisthemostwidelyusednetworkarchitecturebyAtollusers.Thefigurebelowshowsthe
recommendedarchitecturealongwithaperusernetworkbandwidthrequirementbetweennetworkcomponents.
Figure 1.1:RecommendedNetworkArchitectureandBandwidthRequirements
CitrixXenAppisusedtocentralisedataandbalanceuserloadsbetweenservers.Anetworkbasedonsuchanarchitecturewith
CitrixserversmustprovidehighspeedconnectionsbetweentheCitrixserversandthefileservers.
TherequirednumberofCitrixserversdependsonthenumberofusers.Ontheaverage,oneprocessorper2to3usersis
recommended.Thus,therequirednumberofCitrixserversdependsonthenumberofprocessorsandendusers.
ComputerNetworkDimensioning
YoushouldsetupyournetworkaccordingtothenumberofAtollusers,whichisrelatedtothesizeoftheplanningproject.A
countrywideprojectwouldhavelargernetworkdimensionsthanaprojectthatcoversacity.
Link
16
RecommendedBandwidth
From
To
Enduser
Citrixserver
300 kbpsperuser
Citrixserver
Fileserver
30 Mbpsperuserperformingcalculations
Chapter2:InstallingAtollandComponents
AT321_AM_E1
2 InstallingAtollandComponents
ThefollowingsectionsdescribetheinstallationproceduresforAtollanditsfollowingcomponents:
DriverforFixedLicenceKeys
DistributedCalculationServer
AtollManagementConsole
Addinsandmacros
YouneedadministratorrightsforinstallingAtollanditscomponents.
2.1 InstallingAtollUsingtheSetupWizard
ToinstallAtoll:
Ifyouworkwithfixedlicences,youmustunplugthekeybeforetheinstallationandwaitfortheinstallationtofinish
beforepluggingitbackin.
DisableUAC(UserAccountControl)forthefollowingversionsofMicrosoftWindows.IfyouareinstallingAtollon
otherversionsofMicrosoftWindows,proceedtostep 1.
MicrosoftWindowsVista
MicrosoftWindows7
MicrosoftWindows8
MicrosoftWindowsServer2008R2
TodisableUAC:
a. GotoControlPanel >UserAccounts.
b. SelectChangeUserAccountControlsettings.TheUserAccountControlSettingsdialogueappears.
c. ChooseNevernotify.
d. ClickOK.
IfyouareinstallingAtoll64bit,makesurethattheMicrosoftAccessDatabaseEngine64bitisalreadyinstalledonthe
computer.MicrosoftAccessDatabaseEngine64bitisincludedinMicrosoftOffice64bit,andisalsoavailableasafree
redistributableMicrosoftWindowscomponentfromForskssupportwebsite.
IfthecomputeronwhichyouwishtoinstallandrunAtoll64bitalreadyhasMicrosoftOfficeinstalled,youmust
upgradeittoMicrosoftOffice64bit(version2010SP1ornewer).ThiswillautomaticallyinstalltheMicrosoftAccess
DatabaseEngine64bit.
IfyoudonothaveMicrosoftOfficeinstalled,youcandownloadandinstalltheMicrosoftAccessDatabaseEngine64
bitredistributable(version2010SP1)neededbyAtoll64bitfromForskssupportwebsite.
InstallingMicrosoftOffice64bitortheMicrosoftAccessDatabaseEngine64bitrequires
uninstalling any 32bit Microsoft Office components that may be installed on the
computer.
1. RuntheAtollsetup.
Thesetupprogramusesawizardinterface,withastepwisedescriptionoftheinstallation.Youcan:
ClickNexttoproceedtothenextstep,
ClickBacktogobackandmodifypreviouslysetoptions,or
ClickCanceltocanceltheinstallation.
2. ClickNext.TheSelectDestinationLocationdialogueappears.
3. Selectthedestinationfolderfortheinstallation:
IfyouareinstallingAtoll32bit,thedefaultinstallationfolderis:
C:\ProgramFiles\Forsk\Atollinthe32bitversionsofMicrosoftWindows,or
C:\ProgramFiles(x86)\Forsk\Atollinthe64bitversionsofMicrosoftWindows
IfyouareinstallingAtoll64bit,thedefaultinstallationfolderis:
C:\ProgramFiles\Forsk\Atollinthe64bitversionsofMicrosoftWindows
YoucanselectadifferentlocationbyclickingBrowse.
17
Forsk2014
Figure 2.1:SelectDestinationLocationDialogueforAtoll
4. SelecttheCreateasystemrestorepointcheckboxifyouwishtotheAtollsetuptocreateasystemrestorepoint.
5. ClickNext.TheSelectComponentsdialogueappears.
6. Selectthecomponentstoinstall.
Fullinstallation:Atollandallitscomponentswillbeinstalled.
Compactinstallation:OnlyAtollwillbeinstalled.
Custominstallation:Atollandtheselectedcomponentswillbeinstalled.
Figure 2.2:SelectComponentsDialogue
7. ClickNext.
If you selected the Distributed Calculation Server component for installation, the Logon Information dialogue
appears.
Ifyoudidnotselectthiscomponent,theSelectStartMenuFolderdialogueappears.Inwhichcase,proceedtostep 8.
Figure 2.3:SelectComponentsDialogue
a. EntertheDomainname,Username,andPassword.
Thisinformationwillbeusedtorunthedistributedcalculationserviceonthecomputer,andallowotherusersof
thedomaintoaccessthisservice.
b. ClickNext.TheSelectStartMenuFolderdialogueappears
8. SelecttheStartMenufolderforAtoll.
18
AT321_AM_E1
ThedefaultStartMenufolderforAtollisAtoll.YoucanselectadifferentfolderbyclickingBrowse.
Figure 2.4:SelectStartMenuFolderDialogue
9. ClickNext.TheReadytoInstalldialogueappears.
10. Reviewtheinstallationparameters.
Figure 2.5:ReadytoInstallDialogue
11. ClickInstall.Atollanditsselectedcomponentsareinstalledonthecomputer.
IfyouworkwithfixedlicencesandyouinstalledtheDriverforFixedLicenceKeys,restartthecomputer.Restarting
thecomputerisnecessaryforthedrivertowork.
Ifyouworkwithfixedlicences,pluginthefixedlicencekey.
OntheversionsofMicrosoftWindowsthatsupportUAC(disabledbeforetheinstallation),runAtollonceusingan
administratoraccountandwithUACdisabledwhentheinstallationiscomplete.
If the following files do not already exist in the installation folder, empty ones are
createdbythesetup:
[Atollinstallationfolder]\Atoll.ini
[Atollinstallationfolder]\coordsystems\Favourites.cs
[Atollinstallationfolder]\CWMeasurementsImport.ini
[Atollinstallationfolder]\DriveTestDataImport.ini
ThesefilesarenotremovedwhenAtollisuninstalled.
IfyouhaveinstalledAtollonaCitrixserver,youmustpublishittomakeitaccessible
tousers.
TorestrictaccesstotheAtollinstallationfolder,youcanassignread/writeaccessrights
tothisfoldertoadministratorsandreadonlyrightstoendusers.
2.2 InstallingaLanguagePackUsingtheSetupWizard
Youcaninstalladditionallanguagestoviewmenus,dialogues,andotheruserinterfaceitemsinyourpreferredlanguage.In
thecurrentversionofAtoll,onlytheFrenchlanguagepackisavailable.
19
Forsk2014
ToinstalltheAtolllanguagepack:
1. RuntheAtolllanguagesetupforthelanguageofyourchoice.
Thesetupprogramusesawizardinterface,withastepwisedescriptionoftheinstallation.
2. ClickNext.TheSelectDestinationLocationdialogueappearsinthelanguageyouchose.
Figure 2.6:SelectDestinationLocationDialogueforaLanguagePack
3. Selectthedestinationfolderfortheinstallation:
IfyouareinstallingalanguagepackforAtoll32bit,thedefaultinstallationfolderis:
C:\ProgramFiles\Atollinthe32bitversionsofMicrosoftWindows,or
C:\ProgramFiles(x86)\Atollinthe64bitversionsofMicrosoftWindows
IfyouareinstallingalanguagepackforAtoll64bit,thedefaultinstallationfolderis:
C:\ProgramFiles\Atollinthe64bitversionsofMicrosoftWindows
ThenexttimeyoulaunchAtoll,theuserinterfacewillbedisplayedinthelanguagecorrespondingtotheinstalledlanguage
pack.
2.3 InstallingAtollC++DevelopmentKit
ToinstalltheAtollC++developmentkit:
VisualC++mustbeinstalledbeforeinstallingtheAtollC++developmentkit.
Atollshouldbeinstalledfortestingtheaddins.
DisableUAC(UserAccountControl)forthefollowingversionsofMicrosoftWindows.IfyouareinstallingAtollC++
developmentkitonotherversionsofMicrosoftWindows,proceedtostep 1.
MicrosoftWindowsVista
MicrosoftWindows7
MicrosoftWindows8
TodisableUAC:
a. GotoControlPanel >UserAccounts.
b. SelectChangeUserAccountControlsettings.TheUserAccountControlSettingsdialogueappears.
c. ChooseNevernotify.
d. ClickOK.
1. RuntheAtollC++developmentkitsetup.
Thesetupprogramusesawizardinterface,withastepwisedescriptionoftheinstallation.Youcan,
ClickNexttoproceedtothenextstep,
ClickBacktogobackandmodifypreviouslysetoptions,or
ClickCanceltocanceltheinstallation.
2. ClickNext.TheSelectDestinationLocationdialogueappears.
3. Selectthedestinationfolderfortheinstallation.
20
IfyouareinstallingtheAtollC++developmentkitwithAtoll32bit,thedefaultinstallationfolderis:
AT321_AM_E1
C:\ProgramFiles\Forsk\Atollinthe32bitversionsofMicrosoftWindows,or
C:\ProgramFiles(x86)\Forsk\Atollinthe64bitversionsofMicrosoftWindows
IfyouareinstallingtheAtollC++developmentkitwithAtoll64bit,thedefaultinstallationfolderis:
C:\ProgramFiles\Forsk\Atollinthe64bitversionsofMicrosoftWindows
Figure 2.7:SelectDestinationLocationDialogue
4. ClickNext.TheReadytoInstalldialogueappears.
5. Reviewtheinstallationparameters.
Figure 2.8:ReadytoInstallDialogue
6. ClickInstall.AtollC++DevelopmentKitisinstalledonthecomputer.
2.4 SetupCommandLineParameters
YoucanalsoinstallAtollanditscomponentsfromthecommandline.TheAtollsetupprogramacceptsoptionalcommandline
parameters,whichcanbeusefultoadministrators,andtootherprogramscallingthesetupprogram.Forexample,when
automatingtheinstallationthroughbatchfiles.
ThefollowingcommandlineparametersareacceptedbytheAtollsetupprogram.
/SILENT,/VERYSILENT
Instructsthesetuptobesilentorverysilent.Whenthesetupissilentthewizardwindowisnotdisplayedbutthe
installation progress window is. When a setup is very silent the installation progress window is not displayed.
Everything else is normal. So, for example, error messages during installation are displayed, and also the startup
prompt.
Ifthesetupissilentanditrequirestorestartthecomputer,butthe/NORESTARToptionisnotused(seebelow),itwill
displayaRebootnow?messagebox.Ifitisverysilentitwillrebootwithoutasking.
/NOCANCEL
Prevents the user from cancelling the installation by disabling the Cancel button and ignoring clicks on the Close
button.Usefulalongwith/SILENTor/VERYSILENT.
/NORESTART
Instructsthesetupnottorestartthecomputerevenifnecessary.
/SAVEINF="filename"
21
Forsk2014
Instructsthesetuptosaveinstallationsettingstothespecifiedfile.Usequotesifthefilenamecontainsspaces.
/LOADINF="filename"
Instructsthesetuptoloadthesettingsfromthespecifiedfileafterhavingcheckedthecommandline.Thisfilecanbe
preparedusingthe/SAVEINFcommandasexplainedabove.Usequotesifthefilenamecontainsspaces.
/DIR="x:\foldername"
OverridesthedefaultinstallationfolderdisplayedontheSelectDestinationLocationwizardpage.Usequotesifthe
foldernamecontainsspaces.
/GROUP="foldername"
OverridesthedefaultstartmenufoldernamedisplayedontheSelectStartMenuFolderwizardpage.Usequotesif
thefoldernamecontainsspaces.
/LOG="filename"
Causesthesetuptocreatealogfilelistingfileinstallationandactionstakenduringtheinstallationprocess.Thiscan
behelpfulfortroubleshooting.Forexample,ifyoususpectafileisnotbeinginstalledasitshouldbe,thelogfilewill
tellyou if thefilewasactually skippedand why.Usequotesif the filenamecontainsspaces.If the filecannotbe
created,thesetupwillabortwithanerrormessage.
/SVRACCOUNT="domainname\username"
Thedomainnameandusernameforinstallingthedistributedcalculationserver.
/SVRPASSWD=password
Passwordforinstallingthedistributedcalculationserver.
/TYPE=typename
Overridesthedefaultsetuptype.Thesetuptypenamesare:
Fullinstallation:full
Compactinstallation:compact
Custominstallation:custom
Forfullandcompactsetuptypes,the/COMPONENTSparametersareignored.
/COMPONENTS="commaseparatedlistofcomponentnames"
Overrides the default component settings. Using this command line parameter causes the setup to automatically
selectacustominstallationtype.Onlythespecifiedcomponentswillbeselected.Componentnamesare:
Atoll:Atoll
ExporttoGoogleEarthaddin:"Addins\GoogleEarth"
BestSignalExportaddin:"Addins\SignalsExport"
Driverforfixedlicencekeys:RainbowDongle
Distributedcalculationserver:Atoll_Server
AtollManagementConsole:AMC
Example:ToinstallAtoll,thedistributedcalculationserver,andthedriverforfixedlicencekeys:
/COMPONENTS="Atoll,Atoll_Server,RainbowDongle"
2.5 InstallingandUninstallingAddins
AddinsarecompiledDLLfileswhichcanbeplacedinanyfolderandactivatedbyregisteringthemintheWindowsregistry.
Addins developed by Forsk have dedicated setup programs, which place the addins DLLs in appropriate locations and
registerthem.Thesetupproceduresinthesecasesaredescribedintheaddinsdocumentation.
ToinstallanaddinbyregisteringitsDLL:
1. CloseAtoll.
2. RightclicktheDLLfileinWindowsExplorer.Thecontextmenuappears.
3. SelectRegister.TheDLLisregistered.
YoucanalsoregistertheDLLfromthecommandpromptusingregsrv32.exe.Onceanaddinisinstalled,Atollloadsit
inthelistofavailableaddins.ItispossibletoaccessandworkwithaddinsandmacroswhenthereisnoATLfileopen
inAtoll.
22
AT321_AM_E1
InstalledaddinsareautomaticallyloadedbyAtollandappearintheAddinsandMacros
dialogue (Figure 2.9 on page 23). Ifyou wish that acertainaddin not be loaded, and
hencebeunavailableforactivationinthisdialogue,youcandosobyaddinganoptionin
theAtoll.inifile.Formoreinformation,see"Loading,Activating,andSettingAddinsas
Visible"onpage 158.
ToactivateordeactivateaninstalledaddininAtoll:
1. InAtoll,selectTools >AddinsandMacros.TheAddinsandMacrosdialogueappears(seeFigure 2.9onpage 23).
2. Selecttheaddinscheckboxtoactivateit,orclearthecheckboxtodeactivateit.
Figure 2.9:AddinsandMacrosDialogue
AddinsinstalledbytheAtollsetupareuninstalledwhenAtollisuninstalled.Touninstallanyotheraddinbyunregisteringits
DLL:
1. CloseAtoll.
2. RightclicktheDLLfileinWindowsExplorer.Thecontextmenuappears.
3. SelectUnregister.TheDLLisunregistered.
YoucanalsounregistertheDLLfromthecommandpromptusingregsrv32.exe/u.
2.6 InstallingandUninstallingMacros
AtollcanloadandexecutemacroswritteninVBScript.
ToloadamacroinAtoll:
2. ClickAdd.TheOpendialogueappears.
3. Selectthemacrofileyouwishtoload.
4. ClickOpen.TheNewScriptwindowopens.
5. Specifythescriptsettings:
Timeout:Thisisdelayafterwhichanunresponsivemacroisstopped.Todisablethemacrotimeout,setitto0.If
youleavethetimeoutempty,avalueof24daysisused.Thedefaultvalueis60seconds.
UTF8Encoding:SelectthisoptionifthemacrofilecontainsnonASCIIcharacters(forexample:""or"").
ListsofmacrosavailableinAtollcanbestoredinuserconfigurationfiles.Macroslistedintheuserconfigurationfilesare
addedtoAtollwhentheuserconfigurationfilesareloaded.Formoreinformation,referto"ContentsofUserConfiguration
Files"onpage 118.
23
Forsk2014
ToremoveamacrofromAtoll:
2. Inthelistofavailablemacros,selectthemacroyouwishtoremove.
3. ClickDelete.
OthercommandsavailableintheAddinsandMacrosdialogueare:
Edit:Edittheselectedmacrointhedefaulttexteditor.
Run:Executetheselectedmacro.
Icon:Assignanicontotheselectedmacro.IconsassignedtomacrosappearintheMacrostoolbar.
Refresh:Toreloadtheselectedmacrofile.
2.7 AtollCommandLineParameters
Atollsupportsthefollowingoptionalcommandlineparameters:
Atoll.exe [-log "logfilename"] [-Ini "inifilename"] [-Cfg "cfgfilename"]
[-Provider providername -UserId username -Password password
-DataSource server -Project projectaccount]
log"logfilename"
Instructs Atoll to create a log file containing all the messages listed in the Events tab. This can be helpful for
troubleshooting."logfilename"isthefullpathandfilenameofthelogfileinsidequotes.
Ini"inifilename"
InstructsAtolltoloadthespecifiedinitialisationfilewhenrun.Thiscanbeusedtooverridethedefaultloadingofthe
Atoll.inifilelocatedintheAtollinstallationfolder."inifilename"isthefullpathandfilenameoftheinitialisationfile
insidequotes.
Cfg"cfgfilename"
InstructsAtolltoloadthespecifieduserconfigurationfilewhenrun.Thiscanbeusedtooverridethedefaultloading
of theAtoll.cfgfilelocated inthe Atollinstallation folder."cfgfilename"is thefull pathand filenameofthe user
configurationfileinsidequotes.
Providerprovidername
InstructsAtolltousethementionedprovidernametoaccessthedatabaseserver:
Provider
Atollversion
providername
MicrosoftAccess
32bit
64bit
Microsoft.Jet.OLEDB.4.0
Microsoft.ACE.OLEDB.12.0
SQLServer
32/64bit
SQLOLEDB
Oracle(Oracledriver)
32/64bit
OraOLEDB.Oracle
DataSourceserver
InstructsAtolltoaccessthementioneddatabaseserverusingthegivenprovider.
UserIdusername
InstructsAtolltoaccessthementionedOracledatabaseserverusingthementionedusername.
Passwordpassword
InstructsAtolltoaccessthementionedOracledatabaseserverusingthementionedpassword.
Projectprojectaccount
InstructsAtolltoaccessthementionedOracledatabaseserverusingthementionedprojectaccount.
24
ThekeywordsProvider,Password,UserId,DataSource,andProjectarecasesensitive.
AT321_AM_E1
2.8 TroubleshootingandOtherInformation
Readandfollowcarefullytheinstructionsin"InstallingAtollUsingtheSetupWizard"onpage 17forasmoothinstallation.
Ifproblemsoccurandyouareunabletoresolvethemwiththehelpofthefollowinginformation,contactForskscustomer
support.
MicrosoftWindowsUpdates
ItisrecommendedtoinstallnewWindowsupdates.However,itisalsorecommendedtogothroughthedescription
ofeachupdatepatchtoseewhetheritmighthaveanegativeeffectonyoursystemornetwork.Payspecialattention
toupdatesandpatchesrelatedtonetworking.
ItisalsorecommendedtokeeptheWindowsupdatesuninstallfolders,named"$NtUninstall...",undertheWindows
folder,incaseyouhavetouninstallacertainpatch.Someoftheupdatepatchesmightrequireuninstallfoldersof
olderpatchestobeavailablefortheirowninstallation.
Fixedlicencekeys
Fixedlicencekeyscannotbeusedwith"Server"typeoperatingsystems.Therefore,youshouldnotinstallthedriver
forfixedlicencekeyson:
Thecurrentversionofthedriverforfixedlicencekeys(SentinelSuperProdriver)installedwithAtollisthe7.6.3.
IfAtollisunabletoaccessthefixedlicencekey,evenafteracleaninstallation,tryreinstallingtheSentinelSuperPro
drivermanually.Thedriverssetupprogram(SPI763.exe)iscopiedbythesetuptotheSentinelsubfolderintheAtoll
installationfolderifyouselectedtheDriverforFixedLicenceKeyscomponentduringtheinstallation.Youcanalso
downloadthedriverfromhttp://www.safenetinc.com.
Restartthecomputerwhenaskedbythesetup.Restartingthecomputerisnecessaryforthedriverforfixedlicence
keystowork.
Ifyougetaprotectionkeyerrormessage,verifythatthefixedlicencekeyiscorrectlypluggedinandthatthelicence
hasnotexpired.
Incasethefixedorthefloatinglicencekeybecomesunavailable,Atollwillasktheuserscurrentlyaccessingthekey
tosavetheiropendocumentsbeforeAtollcloses.Ifthekeybecomesavailableagain,Atollwilllettheuserscontinue
working.
Donotchangethecomputersdate.
Citrix
IfyouhaveinstalledAtollonaCitrixXenAppserver,youmustpublishittomakeitavailabletotheusers.
Atollversionandbuild
YoucangetinformationaboutAtoll(version,build,typeoflicenceandremainingtimebeforeexpiration,etc.)by
selectingHelp >AboutAtollinthemainmenuinAtoll.
Atollfileversionandtechnology
ATLfilepropertiesstoretheAtollversionandbuildnumberinwhichthefilewaslastsaved,andthetechnologiescontained
inthefile.ToaccesstheATLfileproperties:
1. RightclicktheATLfileintheWindowsExplorer.Thecontextmenuappears.
2. SelectPropertiesfromthecontextmenu.Thefilepropertiesdialogueappears.
3. InWindowsXP,clicktheSummarytabandthentheAdvancedbutton.
InWindowsVista,7and8,clicktheDetailstab.
TheAtollversionandbuildnumberinwhichtheATLfilewaslastsavedarestoredintheRevisionnumberproperty.
ThetechnologiesofthedocumentarelistedintheCategoryproperty.
Supportwebsite
YoucandownloadthelatestversionsofAtollfromtheForskssupportwebsitebylogginginwiththeusernameand
passwordprovidedtoyoubyForsk.
TheAtollUserManualandotherdocumentsareavailableontheinstallationCD.Moredocumentsareavailablefor
downloadontheForskssupportwebsite.
Thesupportwebsitealsooffersyou:
25
Sampleaddins,macros,andscripts
Samplegeographicdata,
Listoffixedissuesintheversionsavailablefordownload,
Listofknownissues,andpossibleworkarounds,
Scheduleforupcomingversions,
Listofholidays.
Forfullcontactdetailsforcustomersupport,seebackcover.
Acknowledgement
AtollusesInnoSetupforinstallation.Formoreinformation,seehttp://www.jrsoftware.org/isinfo.php.
UninstallingAtollanditscomponents
ItisrecommendedtouninstallAtollanditscomponentsthroughtheControlPanel.
TouninstallAtoll:
InWindowsXPorWindowsServer2003:
a. GotoControlPanel >AddorRemovePrograms.
b. IntheInstall/Uninstalltab,selectAtollfromthelistofinstalledprograms.
c. ClicktheRemovebutton.
InWindowsVista,Windows7and8,orWindowsServer2008and2012:
a. GotoControlPanel >ProgramsandFeatures.
b. IntheUninstallorchangeaprogramwindow,rightclickAtoll.Thecontextmenuappears.
c. SelectUninstall.
26
Forsk2014
Chapter3:SettingUpDistributedCalculationServer
AT321_AM_E1
3 SettingUpDistributedCalculationServer
Distributedcalculationenablesyoutodistributethecalculationofpathlossmatricesovermanycomputersinanetwork.The
distributedcalculationserviceisanoptionalservicethatcanbeinstalledatthesametimeasAtoll.Formoreinformationon
installation,see"InstallingAtollandComponents"onpage 17.
Acomputeronwhichthedistributedcalculationserviceisinstalledandrunningiscalledadistributedcalculationserver.This
computer,thedistributedcalculationserver,isvisibletoalltheothercomputersonthenetworkthroughAtoll.Youcanset
upasmanydistributedcalculationserversasrequired.
Thedistributedcalculationservicedoesnothaveauserinterface,andhencehaslowermemoryrequirementsthanAtoll.The
distributed calculation server uses the standard Atoll API to exchange data with the path loss calculator and Atoll. The
distributedcalculationservicesupportsdualprocessorconfigurationsanduptofourthreads.
AnyversionofAtollcanworkwiththedistributedcalculationserviceofthesameorlaterversion.Consequently,anyversion
ofthedistributedcalculationservicecanworkwiththesameorpreviousversionsofAtoll(versionsstillmaintainedbyForsk).
FordistributedcalculationserveroptionsavailablethroughtheAtoll.inifile,see"DistributedCalculationServerOptions"on
page 163.
3.1 SettingUpServers
When installed, the distributed calculation service automatically starts and remains available as long as the computer is
turnedon.Theservicedoesnotrequireanyactiveusersessiononthecomputer,i.e.,theservicekeepsrunningevenwhen
thereisnouserloggedon.Theservicesexecutable(AtollSvr.exe)isinstalledintheAtollinstallationfolder.
The Atoll distributed calculation service is listed as Atoll Server in the Services management console under Control
Panel >AdministrativeTools.
Duringcalculations,thedistributedcalculationserversrequireaccesstogeographicdataforcalculatingthepathlossmatrices.
Thedistributedcalculationservicemustberunwithauseraccountthathassufficientprivilegestoaccesstherequireddata.
Tomodifytheuseraccountthroughwhichthedistributedcalculationserviceisrunonacomputer:
1. Logontothecomputerwithauseraccountwithadministratorrights.
2. GotoControlPanel >AdministrativeTools >Services.
3. Inthelistofservices,rightclicktheAtollServerservice.Thecontextmenuappears.
4. SelectProperties.TheAtollServerPropertiesdialogueappears.
Figure 3.1:AtollServerProperties
5. OntheLogOntab,entertheusernameandpasswordfortheuseraccountthroughwhichyouwishtorunthisservice.
6. ClickOK.
27
Forsk2014
RunningMoreThanOneInstanceoftheService
Bydefault,asingleinstanceofthedistributedcalculationserviceisrun.Youcan,however,runupto9additionaldistributed
calculationservices(atotalof10includingthefirstone)manually.
Tomanuallyrunadditionaldistributedcalculationservices,doubleclicktheAtollSvr.exefilelocatedintheAtollinstallation
folder.Foreachnewinstanceoftheservice,acommandpromptwindowopens.Tostopanadditional,manuallyrunservice,
closethecommandpromptwindowcorrespondingtoit.
Atollcandetectatotalof10instancesofthedistributedcalculationservice.Ifyourun
morethan9additionaldistributedcalculationservices,theywillnotbedetectedbyAtoll
andcancausetheoperatingsystemtostopresponding.
StoppingandStartingtheDistributedCalculationServer
Tostopthedistributedcalculationservice:
2. GotoControlPanel >AdministrativeTools >Services.
3. Inthelistofservices,rightclicktheAtollServerservice,andselectStoporStartfromthecontextmenu.
UninstallingtheDistributedCalculationServer
Touninstallthedistributedcalculationservice:
2. Stopthedistributedcalculationservice:
a. GotoControlPanel >AdministrativeTools >Services.
b. Inthelistofservices,rightclicktheAtollServerservice,andselectStopfromthecontextmenu.
3. Unregistertheservice:
a. SelectStart >Run.TheRundialogueappears.
b. Type "<Atoll Installation Path>\AtollSvr.exe /UnregServer". <Atoll Installation Path> is the path to the Atoll
installationfolder.
c. ClickRun.
Thiswillremovethedistributedcalculationservicefromthecomputer.
3.2 SettingUpAtolltoAccesstheServers
ToactivatedistributedcalculationsinAtoll:
1. SelectTools >DistributedCalculationsfromthemainmenu.TheDistributedCalculationsdialogueappears.
2. SelecttheActivatedistributedcalculationcheckbox.
a. Tousealltheavailabledistributedcalculationservers,clickAll.
b. Touseselecteddistributedcalculationserversonly,clickDetect.
Atoll searches for the available distributed calculation servers on the network. The available distributed
calculationserversarelistedintheeditbox.
c. Removethedistributedcalculationserversthatyoudonotwishtoinclude.
3. ClickOK.Theselecteddistributedcalculationserversarenowavailableforpathlosscalculations.
3.3 DistributedCalculationProcess
Oncedistributedcalculationshavebeensetuponthecalculationserverandontheusersides,thepathlosscalculationsrun
bytheuseraredistributedovertheavailablecalculationservers.Thecalculationprocessisasfollows:
1. Atolluserrunspathlosscalculations.
2. Atollsendstheneedednetworkdatatotheavailablecalculationservers.
3. EitherAtollsendstheneededgeographicdatatothecalculationserversortheserversaccessthegeographicdataon
afileserver.
28
AT321_AM_E1
4. Distributedcalculationserverscalculatethepathlossmatricesonebyone.
Distributed calculation servers that have spare threads start the calculations using these threads. If no thread is
available,therequestisplacedinaqueuetowaitforathreadtobecomeavailable.
5. For each calculated path loss matrix, a confirmation is sent to the Atoll session. Any error or warning messages
generatedarepassedbacktotheAtollsessionanddisplayedintheEventViewer.
If an error occurs on any of the distributed calculation servers, Atoll transfers the calculations back to the local
computer.However,toavoidmemorysaturation,Atollusesonethreadonthelocalcomputerandcalculatesthepath
lossmatricesonebyone.Itdoesnotattemptcreatingmorethanonethread.
6. Inordertoreducetheamountofdataflowinthenetwork,distributedcalculationserverssendtheresultsdirectlyto
thestoragelocation(whichcanalsobeonafileserver,notnecessarilyontheuserscomputerthatrequestedthe
calculations).
7. Atollusercanthenrequestthepathlossmatricesfromthefileserveriftheyareneededforcoveragepredictions.
29
30
Forsk2014
Chapter4:ManagingLicences
AT321_AM_E1
4 ManagingLicences
Atollcanbeusedon:
ComputerswithfixedlicencekeyspluggedintoUSBslotsonthecomputersthemselves,or
ComputersconnectedtoalicenceserverwithafloatinglicencekeypluggedintoaUSBportontheserver.
ThedriverforfixedlicencekeyscanbeinstalledatthesametimeasAtoll.Formoreinformation,see"InstallingAtolland
Components"onpage 17.
ThesoftwareformanagingfloatinglicencekeysmustbeinstalledonaserveraccessibletothecomputersonwhichAtollis
goingtobeused.Formoreinformation,see"WorkingwithFloatingLicences"onpage 31.
ForinformationontheAtolllicencemanagementutility,see"UsingtheAtollLicenceManager"onpage 33.
4.1 WorkingwithFloatingLicences
AfloatinglicencekeycanbeusedwhenusersworkwithAtolloncomputersonanetwork.Inafloatinglicenceenvironment,
licencekeysarenotpluggedintoeachindividualuserscomputer,butasharedlicencekeywithmultipletokensisavailable
tousersthroughaserver.
A floating licence server is a computer, accessible to other computers on a network, on which the floating licence
managementsoftwarehasbeeninstalledandafloatinglicencekeypluggedin.Thefloatinglicenceservercanbeoneofthe
computersonwhichAtollisinstalled.
ThefloatinglicencemanagementsoftwareandthefloatinglicencekeycontrolthenumberofpotentialAtollusers.Afloating
licencesystemhasadefinedmaximumnumberoftokensavailable.ThisisthemaximumnumberofcomputersonwhichAtoll
canberunsimultaneously.EachcomputerthatrunsAtolltakesonetokenfromthefloatinglicencekey,evenifmorethan
oneAtollsessionisrunonthesamecomputer.ThetokenisreleasedandmadeavailableforotheruserswhenalltheAtoll
sessionsonthecomputerareclosed.
Ifacomputerisconnectedtoafloatinglicenceserverandalsohasafixedlicencekeypluggedin,thefixedlicencekeyis
accessedfirst.
Atoll uses a 3rdparty floating licence management system called HASP from Aladdin. The floating licence management
systemincludes:
HASPfloatinglicencekey:Hardwarekeyprogrammedwiththenumbersoftokensavailableforeachmodule.
HASPlicencemanager:InterfacebetweenAtollandthefloatinglicencekey.
HASPdevicedriver:InterfacebetweentheHASPlicencemanagerandfloatinglicencekey.
HASPmonitor:Enablesyoutocheckthenumberofusedandavailabletokens.
nhsrv.inifile:Installedonthefloatinglicenceservertoenablecomputerstousetokens.
nethasp.inifile:Installedonthecomputerstofacilitateaccesstothefloatinglicenceserver.
nhsrv.iniandnethasp.inifilesareusediftheyexist.Defaultsettingsareusedotherwise.
YoucandownloadtheHASPlicencemanager,theHASPdevicedriver,andtheHASP
monitor from http://www3.safenetinc.com/support/hasp/hasp4/enduser.aspx.
Newerversionscanbeavailablefordownloadatthewebsitethanthoseprovidedon
theAtollinstallationdisk.
When downloading setup files from the Aladdin website, remember to download
setupfilesforHASP4,notHASPHL.
Thecorrect(recommended)versionofthedevicedriversetuptodownloadistheone
thatworkswith"HASP4APIv8.xorEnvelope12.x".
HASPhardwarekeyissupportedbyWindows2000ServerandWindowsServer2003
withHASPLicenceManager8.20orabove.
4.1.1 HASPLicenceManagerandDeviceDriver
TheHASPlicencemanagercontrolstheallocationandretrievaloflicencetokensavailableonafloatinglicencekey.Itusesthe
HASPdevicedriverforcommunicatingwiththefloatinglicencekey.
TheHASPlicencemanagercanbeinstalledonacomputerrunningWindows2000orlater.AUSBportmustbeavailableon
theserverforplugginginthefloatinglicencekey.
31
Forsk2014
Donotplugthefloatinglicencekeyintheserverbeforeinstallingthedevicedrivers.
WaitfortheHASPlicencemanagersetuptoindicatewhentopluginthekey.
Ifthefloatinglicenceserverisprotectedbyafirewall,port475mustbeopenwhen
usingtheUDPorTCPprotocols.
Once the HASP licence manager has been installed, the floating licence key must
alwaysremainpluggedin.
In case the fixed or the floating licence key becomes unavailable, Atoll will ask the
userscurrentlyaccessingthekeytosavetheiropendocumentsbeforeAtollcloses.If
thekeybecomesavailableagain,Atollwilllettheuserscontinueworking.
Thefloatinglicencekeycanbecomeunavailableandakeyprotectionerrormessage
appearsinAtollifthelicencemanagementserverisheavilyloaded.Checkifthereis
anyapplicationrunningontheserverthatmightbecausingtheproblem.Ifthisisthe
case,removeanysuchapplicationfrommemory.Ifthisisnotpossible,trychanging
thelatencyassociatedtotheHASPlicencemanagerinaccessingthekey.
InstallationandStartup
TheHASPlicencemanager,theHASPdevicedriver,andthefloatinglicencekeymustbeinstalledontheserver.
ThefollowingoptionsshouldbeselectedwheninstallingtheHASPlicencemanager:
Choose"Service"asthetypeofinstallation.
Thismeansthatthelicencemanagerwillrunasaservice,andwillbeaccessibleevenifthereisnouserloggedon.You
canchoosetoinstallitasanapplication,butinthatcaseyouwillhavetorunthelicencemanagermanuallyeverytime
youlogontotheserverandyouwillhavetostayloggedonforthelicenceservertobeavailabletotheAtollusers.
Acceptautomaticdriverinstallation.
ThiswillinstalltheHASPdevicedriverrequiredbytheHASPlicencemanager.
Oncethedevicedriverissuccessfullyinstalled,pluginthefloatinglicencekey.
Onceinstalled,starttheHASPlicencemanager.
Ifyouselected"Service"asthetypeofinstallation,thelicencemanagerwillstartinservicemode.Aniconwillbe
availableinthetaskbar.Youcanaccessthenetworkcommunicationprotocolsbydoubleclickingthisicon.
TheHASPlicencemanagerwindowdisplaysalistofsupportedprotocolswhichcanbemodifiedthroughtheLoadand
Removemenus.Closingthiswindowdoesnotstopthelicencemanager.Theiconremainsavailableinthetaskbaras
longastheserviceisrunning.
TostoptheHASPlicencemanager:
a. GotoControlPanel >AdministrativeTools >Services.
b. Inthelistofservices,rightclicktheHASPLoaderservice,andselectStopfromthecontextmenu.
Youcanalsocopy(fromtheinstallationCD)orcreatethenhsrv.inifileonthefloatinglicenceserver(intheHASP
licencemanagerinstallationfolder).TheHASPlicencemanagersettingsinthisfilecanbemodifiedaccordingtothe
yourrequirements.Formoreinformationonthecontentsofthenhsrv.inifile,see"nhsrv.iniFile"onpage 32.
TorestrictaccesstotheHASPlicencemanagerinstallationfolder,youcanassignread/
writeaccessrightstothisfoldertoadministratorsandreadonlyrightstoendusers.
HASPMonitor(Optional)
YoucaninstalltheHASPmonitoronthefloatinglicenceserver,orononeorseveralothercomputers,tomonitorthetoken
allocationandretrievalactivity.TheHASPmonitordisplaysthelistofcomputersusingtokensavailableonthefloatinglicence
key.
4.1.2 nhsrv.iniFile
Thenhsrv.inifilecanbeusedtodefinealistofcomputersallowedtorequesttokensfromthefloatinglicenceserver.
FileLocation
Ifused,thenhsrv.inifilemustbelocatedinafolderlistedinthesystempathvariable,suchastheWindowsfolder(usually
C:\Windows).
32
AT321_AM_E1
FileContents
Thefollowingisasampleofthenhsrv.inifilethatshowshowtosetalistofcomputersallowedaccesstothefloatinglicence
server.CompletesyntaxcanbefoundontheHASPinstallationCDorontheAladdinwebsite.
[NHS_SERVER]
;NHS_IP_LIMIT = <IpAddr0>[,<IpAddr1>,<IpAddr2>,...]
;Specifies the IP addresses of computers served by the licence manager
;Example: 10.1.1.1, 10.1.1.*
;For use, remove the semi-colon before NHS_IP_LIMIT
4.1.3 nethasp.iniFile
Thenethasp.inifileenablesAtolltolocatethefloatinglicenceserverquickly.Withoutthenethasp.inifile,findingthefloating
licenceserveronthenetworkcantakealongtime.
FileLocation
Thenethasp.inifileshouldbelocatedintheAtollinstallationfolder(recommended).If,forsomereason,itisnotpossibleto
storethefileintheAtollinstallationfolder,itcanbestoredin(intheorderinwhichitissearchedforbyAtoll):
TheWindowsfolder(usuallyC:\Windows)
Afolderlistedinthesystempathvariable
Anethasp.inifilelocatedintheAtollinstallationfolderhaspriorityoveranynethasp.inifilelocatedintheWindowsfolder,
whichinturnhaspriorityoveranynethasp.inifilelocatedinafolderlistedinthesystempathvariable.
Storingthenethasp.inifileintheWindowsfolderinsteadoftheAtollinstallationfoldercanbeusefulifyouhavemorethan
oneversionofAtollinstalled,andyouwishtoaccessthesamefloatinglicenceserver.Thisavoidsmakingacopyofthefilein
eachAtollinstallationfolder.
FileContents
Thefollowingisasampleofthenethasp.inifilewiththeminimumrequiredinformation.Completesyntaxcanbefoundon
theHASPinstallationCDorontheAladdinwebsite.
[NH_COMMON]
NH_IPX = Disabled
;Use the IPX protocol - Enabled or Disabled
NH_NETBIOS = Disabled
;Use the NETBIOS protocol - Enabled or Disabled
NH_TCPIP = Enabled
;Use the TCP/IP protocol - Enabled or Disabled
[NH_TCPIP]
NH_SERVER_ADDR = 3CT000J
;(a)IP address of the floating licence server
NH_TCPIP_METHOD = UDP
;(b)Send TCP or UDP packets
NH_USE_BROADCAST = Disabled
;Use TCP/IP broadcast - Enabled or Disabled
a.
b.
Itisrecommendedtoentertheservernamewithinthedomain.
Forexample,forservername.domainname.com,enterservernameonly.
Onlyoneservernameissupportedinthenethasp.inifile.
ForHASPLicenceManager8.20andlater,AladdinrecommendsUDPasthedefaultTCP/IPmethod.
RemovetheNH_SESSIONandNH_SEND_RCVentriesfromthenethasp.inifileifthese
exist.
Thesefieldsdefinethetimeoutdelaysdependingtothenetwork.Theycanbeuseful
inslownetworksandshouldbesetonlyifrequired.
4.2 UsingtheAtollLicenceManager
AtollLicenceManagerenablesyoutomonitor,troubleshoot,andupdatelicencekeys.Youmustnotusethelicencemanager
without full instructions and details from Forsk customer support. Modifying parameters in the licence manager without
properinputfromForskcustomersupportcandamageyourfixedorfloatinglicencesandblockaccessofAtolluserstothe
licences.
33
Forsk2014
4.2.1 LicenceManagerInterface
ToopentheAtolllicencemanager:
1. CloseAtoll.
2. GototheAtollinstallationfolder.
3. RunLic.exe.Thelicencemanageropens(seeFigure 4.1onpage 34).
Figure 4.1:AtollLicenceManager
4. UnderAvailablelicences,selectalicencekeyinordertodisplaytheinformationrelatedtoit.
TheClearallbuttonisreservedforForskuseonly.
UnderSelectedkeythefollowinginformationisavailablefortheselectedkey:
Number: Unique key number given by the key provider. This number must be communicated to Forsk, when
requested,forreprogrammingthelicencekey.
Type:Thetypeofkey,FixedlicenceorFloatinglicence.
Reference:UniquefloatinglicencekeyreferenceprovidedbyForsk.ThisnumbermustbecommunicatedtoForsk,
whenrequested,forreprogrammingthelicencekey.Thisreferenceisalsoprintedonthestickeronthekey.
Location(server):Nameofthefloatinglicencemanagementserveronwhichthefloatinglicencekeyisplugged.
UnderModulesandlicences,alltheAtollmodulesavailableontheselectedkeyarelistedalongwiththenumbers
oflicencetokensofeach.
UnderNumberoflicences,theModifybuttonsarereservedforForskuseonly.
UnderDatesanddurations,thefollowingdatesanddurationsareavailable:
34
Licencestart
Licenceend
Durationofvalidity
Timebomb
AT321_AM_E1
ApurchasedAtolllicencecorrespondstoaparticularAtollversion.Thereisnotimelimitonusingthisversion.
However,yearlymaintenancemustbepurchasedinordertoaccessnewerversionswithupdatesandbugfixes.
Whenyoupurchasemaintenance,Forskreprogramsyourlicencekeystoallowaccesstonewversions.
TheTimebombdateistheenddateformaintenance.Whenthetimebombdatepasses,thelicencekeystops
working. You can then choose to either purchase maintenance for the next year, and benefit from the new
featuresandbugfixes,orhavethelicencekeyreprogrammedwithoutmaintenanceforthenextyear,inwhich
caseuserscancontinueworkingwiththeexistingversion.
Atollcaninformyouabouttheapproachingtimebombdate30daysinadvance.Thisalertcanbeconfigured
throughtheAtoll.inifile.
Do not attempt to modify the Time bomb settings on the fixed licence key. Contact
Forskscustomersupport.
Donotchangethecomputersdate.
UnderProfilesignature,thePID(profilesignatureorID)istheencrypteddescriptionoftheuserrightsavailable
onthekey.EachkeyhasauniquePID.
UnderCurrentprofilesummary,alloftheaboveinformationissummarised.
4.2.2 UpdatingLicenceKeys
AtolllicencemanagerenablesadministratorstoupdatelicencekeysbyloadingnewkeyprogrammingdatafromALICfiles
providedbyForsk.Toupdatealicencekey,youmusthavetheALICfilesentbyForsk.
Donotattempttoreprogramalicencekeywithoutfullinformationandsupportfrom
Forskcustomersupport.
Toupdatealicencekey:
1. CloseallAtollsessions.
Atollreadslicenceinformationfromthekeyatthestartofeachsession.Thisinformationiskeptinmemoryaslong
asasessionisrunning.Ifalicencekeyisupdatedwhileasessionisstillrunning,therunningsessionwillnotreadthe
updatedlicenceinformationfromthekeyandwillexpireaccordingtotheoldlicenceinformation.
4. UnderAvailablelicences,selectthekeytoupdate.Ifthekeydoesnotappearintheavailablelicenceslist,checkthat
itispluggedintoyourcomputer.
5. UnderKeyprogramming,clickLoad.TheOpendialogueappears.
6. SelecttheALICfileprovidedbyForsk.
7. ClickSave.Thekeyisupdated.
4.2.3 TestingLicenceKeys
TheAtolllicencemanagerenablesadministratorstotestlicencekeys.
Totestalicencekey:
1. CloseAtoll.
4. UnderAvailablelicences,selectthekeytotest.Ifthekeydoesnotappearintheavailablelicenceslist,checkthatit
ispluggedintoyourcomputer.
5. UnderKeyprogramming,clickTest.TheKeytestdialogueappears.
35
Forsk2014
Figure 4.2:TestKeyDialogue
6. IntheKeytestdialogue,underModules,selectthemodulethatyouwishtotest.
7. ClickTest.Thetestshowswhethertheselectedmoduleisavailableonthekeyornot.
Nevertestamoduleforafuturedate.Ifyouenterafuturedatewhentestingakey,this
canreducethetimeleftforusingthekey.
4.2.4 ReducingtheNumberofModuleTokensinALICFiles
ALICfilesareusedbyForskAlcatelLucenttoprogramfixedorfloatinglicencekeys.ALICfilesconsistofaprefixwhichincludes
eithertheletterA(forfloatinglicencekeys)orR(forfixedlicencekeys)followedbythereferencenumberofthekey.One
ALICfilecorrespondstooneuniquekeywiththesamereferencenumberonitssticker.
OEMclientscancreatenewALICfiles,containingreducednumbersofmoduletokens,fromanexistingALICfile.TheALICfiles
containingreducednumbersofmoduletokenscanthenbeusedforprogrammingfloatinglicencekeysallowingtheuseof
onlytheselectedmodules.
ThefollowingsectionsdescribehowyoucanactivatethisfeatureanduseitforcreatingreducedtokenALICfiles.
4.2.4.1 ActivatingtheOptionintheLicenceManager
ThefeatureisavailablethroughtheLicenceManager(Lic.exe).Toactivatethisfeature,addthefollowinglinesintheAtoll.ini
filebeforerunningLic.exe:
[RestrictAlicModuleCount]
AD384D8F-93EF-481D-B007-8F5B7E0033BC = 1
4.2.4.2 ReducingtheNumberofModuleTokens
Onceyouhaveactivatedthefeature,youcanusethelicencemanagertoreducethenumberofmodulesallowedonanew
ALICfileasfollows:
2. Runthelicencemanager.Formoreinformation,see"UsingtheAtollLicenceManager"onpage 33.
Afixedorfloatinglicencekeymustbepluggedintothecomputeronwhichyouarerunningthelicencemanager.This
keyisrequiredforopeningthelicencemanagerwindow.TheALICfilethatyouwillcreatewillnotbeforthiskey.The
dongleforwhichyouaregoingtocreatethenewALICfilewiththereducednumberoftokensshouldbeblankand
notpluggedintoanycomputer.
3. ClicktheReducingprogrammingfiletokensbutton.TheOpendialogueappears.
4. SelecttheALICfilefromwhichyouwishtocreateanotherALICfilewithareducednumberoftokens.
5. ClickOpen.TheModuleRestrictiondialogueappears.
6. IntheModuleRestrictiondialogue,setthenumberoftokensofeachmodulethatyouwishtoallowinthenewALIC
file.
Youcanonlyreducethenumbersoftokens.ToreducethenumberoftheBasemodules,youmustfirstreducethe
correspondingnumbersofothermodules.
7. ClickGenerate.AnewALICfileisgeneratedwiththenumbersofmoduletokensthatyouselected.Thisfileislocated
inthesamefolderastheoriginalALICfile.
36
AT321_AM_E1
8. Closethelicencemanager.
9. MakeabackupcopyoftheoriginalALICfile.
10. Removethe".restricted"extensionfromthenewALICfilename.
4.2.4.3 ProgrammingaBlankLicenceKeyUsingtheRestrictedALICFile
OnceyouhavegeneratedthenewALICfilewiththereducednumbersofmoduletokens,youcanprogrammeanewblank
licencekeyusingthisfile.
ToprogramthelicencekeywiththenewALICfilewithreducednumbersoftokens:
2. Plugthelicencekeyintothecomputer.
Ifitisafloatinglicencekey,settheADDR_SERVERinthenethasp.inifileequaltothenameofyourcomputer.
Tocheckthatthekeyisavailable:
a. RunLic.exe.
b. UnderAvailablelicences,selecttheblankkey.TheModulesandlicencessectionshouldbeemptyfortheblank
key.
c. CloseLic.exe.
3. DoubleclicktheALICfile.Amessagewillappearindicatingthattheprogrammingwassuccessful.
4. CheckthenewcontentsofthekeywithLic.exe.
Ifthecontentsofthekeyarecorrect,youcansendthekeytoyourcustomer.
ForsksendsanewALICfileeveryyeartoupdatethetimebombandmaintenancedates.Oneyearafterthisfirstprogramming,
afterreceivingtheALICcorrespondingtothekey,thesameprocesshastobecarriedoutusingthenewALICfile,andthe
generatedALICfileshavetobesenttothecustomerstoenablethemtoupdatetheirkeys.
37
38
Forsk2014
Chapter5:ManagingDatabases
AT321_AM_E1
5 ManagingDatabases
In Atoll, you can work with standalone documents, i.e., documents without any backend database, or with documents
connectedtodatabases.Standalonedocumentsaremoreportable,howeverabackenddatabaseisrequiredwhenworking
inamultiuserenvironment.Inmultiuserenvironments,severalusersworkonthesameprojectandacentraldatastorage
isnecessaryforkeepingthedatamodificationsmadebyateamofradioplanningandoptimisationengineers.
Atollenablesyoucreatedatabases,upgradethemtonewerversions,archiveandrefreshdatawithdatabases,manageand
resolvedataconflicts,andcreateandworkwithmultileveldatabases.
Adatabaseservercanstoreoneormoredatabases.Forexample,aGSM,aUMTS,andamicrowavelinksdatabasecanbe
storedonthesamedatabaseserverusingthesameRDBMS(Oracle,forexample).
Inthischapter,thefollowingareexplained:
"AtollDatabaseTemplates"onpage 39
"CustomisingAtollDatabaseStructures"onpage 40
"AtollManagementConsole"onpage 42
"CreatingNewDatabases"onpage 43
"UpgradingExistingDatabases"onpage 45
"WorkingWithaMultilevelDatabases"onpage 49
"SettingDatabaseAccessPrivileges"onpage 53
"ManagingDataModificationsHistory"onpage 54
5.1 AtollDatabaseTemplates
AllthetechnologymodulesavailableinAtoll(GSM,UMTS,LTE,CDMA2000,TDSCDMA,WiMAX,WiFi,andMicrowaveRadio
Links)arebasedondatabasetemplates.ThesetemplatesareusedforcreatingAtolldocumentswiththeappropriatedata
structurerequiredforplanningforanytechnology.Databases(usingRDBMS)canthenbecreatedfromanyAtolldocument.
ThesedatabasesarehencealsobasedonthedatastructuredefinedbytheAtolldatabasetemplates.
Ineachnewmajorrelease,databasetemplatesundergomodificationsrequiredtosupportnewfeatures.Thesemodifications
areappliedtoexistingAtolldocumentsanddatabasesbyAtollandtheAtollManagementConsole,respectively.Itisalso
possible to upgrade an existing database manually, but due to the complex nature of the upgrade process, it is highly
recommendedtousetheAtollManagementConsoleforupgradingexistingdatabases.
EachdatabasetemplateisanMSAccessMDBfilelocatedinthetemplatesfolderintheAtollinstallationfolder.Forthelistof
tablesandfields,andtheirrelationships,ineachdatabasetemplate,seethesechaptersintheDataStructureReferenceGuide:
Chapter1:"GSMGPRSEDGEDataStructure"
Chapter2:"UMTSHSPADataStructure"
Chapter3:"CDMA2000DataStructure"
Chapter4:"LTEDataStructure"
Chapter5:"3GPPMultiRATDataStructure"
Chapter6:"3GPP2MultiRATDataStructure"
Chapter7:"TDSCDMADataStructure"
Chapter8:"WiMAXandWiFiDataStructure"
Chapter9:"MicrowaveLinksDataStructure"
DatabasetemplatefilesmustnotbemodifiedwithoutconsultingForskcustomersupport.
The relationshipsin thedatabase schema figures are represented by arrows. These

unidirectionalarrowsshouldbereadas:
= n or
1
Inthetables,primarykeysarelistedinboldanditaliccharacters.
Inthedatabaseschemafigures,primarykeysareinboldandunderlinedcharacters,
andrequiredfieldsareinboldcharacters.
ThefollowingtableliststhetypesoffieldsusedinAtolldatabasetemplates,theirsizes,andtheequivalentfieldtypesand
sizesindifferentRDBMS:
39
Forsk2014
Atoll
OracleEquivalent
MicrosoftSQLServerEquivalent
FieldType
Length
FieldType
Length
FieldType
Length
Microsoft
Access
Equivalent
Float
FLOAT
32
real
Single
Double
FLOAT
64
float
Double
Integer
NUMBER
11
int
LongInteger
Short
NUMBER
tinyint
Integer
Boolean
NUMBER
bit
Yes/No
Text
Variable
VARCHAR2
Variable1
varchar
Variable1
Text1
Memo
Variable
VARCHAR2
2000
varchar
4000
Memo
image
16
OLEObject
Binary
Variable
CLOB
>2000
BLOB3
Variable
1.Lengthsforthesefieldsarespecifiedinparenthesesinthedatabasestructuretables.
2.CLOB:Characterlargeobject
3.BLOB:Binarylargeobject
IfyouexportthecontentsofanAtolldocument,alreadyconnectedtoadatabase,to
anotherRDBMS(forexample,ifyouexportadocumentconnectedtoanOracledatabase
to SQL Server), some field types will be converted according to the above table. This
conversiondoesnothaveanyimpactonthedocumentinAtoll.
For more information on the Atoll Management Console and upgrading databases, see "Atoll Management Console" on
page 42and"UpgradingExistingDatabases"onpage 45,respectively.
5.2 CustomisingAtollDatabaseStructures
Atolldatabasestructurescanbecustomisedby:
Addingcustomfieldstodatatables,
Settinguserdefineddefaultvaluesforfields,and
Settinguserdefinedchoicelistsfortextfields.
Custom fields, as well as userdefined default values and choice lists for standard and custom fields, are stored in the
CustomFieldstable.
AddingCustomFieldstoDataTables
Customfieldscanbeaddedtodatatablesatdifferentstageskeepinginmindthat:
Custom fields added directly to the Atoll database templates (MDB files), using Microsoft Access 2003, will be
available in all new Atoll documents created from that template. A new database created by exporting such a
documentwillalsocontainthesecustomfields.
CustomfieldsaddedtoanAtolldocumentthroughtheAtolluserinterfacewillnotbeautomaticallyaddedtothe
correspondingAtolldatabasetemplate.However,anewdatabasecreatedbyexportingsuchadocumentwillcontain
thesecustomfields.FormoreinformationonaddingcustomfieldstoAtolldocumentsthroughtheuserinterface,see
theUserManual.
CustomfieldsaddedtoanAtolldatabasewillbeavailableinallnewAtolldocumentscreatedfromthatdatabase.
Toaddacustomfieldtoadatatable:
1. Addthecustomfieldtothedefinitionofthedatatablebydefiningitsname,type,andsize.
2. AddacorrespondingrecordintheCustomFieldstableandentervaluesforeachofthefollowingfields:
Field
UserInterface
Caption
TABLE_NAME
40
Description
Databasenameofthedatatablethatcontainsthefield
COLUMN_NAME
Name
Databasenameofthefield
DEFAULT_VALUE
Defaultvalue
Userdefineddefaultvalue(optional)
CHOICE_LIST
Choicelist
Userdefinedchoicelistfortextfields(optional)
AT321_AM_E1
Field
UserInterface
Caption
Description
CAPTION
Legend
Captionofthefieldasitwillappearintheuserinterface(optionalbut
recommended)
GROUP_NAME
Group
Semicolonseparatedlistofthenamesofgroupstowhichthefieldbelongs
(optional)
CHOICE_TYPE
Restricted
1:Customfieldonlyacceptsvalueslistedinthechoicelist
0:Customfieldacceptsvaluesotherthatthoselistedinthechoicelist
DISPLAY_TYPE
Readonly
1:Customfieldisreadonlyintheuserinterface
0:Customfieldismodifiableintheuserinterface
Customfieldsareforinformationonlyandarenottakenintoaccountinanycalculation.
You can find these fields on the Other Properties tab of an object types Properties
dialogue.
SettingUserdefinedDefaultValuesforFields
YoucansetyourowndefaultvaluesforstandardaswellascustomfieldsusingtheCustomFieldstable.Userdefineddefault
valuesenteredintheCustomFieldstablehaveprecedenceoverthepredefineddefaultvalues.
Toenterauserdefineddefaultvalueforanyfield,addanewrecordintheCustomFieldstableandentervaluesforeachof
thefollowingfields:
Field
UserInterface
Caption
TABLE_NAME
Description
Databasenameofthedatatablethatcontainsthefield
COLUMN_NAME
Name
Databasenameofthefield
DEFAULT_VALUE
Defaultvalue
Userdefineddefaultvalue
For floating point default values, make sure that all the users have the same decimal
symbol.
SettingUserdefinedChoiceListsforTextFields
YoucansetyourownchoicelistsforstandardaswellascustomtextfieldsusingtheCustomFieldstable.Userdefinedchoice
listsenteredintheCustomFieldstablehaveprecedenceoverthepredefinedchoicelists.
Toenterauserdefinedchoicelistforanytextfield,addanewrecordintheCustomFieldstableandentervaluesforeachof
thefollowingfields:
Field
UserInterface
Caption
TABLE_NAME
Description
Databasenameofthedatatablethatcontainsthetextfield
COLUMN_NAME
Name
Databasenameofthetextfield
CHOICE_LIST
Choicelist
Choicelistitems,oneperline
Forexample,youcanreplacethedefaultchoicelistavailablefortheSUPPORT_INFOfieldintheSitestablewithadifferent
listofoptionscorrespondingtothedifferenttypesoftowersandpylonsthatmayexistinyournetwork.
You can enter one of the choice list items in theDEFAULT_VALUEinorder to set a
defaultvalueforthetextfield.
Forcustomtextfields,youcansettheCHOICE_TYPEto1ifyouwantthecustomtext
field to only accept values listed in the choice list. By default, CHOICE_TYPE is
consideredtobe0meaningthatusersareallowedtoentervaluesotherthanthose
definedinthechoicelist.
41
Forsk2014
5.3 AtollManagementConsole
TheAtollManagementConsoleprovidesthedatabaseadministratorthepossibilityofgloballymanagingthedatabasewith
theeasytousestepbystepprocedureswhichusewizardinterfaces.TheAtollManagementConsoleletsyou:
Createdatabases(see"CreatingNewDatabases"onpage 43)
Upgradedatabasestructuresfromonemajorversiontothenext(see"UpgradingExistingDatabases"onpage 45)
Workwithmultileveldatabases(see"WorkingWithaMultilevelDatabases"onpage 49)
Managedatamodificationshistoryindatabases(see"ManagingDataModificationsHistory"onpage 54)
Manageuseraccountsandaccessrights(see"ManagingUserAccountsandAccessRightsinOracle"onpage 65)
TheAtollManagementConsolesupports:
Oracle
MicrosoftSQLServer
TheAtollManagementConsolecanbeinstalledwithAtoll.Formoreinformation,see"InstallingAtollandComponents"on
page 17.YoucanruntheAtollManagementConsolefromtheWindowsStartmenuprogramgrouporbydoubleclicking
AMC.msc in the management subfolder of the Atoll installation folder. The Atoll Management Console runs using the
MicrosoftManagementConsoleenvironment.
WhentheAtollManagementConsoleisrunforthefirsttime,youmustregisteryourdatabaseserverinordertohavethe
databasesinstalledontheservertobeavailableintheAtollManagementConsole.
Toregisteradatabaseserver:
1. IntheAtollManagementConsolewindow,intheleftpane,rightclicktheDatabaseitemundertheAdministration
Atoll.Thecontextmenuappears.
2. SelectRegisteraNewServer.TheDataLinkPropertiesdialogueappears.
3. ClicktheProvidertab.OntheProvidertab,selecttheproviderforyourdatabaseserverdependingonwhetheritis
OracleorSQLServer.
Figure 5.1:DataLinkPropertiesdialogueProviderTab
4. ClickNext.OntheConnectiontab,entertheservername,andtheusernameandpasswordrequiredtoaccessthe
databaseserver.
YoucanchecktoseeiftheenteredinformationiscorrectbyclickingtheTestConnectionbutton.
5. ClickOK.TheselecteddatabaseserverisregisteredandavailableintheAtollManagementConsole(seeFigure 5.2
onpage 42).YounowhaveaccesstothefeaturesofferedbytheAtollManagementConsole.
Figure 5.2:AtollManagementConsole
42
AT321_AM_E1
The tree in the left pane lists the registered database servers. Registered database servers can be connected (
disconnected( ).
) or
Therightpaneliststhedatabasesavailableontheconnecteddatabaseservercurrentlyselectedintheleftpane.Thecurrent
usercanbetheownerofoneofthelisteddatabases.Theusernameoftheownerofadatabaseappearsinparenthesesin
thetitlebar.OneOracleusercancreateandownonedatabase.Foreachnewdatabase,youmustcreateanewuserowner
ofthedatabase.
ThefollowingdetailsareavailablefordatabasescreatedorupgradedusingtheAtollManagementConsole:
WhetherthedatabasecorrespondstothecurrentAtollversion(
thecurrentversion.
Thetypeofthedatabase:masterorproject.
)orapreviousversion(
),notyetupgradedto
Amasterdatabasecanhaveoneormoreprojectdatabasescreatedfromandconnectedtoit.Formoreinformation
onmasterandprojectdatabases,see"WorkingWithaMultilevelDatabases"onpage 49.
Thetechnologyofthenetworkmodelledbythedatabase.
Thepathofthesharedpathlossfolder.
Toviewdetailsofadatabase:
1. Intherightpane,rightclickthedatabaseinthelist.Thecontextmenuappears.
2. SelectProperties.ThedatabasePropertiesdialogueappears.
3. ThePropertiesdialoguecontainstwotabs:
Generaltab:TheGeneraltabdisplaystheName,Description,Owner,Type,andVersionofthedatabase.
Statisticstab:TheStatisticstabdisplaysthenumberofrecordsineachtableofthedatabase.
5.4 CreatingNewDatabases
NewdatabasescanbecreatedusingtheAtollManagementConsoleorbydirectlyexportingadocumenttoadatabasefrom
Atoll.Inthissection,thefollowingareexplained:
"CreatingaNewDatabaseUsingtheAtollManagementConsole"onpage 43
"CreatingaNewDatabaseUsingAtoll"onpage 45
5.4.1 CreatingaNewDatabaseUsingtheAtollManagement
Console
YoucancreatenewdatabasesusingtheAtollManagementConsole.
Youmusthaveadministratorrightstothedatabaseandtotheserverforcreatingnew
databases.
Tocreateanewdatabase:
1. IntheAtollManagementConsolewindow,intheleftpane,rightclickthedatabaseserveronwhichyouwantto
createanewdatabase.Thecontextmenuappears.
2. SelectNew >Database.TheNewDatabaseWizarddialogueappears.
Figure 5.3:NewDatabaseWizard
43
Forsk2014
Figure 5.3:NewDatabaseWizard
3. ClickNext.TheSpecifythedatabaseownerpageappears.
4. SelectUsethecurrentconnectionifyouwanttocreateanewdatabaseusingthecurrentuser,orselectCreateanew
userandenteraNameandPasswordtocreateanewuserthatwillbeownerofthenewdatabase.
If your password must contain special characters, for example, !, ?, etc., type the
passwordinsidedoublequotationmarks:"mypassword!"insteadofmypassword!
5. ClickNext.TheNamethedatabaseandspecifyanetworktypepageappears.
6. EnteraNameforthenewdatabaseandselecttheNetworktype.TheNetworktypecanbeoneofthedatabase
templatesinstalledwithAtoll.
AtollandtheAtollManagementConsolemusthavethesameversion.Thismeansthat
theAtollManagementConsolecancreatedatabasesbasedonthedatabasetemplates
installedwithAtollofthesameversion.
7. ClickNext.TheSpecifyunitsandcoordinatesystemspageappears.
8. SelectaTransmissionpowerunitandaReceptionthresholdunit.
9. UnderCoordinatesystems,selectaCartographicprojectionsystemandtheSystemtobeusedinthedatabase.
10. ClickNext.TheReadytocreatedatabasepageappears.Thispageprovidesasummaryoftheselectedparameters.
11. ClickExecute.TheAtollManagementConsolecreatesthenewdatabasewiththedefinedparametersontheselected
databaseserver.
AdatabasecreatedusingtheAtollManagementConsolecontainsanATOLL_ADMINtablewiththefollowingstructure:
44
Field
Type
Description
NAME
Text(50)
Thenameofthedatabase
DESCRIPTION
Text
(255)
Descriptionofthedatabase
ATOLL_VERSION
Text(10)
ThecurrentversionofAtoll
ATOLL_BUILD
Integer
CurrentbuildofAtoll
ATOLL_DBTYPE
Text(10)
TypeofAtolldatabase(i.e.,MasterorProject)
AT321_AM_E1
Field
Type
Description
ATOLL_TEMPLATE
Text(50)
Atolldatabasetemplateusedtocreatethedatabase
DBSCHEMA
Memo
Animageoftheschemaoftheoriginaldatabase
Amongotheruses,theATOLL_ADMINtableisusedtospeedupthedatabaseupgradetothenextversion.Thistablestores
thedatarequiredbytheAtollManagementConsolefordatabaseupgrade.
DatabasescreatedwithAtoll,insteadoftheAtollManagementConsole,anddatabasesthathaveneverbeenupgradedusing
the Atoll Management Console contain a smaller ATOLL_ADMIN table, with just the NAME, ATOLL_VERSION, and
ATOLL_BUILDfields.UpgradingsuchdatabasesusingtheAtollManagementConsolecantakealongtimebecausetheAtoll
ManagementConsolemustsearchforthedatarequiredfortheupgradeinthewholedatabase.
Formoreinformationonupgradingdatabases,see"UpgradingExistingDatabases"onpage 45.
AllthetablesinadatabasecreatedusingtheAtollManagementConsole(excepttheCOORDSYSandUNITStables)containa
nonmodifiable,integerDB_RECORD_IDfield.ThisfieldisusedtostoretheIDofeveryrecordinthetable.Itisnotaddedto
MicrosoftAccessdatabases.
5.4.2 CreatingaNewDatabaseUsingAtoll
YoucancreatenewdatabasesinallsupportedRDBMSusingAtoll.
Tocreateanewdatabase:
1. RunAtoll.
2. CreateanewAtolldocumentoropenanexistingone.Thenewdatabasewillbecreatedfromthisdocument.
3. SelectDocument >Database >Export.TheExporttoaDatabasedialogueappears.
4. IntheExporttoaDatabasedialogue,selectthedatabasetypeintheSaveastypelist.
BysettinganoptionintheAtoll.inifile,youcaninstructAtolltoalwaysuseadefined
databasetype(MSAccess,SQLServer,orOracle).Inthiscase,theExporttoaDatabase
dialoguewillbeskippedandthedatabasespecificauthenticationdialoguewillappear
immediately.Formoreinformation,see"SettingtheTypeofDatabaseBeingUsed"on
page 167.
5. Dependingontheselecteddatabasetype,entertheusernameandpasswordofthedatabaseowner.
6. ClickSave.Atollaskswhetheryouwanttoconnectthedocumenttothenewdatabase.
7. ClickYesorNo.Atollcreatesanewdatabasebasedonthedocument.
AdatabasecreatedusingAtollcontainsanATOLL_ADMINtablewiththefollowingstructure:
Field
Type
Description
NAME
Text(50)
Thenameofthedatabase
ATOLL_VERSION
Text(10)
ThecurrentversionofAtoll
ATOLL_BUILD
Integer
CurrentbuildofAtoll
Before creating the database, make sure that you have defined the coordinate
systemsandunitsinthesourcedocument.
Beforecreatingthedatabase,makesurethatyouhaveaddedanyrequiredcustom
fields.Customfieldsofthesourcedocumentarecreatedinthenewdatabase.
If you want to add a custom field to the data structure after you have created the
database, you will have to add it directly in the database and not through Atoll.
Customfieldsaddedtoadatabaseareavailabletousersconnectedtothedatabase
whentheycreateanewAtolldocumentfromthedatabaseorrefreshanexistingone.
5.5 UpgradingExistingDatabases
Ineachnewmajorrelease,datastructurechangesmustbemadeinthedatabaseinordertosupportthenewfeaturesadded
in the version. The data structures of standalone Atoll documents, i.e., documents not connected to any database are
upgradedwhentheyareopenedinthenewAtollversion.YoucanupgradedatabasesusingtheAtollManagementConsole.
45
Forsk2014
DonotskipamajorversionofAtoll.Forexample,ifyouarecurrentlyusingAtoll2.8.x,
youshouldfirstupgradethedatabasetoAtoll3.1.xbeforeupgradingtoAtoll3.2.x.
Upgradingyourdatabasewillbesimplerifyoudonotskipamajorversion.Ifyouskip
or have skipped an intermediate major version, you must upgrade your database
twiceinordertomakeitcompatiblewiththenewversion.
Ifyouareupgradingadatabasewhichwasneithercreatednoralreadyupgraded(at
leastonce)usingtheAtollManagementConsole,see"UpgradingDatabasesforthe
FirstTime"onpage 47first.
The Microwave Radio Links template now supports Radio Series. Similar microwave
radios belong to the same radio series. In order to organise the microwave radios
(microwaveequipment)inradioseriesbeforethedatabaseupgrade:
1. In Atoll 2.8.x, add a custom field named FAMILY of type Text (50) to the
MWEquipmentstable.
2. Entertheradioseriesnamesinthisfieldforeachradio,i.e.,grouptheradiosof
thesameseriesunderthesameradioseriesnameintheFAMILYfield.
Withoutthismanualorganisationofthemicrowaveradiosintoradioseries,thedatabase
upgradewillcreateoneradioseriesforeachmicrowaveradio.
ToupgradeadatabaseusingtheAtollManagementConsole:
1. IntheAtollManagementConsolewindow,intherightpane,rightclickthedatabasethatyouwanttoupgrade.The
contextmenuappears.
2. SelectUpgradeDatabase.TheDatabaseUpdateWizarddialogueappears.
TheDatabaseUpgradeWizarddisplaysthecurrentdatabaseversionandtheversiontowhichthedatabasewillbe
upgraded.
3. ClickNext.TheNamethedatabasepageappears.
4. EnteraNameanddescriptionforthedatabase.
5. ClickNext.
The Database Upgrade Wizard reads the database to determine the Atoll database template using which it was
created.Ifthereismorethanonetemplatecorrespondingtothenetwork,selectthetemplatetobeusedforthe
upgradeandclickNext.
TheAtollManagementConsoleupgradesthedatabase.
If some of the tables in a database have been replaced by views, the Database
UpgradeWizardaskstoselecttheviewstoupgrade.Selecttheviewsthatyouwant
theAtollManagementConsoletoupgradeandclickExecute.
If,forexample,thedefinitionofaviewisgivenbythecondition:
SelectField1,Field2fromTable1where(Condition1);
ThewizardfirstupgradestheschemaofTable1andthenupgradesthedefinitionof
theview.Theupgradeddefinitionwilltakethenewlyaddedfieldsintoaccount.
Whenyouupgradea3GPPMultiRATdatabase,theAtollManagementConsoleadds
anymissingtablestothedatabase.Forexample,adatabasecreatedbyexportinga
3GPP MultiRAT document containing only GSM contains only GSM tables. When
upgraded,theAtollManagementConsolewilladdtheUMTSandLTEtablestothe
databaseaswell.
ObsoletefieldsinthedatastructureareautomaticallydeletedfromthedatabasebytheAtollManagementConsoleduring
theupgrade.
IfyouusetheAtollManagementConsoleshistorymanagementtool,youmustrepair
theupgradeddatabaseinordertocontinueusingthistool.Formoreinformation,see
"ManagingDataModificationsHistory"onpage 54.
Oncethedatabasehasbeenupgradedtothenewversion,
1. InstallthenewAtollversionsfortheendusers,and
2. AskalltheenduserstofullyrefreshdataintheirAtolldocumentsfromthedatabase.
46
AT321_AM_E1
WhenusersopentheirexistingdocumentsinthenewAtollversion,theyareaskedwhethertheywanttoupgradethe
documentsdatastructurestothenewversionortodisconnectthedocumentsfromthedatabase.Onselectingthe
upgradeoption,Atollupgradesthedocumentdatastructurestomakethemcompatiblewiththenewversion.
NotesonDocumentDataStructureUpgrade
The data structure of an Atoll document not connected to any database is

automaticallyupgradedtothenewAtollversionwhenthedocumentisopenedand
savedinthenewversion.
Oncesaved,itisnotpossibletoopenthedocumentinanearlierAtollversion.
ThedatastructureofanAtolldocumentconnectedtoadatabasenotyetupgraded
tothenewversioncanbeupgradedby:
EitheropeningthedocumentinthenewAtollversion,disconnectingitfromthe
database,andsavingitinthenewversion,or
Upgrading the database to the new version and then opening and saving the
documentinthenewAtollversion.
Oncedisconnectedfromitsdatabase,itisnotpossibletoreconnectthedocument
toanydatabase.
Obsoletefieldsinthedatastructureofadocumentnotconnectedtoanydatabase
areautomaticallydeletedbyAtollwhenthedocumentissavedinthenewversion.
If the database has been upgraded to the new version but an Atoll document
connected to the database has not yet been upgraded, it is possible to open the
document in the previous Atoll version as readonly. It is also not possible to
interact with the upgraded database (archive, refresh, etc., are not allowed). To
make the document writeaccessible in the previous Atoll version, it must be
disconnectedfromtheupgradeddatabase.
It is possible to upgrade an existing database manually (not recommended) by adding and deleting tables and fields as
requiredbythenewversion.Forinformationonmanuallyupgradingadatabase,see"UpgradingDatabasesManually"on
page 48.
UpgradingDatabasesfortheFirstTime
If you want to upgrade a database which was neither created nor already upgraded (at least once) using the Atoll
ManagementConsole,youmustfirstupgradethedatabasetothesameversionasthecurrentversionofthedatabase.This
isrequiredsothattheAtollManagementconsoleaddstherequiredinformationtothedatabasetomakeitupgradableto
newerversions.
Toupgradethedatabase:
1. BeforeinstallingthenewversionofAtoll,installtheAtollManagementConsole(ifnotalreadyinstalled)compatible
withtheexistingversionofAtoll.
2. Upgrade the database (as described in "Upgrading Existing Databases" on page 45) using the Atoll Management
ConsoletotheexistingversionofAtoll.
TheAtollManagementConsoleaddsadditionalfieldstotheATOLL_ADMINtableandDB_RECORD_IDfieldsinallthe
tables,asdescribedin"CreatingaNewDatabaseUsingtheAtollManagementConsole"onpage 43.OncetheAtoll
ManagementConsolehasperformedthenecessarymodifications,youcanupgradethedatabasetothenewAtoll
version.
3. InstallthenewversionofAtollandtheAtollManagementConsole.
4. Upgradethedatabase(asdescribedin"UpgradingExistingDatabases"onpage 45),usingthenewversionoftheAtoll
ManagementConsole,tothenewversionofAtoll.
WhenanewversionoftheAtollManagementConsoleisinstalled,thesetupoverwritestheWindowsregistrykeythatstores
theinformationabouttheAdmin.dllfile,andtheexistingversionoftheAtollManagementConsolecannolongerbeused.
IfyouhavealreadyinstalledthenewversionoftheAtollManagementConsole,youwillhavetoregistertheoldAdmin.dll
again,upgradethedatabasetotheexistingversion,registerthenewAdmin.dll,andupgradethedatabasetothenewversion
usingthenewAtollManagementConsole.
FortheAtollManagementConsoletobeabletorecogniseobsoleteordeletedfields
fromdatabasetables,itisimperativethattheATOLL_ADMINtableexistinthedatabase.
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,itwillbeabletorecogniseobsoleteordeletedfieldsinthefollowingupgrades.
47
Forsk2014
UpgradingDatabasesManually
Duetothecomplexnatureofthedatabaseupgradeprocess,itishighlyrecommendedtousetheAtollManagementConsole
forupgradingexistingdatabases.Youshouldonlyproceedwithamanualupgradeofyourdatabase,asdescribedbelow,if
andonlyifanautomaticupgradeusingtheAtollManagementConsoleisnotpossible.
The following procedure is not recommended for customised Atoll databases and only suits very simple databases.
Parametersandsettings(triggers,views,userprivileges,customfields,etc.)definedinadvanceddatabaseconfigurationsare
lostfollowingthemanualdatabaseupgrade.
1. InthepreviousversionofAtoll,createanewdocumentfromthedatabase.
2. InthenewversionofAtoll,openthedocumentcreatedinstep 1.Atollupgradesthedocumentdatastructuretomake
itcompatiblewiththenewversion.
3. Using the upgraded document, create a new database as explained in "Creating a New Database Using Atoll" on
page 45.
If you are upgrading your database using a script based on the data structure
modificationslistedintheDataStructureReferenceGuide,youmust:
AddtheATOLL_ADMINtabletothedatabase.Formoreinformationonthistable,
see"CreatingaNewDatabaseUsingtheAtollManagementConsole"onpage 43.
ForLTEdatabases,renamethesmartantennamodelsandequipmentasfollows:
Delete existing smart antenna equipment ("Optimum Beamforming Smart
Antenna")fromtheSmartAntennastable.
Delete existing smart antenna model ("Optimum Beamformer") from the
SmartAntennasModelstable.
Createanewsmartantennaequipment("ConventionalBeamformingSmart
Antenna")intheSmartAntennastable.Setthesmartantennamodelforthis
equipmentto"ConventionalBeamformer."
AddingaTechnologyinaMultiRATDatabase
AmultiRATAtolldocumentcanbebasedononeortworadiotechnologiesoutofamaximumofthree(GSM,UMTS,andLTE).
Providedsuchadocumenthasalreadybeenexportedtoadatabase,youcanaddatechnologytothecorrespondingdatabase
throughtheAtollManagementConsole.
1. StarttheAtollManagementConsole.
2. WhentheAtollManagementConsoleopens,rightclickonDatabaseintheleftpane.Thecontextmenuappears.
3. SelectRegisteraNewServer.TheDataLinkPropertiesdialogueisdisplayed.
4. OntheProvidertab,selectanOLEDBproviderandclickNext.
5. OntheConnectiontab,specifyadatabaseintheSelectorenteradatabasenamefield.
6. ClicktheTestConnectionbutton.Iftheconnectionissuccessful,clickOKtoclosetheDataLinkPropertiesdialogue.
7. Upgradethedatabaseifnecessary,asexplainedin"UpgradingExistingDatabases"onpage 45.
8. Intherightpane,rightclickthedatabaseyouwanttoupgradewithanadditionaltechnologyandselectMultiRAT:
View/AddTechnologies.TheTechnologiesintheMultiRATDatabasedialogueisdisplayed.
Figure 5.4:TechnologiesintheMultiRATDatabase
9. SelectthetechnologyyouwanttoaddandclickOK.
48
AT321_AM_E1
YoucannotdeselectatechnologyalreadypresentinamultiRATdatabase.
Anewrecordisaddedtothenetworkstableforeachtechnologyaddedtothedatabase.
5.6 WorkingWithaMultilevelDatabases
AtollManagementConsoleallowsyoutosetupandworkwithmultileveldatabasesusingOracle.Inthisoptionaldatabase
architecture, the master database is not directly accessible to endusers. Groups of endusers work with their respective
projectdatabaseswhichareinturnconnectedtothemasterdatabase.Theendusersarchivedatatoandrefreshdatafrom
theirrespectiveprojectdatabases,andthedatabaseadministratormanagestheconnectionsanddataexchangebetweenthe
projectdatabasesandthemasterdatabase.
Forexample,youcanhaveacountrywidemasterdatabaseandmorethanoneregionalprojectdatabases.Enduserscanhere
workwiththeirlocalregionsprojectdatabase,andwouldnothavetounnecessarilyloadcountrywidedata.
Figure 5.5:WorkingWithaSingleLevelDatabase
Projectdatabasesareintermediatedatabasescreatedfromacommonmasterdatabase.Aprojectdatabasecontainsthe
originalmasterdatabase,thatremainshiddenfromtheendusers,andancopyofthemasterdatabaseaccessibletotheend
users.Whenausermodifiesarecord,onlyitsaccessiblecopyismodifiedintheprojectdatabase.Theoriginalvalueinthe
master database remains unchanged until the database administrator archives all the modifications from the project
databasestothemasterdatabase.
Figure 5.6:WorkingWithProjectDatabases
Projectdatabasescanbeusedtoimproveperformanceandensuredatasecurityandreliability.Insteadallowingalltheend
userstoworkdirectlywiththemasterdatabase,oneormanyprojectdatabasescanbecreatedwithcopiesoftheentire
masterdatabaseorapartofthemasterdatabasecorrespondingtoagivenphysicallocationorregion.
Creatingandworkingwithprojectdatabasesrestrictsthenumberofuserswhohaveaccesstothemasterdatabase.This
reduces the risk of conflicts in the database as only the database administrator can archive modifications from project
databasestothemasterdatabase.
Forexample,ifacountrywidenetworkdatabaseisaccessibletoallendusers:
49
Forsk2014
Theprobabilityofhumanerrorincreaseswiththenumberofuserswhocanmodifydata.
Theprobabilityofconflictsincreaseswiththenumberofusersaccessingthedatabase.
Theperformanceisreducedbecausetheentirenetworkisloadedeverytimeauseraccessesthedatabase.
Forroutinecitywideplanning,anenduserdoesnotrequiretheentirecountrysdatabasetobeloaded.
Projectdatabasescanbecreatedusingfiltersonsites,thusallowinguserstoworkwithregionaldatabases.Apossiblescenario
isdepictedinthefigurebelow:
Figure 5.7:MultipleProjectDatabasesFromaSingleMasterDatabase
MultileveldatabasescanbesetupusingtheAtollManagementConsole.Inthissection,thefollowingareexplained:
"CreatingProjectDatabases"onpage 50
"ArchivingProjectDatabasestoMasterDatabases"onpage 52
"RefreshingProjectDatabasesfromMasterDatabases"onpage 53
5.6.1 CreatingProjectDatabases
YoucancreateprojectdatabasesusingtheAtollManagementConsole.
Forcreatingaprojectdatabase,youmusthaveenoughrightstobeabletocreatenew
tablesinthemasterdatabaseschema.
Tocreateaprojectdatabasefromanexistingmasterdatabase:
1. IntheAtollManagementConsolewindow,intherightpane,rightclickthemasterdatabasefromwhichyouwantto
createaprojectdatabase.Thecontextmenuappears.
2. SelectCreateaProjectDatabase.TheProjectDatabaseCreationWizarddialogueappears.
3. ClickNext.TheSpecifytheserverandtheowneroftheprojectdatabasepageappears.
4. SelecttheDestinationserverfortheprojectdatabase.
5. UnderOwner,selectCurrentuserifyouwanttocreatethenewprojectdatabaseusingthecurrentuser,orselect
CreateanewuserandenteraUsernameandPasswordtocreateanewuserthatwillbeownerofthenewproject
database.
SomeversionsofOracleletyoucreateanewuserthroughthisdialoguebutthenewuser
is not assigned DBA rights, which makes the new user unable to create the project
database.Therefore,itisrecommendedtocreatethenewuserwithDBArightsdirectly
inthedatabasebeforecreatetheprojectdatabaseusingtheAtollManagementConsole
usingthenewuseraccount.
6. ClickNext.TheNamethedatabasepageappears.
50
AT321_AM_E1
7. EnteraNameandDescriptionforthenewprojectdatabase.
8. ClickNext.TheSpecifythesitestoincludeintheprojectdatabasepageappears.
9. Onthispage,choosefromoneofthefollowingoptions:
Includeallthesitesofthemasterdatabase
Selectthisoptionifyouwanttocreateaprojectdatabasethatcontainsallthedataofthemasterdatabase.
Includeasitelistcontainedinthemasterdatabase
Selectthisoptionifyouwanttocreateaprojectdatabasecontainingthenetworkdatacorrespondingtothesites
includedinasitelistofthemasterdatabase,andselectasitelist.Thisoptionisonlyavailablewhenatleastone
sitelistexistsinthemasterdatabase.
SelectthesitestoincludeusinganSQLcondition
that verify an SQL condition (for example, sites that have a common parameter or flag), and enter the SQL
condition.
Includethesitescontainedwithinapolygoncontainedinafile
thatarelocatedinsideapolygon,andselectthefilecontainingthepolygontouse.
10. ClickNext.TheAtollManagementConsolecreatesthenewprojectdatabasewiththedefinedparametersonthe
selecteddatabaseserver.
TheprojectdatabasewillhavethetypePROJECTlistedintheAtollManagementConsolewindow.
Figure 5.8:NewProjectDatabaseWizard
AprojectdatabasecreatedusingtheAtollManagementConsolecontainsanATOLL_ADMIN_PRJtable,inadditiontothe
ATOLL_ADMINtable,withthefollowingstructure:
Field
Type
Description
NAME
Text(50)
Thenameoftheprojectdatabase
MASTER_CONNECTION
Text
(255)
Connectionparameterstothemasterdatabase
MASTER_DBSCHEMA
Text(50)
Thenameoftheoriginalschemaofthemasterdatabase
Short
Dataextractionmethodusedtoselectthesitestoincludeintheproject
database
SEL_METHOD
51
Forsk2014
Field
Type
Description
SEL_PARAM
Text
(255)
Siteselectionmethodparameters(theSQLcondition,ifany)
SEL_PGON
Memo
Siteselectionpolygon(ifused)
YoucanviewthedetailsstoredintheATOLL_ADMIN_PRJtableintheprojectdatabaseproperties.Toviewtheabovedetails
ofaprojectdatabase:
1. Intherightpane,rightclicktheprojectdatabaseinthelist.Thecontextmenuappears.
2. SelectProperties.ThedatabasePropertiesdialogueappears.
3. ThePropertiesdialoguecontainsthreetabs:
Generaltab:TheGeneraltabdisplaystheName,Description,Owner,Type,andVersionofthedatabase.
ProjectDatabasetab:UnderSourcemasterdatabase,theProjectDatabasetabdisplaystheConnectionsettings
toandtheOwnerofthemasterdatabase.UnderSiteselection,thistabdisplaysthesitefilteringMethodand
Settingsusedforcreatingtheprojectdatabase.
Statisticstab:TheStatisticstabdisplaysthenumberofrecordsineachtableoftheprojectdatabase.
Theprojectdatabasecontainsacopyofalltheoriginaltablesofthemasterdatabase.Thenamesoftheoriginaltablesare
prefixedwith"O_".Forexample,theANTENNAStableofthemasterdatabaseisstoredintheprojectdatabaseunderthe
nameO_ANTENNAS.TheCOORDSYSandUNITSarenotcopiedtotheprojectdatabasebecausetheircontentscannotbe
differentfromthoseofthemasterdatabase.
Allthetablesinaprojectdatabasecontainanonmodifiable,integerO_RECORD_IDfieldandaBooleanO_CHANGEDfield.
TheO_RECORD_IDfieldisusedtolocaterecordsinthemasterdatabase.Modifiedrecordsarearchivedinmasterdatabase
usingtheO_RECORD_IDoftheprojectdatabaseandDB_RECORD_IDofthemasterdatabase.TheO_CHANGEDfieldissetto
TRUEforrecordsmodifiedintheprojectdatabase.
5.6.2 ArchivingProjectDatabasestoMasterDatabases
ChangesmadeintheprojectdatabasescanbearchivedtothemasterdatabaseusingtheAtollManagementConsole.The
Archivedialogueletsyouselectchangesyouwanttoarchive.
Toarchivethechangesfromaprojectdatabasetoitsmasterdatabase:
1. IntheAtollManagementConsolewindow,intherightpane,rightclicktheprojectdatabasefromwhichyouwantto
archivechangestoitsmasterdatabase.Thecontextmenuappears.
2. SelectArchive.Ifpendingchangesexist,theArchivedialogueappears.TheArchivedialogueliststherecordsofthe
projectdatabaseforwhichtheO_CHANGEDfieldisTRUE.
3. IntheArchivedialogue,youcandothefollowing:
SelectasitelistinFilterbysitelisttofilterthependingchangesbyasitelist.
ClickArchiveAlltoarchiveallthechangestothemasterdatabase.
SelectthecheckboxestotheleftofthechangesthatyouwanttoarchiveandclickArchiveSel.toarchiveonlythe
selectedchanges.
ClickUndoAlltooverwriteallthechangesintheprojectdatabasewithdatafromthemasterdatabase.
SelectthecheckboxestotheleftofthechangesthatyouwanttoundoandclickUndoSel.tooverwriteonlythe
selectedchangesintheprojectdatabasewithdatafromthemasterdatabase.
SelecttheCheckconflictscheckboxtoseewhetherconflictsoccurredduringthearchive.
Aconflictoccurswhentheprojectdatabasecontainsadifferentoriginalvalueofafieldthanthecurrentvalueof
the field in the master database. This can occur if the master database has been updated with changes from
anothersourceandtheprojectdatabasehasnotyetbeenrefreshedwithdatafromthemasterdatabase.
52
AT321_AM_E1
Figure 5.9:ArchivingChangesinMasterDatabases
UnderErrors,AtollManagementConsoledisplayserrorsthatoccurredduringarchive.
4. Oncearchiveiscomplete,clickClose.
5.6.3 RefreshingProjectDatabasesfromMasterDatabases
ProjectdatabasescanberefreshedwithdatafromthemasterdatabaseusingtheAtollManagementConsole.
Torefreshaprojectdatabasewithdatafromitsmasterdatabase:
1. IntheAtollManagementConsolewindow,intherightpane,rightclicktheprojectdatabasethatyouwanttorefresh
withdatafromitsmasterdatabase.Thecontextmenuappears.
2. SelectRefresh.Ifpendingchangesexist,theRefreshaProjectDatabasedialogueappears.
3. IntheRefreshaProjectDatabasedialogue,youcan:
SelectRefreshunmodifieddataonlytokeepanychangesintheprojectdatabaseandonlyupdateunmodified
recordsfromthemasterdatabase.Duringtherefresh,theAtollManagementConsolewillreloadrecordsfrom
themasterdatabaseforwhichtheO_CHANGEDfieldisFALSEintheprojectdatabase.
SelectCancelyourchangesandreloadalldatafromthemasterdatabasetooverwritemodifiedandunmodified
recordsintheprojectdatabasewithdatafromthemasterdatabase.
1. ClickOK.Theprojectdatabaseisrefreshedwithdatafromthemasterdatabase.
5.7 SettingDatabaseAccessPrivileges
Youcanassigndifferentlevelsofprivilegestodifferentusersforaccessing(reading/writing)tablesandviewsofadatabase.
YoucangrantuserprivilegesforDatabase,Table,Column,andRowlevelskeepingthefollowinginmind:
DatabaseLevel:
UserstryingtocreateanewAtolldocumentfromadatabaseareprovidedalistofavailabledatabasestoselectfrom.
Thelistcanbelimitedtoafewdatabasesbasedontheuserconnectionproperties(login).
TableLevel:
Forconsistencyreasons,allthetablesavailableinanAtolldatabasemustbereadablebyalltheuserswhohaveaccess
tothedatabase.However,writeaccess(INSERT,DELETE,UPDATE)canbegrantedonalimitednumberoftables.
ColumnLevel:
Similartotablelevel,allthecolumnsofallthetablesinanAtolldatabasemustbereadableandselectablebyallthe
userswhohaveaccesstothedatabase.Differentwritepermissionscanbegrantedforcolumnsofthetables.For
example,customfieldscanbeassignedreadandwritepermissionswithoutrestrictions.
RowLevel:
RowlevelpermissionscanbesetbydefiningcustomviewsonAtolltables.Accesstotheseviewscanbebasedonuser
connection properties (log in), on external table references, or on the geographiclocations of sites (e.g., through
polygons,orwhenusingthespatialfeaturesofdatabases).
53
Forsk2014
AllofthesepermissionscanbesetasregularSELECT,INSERT,UPDATE,andDELETEprivilegesondatabaseobjects.Triggers
canalsobeusedtopreventusersmakingcertainactionsonthedatabase.
Differentpermissionsfordifferentuserscanbegranteddirectlyorthroughdatabaseroles.Databaserolesenableyouto
definepermissiontemplates,whichcanthenbeassignedtoexistingornewusersofthedatabase.
YoucanusetheAtollManagementConsolefordefininguseraccessrightstodatabasetablesandelementsintheAtollGUI.
Formoreinformationonmanaginguseraccessrights,see"ManagingUserAccountsandAccessRightsinOracle"onpage 65.
5.8 ManagingDataModificationsHistory
TheAtollManagementConsoleallowsyoutokeepandmanagethehistoryofmodificationsmadeinthenetworkdataby
differentusers.ThehistorymanagementtoolkeepstrackofallthemodificationsmadeinthefollowingAtolltables:
Technology
TrackedTables
GSMGPRSEDGE
Sites,Transmitters,TRGs,TRXs,Repeaters,SecondaryAntennas,Neighbours,
NeighboursExt
UMTSHSPA
Sites,Transmitters,CDMACells,Repeaters,SecondaryAntennas,Neighbours,
NeighboursExt
LTE
Sites,Transmitters,T4GCells,Repeaters,SecondaryAntennas,Neighbours,
NeighboursExt
3GPPMultiRAT
sites,ltransmitters,utransmitters,gtransmitters,lcells,ucells,gtrgs,gtrxs,
lrepeaters,urepeaters,grepeaters,lsecondaryantennas,usecondaryantennas,
gsecondaryantennas,lneighbours,uneighbours,gneighbours,lneighext,uneighext,
gneighext,guneighbours,ugneighbours,glneighbours,lgneighbours,ulneighbours,
luneighbours
CDMA20001xRTT1xEVDO
Sites,Transmitters,CDMACells,Repeaters,SecondaryAntennas,Neighbours,
NeighboursExt
WiMAX
Sites,Transmitters,WCells,Repeaters,SecondaryAntennas,Neighbours,
NeighboursExt
MicrowaveRadioLinks
Sites,MWLinks,MWHubs,MWPMP,MWMultiHops,MWMultiHopsLinks,
MWRepeaters
Youcan,however,enableordisablehistorymanagementfortableasrequired(see"Enabling/DisablingDataModifications
HistoryManagement"onpage 55formoreinformation).Ifyouwant,youcanalsopurgeolddatamodificationshistory(see
"PurgingOldDataModificationRecords"onpage 56formoreinformation).
ThehistorymanagementtoolisavailableforOracledatabases.Thefollowingsectiondescribeshowtosetupthehistory
managementtoolusingtheAtollManagementConsole.
5.8.1 SettingUpDataModificationsHistoryManagement
Whenyousetuphistorymanagementforanydatabase,theAtollManagementConsoleaddsnewtablestothedatabase
structure.Foreachtrackedtable,itaddsacorrespondinghistorytablethathasthesamenameasthetrackedtablewiththe
suffix "_H". Each history table has the same structure as the corresponding tracked table, but with the following four
additionalfields.ThesefieldsenabletheAtollManagementConsoletostorethemodificationsmadebyuserstoeachtracked
table:
Field
Type
Description
HISTORY_ID
Integer
AuniqueIDofthemodificationhistoryrecord
MODIFIED_BY
Text(50)
Theuserwhomadethemodification
MODIFIED_DATE
Date
Thedatewhenthemodificationwasmade
HISTORY_STATUS
Text(10)
Statusofthemodificationhistoryrecord
Theabovefieldsarealsoaddedtoallthetrackedtablesinordertostoreinformationaboutthelatestmodification.Therefore,
openinganytrackedtable,youcanseewhenarecordwaslastmodified,bywhom,andthetypeofmodification.
Tosetupdatamodificationshistorymanagementforadatabase:
1. IntheAtollManagementConsolewindow,intherightpane,rightclickthedatabaseforwhichyouwanttosetup
datamodificationshistorymanagement.Thecontextmenuappears.
2. SelectManageDataModificationsHistory.TheDataModificationsHistoryManagementdialogueappears.
3. ClickYeswhenaskedwhetheryouwanttomakeyourdatabasecompatiblewiththedatamodificationshistorytool.
54
AT321_AM_E1
TheAtollManagementConsoleupdatesthedatabasestructuretomakeitcompatiblewiththedatamodifications
historytool.Datamodificationshistoryisenabledforthedatabase.
Once finished, it opens the Data Modifications History Management dialogue (see Figure 5.10 on page 56). This
dialoguelistsallthetablesforwhichthedatamodificationshistorymanagementhasbeenenabled,thetotalnumbers
ofrecordsinthesetables,andthestatusofthehistorymanagement.
Allthemodificationsmadeinthetableslistedin"ManagingDataModificationsHistory"onpage 54arestoredinthehistory
tablesaddedtothedatabase.
Ifyouwant,youcandisablethedatamodificationshistorymanagementforanytable.Formoreinformation,see"Enabling/
DisablingDataModificationsHistoryManagement"onpage 55.
5.8.2 Enabling/DisablingDataModificationsHistoryManagement
You can enable or disable data modifications history management for any table. You can enable or disable history
managementforeachindividualtable.Whenhistorymanagementisenabledforatable,theMODIFIED_BY,MODIFIED_DATE,
andHISTORY_STATUSfieldsareupdatedwitheachmodification,andacopyofeachmodificationisstoredinthehistorytable
corresponding to the table. When history management is disabled for a table, the MODIFIED_BY, MODIFIED_DATE, and
HISTORY_STATUS fields are still updated with each modification, but the history of modifications is not stored in the
correspondinghistorytable.
Toenabledatamodificationshistorymanagementforatable:
1. IntheAtollManagementConsolewindow,intherightpane,rightclickthedatabaseforwhichyouwanttoenable
3. In the Data ModificationsHistory Managementdialogue,rightclick the table forwhich you want toenable data
modificationshistorymanagement.Thecontextmenuappears.
4. SelectEnableinthecontextmenu.
Datamodificationshistorymanagementisnowenabledforthistable.TheStatusintheDataModificationsHistory
ManagementdialogueissettoOKforthistable.
Todisabledatamodificationshistorymanagementforatable:
1. IntheAtollManagementConsolewindow,intherightpane,rightclickthedatabaseforwhichyouwanttodisable
3. In the Data ModificationsHistory Managementdialogue,rightclick the table forwhich you want toenable data
modificationshistorymanagement.Thecontextmenuappears.
4. SelectDisableinthecontextmenu.
History management is now disabled for this table. The Status in the Data Modifications History Management
dialogueissettoDeactivatedforthistable.
5.8.3 UpdatingAfterDataStructureUpgrade
Whenyoumodifythestructureofatrackeddatabasetable(forwhichdatamodificationshistorymanagementisenabled),
eitherautomaticallyupgradingyourdatabaseusingtheAtollManagementConsole,ormanuallybyaddingorremovingfields,
orbymodifyingafieldtype,thecorrespondingdatamodificationshistorymanagementtablebecomesinvalidandhastobe
updatedtomatchthenewstructureofthetrackedtable.
TheStatuscolumnoftheDataModificationsHistoryManagementdialogueshowsanerrorforthetrackedtablewhose
historymanagementtabledoesnotmatchitsstructure.
Toupdatethedatamodificationshistorymanagementtables:
1. In the Atoll Management Console window, in the right pane, rightclick the database whose tables you want to
update.Thecontextmenuappears.
3. IntheDataModificationsHistoryManagementdialogue,rightclickthetablethatyouwanttoupdate.Thecontext
menuappears.
4. SelectInstall/Repairinthecontextmenu.
TheAtollManagementConsolerepairsthedatastructureofthehistorymanagementtabletomatchthestructureof
thecorrespondingtrackedtable.
55
Forsk2014
5.8.4 PurgingOldDataModificationRecords
Historymanagementtablesstorethelistsofallthemodificationsmadebyalltheusers.Thesetablescanthereforequickly
becomeverylargeandrequirealotofdiskspace.Youcanpurgeolddatamodificationshistory(records)fromthesetablesin
ordertogaindiskspace.
Inthissection,thefollowingisexplained:
"PurgingOldDataModificationRecordsofaTable"onpage 56
"PurgingOldDataModificationRecordsofaDatabase"onpage 57.
5.8.4.1 PurgingOldDataModificationRecordsofaTable
Topurgeolddatamodificationrecordsfromahistorymanagementtable:
1. IntheAtollManagementConsolewindow,intherightpane,rightclickthedatabaseinwhichyouwanttopurgeold
datamodificationshistory.Thecontextmenuappears.
2. In the context menu, select Manage Data Modifications History. The Data Modifications History Management
dialogueappears(seeFigure 5.10onpage 56).
Figure 5.10:DataModificationsHistoryManagementDialogue
3. IntheDataModificationsHistoryManagementdialogue,rightclickthetableforwhichyouwanttopurgeolddata
modificationshistory.Thecontextmenuappears.
4. Inthecontextmenu,selectPurge.Thetablerecordpurgedialogueappears(seeFigure 5.11onpage 56).
Figure 5.11:TableRecordPurgeDialogue
5. UnderPurgedatamodificationsrecordedbefore,movetheslidertoselectfromwhichdateonwardsyouwantto
keepthedatamodificationhistoryrecords.
Allthedatamodificationhistoryrecordsbeforethisdatewillbedeleted.Numberofrecordsshowsthenumberof
recordsthatwillbeleftafterthepurge.Datasizeshowsthesizeoftherecordsthatwillbeleftafterthepurge.
6. UnderOptions,selecttheKeepcreationanddeletionrecordscheckboxifyouwanttokeeptherecordsrelatedto
creationanddeletion.
7. ClickPurge.Allthehistoryrecordsbeforetheselecteddatearedeletedfromthehistorymanagementtable.
IfyouselectedtheKeepcreationanddeletionrecordscheckbox,creationanddeletionrecordsbeforetheselected
datearenotdeleted.
56
AT321_AM_E1
5.8.4.2 PurgingOldDataModificationRecordsofaDatabase
Topurgeolddatamodificationrecordsfromallthehistorymanagementtablesofadatabase:
1. IntheAtollManagementConsolewindow,intherightpane,rightclickthedatabaseinwhichyouwanttopurgeold
datamodificationshistory.Thecontextmenuappears.
2. In the context menu, select Manage Data Modifications History. The Data Modifications History Management
3. In the Data Modifications History Management dialogue, click the Scheduler button. The database record purge
Figure 5.12:DatabaseRecordPurgeDialogue
4. UnderConditions,selecttherecordstopurge:
None:SelectNoneifyoudonotwanttopurgeanyrecord.
KeeponlyrecordsofNlastmonths:SelectKeeponlyrecordsofNlastmonthsandenterthenumberofmonths
priortowhichrecordsofdatamodificationswillbepurged.
Keepcreationanddeletionrecords:SelecttheKeepcreationanddeletionrecordscheckboxifyouwanttokeep
allthecreationanddeletionrecords,independentoftheaboveoptions.
5. Ifyouwishtopurgerecordsnow,clicktheRunnowbutton.
6. Ifyouwishtoscheduleregularpurges,underScheduling,definethepurgefrequency:
a. Period:Selectthefrequencyofthescheduledregularpurges.
b. Day:Selectthedayoftheweek(MondaytoSunday),month(1to28),oryear(1to365),dependingonthepurge
periodicitydefinedinPeriod,onwhichthescheduledpurgeswillrun.
c. Time:Enterthetime,i.e.,thehour(0to23)andminutes(0to59)atwhichscheduledpurgeswillrun.
Scheduled regular purges will delete all the data modification records according to the criteria defined under
Conditions.
7. SettheOff/OnslidertoOntoturnonthescheduledpurges.
SettingtheOff/OnslidertoOffletsyoususpendthescheduledpurgesandkeeptheschedulesettings.
8. ClicktheUpdatebuttontostorethescheduleparameters.
ThecurrentpurgestatusisshownunderStatus.Statusinformationincludes:
Lastexecution:Timeofexecutionofthelastpurge.
Result:Whetherthelastpurgewassuccessfulornot.
Nextexecution:Timeofexecutionofthenextscheduledpurge.
YoucanclicktheViewlogsunderStatustoviewthehistoryofpastpurges(seeFigure 5.12onpage 57).

9. ClicktheClosebutton.
57
Forsk2014
ScheduledregularpurgesareprogrammedasascheduledjobinOracleusingtheDBMS_SCHEDULER.create_jobfunction.The
followingSQLstringgeneratesscheduledjob:
"BEGIN DBMS_SCHEDULER.create_job ("
"job_name => 'AHMS_%s',"
"job_type => '%s',"
"job_action => '%s',"
"start_date => SYSTIMESTAMP,"
"repeat_interval => '%s',"
"end_date => NULL,"
"enabled => %s,"
"comments => '%s'); END;"
Here:
Parameter
Description
job_name
AHMS_<schema_name>
job_type
PLSQL_BLOCK
job_action
ActualPLSQLcodeforthepurge
start_date
SYSTIMESTAMP
repeat_interval
Frequencyofthescheduledpurge
Forexample,onceamonth,onthe15th,at1:30am:"freq=month;monthday=15;byhour=1;byminute=30"
end_date
NULL
enabled
TRUEorFALSE,basedontheuserinput
comments
Customcharacterstringwithcodesforeasyidentificationoftheschedulertype
5.9 Appendices
ThefirstappendixshowshowtouseSQLforOracledatabasecustomisationandthesecondappendixshowshowtosetup
databasesforcoplanningtakingtheexampleofGSMandUMTSMSAccessdatabases.
5.9.1 Appendix1:AdvancedCustomisation
YoucanuseSQLinordertomanageaccesstoandsharetheSitestable(example1),ortorestricttheconnectiontoasetof
transmittersforsomeusers(example2).Toimplementthefollowingtwoexamples,youmustlogonastheownerofthe
tablesthroughSQLPlus8.
Example1:ManagingSiteSharing
Assumptions:
Connectionstring=AtollDB
GSMProjectaccount=AtollADMINGSM,password=ADMINGSM
UMTSProjectaccount=AtollADMINUMTS,password=ADMINUMTS
CommonProjectaccount=AtollADMIN,password=ADMIN
TosharetheSitestable:
1. CreatetheAtollADMIN.SITEStableandcopyallsitesfromAtollADMINGSM.SITEStoAtollADMIN.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. ReplacetheAtollADMINGSM.SITEStablebyanAtollADMINGSM.SITESview.
SQL > connect AtollADMINGSM/ADMINGSM@AtollDB;
SQL > drop table AtollADMINGSM.SITES;
SQL > grant delete on AtollADMIN.SITES to AtollADMINGSM with grant option;
58
AT321_AM_E1
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. FollowthesameprocedureforUMTS(AtollADMIN.SITESalreadycreated).
SQL > connect AtollADMINUMTS/ADMINUMTS@AtollDB;
SQL > drop table AtollADMINUMTS.SITES;
SQL > grant delete on AtollADMIN.SITES to AtollADMINUMTS with grant option;
SQL > grant insert on AtollADMIN.SITES to AtollADMINUMTS with grant option;
SQL > grant select on AtollADMIN.SITES to AtollADMINUMTS with grant option;
SQL > grant update on AtollADMIN.SITES to AtollADMINUMTS with grant option;
SQL > create view AtollADMINUMTS.SITES as select * from AtollADMIN.SITES;
4. Commit.
SQL > commit;
Example2:ManagingUsersbyPostalCode
Torestrictaccesstotransmittersforsomeusersbypostalcode:
1. AddaPOSTCODEfieldtotheSITEStable.
SQL > alter table SITES add (POSTCODE number);
2. RenametheSITEStabletobeabletohideitbyaview.
SQL > rename SITES to PRIVATE_SITES;
3. CreateaPOSTCODETABLEtabletolinkusersandpostcodes(oneusercanbelinkedtoseveralpostcodes).
SQL > create table POSTCODETABLE (USERNAME varchar2(30), POSTCODE number);
Youcanfillthistableusingthisinstruction.
SQL > insert into POSTCODETABLE values (USER1, 75);
4. CreateaviewownedbythisuserhidingtheactualSITEStablethroughthesecommands.
SQL > create view SITES as
select * from PRIVATE_SITES
where POSTCODE in
(select POSTCODE from POSTCODETABLE where USERNAME =USER)
with check option;
"withcheckoption"isveryimportantasitspecifiesthatinsertandupdateoperationsperformedthroughtheview
mustresultinrowsthattheviewquerycanselect.
5. HidetheTRANSMITTERStable,sothatAtollcanonlyselecttransmitterswhoseassociatedsitesarepresentinthe
SITESview.
SQL > rename TRANSMITTERS to PRIVATE_TRANSMITTERS;
SQL > create view TRANSMITTERS as
select * from PRIVATE_TRANSMITTERS
where SITE_NAME in (select NAME from SITES);
6. Commit.
SQL > commit;
59
Forsk2014
Theerrormessage"ORA01402:viewWITHCHECKOPTIONclauseviolation"appearsif
youtrytoarchivearecordthatdoesnotmatchtheproject.
5.9.2 Appendix2:SettingUpDatabasesforCoplanning
TwocoplanningapproachesarepossibleinAtoll:
CoplanningGSM,UMTS,andLTEusingaunifiedmultitechnologydatastructure,i.e.,workingwitha3GPPMultiRAT
document.
Coplanninganytworadiotechnologies(GSM,UMTS,LTE,CDMA2000,TDSCDMA,andWiMAX),withtwoseparate
datastructures,bylinkingAtolldocuments.
Intermsofdatabase,whilethefirstapproachprovidesanintegratedmultitechnologycoplanningenvironment,thesecond
requiressettingupsharingoftheSitestablebetweenthedatabasesofthetwotechnologiesbeingcoplanned.TheSitestable
mustbesharedbetweenthedatabasesofthetwotechnologiesbeingcoplannedsothatthesiteswheresectorsofboth
technologiesareinstalledarelistedonlyonceinacommonSitestable.Inotherwords,theSitestablesinthedatabasesofthe
twotechnologiesmustbeviewsofacommonSitestable.
ThissectiondescribestablesharingbetweenGSMandUMTS,althoughthesamedescriptioncanbeappliedtoanytworadio
technologymodulesofAtoll
Youcancreateviewstosharetablesthathavethesamestructureinthedatabasesofthetwotechnologiesbeingcoplanned,
i.e.,theSitesandAntennastables.Inthefollowing,weassumethattheSitestablesoftheGSMandUMTSdocumentscontain
thesamedataandthattwousers,namedGSMUserandUMTSUserinthisexample,existinthedatabases.
TosetupasharedSitestableforaGSMUMTScoplanningprojectinOracleorSQLServer:
1. MakebackupsoftheGSMandUMTSdocuments.
2. OpentheGSMdocumentinAtoll.
3. DeleteallthetransmittersfromtheTransmitterstableandallthesitesfromtheSitestable.
4. ExporttheGSMdocumenttothedatabasebyenteringtheusernameandpasswordforGSMUser.
5. LoginasGSMUsertothedatabase.
6. DeletetheSitestable.
7. OpentheUMTSdocumentinAtoll.
8. ExporttheUMTSdocumenttothedatabasebyenteringtheusernameandpasswordforUMTSUser.
9. LoginasUMTSUsertothedatabase.
10. RightclicktheSitestableandselectCreateaViewfromthecontextmenu.TheCreateViewdialogueappears.
a. EnterSitesastheviewname.
b. EnterGSMUserasthenameoftheschemawhichwillcontaintheview.
c. SelectTableasobjecttype.
d. EnterUMTSUserasthenameoftheschemayouwanttouse.
e. SelectSitesastheobjectusedtomodeltheview.
11. ClickCreate.TheviewoftheSitestablefromUMTSUseriscreatedinGSMUser.TheGSMUserSitestableisnowthe
sameasUMTSUserSitestable.
12. SetupuserprivilegesfortheSitesviewinGSMUsertoalloweachusertoImport,Update,Delete,andSelect.
TosetupasharedSitestableforaGSMUMTScoplanningprojectinMicrosoftAccess:
1. MakebackupsoftheGSMandUMTSdocuments.
2. OpentheGSMdocumentinAtoll.
3. DeleteallthetransmittersfromtheTransmitterstableandallthesitesfromtheSitestable.
4. ExporttheGSMdocumenttoaMicrosoftAccessdatabase(GSM.mdb).
5. OpenGSM.mdbinMicrosoftAccess.
6. DeletetheSitestable.
7. OpentheUMTSdocumentinAtoll
8. ExporttheUMTSdocumenttoaMicrosoftAccessdatabase(UMTS.mdb).
9. OpenGSM.mdbinMicrosoftAccess.
60
AT321_AM_E1
10. InMicrosoftAccess2003andearlier,selectFile >GetExternalData >LinkTables.InMicrosoftAccess2007andlater,

selectExternalData >AccessDatabase.
11. InMicrosoftAccess2003andearlier,theLinkdialogueappears.SelectUMTS.mdb.InMicrosoftAccess2007andlater,
theGetExternalDataAccessDatabasedialogueappears,specifyUMTS.mdbasdatasourceandselectLinktodata
sourcebycreatingalinkedtable.
12. ClickOK.TheLinkTablesdialogueappears.
13. SelecttheSitestable.
14. ClickOK.MicrosoftAccesscreatesaSitestableinGSM.mdbwhichislinkedtotheSitestableinUMTS.mdb.Thetables
containthesamedata.
OncethelinkedSitestablehasbeencreatedintheGSMdatabase,youhavetodefinetherelationsofthistablewiththeother
tablesinthedatabase.SeetheDataStructureReferenceGuidefordetailedinformationondatabasetables.
TheUMTSSitestablehasmorefieldsthantheGSMSitestable.Therefore,youshould
replacetheGSMSitestablewiththeUMTSone.
WhenyouupgradeonebyonethedatabasesthatsharetheSitestable,anytriggers
thatyoumighthavesetontheSitestableofthedatabasethatisupgradedfirstmight
beoverwrittenbythetriggerssetontheSitestableofthedatabaseupgradedlast.In
order to avoid the triggers being overwritten, you can rename the triggers on the
Sites table of the database upgraded first (by adding, for example, the database
technologyasprefixtothetriggernames)beforeupgradingtheotherdatabase(s).
EnsuringDatabaseConsistencyBetweenLinkedDocuments
WhenusersworkwithtwoAtolldocumentsanddatabasesatthesametime,itisimportanttohaveaprotectionmechanism
againstdatabaseinconsistencies.Ifauserarchivesthechangesmadeinonedocumentbutforgetstoarchivethechanges
madeintheother,thiscancreateinconsistenciesbetweenthetwonetworks.
Toensuredatabaseconsistency,youcansaveorarchivethelinkeddocumentsatthesametime,i.e.,whenausersavesor
archivesonedocument,Atollautomaticallysavesorarchivestheother.Thiscanbedoneusingamacrotriggeredbythesave
orarchiveoperation.
61
62
Forsk2014
Chapter6:MultiuserEnvironments
AT321_AM_E1
6 MultiuserEnvironments
AmultiuserenvironmentiswheremorethanoneuserworksimultaneouslyonanAtollproject,sharingdataoveranetwork.
Inlarge,structuredmultiuserenvironments,groupsofuserscanworkonspecificpartsofacommon,largescaleproject.For
example,differentusergroupscanworkondifferentregionsofacountrywidenetwork.Inthischapter,thefollowingare
explained:
"SettingUpMultiuserEnvironments"onpage 63
"ComponentsofMultiuserEnvironments"onpage 63
"ManagingUserAccountsandAccessRightsinOracle"onpage 65
6.1 SettingUpMultiuserEnvironments
The general processof setting up a multiuser environment is described below. Each component is described in detail in
"ComponentsofMultiuserEnvironments"onpage 63.
1. CreatethemasterAtolldocumentwiththerequirednetworkdataandgeographicdata.Formoreinformation,see
"MasterAtollDocument"onpage 64and"SharedGeographicData"onpage 64.
2. ExportthemasterAtolldocumenttoanewdatabaseandkeepthedocumentconnectedtothenewdatabase.For
moreinformation,see"MasterDatabase"onpage 64.
3. Create the private path loss matrices folder for the master Atoll document and calculate the private path loss
matrices.Formoreinformation,see"SharedPathLossMatrices"onpage 65.
4. Create user Atoll documents from the master database. For more information, see "User Atoll Documents" on
page 65.
5. IntheuserAtolldocuments,addtherequiredgeographicdataandsetthemasterAtolldocumentsprivatepathloss
matricesfolderasthesharedpathlossmatricesfolderoftheuserdocuments.
TheAtolladministratorshouldregularlyupdatethesharedpathlossmatrices.
As the users work on the network and archive changes in the database, the Atoll
administrator should regularly run data integrity checks on the master Atoll
document after loading modified data from the master database. For more
information,see"Appendix1:CheckingDataIntegrity"onpage 69.
6.2 ComponentsofMultiuserEnvironments
Figure 6.1onpage 63showsthecomponentsofamultiuserenvironment.
Figure 6.1:ComponentsofMultiuserEnvironments
63
Forsk2014
Inthissection,thefollowingareexplained:
"MasterAtollDocument"onpage 64
"MasterDatabase"onpage 64
"SharedGeographicData"onpage 64
"SharedPathLossMatrices"onpage 65
"UserAtollDocuments"onpage 65
6.2.1 MasterAtollDocument
ItisthesourceAtolldocumentthatcontainstheentireprojectsnetworkdata.ItiscreatedandmaintainedbytheAtoll
administrator.Thisdocumentisinitiallyusedtocreatetheradionetworkdatabasewithwhichalltheenduserswork.The
masterAtolldocumentallowstheadministratortogloballymanageallthedatasharedbytheendusers.
The master Atoll document is also used for calculating path loss matrices for the transmitters of the entire network and
keepingthepathlossmatricesuptodatewiththeusermodificationstotheradionetworkdata.Thedocumentalsocontains
therequiredgeographicdataforpathlosscalculations.Geographicdataareusuallylocatedonfileserversandlinkedtothe
document,notembeddedintheATLfile.Theprivatepathlossmatricesofthisdocumentareusedassharedpathlossmatrices
bytheendusers.Thesharedpathlossmatricesfolderisusuallylocatedonafileserveraccessibletoalltheusersonthe
network.
Forexceptionallylargenetworks,youcanalsoworkwithmorethanonemasterAtolldocument(forexample,onemaster
documentperregion).However,themultiuserenvironmentsetupremainsthesame.MasterAtolldocumentsshouldnot
haveredundantradionetworkdata(samesites,forexample),andshouldideallycoverdifferentgeographicalregions.For
moreinformationonregionalisation,see"Appendix2:DatabaseRegionalisation"onpage 70.
IfyouwishtoaddcustomfieldsintheAtolldocument,youshouldfirstaddthefieldin
thedatabase,andthenupdateyourAtolldocumentfromthedatabase.Customfields
addedinanAtolldocumentconnectedtoaMicrosoftAccessdatabaseareautomatically
addedtothedatabase.However,thisisnotthecasewithotherRDBMS,suchasOracle.
6.2.2 MasterDatabase
Themasterdatabasestorestheradionetworkdatasharedbyalltheendusers.Itcanbe createdbyexportingtheradio
networkdatainthemasterAtolldocumenttoadatabasefromAtoll(formoreinformation,see"CreatingaNewDatabase
UsingAtoll"onpage 45).AnemptydatabasecanalsobecreatedusingtheAtollManagementConsole,andpopulatedwith
datalateron(formoreinformation,see"CreatingaNewDatabaseUsingtheAtollManagementConsole"onpage 43).
Onlyradionetworkdataarestoredinthedatabase,i.e.,sites,transmitters,antennas,etc.Parametersrelatedtogeographic
datafiles,theirpaths,folderconfigurations,predictiondefinitions,zones,trafficmaps,measurementscanbestoredinuser
configurationfiles(see"ConfigurationFiles"onpage 117fordetails).
Forlargenetworks,youcansubdividethenetworksmasterdatabaseintoregions.Formoreinformationonregionalisation,
see "Appendix 2:DatabaseRegionalisation" on page 70.For more informationondatabase management, see"Managing
Databases" on page 39. The recommended database server configuration is provided in "Recommended Hardware and
Software"onpage 14.
The same database server can be used to store one or more master databases
corresponding to different technologies. For example, a GSM database and a UMTS
databasecanbestoredonthesamedatabaseserverusingthesameRDBMS(Oracle,for
example).
6.2.3 SharedGeographicData
Geographicdatafilesareusuallystoredonafileserveraccessibletoandsharedbyalltheusersworkingonthesamenetwork.
Userconfigurationfiles(CFGorGEO)areusedtostoretheparametersrelatedtogeographicdata.Formoreinformation,see
"ConfigurationFiles"onpage 117.
Theadministratorcansetupdifferentuserconfigurationfiles(CFG)forseparateusergroups.Userconfigurationfilescanbe
created so that only the geographic data required by a user are loaded. It is possible to load a user configuration file
automaticallywhenrunningAtoll.Userconfigurationfilescanbesharedandexchangedbetweenusersworkingonthesame
project.Formoreinformation,see"AtollCommandLineParameters"onpage 24.
Geographicdatafilesareusuallylargefiles,anditisrecommendedthatthesebestoredexternallyandnotembeddedinAtoll
documents.Therecommendedfileserverconfigurationisprovidedin"RecommendedHardwareandSoftware"onpage 14.
64
AT321_AM_E1
If users modify geographic data locally, for example edit clutter or traffic in their
respectiveprojects,theyshouldstorethesemodifiedgeographicdatalocallysothatthe
modificationsdonotimpactotherusers.
6.2.4 SharedPathLossMatrices
Sharedpathlossmatricesareusuallystoredonafileserveraccessibletoandsharedbyalltheusersworkingonthesame
project.ThesepathlossesarecalculatedusingthemasterAtolldocumentbytheAtolladministrator.Theprivatepathloss
matricesofthemasterAtolldocumentareusedassharedpathlossmatricesbytheendusers.
TheAtolladministratoristheownerofthesharedpathlossmatrices,andmusthaveread/writeaccesstothesharedpath
lossmatricesfolder.Endusersshouldhavereadonlyaccesstothisfolder.
It is the administrators duty to regularly update the master Atoll document with the modifications made to the master
databasebytheendusers,andtocalculatethesharedpathlossmatricesusingthemasterAtolldocumentonaroutinebasis.
Thistaskcanbecarriedoutusingamacro.Formoreinformation,see"Appendix3:CalculatingPathLossMatrices"onpage 70.
Sharedpathlossmatricesareavailableforuseincalculationstoalltheendusers.However,endusersarenotallowedto
modifythesharedpathlossmatrices.
Thesharedpathlossmatricesmustbeunlockedinorderforuserstobeabletoworkwith
them.YoucancheckwhetherpathlossmatricesareunlockedinthePropagationtabof
theTransmittersfolderspropertiesdialogue.
6.2.5 UserAtollDocuments
UserAtolldocumentsarecreatedfromthemasterdatabase.Thesecancontaintheentireprojectnetworkdataoronlyapart
ofit.UserdocumentsaretheworkingdocumentsoftheAtollendusersconnectedtothemasterdatabase,thegeographic
data,andthesharedpathlossmatricesfolder.
YoushouldloaddatafromthemasterdatabaseineachuserAtolldocumentandsaveitbeforesettingthesharedpathloss
matricesfolderforthedocument.ForanymodificationsmadebyendusersintheirAtolldocumentsthatrendersomeshared
pathlossesinvalid,Atollcalculatestheinvalidpathlossmatriceslocallyfortheendusersandstoresthemintheirprivatepath
loss matrices location. Shared path loss matrices are only used in calculations if valid private path loss matrices are not
available.Therefore,inordertousesharedpathlossmatrices,youmustdeletethecorrespondingprivatepathlossmatrices.
Ifusersaregoingtoworkonregionsofanetwork,theregionalisationshouldbesetupbeforecreatingtheuserdocuments.
Formoreinformationonregionalisation,see"Appendix2:DatabaseRegionalisation"onpage 70.
IfyouwishtoaddcustomfieldsintheAtolldocument,youshouldfirstaddthefieldin
thedatabase,andthenupdateyourAtolldocumentfromthedatabase.Customfields
addedinanAtolldocumentconnectedtoaMicrosoftAccessdatabaseareautomatically
addedtothedatabase.However,thisisnotthecasewithotherRDBMS,suchasOracle.
6.3 ManagingUserAccountsandAccessRightsinOracle
TheAtollManagementConsoleenablesyoutocreateanddeletedatabaseuseraccounts,edituseraccountinformation,and
defineuseraccessrightstodifferentcomponentsofaprojectsuchasdatabasetables,andradiodataandparametersinAtoll.
InordertobeabletomanageuseraccountsandaccessrightsusingtheAtollManagementConsole,youfirsthavetomake
thedatabasecompatiblewiththeusermanagementtool.Thisisdoneautomaticallywhentheusermanagementtoolisrun
onadatabaseforthefirsttime.ThedatabasehastobeofthesameversionastheAtollManagementConsolebeingusedto
manageuseraccountsandaccessrights.
Tomakeyourdatabasecompatiblewiththeusermanagementtool:
1. IntheAtollManagementConsolewindow,rightclickthedatabasewhoseuseraccountsyouwishtomanage.
2. SelectManageUsers.TheUserManagementdialogueappears(seeFigure 6.2onpage 66).
3. ClickYeswhenaskedwhetheryouwanttomakeyourdatabasecompatiblewiththeusermanagementtool.
TheAtollManagementConsoleaddsaGUIUserRightstableinthedatabasewiththefollowingstructure:
Field
Type
Description
ATOLL_USER
Text(50)
Nameoftheuseraccount
65
Forsk2014
Field
Type
Description
RIGHTS
Memo
Semicolonseparatedsetofinterfaceaccessrights
EachusersinterfaceaccessrightsarestoredinauniquerecordintheGUIUserRightstable.ThecontentsoftheRIGHTSfield
havethefollowingsyntax:
RADIOPARAMS;CALCPARAMS;PROPAGMODELS;PASSWORD
Thesyntaxisexplainedindetailin"DefiningDatabaseandInterfaceAccessRights"onpage 66.
If interface access rights are not defined for a database, i.e., the GUIUserRights table does not exist, all the users have
unrestrictedaccesstotheAtollinterface.
Ifinterfaceaccessrightsaredefinedforadatabase,andausercreatesadocumentfromthedatabaseoropensadocument
connectedtothedatabase,Atollretrievestheinterfaceaccessrightsfortheuserwhenheentershisusernameandpassword
toaccessthedatabase.
Ifthedatabaseisnotreachable,theuserisnotlistedintheGUIUserRightstable,orifthepasswordisnotcorrect,theusers
interfaceaccessrightsaresettoreadonlybydefault(formoreinformation,see"DefiningDatabaseandInterfaceAccess
Rights"onpage 66).IftheuserislistedintheGUIUserRightstable,hisinterfaceaccessrightsarereadandappliedtotheAtoll
interface(tablegridsandpropertiesdialogues).AmessageisdisplayedintheEventViewerwindowtoinformtheuserofhis
interfaceaccessrights.Itispossibletoremoveinterfaceaccessrestrictionsbydisconnectingthedocumentfromthedatabase.
However,adisconnecteddocumentcannotbereconnectedtothedatabase.
TheGUIUserRightstableisalsostoredintheAtolldocument,andisupdatedwhenthedocumentissaved.Hence,userscan
workontheirdocumentswithoutactuallybeingconnectedtothedatabase,andstillhavetheirusualinterfaceaccessrights
appliedinthedocument.
Atolldoesnotaskfortheusernameandpasswordwhenadocumentisopenedusingthe
API.Theinterfaceaccessrightsstoredinthedocumentareused.
Whendatabaseconnectionpropertiesaremodifiedforadocument,forexample,whenadifferentuserentershisusername
andpasswordintheconnectionproperties,Atollreadsandappliestheinterfaceaccessrightsdefinedforthenewuser.
6.3.1 DefiningDatabaseandInterfaceAccessRights
Foranyexistinguseraccount,youcansetthedatabaseandAtollinterfaceaccessrightsusingtheAtollManagementConsole.
TomanagedatabaseandAtollinterfaceaccessrightsforanexistinguseraccount:
1. IntheAtollManagementConsolewindow,rightclickthedatabasewhoseuseraccountsyouwishtomanage.
Figure 6.2:UserAccountandAccessRightsManagementDialogue
3. UnderAtollprojects,selecttheprojectforwhichyouwanttomanageuseraccounts.
66
AT321_AM_E1
4. UnderListofusers,selecttheuseraccountwhosedatabaseandinterfaceaccessrightsyouwanttoset.
Userswhohavedatabaseaccessrightsintheselecteddatabasearemarkedwiththegreenicon( ).Userswhodo
nothaveanydatabaseaccessrightsintheselecteddatabase(Category=NoAccess)aremarkedwiththeredicon
( ).Locked(deactivated)useraccountsaremarkedwithayellowlockicon( ).Formoreinformationonlocked
useraccounts,see"CreatingandEditingUserAccounts"onpage 68.
YoucanusetheFilterlisttodisplay:
),withoutaccess(
),orlocked(
Allusers:Userswithaccess(
Userswithaccess( )
Administrators:Userswithadministratorrightsamongtheuserswithaccess
Standardusers:Userswithstandardrightsamongtheuserwithaccess
Readonlyusers:Userswithreadonlyaccessrightsamongtheuserswithaccess
5. UnderDatabaserights,youcanselectadatabaseaccessRightscategory:
Noaccess:Userwithoutreadandwriteaccesstothedatabase.Thedatabaseisnotvisibletotheseusersandthey
arenotallowedtocreateAtolldocumentsbasedonthisdatabase.
Readonly:UsersallowedtocreateAtolldocumentsfromthedatabasebutwithoutwritepermissionstoanytable
ofthedatabase,i.e.,userscannotarchivechangesmadeintheAtolldocumenttothedatabase.
Standard:Userswithreadandwriteaccesstosometablesofthedatabase.Thesetablesincluderadionetwork
datatablesincludingsites,transmitters,cells,subcells,repeaters,remoteantennas,secondaryantennas,intra
andintertechnologyneighboursandexceptionalpairs,siteandtransmitterlists,microwavepointtopoint,point
tomultipoint,andmultihoplinks,microwaverepeaters,microwavehubs.
Administrator:Userswithreadandwriteaccesstoallthetablesofthedatabase.
DatabaseaccessrightsarestoredintheuseraccountpropertiesinOracle.IfyouareworkingwithanRDBMSother
thanOracle,youwillnotbeabletosetdatabaseaccessrights.Youcan,however,stillsetinterfaceaccessrightsas
explainedbelow.
6. UnderInterfacerights,youcanselectinterfaceaccessrightsfor:
Accesstoradiodata:
Full:(RADIOPARAMS=ALL)Userswithreadandwriteaccesstoallthetablesandpropertiesdialogues.
Standard: (RADIOPARAMS = STD) Users with read and write access to radio network data tables and
properties dialogues including sites, transmitters, cells, subcells, repeaters, remote antennas, secondary
antennas,intraandintertechnologyneighboursandexceptionalpairs,siteandtransmitterlists,microwave
pointtopoint,pointtomultipoint,andmultihoplinks,microwaverepeaters,microwavehubs.
Readonly:(RADIOPARAMS=NONE)Userswithreadonlyaccesstotablesandpropertiesdialogues,i.e.,users
arenotallowedtomodifyradionetworkdataandparameters.
Database access rights and access rights to radio data in Atoll can be set
independently.Forexample,ausercanhavefullaccessrightsintheinterfacebutnot
beallowedtoarchivechangestothedatabase.
However,accessrightsintheinterfaceshouldonlybegrantediftheuserhasatleast
readonlyaccesstothedatabase.
Accesstocalculationsettings:
All: (CALCPARAMS = ALL) Users with read and write access to all coverage predictions, their calculation
settings, and to microwave calculation settings (Models, Objectives, and Clutter Categories tabs of the
PropertiesdialogueoftheMicrowaveRadioLinksfolder).
Standard:(CALCPARAMS=STD)Userswithaccesstocustomisedcoveragepredictionsonly,andallowedto
modifycoverageconditionsanddisplaysettings.Theseusersdonothaveaccesstothemicrowavecalculation
settingsmentionedabove.
Customisedonly:(CALCPARAMS=NONE)Userswithaccesstocustomisedcoveragepredictionsonly,butnot
allowedtomodifycoverageconditionsanddisplaysettings.Theseusersdonothaveaccesstothemicrowave
calculationsettingsmentionedabove.
Accesstopropagationmodels:
Full:(PROPAGMODELS=ALL)Userswithreadandwriteaccesstoallpropagationmodelsandtheirproperties.
Readonly:(PROPAGMODELS=NONE)Userswithreadonlyaccesstothepropertiesofallthepropagation
models.Addinganddeletingpropagationmodelsisalsonotallowed.
Passwordconfirmation:
Yes: (PASSWORD = STD) Atoll will ask users for password when opening a document connected to this
databaseorcreatinganewdocumentfromthisdatabase.
No:(PASSWORD=NONE)Atollwillnotaskusersforpasswordwhenopeningadocumentconnectedtothis
databaseorcreatinganewdocumentfromthisdatabase.
67
Forsk2014
7. ClickOK.Thedatabaseandinterfaceaccessrightsoftheselecteduseraresavedinthedatabase.
6.3.2 CreatingandEditingUserAccounts
YoucancreateandedituseraccountsusingtheAtollManagementConsole.
Tomanageuseraccounts:
1. IntheAtollManagementConsolewindow,rightclickthedatabasewhoseuseraccountsyouwanttomanage.
3. Tocreateanewuseraccount:
a. UnderUsers,clickCreate.TheCreate/EditUserdialogueappears(Figure 6.3onpage 68).
b. UnderIdentification,enteraUsername(inblockletters)andPassword,andselectaTablespaceforthenewuser
account.
c. UnderAdvanced,selectUseoperatingsystemauthenticationifyouwanttouseOSauthenticationprefixwiththe
username,andUnlimitedtablespaceprivilegeifyouwanttoassignthissystemprivilegetotheuser.
d. ClickOK.Thenewuseraccountiscreated.
4. Toeditauseraccount:
a. UnderListofusers,selecttheuseraccountwhoseinformationyouwanttoedit.
b. UnderUsers,clickEdit.TheCreate/EditUserdialogueappears(Figure 6.3onpage 68).
c. UnderIdentification,modifytheusersPasswordorassignedTablespace.
d. UnderAdvanced,selectUseoperatingsystemauthenticationifyouwanttouseOSauthenticationprefixwiththe
username,andUnlimitedtablespaceprivilegeifyouwanttoassignthissystemprivilegetotheuser.
e. ClickOK.Themodifieduseraccountinformationissaved.
5. Todeactivate(lock)auseraccount:
a. UnderListofusers,selecttheuseraccountyouwanttodeactivate.
b. UnderUsers,clickEdit.TheCreate/EditUserdialogueappears(Figure 6.3onpage 68).
c. UnderAdvanced,selectAccountlockedcheckbox.
d. ClickOK.Theuseraccountisdeactivatedandcannolongerbeused.
6. Todeleteauseraccount:
a. UnderListofusers,selecttheuseraccountyouwanttodelete.
b. UnderUsers,clickDelete.Theuseraccountisdeleted.
Figure 6.3:CreatingorEditingaUserAccount
6.3.3 ResettingUserDatabasePermissions
Thepermissionsresetfeatureenablesyoutorebuilduserdatabasepermissionswhilekeepingexistingroleassignments.
YoucanresetuserpermissionsfromtheAtollManagementConsole.
68
AT321_AM_E1
ThisfeatureisparticularlyusefulafteramajorAtollupgradeoraftertableswereaddedasaresultofaprojectcustomization,
andforallunforeseenreasonswhichcanrequirefixinguserdatabasepermissions.
Thepermissionsresetprocessdoesnotremoveanyobjectprivilegeswhichassignedpriortorebuildingthedatabase.Itjust
looksfornewobjectsandassignspermissionsbasedonexistinguserprofiles("Administrator","Standard"or"Readonly").
Toresetuserpermissions:
1. OpenthedatabaseforwhichyouwanttoresetuserpermissionsintheAtollManagementConsolewindow.
2. UnderDatabaserights,clickontheResetbutton.
3. Acknowledgethemessageinformingyouabouttherebuildingprocessduration.
Thedurationofthedatabaserebuildingprocessdependsonthenumberofusersandon
thedatabaseprocessingspeed.
6.4 Appendices
Thefollowingappendicesprovideadditionalinformationon:
"Appendix1:CheckingDataIntegrity"onpage 69
"Appendix2:DatabaseRegionalisation"onpage 70
"Appendix3:CalculatingPathLossMatrices"onpage 70
"Appendix4:PathLossMatricesFromDifferentSources"onpage 71
6.4.1 Appendix1:CheckingDataIntegrity
Atollincludesdataconsistencyandintegritycheckingtoolsthatallowyoutocheckdataconsistencybetweenthedifferent
Atolltables(Sites,Transmitters,etc.).ItisrecommendedthattheAtolladministratorrunsdataintegritychecksregularlyon
themasterAtolldocumentafteritisupdatedwithdatamodificationsinthemasterdatabase.
Toperformdataintegritycheck:
InAtoll,selectDocument >DataAudit >IntegrityCheck.

Atoll searches for records with integrity problems which can occur with objects that have foreign keys. Integrity
problemsoccurwhenrecordsreferrecordsthatdonotexist.Forexample,transmitterslocatedonsitesthatdonot
existintheSitestable,transmittersreferringtoanantennathatdoesnotexistintheAntennastable,etc.).Records
withintegrityproblemscanbedeletedwhenfound.
Toperformundefinedrecordcheck:
InAtoll,selectDocument >DataAudit >UndefinedRecordCheck.

Atoll searches for undefined records such as sites without transmitters, transmitters without subcells, TRXs, and
neighboursinGSM,transmitterswithoutcells,andcellswithoutneighboursinUMTS,CDMA2000,TDSCDMA,LTE,
WiMAX,andWiFi.AtolllistsalltheundefinedrecordsfoundintheEventViewer.
Toperformduplicaterecordcheck:
InAtoll,selectDocument >DataAudit >DuplicateRecordCheck.

Atollsearchesforrecordsthathavethesameidentifier.Forexample,siteswiththesamename,transmitterswiththe
samename,etc.AtolllistsalltheduplicaterecordsintheEventViewer.
Toperformmicrowavedatacheck:
1. InAtoll,selectDocument >DataAudit >MicrowaveLinkDataCheck.TheMicrowaveDataCheckdialogueappears.
2. IntheMicrowaveDataCheckdialogue,selectthedatatocheck.
3. SelectListallthecheckstolistallthechecksintheEventViewer.
4. ClickOK.
Atollsearchesthemicrowavelinkstablesforproblemsrelatedtotheselectedchecks.Atollliststheproblemsfound
intheEventViewer.
If you fix any problems in the Atoll document, you must archive the changes in the
databaseinordertofixtheproblemsforalltheusersworkingwiththatdatabase.
69
Forsk2014
6.4.2 Appendix2:DatabaseRegionalisation
Youcansubdividethenetworkintoregionsinthefollowingways:
Staticregionalisationusingmultileveldatabases
Staticregionalisationcanbebasedonsitelists,SQLfilters,orgeographiczonesintheformoffilteringpolygons.Static
regionalisationiscarriedoutbycreatingprojectdatabasesfromthemasterdatabase,i.e.,multileveldatabasesas
explainedin"WorkingWithaMultilevelDatabases"onpage 49.
Static regionalisation requires manual synchronisation between the master database and the regional project
databasesusingtheAtollManagementConsole.Inamultileveldatabaseenvironment,endusersworkwithproject
databases,refreshingandarchivingdataastheycontinuetoworkontheirrespectiveregionsofthenetwork.Data
archive and refresh between the project databases and the master database are performed by the administrator
alone.
Advantage:Highperformance.
Disadvantage:ManualSynchronisationbetweenthemasterandtheprojectdatabases.
DynamicregionalisationusingOracleSpatialorOracleLocator
DynamicregionalisationcanbebasedonOracleSpatial,whichdoesnotcreateseparateregionaldatabasesfromthe
masterdatabase,butratherletsthedifferentusersworkwiththemasterdatabasedirectlywhilemanagingtheir
accessprivilegesaccordingtotheiruserconnectionproperties.InanAtollmultiuserenvironment,youcancreate
suchregionalisationwithoutinstallingOracleSpatial.YoucanimplementthissolutionusingOracleLocator,whichis
providedinthestandardOracleinstallation.
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,advanceduser,readonlyuser,etc.,andgiveexamplesofhowtosetupregionsinthenetworkandhow
toassignuserrightstoeachregion.
Advantage:Oncesetup,doesnotrequireadministratorintervention.
Disadvantage:Slowperformance(archivingdatainthedatabasetakesalongtime).
6.4.3 Appendix3:CalculatingPathLossMatrices
YoucancalculateonlytheinvalidpathlossmatricesorallthepathlossmatricesinAtollorusingamacro.
Youshouldonlycalculatethesharedpathlossmatriceswhentheyarenotbeingaccessed
byusers.
Tocalculateinvalidpathlossmatricesonly:
1. RightclicktheTransmittersfolder.Thecontextmenuappears.
2. SelectCalculations >CalculatePathLossMatrices.
Atollcalculatespathlossmatricesforallactivetransmittersinthefolderorsubfolder.Onlyinvalidandnonexistent
matricesarecalculated.
Tocalculateallthepathlossmatrices(validandinvalid):
1. RightclicktheTransmittersfolder.Thecontextmenuappears.
2. SelectCalculations >ForcePathLossMatrixCalculation.
Atollcalculatesallthepathlossmatricesforallactivetransmittersinthefolderorsubfolder.
Youcanwriteascriptormacrotoupdatepathlossmatricesautomaticallyatregularintervals.Thescriptormacroshould:
1. StartAtoll(Start).
2. OpenthemasterAtolldocument(Open).
3. Refreshthecontentsofthedocumentwithdatafromthedatabase(Refresh).
4. Calculatepathlossmatrices(Calculate).
5. SavethemasterAtolldocument(Save).
6. CloseAtoll(Exit).
ApathlossupdatemacroisavailablefromForskondemand.
70
AT321_AM_E1
YoushouldalsomakeregularbackupsofthemasterAtolldocument.Theabovemacro
couldalsocreateabackupATLfileofthemasterAtolldocumentonaregularbasis.This
filecanbeoverwrittendaily,wheneverpathlossesarecalculated.
6.4.4 Appendix4:PathLossMatricesFromDifferentSources
Atoll calculates path loss matrices and creates path loss matrix storage files using the propagation models assigned to
transmitters.Atollcanalsoworkwithpathlossmatricescalculatedbyothertools.Tousepathlossmatricesfromdifferent
sources,makesurethatthepathlossmatricesare:
AvailableinaformatcompatiblewithAtoll.Fileformatsaredescribedin"PathLossMatrixFileFormat"onpage 92.
StoredatthelocationsetintheAtolldocument.
Valid.Ifthepathlossmatricesarenotvalid,Atollwillautomaticallycalculatethemthenexttimetheyareused.
Pathlossmatricescalculatedbyothertoolsshouldincludeantennapatternattenuation
(i.e.,shouldbemasked)inordertobeconsistentwiththepathlossmatricescalculated
byAtoll.
The shared path loss matrices architecture can contain path loss matrices from different sources. The Pathloss.dbf file
providesthemeanstomanageseveralsourcesofpathlossmatrices.Thisfilestores,amongotherinformation,thevalidity
statusandthelocation(path)ofthepathlossmatrixfilesforeachtransmitter.
LetusassumethatusersofgroupAwishtoworkwiththepathlossmatricesgeneratedbyAtollonly,andusersofgroupB
wishtoworkwithpathlossmatricesgeneratedbyadifferenttoolforapartofthenetworkandwithpathlossmatrices
generatedbyAtollwherethematricesfromtheothertoolarenotavailable.
Let us assume that the shared path loss matrices folder where Atoll stores the generated path loss matrices files is
C:\Path_Loss_Internal,andthefolderwheretheothertoolstoresitspathlossmatricesisC:\Path_Loss_External.
ThePathloss.dbffileinthePath_Loss_InternalfolderwillstorethepathtotheLOSfilesforeachtransmitterinthenetwork.
ThisfoldercanbesetasthesharedpathlossmatricesfolderintheATLfilesofgroupAusers.
TosetupthesharedpathlossmatricesfolderforgroupBusers,youmustcreateanewfolderwithaPathloss.dbffileinit.
ThisfoldercanbecalledC:\Path_Loss_Mixed.ThePathloss.dbffileinthisfoldercanbeacopyofthePathloss.dbffileinthe
Path_Loss_InternalfolderwiththepathstotheLOSfilesmodified.Forexample,ifthepathlossmatricesgeneratedbythe
other tool include Transmitter_1, the Pathloss.dbf file in the Path_Loss_Mixed folder will have all the same entries as
Pathloss.dbffileinthePath_Loss_InternalfolderexceptforthepathfortheTransmitter_1pathlossmatricesfile.Figure 6.4
onpage 71explainsthisconcept.
Figure 6.4:PathLossArchitectureforMultipleSourcePathLossMatrices
OncethePathloss.dbffileinthePath_Loss_Mixedfolderisupdatedwiththecorrectpathscorrespondingtothedifferent
transmitters,thePath_Loss_MixedfoldercanbesetasthesharedpathlossmatricesfolderintheATLfilesofgroupBusers.
IfagroupBuserchangessomeparameterswhichmakesomepathlossmatricesinvalid,Atollwillrecalculatetheprivatepath
lossmatriceswiththepropagationmodelsassignedtothetransmitters.Theexternalpathlossmatrixwillnolongerbeused.
71
72
Forsk2014
Chapter7:CoordinateSystemsandUnits
AT321_AM_E1
7 CoordinateSystemsandUnits
7.1 CoordinateSystems
Amaporageospatialdatabaseisaflatrepresentationofdatacollectedoveracurvedsurface.Projectionisameansof
producingallorpartofaspheroidonaflatsurface,whichcannotbedonewithoutdistortion.Itisuptothecartographerto
choosethecharacteristic(distance,direction,scale,area,orshape)thathewantstoproduceaccuratelyonaflatsurfaceat
the expense of the other characteristics, or to make a compromise on several characteristics. The projected zones are
referencedusingcartographiccoordinates(metre,yard,etc.).Twoprojectionmethodsarewidelyused:
TheLambertConformalConicMethod:Aportionoftheearthisprojectedonaconeconceptuallysecantatoneor
twostandardparallels.Thisprojectionmethodisusefulforrepresentingcountriesorregionsthathaveapredominant
eastwestexpanse.
TheUniversalTransverseMercator(UTM)Method:Aportionoftheearthisprojectedonacylindertangenttoa
meridian(whichistransverseorcrosswisetotheequator).Thisprojectionmethodisusefulformappinglargeareas
thatareorientednorthsouth.
A geographic system is not a projection, but a representation of a location on the surface of the earth in geographic
coordinates(degreeminutesecond,gradient)withthelatitudeandlongitudewithrespecttoameridian(e.g.,ParisforNTF
systemandGreenwichforED50system).Locationsinageographicsystemcanbeconvertedintootherprojections.
References:
1. Snyder,John.P.,MapProjectionsUsedbytheUSGeologicalSurvey,2ndEdition,
UnitedStatesGovernmentPrintingOffice,Washington,D.C.,313pages,1982.
2. http://www.colorado.edu/geography/gcraft/notes/gps/gps_f.html
3. http://www.epsg.org/Geodetic.html
4. http://geodesie.ign.fr/contenu/fichiers/documentation/pedagogiques/
transfo.pdf(French)
7.1.1 DefinitionofaCoordinateSystem
Ageographiccoordinatesystemisalatitudeandlongitudecoordinatesystem.Thelatitudeandlongitudearerelatedtoan
ellipsoid,ageodeticdatum,andaprimemeridian.Thegeodeticdatumprovidesthepositionandorientationoftheellipsoid
relativetotheearth.
Cartographiccoordinatesystemsareobtainedbytransformingeach(latitude,longitude)valueintoan(easting,northing)
value.Aprojectioncoordinatesystemisobtainedbytransformingeach(latitude,longitude)valueintoan(easting,northing)
value. Projection coordinate systems are geographic coordinate systems that provide longitude and latitude, and the
transformationmethodcharacterisedbyasetofparameters.Differentmethodsmightrequiredifferentsetsofparameters.
Forexample,theparametersrequiredforTransverseMercatorcoordinatesystemsare:
Thelongitudeofthenaturalorigin(centralmeridian)
Thelatitudeofthenaturalorigin
TheFalseEastingvalue
TheFalseNorthingvalue
Ascalingfactoratthenaturalorigin(centralmeridian)
Basicdefinitionsarepresentedbelow.
GeographicCoordinateSystem
The geographic coordinate system is a datum and a meridian. Atoll enables you to choose the most suitable geographic
coordinatesystemforyourgeographicdata.
Datum
ThedatumconsistsoftheellipsoidanditspositionrelativetotheWGS84ellipsoid.Inadditiontotheellipsoid,translation,
rotation,anddistortionparametersdefinethedatum.
Meridian
ThestandardmeridianisGreenwich,butsomegeographiccoordinatesystemsarebasedonothermeridians.Thesemeridians
aredefinedbythelongitudewithrespecttoGreenwich.
73
Forsk2014
Ellipsoid
Theellipsoidisthepatternusedtomodeltheearth.Itisdefinedbyitsgeometricparameters.
Projection
Theprojectionisthetransformationappliedtoprojecttheellipsoidoftheearthontoaplane.Therearedifferentprojection
methodsthatusespecificsetsofparameters.
ProjectionCoordinateSystem
The projection coordinate system is the result of the application of a projection to a geographic coordinate system. It
associatesageographiccoordinatesystemandaprojection.Atollenablesyoutochoosetheprojectioncoordinatesystem
matchingyourgeographicdata.
7.1.2 TypesofCoordinateSystemsinAtoll
Dependingontheworkingenvironment,therecanbeeithertwoorfourcoordinatesystemsusedinAtoll.Ifyouareworking
withstandalonedocuments,i.e.,documentsnotconnectedtodatabases,therearetwocoordinatesystemsusedinAtoll:
Projectioncoordinatesystem
Displaycoordinatesystem
Ifyouareworkinginamultiuserenvironment,Atollusesfourcoordinatesystems:
ProjectioncoordinatesystemfortheAtolldocument
DisplaycoordinatesystemfortheAtolldocument
Internalprojectioncoordinatesystemforthedatabase
Internaldisplaycoordinatesystemforthedatabase
ProjectionCoordinateSystem
Theprojectioncoordinatesystemisthecoordinatesystemoftheavailablerastergeographicdatafiles.Youshouldsetthe
projectioncoordinatesystemofyourAtolldocumentsothatitcorrespondstothecoordinatesystemoftheavailableraster
geographicdata.YoucansettheprojectioncoordinatesystemofyourdocumentintheOptionsdialog.
AlltherastergeographicdatafilesthatyouwanttoimportanduseinanAtolldocumentmusthavethesamecoordinate
system.Youcannotworkwithrastergeographicdatafileswithdifferentcoordinatesystemsinthesamedocument.
If you import vector geographic data (e.g., traffic, measurements, etc.) with different
coordinatesystems,itispossibletoconvertthecoordinatesystemsofthesedatainto
theprojectioncoordinatesystemofyourAtolldocument.
Theprojectioncoordinatesystemisusedtokeepthecoordinatesofsites(radionetworkdata)consistentwiththegeographic
data.
Whenyouimportarastergeographicdatafile,Atollreadsthegeoreferencinginformationfromthefile(orfromitsheader
file,dependingonthegeographicdatafileformat),i.e.,itsNorthwestpixel,todeterminethecoordinatesofeachpixel.Atoll
doesnotuseanycoordinatesystemduringtheimportprocess.However,thegeoreferencinginformationofgeographicdata
filesareconsideredtobeprovidedintheprojectioncoordinatesystemofthedocument.
DisplayCoordinateSystem
Thedisplaycoordinatesystemisthecoordinatesystemusedforthedisplay,e.g.,indialogs,intheMapwindowrulers,inthe
statusbar,etc.Thecoordinatesofeachpixelofgeographicdataareconvertedtothedisplaycoordinatesystemfromthe
projectioncoordinatesystemfordisplay.Thedisplaycoordinatesystemisalsousedforsites(radionetworkdata).Youcan
setthedisplaycoordinatesystemofyourdocumentintheOptionsdialog.
Ifyouimportsitesdata,thecoordinatesystemofthesitesmustcorrespondtothedisplaycoordinatesystemofyourAtoll
document.
Ifyouchangethedisplaycoordinatesysteminadocumentwhichisnotconnectedtoadatabase,thecoordinatesofallthe
sitesareconvertedtothenewdisplaysystem.
Ifthecoordinatesystemsofallyourgeographicdatafilesandsites(radionetworkdata)
arethesame,youdonothavetodefinetheprojectionanddisplaycoordinatesystems
separately.Bydefault,thetwocoordinatesystemsarethesame.
74
AT321_AM_E1
InternalCoordinateSystems
Theinternalcoordinatesystemsaretheprojectionandthedisplaycoordinatesystemsstoredinadatabase.Theprojection
anddisplaycoordinatesystemssetbytheadministratorinthecentralAtollprojectarestoredinthedatabasewhenthe
databaseiscreated,andcannotbemodifiedbyusers.Onlytheadministratorcanmodifytheinternalcoordinatesystems
manuallybyeditingtheentriesintheCoordSysandtheUnitstables.AllAtolldocumentsopenedfromadatabasewillhave
theinternalcoordinatesystemsofthedatabaseastheirdefaultprojectionanddisplaycoordinatesystems.
WhenexportinganAtollprojecttoadatabase,thecurrentlychosendisplaycoordinatesystembecomestheinternaldisplay
coordinatesystemforthedatabase,andthecurrentlychosenprojectioncoordinatesystembecomestheinternalprojection
coordinatesystemforthedatabase.
AlthoughAtollstoresboththecoordinatesystemsinthedatabase,i.e.,theprojectionandthedisplaycoordinatesystems,
theonlyrelevantcoordinatesystemforthedatabaseistheinternaldisplaycoordinatesystembecausethiscoordinatesystem
istheoneusedforthecoordinatesofsites(radionetworkdata).
Usersworkingondocumentsconnectedtoadatabasecanmodifythecoordinatesystemsintheirdocumentslocally,andsave
thesechangesintheirdocuments,buttheycannotmodifythecoordinatesystemsstoredinthedatabase.
Ifyouchangethedisplaycoordinatesysteminadocumentwhichisnotconnectedtoadatabase,thecoordinatesofallthe
sitesareconvertedtothenewdisplaysystem.
Ifyouchangethedisplaycoordinatesysteminadocumentwhichisconnectedtoadatabase,thecoordinatesofallthesites
are converted to the new coordinate system in the Atoll document locally but not in the database because the internal
coordinatesystemscannotbechanged.
Atollusestheinternalcoordinatessystemsinordertokeepthesitecoordinatesconsistentinthedatabasewhichisusually
accessedbyalargenumberofusersinamultiuserenvironment.
7.1.3 CoordinateSystemsFileFormat
TheCoordsystemsfolderlocatedintheAtollinstallationdirectorycontainsallthecoordinatesystems,bothgeographicand
cartographic, offered in the tool. Coordinate systems are grouped by regions. A catalogue per region and a "Favourites"
catalogueareavailableinAtoll.TheFavouritescatalogueisinitiallyemptyandcanbefilledbytheuserbyaddingcoordinate
systems to it. Each catalogue is described by an ASCII text file with .cs extension. In a .cs file, each coordinate system is
describedinoneline.Thelinesyntaxfordescribingacoordinatesystemis:
Code = "Name of the system"; Unit Code; Datum Code; Projection Method Code, Projection
Parameters; "Comments"
Examples:
4230 = "ED50"; 101; 230; 1; "Europe - west"
32045 = "NAD27 / Vermont"; 2; 267; 6, -72.5, 42.5, 500000, 0, 0.9999643; "United
States - Vermont"
Youshouldkeepthefollowingpointsinmindwheneditingorcreating.csfiles:
The identification code enables Atoll to differentiate coordinates systems. In case you create a new coordinate
system,itscodemustbeanintegervaluehigherthan32767.
When describing a new datum, you must enter the ellipsoid code and parameters instead of the datum code in
brackets.Therecanbe3to7parametersdefinedinthefollowingorder:Dx,Dy,Dz,Rx,Ry,Rz,S.Thesyntaxoftheline
inthe.csfilewillbe:
Code = "Name of the system"; Unit Code; {Ellipsoid Code, Dx, Dy, Dz, Rx, Ry, Rz, S};
Projection Method Code, Projection Parameters; "Comments"
Therecanbeuptosevenprojectionparameters.Theseparametersmustbeorderedaccordingtotheparameterindex
(see"ProjectionParameterIndices"onpage 78).Parameterwithindex0isthefirstone.Projectionparametersare
delimitedbycommas.
ForUTMprojections,youmustprovidepositiveUTMzonenumbersfornorthUTMzonesandnegativenumbersfor
southUTMzones.
Youcanaddallotherinformationascomments(suchasusageorregion).
Codesofunits,data,projectionmethods,andellipsoids,andprojectionparameterindicesarelistedinthetablesbelow.
75
Forsk2014
UnitCodes
Code
CartographicUnits
Code
GeographicUnits
Metre
100
Radian
Kilometre
101
Degree
Foot
102
Grad
Link
103
ArcMinute
Chain
104
ArcSecond
Yard
Nauticalmile
Mile
Unspecified
Unspecified
Code
Datum
Code
Datum
121
GreekGeodeticReferenceSystem1987
260
Manoca
125
Samboja
261
Merchich
126
Lithuania1994
262
Massawa
130
Moznet(ITRF94)
263
Minna
131
Indian1960
265
MonteMario
201
Adindan
266
M'poraloko
202
AustralianGeodeticDatum1966
267
NorthAmericanDatum1927
203
AustralianGeodeticDatum1984
268
NADMichigan
204
AinelAbd1970
269
NorthAmericanDatum1983
205
Afgooye
270
Nahrwan1967
206
Agadez
271
Naparima1972
207
Lisbon
272
NewZealandGeodeticDatum1949
DatumCodes
76
208
Aratu
273
NGO1948
209
Arc1950
274
Datum73
210
Arc1960
275
NouvelleTriangulationFranaise
211
Batavia
276
NSWC9Z2
212
Barbados
277
OSGB1936
213
Beduaram
278
OSGB1970(SN)
214
Beijing1954
279
OS(SN)1980
215
ReseauNationalBelge1950
280
Padang1884
216
Bermuda1957
281
Palestine1923
217
Bern1898
282
PointeNoire
218
Bogota
283
GeocentricDatumofAustralia1994
219
BukitRimpah
284
Pulkovo1942
221
CampoInchauspe
285
Qatar
222
Cape
286
Qatar1948
223
Carthage
287
Qornoq
224
Chua
288
LomaQuintana
225
CorregoAlegre
289
Amersfoort
226
Coted'Ivoire
290
RT38
227
DeirezZor
291
SouthAmericanDatum1969
228
Douala
292
SapperHill1943
229
Egypt1907
293
Schwarzeck
230
EuropeanDatum1950
294
Segora
AT321_AM_E1
Code
Datum
Code
Datum
231
232
EuropeanDatum1987
295
Serindung
Fahud
296
Sudan
233
Gandajika1970
297
Tananarive1925
234
Garoua
298
Timbalai1948
235
GuyaneFrancaise
299
TM65
236
HuTzuShan
300
TM75
237
HungarianDatum1972
301
Tokyo
238
IndonesianDatum1974
302
Trinidad1903
239
Indian1954
303
TrucialCoast1948
240
Indian1975
304
Voirol1875
241
Jamaica1875
305
VoirolUnifie1960
242
Jamaica1969
306
Bern1938
243
Kalianpur
307
NordSahara1959
244
Kandawala
308
Stockholm1938
245
Kertau
309
Yacare
247
LaCanoa
310
Yoff
248
ProvisionalSouthAmericanDatum1956
311
Zanderij
249
Lake
312
MilitarGeographischeInstitut
250
Leigon
313
ReseauNationalBelge1972
251
Liberia1964
314
DeutscheHauptdreiecksnetz
252
Lome
315
Conakry1905
253
Luzon1911
322
WGS72
254
HitoXVIII1963
326
WGS84
255
HeratNorth
901
AncienneTriangulationFranaise
256
Mahe1971
902
NorddeGuerre
903
NAD1927Guatemala/Honduras/Salvador
(PanamaZone)
ProjectionMethod
Code
ProjectionMethod
Undefined
ObliqueStereographic
Noprojection>Longitude/Latitude
NewZealandMapGrid
LambertConformalConical1SP
10
HotineObliqueMercator
LambertConformalConical2SP
11
LabordeObliqueMercator
257
Makassar
258
EuropeanReferenceSystem1989
ProjectionMethodCodes
Code
Mercator
12
SwissObliqueCylindrical
CassiniSoldner
13
ObliqueMercator
TransverseMercator
14
UTMProjection
TransverseMercatorSouthOriented
EllipsoidCodes
Code
Name
MajorAxis
MinorAxis
Airy1830
6377563.396
6356256.90890985
AiryModified1849
6377340.189
6356034.44761111
AustralianNationalSpheroid
6378160
6356774.71919531
Bessel1841
6377397.155
6356078.96261866
BesselModified
6377492.018
6356173.50851316
BesselNamibia
6377483.865
6356165.38276679
77
Forsk2014
Code
Name
MajorAxis
MinorAxis
Clarke1858
6378293.63924683
6356617.98173817
Clarke1866
6378206.4
6356583.8
Clarke1866Michigan
6378693.7040359
6357069.45104614
10
Clarke1880(Benoit)
6378300.79
6356566.43
11
Clarke1880(IGN)
6378249.2
6356515
12
Clarke1880(RGS)
6378249.145
6356514.86954978
13
Clarke1880(Arc)
6378249.145
6356514.96656909
14
Clarke1880(SGA1922)
6378249.2
6356514.99694178
15
Everest1830(1937Adjustment)
6377276.345
6356075.41314024
16
Everest1830(1967Definition)
6377298.556
6356097.5503009
17
Everest1830(1975Definition)
6377301.243
6356100.231
18
Everest1830Modified
6377304.063
6356103.03899315
19
GRS1980
6378137
6356752.31398972
20
Helmert1906
6378200
6356818.16962789
21
IndonesianNationalSpheroid
6378160
6356774.50408554
22
International1924
6378388
6356911.94612795
23
International1967
6378160
6356774.71919530
24
Krassowsky1940
6378245
6356863.01877305
25
NWL9D
6378145
6356759.76948868
26
NWL10D
6378135
6356750.52001609
27
Plessis1817
6376523
6355862.93325557
28
Struve1860
6378297
6356655.84708038
29
WarOffice
6378300.583
6356752.27021959
30
WGS84
6378137
6356752.31398972
31
GEM10C
6378137
6356752.31398972
32
OSU86F
6378136.2
6356751.51667196
33
OSU91A
6378136.3
6356751.61633668
34
Clarke1880
6378249.13884613
6356514.96026256
35
Sphere
6371000
6371000
ProjectionParameterIndices
Index
ProjectionParameter
Index
ProjectionParameter
UTMzonenumber
Scalefactoratorigin
Longitudeoforigin
Latitudeof1stparallel
Latitudeoforigin
Azimuthofcentralline
FalseEasting
Latitudeof2ndparallel
FalseNorthing
Anglefromrectifiedtoskewedgrid
7.1.4 CreatingaCoordinateSysteminAtoll
Atollprovidesalargedefaultcatalogueofcoordinatesystems.However,itispossibletoaddnewgeographicandcartographic
coordinatesystems.Newcoordinatesystemscanbecreatedfromscratchorinitialisedbasedonexistingones.
Tocreateanewcoordinatesystemfromscratch:
1. SelectDocument >Properties.ThePropertiesdialogueopens.
2. SelecttheCoordinatestab.
3. ClicktheBrowsebutton(
)totherightofProjection.TheCoordinateSystemsdialogueappears.
4. ClickNew.TheCoordinateSystemdialogueappears.
78
AT321_AM_E1
5. IntheCoordinateSystemdialogue:
a. Selectthecoordinatesystemscataloguetowhichyouwanttoaddthenewcoordinatesystem.
b. UnderGeneral,enteraNameforthenewcoordinatesystemandselectaUnit.InUse,youcanentercomments
aboutitsusage.Atollassignsthecodeautomatically.
c. Under Category, select the Type of coordinate system. Enter the longitude and latitude for a geographic
coordinatesystem,orthetypeofprojectionanditssetofassociatedparametersforacartographiccoordinate
system(falseeastingandnorthing,andthefirstandsecondparallels).
d. Under Geo, specify the meridian and choose a Datum for the coordinate system. The associated ellipsoid is
automaticallyselected.Youcanalsodescribeageodeticdatumbyselecting"<Customised>"intheDatumlist.In
this case, you must select an Ellipsoid and enter parameters (Dx, Dy, Dz, Rx, Ry, Rz, and S) needed for the
transformationofthedatumintoWGS84.
6. ClickOK.Thenewcoordinatesystemisaddedtotheselectedcoordinatesystemcatalogue.
To create a new coordinate system based on an existing system, select a coordinate system in the Coordinate Systems
dialoguebeforeclickingNewinstep 4.Thenewcoordinatesystemisinitialisedwiththevaluesoftheselectedcoordinate
system.
7.2 Units
IntheAtolldocuments,youcandefinemeasurementunitsforreception,transmission,antennagain,distance,heightand
offset, and temperature. You can accept the default measurement units, or you can change them using the document
propertiesdialogue.
TransmissionandReceptionPowerUnits
Dependingontheworkingenvironment,Atollcanuseeitheroneortwomeasurementunitsforthetransmission/reception
power.
Ifyouareworkingwithstandalonedocuments,i.e.,documentsnotconnectedtodatabases,thereisonlyonemeasurement
unitusedinAtollfordisplay.Itcorrespondstothetransmission/receptionpowerunitdefinedintheAtolldocument.
Ifyouareworkinginamultiuserenvironment,Atollusestwomeasurementunits:
A measurement unit for display in the Atoll document. It corresponds to the transmission/reception power unit
definedinthecurrentAtolldocument.Itisusedforthedisplayinthedialoguesandinthetables,e.g.,reception
thresholds (coverage prediction properties, microwave link properties, etc.), and received signal levels
(measurements,pointanalysis,coveragepredictions,microwavelinkproperties,etc.).
Aninternalmeasurementunitforthedatabase.Theinternalunitisthetransmission/receptionpowerunitstoredin
thedatabase.Itcorrespondstothetransmission/receptionpowerunitusedinthemasterAtolldocumentwhenthe
databaseiscreated.Usersworkingindocumentsconnectedtoadatabasecanmodifythetransmission/reception
powerunitandsavethischangeintheirdocumentslocally,buttheycannotmodifytheinternalpowerunitstoredin
thedatabase.OnlytheadministratorcanmodifyitmanuallybyeditingtheentryintheUnitstables.
AntennaGainUnits
Dependingontheworkingenvironment,Atollcanuseeitheroneortwomeasurementunitsfortheantennagain.
Ifyouareworkingwithstandalonedocuments,i.e.,documentsnotconnectedtodatabases,thereisonlyonemeasurement
unitusedinAtollfordisplay.ItcorrespondstotheantennagainunitdefinedintheAtolldocument.
Ifyouareworkinginamultiuserenvironment,Atollusestwomeasurementunits:
AmeasurementunitfordisplayintheAtolldocument.Itcorrespondstotheantennagainunitdefinedinthecurrent
Atolldocumentanditisusedforthedisplayinthedialoguesandinthetables.
Aninternalmeasurementunitforthedatabase.Theinternalunitistheantennagainunitstoredinthedatabase.It
correspondstotheantennagainunitusedinthemasterAtolldocumentwhenthedatabaseiscreated.Usersworking
indocumentsconnectedtoadatabasecanmodifytheantennagainunitandsavethischangeintheirdocuments
locally,buttheycannotmodifytheantennagainunitstoredinthedatabase.Onlytheadministratorcanmodifyit
manuallybyeditingtheentryintheUnitstables.
DistanceUnits
AtollusesthedistanceunitdefinedinthecurrentAtolldocumentasdisplayunitofthedistancesinthedialogues,inthe
tables,andinthestatusbar.
Metre is used as the internal measurement unit for the distance in all Atoll documents whether they are connected to
databasesornot.Theinternalmeasurementunitisnotstoredinthedatabaseandcannotbechanged.
79
Forsk2014
HeightandOffsetUnits
AtollusestheheightandoffsetunitdefinedinthecurrentAtolldocumentasdisplayunitoftheheightsandtheoffsetsinthe
dialogues,inthetables,andinthestatusbar.
MetreisusedastheinternalmeasurementunitfortheheightsandoffsetsinallAtolldocumentswhethertheyareconnected
todatabasesornot.Theinternalmeasurementunitisnotstoredinthedatabaseandcannotbechanged.
TemperatureUnits
AtollusesthetemperatureunitdefinedinthecurrentAtolldocumentasdisplayunitofthetemperaturesinthedialogues
andinthetables.
Degree Celsius is used as the internal measurement unit for the temperature in all Atoll documents whether they are
connectedtodatabasesornot.Theinternalmeasurementunitisnotstoredinthedatabaseandcannotbechanged.
7.3 BSICFormat
Dependingontheworkingenvironment,therecanbeeitheroneortwotypesofBSICformats.Ifyouareworkingwithstand
alonedocuments,i.e.,documentsnotconnectedtodatabases,thereisonlyoneBSICformat:
DisplayBSICformat
Ifyouareworkinginamultiuserenvironment,Atollusestwotypeofformats:
DisplayBSICformatfortheAtolldocument
InternalBSICformatforthedatabase
Thedisplayformatisusedforthedisplayindialogsandtables.Youcansetthedisplayformatforyourdocumentfromthe
Transmittersfolderscontextmenu.
TheinternalformatistheBSICformatstoredinadatabase.TheBSICformatsetbytheadministratorinthecentralAtoll
projectisstoredinthedatabasewhenthedatabaseiscreated,andcannotbemodifiedbyusers.Onlytheadministratorcan
modifytheinternalformatmanuallybyeditingthecorrespondingentryintheUnitstables.AllAtolldocumentsopenedfrom
adatabasewillhavetheinternalformatofthedatabaseastheirdefaultBSICformat.
Usersworkingondocumentsconnectedtoadatabasecanmodifytheformatintheirdocumentslocally,andsavethischange
intheirdocuments,buttheycannotmodifytheformatstoredinthedatabase.
80
Chapter8:GeographicData
AT321_AM_E1
8 GeographicData
Atollsupportsseveralgeographicdatatypes;DTM(DigitalTerrainModel),clutter,scannedimages,vectordata,trafficmaps,
population, and custom geographic data. Atoll offers import/export filters for the most commonly used geographic data
formats.
Thefollowingtablesummarizesthesupportedformatsandfilters:
FileFormat
Import
Export
BIL
GeographicDataTypes
Clutter
Heights
Both
8,16,or32
bit
8bit
TIFF
Both
8or16bit
8bit
8or16bit
Planet
Both
16bit
16bit
16bit
Userprofiledensity
Sectortrafficmaps
1,4,8or24
bit
Userprofileraster(16bit)
Userdensityraster(16bit)
BMP
Both
8bit
8bit
8bit
Userdensityraster(16,32
bit)
DXF
Import
Userprofiledensity
Sectortrafficmaps
SHP
Both
Userprofiledensity
Sectortrafficmaps
MapInfo
(MIF,TAB)
Both
Userprofiledensity
Sectortrafficmaps
ErdasImagine
(IMG)
Import
8,16,and
32bit
8bit
8,16,and
32bit
ArcViewGrid
(TXT)
Export
Text
Text
Text
AtollGeoData
(AGD)
Both
VerticalMapper
(GRD,GRC)
Both
ECW
Import
24bit
PNG
Both
All
All
PGWfiles
JPEG
Both
All
All
JGWfiles
TrafficMaps
Raster
Images
Clutter
Classes
WebMap
Services
8,16,or32
1,4,8or24 8,16,or32
bit
bit
bit
bit)
Clutter
Heights
HDRfiles
Userprofileraster(8bit),
1,4,8or24 8,16,or32
bit
bit
bit)
1to24bit
Yes
Yes
8or32bit
TFWfiles
indexfiles
Yes
BPWorBMWfiles
Yes
Yes
Vector
Yes
Yes
Vector
Yes
Yes
1,4,8or24 8,16,or32
bit
bit
bit)
Text
Text
Userprofiledensities
Sectortrafficmaps
DTM
Population
Vector
Data
Georeferencing
DTM
Clutter
Classes
Userprofileraster
Userdensityraster
Text
Vector
Raster
Images
Yes
Embeddeddata
Yes
Embeddeddata
Vector
Embeddeddata
ERSfiles
YoucanimportcustomgeographicdatatypesotherthanthoselistedaboveintoAtoll.Custommapscanbetakenintoaccount
inclutterstatisticsandcoveragepredictionreports.
CustomfileformatssupportedbyAtollare:
BIL(8,16,32bits)
TIFF(8,16,32bits)
BMP(8,32bits)
ErdasImagine(8,16,32bits)
MIF/TAB
SHP
VerticalMapper(GRD,GRC)
AGD
WLDfilescanbeusedforgeoreferencingforanytypeofbinaryrasterfile.
Thesmallestsupportedresolutionforrasterfilesis1 m.Thereisnorestrictiononthe
resolutionofimages.
DTM,clutterclasses,andclutterheightmapsmusthaveanintegerresolution.
AlltherastermapsyouwanttoimportinanATLdocumentmustberepresentedin
thesameprojectionsystem.
81
Forsk2014
8.1 GeographicHeaderFileFormats
Headerfilesareusedtodescribehowdataisorganisedwithinadatafile.Thissectioncoversthefollowingtopics:
"HDRHeaderFileforBILFiles"onpage 82
"TFWHeaderFileforTIFFFiles"onpage 83
"BPW/BMWHeaderFilesforBMPFiles"onpage 84
"PGWHeaderFileforPNGFiles"onpage 84
"JGWHeaderFileforJPGFiles"onpage 84
"GenericRasterHeaderFile"onpage 85
8.1.1 HDRHeaderFileforBILFiles
TheHDRfileisatextfilethatcontainsmetadatadescribingtheorganisationoftheBILfile.Theheaderfileismadeofrows,
eachrowhavingthefollowingformat:
keyword
value
wherekeywordcorrespondstoanattributetype,andvaluedefinestheattributevalue.
KeywordsrequiredbyAtollaredescribedbelow.Otherkeywordsareignored.
ulxmap
x coordinate of the centre of the upper-left pixel.
ulymap
y coordinate of the centre of the upper-left pixel.
xdim
x size in metre of a pixel.
ydim
y size in metre of a pixel.
ncols
Number of columns in the image.
nrows
Number of rows in the image.
nbits
Number of bits per pixel per band; 8 or 16 for DTMs or Clutter heights
(altitude in metres), 8 for clutter classes file (clutter code), 16 for
path loss matrices (path loss in dB, field value in dBm, dBV and DBV/m).
nbands
Number of spectral bands in the image, (1 for DTM and 8 bit pictures).
byteorder Byte order in which image pixel values are stored. Accepted values are M
(Motorola byte order) or I (Intel byte order).
layout
Must be bil.
bandrowbytes
Number of bytes per band per row.
totalrowbytes
Total number of bytes of data per row.
skipbytes Byte to be skipped in the image file in order to reach the beginning of
the image data. Default value is 0.
Fouradditionalkeywordscanoptionallybemanaged.
pixeltype Type of data read (in addition to the length)
Thiscanbe:
UNSIGNDINT
Undefined
8,16,24or32bits
SIGNEDINT
Integer
16or32bits
FLOAT
Real
32or64bits
Insomecases,thiskeywordcanbereplacedbydatatypedefinedasfollows:
datatype
Thiscanbe:
82
Type of data read (in addition to the length)
AT321_AM_E1
Un
Undefined
nbits(8,16,24or32bits)
In
Integer
nbits(16or32bits)
Rn
Real
nbits(32or64bits)
RGB24
Integer
3colourcomponentson24bits
Theotheroptionalkeywordsare:valueoffset,valuescale,andnodatavalue.
Bydefault,integerdatatypesarechosenwithrespecttothepixellength(nbits).
valueoffset
Real value to be added to the read value (Vread)
valuescale
Scaling factor to be applied to the read value
So,wehave V = Vread valuescale + valueoffset

nodatavalue
Value corresponding to NO DATA
DTMSample
Here,thedatais20 m.
nrows
1500
ncols
1500
nbands
nbits
8 or 16
byteorder M
layout
bil
skipbytes 0
ulxmap
975000
ulymap
1891000
xdim
20.00
ydim
20.00
ClutterClassesSample
nrows
1500
ncols
1500
nbands
nbits
byteorder M
layout
bil
skipbytes 0
ulxmap
975000
ulymap
1891000
xdim
20.00
ydim
20.00
8.1.2 TFWHeaderFileforTIFFFiles
TFWfilescontainthespatialreferencedataofassociatedTIFFfiles.TheTFWfilestructureissimple;itisanASCIItextfilethat
containssixlines.YoucanopenaTFWfileusinganyASCIItexteditor.TheTFWfilestructureisasfollows:
Line
Description
xdimensionofapixelinmapunits
2a
amountoftranslation
amountofrotation
negativeoftheydimensionofapixelinmapunits
83
Forsk2014
Line
a.
Description
xaxismapcoordinateofthecentreoftheupperleftpixel
yaxismapcoordinateofthecentreoftheupperleftpixel
Atolldoesnotusethelines2and3whenimportingaTIFFformatgeographicfile.
100.00
0.00
0.00
-100.00
60000.00
2679900.00
8.1.3 BPW/BMWHeaderFilesforBMPFiles
TheheaderfileisatextfilethatdescribeshoworganisedintheBMPfile.Theheaderfileismadeofrows,eachrowhaving
thefollowingdescription:
Line
Description
amountoftranslation
amountofrotation
AtollsupportsBPWandBMWheaderfileextensionsforImport,butexportsheaderswithBPWfileextensions.
100.00
0.00
0.00
-100.00
60000.00
2679900.00
8.1.4 PGWHeaderFileforPNGFiles
A PNG world file (PGW file) is a plain text file used by geographic information systems (GIS) to provide georeferencing
informationforrastermapimagesinPNGformat.Theworldfileparametersare:
Line
Description
amountoftranslation
amountofrotation
8.1.5 JGWHeaderFileforJPGFiles
A JPEG world file (JGW file) is a plain text file used by geographic information systems (GIS) to provide georeferencing
informationforrastermapimagesinJPEGformat.Theworldfileparametersare:
84
AT321_AM_E1
Line
Description
amountoftranslation
amountofrotation
8.1.6 GenericRasterHeaderFile
WLDisaheaderformatforAtollthatcanbeusedforanyrasterdatafileforgeoreferencing.Atthetimeofimportofanyraster
datafile,AtollcanusethecorrespondingWLDfiletoreadthegeoreferencinginformationrelatedtotherasterdatafile.The
WLDfilecontainsthespatialreferencedataofanyassociatedrasterdatafile.TheWLDfilestructureissimple;itisanASCII
textfilecontainingsixlines.YoucanopenaWLDfileusinganyASCIItexteditor.
TheWLDfileisatextfilethatdescribeshoworganisedintheassociatedrasterdatafile.Theheaderfileismadeofrows,each
rowhavingthefollowingdescription:
Line
Description
amountoftranslation
amountofrotation
ClutterClassesFileSample
100.00
0.00
0.00
-100.00
60000.00
2679900.00
85
86
Forsk2014
Chapter9:RadioDataFormats
AT321_AM_E1
9 RadioDataFormats
RadionetworkdatainAtollincludesthefollowing,dependingonthetechnologyusedinthenetworkbeingplanned:
Site:Thegeographiclocationoftransmitters(sectors,installedantennas,otherequipment).Asitecanhaveoneor
moretransmitters.
Antenna:Theradiationpatternsandgainsforantennasinstalledattransmitters.
Transmitter:Agroupofradiodevicesinstalledatasitewiththeretransmission/receptioncharacteristics(antennas,
feeders,TMAs,otherequipment).Atransmittercanhaveoneormorecellsorsubcells.
Cell:AnRFcarrieravailableatatransmitterinUMTS,CDMA2000,TDSCDMA,LTE,WiMAX,andWiFinetworks.Acell
isfullydefinedbythe"transmittercarrier"pair.Eachcellinthesenetworksisindependent,i.e.,hasitsownidentifier,
powerlevels,performancecharacteristics.
TRX:AnRFcarrieravailableatatransmitterinGSMnetworks.Atransceiver(TRX)cancarryoneARFCNwhichcan
correspondtotheBCCH(7traffictimeslots)orTCH(8traffictimeslots).
Subcell:AsubcellisagroupofTRXswiththesameradiocharacteristics.Asubcellisfullydefinedbythe"transmitter
TRXtype"pair.
Basestation:Thisisthegenericnameforacellsite("sitetransmittercell"or"sitetransmittersubcells").Technology
specificnamescanbeBTS,NodeB,eNodeB,etc.
RFrepeater:AnRFrepeaterreceives,amplifies,andretransmitsRFcarriersbothindownlinkanduplink.Therepeater
receivessignalsfromadonortransmitterwhichitretransmitsusingacoveragesideantennawithamplification.
Remoteantenna:Transmitterantennaslocatedataremotelocationwithrespecttothetransmitterssite.
Microwavelink:Apointtopointlinkusingmicrowavefrequenciesusedforbackhaulinradioaccessnetworksorfor
fixedwirelessaccess.
PMPmicrowavelink:Agroupofmicrowavelinksoriginatingfromacommonnodetoservemorethanonelocation.
Passive microwave repeater: A passive microwave repeater receives and retransmits microwave signals without
amplification.Passiverepeatersdonothavepowersourcesoftheirown.Activerepeaters,ontheotherhand,amplify
thereceivedsignal.Reflectorsareexamplesofpassiverepeaters.
9.1 XMLImport/ExportFormat
AllthedatatablesinanAtolldocumentcanbeexportedtoXMLfiles.Atollcreatesthefollowingfileswhendatatablesare
exportedtoXMLfiles:
Anindex.xmlfilewhichcontainsthemappingbetweenthedatatablesinAtollandtheXMLfilecreatedforeachtable.
OneXMLfileperdatatablewhichcontainsthedatatableformat(schema)andthedata.
When XML files are imported to a document, the table and field definitions are not modified, i.e., the Networks and
CustomFieldstablesareexportedtoXMLfilebutarenotimported.
ThefollowingsectionsdescribethestructuresoftheXMLfilescreatedatexport.
9.1.1 Index.xmlFileFormat
Theindex.xmlfilestoresthesystem(GSM,UMTS,etc.)andthetechnology(TDMA,CDMA,etc.)ofthedocument,andthe
versionofAtollusedforexportingthedatatablestoXMLfiles.Italsocontainsthemappingbetweenthedatatablesinthe
AtolldocumentandtheXMLfilecorrespondingtoeachdatatable.
Theroottag<Atoll_XML_Config...>oftheindex.xmlfilecontainsthefollowingattributes:
Attribute
Description
Atoll_File_System
CorrespondstotheSYSTEM_fieldoftheNetworkstableoftheexporteddocument
Atoll_File_Technology
CorrespondstotheTECHNOLOGYfieldoftheNetworkstableoftheexporteddocument
Atoll_File_Version
CorrespondstotheAtollversion
TheindexfilealsocontainsthemappingbetweenthetablesexportedfromAtollandtheXMLfilescorrespondingtoeach
table.ThislistissortedintheorderinwhichtablesmustbeimportedinAtoll.
Thelistiscomposedof<XML_Table.../>tagswiththefollowingattributes:
Attribute
Description
XML_File
CorrespondstotheexportedXMLfilename(e.g.,"Sites.xml")
Atoll_Table
CorrespondstotheexportedAtolltablename(e.g.,"Sites")
Asampleextractoftheindex.xmlisgivenbelow:
87
Forsk2014
<Atoll_XML_Config Atoll_File_System="UMTS" Atoll_File_Technology="CDMA"

Atoll_File_Version="3.x.x build xxxx">
<XML_Table XML_File="CustomFields.xml" Atoll_Table="CustomFields" />
<XML_Table XML_File="CoordSys.xml" Atoll_Table="CoordSys" />
...
</Atoll_XML_Config>
Notethatnoclosingtag</XML_Table>isrequired.
9.1.2 XMLFileFormat
AtollcreatesanXMLfileperexporteddatatable.ThisXMLfilehastwosections,oneforstoringthedescriptionofthetable
structure,andthesecondforthedataitself.TheXMLfileusesthestandardXMLrowsetschema(schemaincludedintheXML
filebetween<s:Schemaid=RowsetSchema>and</s:Schema>tags).
RowsetSchema
TheXMLroottagforXMLfilesusingtherowsetschemaisthefollowing:
<xml xmlns:s='uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882'
xmlns:dt='uuid:C2F41010-65B3-11d1-A29F-00AA00C14882'
xmlns:rs='urn:schemas-microsoft-com:rowset'
xmlns:z='#RowsetSchema'>
Theschemadefinitionfollowstheroottagandisenclosedbetweenthefollowingtags:
<s:Schema id=RowsetSchema>
<!-Schema is defined here, using <s:ElementType> and <s:AttributeType> tags ->
</s:Schema>
Intherowsetschema,aftertheschemadescription,thedataareenclosedbetween<rs:data>and</rs:data>.
Betweenthesetags,eachrecordishandledbya<z:row/>taghavingitsattributessettotherecordfieldvaluessinceinthe
rowsetschema,valuesarehandledbyattributes.Notethatnoclosingtag</z:row>isrequired.
AsampleextractofaSites.xmlfilecontainingtheSitestablewithonlyonesiteisgivenbelow:
<xml xmlns:s='uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882'
xmlns:dt='uuid:C2F41010-65B3-11d1-A29F-00AA00C14882'
xmlns:rs='urn:schemas-microsoft-com:rowset'
xmlns:z='#RowsetSchema'>
<s:Schema id='RowsetSchema'>
<s:ElementType name='row' content='eltOnly' rs:updatable='true'>
<s:AttributeType name='NAME' rs:number='1' rs:maydefer='true'
rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='NAME'
rs:keycolumn='true'>
<s:datatype dt:type='string' dt:maxLength='50'/>
</s:AttributeType>
<s:AttributeType name='LONGITUDE' rs:number='2' rs:maydefer='true'
rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='LONGITUDE'>
<s:datatype dt:type='float' dt:maxLength='8' rs:precision='15'
rs:fixedlength='true'/>
</s:AttributeType>
<s:AttributeType name='LATITUDE' rs:number='3' rs:maydefer='true'
rs:writeunknown='true' rs:basetable='Sites' rs:basecolumn='LATITUDE'>
<s:datatype dt:type='float' dt:maxLength='8' rs:precision='15'
</s:AttributeType>
88
AT321_AM_E1
<s:AttributeType name='ALTITUDE' rs:number='4' rs:nullable='true'

rs:maydefer='true' rs:writeunknown='true' rs:basetable='Sites'
rs:basecolumn='ALTITUDE'>
<s:datatype dt:type='r4' dt:maxLength='4' rs:precision='7'
</s:AttributeType>
<s:AttributeType name='COMMENT_' rs:number='5' rs:nullable='true'
rs:maydefer='true' rs:writeunknown='true' rs:basetable='Sites'
rs:basecolumn='COMMENT_'>
<s:datatype dt:type='string' dt:maxLength='255'/>
</s:AttributeType>
<s:extends type='rs:rowbase'/>
</s:ElementType>
</s:Schema>
<rs:data>
<rs:insert>
<z:row NAME='Site0' LONGITUDE='8301' LATITUDE='-9756'/>
</rs:insert>
</rs:data>
</xml>
9.2 RF2DAntennaPatternFormat
ThissectiondescribestheformatoftheDIAGRAMfieldoftheAntennastable.Thisfieldstorestheantennadiagramsina2D
(anglevs.attenuation)format.ThisistheformatofthecontentsoftheDIAGRAMfieldoftheAntennastablewhenitiscopied
from,pastedto,importedto(fromTXTorCSVfiles),andexportedfrom(fromTXT,CSV,orXLSfiles)theAntennastable.
AntennapatternscanalsobeimportedinPlanet2Dformatantennafilesand3Dantennafiles.Thefileformatrequiredfor
3Dantennafileimportisdescribedin"ImportFormatof3DAntennaPatternTextFiles"onpage 91.
Theformatof2DantennapatternscontainingcopolardiagramsonlycanbeunderstoodfromFigure 9.1onpage 89.
Pattern
Discriptor 1
Co-polar Horizontal Diagram
Pattern
Discriptor 2
Co-polar Vertical Diagram
End
2 0 0 360 0 0 1 0 2 0.1 1 0 360 0 0 1 0.1 0

Figure 9.1:2DRFAntennaPatternFormatContainingCopolarDiagramsOnly
ThecontentsoftheDIAGRAMfieldareformattedasfollows:
PatternDescriptor1:Spaceseparatedlistofparameters.
Firstentry:Thenumberofcopolardiagrams.Forexample,2.
Secondentry:Firstcopolardiagramtype=0forazimuth(horizontal)diagram.
Thirdentry:Theelevationangleoftheazimuthdiagram.
Fourthentry:Thenumberofangleattenuationpairsinthefirstcopolardiagram.Forexample,360.
CopolarHorizontalDiagram:Horizontalcopolardiagram(thesecondentryintheprecedingdescriptoris0).The
formatisspaceseparatedangleattenuationpairs.Forexample,001020.1....
Firstentry:Secondcopolardiagramtype=1forelevation(vertical)diagram.
Secondentry:Theazimuthangleoftheelevationdiagram.
Thirdentry:Thenumberofangleattenuationpairsinthesecondcopolardiagram.Forexample,360.
CopolarVerticalDiagram:Verticalcopolardiagram(thefirstentryintheprecedingdescriptoris1).Theformatis
spaceseparatedangleattenuationpairs.Forexample,0010.1....
End:Thenumbercrosspolardiagrams=0.
The format of 2D antenna patterns containing copolar and crosspolar diagrams can be understood from Figure 9.2 on
page 90.
89
Forsk2014
Pattern
Discriptor 1
Co-polar Horizontal Diagram
Pattern
Discriptor 3
Pattern
Discriptor 2
Cross-polar Horizontal Diagram
Pattern
Discriptor 4
Co-polar Vertical Diagram
Cross-polar Vertical Diagram
2 0 0 360 0 0 1 0 2 0.1 1 0 360 0 0 1 0.1

2 0 0 360 0 0 1 0 2 0.1 1 0 360 0 0 1 0.1
Figure 9.2:2DRFAntennaPatternFormatContainingCopolarandCrosspolarDiagrams
ThecontentsoftheDIAGRAMfieldareformattedasfollows:
Firstentry:Thenumberofcopolardiagrams.Forexample,2.
Secondentry:Firstcopolardiagramtype=0forazimuth(horizontal)diagram.
Fourthentry:Thenumberofangleattenuationpairsinthefirstcopolardiagram.Forexample,360.
CopolarHorizontalDiagram:Horizontalcopolardiagram(thesecondentryintheprecedingdescriptoris0).The
formatisspaceseparatedangleattenuationpairs.Forexample,001020.1....
Firstentry:Secondcopolardiagramtype=1forelevation(vertical)diagram.
Thirdentry:Thenumberofangleattenuationpairsinthesecondcopolardiagram.Forexample,360.
CopolarVerticalDiagram:Verticalcopolardiagram(thefirstentryintheprecedingdescriptoris1).Theformatis
spaceseparatedangleattenuationpairs.Forexample,0010.1....
Firstentry:Thenumberofcrosspolardiagrams.Forexample,2.
Secondentry:Firstcrosspolardiagramtype=0forazimuth(horizontal)diagram.
Fourthentry:Thenumberofangleattenuationpairsinthefirstcrosspolardiagram.Forexample,360.
CrosspolarHorizontalDiagram:Horizontalcrosspolardiagram(thesecondentryintheprecedingdescriptoris0).
Theformatisspaceseparatedangleattenuationpairs.Forexample,001020.1....
Firstentry:Secondcrosspolardiagramtype=1forelevation(vertical)diagram.
Thirdentry:Thenumberofangleattenuationpairsinthesecondcrosspolardiagram.Forexample,360.
CrosspolarVerticalDiagram:Verticalcrosspolardiagram(thefirstentryintheprecedingdescriptoris1).Theformat
isspaceseparatedangleattenuationpairs.Forexample,0 0 1 0.1....
Youcanusea3rdpartysoftwareordevelopatooltoconvertthecontentsoftheDIAGRAMfieldintobinary.Inbinary,each
antennaisdescribedbyaheaderandalistofvaluepairs.
Theheaderisdefinedasfollows:
flag:(Integer,32bits)1foromnidiagrams,0fordirectional
num:(Shortinteger,16bits)Numberofdiagrams(0,1,2,3,4)
siz0:(Shortinteger,16bits)Sizeofthefirstdiagram(horizontalcopolarsection,elevation=0)
siz1:(Shortinteger,16bits)Sizeoftheseconddiagram(verticalcopolarsection,azimuth=0)
siz2:(Shortinteger,16bits)Sizeofthethirddiagram(horizontalcrosspolar)
siz3:(Shortinteger,16bits)Sizeofthefourthdiagram(verticalcrosspolar)
prec:(Shortinteger,16bits)Precisionofthefollowinganglevalues(100)
Thenfollowsthecontentofeachofthedefineddiagrams,i.e.,thediagramswhosesizes(siz0,siz1,siz2,siz3)arenotzero.
Eachdiagramconsistsofalistofvaluepairs.Thenumberofvaluepairsinalistdependsonthevalueofthesiz0,siz1,siz2,
andsiz3parameters.Forexample,siz2=5meanstherearefivevaluepairsinthethirddiagram.
Thevaluepairsineachlistare:
ang: (Short integer, 16 bits) The first component of the value pair is the angle in degrees multiplied by 100. For
example,577means5.77degrees.
loss:(Shortinteger,16bits)ThesecondcomponentofthevaluepairisthelossindBforthegivenangleang.
Allthelistsofvaluepairsareconcatenatedwithoutaseparator.
90
AT321_AM_E1
9.3 ImportFormatof3DAntennaPatternTextFiles
Textfilescontaining3DantennapatternsthatcanbeimportedinAtollmusthavethefollowingformat:
Header:Thetextfilecancontainaheaderwithadditionalinformation.Whenyouimporttheantennapatternyoucan
indicatetherownumberinthefilewheretheheaderendsandtheantennapatternbegins.
AntennaPattern:Eachrowcontainsthreevaluestodescribethe3Dantennapattern.Thecolumnscontainingthe
valuescanbeinanyorder:
Azimuth:Allowedrangeofvaluesisfrom0to360.Thesmallestincrementallowedis1.
Tilt:Allowedrangeofvaluesisfrom90to90orfrom0to180.Thesmallestincrementallowedis1.
Attenuation:TheattenuationindB.
9.4 Microwave2DAntennaPatternFormat
ThissectiondescribestheformatofthePATTERNfieldoftheMWAntennastable.Thisfieldstorestheantennadiagramsina
2D(anglevs.attenuation)format.ThisistheformatofthecontentsofthePATTERNfieldoftheMWAntennastablewhenit
is copied from, pasted to, imported to (from TXT or CSV files), and exported from (from TXT, CSV, or XLS files) the MW
Antennastable.
AntennapatternscanalsobeimportedinPlanet2Dformatantennafilesand3Dantennafiles.Thefileformatrequiredfor
3Dantennafileimportisdescribedin"ImportFormatof3DAntennaPatternTextFiles"onpage 91.
Theformatof2DantennapatternscanbeunderstoodfromFigure 9.3onpage 91.
Pattern
Discriptor 1
Co-polar H-V Diagram
Pattern
Discriptor 2
Co-polar H-H Diagram
Pattern
Discriptor 3
Cross-polar H-V Diagram
Pattern
Discriptor 4
Cross-polar H-H Diagram
Pattern
Discriptor 5
Co-polar V-V Diagram
Pattern
Discriptor 6
Co-polar V-H Diagram
Pattern
Discriptor 7
Cross-polar V-V Diagram
Pattern
Discriptor 8
Cross-polar V-H Diagram
4 0 1 0 360 0 0 1 0.5 ... 0 0 0 360 0 0 1 0.5 ...

1 1 0 360 0 0 1 0.5 ... 1 0 0 360 0 0 1 0.5 ...
4 0 1 0 360 0 0 1 0.5 ... 0 0 0 360 0 0 1 0.5 ...
1 1 0 360 0 0 1 0.5 ... 1 0 0 360 0 0 1 0.5 ...
Figure 9.3:2DMicrowaveAntennaPatternFormat
ThecontentsofthePATTERNfieldareformattedasfollows:
Firstentry:ThenumberofH_polarisationdiagrams.Forexample,4.
Secondandthirdentries:Firstdiagramtype=01,forcopolarHVdiagram("ELHH"inAtoll).
Fourthentry:Theelevationangleoftheazimuthdiagram.
Fifthentry:Thenumberofangleattenuationpairsinthefirstcopolardiagram.Forexample,360.
CopolarHVDiagram:CopolarHVdiagram(thesecondandthirdentriesintheprecedingdescriptorare01).
Firstandsecondentries:Seconddiagramtype=00,forcopolarHHdiagram("HH"inAtoll).
Thirdentry:Theazimuthangleoftheelevationdiagram.
91
Forsk2014
Fourthentry:Thenumberofangleattenuationpairsinthesecondcopolardiagram.Forexample,360.
CopolarHHDiagram:CopolarHHdiagram(thefirstandsecondentriesintheprecedingdescriptorare00).
Firstandsecondentries:Thirddiagramtype=11,forcrosspolarHVdiagram("ELVH"inAtoll).
Fourthentry:Thenumberofangleattenuationpairsinthethirdcopolardiagram.Forexample,360.
CrosspolarHVDiagram:CrosspolarHVdiagram(thesecondandthirdentriesintheprecedingdescriptorare01).
Firstandsecondentries:Fourthdiagramtype=10,forcrosspolarHHdiagram("VH"inAtoll).
Fourthentry:Thenumberofangleattenuationpairsinthefourthcopolardiagram.Forexample,360.
CrosspolarHHDiagram:CrosspolarHHdiagram(thefirstandsecondentriesintheprecedingdescriptorare00).
Firstentry:ThenumberofV_polarisationcrosspolardiagrams.Forexample,4.
Secondandthirdentries:Firstdiagramtype=01,forcopolarVVdiagram("ELVV"inAtoll).
Fourthentry:Theelevationangleoftheazimuthdiagram.
Fifthentry:Thenumberofangleattenuationpairsinthefirstcrosspolardiagram.Forexample,360.
CopolarVVDiagram:CopolarVVdiagram(thefirstandsecondentriesintheprecedingdescriptorare11).
Firstandsecondentries:Seconddiagramtype=00,forcopolarVHdiagram("VV"inAtoll).
Fourthentry:Thenumberofangleattenuationpairsinthesecondcrosspolardiagram.Forexample,360.
CopolarVHDiagram:CopolarVHdiagram(thefirstandsecondentriesintheprecedingdescriptorare10).
Firstandsecondentries:Thirddiagramtype=11,forcrosspolarVVdiagram("ELHV"inAtoll).
Fourthentry:Thenumberofangleattenuationpairsinthethirdcrosspolardiagram.Forexample,360.
CrosspolarVVDiagram:CrosspolarVVdiagram(thefirstandsecondentriesintheprecedingdescriptorare11).
Firstandsecondentries:Fourthdiagramtype=10,forcrosspolarVHdiagram("HV"inAtoll).
Fourthentry:Thenumberofangleattenuationpairsinthefourthcrosspolardiagram.Forexample,360.
CrosspolarVHDiagram:CrosspolarVHdiagram(thefirstandsecondentriesintheprecedingdescriptorare10).
9.5 PathLossMatrixFileFormat
Whenpathlossmatricesarestoredexternally,i.e.,outsidetheATLfile,thepathlossmatricesfoldercontainsapathloss.dbf
filecontainingthecalculationparametersofthetransmittersandoneLOS(pathlossresults)filepercalculatedtransmitter.
ThepathlossmatricesfolderalsocontainsaLowResfolderwithanotherpathloss.dbffileandoneLOS(pathlossresults)file
pertransmitterthathasanextendedpathlossmatrix.
Theformatsofthepathloss.dbfandLOSfilesaredescribedhere.
9.5.1 Pathloss.dbfFileFormat
Thepathloss.dbffilehasastandardDBF(dBaseIII)format.ThefilecanbeopenedinMicrosoftAccess,butitshouldnotbe
modifiedwithoutconsultingtheForskcustomersupport.
Forgeneralinformation,theformatofDBFfilesinanyXbaselanguageisasfollows:
Notationsusedinthefollowingtables:FS=FlagShip;D3=dBaseIII+;Fb=FoxBase;D4=
dBaseIV;Fp=FoxPro;D5=dBaseV;CL=Clipper
92
AT321_AM_E1
DBFStructure
Byte
Description
0...n
DBFheader(seenextpartforsize,byte8)
Remarks
n+1
1strecordoffixedlength(seenextparts);2ndrecord(seenextpartforsize,byte10);last
record
last
optional:0x1a(eofbyte)
If.dbfisnotempty
DBFHeader
TheDBFheadersizeisvariableanddependsonthefieldcount.
Byte
Size
Contents
Description
Appliesto
00
0x03
plain.dbf
FS,D3,D4,D5,Fb,Fp,CL
0x04
plain.dbf
D4,D5(FS)
0x05
plain.dbf
D5,Fp(FS)
0x43
with.dbvmemovarsize
FS
0xB3
with.dbvand.dbtmemo
FS
0x83
with.dbtmemo
FS,D3,D4,D5,Fb,Fp,CL
0x8B
with.dbtmemoinD4format
D4,D5
0x8E
withSQLtable
D4,D5
0xF5
with.fmpmemo
Fp
01
YYMMDD
Lastupdatedigits
All
04
ulong
Numberofrecordsinfile
All
08
ushort
Headersizeinbytes
All
10
ushort
Recordsizeinbytes
All
12
0,0
Reserved
All
14
0x01
Begintransaction
D4,D5
0x00
EndTransaction
D4,D5
0x00
ignored
FS,D3,Fb,Fp,CL
0x01
Encrypted
D4,D5
0x00
normalvisible
All
15
16
12
0(1)
multiuserenvironmentuse
D4,D5
28
0x01
productionindexexists
Fp,D4,D5
0x00
indexupondemand
All
29
languagedriverID
D4,D5
0x01
codepage437DOSUSA
Fp
0x02
codepage850DOSMultiling
Fp
30
32
n*32
+1
0x03
codepage1251WindowsANSI
Fp
0xC8
codepage1250WindowsEE
Fp
0x00
ignored
FS,D3,Fb,Fp,CL
0,0
reserved
All
0x0D
FieldDescriptor(seenextparagraph)
all
HeaderRecordTerminator
all
FielddescriptorarrayintheDBFheader(32bytesforeachfield):
Byte
Size
Contents
Description
Appliesto
11
ASCI
fieldname,0x00termin
all
11
ASCI
fieldtype(seenextparagraph)
all
12
n,n,n,n
Fldaddressinmemory
D3
93
Byte
Forsk2014
Size
Contents
Description
Appliesto
n,n,0,0
offsetfromrecordbegin
Fp
0,0,0,0
ignored
FS,D4,D5,Fb,CL
16
byte
Fieldlength,bin(seenextparagraph)
all\FS,CL:forCfieldtype
17
byte
decimalcount,bin
all/bothusedforfldlng
18
0,0
reserved
all
20
byte
WorkareaID
D4,D5
0x00
unused
FS,D3,Fb,Fp,CL
multiuserdBase
D3,D4,D5
21
n,n
0,0
ignored
FS,Fb,Fp,CL
23
0x01
SetFields
D3,D4,D5
0x00
ignored
FS,Fb,Fp,CL
all
24
0...0
reserved
31
0x01
Fieldisin.mdxindex
D4,D5
0x00
ignored
FS,D3,Fb,Fp,CL
FieldtypeandsizeintheDBFheader,fielddescriptor(1byte):
Size
Type
Description/Storage
Appliesto
C1...n
Char
ASCII(OEMcodepagechars)
rest=space,not\0term.
all
FS
n=1...32kb(usingdecicount)
Fp,CL
n=1...254
all
D8
Date
8ASCIIdigits(0...9)intheYYYYMMDDformat
all
F1...n
Numeric
ASCIIdigits(.0123456789)
variablepos.offloat.point
n=1...20
FS,D4,D5,Fp
N1...n
Numeric
ASCIIdigits(.0123456789)
fixposit/nofloat.point
all
n=1...20
FS,Fp,CL
n=1...18
D3,D4,D5,Fb
Logical
ASCIIchars(YyNnTtFfspace)
FS,D3,Fb,Fp,CL
ASCIIchars(YyNnTtFf?)
D4,D5(FS)
Memo
10digitsrepres.thestartblockposit.in.dbtfile,or10
spacesifnoentryinmemo
all
V10
Variable
Variable,bin/ascdatain.dbv
4bytesbin=startposinmemo
4bytesbin=blocksize
1byte=subtype
1byte=reserved(0x1a)
10spacesifnoentryin.dbv
FS
P10
Picture
binarydatain.ftp
structurelikeM
Fp
B10
Binary
binarydatain.dbt
structurelikeM
D5
G10
General
OLEobjects
structurelikeM
D5,Fp
22
shortint
binaryintmax+/32767
FS
44
longint
binaryintmax+/2147483647
FS
88
double
binarysigneddoubleIEEE
FS
L1
M10
EachDBFrecord(fixedlength):
94
n=1...64kb(usingdecicount)
AT321_AM_E1
Byte
Size
Description
Appliesto
deletedflag"*"ornotdeleted""
All
1n
xtimescontentsoffields,fixedlength,unterminated.
Forn,see(2)byte1011
All
9.5.2 Pathloss.dbfFileContents
TheDBFfileprovidesinformationthatisneededtocheckvalidityofeachpathlossmatrix.
Field
Type
Description
TX_NAME
Text
Nameofthetransmitter
FILE_NAME
Text
Name(andoptionally,path)of.losfile
MODEL_NAME
Text
Nameofpropagationmodelusedtocalculatepathloss
MODEL_SIG
Text
Signature(identitynumber)ofmodelusedincalculations.Youcancheckitinthe
propagationmodelproperties(Generaltab).
TheModel_SIGisusedforthepurposeofvalidity.AuniqueModel_SIGisassignedto
eachpropagationmodel.Whenmodelparametersaremodified,theassociatedmodel
IDchanges.ThisenablesAtolltodetectpathlossmatrixinvalidity.Inthesameway,two
identicalpropagationmodelsindifferentprojectsdonothavethesamemodelIDa.
ULXMAP
Float
Xcoordinateofthetopleftcornerofthepathlossmatrixupperleftpixel
ULYMAP
Float
Ycoordinateofthetopleftcornerofthepathlossmatrixupperleftpixel
RESOLUTION
Float
Resolutionofpathlossmatrixinmetre
NROWS
Float
Numberofrowsinpathlossmatrix
NCOLS
Float
Numberofcolumnsinpathlossmatrix
FREQUENCY
Float
Frequencyband
TILT
Float
Transmitterantennamechanicaltilt
AZIMUTH
Float
Transmitterantennaazimuth
TX_HEIGHT
Float
Transmitterheightinmetre
TX_POSX
Float
Xcoordinateofthetransmitter
TX_POSY
Float
Ycoordinateofthetransmitter
ALTITUDE
Float
Groundheightabovesealevelatthetransmitterinmetre
RX_HEIGHT
Float
Receiverheightinmetre
ANTENNA_SI
Float
Logicalnumberreferringtoantennapattern.Antennaswiththesamepatternwillhave
thesamenumber.
MAX_LOS
Float
Maximumpathlossstatedin1/16dB.Thisinformationisused,whennocalculation
radiusisset,tocheckthematrixvalidity.
CAREA_XMIN
Float
Lowestxcoordinateofcentrepixellocatedonthecalculationradiusb
CAREA_XMAX
Float
Highestxcoordinateofcentrepixellocatedonthecalculationradius
CAREA_YMIN
Float
Lowestycoordinateofcentrepixellocatedonthecalculationradius
CAREA_YMAX
Float
Highestycoordinateofcentrepixellocatedonthecalculationradius
WAREA_XMIN
Float
Lowestxcoordinateofcentrepixellocatedinthecomputationzonec
WAREA_XMAX
Float
Highestxcoordinateofcentrepixellocatedinthecomputationzone
WAREA_YMIN
Float
Lowestycoordinateofcentrepixellocatedinthecomputationzone
WAREA_YMAX
Float
Highestycoordinateofcentrepixellocatedinthecomputationzone
LOCKED
Boolean
Lockingstatus
0:pathlossmatrixisnotlocked
1:pathlossmatrixislocked.
Boolean
Atollindicatesiflossesduetotheantennapatternaretakenintoaccountinthepath
lossmatrix.
0:antennalossesnottakenintoaccount
1:antennalossesincluded
INC_ANT
95
a.
Forsk2014
Inordertobenefitfromthecalculationsharingfeature,usersmustretrievethepropagationmodelsfromthesame
central database. This can be done using the Open from database command for a new document or the Refresh
commandforanexistingone.Otherwise,Atollgeneratesdifferentmodel_ID(evenifsameparametersareappliedon
thesamekindofmodel)andcalculationsharingbecomeunavailableduetoinconsistency.
ThesecoordinatesenableAtolltodeterminetheareaofcalculationforeachtransmitter.
ThesecoordinatesenableAtolltodeterminetherectangleincludingthecomputationzone.
b.
c.
9.5.3 LOSFileFormat
The LOS (path loss results) files are binary files with a standard rowcolumn structure. Data are stored starting from the
southwesttothenortheastcornerofthearea.Thefilecontains16bitsignedintegervaluesintherange[32768;+32767]
witha1/16 dBprecision."Nodata"valuesarerepresentedby+32767.
9.6 PathLossTuningFileFormat
AtollcantunepathlossescalculatedbypropagationmodelsusingCWmeasurementsordrivetestData.Pathlossesaretuned
bymergingmeasurementdatawithpropagationresultsonpixelscorrespondingtothemeasurementpointsandthepixelsin
thevicinity.Pathlossessurroundingthemeasurementpointsaresmoothedforhomogeneity.
Measuremmentpathsthatareusedforpathlosstuningarestoredasacatalogueinafoldercontainingapathloss.dbffileand
onePTS(pathlosstuning)filepertransmitter.Atuningfilecancontainseveralmeasurementpaths.
Formoreinformationonthepathlosstuningalgorithm,seetheTechnicalReferenceGuide.
9.6.1 Pathloss.dbfFileFormat
See"Pathloss.dbfFileFormat"onpage 92.
9.6.2 Pathloss.dbfFileContents
TheDBFfileprovidesinformationaboutthemeasuredtransmittersinvolvedinthetuning.
Field
Type
Description
TX_NAME
Text
FILE_NAME
Text
Name(andoptionally,path)of.ptsfile
AREA_XMIN
Float
Notused
AREA_XMAX
Float
Notused
AREA_YMIN
Float
Notused
AREA_YMAX
Float
Notused
9.6.3 PTSFileFormat
ThePTS(pathlosstuning)filescontainaheaderandthelistofmeasurementpoints.
Header:
4bytes:version
4bytes:flag(canbeusedtomanageflagslikeactiveflag)
50bytes:GUID
4bytes:numberofpoints
255bytes:originalmeasurementname(withprefix"Num"fordrivetestdataand"CW"forCWmeasurements)
256bytes:comments
4bytes:X_RADIUS
4bytes:Y_RADIUS
4bytes:gain=measurementgainlosses
4bytes:globalerror
4bytes:rxheight
4bytes:frequency
8bytes:txPosition
Listofmeasurementpoints:
96
4bytes:X
AT321_AM_E1
4bytes:Y
4bytes:measurementvalue
4bytes:incidenceangle.
9.7 InterferenceMatrixFileFormats
InterferencematricesareusedbyGSM,LTE,andWiMAXAFPs(automaticfrequencyplanningtools).Interferencematrices
canbeimportedandexportedusingthefollowingformats:
GSM:CLC,IM0,IM1,IM2
LTEandWiMAX:IM2,TXT,CSV
Interferencematrixfilesmustcontaininterferenceprobabilityvaluesbetween0and1,andnotinprecentage(between0and
100%).Wheninterferencematrixfilesareimported,Atolldoesnotchecktheirvalidityandimportsinterferenceprobability
valuesforloadedtransmittersonly.
Inthefollowingformatdescriptionsandsamples,linesstartingwiththe"#"areconsideredascomments.
InGSMinterferencematrices:
The interferer TRX type is not specified and is always considered to be BCCH.
Subcells have different powers defined as offsets with respect to the BCCH. For
subcells other than the BCCH, if the power offset of a subcell is X dB, then its
interferencehistogramwillbeshiftedbyX dBwithrespecttotheBCCHinterference
histogram.
IfnopoweroffsetisdefinedontheinterferedTRXtype,itispossibletoset"All".
For each interfered subcellinterferer subcell pair, Atoll saves probabilities for
severalC/Ivalues(6to24values),includingfivefixedones:9,1,8,14,and22 dB.
BetweentwofixedC/Ivalue,therecanbeuptothreeadditionalvalues(thisnumber
dependsontheprobabilityvariationbetweenthefixedvalues).TheC/Ivalueshave
0.5 dBaccuracyandprobabilityvaluesarecalculatedandstoredwithanaccuracyof
0.002 for probabilities between 1 and 0.05, and with an accuracy of 0.0001 for
probabilitieslowerthan0.05.
9.7.1 CLCFormat(OneValueperLine)
TheCLCformatuseswoASCIItextfiles:aCLCfileandaDCTfile.InterferencematricesareimportedbyselectingtheCLCfile
toimport.AtolllooksfortheassociatedDCTfileinthesamedirectoryandusesittodecodetransmitteridentifiers.IfnoDCT
fileisavailable,Atollassumesthatthetransmitteridentifiersarethetransmitternames,andthecolumns1and2oftheCLC
filemustcontainthenamesoftheinterferedandinterferingtransmittersinsteadoftheiridentificationnumbers.
9.7.1.1 CLCFileFormat
TheCLCfileconsistsoftwoparts.Thefirstpartisaheaderusedforformatidentification.Itmuststartwithandcontainthe
followinglines:
# Calculation Results Data File.
# Version 1.1, Tab separated format. Commented lines start with #.
Thesecondpartdetailsinterferencehistogramofeachinterferedsubcellinterferingsubcellpair.Thelinesaftertheheader
areconsideredascommentsiftheystartwith"#".Ifnot,theymusthavethefollowingformat:
<Column1><tab><Column2><tab><Column3><tab><Column4><tab><Column5><newline>
The5tabseparatedcolumnsaredefinedinthetablebelow:
Column
Name
Description
Column1
Interferedtransmitter
Identificationnumberoftheinterferedtransmitter.Ifthecolumnisempty,
itsvalueisidenticaltotheoneofthelineabove.
Column2
Interferingtransmitter
Identificationnumberoftheinterferertransmitter.Ifthecolumnisnull,its
valueisidenticaltotheoneofthelineabove.
Column3
InterferedTRXtype
Interferedsubcell.Ifthecolumnisnull,itsvalueisidenticaltotheoneofthe
lineabove.Inordertosavestorage,allsubcellswithnopoweroffsetarenot
duplicated(e.g.BCCH,TCH).
97
Forsk2014
Column
Name
Column4
C/Ithreshold
C/Ivalue.Thiscolumncannotbenull.
ProbabilityC/I>Threshold
ProbabilitytohaveC/Ithevaluespecifiedincolumn4(C/Ithreshold).This
fieldmustnotbeempty.
Column5
Description
Thecolumns1,2,and3mustbedefinedonlyinthefirstlineofeachhistogram.
Sample
# Version 1.1,
# Remark:
Tab separated format. Commented lines start with #.
C/I results do not incorporate power offset values.
# Fields are:
##------------#------------#------------#-----------#------------------#
#| Interfered | Interfering| Interfered | C/I
#| Transmitter| Transmitter| Trx type
| Probability
| Threshold | C/I >= Threshold |
##------------#------------#------------#-----------#------------------#
#
# Warning, The parameter settings of this header can be wrong if
# the "export" is performed following an "import". They
# are correct when the "export" follows a "calculate".
#
# Service Zone Type is "Best signal level of the highest priority HCS layer".
# Margin is 5.
# Cell edge coverage probability 75%.
# Traffic spreading was Uniform
##---------------------------------------------------------------------#
1
TCH_INNER
8
9
a.
BCCH,TCHa
1
0.944
10
0.904
11
0.892
14
0.844
15
0.832
16
0.812
17
0.752
22
0.316
25
0.292
0.944
10
.904
13
0.872
14
0.84
17
0.772
IftheTCHandBCCHhistogramsarethesame,theyarenotrepeated.Asinglerecordindicatesthatthehistograms
belongtoTCHandBCCHboth.
9.7.1.2 DCTFileFormat
The.dctfileisdividedintotwoparts.Thefirstpartisaheaderusedforformatidentification.Itmuststartwithandcontain
thefollowinglines:
# Calculation Results Dictionary File.
98
AT321_AM_E1

ThesecondpartprovidesinformationabouttransmitterstakenintoaccountinAFP.Thelinesaftertheheaderareconsidered
ascommentsiftheystartwith"#".Ifnot,theymusthavethefollowingformat:
<Column1><tab><Column2><newline>
Column
Name
Type
Description
Column1
Transmittername
Text
Column2
TransmitterIdentifier
Integer
Identificationnumberofthetransmitter
Column3
BCCHduringcalculation
Integer
BCCHusedincalculations
Column4
BSICduringcalculation
Integer
BSICusedincalculations
Column5
%ofviccoverage
Float
Percentageofoverlapofthevictimservicearea
Column6
%ofintcoverage
Float
Percentageofoverlapoftheinterfererservicearea
The lastfour columns describe the interference matrix scope. One transmitter per line is described separated with atab
character.
Sample
# Calculation Results Dictionary File.
# Version 2.1,
Tab separated format. Commented lines start with #.
# Fields are:
##-----------#-----------#-----------#-----------#---------#---------#
#|Transmitter|Transmitter|BCCH during|BSIC during|% of vic'|% of int'|
#|Name
|Identifier |calculation|calculation|coverage |coverage |
##-----------#-----------#-----------#-----------#---------#---------#
#
#
# Service Zone Type is "Best signal level per HCS layer".
# Margin is 5.
# Cell edge coverage probability is 75%.
# Traffic spreading was Uniform (percentage of interfered area)
##---------------------------#
Site0_0
-1
-1
100
100
Site0_1
-1
-1
100
100
Site0_2
-1
-1
100
100
Site1_0
-1
-1
100
100
Site1_1
-1
-1
100
100
Site1_2
-1
-1
100
100
Site2_0
-1
-1
100
100
Site2_1
-1
-1
100
100
9.7.2 IM0Format(OneHistogramperLine)
Thisfilecontainsonehistogramperlineforeachinterfered/interferingsubcellpair.ThehistogramisalistofC/Ivalueswith
associatedprobabilities.
The.im0fileconsistsoftwoparts.Thefirstpartisaheaderusedforformatidentification.Itmuststartwithandcontainthe
followinglines:
99
Forsk2014

Thesecondpartdetailsinterferencehistogramofeachinterferedsubcellinterferersubcellpair.Thelinesaftertheheader
<Column1><tab><Column2><tab><Column3><tab><Column4><newline>
Column
Name
Description
Column1
Nameoftheinterferedtransmitter.
Column2
Nameoftheinterferertransmitter.
Column3
InterferedTRXtype
Interferedsubcell.Inordertosavestorage,allsubcellswithnopoweroffset
arenotduplicated(e.g.BCCH,TCH).
Column4
C/Iprobability
C/Ivalueandtheprobabilityassociatedtothisvalueseparatedbyaspace
character.Thisentrycannotbenull.
Sample
# Remark:
# Fields are:
#-----------------------------------------------------------------------#Transmitter
Interferer
TRX type
{C/I Probability} values
#-----------------------------------------------------------------------#
#
# Margin is 5.
##---------------------------------------------------------------------#
#
Site0_2
Site0_1
BCCH,TCH-10 1 -9 0.996 -6 0.976 -4 0.964 -1 0.936

0 0.932 1 0.924 4 0.896 7 0.864 8 0.848
9 0.832 10 0.824 11 0.804 14 0.712 17 0.66
Site0_2
Site0_3
BCCH,TCH-10 1 -9 0.996 -6 0.976 -4 0.972 -1 0.948

0 0.94 1 0.928 4 0.896 7 0.856 8 0.84
11 0.772 13 0.688 14 0.636 15 0.608 18 0.556
Site0_3
Site0_1
BCCH,TCH-10 1 -9 0.996 -6 0.98 -3 0.948 0 0.932

1 0.924 4 0.892 7 0.852 8 0.832 9 0.816
10 0.784 11 0.764 14 0.644 15 0.616 18 0.564
Site0_3
Site0_2
BCCH,TCH-9 1 -6 0.972 -3 0.964 -2 0.96 0 0.94

1 0.932 4 0.904 7 0.876 8 0.86 9 0.844
11 0.804 13 0.744 14 0.716 15 0.692 18 0.644
9.7.3 IM1Format(OneValueperLine,TXNameRepeated)
This file contains one C/I threshold and probability pair value per line for each interfered/interfering subcell pair. The
histogramisalistofC/Ivalueswithassociatedprobabilities.
100
AT321_AM_E1
The.im1fileconsistsoftwoparts.Thefirstpartisaheaderusedforformatidentification.Itmuststartwithandcontainthe
followinglines:
Thesecondpartdetailsinterferencehistogramofeachinterferedsubcellinterferersubcellpair.Thelinesaftertheheader
<Column1><tab><Column2><tab><Column3><tab><Column4><tab><Column5><newline>
Column
Name
Description
Column1
Nameoftheinterferedtransmitter.
Column2
Nameoftheinterferertransmitter.
Column3
InterferedTRXtype
Interferedsubcell.Inordertosavestorage,allsubcellswithnopoweroffset
arenotduplicated(e.g.BCCH,TCH).
Column4
C/Ithreshold
C/Ivalue.Thiscolumncannotbenull.
ProbabilityC/I>Threshold
ProbabilitytohaveC/Ithevaluespecifiedincolumn4(C/Ithreshold).This
fieldmustnotbeempty.
Column5
Sample

# Remark:
# Fields are:
#-----------------------------------------------------------------------#Transmitter
Interferer
TRX type
C/I
Probability
#-----------------------------------------------------------------------#
#
# Margin is 5.
##---------------------------------------------------------------------#
Site0_2
Site0_1
BCCH,TCH
-10
Site0_2
Site0_1
BCCH,TCH
-9
0.996
Site0_2
Site0_1
BCCH,TCH
-6
0.976
Site0_2
Site0_1
BCCH,TCH
-4
0.964
Site0_2
Site0_1
BCCH,TCH
-1
0.936
Site0_2
Site0_1
BCCH,TCH
0.932
Site0_2
Site0_1
BCCH,TCH
0.924
Site0_2
Site0_1
BCCH,TCH
0.896
Site0_2
Site0_1
BCCH,TCH
0.864
Site0_2
Site0_1
BCCH,TCH
0.848
Site0_2
Site0_1
BCCH,TCH
0.832
Site0_2
Site0_1
BCCH,TCH
10
0.824
...
101
Forsk2014
9.7.4 IM2Format(CoandAdjacentchannelProbabilities)
IM2 files contain cochannel and adjacentchannel interference probabilities for each interfered transmitter interfering
transmitterpair.InGSM,thereisonlyonesetofvaluesforallthesubcellsoftheinterferedtransmitter.Eachlinemusthave
thefollowingformat:
<Column1><SEP><Column2><SEP><Column3><SEP><Column4><newline>
Wheretheseparator(<SEP>)caneitherbeataborasemicolon.
Thefourcolumnsaredefinedinthetablebelow:
Column
Name
Description
Column1
Nameoftheinterferedtransmitter
Column2
Nameoftheinterferertransmitter
Column3
Cochannelprobability
Cochannelinterferenceprobability
Column4
Adjacentchannelprobability
Adjacentchannelinterferenceprobability
Sample
# Remark:
# Fields are:
#-----------------------------------------------------------------------#Transmitter
Interferer
Co-channel
Adjacent channel
#-----------------------------------------------------------------------#
#
# Margin is 5.
##---------------------------------------------------------------------#
Site0_2
Site0_1
0.226667
0.024
Site0_2
Site0_3
0.27
0.024
Site0_3
Site0_1
0.276
0.02
Site0_3
Site0_2
0.226
0.028
Thecolumnsinthesampleaboveareseparatedwithatab.Thesecolumnscanalsobeseparatedwithasemilcolon:
Site0_2;Site0_1;0.226667;0.024
Site0_2;Site0_3;0.27;0.024
Site0_3;Site0_1;0.276;0.02
Site0_3;Site0_2;0.226;0.028
9.8 "PerTransmitter"PredictionFileFormat
Whenacoveragepredictioniscalculatedbyvalueintervalsitisstoredexternally,i.e.,outsidetheATLfile.Acorresponding
<doc_name>\{<GUID>}folderisactuallycreatedwheretheATLdocumentislocated,assoonasthelatterissaved.
102
AT321_AM_E1
Thecalculationofthecoveragepredictioniseitherglobalor"pertransmitter".
Whenthecalculationisglobal,theresultsarestoredintwofilesfortheentireprediction:oneHDRfileandoneBIL
file(bothidentifiedbythepredictionname).
Whenacalculationis"pertransmitter",oneHDRfileandoneBILfilearecreatedforeachtransmitterintheprediction
(bothidentifiedbythetransmittersname).Insome"pertransmitter"predictions,anadditionalDBFfileiscreatedfor
theentireprediction(identifiedbythepredictionname).TheDBFfilecontainsinformationoneachtransmitteranda
pointertoeachtransmittersspecificHDRandBILfiles.
InLTE,whenaCellIdentifierCollisionZones(DL)predictioniscalculatedbyvalueintervalswiththedisplaytypeset
"No.ofinterfererspercell",theHDRfileandtheBILfilearecreatedforeachcellintheprediction(bothidentifiedby
thecellsname).
TheformatandthecontentoftheDBFfileisdescribedhere.
Inbothcases,anXMLfiledescribingthepredictionisalsocreatedinthecorresponding
<doc_name>\{<GUID>}folder.
9.8.1 <per_transmitter_prediction>.dbfFileFormat
Theformatof<per_transmitter_prediction>.dbffilesisidenticaltotheformatdescribedin"Pathloss.dbfFileFormat"on
page 92.
9.8.2 <per_transmitter_prediction>.dbfFileContents
The<per_transmitter_prediction>.dbffilesgeneratedinspecific{<GUID>}foldersprovideinformationthatisneededto
checkthevalidityofeach"pertransmitter"prediction>calculatedbyvalueintervals.
Field
Type
Description
TX_NAME
Text
FILE_NAME
Text
NameofthetransmittersBILresultfile
RESOLUTION
Float
Resolutionofthecalculation,sameasxdimandydimintheHDRfile
AREA_XMIN
Float
SameasulxmapintheHDRfile
AREA_XMAX
Float
Sameasulxmap+xdim*ncolsintheHDRfile
AREA_YMIN
Float
SameasulymapintheHDRfile
AREA_YMAX
Float
Sameasulymap+ydim*nrowsintheHDRfile
NBITS
Float
SameasnbitsintheHDRfile
NBANDS
Float
SameasnbandsintheHDRfile
BYTE_ORDER
Float
SameasbyteorderintheHDRfile
BAND_ROW_BYTES
Float
SameasbandrowbytesintheHDRfile
TOTAL_ROW_BYTES
Float
SameastotalrowbytesintheHDRfile
SKIP_BYTES
Float
SameasskipbytesintheHDRfile
DATA_TYPE
Text
SameasdatatypeintheHDRfile
NO_DATA_VALUE
SameasnodatavalueintheHDRfile
103
104
Forsk2014
Chapter10:AdministrationandUsageRecommendations
AT321_AM_E1
10 AdministrationandUsageRecommendations
ThischapterlistsvarioustechnicalrecommendationsforoptimisingyourworkwithAtoll.
10.1 GeographicData
LocationoftheGeographicData
Inmultiuserenvironments,itisrecommendedtoplaceallthegeographicdataonafileserveraccessibletoallthe
users.Thisapproachavoidstheneedtoreplicatethegeographicdataonalltheworkstations.
Geographicdatashouldeitherbelocatedoneachserveroraccessiblethroughafastnetworkconnection,e.g.,1 Gbps.
Youcanrestrictaccesstothegeographicdatalocationsbyassigningread/writeaccessrightstoadministratorsand
readonlyrightstoendusers.
LinkorEmbed
Only embed geographic data in ATL files if you wish to make a portable document. In all other cases, it is
recommendedtolinkgeographicdatafilestotheAtolldocuments.
ItisrecommendedtosetthepathstolinkedgeographicdatafilesusingtheUniversalNamingConvention(UNC).
Following the UNC, an absolute path, such as "C:\Program Files\Forsk\Geo Data\...", is represented as
"\\Computer\C\ProgramFiles\Forsk\GeoData\...",where"Computer"isthecomputername,and"C"istheshare
nameofdiskC.
Example:
AbsolutePath
C:\ProgramFiles\Forsk\GeoData\...
RelativePath
\ProgramFiles\Forsk\GeoData\...
UNCPath
\\Computer\C\ProgramFiles\Forsk\GeoData\...
IfyoudefinepathstogeographicdatafilesusingtheUNC,Atollwillbeabletokeeptrackofthelinkedfilesevenifthe
Atolldocumentismovedtoanothercomputer.
SizeofTiles
Somenetworkplanningtoolsrequiregeographicdatatobeavailableinsmalltilesinordertoworkmoreefficiently.
For acountrywide project, thiscan leadto hundreds of files describing the geographic data. Atollis designed to
optimisememoryconsumption,whichenablesittoperformefficientlywithregionaltiles(1tile/fileperregion).In
Atoll,Mergingsmalltilestobuildaregionaltilecanimproveperformancegreatly.
Tonoteaswell:
Recommendedfilesize:100to200MB
ErdasImaginePyramidsfilescanbebigger.
ECWfilescanbeofanysize(nolimitations).
RecommendedFormats
Inordertoimproveperformance,itisrecommendedtouseuncompressedDTMandclutterfiles,forexample,BIL
files.Usingcompressedgeographicdatafiles,forexample,compressedTIForErdasImagine,cancauseperformance
reductionduetodecompressionofthesefilesinrealtime.Ifyouareusingcompressedgeographicdatafiles,itis
stronglyrecommendedto:
Either,hidethestatusbarthatdisplaysgeographicdatainformationinrealtime.Youcanhidethestatusbarfrom
theViewmenu.
Or,disablethedisplayofsomeoftheinformationcontainedinthestatusbar,suchasaltitude,clutterclass,and
clutterheightusinganoptionintheAtoll.inifile,see"HidingInformationDisplayedintheStatusBar"onpage 160.
Thefollowingtableshowstherecommendedfileformatsfordifferentgeographicdata:
Geographicdatatype
Recommendedfileformat
Scannedmaps
ECW
Vectors
SHP
105
Forsk2014
10.2 PathLossMatrices
SharedPathLossMatrices
Sharedpathlossmatricesshouldbeaccessiblethroughafastnetworkconnection,e.g.,1 Gbps.Theseresultsare
accessedbyAtollduringcalculations,andshouldbeavailabletotheusersthroughafastnetworkconnection,i.e.,
30 Mbpsatleastperuser.
Youcanrestrictaccesstothesharedpathlossmatricesfolderbyassigningread/writeaccessrightstoadministrators
andreadonlyrightstoendusers.
PrivatePathLossMatrices
Atollsynchronisestheprivatepathlossmatriceswiththesharedpathlossmatrices.Ifprivatepathlossmatricesare
invalid,andthecorrespondingsharedpathlossmatricesarevalid,Atolldeletestheinvalidprivatepathlossmatrices
andusesthesharedones.YoucanmakeAtollverifyandremoveprivatepathlossmatrices,validorinvalid,whose
corresponding shared path loss matrices are valid. This can be useful for disk space management. For more
information,see"SynchronisingPrivateandSharedPathLossMatrices"onpage 155.
LinkorEmbed
Only embed path loss matrices in ATL files if you wish to make a portable document. In all other cases, it is
recommendedtolinkpathlossmatricestotheAtolldocuments.
ExternalisingpathlossmatricestosharedorprivatepathlossfolderswillkeeptheATLfilesizereasonable,whichwill
result in less fragmentation. Externalising path loss matrices does not reduce the performance of display and
calculationsinAtoll.
ItisrecommendedtosetthepathstotheprivateandsharedpathlossmatricesfoldersusingtheUniversalNaming
Convention(UNC).
Following the UNC, an absolute path, such as "C:\Program Files\Forsk\PathLosses\...", is represented as
"\\Computer\C\ProgramFiles\Forsk\PathLosses\...",where"Computer"isthecomputername,and"C"istheshare
nameofdiskC.
Example:
AbsolutePath
C:\ProgramFiles\Forsk\PathLosses\...
RelativePath
\ProgramFiles\Forsk\PathLosses\...
UNCPath
\\Computer\C\ProgramFiles\Forsk\PathLosses\...
IfyoudefinepathstotheprivateandsharedpathlossmatricesfoldersusingtheUNC,Atollwillbeabletokeeptrack
ofthelinkedfileseveniftheAtolldocumentismovedtoanothercomputer.
CalculatingPathLossMatricesinMultiRATDocuments
WhenthepathlossmatricesinmultiRATdocumentsusingtheRunPathlossAPIfunction,thepathlossmatricesof
eachtechnologyarecalculatedsimultaneouslyusingthesamenumberofthreads.Forexample,if4threadsareused
tocalculatepathlossmatrices,andthereare3technologies(GSM,UMTS,andLTE),atotalof12threadswillbeused
tocalculatethepathlossmatricesatthesametime.Thiscanleadtothefollowingproblems:
InsufficientCPUresources
Insufficientmemory
Insufficientlicencesifexternalpropagationmodelsareused.
To avoid these problems when using the RunPathloss API function to calculate path loss matrices in multiRAT
documents,usethefollowingworkarounds:
UsetheDistributedCalculationServer,evenlocally.
Inyourscriptormacro,deactivatethetransmittersofthetechnologiesforwhichyoudonotwanttocalculatethe
pathlossmatricesandreactivatethemafterwards.Repeatitforalltechnologies.
Lower the number of threads using the NumberOfThreadsPathloss option in RemoteCalculation section in
Atoll.ini.Forexample,youcansettheoptionto2touseamaximumof6threads(3*2)duringpathlosscalculation
usingtheRunPathlossfunction.
106
Resource saturation during the calculation of path loss matrices for multiRAT
documentsonlyoccurswhenusingtheRunPathlossAPIfunctioninamacroorscript.
WhencalculatingpathlossmatricesforamultiRATdocumentusingAtoll,thisdoes
notoccur.
AT321_AM_E1
Atollsynchronisestheprivatepathlossmatriceswiththesharedpathlossmatrices.Ifprivatepathlossmatricesare
invalid,andthecorrespondingsharedpathlossmatricesarevalid,Atolldeletestheinvalidprivatepathlossmatrices
andusesthesharedones.YoucanmakeAtollverifyandremoveprivatepathlossmatrices,validorinvalid,whose
corresponding shared path loss matrices are valid. This can be useful for disk space management. For more
information,see"SynchronisingPrivateandSharedPathLossMatrices"onpage 155.
10.3 AtollDocuments
General
ItisrecommendedtodefinearuleformakingbackupsofyourAtolldocumentsatregularintervals.
DonotskipamajorAtollversion.Forexample,ifyouarecurrentlyusingAtoll2.8.x,youshouldfirstupgradethe
documenttoAtoll3.1.xbeforeupgradingtoAtoll3.2.x.
Upgrading your document will be simpler if you do not skip a major version. If you skip or have skipped an
intermediatemajorversion,youshouldupgradeyourdocumenttwiceinordertomakeitcompatiblewiththenew
version.
10.4 Databases
General
InordertouseAtollwithOracle,youmustcreateOracleusersandschemawithnamesinuppercase.
Createbackupsofthedatabasebeforeupgrading.
Itisrecommendedtodefinearuleformakingbackupsofthedatabaseatregularintervals.
DonotskipamajorAtollversion.Forexample,ifyouarecurrentlyusingAtoll2.7.x,youshouldfirstupgradethe
databasetoAtoll2.8.xbeforeupgradingtoAtoll3.1.x.
Upgradingyourdatabasewillbesimplerifyoudonotskipamajorversion.Ifyouskiporhaveskippedanintermediate
majorversion,youmustupgradeyourdatabasetwiceinordertomakeitcompatiblewiththenewversion.
TablesandFields
Tableandfieldnamesarecasesensitive.
Tableandfieldnamesshouldbenotmorethan20characterslong.
Oracledatabasesallowamaximumlengthof30charactersforfieldandtablenames.However,foruseinAtoll,you
mustnotcreatetablesandfieldswithnameslongerthan20characters.ThisisbecauseAtolladdssomecharactersto
thetableandfieldnamesforcertainoperations:creatingassociatedtriggers,creatingprojectdatabases,etc.Limiting
thelengthoftableandfieldnamesto20characterswillhelpavoiddatabaseconnectionandconsistencyproblems.
Tableandfieldnamesshouldonlyusealphanumericcharacters(AZ,az,09)andunderscores(_).
Tableandfieldnamesmustnotstartwithanumericcharacter(09).
TableandfieldnamesmustnotcontainanSQLorRDBMSspecifickeyword,suchasORDER,DATE,etc.
Tableandfieldnamesmustnotcontainspacesorspecialcharacters,suchasperiods(.),exclamationmarks(!),colons
(:),semicolons(;),interrogationmarks(?),parentheses(()),brackets({}),squarebrackets([]),etc.
Booleanfields,systemoruserdefined,shouldalwayshavedefaultvaluesassigned.
TheCustomFieldstableenablesyoutodefinedefaultvalues,choicelists,andread/writeaccessforanyfieldinany
tablein Atoll, includinguserdefined fields that you addto the Atolltables. Thevalues definedin thistablehave
priorityovertheinternalpredefineddefaultvalues.Ifyoudefinefloatingpointdefaultvalues,makesurethatallthe
usershavethesamedecimalseparator.
IfyouwishtoaddcustomfieldsintheAtolldocument,youshouldfirstaddthefieldinthedatabase,andthenupdate
yourAtolldocumentfromthedatabase.
Whensettingupyourdatabaseforthefirsttime,trytoanticipateuserrequirementsintermsofcustomfieldsinAtoll
tables.Somerequirementsofthedifferentusergroupscanbesatisfiedifafewgeneralpurposeuserdefinedfields
areaddedinAtolltableswhensettingupthedatabase.
Forexample,ifyouaddthreeuserdefinedfields(oneoftypeinteger,float,andtext(limitedsize))totheSitesand
Transmitterstables,userswillbeabletousetheseforsorting,filtering,grouping,orotherpurposes.Thisapproach
canhelpthedatabasefunctionalongtimebeforeusersrequiretheadditionofothercustomfields.
To improve performance, if your projects allow it, reduce the size of the fields corresponding to the sites and
transmittersnames.
To improve performance, unless absolutely necessary, do not add userdefined fields of Text type. Rather, use
numericfieldtypes,whichallowsortingandotherfunctions.IfyoumustaddTextfields,allocatethemtheappropriate
sizethatwouldsuffice.Forexample,a255characterlongTexttypefieldwould,forthemostpart,occupydiskspace
fornopurpose.
Toimproveperformance,youshouldavoidaddingcustomfieldstotheneighbourmanagementtables.
107
Forsk2014
10.5 CalculationServer
ComputationServerStabilityandResourceManagement
Incertainconditions,asdescribedbelow,Atollusersmightexperienceadecreaseinserverperformanceandstabilityina
multiuserCitrixenvironment.TheprincipaldifferenceobservedmightbetheinabilitytorunmultipleAtollsessionsonthe
serverwithoutgettingerrormessages,generalapplicationfailures,orservercrashes.Suchproblemscanoccurwhenthe
numberofAtollsessionsontheserver,carryingoutcalculations,increasestomorethanfour.
CausesofInstabilityandLossofPerformance
Thisgeneralinstabilityandlowperformanceoftheserversisdueto:
Insufficientmemoryresources:globallyandperprocess(Atollsession)
InsufficientCPUresources
Networkcongestion
Atollcanprocessfoursimultaneouspathlossmatricescalculations,whichmeanshighCPUandRAMresourceconsumption,
andaspathlosscalculationssharetheamountofmemoryallocatedtotheAtollsession,thetotalmemoryrequirementcan
exceed the Microsoft Windows (32bit editions) limit of 2 GB per process. This is especially the case with large Atoll
documentsandpropagationmodelsthatrequireconsiderablememory.
TroubleshootingandSolution
Asthecauseofthisproblemisresourcesaturationontheserver,resourceconsumptionshouldbecontrolledinordertoavoid
memoryandCPUoverloadingasfollows:
Toreducetheimpactofalargenumberofsimultaneouspathlosscalculations,aDistributedCalculationServershould
besetup.UsingtheDistributedCalculationServer,pathlosscalculationscanbeperformedoutsideAtoll.Usingthe
DistributionCalculationServerhasthefollowingadvantages:
PathlosscalculationsarelimitedtofourparallelinstancesregardlessofthenumberofAtollsessionsrunningon
theserver.ThisnotablyimprovesthememoryandCPUconsumption.
A queuing system, integrated in the Distributed Calculation Server, manages the calculation requests from
differentAtollsessions.
AfailovermechanismautomaticallyswitchesandhandsoverthepathlosscalculationsbacktoAtollincasea
problemoccurs.
Pathlosscalculationsarecarriedoutbyaseparateprocess(AtollSvr),whichhasitsownmemoryallocationapart
fromAtoll,i.e.,theamountofmemoryneededforcalculationsdoesnotimpactstheAtollmemoryallocation.
ThissetupcanintroduceconsiderableimprovementsinboththenumberofAtollsessionsperserverandthecalculations.A
serverwithfourprocessors(eightthreadswithhyperthreading)canaccommodatefoursimultaneouspathlosscalculations
andusetheotherfourthreadsforAtollsessions.Atollsinterfacewillalsobemoreefficientandtheoverallprocessingtime
forvarioustaskswillbeimproved.
InordertopreventusersfromdeactivatingtheuseoftheDistributedCalculationServer,
andhencebypassingtheresourcecontrolprocedureestablishedabove,theAtoll.inifile
shouldbesetmadereadonlyforendusers.
Apartfromtheabovesetup,youcanalsomakesomeothersystemimprovements:
To avoid error messages caused by requesting a large number of files over the network, the following Microsoft
Windowsregistryparametercanbemodifiedinordertodedicatemoreresourcestonetworkread/writeoperations:
IRQSTACKSIZEshouldbesetto30insteadof11,forexample.
Toavoidoutofmemoryproblems,thePagefilesizeshouldbeincreasedsothattheserverdoesnotrunoutofglobal
memorywhensupportingmorethan10Atollsessionssimultaneously.Thisisdifferentfromthe2 GBperprocess
limit.Virtualmemorycanbeincreasedfrom8 GBto16 GB,forexample.
For32bitWindowsoperatingsystems,youcanalsoincreasethedefaultWindowsmemoryallocationlimitfrom2 GB
to3 GBasexplainedin"ProcessMemory"onpage 109.
10.6 AtollAdministrationFiles
ThereisnospecificorderinwhichconfigurationandinitialisationfilesshouldbecreatedorinstalledonAtollworkstations
and servers. It is sufficient to have these files created and placed in the right locations before running Atoll to have the
predefinedconfigurationofallworkstationsandservers.
Ifyouhavealreadyconfiguredthesefilesforoneserver,andyouaresettingupanotherserver,youcancopythesefilesto
theirrespectivelocationsonthenewservertohavetheexactconfigurationandsetupasthefirst.Ifyoudonotcopythese
108
AT321_AM_E1
files,orcreatethem,youwillnothavethesameconfigurationofthenewserver,butapartfromthatyouwillbeabletowork
withAtollnormally.Thesefilesareoptional,notobligatory.
InitialisationFile(INI)
ItishighlyrecommendedthattheAtollinitialisationfilebecreatedandmodifiedonlybytheadministrator.
IfyouareusingWindows2000Server,statetheactualnumberofprocessorsintheINIfile.
UserConfigurationFile(CFG)
UseAtolltocreatethesefilesandavoidmodifyingthesefilesmanuallyashumanerrorscancreateproblems.
Uncheckimagevisibilitytoavoidloadingunnecessarydatainthememory.
Youcansetupyourconfigurationfilesinthefollowingmanner:
Acommonconfigurationfilethatpointstothegeographicdata,macros,andothercommonparametersinyour
Atolldocuments.
Separateconfigurationfilescreatedforyour2Gand3Gprojects,whichwouldstoretheirrespectivecoverage
prediction studies parameters, traffic information, neighbour allocation parameters, and other technology
specificparameters.
Separate configuration files based on, and for, different groups of users. These groups of users can be, for
example,groupsofusersworkingondifferentregions,groupsofusersworkingondifferenttechnologies,groups
ofusersfocusingoncertainoperations(i.e.,performingcertaintypesofcoveragepredictions,performingtheAFP,
etc.).
CustomPredictionsFile
Coverage prediction studies can easily be duplicated within Atoll. Before creating study templates, and the XML
studiesfile,makesurethatthisstudytemplateisaimedatservinganumberofusers.Thismeans,avoidcreatingstudy
templatesunlessthesewillbeneededforalongtimebyanumberofusers.Youcanusetheconfigurationfilestostore
yourcreatedcoveragepredictionstudieslocally.And,youcanalsousethestudyduplicatefeaturetocreatecopiesof
existingcoveragepredictionstudies.
10.7 ProcessMemory
32bitOperatingSystems
Atoll can support 3 GB address space on a properly configured 32bit 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
SupportandWindowsOperatingSystems).
ThefollowinglinkprovidesinformationonhowyoucansetupyourWindowsServer2003systemstoactivatethe3 GBswitch
atstartup:http://technet.microsoft.com/enus/library/bb124810.aspx.
64BitOperatingSystems
The64biteditionsofMicrosoftWindowsprovide4 GBofmemoryperprocess.
10.8 Printing
Youshouldplacedifferentlayersofgeographicandradiodatainadefiniteorderwhenprintingaprojectorasectionofthe
project.Thefollowingordershouldbefollowed:
1. VisibleobjectsoftheDatatab
AllthevisibleobjectsoftheDatatabaredisplayedabovethoseintheGeotab.However,itisstronglyrecommended
toplacevectorlayersonthetopofcoveragepredictionplots.Youcandothisbytransferringthesevectorlayersto
theDatatabusingthecontextmenu.Forperformancereasons,itisadvisedtoplacevectorlayersontopofraster
layersbeforeprintingaproject.SitesandTransmittersmustbeontheverytop,aboveallotherlayers.Youshould
placesitesandsectorsonthetop,thenvectorlayers,andthenrasterlayers.
2. Unidimensionalvectors(points)
3. Openpolygonalvectors(lines,i.e.,roadsandotherlinearitems,etc.)
4. Closedpolygonalvectors(surfaces,i.e.,zonesandareas,etc.)
5. Multiformatmaps(vectororrastermaps,i.e.,population,rain,genericmaps,traffic,etc.)
6. Transparentrastermaps(clutterclassmaps,etc.)
7. Nontransparentmaps(images,DTM,clutterheightmaps,etc.)
109
Forsk2014
10.9 CoveragePredictionCalculations
IfyoudonotwantAtolltocalculatetheshadowingmarginduringacoverageprediction,itisadvisedtoclearthe
Shadowingtakenintoaccountcheckbox.Thisapproachismoreefficientintermsofperformancethanselectingthis
optionandsettingtheCelledgecoverageprobabilityto50%.
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
usuallysufficient:
Sizeofthecoverageprediction
Displayresolution
CityCenter
5m
City
20m
County
50m
State
100m
Country
Accordingtothesize
10.10 CWMeasurementsandDriveTestData
ItisrecommendedtouseFastDisplayinordertoincreasedisplayspeed.ThisoptionisavailableintheDisplaytabof
thePropertiesdialoguesforCWMeasurementsandDriveTestDatafolders.Althoughthisapproachonlydisplays
measurementpointsassmallsquares,itcanhaveasignificantimpactonperformancedependingonthenumberof
measurementpointsintheAtolldocument.
WhenperformingaCWmeasurementsdrivetestcampaign,pleasefollowtherecommendedproceduredescribedin
theMeasurementsandModelCalibrationGuide.
10.11 AntennaPatternsandImport
Antennanamesusedinsometools,suchasNetAct,canbedifferentfromthoseusedintheircorrespondingantenna
files.Tosolvethisissue,youcancreateanewfile,named"Index",containingthelistofantennanames,whichwould
infactbethepattern(antennafile)names.Youshouldplacethisfileatthesamelocationastheantennapatterns
(files).Thiswillreplacetheantennanameswiththenewantennanames.
SomeKathreinantennapatternfilesmighthavenamesdifferentfromtheantennapatternnamespresentinsidethe
file.Youwillhavetoreplacethenameofthepatterninsidethefilebythenameofthepatternfileitself,inorderto
importtheseantennascorrectly.
APlanetIndexfilecontainsthepathtoandthenameofeachantennafileavailable.CreatingsuchanIndexfilewhen
therearehundredsofantennapatternsavailablecanbeadifficulttask.Youcaneasilycreatetheindexfilefromthe
MicrosoftWindowscommandprompt.YoucanopentheCommandPromptwindowbyselectingStart>Run,entering
"cmd" and pressing ENTER. In the Command Prompt window, navigate to the directory containing the antenna
patternfiles,enterthefollowingcommandandpressENTER:
dir /b > Index
Thiswillcreateafilecalled"Index"inthesamedirectoryastheantennapatterfilescontainingalistofalltheantenna
patternfilenames,withonenameperline.Thefilewillalsocontainalinewithitsownname,so,beforeimporting
thisfileintoAtoll,youshoulduseatexteditortoremovethelinecontainingthefilename"Index."
Theelectricaltilt,whichcanbedefinedintheantennapropertiesdialoguesinAtoll,isanadditionalelectricaldowntilt.
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
includetheeffectofanelectricaltilt.
10.12 TrafficMaps
110
Userprofileenvironmentbasedtrafficmapsshouldonlybeusedforaprecisionontrafficthatisofthesamelevelas
thestatisticalclutteravailableinaproject.
Forhigherprecisionontrafficdata,youshouldusesectortrafficmapsoruserdensitytrafficmaps.Userdensitytraffic
mapsprovideyouwithameanstodefineadensityforeachsetofservice,terminaltype,andmobilitytype.
SectortrafficmapsarebestsuitedfortrafficdataissuedbytheOMC.
AT321_AM_E1
10.13 AtollAPI
CorrectfunctioningofAtollwhenusingAtollthroughtheAPIisguaranteedduringinteractiveusersessionsonly.Atollisan
application that requires creating tool bars, creating menus, reading user profile options from the Windows registry,
accessingprinters,etc.,evenwhenitisaccessedthroughtheAPI.ThesameistrueforaddinsworkingwithAtoll.
EventhoughitispossibletoloadanduseAtollwhenthereisnousersessionopenonacomputer,itscorrectfunctioningis
notguaranteed.Unexpectederrorscanoccur.Particularly,creatingobjectsthroughCreateObjectorCoCreateInstancemight
fail.
Therefore,thecorrectfunctioningofAtollrequiresanopenusersessiononthecomputer.
10.14 PerformanceandMemory
MemoryRefresh
YoucanavoidmemoryfragmentationwhileworkingwithAtolldocumentsbysavingtheAtolldocumentfromtimeto
time,closingandrestartingAtoll,andreopeningthedocument.
ThisadviceisapplicabletoanyapplicationrunningunderMicrosoftWindowsbecausemanycommonDLLfilesare
accessedbyapplications,andunloadingandreloadingtheseDLLfilesrefreshesthememoryallocation.
IfyouareworkinginaCitrixXenAppenvironment,youshouldrestartyourCitrixservereveryweekorfortnight.The
exacttimeshouldbedeterminedbytheadministratordependingonthestateofthenetwork(LAN).
Incertaincases,itmightbemoreappropriatetostartworkingonacompletelyfreshATLfile.Ifyouhavebeenworking
onyourexistingATLfileforalongtime,itmightbecomeunnecessarilylargeandmightcontainsomeuselessremains
fromyour earlieroperations, e.g.,tracesof records thatnolongerexist inthedatabase,etc. You cancompletely
refreshyourprojectbyfollowingthesesteps:
a. OpentheexistingATLfileinAtollthatyouwanttoreplace.
b. CreateaCFGfilefromyourexistingATLfilewithalltherequiredinformation,e.g.,geographicdataset,coverage
predictionparameters,neighbourallocationparameters,etc.Formoreinformation,referto"ConfigurationFiles"
onpage 117.
c. ClosetheoldATLfile.
d. CreateanewATLfromthedatabasetocreateafreshATLfile.
e. ImporttheCFGfileinthenewATLfile.
YounowhaveacleanATLfiletoworkwith,whichhasallthesameinformationastheoldATLfile,andtakesupless
spaceontheharddisk,haslessfragmenteddata,andimprovedperformance.
MemoryAllocation
IfyouhavetoopenseverallargeATLfilessimultaneouslyonthesamecomputer,itisbettertoopeneachinaseparate
AtollsessionratherthantoopenthemallinthesameAtollwindow.EachAtollsessiononthesamecomputerhasits
ownmemoryspaceallocatedbytheoperatingsystem.Eachcomputerconsumesasinglelicencetokenindependent
ofthenumberofAtollsessionsopenedsimultaneously.
For32bitWindowsoperatingsystems,youcanalsoincreasethedefaultWindowsmemoryallocationlimitfrom2 GB
to3 GBasexplainedin"ProcessMemory"onpage 109.
FileSize
Coveragepredictionscalculatedoverlargeareasrequiremorememory.IfyouareworkingonanAtolldocument
coveringalargearea,withcoveragepredictionscalculatedovertheentirenetwork,thisdocumentwillrequiremore
memoryforloadingallthecoveragepredictions.YoucanreducememoryconsumptionbymakingcopiesofyourAtoll
document,andkeepingafewcoveragepredictionsineachcopy.TheseATLfileswillbefastertoloadandworkwith
comparedtoasingleATLfilewithallthecoveragepredictions.
Largecoveragepredictionscantakeupaconsiderableamountofmemoryeveniftheyarenotdisplayedonthemap.
ExternaliseDTM,clutter,pathlossmatrices,andanyotherdatathatcanbeexternalised,sothattheATLfilesizedoes
notbecomeunnecessarilylarge.
PathLossCalculation
Beforestartingpathlosscalculation,verifythatthecalculationradiiandresolutionsassignedtothedifferenttypesof
transmittersareconsistent.Forexample,calculatingpathlossmatricesofpicocellsoverlargecalculationradiiwould
onlywastememoryanddiskspace.
111
Forsk2014
Forcalculatingpathlossmatricesoverlargeareas,youshouldusethedualresolutionfeatureinAtoll.Defineshort
calculationradiiandfineresolutionsforthemainpathlossmatrices,andlargecalculationradiiandlowresolutions
forextendedpathlossmatrices.Thisapproachdecreasesthecalculationtimesignificantlycomparedtocalculating
justonematrixpertransmitterusingafineresolution.Themainpathlossmatricesshouldbecalculatedusingthe
sameresolutionastheresolutionofthegeographicdataavailable.Theextendedpathlossmatricescanbecalculated
usingalowerresolution,e.g.,twicetheresolutionofthegeographicdata.
Regionalisation
Usedatabaseregionalisationorsitelistsifyouareworkingonsmallerpartsofalargenetwork.Atollloadsonlythe
data necessary for your working area. If you load a large network, Atoll will load a lot of data that might not be
necessaryallthetime,suchastheneighbourrelationdata.
PerformanceandMemoryIssuesinLargeGSMProjects
MemoryproblemsmightbeexperiencedintheC/Icoveragepredictionstudies,interferencematricescalculations,andthe
AFPwhileworkingonlargeGSMnetworks.Largenetworkprojectsaremoresusceptibletotheseproblems.Ifthenetworkis
largebuthomogeneous,theseproblemsmightonlyappearifthenumberoftransmittersisover15,000orso.But,ifthereare
largecitycentresinvolved,witheachpixelhavingmanyoverlappingpathlossmatrices,thenthissizelimitmightdecreaseto
around5,000transmittersorso.
Also, if the Atoll session has been open for a long time, memory problems can even appear while working on smaller
networks.Thisisbecausetheprocessmemoryspace(memoryspaceallocatedtoAtollbytheoperatingsystem)becomes
fragmented.
Followingisalistofadvicewhichyoucanfollowinordertoavoidsuchproblems:
Useregionalisationorsitelists:Ifyouloadalargenetwork,Atollwillberequiredtoloadalotofdatathatmightnot
benecessaryallofthetime.Forexample,inatypicallargeGSMnetwork,youmighthavearound10,000transmitter
records,20,000subcellrecords,50,000TRXrecords,andupto150,000neighbourrecords.
Externaliseembeddedinterferencematrices:YoucanstoreinterferencematriceslistedintheInterferenceMatrices
folderinexternalfiles.Atollloadsinterferencematricesfromtheexternalfilestothememoryonlywhenneeded.You
willalsoreducetheATLfilesizebyexternalisingtheinterferencematrices.
Adapt calculation radii to the cell type and the EIRP: Before calculating path loss matrices, take care to correctly
associatecalculationradiiandresolutionstodifferenttypesofcells.Ifyoucalculatepathlossmatricesforalltypesof
cellsoveralargecalculationradius,itwillunnecessarilyburdentheC/Iandinterferencematricescomputations.
Properlyconfiguretheinterferencethresholds:Thesethresholdsindicatethelevelafterwhichaninterferercanbe
ignored.Thedefaultvalueforthisthreshold(130dBm),definedinthePredictionstabofthePredictionsfolders
Propertiesdialogue,meansthatthecomputationswilltakeintoaccountalltheinterferers.However,ifyousetittoo
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,RTiisthereceptionthresholdofthesubcelli,CITitheC/Ithresholdofthissubcell,andMisasafety
margin.
Sincethisinterferencethresholdisusedbothininterferencematricescalculationandininterferencepredictions,itis
importanttohaveatleasta3dBmarginfortheinterferenceenergyaggregationinC/Istudies.Werecommenda
safetymarginof5dB,whichcanbereducedifanyproblemisencountered.
DonotdefineveryhighC/Iqualitythresholds(Defaultvalues:12dBforBCCHand9dBforTCH).Ifyouwantacertain
TRXtypetocarryGPRS/EDGEtraffic,youcanadd1or2dBtothisvalueforthatTRXtype,andusetheoptionofsafety
margin in the AFP modules Cost tab. The 12 dB and 9 dB default values already include safety margins. If you
incrementthesevaluestoomuch,itwillunnecessarilyloadtheinterferencematrixgenerationandtheAFP.
DonotstartanAFPsessioniftheinterferencematricesreportindicatesproblems:Allthetransmittersshouldhave
interferersandveryfewofthem(notmorethan20%)shouldhavemorethan70interferers.Iftherearetoomanyor
toofewentriesinyourinterferencematrices,theAFPplanwillnotbeoptimal.
Ifthememorycriticaltaskisinterferencematricesgeneration:Youcangenerateinterferencematricesinapiecewise
manner.
Thismeansthatyoucangeneratenationwideinterferencematriceswithlowresolutionsbasedonthepercentageof
interferedarea(toimprovecomputationtime),withacelledgecoverageprobabilityof50%(whichmeansnoaccess
toclutterforreadingstandarddeviationvalues),andaninterferencethresholdof112dBm.Thiswillproviderough
global interference matrices which can be locally improved. These interference matrices will be less memory
consuming.
Then,usepolygonorsitelistfilterstofocusoneachimportantlocation,andcalculatelocalinterferencematriceswith
higherresolutionsandreliabilities.Makesurethatthecomputationzoneinyourprojectcompletelyencompassesthe
filteringzonesthatyoudefine.
112
IfthememorycriticaltaskistheAFPsession:Trytomakethedocumentlighter,e.g.,removecoverageprediction
studies,exitandrestartAtoll,andtrytogenerateinterferencematriceswithfewerentries.
AT321_AM_E1
Ifthememorycriticaltaskisthetrafficcapture:YoucanusetrafficloadfieldoftheSubcellstabletoprovidetraffic
loadsdirectlytotheAFP,andpossiblyskipthisstep.
PerformanceandMemoryIssuesinUMTS/CDMASimulations
Inordertooptimisememoryusageduringsimulations,youcansetthe"Informationtoretain"optionto"Onlythe
Average Simulation and Statistics". With this option Atoll uses much less memory because it only keeps limited
informationinmemoryduringthesimulationprocess.Simulationresultsaredetailedenoughtobeusedingenerating
coveragepredictionstudies.
PerformanceandMemoryIssuesinCoplanningProjects
Coplanning 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
containlarge,countrywidenetworks.TodecreasetheamountofmemoryusedbyAtollinsuchcases,youcan:
Loadvectorlayersinmaindocumentonly.Loadingvectorsinthelinkeddocumentisnotnecessaryandonlyconsumes
morememory.
Avoidloadingneighboursandcustomfieldswhicharenotrequired.Thiscanbeperformedbycreatingviewsinthe
database.Formoreinformation,see"Appendix2:SettingUpDatabasesforCoplanning"onpage 60.
10.15 Appendix:MemoryRequirements
Thispartgivessomeaspectsofmemoryrequirements(bothRAMandharddiskspace)forAtolldependingonthenetworkto
beplanned.
Atoll is capable of performing computations in pixel sizes different from those of the raster maps in a project. It is
recommendedtoperformdetailedplanningwithsmallerpixelsizesinhighdensityareas,andcountrywide(orregionwide,
dependingonthesize)coveragepredictionsandothercalculationsusinglargerpixelsizes.Thisapproachwillprovideoverall
satisfactoryresults,andwillconsiderablyimprovethediskspacerequirements,RAMallocationandcalculationtime.
Pleasenotethatthefiguresmentionedinthefollowingsectionsareapproximate,andthoughactualfigurescanvary,their
deviation from the approximate values will be negligible. These approximate values are computed through simplified
formulas.Theseformulasdonotconsideralltheinputparameters,butonlytheinputparametersthathaveaconsiderable
impactonmemoryrequirements.
10.15.1 DiskSpaceRequirements
Theamountofdiskspacerequiredfordatavariesfromprojecttoproject.Itdependsmainlyonthesizeoftheplanningarea,
the pixel size, and the number of cells. In networks with only a few cells, the amount of disk space required is chiefly
determinedbythesizeoftheplanningarea.Innetworkswithalargenumberofsites,transmittersandcells,itisthenumber
ofthesenetworkentitiesthatgovernsthisrequirement.Pixelsizeplaysanequallyimportantroleinallcases.
NetworkWideInput
Thefilesizesforrastermaps(DTM,clutterheights,clutterclasses,trafficdensityorenvironments,images,etc.)doesnot
dependonthenumberofcells,butonlyonthesizeoftheplanningareainpixels.
Thefollowinginformationcanprovideyouwithanestimateofdiskusagefordifferentgeographicdata:
Clutterclassmapsrequire1byteperpixel(2bytesforPlanetformat).
Backgroundimagesrequirefrom1to3bytesperpixel.
Trafficmapsrequire1byteperpixel(2bytesforPlanetformat).
DTMorclutterheightmapsrequire2bytesperpixel.
Populationmapsorothergenericmapsrequirefrom1to4bytesperpixel.
Foronecluttermap,oneDTMmap,onetrafficmap,andonebackgroundimage,youcanestimate6bytesperpixelofthe
inputarea.Thisdatacanbesharedbetweendifferentplanningalternativesofthesamenetwork.
If an embedded geographic data file is deleted from the project, Atoll automatically
compressestheATLfiletoavoidfilefragmentation.
CellSpecificResults
Foraprojectwithalargenumberofcells,itisimportanttoconsiderthediskspacerequiredbythepropagationprediction
resultsofeachcell.Here,thecellcalculationareaandthecalculationresolutionareimportantfactors.
113
Forsk2014
Cellspecificresultsrequire2bytesperpixel.Forexample,thepropagationresultsforasectorwithacalculationareaof1024
x1024pixelswillrequire2MBdiskspace.
IftherearedifferentATLfilesforplanningthesamepartofthenetworkindifferentways,eachATLfilewillrequirethesame
amountofdiskspace.
Thesameruleappliestoextendedpathlossmatricesaswell.
Ifembeddedpathlossmatricesareexternalised,AtollautomaticallycompressestheATL
filetoavoidfilefragmentation.
NetworkWideOutput
Networkwideoutput(rasterresults)mainlydependson:
Thesizeoftheplanningarea
Thepixelsize
Thenumberofcoveragepredictions
Thetypesofcoveragepredictions
Coveragepredictionscanhaveanumberoflayersdependingonthecalculationcriteria.Therecanbeasinglelayerforthe
entire networkor alayerpertransmitter,sector,or subcell. The resultingsize depends on the number of layers andthe
numberofcoloursandthresholds.Therefore,Atollcoveragepredictionscanrequirebetween1bitand2bytesperpixelof
thecalculationarea.
AtollcancompressthecoveragepredictionresultswhensavingaATLfiletoavoidfile
fragmentation.
Youcanconsider14bytesperpixelasaroughestimatetodeterminethediskspace
requiredforeachindividualATLfile.
TemporaryDiskSpace
Atollrequiressomediskspacetotemporarilystoreintermediateresultsduringcalculations.Afileiscreatedinthesystems
temporary directory whose size depends on the calculations. This file is described in the section on RAM requirements.
Likewise,atemporaryfileiscreatedwhenusingthe"SaveAs"command.Thesefilesareerasedafterthecalculationsoronce
thestoragehasfinished.
OtherDiskSpaceRequirements
OtherobjectsinaATLfilethatrequirediskspacecaneasilybeneglectedinreallifescenariossincetherequireddiskspace
dependingonthesizeoftheplanningareaandthenumberoftransmittersismuchhigher.
ATLfilesstoredatabasetablesandcalculationresults.AnemptyATLfilerequiresaround500 KB.Eachadditionalsiterequires
between1and2 KB,whichisnegligiblecomparedtothesizeofthepropagationresults.
Furthermore,thesizeofvectorfilesisnegligiblecomparedtothatofothergeographicdata,astheirsizeisusuallymuch
smallerthantheDTM,clutterheight,andclutterclassmaps.
When saving an ATL file, Atoll estimates the size of unused spaces in the file due to
fragmentation.If theamountofunusedspacesis morethan halfofthe usefulspace,
Atollproposescompressingthefile.
10.15.2 RAMRequirements
Usually, 512 MB of RAM in a workstation is sufficient for all operations with Atoll, provided that there are no other
applicationsbeingusedinparallelthatconsumelargeamountsofmemory.
Starting Atoll withoutloading a projectrequires around 20 MB of RAM (asmonitoredwiththeWindows Task Manager).
Loadingaprojectwith500sites,afewpredictions,andsomesimulationscanincreasetheconsumedmemorytoaround50
to100 MB.
MonteCarloSimulations
UMTSMonteCarlosimulationsarecalculationsthatconsumelargeamountsofmemory.Thememoryrequirementofthese
calculationsisafunctionofthefollowing:
114
Thenumberofsitesinvolved
AT321_AM_E1
Thenumberoftransmittersinvolved
Thenumberofcellsinvolved
ThenumberofmobilesgeneratedbytheUMTSsimulation
Thenumberoftransmitterscoveringapixel
Thenumberofservicessimulated
Thenumberofneighbourspercell
The"DetailedResults"and"LimitActiveSettoNeighbours"flags
Thenumberoflinkspermobile
Thenumberofchannelelementspersite
Mostoftheseparametershaveminorinfluencesandtheactualrequirementsaremostlygovernedbythenumberofcellsand
thenumberofmobilesgenerated.
Assumingthattherearethreecarriersusedandthenumberoftransmittersandmobilesishighenoughsothattheotherinput
canbeignored,therequiredmemorycanberoughlyapproximatedby:
R = 14.0 t + 3.25 m
fornormalsimulations
R = 14.0 t + 4.3 m
usingthe"detailedresults"option
withR:peakRAMrequirementinKBytes
t:numberoftransmittersaffectingthecomputationzone
m:numberofmobilesgeneratedbytheUMTSsimulation
Example:Tocalculatefor500sites(or1500transmitters)and2400mobiles,around28 MBofRAMarerequiredforanormal
simulationand30 MBifdetailedresultsaretobestoredaswell.
Pleasenotethatthisisthepeakrequirement.Lessmemorywillberequiredoncethe
calculationsareterminated.
This approximation also considers effects due to the operating system, such as
memoryoverallocationduetofragmentation.Itisaconservativeapproximationand
inmostcasestheactualRAMrequirementwillbebelowthesecalculatedfigures.
AmoreaccurateestimationoftheusedandrequiredmemoryforUMTSsimulationsis
availableintheSourceTraffictabofthenewsimulationgroupdialogue.Toactivate
thememoryestimationfeature,youmustaddanoptionintheAtoll.inifile.Formore
information,see"EstimatingRequiredandUsedMemorySizeforUMTSSimulations"
onpage 172.
CoveragePredictions
RAMrequiredduringcoveragepredictioncalculations(networkwiderasterresult)isthesameastherequiredadditionaldisk
space,i.e.,between1bitand2bytesperpixelofthecalculationarea.Apartfromthis,temporarymemoryisrequiredfor
calculationslike"Coveragebytransmitter"and"Coveragebysignallevel".Forthese,Atolltemporarilyallocatesanaverage
of4bytesmoreperpixel(8bytes,ifthebestservermarginisnotzero)ofthecalculationarea.
Example:TheParisregionhasasizeofaround10x13 km.Foracalculationresolutionof25 m,thisequals5.2millionpixels.
IfacoveragepredictioncalculatesthesignalstrengthoftheUMTSpilotinlessthan16colours,itwouldrequireamemoryof
4bitsperpixel,oratotalof2.6 MB.Duringthecalculation,Atollwouldalsorequire4morebytesperpixel,whichequals
20.8 MBmoreapartfromthe2.6 MB.
For large networks, to avoid loading the entire computation zone in memory, Atoll
divides the coverage prediction computations into smaller tiles, and carries out the
computationsonthemsuccessively.Thissubdivisionisinvisibletotheuser.
115
116
Forsk2014
Chapter11:ConfigurationFiles
AT321_AM_E1
11 ConfigurationFiles
Configurationfilescanbeusedtostoreparameteranddisplaysettings.Thesefilesareoptional,notrequiredforworkingwith
Atoll,butareusefulmeansformakingworkeasier.
Thischapterdescribestheformatsofthesefilesindetail:
Userconfigurationfiles(UTF8encodedXMLformatGEOorCFGfiles)
A user configuration file containing only the geographic data settings can be saved with a GEO extension. A user
configuration file containing the geographic data settings and other parameter settings can be saved with a CFG
extension.
UserconfigurationfilesmustbecreatedusingAtolltoensurecorrectsyntaxandstructure.Itispossibletoeditthe
contentsofthesefilesinanXMLeditorandmakechangesifrequired(forexample,toupdatethepathstogeographic
datafiles).FormoreinformationonhowtocreateandloaduserconfigurationfilesinAtoll,seetheUserManual.
Thesefilescanstore:
Geographicdatasettings
Filtering,focus,computation,printing,andgeographicexportzones
Mapcentreandzoomlevel
Folderconfigurations
ListofcoveragepredictionsinthePredictionsfolderandtheirsettings
Automaticneighbourallocationparameters
Automaticfrequencyplanningparameters(GSMGPRSEDGEdocuments)
Automaticscramblingcodeallocationparameters(UMTSHSPAandTDSCDMAdocuments)
AutomaticPNoffsetallocationparameters(CDMA2000documents)
AutomaticOFDMresourceallocationparameters(LTE,WiMAX,WiFi)
Microwavelinkparameters
Fullpathstomacrofiles
Projection and display coordinate systems are stored in the database, not in user
configurationfiles.
Simulationsettingsarenotstoredinuserconfigurationfiles.
For more information on the contents of user configuration files, see "Contents of User Configuration Files" on
page 118.
AuserconfigurationfilecanbeautomaticallyloadedwhenAtollisrunif:
a. ThefileisidentifiedinthecommandlineparameterCfg"cfgfilename"(see"AtollCommandLineParameters"on
page 24formoreinformation),or
b. The file is named "Atoll.cfg" and is located in the Atoll installation folder. This file will be ignored if a user
configurationfileisloadedthroughthecommandlineparameter.
Additionalconfigurationfiles(UTF8encodedXMLformatCFGfilesorplaintextINIfiles)
ThefollowingparametersettingscanbestoredinadditionalconfigurationfileswithaCFGextension:
Printsetupconfiguration
Tableimport/exportconfiguration
Coveragepredictionreportconfiguration
ThefollowingparametersettingscanbestoredinspecificINIfiles:
CWmeasurementimportconfiguration
Drivetestdataimportconfiguration
For more information on the contents of additional configuration files, see "Contents of Additional Configuration
Files"onpage 141.
Custompredictionsfile(UTF8encodedXMLfiles)
This file (one for all customised predictions) contains the list and parameter settings of customised coverage
predictions.Bydefault,thisfileisnamed"Studies.xml"andislocatedintheAtollinstallationfolder.
ThecustompredictionsfilemustbecreatedusingAtolltoensurecorrectsyntaxandstructure.Itispossibletoedit
the contents of this file in an XML editor and make changes if required. For more information on working with
customisedpredictionsinAtoll,seetheUserManual.
117
Forsk2014
Formoreinformationonthecontentsofthecustompredictionsfile,see"ContentoftheCustomPredictionsFile"on
page 145.
PredictionsfilescalculatedbyValueIntervals(UTF8encodedXMLfiles)
Thesefiles(oneperprediction)containtheparametersettingsofthecoveragepredictionscalculatedwiththedisplay
type (on the General tab of the Properties dialog box) set to "Value intervals". By default, these files are named
"<prediction_name>.XML"andarelocatedin"C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}".
11.1 ContentsofUserConfigurationFiles
Thedescriptionsandexamplesprovidedbelowforeachparametersetcanhelpunderstandtheformatandfunctionofthe
userconfigurationfiles.Thefollowingdetailsareavailable:
"GeographicDataSet"onpage 118
"MapCentreandZoomLevel"onpage 122
"Zones"onpage 121
"FolderConfiguration"onpage 122
"CoveragePredictions"onpage 129
"AutomaticNeighbourAllocationParameters"onpage 131
"AutomaticFrequencyPlanningParameters"onpage 133
"AutomaticScramblingCodeAllocationParameters"onpage 134
"AutomaticPNOffsetAllocationParameters"onpage 136
"MicrowaveRadioLinksParameters"onpage 138
"Macros"onpage 141.
11.1.1 GeographicDataSet
Thefollowingparametersaresavedforvariousgeographicdatatypes:
118
<DegreeFormat>:Formatusedtodisplaydegrees,minutes,andsecondsforgeographiccoordinatesystems
Population,geoclimaticparameters,vectortrafficmaps,andothervectorlayers:
<Name>:Nameofthefolder
<Display>:(Differentcombinationsofthefollowingparametersexistindifferentdisplaysettings.)
Displaytype<type>,selectedfield<FieldSelector>,fielddescription<FieldDesc>containing<FieldId>(same
as <FieldSelector>) and <FieldTitle>, visibility flag <visible>, and visibility range between <minZoom> and
<maxZoom>
<SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, background
colour<BackColor>,andfontstyle<Style>
<LabelFont>properties,suchas:labelfontname<Name>,labelfontsize<Size>,labelfontcolour<Color>,
labelfontbackgroundcolour<BackColor>,andlabelfontstyle<Style>
<Items> properties, such as for each item: <Value>, <Min>, <Max>, <Legend>, <MainColor>,
<SecondaryColor>,<LineStyle>,<LineWidth>,and<FillStyle>
<AddToLegend>:Addtolegendoptioncheckedornot
<Type>:Datatypeproperties,suchas<Name>,<Formats>,<Type>,and<Integrable>
<File>:Containsthefileformat,path,coordinatesysteminformation.
<Format>ofand<Path>tolinkedfiles,ifany
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>
ClutterClasses:
Displatetype<type>,selectedfield<FieldSelector>,fielddescription<FieldDesc>containing<FieldId>(same
as<FieldSelector>)and<FieldTitle>,transparencylevel<Opacity>,visibilityflag<visible>,andvisibilityrange
between<minZoom>and<maxZoom>
<Attributes>,suchas:<records>and<fields>,whichare,
Common:CODE,COLOR,NAME,HEIGHT,INDOOR
Under<GSM>:STDDEV,COVERI_STDDEV,TX_DIV_GAIN,ANT_HOP_GAIN
AT321_AM_E1
Under <UMTS>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, ALPHA, FORTHO,

SM_GAIN_FACTOR,STTD_GAIN_OFFSET
Under
<LTE>:
STDDEV,
COVERI_STDDEV,
MIMO_GAIN_FACTOR,
DIV_GAIN_OFFSET_DL,
DIV_GAIN_OFFSET_UL
Under<1XRTT>:STDDEV,EC_IO_STDDEV,EB_NT_DL_STDDEV,EB_NT_UL_STDDEV,ALPHA,FORTHO
Under <TDSCDMA>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, FORTHO_UL,
FORTHO_DL,ANGULAR_SPREAD
Under <IEEE_802.16e>: STDDEV, COVERI_STDDEV, MIMO_GAIN_FACTOR, STTD_OFFSET_DL,
STTD_OFFSET_UL
Under<WiFi>:STDDEV,COVERI_STDDEV,MIMO_GAIN_FACTOR,STTD_OFFSET_DL,STTD_OFFSET_UL
<DefaultValues>,forthefieldsstatedabove.
ClutterHeightsandDigitalTerrainModels:
as<FieldSelector>)and<FieldTitle>,transparencylevel<opacity>,visibilityflag<visible>,andvisibilityrange
between<minZoom>and<maxZoom>
<File>:<Format>and<Path>tolinkedfiles,ifany
Sample
Samplewithdisplaysettovalueintervals.
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<Geodataset version="2">
<DegreeFormat>0</DegreeFormat>
<Population> // or <GeoClimaticParams> or <Vectors>
<Name>Population</Name> // or <Name>Geoclimatic Parameters</Name>
or <Name>Vectors</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
<Type>ByIntervals</Type>
<FieldSelector>80000001</FieldSelector>
<FieldDesc>
<FieldId>80000001</FieldId>
<FieldTitle>Population (inhab./km)</FieldTitle>
</FieldDesc>
<SymbolFont>
<Name>Wingdings</Name>
<Size>-120</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-83</Size>
<Style>0</Style>
119
</LabelFont>
<Items>
<Item>
<Min>900.</Min>
<Max>1000.</Max>
<Legend>900 <=Population(Density) <1 000</Legend>
<MainColor>255 96 0</MainColor>
<SecondaryColor>255 0 0</SecondaryColor>
</Item>
</Items>
</Display>
<AddToLegend>0</AddToLegend>
<Type>
<Name>Population</Name>
<Formats>15</Formats>
<Type>800</Type>
<Integrable>1</Integrable>
</Type>
<Files/>
</Population> // or </GeoClimaticParams> or </Vectors>
<ClassifiedClutter UseOnlyDefault="0">
<Display>
<FieldDesc>
<FieldTitle>Height (m)</FieldTitle>
</FieldDesc>
<Opacity>50</Opacity>
<Items>
<Item>
<Min>54.</Min>
<Max>56.</Max>
<Legend>54 <=Height (m) <56</Legend>
<LineStyle>5</LineStyle>
<LineWidth>10</LineWidth>
<FillStyle>1</FillStyle>
</Item>
</Items>
</Display>
<Attributes>
<fields>
<field length="1" type="uint" name="CODE"/>
<field length="4" type="int" name="COLOR"/>
120
Forsk2014
AT321_AM_E1
<field length="50" type="text" name="NAME"/>

<field length="4" type="real" name="HEIGHT"/>
<field length="2147483647" type="text" name="INDOOR"/>
</fields>
<records/>
</Attributes>
<Name>Clutter Classes</Name>
<DefaultValues>
</DefaultValues>
</ClassifiedClutter>
<Altitudes> // or <BuildingHeights>
<Name>Digital Terrain Model</Name> // or <Name>Clutter Heights</Name>
<Display>
<FieldDesc>
<FieldTitle>Altitude</FieldTitle>
</FieldDesc>
<Items>
<Item>
<Min>900.</Min>
<Max>1000.</Max>
<Legend>900 <=Altitude <1 000</Legend>
</Item>
</Items>
</Display>
</Altitudes> // or </BuildingHeights>
</Geodataset>
</Atoll>
11.1.2 Zones
Theuserconfigurationfilesstorethecoordinatesoftheverticesofthefiltering,focus,computation,printing,andgeographic
exportzonepolygons,i.e.,thepointsformingthesepolygons.Thefirstandthelastpointshavethesamecoordinates.
Sample
Thefollowingsamplehasrectangularcomputationandfocuszonesofthesamesize.
121
Forsk2014

<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>
11.1.3 MapCentreandZoomLevel
Thefollowingparametersaresaved:
<MapPosition>:XandYcoordinatesofthecentreofthemapwindowandthezoomlevel.
Sample
<Atoll>
<MapPosition CenterX="609433" CenterY="5632019" Scale="250000"/>
</Atoll>
11.1.4 FolderConfiguration
Thefollowingparametersaresavedforthefollowingfolders:
122
Sitesfolder:
<Display>:
as <FieldSelector>) <FieldTitle> and <FieldDBName>, visibility flag <Visible>, and visibility range between
<MinZoom>and<MaxZoom>
<SymbolFont> properties, such as font name <Name>, font size <Size>, font colour <Color>, background
<LabelFont>properties,suchaslabelfontname<Name>,labelfontsize<Size>,labelfontcolour<Color>,label
fontbackgroundcolour<BackColor>,andlabelfontstyle<Style>
<Items>properties,suchasforeach<Item>:<Value>,<Legend>,<MainColor>,<SecondaryColor>,<Symbol>,
and<SymbolSize>
<DataTips>:Listof<items>displayedintiptexts
<Labels>:Listof<items>displayedinlabels
<DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration
<Filter>,<Groups>,and<Sort>criteria
<Configuration>:Ifanyconfigurationexistsforthefolder,thistagcontainstheconfiguration<Name>andthe
Antennasfolder:
AT321_AM_E1
Transmitters,MultiHops,andPointtoMultipointfolders:
<Display>:
Displatetype<Type>,selectedfield<FieldSelector>,fielddescription<FieldDesc>containing<FieldId>(same
as <FieldSelector>) <FieldTitle> and <FieldDBName>, visibility flag <Visible>, and visibility range between
<LabelFont>properties,suchaslabelfontname<Name>,labelfontsize<Size>,labelfontcolour<Color>,label
<Items>properties,suchasforeach<Item>:<Value>,<Legend>,<MainColor>,<SecondaryColor>,<Symbol>,
and<SymbolSize>
<OFDM_AFP>:LTE,WiMAX,andWiFifrequencyallocationconstraintweights:
<Techno>:Nameofthetechnology
<NeighbourWeight>:Weightofthefirstorderneighbourrelation
<InterNeighbourWeight>:Weightoftherelationbetweentwoneighboursofacommoncell
<IMWeight>:Weightoftheinterferencematricesrelation
<DistanceWeight>:Weightofthedistancebasedrelation
<PCI_Alloc>:LTEphysicalcellIDallocationconstraintweights:
<SecondNeighbourWeight>:Weightofthesecondorderneighbourrelation
<IDWeight>:WeightofthephysicalcellIDconstraint
<PSSWeight>:WeightofthePSSIDconstraint
<SSSWeight>:WeightofthesameSSSIDpersiteconstraint
<ULDMRSSGWeight>:WeightoftheULDMRS(PCIMod30)collisionconstraint
<DLRSSCaWeight>:WeightofthesingleantennaportDLCRS(PCIMod6)collisionconstraint
<PCFICHREGWeight>:WeightofthePCFICHREG(PCIMod(N_RB/2))collisionconstraint
<PI_Alloc>:WiMAXpreambleindexallocationconstraintweights:
<SecondNeighbourWeight>:Weightofthesecondorderneighbourrelation
<IndexWeight>:Weightofthepreambleindexconstraint
<SegmentWeight>:Weightofthesegmentconstraint
<PermBaseWeight>:Weightofthesamecellpermbasepersiteconstraint
Linksfolder:
<Display>:Containsvisibilityflag<visible>,andvisibilityrangebetween<minZoom>and<maxZoom>
<DefaultConfiguration>:Thedefaultconfigurationforthefolder
<LabelFont>properties,suchas:labelfontname<Name>,labelfontsize<Size>,labelfontcolour<Color>,label
<SiteDisplay>properties,suchas:
<Symbol>:Symbolusedformicrowavelinks
<ShowText>:Captionformicrowavelinksshownornot
<RepeaterDisplay>properties,suchas:
CWMeasurementsfolder:
<Distance>:Theminimum<Min>andmaximum<Max>distanceformeasurementfiltering
123
Forsk2014
<DistanceUnit>:Thedistanceunit
<Measure>:Theminimum<Min>andmaximum<Max>measuredlevelforfiltering
<MeasureUnit>:Themeasurementunit
<Angle>:Theminimum<Min>andmaximum<Max>angleformeasurementfiltering
<Relative>:Whethertheangleisrelativetoeachtransmittersazimuthoranabsolutevalue
<Clutter>:Foreach<Class>,its<Code>andwhetheritisinthe<Filter>ornot
<Advanced>:Anyadvancedfilterusedforfiltering
<PathLosses>:Pathlosstuingparameters,i.e.,<ParallelAxisRadius>,<PerpendicularAxisRadius>,<GlobalMargin>,
<LocalMargin>,and<Threshold>
<Display>:
Displate type <Type>, selected field <FieldSelector>, visibility flag <Visible>, and visibility range between
<Items> properties, such as for each <Item>: <Legend>, <MainColor>, <SecondaryColor>, <Symbol>, and
<SymbolSize>
DriveTestDatafolder:
<Techno>:Nameofthetechnology(ifexportedfroma3GPPMultiRATdocument.
<Clutter>:Foreach<Class>,its<Code>andwhetheritisinthe<Filter>ornot
<Advanced>:Anyadvancedfilterusedforfiltering
<PathLosses>:Pathlosstuingparameters,i.e.,<ParallelAxisRadius>,<PerpendicularAxisRadius>,<GlobalMargin>,
<LocalMargin>,and<Threshold>
<Display>:
Displate type <Type>, selected field <FieldSelector>, visibility flag <Visible>, and visibility range between
<Items> properties, such as for each <Item>: <Legend>, <MainColor>, <SecondaryColor>, <Symbol>, and
<SymbolSize>
PropagationModelsandSmartAntennaModelsfolders:
Sample
<Atoll>
<FoldersConfigurations>
<Sites>
<Name>Sites</Name>
<Display>
<Type>ByValues</Type>
<FieldDesc>
<FieldTitle>Vendor</FieldTitle>
124
AT321_AM_E1
</FieldDesc>
<SymbolFont>
<Size>-120</Size>
<Style>32</Style>
</SymbolFont>
<LabelFont>
<Size>-80</Size>
<Style>33</Style>
</LabelFont>
<Items>
<Item>
<Value>Vendor</Value>
<Legend>Vendor</Legend>
<Symbol>164</Symbol>
<SymbolSize>120</SymbolSize>
</Item>
</Items>
<DataTips>
<Item>0</Item>
</DataTips>
<Labels>
<Item>0</Item>
</Labels>
</Display>
<DefaultConfiguration>
<Groups>Type</Groups>
</DefaultConfiguration>
</Sites>
<Antennas>
<Name>Antennas</Name>
<Filter>([CONSTRUCTOR]= Kathrein)</Filter>
<Configuration>
<Name>Conf</Name>
<Filter>([CONSTRUCTOR]= Kathrein)</Filter>
</Configuration>
</Antennas>
<Transmitters> // or <MWMultiHops> // or <MWHubs>
125
<Name>Transmitters</Name> // or <Name>Multi-Hops</Name> //
or <Name>Point to Multipoint</Name>
<Display>
<Type>ByValues</Type>
<FieldDesc>
<FieldTitle>Automatic</FieldTitle>
</FieldDesc>
<Items>
</Items>
<DataTips>
<Item>0</Item>
</DataTips>
</Display>
<DefaultConfiguration/>
</Transmitters> // or </MWMultiHops> // or </MWHubs>
<MWLinks>
<Name>Links</Name>
<Display>
</Display>
<LabelFont>
<Size>-83</Size>
<Style>0</Style>
</LabelFont>
<SiteDisplay>
<SymbolFont>
<Size>80</Size>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Size>-80</Size>
126
Forsk2014
AT321_AM_E1

<Style>0</Style>
</LabelFont>
</SiteDisplay>
<ShowText>0</ShowText>
<RepeaterDisplay>
<SymbolFont>
<Size>80</Size>
<Style>0</Style>
</SymbolFont>
</RepeaterDisplay>
</MWLinks>
<CWMeasurements>
<Distance>
<Min>0.</Min>
<Max>1000.</Max>
</Distance>
<DistanceUnit>0</DistanceUnit>
<Measure>
<Min>-105.</Min>
<Max>-90.</Max>
</Measure>
<MeasureUnit>0</MeasureUnit>
<Angle>
<Min>-180.</Min>
<Max>180.</Max>
</Angle>
<Relative>Yes</Relative>
<Clutter>
<Class>
<Code>1</Code>
<Filter>Yes</Filter>
</Class>
</Clutter>
<Advanced>([DIST]> 500)</Advanced>
<PathLosses>
<ParallelAxisRadius>200.</ParallelAxisRadius>
<PerpendicularAxisRadius>100.</PerpendicularAxisRadius>
<GlobalMargin>30.</GlobalMargin>
<LocalMargin>30.</LocalMargin>
<Threshold>-130.</Threshold>
</PathLosses>
<Display>
127
<FieldSelector>Error (P-M) (dB)</FieldSelector>
<SymbolFont>
<Size>-120</Size>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Size>-83</Size>
<Style>0</Style>
</LabelFont>
<Items>
<Item>
<Min>-20.</Min>
<Legend>Error (P-M) (dB) >=-20</Legend>
</Item>
</Items>
<DataTips>
<Item>M (dBm)</Item>
</DataTips>
<Labels>
<Item>M (dBm)</Item>
</Labels>
</Display>
</CWMeasurements>
<TestMobileData>
<Techno>GSM</Techno>
<Clutter>
<Class>
<Code>1</Code>
<Filter>Yes</Filter>
</Class>
</Clutter>
<Advanced></Advanced>
<PathLosses>
<ParallelAxisRadius>200.</ParallelAxisRadius>
<PerpendicularAxisRadius>100.</PerpendicularAxisRadius>
<GlobalMargin>30.</GlobalMargin>
128
Forsk2014
AT321_AM_E1
<LocalMargin>30.</LocalMargin>
<Threshold>-130.</Threshold>
</PathLosses>
<Display>
<FieldSelector>Ec_I0</FieldSelector>
<SymbolFont>
<Size>-120</Size>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Size>-83</Size>
<Style>0</Style>
</LabelFont>
<Items>
<Item>
<Min>-60.</Min>
<Legend>Ec_I0 >=-60</Legend>
</Item>
</Items>
</Display>
</TestMobileData>
<PropagationModels> // or <SmartAntennasModels>
<Name>Propagation Models</Name> // or <Name>Smart Antenna Models</Name>
</PropagationModels> // or </SmartAntennasModels>
</FoldersConfigurations>
</Atoll>
11.1.5 CoveragePredictions
ThelistofcoveragepredictionsavailableinthePredictionsfolderandthefollowingparametersaresaved:
Generaltab:
<Techno>:Nameofthetechnology
<Resolution>:Predictionresolution
<Configuration>:<Filter>,<Groups>,and<Sort>criteriafortheprediction
<LockedStudy>:Lockedornot
Conditionstab:Dependontechnologiesandpredictiontypes.
<Reliability>:Celledgecoverageprobability
<Indoor>:Indoorcoveragecheckedornot
<WithShadowing>:Shadowingmargintakenintoaccountornot
129
...
Displaytab:
Displaytype<type>,selectedfield<FieldSelector>,fielddescription<FieldDesc>containing<FieldId>(same
as<FieldSelector>)and<FieldTitle>,visibilityflag<visible>,opacity<Opacity>,andvisibilityrangebetween
<minZoom>and<maxZoom>
Sample
GSMcoveragebysignallevel
<Atoll>
<Studies>
<CoverageTRXStudy>
<Techno>GSM</Techno>
<Name>GSM: Coverage by Signal Level 0</Name>
<Display>
<Items>
<Item>
<Min>-75.</Min>
<Legend>Best Signal Level (dBm) >=-75</Legend>
</Item>
<Item>
<Min>-85.</Min>
</Item>
<Item>
<Min>-95.</Min>
130
Forsk2014
AT321_AM_E1
</Item>
<Item>
<Min>-105.</Min>
</Item>
</Items>
<DataTips>
<Item>c0000000</Item>
<Item>c0000001</Item>
</DataTips>
</Display>
<Resolution>50</Resolution>
<GUID>{52D66F26-5710-4F4B-A327-6DAFF337AB21}</GUID>
<LockedStudy>0</LockedStudy>
<ComputeHisto>1</ComputeHisto>
<HistoPerTx>0</HistoPerTx>
<HistoLabel></HistoLabel>
<Conditions>
<FieldDbm>
<Min>-105.</Min>
</FieldDbm>
<Reliability>0.75</Reliability>
<TRXType>BCCH</TRXType>
<DefTrgThreshold>1</DefTrgThreshold>
<Indoor>0</Indoor>
<WithShadowing>0</WithShadowing>
</Conditions>
</CoverageTRXStudy>
</Studies>
</Atoll>
11.1.6 AutomaticNeighbourAllocationParameters
The following parameters are saved for intratechnology (intracarrier and intercarrier) and intertechnology automatic
neighbourallocations:
<ANP_options>:Intratechnology(intracarrier)neighbourallocationparameters
<ANP_IL_options>: Intratechnology intercarrier neighbour allocation parameters (UMTS HSPA and CDMA2000
documents)
<ANP_IT_options>:Intertechnologyneighbourallocationparameters
A<Techno></Techno>tagisalsopresentiftheuserconfigurationisexportedfroma3GPPMultiRATdocument.This
tagcontainsthenameofthetechnologytowhichtheparametersbelong.
131
Forsk2014
Thefollowingparametersaresaved:
Parameterscommontoalltechnologies:
<numMax>:Maximumnumberofneighbourstoallocate
<useCoSite>:Forcecositetransmitters/cellsasneighboursornot
<useAdjacent>:Forceadjacenttransmitters/cellsasneighboursornot
<symetric>:Forcesymmetrybetweenneighboursornot
<keepNeighbs>:Resetexistingneighboursorkeepthem
<MaxDist>:Maximumdistancebetweensites
<PercentCoverage>:Coverageconditions:Minimumpercentageofcoveredarea
<UseShadowing>:Coverageconditions:Takeshadowingintoaccountornot
<reliability>:Coverageconditions:Celledgecoverageprobability
<applyConstraints>:Forceexceptionalpairsasneighboursornot
<covBased>:Notimplementedyet
<minCov>:Neighbourimportance:minimumfactorforcoverage
<maxCov>:Neighbourimportance:maximumfactorforcoverage
<minAdj>:Neighbourimportance:minimumfactorforadjacency
<maxAdj>:Neighbourimportance:maximumfactorforadjacency
<minCos>:Neighbourimportance:minimumfactorforcosite
<maxCos>:Neighbourimportance:maximumfactorforcosite
<minDistImportance>:Neighbourimportance:minimumfactorfordistance
<maxDistImportance>:Neighbourimportance:maximumfactorfordistance
<resolution>:Resolutionusedforcoveragecalculationforoverlapping(1meansthedefaultresolutiondefinedin
thepropertiesofthePredictionsfolderisused)
<UseIndoor>:Coverageconditions:Useindoorlossesdefinedperclutterclassornot
<UseGlobalThreshold>:CoverageconditionsforWiMAXandLTE:WhethertouseaglobalminimumpreambleC/
NorRSRP,orpercellvalues
ParametersspecifictoGSMGPRSEDGE:
<minField>:Coverageconditions:MinimumBCCHsignallevel
<margin>:Coverageconditions:Marginfortheminimumsignallevel(Handoverstart)
<traffic>:Coverageconditions:Taketrafficintoaccountornot
<deltaMax>:Coverageconditions:Handoverend
ParametersspecifictoUMTSHSPA,TDSCDMA,andCDMA20001xRTT1xEVDO:
<minField>:Coverageconditions:Minimumpilotsignallevel
<margin>:Coverageconditions:Marginfortheminimumsignallevel(Ec/I0margin)
<traffic>:Coverageconditions:Taketrafficintoaccountornot
<deltaMax>:Coverageconditions:Handoverend
<EcIoMin>:Coverageconditions:MinimumEc/I0
<usePmax>:Coverageconditions:Usemaximumpowerornot
<PerCentMaxPower>:Coverageconditions:Percentageofmaximumpowertoconsiderincalculations
<EcIoMax>:Coverageconditions:MaximumEc/I0
<useEcIoMax>:Coverageconditions:UsemaximumEc/I0ornot
<TDrop>:TDropvalue(TDSCDMAdocuments,intratechnologyneighbourallocationonly)
ParametersspecifictoWiMAX802.16eandLTE:
<HOStart>:Thehandoverstartmargin(intratechnologyneighbourallocationonly)
<HOEnd>:Thehandoverendmargin(intratechnologyneighbourallocationonly)
<BSmargin>:RSRPmarginfromthebestserver(intertechnologyneighbourallocationonly)
Sample
UMTSHSPAintertechnology,intracarrierneighbourallocationparameters:
<Atoll>
<ANP_options>
<Techno>UMTS</Techno>
<numMax>16</numMax>
<resolution>-1</resolution>
<minField>-10500</minField>
<margin>500</margin>
<useCoSite>1</useCoSite>
<useAdjacent>1</useAdjacent>
132
AT321_AM_E1
<traffic>0</traffic>
<symetric>0</symetric>
<keepNeighbs>0</keepNeighbs>
<MaxDist>10000</MaxDist>
<PercentCoverage>1000</PercentCoverage>
<UseShadowing>0</UseShadowing>
<reliability>7500</reliability>
<UseIndoor>0</UseIndoor>
<deltaMax>1200</deltaMax>
<applyConstraints>0</applyConstraints>
<covBased>1</covBased>
<minDistImportance>100</minDistImportance>
<maxDistImportance>1000</maxDistImportance>
<minCov>1000</minCov>
<maxCov>3000</maxCov>
<minAdj>3000</minAdj>
<maxAdj>6000</maxAdj>
<minCos>6000</minCos>
<maxCos>10000</maxCos>
<UseGlobalThreshold>0</UseGlobalThreshold>
<EcIoMin>-1400</EcIoMin>
<usePmax>0</usePmax>
<PerCentMaxPower>5000</PerCentMaxPower>
<EcIoMax>-700</EcIoMax>
<useEcIoMax>0</useEcIoMax>
</ANP_options>
</Atoll>
11.1.7 AutomaticFrequencyPlanningParameters
Thefollowingparametersaresavedforautomaticfrequencyplanning(GSMGPRSEDGEdocuments):
<defSeparations__CONF_CO_SITE_BB>:DefaultcositeseparationrulefortwoBCCHtypeTRXs.
<defSeparations__CONF_CO_CELL_BB>:DefaultcotransmitterseparationrulefortwoBCCHtypeTRXs.
<defSeparations__CONF_NEIGH_BOUR_BB>:DefaultneighbourseparationrulefortwoBCCHtypeTRXs.
<defSeparations__CONF_CO_SITE_BT>:DefaultcositeseparationruleforaBCCHandaTCHtypeTRX.
<defSeparations__CONF_CO_CELL_BT>:DefaultcotransmitterseparationruleforaBCCHandaTCHtypeTRX.
<defSeparations__CONF_NEIGH_BOUR_BT>:DefaultneighbourseparationruleaforBCCHandaTCHtypeTRX.
<defSeparations__CONF_CO_SITE_TT>:DefaultcositeseparationrulefortwoTCHtypeTRXs.
<defSeparations__CONF_CO_CELL_TT>:DefaultcotransmitterseparationrulefortwoTCHtypeTRXs.
<defSeparations__CONF_NEIGH_BOUR_TT>:DefaultneighbourseparationrulefortwoTCHtypeTRXs.
<freezeState>:LastminuteresourcefreezingoptionsavailableintheAFPlaunchwizard
<numMinutes>:TargettimeallotedtotheAFP
<useDTX>:Considertheeffectofdiscontinuoustransmissionornot
<dtxVocalFactor>:Voiceactivityfactorfordiscontinuoustransmission
<AfpBasedOnInterference>:Loadallpotentialinterferersornot
<AfpBasedOnSeparations>:Loadallthesubcellspotentiallyinvolvedinseparationconstraintsornot
<IM_calculate__WithTraffic>:Whethertrafficspreadingisuniformorbasedonthemapsusedinthedefaulttraffic
capture(forinterferencematricescalculation)
<IM_calculate__BestServerZoneMargin>:MarginincaseofBestsignallevelperHCSlayer(forinterferencematrices
calculation)
<IM_calculate__ServiceZoneType>:AllorBestsignallevelperHCSlayer(forinterferencematricescalculation)
<IM_calculate__reliability_X_10000>:Celledgecoverageprobability(forinterferencematricescalculation)
<TakeTfFromCapt>:WhethertrafficloadsarereadfromthedefaulttrafficcaptureorfromtheSubcellstable
<preferedSenario>:Scenariotype,i.e.,modificationofexistingTRXsallowedornot
133
Forsk2014
Sample
<Atoll>
<AFP_options>
<defSeparations__CONF_CO_SITE_BB>2</defSeparations__CONF_CO_SITE_BB>
<defSeparations__CONF_CO_CELL_BB>3</defSeparations__CONF_CO_CELL_BB>
<defSeparations__CONF_NEIGH_BOUR_BB>2</defSeparations__CONF_NEIGH_BOUR_BB>
<defSeparations__CONF_CO_SITE_BT>2</defSeparations__CONF_CO_SITE_BT>
<defSeparations__CONF_CO_CELL_BT>3</defSeparations__CONF_CO_CELL_BT>
<defSeparations__CONF_NEIGH_BOUR_BT>1</defSeparations__CONF_NEIGH_BOUR_BT>
<defSeparations__CONF_CO_SITE_TT>1</defSeparations__CONF_CO_SITE_TT>
<defSeparations__CONF_CO_CELL_TT>2</defSeparations__CONF_CO_CELL_TT>
<defSeparations__CONF_NEIGH_BOUR_TT>1</defSeparations__CONF_NEIGH_BOUR_TT>
<freezeState>0</freezeState>
<numMinutes>1000</numMinutes>
<useDTX>0</useDTX>
<dtxVocalFactor>70</dtxVocalFactor>
<AfpBasedOnInterference>1</AfpBasedOnInterference>
<AfpBasedOnSeparations>1</AfpBasedOnSeparations>
<IM_calculate__WithTraffic>0</IM_calculate__WithTraffic>
<IM_calculate__BestServerZoneMargin>5</IM_calculate__BestServerZoneMargin>
<IM_calculate__ServiceZoneType>1</IM_calculate__ServiceZoneType>
<IM_calculate__reliability_X_10000>7500</IM_calculate__reliability_X_10000>
<TakeTfFromCapt>1</TakeTfFromCapt>
<preferedSenario></preferedSenario>
</AFP_options>
</Atoll>
11.1.8 AutomaticScramblingCodeAllocationParameters
Thefollowingparametersaresavedforautomaticscramblingcodeallocation(UMTSHSPAandTDSCDMAdocuments):
134
<MinEcI0>:MinimumEc/I0constraint(notusedinTDSCDMA)
<margin>:Ec/I0margin(notusedinTDSCDMA)
<reliability>:Celledgecoverageprobability(notusedinTDSCDMA)
<DistanceMin>:Defaultreusedistance
<Strategy0>:Clusteredstrategyavailableornot
<Strategy1>:DistributedperCellstrategyavailableornot
<Strategy2>:OneCluster/SYNC_DLCodeperSitestrategyavailableornot
<Strategy3>:DistributedperSitestrategyavailableornot
<Strategy>:Scramblingcodeallocationstrategy
<FromScratch>:Resetallalreadyallocatedcodesornot
<UseCurrentNghbs>:Useexistingfirstorderneighboursornot
<NghbOrder>:Theorderofneigbourstotakeintoaccount,i.e.,1st,2nd,or3rd
<ComputeNghbs>:CalculateneighboursusingtheadditionEc/I0conditionsornot
<UseMaxCodes>:Useamaximumofcodesornot
<UseShadowing>:Shadowingtakenintoaccountornot(notusedinTDSCDMA)
<SameCodeForCarriers>:Allocatecarriersidenticallyornot
<NbClusterPerSite>:Numberoftransmitterspersiteamongwhichaclustershouldbedistributed
<ClustNghbs>:Additionalconstraintoftakingintoaccountthefirstorderneighboursinotherclusters
<Clust2ndNghbs>:Additionalconstraintoftakingintoaccountthesecondorderneighboursinotherclusters
<NbCodesPerCluster>:Thenumberofscramblingcodesinonecluster/SYNC_DL
<UseDistance>:Taketheminimumreusedistanceintoaccountornot
<UseExcepPairs>:Takeexceptionalpairsintoaccountornot
<minField>:Minimumpilotsignallevelconstraint(notusedinTDSCDMA)
<usePmax>:Usethemaximumdownlinktransmissionpowerornot(notusedinTDSCDMA)
AT321_AM_E1
<PerCentMaxPower>:Thepercentageofthemaximumdownlinkpoweris<usePmax>issetto0(notusedinTD
SCDMA)
<Max1stNghbCost>:Themaximumcostof1storderneighbours
<Max2ndNghbCost>:Themaximumcostof2ndorderneighbours
<Max3rdNghbCost>:Themaximumcostof3rdorderneighbours
<CoplanCost>:Thecostforintertechnologyneighbours
<MaxCoClusterCost>:Themaximumcostforsamecluster/SYNC_DLneighbours
<MaxDistCost>:Themaximumcostforaminimumreusedistanceconstraintviolation
<ExcepPairCost>:Thecostforexceptionalpairconstraintviolation
<UseCloseNghbs>:TaketheCloseNeighboursconstraintintoaccountornot(TDSCDMAonly)
<CloseDistance>:Maximumdistancewithinwhichcloseneighboursarelocated(TDSCDMAonly)
<CloseImportance>:Minimumimportancevalueofcloseneighbour(TDSCDMAonly)
<MaxCloseCost>:Maximumcostofacloseneighbourrelation(TDSCDMAonly)
Sample
<Atoll>
<SCP_options>
<MinEcI0>-1500.</MinEcI0>
<margin>500.</margin>
<reliability>5000.</reliability>
<DistanceMin>200000.</DistanceMin>
<Strategy0>1</Strategy0>
<Strategy>0</Strategy>
<FromScratch>1</FromScratch>
<UseCurrentNghbs>1</UseCurrentNghbs>
<NghbOrder>1</NghbOrder>
<ComputeNghbs>0</ComputeNghbs>
<UseMaxCodes>1</UseMaxCodes>
<SameCodeForCarriers>0</SameCodeForCarriers>
<NbClusterPerSite>3</NbClusterPerSite>
<ClustNghbs>0</ClustNghbs>
<Clust2ndNghbs>0</Clust2ndNghbs>
<NbCodesPerCluster>8</NbCodesPerCluster>
<UseDistance>1</UseDistance>
<UseExcepPairs>1</UseExcepPairs>
<Max1stNghbCost>100</Max1stNghbCost>
<Max2ndNghbCost>50</Max2ndNghbCost>
<Max3rdNghbCost>5</Max3rdNghbCost>
<CoplanCost>100</CoplanCost>
<MaxCoClusterCost>50</MaxCoClusterCost>
<MaxDistCost>100</MaxDistCost>
<ExcepPairCost>100</ExcepPairCost>
135
<UseCloseNghbs>1</UseCloseNghbs>
<CloseDistance>80000.</CloseDistance>
<CloseImportance>3000.</CloseImportance>
<MaxCloseCost>100</MaxCloseCost>
</SCP_options>
</Atoll>
11.1.9 AutomaticPNOffsetAllocationParameters
ThefollowingparametersaresavedforautomaticPNoffsetallocation(CDMA2000documents):
<MinEcI0>:MinimumEc/I0constraint
<TDrop>:ValuefortheTDrop
<reliability>:Celledgecoverageprobability
<DistanceMin>:Defaultreusedistance
<Strategy0>:PNOffsetperCellstrategyavailableornot
<Strategy1>:AdjacentPNClusterperSitestrategyavailableornot
<Strategy2>:DistributedPNClusterperSitestrategyavailableornot
<Strategy>:PNoffsetallocationstrategy
<FromScratch>:Resetallalreadyallocatedcodesornot
<UseCurrentNghbs>:Useexistingneighboursornot
<NghbOrder>:Theorderofneigbourstotakeintoaccount,i.e.,1st,2nd,or3rd
<ComputeNghbs>:CalculateneighboursusingtheadditionEc/I0conditionsornot
<UseShadowing>:Shadowingtakenintoaccountornot
<SameCodeForCarriers>:AllocatesamePNoffsettocellsofthesametransmitterornot
<PilotIncr>:ValueforthePILOT_INC
<PNClusterSize>:NumberofPNoffsetspercluster
<UseDistance>:Taketheminimumreusedistanceintoaccountornot
<UseExcepPairs>:Takeexceptionalpairsintoaccountornot
<UseMaxCodes>:Useamaximumofcodesornot
<minField>:Minimumpilotsignallevelconstraint
<usePmax>:Usethemaximumdownlinktransmissionpowerornot
<PerCentMaxPower>:Thepercentageofthemaximumdownlinkpoweris<usePmax>issetto0
<Max1stNghbCost>:Themaximumcostof1storderneighbours
<Max2ndNghbCost>:Themaximumcostof2ndorderneighbours
<Max3rdNghbCost>:Themaximumcostof3rdorderneighbours
<CoplanCost>:Thecostforintertechnologyneighbours
<MaxDistCost>:Themaximumcostforaminimumreusedistanceconstraintviolation
<ExcepPairCost>:Thecostforexceptionalpairconstraintviolation
Sample
<Atoll>
<PNO_options>
<DistanceMin>200000.</DistanceMin>
<Strategy>2</Strategy>
<FromScratch>1</FromScratch>
<UseCurrentNghbs>1</UseCurrentNghbs>
<NghbOrder>1</NghbOrder>
<ComputeNghbs>1</ComputeNghbs>
<SameCodeForCarriers>0</SameCodeForCarriers>
<PilotIncr>4</PilotIncr>
<PNClusterSize>3</PNClusterSize>
136
Forsk2014
AT321_AM_E1
<UseExcepPairs>1</UseExcepPairs>
<UseMaxCodes>1</UseMaxCodes>
<MinEcI0>-1600.</MinEcI0>
<TDrop>-1800.</TDrop>
<reliability>6000.</reliability>
<Max1stNghbCost>100</Max1stNghbCost>
<Max2ndNghbCost>50</Max2ndNghbCost>
<Max3rdNghbCost>5</Max3rdNghbCost>
<CoplanCost>100</CoplanCost>
<MaxDistCost>100</MaxDistCost>
<ExcepPairCost>100</ExcepPairCost>
</PNO_options>
</Atoll>
11.1.10 AutomaticOFDMResourceAllocationParameters
ThefollowingparametersaresavedforautomaticallocationofresourcesinOFDMnetworks:
<UseNeighbs>:Neighbourstakenintoaccountornot
<UseDistance>:Distancetakenintoaccountornot
<UseIM>:Interferencematricestakenintoaccountornot
<BasedOnFrqPlan>:Frequencyplantakenintoaccountornot
<SameSegPerTx>:Allocatethesamesegmenttocotransmittercellsornot
<MinDistance>:Minimumglobalreusedistance
<SiteStrategy>:PersiteorfreeallocationforSSSID(LTE)andcellpermbase(WiMAX)
<UniformIDDistribution>:UniformphysicalcellIDorpreambleindexdistributionactiveornot
<RangeType>:PhysicalcellID,preambleindex,orzonepermbaseallocationdomain(restricted=0,entire=1,custom
=2,orpercell=3)
<ExcludedPis>:ListofexcludedphysicalcellIDs,preambleindexes,orzonepermbasesforcustomallocationdomain
type
AutomaticallyallocatedresourcesinOFDMnetworksinclude:
LTE:FrequencyandphysicalcellIDallocationparameters
WiMAX:Frequency,preambleindex,andzonepermbaseallocationparameters
WiFi:Frequencyallocationparameters
Sample
<Atoll>
<OFDM_AFP_options>
<UseNeighbs>1</UseNeighbs>
<UseIM>1</UseIM>
<BasedOnFrqPlan>1</BasedOnFrqPlan>
<SameSegPerTx>0</SameSegPerTx>
<MinDistance>100.</MinDistance>
<SiteStrategy>1</SiteStrategy>
<UniformIDDistribution>1</UniformIDDistribution>
137
Forsk2014
<RangeType>2</RangeType>
<ExcludedPis></ExcludedPis>
</OFDM_AFP_options>
</Atoll>
11.1.11 MicrowaveRadioLinksParameters
Thefollowingparametersaresavedformicrowaveradiolinks:
<QualityModel>:Qualitymodelusedforcalculations
<QualityObjective0>,<QualityObjective1>,<QualityObjective2>,<QualityObjective3>:Qualityobjectives
<AvailabilityObjective0>, <AvailabilityObjective1>, <AvailabilityObjective2>, <AvailabilityObjective3>: Availability
objectives
<RainModel>:Rainmodelused
<RBER>:ResidualBER
<ALFA1>:Valueofalpha1
<ALFA2>:Valueofalpha2
<RefDelayM>:Referencedelayforminimumphase
<refDelayNM>:Referencedelayfornonminimumphase
<EquipPercent>:Availabilityobjectivesratioforequipment
<RainPercent>:Availabilityobjectivesratioforrain
<kMoy>:Averagevalueofk
<kMin>:Minimumvalueofk
<UseAtpc>:Useautomaticpowercontrolornot
<P0Method>:Multipathoccurencemethod
<IgnoreXPD>:Ignorecrosspolardiscrimination
<IgnorePR>:Ignorepassiverepeaters
<WhichBER>:BERtocalculate
<BER1>:ValueofBER1
<BER2>:ValueofBER2
<Rec838>:Rainmodelrecommendationsversion
<UseK1Global>:Usetheglobalvaluefork1
<UseK2Global>:Usetheglobalvaluefork2
<CALC_LINK_PORTS>:Calculateforgivenlinkports
<MultilineShared>:Sharedmultichannelfrequencydiversity
<NoAcm>:Signalenhancements
<InterferenceDistanceMax>:Maximumdistanceforinterferencefiltering
<InterferenceDropMin>:Localminthresholddegradation
<InterferenceDropMinGlobal>:Globalminthresholddegradation
<InterferenceCalcGo>:InterferencecalculationinthedirectionfromsiteAtositeB
<InterferenceCalcReturn>:InterferencecalculationinthedirectionfromsiteBtositeA
<InterferenceCalcUplink>:Interferencecalculationintheuplink
<InterferenceCalcDownlink>:Interferencecalculationinthedownlink
<InterferenceRainSurfCorrelation>:Interferencecorrelationsurfacearea
<InterferenceAutoWeight>:Automaticinterferenceweighting
<InterferenceUseAtpc>:Powercontrolforinterferencecalculation
<InterferenceWidth>:Interferedwantedbandwidth
<InterferenceOverShoot>:Interferenceovershootcalculation
<CochannelOnly>:Interferedbandwidthcochannelonly
<IgnoreIntraLinkInterference>:Ignoreinterferencebetweenchannelsofthesamelink
<Resolution>:Interferingprofilecalculationstep
<INTERF_DETAIL>:Calculationdetails(none,uplink,downlink,both)
<ClutterCategory0>through<ClutterCategory36>:Bitsetsforcluttercategoryproperties
<ClutterDryCategory0>through<ClutterDryCategory36>:Soiltype
Sample
<Atoll>
<Microwave>
<QualityModel>6</QualityModel>
<QualityObjective0>3</QualityObjective0>
138
AT321_AM_E1
<AvailabilityObjective0>3</AvailabilityObjective0>
<RainModel>5</RainModel>
<RBER>1.e-012</RBER>
<ALFA1>10</ALFA1>
<ALFA2>1</ALFA2>
<RefDelayM>6.30000019</RefDelayM>
<refDelayNM>6.30000019</refDelayNM>
<EquipPercent>33.</EquipPercent>
<RainPercent>33.</RainPercent>
<kMoy>1.33</kMoy>
<kMin>0.88</kMin>
<UseAtpc>0</UseAtpc>
<P0Method>1</P0Method>
<IgnoreXPD>1</IgnoreXPD>
<IgnorePR>0</IgnorePR>
<WhichBER>5</WhichBER>
<BER1>1.e-003</BER1>
<BER2>1.e-006</BER2>
<Rec838>1</Rec838>
<UseK1Global>1</UseK1Global>
<UseK2Global>1</UseK2Global>
<CALC_LINK_PORTS>selected</CALC_LINK_PORTS>
<MultilineShared>0</MultilineShared>
<NoAcm>1</NoAcm>
<InterferenceDistanceMax>50000.</InterferenceDistanceMax>
<InterferenceDropMin>1.</InterferenceDropMin>
<InterferenceDropMinGlobal>3.</InterferenceDropMinGlobal>
<InterferenceCalcGo>1</InterferenceCalcGo>
<InterferenceCalcReturn>1</InterferenceCalcReturn>
<InterferenceCalcUplink>0</InterferenceCalcUplink>
<InterferenceCalcDownlink>0</InterferenceCalcDownlink>
<InterferenceRainSurfCorrelation>100.</InterferenceRainSurfCorrelation>
<InterferenceAutoWeight>0</InterferenceAutoWeight>
<InterferenceUseAtpc>0</InterferenceUseAtpc>
<InterferenceWidth>250</InterferenceWidth>
<InterferenceOverShoot>0</InterferenceOverShoot>
<CochannelOnly>0</CochannelOnly>
<IgnoreIntraLinkInterference>1</IgnoreIntraLinkInterference>
<Resolution>50</Resolution>
<INTERF_DETAIL>both</INTERF_DETAIL>
<ClutterCategory0>0</ClutterCategory0>
<ClutterDryCategory0>B</ClutterDryCategory0>
139
<ClutterDryCategory15>E</ClutterDryCategory15>
<ClutterDryCategory26>A</ClutterDryCategory26>
140
Forsk2014
AT321_AM_E1
</Microwave>
</Atoll>
11.1.12 Macros
Thefollowingparametersaresavedformacros:
<Path>:Fullpathtothemacrofile
<Language>:Languageinwhichthemacroiswritten
<Timeout>:Thetargettimeallocatedtomacroexecution
Sample
<Atoll>
<Macros>
<File>
<Path>C:\TestsAddin\testEvents.vbs</Path>
<Language>VBScript</Language>
<Timeout>3600</Timeout>
</File>
</Macros>
</Atoll>
11.2 ContentsofAdditionalConfigurationFiles
Completedescriptionsofthedifferentadditionalconfigurationfilesareprovidedbelow.
11.2.1 PrintSetupConfiguration
Thefollowingparametersaresavedforprintsetup:
Pagetab<Page>:
141
Forsk2014
Papersizeandorientation<Papersize=""orientation=""/>,margins<Marginsright=""left=""bottom=""top="">,
scalingwiththefittopageoption<ScalefitToPage="">
Componentstab:
Rulersandareainsidefocuszoneonly<Map>:<MapinsideFZonly=""rulers=""/>
Legend<Legend>:Legendflag,outerandinnerposition,andinsidemapflag<LegendPosenable=""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/Footertab:
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=""/>,titletext<text>,andfontdetails<fontheight=""weight=""charset=""face=""
italic=""/>
Footerlogo<LogoBottom>:Logoflag,verticalandhorizontalposition,andtheinsidemapflag<PositionvPos=""
enable="" hPos="" insideMap=""/>, logo image <bitmap>, and logo width and height in pixels <Dimensions
width=""height=""/>
Footer text <Footer>: Footer flag, vertical and horizontal position, and the inside map flag <Position vPos=""
enable="" hPos="" insideMap=""/>, footer text <text>, and font details <font height="" weight="" charset=""
face=""italic=""/>
Sample
<PrintConfiguration version="1">
<Page>
<Paper size="" orientation="1"/>
<Margins right="2000" left="2000" bottom="2000" top="2000"/>
<Scale fitToPage="1">12 495</Scale>
</Page>
<Map insideFZonly="1" rulers="1"/>
<Legend>
<LegendPos enable="0" majorPos="3" minorPos="0" insideMap="0"/>
</Legend>
<Comments>
<Position vPos="1" enable="0" hPos="1" insideMap="0"/>
<text></text>
<font height="14" weight="400" charset="1" face="MS Shell Dlg" italic="0"/>
</Comments>
<Logo>
<bitmap></bitmap>
<Dimensions width="46" height="18"/>
</Logo>
<Title>
<text></text>
</Title>
<LogoBottom>
<bitmap></bitmap>
<Dimensions width="46" height="18"/>
</LogoBottom>
142
AT321_AM_E1
<Footer>
<text></text>
</Footer>
</PrintConfiguration>
11.2.2 TableImport/ExportConfiguration
Thefollowingparametersaresavedfortableimport/export:
Headerflag<TITRE>
Fieldseparator<FLD_SEPARATOR>
Decimalsymbol<DEC_SEPARATOR>
Fieldsavailableinthetable(fieldlegends)<FIELDS>
Fieldsselectedforimport/export(fieldlegends)<CHOOSEN_FIELDS>
Sample
<TITRE>1</TITRE>
<FLD_SEPARATOR><tab></FLD_SEPARATOR>
<DEC_SEPARATOR>.</DEC_SEPARATOR>
<FIELDS>
Site
Transmitter
...
</FIELDS>
<CHOOSEN_FIELDS>
Site
Transmitter
...
</CHOOSEN_FIELDS>
11.2.3 CoveragePredictionReportConfiguration
Thefollowingparametersaresavedforcoveragepredictionreports:
ColumnsselectedintheColumnstobedisplayeddialogue<SelectedFields>includingthefieldtitles<Field><Title>
Sample
<ReportConfiguration>
<SelectedFields>
<Field>
<Title>Surface (km)</Title>
</Field>
<Field>
<Title>% of Covered Area</Title>
</Field>
...
</SelectedFields>
</ReportConfiguration>
143
Forsk2014
11.2.4 CWMeasurementImportConfiguration
MorethanoneCWmeasurementimportconfigurationscanbesavedinasingleCWMeasurementsImport.inifile.
ThefollowingparametersaresavedintheCWMeasurementsImport.inifiles:
Configurationnameinsquarebrackets
Firstmeasurementrow(Header)
Separator(Separator)
Decimalsymbol(DecimalSeparator)
Typeoffilesforwhichtheconfigurationhasbeendefined(Pattern)
ColumncontainingtheXcoordinates(Xindex)
ColumncontainingtheYcoordinates(Yindex)
Columncontainingthemeasurementvalues(MeasIndex)
Unitofthemeasurementvalues(Unit)
Frequencyofthemeasurements(Frequency)
Heightofthereceiverusedformeasurements(Height)
Gainofthereceiverusedformeasurements(Gain)
Lossesofthereceiverusedformeasurements(Losses)
Totalnumberofcolumnsinmeasurementfiles(NbCol)
Columntypes(Col0toColNbCol)
Thecolumntypeindexesareasfollows:
Type
Index
Text
Integer
Real
Date
<Ignore>
Sample
[ConfigurationName]
Header=2
Separator=tab
DecimalSeparator=.
Pattern=*.txt
Xindex=1
Yindex=2
MeasIndex=4
Unit=0
Frequency=2110
Height=1.5
Gain=0
Losses=0
NbCol=23
Col0=1
Col3=4
Col5=0
...
11.2.5 DriveTestDataImportConfiguration
MorethanonedrivetestdataimportconfigurationscanbesavedinasingleDriveTestDataImport.inifile.
ThefollowingparametersaresavedintheDriveTestDataImport.inifiles:
144
Configurationnameinsquarebrackets
Firstmeasurementrow(Header)
AT321_AM_E1
Separator(Separator)
Decimalsymbol(DecimalSeparator)
Typeoffilesforwhichtheconfigurationhasbeendefined(Pattern)
ColumncontainingtheXcoordinates(Xindex)
ColumncontainingtheYcoordinates(Yindex)
Unitofthemeasurementvalues(Unit)
Heightofthereceiverusedformeasurements(Height)
Gainofthereceiverusedformeasurements(Gain)
Lossesofthereceiverusedformeasurements(Losses)
Firstidentifier(GenericNameIdOne)
Secondidentifier(GenericNameIdTwo)
Formatofthesecondidentifier(IdFormat)
Wirelesstechnology(Techno)
Totalnumberofcolumnsinmeasurementfiles(NbCol)
Columntypes(Col0toColNbCol)
Thecolumntypeindexesareasfollows:
Type
Index
Text
Integer
LongInteger
Single
Double
Date
<Ignore>
Sample
[ConfigurationName]
Header=2
Separator=tab
DecimalSeparator=.
Pattern=*.*
Xindex=1
Yindex=2
Unit=0
Height=1.5
Gain=0
Losses=0
GenericNameIdOne=
GenericNameIdTwo=BSID
IdFormat=Decimal
Techno=IEEE 802.16e
NbCol=21
Col0=1
Col3=1
Col4=4
...
11.3 ContentoftheCustomPredictionsFile
Thecontentofthecustompredictionsfile(bydefault,studies.XMLintheinstallationfolder)isidenticaltothecontentfound
betweenthe<Studies>and</Studies>tagsintheconfigurationfile.Formoreinformation,see"CoveragePredictions"on
page 129.
145
Forsk2014
11.4 Contentofthe"ValueIntervals"PredictionsFiles
ThecontentoftheXMLfilesforcoveragepredictionscalculatedbyvalueintervals(bydefault,prediction_name>.XMLinthe
C:\<path_to_doc>\<doc_name>.studies\{<Unique_ID>}folder)isidenticaltothecontentfoundbetweenthe<Studies>and</
Studies>tagsintheconfigurationfile.Formoreinformation,see"CoveragePredictions"onpage 129.
146
Chapter12:InitialisationFiles
AT321_AM_E1
12 InitialisationFiles
Initialisationfilescanbeusedtostoreoperationalandworkingenvironmentsettings.Thesefilesareoptional,notrequired
forworkingwithAtoll,butareusefulmeansforselectingrequiredcalculationmethodsandothersettings.
Thischapterdescribestheformatsofthesefilesindetail:
Atollinitialisationfile(Atoll.ini)
Thisfilecontainsconventions,calculationsettings,andotheroptionsforAtoll.Formoreinformationontheseoptions,
see"AtollInitialisationFile"onpage 147.
Atoll.inicanbeautomaticallyloadedwhenAtollisrunwhenitis:
a. IdentifiedinthecommandlineparameterIni"inifilename"(see"AtollCommandLineParameters"onpage 24for
moreinformation),or
b. Located in the Atoll installation folder. This file will be ignored if an initialisation file is loaded through the
commandlineparameter.
Youcan open the Atoll.ini file in the Atoll installation folderfor editingby pressing
CTRL+SHIFT+i.IfnoAtoll.inifileexists,ablankAtoll.inifileiscreated.
YoumustrestartAtollinordertotakeintoaccountmodificationsmadeinAtoll.ini.
AgivenAtoll.inisection,e.g.[GUIUserRights]or[LTE],mustoccuronlyonceinthefile,
withalloptionspertainingtothatsectionlistedunderit.Ifyouenterthesamesection
twice,onlythefirstoccurrenceofthesectionwillbereadandloadedbyAtoll.
ACPinitialisationfile(ACP.ini)
ThisfilecontainscalculationsettingsandotheroptionsfortheAtollACPmodule.Formoreinformationonthese
options,see"ACPInitialisationFile"onpage 194.
12.1 AtollInitialisationFile
Thefollowingmaingroupsofoptionsareavailable:
"GeneralOptions"onpage 147
"GUIOptions"onpage 159
"DistributedCalculationServerOptions"onpage 163
"LicenceManagementOptions"onpage 164
"DatabaseOptions"onpage 165
"CommonCalculationOptions"onpage 168
"GSMGPRSEDGEOptions"onpage 175
"UMTSHSPA,CDMA2000,andTDSCDMAOptions"onpage 180
"LTE,WiMAX,andWiFiOptions"onpage 185
"3GPPMultiRATOptions"onpage 190
"MicrowaveRadioLinksOptions"onpage 191
"MeasurementOptions"onpage 193
"ACPOptions"onpage 194
TheAtollinitialisationfileisapowerfultool.Youshouldnotmodifyanyoptionuntiland
unlessyouareabsolutelysureofwhatyouaredoing.
12.1.1 GeneralOptions
12.1.1.1 ModifyingtheDefaultFormatsofSiteandTransmitterNames
ThroughtheAtoll.inifile,itispossibletospecifyprefixestobeusedfornamingsitesandtransmitters.
Incaseofsites,youmustaddtheselines:
[Site]
Prefix = "newprefix"
EachnewsitewillthenbenamednewprefixNinsteadofSiteN,whereNisthesitenumberorindex.
147
Forsk2014
Fortransmitters,youcandefineaprefixbyaddingtheselines:
[Transmitter]
Prefix = "newprefix"
Each new transmitter will be named newprefixN instead of Sitename_X (Sitename is the name of the site where the
transmitterislocatedandXisthetransmittersectornumberonthissite).Notaddingtheabovelines,orsettingtheprefixto
<Auto>(Prefix="<AUTO>"),willinstructAtolltokeeptheconventionalnamingmethod,i.e.,eachtransmitterwillbenamed
Sitename_X.
Furthermore,itisalsopossibletoremovetheunderscorecharacter"_"fromthetransmittersname,i.e.,thetransmittercan
benamedSitenameXinsteadofSitename_X.Todothis,addthefollowinglineinthe[Transmitter]sectionoftheAtoll.inifile:
[Transmitter]
Underscore = 0 or 1
Settingthisvalueto0meanstheunderscorecharacterwillnotbeusedwhennamingtransmitters.Thedefaultvalueis1.You
canalsodefinewhetherthesuffixXinthetransmittersnameshouldbeanumberoraletter.Thefollowingtwolinesdefine
thisoptionintheAtoll.inifile:
[Transmitter]
SuffixIsNum = 0 or 1
FirstCharSuffix = "A"
WhenSuffixIsNum=1,thedefault,thesuffixXinthetransmitternameSitename_Xwillbeanumber.Whenitissetto0,this
suffixwillbealetter.ThestartingsuffixinthiscasewillbeAbydefaultbutcanbechangedtoanyothercharacterthrough
thesecondline.
Ifyouareusingnumbersuffixes,youcanalsoinitialisethenumbersuffixatanyothernumberthan1.Todothis,youcanadd
thefollowinglinesunderthe[Transmitter]sectionoftheAtoll.inifile:
[Transmitter]
First = X
Where,Xisanumber.
12.1.1.2 DisablingAutomaticRenamingofTransmittersandCells
Whenthenameofanysiteismodified,Atollautomaticallyrenamesthetransmittersandcellsrelatedtothesiteaccordingto
thenewsitename.Similarly,renamingatransmitterrenamesthecorrespondingcellsautomatically.Automaticrenaming
accordingtositenamesisenabledbydefault.However,itcanbedisabledbyaddingthefollowinglinesintheAtoll.inifile:
[AutoRename]
Transmitters = 0
3GCells = 0
"Transmitters"referstotransmitterrenamingwhenthesitenameischanged.
"3Gcells"referstocellrenamingwhenthetransmitternameischanged.
12.1.1.3 SettingtheTIFFColourConvention
Inthedefaultpalette,thefirstcolourindexesrepresenttheusefulinformationandtheremainingcolourindexesrepresent
thebackground.YoucanexportTIFFfileswithapalettecontainingthebackgroundcolouratindex0alongwithothercolour
indicesrepresentingtheforeground.ThiscanbehelpfulwhenworkingonTIFFfilesexportedbyAtollinothertools.Todoso,
theAtoll.inifilemustcontaintheselines:
[TiffExport]
PaletteConvention = Gis
12.1.1.4 CreatinganEventViewerLogFile
YoucandefinealogfilepathandfilenameinAtoll.iniinordertosaveallthewarning,error,andinformationmessages
displayedintheEventViewerwindowtoalogfile.Todothis,addthefollowinglinestoAtoll.ini:
148
AT321_AM_E1
[EventsObserver]
LogPath = FullPath\LogFile.log
Thepathshouldbethefullpathtothelogfile,whichcanbe,forexample,"\\Server\Drive\Root\Folder\Atoll\"or"C:\Program
Files\Forsk\Atoll\"(withoutquotationmarks)."LogFile.log"willbecreatedbyAtollasanASCIItextfile,andcanhaveanyfile
nameandextension.Atollwilloverwriteanyalreadyexistinglogfilewiththesamename.IfAtollisunabletooverwritethe
existinglogfile,itwillnotcreateanylog.
YoucanalsostartAtoll,specifyingalogfile,bystartingitwith"Atoll.exelogLogFile.log",eitherfromthecommandline,or
bymodifyingtheshortcutparameters.IfyouhavealogfiledefinedintheAtoll.inifile,andrunAtollwiththelogoptionin
thecommandline,thecommandlinelogfilewillhavepriorityovertheonementionedintheAtoll.inifile.
TheoptionavailableinAtoll.iniismoresuitableforrunningAtollusingmacros.Apartfromtheseoptions,youalsohavethe
possibilitytosavethemessagesintheEventViewertoalogfileduringanAtollsession(throughtheEventViewercontext
menu).
12.1.1.5 DisplayingInsufficientPermissionMessagesintheEventViewer
Ifauserattemptstoloadanaddinforwhichhedoesnothavethenecessarypermissions,bydefault,amessagewillbe
displayedintheEventViewer.BydefininganoptionintheAtoll.inifile,messagesregardinginsufficientpermissionwillnotbe
displayed.
[EventsObserver]
ShowAddinAccessDeniedMsg=0 # 1 by default; insufficient permission messages are shown
12.1.1.6 IncreasingtheMaximumPrintingResolution
Bydefault,Atolllimitstheprintingresolutionto150dpi(dotsperinch)toimproveperformanceandconsumelessmemory
whenprinting.IfyouwantAtolltoprintyourmapsinahigherresolutionthan150dpi,youcanaddthefollowinglinestothe
Atoll.inifile:
[Print]
MaxDPI = 300
300dpiisgivenasanexampleonly.
12.1.1.7 DuplicatingLinkedPathLossMatricesonSaveAs
WhenyousaveanAtolldocumentwithlinkedpathlossmatricesasanotherdocumentusingSaveAs,Atollcreatesthethe
linkedpathlossmatricesfoldercorrespondingtothecreatedfileandcopiestheexistinglinkedpathlossmatricesfromthe
pathlossmatricesfolderoftheoriginaldocument.TherecanbealargenumberofLOSfiles,andcopyingthesefilescantake
alongtimeandusealotofdiskspace.IfyouwantAtollnottomakecopiesofthelinkedpathlossmatrices,youcanaddthe
followinglinestotheAtoll.inifile:
[Perfos]
StoreExternPrivLosFilesOnCopy = 0
StoreExternPrivLosFilesOnCopyissetto1bydefault,whichmeansthatAtollmakescopiesofthelinkedpathlossmatriceson
Save As. If you set StoreExternPrivLosFilesOnCopy to 0, Atoll does not create the linked path loss matrices folder
correspondingtothecreatedfile,andthelinkedpathlossmatricesoftheoriginalAtolldocumentareusedforthenewAtoll
documentaswell.
AfileopeninAtollhasexclusiveaccessrightstoitsprivatepathlossmatrices.Iftwofilespointtothesamelinkedpathloss
matricesfolder,thefileopenfirstwillhaveaccesstothethepathlossmatrices.Youwillbeabletoopenthesecondfile,but
itwillnolongerpointtoanyprivatepathlossmatricesfolder.Therefore,ifyouhavemorethanonefilethatpointstothe
sameprivatepathlossmatricesfolder,youshouldnotopenthematthesametime.
WhenStoreExternPrivLosFilesOnCopyissetto1,youcanaddanotheroptionintheAtoll.inifiletomakeAtollaskthewhether
theuserwantsAtolltomakecopiesthelinkedpathlossmatricesornot.ToaddthisconfirmationsteponSaveAs,addthe
followinglinesintheAtoll.inifile:
[Perfos]
ConfirmStoreExternPrivLosFilesOnCopy = 1
ConfirmStoreExternPrivLosFilesOnCopyissetto0bydefault.ThisoptionisignoredwhenAtollisruninnoninteractivemode,
forexampleusingtheAPI.
149
Forsk2014
12.1.1.8 DisablingExternalStorageofNumericalResultsFilesforPredictions
Thenumericalresultsofcoveragepredictionscalculatedbyvalueintervalsarestoredexternallyfiles.Thisavoidsrecalculating
acoveragepredictionwhenthelegendismodifiedandprovidesanumericaldifferencefeaturebetweenbasicpredictions.
However,thestorageofnumericalresultsmayrequireadditionaldiskspacewhenyourdocumentcontainsseveralcoverage
predictionsandtransmitters,and/orhighresolutionsareused.ifyouhavelimiteddiskspace,youcandisablethisfeatureby
addingthefollowinglinesintheAtoll.inifile:
[Studies]
NumericalResults = 0
NumericalResultsissetto1bydefault,whichmeansthatAtollwillgenerateexternalresultsfilesandrequiremorediskspace.
MemoryspaceisnotimpactedwhenNumericalResultsissetto1.
12.1.1.9 RestrictingtheListofPredictionsforCreatingSectorTrafficMaps
Whenyoucreateasectortrafficmap,i.e.,trafficmapbasedoncellcoverageareas,Atollusesanexistingbestservercoverage
predictioninordertobeabletodistributethelivetrafficdatageographically.Atollletsyouselectthebestservercoverage
predictiononwhichthetrafficmapwillbebased.Inthelistofavailablebestservercoveragepredictions,Atolllistsallthebest
servercoveragepredictionavailableinthePredictionsfolder,whethertheywerecreatedusingamarginorwithout.
IfyouwantAtolltolistonlythebestservercoveragepredictionsthatwerecreatedwithoutamargin,i.e.,with0 dBmargin,
youcanaddthefollowinglinestotheAtoll.inifile:
[Studies]
SelectNullMarginOnly = 1
SelectNullMarginOnlyissetto0bydefault,whichmeansthatAtolllistsallthebestservercoveragepredictionsavailable.
12.1.1.10 DisplayingPathLossCalculationDetailsintheEventViewer
Duringpathlosscalculations,AtolldisplaysdetailsaboutthesecalculationsintheTaskstaboftheEventViewer.Thesedetails
cannotbecopiedorsaved.Ifyouwantaccesstothesedetails,ortoasummaryofthesedetails,oncethecalculationshave
finished,youcanaddthefollowinglinesintheAtoll.inifile:
[Pathlosses]
DisplayInvalidityCause = 1
DisplayIndividualSuccessOrFailure = 1
DisplayOverallSuccessOrFailure = 1
SettingtheDisplayInvalidityCauseoptionto1willdisplaythecauseforwhichpathlosseswerecalculatedforeachtransmitter,
setting DisplayIndividualSuccessOrFailure to 1 will display whether the path loss calculation succeeded or failed for each
transmitter,andsettingDisplayOverallSuccessOrFailureto1willdisplaythetotalnumberofpathlossmatricescalculated,the
numberofpathlossmatricescalculatedsuccessfully,andthenumberofcalculationsthatfailed.
ThesedetailsarelistedintheEventstaboftheEventViewer.
12.1.1.11 MappingAtollCoordinateSystemswithMapInfo/ESRIVectorFiles
ItisnowpossibletodefineamappingbetweenthecoordinatesystemsinAtollandthecoordinatesystemsdefinedinthe
headerfilesofMapInfo(MIF)andESRI(PRJ)vectorfilesthatyouwanttoimport.Youcandefineamappingbetweenthetwo
coordinatesystemsbyaddingthefollowinglinesintheAtoll.inifile:
[MITAB]
Coordinate system definition in the header file = Coordinate system code in Atoll
Inthisway,Atollisabletoexactlydetectthecoordinatesystemusedbythevectorfilebeingimported.InMIFfiles,the
CoordSys clause defines the coordinate systems, datum, unit, and other information. The coordinate system definition is
differentinthePRJfiles.ThesyntaxusedinAtoll.inifollowsthesyntaxoftheCoordSysclauseinMIFfiles.Usingthesame
syntaxforMIFandPRJfiles,AtollisabletoreadthedetectthecoordinatesystemsforbothMapInfoandESRIvectorfiles.
150
AT321_AM_E1
ThecoordinatesystemcodesinAtollarestoredintheCSfilesinthecoordsystemsfolder.Toaccessthecoordinatesystem
codesthroughAtoll:
1. SelectTools>Options.TheOptionsdialogueopens.
2. On the Coordinates tab, click the browse button (...) to the left of the Projection field. The Coordinate Systems
dialogueopens.
3. Selectacoordinatesysteminthepane.
4. ClickthePropertiesbutton.TheCoordinateSystempropertiesdialogueopens.
Thecoordinatesystemcodeisavailableinthepropertiesdialogue.
Afewexamplesofsuchmappingaregivenbelow.
[MITAB]
; NTF
Earth Projection 1, 107 = 4275
; Tokyo
Earth Projection 1, 97 = 4301
; WGS 84 / UTM zone 31N
Earth Projection 8, 104, "m", 3, 0, 1, 500000, 0 = 32631
Earth Projection 8, 104, "m", 135, 0, 0.9996, 500000, 0 = 32653
Earth Projection 8, 104, "m", 141, 0, 0.9996, 500000, 0 = 32654
; NTF (Paris) / France II tendue
Earth Projection 3, 1002, "m", 0, 46.8, 45.8989188889, 47.69601444, 600000, 2200000
= 27595
12.1.1.12 ExportingCoveragePredictionPolygonsinTextFormat
Youcanexportcoveragepredictionsintheformofpolygonstotextformatfiles.
Enablingthisoptioninfluencestheexportfeatureforallexportablevectorfomats(MIF,
TAB,AGD,SHP,TXT).Whenthisoptionisenabled,onlythelargestpolygonisexported
forcoveragelayershavingmorethanonepolygon.
YoucanenablethisfeaturebyaddingthefollowinglinesintheAtoll.inifile:
[Studies]
EnableLBS = 1
SettingEnableLBSto1addsanewcoveragepredictionexportformat"LBSPolygonFiles(*.txt)"toAtoll.Thepolygonsare
exportedinacommaseparatedvaluesformat.
12.1.1.13 DefiningWebMapServicesServers
WebMapServicesallowyoutodirectlyimportgeographicdatafromspecialisedserversintoAtoll.ThelistofWMSservers
canbedefinedintheAtoll.inifileasfollows:
[WMS]
S1 = Server1
S2 = Server2
...
SN = ServerN
YoucandefineanynumberofserversbyincrementingtheindexN.TheseserverswillbeavailableintheWMSdataimport
dialogueinAtoll.
151
Forsk2014
12.1.1.14 ImprovingPointAnalysisPerformance
Youcanimprovetheperformance,i.e.,calculationspeed,ofthePointAnalysistoolbyrestrictingthenumberoftransmitters
forwhichthereceivedsignallevelsarecalculated.TorestrictthenumberoftransmittersconsideredinthePointAnalysistool,
addthefollowinglinesintheAtoll.inifile:
[Perfos]
PtAnalysisNbServersMax = X
PtAnalysisMargin = Y
The option PtAnalysisNbServersMax lets to define the maximum number of transmitters (servers) to consider for the
calculationofthereceivedsignallevels.Xisthemaximumnumberoftransmitters.
TheoptionPtAnalysisMarginletsyoudefinethemarginwithrespecttothebestserversignallevel.Atollcalculatesthesignal
levelsfromallthetransmitterswithinY dBmarginfromthebestserversignallevel.ThedefaultvalueforPtAnalysisMarginis
30 dB.
Inadditiontotheabove,youcanalsosetthenumberoftransmittersforwhicharrowsaredisplayedfromthepointerlocation
inthemapwindow.Forsettingthisnumber,addthefollowinglinesintheAtoll.inifile:
[ReceptionTab]
NumberOfTransmitterDisplayed = Z
Zisthenumberoftransmittersforwhicharrowsgeneratedfromthepointerlocationwillbedisplayedinthemapwindow.
12.1.1.15 LoadingVectorFilesDynamically
VectorgeodatafromfilesimportedinanAtolldocumentareloadedinthememorywhenthedocumentisopen.Atollcan
dynamicallyloadthedatafromSHPandTABvectorfileswhenthefollowingoptionissetintheAtoll.inifile:
[Import]
LoadVectors = 1
LoadVectorsissetto0bydefault,whichmeansthatthedatafromimportedvectorfilesareloadedinmemory.Whenyouset
LoadVectorsto1,Atollreadsthedatafromthevectorfilesdirectly.
Fromthepointofviewofperformance,thisoptionisonlyadvisablewhenworkingwithlargevectordatafiles.
12.1.1.16 ExcludingVectorsfromImportedKML/KMZFiles
Bydefault,whenaKMLorKMZfileisimportedinanAtolldocument,theplacemarksandvectorsarebothimported.By
definingthefollowingoptionintheAtoll.inifile,youcanimportKMLandKMZfileswithoutvectors:
[Import]
LoadKMLVectors = 0
LoadKMLVectorsissetto1bydefault,whichmeansthatvectorsareimportedalongwithplacemarks.
12.1.1.17 SettingthePrecisionfortheAntennaPatternVerificationatImport
Atollcheckswhethertheverticalandhorizontalpatternsarecorrectlyalignedattheextremities.Theantennapatternsare
correctlyalignedwhen:
thehorizontalpatternattenuationat0isthesameastheverticalpatternattenuationatthepatternelectricaltilt
angle,and
thehorizontalpatternattenuationat180isthesameastheverticalpatternattenuationatthe180lessthepattern
electricaltiltangle.
Bydefault,theoptionisinactive,i.e.,thepatternattenuationsareconsideredthesameiftheydifferlessthan100 dB.Ifyou
wanttochangethisdefaultprecision,addthefollowinglinesintheAtoll.inifile:
[Antenna]
PrecisionTimes10 = X
WhereXistherequiredprecisionindBmultipliedby10.Forexample,ifyouwanttosettheprecisionto0.5 dB,Xwillbe
0.5 10 = 5 .
152
AT321_AM_E1
12.1.1.18 OpeningExportedXLSFilesAutomaticallyinMSExcel
Whenyouexportanentiredatatable,orselectedcolumns,toanMSExcelfile,AtollcanautomaticallyrunMSExceloncethe
exportiscompleteandopentheXLSfilecreatedbytheexportinMSExcel.Toenablethisfeature,addthefollowingoption
intheAtoll.inifile:
[Export]
AutoOpenWithExcel = 1
AutoOpenWithExcelissetto0bydefault.
12.1.1.19 DisablingCreationofNewDocumentsfromTemplates
YoucandisablethecreationofnewAtolldocumentsfromtemplatesbyaddingthefollowinglinesintheAtoll.inifile:
[GUIUserRights]
EnableNewDocFromTemplate = 0
EnableNewDocFromTemplateissetto1bydefault.
12.1.1.20 BlockingAccesstoMacrosandAddins
YoucanblockaccesstotheAddinsandMacrosdialoguebyaddingthefollowinglinesintheAtoll.inifile:
[GUIUserRights]
EnableMacrosAddins = 0
EnableMacrosAddinsissetto1bydefault.
12.1.1.21 DisablingSavingandOpeningZIPFiles
YoucanblockaccesstotheFile>SavetoZipandFile>OpenFromZipmenusbyaddingthefollowinglinesintheAtoll.inifile:
[GUIUserRights]
EnableZip = 0
EnableZipissetto1bydefault.
12.1.1.22 EnablingNotificationforDonorTransmitterParameterModifications
Atollcannotifyyouwheneveradonortransmitterparameter,whichhasanimpactonarepeater,ismodified.Toactivatethe
notification,addthefollowinglinesintheAtoll.inifile:
[Transmitter]
CheckImpactOnRepeaters = 1
CheckImpactOnRepeatersissetto0bydefault,whichmeansthatnonotificationsaredisplayed.
12.1.1.23 SettingtheDisplayPrecisionofFloatingPointValues
MostfloatingpointvaluesinAtollareformattedfordisplayingtwodigitsafterthedecimalpoint.Suchformattedfloating
pointvaluesincludethresholdsandpowervaluesindBm.However,incaseofdocumentsconnectedtodatabases(otherthan
MSAccess),somenonformattedfloatingpointvaluescanbedisplayedwithtoomanydigitsafterthedecimalpoint.
YoucansetthedisplayprecisionfornonformattedfloatingpointvaluesinAtolldialoguesandtables.Forexample,inorder
todisplaytwodigitsafterthedecimalpoint,youcanaddthefollowinglinesintheAtoll.inifile:
[Grids]
NbDecimals = 2
This option applies to all nonformatted floating point parameters in Atoll, i.e., excluding geographic coordinates and
formattedfloatingpointvalues.
NbDecimalsissetto1bydefault.Thiscorrespondstomaximumprecision,i.e.,allthedigitsafterthedecimalpointavailable
inthedatabasearedisplayed.
153
Forsk2014
12.1.1.24 ChangingthePathtoLinkedGeoDataFiles
YoucanchangethepathtoalinkedgeographicdatafilebyclickingtheFindbuttoninthePropertiesdialogueofthefile.By
default,theFindbuttoninthePropertiesdialogueisavailableonlyformissinggeographicdatafiles,i.e.,thelinkedfilesthat
Atollisunabletolocateandload.However,youcanenabletheFindbuttonevenforavailablegeographicdatafilesbyadding
thefollowinglinesintheAtoll.inifile:
[Geo]
FindGeoButtonAlwaysActive = 1
FindGeoButtonAlwaysActive is set to 0 by default. This option can be useful when you have changed the location of a
geographicdatafile,andyouwishtochangethepathtothenewlocation.
Whenchangingthepathtoalinkedgeographicdatafile,youmustprovidethenewpath
tothesamefile.Thisoptiondoesnotallowlinkingtoanotherfileinstead.Inordertolink
toanotherfile,youmustfollowthenormalfileimportprocedure.
12.1.1.25 Exporting/ImportingVectorDatawithaDisplayConfigurationFile
WhenyouexportvectordatafromanAtolldocument,youcansimultaneouslyexportthecorrespondingdisplayconfiguration
file(CFG)oftheeditedvectorlayerbyaddingthefollowinglinesintheAtoll.inifile.Theexporteddisplayconfigurationfilewill
havethesamefilenameandwillbesavedinthesamedirectoryastheexportedvectorformatfile.
[Geo]
VectorDisplayConfigurationCompanionFile = 1
VectorDisplayConfigurationCompanionFileissetto1bydefault.WhenyouimportvectordatainanAtolldocument,thesame
optionenablesyoutosimultaneouslyimportthecorrespondingdisplayconfigurationfile(CFG).Thedisplayconfigurationfile
willonlybeimportedifithasthesamefilenameandifitislocatedinthesamedirectoryastheimportedvectorformatfile.
12.1.1.26 UsingOnlyVisibleGeoDatainPredictionReports
Bydefault,Atolltakesintoaccountallthegeographicdatawhengeneratingpredictionreports,whetherthegeographicdata
isvisibleonthemapornot.Youcanchangethedefaultbehaviourforpopulation,traffic,andgenericgeographicdataby
[Geo]
ReportObeysVisibility = 1
ReportObeysVisibilityissetto0bydefault.
12.1.1.27 ExportingBMP,TIF,andPNGFileswithaTABReferenceFile
WhenexportingBMP,TIF,andPNGfiles,AtollcanexportthegeoreferenceinformationinaTABfileinsteadofthedefault
respectiveWorldfiles(BPWorBMWforBMP,TFWforTIF,andPGWforPNG).IfyouwantAtolltoexportthegeoreference
informationinaTABfilewhenyouexportinBMP,TIF,andPNGformats,addthefollowinglinesintheAtoll.inifile:
[RasterExport]
GeorefWithTAB = 1
GeorefWithTABissetto0bydefault.
12.1.1.28 CoPlanning:LinkingtheSitesFolder
You can link the Sites folder, in addition to the Transmitters and Predictions folders, of a document to another (main)
documentusingtheFile >LinkWithcommandbyaddingthefollowinglinesintheAtoll.inifile:
[CoPlanning]
LinkSites = 1
LinkSitesissetto0bydefault.
154
AT321_AM_E1
12.1.1.29 DisablingNormalisationofMIF/TABVectorFiles
Whenimportingvectorfiles,Atollnormalisesallthevectorsinthefilesbasedontheconventionthatavectorwhosevertices
coordinates are defined clockwise creates a filled polygon,and avector whose vertices coordinates aredefinedcounter
clockwisecreatesahole.MapInfovectorsdonotfollowthesameconvention,andhencetheirnormalisationatthetimeof
import can take a long time. If you want to disablethis normalisation when importing MIF and TAB vector files, add the
[MITAB]
DisableNormalization = 1
DisableNormalizationissetto0bydefault.
12.1.1.30 AddingtheDuplicateSitetotheOriginalSitesSiteList
Whenyouduplicateasite,youcanchoosetoaddtheduplicatesitetothesitelist(ifany)oftheoriginalsitebyaddingthe
[Site]
AddToSiteListOnDuplicate = 1
AddToSiteListOnDuplicateissetto0bydefault.
12.1.1.31 UsingOnlyVisibleClutterClassesinInterferencePredictionReports
By default, Atoll takes into account all the clutter classes when generating reports on interferencebased coverage
predictions,whethertheclutterclassesarevisibleonthemapornot.Youcanchangethedefaultbehaviourbyaddingthe
[Clutter]
OnlyVisibleClassesInInterferenceReport = 1
OnlyVisibleClassesInInterferenceReportissetto0bydefault.The visibilityofclutterclassesonthemapcanbemanaged
throughtheDisplaytabofthePropertiesdialogueoftheClutterClassesfolder.Usingthisoption,youcanexcludeclutter
classeswhicharenotrelevantininterferencepredictionreports,forexample,water.
12.1.1.32 Displaying%ofCoveredClutterClassesw.r.t.theFocusZoneinReports
Incoveragepredictionreports,Atolldisplaysthepercentagesofcoveredclutterclasseswithrespecttothetotalsurfacearea
ofalltheclutterclassescoveredbytheprediction.IfyouwantAtolltodisplaythepercentagesofcoveredclutterclasseswith
respecttothetotalsurfaceareaofalltheclutterclasseswithintheFocusZone,addthefollowinglinesintheAtoll.inifile:
[Clutter]
PerClassPercentagesRelativeToCoverageInReport = 0
PerClassPercentagesRelativeToCoverageInReportissetto1bydefault.
12.1.1.33 Displaying%ofCoveredTrafficClassesw.r.t.theFocusZoneinReports
Incoveragepredictionreports,Atolldisplaysthepercentagesofcoveredenvironmenttrafficclasseswithrespecttothetotal
surfaceareaofalltheenvironmenttrafficclassescoveredbytheprediction.IfyouwantAtolltodisplaythepercentagesof
coveredenvironmenttrafficclasseswithrespecttothetotalsurfaceareaofalltheenvironmenttrafficclasseswithinthe
FocusZone,addthefollowinglinesintheAtoll.inifile:
[Traffic]
PerClassPercentagesRelativeToCoverageInReport = 0
PerClassPercentagesRelativeToCoverageInReportissetto1bydefault.
12.1.1.34 SynchronisingPrivateandSharedPathLossMatrices
Whencalculationsarerun,Atollverifieswhetherthesharedandprivatepathlossmatricesarevalid.Ifthesharedpathloss
matricesarevalid,
Atolldeletesanycorrespondinginvalidprivatepathlossmatricesandusesthevalidsharedonesforcalculationsif
Atoll.inicontainsthefollowinglines:
155
Forsk2014
[Pathlosses]
FullResyncPrivShared = 0
Atoll deletes any corresponding valid and invalid private path loss matrices and uses the valid shared ones for
calculationsifAtoll.inicontainsthefollowinglines:
[Pathlosses]
FullResyncPrivShared = 1
Ifyouhaveprivatepathlossmatricestunedusingmeasurementdata,settingFullResyncPrivSharedto1willmake
Atollautomaticallydeletethemwhencalculationsarerun.YoushouldsetFullResyncPrivSharedto0whenworking
withtunedprivatepathlossmatrices.
FullResyncPrivSharedissetto1bydefault.
12.1.1.35 SelectingtheLogo2CheckBoxbyDefaultinPrintSetup
PrintsetupparametersarestoredintheAtolldocuments,andyoucansavetheprintsetupparametersinCFGfiles(see"Print
SetupConfiguration"onpage 141).IfyouwishtohavetheLogo2checkboxselectedbydefaultforanynewAtolldocument,
addthefollowinglinestotheAtoll.inifile:
[Print]
LogoFooterChecked = 1
LogoFooterCheckedissetto0bydefault.
12.1.1.36 FilteringPredictionsbyTechnologyWhenReadingtheXMLStudiesFile
IntheXMLstudiesfile,somecommonCDMAcoveragepredictionscanbeavailableforbothCDMA2000andUMTS,orsome
common OFDMA coverage predictions can be available for both WiMAX and LTE. If you wish to filter the customised
predictionsstoredintheXMLstudiesfilebytheirtechnology,e.g.,separatetheWiMAXandLTEcoveragepredictions,and
onlyloadthepredictionsspecifictothetechnologyofthecurrentactiveAtolldocument,addthefollowinglinesintheAtoll.ini
file:
[Studies]
CustomStudiesFilteredByTechno = 1
CustomStudiesFilteredByTechnoissetto0bydefault.ThisoptionisonlyrelevantforreadingtheXMLstudiesfile.Atollalways
writesthetechnologytypeintheXMLstudiesfilewhencustomisedcoveragepredictionsaresavedinit.
12.1.1.37 EnablingEventViewerMessagesforMapInfoFileImport/Export
YoucanenablethedisplayofEventViewerinformation,warning,orerrormessagesrelatedtoMapInfofilesbyaddingthe
[MITAB]
EnableMessages = 1
EnableMessagesissetto0bydefault,andAtolldoesnotdisplayanymessagesrelatedtoMapInfofileimportandexport.
12.1.1.38 SettingtheResolutionofPopulationMapsinCoveragePredictionReports
Atollusesthedefaultresolution,definedinthePredictionsfoldersPropertiesdialogue,forrasterisationofthepopulation
maps.Inordertouseadifferentresolutionforhigherorlowerprecision,youcanaddthefollowinglinesintheAtoll.inifile:
[Population]
ReportResolution = X
WhereXistheresolutionfortheconversionofpopulationmapvectorsintoraster.
IfyousetReportResolutiontoaveryprecise(low)value,theperformance(calculation
speed)canbeconsiderablydecreaseddependingonthesizeofthepopulationmapsin
thedocument.Itisrecommendedtosetthisparametertoanoptimumvalue,i.e.,just
preciseenoughtogettherequiredaccuracy.
156
AT321_AM_E1
12.1.1.39 SettingthePrecisioninCoveragePredictionReports
Youcansettheprecisionofthefloatingpointvaluesdisplayedintheabsolutevaluecolumnsofcoveragepredictionreports
byaddingthefollowinglinesintheAtoll.inifile:
[Studies]
ReportDecimalPlacesAbsolute = X
WhereXisthenumberofdigitsfollowingthedecimal.
Youcansettheprecisionofthefloatingpointvaluesdisplayedinthepercentagevaluecolumnsofcoveragepredictionreports
byaddingthethefollowinglinesintheAtoll.inifile:
[Studies]
ReportDecimalPlacesPercent = X
WhereXisthenumberofdigitsfollowingthedecimal.
12.1.1.40 IncludingPixelfreeRangesinCoveragePredictionReports
Bydefault,therangeswhichdonotcontainanypixelsdonotappearinthecoveragepredictionreports.Youcanincludethese
rangesincoveragepredictionreportsbyaddingthefollowinglinesintheAtoll.inifile.
[Studies]
ShowIntervalsWithNoCoverageInReport = 1 # (Default=0)
12.1.1.41 ChangingHotSpotReferenceSurfaceinPredictionReports
Inacoveragepredictionreport,Atolldisplaysthepercentageofhotspotscoveredbyeachcoveragelayer(displaythresholds)
withasreferencethehotspotsurfaceareacoveredbythewholeprediction.IfyouwantAtolltodisplaythepercentageof
hotspotscoveredbyeachcoveragelayer(displaythresholds)withasreferencethehotspotsurfacearea,addthefollowing
linesintheAtoll.inifile:
[Studies]
UseFullHotSpotSurfaceOnReport = 1 # "1" = activated (Default)
12.1.1.42 ExportingOnlyVisibleValueIntervalLayersofCoveragePredictions
By default, Atoll exports all the layers (levels) of a coverage prediction being exported. For some coverage predictions
(coveragepredictionsdisplayedbyvalueintervalsandnotbydiscretevalues,excludingGSMcoveragepredictionsbycoding
schemes,throughput,andCQI),youcanexportonlythevisiblelevelsbyaddingthefollowinglinesintheAtoll.inifile:
[Studies]
ExportOnlyVisibleLevels = 1
ExportOnlyVisibleLevelsissetto0bydefault,whichmeansthatwhenanycoveragepredictionisexported,Atollexportsall
itslevels,visibleornot.
Atollexportsonlyvisiblecoveragepredictions.Ifacoveragepredictionconsistsofonly
onelevel,thevisibilitycheckboxofthatlevelalsocontrolsthevisibilitycheckboxofthe
prediction itself. This means that if the visibility check box of the only level of such a
predictioniscleared,thepredictionwillitselfbehiddenandwillnotbeexported.
12.1.1.43 AvoidingOverlappingPixelsinBestServerCoveragePrediction
Inbestservercoveragepredictions,i.e.,CoveragebyTransmitterwithoption"Bestserver"andamarginof0 dB,somepixels
canbecoveredbymorethanonetransmitterifthereceivedsignallevelfromtwoormoretransmittersisexactlythesame.
Toavoidthis,addthefollowinglinesintheAtoll.inifile:
[Studies]
NoOverlapOnBestServer = 1
Bydefault,NoOverlapOnBestServerissetto0.WhenNoOverlapOnBestServerissetto1,Atollarbitrarilyselectsoneofthe
bestserversonsuchpixels.Thisoptioncanbeuseful,forexample,whencalculatingpopulationstatisticsbasedonabest
157
Forsk2014
servercoverageprediction.Whenapixeliscoveredbymorethanonebestserver,thepopulationbelongingtothatpixelis
countedasmanytimesasthenumberofbestservers,whichcangiveerroneouspercentagesofcoveredpopulation.
12.1.1.44 SettingtheMinimumATLFileSizeRequiringCompression
YoucansetthefilesizeabovewhichAtollshouldcompressdatainATLfilesbyaddingthefollowinglinesintheAtoll.inifile:
[Compression]
StartSizeInMB = X
WhereXisthefilesizeinMB.AtollwillcompresstheATLfileifitislargerthanX.Bydefault,StartSizeInMBissetto800.
12.1.1.45 Loading,Activating,andSettingAddinsasVisible
Installed addins are automatically loaded by Atoll and appear in the Addins and Macros dialogue. You can change this
defaultbehaviourforeachindividualaddinasfollows:
Ifyouwantanaddinneithertobeloaded(i.e.,deactivated)norbeavailableintheAddinsandMacrosdialogue,add
[Add-ins]
Add-in Name = 0
If you want an addin to be loaded, activated, and accessible in the Addins and Macros dialogue for activation/
deactivation,addthefollowinglinesintheAtoll.inifile:
[Add-ins]
Add-in Name = 1
Ifyouwantanaddintobeloadedandactivated,butonlyshownintheAddinsandMacrosdialogueforinformation
(impossibletodeactivate),addthefollowinglinesintheAtoll.inifile:
[Add-ins]
Add-in Name = 2
IfyouwanttosetanaddintobemandatoryforAtoll,addthefollowinglinesintheAtoll.inifile:
[Add-ins]
Add-in Name = 3
Any addin set to option 3 will be loaded and activated, but only shown in the Addins and Macros dialogue for
information(impossibletodeactivate).Atollwillnotrunifitisunabletoloadthisaddin.
AddinNameisthenameoftheaddinasitappearsintheAddinsandMacrosdialogueinAtoll.Atollfailstostartifforsome
reasonitisunabletoloadanaddinwhosestatusissetto3.Thedefaultstatusforaddinsis1.
12.1.1.46 DefiningOnlineMapURLs
OnlinemapsallowyoutodisplaymapdatafromtheInternetinAtoll.YoucandefinealistofonlinemapURLsintheAtoll.ini
fileasfollows:
[OnlineMaps]
Name1 = City1
URL1 = http://...
Name2 = City2
URL2 = http://...
...
NameN = CityN
URLN = http://...
YoucandefineanynumberofonlinemapURLsbyincrementingtheindexN.TheseURLswillbeavailableintheonlinemap
importdialogueinAtoll.
158
AT321_AM_E1
12.1.1.47 ChangingtheDefaultCacheLocationfortheLoadedMapTiles
ThemaptilesthatyouloadintoAtollarestoredinaspecificcachedirectorynamedafterthecorrespondingtileserver.By
default,thelocationofthiscacheis"%TEMP%\OnlineMaps".Youcanchangethislocationbyaddingthefollowinglinesinthe
Atoll.inifile:
[OnlineMaps]
TilesCachePath = <new path>
12.1.1.48 ManagingCarriageReturnsinImportedTXT/CSVFiles
BydefaultwhenyouexportthecontentofatabletoaTXT/CSVformat,thecarriagereturnsarereplacedbyspacesinthetext
fields.YoucanavoidthisbyaddingthefollowinglinesintheAtoll.inifile:
[Export]
NewLineEscapeSequence = "\n"
WhenNewLineEscapeSequenceissetto"\n",thecarriagereturnsarereplacedby"\n"intheexportedfilesandeach"\n"is
replacedbyacarriagereturnwhenthefilesareimported.
Ifyouwanttogobacktothepreviousbehaviour,setNewLineEscapeSequenceto""(space).Inthiscase,thecarriagereturns
arenotreplacedbyaspacewhenafileisimported.
12.1.1.49 DeletingtheFilteringZoneonRemovingFiltersFromTables
Bydefault,whenyouremovefiltersappliedtotables,Atollkeepsthefiltersappliedonthroughthemapusingthefiltering
zone.Ifyouwishtoremovethefilteringzoneaswellwhenremovingfiltersfromtables,addthefollowinglinesintheAtoll.ini
file:
[Settings]
KeepFilterZoneOnRemoveFilter = 0
KeepFilterZoneOnRemoveFilterissetto1bydefault.
12.1.2 GUIOptions
12.1.2.1 DefiningtheParametersfortheDefaultSitesSymbol
YoucandefinetheparametersofthedefaultsymbolusedfordisplayingsitesonthemapthroughtheAtoll.inifile.Youcan
definetheparametersasfollows:
[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
ThedefaultsitessymbolisusedwhenanewdocumentiscreatedinAtoll.Toknowthenameofthefonttouse,andtosetthe
symbol,youcanusetheWindowsCharacterMaptool.Youcanusethecopy/pastefeaturestosetthesymbolintheAtoll.ini
file.
Example:
[SitesSymbol]
FontName = Wingdings
Symbol =
Size = 12
Color = 0
12.1.2.2 UsingaUniqueSymbolforRemoteAntennas
Bydefault,remoteantennasaredisplayedusingthesamesymbolonthemapastransmitters.Youcanuseaunique,non
modifiablesymbolforremoteantennasonthemapbyaddingthefollowinglinesintheAtoll.inifile:
159
Forsk2014
[RemoteAntennas]
FrozenSymbol = 1
FrozenSymbolissetto0bydefault.WhenyousetFrozenSymbolto1,theremoteantennasymbolwillbefixedandnolonger
linkedwiththetransmittersymbol.
12.1.2.3 KeepingTransmitterSymbolsFromChangingonSearch
WhenusingtheSearchTool,allthetransmittersthatdonotfulfilthesearchcriteriaaredisplayedasgreylinesonthemap.If
youwantthesetransmitterstokeeptheiroriginalsymbols,addthefollowinglinesintheAtoll.inifile:
[Transmitter]
ChangeSymbolOnSearch = 0
ChangeSymbolOnSearchissetto1bydefault.
12.1.2.4 DisplayingFilledSymbolsforInactiveTransmittersontheMap
Bydefault,Atollemptiesthesymbolsofinactivetrasnmitters,repeaters,andremoteantennasonthemap.Ifyouwishto
displayfilledsymbolsforinactivetransmitters,repeaters,andremoteantennasonthemap,addthefollowinglinesinthe
Atoll.inifile:
[Transmitter]
EmptySymbolWhenInactive = 0
EmptySymbolWhenInactiveissetto1bydefault.
12.1.2.5 RefreshingtheDisplayAutomaticallyWhenaNewStationisDropped
YoucanhaveAtollrefreshthedisplayautomaticallyeachtimeanewstationoragroupofstationsisdroppedonthemapby
[Transmitter]
AutoSynchronizeDisplay = 1
AutoSynchronizeDisplayissetto0bydefault.
12.1.2.6 HidingInformationDisplayedintheStatusBar
Usingcompressedgeodataformats(TIFF,ErdasImagine,ECW)cancauseperformancelossduetorealtimedecompression.
PerformancecanbeimprovedbyeitherhidingtheStatusBarorbyhidingsomeoftheinformationdisplayedintheStatusBar
(altitude,clutterclass,orclutterheight).TohideinformationintheStatusBar,addthefollowinglinestotheAtoll.ini:
[StatusBar]
DisplayZ = 0
DisplayClutterClass = 0
DisplayClutterHeight = 0
DisplayZ,DisplayClutterClassandDisplayClutterHeightrespectivelyrefertothedisplayofaltitude,clutterclass,andclutter
height.
12.1.2.7 DisplayingDateandTimeintheEventViewer
YoucaninstructAtolltodisplaythedate,andtimewithmillisecondsintheEventviewer.Todisplaythisinformation,addthe
followinglinestotheAtoll.inifile:
[EventsObserver]
milliseconds = 1
date = 1
160
AT321_AM_E1
12.1.2.8 SettingtheMaximumNumberofLinesinCoveragePredictionToolTips
Ifyouhavemorethanonecoveragepredictiondisplayedonthemap,thetooltipsdisplaythetiptextforallthecoverage
predictionsavailableatapixelupto30linesbydefault.Youcanchangethisdefaultnumberoftooltiptextlinesthroughthe
followingoptionintheAtoll.inifile:
[Studies]
MultiplePlotsTipTextLines = X
Xisthenumberoflinestodisplayinthetooltips.Bydefault,MultiplePlotsTipTextLinesissetto30.Ifyousetittoaverylarge
value,however,thetooltipmightnotdisplaycorrectly.
12.1.2.9 ChangingtheDisplayforDownlinkSmartAntennaResults
The downlink smart antenna simulation results, i.e, the angular distributions of downlink transmitted power density,
calculatedduringMonteCarlosimulationsusingtheOptimumBeamformerandConventionalBeamformercanbedisplayed
intwodifferentways.Bydefault,thesediagramsrepresenttheaveragearraycorrelationmatricesandaresymmetricabout
thexaxis(sameonthefrontandback).Ifyouwanttodisplaythesediagramstakingintoaccounttheantennapatternofthe
singleantennaelement,addthefollowingoptionintheAtoll.inifile:
[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
DrawSingleElementPatternto1,thediagramdisplayedwillrepresent g n S R Avg S .
12.1.2.10 AddingExposureAnalysistotheListofMultiRATCoveragePredictions
(Hiddenen3.2.0.02,cesinfossontdansTN013)
Themaximumpermissibleexposure(MPE)toelectromagneticfields(EMF)canbeanalysedinsingleRATandmultiRATdocu
ments.AmultiRATexposureanalysisisacombinationofthecorrespondingsingleRATexposureanalyses.
Youcaninclude"ExposureAnalysis"inthelistofcoveragepredictionsavailableinsingleRATandmultiRATdocumentsby
[Studies]
ExposureStudy = 1
WhenExposureAnalysispredictionsareenabled,"ExposureAnalysis"appearsinthelistofpredictionsinalltypesofsingle
RAT(exceptTDSCDMAandWiFi)andmultiRAT(including3GPP2)documents.
12.1.2.11 DisplayingCoveragePredictionCommentsintheLegendWindow
YoucandisplaythecontentsoftheCommentsboxofcoveragepredictionpropertiesintheLegendwindowbyaddingthe
[Studies]
CommentsInLegend = 1
Thecommentsaredisplayedbetweenthenameofthecoveragepredictionandthethresholds.CommentsInLegendissetto
0bydefault.
12.1.2.12 DisplayingLeadingZerosintheCELL_IDENTITYField
Bydefault,AtolldoesnotdisplayleadingzerosintheCELL_IDENTITYfieldoftheTransmitterstableinGSMandtheCellstables
inUMTS,CDMA2000,andTDSCDMA.Forexample,cellidentity"00678"isdisplayedas"678".IfyouwantAtolltodisplay
leadingzeros,youmustsettheminimunnumberofdigitstheCELL_IDENTITYfieldshouldcontainbyaddingthefollowinglines
intheAtoll.inifile:
[Display]
CellIDNbDigits = X
WhereXisthenumberofdigitsthattheCELL_IDENTITYfieldshouldcontain.Forexample,CellIDNbDigits=5meansthatAtoll
willdisplayatleastfivedigitsintheCELL_IDENTITYfieldbyaddingleadingzeroswhererequired.ThismeansthatAtollwill
display"00678"intheaboveexample.However,iftheCELL_IDENTITYfieldcontainsanumberthathasmorethanXdigits,all
161
Forsk2014
thedigitswillstillbedisplayed.Forexample,allsevendigitsin"9376562"willstillbedisplayedevenifCellIDNbDigitsissetto
5.
12.1.2.13 MakingtheAntennaAdditionalElectricalDowntiltAccessible
By default, Atoll does not allow modification of the Additional Electrical Downtilt for transmitters, station templates,
repeaters,andremoteantennas.TomakethisparameteraccessibleintheGUI,addthefollowinglinesintheAtoll.inifile:
[Antenna]
REDTDisplay = 1
REDTDisplayissetto0bydefault.
12.1.2.14 IncreasingtheWidthoftheClutterDescriptionPaneintheStatusBar
YoucanincreasethewidthoftheclutterdescriptionpaneintheStatusbar(bottomright),todisplaythedescriptionsof
clutterclasseswithlongnames,byaddingthefollowinglinesintheAtoll.inifile:
[StatusBar]
ClutterPaneWidth = X
ClutterPaneWidthissetto100bydefault,whichmeans100%ofitsdefaultwidth.Toincreasethewidthto,forexample,twice
theoriginalwidth,setClutterPaneWidthto200.
12.1.2.15 HidingtheTechnologyNameintheTitleBar
Thenamesofthetechnologiescorrespondingtothecurrentactivedocumentaredisplayedinthetitlebar.Youcanhidethe
technologynamesbyaddingthefollowinglinesintheAtoll.inifile:
[DocTitle]
UseTechnoName = 0
UseTechnoNameissetto1bydefault.
12.1.2.16 DisplayingObjectsDiscreteValueswithUserdefinedColours
Whenobjectsaredisplayedbydiscretevalues,Atollappliescoloursautomaticallyon36colourcycles.Asopposedtoshading,
thisisparticularlyusefultodistinguishneighbouringzoneswhichhaveveryclosecolourvalues.Bysettingsomeoptionsinthe
Atoll.inifile,youcanconfigureAtolltolooponasmanyuserdefinedcoloursasyouwant.
ForinstanceifyouinsertthefollowinglinesintheAtoll.inifile,Atollwillloopon12colourvalues(PaletteColor0through
PaletteColor11)thenexttimeyoudisplayobjectsbydiscretevalues.
[Display]
PaletteColor0=141 211 199
Youcanalsooverrideuserdefinedcolours,ifany,andforceshading(fromredtoblue)bysettingthefollowingoptioninthe
Atoll.inifile.
[Display]
DiscreteValueColoring=Shading
162
AT321_AM_E1
12.1.2.17 DisplayingVerticalBeamwidthinProfileAnalysis
YoucanconfigureAtolltodisplaytheverticalbeamwidth(3 dBupperandlowerlimitsintheverticalplane)aswellasthe
actual tilt in the geographic profile view of the Profile Analysis tool. You can configure this display mode by adding the
[GeoProfileDisplay]
Beamwidth=1
The geographic profile displays clutter classes and the Fresnel ellipsoid by default. When this option is enabled, three
additionallinesareaddedtothediagram:
Thickyellowandgreenlines:Theselinesindicatetheupperandlower3 dBbeamwidthlimitintheverticalplane.
Thickblueline:Thislineindicatestheaxisofminimalloss,whichcoincideswiththeactualtiltaxisoftheantenna
(combiningthephysicalandelectricaltilt).
Theverticalbeamwidthiswidestintheazimutaxisoftheantenna.IfyoumovethepositionofthePointAnalysistooloffof
theantennaazimutaxis,theverticalbeamwidthdiminishesanddisappearswhentheverticalbeamwidthlossexceeds3 dB.
12.1.3 DistributedCalculationServerOptions
12.1.3.1 DetectingandListingDistributedCalculationServers
YoucanuseAtolltodetectdistributedcalculationserversandlistthemintheAtoll.inifile.Acomputer,servingasadistributed
calculationserver,canrunupto10instancesofAtollsvr,thedistributedcalculationapplication.Thedistributedcalculation
servernamescanbelistedintheAtoll.inifileinthefollowingformat:
[RemoteCalculation]
NumberedServers = Server1NameN; Server2NameN; ...
HereServer1NameandServer2Namerefertothenamesofthecomputersbeingusedascalculationservers,andNisanumber
from0to9.Thismeans,forexample,thatServer1canrunupto10instancesofthedistributedcalculationapplication,and
alltheseinstancescanbelistedintheNumberedServersoption(Server1Name0;Server1Name1;Server1Name2;...).Using
thisoption,youcanassigndistributedcalculationserverstodifferentgroupsofusersworkingwithtwodifferentAtoll.inifiles.
Forexample,usergroup1canuseServer1Name0toServer1Name4,andgroup2canuseServer1Name5toServer1Name9.
Ifanerroroccursonanyofthedistributedcalculationservers,Atolltransfersthecalculationsbacktothelocalcomputer.
However,toavoidmemorysaturation,Atollusesonethreadonthelocalcomputerandcalculatesthepathlossmatricesone
byone.Itdoesnotattemptcreatingmorethanonethread.
12.1.3.2 SettingtheDistributedCalculationServerPriority
Bydefault,theAtolldistributedcalculationserver(AtollSvr.exe)runswithanormalprocesspriority.However,itispossible
tomodifyitspriority,inbothserviceandapplicationmodes,andsetithigherorlower.Youcandothisbyaddingthefollowing
[RemoteCalculation]
AtollSvrPriority = -1, 0, 1 or 2
Youcanchoosebetween4possibleprioritylevels:
1:BelowNormalpriority
0:Normalpriority
1:AboveNormalpriority
2:Highpriority
Thisoptionworksforboth,applicationandservice,modesofthedistributedcalculationserver.
The distributed calculation server (AtollSvr.exe) must be restarted in order to take

intoaccountthenewvaluefortheAtollSvrPriorityoption.
TheRealtimeprioritymodehasnotbeenimplementedforreasonsofstability.
12.1.3.3 ModifyingtheDefaultDetectionTimeout
Thedefaulttimeout(2seconds)forlocatingcalculationserverswithinthenetworkmightbetooshortincertaincases.You
canincreasethistimeoutbyaddingthefollowinglinestotheAtoll.inifile:
163
Forsk2014
[RemoteCalculation]
DetectTimeOut = 5000
Inthisexample,thedetectiontimeoutissetto5000ms.
12.1.4 LicenceManagementOptions
12.1.4.1 SettinganAlarmfortheLicenceEndDate
Youcansetawarningmessageaboutthelicenceenddatetoappearacertainnumberofdaysbeforethisdate.TheAtoll.ini
fileshouldcontainthefollowinglines:
[License]
TimeBombNotice = X
XisthenumberofdayspriortothetemporarylicenceenddateyouwantAtolltowarnyou.Whennoinformationisgivenin
theAtoll.inifile,Atollwarnstheuser30daysbeforethelicenceend.
12.1.4.2 BlockingAccesstoTechnologyModules
Thisoptionisusefulwhenworkingwithafloatinglicencemanagementsystemwhereafloatinglicenceservermanagesand
distributestokensbetweenseveralAtollusers.Thisoptioncanalsobeusefulinsettingdifferentlicencerightstousers.
Toblockaccesstothedifferenttechnologymodules,addthecorrespondinglinesinthe[License]sectionoftheAtoll.inifile:
Toblockaccessto
Add
GSMGPRSEDGE
GSM=0
UMTSHSPA
UMTS=0
CDMA2000
CDMA=0
TDSCDMA
TDSCDMA=0
WiMAXandWiFi
WiMAX=0
LTE
LTE=0
MicrowaveRadioLinks
MW=0
Backhaul
BH=0
Measurements
Measures=0
YoucanalsoblockaccesstoGSM,UMTS,orLTEradioaccesstechnologiesin3GPPMultiRATdocumentsusingtheseoptions.
12.1.4.3 BlockingAccesstoACPandAFPModules
YoucanblockaccesstotheACPandAFPlicencesforusersorusergroups.ToblockaccesstoACPorAFPmodules,addthe
correspondinglinesinthe[License]sectionoftheAtoll.inifile:
[License]
ACP_GSM = 0
ACP_UMTS = 0
ACP_LTE = 0
ACP_WiMAX = 0
GSM_AFP = 0
LTE_AFP = 0
WiMAX_AFP = 0
InordertocarryoutacombinedGSMandUMTSoptimisationusingtheACPmodule,youmusthaveaccesstobothACP
modulelicences,i.e.,ACP_GSMandACP_UMTSmustbothnotbesetto0.
InordertocarryoutaWiFioptimisationusingtheACPmodule,youmusthaveaccesstotheWiMAXACPmodulelicence,i.e.,
ACP_WiMAXmustnotbesetto0.
InordertocarryoutaWiFifrequencyplanningusingtheAFPmodule,youmusthaveaccesstotheWiMAXAFPmodule
licence,i.e.,WiMAX_AFPmustnotbesetto0.
164
AT321_AM_E1
12.1.4.4 ChangingtheNetHASPLicenceManagerIdleTimeSetting
Thefloatinglicencemanagerhasanidletimeparameterwith10minutesasdefaultvalue.Atollsessionsconsumingfloating
licencesfromalicencemanagerserverresetthisidletimeparametertoitsinitialvalueeveryminute.Ifyouareperforming
timeconsumingcalculationsonAtollconnectedtoafloatinglicenceserver,andconsumingalicence,itmightoccurthatAtoll
doesnotgetthechancetoresettheidletimevaluetoitsinitialvalue.Inthiscase,anewAtollsessioncanstealthelicence
actuallyallocatedtoanalreadyrunningsession.Thismightcauseproblemsinthecasewhereallthelicencesareused,the
Atollsessionperformingheavycalculationsdoesnotgetthechancetoinitialisetheidletimeparameterforitslicence,anda
new Atoll session is launched on another computer. In such a situation, the floating licence manager considers that the
alreadyrunningsessionhasbeeninactiveorclosed,andthelicenceallocatedtothealreadyrunningAtollsessionisallocated
tothenewsession.
Youcanmodifythedefaultidletimeparametervaluetoahighervaluetoavoidthiseffect.Tosetadifferentdefaultvaluefor
theidletimeparameter,addthefollowinglinestotheAtoll.inifile:
[License]
IdleTime = X
WhereXisthetimeinminutes.TheidletimecanbesettoinfinitybydefiningIdleTime=0.
12.1.5 DatabaseOptions
12.1.5.1 CheckingDataIntegrityAfterDatabaseUpgradeandDataRefresh
AtollasksyoutoperformadatabaseintegritycheckwhenyouopenanAtolldocumentconnectedtoadatabasethatwas
recentlyupgradedtoanewversion,orwhenyourefreshdatainanAtolldocumentfromthedatabase.Itisrecommededto
performtheproposeddataintegritycheck.
However,ifyoudonotwishtocheckthedataintegrity,addthefollowinglinesintheAtoll.inifile:
[Refresh]
ControlIntegrity = 0
ControlIntegrityissetto1bydefault.
12.1.5.2 AutomaticallyRunningaDatabaseIntegrityCheckatOpenorRefresh
Thisoptionautomaticallyperformsadataintegritycheckwhenopeningadocumentfromadatabaseorrefreshingdatafrom
adatabase.Toturnthisfeatureon,youhavetoaddthefollowinglinesintheAtoll.inifile:
[Database]
IntegrityChecker = 1
Ifthisoptionissetto1,AtollperformsSELECTfiltersinthedatabasetoguaranteedataintegrity.Thisfeatureenablesselection
directlyinthedatabaseinordertoavoidintegrityproblemsinthefuture.
12.1.5.3 AllowingNullEntriesinNonnullableCustomFields
Bydefault,topreventfromarchivalissuesandcrashes,Atolldoesnotsupportnullentriesinnonnullablecustomfieldsof
connecteddocuments.Failingtofillanonnullablecustomfieldwhenyouaddanewrecordviaarecordtemplate,afile
import,ortableedition,willreturnamessageintheform"NameOfFieldcolumncannotbenull".Toavoidthis,youcandefine
thecustomfieldasnullableinthedatabase,useadefaultvalueinthefielddefinition,orcreatethefieldandfillitinthe
relevanttemplate.
Asalastresort,youcanforcethepreviousbehaviourofAtollbyaddingthefollowinglinesintheAtoll.inifile:
[Database]
AllowNullRecordsForNonNullableCustomFields = 1 #default=0
12.1.5.4 AutomaticallyRunningGSMSubcellAuditatOpenorRefresh
ThefollowingoptionsautomaticallyperformsubcellauditwhenopeningaGSMdocumentfromadatabaseorrefreshingdata
fromadatabase.
Toautomaticallyaudittheconsistencyofredundantvaluesinthetransmitters,subcells,andTRXstableswithoutfixingany
problemsfound,addthefollowinglinesintheAtoll.inifile:
165
Forsk2014
[Database]
SubCellAuditConsistency = 1
Toautomaticallyaudittheconsistencyofredundantvaluesinthetransmitters,subcells,andTRXstablesandfixanyproblems
found,addthefollowinglinesintheAtoll.inifile:
[Database]
SubCellAuditConsistency = 2
Toautomaticallyauditthecompatibilityofthemainsubcellvalueswithoutfixinganyproblemsfound,addthefollowinglines
intheAtoll.inifile:
[Database]
SubCellAuditMainValues = 1
Toautomaticallyauditthecompatibilityofthemainsubcellvaluesandfixianyproblemsfound,addthefollowinglinesinthe
Atoll.inifile:
[Database]
SubCellAuditMainValues = 2
SubCellAuditConsistencyandSubCellAuditMainValuesaresetto0bydefault.
12.1.5.5 ModifyingtheDefaultDatabaseConnectionTimeout
TheODBCdriverhasadefaultcommandtimeoutvaluewhichcouldbetooshortinsomecases,suchasslownetworks.You
canchangethisdefaulttimeoutvalueandsetahighervalueifyouencounterproblems,duringexecutionofcommandson
thedatabase,whichmightberelatedtotimeout.TochangethevalueofthecommandtimeoutparameteroftheODBCdriver,
[Database]
CommandTimeout = X
Where X is the timeout value in an integer number of seconds. After X seconds, the command isconsidered too long to
execute.IfyousetCommandTimeout=0,therewillbenotimelimitfortheexecutionofthecommand.
12.1.5.6 MakingAtollCaseSensitiveforDatabaseImportFromPlanet
ThenetworkdataimportfromaPlanetdatabaseintoAtollisnotcasesensitivebydefault.Youcansetthisimporttocase
sensitivebyaddingthefollowinglinesintheAtoll.inifile:
[PlanetImport]
SensitiveCase = 1
Casesensitivemeansthat"Site0"willbeconsidereddifferentfrom"site0"duringimport.
12.1.5.7 SettingtheSignforKClutterWhenImportingDataFromPlanetEV
PlanetEVusestheoppositesignfortheKclutterparameterwithrespecttoPlanetDMS.IfyouareimportingdatafromPlanet
EV,youmighthavetochangethesignofthisparameter.YoucaninstructAtolltochangethesignforKclutterwhenimporting
datafromPlanetEVbyaddingthefollowinglinestotheAtoll.inifile:
[PlanetImport]
ChangeKclutterSign = 1
ChangeKclutterSignissetto0bydefault.
12.1.5.8 Enabling/DisablingPasswordPromptatArchive
YoucaninstructAtolltoprompttheuserforpasswordbeforearchivingdatainadatabase.IfyouwantAtolltoasktheuser
toentertheusernameandpasswordonceperAtollsession,addthefollowinglinesintheAtoll.inifile:
[Database]
PromptOnArchive = 1
166
AT321_AM_E1
PromptOnArchive=1isthedefaultsettingusedifthisoptionisnotprovidedintheAtoll.inifile.Theuserwillbepromptedfor
passwordwhenhetriestoarchivedatainthedatabaseforthefirsttimeduringanAtollsession.
IfyouwantAtolltoasktheusertoentertheusernameandpasswordforeveryrefreshandarchive,set:
PromptOnArchive = 2
Ifyouwanttodisablethepromptforpassword,set:
PromptOnArchive = 0
UsernameandpasswordarestoredintheATLfileinanencryptedform.
Thisoptionisonlyappropriateifthedatabaseconnectionstringcontainsapassword.
12.1.5.9 ArchivingDatatoDatabasesUsingTransactions
Atollsupportstransactionsforarchivingdatatodatabases.Thisapproachensuresthatusersalwaysgetconsistentdatawhen
refreshingtheirdocumentswithdatafromthedatabase,evenwhenanotheruserisarchivinghismodificationsatthesame
time.Bydefault,Atollusestransactionsforarchivingdata,howeveryoucandisablethetransactionmodeforAtollbyadding
thefollowinglinestotheAtoll.inifile:
[Database]
UseTransaction = 0
UseTransactionissetto1bydefault.
Beforemodifyingthisoption,makesurethatthedatabaseserveriscorrectlyconfigured
fortransactions.
12.1.5.10 KeepingSeparateWorkandMasterPathLossDirectories
Whensynchronisingamasterprojectwithaworkproject,thesharedpathlossdirectoryisalsoupdated.Thiscancausethe
workandmasterprojectstooverwriteeachotherssharedfolder.Fromanoperationalstandpoint,itisoftenpreferableto
keeptwodifferentpathlossdirectories:oneforthemasterprojectandasecondfortheworkproject.
Whenthe[OverwriteSharedFolderPath]optionissetto"0",Atolldoesnotoverwritethesharedpathlossdirectory.
[Database]
OverwriteSharedFolderPath = 0 # "1" is default: path loss directory is overwritten
12.1.5.11 EnablingPartialRefreshfromRecentlyUpgradedDatabases
WhenyouopenanAtoll2.8.xdocumentconnectedtoadatabasethathasbeenupgradedtoAtoll3.1.0,Atollautomatically
performsafullrefresh,i.e.,loadsallthedatafromthedatabase,whenupgradingthedocumenttothenewversion.Ifyou
wishtoenablepartialrefreshofdatafromtheupgradeddatabase(notrecommendedasitcancausedataintegrityproblems),
[MajorVersionChange]
EnablePartialRefreshInMigration = 1
EnablePartialRefreshInMigrationissetto0bydefault.
12.1.5.12 SettingtheTypeofDatabaseBeingUsed
YoucansetthetypeofdatabasebeingusedbyaddingthefollowinglinesintheAtoll.inifile:
[Database]
ExclusiveProvider = providername
Whereprovidernamecanbe"Access","SQLServer",or"Oracle".Whenthisoptionisset,Atollusesthedefineddatabasetype
anddoesnotdisplaythedatabaseselectiondialoguethatappearswhencreatinganewdocumentfromanexistingdatabase
orwhenexportingadocumenttocreateanewdatabase.
167
Forsk2014
12.1.6 CommonCalculationOptions
12.1.6.1 SettingtheAntennaPatternsModellingMethod
Inordertosetthemodellingmethodforantennapatterns,theAtoll.inifilecancontainthefollowinginformation:
[Antenna]
AngleCalculation = 2000 or 3000
Catalog Vertical Diagram Orientation = 90 or angle value
InterpolatePatternEvenIfOnlyOneDiagram = 0 or 1
InterpolatePatternIndB = 0 or 1
AngleCalculationvaluesof2000and3000areonlyvalidfortheForskspropagationmodellibrary,i.e.,thepropagationmodels
availablewithAtollbydefault.SettingAngleCalculation=2000makesthepropagationmodelscalculate"unmasked"path
losses, i.e., path losses without considering the transmitter antenna patterns. Setting AngleCalculation = 3000 makes the
propagationmodelscalculatetheanglesofincidencetoeachpixelinsteadofpathloss.
CatalogVerticalDiagramOrientationisadisplayoption.Itenablesrotatingtheantennasverticaldiagramtoauserdefined
angle.Bydefault,CatalogVerticalDiagramOrientationissetto90meaningthattheverticaldiagramisdisplayedpointingto
theright.Settingitto0,forexample,willshowtheverticaldiagrampointingtothetop.
InterpolatePatternEvenIfOnlyOneDiagram can be used to change the way Atoll interpolates antenna pattern attenuation
diagrammes for antennas with only one diagramme available, vertical or horizontal. With
InterpolatePatternEvenIfOnlyOneDiagram = 0 (default, new method), Atoll uses the only diagramme available for both
vertical and horizontal planes. With InterpolatePatternEvenIfOnlyOneDiagram = 1 (previous method), Atoll uses the
diagrammeavailablefortheplanetowhichitcorresponds,verticalorhorizontal,andanisotropicdiagramme(a0 dBcircular
attenuationpattern)fortheplaneforwhichnodiagrammeisavailable.
InterpolatePatternIndBsetstheunitusedbyAtollwhenitperformslinearinterpolationsonantennapatternattenuation.
WhenInterpolatePatternIndB=0(default),interpolationsarecalculatedinWatts.WhenInterpolatePatternIndB=1(orany
valueotherthan0),interpolationsarecalculatedindBleadingtostrongerantennapatternattenuation.
12.1.6.2 DisablingAutomaticLockingofCoveragePredictions
Bydefault,Atollautomaticallylocksacoveragepredictionstudyonceitiscalculated.ToinstructAtollnottolockprediction
studiesautomatically,theselineshavetobeincludedintheAtoll.inifile:
[Studies]
AutoLock = 0
AutoLockisto1bydefault.
12.1.6.3 EnablingShadowingMargininCalculations
AnaveragevalueofshadowingmarginiscalculatedbyAtollandappliedtothesignallevelandinterferencelevelsduring
coverage predictions and othercalculations such aspoint analysis, automatic neighbour allocation, automatic scrambling
codeandPNoffsetallocation,andinterferencematricescalculation.Thisaveragevaluedependsonthecelledgecoverage
probabilitythatyoudefineforthecalculationandthestandarddeviationsdefinedperclutterclass.
In the dialoguesof all the abovementioned calculations, the Shadowing takeninto account checkbox is not selected by
default.Notselectingthischeckboximpliesthattheshadowingmarginisneithercalculatednorusedinthecalculations.
IfyouwanttoselecttheShadowingtakenintoaccountcheckboxbydefaultinalltheabovementioneddialogues,youhave
toenterthefollowinglinesintheAtoll.inifile:
[Shadowing]
UseShadowing = 1
UseShadowingissetto0bydefault.
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
margindependingonthecelledgecoverageprobability.DuringMonteCarlosimulations,
randomshadowingmarginvaluesarecalculatedbasedonlyonthestandarddeviations
definedperclutterclass.
168
AT321_AM_E1
InUMTSHSPAandCDMA2000documents,youcanalsodeactivatethecalculationanduseofmacrodiversitygains.Formore
information,see"DisablingMacrodiversity(SHO)GainsinCalculations"onpage 180.
12.1.6.4 SettingaDefaultValuefortheCellEdgeCoverageProbability
ThedefaultvalueofthecelledgecoverageprobabilitycanbeconfiguredintheAtoll.inifile.Ifyouenterthefollowinglinesin
theAtoll.inifile,AtollwillconsiderthevalueofthecelledgecoverageprobabilitydefinedintheAtoll.inifileasthedefault
value,andwilltakeitintoaccountwhenperformingpointanalysis,intheshadowingmarginscalculator,andwillproposeit
asthedefaultvalueforcoveragepredictionstudies.
[Shadowing]
Reliability = 60
Reliability=60means60 %celledgecoverageprobability.
Thevalueofcelledgecoverageprobabilityusedforautomaticneighbourallocationand
interferencematricescalculationisstoredinuserconfigurationfiles(CFG).
12.1.6.5 EnablingIndoorCoverageinCalculations
IndoorlossesaretakenintoaccountincalculationswhentheIndoorCoveragecheckboxisselected.Thischeckboxisnot
selectedbydefault.Ifyouwanttoselectthecheckboxbydefaultinthepropertiesdialoguesofallthecalculations,youhave
toenterthefollowinglinesintheAtoll.inifile:
[ClutterParams]
IndoorActivity = 1
IndoorActivityissetto0bydefault.
12.1.6.6 ModifyingtheResolutionfortheLOSAreaCalculationAroundaSite
Thecalculationoflineofsightareaaroundagivensiteusestheresolutionofthegeographicdataasthedefaultcalculation
resolution.Thesecalculationscanbetimeconsumingifthegeographicdataisavailablewithaveryhighresolution.Youcan
setthecalculationresolutiontoamultipleoftheresolutionofthegeographicdatabyaddingthefollowinglinesintheAtoll.ini
file:
[LOSArea]
ResolutionMultFactor = X
WhereXisaninteger.Therefore,settingResolutionMultFactorto2willdoublethecalculationresolutionanddecreasethe
timerequiredforthecalculationbyhalf.
12.1.6.7 EmbeddingPathLossesinNewDocuments
Ifyoucalculatepathlossmatricesforanewdocumentthathasnotbeensavedyet,Atollasksifyouwouldliketosavethe
document and externalise the path loss matrices or if you would like to keep the path loss matrices embedded in the
documentandsaveitlater.YoucansuppressthismessagebyaddingthefollowinglinesintheAtoll.inifile:
[Pathlosses]
EmbeddedByDefault = 1
EmbeddedByDefaultissetto0bydefault.
12.1.6.8 StoppingCalculationsonError
Ifaproblemoccursincalculatingoneormorepathlossmatriceswhilecalculatingacoverageprediction,Atollcontinues
performing the remaining calculations, and provides results even if they are not complete. If you want Atoll to stop the
calculationsifthereisanerror,youcanaddthefollowinglinesintheAtoll.inifile:
[Studies]
ContinueOnError = 0
ContinueOnError=1bydefault.ThismeansthatbydefaultAtolldoesnotstopthecalculationsonerror.
169
Forsk2014
12.1.6.9 WarningAboutPredictionValidityWhenDisplayOptionsareModified
Coveragepredictionshavetoberecalculatedifyoumodifytheirdisplayoptions.Atolldisplaysawarningmessagewhenyou
modifythedisplayoptionsforcoveragepredictions.Todeactivatethiswarningmessage,addthefollowinglinesintheAtoll.ini
file:
[Studies]
RecomputationWarning = 0
RecomputationWarningissetto1bydefault.
12.1.6.10 ReadingExactAltitudesFromtheDTM
AtolluseseithertheuserdefinedsitealtitudesfromtheSitestableor,iftheyarenotdefined,thesitealtitudesreadfromthe
DTMforthesitecoordinatesdefinedintheSitestable.However,transmitterscanbelocatedatcertaindistancesfromthe
sitecoordinates.YoucansetthesedistancesoftransmittersfromtheirsitesintheTransmitterstableunderDXandDY.
IfyouwantAtolltoconsidertheexacttransmittercoordinates,i.e.,includingDXandDY,duringcalculationsfordetermining
thetransmitterheight,whichwillbereadfromtheDTMattheexacttransmittercoordinates,youmustaddthefollowinglines
intheAtoll.inifile:
[Calculations]
UseSiteAltitude = 0
UseSiteAltitudeissetto1bydefault,whichmeansthatthealtitudeusedincalculationswillbetheonewhichiseitherread
fromtheSitestableorfromtheDTMatthesitescoordinates,iftheuserdefinedaltitudeisnotavailableintheSitestable.
Setting UseSiteAltitude to 0 means that, during calculations, Atoll will read the altitudes from the DTM at the exact
coordinatesofeachtransmitterconsideringthevaluesenteredfortheDXandDYparameters.
Theaboveoptionisalsovalidformicrowavelinks.Inthiscase,settingUseSiteAltitudeto0meansthat,duringcalculations,
AtollwillreadthealtitudesfromtheDTMattheexactcoordinatesofeachmicrowavelinkconsideringthevaluesenteredfor
theDX_A,DY_A,DX_B,andDY_Bparameters.
WithUseSiteAltitude=0,ifDXandDYare0,i.e.,fortransmittersandmicrowavelinks
locatedatthesitecoordinates,Atollwillstillusethealtitudesdefinedpersite,ifany,or
thealtitudesfromtheDTMotherwise
12.1.6.11 SettingaCommonDisplayResolutionForAllCoveragePredictions
Youcansetadisplayresolutionforeachcoveragepredictionindividuallyaswellasadefaultdisplayresolutionforallcoverage
predictionsthatyoucreate,inthePredictionstabofthePredictionsfoldersPropertiesdialogue.Ifyoucreateanewcoverage
prediction,AtollreadsthedefaultresolutionfromthePredictionsfoldersPropertiesdialogueandsetsthatasthedisplay
resolutionforthenewcoverageprediction.Then,ifyoudeletethisresolutionfromthecoveragepredictionproperties,and
donotenteranyresolution,Atollresetstheresolutiontothedefaultvalue.Inthisway,eachcoveragepredictionhasadisplay
resolution defined. However, it is possible to manage a common display resolution for all coverage predictions, new or
existing,thatdonothavearesolutiondefinedforthem.Youcanswitchtothisoptionbyaddingthefollowinglinesinthe
Atoll.inifile:
[Studies]
SpecifyResolutionAfterComputation = 0
OnceSpecifyResolutionAfterComputationissetto0,Atollnolongerresetstheresolutiontothedefaultvalueforcoverage
predictions that do not have a resolution defined. Atoll allows you to leave the field empty in the coverage prediction
properties,anddirectlyreadsthedefaultresolutiondefinedinthePredictionsfoldersPropertiesdialogue.Inthisway,when
you create coverage predictions without defining resolutions for them, you can modify the default resolution of the
PredictionsfoldersPropertiesdialogueand,therefore,changethedisplayresolutionforallthecoveragepredictions,newor
existing.
To return to the normal working, you can either remove the lines from the Atoll.ini file, or set
SpecifyResolutionAfterComputationto1.
12.1.6.12 SettingthePrioritiesforGUIandCalculations
YoucansettheprioritiesforuserinterfaceandcalculationsthroughthefollowingoptionintheAtoll.inifile:
[RemoteCalculation]
170
AT321_AM_E1
Priority = 0, 1, or 2
Priorityenablesyoutosettheprioritybetweencalculationsanduserinterface.
0:Userinterfacehasthehighestpriority.
1(default):Userinterfacehasahigherprioritythancalculations.
2:Userinterfaceandcalculationshavethesamepriority.
12.1.6.13 SettingtheNumberofParallelProcessorsandThreads
YoucanmanagethenumberofprocessorsandthreadsthroughtheAtoll.inifile.Thefileshouldcontainthefollowingoptions:
[RemoteCalculation]
NumberOfProcessors = X
NumberOfThreadsPathloss = 1, 2, ..., or 8
NumberOfThreadsSimulation = 1, 2, ..., or 8
NumberOfThreadsStudy = 1, 2, ..., or 8
NumberOfThreadsStudyTile = 0, 1, 2, ..., or 8
NumberOfThreadsNeighbour = 1, 2, ..., or 8
NumberOfThreadsMicrowave = 1, 2, ..., or 8
Maximumnumberofprocessors:
NumberOfProcessorsisthemaximumnumberofprocessorsthatcanbeusedforcalculations.Ifyousetthisoptionto
0,Atollwilluseactualnumberofavailableprocessors.
Maximumnumberofcalculationthreads:
NumberOfThreadsPathloss is the maximum number of threads that can be used for path loss calculations (4 by
default,8maximum)
NumberOfThreadsSimulation is the maximum number of threads that can be used for Monte Carlo simulation
calculations(4bydefault,8maximum)
NumberOfThreadsStudy is the maximum number of threads that can be used for the calculation of coverage
predictions(4bydefault,8maximum)
NumberOfThreadsStudyTileisthemaximumnumberofthreadsthatcanbeusedpercoveragepredictioncalculation
(0bydefault,8maximum).Ifyousetthisoptionto0or1(recommended),Atollwilluseonethreadforthecalculation.
NumberOfThreadsNeighbouristhemaximumnumberofthreadsthatcanbeusedforautomaticneighbourallocation
(4bydefault,8maximum)
NumberOfThreadsMicrowaveisthemaximumnumberofthreadsthatcanbeusedformicrowavelinkcalculations(4
bydefault,8maximum)
Alltheseoptionsareupperlimitspercomputer.Atollsupportsamaximumof64parallelthreads.
12.1.6.14 DisablingParallelCalculationofMonteCarloSimulations
For UMTS HSPA and CDMA2000 1xRTT 1xEVDO documents, Atoll can perform multithread calculations of Monte Carlo
simulations.Ifyouwanttodisabletheparallelcalculation,addthefollowinglinestotheAtoll.inifile:
[CDMA]
ParallelSimulations = 0
ParallelSimulationsissetto1bydefault.
TheGeneratorInitialisationmustbesetto0inorderforthesimulationstobecalculated
inparallel.
TheparallelcalculationofMonteCarlosimulationsinTDSCDMA,WiMAX,LTE,andWiFidocumentsisdisabledbydefault.It
shoudnotbeenabledinTDSCDMAdocuments.
12.1.6.15 PerformingCalculationsinReadOnlyDocuments
Bydefault,whenyouopenareadonlyAtolldocument,itisnotpossibletoruncalculationsinit.Ifyouwanttoruncalculations
inreadonlydocuments,addthefollowinglinesintheAtoll.inifile:
[Studies]
171
Forsk2014
ComputeEvenIfReadOnly = 1
IfyouopenadocumentthatisalreadyopeninanotherAtollsession,Atollletsyouopenthedocumentasreadonly.
12.1.6.16 IdentifyingTransmitter,Repeater,andRemoteAntennaCoverageAreas
InGSM,UMTS,CDMA2000,LTE,andWiMAXdocuments,youcancreatea"CoveragebyAerial"predictionprovidingseparate
coverageareasoftransmitters,repeaters,andremoteantennas.
InordertomakethiscoveragepredictionavailableinAtoll,addthefollowinglinesintheAtoll.inifile:
[Studies]
AerialStudy = 1
12.1.6.17 ChangingtheRoundingMethodUsedforProfileExtraction
BeforeAtoll2.8.0,realvaluesforaltitudesreadfromtheDTMfileswereroundeddowntotheirintegervalues.However,from
Atoll2.8.0 onwards, real values are rounded up or down to their nearest integer values. For example, using the previous
method,98.8 mwasroundedto98 m,butwiththenewmethod,itisroundedto99 m.Ifyouwanttoswitchbacktothe
previousmethod,addthefollowinglinesintheAtoll.inifile:
[Calculations]
RoundAltitudes = 0
RoundAltitudesissetto1bydefault.
12.1.6.18 EstimatingRequiredandUsedMemorySizeforUMTSSimulations
AtollcanestimatetherequiredandusedmemorysizesforUMTSsimulationsanddisplaytheestimatesintheSourceTraffic
tabofthenewsimulationgroupdialogue.Estimatedmemorysizewithinthegreenregionmeanslowconsumption,within
theyellowregionmeansmediumconsumption,withintheorangeregionmeanshighconsumption,andwithintheredregion
meansveryhighconsumption,inwhichcasethesimulationsmightgenerateanoutofmemoryerrorandnotcomplete.
Toactivatethememoryestimationfeature,addthefollowinglinesintheAtoll.inifile:
[CDMA]
PredictSimuMemorySize = 1
PredictSimuMemorySizeissetto0bydefaultwhichmeansthefeatureisnotactive.
12.1.6.19 DisablingCalculationsOverNoDataValuesforDTMandClutterClasses
IfyoudontwantAtolltocalculatepathlossesonthepixelslocatedovernodatavaluesdefinedintheDTMandclutterclasses
files,addthefollowinglinesintheAtoll.inifile:
[FskPropagModels]
OptimOnNoData = 1
Bydefault,OptimOnNoDataissetto0.ThisoptiononlyworkswiththepropagationmodelsavailablewithAtollbydefault.
12.1.6.20 Coplanning:CalculatingPredictionsintheCurrentDocumentOnly
AtollcalculatesalltheunlockedcoveragepredictionsinthePredictionsfolderofthecurrentdocumentandtheunlocked
coveragepredictionsinthelinkedPredictionsfolderfromanotherdocumentwhenyouclicktheCalculatebutton,pressF7,
or select the command from a context menu in the current document. If you want Atoll to calculate only the unlocked
coveragepredictionsinthePredictionsfolderofthecurrentdocument,andnotinthelinkedPredictionsfolderfromanother
document,addthefollowinglinesintheAtoll.inifile:
[CoPlanning]
ComputeLinkedPredictions = 0
ComputeLinkedPredictionsissetto1bydefault.
172
AT321_AM_E1
12.1.6.21 Coplanning:CalculatingPredictionsinSerialorinParallel
IfyouwantAtolltocalculateinparalleltheinvalidorunavailablepathlossmatricesandunlockedcoveragepredictionsinthe
PredictionsfolderofthecurrentdocumentandthelinkedPredictionsfolderfromanotherdocument,addthefollowinglines
intheAtoll.inifile:
[CoPlanning]
LinkedPredictionsComputationMode = Parallelized
LinkedPredictionsComputationMode is set to Serialized by default, which means the path loss matrices and unlocked
coveragepredictionsinthecurrentandlinkeddocumentsarecalculatedinserial.
IfyousetLinkedPredictionsComputationModetoanyothervalue,thecalculationsareperformedinparallelbutwithoutbeing
managedbyatasklist.
CalculationsarecarriedoutstartingwiththecurrentdocumentintheorderofthecoveragepredictionsinthePredictions
folder.
12.1.6.22 ForcingNeighbourSymmetryOnlyInsideFocusZone
AtollcarriesoutautomaticneighbourallocationontransmitterslocatedinsidetheFocusZone(ortheComputationZoneif
theFocusZonedoesnotexist).WhenyourunanautomaticneighbourallocationwiththeForceSymmetryoptionselected,
Atollmakescalculatedneighbourrelationssymmetricalevenifoneofthetransmitterintheneighbourrelationislocated
outsidetheFocusZone.IfyouwantAtolltomakeonlythoseneighbourrelationssymmetricalforwhichbothtransmittersin
theneighbourrelationarelocatedinsidetheFocusZone,addthefollowinglinesintheAtoll.inifile:
[Neighbours]
ForceSymmetryInFocusZone = 1
ForceSymmetryInFocusZoneissetto0bydefault.
12.1.6.23 UsingPoissonDistributioninMonteCarloSimulations
By default, mobiles are generated in each simulation following a Poisson distribution. This means that there are small
variationsinthenumberofrandomlydistributedmobilesfromonesimulationtoanother.Todisablethistypeofdistribution,
i.e.,tohavethesamenumberofmobilesgeneratedineachsimulationofagroup,addthefollowinglinesintheAtoll.inifile:
[Simulation]
RandomTotalUsers = 0
Bydefault,RandomTotalUsersissetto1.
12.1.6.24 CalculatingEIRPfromMaxPowerinSignalLevelPredictions
AtollcalculatestheEIRPfromthepilotpowerinUMTSandCDMA2000,andreferencesignalpowerinLTE.Ifyouwishto
calculatetheEIRPfromtheMaxPowervalueswhencalculatingsignallevelbasedcoveragepredictions,addthefollowing
[Studies]
EIRPfromMaxPower = 1
Bydefault,EIRPfromMaxPowerissetto0.
This option applies to Coverage by Transmitter, Coverage by Signal Level, and Overlapping Zones predictions in UMTS,
CDMA2000,andLTE.
12.1.6.25 ExcludingFilteredTransmittersfromtheListofNeighbours
Bydefault,Atollincludesfilteredtransmittersinthelistofneighbours.Ifyouwishtoexcludefilteredtransmittersfromthe
listofneighbours,addthefollowinglinesintheAtoll.inifile:
[Neighbours]
ExcludeFilteredCellsFromNeighbourLists = 0 (default)
Bydefault,ExcludeFilteredCellsFromNeighbourListsissetto0.
173
Forsk2014
12.1.6.26 ChangingtheWeightingFactoroftheEffectiveIntertransmitterDistance
Bydefault,theweightingfactoroftheeffectiveintertransmitterdistanceisset0.3.Tochangethisweightingfactor,addthe
[Neighbours]
DistanceAzimutWeightingPercent = 0.3 (default)
Ifthevalueyousetistoohigh(e.g.0.7),theresultingintertransmitterdistancecanbe
negative.Insuchacase,nothingwillbedisplayedinthecorrespondingtablecell.
12.1.6.27 ExtendingtheMaximumIntersiteDistancetoRepeatersandRemote
Antennas
Themaximumintersitedistanceusedinautomaticneighbourallocationandneighbourimportanceevaluationconsidersthe
donorsitesonly.Ifyouwantittoalsoconsiderrepeatersandremoteantennas,thenaddthefollowinglinesintheAtoll.inifile:
[Neighbours]
RepeaterInterSiteDistanceInAlloc = 1 #(default = 0)
12.1.6.28 ForcingtheRealIntersiteDistanceThreshold
By default, the automatic neighbour allocation compares the defined Max intersite distance with the effective inter
transmitterdistance.Asaconsequence,therecanbecaseswheretherealdistancebetweenassignedneighboursishigher
thantheMaxintersitedistance,becausetheeffectivedistanceissmaller.
ToforceAtolltocomparethedefinedMaxintersitedistancewiththerealintersitedistance,addthefollowinglinesinthe
Atoll.inifile:
[Neighbours]
RealInterSiteDistanceCondition = 1 #(default = 0)
12.1.6.29 PrioritisingIndividualIntersiteDistancesinNeighbourImportance
Calculation
Bydefault,theneighbourimportancecalculatedwithrespecttodistanceisbasedontheglobalMaxintersitedistancesetting
forallneighbourcandidates.Asaconsequence,therecanbecaseswherethecalculatedimportanceisdifferentwhenthe
globalMaxintersitedistanceismodified.
YoucanavoidthatbyforcingAtolltoprioritiseindividualdistancesbetweenreferencetransmitters/cellsandtheirrespective
neighbourcandidates.Todothat,addthefollowinglinesintheAtoll.inifile:
[Neighbours]
CandidatesMaxDistanceInImportanceCalculation = 1 #(default = 0)
12.1.6.30 KeepingtheAssignedNeighbourswhicharenotSymmetrisedwiththe
ReferenceTransmitter
By default, when the Force Symmetry option is selected and the neighbour list of a transmitter is full, the reference
transmitterisnotaddedasaneighbourandthattransmitterisremovedfromthereferencetransmittersneighbourslist.
ToforceAtolltokeepthattransmitterinthereferencetransmittersneighbourslist,addthefollowinglinesintheAtoll.inifile:
[Neighbours]
DoNotDeleteSymmetrics = 1 #(default = 0)
12.1.6.31 EnablingandDisablingPersitePathLossMatrixCalculations
Atollcalculatespathlossmatricesofcolocatedcositetransmittersinasinglestep,i.e.,persite,insteadofcalculatingeach
transmittersmatrixseparately.Youcandisablepersitecalculationofpathlossmatricesbyaddingthefollowinglinesinthe
Atoll.inifile:
[RemoteCalculation]
174
AT321_AM_E1
DisablePathlossPerSiteCalculation = 1
DisablePathlossPerSiteCalculationissetto0bydefaultforAtoll64bitandto1forAtoll32bit.
12.1.6.32 DefiningaGlobalMaximumPathLossCalculationRadius
Youcansetamaximumpathlosscalculationradius,applicabletobothmainandextendedmatrices,byaddingthefollowing
[Transmitter]
MaximumCalculationRadius = X
WhereXisthemaximumcalculationradiusinmetres.Bydefault,thereisnolimitforthepathlosscalculationradii.Thelimit
yousethereisappliedtovaluesenteredbytheuserintheTransmitterstableorpropertiesdialogbox.
12.1.7 GSMGPRSEDGEOptions
12.1.7.1 ConsideringIntertechnologyInterference
InGSM"CoveragebyC/ILevel(DL)"predictionsandinpointanalysis("Interference"and"Details"views),intertechnology
interference is taken into account by default. By adding the following option in the Atoll.ini file, you can add an Inter
technologycheckboxtothelistofInterferenceSourcesontheConditionstabof"CoveragebyC/ILevel(DL)"predictions
Propertiesdialogboxesandinpointanalyses"Interference"and"Details"views,whichwillallowtoconsiderornotinter
technologyinterference.
[GSM]
ExternalIncluded = 0
ExternalIncludedissetto1bydefault,i.e.intertechnologyinterferenceistakenintoaccountbydefaultinGSM"Coverageby
C/ILevel(DL)"predictions(theIntertechnologycheckboxdoesnotappearinthelistofInterferenceSources)andinpoint
analyses"Interference"and"Details"views.
12.1.7.2 ConsideringOverlappingZonesforIMCalculationBasedonTraffic
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
calculationbasedon"All"theservers(notBestServer),Atolldoesnotconsidertheoverlappingtoimproveperformance.
However,youcaninstructAtolltoconsidertheoverlappingduringthesecalculationsaswellbyaddingthefollowinglinesin
theAtoll.inifile:
[Features]
IM_TRAFFIC_OVERLAP = 1
12.1.7.3 SettingtheDefaultBSICFormat
YoucansetthedefaultBSICformattobeusedbyAtollbyaddingtheselinesintheAtoll.inifile:
[BsicFormat]
DefaultValue = 1 for Octal or 0 for Decimal format
DefaultValueenablesyoutochangethedefaultBSICformat(Octalbydefault)whenyoucreateanewAtolldocument.
12.1.7.4 CheckingDatabaseConsistencyAutomatically
IfyouwantAtolltoautomaticallyperformabasicdataconsistencychecktoavoidincompatibilitybetweenredundantfields
inGSMGPRSEDGEdocuments,addthefollowinglinestotheAtoll.inifile:
[Refresh]
TRXIntegrity = 1
Bydefault,thisoptionisconsideredtobesetto0,whichimprovesAtollsperformance.
If this option is set to 1, Atoll updates the values of the fields "Number of TRXs" and "Channels" in the Table tab of the
TransmittersfoldersPropertiesdialoguewiththevaluesfromtheTRGsandtheTRXstablesrespectively,whenadocument
isopenedfromadatabaseorrefreshed.
175
Forsk2014
12.1.7.5 DisablingtheMaximumRangeParameter
Themaximumcellrangeparameter(SystemframeintheNetworkSettingsfoldersPropertiesdialogue)inGSMGPRSEDGE
documentsisusedbydefaultandsetto35 km.YoucandisablethisoptionbyaddingthefollowinglinesintheAtoll.inifile:
[Perfos]
MaxRangeApplied = No
Ifyousetthisoptiontoanythingotherthan"No",Atollwillusethemaximumrangeparameterandsetittothedefaultvalue
of35 km.
12.1.7.6 EnablingtheSupportforMultibandTransmitters
Atolliscapableofmodellingtransmitterswithsubcells(TRXgroups)belongingtodifferentfrequencydomains.Toturnonthe
multibandmodellingfeature,addthefollowinglinesintheAtoll.inifile:
[Studies]
MultiBandManagement = 1
MultiBandManagementissetto0bydefault.Enablingmultibandmanagementallowstheuserstoaccessthemultiband
management features through the Frequency Band Propagation button under the Subcells section of the TRXs tab of a
transmittersPropertiesdialogue,andthroughtheSubcells>MultiBandPropagationParameterscommandinthecontext
menuoftheTransmittersfolder.
IntheMultiBandPropagationParameterstableandinthedatabase,Atollusesthe"@"charactertoidentifythemultiband
transmitters.Therefore,ifyouareworkingonadocumentwithmultibandtransmitters,andyouhavethe"@"characterin
thenamesofrepeaters,remoteantennas,orsubcellswithoutadonor/maintransmitter,Atolldeletestheserecordswhen
openingthedocumentfromadatabase.IfyoudonotwantAtolltoautomaticallydeletesuchrecordswhenopeningthe
documentfromadatabase,youhavetosettthefollowingoptionintheAtoll.inifile:
[Studies]
RemoveBadMultiCells = 0
RemoveBadMultiCellsissetto1bydefault.
Ifyouarenotworkingwithmultibandtransmitters,i.e.,MultiBandManagementissetto0,Atolldoesnotautomatically
deletesuchrecords.IfyouwantAtolltoautomaticallydeletesuchrecordswhenopeningthedocumentfromadatabase,you
havetosettthefollowingoptionintheAtoll.inifile:
[Studies]
CleanMultiCellManagement = 1
CleanMultiCellManagementissetto0bydefault.
12.1.7.7 SettingtheBestServerCalculationMethodinSamePriorityHCSLayers
AtollcancalculateservingtransmittersaccordingtoHCSlayerprioritiesincoveragepredictions.Thesignallevelreceivedfrom
HCS
theservingtransmittermustbehigherthantheminimumreceptionthreshold( T Rec )foritsHSClayer.

IftherearetwoHCSlayerswithdifferentpriorities:
TheservingtransmitteristheonethatbelongstotheHCSlayerwiththehighestpriority.
IftherearetwoHCSlayerswiththesamepriority:
1ststrategy:Theservingtransmitteristheoneforwhichthedifferencebetweenthereceivedsignalleveland T HCS
Rec
isthehighest.Where, T HCS
Rec istheminimumreceptionthresholdfortheHSClayerofeachrespectivetransmitter.
2ndstrategy:Theservingtransmitteristheonewhichhasthehighestreceivedsignallevel.
Thedefaultstrategyisthe1stone.Youcanusethe2ndstrategybyaddingthefollowinglinesintheAtoll.inifile:
[Studies]
UseThresholdForSameLayerPriorities = 0
UseThresholdForSameLayerPrioritiesissetto1bydefault.
176
AT321_AM_E1
12.1.7.8 HidingAdvancedAFPParameters
YoucanhidetheadvancedparametersfromtheAtollAFPPropertiesdialoguebyaddingthefollowinglinesintheAtoll.inifile:
[AFP]
SimpleUserGUI = 1
SimpleUserGUIissetto0bydefault.SettingSimpleUserGUIto1hidestheInterferenceMatrices,MAIO,andAdvancedtabs.
12.1.7.9 ModifyingtheThresholdsforImportantViolationsinAFP
Bydefault,AFPallocationresultsaredisplayedinredwhenaresourcehasbeenmodifiedandthereisanimportantseparation
constraintviolation.Youcanmodifythethresholdsabovewhichtheimportantviolationswillbehighlightedbyaddingthe
[GSM]
CoRedColorThreshPercent = 12
AdjRedColorThreshPercent = 15
CoRedColorThreshPercent(forcochannels)andAdjRedColorThreshPercent(foradjacentchannels)aresetto12and15by
default.Youcanmodifythesethresholdstoanyvaluerangingfrom0to999.
SettingCoRedColorThreshPercentand/orAdjRedColorThreshPercentto0willforcethebehaviourofpreviousreleaseswhere
importantandlessimportantviolationswerebothhighlighted.
12.1.7.10 HidingViolationsBetweenLowImportanceGSMNeighboursinAFP
Results
Bydefault,eachneighbourpairhasanimportancevaluewhichdefinesthequality(andtherank)oftheneighbourlink.This
importancecanbeevaluatedduringtheautomaticneighbourallocation,aspecificcalculationprocessormanuallypopulated
in the neighbour tables. In the Allocation tab of the AFP results dialogue, no difference is made between high and low
importanceneighboursintermofviolationdisplay.Inotherwords,whatevertheimportancevalueis,anyneighbourlinkina
separationviolationissystematicallydisplayedinaspecificcolour.Youcanavoiddisplayingseparationviolationsbetween
lowimportanceneighboursinaspecificcolourbyaddingthefollowinglinesintheAtoll.inifile:
[GSM]
MinNeighbourImportanceInAFPResults = XX
WhereXXistheminimumimportanceforaneighbourpairtobeconsideredaspotentiallyviolated.
ThevalueintheAtoll.inifilehastobebetween0and100whereastheimportancevalue
intheneighbourstablesisbetween0and1.
12.1.7.11 HidingViolationsBetweenNonsynchronisedMALsMAIOsinAFPResults
In SFH, one can call synchronised MALsMAIOs the case where, assuming the synchronisation site and the HSN can be
identifiedovertheentiredurationofaGSMframe.Asanexample,whenthesynchronisationsite,theHSNandtheMALlength
of 2 MALsMAIOs are identical, it is always possible to identify if these are or not in separation violation. In case the
synchronisationsite,theHSNand/ortheMALlengthsor2MALsMAIOsaredifferent,acertainprobabilityofcollision(and
consequentlyaseparationviolation)mayoccur.
You can avoid displaying separation violations between nonsynchronised MALsMAIOs in a specific colour by adding the
[GSM]
ShowNonSynchSFHViolationsInAFPResults = 0
ShowNonSynchSFHViolationsInAFPResultsissetto1bydefault.SettingShowNonSynchSFHViolationsInAFPResultsto0does
notshownonsynchronised(MALsMAIOs)possiblyinaseparationviolationcase.
12.1.7.12 SelectingtheInterferenceMatricesUsedDuringtheAFP
AllactiveinterferencematricesaretakenintoaccountduringanAFPsessionaccordingtothemethoddefinedintheAtoll.ini
file:
177
Forsk2014
[AFP]
WorstCaseIM_FskAfp = 0 or 1
ThisoptionisvalidforForsksAFP.
1referstothedefaultmethod,whichistheworstcaseone.Settingthisvalueto0willinstructtheAFPtousethesecond
method.
Worst Case Method: For each interference matrix relationship, the worst case value in all the active interference
matricesistakenintoconsideration.
FirstValueMethod:Foreachinterferencematrixrelationship,thefirstvaluefoundinanyactiveinterferencematrix
istakenintoconsideration.Theorderinwhichtheinterferencematricesarescannedtofindthefirstvalueistheorder
oftheinterferencematricesintheInterferenceMatricesfolderintheNetworktab,i.e.thefirstIMistheoneatthe
top.
TheFirstValuemethodwasthedefaultmethodinearlierversionsofAtollwhichallowedmultipleinterferencematriximport.
12.1.7.13 DefiningtheMaximumNumberofTransmittersforReuseDistance
WhenusingthereusedistancewiththeAFP,youcanlimitthenumberofrelationsbasedondistancetakenintoconsideration
foreachtransmitterinordertoensurethatperformanceisnotdegraded.Inthisexample,thenumberislimitedto70:
[AFP]
GlobalDistanceMatrixDegreeUB = 70
12.1.7.14 MakingRedundantFieldsintheTransmittersTableReadonly
SomeofthefieldsintheTransmitterstableareredundantwithotherfieldsintheSubcellstable.Modifyingvaluesinonetable
mightcauseinconsistenciesbetweenthetwotablesinsomecases.Youcanmaketheseredundantfieldsuneditableinthe
TransmitterstablebyaddingthefollowinglinesintheAtoll.inifile:
[GSM]
CanEditTRXInfoAtTXLevel = 0
TheredundantfieldsintheTransmitterstablearetheBCCHandtheNumberofTRXsfields.
CanEditTRXInfoAtTXLevelissetto1bydefault,whichmeansthatthefieldsareeditable.
12.1.7.15 SettingtheTransmissionDiversityGain
Ifasubcellisusingtransmissiondiversity,theaircombininggainof3 dBisappliedtoallthereceivedsignallevels,wanted(C)
aswellasinterfering(I),duringcalculations.Youcanmodifythedefaultvalueof3 dBbyaddingthefollowinglinesinthe
Atoll.inifile:
[Studies]
2GTxDiversityGain = X
WhereXisthevalueoftheaircombininggainindB.
MT/YR24/10/13:OptionGroupedHCSServerssupprimeduUM,textecidessouscachaucasoonfaitmarchearrire
12.1.7.16 AddingGroupedHCSServersOptioninCalculations
Bydefault,theGroupedHCSServersoptionisnotavailableinthelistofchoicesforServerincoveragepredictions,traffic
capture,andinterferencematrixcalculations.Tomakethisoptionavailable,addthefollowinglinesintheAtoll.inifile:
[TMP]
ExtraServZone = 1
12.1.7.17 DeactivatingFrequencyBandFilteringinIMCalculation
Whencalculatinginterferencematrices,Atollfilterspotentialinterferersbasedonthefrequencybandsusedbytheinterfered
and interferingsubcells. Forexample,ifthe interferedsubcelluses theGSM900bandandapotential interferer usesthe
GSM1800band,andthetwobandsdonotoverlap,thenthispotentialinterfererisignored.Thisfilteringhelpsimprovethe
calculationperformancebyignoringtheinterferedinterfererpairsthatwouldhaveeventuallyresultedinnoIMentryafter
thecalculation.Anyinterfererwhoseassignedfrequencybandoverlapswiththefrequencybandassignedtotheinterfered
subcellisnotfiltered.
YoucandeactivatethisfilteringbyaddingthefollowinglinesintheAtoll.inifile:
178
AT321_AM_E1
[IM]
FilterByFrequencyBands = 0
FilterByFrequencyBandsissetto1bydefault.
12.1.7.18 StartingTRXIndexesat1
Bydefault,TRXsareindexedbyAtollstartingatindex0.Ifyouwishtostarttheindexingat1,addthefollowinglinesinthe
Atoll.inifile:
[GSM]
FirstTRXIndex = 1
FirstTRXIndexissetto0bydefault.SettingFirstTRXIndextoanyothervaluehasthesameeffectassettingitto1.
12.1.7.19 HidingtheTRXIndex
IfyouwishtohidetheTRXindexcolumn,addthefollowinglinesintheAtoll.inifile:
[GSM]
TRXIndexHidden = 1
TRXIndexHiddenissetto0bydefault.
12.1.7.20 ExtendingtheAllowedValueRangeforC/IandReceptionThresholds
CurrentlythesubcellC/Ithresholdallowsvaluesfrom0to24 dBandthereceptionthresholdallowsvaluesfrom116to
50 dBm.Ifyouwishtoextendthisrangeto30 dBand134 dBmfortheC/Iandreceptionthresholdsrespectively,addthe
[GSM]
WideRangeSubcellThresholds = 1
WideRangeSubcellThresholdsissetto0bydefault,whichcorrespondstothedefaultvalueranges.
12.1.7.21 AutomaticallyCorrectingOutofrangeSubcellValues
WhenoutofrangesubcellvaluesarefoundintheGSMnetwork,Atollfixesthembydefaultasfollows:
SubcellValue
Ifitis...
...thenitisreplacedby:
NumberofrequiredTRXs
<1or>62
NumberofrequiredBCCHs
not1
Trafficload
<0or>1
Receptionthreshold
<116dBmor>50dBm
102dBm
MinimumC/I
>25 dB
12dB
Halfratetrafficratio
<0%or>100%
40%
Meanpowercontrolgain
<0dBor>32dB
4dB
DLpowerreduction
<0dBor>25dB
0dB
AFPweight
<0or>100
Targetrateoftrafficoverflow
<0%or>100%
0%
Maximumpercentageofinterference
<1%or>100%
1%
MaximumMALsize
>62
62
Ifyouwishtomodifythisdefaultbehaviour,addthefollowinglinesintheAtoll.inifile:
[GSM]
SubcellValueFixMethod = 1
SubcellValueFixMethodissetto0bydefault,whichcorrespondstothedefaultbehaviourdescribedabove.
179
Forsk2014
Ifyousetthisparameterto1,thevaluescurrentlyoutofrangeareshiftedtotheclosestboundaryoftheauthorisedrange.
Forexampleifthereceptionthresholdislessthan116dBm,itwillbereplacedby116dBminsteadof102dBmasinthe
defaultbehaviour.Likewise,ifitisgreaterthan50dBm,itwillbereplacedby50dBminsteadof102dBm.
Ifyousetthisparameterto2,thevalueswhicharecurrentlyoutofthepermittedrangeswillnotmodified.
12.1.8 UMTSHSPA,CDMA2000,andTDSCDMAOptions
12.1.8.1 SuppressingCellNameCarrierSuffixes
Itisonlypossibletosuppressthecarriersuffixina3Gcellnameinthecaseofasinglecarrierscenario,i.e.,thefirstcarrieris
alsothelastcarrierintheglobalparameters.Todothis,addthefollowinglinesintheAtoll.inifile:
[3GCells]
NoSuffixIfUniqueCarrier = 0 or 1
Thisissetto0bydefault,whichmeansthatcellnameswillfollowthenormalconventionofAtoll,SiteN_X(C).Ifthereisonly
onecarrier,meaningthatCisunique,thenthisoptioncanbesetto1.Thiswillresultincellnameswhichwillbesameasthe
transmitternames,SiteN_X.
12.1.8.2 DisablingMacrodiversity(SHO)GainsinCalculations
InUMTSHSPAandCDMA2000documents,macrodiversitygainsarecalculatedforpilotEc/Io,andDLandULEb/Ntbasedon
therespectivestandarddeviations.Youcandeactivatethecalculationanduseofmacrodiversitygainsinallthecalculations
[Shadowing]
WithSHOGain = 0
WithSHOGainissetto1bydefault.
Ifyouwish,youcandeactivatethemacrodiversitygaincalculationforthepilotEc/Ioonlybyaddingthefollowinglinesinthe
Atoll.inifile:
[CDMA]
AddPilotSHOGain = 0
AddPilotSHOGainissetto1bydefault.
12.1.8.3 CalculatingandDisplayingPeakorInstantaneousHSDPAThroughput
InUMTSHSPAdocuments,youcanchoosetodisplayandworkwitheitherpeakvaluesorinstantaneousvaluesoftheHSDPA
throughputspermobile,cell,andsiteinsimulationresults.Todothis,youcanaddthefollowinglinesintheAtoll.inifile:
[CDMA]
HSDPAThroughputPeak = 0 or 1
0:Instantaneousthroughput(Default)
1:Peakthroughput
IfyouchoosetodisplaytheinstantaneousHSDPAthroughputs,Atollwill:
DisplaythenumberofsimultaneousHSDPAusersinthesimulationresults.
PlaceacertainpartofHSDPAusersinawaitingqueueduringsimulations.
Display the instantaneous gross and instantaneous application level throughputs per mobile and per cell in the
simulationresults.
DisplaytheinstantaneousthroughputpersiteintheSitestabofthesimulationresults.
IfyouchoosetodisplaythepeakHSDPAthroughputs,Atollwill:
NotdisplaythenumberofsimultaneousHSDPAusersinthesimulationresults.
Displaythepeakgrossandpeakapplicationlevelthroughputspermobileandpercellinthesimulationresults.
DisplaytheMUGtableinthecellproperties.Inputfromthisareusedtocalculatethepeakgrossthroughputpercell
whentheschedulingalgorithmis"ProportionalFair".
DisplaytheaverageHSDPAthroughputperuserintheCellstabofthesimulationresults.
HSDPAresourceschedulingwillnotbecarriedout.TheHSDPAthroughputforeachuserwillbecalculatedbytakinginto
accounttheMUGcorrespondingtothecurrentnumberofconnectedHSDPAusers.
180
AT321_AM_E1
InAverageSimulationresults,theaverageHSDPAthroughputperusercanbecalculatedexcludingthesimulationswhereno
HSDPAuserswereserved.Todothis,enterthefollowinglinesintheAtoll.inifile:
[CDMA]
HSDPAAvgSimuResults = 1
HSDPAAvgSimuResults=0bydefault.
12.1.8.4 SettingthePowertoUseforIntracellInterferenceinHSDPA
InHSDPApredictionstudies,youcanchoosewhethertoperformintracellinterferencecalculationsbasedontotalcellpower
(Ptot)ormaximumcellpower(Pmax).Bydefault,Atollperformsthiscalculationbasedonthetotalpower.Youcaninstruct
AtolltousemaximumpowerinsteadbyaddingthefollowinglinesintheAtoll.inifile:
[CDMA]
PmaxInIntraItf = 1
0:Intracellinterferencecalculationbasedontotalpower(Default)
1:Intracellinterferencecalculationbasedonmaximumpower
12.1.8.5 EnablingCoveragePredictionsofConnectionProbabilities
YoucanperformcoveragepredictionstudiesforconnectionprobabilitiesinUMTSHSPAdocumentsbyaddingthefollowing
[CDMA]
UseStudyCnxProba = 1
MinUsersPerBin = X
ThiscoveragepredictionstudyisavailableinthelistofpredictionstudiesifUseStudyCnxProbaissetto1.Otherwise,itwill
notbeavailable.MinUsersPerBinistheminimumnumberofusersperpixelrequiredforthatpixeltobetakenintoaccount
inthecoverageprediction.
12.1.8.6 SettingtheCalculationMethodforHSPDSCHCQI
IfyouchoosetheCQIbasedonCPICHqualityoptioninGlobalParameters,youcanselecttheformulausedforcalculating
HSPDSCHCQIinAtollbyaddingthefollowinglinesinthefile:
[CDMA]
CQIDeltaWithPower = 0 or 1
CQIDeltaWithPowerissetto1bydefault.Inthiscase,theHSPDSCHCQIiscalculatedusingtheformula:
CQI HS PDSCH = CQI pilot P pilot + P HS PDSCH
IfyousetCQIDeltaWithPowerto0,theHSPDSCHCQIwillbecalculatedusingtheformula:
EC
EC
CQI HS PDSCH = CQI pilot -------
+ -------
N T pilot N T HS PDSCH
Notethatthedefaultconfiguration(CQIDeltaWithPowersetto1)isrelevantonlywhen N T iscalculatedusingthe"Total
Noise"option.
TheaboveequationsareindB.RefertotheTechnicalReferenceGuideformoredetails.
12.1.8.7 EnablingOrthogonalityFactorinPilotEC/NTCalculationinHSDPA
%PilotFingerandtheOrthogonalityFactormodeltwodifferenteffectsontheCPICHquality.%PilotFingerisrelatedtothe
CPICHphysicalchannelonlyandmodelsthelossofenergyintheCPICHsignalduetomultipath.TheOrthogonalityFactoris
relatedtothecorrelationbetweentheCPICHphysicalchannelandotherintracellphysicalchannels.
YoucaninstructAtolltousetheOrthogonalityFactorinthecalculationofpilotEC/NTinHSDPAinsteadof%PilotFingerby
[CDMA]
OrthoInCPICH = 1
181
Forsk2014
12.1.8.8 SettingtheMaximumNumberofRejectionsforMobiles
YoucandefineamaximumnumberofrejectionsformobilesduringsimulationsbyaddingthefollowinglinesintheAtoll.ini
file:
[CDMA]
MaxRejections = X
IfamobileisrejectedXnumberoftimes,itwillnolongerbeconsideredinthenextiterations.
12.1.8.9 SettingtheMaximumNumberofRejectionsforHSDPAMobiles
You can set the number of times an HSDPA mobile should be rejected (or placed in a queue) before it is considered
permanentlyrejected(orpermanentlyplacedinthequeue).Thedefaultvalueofthisoptionis5.Tomodifythedefaultvalue,
enterthefollowinglinesintheAtoll.inifile:
[CDMA]
HSDPAMaxRejections = X
Where X is the number of times an HSDPA mobile should be rejected to be considered permanently rejected for the
simulation.
12.1.8.10 DefininganOffsetWithRespecttoTheThermalNoise
YoucandefineanoffsetwithrespecttothethermalnoisebyaddingthefollowinglinesintheAtoll.inifile:
[CDMA]
CutOffSimu = X
Where,XistheoffsetvalueindBs.DuringMonteCarlosimulations,calculationsperformedoneachmobileonlytakeinto
accountthecellswhosereceivedpower,atthemobilelocation,isgreaterthanthethermalnoiseminusthisoffset.Youshould
setCutOffSimuto20dBforoptimumperformancewithoutlosingalotofinterference.
12.1.8.11 SettingPrecisionoftheRasterisationProcess
During Monte Carlo simulations, Atollinternallyconverts vectortraffic maps to rastertrafficmaps in order to perform a
distributionofusersaccordingtothetrafficdensitiesandtheconnectionprobabilities.Theaccuracyofthisconversionfrom
vectorstorasterishighenoughformost,nearlyall,cases.However,thisaccuracymightnotbeenoughforhighlyprecise
vectorpolygonsdefiningtraffichotspots.
Thefigurebelowdepictsthiseffectforavectorpolygonwhichisjustslightlylargerthan1rasterpixel.Thevectorpolygonand
therasterbinhavethesametrafficdensityinthefollowingfigure.
Figure 12.1:RasterisationProcess
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
(accuratetoallthedecimalplaces)sizeofapixel(ormultiplesofapixel)inordertogetrasterpixelswiththeexactsame
surfaceareaasthevectorpolygons.Ifthecoordinatesofthevectorpolygonsarenotaccurate,itispossiblethattheraster
pixelfoundfromthevectorpolygonwillbeshifted1bintotherightortotheleft.
Sucharasterisationmeansthatthenumberofusersinthevectorremainscorrect,butthedensitymightbedifferentsince
thesurfaceareahaschanged(Numberofusers=UserDensityxArea).
IfyouwantAtolltoincreasetheprecisionoftherasterisationprocessforhotspotsinyournetwork.Youcanaddthefollowing
182
AT321_AM_E1
[Rasterization]
Improve = 0 or 1
Precision = 1
SurfRatio = 20
MaximumSurf = 2500
Theoptionsare:
Improve=1(bydefault)meansthatAtollwillusetheaccuraterasterisationmethodforsmallpolygons.Improve=0
meansthatthenormalrasterisationmethodwillbeusedforallpolygons.Settingthisoptionto1impliesthatthis
algorithmwillnotbeusedgloballyforallpolygons,butonlyforsmallpolygonswhicharedefinedbytheoptions
SurfRatioorMaximumSurf.
Precision=1(bydefault)meansthattherasterisationresolution(step)usedbythealgorithmforsmallpolygonsis1
metre.Youcansetittoahighervalueifyouobserveperformancedegradation.Thestepofrasterisationmeansthe
sizeofthebinusedtoapproximatethevectorshapewithbins.
If you set Precision = 1, the performance (calculation speed) can be considerably
decreased depending onthesize ofyour network.It is recommendedto seta higher
valueforthePrecisionoption.
SurfRatio=20(bydefault)meansthattheaccuratealgorithmwillbeusedonlyforpolygonswhosesizeissmallerthan
20timesthesizeofthenormalrasterbin.ThenormalrasterbinsizeinanAtolldocumentisthefinestresolution
amongthegeographicdataavailableinthedocument.
IfyourAtolldocumentcontainstwogeographicdatafiles,onewitha20mresolutionand
theotherwitha5mresolution,andyouremovethe5monefromyourdocument,Atoll
willstillkeep5masthenormalrasterbinsize.
MaximumSurf=2500(bydefault)meansthatapolygonwillbeconsideredsmallonlyifitssurfaceareaislessthanor
equalto2500sq.m.
So,apolygonwillbeconsideredsmall,andwillberasterisedusingtheaccuratealgorithm,ifeithertheratioofitssurfacearea
tothesurfaceareaofthenormalrasterbinisequaltoorlessthanSurfRatio,orifitssurfaceareaislessthanMaximumSurf.
IfyouwanttousejusttheMaximumSurfoption,youcansettheSurfRatioto0.
12.1.8.12 DefiningtheNumberofIterationsBeforeDowngrading
YoucansetthenumberofiterationsthatAtollshouldcarryoutbeforestartingthedowngrading.Thedefaultvalueofthis
optionis30.Tomodifythedefaultvalue,enterthefollowinglinesintheAtoll.inifile:
[CDMA]
IterBeforeDown = X
WhereXistheintegernumberofiterations.
12.1.8.13 AdjustingtheWorkingoftheProportionalFairScheduler
InUMTSHSPAdocuments,youcanadjusthowtheproportionalfairschedulerfunctionsbyaddingthefollowinglinesinthe
Atoll.inifile:
[CDMA]
PFSchedulerCQIFactor = X
WhereXisanumberbetween0and100,whichrepresentstheproportionalfairschedulerweight.PFSchedulerCQIFactor=
50bydefault.IfyousetPFSchedulerCQIFactor=0,theproportionalfairschedulerfunctionsliketheRoundRobinscheduler.
IfyousetPFSchedulerCQIFactor=100,theproportionalfairschedulerfunctionsliketheMaxC/Ischeduler.
12.1.8.14 DisplayingEc/I0ofRejectedMobilesinSimulationResults
InUMTSandCDMAsimulationresults,theEc/I0AS1columnintheMobilestabcanlisttheEc/I0valuesfromthebestserver
forallthemobiles,connectedorrejected.TodisplaytheEc/I0fromthebestserverfortherejectedmobiles,addthefollowing
183
Forsk2014
[CDMA]
DisplayEcIoOfRejected = 1
DisplayEcIoOfRejectedissetto0bydefault.
12.1.8.15 SwitchingBacktotheOldBestServerDeterminationMethod
BeforeAtoll2.8.0,bestserverdeterminationinUMTSandCDMAnetworksusedtobeperformedbyselectingthebestcarrier
withintransmittersaccordingtotheselectedmethod(siteequipment)andthenthebesttransmitterusingthebestcarrier.
Toswitchbacktothisbestserverdeterminationmethod,addthefollowinglinesintheAtoll.inifile:
[CDMA]
MultiBandSimu = 0
MultiBandSimuissetto1bydefault.
12.1.8.16 DisplayingAutomaticAllocationCostValues
YoucandisplaythecostvaluescalculatedbyAtollfordifferentrelationswhenallocatingscramblingcodesandPNoffsets.To
displaycostvalues,addthefollowinglinesintheAtoll.inifile:
[PSC]
DisplayCostValues = 1
DisplayCostValuesissetto0bydefault.
12.1.8.17 SelectingSCandPNOffsetAllocationStrategiesAvailableintheGUI
IntheAtoll.inifile,youcanselectthescramblingcode(UMTSandTDSCDMA)andPNoffset(CDMA2000)allocationstrategies
thatwillbeavailabletotheuserintheautomaticallocationdialogue.Toselecttheallocationstrategies,addthefollowing
[CDMA]
CodeStrategies = 1, 2, 3, 4
Theallocationstrategies1,2,3,and4correspondtothefollowing:
InUMTS:
1:Clustered
2:DistributedperCell
3:OneClusterperSite
4:DistributedperSite
InTDSCDMA:
1:Clustered
2:DistributedperCell
3:OneSYNC_DLCodeperSite
4:DistributedperSite
InCDMA2000:
1:PNOffsetperCell
2:AdjacentPNClustersperSite
3:DistributedPNClustersperSite
12.1.8.18 DefiningaFixedIntervalBetweenScramblingCodes
Youcandefineafixedintervalbetweenscramblingcodesassignedtocellsonasamesitewhentheallocationisbasedona
distributedstrategy(DistributedperCellorDistributedperSite).Toapplythedefinedinterval,addthefollowinglinesinthe
Atoll.inifile:
[PSC]
ConstantStep = 1
ConstantStepissetto0bydefault.
184
AT321_AM_E1
12.1.8.19 CompressedMode:RestrictingIntercarrierandIntertechnology
NeighbourAllocation
YoucanpreventAtollfromallocatingintercarrierandintertechnologyneighbourstocellslocatedonsiteswhoseequipment
doesnotsupportcompressedmode,byaddingthefollowinglinesintheAtoll.inifile:
[Neighbours]
CompressModeEval = 1
CompressModeEvalissetto0bydefault.
12.1.8.20 SettingtheMaximumASSizeforSCInterferencePrediction
Youcansetthemaximumactivesetsizetoafixednumberoftransmittersforthescramblingcodeinterferencecoverage
predictionbyaddingthefollowinglinesintheAtoll.inifile:
[Studies]
SCActivesetMaxSize = X
WhereXisthemaximumnumberoftransmittersintheactiveset.IfyousetSCActivesetMaxSize=10,youwillgetthesame
resultsinthecoveragepredictionastheSCInterferencetabinthepointanalysis.
12.1.8.21 DisplayingUplinkTotalLossesinCoveragebySignalLevel
InUMTSandCDMAdocuments,youcanactivatetheUplinkTotalLossesandMinimumUplinkTotalLossesdisplayoptionsin
theCoveragebySignalLevelpredictionbyaddingthefollowinglinesintheAtoll.inifile:
[Studies]
UplinkLosses = 1
UplinkLossesissetto0bydefault.Uplinktotallossesarecalculatedfromthedownlinktotallossesbyreplacingthedownlink
transmitterlossesbyuplinktransmitterlosses.
12.1.8.22 SettingtheMaximumULReuseFactorforHSUPAUsersNoiseRise
Estimation
InUMTSHSPAsimulations,Atollassumesaconstantuplinkreusefactorforestimatingthemaximumavailablenoiseriseper
HSUPAuser.ThiscancauseunnecessaryrejectionofsomeHSUPAusersinverylowtrafficcases.Youcansetanupperlimit
fortheuplinkreusefactorbyaddingthefollowinglinesintheAtoll.inifile:
[UMTSSimus]
MaxReuseFactor = X
MaxReuseFactorissetto5bydefault.
12.1.9 LTE,WiMAX,andWiFiOptions
12.1.9.1 BlockingAccesstoIEEEParametersinWiMAX
YoucandisallowmodificationoftheparametersthatcomefromtheIEEEspecifications,andarenotsupposedtobechanged,
[WiMAX]
ModifiableIEEEParams = 0
By default, ModifiableIEEEParams is set to 1, which means that all the parameters are modifiable. When you set
ModifiableIEEEParamsto0,itmeansthatthefollowingparameterswillbeunmodifiableintheGUI:
In the Permutation Zones table: Number of Used Subcarriers, Number of Data Subcarriers, and Number of
SubchannelsperChannel.
InthePermutationZonestable:SubchannelGroups(Segment0),SubchannelGroups(Segment1),andSubchannel
Groups(Segment2)forFFTsizes<1000.
185
Forsk2014
In the Permutation Zones table, the first DL PUSC permutation zone cannot be
deactivated.
IntheFrameConfigurationstableandintheGeneraltaboftheframeconfigurationsPropertiesdialogue:
NumberofPreambleSubcarriers.
IntheFramesConfigurationstable,thecellsunderTotalNumberofSubcarrierschange
intocomboboxeswiththefollowingfivevalues:128,256,512,1024,2048.
12.1.9.2 UsingOnlyBearersCommonBetweentheTerminalsandCells
Equipment
IfyouwantAtolltoperformanintersectionoverthebearerssupportedbythecellequipmentandbytheterminalequipment,
[OFDM]
UseCommonBearersOnly = 1
UseCommonBearersOnlyissetto0bydefault.WhenUseCommonBearersOnlyissetto1,Atollonlyusesthebearersfor
whichselectionthresholdsaredefinedinboththeterminalsandthecellsequipmentforbothdownlinkanduplinkbearer
selection.
12.1.9.3 EnablingDisplayofSignalsperSubcarrierPointAnalysisinLTE
BydefaultapointanalysisinLTEdisplaysRSperchannel,SS&PBCHperchannel,PDCCH&PDSCHperchannel,andRSper
subcarrier.Ifdesired,youcanalsouseapointanalysistodisplaySS&PBCHpersubcarrierandPDCCH&PDSCHpersubcarrier
[LTE]
DisplaySignalsPerSCInPtA = 1
DisplaySignalsPerSCInPtAissetto0bydefault.WhentheDisplaySignalsPerSCInPtAoptionissetto"0"orisabsent,SS&PBCH
persubcarrierandPDCCH&PDSCHpersubcarrierarenotavailableoptionsinapointanalysis.
12.1.9.4 IncludingCyclicPrefixEnergyinLTESignalLevelCalculation
Theusefulsignallevelcalculationtakesintoaccounttheusefulsymbolenergy(Es),i.e.,excludingtheenergycorresponding
tothecyclicprefixpartofthetotalsymbolduration.However,youcanincludethecyclicprefixenergyintheusefulsignallevel
calculationbyaddingthefollowinglinesintheAtoll.inifile:
[LTE]
ExcludeCPFromUsefulPower = 0
ExcludeCPFromUsefulPowerissetto1bydefault.
Independant of the option, interference levels are calculated for the total symbol durations, including the energy useful
symboldurationandthecyclicprefixenergy.
12.1.9.5 ExcludingCyclicPrefixEnergyinWiMAXandWiFiSignalLevelCalculation
Theusefulsignallevelcalculationcanexcludetheenergycorrespondingtothecyclicprefixpartofthetotalsymbolduration,
hence taking into account only the energy belonging to the usefulsymbolduration.In order to do so, you mustadd the
[WiMAX]
ExcludeCPFromUsefulPower = 1
ExcludeCPFromUsefulPowerissetto0bydefault.
Independant of the option, interference levels are calculated for the total symbol durations, including the energy useful
symboldurationandthecyclicprefixenergy.
186
AT321_AM_E1
12.1.9.6 IgnoringInterNeighbourPreambleIndexCollisioninWiMAX
The automatic preamble index allocation algorithm in Atolltakesintoaccount the possible collision of preamble indexes
assignedtoneighboursofacell.ThismeansthatAtolltriestonotallocatethesamepreambleindextotwoneighboursofa
cell.Ifyouwanttodisablethisconstraint,i.e.,allowAtolltoallocatethesamepreambleindextotwoneighboursofacell,
[WiMAX]
InterNeighbourPICollisions = 0
InterNeighbourPICollisionsissetto1bydefault.
Thepreambleindexauditbasedonneighboursalsotakesthisoptionintoaccount.WithInterNeighbourPICollisions=1,the
audit lists the cell pairs that are neighbours of a cell and are allocated the same preamble index. When
InterNeighbourPICollisions=0,thepreambleindexcollisionisnotverifiedbetweenneighboursofacell.
12.1.9.7 IgnoringInterNeighbourPhysicalCellIDCollisioninLTE
TheautomaticphysicalcellIDallocationalgorithminAtolltakesintoaccountthepossiblecollisionofphysicalcellIDsassigned
toneighboursofacell.ThismeansthatAtolltriestonotallocatethesamephysicalcellIDtotwoneighboursofacell.Ifyou
want to disable this constraint, i.e., allow Atoll to allocate the same physical cell ID to two neighbours of a cell, add the
[LTE]
InterNeighbourIDCollisions = 0
InterNeighbourIDCollisionsissetto1bydefault.
ThephysicalcellIDauditbasedonneighboursalsotakesthisoptionintoaccount.WithInterNeighbourIDCollisions=1,the
audit lists the cell pairs that are neighbours of a cell and are allocated the same physical cell ID. When
InterNeighbourIDCollisions=0,thephysicalcellIDcollisionisnotverifiedbetweenneighboursofacell.
12.1.9.8 ApplyingTransmitDiversityGainstoReferenceSignals
Formorethanonetransmissionantennaport,antennaports0and1transmitreferencesignalsusingdifferentsubcarriers
duringthesameOFDMsymbol.Ifyouwanttoincludethesubcarrierstransmittedsimultaneouslyonbothantennaportswhen
calculatingthereceivedreferencesignallevel,addthefollowinglinesintheAtoll.inifile:
[LTE]
UseDivGainOnRS = 1
IfyouwishtomakeAtollapplythesametransmitdiversitygainsonreferencesignalsasusedforPDSCH,addthefollowing
[LTE]
UseDivGainOnRS = 2
UseDivGainOnRSissetto0bydefault.ThiscorrespondstotheequationpresentintheTechnicalReferenceGuide.
12.1.9.9 RenamingOPUSCZonetoPUSCULinWiMAX
IfyouwishtoworkwithtwoPUSCULpermutationzones,youcanrenametheOPUSCpermutationzonetoPUSCULbyadding
[WiMAX]
ReplaceOPUSCwithPUSCUL = 1
ReplaceOPUSCwithPUSCULissetto0bydefault.
12.1.9.10 DeactivatingUniformDistributionofResources
By default, the basic automatic allocation of physical cell IDs and preamble indexes distributes the allocated resources
uniformly.Ifyouwishtodeactivatetheuniformdistributionofresources,addthefollowinglinesintheAtoll.inifile:
[OFDM]
UniformIDDistribution = 0
187
Forsk2014
UniformIDDistributionissetto1bydefault.
12.1.9.11 TakingSecondOrderNeighboursintoAccountintheAFP
TheLTEAFPtakesfirstorderneighboursintoaccountwhenallocatingphysicalcellIDs.TheWiMAXAFPtakesfirstorder
neighboursintoaccountwhenallocatingpreambleindexesanddownlinkanduplinkzonepermbases.IfyouwanttheAFPto
takebothfirstandsecondorderneighboursintoaccount,addthefollowinglinesintheAtoll.inifile:
[OFDM]
SecondNeighbours = 1
SecondNeighboursissetto0bydefault.
12.1.9.12 ExcludingtheAdjacentChannelOverlapfromtheAFPCostFunctions
TheLTE,WiMAX,andWiFiAFPstaketheadjacentchanneloverlapintoaccountforallocationfrequencies,physicalcellIDs,
preambleindexes,andotherresources.Ifyouwishtotakeonlythecochanneloverlapintoaccountandexcludetheeffectof
adjacentchanneloverlapinresourceallocation,addthefollowinglinesintheAtoll.inifile:
[OFDM_AFP]
AdjacentProtection = 0
AdjacentProtectionissetto1bydefault.
12.1.9.13 SwitchingBetweenSynchronisedandUnsynchronisedInterference
CalculationMethods
TwodownlinkinterferencecalculationmethodsexistinAtoll:
Method1:SynchronisedTransmissionandReception(default)
Atollcalculatestheinterferencebetweentwocellsusingthismethodwhen:
[LTE]
Thefrequencychannelsassignedtotheinterferedandinterferingcellshavethesamecentrefrequency,and
Theinterferedandinterferingcellsbothhaveanevennumberoffrequencyblocksorbothhaveanoddnumber
offrequencyblocks,and
ThefollowingoptionissetintheAtoll.inifile(defaultvalue):
SameItf_PDSCH_RS_PDCCH = 0
Synchronised transmission and reception means that the OFDM symbols of the interfered and interfering frames
overlapandmatcheachotherintime.
Method2:NonsynchronisedTransmissionandReception
Atollcalculatestheinterferencebetweentwocellsusingthismethodwhen:
[LTE]
Thefrequencychannelsassignedtotheinterferedandinterferingcellsdonothavethesamecentrefrequency,or
Theinterferedandinterferingcellsdonotbothhaveanevennumberoffrequencyblocksordonotbothhavean
oddnumberoffrequencyblocks,or
ThefollowingoptionissetintheAtoll.inifile:
ThismethodisalsousedforcalculatingtheinterferencereceivedfromLTEcellsofanexternalnetworkincoplanning
mode,i.e.,intertechnologyinterferencereceivedfromLTEcellscalculatedusingtheintertechnologyIRFs.
Formoreinformation,seetheTechnicalReferenceGuide.
12.1.9.14 SettingPDCCHto100%LoadedinLTEInterferenceCalculations
Bydefault,thedownlinkinterferencecalculatedfromPDSCHandPDCCHisweightedbythedownlinktrafficloadsofthe
interferingcells.IfyouwishtosetthePDCCHto100%loaded,i.e.,onlyweighttheinterferencefromPDSCHbythedownlink
trafficloadandnottheinterferencefromthePDCCH,addthefollowinglinesintheAtoll.inifile:
[LTE]
ApplyDLLoadOnPDCCHInterf = 0
188
AT321_AM_E1
ApplyDLLoadOnPDCCHInterfissetto1bydefault.ThisoptionisonlyrelevantwhenSameItf_PDSCH_RS_PDCCHissetto1.
12.1.9.15 CalculatingEIRPfromRSEPREinLTESignalLevelPredictions
AtollcalculatestheEIRPfromthereferencesignalpowerinLTE.Insignallevelbasedcoveragepredictions,ifyouwishto
calculatetheEIRPfromtheReferenceSignalEPREinstead,addthefollowinglinesintheAtoll.inifile:
[LTE]
EIRPfromRSEPRE = 1
EIRPfromRSEPRE is set to 0 by default. This option applies to Coverage by Transmitter, Coverage by Signal Level, and
OverlappingZonespredictionsinLTE.
12.1.9.16 AveragingtheUplinkNoiseRiseindB
TheaveragesimulationresultsprovidethelinearaverageofuplinknoiserisevaluesdisplayedindB.IfyouwantAtollto
calculatetheaveragebydirectlyusingthenoiserisevaluesindB,addthefollowinglinesintheAtoll.inifile:
[OFDM_SIMU]
MeanNRInDB = 1
MeanNRInDBissetto0bydefault.
12.1.9.17 DeactivatingServiceMaxThroughputDemandDowngradinginLTE
Service maximum throughput demand downgrading is active by default in LTE Monte Carlo simulations. If you wish to
deactivatethisdowngrading,addthefollowinglinesintheAtoll.inifile:
[LTE]
ServiceMBRDowngrading = 0
ServiceMBRDowngradingissetto1bydefault.
12.1.9.18 DisplayingPixelswithZeroThroughputinCoveragePredictions
Inthroughputcoveragepredictions,pixelsarecolouredaccordingtothedefinedthroughputthresholdcoloursifthereare
bearersavailableonthosepixels.Ifyouwishtohaveotherpixels,i.e.,thosewithnoavailablebearerhencezerothroughput,
tobecolouredaswell,addthefollowinglinesintheAtoll.inifile:
[OFDM]
DisplayThroughputZero = 1
DisplayThroughputZeroissetto0bydefault.
12.1.9.19 SettingUplinkNoiseRiseControlParametersinLTE
Thedefaultmethodofuplinknoiserisecontrolisthebesteffortmethod.Thismeansthatuplinknoiserisecontrolisnotpart
ofthesimulationconvergencecriteria.Forbesteffortnoiserisecontrol,youcanmodifythenoiserisecontrolmarginthrough
Atoll.inifilebyaddingthefollowinglines:
[LTE]
NR_CONTROL_MARGIN_MIN = X
PositivevaluesofNR_CONTROL_MARGIN_MINareconsideredasnegativemargins.Forexample,XisinterpretedbyAtollas
X dB.NR_CONTROL_MARGIN_MINissetto1bydefault,interpretedas1 dB.
Ifyouwishtoincludetheuplinknoiserisecontrolinthesimulationconvergencecriteria,youcanchangetheuplinknoiserise
controlmethodfrombestefforttostrictbysettingthefollowingoptionintheAtoll.inifile:
[LTE]
ULNRControlMethod = 1
ULNRControlMethodissetto0bydefault.
Forthestrictnoiserisecontrolmethod,youcanmodifythenoiserisecontrolprecisionlevelthroughtheAtoll.inifilebyadding
thefollowinglines:
189
Forsk2014
[LTE]
ULNRControlPrecision = X
Integer values of ULNRControlPrecision are considered as tenths of dB. For example, X is interpreted by Atoll as 0.X dB.
ULNRControlPrecisionissetto5bydefault,interpretedas0.5 dB.
12.1.9.20 UsingtheABSPatternsThroughoutaCellinLTE
Bydefault,ABSpatternsareusedonlyonthecelledges.ThismeansthatallsubframesareconsiderednonABSsubframesin
thecellcentre.Thismethodenablesyoutoincludethecelledgetrafficratiointhecalculationofinterference.Ifyouwishto
applytheABSpatternsthroughoutthecell,irrespectiveofthecelledgeareaandthecelledgetrafficratio,youcandosoby
[LTE]
UseABSonCellEdgeOnly = 0
Bydefault,UseABSonCellEdgeOnlyissetto1.
12.1.9.21 ApplyingtheABSCollisionProbabilityonInterferencefromRS
Almostblanksubframesdonotcontainanytrafficdata.They,however,containtransmittedreferencesignalsthatgenerate
certain amount of interference. The 3GPP defines further enhanced ICIC (FeICIC) as the possibility for some advanced
receiverstoeliminateinterferencefromreferencesignalsontheABS.Ifyouwishtoeliminateinterferencefromreference
signalstransmittedontheABS,addthefollowinglinesintheAtoll.inifile:
[LTE]
eICICOnRS = 1
Bydefault,eICICOnRSissetto0.
12.1.9.22 EnablingMultieNodeBCarrierAggregation
Bydefault,AtollsupportsintraeNodeBcarrieraggregation.Thismeansthat,Atollonlyselectssecondaryservingcellsfrom
withinthesameeNodeB(belongingtothesamesite)astheselectedprimaryservingcellofanLTEAuser.Ifyouwishto
switchtomultieNodeBcarrieraggregation,youcandosobyaddingthefollowinglinesintheAtoll.inifile:
[LTE]
CAWithinENB = 0
CAWithinENBissetto1bydefault.
12.1.9.23 SwitchingBetweenCarrierAggregationSchedulingMethods
Fortheirmaximumthroughputdemands,LTEAusersarescheduledseparatelyoneachoftheirservingcells,primaryand
secondary. Each users remaining throughput demand (maximum minimum) is distributed over each of its serving cells
proportionallytotheresourcesavailableoneachservingcellandtotheusersdownlinkeffectiveRLCchannelthroughputor
uplinkeffectiveRLCallocatedbandwidththroughputoneachofitsservingcell.Withineachservingcell,resourceallocation
forthemaximumthroughputdemandsiscarriedoutaccordingtotheschedulerusedbythatparticularcell.
Ifyouwishtohaveeachusersremainingthroughputdemand(maximumminimum)distributedovereachofitsservingcells
proportionallyonlytotheresourcesavailableoneachservingcell,addthefollowinglinesintheAtoll.inifile:
[LTE]
CASchedulingMethod = 1
CASchedulingMethodissetto0bydefault.
12.1.10 3GPPMultiRATOptions
12.1.10.1 BSIC,SC,andPCIAllocationwithIntertechnologyNeighbourConstraints
TheautomaticallocationsofBSIC(usingtheGSMAFP),scramblingcodes(inUMTS),andphysicalcellIDs(usingtheLTEAFP)
takeintertechnologyneighbourconstraintsintoaccount.Forexample,differentphysicalcellIDsareassignedtotwoLTEcells
that are neighbours of the same GSM transmitter or UMTS cell. If you wish to disable the intertechnology neighbour
constraintsintheautomaticallocationsofBSIC,SC,andPCI,addthefollowinglinesintheAtoll.inifile:
190
AT321_AM_E1
[MultiRAT]
AllCodesAllocWithInterRATNeighbours = 0
AllCodesAllocWithInterRATNeighboursissetto1bydefault.
12.1.11 MicrowaveRadioLinksOptions
12.1.11.1 UpdatingA>>BandB>>AProfilesinRealtime
IntheMWAnalysiswindowsProfileview,whenachangeismadeontheA>>Blink,itisnotautomaticallytakenintoaccount
intheB>>Adirectioninrealtime.Thisproducesinconsistentresultsinthe2directions.Ifyouwanttomaketheprofileupdate
realtimeinbothdirections,i.e.,changesinonedirectionautomaticallyupdatedintheotherdirection,addthefollowinglines
intheAtoll.inifile:
[MWCalculations]
UpdateOppositeHop = 1
UpdateOppositeHopissetto1bydefault.
12.1.11.2 DisablingShieldingFactoronWantedSignalatReceiver
Ifyouwanttodisabletheuseoftheshieldingfactoronthewantedsignalatthereceiverduringinterferencecalculations,add
[MWCalculations]
ShieldingFactorOnWantedSignal = 0
ShieldingFactorOnWantedSignal is set to 1 by default, which means that the shielding factor is taken into account at the
receiver when calculating interference. On the transmitter side, the shielding factor is always taken into account when
calculatinginterference.
12.1.11.3 MakingtheITURP.5305MethodAvailable
TheRec.ITURP.5305methodishiddenbydefaultontheModelstaboftheMicrowaveRadioLinksPropertiesdialogue.
YoucanmakethismethodavailableforavailabilityandqualitycalculationsbyaddingthefollowinglinesintheAtoll.inifile:
[MWCalculations]
HIDE_REC530_5 = 0
HIDE_REC5is setto1 by default. If the method wasselected in a document savedin a previousAtollversion, itwill be
availableevenifHIDE_REC5issetto1intheAtoll.inifile.
12.1.11.4 DecreasingCalculationTimeofPathProfiles
Whenyoucalculatealinkbudgetorinterferenceforamicrowavelink:
Thepathprofileiscalculatedtwice(A>>BandB>>A)andupto3separateextractionscanbeused:oneforDTM,one
forclutterheights,andoneforclutterclasses.
Anewdirectory,C:\<path_to_doc>\<doc_name>.profiles,iscreated.Itcontainstheexternalfiles(whichincludeall
thecalculatedpathprofiles)thatwillbeusedthenexttimelinkbudgetsorinterferencesneedtoberecalculated.
YoucandisablethisfeaturebysettingthefollowingoptionintheAtoll.inifile:
[MWCalculations]
UseProfilesFiles = 0 # (default=1)
Keep the ATL file on your machine instead of a server to significantly decrease the
calculationtimeofpathprofiles.
This feature is more efficient when the DTM resolution is low, provided that the
calculationresolutionisgreaterthanorequaltothegeodataresolution.
Profilefilesarenotcreatedforlinkswithatleastoneremoteantenna.Theywillnot
beusedeitheriftheywerecreatedbeforeanantennahasbecomeremote.
191
Forsk2014
12.1.11.5 UsingOldMinC/IValues
IfyouwishtouseMinC/IvaluesdefinedorcalculatedinoldversionsofAtoll,addthefollowinglinesintheAtoll.inifile:
[Compatibility]
MWEquipment_CIMIN = 1
MWEquipment_CIMINissetto0bydefault.
12.1.11.6 SolvingAlignmentIssueinGeneratedReports
IfyouencounteranalignmentissueintheMicrowavereportorintheReflectionAnalysisreport,youcansolveitbyincreasing
thetabvalue.Todothat,addthefollowinglinesintheAtoll.inifile:
[MWReport]
tab = 2000 # Default value is 500
12.1.11.7 UsingDefaultMethodforCalculatingUnavailability
When generating an Analysis Report, Atoll calculates the availability (average over a year) using the Crane or the ITU
recommendations:ITURP.5305,ITURP.5308,ITURP.53010,ITURP.53011,ITURP.53012andITURP.53013.Under
Unavailabilityduetorain,however,thevaluesareextrapolatedtogiveamoreaccurateresult.
Thedefaultforoption"RainBelow0001"is"1"whichusesthesameextrapolationmethodasPathloss.Ifdesired,theoption
"RainBelow0001"canbesetto"2"inordertofollowtheAtollextrapolation(asbefore)orto"0",tousenoextrapolationwhen
calculatingunavailabilityduetorain.
[MWReport]
RainBelow0001 = 1 # Default; the same extrapolation method as Pathloss
12.1.11.8 DefiningDefaultConfigurationFilesforLinkBudgetsReports
YoucandefineadefaultconfigurationfileforeachlinkbudgetreportbyspecifyinganabsoluteorUNCpathintheAtoll.inifile:
[MWReport]
DesignSummaryCfg = path to the reports default configuration file
LinkAnalysisCfg = path to the reports default configuration file
LinkInterferenceCfg = path to the reports default configuration file
RequiredMarginCfg = path to the reports default configuration file
LinksBudgetCfg = path to the reports default configuration file
LinksInterferenceCfg = path to the reports default configuration file
MultihopAnalysisCfg = path to the reports default configuration file
ReflectionAnalysisCfg = path to the reports default configuration file
WhereeachoftheaboveoptionscorrespondstoaspecificReportConfigurationdialogue:
192
DesignSummaryCfg:correspondstotheReportConfigurationdialoguedisplayedafterclickingtheConfigureReport
button( )fromtheDesignSummaryview(MWAnalysiswindow).
LinkAnalysisCfg: corresponds to the Report Configuration dialogue displayed after clicking the Configure Report
buttonfromtheAnalysisReportview(MWAnalysiswindow).
LinkInterferenceCfg:correspondstotheReportConfigurationdialoguedisplayedafterclickingtheConfigureReport
buttonfromtheInterferenceReportview(MWAnalysiswindow).
RequiredMarginCfg:correspondstotheReportConfigurationdialoguedisplayedafterclickingtheConfigureReport
buttonfromtheRequiredMarginview(MWAnalysiswindow).
LinksBudgetCfg:correspondstotheReportConfigurationdialoguedisplayedafterselectingMicrowaveRadioLinks
>Links>LinkBudgets>ConfigurationReportfromtheNetworkexplorer.
LinksInterferenceCfg:correspondstotheReportConfigurationdialoguedisplayedafterselectingMicrowaveRadio
Links>Links>Interference>ConfigurationReportfromtheNetworkexplorer.
MultihopAnalysisCfg:correspondstotheReportConfigurationdialoguedisplayedafterselectingMicrowaveRadio
Links>MultiHops>[MultiHopX]>AnalysisfromtheNetworkexplorer.
ReflectionAnalysisCfg:correspondstotheReportConfigurationdialoguedisplayedafter:
rightclickingintheProfileAnalysisview(MWAnalysiswindow)andselectingReflectionandDiversityAnalysis,
thenclickingtheConfigureReportbuttonfromtheAnalysisReportview(MWReflection/Diversitywindow).
AT321_AM_E1
12.1.11.9 DefiningaDefaultConfigurationFilefortheChannelArrangement
Display
YoucandefineadefaultconfigurationfileforthechannelarrangementdisplaybyspecifyinganabsoluteorUNCpathinthe
Atoll.inifile:
[MWChannelArrangement]
DefaultConfiguration = path to the channel arrangement default configuration file
WheretheaboveoptioncorrespondstotheChannelArrangementdialoguedisplayedafterselectingMicrowaveRadioLinks
>Interference>ChannelArrangement>DisplayonMapfromtheNetworkexplorer.
12.1.11.10 DefiningaDefaultTemplateforMicrowaveLinksCustomReports
YoucandefineadefaulttemplateformicrowavelinkscustomreportsbyspecifyinganabsoluteorUNCpathintheAtoll.ini
file:
[MWReport]
DefaultTemplate = path to the default template for microwave links custom reports
12.1.12 MeasurementOptions
12.1.12.1 DisplayingAdditionalInformationinDriveTestData
Itispossibletodisplaythefollowingadditionalinformationinthecolumnsofservingandneighbourcells:
BCCHBSICpair(GSMGPRSEDGEdocuments)
ScramblingCodeScramblingCodeGrouppair(UMTSHSPAdocuments)
PNOffsetPNOffsetGrouppair(CDMA20001xRTT1xEVDOdocuments)
YouhavetoaddthefollowinglinesintheAtoll.inifiletodisplaythisinformation:
[TestMobileData]
ShowCoupleInfo = 1
SettingShowCoupleInfoto0hidesthisinformation.
12.1.12.2 SettingtheNumberofTransmittersperDriveTestDataPath
By default, Atoll can import information about one serving transmitter (or cell in CDMA documents) and six neighbour
transmitters(orcellsinCDMAdocuments)fordrivetestdatapaths.Youcanchangethenumberoftransmittersperdrivetest
datapathbyaddingthefollowinglinesintheAtoll.inifile:
[TestMobileData]
NumberOfTestMobileTransmitters = X
WhereXisthenumberoftransmittersperdrivetestdatapath.ThedefaultvalueofNumberOfTestMobileTransmittersis7.
12.1.12.3 RecalculatingDistancesofPointsFromThereServingCellsatImport
IfyouwantAtolltocalculatethedistanceofeachmeasurementpointfromitsnearestservingcell,youcanaddthefollowing
[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
nearestservingcellistheoneclosesttothemeasurementpointwhichhasthesame(ScramblingCode,SCGroup),(BSIC,
BCCH),or(PNOffset,PNOffsetGroup)pairasthepoint.
12.1.12.4 DefiningtheBCCHandBSICColumnsforFMTImport
The.fmtfilesgeneratedbytheTEMSInvestigationGSMtoolcontainanumberofcolumns.Todefinewhichofthesecolumns
shouldbeimportedastheBCCHcolumnandwhichoneastheBSICcolumninAtoll,youcanaddthefollowinglinesinthe
Atoll.inifile:
193
Forsk2014
[TestMobileDataImportFmt]
BCCHColumn = Column1
BSICColumn = Column2
Where, Column1andColumn2 arethe titles of the twocolumnsin the .fmtfilecorrespondingto the BCCHandthe BSIC
columnsrespectively.
12.1.12.5 ImportingDriveTestDatawithScramblingCodesasIntegers
Youcanforcetheconversionofscramblingcodestointegervalueswhenimportingdrivetestdatabyaddingthefollowing
optionintheAtoll.inifile:
[TestMobileData]
FloatingPointScramblingCodeSupport = 1
FloatingPointScramblingCodeSupportissetto0bydefault,andthescramblingcodesareimportedaccordingtothenumeric
datatypeselectedforthescramblingcodecolumnintheimportdialogue.
12.1.12.6 ImportingDriveTestDataforActiveandFilteredTransmittersOnly
WhenyouimportdrivetestdatainAtoll,itassignsserversandneighbourstoeachmeasurementpointbasedonthecell
identification method defined for the import. By default, Atoll takes all the transmitters and cells of the document into
account,whethertheyareactiveorinactiveandfilteredornot.IfyouwantAtolltotakeonlyactiveandfilteredtransmitters
andcellsintoaccountfordrivetestdataimport,addthefollowingoptionintheAtoll.inifile:
[TestMobileData]
ImportForFilteredTransmittersOnly = 1
ImportForFilteredTransmittersOnlyissetto0bydefault.
12.1.13 ACPOptions
Forthemostpart,youcanconfiguretheACPwithitsowninitialisationfile:theacp.ini.However,thereareafewoptionsthat
youcansetintheAtoll.initoconfiguretheACP.
12.1.13.1 SpecifyingtheLocationoftheAcp.iniFile
Bydefault,AtollACPusestheglobalacp.inifile,locatedintheinstallationdirectoryofAtoll.Youcansetanoptioninthe
Atoll.inifiletodefineadifferentlocationfortheacp.inifile.ThisoptionisusefulforassigningadifferentACPinitialisationfor
adifferentgroupofusers.
Touseanotherlocation,addthefollowinglinetotheAtoll.inifile:
[ACP]
iniFile = /path/to/the/ACP.ini
12.2 ACPInitialisationFile
TheACPinitialisationfileisusedtoinformAtollofthepreferredsettingswhentheACPisusedforautomaticcellplanning
duringAtollsessions.ItcanbeusedtoadjustthebehaviouroftheACP.
Youcancommentoutanyoptionintheacp.inibyprecedingthelinewithasemicolon(";")orwithahashmark("#").
The ACP initialisation file is a powerful tool. You should not modify any option in the
acp.inifileuntilandunlessyouareabsolutelysureofwhatyouaredoing.
InorderfortheACPinitialisationfiletobeusedbyAtoll,youshouldplacetheacp.inifileintheAtollinstallationdirectory.
Youcandefineadifferentlocationfortheacp.inifileasshownin"SpecifyingtheLocationoftheAcp.iniFile"onpage 194:
194
AT321_AM_E1
12.2.1 ManagingPreferences
Someofthesettingsprovidedintheacp.inifilecanbemodifieddirectlyusingtheACPAutomaticCellPlanningProperties
dialogue,underACPAutomaticCellPlanningontheSetupTemplatetab.ACPeitherembedsthesesettingsdirectlyintheATL
documentorinauserdefinedacp.inifile.Thesesettingsarereferredas"localsettings."Localsettingsarethesettingsfound
insectionsusingthe"Tpl"keyword,suchas[ACPTplGeneralPage].
Thelocalsettings,definedusingtheACP AutomaticCellPlanningProperties
dialogue,takeprecedenceoverthesamesettingsdefinedintheglobalacp.ini
file. The settings in the acp.ini file are read when you start a new project to
initialisethesettingsoftheACP.
When using the acp.ini file to define options, instead of using the ACP
Automatic Cell Planning Properties dialogue, you can also define any other
settings even if they can not be set using the ACP Automatic Cell Planning
Propertiesdialogue.Thesesettingsredefinedlocallyhaveprecedenceoverthe
globalsettings.
12.2.2 GUIOptions
InthissectionarethesettingsdefiningdefaultvaluesanddefiningcertainaspectsoftheGUIconfiguration.Thesesettingsare
localandareusuallydefinedusingSetupTemplatetaboftheACP AutomaticCellPlanningPropertiesdialogue,andstored
eitherintheAtollprojectoralocalacp.inifile.
12.2.2.1 DefaultValuesontheOptimisationTab
Inthe[ACPTplGeneralPage]section,youcanfindtheoptionsusedtosetdefaultvaluesfortheOptimisationtab.
Thefollowingoptionscanbeusedtosetdefaultvaluesforthenumberofiterationsandresolution:
[ACPTplGeneralPage]
nbIteration=100
resolution=50
Otheroptionscanbeusedtodefinethedefaultvaluesforcalculatingcost:
cost.type=0 # 0=off, 1=limt_to_max, 2=apply_cost_to_change_plan
;cost.unit=
# here define the optional 'unit' for cost: $, 'yen', etc. Less than 4 characters
cost.tradeoffLevel=1 # 0=low, 1=normal, 2=strong
cost.maxCost=50
cost.azimuth.cost=1
cost.azimuth.isSiteVisit=true
cost.tilt.cost=1
cost.tilt.isSiteVisit=true
cost.antenna.cost=1
cost.antenna.isSiteVisit=true
cost.etilt.cost=0.1
cost.etilt.isSiteVisit=false
cost.height.cost=1
cost.height.isSiteVisit=true
cost.power.cost=0.1
cost.power.isSiteVisit=false
cost.siteVisitCost=2
cost.upgradeSiteCost=5
cost.newSiteCost=10
cost.removeSiteCost=-5
195
Forsk2014
12.2.2.2 DisplayingAdvancedCostOptions
Inthe[ACPGeneralPage]section,youcandefineanoptiontodisplayadvancedcostoptionswhichenabletheusertodefine
themaximumnumberofchangestobemade(eitherasavalueoraratio)andtochangetherankingoftheorderofcostin
the final implementation plan: changes with the lowest cost are performed first and changes with the highest cost are
performedlast.
[ACPGeneralPage]
enableAdvancedCost=0 # "1" to display (default); "0" to hide
Inthe[ACPTplGeneralPage]section,youcandefinedefaultvaluesforadvancedcostcontrol.The"cost.planCostWeighting"
optionenablesyoutodefinetheimportanceofcostintheimplementationplan:
[ACPTplGeneralPage]
cost.planCostWeighting=0 # "0"=low, "1"=medium (default), "2"=high
The"cost.planLimitType"optionenablesyoutolimitthenumberofchangesintheimplementationplan:
[ACPTplGeneralPage]
cost.planLimitType=0 # "0"=no limit (default) "1"=absolute value
# "2"=percent of total antennas in the computation zone
Ifthe"cost.planLimitType"optionissetto"1"(i.e.,anabsolutevalue),thenthe"cost.planChangeMax"optionmustbesetto
definethenumberofchangesintheimplementationplan:
[ACPTplGeneralPage]
cost.planLimitType=1
cost.planChangeMax=10 # In this example, the maximum no. of changes is "10."
Ifthe"cost.planLimitType"optionissetto"2"(i.e.,apercentageofthetotalantennasinthecomputationzone),thenthe
"cost.planChangePercent"optionmustbesettodefinethenumberofchangesintheimplementationplanasapercentage
ofthenumberofantennas:
[ACPTplGeneralPage]
cost.planLimitType=1
cost.planChangePercent=10 # In this example, the maximum no. of changes is "10%"
# of the total number of antennas in the computation zone
Ifthe"cost.planLimitType"optionissetto"2"(i.e.,apercentageofthetotalantennas),theusercanthenusethefocuszone
instead of the computation zone as the reference zone by setting the "cost.planChangRefZone" option in the
[ACPGeneralPage]:
[ACPGeneralPage]
cost.planChangRefZone=1 # Ration computed against computation zone
# (0:Default) or focus zone (1)
12.2.2.3 AutomaticallyCreatingCustomZonesontheOptimisationTab
Inthe[ACPTplGeneralPage]section,youcanfindtheoptionsusedtoautomaticallycreatecustomzonesthatwillappearon
theOptimisationtabwhenyoucreateanewACPsetup.
ThefollowingoptioncanbeusedtoautomaticallycreateACPcustomzonesfromthehotspotsintheAtollproject:
[ACPGeneralPage]
zone.autobuildHotspot=1 # automatically build hotspot from Atoll hotspot (default)
ThefollowingoptionscanbeusedtoautomaticallycreateACPcustomzonesfromoneormoreclutterclassesorfromaSHP
file:
[ACPGeneralPage]
zone.count=2 # The number of zones to be created.
zone.0.name=MyClutterZone1 # The name of the zone (in this case from clutter)
zone.0.clutter=10,11,12 # The clutter classes that will constitute this zone
zone.1.name=MyVectorZone2 # The name of the zone (in this case from SHP)
196
AT321_AM_E1
zone.1.file=c:\path\to\file.shp # Absolute path to the SHP file.
12.2.2.4 DefaultValuesontheObjectivesTab
Inthe[ACPTplObjectivePage]sectionarethesettingsdefiningdefaultvaluesfortheObjectivestab.
Thefollowingoptionisusedtodefinethedefaultvaluefortrafficextractionresolutioninmetres:
[ACPTplObjectivePage]
traffic.extraction.resolution=50 # the traffic extraction resolution, in metres
Thefollowingoptionsareusedtodefinethedefaultvaluesforthetechnologyqualityindicators(UMTSEc/Io,UMTSRSCP,
UMTSoverlap,GSMsignallevel,GSMoverlap,WiMAXCINR,WiMAXC/N,LTEC/N,etc.):
param.gsm.overlap.autoPrediction=yes
param.gsm.overlap.margin=5
param.gsm.overlap.minRxLevel=0 # 0=use defined TRG threshold, other=defined value
param.gsm.bcch.autoPrediction=yes
param.gsm.bcch.isShadowing=no
param.gsm.bcch.cellEdgeCov=0.75
param.umts.overlap.autoPrediction=yes
param.umts.overlap.margin=10
param.umts.overlap.minRxLevel=-120
param.umts.rscp.autoPrediction=yes
param.umts.rscp.isShadowing=no
param.umts.rscp.cellEdgeCov=0.75
param.umts.ecio.autoPrediction=yes
param.umts.ecio.isShadowing=no
param.umts.ecio.cellEdgeCov=0.75
param.cdma.overlap.autoPrediction=yes
param.cdma.overlap.margin=10
param.cdma.overlap.minRxLevel=-120
param.cdma.coverage.autoPrediction=yes
param.cdma.coverage.isShadowing=no
param.cdma.coverage.cellEdgeCov=0.75
param.cdma.ecio.autoPrediction=yes
param.cdma.ecio.isShadowing=no
param.cdma.ecio.cellEdgeCov=0.75
param.wimax.overlap.autoPrediction=yes
param.wimax.overlap.margin=5
param.wimax.overlap.minRxLevel=-105
param.wimax.coverage.autoPrediction=yes
param.wimax.coverage.isShadowing=no
param.wimax.coverage.cellEdgeCov=0.75
param.wimax.cnir.autoPrediction=yes
param.wimax.cnir.isShadowing=no
param.wimax.cnir.cellEdgeCov=0.75
param.wimax.cnir.useFreqBand=1
param.wimax.cnir.useSegmentation=1
197
Forsk2014
param.lte.overlap.autoPrediction=yes
param.lte.overlap.margin=5
param.lte.overlap.minRxLevel=-105
param.lte.coverage.autoPrediction=yes
param.lte.coverage.isShadowing=no
param.lte.coverage.cellEdgeCov=0.75
param.lte.cinr.autoPrediction=yes
param.lte.cnir.isShadowing=no
param.lte.cnir.cellEdgeCov=0.75
param.lte.cnir.useFreqBand=1
param.lte.cnir.useSegmentation=1
Thefollowingoptionsareusedtodefinethedefaultthresholdforeachobjectiverule:
quality.gsm.bcch.threshold= -85
quality.gsm.overlap.threshold=4
quality.umts.rscp.threshold= -85
quality.umts.ecio.threshold= -13
quality.umts.overlap.threshold=4
quality.cdma.rscp.threshold= -85
quality.cdma.ecio.threshold= -13
quality.cdma.overlap.threshold=4
quality.wimax.coverage.threshold= -85
quality.wimax.c.threshold=-85
quality.wimax.cn.threshold=20
quality.wimax.cinr.threshold=10
quality.wimax.overlap.threshold=5
quality.lte.coverage.threshold= -85
quality.lte.c.threshold= -85
quality.lte.cn.threshold=20
quality.lte.rsrp.threshold= -105
quality.lte.cinr.threshold=10
quality.lte.rsrq.threshold= -12
quality.lte.overlap.threshold=5
ThefollowingoptionsareusedtodefinethedefaultobjectivesproposedbytheACP.Allobjectivesdefinedwiththeoption
"auto=yes"areautomaticallycreatedduringanewsetup.Othersareavailableonthecontextmenuusedforcreatingnew
objectives.
Forthesetting"objective.X.conditions.X.operande,"avalueof"0"means"<"(lessthan)
and"1"means">"(greaterthan).
objective.count=14 # The total number of objectives to be defined.
objective.0.name=GSM Coverage # Name of objective "0" defined.
objective.0.conditions.count=1
objective.0.conditions.0.layer=gsm
198
AT321_AM_E1
objective.0.conditions.0.quality=bcch
objective.0.conditions.0.threshold=-85
objective.0.conditions.operande=OR
objective.0.auto=true
objective.0.weight=1
objective.0.targetZone=-1
# -2=compZone, -1=focusZone, or other zone idx
objective.0.target.isAbsoluteCoverage=yes
objective.0.target.absoluteCoverage=90
objective.0.filter.count=0
;; The following objective should be defined separately for each layer
objective.1.name=GSM Cell Dominance # Name of objective "1" defined.
objective.1.conditions.operande=AND
objective.1.conditions.0.quality=overlap
objective.1.conditions.0.operande=1 # "1" means ">" (greater than).
objective.1.conditions.0.threshold=0
objective.1.conditions.1.operande=0 # "0" means "<" (less than)
objective.2.name=UMTS RSCP Coverage # Name of objective "2" defined.
objective.2.conditions.0.layer=umts
objective.2.conditions.0.quality=rscp
objective.3.name=UMTS EcIo # Name of objective "3" defined.
objective.3.conditions.0.quality=ecio
objective.4.name=UMTS Pilot Pollution # Name of objective "4" defined.
objective.4.auto=false
199
objective.5.name=UMTS Soft Handover # Name of objective "5" defined.
objective.5.conditions.0.operande=1 # "1" means ">" (greater than)
objective.5.filters.count=1
objective.5.filters.0.layer=umts
objective.5.filters.0.quality=rscp
objective.5.filters.0.operande=0
objective.5.filters.0.threshold=-95
objective.6.name=WiMAX Preamble Coverage # Name of objective "6" defined.
objective.6.conditions.0.layer=wimax
objective.6.conditions.0.quality=coverage
objective.7.name=WiMAX Preamble CINR # Name of objective "7" defined.
objective.7.conditions.0.layer=wimax
objective.7.conditions.0.quality=cinr
objective.7.conditions.0.operande=1 # "1" means ">" (greater than)
objective.8.name=LTE RS Coverage # Name of objective "8" defined.
objective.8.conditions.0.layer=lte
objective.9.name=LTE RS CINR # Name of objective "9" defined.
objective.9.conditions.0.layer=lte
objective.9.conditions.0.quality=cinr
200
Forsk2014
AT321_AM_E1
objective.10.name=CDMA Coverage # Name of objective "10" defined.
objective.10.conditions.0.layer=cdma
objective.11.name=CDMA EcIo # Name of objective "11" defined.
objective.11.conditions.0.quality=ecio
objective.12.name=CDMA Pilot Pollution # Name of objective "12" defined.
objective.13.name=CDMA Soft Handover # Name of objective "13" defined.
objective.13.conditions.1.operande=0 # "0" means "<" (less than
objective.13.filters.count=1
objective.13.filters.0.layer=cdma
objective.13.filters.0.quality=coverage
objective.13.filters.0.operande=0
objective.13.filters.0.threshold=-95
201
Forsk2014
ThefollowingoptionenablesyoutousetheXORbooleanexpressionwhencreatingobjectives.
[ACPObjectivePage]
combination.XOR.use=0 # disabled by default
ThefollowingoptionisusedtoremovetheCapacityandLoadBalancingfeaturesfromtheObjectivestab:
[ACPCapacityPage]
enable=0 (default=1 => capacity and load balancing enabled)
ThefollowingoptionisusedtocleartheScaleTrafficaccordingtoZoneWeightingcheckboxontheCapacitypageofthe
Objectivestab:
[ACPTplCapacityPage]
useZoneWeight=0 (default=1 => zone weighting applied on capacity traffic)
Thefollowingoptionsareusedtodefineacapacitytrafficmap,eitherbyaBILfileorbyacommaseparatedlistoftrafficmap
names:
traffic.file=c:\tmp\traffic.bil
traffic.maps=User density traffic map; environment map
traffic.resolution=50
Thefollowingoptionsareusedtodefinethedefaultthresholdforeachquality(Objectivestab>Capacitypage>Services
Definitionframe):
quality.gsm.bcch.threshold=-85
quality.umts.rscp.threshold=-85
quality.umts.ecio.threshold=-13
quality.cdma.rscp.threshold=-85
quality.cdma.rscp.threshold=-85
quality.wimax.coverage.threshold=-85
quality.wimax.c.threshold=-85
quality.wimax.cn.threshold=20
quality.wimax.cinr.threshold=10
quality.lte.coverage.threshold=-85
quality.lte.c.threshold=-85
quality.lte.cn.threshold=20
quality.lte.rsrp.threshold=-105
quality.lte.cinr.threshold=10
quality.lte.rsrq.threshold=-12
Thefollowingoptionsareusedtodefinethedefaultqualityusedbyeachtechnologyfortrafficcapturecondition:
service.gsm.condition.quality=bcch
service.umts.condition.quality=rscp
service.cdma.condition.quality=coverage
service.wimax.condition.quality=coverage
service.lte.condition.quality=coverage
service.factor=1.0
202
AT321_AM_E1
service.density=30
Thefollowingoptionisusedtoenabletheloadbalancingfeaturebydefault:
loadBalancing.enable=1 (default setting is 0 => load balancing feature disabled)
Thefollowingoptionisusedtospecifytheloadbalancingdefaulttargetzone:
2=>computationzone
1=>focuszone
0andabove=>indexofcustomzone
loadBalancing.targetZoneIdx=-2
loadBalancing.target=80
loadBalancing.weight=1
12.2.2.5 DefaultValuesontheReconfigurationpage
Inthe[ACPTplReconfPage]sectionarethesettingsdefiningdefaultvaluesfortheReconfigurationpage.
The following options enable you to define the default reconfiguration that will be done: power, antenna, azimuth, or
mechanicaltiltoptimisation.
Whentheoptionsinthissectionaresetto"1",thedefaultreconfigurationoptionisnot
selected.Insteadthereconfigurationoptionisdisabled.
[ACPTplReconfPage]
umts.disablePilotPowerOptimisation=1
umts.disableMaxPowerOptimisation=1
umts.SyncMultiCellPower=1
umts.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm
# around actual value. If 0, use fixed value 37-46
cdma.1xrtt.SyncMultiCellPower=1
cdma.1xevdo.SyncMultiCellPower=1
cdma.1xrtt.disablePilotPowerOptimisation=1
cdma.1xrtt.disableMaxPowerOptimisation=1
cdma.1xevdo.disableMaxPowerOptimisation=1
cdma.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm
gsm.disablePowerOptimisation=1
gsm.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm
wimax.disablePreamblePowerOptimisation=1
wimax.SyncMultiCellPower=1
wimax.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm
lte.disablePowerOptimisation=1
lte.SyncMultiCellPower=1
lte.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm
203
Forsk2014
Thefollowingoptionsareusedtodefinethedefaultreconfigurationthatwillbedoneontransmittersandsites:
[ACPTplReconfPage]
disableAntennaOptimization=1
disableETiltOptimization=1
disableAzimuthOptimization=1
disableMechTiltOptimization=1
disableSiteSelection=1
Thefollowingoptionsareusedtospecifydefaultvaluesforthereconfigurationranges:
[ACPTplReconfPage]
defaultTxAzimuthVariation=20
defaultTxAzimuthStep=5
defaultTxAzimuthMinInterSector=0
defaultTxTiltMin=0
defaultTxTiltMax=5
defaultTxTiltStep=1
defaultTxETiltMin=0
defaultTxETiltMax=10
defaultTxHeightMin=0
defaultTxHeightMax=10
defaultTxHeightStep=5
defaultTxHeightMin.feet=0
defaultTxHeightMax.feet=30
defaultTxHeightStep.feet=15
umts.disablePilotPowerOptimization=0
umts.disableMaxPowerOptimization=0
ThefollowingoptioncanbeusedtodisplayanadditionalconstraintontheTransmitterstaboftheReconfigurationtabthat
willbeappliedtoelectricaltiltchanges.
[ACPReconfPage]
tx.etilt.deltaLimitConstraint.show=1 (default=0)
Whentheoptionaboveissettoone,youcandefinethevariationintheheaderofthenewVariation+column.Thevalue
youenterbesidetheVariation+headerdefinestherangeofelectricaltiltchangeswithrespecttothecurrentelectricaltilt.
Forexample,settingavariationof"4"meansthattheACPcanfindanoptimalelectricaltiltthatis4degreesmoreor4degrees
lessthanthecurrentelectricaltilt.Thepossiblerangeisdisplayedforeachantenna.
Eachcellintheelectricaltiltcolumndisplaysacheckboxenablingtheusertodefinewhethertheconstraintshouldbeused,
and the corresponding absolute limit for the electrical tilt. This constraint is an additional constraint on the electrical tilt
configurationoptions.Thefinalelectricaltiltwillbeallowedwithintheintersectionofthetworangeconstraints.
ThefollowingoptioncanbeusedtodefineadefaultvaluefortheVariation+headermentionedabove:
[ACPTplReconfPage]
etilt.deltaLimitConstraint=4 (default=0)
Thefollowingoptionisusedtoautomaticallydisablereconfigurationofalldonors(possiblyincascade)ofarepeater:
[ACPTplReconfPage]
autoLockDonor=0
Thepossiblevaluesare:
204
"0",noautolock(thedefaultvalue)
"1",theUsecheckboxesfortransmitterreconfigurationparametersarecleared(antenna,tilt,azimuth,andheight).
Only the last repeater in a series of cascading repeaters is optimised; the rest are cleared by default (but can be
selectedmanually).
AT321_AM_E1
"2",theUsecheckboxesforallreconfigurationparametersarecleared(antenna,tilt,azimuth,height,andpower).
Only the last repeater in a series of cascading repeaters is optimised; the rest are cleared by default (but can be
selectedmanually).
"5",thesameasoption"1",exceptthattheUsecheckboxescannotbeselectedintheuserinterface.
"6",thesameasoption"2",exceptthattheUsecheckboxescannotbeselectedintheuserinterface.
12.2.2.6 DefaultValuesonSitestabofReconfigurationpage
Inthe[ACPTplReconfPage]sectionarethesettingsdefiningdefaultvaluesfortheSitestaboftheReconfigurationpage.
Thefollowingoptionsenableyoutodefinethereconfigurationoptionsthatareselectedbydefault:siteorsectorremovable,
or antenna azimuth or height. The settings of "defaultSiteCellsRemoveable", "defaultSiteRemoveable", and
"defaultSiteHeightLocked"alsodefinethedefaultsettingsforStationTemplateReconfigurationdialogue.
Whentheoptionsinthissectionaresetto"1",thecorrespondingreconfigurationoption
isselectedbydefault.
[ACPTplReconfPage]
# Specify the default values for the site selection
defaultSiteCellsRemoveable=0 # "0" means Sectors removable not selected by default.
defaultSiteRemoveable=1 # "0" means Site removable not selected by default.
defaultSiteAzimuthLocked=0 # "0" means Lock Sector/Azimuth not selected by default.
defaultSiteHeightLocked=1 # "0" means Lock Sector/height not selected by default.
# "defaultSiteHeightLocked" is forced to false ("0") for sites that have antennas
# at different heights
defaultSiteReconfigurationLocked=0 # "0" means that the default value for the Disable
reconfiguration option is not selected by default.
12.2.2.7 CustomColumnsonSitestabofReconfigurationpage
ThefollowingoptionscanbeusedtodefinethenumberofcustomcolumnstodisplayontheSitestaboftheReconfiguration
page:
[ACPReconfPage]
site.custom.count=x
site.custom.1.type=tabularDataColumn
site.custom.1.column=FOO
Where tabularDataColumn displays data issued from Atolls SITES table and identified by site.custom.1.column (column
name).Atollcolumnnamesarecasesensitive.
Theoptionbelowdefinesanoptionallabelforagivencolumn.Ifunset,theAtollcolumnnameisused(e.g."FOO"):
site.custom.1.label=The Foo Label
12.2.2.8 DefaultValuesontheTransmittersTaboftheReconfigurationPage
Inthe[ACPReconfPage]sectionarethesettingsdefiningdefaultvaluesforthedisplayofmechanicalandelectricaltilts,and
forthedisplayoflinkedtransmitters.
Thefollowingoptionsareusedtodisplaythemechanicalandelectricaltiltsasrelativevaluesinsteadofabsolutevalues.Asa
result,theMin.andMax.columnswillberenamedtoMin.Offset.andMax.Offset.
[ACPReconfPage]
tx.tilt.asRelative=1 (default=0)
tx.etilt.asRelative=1 (default=0)
The following option is used to display the minimum and maximum electrical tilts only once for each group of linked
transmitters,whentheAdvancedmodeisselectedfordisplay.
[ACPReconfPage]
tx.etilt.groupMinMax=1 (default=1)
205
Forsk2014
When"tx.etilt.groupMinMax"issetto0,themin/maxelectricaltiltsaredisplayedforeachtransmitter.
12.2.2.9 CustomColumnsonTransmitters/RemotestabsofReconfigurationpage
The following option can be used to define the number of custom columns to display on the Transmitters tab of the
Reconfigurationpage:
[ACPReconfPage]
tx.custom.count=x
Theoptionsbelowallowyoutospecifythedatayouwanttoshowundereachcustomcolumn.
tx.custom.x.type=elevation
tx.custom.x.type=bandwidth
tx.custom.x.type=tabularDataColumn
Where:
elevationdisplaysthetransmitterelevation(sitealtitudeplustransmitterheight).
bandwidthdisplaysthecellbandwidth(onlyforLTE,WiMAX,andWiFi).
tabularDataColumn displays data issued from Atolls TRANSMITTERS table and identified by tx.custom.x.column
(columnname).
Atollcolumnnamesarecasesensitive:
tx.custom.x.column=FOO
Theoptionbelowdefinesanoptionallabelforagivencolumn.Ifunset,theAtollcolumnnameisused(e.g."FOO"):
tx.custom.x.label=OptionalFooLabel
12.2.2.10 DefaultValuesonthePatternstaboftheAntennaTab
In the [ACPAntennaPage] section are the settings defining default values for the display of additional constraints on
mechanicalandelectricaltiltvalues.Thefollowingoptionsareusedtodisplaytheseadditionalconstraints:
[ACPReconfPage]
enableMTilt=1 # (default=0)
enableETilt=1 # (default=0)
12.2.2.11 DefaultValuesforEMFExposure
Inthe[ACPTplEMFPage]sectionarethesettingsdefiningdefaultvaluesfortheEMFExposuresectionoftheOptimisationtab.
ThefollowingoptionisusedtoenabletheEMFexposuremodule:
[ACPTplEMFPage]
enable=1
Theoption"weightLevel"enablesyoutodefinethelevelofimportanceaccordedtotheoptimisationofEMFexposure.Thre
arethreepossiblevalues:
0:Low:EMFexposureisoptimisedonlyifdoesnotworsencoveragequality.
1:normal:ThereisatradeoffbetweenEMFexposureandcoveragequality(default).
2:critical:EMFexposureisoptimisedindependentlyoftheeffectitmighthaveoncoveragequality.
weightLevel=1 # 0=low, 1=normal, 2=critical
ThefollowingoptionsenableyoutodefinethedefaultresolutioninmetresintheX,Y,andZplanes:
resolutionXY=5
resolutionZ=3
ThefollowingoptionsdefinehowEMFexposurewillbemeasuredinbuildings:onlyonthefacadeorinsidethebuildingas
well:
206
AT321_AM_E1
onlyFacade=1 # Measurement only on facade in building propagation classes.

# Default = 1 (yes)
buildingDeeping=10 # if "onlyFacade" is set to 0, the depth in the building measured.
Thefollowingoptiondefineswhetherclutterclassesandclutterheightsareusedtocreatea3Drepresentationoftheterrain
orwhetherjustvectorsaretobeused.Thedefaultis"1"(yes),but,giventhatvectorsarealwaysgivenprioritywherethey
exist,thisoptioncanbedisabledifvectorsareavailablefortheentireareaofinterest.
useDhmFromClutter=1 # Default is "1" (yes)
Thefollowingoptiondefineswhetherthe3Dpropagationmodelisusingdiffraction.Whenitisnot,onlypositionswithadirect
LOStotransmitterswillregisterEMFexposure.
useDiffraction=0
ThefollowingoptiondefineswhethertheEMFmoduleshouldusetransparentmode.Whentransparentmodeisused,no
obstacleorindoorlossisaccountedfor.
isWorstCase=0 # Default is "0" (no)
Thefollowingoptiondefinesthecalculationradius(inmetres)aroundtransmitterswhencalculatingEMFexposure:
calculationRadius=300
ThefollowingoptionsdefinethedefaultthresholdandweightfortheEMFexposureobjective:
defaultObjThreshold=0.6
defaultObjWeight=1
Thefollowingoptionsenableyoutodefineupto16propagationclassesforEMFexposure.Eachclassisdefinedbyaname,
anindoorloss,andwhetheritcanbeeditedbytheuser.
eclass.count=2 # The total number of propagation classes defined.
eclass.0.name=Open
eclass.0.position=0 # Distribution of measurement points:
# 0=3D, i.e., distribution at all heights over area, 1=2D on top, 2=2D on bottom
eclass.0.buildingLos=0
eclass.0.linearBuildingLos=0
eclass.0.linearBuildingStart=0
eclass.0.editionFlag=0 # 0 can not be edited by user
Thefollowingoptionsenableyoutomapclutterclassestopropagationclasses.Eachmappingisdefinedontwolines:thefirst
linedefinestheclutterclass(byitscodefromtheDescriptiontaboftheClutterClassesPropertiesdialogue);thesecondline
definesthepropagationclass(byitsIDunderPropagationontheOptimisationtaboftheACPSetupdialogue).Thedefault
propagationclassesintheACPare"Open"(ID"0"),"Vegetation"(ID"1"),and"Building"(ID"2").Anyadditionalpropagation
classeswillhaveanIDassignedwhentheyarecreated.
clutterMapping.count=3
clutterMapping.0.clutterCode=10
clutterMapping.0.classCode=0
Inthe[ACPEMFPage]section,youcanspecifywhetherornotuserscandefinenewpropagationclasses:
[ACPEMFPage]
isPropClassesExtendable=1 # "1" enables user to create propagation classes.
207
Forsk2014
12.2.2.12 ControllingAntennaPatternSmoothing
Crosswave version 4.0.4 has introduced the "AntennaLossesThreshold" option to control the smoothing performed on
antennapatternsingaincalculations.AsimilaroptionhasbeenintroducedinAtollACPforcompliancewithCrosswaveresults.
When"AntennaLossesThreshold"isspecifiedintheCrosswave.inifile,thefollowinglinesmustbeincludedinACP.ini:
[ACPGenericPM]
cw.antennaLossesThreshold = X
where X is a value between 0 and 500 specified by "AntennaLossesThreshold" in Crosswave.ini to increase the specific
thresholdappliedbyCrosswave.
12.2.2.13 DefaultValuesontheAntennasTab
Inthe[ACPAntennaPage]sectionarethesettingsdefiningdefaultvaluesfortheAntennastab.
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=(.*)_
Bysettingthefollowingoptionto"1"(default),ACPwillautomaticallyapplythedefaultantennaconfigurationeachtimea
newsetupiscreated(i.e.,theconfigurationwhichhavehavebeenbackedupbyauser):
autoRestoreDefaultConfig=1
Bysettingthefollowingoptionto"1",youenabletheuseofAEDT(additionalelectricaltilt)formanagingdifferentelectrical
tiltoneachantennapattern:
enableAedt=1
By setting the following option, you can control the internal logic that ACP uses to assign different antenna patterns to
differentfrequencybands.ACPconsidersthatanantennapatternisallowedforagivenfrequencybandifitsbasefrequency
iswithintheallowedrange(inMHz):
freqBandRange=99
12.2.2.14 DefiningtheAntennaMaskingModel
Inthe[ACPAntMaskModelPage]section,youcanfindtheoptionsusedtosetthechoicesavailableunderAntennaMasking
MethodontheSetupTemplatetaboftheACP AutomaticCellPlanningPropertiesdialogue.
You can use the "advancedUI" option to display a column called Delegate Calculation to Model. Using the Delegate
CalculationtoModelcolumn,youcandefinewhethertheACPcalculatesthepathlossmatricesoranglesofincidenceused
in antenna masking or whether it delegates calculation to the propagation model (providing the propagation model
implementstheappropriatemethodsofAtollsAPI).Delegatingcalculationtothepropagationmodelprovidesmoreaccurate
resultsbutmighttakelonger.Additionally,itwillusediskspacetostorethecalculationresults.
[ACPAntMaskModelPage]
advancedUI=1 # The default is "0"; the "Delegate Calculation to Model"
# feature is disabled.
Thefollowingoptioncanbeusedtoallow"Optimised"propagationmodels(i.e.,propagationmodelsthatusethe"Optimised"
mode)touse"FullPathLoss"mode:
nativeAllowFullPathLoss=1 # The default is "0"; the feature is disabled.
12.2.2.15 DefiningMultiStoreyOptions
Inthe[ACPGeneralPage]section,youcandefineanoptiontodisplaythemultistoreymodule.Oncedisplayed,theusercan
stillchoosetonotmakeamultistoryoptimisation;the"enable3dMode"onlygovernsthedisplayofthemodule.
[ACPAntMaskModelPage]
enable3dMode=1 # The default is "1"; Setting the option to "0" hides the module.
208
AT321_AM_E1
12.2.2.16 DefiningReconfigurationValuesinCustomAtollFields
Inthe[ACPCustomFieldExtraction]section,youcansetoptionsthatwillenableACPtoextractdatafromcustomfieldsfrom
tablesintheAtolldatabase.ACPwillextractthevaluesenteredinthecustomfieldsandusethemasdefaultreconfiguration
valueswhenanewoptimisationsetupiscreated.ThevaluesextractedcanbeupdatedintheACPsetup,butACPwillnot
updatetheAtolltableswiththenewvalues.
Ifavalueisundefinedinacustomfieldforacell,ACPwillusethedefaultvalueforthat
parameter.
12.2.2.16.1
DefiningReconfigurationValuesforTransmittersandRepeatersUsingCustomAtollFields
theTransmittersandRepeaterstablesintheAtolldatabase.ThecustomcolumnsintheTransmittersorRepeaterstables
mustmatchthecolumnnamedefinedintheacp.inifile.Bydefault,theACPdoesnotextractcustomfields.
[ACPCustomFieldExtraction]
# The name of the custom column in Transmitters and Repeaters table use to
# initialize the reconfiguration parameter for each transmitter or repeater.
tx.antenna.optimize=acp_ant_use
# Best to define this column as a Boolean
tx.antenna.group=acp_ant_group
tx.etilt.optimize=acp_etilt_use
tx.etilt.min=acp_etilt_min
tx.etilt.max=acp_etilt_max
tx.tilt.optimize=acp_tilt_use
tx.tilt.min=acp_tilt_min
tx.tilt.max=acp_tilt_max
tx.tilt.step=acp_tilt_step
tx.azimuth.optimize=acp_azim_use # relative values from current azimuth
tx.azimuth.deltamin=acp_azim_deltamin
tx.azimuth.deltamax=acp_azim_deltamax
tx.azimuth.min=acp_azim_min # absolute value for azimuth angle
tx.azimuth.max=acp_azim_max
tx.azimuth.step=acp_azim_step
tx.azimuth.minInterSector=acp_azim_inter
tx.height.optimize=acp_height_use
tx.height.deltamin=acp_height_deltamin # relative values from current height
tx.height.deltamax=acp_height_deltamax
tx.height.min=acp_height_min # absolute value for height values
tx.height.max=acp_height_max
tx.height.step=acp_height_step
tx.gsm.power.optimize=acp_gsmpower_use
tx.gsm.power.min=acp_gsmpower_min
tx.gsm.power.max=acp_gsmpower_max
tx.gsm.power.step=acp_gsmpower_step
repeater.gain.optimize=acp_gain_use
repeater.gain.min=acp_gain_min
repeater.gain.max=acp_gain_max
repeater.gain.step=acp_gain_step
209
Forsk2014
Somereconfigurationparameterssuchasheightandazimuthcanbedefinedeitheras
relativevalues(i.e.,bydefiningthereconfigurationrangestartingfromthecurrentvalue)
orasabsolutevalues.Youthereforeonlyneedtodefinethesettingsrelevanttothevalue
type(i.e.,relativeorabsolute).
12.2.2.16.2
DefiningReconfigurationValuesforSecondaryAntennasUsingCustomAtollFields
theSecondaryAntennastableintheAtolldatabase.ThecustomcolumnsintheSecondaryAntennastablemustmatchthe
columnnamesdefinedintheacp.inifile.Bydefault,theACPdoesnotextractcustomfields.Howeve,ifthecustomcolumns
are defined using these options and the column exists in the secondary antenna table, the reconfiguration items are
automaticallyconfiguredusingthesevalues(insteadofusingthevaluesdefinedatthetransmitterlevel).
# The name of the custom column in Secondary Antenna table use to
# initialize the reconfiguration parameter for each transmitter or repeater.
tx.antenna.optimise=acp_ant_use # Best to define this column as a Boolean
tx.antenna.group=acp_ant_group
tx.etilt.optimize=acp_etilt_use
tx.etilt.min=acp_etilt_min
tx.etilt.max=acp_etilt_max
tx.tilt.optimize=acp_tilt_use
tx.tilt.min=acp_tilt_min
tx.tilt.max=acp_tilt_max
tx.tilt.step=acp_tilt_step
tx.azimuth.optimize=acp_azim_use # relative values from current azimuth
tx.azimuth.deltamin=acp_azim_deltamin
tx.azimuth.deltamax=acp_azim_deltamax
tx.azimuth.min=acp_azim_min # absolute value for azimuth angle
tx.azimuth.max=acp_azim_max
tx.azimuth.step=acp_azim_step
tx.azimuth.minInterSector=acp_azim_inter
Somereconfigurationparameterssuchasheightandazimuthcanbedefinedeitheras
relativevalues(i.e.,bydefiningthereconfigurationrangestartingfromthecurrentvalue)
orasabsolutevalues.Youthereforeonlyneedtodefinethesettingsrelevanttothevalue
type(i.e.,relativeorabsolute).
12.2.2.16.3
DefiningReconfigurationValuesforCellsUsingCustomAtollFields
theCellstableintheAtolldatabase.ThecustomcolumnsintheCellstablemustmatchthecolumnnamesdefinedinacp.ini
file.
ThefollowingoptionscanbeusedtodefinethecustomcolumnsintheCdmaCellstable.Bydefault,theACPdoesnotextract
customfields.
ccell.pilotPower.optimize=acp_pilotpower_use
ccell.pilotPower.min=acp_pilotpower_min
ccell.pilotPower.max=acp_pilotpower_max
ccell.pilotPower.step=acp_pilotpower_step
ccell.maxPower.optimize=acp_maxpower_use
ccell.maxPower.min=acp_maxpower_min
ccell.maxPower.max=acp_maxpower_max
ccell.maxPower.step=acp_maxpower_step
210
AT321_AM_E1
The following options can be used to define the custom columns in the WCells table. These will be used for default
reconfigurationoptionsforWiMAXcells.Bydefault,thevalueofeachisundefined;thereforethefieldwillnotbeextracted.
wcell.power.optimize=acp_power_use
wcell.power.min=acp_power_min
wcell.power.max=acp_power_max
wcell.power.step=acp_power_step
The following options can be used to define the custom columns in the T4GCells table. These will be used for default
reconfigurationoptionsforLTEcells.Bydefault,thevalueofeachisundefined;thereforethefieldwillnotbeextracted.
lcell.power.optimize=acp_power_use
lcell.power.min=acp_power_min
lcell.power.max=acp_power_max
lcell.power.step=acp_power_step
12.2.2.16.4
DefiningReconfigurationValuesforSitesUsingCustomAtollFields
SitestableintheAtolldatabase.ThecustomcolumnsintheSitestablemustmatchthecolumnnamedefinedbythesettings
intheacp.inifile:
Statusofsites:Byusingthe"site.status"optiontodefinethenameofthecustomstatuscolumnintheSitestable,
youcanextractthestatus(candidateorexisting)ofsitesforsiteselection.AllsitesintheSitestablewiththelabelset
totheonedefinedbythe"site.status.candidate"optionwillbeautomaticallysetascandidatesites.Anysiteswitha
labelotherthantheonedefinedbythe"site.status.candidate"optionwillbeconsideredasexistingsites.Bydefault,
allactivesitesareconsideredasexistingsites.
site.status=acp_site_status # Name of the custom column in Sites table.
# Default value is 'ACP_STATUS'.
site.gsm.status=acp_site_gsm_status
site.umts.status=acp_site_umts_status
site.lte.status=acp_site_lte_status
site.status.candidate=candidate # Name used to define a candidate site.
ThefollowingoptionscanbeusedtodefinecustomcolumnsintheSitestable.Thesewillbeusedfordefaultreconfiguration
optionsforeachsite.
site.disableSelection=acp_site_disableSelection
site.gsm.disableSelection=acp_site_gsm_disableSelection
site.umts.disableSelection=acp_site_umts_disableSelection
site.lte.disableSelection=acp_site_lte_disableSelection
site.removeable=acp_site_removeable
site.gsm.removeable=acp_site_gsm_removeable
site.umts.removeable=acp_site_umts_removeable
site.lte.removeable=acp_site_lte_removeable
site.sectorsRemoveable=acp_site_sectorsRemoveable
site.gsm.sectorsRemoveable=acp_gsm_site_sectorsRemoveable
site.umts.sectorsRemoveable=acp_umts_site_sectorsRemoveable
site.lte.sectorsRemoveable=acp_lte_site_sectorsRemoveable
site.azimLocked=acp_site_azimLocked
site.heightLocked=acp_site_heightLocked
211
Forsk2014
Thefollowingoptioncanbeusedtomanagethedisablereconfigurationattribute.
site.reconfLocked=acp_site_reconfLocked
12.2.2.16.5
DefiningReconfigurationValuesforAntennasUsingCustomAtollFields
AntennastableintheAtolldatabase.ACPcanusetheinformationinthecustomfieldstogroupantennasandtosetdefault
reconfigurationvalueswhenanewoptimisationsetupiscreated.ThecustomcolumnintheAntennastablemustmatchthe
columnnamesdefinedintheacp.inifile.
ThefollowingoptioncanbeusedtonamethecustomcolumnintheAntennastabletogroupantennapatternsintogroups
ofphysicalantennas(i.e.,allpatternsrelatedtothesamephysicalantenna)andgroupthephysicalantennasatdifferent
frequenciesintoradomesbyusingthe"antenna.model"option.Usingthe"antenna.model"enablesyoutoautomatically
formamultibandantenna.TheantennamodelisbydefaultsettothePHYSICAL_ANTENNAcolumnoftheAntennastable.
Hencebydefaulttheautoantennagroupingisalwaysenabledifantennapatternsarecorrectlyassignedtophysicalantennas.
antenna.model=PHYSICAL_ANTENNA
Ifthephysicalantennahasbeendefinedusingthe"antenna.model"option,thefollowingoptioncanbeusedtonamethe
customcolumnintheAntennastablethatisusedtodefineantennagroups.InthecustomcolumnintheAntennastable,all
antennapatternscorrespondingtophysicalantennabelongingtothesamegroupareidentifiedwithauniquestring.TheACP
automaticallygroupsallphysicalantennaintoanewgroupwiththenamegivenbythestringusedinthecolumn.
antenna.group.model=acp_group_model
ThefollowingoptionscanbeusedtonamethecustomcolumnsintheAntennastabletoautomaticallydefinethemechanical
tiltoptions.
# The name of the custom column in ANTENNA table of type 'bool', defining
# which antenna pattern is associated with a 'mechanical tilt constraint'
antenna.tilt.use=ACP_TILT_USE
# The name of the custom columns in ANTENNA table of type 'string' or numeric,
# defining the mechanical tilt allowed range. Non-valid values are treated as
# "forbidden"
antenna.tilt.min=ACP_TILT_MIN
antenna.tilt.max=ACP_TILT_MAX
ThefollowingoptioncanbeusedtonamethecustomcolumnintheAntennastabletoautomaticallylinkantennaelements
of a multiband physical antenna which have the same electrical tilt. In the ACP Setup dialogue, this is accomplished by
selectingthecheckboxintheSameElec.Tiltcolumn.The"antenna.etilt.share"optionshouldcontainalistofthespace
separatedfrequenciesforwhichthecorrespondingphysicalantennamustbelinked(i.e.,physicalantennathatalwaysuses
sameelectricaltilt).
antenna.etilt.share=ACP_ETILT_SHARE
ThefollowingoptionscanbeusedtonamethecustomcolumnsintheAntennastabletoautomaticallydefinetheelectrical
tiltoptions.
Tooptimisetheelectricaltilt,firstsetthe"enableAedt"and"enableETilt"optionsto"1"
toactivatethem.
# The name of the custom column in ANTENNA table of type 'bool', defining
# which antenna pattern is associated with an 'electrical tilt constraint'
antenna.etilt.use=ACP_ETILT_USE
212
AT321_AM_E1
# The name of the custom columns in ANTENNA table of type 'string' or numeric,
# defining the AEDT and e-tilt allowed range. Non-valid values are treated as
# "forbidden"
antenna.etilt.min=ACP_ETILT_MIN
antenna.etilt.max=ACP_ETILT_MAX
12.2.2.17 DefiningSiteClassOptions
YoucansetoptionsintheACP.inifiletodefinesiteclassesintheACP.Youcanbothdefinesiteclassesthatautomatically
appearintheACPSetupdialogueandsetoptionsintheACP.inisothattheACPappliessiteclassesbasedonoptionaldatain
theAtolldatabase.
12.2.2.17.1
DefiningAutomaticSiteClasses
Inthe[ACPGeneralPage]section,youcanfindtheoptionusedtodefinethewhetherthesiteclassfeatureappears.
Thefollowingoptioncanbeusedtoshoworhidethesiteclassfeatureandsetthenumberofsiteclassesdefined:
[ACPGeneralPage]
cost.classes.showUI=1 # The default is "1"; the site class feature is enabled.
cost.classes.count=1 # Number of defined classes
Inthe[ACPTplGeneralPage]section,youcandefinethedefaultvalueswhenthesiteclassoptionisavailable.Thesesettings
arelocalsettings.
[ACPTplGeneralPage]
cost.classes.count=1 # Number of defined classes
YoucanthendefinethesiteclassesthatwillappeareachtimeanewACPoptimisationiscreatedalongwithpredefinedcosts.
ThenameofeachclassasitappearsintheACPisdefinedbyanoptioncalled"cost.classes.X.name"where"X"isasequential
number.Thecorrespondingsettingsfortheclassdefinedin"cost.classes.X.name"aredefinedusingthefollowingoptions:
cost.classes.X.azimuth.cost:Thiskeyisusedtodefinethecostofchangingtheantennaazimuth.
cost.classes.X.azimuth.isSiteVisit:Thiskeyissetto"true"ifthiscostentailsasitevisit;"false"ifitdoesnot.
cost.classes.X.tilt.cost:Thiskeyisusedtodefinethecostofchangingthemechanicaltiltoftheantenna.
cost.classes.X.tilt.isSiteVisit:Thiskeyissetto"true"ifthiscostentailsasitevisit;"false"ifitdoesnot.
cost.classes.X.antenna.cost:Thiskeyisusedtodefinethecostofchangingthetypeoftheantenna.
cost.classes.X.antenna.isSiteVisit:Thiskeyissetto"true"ifthiscostentailsasitevisit;"false"ifitdoesnot.
cost.classes.X.etilt.cost:Thiskeyisusedtodefinethecostofchangingtheelectricaltiltoftheantenna.
cost.classes.X.etilt.isSiteVisit:Thiskeyissetto"true"ifthiscostentailsasitevisit;"false"ifitdoesnot.
cost.classes.X.height.cost:Thiskeyisusedtodefinethecostofchangingtheantennaheight.
cost.classes.X.height.isSiteVisit:Thiskeyissetto"true"ifthiscostentailsasitevisit;"false"ifitdoesnot.
cost.classes.X.power.cost:Thiskeyisusedtodefinethecostofchangingthepower.
cost.classes.X.power.isSiteVisit:Thiskeyissetto"true"ifthiscostentailsasitevisit;"false"ifitdoesnot.
cost.classes.X.siteVisitCost:Thiskeyisusedtodefinethecostofasitevisit.
cost.classes.X.upgradeSiteCost:Thiskeyisusedtodefinethecostofupgradinganexistingsite.
cost.classes.X.newSiteCost:Thiskeyisusedtodefinethecostofcreatinganewsite.
cost.classes.X.removeSiteCost:Thiskeyisusedtodefinethecostofremovinganexistingsite.
Thefollowingisanexampleofthekeysforthefirstsiteclass(numbered"0")called"Planned"inthisexample.
cost.classes.0.name=Planned
cost.classes.0.azimuth.cost=1
cost.classes.0.azimuth.isSiteVisit=true
cost.classes.0.tilt.cost=1
cost.classes.0.tilt.isSiteVisit=true
cost.classes.0.antenna.cost=1
cost.classes.0.antenna.isSiteVisit=true
cost.classes.0.etilt.cost=0.1
cost.classes.0.etilt.isSiteVisit=false
cost.classes.0.height.cost=1
cost.classes.0.height.isSiteVisit=true
cost.classes.0.power.cost=0.1
213
Forsk2014
cost.classes.0.power.isSiteVisit=false
cost.classes.0.siteVisitCost=2
cost.classes.0.upgradeSiteCost=5
cost.classes.0.newSiteCost=10
cost.classes.0.removeSiteCost=-5
12.2.2.17.2
AutomaticAssignmentofSiteClassesintheACP
In the [ACPCustomFieldExtraction] section, you can define the custom field in the Sites table of the Atoll database that
identifiesthesiteclassofeachsite.
YoumustfirstcreatethecorrespondingcustomcolumnintheSitestableoftheAtoll
databaseandassignasiteclasstoeachsiteinthiscolumnforthisoptiontohaveeffect.
site.costClass=[name of custom field in Site table]
ThesiteclassdefinedintheSitestablewillbeassignedautomaticallywhenanACPoptimisationisdefined.Fornewcandidate
siteswhicharelocatedonanexistingsite,thesiteclassisthesameasthesiteonwhichthenewcandidateislocated.Fornew
candidatesiteswhicharenotcolocatedonanexistingsite,thesiteclassissetto"Default"andcanbechangedmanually.
Bydefiningthecostsofeachsiteclassasexplainedin"DefiningAutomaticSiteClasses"onpage 213,thecoststructureis
automaticallydefinedaswell.
12.2.2.18 DefiningtheAppearanceoftheOptimisationDialogBoxDuringaRun
In the [ACPMapDefault] and [ACPMapPage] sections are the settings you can use to define the appearance of the
Optimisationdialogboxduringarun.SomeoptionsrefertotheQualitytabandotherstotheGraphstab.
12.2.2.18.1
DefiningtheColoursintheAnalysisMapsontheQualityTab
ThefollowingsettingscanbeusedtodefinethecoloursintheanalysismapsontheQualitytab.
Therearetwopossibleformatsfordefiningtherangeofcoloursonmaps:
1. Detailedformat:Thedetailedformatenablesyoutosetanonuniformrange.Thenumberofrangesisdefinedand,
foreachrange,theminimumandmaximumvalueoftherangefollowedbyitsRGBcolorrepresentation.
[ACPMapDefault]
colormap.<techno>.<quality>.nbRange=8 # Number of ranges to be defined
colormap.<techno>.<quality>.range.0=[-99999.000000 -15.000000] RGB(0 0 255)
colormap.<techno>.<quality>.range.7=[-3.000000 99999.000000] RGB(255 0 0)
2. Uniformformatdescription:Auniformformatdescriptionusingarangeandstep,inoneofthefollowingintervals:
[firstBreakstartcolor][lastBreakendColor]
INF[firstBreakstartcolor][lastBreakendColor]
whereintervalstartsfromminusinfinitetoenglobealllowervaluesandavoidtransparentpixelsforlowervalues.
[ACPMapDefault]
colormap.<techno>.<quality>.rangeDefinition=[-5 RGB(255 0 0)] [-20 RGB(0 0 255)] -5
colormap.<techno>.<qual>.rangeDefinition=-INF[-5 RGB(255 0 0)] [-20 RGB(0 0 255)] -5
Thesecolormapdescriptionsareusedfordefaultcolormapandcaneasilybechangedbytheuser.Thesettingsarethesame
forthevariousqualityindicatorofthevarioustechnologies,whereyoureplace:
214
<techno>with:umts,gsm,lte,wimax,cdma
AT321_AM_E1
<quality>with:
InGSM:sl,slgain,
InUMTS:ecio,ec,ecgain,eciogain,ecnt,ecntgain
InLTE:sl,slC,slCN,rsrp,cinr,rsrq,slgain,cinrgain,rssi
InWiMAX:sl,slC,slCN,cinr,slgain,cinrgain
Inaddition,anumberofothercolormapscanbedefinedforothertypesofmaps:
12.2.2.18.2
colormap.overlapandcolormap.overlapgainforoverlapmaps
colormap.objectiveandcolormap.objective.gainforobjectivestatusmaps
colormap.bestcell.ttiltandcolormap.change.ttiltforcombinedelectrical/mechanicaltiltmaps
andafewothersforchangemaps,emfmaps,etc.Thedefaultacp.inifileinstalledwiththeACPhasacompletelist
OtherComponentsoftheOptimisationDialogBox
ThefollowingoptionscanbeusedtodefineothercomponentsoftheOptimisationdialogboxduringarun.
BelowarethedefaultcolourcodesfortheforegroundandbackgroundontheQualitytab,withtheRGBcodeasaninteger:
[ACPMapPage]
config.foreground = 0 #default foreground colour setting (black)
config.background = 16777215 #default background colour code (white)
8
16
TheRGBcodeforwhiteiscalculatedasfollows: 255 + 255 2 + 255 2 = 16777215 .
ThefollowingoptionsdefinethepixelsizeusedinthemapsontheQualitytab.YoucanletACPautomaticallydefinethepixel
sizeoryoucandefineityourself:
config.isAutoPixel=1 # Automatically calculate point size from coverage surface
config.pixelSize=1 # If autopixel is not set, use this number of pixels for each point
config.pixelCoverage=50 # If autopixel is set, calculate the pixel size of a point
to try to cover the set percentage of the used surface
config.maxPixelSize=6 # If autopixel is set, limit the pixel size to the set maximum.
ThefollowingoptionsdefinethesizeofthemaptitleontheQualitytab:
config.titleHeight=16 # Title height in pixels
config.titleFontSize=16 # Size of title font in points
ThefollowingoptiondefinesthewidthofthemarginontheQualitytab:
config.margin=2 # Margin width in pixels
ThefollowingoptionsdefinetheappearanceofthemaplegendontheQualitytab:
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
ThefollowingoptiondefineswhetherornottheaxiswillbedisplayedontheQualitytab:
config.showAxis=1
ThefollowingoptionsdefinetheappearanceofthehistogramontheQualitytab:
config.showHistogram=1 # Defines whether the histogram is displayed.
config.histogramHeight=60 # Defines the width of the histogram in pixels.
ThefollowingoptionsdefinetheappearanceofthefocuszoneontheQualitytab:
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.
215
Forsk2014
12.2.2.19 DefiningtheAppearanceofPredictions
Inthe[ACPMapDefault]sectionistheoptionfordefiningtheappearanceofpredictionscreatedfromoptimisationresults.
Thefollowingoptiondefinesthetransparencyofpredictions:
transparency=50
12.2.2.20 DefiningNewPredictions
Inthe[ACPNewMapDlg]sectionareoptionsfordisplayingadditionalpredictionsthatcanbecreatedfromsetupsandfrom
theoptimisationresults.
Setting the option "showBestServerAerialMap" enables the user to create a prediction that displays the initial and final
coveragebyantenna.
[ACPNewMapDlg]
showBestServerAerialMap=1 # "1" displays the option, "0" hides the option
Settingtheoption"showObjectiveWeightMap"enablestheusertocreateapredictionthatdisplaystheweightusedforthe
trafficandforeachzone.
[ACPNewMapDlg]
showObjectiveWeightMap=1 # "1" displays the option, "0" hides the option
Settingtheoption"showBestServerTxMap"enablestheusertocreateapredictionthatdisplaystheinitialandfinalcoverage
bytransmitter.
[ACPNewMapDlg]
showBestServerTxMap=1 # "1" displays the option, "0" hides the option
Settingtheoption"showchangeImprovementMap"enablestheusertocreateapredictionthatdisplaystheimprovementin
coverage.
[ACPNewMapDlg]
showchangeImprovementMap=1 # "1" displays the option, "0" hides the option
Settingtheoption"showSectorSelectionMap"enablestheusertocreateapredictionthatdisplaystheaddedorremoved
sectorsduringsiteselection.
[ACPNewMapDlg]
showSectorSelectionMap=1 # "1" displays the option, "0" hides the option
Settingtheoption"showTotTilt"enablestheusertocreateapredictionthatdisplaysthetotaltilt(electricalandmechanical).
[ACPNewMapDlg]
showTotTilt=1 # "1" (default) displays the option, "0" hides the option
12.2.2.21 DefiningtheFunctionalityoftheCommitTab
Inthe[ACPCommitPage]sectionistheoptionfordefiningwhethertheusercanonlyeditthesetofchangestobecommitted
ontheChangeDetailstab(default).Setting"allowUserChangeForCommit"to"true"allowstheusertoeditthesetofchanges
ontheCommittab;thissettingisnotrecommended.
[ACPCommitPage]
allowUserChangeForCommit=false
Youcanusethe"addCandidateComment"optiontocreateacommentinanysite,transmitter,andcellsautomaticallycreated
byACPinAtollaspartofthecandidatesiteselection.Nocommentisaddedifthisoptionisleftblank.
[ACPCommitPage]
addCandidateComment=Created from ACP candidate list
Trac1905:YoucanusethefollowingoptionstotransfertoAtollthecandidatepathlosscomputedbyACP,soastoavoidre
computationbyAtoll.
216
AT321_AM_E1
[ACPCommitPage]
transferCandidatePathlossToAtoll=0
transferCandidatePathlossToAtoll.autoRemoveHdr=1
12.2.2.22 DefiningtheAppearanceoftheOverlayWindow
Inthe[ACPOverlayDialog]sectionistheoptionfordefiningtheopacityoftheoverlaywindowwhenitlosesfocus.Avalueof
100disablesit.
[ACPOverlayDialog]
opacity=100
12.2.2.23 DefiningtheAppearanceoftheGraphTab
Inthe[ACPGraphPage]sectionistheoptionforenablingthedisplayoftimemarkersontheGraphtaboftheOptimisation
Propertiesdialogue.Avalueof100disablesit.
[ACPGraphPage]
showTimeMarkers=1 # add time markers on the X axis. Default is "0" (OFF)
12.2.2.24 DefiningtheDefaultFont
In the [ACPUI] section is the option for defining the default font to be used by the grid, graph component, and map
component.Intheexamplebelow,thefont"MSUIGothic,"usedinJapanesesystems,issetasthedefaultfont.
[ACPUI]
# define the font used by grid, graph component and map component
DefaultFont=MS UI Gothic
# for grid only, define the used font size. 0 mean default size
DefaultGridFontSize=0
12.2.2.25 ExportingOptimisationResultsinXML
Inthe[ACPXmlReport]sectionaretheoptionsfordefiningthecontentsandappearanceofanXMLreportgeneratedfromthe
StatisticstaboftheoptimisationPropertiesdialogue.
enableXmlExport=1 #enable the xml report from the ResultStatPage
generateXmlSection=-1 # bit combination of following: 1=metadata, 2=setup,
4=resultSummary, 8=resultSectors, 16=resultIterations, 32=resulstChangeset,
64=resultMaps., -1=all
encoding=UTF-8
saveDefaultStylesheet=1
#save a default stylesheet if none exist
defaultStylesheetName=.acpReport.xslt # name of the default stylesheet file. set it

empty to disable stylesheet processing instruction
12.2.2.26 ChangingtheColourLegendfortheOptimisationGraph
Inthe[ACPColorsDefault]sectionaretheoptionsfordefiningthedefaultcoloursintheOptimisationwindow(duringand
afterarun).Thesedefaultcolourscanbedefinedineitherofthefollowingformats:
graph.umts1 = RGB(0 0 255)
or
graph.umts1 = 0000FF -> RGB hexadecimal color code as used in HTML
ThefollowingarethedefaultcolourcodesforthegraphsintheOptimisationwindow(ontheGraphstabduringarun)andin
theOptimisationresultsafterarun(ontheChangeDetailsandGraphtabs)
graph.umts1 = B34700 (samecolourcodesareusedinCDMA)
graph.umts2 = FF6600
graph.umts3 = FFB380
217
Forsk2014
graph.gsm1 = 660099
graph.gsm2 = D580FF
graph.gsm3 = EABFFF
graph.wimax1 = 458A8A (samecolourcodesareusedinWiFi)
graph.wimax2 = 30BFBF
graph.wimax3 = 66FFFF
graph.lte1 = FFD100
graph.lte2 = 999900
graph.lte3 = D9CC7F
graph.obj1
graph.obj2
graph.obj3
graph.obj4
=
=
=
=
FF000D (colourcodesusedformultitechnologyobjectivesinmultitechnologyoptimisations)
3600FF
18FF00
FFD100
graph.cost = 00FF00 (colourcodeforfinancialcost)

graph.expos = 3737A6 (colourcodeforEMFexposure)
graph.load = 0AFFFF (colourcodesforloadbalance)
graph.loadqi = A27901
graph.traf = F9F602
ThefollowingarethedefaultcolourcodesforthehistogramintheOptimisationwindow(ontheChangestabduringarun).
change.antenna = RGB(0 0 255)
change_etilt = RGB(64 224 208)
change_azimuth = RGB(0 255 0)
change_tilt = RGB(255 255 0)
change_power = RGB(193 0 66)
change_height = RGB(255 173 93)
change_txRemoved = FFCDE8
change_siteRemoved = FF99CC
change_siteAdded = 99CCFF
change_txAdded = 5D927D
change_repGain = 660099
12.2.3 ACPCoreEngineOptions
Thesettingsinthe[ACPCore]sectionareusedtodefinehowtheACPenginefunctions.
12.2.3.1 LogFileSettings
ACPenablesyoutosetupalogfileaswellascreateacrashreportincaseofanapplicationcrash.
ThefollowingoptiondefineswhetherACPgeneratesalogfile(withthenameATL_NAME_optim.log):
[ACPCore]
generateLogFile=0 # The default is "0"; no log file.
12.2.3.2 CalculationThreadPoolSettings
The following options define how the calculation thread pool will be managed. If "useComputationThreadPool" is set to
"false,"ACPusesonlyonethread.If"useComputationThreadPool"issetto"true,"ACPusesthenumberofthreadsspecified
bythe"computationThreadPoolSize"option.Thedefaultsettingfor"computationThreadPoolSize"is"1"andmeansthatACP
willuseonethreadperprocessorcore(CPU)available.
[ACPCore]
useComputationThreadPool=true
computationThreadPoolSize=-1
218
AT321_AM_E1
12.2.3.3 NumberofThreadsUsedforPropagationModelCalculations
Thefollowingoptiondefineshowmanythreadsthepropagationmodelcanusewhencalculations(forexample,ofheightor
angles of incidence) are delegated to the propagation model. This can be useful, for example, to control the number of
licencestakenbytheACP,withoutreducingthenumberofthreadsusedbyregularACPcalculations.Thefollowingsettings
arepossible:
2:Thedefaultvaluemeansthatthepropagationmodelwillusethesamenumberofthreadsasthatdefinedbythe
"computationThreadPoolSize"option.
1:Autoconfiguration;thepropagationmodelwilluseonethreadforeachCPUcore.
Other: Entering a numerical value for "pathlossThreadPoolSize" indicates the number of threads the propagation
modelcanuse.
[ACPCore]
pathlossThreadPoolSize=-2 # Default. Same as computationThreadPoolSize.
12.2.3.4 MemoryManagementSettings
ThefollowingoptionsdefinehowtheACPmanagesmemoryduringcalculations.
TheACPtriestoestimatetheworstcasescenarioinmemoryuse,andindicatestotheuserwhenmemoryuseseemstoohigh.
Usingoneofthefollowingoptions,youcandefinethemethodACPusestoindicateexcessivememoryuse:
memLimitNumPos:Memoryuseisdeterminedtobeexcessivewhenthemaximumnumberofpixels,asdefinedin
"memLimitNumPos"isreachedduringacalculation.Setting"memLimitNumPos"to"1"deactivatesthisoption.
memLimitMemory:MemoryuseisdeterminedtobeexcessivewhentheestimatedmemoryuseinMb,asdefinedin
"memLimitMemory"isreachedduringacalculation.Setting"memLimitMemory"to"1"deactivatesthisoption.
memLimitUseableMemory:Memoryuseisdeterminedtobeexcessivewhentheestimatedmemoryuseexceedsthe
percentage of the total memory available for Atoll, as defined in "memLimitUseableMemory." Setting
"memLimitUseableMemory"to"1"deactivatesthisoption.
Ifallthreeoptionsaredeactivated,ACPdoesnotcheckexcessivememoryusage.
The"abortIfMemLimitReach"optiondefineshowACPreactsifthedefinedmaximummemoryuseisreached.Bydefault(with
"abortIfMemLimitReach"setto"0"),ACPwillattempttoallocatememory.Ifunabletosuccessfullyallocatememory,ACP
displaysamessageandthecalculationisstopped.Whenusingtheoption"abortIfMemLimitReach",thenACPwillnotstartif
themessageindicatingexcessivememoryuseisdisplayed.
By default, excessive memory use is considered an estimate of 80% of the memory available to the process; ACP is not
preventedrunningevenwhen80%isexceeded.
When ACP estimates actual memory use (i.e., using either "memLimitMemory" or
"memLimitUseableMemory"),thememoryestimateisonlyaroughestimate.Depending
ontheproject,actualmemoryusagecanbequitedifferent.
memLimitNumPos=-1 # A setting of "-1" deactivates this option.

memLimitMemory=-1 # A setting of "-1" deactivates this option.
memLimitUseableMemory=80 # A setting of "-1" deactivates this option.
abortIfMemLimitReach=0
12.2.3.5 SignalLevelandMacroDiversityGainCalculationOptions
ThefollowingoptionsdeterminehowACPcalculatesthesignallevelandthemacrodiversitygainmode.
12.2.3.5.1
SignalLevel
YoucandefinehowACPmeasuresthesignallevel(UMTSRSCP,GSMBCCHPower,WiMAXPreamblePower,LTEReference
signalPower,CDMApilotpower)usingthe"linkMode"option.The"linkMode"optioncanhaveoneofthefollowingvalues:
0:When"linkMode"issetto"0,"ACPconsidersthesignallevelonthedownlinkandtransmissionlossesaretaken
intoaccount.Thisisthedefaultsetting.
1:When"linkMode"issetto"1,"ACPconsidersthesignallevelontheuplinkandreceptionlossesaretakeninto
account.
2:When"linkMode"issetto"2,"ACPdoesnottakereceptionortransmissionlossesintoaccount.
linkMode = 0 # The default
219
12.2.3.5.2
Forsk2014
MacroDiversityGain(UMTSOnly)
ThefollowingoptiondefineswhetherACPtakesmacrodiversitygainintoaccountinUMTS."addPilotSHOGain"canhavethe
followingvalues:
0:When"addPilotSHOGain"issetto"0,"ACPdoesnottakemacrodiversitygainintoaccount.
1:When"addPilotSHOGain"issetto"1,"ACPtakesmacrodiversitygainintoaccount.Thisisthedefaultvalue.
AnychangesyoumakeheremustmatchcorrespondingchangesintheAtoll.inifile.When
"addPilotSHOGain"issetto"0,"theACPresultswillonlymatchtheresultsinAtollifthe
followingsettingsaremadeinthe[CDMA]sectionoftheAtoll.inifile:AddPilotSHOGain=0
addPilotSHOGain=1 # The default
12.2.3.6 DeterminingTransmitterAltitude
The following option defines how ACP determines the transmitter altitude when no site altitude is defined in Atoll.
"useSiteAltitude"canhavethefollowingvalues:
0:When"useSiteAltitude"issetto"0,"ACPusestheexacttransmittercoordinates,includingdxanddyoffset.
1:When"useSiteAltitude"issetto"1,"ACPusesonlythecoordinatesofthesite.Thisisthedefaultvalue.
AnychangeyoumakeheremustmatchacorrespondingchangeintheAtoll.inifile.When
"useSiteAltitude"issetto"1,"theACPresultswillonlymatchtheresultsinAtollifthe
followingsettingismadeintheAtoll.inifile:useSiteAltitude=1
useSiteAltitude=1 # The default
12.2.3.7 AutomaticCandidatePositioningOptions
Thefollowingoptiondefinestheminimumdistancethatmustberespectedbetweenanautomaticallycreatedcandidateand
anexistingsiteorapredefinedcandidatesite.IfAtollcannotcreateanautomaticcandidatesiteandrespectthisdistance,
no candidate will be created. The default value is 25% of the intersite distance defined in the Automatic Candidate
Positioningdialogue.
[ACPAutoCandPosDlg]
minInterSiteDistRatio=0.25 # Default
Thefollowingoptiondefinesthedefaultintercandidatesitedistanceinmetres.
interSiteDist=500
TheACPnormallyplacescandidatesitesinastricthexagonalpattern.However,theACPcansearchforamoreappropriate
sitewithinasearchradiusratioaccordingtothedefinedrules.Thefollowingoptiondefinesthedefaultsearchradiusratioas
apercentageofthedefinedintercandidatesitedistance.
searchRadiusRatio=30
Thefollowingoptiondefinesthedefaultminimumincreaseinaltitude(inmetres)thattheACPmustfindwhenplacinganew
automaticcandidatesite.
hpHeightThres=10
12.2.3.8 BalancingSpeed,MemoryUse,andAccuracyinCalculations
OntheUserPreferencestaboftheACPAutomaticCellPlanningPropertiesdialogue,ACPenablesyoutoselectamodeof
operationthatbalancesbalancespeed,memoryuse,andaccuracy.Bydefiningthesettingsoftheoptionsintheacp.inifile
thateachmodeuses,youcanfinetunehowACPwilloperateintheselectedmode:
220
High Speed: Using the highest speed also uses the least memory although the final results might be slightly less
accurate.
Default:Whennochangesaremadetotheacp.inifile,ACPusesthedefaultsettings.Thedefaultsettingscanbe
overriddenbychangingthesettingsinthissection.
HighPrecision:Whenthesettingsinthissectionaredefinedtogivetheresultsofthehighestprecision,calculating
theresultswilltakethelongesttimeandwillusemorememory.
AT321_AM_E1
Theoptionsdescribedbelowarethoseusedforthedefaultoperationmode
Theacp.inioptionsthatdefinehowtheselectedmodeworksaredescribedbelow:
maxMonitorCell:The"maxMonitorCell"definesthemaximumnumberofcellsmonitored.Thisoptionaffectsmemory
use and accuracy. The analogous options for the high speed mode and the high precision mode are
"maxMonitorCellSpeed"and"maxMonitorCellPrec",respectively.
threshLevelMonitorCell: The"threshLevelMonitorCell" definesthebest serversignal threshold(dB) inorderto be
monitored.Thisoptionaffectsmemoryandaccuracy.
Theanalogousoptionsforthehighspeedmodeandthehighprecisionmodeare"threshLevelMonitorCellSpeed"and
"threshLevelMonitorCellPrec",respectively.
ThefollowingoptionsdefinethevaluesACPusesfordefaultmode:
maxMonitorCell=32
threshLevelMonitorCell = 35
ThefollowingoptionsdefinethevaluesACPusesforhighspeedmode:
maxMonitorCellSpeed=30
threshLevelMonitorCellSpeed = 30
ThefollowingoptionsdefinethevaluesACPusesforhighprecisionmode:
maxMonitorCellPrec=35
threshLevelMonitorCellPrec = 40
Otheroptionsintheacp.inifilecanbeusedtodefineadditionaloffsetsthatwillbeusedbythespecifictechnologythatACP
isoptimising:
threshLevelOffUmts=0
maxMonitorOffUmts=0
threshLevelOffGsm=0
maxMonitorOffGsm=0
threshLevelOffWimax=5
maxMonitorOffWimax=5
threshLevelOffLte=10
maxMonitorOffLte=10
12.2.3.9 AccessingRasterData
Whenworkingincoplanningmode,youhaveseveralAtolldocumentsopenandyouareworkingwiththeACPfromthemain
document.ACPneedstoaccessrasterdataandbydefaultitaccessesonlytherasterdataspecifiedinthemaindocument.If
forsomereasondifferentrasterdataisusedinthesecondarydocument,youmustsettheACPtoaccessrasterdataforeach
documentseparatelyusingthefollowingoption:
gisDataTechnoShared=0
AtollACPloadsrasterdatawithblockbasedprocessingtoreducememoryusage.Themaximummemory(inMb)allowedfor
thisblockprocessinginMbiscontrolledwiththefollowingsetting:
gisDataCacheMemMax=256
YoucanreducethisnumberifyouexperienceissueswithACPfailureduetomemoryallocation.
12.2.3.10 AccessingPathLossMatrices
YoucandefinehowACPaccessespathlossmatricesusingthe"pathlossAccessMode"option.Thisoptionhastwopossible
values:
0:Ifthisoptionissetto"0,"ACPwillaccesspathlossmatricesthroughAtoll.
1:Ifthisoptionissetto"1,"ACPwillaccesspathlossmatricesdirectly.Withthissetting,thepathlossmatricesmust
bestoredexternally;theycannotbeembedded.
2:Ifthisoptionissetto"2,"ACPwillaccesspathlossmatricesdirectlyiftheyareexternal,otherwisethroughAtollif
theyareembedded.Thisisthedefaultvalue.
221
Forsk2014
pathlossAccessMode=2
12.2.3.11 FilteringClutterClassLayers
Whenusingseverallayersofrasterclutterclasses,eachwithadifferentresolution,youcandefinewhichresolution(usually
thelowerresolution)ACPshouldusewhendefiningzonesbyclutterclass.Settingthe"gisDataClutterOnlyRes"optionto"0"
(thedefault)meansthatclutterclasslayerswillnotbefilteredoutbyresolution.Settingthisoptiontoanyothervalue(for
example,"20")meansthatACPwillonlyuseclutterclasseswiththatresolution(inthiscalse,"20").
[ACPCore]
gisDataClutterOnlyRes=20 # ACP will only use clutter classes with this resolution
Ifyousetthe"gisDataClutterOnlyRes"optiontofilteroutallclutterclassesbutthosewiththedefinedoption,youshouldalso
listtheclutterclassesthatarenottobeusedinthe"zone.clutter.hiddenCodes"inthe[ACPGeneralPage]sectiontoensure
thattheuserwillnotcreatezonesbasedonclutterclassesthatarenotused.Whenyoudefinetheclutterclassesthatarenot
used,theywillnotbedisplayedintheZoneDefinitiondialogue.
[ACPGeneralPage]
zone.clutter.hiddenCodes=0,1,2,12,13 # These clutter classes are not displayed
12.2.3.12 PreambleSegmentation(WiMAX)
YoucandefinehowACPtakessegmentationintoaccountusingthe"wimaxPreambleSegmented"option.Thisoptionenables
youtotakeintoaccountthechangeinchangeincalculationmethodsfromversion2.7.1toversion2.8.0ofAtoll.Inversion
2.7.1, the preamble was not considered as segmented unless the frame configuration used by the cell was flagged as
segmented.Inversion2.8.0,thepreambleisconsideredbydefaulttobesegmented.
Thisoptionhasthepossiblevalues:
0:ThisvalueisintendedforversionsofAtolluptoandincludingversion2.7.1.Ifthisoptionissetto"0,"ACPwillonly
takepreamblesegmentationintoaccountifthesegmentationflagofcellframeconfigurationissettoON.
1:ThisvalueisintendedforversionsofAtollof2.8.0andup.Ifthisoptionissetto"1,"ACPalwaystakespreamble
segmentationintoaccount.
2:Ifthisoptionissetto"2,"ACPautomaticallydetectstheversionofAtollused.Thisisthedefaultvalue.
wimaxPreambleSegmented=2
12.2.3.13 MultiantennaInterferenceCalculation(LTE)
0:Interferenceindependentofnumberoftransmitantennas.
1:Interferencemultipliedbynumberoftransmitantennas.
2:ACPautomaticallydetectstheversionofAtollused,andhencethevalueusedbyAtollforthisoption.Thisisthe
defaultvalue.
lteMultiAntennaInterference=2
12.2.3.14 MultiantennaInterferenceCalculation(WiMAX)
0:Interferenceindependentofnumberoftransmitantennas.
1:Interferencemultipliedbynumberoftransmitantennas.
defaultvalue.
wimaxMultiAntennaInterference=2
12.2.3.15 CyclicPrefixEnergyinSignalLevelCalculation(LTE)
Referto"IncludingCyclicPrefixEnergyinLTESignalLevelCalculation"onpage 186fordetails.
222
0:Included.
1:Excluded.
AT321_AM_E1
defaultvalue.
lteExcludeCPFromUsefulPower=2
12.2.3.16 CyclicPrefixEnergyinSignalLevelCalculation(WiMAX)
Referto"ExcludingCyclicPrefixEnergyinWiMAXandWiFiSignalLevelCalculation"onpage 186fordetails.
0:Included.
1:Excluded.
defaultvalue.
wimaxExcludeCPFromUsefulPower=2
12.2.3.17 ApplyingTransmitDiversityGainstoReferenceSignals(LTE)
ThisoptiondefinesinmultiantennamodehowtheinstantaneousReferenceSignalpoweriscalculated.
0:usethepowertransmittedonasingleport(Default)
1:usethepowertransmittedonbothports
2:usethesametransmitdiversitygainasusedforPDSCH(unsupported)
lteUseDivGainOnRS=0
12.2.3.18 FixedRatioBetweenPilotPowerandMaxPower(UMTS)
WhenoptimisingthemaximumcellpowerinUMTS,theACPforcestheratiobetweenpilotpowerandmaximumpowerto
stayconstant.Youcanremovethisconstraintusingthefollowingoption:
umtsPilotPowerRatioFixed=0
12.2.3.19 ShowingInitial/Final"TotalPower"or"DLLoad"onSectorsTab(UMTS)
WhenoptimisingthepilotpowerinUMTS,youcandisplayanadditionalTotalPower(dBm)orDLLoad(%)columnonthe
SectorstaboftheOptimisationPropertiesdialogbox,accordingtotheDLloadsetting(Absoluteor%Pmax,resp.)inthe
NetworkSettingsPropertiesdialogbox.
Beforeyourunanoptimisation,makesurethatPilotPowerisselectedontheUMTSCellstaboftheReconfigurationpage
(SetupProperties)andsetthefollowingoptioninACP.ini:
[ACPResultSectorPage]
showDlLoad=1 # (default=0)
12.2.3.20 EnablingMultitechnologyOptimisationIncludingWiMAX
InordertousetheACPtooptimiseyourWiMAXnetworkwithanyothertechnologynetwork(GSM,UMTS,CDMA2000,and
LTE),setthefollowingoptioninACP.ini:
[ACPImportProject]
importWimax=1 # (default=0)
ThisoptionisvalidforcoplanningsupportbetweenWiMAXand:
SingleRANGSM,UMTS,CDMA2000,andLTE
MultiRAT3GPPand3GPP2
12.2.4 EMFExposureCoreOptions
Inthe[ACPEMFCore]sectionthereareseveraloptionscontrollingtheEMFexposurecalculationengine.
223
Forsk2014
Onesetofoptionsallowsforthedetectionandautocorrectionoftransmitterheightswhicharefoundtobeindoors,just
belowtheroof.Thisisusuallycausedbyinconsistenciesbetweenthevectorsimportedtocreatethe3Drepresentationofthe
terrainandAtolldatabase.
Theotheroptioncontrolstheresolutionusedinternallytorasteriseinputvectors,thedefaultbeing2 metres.
WhentheheightofatransmitteriswithintheDigitalHeightModel(i.e.,thecombinationofclutterheightsandimported
vectorsusedtocreatethe3Drepresentationoftheterrain)andDHMoffset,thenitisconsideredtobeindoors,justbelow
the roof. The ACP automatically detects these transmitters and displays warnings in the Event Viewer. The default
distancebeneaththeroofis5 metres.
[ACPEMFCore]
detectTxIndoorOffset=5
TheACPcanautomaticallyadjusttheheightoftransmittersthatarebelowroofsothattheyareontopoftheclutterheight
usingthedefinedoffset(inmetres).
resetTxHeightWhenIndoor=0 # "0" is the default; height is not reset.
Thefollowingoptiondefinestheinternalresolutioninmetresforterrain3DrepresentationwhentheACPrasterisesinput
vectors:
vectorRasterizationResolution=2 # "2" is the default.
ThefollowingoptionallowsyoudecreasethedisplayedEMFlevelwhenpenetrationlossisincreasedforbuildings.
flagPixelFacadeDist=0 # "0" is a distance in metres.
flagPixelFacadeDistdefinestheindoordistancefromfaadeforapixeltobeconsideredas"indoor".Whenthedistanceis0,
theoutdoorpixelswillbeappliedtheindoorpenetrationlossspecifiedinthePropagationClassDefinitiontable(Propagation
pageontheOptimisationtab).
12.2.5 OtherOptions
Inthe[ACPMisc]sectionareseveraladditionalACPconfigurationoptions.
12.2.5.1 ValidityofCoveragePredictions
Youcanusethefollowingoptiontoenableordisabletheautomaticverificationofthevalidityofcoveragepredictionsbefore
runninganoptimisationsetup.
autoCheckPredictionValidity=1 # "1" enables the automatic verification
Thefollowingoptionscanbeusedtoenableotherautomaticverificationsonthenumberofactivetransmitters,theirpathloss
filesize,andlockedstatusintheAtolldocument:
autoCheckPredictionFileValidity=1 # Check of path loss matrices before a run.
autoCheckTxNumber=1 # Check number of active transmitters.
manageLockedPredictionAsvalid=1 # Treat locked prediction as always valid.
# Default is "1" (true)
If"autoCheckPredictionValidity"issetto"1,"therebyenablingtheverificationofthevalidityofcoveragepredictions,youcan
haveACPautomaticallyrecalculatetheinvalidcoveragepredictionsusingthefollowingoption.Ifitissetto"0,"ACPwillnot
automaticallyrecalculatepredictions.
autoPathlossRecomputation=0
224
IndexofInitialisationOptions
AT321_AM_E1
A
acp.inimainoptions
CalculationThreadPoolSettings
computationThreadPoolSize 218
useComputationThreadPool 218
CustomcolumnsonTransmittersandRemotetabsofReconfigu
rationpage
206
tx.custom.x.column 206
tx.custom.x.label 206
tx.custom.x.type 206
DefaultValuesontheAntennasTab
enableAedt 208
DefaultValuesontheOptimisationTab
cost.antenna.cost 195
cost.antenna.isSiteVisit 195
cost.azimuth.cost 195
cost.azimuth.isSiteVisit 195
cost.etilt.cost 195
cost.etilt.isSiteVisit 195
cost.height.cost 195
cost.height.isSiteVisit 195
cost.newSiteCost 195
cost.power.cost 195
cost.power.isSiteVisit 195
cost.removeSiteCost 195
cost.siteVisitCost 195
cost.tilt.cost 195
cost.tilt.isSiteVisit 195
cost.upgradeSiteCost 195
DefaultValuesonthePatternstaboftheAntennaTab
enableETilt 206
enableMTilt 206
DefaultValuesontheReconfigurationTab
defaultTxAzimuthMinInterSector 204
defaultTxAzimuthStep 204
defaultTxAzimuthVariation 204
defaultTxETiltMax 204
defaultTxETiltMin 204
defaultTxHeightMax 204
defaultTxHeightMax.feet 204
defaultTxHeightMin 204
defaultTxHeightMin.feet 204
defaultTxHeightStep 204
defaultTxHeightStep.feet 204
defaultTxTiltMax 204
defaultTxTiltMin 204
defaultTxTiltStep 204
tx.etilt.deltaLimitConstraint.show 204
DefaultValuesontheTransmittersTaboftheReconfiguration
Tab
tx.tilt.asRelative 205
DefiningAutomaticSiteClasses
cost.classes.0.antenna.cost 213
cost.classes.0.antenna.isSiteVisit 213
cost.classes.0.azimuth.cost 213
cost.classes.0.azimuth.isSiteVisit 213
cost.classes.0.etilt.cost 213
cost.classes.0.etilt.isSiteVisit 213
cost.classes.0.height.cost 213
cost.classes.0.height.isSiteVisit 213
cost.classes.0.name 213
cost.classes.0.newSiteCost 213
cost.classes.0.power.cost 213
cost.classes.0.power.isSiteVisit 213
cost.classes.0.removeSiteCost 213
cost.classes.0.siteVisitCost 213
cost.classes.0.tilt.cost 213
cost.classes.0.tilt.isSiteVisit 213
cost.classes.0.upgradeSiteCost 213
cost.classes.count 213
DefiningReconfigurationValuesforSitesUsingCustomAtoll
Fields
site.gsm.status 211
site.lte.status 211
site.status 211
site.status.candidate 211
site.umts.status 211
DefiningtheAppearanceoftheGraphTab
showTimeMarkers 217
DefiningtheFunctionalityoftheCommitTab
allowUserChangeForCommit 216
NumberofThreadsUsedforPropagationModelCalculations
pathlossThreadPoolSize 219
atoll.inioptionslistedbyINIsection
3GCells,NoSuffixIfUniqueCarrier 180
ACP,iniFile 194
Addins,AddinName 158
AFP,GlobalDistanceMatrixDegreeUB 178
AFP,SimpleUserGUI 176
AFP,WorstCaseIM_FskAfp 177
Antenna,AngleCalculation 168
Antenna,CatalogVerticalDiagramOrientation 168
Antenna,InterpolatePatternEvenIfOnlyOneDiagram 168
Antenna,InterpolatePatternIndB 168
Antenna,PrecisionTimes10 152
Antenna,REDTDisplay 162
AutoRename,3GCells 148
AutoRename,Transmitters 148
BsicFormat,DefaultValue 175
Calculations,RoundAltitudes 172
Calculations,UseSiteAltitude 170
CDMA,AddPilotSHOGain 180
CDMA,CodeStrategies 184
CDMA,CQIDeltaWithPower 181
CDMA,CutOffSimu 182
CDMA,DisplayEcIoOfRejected 183
CDMA,HSDPAAvgSimuResults 180
CDMA,HSDPAMaxRejections 182
225
CDMA,HSDPAThroughputPeak 180
CDMA,IterBeforeDown 183
CDMA,MaxRejections 182
CDMA,MinUsersPerBin 181
CDMA,MultiBandSimu 184
CDMA,OrthoInCPICH 181
CDMA,ParallelSimulations 171
CDMA,PFSchedulerCQIFactor 183
CDMA,PmaxInIntraItf 181
CDMA,PredictSimuMemorySize 172
CDMA,UseStudyCnxProba 181
Clutter,OnlyVisibleClassesInInterferenceReport 155
Clutter,PerClassPercentagesRelativeToCoverageInReport 155
ClutterParams,IndoorActivity 169
Compatibility,MWEquipment_CIMIN 191
Compression,StartSizeInMB 158
CoPlanning,ComputeLinkedPredictions 172
CoPlanning,LinkedPredictionsComputationMode 173
CoPlanning,LinkSites 154
Database,AllowNullRecordsForNotNullableCustomFields 165
Database,CommandTimeout 166
Database,ExclusiveProvider 167
Database,IntegrityChecker 165
Database,OverwriteSharedFolderPath 167
Database,PromptOnArchive 166
Database,SubCellAuditConsistency 165
Database,SubCellAuditMainValues 166
Database,UseTransaction 167
Display,CellIDNbDigits 161
Display,DiscreteValueColoring 162
Display,PaletteColor0 162
DocTitle,UseTechnoName 162
EventsObserver,LogPath 149
EventsObserver,milliseconds 160
EventsObserver,ShowAddinAccessDeniedMsg 149
EventsObserver,date 160
Export,AutoOpenWithExcel 153
Export,NewLineEscapeSequence 159
Features,IM_TRAFFIC_OVERLAP 175
FskPropagModels,OptimOnNoData 172
Geo,FindGeoButtonAlwaysActive 154
Geo,ReportObeysVisibility 154
Geo,VectorDisplayConfigurationCompanionFile 154
Grids,NbDecimals 153
GSM, 177
GSM,CanEditTRXInfoAtTXLevel 178
GSM,ExternalIncluded 175
GSM,FirstTRXIndex 179
GSM,MinNeighbourImportanceInAFPResults 177
GSM,ShowNonSynchSFHViolationsInAFPResults 177
GSM,SubcellValueFixMethod 179
GSM,TRXIndexHidden 179
GSM,WideRangeSubcellThresholds 179
GUIUserRights,EnableMacrosAddins 153
GUIUserRights,EnableNewDocFromTemplate 153
GUIUserRights,EnableZip 153
IM,FilterByFrequencyBands 178
226
Forsk
Import,LoadKMLVectors 152
Import,LoadVectors 152
License,ACP_GSM 164
License,ACP_LTE 164
License,ACP_UMTS 164
License,ACP_WiMAX 164
License,BH 164
License,CDMA 164
License,GSM 164
License,GSM_AFP 164
License,IdleTime 165
License,LTE 164
License,LTE_AFP 164
License,Measures 164
License,MW 164
License,TDSCDMA 164
License,TimeBombNotice 164
License,UMTS 164
License,WiMAX 164
License,WiMAX_AFP 164
LOSArea,ResolutionMultFactor 169
LTE,ApplyDLLoadOnPDCCHInterf 188
LTE,DisplaySignalsPerSCInPtA 186
LTE,eICIConRS 190
LTE,EIRPfromRSEPRE 189
LTE,ExcludeCPFromUsefulPower 186
LTE,InterNeighbourIDCollisions 187
LTE,NR_CONTROL_MARGIN_MIN 189
LTE,SameItf_PDSCH_RS_PDCCH 188
LTE,ServiceMBRDowngrading 189
LTE,ULNRControlMethod 189
LTE,ULNRControlPrecision 189
LTE,UseABSonCellEdgeOnly 190
LTE,UseDivGainOnRS 187
MajorVersionChange,EnablePartialRefreshInMigration 167
MITAB,Coordinatesystemdefinitionintheheaderfile 150
MITAB,DisableNormalization 155
MITAB,EnableMessages 156
MultiRAT,AllCodesAllocWithInterRATNeighbours 190
MWCalculations,HIDE_REC530_5 191
MWCalculations,ShieldingFactorOnWantedSignal 191
MWCalculations,UpdateOppositeHop 191
MWCalculations,UseProfilesFiles 191
MWReport,DefaultTemplate 193
MWReport,DesignSummaryCfg 192, 193
MWReport,LinkAnalysisCfg 192
MWReport,LinkInterferenceCfg 192
MWReport,LinksBudgetCfg 192
MWReport,LinksInterferenceCfg 192
MWReport,MultihopAnalysisCfg 192
MWReport,RainBelow0001 192
MWReport,ReflectionAnalysisCfg 192
MWReport,RequiredMarginCfg 192
MWReport,tab 192
Neighbours,CandidatesMaxDistanceInImportanceCalculation
174
Neighbours,CompressModeEval 185
AT321_AM_E1
Neighbours,DistanceAzimutWeightingPercent 174
Neighbours,DoNotDeleteSymmetrics 174
Neighbours,ExcludeFilteredCellsFromNeighbourLists 173
Neighbours,ForceSymmetryInFocusZone 173
Neighbours,RealInterSiteDistanceCondition 174
Neighbours,RepeaterInterSiteDistanceInAlloc 174
OFDM_AFP,AdjacentProtection 188
OFDM_SIMU,MeanNRInDB 189
OFDM,DisplayThroughputZero 189
OFDM,SecondNeighbours 188
OFDM,UniformIDDistribution 187
OFDM,UseCommonBearersOnly 186
OnlineMaps,Name 158
OnlineMaps,TilesCachePath 159
OnlineMaps,URL 158
Pathlosses,EmbeddedByDefault 169
Pathlosses,FullResyncPrivShared 156
Pathlosses,DisplayIndividualSuccessOrFailure 150
Pathlosses,DisplayInvalidityCause 150
Pathlosses,DisplayOverallSuccessOrFailure 150
Perfos,MaxRangeApplied 176
Perfos,PtAnalysisMargin 152
Perfos,PtAnalysisNbServersMax 152
Perfos,ConfirmStoreExternPrivLosFilesOnCopy 149
Perfos,StoreExternPrivLosFilesOnCopy 149
PlanetImport,ChangeKclutterSign 166
PlanetImport,SensitiveCase 166
Population,ReportResolution 156
Print,LogoFooterChecked 156
Print,MaxDPI 149
PSC,ConstantStep 184
PSC,DisplayCostValues 184
RasterExport,GeorefWithTAB 154
Rasterization,Improve 182
Rasterization,MaximumSurf 183
Rasterization,Precision 182
Rasterization,SurfRatio 183
ReceptionTab,NumberOfTransmitterDisplayed 152
Refresh,ControlIntegrity 165
Refresh,TRXIntegrity 175
RemoteAntennas,FrozenSymbol 159
RemoteCalculation,AtollSvrPriority 163
RemoteCalculation,DetectTimeOut 163
RemoteCalculation,DisablePathlossPerSiteCalculation 174
RemoteCalculation,NumberedServers 163
RemoteCalculation,NumberOfProcessors 171
RemoteCalculation,NumberOfThreadsMicrowave 171
RemoteCalculation,NumberOfThreadsNeighbour 171
RemoteCalculation,NumberOfThreadsPathloss 171
RemoteCalculation,NumberOfThreadsSimulation 171
RemoteCalculation,NumberOfThreadsStudy 171
RemoteCalculation,NumberOfThreadsStudyTile 171
RemoteCalculation,Priority 171
SAMModel,DrawSingleElementPattern 161
Settings,KeepFilterZoneOnRemoveFilter 159
Shadowing,Reliability 169
Shadowing,UseShadowing 168
Shadowing,WithSHOGain 180
Simulation,RandomTotalUsers 173
Site,AddToSiteListOnDuplicate 155
Site,Prefix 147
SitesSymbol,Color 159
SitesSymbol,FontName 159
SitesSymbol,Size 159
SitesSymbol,Symbol 159
StatusBar,ClutterPaneWidth 162
StatusBar,DisplayClutterClass 160
StatusBar,DisplayClutterHeight 160
StatusBar,DisplayZ 160
Studies, 150
Studies,2GTxDiversityGain 178
Studies,AerialStudy 172
Studies,AutoLock 168
Studies,CleanMultiCellManagement 176
Studies,CommentsInLegend 161
Studies,ComputeEvenIfReadOnly 172
Studies,ContinueOnError 169
Studies,CustomStudiesFilteredByTechno 156
Studies,EIRPfromMaxPower 173
Studies,ExportOnlyVisibleLevels 157
Studies,ExposureStudy 161
Studies,MultiBandManagement 176
Studies,MultiplePlotsTipTextLines 160
Studies,NoOverlapOnBestServer 157
Studies,RecomputationWarning 170
Studies,RemoveBadMultiCells 176
Studies,ReportDecimalPlacesAbsolute 157
Studies,ReportDecimalPlacesPercent 157
Studies,SCActivesetMaxSize 185
Studies,ShowIntervalsWithNoCoverageInReport 157
Studies,SpecifyResolutionAfterComputation 170
Studies,UplinkLosses 185
Studies,UseFullHotSpotSurfaceOnReport 157
Studies,UseThresholdForSameLayerPriorities 176
Studies,SelectNullMarginOnly 150
TestMobileData,FloatingPointScramblingCodeSupport 194
TestMobileData,ImportForFilteredTransmittersOnly 194
TestMobileData,NumberOfTestMobileTransmitters 193
TestMobileData,RecalcDist 193
TestMobileData,ShowCoupleInfo 193
TestMobileDataImportFmt,BCCHColumn 193
TestMobileDataImportFmt,BSICColumn 193
TiffExport,PaletteConvention 148
TMP,ExtraServZone 178
Traffic,PerClassPercentagesRelativeToCoverageInReport 155
Transmitter,AutoSynchronizeDisplay 160
Transmitter,ChangeSymbolOnSearch 160
Transmitter,CheckImpactOnRepeaters 153
Transmitter,EmptySymbolWhenInactive 160
Transmitter,First 148
Transmitter,FirstCharSuffix 148
Transmitter,Prefix 148
Transmitter,SuffixIsNum 148
Transmitter,Underscore 148
227
UMTSSimus,MaxReuseFactor 185
WiMAX,ExcludeCPFromUsefulPower 186
WiMAX,InterNeighbourPICollisions 187
WiMAX,ModifiableIEEEParams 185
WiMAX,ReplaceOPUSCwithPUSCUL 187
atoll.inioptionslistedbytopic
AddingExposureAnalysistotheListofMultiRATCoverage
Predictions
Studies,ExposureStudy 161
AddingtheDuplicateSitetotheOriginalSitesSiteList
Site,AddToSiteListOnDuplicate 155
AdjustingtheWorkingoftheProportionalFairScheduler
CDMA,PFSchedulerCQIFactor 183
AllowingNullEntriesinNonnullableCustomFields
Database, AllowNullRecordsForNotNullableCustomFields
165
ApplyingtheABSCollisionProbabilityonInterferencefromRS
LTE,eICIConRS 190
ApplyingTransmitDiversityGainstoReferenceSignals
LTE,UseDivGainOnRS 187
ArchivingDatatoDatabasesUsingTransactions
Database,UseTransaction 167
AutomaticallyCorrectingOutofrangeSubcellValues
GSM,SubcellValueFixMethod 179
AutomaticallyRunningaDatabaseIntegrityCheckatOpenor
Refresh
Database,IntegrityChecker 165
AutomaticallyRunningGSMSubcellAuditatOpenorRefresh
Database,SubCellAuditConsistency 165
Database,SubCellAuditMainValues 166
AveragingtheUplinkNoiseRiseindB
OFDM_SIMU,MeanNRInDB 189
AvoidingOverlappingPixelsinBestServerCoveragePrediction
Studies,NoOverlapOnBestServer 157
BlockingAccesstoACPandAFPModules
License,ACP_GSM 164
License,ACP_LTE 164
License,ACP_UMTS 164
License,ACP_WiMAX 164
License,GSM_AFP 164
License,LTE_AFP 164
License,WiMAX_AFP 164
BlockingAccesstoIEEEParametersinWiMAX
WiMAX,ModifiableIEEEParams 185
BlockingAccesstoMacrosandAddins
GUIUserRights,EnableMacrosAddins 153
BlockingAccesstoTechnologyModules
License,BH 164
License,CDMA 164
License,GSM 164
License,LTE 164
License,Measures 164
License,MW 164
License,TDSCDMA 164
License,UMTS 164
License,WiMAX 164
BSIC,SC,andPCIAllocationin3GPPwithIntertechnologyNeigh
bourConstraints
MultiRAT,AllCodesAllocWithInterRATNeighbours 190
228
Forsk
CalculatingandDisplayingPeakorInstantaneousHSDPA
Throughput
CDMA,HSDPAAvgSimuResults 180
CDMA,HSDPAThroughputPeak 180
CalculatingEIRPfromMaxPowerinSignalLevelPredictions
Studies,EIRPfromMaxPower 173
CalculatingEIRPfromRSEPREinLTESignalLevelPredictions
LTE,EIRPfromRSEPRE 189
ChangingHotSpotReferenceSurfaceinPredictionReports
Studies,UseFullHotSpotSurfaceOnReport 157
ChangingtheDefaultCacheLocationfortheLoadedMapTiles
OnlineMaps,TilesCachePath 159
ChangingtheDisplayforDownlinkSmartAntennaResults
SAModel,DrawSingleElementPattern 161
ChangingtheNetHASPLicenceManagerIdleTimeSetting
License,IdleTime 165
ChangingthePathtoLinkedGeoDataFiles
Geo,FindGeoButtonAlwaysActive 154
ChangingtheRoundingMethodUsedforProfileExtraction
Calculations,RoundAltitudes 172
ChangingtheWeightingFactoroftheEffectiveIntertransmitter
Distance
Neighbours,DistanceAzimutWeightingPercent 174
CheckingDataIntegrityAfterDatabaseUpgradeandData
Refresh
Refresh,ControlIntegrity 165
CheckingDatabaseConsistencyAutomatically
Refresh,TRXIntegrity 175
CompressedModeRestrictingIntercarrierandIntertech
nologyNeighbourAllocation
Neighbours,CompressModeEval 185
ConsideringIntertechnologyInterferenceinGSM
GSM,ExternalIncluded 175
ConsideringOverlappingZonesforIMCalculationBasedon
Traffic
Features,IM_TRAFFIC_OVERLAP 175
CoplanningCalculatingPredictionsinSerialorinParallel
CoPlanning,LinkedPredictionsComputationMode 173
CoplanningCalculatingPredictionsintheCurrentDocument
Only
CoPlanning,ComputeLinkedPredictions 172
CreatinganEventViewerLogFile
EventsObserver,LogPath 149
DeactivatingFrequencyBandFilteringinIMCalculation
IM,FilterByFrequencyBands 178
DeactivatingServiceMaxThroughputDemandDowngradingin
LTE
LTE,ServiceMBRDowngrading 189
DeactivatingUniformDistributionofResources
OFDM,UniformIDDistribution 187
DecreasingCalculationTimeofPathProfiles
MWCalculations,UseProfilesFiles 191
DefiningaDefaultTemplateforMicrowaveLinksCustom
Reports
MWReport,DefaultTemplate 193
DefiningaFixedIntervalBetweenScramblingCodes
PSC,ConstantStep 184
DefiningaGlobalMaximumPathLossCalculationRadius
AT321_AM_E1
Transmitter,MaximumCalculationRadius 175
DefininganOffsetWithRespecttoTheThermalNoise
CDMA,CutOffSimu 182
DefiningDefaultConfigurationFilesforLinkBudgetsReports
MWReport,DesignSummaryCfg 192, 193
MWReport,LinkAnalysisCfg 192
MWReport,LinkInterferenceCfg 192
MWReport,LinksBudgetCfg 192
MWReport,LinksInterferenceCfg 192
MWReport,MultihopAnalysisCfg 192
MWReport,ReflectionAnalysisCfg 192
MWReport,RequiredMarginCfg 192
DefiningOnlineMapURLs
OnlineMaps,Name 158
OnlineMaps,URL 158
DefiningtheBCCHandBSICColumnsforFMTImport
TestMobileDataImportFmt,BCCHColumn 193
TestMobileDataImportFmt,BSICColumn 193
DefiningtheMaximumNumberofTransmittersforReuse
DistanceinAFP
AFP,GlobalDistanceMatrixDegreeUB 178
DefiningtheNumberofIterationsBeforeDowngrading
CDMA,IterBeforeDown 183
DefiningtheParametersfortheDefaultSitesSymbol
SitesSymbol,Color 159
SitesSymbol,FontName 159
SitesSymbol,Size 159
SitesSymbol,Symbol 159
DefiningWebMapServicesServers
WMS,Webmapservicesservers 151
DeletingtheFilteringZoneonRemovingFiltersFromTables
Settings,KeepFilterZoneOnRemoveFilter 159
DetectingandListingDistributedCalculationServers
RemoteCalculation,NumberedServers 163
DisablingAutomaticLockingofCoveragePredictions
Studies,AutoLock 168
DisablingAutomaticRenamingofTransmittersandCells
AutoRename,3GCells 148
AutoRename,Transmitters 148
DisablingCalculationsOverNoDataValuesforDTMandClutter
Classes
FskPropagModels,OptimOnNoData 172
DisablingExternalStorageofNumericalResultsFilesforPredic
tions
Studies,NumericalResults 150
DisablingMacrodiversity(SHO)GainsinCalculations
CDMA,AddPilotSHOGain 180
Shadowing,WithSHOGain 180
DisablingNormalisationofMIF/TABVectorFiles
MITAB,DisableNormalization 155
DisablingParallelCalculationofMonteCarloSimulations
CDMA,ParallelSimulations 171
DisablingSavingandOpeningZIPFiles
GUIUserRights,EnableZip 153
DisablingShieldingFactoronWantedSignalatReceiver
MWCalculations,ShieldingFactorOnWantedSignal 191
DisablingtheMaximumRangeParameter
Perfos,MaxRangeApplied 176
DisallowingCreationofNewDocumentsfromTemplates
GUIUserRights,EnableNewDocFromTemplate 153
Displaying%ofCoveredClutterClasseswithRespecttothe
FocusZoneinReports
Clutter, PerClassPercentagesRelativeToCoverageInReport
155
Displaying%ofCoveredTrafficClasseswithRespecttotheFocus
ZoneinReports
Traffic, PerClassPercentagesRelativeToCoverageInReport
155
DisplayingAdditionalInformationinDriveTestData
TestMobileData,ShowCoupleInfo 193
DisplayingAutomaticAllocationCostValues
PSC,DisplayCostValues 184
DisplayingCoveragePredictionCommentsintheLegend
Window
Studies,CommentsInLegend 161
DisplayingDateandTimeintheEventViewer
EventsObserver,date 160
EventsObserver,milliseconds 160
DisplayingEc/I0ofRejectedMobilesinSimulationResults
CDMA,DisplayEcIoOfRejected 183
DisplayingFilledSymbolsforInactiveTransmittersontheMap
Transmitter,EmptySymbolWhenInactive 160
DisplayingLeadingZerosintheCELL_IDENTITYField
Display,CellIDNbDigits 161
DisplayingObjectsDiscreteValueswithUserdefinedColours
Display,DiscreteValueColoring 162
Display,PaletteColor0 162
DisplayingPathLossCalculationDetailsintheEventViewer
Pathlosses,DisplayIndividualSuccessOrFailure 150
Pathlosses,DisplayInvalidityCause 150
Pathlosses,DisplayOverallSuccessOrFailure 150
DisplayingPixelswithZeroThroughputinCoveragePredictions
OFDM,DisplayThroughputZero 189
DisplayingUplinkTotalLossesinCoveragebySignalLevel
Studies,UplinkLosses 185
DuplicatingLinkedPathLossMatricesonSaveAs
Perfos,ConfirmStoreExternPrivLosFilesOnCopy 149
Perfos,StoreExternPrivLosFilesOnCopy 149
EmbeddingPathLossesinNewDocuments
Pathlosses,EmbeddedByDefault 169
EnablingandDisablingPersitePathLossMatrixCalculations
RemoteCalculation,DisablePathlossPerSiteCalculation 174
EnablingCoveragePredictionsofConnectionProbabilities
CDMA,MinUsersPerBin 181
CDMA,UseStudyCnxProba 181
EnablingDisplayofSignalsperSubcarrierPointAnalysisinLTE
LTE,DisplaySignalsPerSCInPtA 186
EnablingEventViewerMessagesforMapInfoFileImport/Export
MITAB,EnableMessages 156
EnablingIndoorCoverageinCalculations
ClutterParams,IndoorActivity 169
EnablingNotificationforDonorTransmitterParameterModifica
tions
Transmitter,CheckImpactOnRepeaters 153
EnablingOrthogonalityFactorinPilotEC/NTCalculationin
HSDPA
CDMA,OrthoInCPICH 181
EnablingPartialRefreshfromRecentlyUpgradedDatabases
229
MajorVersionChange,
Forsk
EnablePartialRefreshInMigration
167
EnablingShadowingMargininCalculations
Shadowing,UseShadowing 168
EnablingtheSupportforMultibandTransmitters
Studies,CleanMultiCellManagement 176
Studies,MultiBandManagement 176
Studies,RemoveBadMultiCells 176
Enabling/DisablingPasswordPromptatArchive
Database,PromptOnArchive 166
EstimatingRequiredandUsedMemorySizeforUMTSSimula
tions
CDMA,PredictSimuMemorySize 172
EventsObserver,ShowAddinAccessDeniedMsg 149
ExcludingCyclicPrefixEnergyinWiMAXandWiFiSignalLevel
Calculation
WiMAX,ExcludeCPFromUsefulPower 186
ExcludingFilteredTransmittersfromtheListofNeighbours
Neighbours,ExcludeFilteredCellsFromNeighbourLists 173
ExcludingtheAdjacentChannelOverlapfromtheAFPCostFunc
tions
OFDM_AFP,AdjacentProtection 188
ExcludingVectorsfromImportedKML/KMZFiles
Import,LoadKMLVectors 152
ExportingBMP,TIF,andPNGFileswithaTABReferenceFile
RasterExport,GeorefWithTAB 154
ExportingCoveragePredictionPolygonsinTextFormat
Studies,EnableLBS 151
ExportingOnlyVisibleValueIntervalLayersofCoveragePredic
tions
Studies,ExportOnlyVisibleLevels 157
Exporting/ImportingVectorDatawithaDisplayConfiguration
File
Geo,VectorDisplayConfigurationCompanionFile 154
ExtendingtheAllowedValueRangeforC/IandReception
Thresholds
GSM,WideRangeSubcellThresholds 179
ExtendingtheMaximumIntersiteDistancetoRepeatersand
RemoteAntennas
Neighbours,RepeaterInterSiteDistanceInAlloc 174
FilteringPredictionsbyTechnologyWhenReadingtheXML
StudiesFile
Studies,CustomStudiesFilteredByTechno 156
ForcingNeighbourSymmetryOnlyInsideFocusZone
Neighbours,ForceSymmetryInFocusZone 173
ForcingtheRealIntersiteDistanceThreshold
Neighbours,RealInterSiteDistanceCondition 174
HidingAdvancedAFPParameters
AFP,SimpleUserGUI 176
HidingInformationDisplayedintheStatusBar
StatusBar,DisplayClutterClass 160
StatusBar,DisplayClutterHeight 160
StatusBar,DisplayZ 160
HidingtheRec.ITURP.5305Method
MWCalculations,HIDE_REC530_5 191
HidingtheTechnologyNameintheTitleBar
DocTitle,UseTechnoName 162
HidingtheTRXIndex
GSM,TRXIndexHidden 179
230
HidingViolationsBetweenLowImportanceGSMNeighboursin
AFPResults
GSM,MinNeighbourImportanceInAFPResults 177
HidingViolationsBetweenNonSynchronisedMALsMAIOsin
AFPResults
GSM,ShowNonSynchSFHViolationsInAFPResults 177
IdentifyingTransmitter,Repeater,andRemoteAntenna
CoverageAreas
Studies,AerialStudy 172
IgnoringInterNeighbourPhysicalCellIDCollisioninLTE
LTE,InterNeighbourIDCollisions 187
IgnoringInterNeighbourPreambleIndexCollisioninWiMAX
WiMAX,InterNeighbourPICollisions 187
ImportingDriveTestDataforActiveandFilteredTransmitters
Only
TestMobileData,ImportForFilteredTransmittersOnly 194
ImportingDriveTestDatawithScramblingCodesasIntegers
TestMobileData, FloatingPointScramblingCodeSupport
194
ImprovingPointAnalysisPerformance
Perfos,PtAnalysisMargin 152
Perfos,PtAnalysisNbServersMax 152
ReceptionTab,NumberOfTransmitterDisplayed 152
IncludingCyclicPrefixEnergyinLTESignalLevelCalculation
LTE,ExcludeCPFromUsefulPower 186
IncludingPixelfreeRangesinCoveragePredictionReports
Studies,ShowIntervalsWithNoCoverageInReport 157
IncreasingtheMaximumPrintingResolution
Print,MaxDPI 149
IncreasingtheWidthoftheClutterDescriptionPaneintheStatus
Bar
StatusBar,ClutterPaneWidth 162
KeepingSeparateWorkandMasterPathLossDirectories
Database,OverwriteSharedFolderPath 167
KeepingtheAssignedNeighbourswhicharenotSymmetrised
withtheReferenceTransmitter
Neighbours,DoNotDeleteSymmetrics 174
KeepingTransmitterSymbolsFromChangingonSearch
Transmitter,ChangeSymbolOnSearch 160
LinkingtheSitesFolderinCoplanning
CoPlanning,LinkSites 154
LoadingVectorFilesDynamically
Import,LoadVectors 152
Loading,Activating,andSettingAddinsasVisible
Addins,AddinName 158
MakingAtollCaseSensitiveforDatabaseImportFromPlanet
PlanetImport,SensitiveCase 166
MakingRedundantFieldsintheTransmittersTableReadonly
GSM,CanEditTRXInfoAtTXLevel 178
MakingtheAntennaAdditionalElectricalDowntiltAccessible
Antenna,REDTDisplay 162
ManagingCarriageReturnsinImportedTXTandCSVFiles
Export,NewLineEscapeSequence 159
MappingAtollCoordinateSystemswithMapInfo/ESRIVector
Files
MITAB, Coordinate system definition in the header file
150
ModifyingtheDefaultDatabaseConnectionTimeout
AT321_AM_E1
Database,CommandTimeout 166
ModifyingtheDefaultDetectionTimeout
RemoteCalculation,DetectTimeOut 163
ModifyingtheDefaultFormatsofSiteandTransmitterNames
Site,Prefix 147
Transmitter,First 148
Transmitter,FirstCharSuffix 148
Transmitter,Prefix 148
Transmitter,SuffixIsNum 148
Transmitter,Underscore 148
ModifyingtheResolutionfortheLOSAreaCalculationArounda
Site
LOSArea,ResolutionMultFactor 169
ModifyingtheThresholdforImportantViolationsinAFP
GSM,AdjRedColorThreshPercent 177
GSM,CoRedColorThreshPercent 177
OpeningExportedXLSFilesAutomaticallyinMSExcel
Export,AutoOpenWithExcel 153
PerformingCalculationsinReadOnlyDocuments
Studies,ComputeEvenIfReadOnly 172
PrioritisingIndividualIntersiteDistancesinNeighbourImpor
tanceCalculation
Neighbours,CandidatesMaxDistanceInImportanceCalcula
tion 174
ReadingExactAltitudesFromtheDTM
Calculations,UseSiteAltitude 170
RecalculatingDistancesofPointsFromThereServingCellsat
Import
TestMobileData,RecalcDist 193
RefreshingtheDisplayAutomaticallyWhenaNewStationis
Dropped
Transmitter,AutoSynchronizeDisplay 160
RenamingOPUSCZonetoPUSCULinWiMAX
WiMAX,ReplaceOPUSCwithPUSCUL 187
RestrictingtheListofPredictionsforCreatingSectorTrafficMaps
Studies,SelectNullMarginOnly 150
SelectingSCandPNOffsetAllocationStrategiesAvailableinthe
GUI
CDMA,CodeStrategies 184
SelectingtheInterferenceMatricesUsedDuringtheAFP
AFP,WorstCaseIM_FskAfp 177
SelectingtheLogo2CheckBoxbyDefaultinPrintSetup
Print,LogoFooterChecked 156
SettingaCommonDisplayResolutionForAllCoveragePredic
tions
Studies,SpecifyResolutionAfterComputation 170
SettingaDefaultValuefortheCellEdgeCoverageProbability
Shadowing,Reliability 169
SettinganAlarmfortheLicenceEndDate
License,TimeBombNotice 164
SettingPDCCHto100%LoadedinLTEInterferenceCalculations
LTE,ApplyDLLoadOnPDCCHInterf 188
SettingPrecisionoftheRasterisationProcess
Rasterization,Improve 182
Rasterization,MaximumSurf 183
Rasterization,Precision 182
Rasterization,SurfRatio 183
SettingtheAntennaPatternsModellingMethod
Antenna,AngleCalculation 168
Antenna,CatalogVerticalDiagramOrientation 168
Antenna,InterpolatePatternEvenIfOnlyOneDiagram 168
Antenna,InterpolatePatternIndB 168
SettingtheBestServerCalculationMethodinSamePriorityHCS
Layers
Studies,UseThresholdForSameLayerPriorities 176
SettingtheCalculationMethodforHSPDSCHCQI
CDMA,CQIDeltaWithPower 181
SettingtheDefaultBSICFormat
BsicFormat,DefaultValue 175
SettingtheDisplayPrecisionofFloatingPointValues
Grids,NbDecimals 153
SettingtheDistributedCalculationServerPriority
RemoteCalculation,AtollSvrPriority 163
SettingtheMaximumASSizeforSCInterferencePrediction
Studies,SCActivesetMaxSize 185
SettingtheMaximumNumberofLinesinCoveragePrediction
ToolTips
Studies,MultiplePlotsTipTextLines 160
SettingtheMaximumNumberofRejectionsforHSDPAMobiles
CDMA,HSDPAMaxRejections 182
SettingtheMaximumNumberofRejectionsforMobiles
CDMA,MaxRejections 182
SettingtheMaximumULReuseFactorforHSUPAUsersNoise
RiseEstimation
UMTSSimus,MaxReuseFactor 185
SettingtheMinimumATLFileSizeRequiringCompression
Compression,StartSizeInMB 158
SettingtheNumberofParallelProcessorsandThreads
RemoteCalculation,NumberOfProcessors 171
RemoteCalculation,NumberOfThreadsMicrowave 171
RemoteCalculation,NumberOfThreadsNeighbour 171
RemoteCalculation,NumberOfThreadsPathloss 171
RemoteCalculation,NumberOfThreadsSimulation 171
RemoteCalculation,NumberOfThreadsStudy 171
RemoteCalculation,NumberOfThreadsStudyTile 171
SettingtheNumberofTransmittersperDriveTestDataPath
TestMobileData,NumberOfTestMobileTransmitters 193
SettingthePowertoUseforIntracellInterferenceinHSDPA
CDMA,PmaxInIntraItf 181
SettingthePrecisionfortheAntennaPatternVerificationat
Import
Antenna,PrecisionTimes10 152
SettingthePrecisioninCoveragePredictionReports
Studies,ReportDecimalPlacesAbsolute 157
Studies,ReportDecimalPlacesPercent 157
SettingthePrioritiesforGUIandCalculations
RemoteCalculation,Priority 171
SettingtheResolutionofPopulationMapsinCoveragePredic
tionReports
Population,ReportResolution 156
SettingtheSignforKClutterWhenImportingDataFromPlanet
EV
PlanetImport,ChangeKclutterSign 166
SettingtheTIFFColourConvention
TiffExport,PaletteConvention 148
SettingtheTransmissionDiversityGain
Studies,2GTxDiversityGain 178
SettingtheTypeofDatabaseBeingUsed
231
Database,ExclusiveProvider 167
SettingUplinkNoiseRiseControlParametersinLTE
LTE,NR_CONTROL_MARGIN_MIN 189
LTE,ULNRControlMethod 189
LTE,ULNRControlPrecision 189
SolvingAlignmentIssueinGeneratedReports
MWReport,tab 192
SpecifyingtheLocationoftheAcp.iniFile
ACP,iniFile 194
StartingTRXIndexesat1
GSM,FirstTRXIndex 179
StoppingCalculationsonError
Studies,ContinueOnError 169
Suppressing3GCellNameCarrierSuffixes
3GCells,NoSuffixIfUniqueCarrier 180
SwitchingBacktotheOldBestServerDeterminationMethod
CDMA,MultiBandSimu 184
SwitchingBetweenSynchronisedandUnsynchronisedInterfer
enceCalculationMethods
LTE,SameItf_PDSCH_RS_PDCCH 188
SynchronisingPrivateandSharedPathLossMatrices
Pathlosses,FullResyncPrivShared 156
TakingSecondOrderNeighboursintoAccountintheAFP
OFDM,SecondNeighbours 188
UpdatingA>>BandB>>AProfilesinRealtime
232
Forsk
MWCalculations,UpdateOppositeHop 191
UsingaUniqueSymbolforRemoteAntennas
RemoteAntennas,FrozenSymbol 159
UsingDefaultMethodforCalculatingUnavailability
MWReport,RainBelow0001 192
UsingOldMinC/IValues
Compatibility,MWEquipment_CIMIN 191
UsingOnlyBearersCommonBetweentheTerminalsandCells
Equipment
OFDM,UseCommonBearersOnly 186
UsingOnlyVisibleClutterClassesinInterferencePrediction
Reports
Clutter,OnlyVisibleClassesInInterferenceReport 155
UsingOnlyVisibleGeoDatainPredictionReports
Geo,ReportObeysVisibility 154
UsingPoissonDistributioninMonteCarloSimulations
Simulation,RandomTotalUsers 173
UsingtheABSPatternsThroughoutaCellinLTE
LTE,UseABSonCellEdgeOnly 190
WarningAboutPredictionValidityWhenDisplayOptionsare
Modified
Studies,RecomputationWarning 170
atoll.inioptionslistedINIoption
Transmitter,MaximumCalculationRadius 175
AT321_AM_E1
233
HeadOffice
7ruedesBriquetiers
31700Blagnac,France
Tel:+33562747210
Fax:+33562747211
AT321_AM_E1
USOffice
ChinaOffice
200SouthWackerDriveSuite3100
Chicago,IL60606,USA
Tel:+13126744800
Fax:+13126744847
Suite302,3/F,WestTower,JiaduCommercialBuilding,
No.66JianzhongRoad,TianheHiTechIndustrialZone,
Guangzhou,510665,P.R.ofChina
Tel:+862085538938 Fax:+862085538285
www.forsk.com
February2014

Atoll 3.2.1 Administrator Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Atoll 3.2.1 Administrator Manual

Uploaded by

Copyright:

Available Formats

Version3.2.

Atoll 3.2.1 Administrator Manual

AllowingNullEntriesinNonnullableCustomFields ...................................................... 165

DisablingMacrodiversity(SHO)GainsinCalculations ................................................... 180

;Use the IPX protocol - Enabled or Disabled

;Use the NETBIOS protocol - Enabled or Disabled

;Use the TCP/IP protocol - Enabled or Disabled

;(a)IP address of the floating licence server

;(b)Send TCP or UDP packets

;Use TCP/IP broadcast - Enabled or Disabled

The relationshipsin thedatabase schema figures are represented by arrows. These

The data structure of an Atoll document not connected to any database is

YoucanclicktheViewlogsunderStatustoviewthehistoryofpastpurges(seeFigure 5.12onpage 57).

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

10. InMicrosoftAccess2003andearlier,selectFile >GetExternalData >LinkTables.InMicrosoftAccess2007andlater,

InAtoll,selectDocument >DataAudit >IntegrityCheck.

InAtoll,selectDocument >DataAudit >UndefinedRecordCheck.

InAtoll,selectDocument >DataAudit >DuplicateRecordCheck.

x coordinate of the centre of the upper-left pixel.

y coordinate of the centre of the upper-left pixel.

x size in metre of a pixel.

y size in metre of a pixel.

Number of columns in the image.

Number of rows in the image.

Number of bytes per band per row.

Total number of bytes of data per row.

Type of data read (in addition to the length)

Real value to be added to the read value (Vread)

Scaling factor to be applied to the read value

So,wehave V = Vread valuescale + valueoffset

Value corresponding to NO DATA

<Atoll_XML_Config Atoll_File_System="UMTS" Atoll_File_Technology="CDMA"

<s:AttributeType name='ALTITUDE' rs:number='4' rs:nullable='true'

Co-polar Horizontal Diagram

Co-polar Vertical Diagram

2 0 0 360 0 0 1 0 2 0.1 1 0 360 0 0 1 0.1 0

Co-polar Horizontal Diagram

Cross-polar Horizontal Diagram

Co-polar Vertical Diagram

Cross-polar Vertical Diagram

2 0 0 360 0 0 1 0 2 0.1 1 0 360 0 0 1 0.1

Co-polar H-V Diagram

Co-polar H-H Diagram

Cross-polar H-V Diagram

Cross-polar H-H Diagram

Co-polar V-V Diagram

Co-polar V-H Diagram

Cross-polar V-V Diagram

Cross-polar V-H Diagram

4 0 1 0 360 0 0 1 0.5 ... 0 0 0 360 0 0 1 0.5 ...

Tab separated format. Commented lines start with #.

C/I results do not incorporate power offset values.

| Threshold | C/I >= Threshold |

# Version 1.1, Tab separated format. Commented lines start with #.

Tab separated format. Commented lines start with #.

|Identifier |calculation|calculation|coverage |coverage |

# Version 1.1, Tab separated format. Commented lines start with #.

C/I results do not incorporate power offset values.

{C/I Probability} values

BCCH,TCH-10 1 -9 0.996 -6 0.976 -4 0.964 -1 0.936

BCCH,TCH-10 1 -9 0.996 -6 0.976 -4 0.972 -1 0.948

BCCH,TCH-10 1 -9 0.996 -6 0.98 -3 0.948 0 0.932

BCCH,TCH-9 1 -6 0.972 -3 0.964 -2 0.96 0 0.94

# Calculation Results Data File.