Professional Documents
Culture Documents
Administrator Manual
AT332_AM_E0
AT332_AM_E0
AT332_AM_E0
Table of Contents
1.1
Supported Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2
1.3
1.4
1.5
1.5.1
1.5.2
1.5.3
1.5.4
1.5.5
2.1
2.2
2.3
2.4
2.5
2.6
2.7
3.1
3.1.1
3.1.2
3.1.3
3.2
3.3
4.1
4.1.1
4.1.1.1
4.1.1.2
4.1.2
4.1.3
4.2
4.2.1
4.2.2
4.2.3
5.1
5.2
5.3
5.4
5.4.1
5.4.2
5.5
5.5.1
5.5.2
5.5.3
5.6
5.6.1
5.6.2
5.6.3
5.7
5.8
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
Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Appendix 1: Advanced Customisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Appendix 2: Setting Up Databases for Co-planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Multi-user Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.1
6.2
6.2.1
6.2.2
6.2.3
6.2.4
6.2.5
6.2.6
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
Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Appendix 1: Checking Data Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Appendix 2: Database Regionalisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Appendix 3: Calculating Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Appendix 4: Path Loss Matrices From Different Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
7.1
7.1.1
7.1.2
7.1.3
7.1.4
7.2
Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
7.3
8
4
Forsk 2016
AT332_AM_E0
8.1
8.1.1
8.1.1.1
8.1.1.2
8.1.2
8.1.3
8.1.4
8.1.5
8.2
8.2.1
8.2.2
8.2.3
8.3
8.3.1
8.3.2
8.3.3
8.4
8.4.1
8.4.1.1
8.4.1.2
8.4.2
8.4.3
8.4.4
8.4.5
8.5
8.5.1
8.5.2
9.1
9.2
9.3
9.4
Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
9.5
9.6
9.7
9.8
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
9.9
9.10
9.11
9.12
9.13
9.14
10
10.1
10.1.1
10.1.2
10.1.3
10.1.4
10.1.5
10.1.6
10.1.7
10.1.8
10.1.9
10.1.10
10.1.11
10.1.12
Forsk 2016
152
154
155
156
159
10.2
10.2.1
10.2.2
10.2.3
10.2.4
10.2.5
159
160
161
161
162
163
10.3
10.4
11
11.1
Atoll Initialisation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1
General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.1
Managing Memory Allocation per Session in Atoll 64-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.2
Changing the Default Metre-to-Feet Conversion Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.3
Changing the Default Mile-to-Metre Conversion Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.4
Modifying the Default Formats of Site and Transmitter Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.5
Disabling Automatic Renaming of Transmitters and Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.6
Setting the TIFF Colour Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.7
Creating an Event Viewer Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.8
Displaying Insufficient Permission Messages in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.9
Increasing the Maximum Printing Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.10
Copying Externalised Calculation Results on Save As. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.11
Disabling External Storage of Numerical Coverage Prediction Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.12
Exporting Prediction Coordinates using the Projection Coordinate System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.13
Restricting the List of Predictions for Creating Sector Traffic Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.14
Displaying Path Loss Calculation Details in the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.15
Mapping Atoll Coordinate Systems with MapInfo/ESRI Vector Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.16
Exporting Coverage Prediction Polygons in Text Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.17
Defining Web Map Services Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.18
Improving Point Analysis Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.19
Excluding Vectors from Imported KML/KMZ Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.20
Combining Imported Zone Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.21
Setting the Precision for the Antenna Pattern Verification at Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.22
Exporting Selected Data Tables to XML Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.23
Keeping the Original List Separator when Exporting in CSV Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.24
Opening Exported XLS Files Automatically in MS Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.25
Disabling Creation of New Documents from Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.26
Blocking Access to Macros and Add-ins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.27
Disabling Saving and Opening ZIP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.28
Hiding the Propagation Models Folder in the Parameters Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.29
Forbidding Shared Antenna Modification in Multi-RAT Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.30
Enabling Notification for Donor Transmitter Parameter Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.31
Setting the Display Precision of Floating Point Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.32
Changing the Path to Linked Geo Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.33
Exporting/Importing Vector Data with a Display Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.34
Using Only Visible Geo Data in Prediction Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.35
Exporting BMP, TIF, and PNG Files with a TAB Reference File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.36
Exporting BIL Files with a PRJ Projection File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.37
Co-Planning: Linking the Sites Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.38
Disabling Normalisation of MIF/TAB Vector Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.39
Customising Performance Optimisation when Exporting Vector Files in TAB Format . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.40
Adding the Duplicate Site to the Original Sites Site List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.41
Moving Sites without Moving Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.42
Real Altitude versus DTM Altitude in Sites Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.42.1
Duplicate/Moved Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.42.2
New Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.43
Using Only Visible Clutter Classes in Interference Prediction Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.44
Displaying % of Covered Clutter Classes w. r. t. the Focus Zone in Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1.1.45
Displaying % of Covered Traffic Classes w. r. t. the Focus Zone in Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
167
167
167
168
168
169
169
170
170
170
170
170
171
171
171
171
172
172
173
173
173
173
174
174
174
174
174
174
175
175
175
175
175
175
176
176
176
176
176
177
177
177
177
177
177
178
178
178
178
AT332_AM_E0
11.1.1.46
11.1.1.47
11.1.1.48
11.1.1.49
11.1.1.50
11.1.1.51
11.1.1.52
11.1.1.53
11.1.1.54
11.1.1.55
11.1.1.56
11.1.1.57
11.1.1.58
11.1.1.59
11.1.1.60
11.1.1.61
11.1.1.62
11.1.1.63
11.1.1.64
11.1.1.65
11.1.1.66
11.1.1.67
11.1.1.68
11.1.1.69
11.1.1.70
11.1.1.71
11.1.1.72
11.1.2
11.1.2.1
11.1.2.2
11.1.2.3
11.1.2.4
11.1.2.5
11.1.2.6
11.1.2.7
11.1.2.8
11.1.2.9
11.1.2.10
11.1.2.11
11.1.2.12
11.1.2.13
11.1.2.14
11.1.2.15
11.1.2.16
11.1.2.17
11.1.2.18
11.1.2.19
11.1.2.20
11.1.2.21
11.1.3
11.1.3.1
11.1.3.2
11.1.3.3
11.1.4
11.1.4.1
11.1.4.2
11.1.4.3
11.1.4.4
11.1.4.5
11.1.5
11.1.5.1
11.1.5.2
11.1.5.3
11.1.5.4
11.1.5.5
11.1.5.6
11.1.5.7
11.1.5.8
11.1.5.9
11.1.5.10
11.1.5.11
11.1.5.12
11.1.5.13
11.1.5.14
11.1.5.15
11.1.5.16
11.1.5.17
11.1.6
11.1.6.1
11.1.6.2
11.1.6.3
11.1.6.4
11.1.6.5
11.1.6.6
11.1.6.7
11.1.6.8
11.1.6.9
11.1.6.10
11.1.6.11
11.1.6.12
11.1.6.13
11.1.6.14
11.1.6.14.1
11.1.6.14.2
11.1.6.15
11.1.6.16
11.1.6.17
11.1.6.18
11.1.6.19
11.1.6.20
11.1.6.21
11.1.6.22
11.1.6.23
11.1.6.24
11.1.6.25
11.1.6.26
11.1.6.27
11.1.6.28
11.1.6.29
11.1.6.30
11.1.6.31
11.1.6.32
11.1.6.33
11.1.6.34
11.1.6.35
11.1.6.36
11.1.6.37
11.1.7
11.1.7.1
11.1.7.2
11.1.7.3
11.1.7.4
11.1.7.5
11.1.7.6
11.1.7.7
11.1.7.8
11.1.7.9
11.1.7.10
11.1.7.11
11.1.7.12
11.1.7.13
11.1.7.14
11.1.7.15
11.1.7.16
Forsk 2016
193
193
193
194
194
194
194
195
195
195
195
195
196
196
196
196
197
197
197
197
197
198
198
198
199
199
199
199
199
200
200
200
200
200
201
201
201
201
201
201
202
202
202
202
202
203
203
203
203
203
204
204
204
204
204
204
205
205
205
206
206
206
206
206
207
207
207
AT332_AM_E0
11.1.7.17
11.1.7.18
11.1.7.19
11.1.7.20
11.1.7.21
11.1.7.22
11.1.8
11.1.8.1
11.1.8.2
11.1.8.3
11.1.8.4
11.1.8.5
11.1.8.6
11.1.8.7
11.1.8.8
11.1.8.9
11.1.8.10
11.1.8.11
11.1.8.12
11.1.8.13
11.1.8.14
11.1.8.15
11.1.8.16
11.1.8.17
11.1.8.18
11.1.8.19
11.1.8.20
11.1.8.21
11.1.8.22
11.1.8.23
11.1.8.24
11.1.9
11.1.9.1
11.1.9.2
11.1.9.3
11.1.9.4
11.1.9.5
11.1.9.6
11.1.9.7
11.1.9.8
11.1.9.9
11.1.9.10
11.1.9.11
11.1.9.12
11.1.9.13
11.1.9.14
11.1.9.15
11.1.9.16
11.1.9.17
11.1.9.18
11.1.9.19
11.1.9.20
11.1.9.21
11.1.9.22
11.1.9.23
11.1.9.24
11.1.9.25
11.1.9.26
11.1.9.27
11.1.9.28
11.1.9.29
11.1.9.30
11.1.10
11.1.10.1
11.1.10.2
11.1.11
11.1.11.1
11.1.11.2
11.1.11.3
11.1.11.4
11.1.11.5
11.1.11.6
11.1.11.7
11.1.11.8
11.1.11.9
11.1.11.10
11.1.11.11
11.1.11.12
11.1.11.13
11.1.12
11.1.12.1
11.1.12.2
11.1.12.3
11.1.12.4
11.1.12.5
11.1.12.6
11.1.12.7
Forsk 2016
222
222
222
223
223
223
223
224
224
224
224
224
224
224
225
225
225
225
225
226
11.2
ACP Initialisation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
11.2.1
Managing ACP Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
11.2.2
ACP GUI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
11.2.2.1
Default Settings of the Optimisation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
11.2.2.2
Default Settings of the Optimisation > Cost Control Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
11.2.2.3
Default Settings of the Optimisation > Advanced Cost Control Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
11.2.2.4
Automatically Creating Custom Zones on the Optimisation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
11.2.2.5
Default Settings of the Objectives Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
11.2.2.6
Default Settings of the Reconfiguration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
11.2.2.7
Default Settings of the Reconfiguration > Sites vertical tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
11.2.2.8
Defining the Inter-site Distance in Co-located Site Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
11.2.2.9
Defining the Inter-antenna Distance in Co-located Transmitter Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
11.2.2.10
Custom Columns on Reconfiguration > Sites Vertical Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
11.2.2.11
Default Settings of the Reconfiguration > Transmitters Vertical Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
11.2.2.12
Custom Columns on the Reconfiguration > Transmitters/Remotes Vertical Tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
11.2.2.13
Default Settings of the Optimisation > EMF Exposure Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
11.2.2.14
Default Settings of the Optimisation > Multi-Storey Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
11.2.2.15
Controlling Antenna Pattern Smoothing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
11.2.2.16
Default Settings of the Antenna Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
11.2.2.16.1
Global Antenna Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
11.2.2.16.2
Patterns Vertical Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
11.2.2.16.3
Physical Antenna Vertical Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
11.2.2.17
Defining the Antenna Masking Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
11.2.2.18
Defining Reconfiguration Values Using Custom Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
11.2.2.18.1
Defining Reconfiguration Values for Transmitters, Repeaters, and Secondary Antennas Using Custom
Fields242
11.2.2.18.2
Defining Reconfiguration Values for Cells Using Custom Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
11.2.2.18.3
Defining Reconfiguration Values for Sites Using Custom Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
11.2.2.18.4
Defining Reconfiguration Values for Antennas Using Custom Fields . . . . . . . . . . . . . . . . . . . . . . . . . 244
11.2.2.19
Defining Site Class Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
11.2.2.19.1
Defining Automatic Site Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
11.2.2.19.2
Automatic Assignment of Site Classes in the ACP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
11.2.2.20
Defining the Appearance of a Running Optimisation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
11.2.2.20.1
Defining the Colours in the Analysis Maps on the Quality Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
11.2.2.20.2
Other Components of the Optimisation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
11.2.2.21
Defining the Appearance of ACP Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
11.2.2.22
Defining New Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
11.2.2.23
Defining the Functionality of the Commit Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
11.2.2.24
Defining the Appearance of the Overlay Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
11.2.2.25
Defining the Appearance of the Graph Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
11.2.2.26
Defining the Default Font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
11.2.2.27
Exporting Optimisation Results in XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
11.2.3
ACP Core Engine Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
11.2.3.1
Log File Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
11.2.3.2
Calculation Thread Pool Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
11.2.3.3
Number of Threads Used for Propagation Model Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
10
AT332_AM_E0
11.2.3.4
11.2.3.5
11.2.3.6
11.2.3.7
11.2.3.8
11.2.3.9
11.2.3.10
11.2.3.11
11.2.3.12
11.2.3.13
11.2.3.14
11.2.3.15
11.2.3.16
11.2.3.17
11.2.4
11.2.5
11.2.5.1
11.2.5.2
11
12
Forsk 2016
AT332_AM_E0
About Atoll
Atoll is a 64-bit multi-technology wireless network design and optimisation platform. Atoll is open, scalable, flexible, and
supports wireless operators throughout the network life cycle, from initial design to densification and optimisation.
Atoll includes integrated single RAN multiple RAT network design capabilities for both 3GPP (GSM/UMTS/LTE) and 3GPP2
(CDMA/LTE) technology streams. It provides operators and vendors with a powerful native 64-bit framework for designing
and optimising current and future integrated multi-technology networks. Atoll supports multi-technology HetNets, small cell
planning, and Wi-Fi offloading.
Atoll Microwave is a complete backhaul and microwave link planning solution based on the leading Atoll platform, which
includes a high performance GIS and advanced data and user management features. Atoll Microwave can share its site database with Atoll radio planning and optimisation modules, thus allowing easy data consistency management across the operator organisation.
Atolls integration and automation features help operators smoothly automate planning and optimisation processes through
flexible scripting and SOA-based mechanisms. Atoll supports a wide range of implementation scenarios, from standalone to
enterprise-wide server-based configurations.
If you are interested in learning more about Atoll, please contact your Forsk representative to inquire about our training solutions.
About Forsk
Forsk is an independent company providing radio planning and optimisation software solutions to the wireless industry since
1987.
In 1997, Forsk released the first version of Atoll, its flagship radio planning software. Since then, Atoll has evolved to become
a comprehensive radio planning and optimisation platform and, with more than 7000 installed licenses worldwide, has
reached the leading position on the global market. Atoll combines engineering and automation functions that enable operators to smoothly and gradually implement SON processes within their organisation.
Today, Forsk is a global supplier with over 450 customers in 120 countries and strategic partnerships with major players in the
industry. Forsk distributes and supports Atoll directly from offices and technical support centres in France, USA, and China as
well as through a worldwide network of distributors and partners.
Since the first release of Atoll, Forsk has been known for its capability to deliver tailored and turn-key radio planning and optimisation environments based on Atoll.
To help operators streamline their radio planning and optimisation processes, Forsk provides a complete range of implementation services, including integration with existing IT infrastructure, automation, as well as data migration, installation, and
training services.
Getting Help
The online help system that is installed with Atoll is designed to give you quick access to the information you need to use the
product effectively. It contains the same material as the Atoll 3.3.2 User Manual.
You can browse the online help from the Contents view, the Index view, or you can use the built-in Search feature.
You can also download manuals from the Forsk web site at:
http://www.forsk.com/MyForskAccount/
13
4. In the Print Topics dialog box, select what you want to print:
If you want to print a single topic, select Print the selected topic.
If you want to print an entire section, including all topics and sections in that section, select Print the selected
heading and all subtopics.
5. Click OK.
To read PDF manuals, download Adobe Reader from the Adobe web site at:
http://get.adobe.com/reader/
Hardcopy manuals are also available. For more information, contact to your Forsk representative.
Forsk US
For North and Central America, contact the Forsk US support team:
Forsk China
For China, contact the Forsk China support team:
Opening Hours: Monday to Friday 9.00am to 5.30pm (GMT+08:00) Beijing, Chongqing, Hong Kong, Urumqi.
14
Chapter 1
Getting Started
This chapter covers the following topics:
16
AT332_AM_E0
1 Getting Started
Atoll is an open, scalable, and flexible multi-technology network design and optimisation platform that supports wireless
operators throughout the network life cycle, from initial design to densification and optimisation. Atoll supports a wide range
of implementation scenarios, from single-user standalone to enterprise-wide server-based configurations using distributed
and multi-threaded computing.
This manual explains how to install, configure, and deploy Atoll and how to set up back-end databases and manage users in
a multi-user environment. In this chapter, the following are explained:
If the computer on which you wish to install and run Atoll 64-bit already has
Microsoft Office installed, you must upgrade it to Microsoft Office 64-bit (version
2010 SP1 or newer).
If you do not have Microsoft Office installed, you can download and install the
Microsoft Access Database Engine 64-bit redistributable (version 2010 SP1)
needed by Atoll 64-bit from the Forsk support website.
Note: Installing Microsoft Office 64-bit or the Microsoft Access Database Engine 64-bit
requires uninstalling any 32-bit Microsoft Office components that may be installed on
the computer.
Supported Operating Systems for Atoll 32-bit
17
Forsk 2016
The physical location of databases varies according to the type of the database. The following table shows where the database
must be installed:
a.
Database
Server
Client computer
Microsoft Access
No
Yesa
Yes
No
Oracle
Yes
It is possible to work with an Atoll document connected to a Microsoft Access database even if Microsoft Access is not
installed on the computer.
Atoll is installed and run directly on the user workstation and all the core software and drivers are provided with the
Atoll installer program.
The following data is stored locally: coverage prediction files, geographic data, and user projects.
18
A USB port must be available on the user workstation to plug a fixed license key dongle.
AT332_AM_E0
a.
Processor
RAM
8 GB or more
Storage
Operating System
Windows 7
Windows 8/8.1 Professional or Enterprise
Atoll is installed and run directly on user workstations and all the base software and drivers are provided with Atoll.
The following data is stored on user workstations: coverage prediction files, geographic data, and user projects.
The user licenses are managed locally (fixed licenses) or from a server (floating licenses):
A USB port must be available on the user workstation to plug a fixed license key dongle.
The nethasp.ini file must be available on the workstation to provide information on accessing a floating license server
through the network.
A connection with the central database is required during synchronisation operations, to exchange between users.
If you are working with an Oracle database, you must install the relevant Oracle clients on the user computers.
Processor
Atoll Workstation
Atoll Database
8 GB or more
8 GB or more
RAM
Storage
512 GB
a (SSD recommended)
19
Forsk 2016
Operating System
a.
b.
Atoll Workstation
Atoll Database
Windows 7
Windows 8/8.1 Professional or Enterprise
An asynchronous connection is required with the central database for data exchange between users.
The user licenses are managed through the network and a limited bandwidth (300+ kbps per user) is required between servers
and client workstations for satisfactory performance.
If you are working with an Oracle database, you must install the relevant Oracle clients on the user computers.
Processor
RAM
8 GB or more
Storage
Operating System
Connectivity
Thin Client
Configuration
Remote Desktop
Citrix XenApp 6.5 or later
Virtualisation
RDBMS
a.
20
AT332_AM_E0
Must be accessible to all the user computers / Citrix servers on the network in order to provide license tokens for Atoll
sessions.
Must have a steady and reliable network connection with user computers / Citrix servers.
Must have the HASP license manager installed and running. For more information, see "Working with Floating
Licenses" on page 43.
Must have the floating license key plugged in.
Can be one of the application servers.
21
22
Forsk 2016
Chapter 2
Atoll and Component
Installation
This chapter covers the following topics:
24
AT332_AM_E0
You need administrator rights for installing Atoll and its components.
If you work with fixed licenses, you must unplug the key before the installation and wait for the installation to finish
before plugging it back in.
Disable UAC (User Account Control) for the following versions of Microsoft Windows. If you are installing Atoll on
other versions of Microsoft Windows, proceed to step 1.
To disable UAC:
a. Go to Control Panel > User Accounts.
b. Select Change User Account Control settings. The User Account Control Settings dialog box appears.
c. Choose Never notify.
d. Click OK.
If you are installing Atoll 64-bit, make sure that the Microsoft Access Database Engine 64-bit is already installed on the
computer. Microsoft Access Database Engine 64-bit is included in Microsoft Office 64-bit, and is also available as a free
redistributable Microsoft Windows component from the Forsk support website.
If the computer on which you wish to install and run Atoll 64-bit already has Microsoft Office installed, you must
upgrade it to Microsoft Office 64-bit (version 2010 SP1 or newer). This will automatically install the Microsoft Access
Database Engine 64-bit.
If you do not have Microsoft Office installed, you can download and install the Microsoft Access Database Engine 64bit redistributable needed by Atoll 64-bit from the Forsk support website.
Installing Microsoft Office 64-bit requires uninstalling any 32-bit Microsoft Office
components that may be installed on the computer.
If you are installing Atoll 32-bit, the default installation folder is:
C:\Program Files\Forsk\Atoll in the 32-bit versions of Microsoft Windows, or
C:\Program Files (x86)\Forsk\Atoll in the 64-bit versions of Microsoft Windows
If you are installing Atoll 64-bit, the default installation folder is:
C:\Program Files\Forsk\Atoll in the 64-bit versions of Microsoft Windows
25
Forsk 2016
26
AT332_AM_E0
If you work with fixed licenses and you installed the Driver for Fixed Licence Keys, restart the computer. Restarting
the computer is necessary for the driver to work.
If you work with fixed licenses, plug in the fixed license key.
On the versions of Microsoft Windows that support UAC (disabled before the installation), run Atoll once using an
administrator account and with UAC disabled when the installation is complete.
If the following files do not already exist in the installation folder, empty ones are
created by the setup:
[Atoll installation folder]\Atoll.ini
[Atoll installation folder]\AntennaImport.ini
[Atoll installation folder]\CWMeasurementsImport.ini
[Atoll installation folder]\DriveTestDataImport.ini
[Atoll installation folder]\coordsystems\Favourites.cs
These files are not removed when Atoll is uninstalled.
If you have installed Atoll on a Citrix server, you must publish it to make it accessible
to users.
To restrict access to the Atoll installation folder, you can assign read/write access rights
to this folder to administrators and read-only rights to end users.
27
Forsk 2016
Visual C++ must be installed before installing the Atoll C++ development kit.
Disable UAC (User Account Control) for the following versions of Microsoft Windows. If you are installing Atoll C++
development kit on other versions of Microsoft Windows, proceed to step 1.
To disable UAC:
a. Go to Control Panel > User Accounts.
b. Select Change User Account Control settings. The User Account Control Settings dialog box appears.
c. Choose Never notify.
d. Click OK.
1. Run the Atoll C++ development kit setup.
The setup program uses a wizard interface, with a step-wise description of the installation. You can,
If you are installing the Atoll C++ development kit with Atoll 32-bit, the default installation folder is:
C:\Program Files\Forsk\Atoll in the 32-bit versions of Microsoft Windows, or
C:\Program Files (x86)\Forsk\Atoll in the 64-bit versions of Microsoft Windows
If you are installing the Atoll C++ development kit with Atoll 64-bit, the default installation folder is:
C:\Program Files\Forsk\Atoll in the 64-bit versions of Microsoft Windows
28
AT332_AM_E0
/SILENT, /VERYSILENT
Instructs the setup to be silent or very silent. When the setup is silent the wizard window is not displayed but the
installation progress window is. When a setup is very silent the installation progress window is not displayed.
Everything else is normal. So, for example, error messages during installation are displayed, and also the startup
prompt.
If the setup is silent and it requires to restart the computer, but the /NORESTART option is not used (see below), it will
display a Reboot now? message box. If it is very silent it will reboot without asking.
/NOCANCEL
Prevents the user from cancelling the installation by disabling the Cancel button and ignoring clicks on the Close
button. Useful along with /SILENT or /VERYSILENT.
/NORESTART
Instructs the setup not to restart the computer even if necessary.
/SAVEINF="file name"
Instructs the setup to save installation settings to the specified file. Use quotes if the file name contains spaces.
/LOADINF="file name"
Instructs the setup to load the settings from the specified file after having checked the command line. This file can be
prepared using the /SAVEINF command as explained above. Use quotes if the file name contains spaces.
/DIR="x:\folder name"
Overrides the default installation folder displayed on the Select Destination Location wizard page. Use quotes if the
folder name contains spaces.
/GROUP="folder name"
Overrides the default start menu folder name displayed on the Select Start Menu Folder wizard page. Use quotes if
the folder name contains spaces.
/LOG="file name"
Causes the setup to create a log file listing file installation and actions taken during the installation process. This can
be helpful for troubleshooting. For example, if you suspect a file is not being installed as it should be, the log file will
tell you if the file was actually skipped and why. Use quotes if the filename contains spaces. If the file cannot be
created, the setup will abort with an error message.
/SVRACCOUNT="domainname\username"
The domain name and user name for installing the distributed calculation server.
/SVRPASSWD=password
29
Forsk 2016
/TYPE=type name
Overrides the default setup type. The setup type names are:
For full and compact setup types, the /COMPONENTS parameters are ignored.
Atoll: Atoll
Export to Google Earth add-in: "Addins\GoogleEarth"
Driver for fixed license keys: RainbowDongle
Distributed calculation server: Atoll_Server
Atoll Management Console: AMC
Example: To install Atoll, the distributed calculation server, and the driver for fixed license keys:
/COMPONENTS="Atoll,Atoll_Server,RainbowDongle"
General add-ins:
Export to Google Earth (installed with Atoll)
Multistorey Prediction
Easy Location Converter
ArcView Grid ASCII Import
Multi-RAT Converter
Difference Plot
Update Sites With Geo Data
FCC Boundaries
Incidence Angle Footprint
Database add-ins:
History Module
Scenario Manager
Geo Selector
30
AT332_AM_E0
Timeout: This is delay after which an unresponsive macro is stopped. To disable the macro timeout, set it to 0. If
you leave the timeout empty, a value of 24 days is used. The default value is 60 seconds.
UTF-8 Encoding: Select this option if the macro file contains non-ASCII characters (for example: "" or "").
6. Click OK. The loaded macro appears under Macros in the Add-ins and Macros dialog box.
To run a macro in Atoll:
1. In Atoll, select Tools > Add-ins and Macros. The Add-ins and Macros dialog box appears.
2. Under Macros, expand the folder containing the macro you want to run.
3. Select the macro you want to run. The Run button becomes active.
4. Click the Run button.
Lists of macros available in Atoll can be stored in user configuration files. Macros listed in the user configuration files are
added to Atoll when the user configuration files are loaded. For more information, refer to "Contents of User Configuration
Files" on page 136.
To remove a macro from Atoll:
1. In Atoll, select Tools > Add-ins and Macros. The Add-ins and Macros dialog box appears.
2. In the list of VBS files, select the one corresponding to the macro you want to remove.
3. Click Delete.
Other commands available in the Add-ins and Macros dialog box are:
Macros:
Predictions Slideshow
Display Site Picture and Antenna Documentation
Show Hide Repeaters and Remote Antennas
Save Part of Document
GSM to UMTS
GSM to LTE
UMTS to LTE
CDMA2000 to LTE
Show in Google Maps Street View
Scripts:
Update Pathloss Matrices
Radio Data Import-Export
Propagation Models Import-Export
CW Measurements Import-Export
Test Mobile Data Import-Export
31
Forsk 2016
-log "logfilename"
Instructs Atoll to create a log file containing all the messages listed in the Events tab. This can be helpful for
troubleshooting. "logfilename" is the full path and file name of the log file inside quotes.
-Ini "inifilename"
Instructs Atoll to load the specified initialisation file when run. This can be used to override the default loading of the
Atoll.ini file located in the Atoll installation folder. "inifilename" is the full path and file name of the initialisation file
inside quotes.
-Cfg "cfgfilename"
Instructs Atoll to load the specified user configuration file when run. This can be used to override the default loading
of the Atoll.cfg file located in the Atoll installation folder. "cfgfilename" is the full path and file name of the user
configuration file inside quotes.
-Stu "studiesfilename"
Instructs Atoll to load the specified studies XML file when run. This can be used to override the default loading of the
studies XML file located in "C:\Temp\studies.xml". "studiesfilename" is the full path and file name of the studies XML
file inside quotes.
-Provider providername
Instructs Atoll to use the mentioned providername to access the database server:
Provider
Atoll version
providername
Microsoft Access
32-bit
64-bit
Microsoft.Jet.OLEDB.4.0
Microsoft.ACE.OLEDB.12.0
SQL Server
32/64-bit
SQLOLEDB
32/64-bit
OraOLEDB.Oracle
-DataSource server
Instructs Atoll to access the mentioned database server using the given provider.
-UserId username
Instructs Atoll to access the mentioned Oracle database server using the mentioned username.
-Password password
Instructs Atoll to access the mentioned Oracle database server using the mentioned password.
-Project projectaccount
Instructs Atoll to access the mentioned Oracle database server using the mentioned projectaccount.
The keywords Provider, Password, UserId, DataSource, and Project are case sensitive.
32
It is recommended to install new Windows updates. However, it is also recommended to go through the description
of each update patch to see whether it might have a negative effect on your system or network. Pay special attention
to updates and patches related to networking.
It is also recommended to keep the Windows updates uninstall folders, named "$NtUninstall...", under the Windows
folder, in case you have to uninstall a certain patch. Some of the update patches might require uninstall folders of
older patches to be available for their own installation.
AT332_AM_E0
Fixed license keys cannot be used with "Server"-type operating systems. Therefore, you should not install the driver
for fixed license keys on:
The current version of the driver for fixed license keys (Sentinel SuperPro driver) installed with Atoll is the 7.6.3.
If Atoll is unable to access the fixed license key, even after a clean installation, try reinstalling the Sentinel SuperPro
driver manually. The drivers setup program (SPI763.exe) is copied by the setup to the Sentinel subfolder in the Atoll
installation folder if you selected the Driver for Fixed Licence Keys component during the installation. You can also
download the driver from http://www.safenet-inc.com.
Restart the computer when asked by the setup. Restarting the computer is necessary for the driver for fixed license
keys to work.
If you get a protection key error message, verify that the fixed license key is correctly plugged in and that the license
has not expired.
In case the fixed or the floating license key becomes unavailable, Atoll will ask the users currently accessing the key
to save their open documents before Atoll closes. If the key becomes available again, Atoll will let the users continue
working.
Do not change the computers date.
Citrix
If you have installed Atoll on a Citrix XenApp server, you must publish it to make it available to the users.
You can get information about Atoll (version, build, type of license and remaining time before expiration, etc.) by
selecting Help > About Atoll in the main menu in Atoll.
You can download the latest versions of Atoll from the Forsks support website by logging in with the user name and
password provided to you by Forsk.
The Atoll User Manual and other documents are available on the installation CD. More documents are available for
download on the Forsks support website.
The support website also offers you:
For full contact details for customer support, see back cover.
Acknowledgement
Atoll uses Inno Setup for installation. For more information, see http://www.jrsoftware.org/isinfo.php.
33
34
Forsk 2016
Chapter 3
Distributed Calculation
Servers
This chapter covers the following topics:
36
AT332_AM_E0
37
Forsk 2016
Where binPath should correspond to the location of the AtollSvr.exe file, DisplayName is the name of the service as it
will appear in the Windows list of services.
3. To start the service created in step 2, type and run the following command:
net start AtollCalcSvr1
4. Repeat steps 2 and 3 for each new instance of the service that you want to run by replacing "AtollCalcSvr1" and "Atoll
DCS1" by "AtollCalcSvr2" and "Atoll DCS2", respectively, and so on.
You can verify that the new service instances appear in the list of services through Control Panel > Administrative Tools >
Services.
You can also run additional instances of the distributed calculation service by double-click the AtollSvr.exe file located in the
Atoll installation folder. For each new instance of the service, a command prompt window opens. To stop an additional,
manually run service, close the corresponding command prompt window.
38
AT332_AM_E0
39
40
Forsk 2016
Chapter 4
License Management
This chapter covers the following topics:
42
AT332_AM_E0
4 License Management
Atoll can be used on:
Computers with fixed license keys plugged in to USB ports on the computers themselves.
Computers connected to a license server with a floating license key plugged in to a physical USB port on the server or
a network-attached USB hub.
The driver for fixed license keys can be installed at the same time as Atoll. For more information, see "Atoll and Component
Installation" on page 25.
The software for managing floating license keys must be installed on a server accessible to the computers on which Atoll is
going to be used. For more information, see "Working with Floating Licenses" on page 43.
For information on the Atoll license management utility, see "Using the Atoll License Manager" on page 46.
HASP floating license key: Hardware key programmed with the numbers of tokens available for each module.
HASP license manager: Interface between Atoll and the floating license key.
HASP device driver: Interface between the HASP license manager and floating license key.
HASP monitor (optional): Enables you to check the number of used and available tokens.
nhsrv.ini file: Installed on the floating license server to enable computers to use tokens.
nethasp.ini file: Installed on the computers to facilitate access to the floating license server.
nhsrv.ini and nethasp.ini files are used if they exist. Default settings are used otherwise.
The HASP device driver, the HASP license manager, and the floating license key must be installed on the server.
Newer versions may be available than those provided on the Atoll installation disk, therefore it is recommended to download
the latest HASP licensing products from the SafeNet web site.
HASP hardware keys are supported by Windows 2000 Server and Windows Server 2003
with HASP License Manager 8.20 or above.
43
Forsk 2016
Do not plug the floating license key into the server before installing the device driver.
Wait for the HASP license manager setup to indicate when to plug in the key.
If the floating license server is protected by a firewall, port 475 must be open for the
UDP protocol.
In case the fixed or the floating license key becomes unavailable, Atoll will ask the
users currently accessing the key to save their open documents before Atoll closes. If
the key becomes available again, Atoll will let the users continue working.
The floating license key can become unavailable and a key protection error message
appears in Atoll if the license management server is heavily loaded. Check if there is
any application running on the server that might be causing the problem. If this is the
case, remove any such application from memory. If this is not possible, try changing
the latency associated to the HASP License Manager in accessing the key.
You can optionally install the HASP Monitor on the floating license server, or on one
or several other computers, to monitor the token allocation and retrieval activity. The
HASP Monitor displays the list of computers using tokens available on the floating
license key.
44
AT332_AM_E0
Once the HASP license manager has been installed, the floating license key must always
remain plugged in.
= enabled
= enabled
= 475
45
Forsk 2016
NH_NETBIOS = Disabled
NH_TCPIP = Enabled
[NH_TCPIP]
NH_SERVER_ADDR = 3CT000J
NH_USE_BROADCAST = Disabled
a.
Remove the NH_SESSION and NH_SEND_RCV entries from the nethasp.ini file if these
exist.
These fields define the timeout delays depending to the network. They can be useful
in slow networks and should be set only if required.
46
AT332_AM_E0
Under Selected key the following information is available for the selected key:
Number: Unique key number given by the key provider. This number must be communicated to Forsk, when
requested, for reprogramming the license key.
Type: The type of key, Fixed license or Floating license.
Reference: Unique floating license key reference provided by Forsk. This number must be communicated to Forsk,
when requested, for reprogramming the license key. This reference is also printed on the sticker on the key.
Location (server): Name of the floating license management server on which the floating license key is plugged.
Under Modules and licenses, all the Atoll modules available on the selected key are listed along with the numbers
of license tokens of each.
Under Number of licenses, the Modify buttons are reserved for Forsk use only.
Under Dates and durations, the following dates and durations are available:
License start
License end
Duration of validity
Time bomb
A purchased Atoll license corresponds to a particular Atollversion. There is no time limit on using this version.
However, yearly maintenance must be purchased in order to access newer versions with updates and bug fixes.
When you purchase maintenance, Forsk reprograms your license keys to allow access to new versions.
The time bomb date is the end date for maintenance. When the time bomb date passes, the license key stops
working. You can then choose to either purchase maintenance for the next year, and benefit from the new
features and bug fixes, or have the license key reprogrammed without maintenance for the next year, in which
case users can continue working with the existing version.
47
Forsk 2016
Atoll can inform you about the approaching time bomb date 30 days in advance. This alert can be configured
through the Atoll.ini file.
Do not attempt to modify the time bomb settings on the fixed license key. Contact Forsk
support.
Do not change the computers date.
Under Profile signature, the PID (profile signature or ID) is the encrypted description of the user rights available
on the key. Each key has a unique PID.
Under Current profile summary, all of the above information is summarised.
48
Chapter 5
Managing Databases
This chapter covers the following topics:
"Appendices" on page 72
50
AT332_AM_E0
5 Managing Databases
In Atoll, you can work with standalone documents, i.e., documents without any back-end database, or with documents
connected to databases. Standalone documents are more portable, however a back-end database is required when working
in a multi-user environment. In multi-user environments, several users work on the same project and a central data storage
is necessary for keeping the data modifications made by a team of radio planning and optimisation engineers.
Atoll enables you to create databases, upgrade them to newer versions, archive and refresh data with databases, manage and
resolve data conflicts, and create and work with multi-level databases.
A database server can store one or more databases. For example, a GSM, a UMTS, and a microwave links database can be
stored on the same database server using the same RDBMS (Oracle, for example).
In this chapter, the following are explained:
The following table lists the types of fields used in Atoll database templates, their sizes, and the equivalent field types and
sizes in different RDBMS:
Atoll
Oracle Equivalent
Field Type
Length
Field Type
Length
Length
Microsoft
Access
Equivalent
Float
FLOAT
32
real
Single
Double
FLOAT
64
float
Double
Integer
NUMBER
11
int
Long Integer
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
OLE Object
Binary
Variable
CLOB
> 2000
BLOBc
Variable
a.
Lengths for these fields are specified in parentheses in the database structure tables.
b.
c.
51
Forsk 2016
Custom fields, as well as user-defined default values and choice lists for standard and custom fields, are stored in the
CustomFields table.
Adding Custom Fields to Data Tables
Do not add custom fields to data tables in the default document templates. It is
recommended to add them in copies of the default templates so that the original database
structure remains intact.
If you add custom fields to a default template of your current Atoll version (N-1), and forget
to add the same in the template of the next version (N), the Atoll Management Console of
the next version (N) will consider that these fields were intentionally removed by the
administrator. It will delete such custom fields from the database during upgrade.
Custom fields can be added to data tables at different stages keeping in mind that:
Custom fields added directly to the Atoll database templates (MDB files), using Microsoft Access 2003, will be
available in all new Atoll documents created from that template. A new database created by exporting such a
document will also contain these custom fields.
Custom fields added to an Atoll document through the Atoll user interface will not be automatically added to the
corresponding Atoll database template. However, a new database created by exporting such a document will contain
these custom fields. For more information on adding custom fields to Atoll documents through the user interface, see
the User Manual.
Custom fields added to an Atoll database will be available in all new Atoll documents created from that database.
User Interface
Caption
TABLE_NAME
52
Description
Database name of the data table that contains the field
COLUMN_NAME
Name
DEFAULT_VALUE
Default value
CHOICE_LIST
Choice list
CAPTION
Legend
Caption of the field as it will appear in the user interface (optional but
recommended)
GROUP_NAME
Group
CHOICE_TYPE
Restricted
DISPLAY_TYPE
Read-only
AT332_AM_E0
Custom fields are for information only and are not taken into account in calculations. You
can find these fields on the Other Properties tab of an objects Properties dialog box.
User Interface
Caption
TABLE_NAME
Description
Database name of the data table that contains the field
COLUMN_NAME
Name
DEFAULT_VALUE
Default value
For floating point default values, make sure that all the users use the same decimal
symbol.
User Interface
Caption
TABLE_NAME
Description
Database name of the data table that contains the text field
COLUMN_NAME
Name
CHOICE_LIST
Choice list
For example, you can replace the default choice list available for the SUPPORT_INFO field in the Sites table with a different
list of options corresponding to the different types of towers and pylons that may exist in your network.
You can enter one of the choice list items in the DEFAULT_VALUE in order to set a
default value for the text field.
For custom text fields, you can set the CHOICE_TYPE to 1 if you want the custom text
field to only accept values listed in the choice list. By default, CHOICE_TYPE is
considered to be 0 meaning that users are allowed to enter values other than those
defined in the choice list.
Oracle
Microsoft SQL Server
The Atoll Management Console can be installed with Atoll. For more information, see "Atoll and Component Installation" on
page 25.
53
Forsk 2016
You can run the Atoll Management Console from the Windows Start menu program group or by double-clicking the AMC.msc
file in the management subfolder of the Atoll installation folder. The Atoll Management Console runs using the Microsoft
Management Console environment.
When the Atoll Management Console is run for the first time, you must register your database server in order to have the
databases installed on the server to be available in the Atoll Management Console.
To register a database server:
1. Open the the Atoll Management Console.
2. In the left pane, right-click Database under Administration Atoll. The context menu appears.
3. Select Register a New Server from the context menu. The Data Link Properties dialog box appears.
54
AT332_AM_E0
) or
The right pane lists the databases available on the connected database server currently selected in the left pane. The current
user can be the owner of one of the listed databases; his name appears between parentheses in the title bar after the name
of the database owner. One Oracle user can create and own one database. Therefore, for each new database, you must create
a new Oracle user who will own the new database.
The following details are available for databases created or upgraded using the Atoll Management Console:
Name: name of the database preceded by an icon which indicates whether the database corresponds:
to the current version of Atoll ( ), or
to a previous version of Atoll not yet upgraded to the current version of Atoll (
The databases corresponding to other major releases of Atoll are not listed.
If the database server does not contain any database corresponding to the current/
previous major release of Atoll, no database is listed.
Network: technology of the network modelled by the database (3GPP or 3GPP2 in case of multi-RAT).
Shared Pathloss Directory: path to the shared path loss folder.
General: This tab displays the Name, Description, Owner, Type, and Version of the database.
Statistics: This tab displays the number of records in each table of the database.
55
Forsk 2016
You must have administrator rights to the database and to the server for creating new
databases.
5. Click Next. The Name the database and specify a network type page appears.
6. Enter a Name for the new database and select the Network type. The Network type can be one of the database
templates installed with Atoll.
56
AT332_AM_E0
Atoll and the Atoll Management Console must have the same version. This means that
the Atoll Management Console can create databases based on the database templates
installed with Atoll of the same version.
7. Click Next. The Specify units and coordinate systems page appears.
8. Select a Transmission power unit and a Reception threshold unit.
9. Under Coordinate systems, select a Cartographic projection system and the System to be used in the database.
10. Click Next. The Ready to create database page appears. This page provides a summary of the selected parameters.
11. Click Execute. The Atoll Management Console creates the new database with the defined parameters on the selected
database server.
A database created using the Atoll Management Console contains an ATOLL_ADMIN table with the following structure:
Field
Type
Description
NAME
Text (50)
DESCRIPTION
Text
(255)
ATOLL_VERSION
Text (10)
ATOLL_BUILD
Integer
ATOLL_DBTYPE
Text (10)
ATOLL_TEMPLATE
Text (50)
DBSCHEMA
Memo
Among other uses, the ATOLL_ADMIN table is used to speed up the database upgrade to the next version. This table stores
the data required by the Atoll Management Console for database upgrade.
Databases created with Atoll, instead of the Atoll Management Console, and databases that have never been upgraded using
the Atoll Management Console contain a smaller ATOLL_ADMIN table, with just the NAME, ATOLL_VERSION, and
ATOLL_BUILD fields. Upgrading such databases using the Atoll Management Console can take a long time because the Atoll
Management Console must search for the data required for the upgrade in the whole database.
For more information on upgrading databases, see "Upgrading Existing Databases" on page 58.
All the tables in a database created using the Atoll Management Console (except the COORDSYS and UNITS tables) contain a
non-modifiable, integer DB_RECORD_ID field. This field is used to store the ID of every record in the table. It is not added to
Microsoft Access databases.
57
Forsk 2016
Field
Type
Description
NAME
Text (50)
ATOLL_VERSION
Text (10)
ATOLL_BUILD
Integer
Before creating the database, make sure that you have defined the coordinate
systems and units in the source document.
Before creating the database, make sure that you have added any required custom
fields. Custom fields of the source document are created in the new database.
If you want to add a custom field to the data structure after you have created the
database, you will have to add it directly in the database and not through Atoll.
Custom fields added to a database are available to users connected to the database
when they create a new Atoll document from the database or refresh an existing one.
Do not skip a major version of Atoll. For example, if you are currently using Atoll 2.8.x,
you should first upgrade the database to Atoll 3.1.x before upgrading to Atoll 3.2.x.
Upgrading your database will be simpler if you do not skip a major version. If you skip
or have skipped an intermediate major version, you must upgrade your database
twice in order to make it compatible with the new version.
If you are upgrading a database which was neither created nor already upgraded (at
least once) using the Atoll Management Console, see "Upgrading Databases for the
First Time" on page 59 first.
The Microwave Radio Links template now supports Radio Series. Similar microwave
radios belong to the same radio series. In order to organise the microwave radios
(microwave equipment) in radio series before the database upgrade:
1. In Atoll 2.8.x, add a custom field named FAMILY of type Text (50) to the
MWEquipments table.
2. Enter the radio series names in this field for each radio, i.e., group the radios of
the same series under the same radio series name in the FAMILY field.
Without this manual organisation of the microwave radios into radio series, the database
upgrade will create one radio series for each microwave radio.
To upgrade a database using the Atoll Management Console:
1. In the Atoll Management Console window, in the right pane, right-click the database that you want to upgrade. The
context menu appears.
2. Select Upgrade Database. The Database Upgrade Wizard dialog box appears with the current database version and
the version to which the database will be upgraded.
3. Click Next. The Name the database page appears.
4. Enter a Name and description for the database.
5. Click Next.
The Database Upgrade Wizard reads the database to determine the Atoll database template using which it was
created. If there is more than one template corresponding to the network, select the template to be used for the
upgrade and click Next.
The Atoll Management Console upgrades the database.
58
AT332_AM_E0
If some of the tables in a database have been replaced by views, the Database
Upgrade Wizard asks to select the views to upgrade. Select the views that you want
the Atoll Management Console to upgrade and click Execute.
If, for example, the definition of a view is given by the condition:
Select Field1, Field2 from Table1 where (Condition1);
The wizard first upgrades the schema of Table1 and then upgrades the definition of
the view. The upgraded definition will take the newly added fields into account.
When you upgrade a 3GPP Multi-RAT database, the Atoll Management Console adds
any missing tables to the database. For example, a database created by exporting a
3GPP Multi-RAT document containing only GSM contains only GSM tables. When
upgraded, the Atoll Management Console will add the UMTS and LTE tables to the
database as well.
Obsolete fields in the data structure are automatically deleted from the database by the Atoll Management Console during
the upgrade.
If you use the Atoll Management Consoles history management tool, you must repair
the upgraded database in order to continue using this tool. For more information, see
"Managing Data Modifications History" on page 67.
Once the database has been upgraded to the new version,
1. Install the new Atoll versions for the end-users, and
2. Ask all the end-users to fully refresh data in their Atoll documents from the database.
When users open their existing documents in the new Atoll version, they are asked whether they want to upgrade the
documents data structures to the new version or to disconnect the documents from the database. On selecting the
upgrade option, Atoll upgrades the document data structures to make them compatible with the new version.
It is possible to upgrade an existing database manually (not recommended) by adding and deleting tables and fields as
required by the new version. For information on manually upgrading a database, see "Upgrading Databases Manually" on
page 60.
59
Forsk 2016
60
Add the ATOLL_ADMIN table to the database. For more information on this table,
see "Creating a New Database Using the Atoll Management Console" on page 55.
For LTE databases, rename the smart antenna models and equipment as follows:
Delete existing smart antenna equipment ("Optimum Beamforming Smart
Antenna") from the SmartAntennas table.
Delete existing smart antenna model ("Optimum Beamformer") from the
SmartAntennasModels table.
Create a new smart antenna equipment ("Conventional Beamforming Smart
Antenna") in the SmartAntennas table. Set the smart antenna model for this
equipment to "Conventional Beamformer."
AT332_AM_E0
A new record is added to the networks table for each technology added to the database.
61
Forsk 2016
The probability of human error increases with the number of users who can modify data.
The probability of conflicts increases with the number of users accessing the database.
The performance is reduced because the entire network is loaded every time a user accesses the database.
For routine city-wide planning, an end-user does not require the entire countrys database to be loaded.
Project databases can be created using filters on sites, thus allowing users to work with regional databases. A possible scenario
is depicted in the figure below:
62
AT332_AM_E0
63
Forsk 2016
10. Click Next. The Atoll Management Console creates the new project database with the defined parameters on the
selected database server.
The project database will have the type PROJECT listed in the Atoll Management Console window.
64
Field
Type
Description
NAME
Text (50)
MASTER_CONNECTION
Text
(255)
MASTER_DBSCHEMA
Text (50)
SEL_METHOD
Short
Data extraction method used to select the sites to include in the project
database
SEL_PARAM
Text
(255)
SEL_PGON
Memo
AT332_AM_E0
You can view the details stored in the ATOLL_ADMIN_PRJ table in the project database properties. To view the above details
of a project database:
1. In the right pane, right-click the project database in the list. The context menu appears.
2. Select Properties. The database Properties dialog box appears.
3. The Properties dialog box contains three tabs:
General tab: The General tab displays the Name, Description, Owner, Type, and Version of the database.
Project Database tab: Under Source master database, the Project Database tab displays the Connection settings
to and the Owner of the master database. Under Site selection, this tab displays the site filtering Method and
Settings used for creating the project database.
Statistics tab: The Statistics tab displays the number of records in each table of the project database.
The project database contains a copy of all the original tables of the master database. The names of the original tables are
prefixed with "O_". For example, the ANTENNAS table of the master database is stored in the project database under the
name O_ANTENNAS. The COORDSYS and UNITS are not copied to the project database because their contents cannot be
different from those of the master database.
All the tables in a project database contain a non-modifiable, integer O_RECORD_ID field and a Boolean O_CHANGED field.
The O_RECORD_ID field is used to locate records in the master database. Modified records are archived in master database
using the O_RECORD_ID of the project database and DB_RECORD_ID of the master database. The O_CHANGED field is set to
TRUE for records modified in the project database.
Select a site list in Filter by site list to filter the pending changes by a site list.
Click Archive All to archive all the changes to the master database.
Select the check boxes to the left of the changes that you want to archive and click Archive Sel. to archive only the
selected changes.
Click Undo All to overwrite all the changes in the project database with data from the master database.
Select the check boxes to the left of the changes that you want to undo and click Undo Sel. to overwrite only the
selected changes in the project database with data from the master database.
Select the Check conflicts check box to see whether conflicts occurred during the archive.
A conflict occurs when the project database contains a different original value of a field than the current value of
the field in the master database. This can occur if the master database has been updated with changes from
another source and the project database has not yet been refreshed with data from the master database.
65
Forsk 2016
Select Refresh unmodified data only to keep any changes in the project database and only update unmodified
records from the master database. During the refresh, the Atoll Management Console will reload records from
the master database for which the O_CHANGED field is FALSE in the project database.
Select Cancel your changes and reload all data from the master database to overwrite modified and unmodified
records in the project database with data from the master database.
1. Click OK. The project database is refreshed with data from the master database.
Database Level:
Users trying to create a new Atoll document from a database are provided a list of available databases to select from.
The list can be limited to a few databases based on the user connection properties (log in).
Table Level:
For consistency reasons, all the tables available in an Atoll database must be readable by all the users who have access
to the database. However, write access (INSERT, DELETE, UPDATE) can be granted on a limited number of tables.
Column Level:
Similar to table level, all the columns of all the tables in an Atoll database must be readable and selectable by all the
users who have access to the database. Different write permissions can be granted for columns of the tables. For
example, custom fields can be assigned read and write permissions without restrictions.
Row Level:
Row level permissions can be set by defining custom views on Atoll tables. Access to these views can be based on user
connection properties (log in), on external table references, or on the geographic locations of sites (e.g., through
polygons, or when using the spatial features of databases).
66
AT332_AM_E0
All of these permissions can be set as regular SELECT, INSERT, UPDATE, and DELETE privileges on database objects. Triggers
can also be used to prevent users making certain actions on the database.
Different permissions for different users can be granted directly or through database roles. Database roles enable you to
define permission templates, which can then be assigned to existing or new users of the database.
You can use the Atoll Management Console for defining user access rights to database tables and elements in the Atoll GUI.
For more information on managing user access rights, see "Managing User Accounts and Access Rights in Oracle" on page 81.
Tracked Tables
UMTS HSPA
LTE
WiMAX/Wi-Fi
3GPP
3GPP2
You can, however, enable or disable history management for table as required (see "Enabling/Disabling Data Modifications
History Management" on page 68 for more information). If you want, you can also purge old data modifications history (see
"Purging Old Data Modification Records" on page 69 for more information).
The history management tool is available for Oracle databases. The following section describes how to set up the history
management tool using the Atoll Management Console.
Type
Description
HISTORY_ID
Integer
MODIFIED_BY
Text (50)
MODIFIED_DATE
Date
HISTORY_STATUS
Text (10)
The above fields are also added to all the tracked tables in order to store information about the latest modification. Therefore,
opening any tracked table, you can see when a record was last modified, by whom, and the type of modification.
67
Forsk 2016
68
AT332_AM_E0
69
Forsk 2016
70
AT332_AM_E0
None: select this option if you do not want data modification records to be purged.
Keep only the last N records: if you select this option, enter the number of most recent records you want to keep.
All older records will be purged.
Keep only records of N last months: if you select this option, enter the number of months prior to which all
records will be purged.
Keep creation and deletion records: select this check box if you want to want to keep all the creation and deletion
records, independent of the above options.
5. If you wish to purge records now, click the Run now button.
6. If you wish to schedule regular purges, under Scheduling, define the purge frequency:
a. Period: Select the frequency of the scheduled regular purges.
b. Day: Select the day of the week (Monday to Sunday), month (1 to 28), or year (1 to 365), depending on the purge
periodicity defined in Period, on which the scheduled purges will run.
c. Time: Enter the time, i.e., the hour (0 to 23) and minutes (0 to 59) at which scheduled purges will run.
Scheduled regular purges will delete all the data modification records according to the criteria defined under
Conditions.
7. Set the Off/On slider to On to activate the scheduled purges.
Setting the Off/On slider to Off allows you to suspend scheduled purges while keeping the scheduler settings.
8. Click the Update button to store the schedule parameters.
The current purge status is shown under Status. Status information includes:
You can click the View logs under Status to view the history of past purges (see Figure 5.13 on page 70).
9. Click the Close button.
Scheduled regular purges are programmed as a scheduled job in Oracle using the DBMS_SCHEDULER.create_job function. The
following SQL string generates scheduled job:
"BEGIN DBMS_SCHEDULER.create_job ("
"job_name => 'AHMS_%s',"
"job_type => '%s',"
"job_action => '%s',"
"start_date => SYSTIMESTAMP,"
"repeat_interval => '%s',"
"end_date => NULL,"
"enabled => %s,"
"comments => '%s'); END;"
Here:
Parameter
Description
job_name
AHMS_<schema_name>
job_type
PLSQL_BLOCK
job_action
start_date
SYSTIMESTAMP
repeat_interval
end_date
NULL
enabled
comments
Custom character string with codes for easy identification of the scheduler type
71
Forsk 2016
5.9 Appendices
The first appendix shows how to use SQL for Oracle database customisation and the second appendix shows how to set up
databases for co-planning taking the example of GSM and UMTS MS Access databases.
72
AT332_AM_E0
The error message "ORA-01402: view WITH CHECK OPTION - clause violation" appears if
you try to archive a record that does not match the project.
Co-planning GSM, UMTS, and LTE using a unified multi-technology data structure, i.e., working with a 3GPP Multi-RAT
document.
Co-planning any two radio technologies (GSM, UMTS, LTE, CDMA2000, TD-SCDMA, and WiMAX), with two separate
data structures, by linking Atoll documents.
In terms of database, while the first approach provides an integrated multi-technology co-planning environment, the second
requires setting up sharing of the Sites table between the databases of the two technologies being co-planned. The Sites table
must be shared between the databases of the two technologies being co-planned so that the sites where sectors of both
technologies are installed are listed only once in a common Sites table. In other words, the Sites tables in the databases of the
two technologies must be views of a common Sites table.
This section describes table sharing between GSM and UMTS, although the same description can be applied to any two radio
technology modules of Atoll
You can create views to share tables that have the same structure in the databases of the two technologies being co-planned,
i.e., the Sites and Antennas tables. In the following, we assume that the Sites tables of the GSM and UMTS documents contain
the same data and that two users, named GSMUser and UMTSUser in this example, exist in the databases.
To set up a shared Sites table for a GSM-UMTS co-planning project in Oracle or SQL Server:
1. Make backups of the GSM and UMTS documents.
2. Open the GSM document in Atoll.
3. Delete all the transmitters from the Transmitters table and all the sites from the Sites table.
73
Forsk 2016
4. Export the GSM document to the database by entering the user name and password for GSMUser.
5. Log in as GSMUser to the database.
6. Delete the Sites table.
7. Open the UMTS document in Atoll.
8. Export the UMTS document to the database by entering the user name and password for UMTSUser.
9. Log in as UMTSUser to the database.
10. Right-click the Sites table and select Create a View from the context menu. The Create View dialog box appears.
a. Enter Sites as the view name.
b. Enter GSMUser as the name of the schema which will contain the view.
c. Select Table as object type.
d. Enter UMTSUser as the name of the schema you want to use.
e. Select Sites as the object used to model the view.
11. Click Create. The view of the Sites table from UMTSUser is created in GSMUser. The GSMUser Sites table is now the
same as UMTSUser Sites table.
12. Set up user privileges for the Sites view in GSMUser to allow each user to Import, Update, Delete, and Select.
To set up a shared Sites table for a GSM-UMTS co-planning project in Microsoft Access:
1. Make backups of the GSM and UMTS documents.
2. Open the GSM document in Atoll.
3. Delete all the transmitters from the Transmitters table and all the sites from the Sites table.
4. Export the GSM document to a Microsoft Access database (GSM.mdb).
5. Open GSM.mdb in Microsoft Access.
6. Delete the Sites table.
7. Open the UMTS document in Atoll
8. Export the UMTS document to a Microsoft Access database (UMTS.mdb).
9. Open GSM.mdb in Microsoft Access.
10. In Microsoft Access 2003 and earlier, select File > Get External Data > Link Tables. In Microsoft Access 2007 and later,
select External Data > Access Database.
11. In Microsoft Access 2003 and earlier, the Link dialog box appears. Select UMTS.mdb. In Microsoft Access 2007 and
later, the Get External Data - Access Database dialog box appears, specify UMTS.mdb as data source and select Link
to data source by creating a linked table.
12. Click OK. The Link Tables dialog box appears.
13. Select the Sites table.
14. Click OK. Microsoft Access creates a Sites table in GSM.mdb which is linked to the Sites table in UMTS.mdb. The tables
contain the same data.
Once the linked Sites table has been created in the GSM database, you have to define the relations of this table with the other
tables in the database. See the Data Structure Reference Guide for detailed information on database tables.
The UMTS Sites table has more fields than the GSM Sites table. Therefore, you should
replace the GSM Sites table with the UMTS one.
When you upgrade one by one the databases that share the Sites table, any triggers
that you might have set on the Sites table of the database that is upgraded first might
be overwritten by the triggers set on the Sites table of the database upgraded last. In
order to avoid the triggers being overwritten, you can rename the triggers on the Sites
table of the database upgraded first (by adding, for example, the database technology
as prefix to the trigger names) before upgrading the other database(s).
74
AT332_AM_E0
To ensure database consistency, you can save or archive the linked documents at the same time, i.e., when a user saves or
archives one document, Atoll automatically saves or archives the other. This can be done using a macro triggered by the save
or archive operation.
75
76
Forsk 2016
Chapter 6
Multi-user
Environments
This chapter covers the following topics:
"Appendices" on page 87
78
AT332_AM_E0
6 Multi-user Environments
A multi-user environment is where more than one user work simultaneously on an Atoll project, sharing data over a network.
In large, structured multi-user environments, groups of users can work on specific parts of a common, large-scale project. For
example, different user groups can work on different regions of a country-wide network. In this chapter, the following are
explained:
The Atoll administrator should regularly update the shared path loss matrices.
As the users work on the network and archive changes in the database, the Atoll
administrator should regularly run data integrity checks on the master Atoll
document after loading modified data from the master database. For more
information, see "Appendix 1: Checking Data Integrity" on page 87.
79
Forsk 2016
80
AT332_AM_E0
If users modify geographic data locally, for example edit clutter or traffic in their
respective projects, they should store these modified geographic data locally so that the
modifications do not impact other users.
81
Forsk 2016
on a database for the first time. The database has to be of the same version as the Atoll Management Console being used to
manage user accounts and access rights.
To make your database compatible with the user management tool:
1. In the Atoll Management Console window, right-click the database whose user accounts you wish to manage.
2. Select Manage Users. The User Management dialog box appears.
3. Click Yes when asked whether you want to make your database compatible with the user management tool.
The Atoll Management Console adds a GUIUserRights table in the database with the following structure:
Field
Type
Description
ATOLL_USER
Text (50)
RIGHTS
Memo
Each users interface access rights are stored in a unique record in the GUIUserRights table. The contents of the RIGHTS field
have the following syntax:
RADIOPARAMS;CALCPARAMS;PROPAGMODELS;PASSWORD
The syntax is explained in detail in "Defining Database and Interface Access Rights" on page 82.
If interface access rights are not defined for a database, i.e., the GUIUserRights table does not exist, all the users have
unrestricted access to the Atoll interface.
If interface access rights are defined for a database, and a user creates a document from the database or opens a document
connected to the database, Atoll retrieves the interface access rights for the user when he enters his user name and password
to access the database.
If the database is not reachable, the user is not listed in the GUIUserRights table, or if the password is not correct, the users
interface access rights are set to read-only by default (for more information, see "Defining Database and Interface Access
Rights" on page 82). If the user is listed in the GUIUserRights table, his interface access rights are read and applied to the Atoll
interface (table grids and properties dialog boxes). A message is displayed in the Event Viewer window to inform the user of
his interface access rights. It is possible to remove interface access restrictions by disconnecting the document from the
database. However, a disconnected document cannot be reconnected to the database.
The GUIUserRights table is also stored in the Atoll document, and is updated when the document is saved. Hence, users can
work on their documents without actually being connected to the database, and still have their usual interface access rights
applied in the document.
Atoll does not ask for the user name and password when a document is opened using the
API. The interface access rights stored in the document are used.
When database connection properties are modified for a document, for example, when a different user enters his user name
and password in the connection properties, Atoll reads and applies the interface access rights defined for the new user.
82
AT332_AM_E0
), without access (
), or locked (
6. Under Database rights, you can select a database access Rights category:
No access: User without read and write access to the database. The database is not visible to these users and they
are not allowed to create Atoll documents based on this database.
Read only: Users allowed to create Atoll documents from the database but without write permissions to any table
of the database, i.e., users cannot archive changes made in the Atoll document to the database.
Standard: Users with read and write access to some tables of the database containing radio network data (see
table below).
Super-User: Users with read and write access to all the tables of the database.
Database access rights are stored in the user account properties in Oracle. If you are working with an RDBMS other
than Oracle, you will not be able to set database access rights. You can, however, still set interface access rights as
explained below.
Technologies
Tracked Tables
UMTS HSPA
83
Forsk 2016
Technologies
Tracked Tables
LTE
WiMAX/Wi-Fi
3GPP
3GPP2
7. Under Interface rights, you can select interface access rights for:
Database access rights and access rights to radio data in Atoll can be set
independently. For example, a user can have full access rights in the interface but not
be allowed to archive changes to the database.
However, access rights in the interface should only be granted if the user has at least
read-only access to the database.
Password confirmation:
Yes: (PASSWORD = STD) Atoll will ask users for password when opening a document connected to this
database or creating a new document from this database.
No: (PASSWORD = NONE) Atoll will not ask users for password when opening a document connected to this
database or creating a new document from this database.
8. Click OK. The database and interface access rights of the selected user are saved in the database.
84
AT332_AM_E0
5. Under Advanced:
Select Use operating system authentication if you want to use OS authentication prefix with the user name.
Select "Unlimited tablespace" privilege if you want to assign this system privilege to the user or specify a Quota
in megabytes.
Select Use operating system authentication if you want to use OS authentication prefix with the user name.
Select "Unlimited tablespace" privilege if you want to assign this system privilege to the user or specify a Quota
in megabytes.
85
Forsk 2016
86
AT332_AM_E0
6.4 Appendices
The following appendices provide additional information on:
In Atoll, select Document > Data Audit > Undefined Record Check.
Atoll searches for undefined records such as sites without transmitters, transmitters without subcells, TRXs, and
neighbours in GSM, transmitters without cells, and cells without neighbours in UMTS, CDMA2000, TD-SCDMA, LTE,
WiMAX, and Wi-Fi. Atoll lists all the undefined records found in the Event Viewer.
In Atoll, select Document > Data Audit > Duplicate Record Check.
Atoll searches for records that have the same identifier. For example, sites with the same name, transmitters with the
same name, etc. Atoll lists all the duplicate records in the Event Viewer.
87
Forsk 2016
88
Available in a format compatible with Atoll. File formats are described in "Path Loss Matrix File Format" on page 108.
Stored at the location set in the Atoll document.
Valid. If the path loss matrices are not valid, Atoll will automatically calculate them the next time they are used.
AT332_AM_E0
Path loss matrices calculated by other tools should include antenna pattern attenuation
(i.e., should be masked) in order to be consistent with the path loss matrices calculated
by Atoll.
The shared path loss matrices architecture can contain path loss matrices from different sources. The Pathloss.dbf file
provides the means to manage several sources of path loss matrices. This file stores, among other information, the validity
status and the location (path) of the path loss matrix files for each transmitter.
Let us assume that users of group A wish to work with the path loss matrices generated by Atoll only, and users of group B
wish to work with path loss matrices generated by a different tool for a part of the network and with path loss matrices
generated by Atoll where the matrices from the other tool are not available.
Let us assume that the shared path loss matrices folder where Atoll stores the generated path loss matrices files is
C:\Path_Loss_Internal, and the folder where the other tool stores its path loss matrices is C:\Path_Loss_External.
The Pathloss.dbf file in the Path_Loss_Internal folder will store the path to the LOS files for each transmitter in the network.
This folder can be set as the shared path loss matrices folder in the ATL files of group A users.
To set up the shared path loss matrices folder for group B users, you must create a new folder with a Pathloss.dbf file in it.
This folder can be called C:\Path_Loss_Mixed. The Pathloss.dbf file in this folder can be a copy of the Pathloss.dbf file in the
Path_Loss_Internal folder with the paths to the LOS files modified. For example, if the path loss matrices generated by the
other tool include Transmitter_1, the Pathloss.dbf file in the Path_Loss_Mixed folder will have all the same entries as
Pathloss.dbf file in the Path_Loss_Internal folder except for the path for the Transmitter_1 path loss matrices file. Figure 6.4
on page 89 explains this concept.
Figure 6.4: Path Loss Architecture for Multiple Source Path Loss Matrices
Once the Pathloss.dbf file in the Path_Loss_Mixed folder is updated with the correct paths corresponding to the different
transmitters, the Path_Loss_Mixed folder can be set as the shared path loss matrices folder in the ATL files of group B users.
If a group B user changes some parameters which make some path loss matrices invalid, Atoll will recalculate the private path
loss matrices with the propagation models assigned to the transmitters. The external path loss matrix will no longer be used.
89
90
Forsk 2016
Chapter 7
Coordinate Systems
and Units
This chapter covers the following topics:
"Units" on page 99
92
AT332_AM_E0
The Lambert Conformal-Conic Method: A portion of the earth is projected on a cone conceptually secant at one or
two standard parallels. This projection method is useful for representing countries or regions that have a predominant
east-west expanse.
The Universal Transverse Mercator (UTM) Method: A portion of the earth is projected on a cylinder tangent to a
meridian (which is transverse or crosswise to the equator). This projection method is useful for mapping large areas
that are oriented north-south.
A geographic system is not a projection, but a representation of a location on the surface of the earth in geographic
coordinates (degree-minute-second, gradient) with the latitude and longitude with respect to a meridian (e.g., Paris for NTF
system and Greenwich for ED50 system). Locations in a geographic system can be converted into other projections.
References:
1. Snyder, John. P., Map Projections Used by the US Geological Survey, 2nd Edition,
United States Government Printing Office, Washington, D.C., 313 pages, 1982.
2. http://www.colorado.edu/geography/gcraft/notes/gps/gps_f.html
3. http://www.epsg.org/Geodetic.html
4. http://geodesie.ign.fr/contenu/fichiers/documentation/pedagogiques/
transfo.pdf (French)
93
Forsk 2016
Ellipsoid
The ellipsoid is the pattern used to model the earth. It is defined by its geometric parameters.
Projection
The projection is the transformation applied to project the ellipsoid of the earth on to a plane. There are different projection
methods that use specific sets of parameters.
Projection Coordinate System
The projection coordinate system is the result of the application of a projection to a geographic coordinate system. It
associates a geographic coordinate system and a projection. Atoll enables you to choose the projection coordinate system
matching your geographic data.
If you are working in a multi-user environment, Atoll uses four coordinate systems:
94
AT332_AM_E0
The identification code enables Atoll to differentiate coordinates systems. In case you create a new coordinate
system, its code must be an integer value higher than 32767.
When describing a new datum, you must enter the ellipsoid code and parameters instead of the datum code in
brackets. There can be 3 to 7 parameters defined in the following order: Dx, Dy, Dz, Rx, Ry, Rz, S. The syntax of the line
in the .cs file will be:
Code = "Name of the system"; Unit Code; {Ellipsoid Code, Dx, Dy, Dz, Rx, Ry, Rz, S};
Projection Method Code, Projection Parameters; "Comments"
There can be up to seven projection parameters. These parameters must be ordered according to the parameter index
(see "Projection Parameter Indices" on page 98). Parameter with index 0 is the first one. Projection parameters are
delimited by commas.
For UTM projections, you must provide positive UTM zone numbers for north UTM zones and negative numbers for
south UTM zones.
You can add all other information as comments (such as usage or region).
Codes of units, data, projection methods, and ellipsoids, and projection parameter indices are listed in the tables below.
95
Forsk 2016
Unit Codes
Code
Cartographic Units
Code
Geographic Units
Metre
100
Radian
Kilometre
101
Degree
Foot
102
Grad
Link
103
ArcMinute
Chain
104
ArcSecond
Yard
-1
Unspecified
Nautical mile
Code
Datum
Mile
-1
Unspecified
Datum Codes
96
Code
Datum
121
260
Manoca
125
Samboja
261
Merchich
126
Lithuania 1994
262
Massawa
130
Moznet (ITRF94)
263
Minna
131
Indian 1960
265
Monte Mario
171
RGF93
266
M'poraloko
181
Luxembourg 1930
267
201
Adindan
268
NAD Michigan
202
269
203
270
Nahrwan 1967
204
271
Naparima 1972
205
Afgooye
272
206
Agadez
273
NGO 1948
207
Lisbon
274
Datum 73
208
Aratu
275
209
Arc 1950
276
NSWC 9Z-2
210
Arc 1960
277
OSGB 1936
211
Batavia
278
212
Barbados
279
OS (SN) 1980
213
Beduaram
280
Padang 1884
214
Beijing 1954
281
Palestine 1923
215
282
Pointe Noire
216
Bermuda 1957
283
217
Bern 1898
284
Pulkovo 1942
218
Bogota
285
Qatar
219
Bukit Rimpah
286
Qatar 1948
221
Campo Inchauspe
287
Qornoq
222
Cape
288
Loma Quintana
223
Carthage
289
Amersfoort
224
Chua
290
RT38
225
Corrego Alegre
291
226
Cote d'Ivoire
292
227
Deir ez Zor
293
Schwarzeck
228
Douala
294
Segora
AT332_AM_E0
Code
Datum
Code
Datum
229
Egypt 1907
295
Serindung
230
296
Sudan
231
297
Tananarive 1925
232
Fahud
298
Timbalai 1948
233
Gandajika 1970
299
TM65
234
Garoua
300
TM75
235
Guyane Francaise
301
Tokyo
236
Hu Tzu Shan
302
Trinidad 1903
237
303
238
304
Voirol 1875
239
Indian 1954
305
240
Indian 1975
306
Bern 1938
241
Jamaica 1875
307
242
Jamaica 1969
308
Stockholm 1938
243
Kalianpur
309
Yacare
244
Kandawala
310
Yoff
245
Kertau
311
Zanderij
247
La Canoa
312
Militar-Geographische Institut
248
313
249
Lake
314
Deutsche Hauptdreiecksnetz
250
Leigon
315
Conakry 1905
251
Liberia 1964
322
WGS 72
252
Lome
326
WGS 84
253
Luzon 1911
611
254
674
SIRGAS 2000
255
Herat North
901
256
Mahe 1971
902
Nord de Guerre
257
Makassar
903
258
1026
Projection Method
Code
Projection Method
Undefined
10
11
12
Mercator
13
Oblique Mercator
Cassini-Soldner
14
UTM Projection
Transverse Mercator
15
16
American Polyconic
Oblique Stereographic
Ellipsoid Codes
Code
Name
Major Axis
Minor Axis
Airy 1830
6377563.396
6356256.90890985
6377340.189
6356034.44761111
6378160
6356774.71919531
97
Forsk 2016
Code
Name
Major Axis
Minor Axis
Bessel 1841
6377397.155
6356078.96261866
Bessel Modified
6377492.018
6356173.50851316
Bessel Namibia
6377483.865
6356165.38276679
Clarke 1858
6378293.63924683
6356617.98173817
Clarke 1866
6378206.4
6356583.8
6378693.7040359
6357069.45104614
10
6378300.79
6356566.43
11
6378249.2
6356515
12
6378249.145
6356514.86954978
13
6378249.145
6356514.96656909
14
6378249.2
6356514.99694178
15
6377276.345
6356075.41314024
16
6377298.556
6356097.5503009
17
6377301.243
6356100.231
18
6377304.063
6356103.03899315
19
GRS 1980
6378137
6356752.31398972
20
Helmert 1906
6378200
6356818.16962789
21
6378160
6356774.50408554
22
International 1924
6378388
6356911.94612795
23
International 1967
6378160
6356774.71919530
24
Krassowsky 1940
6378245
6356863.01877305
25
NWL 9D
6378145
6356759.76948868
26
NWL 10D
6378135
6356750.52001609
27
Plessis 1817
6376523
6355862.93325557
28
Struve 1860
6378297
6356655.84708038
29
War Office
6378300.583
6356752.27021959
30
WGS 84
6378137
6356752.31398972
31
GEM 10C
6378137
6356752.31398972
32
OSU86F
6378136.2
6356751.51667196
33
OSU91A
6378136.3
6356751.61633668
34
Clarke 1880
6378249.13884613
6356514.96026256
35
Sphere
6371000
6371000
Projection Parameter
Index
Projection Parameter
Longitude of origin
Latitude of origin
False Easting
False Northing
98
AT332_AM_E0
7.2 Units
In the Atoll documents, you can define measurement units for reception, transmission, antenna gain, distance, height and
offset, and temperature. You can accept the default measurement units, or you can change them using the document
properties dialogue.
Transmission and Reception Power Units
Depending on the working environment, Atoll can use either one or two measurement units for the transmission/reception
power.
If you are working with stand-alone documents, i.e., documents not connected to databases, there is only one measurement
unit used in Atoll for display. It corresponds to the transmission/reception power unit defined in the Atoll document.
If you are working in a multi-user environment, Atoll uses two measurement units:
A measurement unit for display in the Atoll document. It corresponds to the transmission/reception power unit
defined in the current Atoll document. It is used for the display in the dialogues and in the tables, e.g., reception
thresholds (coverage prediction properties, microwave link properties, etc.), and received signal levels
(measurements, point analysis, coverage predictions, microwave link properties, etc.).
An internal measurement unit for the database. The internal unit is the transmission/reception power unit stored in
the database. It corresponds to the transmission/reception power unit used in the master Atoll document when the
database is created. Users working in documents connected to a database can modify the transmission/reception
power unit and save this change in their documents locally, but they cannot modify the internal power unit stored in
the database. Only the administrator can modify it manually by editing the entry in the Units tables.
A measurement unit for display in the Atoll document. It corresponds to the antenna gain unit defined in the current
Atoll document and it is used for the display in the dialogues and in the tables.
An internal measurement unit for the database. The internal unit is the antenna gain unit stored in the database. It
corresponds to the antenna gain unit used in the master Atoll document when the database is created. Users working
in documents connected to a database can modify the antenna gain unit and save this change in their documents
locally, but they cannot modify the antenna gain unit stored in the database. Only the administrator can modify it
manually by editing the entry in the Units tables.
Distance Units
Atoll uses the distance unit defined in the current Atoll document as display unit of the distances in the dialogues, in the
tables, and in the status bar.
99
Forsk 2016
Metre is used as the internal measurement unit for the distance in all Atoll documents whether they are connected to
databases or not. The internal measurement unit is not stored in the database and cannot be changed.
Height and Offset Units
Atoll uses the height and offset unit defined in the current Atoll document as display unit of the heights and the offsets in the
dialogues, in the tables, and in the status bar.
Metre is used as the internal measurement unit for the heights and offsets in all Atoll documents whether they are connected
to databases or not. The internal measurement unit is not stored in the database and cannot be changed.
Temperature Units
Atoll uses the temperature unit defined in the current Atoll document as display unit of the temperatures in the dialogues
and in the tables.
Degree Celsius is used as the internal measurement unit for the temperature in all Atoll documents whether they are
connected to databases or not. The internal measurement unit is not stored in the database and cannot be changed.
If you are working in a multi-user environment, Atoll uses two types of formats:
The display format is used for the display in dialogs and tables. You can set the display format for your document from the
Transmitters folders context menu.
The internal format is the BSIC format stored in a database. The BSIC format set by the administrator in the central Atoll
project is stored in the database when the database is created, and cannot be modified by users. Only the administrator can
modify the internal format manually by editing the corresponding entry in the Units tables. All Atoll documents opened from
a database will have the internal format of the database as their default BSIC format.
Users working on documents connected to a database can modify the format in their documents locally, and save this change
in their documents, but they cannot modify the format stored in the database.
Atoll expects the BSIC format in the database to be the octal format. If that is not the case,
do the following:
100
Chapter 8
Atoll File Formats
This chapter covers the following topics:
102
AT332_AM_E0
Site: The geographic location of transmitters (sectors, installed antennas, other equipment). A site can have one or
more transmitters.
Antenna: The radiation patterns and gains for antennas installed at transmitters.
Transmitter: A group of radio devices installed at a site with there transmission/reception characteristics (antennas,
feeders, TMAs, other equipment). A transmitter can have one or more cells or subcells.
Cell: An RF carrier available at a transmitter in UMTS, CDMA2000, TD-SCDMA, LTE, WiMAX, and Wi-Fi networks. A cell
is fully defined by the "transmitter-carrier" pair. Each cell in these networks is independent, i.e., has its own identifier,
power levels, performance characteristics.
TRX: An RF carrier available at a transmitter in GSM networks. A transceiver (TRX) can carry one ARFCN which can
correspond to the BCCH (7 traffic timeslots) or TCH (8 traffic timeslots).
Subcell: A subcell is a group of TRXs with the same radio characteristics. A subcell is fully defined by the "transmitterTRX type" pair.
Base station: This is the generic name for a cell site ("site-transmitter-cell" or "site-transmitter-subcells"). Technologyspecific names can be BTS, Node-B, eNode-B, etc.
RF repeater: An RF repeater receives, amplifies, and retransmits RF carriers both in downlink and uplink. The repeater
receives signals from a donor transmitter which it retransmits using a coverage-side antenna with amplification.
Remote antenna: Transmitter antennas located at a remote location with respect to the transmitters site.
Microwave link: A point-to-point link using microwave frequencies used for backhaul in radio access networks or for
fixed wireless access.
PMP microwave link: A group of microwave links originating from a common node to serve more than one location.
Passive microwave repeater: A passive microwave repeater receives and retransmits microwave signals without
amplification. Passive repeaters do not have power sources of their own. Active repeaters, on the other hand, amplify
the received signal. Reflectors are examples of passive repeaters.
This section covers the following file types that are used by Atoll:
File Format
Import
Export
Both
Planet
Both
Clutter
Classes
Clutter
Heights
Traffic Maps
Raster
Images
16-bit
16-bit
16-bit
DTM
Clutter
Classes
Clutter
Heights
Population
Web Map
Services
Vector
Georeferencing
(World File)
Embedded
1, 4, 8, 24bit
Index file
"Vector" Formats
File Format
Import
Export
SHP
Both
MapInfo
(MIF, TAB)
Both
Raster
Images
Population
Web Map
Services
Georeferencing
(World File)
Vector
Vector
103
Forsk 2016
"Raster" Formats
Geographic Data Types
File Format
Import
Export
DTM
Clutter
Classes
BIL
Both
8, 16, 32-bit
8-bit
TIFF
Both
8, 16-bit
8-bit
BMP
Both
8-bit
8-bit
DXF
Import
Erdas Imagine
(IMG)
Import
8, 16, 32-bit
8-bit
ArcView ASCII
Grid (TXT)
Export
ASCII
ASCII
ASCII
Vertical Mapper
(GRD, GRC)
Both
GRD
GRC
GRD
ECW
Import
24-bit
PNG
Both
All
Yes
PGW file
JPEG
Both
All
Yes
JGW file
Clutter
Heights
Web Map
Services
Population
1, 4, 8, 24bit
8, 16, 32-bit
8, 16-bit
1, 4, 8, 24bit
8, 16, 32-bit
Yes
TFW file
8-bit
1, 4, 8, 24bit
8, 32-bit
Yes
HDR file
Georeferencing
(World File)
Raster
Images
Traffic Maps
Embedded
1, 4, 8, 24bit
8, 16, 32-bit
Embedded
ASCII
ASCII
ASCII
Embedded
Raster
Images
Vector
Embedded
ERS file
World files (e.g. TFW, BPW) are header files used for the georeferencing of raster
files. See next sections for more information on World file types generated by Atoll.
The smallest supported resolution for raster files is 1 m. There is no restriction on the
resolution of images.
DTM, clutter classes, and clutter height maps must have an integer resolution.
All the raster maps you want to import in an ATL document must be represented in
the same projection system.
Specific header files are used to describe how data is organised within any of these geographic data file formats. This section
describes the following header file formats:
value
where keyword corresponds to an attribute type, and value defines the attribute value.
Keywords required by Atoll are described below. Other keywords are ignored.
104
ulxmap
ulymap
xdim
ydim
ncols
nrows
AT332_AM_E0
nbits
nbands
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
totalrowbytes
skipbytes Byte to be skipped in the image file in order to reach the beginning of
the image data. Default value is 0.
Four additional keywords can optionally be managed.
pixeltype Type of data read (in addition to the length)
This can be:
SIGNEDINT
Signed integer
8, 16, or 32 bits
FLOAT
Real
32 or 64 bits
If no pixeltype parameter is available, then the default value is UNSIGNEDINT (8, 16, or
32 bits).
Undefined
Inumber
Integer
Rnumber
Real
valuescale
DTM Sample
Here, the data is 20 m.
nrows
1500
ncols
1500
nbands
nbits
8 or 16
byteorder M
layout
bil
105
Forsk 2016
skipbytes 0
ulxmap
975000
ulymap
1891000
xdim
20.00
ydim
20.00
1500
ncols
1500
nbands
nbits
byteorder M
layout
bil
skipbytes 0
ulxmap
975000
ulymap
1891000
xdim
20.00
ydim
20.00
a.
106
Line
Description
2a
amount of translation
amount of rotation
Atoll does not use the lines 2 and 3 when importing a TIFF format geographic file.
AT332_AM_E0
Description
amount of translation
amount of rotation
Atoll supports BPW and BMW header file extensions for Import, but exports headers with BPW file extensions.
Clutter Classes Sample
100.00
0.00
0.00
-100.00
60000.00
2679900.00
Description
amount of translation
amount of rotation
Description
amount of translation
amount of rotation
107
Forsk 2016
Line
Description
DBF Structure
Byte
Description
Remarks
0...n
n+1
1st record of fixed length (see next parts); 2nd record (see next part for size, byte10) ; last
record
last
DBF Header
The DBF header size is variable and depends on the field count.
108
Byte
Size
Contents
Description
Applies to
00
0x03
plain .dbf
0x04
plain .dbf
D4, D5 (FS)
0x05
plain .dbf
D5, Fp (FS)
0x43
FS
0xB3
FS
0x83
0x8B
D4, D5
0x8E
D4, D5
0xF5
Fp
01
YYMMDD
All
04
ulong
All
08
ushort
All
10
ushort
All
12
0,0
Reserved
All
14
0x01
Begin transaction
D4, D5
0x00
End Transaction
D4, D5
0x00
ignored
AT332_AM_E0
Byte
Size
Contents
Description
Applies to
15
0x01
Encrypted
D4, D5
0x00
normal visible
All
16
12
0 (1)
D4,D5
28
0x01
Fp, D4, D5
0x00
All
29
language driver ID
D4, D5
0x01
Fp
0x02
Fp
30
32
n*32
+1
0x03
Fp
0xC8
codepage1250 Windows EE
Fp
0x00
ignored
0,0
reserved
All
0x0D
all
all
Field descriptor array in the DBF header (32 bytes for each field):
Byte
Size
Contents
Description
Applies to
11
ASCI
all
11
ASCI
all
12
n,n,n,n
D3
n,n,0,0
Fp
0,0,0,0
ignored
16
byte
17
byte
18
0,0
reserved
all
20
byte
Work area ID
D4, D5
0x00
unused
21
n,n
multi-user dBase
D3, D4, D5
0,0
ignored
0x01
Set Fields
D3, D4, D5
23
0x00
ignored
24
0...0
reserved
all
31
0x01
D4, D5
0x00
ignored
Field type and size in the DBF header, field descriptor (1 byte):
Size
Type
Description/Storage
Applies to
C 1...n
Char
all
FS
Fp, CL
n = 1...254
all
D8
Date
all
F 1...n
Numeric
N 1...n
Numeric
all
109
Forsk 2016
Size
Type
Description/Storage
Applies to
n = 1...20
FS, Fp, CL
n = 1...18
D4, D5 (FS)
Memo
all
V 10
Variable
FS
P 10
Picture
Fp
B 10
Binary
D5
G 10
General
OLE objects
structure like M
D5, Fp
22
short int
FS
44
long int
FS
88
double
FS
L1
Logical
M 10
Size
Description
Applies to
All
1n
All
110
Field
Type
Description
TX_NAME
Text
FILE_NAME
Text
MODEL_NAME
Text
MODEL_SIG
Text
Signature (identity number) of model used in calculations. You can check it in the
propagation model properties (General tab).
The Model_SIG is used for the purpose of validity. A unique Model_SIG is assigned to
each propagation model. When model parameters are modified, the associated model
ID changes. This enables Atoll to detect path loss matrix invalidity. In the same way, two
identical propagation models in different projects do not have the same model IDa.
ULXMAP
Float
X-coordinate of the top-left corner of the path loss matrix upper-left pixel
ULYMAP
Float
Y-coordinate of the top-left corner of the path loss matrix upper-left pixel
RESOLUTION
Float
NROWS
Float
NCOLS
Float
FREQUENCY
Float
Frequency band
TILT
Float
AZIMUTH
Float
TX_HEIGHT
Float
TX_POSX
Float
TX_POSY
Float
AT332_AM_E0
Field
Type
Description
ALTITUDE
Float
RX_HEIGHT
Float
ANTENNA_SI
Float
Logical number referring to antenna pattern. Antennas with the same pattern will have
the same number.
MAX_LOS
Float
Maximum path loss stated in 1/16 dB. This information is used, when no calculation
radius is set, to check the matrix validity.
CAREA_XMIN
Float
CAREA_XMAX
Float
CAREA_YMIN
Float
CAREA_YMAX
Float
WAREA_XMIN
Float
WAREA_XMAX
Float
WAREA_YMIN
Float
WAREA_YMAX
Float
LOCKED
Boolean
Locking status
0: path loss matrix is not locked
1: path loss matrix is locked.
Boolean
Atoll indicates if losses due to the antenna pattern are taken into account in the path
loss matrix.
0: antenna losses not taken into account
1: antenna losses included
INC_ANT
a.
b.
c.
In order to benefit from the calculation sharing feature, users must retrieve the propagation models from the same
central database. This can be done using the Open from database command for a new document or the Refresh
command for an existing one. Otherwise, Atoll generates different model_ID (even if same parameters are applied on
the same kind of model) and calculation sharing become unavailable due to inconsistency.
These coordinates enable Atoll to determine the area of calculation for each transmitter.
These coordinates enable Atoll to determine the rectangle including the computation zone.
Type
Description
TX_NAME
Text
FILE_NAME
Text
111
Forsk 2016
Field
Type
Description
AREA_XMIN
Float
Not used
AREA_XMAX
Float
Not used
AREA_YMIN
Float
Not used
AREA_YMAX
Float
Not used
4 bytes: version
4 bytes: flag (can be used to manage flags like active flag)
50 bytes: GUID
4 bytes: number of points
255 bytes: original measurement name (with prefix "Num" for drive test data and "CW" for CW measurements)
256 bytes: comments
4 bytes: X_RADIUS
4 bytes: Y_RADIUS
4 bytes: gain = measurement gain - losses
4 bytes: global error
4 bytes: rx height
4 bytes: frequency
8 bytes: tx Position
4 bytes: X
4 bytes: Y
4 bytes: measurement value
4 bytes: incidence angle.
Interference matrix files must contain interference probability values between 0 and 1, and not in precentage (between 0 and
100%). When interference matrix files are imported, Atoll does not check their validity and imports interference probability
values for loaded transmitters only.
In the following format descriptions and samples, lines starting with the "#" are considered as comments.
112
The interferer TRX type is not specified and is always considered to be BCCH.
Subcells have different powers defined as offsets with respect to the BCCH. For
subcells other than the BCCH, if the power offset of a subcell is X dB, then its
interference histogram will be shifted by X dB with respect to the BCCH interference
histogram.
If no power offset is defined on the interfered TRX type, it is possible to set "All".
For each interfered subcell-interferer subcell pair, Atoll saves probabilities for
several C/I values (6 to 24 values), including five fixed ones: 9, 1, 8, 14, and 22 dB.
Between two fixed C/I value, there can be up to three additional values (this number
depends on the probability variation between the fixed values). The C/I values have
0.5 dB accuracy and probability values are calculated and stored with an accuracy of
0.002 for probabilities between 1 and 0.05, and with an accuracy of 0.0001 for
probabilities lower than 0.05.
AT332_AM_E0
Name
Description
Column1
Interfered transmitter
Column2
Interfering transmitter
Column3
Interfered subcell. If the column is null, its value is identical to the one of the
line above. In order to save storage, all subcells with no power offset are not
duplicated (e.g. BCCH, TCH).
Column4
C/I threshold
Column5
Probability to have C/I the value specified in column 4 (C/I threshold). This
field must not be empty.
The columns 1, 2, and 3 must be defined only in the first line of each histogram.
Sample
# Calculation Results Data File.
# Version 1.1,
# Remark:
# Fields are:
##------------#------------#------------#-----------#------------------#
#| Interfered | Interfering| Interfered | C/I
#| Transmitter| Transmitter| Trx type
| Probability
##------------#------------#------------#-----------#------------------#
#
# Warning, The parameter settings of this header can be wrong if
# the "export" is performed following an "import". They
# are correct when the "export" follows a "calculate".
#
# Service Zone Type is "Best signal level of the highest priority HCS layer".
# Margin is 5.
# Cell edge coverage probability 75%.
# Traffic spreading was Uniform
##---------------------------------------------------------------------#
1
TCH_INNER
8
9
1
0.944
113
Forsk 2016
BCCH,TCHa
a.
10
0.904
11
0.892
14
0.844
15
0.832
16
0.812
17
0.752
22
0.316
25
0.292
0.944
10
.904
13
0.872
14
0.84
17
0.772
If the TCH and BCCH histograms are the same, they are not repeated. A single record indicates that the histograms
belong to TCH and BCCH both.
Name
Type
Description
Column1
Transmitter name
Text
Column2
Transmitter Identifier
Integer
Column3
Integer
Column4
Integer
Column5
% of vic coverage
Float
Column6
% of int coverage
Float
The last four columns describe the interference matrix scope. One transmitter per line is described separated with a tab
character.
Sample
# Calculation Results Dictionary File.
# Version 2.1,
# Fields are:
##-----------#-----------#-----------#-----------#---------#---------#
#|Transmitter|Transmitter|BCCH during|BSIC during|% of vic'|% of int'|
#|Name
##-----------#-----------#-----------#-----------#---------#---------#
#
# Warning, The parameter settings of this header can be wrong if
# the "export" is performed following an "import". They
# are correct when the "export" follows a "calculate".
114
AT332_AM_E0
#
# Service Zone Type is "Best signal level per HCS layer".
# Margin is 5.
# Cell edge coverage probability is 75%.
# Traffic spreading was Uniform (percentage of interfered area)
##---------------------------#
Site0_0
-1
-1
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
Name
Description
Column1
Interfered transmitter
Column2
Interfering transmitter
Column3
Interfered subcell. In order to save storage, all subcells with no power offset
are not duplicated (e.g. BCCH, TCH).
Column4
C/I probability
C/I value and the probability associated to this value separated by a space
character. This entry cannot be null.
Sample
# Calculation Results Data File.
# Version 1.1, Tab separated format. Commented lines start with #.
# Remark:
# Fields are:
#-----------------------------------------------------------------------#Transmitter
Interferer
TRX type
#-----------------------------------------------------------------------#
# Warning, The parameter settings of this header can be wrong if
# the "export" is performed following an "import". They
# are correct when the "export" follows a "calculate".
#
115
Forsk 2016
# Service Zone Type is "Best signal level of the highest priority HCS layer".
# Margin is 5.
# Cell edge coverage probability 75%.
# Traffic spreading was Uniform
##---------------------------------------------------------------------#
#
Site0_2
Site0_1
Site0_2
Site0_3
Site0_3
Site0_1
Site0_3
Site0_2
Name
Description
Column1
Interfered transmitter
Column2
Interfering transmitter
Column3
Interfered subcell. In order to save storage, all subcells with no power offset
are not duplicated (e.g. BCCH, TCH).
Column4
C/I threshold
Probability to have C/I the value specified in column 4 (C/I threshold). This
field must not be empty.
Column5
Sample
# Fields are:
#-----------------------------------------------------------------------#Transmitter
Interferer
TRX type
C/I
Probability
#------------------------------------------------------------------------
116
AT332_AM_E0
#
# Warning, The parameter settings of this header can be wrong if
# the "export" is performed following an "import". They
# are correct when the "export" follows a "calculate".
#
# Service Zone Type is "Best signal level of the highest priority HCS layer".
# Margin is 5.
# Cell edge coverage probability 75%.
# Traffic spreading was Uniform
##---------------------------------------------------------------------#
Site0_2
Site0_1
BCCH,TCH
-10
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
...
Name
Description
Column1
Interfered transmitter
Column2
Interfering transmitter
Column3
Co-channel probability
Column4
Adjacent-channel probability
Sample
# Calculation Results Data File.
# Version 1.1, Tab separated format. Commented lines start with #.
# Remark:
# Fields are:
#-----------------------------------------------------------------------#Transmitter
Interferer
Co-channel
Adjacent channel
#-----------------------------------------------------------------------#
# Warning, The parameter settings of this header can be wrong if
117
Forsk 2016
Site0_1
0.226667
0.024
Site0_2
Site0_3
0.27
0.024
Site0_3
Site0_1
0.276
0.02
Site0_3
Site0_2
0.226
0.028
The columns in the sample above are separated with a tab. These columns can also be separated with a semilcolon:
Site0_2;Site0_1;0.226667;0.024
Site0_2;Site0_3;0.27;0.024
Site0_3;Site0_1;0.276;0.02
Site0_3;Site0_2;0.226;0.028
Type
Description
Class code
Integer (>0)
Class name
Text (50)
none
open
sea
inland_water
residential
meanurban
When the calculation is global, the results are stored in two files for the entire prediction: one HDR file and one BIL
file (both identified by the prediction name).
When a calculation is "per transmitter", one HDR file and one BIL file are created for each transmitter in the prediction
(both identified by the transmitters name). In some "per transmitter" predictions, an additional DBF file is created for
the entire prediction (identified by the prediction name). The DBF file contains information on each transmitter and a
pointer to each transmitters specific HDR and BIL files.
118
AT332_AM_E0
In LTE, when a Cell Identifier Collision Zones (DL) prediction is calculated by value intervals with the display type set
"No. of interferers per cell", the HDR file and the BIL file are created for each cell in the prediction (both identified by
the cells name).
The format and the content of the DBF file is described here.
In both cases, an XML file describing the prediction is also created in the corresponding
<doc_name>\{<GUID>} folder.
Type
Description
TX_NAME
Text
FILE_NAME
Text
RESOLUTION
Float
Resolution of the calculation, same as xdim and ydim in the HDR file
AREA_XMIN
Float
AREA_XMAX
Float
AREA_YMIN
Float
AREA_YMAX
Float
NBITS
Float
NBANDS
Float
BYTE_ORDER
Float
BAND_ROW_BYTES
Float
TOTAL_ROW_BYTES
Float
SKIP_BYTES
Float
DATA_TYPE
Text
NO_DATA_VALUE
119
120
Forsk 2016
Chapter 9
Administration and
Usage
Recommendations
122
AT332_AM_E0
In multi-user environments, it is recommended to place all the geographic data on a file server accessible to all the
users. This approach avoids the need to replicate the geographic data on all the workstations.
Geographic data should either be located on each server or accessible through a fast network connection, e.g., 1 Gbps.
You can restrict access to the geographic data locations by assigning read/write access rights to administrators and
read-only rights to end-users.
Link or Embed
Only embed geographic data in ATL files if you wish to make a portable document. In all other cases, it is
recommended to link geographic data files to the Atoll documents.
It is recommended to set the paths to linked geographic data files using the Universal Naming Convention (UNC).
Following the UNC, an absolute path, such as "C:\Program Files\Forsk\Geo Data\...", is represented as
"\\Computer\C\Program Files\Forsk\Geo Data\...", where "Computer" is the computer name, and "C" is the share
name of disk C.
Example:
Absolute Path
Relative Path
UNC Path
If you define paths to geographic data files using the UNC, Atoll will be able to keep track of the linked files even if the
Atoll document is moved to another computer.
Size of Tiles
Some network planning tools require geographic data to be available in small tiles in order to work more efficiently.
For a country-wide project, this can lead to hundreds of files describing the geographic data. Atoll is designed to
optimise memory consumption, which enables it to perform efficiently with regional tiles (1 tile/file per region). In
Atoll, Merging small tiles to build a regional tile can improve performance greatly.
To note as well:
Recommended Formats
In order to improve performance, it is recommended to use uncompressed DTM and clutter files, for example, BIL
files. Using compressed geographic data files, for example, compressed TIF or Erdas Imagine, can cause performance
reduction due to decompression of these files in real time. If you are using compressed geographic data files, it is
strongly recommended to:
Either, hide the status bar that displays geographic data information in real time. You can hide the status bar from
the View menu.
Or, disable the display of some of the information contained in the status bar, such as altitude, clutter class, and
clutter height using an option in the Atoll.ini file, see "Hiding Information Displayed in the Status Bar" on page 186.
The following table shows the recommended file formats for different geographic data:
Geographic data type
Scanned maps
ECW
Vectors
SHP
123
Forsk 2016
Shared path loss matrices should be accessible through a fast network connection, e.g., 1 Gbps. These results are
accessed by Atoll during calculations, and should be available to the users through a fast network connection, i.e.,
30 Mbps at least per user.
You can restrict access to the shared path loss matrices folder by assigning read/write access rights to administrators
and read-only rights to end-users.
Atoll synchronises the private path loss matrices with the shared path loss matrices. If private path loss matrices are
invalid, and the corresponding shared path loss matrices are valid, Atoll deletes the invalid private path loss matrices
and uses the shared ones. You can make Atoll verify and remove private path loss matrices, valid or invalid, whose
corresponding shared path loss matrices are valid. This can be useful for disk space management. For more
information, see "Synchronising Private and Shared Path Loss Matrices" on page 178.
Link or Embed
Only embed path loss matrices in ATL files if you wish to make a portable document. In all other cases, it is
recommended to link path loss matrices to the Atoll documents.
Externalising path loss matrices to shared or private path loss folders will keep the ATL file size reasonable, which will
result in less fragmentation. Externalising path loss matrices does not reduce the performance of display and
calculations in Atoll.
It is recommended to set the paths to the private and shared path loss matrices folders using the Universal Naming
Convention (UNC).
Following the UNC, an absolute path, such as "C:\Program Files\Forsk\PathLosses\...", is represented as
"\\Computer\C\Program Files\Forsk\PathLosses\...", where "Computer" is the computer name, and "C" is the share
name of disk C.
Example:
Absolute Path
C:\Program Files\Forsk\PathLosses\...
Relative Path
\Program Files\Forsk\PathLosses\...
UNC Path
\\Computer\C\Program Files\Forsk\PathLosses\...
If you define paths to the private and shared path loss matrices folders using the UNC, Atoll will be able to keep track
of the linked files even if the Atoll document is moved to another computer.
Calculating Path Loss Matrices in Multi-RAT Documents
When the path loss matrices in multi-RAT documents using the RunPathloss API function, the path loss matrices of
each technology are calculated simultaneously using the same number of threads. For example, if 4 threads are used
to calculate path loss matrices, and there are 3 technologies (GSM, UMTS, and LTE), a total of 12 threads will be used
to calculate the path loss matrices at the same time. This can lead to the following problems:
To avoid these problems when using the RunPathloss API function to calculate path loss matrices in multi-RAT
documents, use the following work-arounds:
124
Resource saturation during the calculation of path loss matrices for multi-RAT
documents only occurs when using the RunPathloss API function in a macro or script.
When calculating path loss matrices for a multi-RAT document using Atoll, this does
not occur.
AT332_AM_E0
Atoll synchronises the private path loss matrices with the shared path loss matrices. If private path loss matrices are
invalid, and the corresponding shared path loss matrices are valid, Atoll deletes the invalid private path loss matrices
and uses the shared ones. You can make Atoll verify and remove private path loss matrices, valid or invalid, whose
corresponding shared path loss matrices are valid. This can be useful for disk space management. For more
information, see "Synchronising Private and Shared Path Loss Matrices" on page 178.
It is recommended to define a rule for making backups of your Atoll documents at regular intervals.
Do not skip a major Atoll version. For example, if you are currently using Atoll 2.8.x, you should first upgrade the
document to Atoll 3.1.x before upgrading to Atoll 3.2.x.
Upgrading your document will be simpler if you do not skip a major version. If you skip or have skipped an
intermediate major version, you should upgrade your document twice in order to make it compatible with the new
version.
9.4 Databases
General
In order to use Atoll with Oracle, you must create Oracle users and schema with names in uppercase.
Create backups of the database before upgrading.
It is recommended to define a rule for making backups of the database at regular intervals.
Do not skip a major Atoll version. For example, if you are currently using Atoll 2.7.x, you should first upgrade the
database to Atoll 2.8.x before upgrading to Atoll 3.1.x.
Upgrading your database will be simpler if you do not skip a major version. If you skip or have skipped an intermediate
major version, you must upgrade your database twice in order to make it compatible with the new version.
Table and field names should only use alphanumeric characters (A-Z, a-z, 0-9) and underscores (_).
Table and field names must not start with a numeric character (0-9).
Table and field names must not contain an SQL or RDBMS-specific keyword, such as ORDER, DATE, etc.
Table and field names must not contain spaces or special characters, such as periods (.), exclamation marks (!), colons
(:), semi-colons (;), interrogation marks (?), parentheses (()), brackets ({}), square brackets ([]), etc.
Boolean fields, system or user-defined, should always have default values assigned.
The CustomFields table enables you to define default values, choice lists, and read/write access for any field in any
table in Atoll, including user-defined fields that you add to the Atoll tables. The values defined in this table have
priority over the internal predefined default values. If you define floating point default values, make sure that all the
users have the same decimal separator.
If you wish to add custom fields in the Atoll document, you should first add the field in the database, and then update
your Atoll document from the database.
When setting up your database for the first time, try to anticipate user requirements in terms of custom fields in Atoll
tables. Some requirements of the different user groups can be satisfied if a few general-purpose user-defined fields
are added in Atoll tables when setting up the database.
For example, if you add three user-defined fields (one of type integer, float, and text (limited size)) to the Sites and
Transmitters tables, users will be able to use these for sorting, filtering, grouping, or other purposes. This approach
can help the database function a long time before users require the addition of other custom fields.
To improve performance, if your projects allow it, reduce the size of the fields corresponding to the sites and
transmitters names.
To improve performance, unless absolutely necessary, do not add user-defined fields of Text type. Rather, use
numeric field types, which allow sorting and other functions. If you must add Text fields, allocate them the appropriate
size that would suffice. For example, a 255-character long Text type field would, for the most part, occupy disk space
for no purpose.
To improve performance, you should avoid adding custom fields to the neighbour management tables.
125
Forsk 2016
Atoll can process four simultaneous path loss matrices calculations, which means high CPU and RAM resource consumption,
and as path loss calculations share the amount of memory allocated to the Atoll session, the total memory requirement can
exceed the Microsoft Windows (32-bit editions) limit of 2 GB per process. This is especially the case with large Atoll
documents and propagation models that require considerable memory.
Troubleshooting and Solution
As the cause of this problem is resource saturation on the server, resource consumption should be controlled in order to avoid
memory and CPU overloading as follows:
To reduce the impact of a large number of simultaneous path loss calculations, a Distributed Calculation Server should
be set up. Using the Distributed Calculation Server, path loss calculations can be performed outside Atoll. Using the
Distribution Calculation Server has the following advantages:
Path loss calculations are limited to four parallel instances regardless of the number of Atoll sessions running on
the server. This notably improves the memory and CPU consumption.
A queuing system, integrated in the Distributed Calculation Server, manages the calculation requests from
different Atoll sessions.
A failover mechanism automatically switches and hands over the path loss calculations back to Atoll in case a
problem occurs.
Path loss calculations are carried out by a separate process (AtollSvr), which has its own memory allocation apart
from Atoll, i.e., the amount of memory needed for calculations does not impacts the Atoll memory allocation.
This set up can introduce considerable improvements in both the number of Atoll sessions per server and the calculations. A
server with four processors (eight threads with hyper-threading) can accommodate four simultaneous path loss calculations
and use the other four threads for Atoll sessions. Atolls interface will also be more efficient and the overall processing time
for various tasks will be improved.
In order to prevent users from deactivating the use of the Distributed Calculation Server,
and hence bypassing the resource control procedure established above, the Atoll.ini file
should be set made read-only for end-users.
Apart from the above setup, you can also make some other system improvements:
To avoid error messages caused by requesting a large number of files over the network, the following Microsoft
Windows registry parameter can be modified in order to dedicate more resources to network read/write operations:
IRQSTACKSIZE should be set to 30 instead of 11, for example.
To avoid out of memory problems, the Pagefile size should be increased so that the server does not run out of global
memory when supporting more than 10 Atoll sessions simultaneously. This is different from the 2 GB per process
limit. Virtual memory can be increased from 8 GB to 16 GB, for example.
For 32-bit Windows operating systems, you can also increase the default Windows memory allocation limit from 2 GB
to 3 GB as explained in "Process Memory" on page 127.
126
AT332_AM_E0
files, or create them, you will not have the same configuration of the new server, but apart from that you will be able to work
with Atoll normally. These files are optional, not obligatory.
Initialisation File (INI)
It is highly recommended that the Atoll initialisation file be created and modified only by the administrator.
If you are using Windows 2000 Server, state the actual number of processors in the INI file.
Use Atoll to create these files and avoid modifying these files manually as human errors can create problems.
Uncheck image visibility to avoid loading unnecessary data in the memory.
You can set up your configuration files in the following manner:
A common configuration file that points to the geographic data, macros, and other common parameters in your
Atoll documents.
Separate configuration files created for your 2G and 3G projects, which would store their respective coverage
prediction studies parameters, traffic information, neighbour allocation parameters, and other technologyspecific parameters.
Separate configuration files based on, and for, different groups of users. These groups of users can be, for
example, groups of users working on different regions, groups of users working on different technologies, groups
of users focusing on certain operations (i.e., performing certain types of coverage predictions, performing the AFP,
etc.).
Coverage prediction studies can easily be duplicated within Atoll. Before creating study templates, and the XML
studies file, make sure that this study template is aimed at serving a number of users. This means, avoid creating study
templates unless these will be needed for a long time by a number of users. You can use the configuration files to store
your created coverage prediction studies locally. And, you can also use the study duplicate feature to create copies of
existing coverage prediction studies.
9.8 Printing
You should place different layers of geographic and radio data in a definite order when printing a project or a section of the
project. The following order should be followed:
1. Visible objects of the Data tab
All the visible objects of the Data tab are displayed above those in the Geo tab. However, it is strongly recommended
to place vector layers on the top of coverage prediction plots. You can do this by transferring these vector layers to
the Data tab using the context menu. For performance reasons, it is advised to place vector layers on top of raster
layers before printing a project. Sites and Transmitters must be on the very top, above all other layers. You should
place sites and sectors on the top, then vector layers, and then raster layers.
2. Unidimensional vectors (points)
3. Open polygonal vectors (lines, i.e., roads and other linear items, etc.)
4. Closed polygonal vectors (surfaces, i.e., zones and areas, etc.)
5. Multi-format maps (vector or raster maps, i.e., population, rain, generic maps, traffic, etc.)
6. Transparent raster maps (clutter class maps, etc.)
7. Non-transparent maps (images, DTM, clutter height maps, etc.)
127
Forsk 2016
If you do not want Atoll to calculate the shadowing margin during a coverage prediction, it is advised to clear the
Shadowing taken into account check box. This approach is more efficient in terms of performance than selecting this
option and setting the Cell edge coverage probability to 50%.
To improve memory consumption and optimise the calculation times, you should set the display resolutions of
coverage predictions according to the precision required. The following table lists the levels of precision that are
usually sufficient:
Size of the coverage prediction
Display resolution
City Center
5m
City
20 m
County
50 m
State
100 m
Country
It is recommended to use Fast Display in order to increase display speed. This option is available in the Display tab of
the Properties dialogues for CW Measurements and Drive Test Data folders. Although this approach only displays
measurement points as small squares, it can have a significant impact on performance depending on the number of
measurement points in the Atoll document.
When performing a CW measurements drive test campaign, please follow the recommended procedure described in
the Measurements and Model Calibration Guide.
Antenna names used in some tools, such as NetAct, can be different from those used in their corresponding antenna
files. To solve this issue, you can create a new file, named "Index", containing the list of antenna names, which would
in fact be the pattern (antenna file) names. You should place this file at the same location as the antenna patterns
(files). This will replace the antenna names with the new antenna names.
Some Kathrein antenna pattern files might have names different from the antenna pattern names present inside the
file. You will have to replace the name of the pattern inside the file by the name of the pattern file itself, in order to
import these antennas correctly.
A Planet Index file contains the path to and the name of each antenna file available. Creating such an Index file when
there are hundreds of antenna patterns available can be a difficult task. You can easily create the index file from the
Microsoft Windows command prompt. You can open the Command Prompt window by selecting Start > Run, entering
"cmd" and pressing ENTER. In the Command Prompt window, navigate to the directory containing the antenna
pattern files, enter the following command and press ENTER:
dir /b > Index
This will create a file called "Index" in the same directory as the antenna patter files containing a list of all the antenna
pattern file names, with one name per line. The file will also contain a line with its own name, so, before importing
this file into Atoll, you should use a text editor to remove the line containing the file name "Index."
The electrical tilt, which can be defined in the antenna properties dialogues in Atoll, is an additional electrical downtilt.
It might be redundant to define an additional electrical downtilt for antennas whose patterns already include
electrical tilt. Users should verify whether the antenna patterns of the antennas in their projects, do not already
include the effect of an electrical tilt.
128
User profile environment-based traffic maps should only be used for a precision on traffic that is of the same level as
the statistical clutter available in a project.
For higher precision on traffic data, you should use sector traffic maps or user density traffic maps. User density traffic
maps provide you with a means to define a density for each set of service, terminal type, and mobility type.
Sector traffic maps are best suited for traffic data issued by the OMC.
AT332_AM_E0
You can avoid memory fragmentation while working with Atoll documents by saving the Atoll document from time to
time, closing and restarting Atoll, and reopening the document.
This advice is applicable to any application running under Microsoft Windows because many common DLL files are
accessed by applications, and unloading and reloading these DLL files refreshes the memory allocation.
If you are working in a Citrix XenApp environment, you should restart your Citrix server every week or fortnight. The
exact time should be determined by the administrator depending on the state of the network (LAN).
In certain cases, it might be more appropriate to start working on a completely fresh ATL file. If you have been working
on your existing ATL file for a long time, it might become unnecessarily large and might contain some useless remains
from your earlier operations, e.g., traces of records that no longer exist in the database, etc. You can completely
refresh your project by following these steps:
a. Open the existing ATL file in Atoll that you want to replace.
b. Create a CFG file from your existing ATL file with all the required information, e.g., geographic data set, coverage
prediction parameters, neighbour allocation parameters, etc. For more information, refer to "Configuration Files"
on page 135.
c. Close the old ATL file.
d. Create a new ATL from the database to create a fresh ATL file.
e. Import the CFG file in the new ATL file.
You now have a clean ATL file to work with, which has all the same information as the old ATL file, and takes up less
space on the hard disk, has less fragmented data, and improved performance.
Memory Allocation
If you have to open several large ATL files simultaneously on the same computer, it is better to open each in a separate
Atoll session rather than to open them all in the same Atoll window. Each Atoll session on the same computer has its
own memory space allocated by the operating system. Each computer consumes a single license token independent
of the number of Atoll sessions opened simultaneously.
For 32-bit Windows operating systems, you can also increase the default Windows memory allocation limit from 2 GB
to 3 GB as explained in "Process Memory" on page 127.
File Size
Coverage predictions calculated over large areas require more memory. If you are working on an Atoll document
covering a large area, with coverage predictions calculated over the entire network, this document will require more
memory for loading all the coverage predictions. You can reduce memory consumption by making copies of your Atoll
document, and keeping a few coverage predictions in each copy. These ATL files will be faster to load and work with
compared to a single ATL file with all the coverage predictions.
Large coverage predictions can take up a considerable amount of memory even if they are not displayed on the map.
Externalise DTM, clutter, path loss matrices, and any other data that can be externalised, so that the ATL file size does
not become unnecessarily large.
Before starting path loss calculation, verify that the calculation radii and resolutions assigned to the different types of
transmitters are consistent. For example, calculating path loss matrices of picocells over large calculation radii would
only waste memory and disk space.
129
Forsk 2016
For calculating path loss matrices over large areas, you should use the dual resolution feature in Atoll. Define short
calculation radii and fine resolutions for the main path loss matrices, and large calculation radii and low resolutions
for extended path loss matrices. This approach decreases the calculation time significantly compared to calculating
just one matrix per transmitter using a fine resolution. The main path loss matrices should be calculated using the
same resolution as the resolution of the geographic data available. The extended path loss matrices can be calculated
using a lower resolution, e.g., twice the resolution of the geographic data.
Regionalisation
Use database regionalisation or site lists if you are working on smaller parts of a large network. Atoll loads only the
data necessary for your working area. If you load a large network, Atoll will load a lot of data that might not be
necessary all the time, such as the neighbour relation data.
Use regionalisation or site lists: If you load a large network, Atoll will be required to load a lot of data that might not
be necessary all of the time. For example, in a typical large GSM network, you might have around 10,000 transmitter
records, 20,000 subcell records, 50,000 TRX records, and up to 150,000 neighbour records.
Externalise embedded interference matrices: You can store interference matrices listed in the Interference Matrices
folder in external files. Atoll loads interference matrices from the external files to the memory only when needed. You
will also reduce the ATL file size by externalising the interference matrices.
Adapt calculation radii to the cell type and the EIRP: Before calculating path loss matrices, take care to correctly
associate calculation radii and resolutions to different types of cells. If you calculate path loss matrices for all types of
cells over a large calculation radius, it will unnecessarily burden the C/I and interference matrices computations.
Properly configure the interference thresholds: These thresholds indicate the level after which an interferer can be
ignored. The default value for this threshold (-130 dBm), defined in the Predictions tab of the Predictions folders
Properties dialogue, means that the computations will take into account all the interferers. However, if you set it too
high, you might lose important interference information. The proper value for this threshold depends on the
Reception Thresholds and the C/I Thresholds defined in the Subcells table. The optimum value would be
Min AllSubcells RT i CIT i M . Which means the minimum value of the factor RT i CIT i M computed for all
subcells, i. Where, RTi is the reception threshold of the subcell i, CITi the C/I threshold of this subcell, and M is a safety
margin.
Since this interference threshold is used both in interference matrices calculation and in interference predictions, it is
important to have at least a 3-dB margin for the interference energy aggregation in C/I studies. We recommend a
safety margin of 5 dB, which can be reduced if any problem is encountered.
Do not define very high C/I quality thresholds (Default values: 12 dB for BCCH and 9 dB for TCH). If you want a certain
TRX type to carry GPRS/EDGE traffic, you can add 1 or 2 dB to this value for that TRX type, and use the option of safety
margin in the AFP modules Cost tab. The 12 dB and 9 dB default values already include safety margins. If you
increment these values too much, it will unnecessarily load the interference matrix generation and the AFP.
Do not start an AFP session if the interference matrices report indicates problems: All the transmitters should have
interferers and very few of them (not more than 20%) should have more than 70 interferers. If there are too many or
too few entries in your interference matrices, the AFP plan will not be optimal.
If the memory-critical task is interference matrices generation: You can generate interference matrices in a piecewise
manner.
This means that you can generate nation-wide interference matrices with low resolutions based on the percentage of
interfered area (to improve computation time), with a cell edge coverage probability of 50% (which means no access
to clutter for reading standard deviation values), and an interference threshold of -112 dBm. This will provide rough
global interference matrices which can be locally improved. These interference matrices will be less memoryconsuming.
Then, use polygon or site list filters to focus on each important location, and calculate local interference matrices with
higher resolutions and reliabilities. Make sure that the computation zone in your project completely encompasses the
filtering zones that you define.
130
If the memory-critical task is the AFP session: Try to make the document lighter, e.g., remove coverage prediction
studies, exit and restart Atoll, and try to generate interference matrices with fewer entries.
AT332_AM_E0
If the memory-critical task is the traffic capture: You can use traffic load field of the Subcells table to provide traffic
loads directly to the AFP, and possibly skip this step.
In order to optimise memory usage during simulations, you can set the "Information to retain" option to "Only the
Average Simulation and Statistics". With this option Atoll uses much less memory because it only keeps limited
information in memory during the simulation process. Simulation results are detailed enough to be used in generating
coverage prediction studies.
Load vector layers in main document only. Loading vectors in the linked document is not necessary and only consumes
more memory.
Avoid loading neighbours and custom fields which are not required. This can be performed by creating views in the
database. For more information, see "Appendix 2: Setting Up Databases for Co-planning" on page 73.
131
132
Forsk 2016
Chapter 10
Configuration Files
This chapter covers the following topics:
134
AT332_AM_E0
10 Configuration Files
Configuration files can be used to store parameter and display settings. These files are optional, not required for working with
Atoll, but are useful means for making work easier.
This chapter describes the formats of these files in detail:
Projection and display coordinate systems are stored in the database, not in user
configuration files.
Simulation settings are not stored in user configuration files.
For more information on the contents of user configuration files, see "Contents of User Configuration Files" on
page 136.
A user configuration file can be automatically loaded when Atoll is run if:
a. The file is identified in the command line parameter -Cfg "cfgfilename" (see "Atoll Command Line Parameters" on
page 31 for more information), or
b. The file is named "Atoll.cfg" and is located in the Atoll installation folder. This file will be ignored if a user
configuration file is loaded through the command line parameter.
Additional configuration files (UTF-8 encoded XML-format CFG files or plain text INI files)
The following parameter settings can be stored in additional configuration files with a CFG extension:
For more information on the contents of additional configuration files, see "Contents of Additional Configuration
Files" on page 159.
135
Forsk 2016
136
<DegreeFormat>: Format used to display degrees, minutes, and seconds for geographic coordinate systems
Population, geoclimatic parameters, vector traffic maps, and other vector layers:
<Name>: Name of the folder
<Display>: (Different combinations of the following parameters exist in different display settings.)
Display type <type>, selected field <FieldSelector>, field description <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>, and font style <Style>
<LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>,
label font background colour <BackColor>, and label font style <Style>
<Items> properties, such as for each item: <Value>, <Min>, <Max>, <Legend>, <MainColor>,
<SecondaryColor>, <LineStyle>, <LineWidth>, and <FillStyle>
<AddToLegend>: Add to legend option checked or not
<Type>: Data type properties, such as <Name>, <Formats>, <Type>, and <Integrable>
<File>: Contains the file format, path, coordinate system information.
<Format> of and <Path> to linked files, if any
Coordinate system information for vector format data including: <CoordinateSystemName>,
<CoordinateSystemCode>, <EllipsoidCode>, <EllipsoidMajorRadius>, <EllipsoidMinorRadius>, <DatumCode>,
<DatumShiftX>, <DatumShiftY>, <DatumShiftZ>, <DatumRotationX>, <DatumRotationY>, <DatumRotationZ>,
<DatumScaleFactor>,
<ProjectionMethod>,
<ProjectionZone>,
<ProjectionLongitudeOrigin>,
<ProjectionLatitudeOrigin>, <ProjectionFalseEasting>, <ProjectionFalseNorthing>, <ProjectionScaleFactor>,
<ProjectionFirstParallel>, <ProjectionSecondParallel>, and <ProjectionAngle>
Clutter Classes:
<Name>: Name of the folder
<Display>: (Different combinations of the following parameters exist in different display settings.)
AT332_AM_E0
Displate type <type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId> (same
as <FieldSelector>) and <FieldTitle>, transparency level <Opacity>, visibility flag <visible>, and visibility range
between <minZoom> and <maxZoom>
<Items> properties, such as for each item: <Value>, <Min>, <Max>, <Legend>, <MainColor>,
<SecondaryColor>, <LineStyle>, <LineWidth>, and <FillStyle>
<AddToLegend>: Add to legend option checked or not
<Attributes>, such as: <records> and <fields>, which are,
Common: CODE, COLOR, NAME, HEIGHT, INDOOR
Under <GSM>: STDDEV, COVERI_STDDEV, TX_DIV_GAIN, ANT_HOP_GAIN
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 <TD-SCDMA>: 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 <Wi-Fi>: STDDEV, COVERI_STDDEV, MIMO_GAIN_FACTOR, STTD_OFFSET_DL, STTD_OFFSET_UL
<DefaultValues>, for the fields stated above.
Sample
Sample with display set to value intervals.
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<Geodataset version="2">
<DegreeFormat>0</DegreeFormat>
<Population> // or <GeoClimaticParams> or <Vectors>
<Name>Population</Name> // or <Name>Geoclimatic Parameters</Name>
or <Name>Vectors</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
<Type>ByIntervals</Type>
<FieldSelector>80000001</FieldSelector>
<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>
137
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-83</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</LabelFont>
<Items>
<Item>
<Min>900.</Min>
<Max>1000.</Max>
<Legend>900 <=Population(Density) <1 000</Legend>
<MainColor>255 96 0</MainColor>
<SecondaryColor>255 0 0</SecondaryColor>
</Item>
</Items>
</Display>
<AddToLegend>0</AddToLegend>
<Type>
<Name>Population</Name>
<Formats>15</Formats>
<Type>800</Type>
<Integrable>1</Integrable>
</Type>
<Files/>
</Population> // or </GeoClimaticParams> or </Vectors>
<ClassifiedClutter UseOnlyDefault="0">
<Display>
<Type>ByIntervals</Type>
<FieldSelector>3</FieldSelector>
<FieldDesc>
<FieldId>3</FieldId>
<FieldTitle>Height (m)</FieldTitle>
</FieldDesc>
<Opacity>50</Opacity>
<Items>
<Item>
<Min>54.</Min>
<Max>56.</Max>
<Legend>54 <=Height (m) <56</Legend>
<MainColor>255 38 0</MainColor>
<SecondaryColor>255 38 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>10</LineWidth>
<FillStyle>1</FillStyle>
</Item>
</Items>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
138
Forsk 2016
AT332_AM_E0
<visible>Yes</visible>
</Display>
<Attributes>
<fields>
<field length="1" type="uint" name="CODE"/>
<field length="4" type="int" name="COLOR"/>
<field length="50" type="text" name="NAME"/>
<field length="4" type="real" name="HEIGHT"/>
<field length="2147483647" type="text" name="INDOOR"/>
</fields>
<records/>
</Attributes>
<Name>Clutter Classes</Name>
<AddToLegend>0</AddToLegend>
<DefaultValues>
</DefaultValues>
</ClassifiedClutter>
<Altitudes> // or <BuildingHeights>
<Name>Digital Terrain Model</Name> // or <Name>Clutter Heights</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
<Type>ByIntervals</Type>
<FieldSelector>0</FieldSelector>
<FieldDesc>
<FieldId>0</FieldId>
<FieldTitle>Altitude</FieldTitle>
</FieldDesc>
<Opacity>50</Opacity>
<Items>
<Item>
<Min>900.</Min>
<Max>1000.</Max>
<Legend>900 <=Altitude <1 000</Legend>
<MainColor>255 96 0</MainColor>
<SecondaryColor>255 96 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>10</LineWidth>
<FillStyle>1</FillStyle>
</Item>
</Items>
</Display>
<AddToLegend>0</AddToLegend>
</Altitudes> // or </BuildingHeights>
</Geodataset>
</Atoll>
139
Forsk 2016
10.1.2 Zones
The user configuration files store the coordinates of the vertices of the filtering, focus, computation, printing, and geographic
export zone polygons, i.e., the points forming these polygons. The first and the last points have the same coordinates.
Sample
The following sample has rectangular computation and focus zones of the same size.
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<CalculationZone>
<Point>35950.000000 -15445.000000</Point>
<Point>33.000000 -15445.000000</Point>
<Point>33.000000 -33.000000</Point>
<Point>35950.000000 -33.000000</Point>
<Point>35950.000000 -15445.000000</Point>
</CalculationZone>
<FocusZone>
<Point>35950.000000 -15445.000000</Point>
<Point>33.000000 -15445.000000</Point>
<Point>33.000000 -33.000000</Point>
<Point>35950.000000 -33.000000</Point>
<Point>35950.000000 -15445.000000</Point>
</FocusZone>
<Atoll>
<MapPosition>: X and Y coordinates of the centre of the map window and the zoom level.
Sample
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<MapPosition CenterX="609433" CenterY="5632019" Scale="250000"/>
</Atoll>
140
Sites folder:
<Name>: Name of the folder
<Display>:
Displate type <type>, selected field <FieldSelector>, field description <FieldDesc> containing <FieldId> (same
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
colour <BackColor>, and font style <Style>
<LabelFont> properties, such as label font name <Name>, label font size <Size>, label font colour <Color>, label
font background colour <BackColor>, and label font style <Style>
<Items> properties, such as for each <Item>: <Value>, <Legend>, <MainColor>, <SecondaryColor>, <Symbol>,
and <SymbolSize>
<DataTips>: List of <items> displayed in tip texts
<Labels>: List of <items> displayed in labels
<AddToLegend>: Add to legend option checked or not
AT332_AM_E0
<DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration
<Filter>, <Groups>, and <Sort> criteria
<Configuration>: If any configuration exists for the folder, this tag contains the configuration <Name> and the
<Filter>, <Groups>, and <Sort> criteria
Antennas folder:
<Name>: Name of the folder
<DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration
<Filter>, <Groups>, and <Sort> criteria
<Configuration>: If any configuration exists for the folder, this tag contains the configuration <Name> and the
<Filter>, <Groups>, and <Sort> criteria
Links folder:
<Name>: Name of the folder
<Display>: Contains visibility flag <visible>, and visibility range between <minZoom> and <maxZoom>
<AddToLegend>: Add to legend option checked or not
<DefaultConfiguration>: The default configuration for the folder
<LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>, label
font background colour <BackColor>, and label font style <Style>
<SiteDisplay> properties, such as:
<SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, background
colour <BackColor>, and font style <Style>
<LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>,
label font background colour <BackColor>, and label font style <Style>
141
Forsk 2016
CW Measurements folder:
<DefaultConfiguration>: The default configuration for the folder
<Distance>: The minimum <Min> and maximum <Max> distance for measurement filtering
<DistanceUnit>: The distance unit
<Measure>: The minimum <Min> and maximum <Max> measured level for filtering
<MeasureUnit>: The measurement unit
<Angle>: The minimum <Min> and maximum <Max> angle for measurement filtering
<Relative>: Whether the angle is relative to each transmitters azimuth or an absolute value
<Clutter>: For each <Class>, its <Code> and whether it is in the <Filter> or not
<Advanced>: Any advanced filter used for filtering
<PathLosses>: Path loss tuing parameters, i.e., <ParallelAxisRadius>, <PerpendicularAxisRadius>, <GlobalMargin>,
<LocalMargin>, and <Threshold>
<Display>:
Displate type <Type>, selected field <FieldSelector>, visibility flag <Visible>, and visibility range between
<MinZoom> and <MaxZoom>
<SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, background
colour <BackColor>, and font style <Style>
<LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>,
label font background colour <BackColor>, and label font style <Style>
<Items> properties, such as for each <Item>: <Legend>, <MainColor>, <SecondaryColor>, <Symbol>, and
<SymbolSize>
<DataTips>: List of <items> displayed in tip texts
<Labels>: List of <items> displayed in labels
<AddToLegend>: Add to legend option checked or not
Sample
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<FoldersConfigurations>
<Sites>
<Name>Sites</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
142
AT332_AM_E0
<visible>Yes</visible>
<Type>ByValues</Type>
<FieldSelector>8</FieldSelector>
<FieldDesc>
<FieldId>8</FieldId>
<FieldTitle>Vendor</FieldTitle>
</FieldDesc>
<SymbolFont>
<Name>Wingdings</Name>
<Size>-120</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>32</Style>
</SymbolFont>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-80</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>33</Style>
</LabelFont>
<Items>
<Item>
<Value>Vendor</Value>
<Legend>Vendor</Legend>
<MainColor>255 0 0</MainColor>
<SecondaryColor>255 255 255</SecondaryColor>
<Symbol>164</Symbol>
<SymbolSize>120</SymbolSize>
</Item>
</Items>
<DataTips>
<Item>0</Item>
</DataTips>
<Labels>
<Item>0</Item>
</Labels>
</Display>
<AddToLegend>1</AddToLegend>
<DefaultConfiguration>
<Groups>Type</Groups>
</DefaultConfiguration>
</Sites>
<Antennas>
<Name>Antennas</Name>
<DefaultConfiguration>
<Filter>([CONSTRUCTOR]= Kathrein)</Filter>
</DefaultConfiguration>
<Configuration>
143
<Name>Conf</Name>
<Filter>([CONSTRUCTOR]= Kathrein)</Filter>
</Configuration>
</Antennas>
<Transmitters> // or <MWMultiHops> // or <MWHubs>
<Name>Transmitters</Name> // or <Name>Multi-Hops</Name> //
or <Name>Point to Multipoint</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
<Type>ByValues</Type>
<FieldSelector>0</FieldSelector>
<FieldDesc>
<FieldId>0</FieldId>
<FieldTitle>Automatic</FieldTitle>
</FieldDesc>
<Items>
</Items>
<DataTips>
<Item>0</Item>
</DataTips>
</Display>
<AddToLegend>1</AddToLegend>
<DefaultConfiguration/>
</Transmitters> // or </MWMultiHops> // or </MWHubs>
<MWLinks>
<Name>Links</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
</Display>
<AddToLegend>0</AddToLegend>
<DefaultConfiguration/>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-83</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</LabelFont>
<SiteDisplay>
<SymbolFont>
<Name>Wingdings</Name>
<Size>80</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
144
Forsk 2016
AT332_AM_E0
</SymbolFont>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-80</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</LabelFont>
</SiteDisplay>
<Symbol>65444</Symbol>
<ShowText>0</ShowText>
<RepeaterDisplay>
<SymbolFont>
<Name>Wingdings</Name>
<Size>80</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</SymbolFont>
</RepeaterDisplay>
</MWLinks>
<CWMeasurements>
<DefaultConfiguration>
<Distance>
<Min>0.</Min>
<Max>1000.</Max>
</Distance>
<DistanceUnit>0</DistanceUnit>
<Measure>
<Min>-105.</Min>
<Max>-90.</Max>
</Measure>
<MeasureUnit>0</MeasureUnit>
<Angle>
<Min>-180.</Min>
<Max>180.</Max>
</Angle>
<Relative>Yes</Relative>
<Clutter>
<Class>
<Code>1</Code>
<Filter>Yes</Filter>
</Class>
</Clutter>
<Advanced>([DIST]> 500)</Advanced>
</DefaultConfiguration>
<PathLosses>
<ParallelAxisRadius>200.</ParallelAxisRadius>
<PerpendicularAxisRadius>100.</PerpendicularAxisRadius>
145
<GlobalMargin>30.</GlobalMargin>
<LocalMargin>30.</LocalMargin>
<Threshold>-130.</Threshold>
</PathLosses>
<Display>
<Type>ByIntervals</Type>
<FieldSelector>Error (P-M) (dB)</FieldSelector>
<SymbolFont>
<Name>Wingdings</Name>
<Size>-120</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-83</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</LabelFont>
<Items>
<Item>
<Min>-20.</Min>
<Legend>Error (P-M) (dB) >=-20</Legend>
<MainColor>255 0 0</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<Symbol>167</Symbol>
<SymbolSize>100</SymbolSize>
</Item>
</Items>
<DataTips>
<Item>M (dBm)</Item>
</DataTips>
<Labels>
<Item>M (dBm)</Item>
</Labels>
</Display>
</CWMeasurements>
<TestMobileData>
<Techno>GSM</Techno>
<DefaultConfiguration>
<Clutter>
<Class>
<Code>1</Code>
<Filter>Yes</Filter>
</Class>
</Clutter>
<Advanced></Advanced>
146
Forsk 2016
AT332_AM_E0
</DefaultConfiguration>
<PathLosses>
<ParallelAxisRadius>200.</ParallelAxisRadius>
<PerpendicularAxisRadius>100.</PerpendicularAxisRadius>
<GlobalMargin>30.</GlobalMargin>
<LocalMargin>30.</LocalMargin>
<Threshold>-130.</Threshold>
</PathLosses>
<Display>
<Type>ByIntervals</Type>
<FieldSelector>Ec_I0</FieldSelector>
<SymbolFont>
<Name>Wingdings</Name>
<Size>-120</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-83</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</LabelFont>
<Items>
<Item>
<Min>-60.</Min>
<Legend>Ec_I0 >=-60</Legend>
<MainColor>255 0 0</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<Symbol>167</Symbol>
<SymbolSize>100</SymbolSize>
</Item>
</Items>
</Display>
</TestMobileData>
<PropagationModels> // or <SmartAntennasModels>
<Name>Propagation Models</Name> // or <Name>Smart Antenna Models</Name>
<DefaultConfiguration/>
</PropagationModels> // or </SmartAntennasModels>
</FoldersConfigurations>
</Atoll>
General tab:
<Techno>: Name of the technology
<Name>: Name of the folder
147
Sample
GSM coverage by signal level
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<Studies>
<CoverageTRXStudy>
<Techno>GSM</Techno>
<Name>GSM: Coverage by Signal Level 0</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
<Type>ByIntervals</Type>
<FieldSelector>80000008</FieldSelector>
<Opacity>50</Opacity>
<Items>
<Item>
<Min>-75.</Min>
<Legend>Best Signal Level (dBm) >=-75</Legend>
<MainColor>255 147 0</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>15</LineWidth>
<FillStyle>1</FillStyle>
</Item>
<Item>
<Min>-85.</Min>
<Legend>Best Signal Level (dBm) >=-85</Legend>
<MainColor>70 255 0</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>15</LineWidth>
<FillStyle>1</FillStyle>
</Item>
<Item>
148
Forsk 2016
AT332_AM_E0
<Min>-95.</Min>
<Legend>Best Signal Level (dBm) >=-95</Legend>
<MainColor>0 255 217</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>15</LineWidth>
<FillStyle>1</FillStyle>
</Item>
<Item>
<Min>-105.</Min>
<Legend>Best Signal Level (dBm) >=-105</Legend>
<MainColor>0 0 255</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>15</LineWidth>
<FillStyle>1</FillStyle>
</Item>
</Items>
<DataTips>
<Item>c0000000</Item>
<Item>c0000001</Item>
</DataTips>
</Display>
<AddToLegend>1</AddToLegend>
<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>
149
Forsk 2016
<ANP_IL_options>: Intra-technology inter-carrier neighbour allocation parameters (UMTS HSPA and CDMA2000
documents)
<ANP_IT_options>: Inter-technology neighbour allocation parameters
A <Techno></Techno> tag is also present if the user configuration is exported from a 3GPP Multi-RAT document. This
tag contains the name of the technology to which the parameters belong.
Sample
UMTS HSPA inter-technology, intra-carrier neighbour allocation parameters:
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<ANP_options>
<Techno>UMTS</Techno>
<numMax>16</numMax>
<resolution>-1</resolution>
150
AT332_AM_E0
<minField>-10500</minField>
<margin>500</margin>
<useCoSite>1</useCoSite>
<useAdjacent>1</useAdjacent>
<traffic>0</traffic>
<symetric>0</symetric>
<keepNeighbs>0</keepNeighbs>
<MaxDist>10000</MaxDist>
<PercentCoverage>1000</PercentCoverage>
<UseShadowing>0</UseShadowing>
<reliability>7500</reliability>
<UseIndoor>0</UseIndoor>
<deltaMax>1200</deltaMax>
<applyConstraints>0</applyConstraints>
<covBased>1</covBased>
<minDistImportance>100</minDistImportance>
<maxDistImportance>1000</maxDistImportance>
<minCov>1000</minCov>
<maxCov>3000</maxCov>
<minAdj>3000</minAdj>
<maxAdj>6000</maxAdj>
<minCos>6000</minCos>
<maxCos>10000</maxCos>
<UseGlobalThreshold>0</UseGlobalThreshold>
<EcIoMin>-1400</EcIoMin>
<usePmax>0</usePmax>
<PerCentMaxPower>5000</PerCentMaxPower>
<EcIoMax>-700</EcIoMax>
<useEcIoMax>0</useEcIoMax>
</ANP_options>
</Atoll>
<defSeparations__CONF_CO_SITE_BB>: Default co-site separation rule for two BCCH type TRXs.
<defSeparations__CONF_CO_CELL_BB>: Default co-transmitter separation rule for two BCCH type TRXs.
<defSeparations__CONF_NEIGH_BOUR_BB>: Default neighbour separation rule for two BCCH type TRXs.
<defSeparations__CONF_CO_SITE_BT>: Default co-site separation rule for a BCCH and a TCH type TRX.
<defSeparations__CONF_CO_CELL_BT>: Default co-transmitter separation rule for a BCCH and a TCH type TRX.
<defSeparations__CONF_NEIGH_BOUR_BT>: Default neighbour separation rule a for BCCH and a TCH type TRX.
<defSeparations__CONF_CO_SITE_TT>: Default co-site separation rule for two TCH type TRXs.
<defSeparations__CONF_CO_CELL_TT>: Default co-transmitter separation rule for two TCH type TRXs.
<defSeparations__CONF_NEIGH_BOUR_TT>: Default neighbour separation rule for two TCH type TRXs.
<freezeState>: Last minute resource freezing options available in the AFP launch wizard
<numMinutes>: Target time alloted to the AFP
<useDTX>: Consider the effect of discontinuous transmission or not
<dtxVocalFactor>: Voice activity factor for discontinuous transmission
<AfpBasedOnInterference>: Load all potential interferers or not
<AfpBasedOnSeparations>: Load all the subcells potentially involved in separation constraints or not
<IM_calculate__WithTraffic>: Whether traffic spreading is uniform or based on the maps used in the default traffic
capture (for interference matrices calculation)
<IM_calculate__BestServerZoneMargin>: Margin in case of Best signal level per HCS layer (for interference matrices
calculation)
151
Forsk 2016
<IM_calculate__ServiceZoneType>: All or Best signal level per HCS layer (for interference matrices calculation)
<IM_calculate__reliability_X_10000>: Cell edge coverage probability (for interference matrices calculation)
<TakeTfFromCapt>: Whether traffic loads are read from the default traffic capture or from the Subcells table
<preferedSenario>: Scenario type, i.e., modification of existing TRXs allowed or not
Sample
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<AFP_options>
<defSeparations__CONF_CO_SITE_BB>2</defSeparations__CONF_CO_SITE_BB>
<defSeparations__CONF_CO_CELL_BB>3</defSeparations__CONF_CO_CELL_BB>
<defSeparations__CONF_NEIGH_BOUR_BB>2</defSeparations__CONF_NEIGH_BOUR_BB>
<defSeparations__CONF_CO_SITE_BT>2</defSeparations__CONF_CO_SITE_BT>
<defSeparations__CONF_CO_CELL_BT>3</defSeparations__CONF_CO_CELL_BT>
<defSeparations__CONF_NEIGH_BOUR_BT>1</defSeparations__CONF_NEIGH_BOUR_BT>
<defSeparations__CONF_CO_SITE_TT>1</defSeparations__CONF_CO_SITE_TT>
<defSeparations__CONF_CO_CELL_TT>2</defSeparations__CONF_CO_CELL_TT>
<defSeparations__CONF_NEIGH_BOUR_TT>1</defSeparations__CONF_NEIGH_BOUR_TT>
<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>
152
AT332_AM_E0
Sample
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<SCP_options>
<MinEcI0>-1500.</MinEcI0>
<margin>500.</margin>
<reliability>5000.</reliability>
<DistanceMin>200000.</DistanceMin>
<Strategy0>1</Strategy0>
<Strategy1>1</Strategy1>
<Strategy2>1</Strategy2>
<Strategy3>1</Strategy3>
<Strategy>0</Strategy>
<FromScratch>1</FromScratch>
<UseCurrentNghbs>1</UseCurrentNghbs>
<NghbOrder>1</NghbOrder>
<ComputeNghbs>0</ComputeNghbs>
<UseMaxCodes>1</UseMaxCodes>
<UseShadowing>1</UseShadowing>
<SameCodeForCarriers>0</SameCodeForCarriers>
<NbClusterPerSite>3</NbClusterPerSite>
<ClustNghbs>0</ClustNghbs>
<Clust2ndNghbs>0</Clust2ndNghbs>
<NbCodesPerCluster>8</NbCodesPerCluster>
<UseDistance>1</UseDistance>
<UseExcepPairs>1</UseExcepPairs>
<minField>-10500</minField>
<usePmax>0</usePmax>
<PerCentMaxPower>5000</PerCentMaxPower>
<Max1stNghbCost>100</Max1stNghbCost>
<Max2ndNghbCost>50</Max2ndNghbCost>
<Max3rdNghbCost>5</Max3rdNghbCost>
<CoplanCost>100</CoplanCost>
<MaxCoClusterCost>50</MaxCoClusterCost>
153
<MaxDistCost>100</MaxDistCost>
<ExcepPairCost>100</ExcepPairCost>
<UseIndoor>0</UseIndoor>
<UseCloseNghbs>1</UseCloseNghbs>
<CloseDistance>80000.</CloseDistance>
<CloseImportance>3000.</CloseImportance>
<MaxCloseCost>100</MaxCloseCost>
</SCP_options>
</Atoll>
Sample
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<PNO_options>
<DistanceMin>200000.</DistanceMin>
<Strategy0>1</Strategy0>
<Strategy1>1</Strategy1>
<Strategy2>1</Strategy2>
<Strategy>2</Strategy>
<FromScratch>1</FromScratch>
<UseCurrentNghbs>1</UseCurrentNghbs>
<NghbOrder>1</NghbOrder>
<ComputeNghbs>1</ComputeNghbs>
154
Forsk 2016
AT332_AM_E0
<SameCodeForCarriers>0</SameCodeForCarriers>
<PilotIncr>4</PilotIncr>
<PNClusterSize>3</PNClusterSize>
<UseDistance>1</UseDistance>
<UseExcepPairs>1</UseExcepPairs>
<UseMaxCodes>1</UseMaxCodes>
<MinEcI0>-1600.</MinEcI0>
<TDrop>-1800.</TDrop>
<reliability>6000.</reliability>
<UseShadowing>0</UseShadowing>
<minField>-10500</minField>
<usePmax>0</usePmax>
<PerCentMaxPower>5000</PerCentMaxPower>
<Max1stNghbCost>100</Max1stNghbCost>
<Max2ndNghbCost>50</Max2ndNghbCost>
<Max3rdNghbCost>5</Max3rdNghbCost>
<CoplanCost>100</CoplanCost>
<MaxDistCost>100</MaxDistCost>
<ExcepPairCost>100</ExcepPairCost>
<UseIndoor>0</UseIndoor>
</PNO_options>
</Atoll>
Sample
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<OFDM_AFP_options>
<UseNeighbs>1</UseNeighbs>
<UseDistance>1</UseDistance>
<UseIM>1</UseIM>
<BasedOnFrqPlan>1</BasedOnFrqPlan>
<SameSegPerTx>0</SameSegPerTx>
155
Forsk 2016
<MinDistance>100.</MinDistance>
<SiteStrategy>1</SiteStrategy>
<UniformIDDistribution>1</UniformIDDistribution>
<RangeType>2</RangeType>
<ExcludedPis></ExcludedPis>
</OFDM_AFP_options>
</Atoll>
Sample
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<Microwave>
156
AT332_AM_E0
<QualityModel>6</QualityModel>
<QualityObjective0>3</QualityObjective0>
<QualityObjective1>4</QualityObjective1>
<QualityObjective2>2</QualityObjective2>
<QualityObjective3>1</QualityObjective3>
<AvailabilityObjective0>3</AvailabilityObjective0>
<AvailabilityObjective1>2</AvailabilityObjective1>
<AvailabilityObjective2>1</AvailabilityObjective2>
<RainModel>5</RainModel>
<RBER>1.e-012</RBER>
<ALFA1>10</ALFA1>
<ALFA2>1</ALFA2>
<RefDelayM>6.30000019</RefDelayM>
<refDelayNM>6.30000019</refDelayNM>
<EquipPercent>33.</EquipPercent>
<RainPercent>33.</RainPercent>
<kMoy>1.33</kMoy>
<kMin>0.88</kMin>
<UseAtpc>0</UseAtpc>
<P0Method>1</P0Method>
<IgnoreXPD>1</IgnoreXPD>
<IgnorePR>0</IgnorePR>
<WhichBER>5</WhichBER>
<BER1>1.e-003</BER1>
<BER2>1.e-006</BER2>
<Rec838>1</Rec838>
<UseK1Global>1</UseK1Global>
<UseK2Global>1</UseK2Global>
<CALC_LINK_PORTS>selected</CALC_LINK_PORTS>
<MultilineShared>0</MultilineShared>
<NoAcm>1</NoAcm>
<InterferenceDistanceMax>50000.</InterferenceDistanceMax>
<InterferenceDropMin>1.</InterferenceDropMin>
<InterferenceDropMinGlobal>3.</InterferenceDropMinGlobal>
<InterferenceCalcGo>1</InterferenceCalcGo>
<InterferenceCalcReturn>1</InterferenceCalcReturn>
<InterferenceCalcUplink>0</InterferenceCalcUplink>
<InterferenceCalcDownlink>0</InterferenceCalcDownlink>
<InterferenceRainSurfCorrelation>100.</InterferenceRainSurfCorrelation>
<InterferenceAutoWeight>0</InterferenceAutoWeight>
<InterferenceUseAtpc>0</InterferenceUseAtpc>
<InterferenceWidth>250</InterferenceWidth>
<InterferenceOverShoot>0</InterferenceOverShoot>
<CochannelOnly>0</CochannelOnly>
<IgnoreIntraLinkInterference>1</IgnoreIntraLinkInterference>
<Resolution>50</Resolution>
<INTERF_DETAIL>both</INTERF_DETAIL>
<ClutterCategory0>0</ClutterCategory0>
<ClutterDryCategory0>B</ClutterDryCategory0>
157
<ClutterCategory1>1</ClutterCategory1>
<ClutterDryCategory1>B</ClutterDryCategory1>
<ClutterCategory2>1</ClutterCategory2>
<ClutterDryCategory2>B</ClutterDryCategory2>
<ClutterCategory3>1</ClutterCategory3>
<ClutterDryCategory3>B</ClutterDryCategory3>
<ClutterCategory4>0</ClutterCategory4>
<ClutterDryCategory4>B</ClutterDryCategory4>
<ClutterCategory5>1</ClutterCategory5>
<ClutterDryCategory5>B</ClutterDryCategory5>
<ClutterCategory6>2</ClutterCategory6>
<ClutterDryCategory6>B</ClutterDryCategory6>
<ClutterCategory7>2</ClutterCategory7>
<ClutterDryCategory7>B</ClutterDryCategory7>
<ClutterCategory8>2</ClutterCategory8>
<ClutterDryCategory8>B</ClutterDryCategory8>
<ClutterCategory9>4</ClutterCategory9>
<ClutterDryCategory9>B</ClutterDryCategory9>
<ClutterCategory10>2</ClutterCategory10>
<ClutterDryCategory10>B</ClutterDryCategory10>
<ClutterCategory11>2</ClutterCategory11>
<ClutterDryCategory11>B</ClutterDryCategory11>
<ClutterCategory12>2</ClutterCategory12>
<ClutterDryCategory12>B</ClutterDryCategory12>
<ClutterCategory13>2</ClutterCategory13>
<ClutterDryCategory13>B</ClutterDryCategory13>
<ClutterCategory14>2</ClutterCategory14>
<ClutterDryCategory14>B</ClutterDryCategory14>
<ClutterCategory15>1</ClutterCategory15>
<ClutterDryCategory15>E</ClutterDryCategory15>
<ClutterCategory16>1</ClutterCategory16>
<ClutterDryCategory16>E</ClutterDryCategory16>
<ClutterCategory17>0</ClutterCategory17>
<ClutterDryCategory17>E</ClutterDryCategory17>
<ClutterCategory18>1</ClutterCategory18>
<ClutterDryCategory18>E</ClutterDryCategory18>
<ClutterCategory19>1</ClutterCategory19>
<ClutterDryCategory19>E</ClutterDryCategory19>
<ClutterCategory20>1</ClutterCategory20>
<ClutterDryCategory20>E</ClutterDryCategory20>
<ClutterCategory21>1</ClutterCategory21>
<ClutterDryCategory21>E</ClutterDryCategory21>
<ClutterCategory22>1</ClutterCategory22>
<ClutterDryCategory22>E</ClutterDryCategory22>
<ClutterCategory23>1</ClutterCategory23>
<ClutterDryCategory23>E</ClutterDryCategory23>
<ClutterCategory24>1</ClutterCategory24>
<ClutterDryCategory24>E</ClutterDryCategory24>
<ClutterCategory25>1</ClutterCategory25>
158
Forsk 2016
AT332_AM_E0
<ClutterDryCategory25>E</ClutterDryCategory25>
<ClutterCategory26>1</ClutterCategory26>
<ClutterDryCategory26>A</ClutterDryCategory26>
<ClutterCategory27>1</ClutterCategory27>
<ClutterDryCategory27>A</ClutterDryCategory27>
<ClutterCategory28>1</ClutterCategory28>
<ClutterDryCategory28>A</ClutterDryCategory28>
<ClutterCategory29>1</ClutterCategory29>
<ClutterDryCategory29>A</ClutterDryCategory29>
<ClutterCategory30>1</ClutterCategory30>
<ClutterDryCategory30>A</ClutterDryCategory30>
<ClutterCategory31>1</ClutterCategory31>
<ClutterDryCategory31>E</ClutterDryCategory31>
<ClutterCategory32>1</ClutterCategory32>
<ClutterDryCategory32>E</ClutterDryCategory32>
<ClutterCategory33>1</ClutterCategory33>
<ClutterDryCategory33>E</ClutterDryCategory33>
<ClutterCategory34>1</ClutterCategory34>
<ClutterDryCategory34>E</ClutterDryCategory34>
<ClutterCategory35>1</ClutterCategory35>
<ClutterDryCategory35>E</ClutterDryCategory35>
<ClutterCategory36>1</ClutterCategory36>
<ClutterDryCategory36>E</ClutterDryCategory36>
</Microwave>
</Atoll>
10.1.12 Macros
The following parameters are saved for macros:
Sample
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<Macros>
<File>
<Path>C:\TestsAddin\testEvents.vbs</Path>
<Language>VBScript</Language>
<Timeout>3600</Timeout>
</File>
</Macros>
</Atoll>
159
Forsk 2016
Sample
<?xml version="1.0" encoding="UTF-8"?>
<PrintConfiguration version="1">
<Page>
<Paper size="" orientation="1"/>
<Margins right="2000" left="2000" bottom="2000" top="2000"/>
<Scale fitToPage="1">12 495</Scale>
</Page>
<Map insideFZonly="1" rulers="1"/>
<Legend>
<LegendPos enable="0" majorPos="3" minorPos="0" insideMap="0"/>
</Legend>
<Comments>
<Position vPos="1" enable="0" hPos="1" insideMap="0"/>
<text></text>
<font height="14" weight="400" charset="1" face="MS Shell Dlg" italic="0"/>
</Comments>
<Logo>
<Position vPos="0" enable="1" hPos="0" insideMap="0"/>
<bitmap></bitmap>
<Dimensions width="46" height="18"/>
</Logo>
<Title>
<Position vPos="0" enable="0" hPos="1" insideMap="0"/>
<text></text>
<font height="14" weight="400" charset="1" face="MS Shell Dlg" italic="0"/>
</Title>
<LogoBottom>
160
AT332_AM_E0
Sample
<?xml version="1.0" encoding="UTF-8"?>
<TITRE>1</TITRE>
<FLD_SEPARATOR><tab></FLD_SEPARATOR>
<DEC_SEPARATOR>.</DEC_SEPARATOR>
<FIELDS>
Site
Transmitter
...
</FIELDS>
<CHOOSEN_FIELDS>
Site
Transmitter
...
</CHOOSEN_FIELDS>
Columns selected in the Columns to be displayed dialogue <SelectedFields> including the field titles <Field> <Title>
Sample
<?xml version="1.0" encoding="UTF-8"?>
<ReportConfiguration>
<SelectedFields>
<Field>
<Title>Surface (km)</Title>
</Field>
<Field>
<Title>% of Covered Area</Title>
</Field>
161
Forsk 2016
...
</SelectedFields>
</ReportConfiguration>
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
...
162
Type
Index
Text
Integer
Real
Date
<Ignore>
AT332_AM_E0
Index
Text
Integer
Long Integer
Single
Double
Date
<Ignore>
Sample
[ConfigurationName]
Header=2
Separator=tab
DecimalSeparator=.
Pattern=*.*
Xindex=1
Yindex=2
Unit=0
Height=1.5
Gain=0
Losses=0
GenericNameIdOne=
GenericNameIdTwo=BSID
IdFormat=Decimal
Techno=IEEE 802.16e
NbCol=21
Col0=1
Col3=1
Col4=4
...
163
Forsk 2016
164
Chapter 11
Initialisation Files
This chapter covers the following topics:
166
AT332_AM_E0
11 Initialisation Files
Initialisation files can be used to store operational and working environment settings. These files are optional, not required
for working with Atoll, but are useful means for selecting required calculation methods and other settings.
This chapter describes the formats of these files in detail:
You can open the Atoll.ini file in the Atoll installation folder for editing by pressing
CTRL+SHIFT+i. If no Atoll.ini file exists, a blank Atoll.ini file is created.
You must restart Atoll in order to take into account modifications made in Atoll.ini.
A given Atoll.ini section, e.g. [GUIUserRights] or [LTE], must occur only once in the file,
with all options pertaining to that section listed under it. If you enter the same section
twice, only the first occurrence of the section will be read and loaded by Atoll.
167
Forsk 2016
Committed Memory: The amount of memory allocated either from the physical memory or from the paging file. This
information is available in the Windows Performance Monitor (Perfmon) under the "Process->Virtual Bytes" counter.
Working Set Memory: The amount of committed memory allocated from the physical memory. The working set
memory is less than or equal to the committed memory. This information is available in the Windows Performance
Monitor (Perfmon) under the "Process->Working Set" counter.
You can set a maximum working set memory per Atoll session by adding the following lines to the Atoll.ini file:
[Memory]
MaximumWorkingSetSize = N
Where N is the maximum working set memory size in MB.
If you set the maximum working set memory to N MB, Atoll will retrieve N MB of memory from the physical memory, if
available, and any additional amount of memory from the paging file, if available. If the amount of retrievable memory from
the paging file is not enough, or if the paging file does not exist on the server, Atoll will try to obtain the additional amount of
memory from the physical memory cache, if available.
A large paging file is recommended.
If required, multiple Atoll shortcuts can also be created, each using a dedicated Atoll.ini file. This enables you to define
different values for the maximum working set memory option in different Atoll.ini files and assign different memory limits to
different users. Once you have created different Atoll.ini files with different values for this option, you can point to these
Atoll.ini files in the path defined in the Atoll shortcut. For more information, see "Atoll Command Line Parameters" on
page 31.
You can also monitor the amount of memory used by an Atoll session using:
The Event Viewer: You can have the maximum working set size defined for the Atoll session displayed in the Atoll
Event Viewer. To do so, add the following lines to the Atoll.ini file:
[Memory]
DisplayMaximumWorkingSetSize = 1
DisplayMaximumWorkingSetSize is set to 0 by default.
The Windows Task Manager: You can monitor the Working Set Memory used by an Atoll session in real time in the
Windows Task Manager's Details tab under the "Working set (memory)" counter.
The Windows Performance Monitor (Perfmon): You can monitor the Working Set Memory used by an Atoll session
in real time in the Windows Performance Monitor via the "Process->Working Set" counter.
168
AT332_AM_E0
[Units]
MilesToMeterFactor = value
When the Prefix parameter is specified, new transmitters are named <prefix>_<number> instead of
<sitename>_<number>.
When the Suffix parameter is specified, new transmitters are named <sitename>_<suffix><number> instead of
<sitename>_<number>.
When both the Prefix and Suffix are specified, new transmitters are named <prefix>_<suffix><number> instead of
<sitename>_<number>.
If you omit the Prefix or Suffix parameters (or if you use Prefix = <AUTO>) the default naming method is used.
It is also possible to remove the underscore character ("_") from the transmitter name. For example, new transmitters can be
named <sitename><number> instead of <sitename>_<number>. To remove the underscore, add the following lines to the
Atoll.ini file:
[Transmitter]
Underscore = 0
By default, Underscore is set to 1. When Underscore is set to 0, the underscore character is omitted in new transmitter names.
You can also specify whether the sequential <number> identifier that is appended to transmitter name should be a numeric
(0-9) or an alphabetic (a-z or A-Z) character. You can also specify whether the numbering sequence starts with 0, 1 or any other
value, or whether the alphabetical sequence starts with a, A (to specify upper or lower case), or any other character. The
following lines define these options in the Atoll.ini file:
[Transmitter]
SuffixIsNum = 0|1
First = <numeric_value>
FirstCharSuffix = <character>
When SuffixIsNum = 1 , new transmitter names are appended with a numeric suffix. The parameter First specifies the
number of the first transmitter in the numbering sequence. For example, if SuffixIsNum = 1 and First = 0, then the
transmitter names will be appended with 0, 1, and 2.
When SuffixIsNum = 0, new transmitter names are appended with a letter. The parameter FirstCharSuffix specifies the
letter of the first transmitter in the alphabetic sequence. For example, if SuffixIsNum = 0 and FirstCharSuffix = a, then
the transmitter names will be appended with a, b, and c.
169
Forsk 2016
Transmitters = 0
3GCells = 0
Repeaters = 0
170
Link the new Atoll document with the externalised calculation results of the original document
AT332_AM_E0
Make copies of the externalised calculation results with the new document
Do not retrieve externalised calculation results for the new document
To set the default option and suppress this dialog box, add the following lines to the Atoll.ini file:
[Settings]
CopyExternalResultsDialog = 0
CopyExternalResults = value
CopyExternalResultsDialog is set to 1 by default. This means that the dialog box appears by default. Setting
CopyExternalResultsDialog to 0 hides the dialog box and the externalised calculation results are managed according to the
value of the CopyExternalResults option:
0: Link the new Atoll document with the externalised calculation results of the original document
1: Make copies of the externalised calculation results with the new document
2: Do not retrieve externalised calculation results for the new document
CopyExternalResultsDialog is ignored when Atoll is run in non-interactive mode, for example using the API, and the
externalised calculation results are managed according to the value of the CopyExternalResults option.
11.1.1.13 Restricting the List of Predictions for Creating Sector Traffic Maps
When you create a sector traffic map, i.e., traffic map based on cell coverage areas, Atoll uses an existing best server coverage
prediction in order to be able to distribute the live traffic data geographically. Atoll lets you select the best server coverage
prediction on which the traffic map will be based. In the list of available best server coverage predictions, Atoll lists all the best
server coverage prediction available in the Predictions folder, whether they were created using a margin or without.
If you want Atoll to list only the best server coverage predictions that were created without a margin, i.e., with 0 dB margin,
you can add the following lines to the Atoll.ini file:
[Studies]
SelectNullMarginOnly = 1
SelectNullMarginOnly is set to 0 by default, which means that Atoll lists all the best server coverage predictions available.
171
Forsk 2016
DisplayOverallSuccessOrFailure = 1
Setting the DisplayInvalidityCause option to 1 will display the cause for which path losses were calculated for each transmitter,
setting DisplayIndividualSuccessOrFailure to 1 will display whether the path loss calculation succeeded or failed for each
transmitter, and setting DisplayOverallSuccessOrFailure to 1 will display the total number of path loss matrices calculated, the
number of path loss matrices calculated successfully, and the number of calculations that failed.
These details are listed in the Events tab of the Event Viewer.
172
AT332_AM_E0
Setting EnableLBS to 1 adds a new coverage prediction export format "LBS Polygon Files (*.txt)" to Atoll. The polygons are
exported in a comma separated values format.
173
Forsk 2016
11.1.1.21 Setting the Precision for the Antenna Pattern Verification at Import
Atoll checks whether the vertical and horizontal patterns are correctly aligned at the extremities. The antenna patterns are
correctly aligned when:
the horizontal pattern attenuation at 0 is the same as the vertical pattern attenuation at the pattern electrical tilt
angle, and
the horizontal pattern attenuation at 180 is the same as the vertical pattern attenuation at the 180 less the pattern
electrical tilt angle.
By default, the option is inactive, i.e., the pattern attenuations are considered the same if they differ less than 100 dB. If you
want to change this default precision, add the following lines to the Atoll.ini file:
[Antenna]
PrecisionTimes10 = X
Where X is the required precision in dB multiplied by 10. For example, if you want to set the precision to 0.5 dB, X will be
0,5 10 = 5 .
11.1.1.23 Keeping the Original List Separator when Exporting in CSV Format
Before exporting in CSV format, Atoll verifies if the list separator symbol is identical to the decimal or digit grouping symbols
defined in your regional settings.
By default, Atoll will change the list separator if it is found to be identical to the decimal symbol or the digit grouping symbols.
You can force Atoll to keep the original list separator symbol by adding the following option in the Atoll.ini file:
[Export]
AlwaysUseListSeparatorInCSV = 1
AlwaysUseListSeparatorInCSV is set to 0 by default.
174
AT332_AM_E0
175
Forsk 2016
[Geo]
FindGeoButtonAlwaysActive = 1
FindGeoButtonAlwaysActive can be useful when you have changed the location of a geographic data file, and you wish to
change the path to the new location. It is set to 0 by default.
When changing the path to a linked geographic data file, you must provide the new path
to the same file. This option does not allow linking to another file instead. In order to link
to another file, you must follow the normal file import procedure.
11.1.1.35 Exporting BMP, TIF, and PNG Files with a TAB Reference File
When exporting BMP, TIF, and PNG files, Atoll can export the georeference information in a TAB file instead of the default
respective World files (BPW or BMW for BMP, TFW for TIF, and PGW for PNG). If you want Atoll to export the georeference
information in a TAB file when you export in BMP, TIF, and PNG formats, add the following lines to the Atoll.ini file:
[RasterExport]
GeorefWithTAB = 1
GeorefWithTAB is set to 0 by default.
176
AT332_AM_E0
11.1.1.40 Adding the Duplicate Site to the Original Sites Site List
When you duplicate a site, you can choose to add the duplicate site to the site list (if any) of the original site by adding the
following lines to the Atoll.ini file:
[Site]
AddToSiteListOnDuplicate = 1
AddToSiteListOnDuplicate is set to 0 by default.
Behaviour
The relative coordinates of the antennas follow the coordinates of the site.
A dialog box appears asking you whether to move the antennas with the site or not.
Duplicate/Moved Sites
By default, when an existing site is duplicated/moved in the map (or when its coordinates are modified from its Properties
dialog box or from the Sites table) while a Real altitude is defined, the same Real altitude is inherited by the duplicate/moved
site. You can force Atoll to clear the duplicate/moved sites Real field or to populate it with the duplicate/moved sites own
DTM value by adding the following lines to the Atoll.ini file:
[Site]
ResetAltitude = 0|1|2
177
Forsk 2016
ResetAltitude is set to 0 by default. The following occurs to the duplicate/moved site according to the setting of ResetAltitude:
ResetAltitude
The Real field of the duplicate/moved site inherits the original sites Real altitude.
The Real field of the duplicate/moved site inherits the duplicate/moved sites own DTM value.
If a sites coordinate(s) and its real altitude are modified at the same time (from the sites
Properties dialog box or from the Sites table), the new value in the Real field will be kept
even if ResetAltitude is set to 1 or 2.
11.1.1.42.2
New Sites
By default, when you create/drop a new site, repeater, remote antenna, or any type of link in the map, the Real field in the
sites Properties dialog boxes is cleared by default. You can force Atoll to populate it with the actual DTM value by setting
ResetAltitude to 2.
ResetAltitude
The Real field of the new site inherits the site own DTM value.
178
AT332_AM_E0
[Pathlosses]
FullResyncPrivShared = 0|1|2
When FullResyncPrivShared is set to 0: invalid private path loss matrices are deleted if shared path loss matrices are
valid when running calculations or checking the validity of path loss matrices (Propagation tab of the transmitter
Properties dialog box). Valid private path loss matrices are preserved.
When FullResyncPrivShared is set to 1: in addition to the 0 setting, valid private path loss matrices are deleted if shared
path loss matrices are valid when checking the validity of path loss matrices.
When FullResyncPrivShared is set to 2: in addition to the 1 setting, valid private path loss matrices are deleted if shared
path loss matrices are valid when running calculations. This setting is not compatible with the use of tuned path loss
matrices.
If you have private path loss matrices tuned using measurement data, setting
FullResyncPrivShared to 2 will force Atoll to delete them automatically when
calculations are run.
You should set FullResyncPrivShared to 1 when working with tuned private path
loss matrices.
11.1.1.48 Filtering Predictions by Technology When Reading the XML Studies File
In the XML studies file, some common CDMA coverage predictions can be available for CDMA2000 and UMTS, or some
common OFDMA coverage predictions can be available for WiMAX and LTE. If you want to filter the customised predictions
stored in the XML studies file by technology, e.g. separate the WiMAX and LTE coverage predictions, and load only the
predictions specific to the technology of the current Atoll document, add the following lines to the Atoll.ini file:
[Studies]
CustomStudiesFilteredByTechno = 1
CustomStudiesFilteredByTechno is set to 0 by default. This option is only relevant for reading the XML studies file. Atoll always
writes the technology type in the XML studies file when customised coverage predictions are saved in it.
179
Forsk 2016
If you set ReportResolution to a very precise (low) value, the performance (calculation
speed) can be considerably decreased depending on the size of the population maps in
the document. It is recommended to set this parameter to an optimum value, i.e., just
precise enough to get the required accuracy.
180
AT332_AM_E0
If you want an add-in neither to be loaded (i.e., deactivated) nor be available in the Add-ins and Macros dialog box,
add the following lines to the Atoll.ini file:
[Add-ins]
Add-in Name = 0
If you want an add-in to be loaded, activated, and accessible in the Add-ins and Macros dialog box for activation/
deactivation, add the following lines to the Atoll file:
[Add-ins]
Add-in Name = 1
If you want an add-in to be loaded and activated, but only shown in the Add-ins and Macros dialog box for information
(impossible to deactivate), add the following lines to the Atoll.ini file:
[Add-ins]
Add-in Name = 2
If you want to set an add-in to be mandatory for Atoll, add the following lines to the Atoll.ini file:
[Add-ins]
Add-in Name = 3
Any add-in set to option 3 will be loaded and activated, but only shown in the Add-ins and Macros dialog box for
information (impossible to deactivate). Atoll will not run if it is unable to load this add-in.
Add-in Name is the name of the add-in as it appears in the Add-ins and Macros dialog box. Atoll fails to start if for some reason
it is unable to load an add-in whose status is set to 3. The default status for add-ins is 1.
181
Forsk 2016
11.1.1.60 Changing the Default Cache Location for the Loaded Map Tiles
The map tiles that you load into Atoll are stored in a specific cache directory named after the corresponding tile server. By
default, the location of this cache is "%TEMP%\OnlineMaps". You can change this location by adding the following lines to the
Atoll.ini file:
[OnlineMaps]
TilesCachePath = new_path
11.1.1.61 Defining the Microsoft Bing Tile Server for Online Maps
If you want to define the Microsoft Bing Maps Server for online maps, you must request a Bing Maps key from Microsoft and
use it with the following option in the Atoll.ini file:
[OnlineMaps]
BingKey = key
You must request your key from Microsoft. When BingKey is specified with a valid key, "Bing" becomes available under
Provider in the Add a Tile Server dialog box. A Type and a Language must also be defined before you can validate.
X = 0 is equivalent to 4th position in the Language list (after the 3 default languages)
culture and language settings can be found in the Culture and Language columns at
the following URL: http://msdn.microsoft.com/en-us/library/hh441729.aspx
11.1.1.62 Defining the Microsoft Bing Tile Server for Online Searches
By default, when you search for a point on the map by its full or partial postal address, Atoll returns specific search results. If
you want to force Atoll to return a list of results based on the Microsoft Bing Maps server, you must request a Bing Maps key
from Microsoft and use it with the following option in the Atoll.ini file:
[OnlineSearch]
BingKey = key
182
AT332_AM_E0
You can specify default paths for the various folders used for saving Atoll files by adding the following lines in the Atoll.ini file:
[DefaultFolders]
183
Forsk 2016
When DefaultStorage is set to 0, favourite views are created and stored in the user profile.
When DefaultStorage is set to 1, favourite views are created and stored in the document.
DefaultStorage is set to 0 by default, which means that favourite views are created and stored in the user profile.
11.1.1.71 Fixing Antenna Electrical Azimuth and Tilt Values on Document Update
Antenna electrical azimuths and tilts are used in calculations to determine the attenuation due to antenna patterns in
different directions. Therefore, it is important that these values be correct. When you update Atoll documents from version
3.2V7.2 to 3.3V7.3, you can have Atoll check and fix any erroneous values in the Antennas table.
If you want Atoll to ignore any errors in the electrical azimuths and tilts, add the following lines to the Atoll.ini file:
[Antenna]
CheckOrFixElecAzAndTilt = 0
If you want Atoll to notify you about any errors in the electrical azimuths and tilts, add the following lines to the
Atoll.ini file:
[Antenna]
CheckOrFixElecAzAndTilt = 1
184
If you want Atoll to notify you about any errors in the electrical azimuths and tilts and fix these errors, add the
following lines to the Atoll.ini file:
AT332_AM_E0
[Antenna]
CheckOrFixElecAzAndTilt = 2
If you want Atoll to notify you about any errors in the electrical azimuths and tilts and set the electrical azimuths to 0,
add the following lines to the Atoll.ini file:
[Antenna]
CheckOrFixElecAzAndTilt = 3
By default, CheckOrFixElecAzAndTilt is set to 1.
185
Forsk 2016
186
AT332_AM_E0
11.1.2.9 Setting the Maximum Number of Lines to Coverage Prediction Tool Tips
If you have more than one coverage prediction displayed on the map, the tool tips display the tip text for all the coverage
predictions available at a pixel up to 30 lines by default. You can change this default number of tool tip text lines through the
following option in the Atoll.ini file:
[Studies]
MultiplePlotsTipTextLines = X
X is the number of lines to display in the tool tips. By default, MultiplePlotsTipTextLines is set to 30. If you set it to a very large
value, however, the tool tip might not display correctly.
DrawSingleElementPattern is set to 1 by default, and the displayed diagram is g n S R Avg S . When you set
H
187
Forsk 2016
11.1.2.14 Increasing the Width of the Clutter Description Pane in the Status Bar
You can increase the width of the clutter description pane in the Status bar (bottom right), to display the descriptions of
clutter classes with long names, by adding the following lines to the Atoll.ini file:
[StatusBar]
ClutterPaneWidth = X
ClutterPaneWidth is set to 100 by default, which means 100% of its default width. To increase the width to, for example, twice
the original width, set ClutterPaneWidth to 200.
188
AT332_AM_E0
The geographic profile displays clutter classes and the Fresnel ellipsoid by default. When the Beamwidth option is set to 1, the
option is enabled and three additional lines are added to the diagram:
Thick upper and lower lines: These lines todicate the upper and lower -3 dB beamwidth limit in the vertical plane.
Thick central line: This line indicates the axis of minimal loss, which coincides with the actual tilt axis of the antenna
(combining the physical and electrical tilt).
You can specify the colors of the lines with the BeamWidthColor, Upper3dbColor, and Lower3dbColor options.
The vertical beamwidth is widest in the azimut axis of the antenna. If you move the position of the Point Analysis tool off of
the antenna azimut axis, the vertical beamwidth diminishes and disappears when the vertical beamwidth loss exceeds -3 dB.
189
Forsk 2016
Here Server1Name and Server2Name refer to the names of the computers being used as calculation servers, and N is a number
from 0 to 9. This means, for example, that Server1 can run up to 10 instances of the distributed calculation application, and
all these instances can be listed in the NumberedServers option (Server1Name0; Server1Name1; Server1Name2; ...). Using
this option, you can assign distributed calculation servers to different groups of users working with two different Atoll.ini files.
For example, user group 1 can use Server1Name0 to Server1Name4, and group 2 can use Server1Name5 to Server1Name9.
If an error occurs on any of the distributed calculation servers, Atoll transfers the calculations back to the local computer.
However, to avoid memory saturation, Atoll uses one thread on the local computer and calculates the path loss matrices one
by one. It does not attempt creating more than one thread.
This option works for both, application and service, modes of the distributed calculation server.
190
Add
GSM = 0
UMTS HSPA
UMTS = 0
CDMA2000
CDMA = 0
AT332_AM_E0
Add
TD-SCDMA
TD-SCDMA = 0
WiMAX = 0
LTE
LTE = 0
LPWA
LPWA = 0
MW = 0
Backhaul
BH = 0
Measurements
Measures = 0
You can also block access to GSM, UMTS, or LTE radio access technologies in 3GPP Multi-RAT documents using these options.
191
Forsk 2016
192
AT332_AM_E0
[Database]
SubCellAuditConsistency = 1
To automatically audit the consistency of redundant values in the transmitters, subcells, and TRXs tables and fix any problems
found, add the following lines to the Atoll.ini file:
[Database]
SubCellAuditConsistency = 2
To automatically audit the compatibility of the main subcell values without fixing any problems found, add the following lines
to the Atoll.ini file:
[Database]
SubCellAuditMainValues = 1
To automatically audit the compatibility of the main subcell values and fixi any problems found, add the following lines to the
Atoll.ini file:
[Database]
SubCellAuditMainValues = 2
SubCellAuditConsistency and SubCellAuditMainValues are set to 0 by default.
193
Forsk 2016
11.1.5.10 Setting the Sign for KClutter When Importing Data From Planet EV
Planet EV uses the opposite sign for the Kclutter parameter with respect to Planet DMS. If you are importing data from Planet
EV, you might have to change the sign of this parameter. You can instruct Atoll to change the sign for Kclutter when importing
data from Planet EV by adding the following lines to the Atoll.ini file:
[PlanetImport]
ChangeKclutterSign = 1
ChangeKclutterSign is set to 0 by default.
11.1.5.11 Setting the Clutter No Data Value for When Importing Data From Planet
EV
Atoll automatically detects undefined clutter class data as No Data when importing data from Planet EV. No Data clutter is
considered transparent on the map and in calculations. You can instruct Atoll to use a specific value as the No Data value when
importing data from Planet EV by adding the following lines to the Atoll.ini file:
[PlanetImport]
ClutterNoData = X
Where X is the No Data value for clutter. ClutterNoData is set to -9999 by default.
Username and password are stored in the ATL file in an encrypted form.
This option is only appropriate if the database connection string contains a password.
194
AT332_AM_E0
11.1.5.17 Displaying Only the First Export to Database Error in a Dialog Box
When a document containing several inconsistencies is exported to a database, you can force Atoll to display only the first
error in a dialog box and log all other inconsistencies in the Events viewer by adding the following lines to the Atoll.ini file:
[Database]
LogExportToDbErrors = 1
LogExportToDbErrors is set to 0 by default.
195
Forsk 2016
diagramme available for the plane to which it corresponds, vertical or horizontal, and an isotropic diagramme (a 0 dB circular
attenuation pattern) for the plane for which no diagramme is available.
InterpolatePatternIndB sets the unit used by Atoll when it performs linear interpolations on antenna pattern attenuation.
When InterpolatePatternIndB = 0 (default), interpolations are calculated in Watts. When InterpolatePatternIndB = 1 (or any
value other than 0), interpolations are calculated in dB leading to stronger antenna pattern attenuation.
11.1.6.4 Setting a Default Value for the Cell Edge Coverage Probability
The default value of the cell edge coverage probability can be configured in the Atoll.ini file. If you enter the following lines to
the Atoll.ini file, Atoll will consider the value of the cell edge coverage probability defined in the Atoll.ini file as the default
value, and will take it into account when performing point analysis, in the shadowing margins calculator, and will propose it
as the default value for coverage prediction studies.
[Shadowing]
Reliability = 60
Reliability = 60 means 60 % cell edge coverage probability.
The value of cell edge coverage probability used for automatic neighbour allocation and
interference matrices calculation is stored in user configuration files (CFG).
196
AT332_AM_E0
[ClutterParams]
IndoorActivity = 1
IndoorActivity is set to 0 by default.
11.1.6.6 Modifying the Resolution for the LOS Area Calculation Around a Site
The calculation of line of sight area around a given site uses the resolution of the geographic data as the default calculation
resolution. These calculations can be time-consuming if the geographic data is available with a very high resolution. You can
set the calculation resolution to a multiple of the resolution of the geographic data by adding the following lines to the Atoll.ini
file:
[LOSArea]
ResolutionMultFactor = X
Where X is an integer. Therefore, setting ResolutionMultFactor to 2 will double the calculation resolution and decrease the
time required for the calculation by half.
11.1.6.9 Warning About Prediction Validity When Display Options are Modified
Coverage predictions have to be recalculated if you modify their display options. Atoll displays a warning message when you
modify the display options for coverage predictions. To deactivate this warning message, add the following lines to the
Atoll.ini file:
[Studies]
RecomputationWarning = 0
RecomputationWarning is set to 1 by default.
197
Forsk 2016
Setting UseSiteAltitude to 0 means that, during calculations, Atoll will read the altitudes from the DTM at the exact
coordinates of each transmitter considering the values entered for the DX and DY parameters.
The above option is also valid for microwave links. In this case, setting UseSiteAltitude to 0 means that, during calculations,
Atoll will read the altitudes from the DTM at the exact coordinates of each microwave link considering the values entered for
the DX_A, DY_A, DX_B, and DY_B parameters.
With UseSiteAltitude = 0, if DX and DY are 0, i.e., for transmitters and microwave links
located at the site coordinates, Atoll will still use the altitudes defined per site, if any, or
the altitudes from the DTM otherwise
NumberOfProcessors is the maximum number of processors that can be used for calculations. If you set this option to
0, Atoll will use the actual number of available processors.
198
AT332_AM_E0
NumberOfThreadsPathloss is the maximum number of threads that can be used for path loss calculations (4 by
default, 8 maximum)
NumberOfThreadsSimulation is the maximum number of threads that can be used for Monte Carlo simulation
calculations (4 by default, 8 maximum)
NumberOfThreadsStudy is the maximum number of threads that can be used for the calculation of coverage
predictions (4 by default, 8 maximum)
NumberOfThreadsStudyTile is the maximum number of threads that can be used per coverage prediction calculation
(0 by default, 8 maximum). If you set this option to 0 or 1 (recommended), Atoll will use one thread for the calculation.
NumberOfThreadsNeighbour is the maximum number of threads that can be used for automatic neighbour allocation
(4 by default, 8 maximum)
NumberOfThreadsMicrowave is the maximum number of threads that can be used for microwave link calculations (4
by default, 8 maximum)
All these options are upper limits per computer. Atoll supports a maximum of 64 parallel threads.
GSM
UMTS HSPA
CDMA2000 (1xRTT and 1xEV-DO)
11.1.6.14.1
11.1.6.14.2
By default, when you open a read-only Atoll document, it is not possible to run calculations in it. If you want to run calculations
in read-only documents, add the following lines to the Atoll.ini file:
[Studies]
ComputeEvenIfReadOnly = 1
If you open a document that is already open in another Atoll session, Atoll lets you open the document as read-only.
199
Forsk 2016
[Studies]
AerialStudy = 1
11.1.6.19 Estimating Required and Used Memory Size for UMTS Simulations
Atoll can estimate the required and used memory sizes for UMTS simulations and display the estimates in the Source Traffic
tab of the new simulation group dialog box. Estimated memory size within the green region means low consumption, within
the yellow region means medium consumption, within the orange region means high consumption, and within the red region
means very high consumption, in which case the simulations might generate an out of memory error and not complete.
This option is only available in the 32-bit version of Atoll.
To activate the memory estimation feature, add the following lines to the Atoll.ini file:
[CDMA]
PredictSimuMemorySize = 1
PredictSimuMemorySize is set to 0 by default which means the feature is not active.
11.1.6.20 Disabling Calculations Over NoData Values for DTM and Clutter Classes
If you dont want Atoll to calculate path losses on the pixels located over nodata values defined in the DTM and clutter classes
files, add the following lines to the Atoll.ini file:
[FskPropagModels]
OptimOnNoData = 1
By default, OptimOnNoData is set to 0. This option only works with the propagation models available with Atoll by default.
200
AT332_AM_E0
201
Forsk 2016
[Neighbours]
DistanceAzimutWeightingPercent = 30 (default)
If the value you set is too high (e.g. 70), the resulting inter-transmitter distance can be
negative. In such a case, nothing will be displayed in the corresponding table cell.
11.1.6.31 Keeping Assigned Neighbours that are not Symmetric with the Reference
Transmitter
By default, when the Force Symmetry option is selected and the neighbour list of a transmitter is full, the reference
transmitter is not added as a neighbour and that transmitter is removed from the reference transmitters neighbours list.
To force Atoll to keep that transmitter in the reference transmitters neighbours list, add the following lines to the Atoll.ini file:
[Neighbours]
DoNotDeleteSymmetrics = 1
DoNotDeleteSymmetrics is set to 0 by default.
202
AT332_AM_E0
[Neighbours]
DeleteOnAuditIfSourceEqualsTarget = false
DeleteOnAuditIfSourceEqualsTarget is set to true by default.
203
Forsk 2016
204
AT332_AM_E0
11.1.7.7 Setting the Best Server Calculation Method in Same Priority HCS Layers
Atoll can calculate serving transmitters according to HCS layer priorities in coverage predictions. The signal level received from
HCS
the serving transmitter must be higher than the minimum reception threshold ( T Rec ) for its HSC layer.
If there are two HCS layers with different priorities:
The serving transmitter is the one that belongs to the HCS layer with the highest priority.
1st strategy: The serving transmitter is the one for which the difference between the received signal level and T HCS
Rec
is the highest. Where, T HCS
Rec is the minimum reception threshold for the HSC layer of each respective transmitter.
2nd strategy: The serving transmitter is the one which has the highest received signal level.
The default strategy is the 1st one. You can use the 2nd strategy by adding the following lines to the Atoll.ini file:
[Studies]
UseThresholdForSameLayerPriorities = 0
UseThresholdForSameLayerPriorities is set to 1 by default.
205
Forsk 2016
11.1.7.10 Hiding Violations from Low Importance GSM Neighbours in AFP Results
By default, each neighbour pair has an importance value which defines the quality (and the rank) of the neighbour link. This
importance can be evaluated during the automatic neighbour allocation, a specific calculation process or manually populated
in the neighbour tables. In the Allocation tab of the AFP results dialog box, no difference is made between high and low
importance neighbours in term of violation display. In other words, whatever the importance value is, any neighbour link in a
separation violation is systematically displayed in a specific colour. You can avoid displaying separation violations between
low importance neighbours in a specific colour by adding the following lines to the Atoll.ini file:
[GSM]
MinNeighbourImportanceInAFPResults = XX
Where XX is the minimum importance for a neighbour pair to be considered as potentially violated.
The value in the Atoll.ini file has to be between 0 and 100 whereas the importance value
in the neighbours tables is between 0 and 1.
206
AT332_AM_E0
Setting CoRedColorThreshPercent and/or AdjRedColorThreshPercent to 0 will force the behaviour of previous versions of
Atoll where important and less important violations were both highlighted.
Worst Case Method: For each interference matrix relationship, the worst case value in all the active interference
matrices is taken into consideration.
First Value Method: For each interference matrix relationship, the first value found in any active interference matrix
is taken into consideration. The order in which the interference matrices are scanned to find the first value is the order
of the interference matrices in the Interference Matrices folder in the Network tab, i.e. the first IM is the one on top.
The First Value Method was the default method in previous versions of Atoll.
That allowed multiple interference matrix imports.
207
Forsk 2016
208
Subcell Value
If it is...
<1 or >62
not 1
Traffic load
<0 or >1
Reception threshold
-102 dBm
Minimum C/I
> 25 dB
12 dB
<0% or >100%
40%
<0 dB or >32 dB
4 dB
DL power reduction
<0 dB or >25 dB
0 dB
AFP weight
<0 or >100
<0% or >100%
0%
<1% or >100%
1%
>62
62
AT332_AM_E0
If you wish to modify this default behaviour, add the following lines to the Atoll.ini file:
[GSM]
SubcellValueFixMethod = 1
SubcellValueFixMethod is set to 0 by default, which corresponds to the default behaviour described above.
If you set this parameter to 1, the values currently out-of-range are shifted to the closest boundary of the authorised range.
For example if the reception threshold is less than -116 dBm, it will be replaced by -116 dBm instead of -102 dBm as in the
default behaviour. Likewise, if it is greater than -50 dBm, it will be replaced by -50 dBm instead of -102 dBm.
11.1.8.2 Disabling Macro-diversity (SHO) Gains Calculation for Ec/Io and Eb/Nt
In UMTS HSPA and CDMA2000 documents, macro-diversity gains are calculated by default for pilot Ec/Io, DL and UL Eb/Nt
based on their respective standard deviations.
You can deactivate the calculation and use of macro-diversity gains for all of the above by adding this option in the Atoll.ini file:
[Shadowing]
WithSHOGain = 0
WithSHOGain is set to 1 by default.
If you want, you can deactivate macro-diversity gain calculations for pilot Ec/Io only by adding this option in the Atoll.ini file:
[CDMA]
AddPilotSHOGain = 0
AddPilotSHOGain is set to 1 by default.
Not display the number of simultaneous HSDPA users in the simulation results.
Display the peak gross and peak application level throughputs per mobile and per cell in the simulation results.
Display the MUG table on the MUG tab of the Proportional Fair properties. Inputs from this is used to calculate the
peak gross throughput per cell when the scheduling algorithm is "Proportional Fair".
209
Forsk 2016
Display the average HSDPA throughput per user in the Cells tab of the simulation results.
HSDPA resource scheduling will not be carried out. The HSDPA throughput for each user will be calculated by taking into
account the MUG corresponding to the current number of connected HSDPA users.
In Average Simulation results, the average HSDPA throughput per user can be calculated excluding the simulations where no
HSDPA users were served. To do this, add the following lines to the Atoll.ini file:
[CDMA]
HSDPAAvgSimuResults = 1
HSDPAAvgSimuResults = 0 by default.
If you set CQIDeltaWithPower to 0, the HS-PDSCH CQI will be calculated using the formula:
EC
EC
CQI HS PDSCH = CQI pilot -------
+ -------
N T pilot N T HS PDSCH
Note that the default configuration (CQIDeltaWithPower set to 1) is relevant only when N T is calculated using the "Total
Noise" option.
The above equations are in dB. Refer to the Technical Reference Guide for more details.
210
AT332_AM_E0
[CDMA]
OrthoInCPICH = 1
211
Forsk 2016
Such a rasterisation means that the number of users in the vector remains correct, but the density might be different since
the surface area has changed (Number of users = User Density x Area).
If you want Atoll to increase the precision of the rasterisation process for hotspots in your network. You can add the following
lines to the Atoll.ini file:
[Rasterization]
Improve = 0 or 1
Precision = 1
SurfRatio = 20
MaximumSurf = 2500
The options are:
Improve = 1 (by default) means that Atoll will use the accurate rasterisation method for small polygons. Improve = 0
means that the normal rasterisation method will be used for all polygons. Setting this option to 1 implies that this
algorithm will not be used globally for all polygons, but only for small polygons which are defined by the options
SurfRatio or MaximumSurf.
Precision = 1 (by default) means that the rasterisation resolution (step) used by the algorithm for small polygons is 1
metre. You can set it to a higher value if you observe performance degradation. The step of rasterisation means the
size of the bin used to approximate the vector shape with bins.
If you set Precision = 1, the performance (calculation speed) can be considerably
decreased depending on the size of your network. It is recommended to set a higher
value for the Precision option.
SurfRatio = 20 (by default) means that the accurate algorithm will be used only for polygons whose size is smaller than
20 times the size of the normal raster bin. The normal raster bin size in anAtoll document is the finest resolution
among the geographic data available in the document.
If your Atoll document contains two geographic data files, one with a 20 m resolution and
the other with a 5 m resolution, and you remove the 5 m one from your document, Atoll
will still keep 5 m as the normal raster bin size.
MaximumSurf = 2500 (by default) means that a polygon will be considered small only if its surface area is less than or
equal to 2500 sq. m.
So, a polygon will be considered small, and will be rasterised using the accurate algorithm, if either the ratio of its surface area
to the surface area of the normal raster bin is equal to or less than SurfRatio, or if its surface area is less than MaximumSurf.
If you want to use just the MaximumSurf option, you can set the SurfRatio to 0.
212
AT332_AM_E0
BestServer_LayerPriority = 0
BestServer_LayerPriority is set to 1 by default.
Before Atoll 2.8.0, best server determination in simulations of UMTS and CDMA networks used to be performed by selecting
the best carrier within transmitters according to the selected method (site equipment) and then the best transmitter using
the best carrier. To switch back to this best server determination method, add the following lines to the Atoll.ini file:
[CDMA]
MultiBandSimu = 0
MultiBandSimu is set to 1 by default.
11.1.8.16 Switching Back to the Old Radio Bearer Allocation Algorithm for Multicarrier EVDO Rev.B
Before Atoll 3.2.1, radio bearer allocation for multi-carrier EVDO Rev.B used to be performed by equally sharing the available
terminal power between the carriers.
To switch back to this radio bearer allocation method, add the following lines to the Atoll.ini file:
[CDMA]
SharingEquallyPower = 1
UsingPreviousIterationPowerWeight = 1
These two options are set to 0 by default.
213
Forsk 2016
In UMTS:
1: Clustered
2: Distributed per Cell
3: One Cluster per Site
4: Distributed per Site
In TD-SCDMA:
1: Clustered
2: Distributed per Cell
3: One SYNC_DL Code per Site
4: Distributed per Site
In CDMA2000:
1: PN Offset per Cell
2: Adjacent PN-Clusters per Site
3: Distributed PN-Clusters per Site
214
AT332_AM_E0
11.1.8.23 Setting the Maximum UL Reuse Factor for HSUPA Users Noise Rise
Estimation
In UMTS HSPA simulations, Atoll assumes a constant uplink reuse factor for estimating the maximum available noise rise per
HSUPA user. This can cause unnecessary rejection of some HSUPA users in very low traffic cases. You can set an upper limit
for the uplink reuse factor by adding the following lines to the Atoll.ini file:
[UMTSSimus]
MaxReuseFactor = value
Where value is 5 by default.
In the Permutation Zones table: Number of Used Subcarriers, Number of Data Subcarriers, and Number of
Subchannels per Channel.
In the Permutation Zones table: Subchannel Groups (Segment 0), Subchannel Groups (Segment 1), and Subchannel
Groups (Segment 2) for FFT sizes < 1000.
In the Permutation Zones table, the first DL PUSC permutation zone cannot be
deactivated.
In the Frame Configurations table and in the General tab of the frame configurations Properties dialog box:
Number of Preamble Subcarriers.
In the Frames Configurations table, the cells under Total Number of Subcarriers change
into combo boxes with the following five values: 128, 256, 512, 1024, 2048.
11.1.9.2 Using Only Bearers Common Between the Terminals and Cells
Equipment
If you want Atoll to perform an intersection over the bearers supported by the cell equipment and by the terminal equipment,
add the following lines to the Atoll.ini file:
[OFDM]
UseCommonBearersOnly = 1
215
Forsk 2016
UseCommonBearersOnly is set to 0 by default. When UseCommonBearersOnly is set to 1, Atoll only uses the bearers for
which selection thresholds are defined in both the terminals and the cells equipment for both downlink and uplink bearer
selection.
11.1.9.5 Excluding Cyclic Prefix Energy in WiMAX and Wi-Fi Signal Level Calculation
The useful signal level calculation can exclude the energy corresponding to the cyclic prefix part of the total symbol duration,
hence taking into account only the energy belonging to the useful symbol duration. In order to do so, you must add the
following lines to the Atoll.ini file:
[WiMAX]
ExcludeCPFromUsefulPower = 1
ExcludeCPFromUsefulPower is set to 0 by default.
Independant of the option, interference levels are calculated for the total symbol durations, including the energy useful
symbol duration and the cyclic prefix energy.
216
AT332_AM_E0
InterNeighbourIDCollisions = 0
InterNeighbourIDCollisions is set to 1 by default.
The physical cell ID audit based on neighbours also takes this option into account. With InterNeighbourIDCollisions = 1, the
audit lists the cell pairs that are neighbours of a cell and are allocated the same physical cell ID. When
InterNeighbourIDCollisions = 0, the physical cell ID collision is not verified between neighbours of a cell.
11.1.9.11 Excluding the Adjacent Channel Overlap from the AFP Cost Functions
The LTE, WiMAX, and Wi-Fi AFPs take the adjacent channel overlap into account for allocation frequencies, physical cell IDs,
preamble indexes, and other resources. If you wish to take only the co-channel overlap into account and exclude the effect of
adjacent channel overlap in resource allocation, add the following lines to the Atoll.ini file:
[OFDM_AFP]
AdjacentProtection = 0
AdjacentProtection is set to 1 by default.
The frequency channels assigned to the interfered and interfering cells have the same centre frequency, and
The interfered and interfering cells both have an even number of frequency blocks or both have an odd number
of frequency blocks, and
The following option is set in the Atoll.ini file (default value):
[LTE]
SameItf_PDSCH_RS_PDCCH = 0
Synchronised transmission and reception means that OFDM symbols of the interfered and interfering frames overlap
and match each other in time.
217
Forsk 2016
The frequency channels assigned to the interfered and interfering cells do not have the same centre frequency, or
The interfered and interfering cells do not both have an even number of frequency blocks or do not both have an
odd number of frequency blocks, or
The following option is set in the Atoll.ini file:
[LTE]
SameItf_PDSCH_RS_PDCCH = 1
This method is also used to calculate interference received from LTE cells of an external network in co-planning and
multi-RAT modes, i.e. inter-technology interference received from LTE cells calculated using inter-technology IRFs.
218
AT332_AM_E0
219
Forsk 2016
220
AT332_AM_E0
221
Forsk 2016
222
AT332_AM_E0
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
calculating interference.
DesignSummaryCfg: corresponds to the Report Configuration dialog box displayed after clicking the Configure Report
button (
223
Forsk 2016
LinkAnalysisCfg: corresponds to the Report Configuration dialog box displayed after clicking the Configure Report
button from the Analysis Report view (MW Analysis window).
LinkInterferenceCfg: corresponds to the Report Configuration dialog box displayed after clicking the Configure Report
button from the Interference Report view (MW Analysis window).
RequiredMarginCfg: corresponds to the Report Configuration dialog box displayed after clicking the Configure Report
button from the Required Margin view (MW Analysis window).
LinksBudgetCfg: corresponds to the Report Configuration dialog box displayed after selecting Microwave Radio Links
> Links > Link Budgets > Configuration Report from the Network explorer.
LinksInterferenceCfg: corresponds to the Report Configuration dialog box displayed after selecting Microwave Radio
Links > Links > Interference > Configuration Report from the Network explorer.
MultihopAnalysisCfg: corresponds to the Report Configuration dialog box displayed after selecting Microwave Radio
Links > Multi-Hops > [Multi-Hop X] > Analysis from the Network explorer.
ReflectionAnalysisCfg: corresponds to the Report Configuration dialog box displayed after:
right-clicking in the Profile Analysis view (MW Analysis window) and selecting Reflection and Diversity Analysis,
then clicking the Configure Report button from the Analysis Report view (MW Reflection/Diversity window).
224
AT332_AM_E0
[MWCalculations]
NewDecouplingCoSite = 0
This option is set to 1 by default. start here
You have to add the following lines to the Atoll.ini file to display this information:
[TestMobileData]
ShowCoupleInfo = 1
Setting ShowCoupleInfo to 0 hides this information.
11.1.12.2 Setting the Number of Transmitters per Drive Test Data Path
By default, Atoll can import information about one serving transmitter (or cell in CDMA documents) and six neighbour
transmitters (or cells in CDMA documents) for drive test data paths. You can change the number of transmitters per drive test
data path by adding the following lines to the Atoll.ini file:
[TestMobileData]
NumberOfTestMobileTransmitters = X
Where X is the number of transmitters per drive test data path. The default value of NumberOfTestMobileTransmitters is 7.
11.1.12.4 Defining the BCCH and BSIC Columns for FMT Import
The .fmt files generated by the TEMS Investigation GSM tool contain a number of columns. To define which of these columns
should be imported as the BCCH column and which one as the BSIC column in Atoll, you can add the following lines to the
Atoll.ini file:
[TestMobileDataImportFmt]
BCCHColumn = Column1
BSICColumn = Column2
Where, Column1 and Column2 are the titles of the two columns in the .fmt file corresponding to the BCCH and the BSIC
columns respectively.
225
Forsk 2016
FloatingPointScramblingCodeSupport is set to 0 by default, and the scrambling codes are imported according to the numeric
data type selected for the scrambling code column in the import dialog box.
11.1.12.6 Importing Drive Test Data for Active and Filtered Transmitters Only
When you import drive test data in Atoll, it assigns servers and neighbours to each measurement point based on the cell
identification method defined for the import. By default, Atoll takes all the transmitters and cells of the document into
account, whether they are active or inactive and filtered or not. If you want Atoll to take only active and filtered transmitters
and cells into account for drive test data import, add the following option in the Atoll.ini file:
[TestMobileData]
ImportForFilteredTransmittersOnly = 1
ImportForFilteredTransmittersOnly is set to 0 by default.
In order for the ACP initialisation file to be used by Atoll, you should place the ACP.ini file in the Atoll installation directory.
You can define a different location for the ACP.ini file as shown in "Specifying the Location of the ACP.ini File" on page 226.
226
The local settings, defined using the ACP - Automatic Cell Planning Properties
dialog box, take precedence over the same settings defined in the global ACP.ini
file. The settings in the ACP.ini file are read when you start a new project to
initialise the settings of the ACP.
When using the ACP.ini file to define options, instead of using the ACP Automatic Cell Planning Properties dialog box, you can also define any other
settings even if they can not be set using the ACP - Automatic Cell Planning
Properties dialog box. These settings redefined locally have precedence over the
global settings.
AT332_AM_E0
11.2.2.3 Default Settings of the Optimisation > Advanced Cost Control Tab
The following options can be used to define the default settings for advanced cost control. Advanced cost control options
allow you to define the maximum number of changes to be made (either as a value or a ratio) and to change the ranking of
the order of cost in the final implementation plan.
The option below allows you to display the Advanced label under Cost Control in the left-hand pane of the Optimisation tab.
It is set to 0 by default.
[ACPGeneralPage]
enableAdvancedCost = 1
The following option enables you to define the importance of cost in the implementation plan. It is set to 1 by default.
[ACPTplGeneralPage]
227
Forsk 2016
cost.planCostWeighting = 0|1|2
#0=low, 1=medium (default), 2=high
The following option enables you to specify the number of changes in the implementation plan. It is set to 0 by default.
[ACPTplGeneralPage]
cost.planLimitType = 0|1|2
#0=unlimited, 1=max as absolute value, 2=max as ratio
1: use cost.planChangeMax to define the max. number of changes in the implementation plan as an absolute value:
cost.planChangeMax = 10
2: use cost.planChangePercent to define the max. number of changes in the implementation plan as a ratio of the
number of antennas currently available in the computation zone:
cost.planChangePercent = 20
When cost.planLimitType is set to 2, you can also set cost.planChangeRefZone to 1 in the [ACPGeneralPage] section
to define the focus zone as the reference zone instead of the computation zone:
cost.planChangeRefZone = 0|1
#0=computation zone (default), 1=focus zone
228
AT332_AM_E0
The following options can be used to define the default values for the technology quality indicators (UMTS Ec/Io, UMTS RSCP,
UMTS overlap, GSM signal level, GSM overlap, WiMAX CINR, WiMAX C/N, LTE C/N, etc.):
[ACPTplObjectivePage]
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.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.cinr.isShadowing = no
param.lte.cinr.cellEdgeCov = 0.75
param.lte.cinr.useFreqBand = 1
param.lte.cinr.useICIC = 1
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.cinr.autoPrediction = yes
param.wimax.cinr.isShadowing = no
param.wimax.cinr.cellEdgeCov = 0.75
param.wimax.cinr.useFreqBand = 1
param.wimax.cinr.useSegmentation = 1
param.wifi.overlap.autoPrediction = yes
param.wifi.overlap.margin = 5
param.wifi.overlap.minRxLevel = -105
param.wifi.coverage.autoPrediction = yes
param.wifi.coverage.isShadowing = no
param.wifi.coverage.cellEdgeCov = 0.75
param.wifi.cinr.autoPrediction = yes
param.wifi.cinr.isShadowing = no
param.wifi.cinr.cellEdgeCov = 0.75
The following options can be used to define the default threshold for each objective rule:
[ACPTplObjectivePage]
229
Forsk 2016
quality.gsm.bcch.threshold = -85
quality.gsm.overlap.threshold = 4
quality.gsm.distance.threshold = 5000
quality.umts.rscp.threshold = -85
quality.umts.ecio.threshold = -13
quality.umts.overlap.threshold = 4
quality.umts.distance.threshold = 5000
quality.cdma.rscp.threshold = -85
quality.cdma.ecio.threshold = -13
quality.cdma.overlap.threshold = 4
quality.cdma.distance.threshold = 5000
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.rssi.threshold = -80
quality.lte.overlap.threshold = 5
quality.lte.distance.threshold = 5000
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.wimax.distance.threshold = 5000
quality.wifi.coverage.threshold = -85
quality.wifi.c.threshold = -85
quality.wifi.cn.threshold = 20
quality.wifi.cinr.threshold = 10
quality.wifi.overlap.threshold = 5
quality.wifi.distance.threshold = 5000
quality.lpwa.coverage.threshold = -130
quality.lpwa.redserver.threshold = 3
The following option can be used to define a default number of servers for the 1st-Nth objective. It is set to 4 by default.
[ACPTplObjectivePage]
NbServers1stNth = value
The following option can be used to remove the Capacity and Load Balancing features from the Objectives tab.
[ACPCapacityPage]
enable = 0
The following option can be used to clear the Scale Traffic according to Zone Weighting check box on the Capacity page:
[ACPCapacityPage]
useZoneWeight = 0
The following options can be used to define a capacity traffic map, either by a BIL file or by a comma-separated list of traffic
map names:
[ACPTplCapacityPage]
traffic.file = c:\tmp\traffic.bil
traffic.maps = user_density_traffic_map; environment_map
traffic.resolution = 50
The following option can be used to avoid recalculating capacity traffic maps after each new run:
[ACPTplCapacityPage]
calculationcapacitytrafficmap = 1
230
AT332_AM_E0
The following option can be used to force ACP to show load balancing and traffic capture results when either feature is
enabled:
[ACPTplCapacityPage]
show.loadbalancingandthroughput = 1
The following options can be used to define the default threshold for each quality (Objectives tab > Capacity page > Services
Definition frame):
[ACPTplCapacityPage]
quality.gsm.bcch.threshold = -85
quality.umts.rscp.threshold = -85
quality.umts.ecio.threshold = -13
quality.cdma.rscp.threshold = -85
quality.cdma.ecio.threshold = -13
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
quality.lte.rssi.threshold = -80
The following options can be used to define the default quality used by each technology for traffic capture condition:
[ACPTplCapacityPage]
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
service.density = 30
The following option can be used to enable the load balancing feature by default:
[ACPTplCapacityPage]
loadBalancing.enable = 1
The following options can be used to specify the load balancing default target coverage (%) and the load balancing weight:
[ACPTplCapacityPage]
loadBalancing.target = 80
loadBalancing.weight = 1
By default, all the zones listed under Zone Parameters on the Optimisation > Zones tab appear in the drop-down list next to
Display on on the Reconfiguration tab (except the KPI zones and lines). You can force ACP to list only the main zones
("Computation", "Focus", "All") in both drop-down lists by adding the following lines to the ACP.ini file:
231
Forsk 2016
[ACPReconfPage]
filter.onlyMainZones = 1
filter.onlyMainZones is set to 0 by default.
The following options can be used to define the default settings for the reconfiguration of power on the Cells vertical tab:
[ACPTplReconfPage]
umts.disablePilotPowerOptimisation = 1
umts.disableMaxPowerOptimisation = 1
umts.SyncMultiCellPower = 1
umts.SyncSiteMultiCellPower = 1
# lock UMTS cell power optimisation for co-site cells
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.1xrtt.SyncSiteMultiCellPower = 0
cdma.1xrtt.disablePilotPowerOptimisation = 1
cdma.1xrtt.disableMaxPowerOptimisation = 1
cdma.1xevdo.SyncMultiCellPower = 1
cdma.1xevdo.SyncSiteMultiCellPower = 0
cdma.1xevdo.disableMaxPowerOptimisation = 1
cdma.defaultPowerAutoMinMax = 3
# automatically set min/max power at an offset of 3dBm around actual value.
# If 0, use fixed value 37-46
gsm.disablePowerOptimisation = 1
gsm.defaultPowerAutoMinMax = 3
# automatically set min/max power at an offset of 3dBm around actual value.
# If 0, use fixed value 37-46
wimax.disablePreamblePowerOptimisation=1
wimax.SyncMultiCellPower = 1
wimax.SyncSiteMultiCellPower = 1
# lock WiMAX cell power optimisation for co-site cells
wimax.defaultPowerAutoMinMax = 3
# automatically set min/max power at an offset of 3dBm around actual value.
# If 0, use fixed value 37-46
lte.disablePowerOptimisation = 1
lte.SyncMultiCellPower = 1
lte.SyncSiteMultiCellPower = 1
# lock LTE cell power optimisation for co-site cells
lte.defaultPowerAutoMinMax = 3
# automatically set min/max power at an offset of 3dBm around actual value.
# If 0, use fixed value 37-46
The following options can be used to define the default settings for the reconfiguration of transmitters and sites:
[ACPTplReconfPage]
disableAntennaOptimisation = 1
disableAzimuthOptimisation = 1
disableHeightOptimisation = 1
disableETiltOptimisation = 1
disableMechTiltOptimisation = 1
disableSiteSelection = 1
disableRepGainOptimisation = 1
disableCandidateSelection = 1
The following options can be used to define default settings for reconfiguration ranges:
[ACPTplReconfPage]
defaultTxAzimuthVariation = 20
defaultTxAzimuthStep = 5
232
AT332_AM_E0
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.disablePilotPowerOptimisation = 0
umts.disableMaxPowerOptimisation = 0
The following options can be used to define a default range for the optimisation of repeater gains:
[ACPTplReconfPage]
defaultRepGainMin = -1
# if -1, the default equipment min value is used
defaultRepGainMax = -1
# if -1, the default equipment max value is used
defaultRepGainStep = 3
# default = 3
The following option can be used to hide the No. Remotes column on the Reconfiguration > Transmitters vertical tab:
[ACPReconfPage]
showNbRemotes = 0
#default = 1 to display the No. Remotes column
The following option can be used to display on the Reconfiguration > Transmitters vertical tab the additional constraint
applied to electrical tilt changes.
[ACPReconfPage]
tx.etilt.deltaLimitConstraint.show = 1
#default = 0
When tx.etilt.deltaLimitConstraint.show = 1, the Variation + column appears under Electrical Tilt (deg). You can enter
a value next to the Variation + header or add the following lines to ACP.ini to define a default value:
[ACPTplReconfPage]
etilt.deltaLimitConstraint = 1,2,...
#default = 0
If etilt.deltaLimitConstraint = 0, the variation constraint is disabled and the Variation + column is greyed.
If etilt.deltaLimitConstraint = 1,2,..., the constraint is enabled and the following appears under Variation +:
A check box which must be selected in order for the constraint to be considered.
A range determined by the value under Current and the value indicated next to the Variation + header.
The Variation + constraint determines one range and the specified Min. and Max. limits determine another range.
The final electrical tilt will fall within the intersection of the two ranges.
You can use the following option to disable proposals for electrical tilt changes below a defined relative variation.
E.g. to disable electrical tilt change proposals for relative variations of 1 degree, you should set this option to 2.
[ACPTplReconfPage]
etilt.relative.min.variation = 2
#default = 1
233
Forsk 2016
The following option can be used to display on the Reconfiguration > Transmitters vertical tab the additional constraint
applied to mechanical tilt changes.
[ACPReconfPage]
tx.tilt.deltaLimitConstraint.show = 1
#default = 0
When tx.tilt.deltaLimitConstraint.show = 1, the Variation + column appears under Mechanical Tilt (deg).
You can enter a value next to the Variation + header or add the following lines to ACP.ini to define a default value:
[ACPTplReconfPage]
tilt.deltaLimitConstraint = 1,2,...
#default = 0
If tilt.deltaLimitConstraint = 0, the variation constraint is disabled and the Variation + column is greyed.
If tilt.deltaLimitConstraint = 1,2,..., the constraint is enabled and the following appears under Variation +:
A check box which must be selected in order for the constraint to be considered.
A range determined by the value under Current and the value indicated next to the Variation + header.
The Variation + constraint determines one range and the specified Min. and Max. limits determine another range.
The final mechanical tilt will fall within the intersection of the two ranges.
You can use the following option to disable proposals for mechanical tilt changes below a defined relative variation.
E.g. to disable mechanical tilt change proposals for relative variations of 1 degree, you should set this option to 2.
[ACPTplReconfPage]
tilt.relative.min.variation = 2
#default = 1
The following option can be used to display on the Reconfiguration > Transmitters vertical tab the additional constraint
applied to global tilt changes (electrical + mechanical).
[ACPReconfPage]
tx.etilt.tilt.sum.deltaLimitConstraint.show = 1
#(Default = 0)
When tx.etilt.tilt.sum.deltaLimitConstraint.show=1, ETilt + MTilt (deg) appears with Current and Variation + columns.
You can enter a value next to the Variation + header or add the following lines to ACP.ini to define a default value:
[ACPTplReconfPage]
etilt.tilt.sum.deltaLimitConstraint = 1|2|...
#(Default = 0)
If etilt.tilt.sum.deltaLimitConstraint = 0, the variation constraint is disabled and the Variation + column is greyed.
If etilt.tilt.sum.deltaLimitConstraint = 1,2,etc., the constraint is enabled and this appears under Variation +:
A check box which must be selected in order for the constraint to be considered.
A range determined by the value under Current (sum of the values under Current for electrical and mechanical
tilts) and the value indicated next to the Variation + header.
The Variation + constraint determines one range and the specified Min. and Max. limits determine another range.
The final gloabl tilt will fall within the intersection of the two ranges.
The final mechanical tilt will fall within the intersection of the two ranges.
The following option allows you to reconfigure inter-sector electrical tilts as asymetrics, i.e. it allows you to obtain different
tilts for sectors belonging to the same site. The value you specify (in degree) is a "minimum difference" constraint if tilts are
reconfigured. If they are not reconfigured, the constraint will not apply.
[ACPTplReconfPage]
etilt.asymetric = 1
#(No default)
The following option can be used to automatically disable reconfiguration of all donors (possibly in cascade) of a repeater:
[ACPTplReconfPage]
autoLockDonor = 0
#(Default = 0)
234
AT332_AM_E0
Possible settings:
Value
Description
The Use check boxes for transmitter reconfiguration parameters are cleared (antenna, tilt,
azimuth, and height). Only the last repeater in a series of cascading repeaters is optimised; the rest
are cleared by default (but can be selected manually).
The Use check boxes for all reconfiguration parameters are cleared (antenna, tilt, azimuth, height,
and power). Only the last repeater in a series of cascading repeaters is optimised; the rest are
cleared by default (but can be selected manually).
Same as 1, except that the Use check boxes can not be selected in the user interface.
Same as 2, except that the Use check boxes can not be selected in the user interface.
235
Forsk 2016
site.custom.0.column=FOO
Where tabularDataColumn displays data issued from Atolls SITES table and identified by site.custom.0.column (column
name). Atoll column names are case sensitive.
The option below defines an optional label for a given column. If unset, the Atoll column name is used (e.g. FOO):
[ACPReconfPage]
site.custom.0.label=The Foo Label
236
AT332_AM_E0
[ACPTplEMFPage]
weightLevel = 1
#(normal, default)
Possible values:
Value
Description
Low: EMF exposure is optimised only if does not worsen coverage quality.
Normal: There is a trade-off between EMF exposure and coverage quality (default).
Critical: EMF exposure is optimised independently from the effect it may have on coverage quality.
The following options enable you to define the default resolution in metres in the X, Y, and Z planes:
[ACPTplEMFPage]
resolutionXY = 5
resolutionZ = 3
The following options define how EMF exposure will be measured in buildings: only on the facade or inside the building as
well:
[ACPTplEMFPage]
onlyFacade=1
#only on facade in building propagation classes. Default = 1 (yes)
buildingDeeping=10
#if onlyFacade is set to 0, the depth in the building measured.
The following option defines whether clutter classes and clutter heights are used to create a 3D representation of the terrain
or whether just vectors are to be used. The default is 1 (yes), but, given that vectors are always given priority where they exist,
this option can be disabled if vectors are available for the entire area of interest.
[ACPTplEMFPage]
useDhmFromClutter=1
# Default is 1 (yes)
The following option defines whether the 3D propagation model is using diffraction. When it is not, only positions with a direct
LOS to transmitters will register EMF exposure.
[ACPTplEMFPage]
useDiffraction = 0
The following option defines whether the EMF module should use transparent mode. When transparent mode is used, no
obstacle or indoor loss is accounted for.
[ACPTplEMFPage]
isWorstCase = 0
# Default is 0 (no)
The following option defines the calculation radius (in metres) around transmitters when calculating EMF exposure:
[ACPTplEMFPage]
calculationRadius = 300
The following options define the default threshold and weight for the EMF exposure objective:
[ACPTplEMFPage]
defaultObjThreshold = 0.6
defaultObjWeight = 1
The following options enable you to define up to 16 propagation classes for EMF exposure. Each class is defined by a name,
an indoor loss, and whether it can be edited by the user.
[ACPTplEMFPage]
237
Forsk 2016
eclass.count = 2
# 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
The following options enable you to map clutter classes to propagation classes. Each mapping is defined on two lines: the first
line defines the clutter class (by its code from the Description tab of the Clutter Classes Properties dialog box); the second
line defines the propagation class (by its ID under Propagation on the Optimisation tab of the ACP Setup dialog box). The
default propagation classes in the ACP are "Open" (ID "0"), "Vegetation" (ID "1"), and "Building" (ID "2"). Any additional
propagation classes will have an ID assigned when they are created.
[ACPTplEMFPage]
clutterMapping.count = 3
clutterMapping.0.clutterCode = 10
clutterMapping.0.classCode = 0
clutterMapping.1.clutterCode = 4
clutterMapping.1.classCode = 1
clutterMapping.2.clutterCode = 6
clutterMapping.2.classCode = 2
clutterMapping.3.clutterCode = 7
clutterMapping.3.classCode = 2
In the [ACPEMFPage] section, you can specify whether or not users can define new propagation classes:
[ACPEMFPage]
isPropClassesExtendable = 1
# 1 enables user to create propagation classes.
238
AT332_AM_E0
[ACPTplMultistoreyPage]
storeyHeight = value
#default = 3
storeyHeight.feet = value
#default=10
The following option can be used to define the traffic weighting method for pixels in storeys, i.e. weight inside buildings Vs.
weight outside buildings (when value = 1, the total weight for all indoor pixels is equal to the weight of an outdoor pixel). The
defined
weighting method will only be considered when the Vertical weight sharing check box is selected.
[ACPTplMultistoreyPage]
weightShareMode = value
#default=1
11.2.2.16.2
239
Forsk 2016
[ACPTplAntennaPage]
defaultETiltMin = 0
#default = 0
defaultETiltMax = 10
#default = 10
You can use the following option if you want to use a regular expression to define a set of antenna patterns on which electrical
tilt constraints will be used automatically. As a result, the Use check box will be selected under Electrical Tilt Constraint ()
and the defined electrical tilt constraints will appear under Min and Max.
[ACPTplAntennaPage]
autoUseEtiltFromRegex=(.*)
Conversely, you can use the autoDisableEtiltFromRegex option if you want to use a regular expression to define a set of
antenna patterns on which electrical tilt constraints will be disabled automatically. As a result, the Use check box is cleared
under Electrical Tilt Constraint () and a dash appears under Min and Max..
[ACPTplAntennaPage]
autoDisableEtiltFromRegex=(.*)
Mechanical Tilt Constraints
You can add the following lines to the ACP.ini file to enable the management of mechanical tilt constraints on antenna
patterns; additional columns appear under Mechanical Tilt Constraint (). When the Use check box is selected, a mechanical
constraint will be applied to the corresponding antenna pattern.
[ACPAntennaPage]
enableMTilt = 1
#default = 0
When enableMTilt is set to 1, you can modify the Min and Max values that appear under Mechanical Tilt Constraint ().
[ACPTplAntennaPage]
defaultTiltMin = 0
#default = 0
defaultTiltMax = 5
#default = 5
You can use the following option if you want to use a regular expression to define a set of antenna patterns on which
mechanical tilt constraints will be used automatically. As a result, the Use check box will be selected under Mechanical Tilt
Constraint () and the defined mechanical tilt constraints appear under Min and Max.
[ACPTplAntennaPage]
autoUseTiltFromRegex=(.*)
Conversely, you can use the autoDisableTiltFromRegex option if you want to use a regular expression to define a set of
antenna patterns on which mechanical tilt constraints will be disabled automatically. As a result, the Use check box is cleared
under Mechanical Tilt Constraint () and a dash appears under Min and Max.
[ACPTplAntennaPage]
autoDisableTiltFromRegex=(.*)
For physical antennas containing several antenna patterns with different electrical tilts, if you set the following option the Use
check box will be selected under Mechanical Tilt Constraint (deg) and a dash appears under Min and Max.
[ACPTplAntennaPage]
autoDisableTiltOnMultiPattern = 1
#default = 0
240
AT332_AM_E0
11.2.2.16.3
The relevant API interface must be implemented in order for the above option to work.
If a value is undefined in a custom field, ACP will use the default value for that
parameter.
241
11.2.2.18.1
Forsk 2016
[ACPCustomFieldExtraction]
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.etilt.deltamin=acp_etilt_deltamin
tx.etilt.deltamax=acp_etilt_deltamax
tx.tilt.optimize=acp_tilt_use
tx.tilt.min=acp_tilt_min
tx.tilt.max=acp_tilt_max
tx.tilt.deltamin=acp_tilt_deltamin
tx.tilt.deltamax=acp_tilt_deltamax
tx.tilt.step=acp_tilt_step
tx.tilt.sum.optimize=acp_tilt_sum_use
tx.tilt.sum.delta=acp_tilt_sum_delta
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
The following options are NOT valid for the SecondaryAntennas table.
[ACPCustomFieldExtraction]
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
242
AT332_AM_E0
The following options are ONLY valid for the GSM Transmitters table.
In GSM, ACP extracts data from custom fields in the GSM Transmitters tables of the Atoll
database and displays it in ACP on the Reconfiguration > GSM Cells vertical tab.
[ACPCustomFieldExtraction]
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
The following options are ONLY valid for the Repeaters table.
[ACPCustomFieldExtraction]
repeater.gain.optimize=acp_gain_use
repeater.gain.min=acp_gain_min
repeater.gain.max=acp_gain_max
repeater.gain.step=acp_gain_step
11.2.2.18.2
243
Forsk 2016
lcell.power.min=acp_power_min
lcell.power.max=acp_power_max
lcell.power.step=acp_power_step
11.2.2.18.3
All sites in the Sites table with the label set to the one defined by the site.status.candidate option will be automatically
set as candidate sites.
Any site in the Sites table with a label other than the one defined by the site.status.candidate option will be considered
as an existing site.
By default, all active sites are considered as existing sites.
[ACPCustomFieldExtraction]
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.
The following options can be used to define custom columns in the Sites table of the Atoll platform. These will be used for
default reconfiguration options for each site.
[ACPCustomFieldExtraction]
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
The following option can be used to manage the Inter Sector Lock check boxes (Height and Azimuth) in the Reconfiguration
column of the Reconfiguration > Sites vertical tab.
The following option can be used to manage the Disable check box in the Reconfiguration column of the Reconfiguration >
Sites vertical tab.
11.2.2.18.4
244
AT332_AM_E0
multi-band antenna. The antenna model is by default set to the PHYSICAL_ANTENNA column of the Antennas table. Hence by
default the auto antenna grouping is always enabled if antenna patterns are correctly assigned to physical antennas.
[ACPCustomFieldExtraction]
antenna.model=PHYSICAL_ANTENNA
If the physical antenna has been defined using the antenna.model option, the following option can be used to name the
custom column in the Antennas table that is used to define antenna groups. In the custom column in the Antennas table, all
antenna patterns corresponding to physical antenna belonging to the same group are identified with a unique string. The ACP
automatically groups all physical antenna into a new group with the name given by the string used in the column.
[ACPCustomFieldExtraction]
antenna.group.model=acp_group_model
The following options can be used to name the custom columns in the Antennas table to automatically define the mechanical
tilt options.
The name of the custom column in ANTENNA table of type 'bool', defining which antenna pattern is associated with
a mechanical tilt constraint:
[ACPCustomFieldExtraction]
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":
[ACPCustomFieldExtraction]
antenna.tilt.min=ACP_TILT_MIN
antenna.tilt.max=ACP_TILT_MAX
The following options can be used to name the custom columns in the Antennas table to automatically define the electrical
tilt options.
In order to optimise the electrical tilt, you must first activate the following option:
[ACPReconfPage]
enableETilt = 1
Optionally, if you want to activate AEDT support, you must also set the following option:
[ACPAntennaPage]
enableAedt = 1
The name of the custom column in the ANTENNA table of type 'bool', defining which antenna pattern is associated
with an 'electrical tilt constraint':
[ACPCustomFieldExtraction]
antenna.etilt.use=ACP_ETILT_USE
ACP supports additional electrical downtilt (AEDT) processing. AEDT is used when antenna patterns are not available
for changes in electrical tilts. The patterns are derived by ACP using geometric downtilts of the original antenna
pattern. When you have activated AEDT support, new columns appear in the Antenna Pattern table on the Antenna
> Patterns vertical tab allowing you to configure which antenna uses AEDT and the range of allowed electrical tilt.
[ACPCustomFieldExtraction]
antenna.aedt.use=ACP_AEDT_USE
The name of the custom columns in the ANTENNA table of type 'string' or numeric, defining the allowed range for
AEDT and electrical tilt. Non-valid values are treated as "forbidden":
[ACPCustomFieldExtraction]
antenna.etilt.min=ACP_ETILT_MIN
antenna.etilt.max=ACP_ETILT_MAX
The following option can be used to name the custom column in the Antennas table to automatically link antenna elements
of a multi-band physical antenna which have the same electrical tilt. In the ACP Setup dialog box, this is accomplished by
selecting the check box in the Same Elec. Tilt column. The antenna.etilt.share option should contain a list of the spaceseparated frequencies for which the corresponding physical antenna must be linked (i.e., physical antenna that always uses
same electrical tilt):
245
Forsk 2016
[ACPCustomFieldExtraction]
antenna.etilt.share=ACP_ETILT_SHARE
11.2.2.19.1
cost.classes.X.azimuth.cost: This key is used to define the cost of changing the antenna azimuth.
cost.classes.X.azimuth.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
cost.classes.X.tilt.cost: This key is used to define the cost of changing the mechanical tilt of the antenna.
cost.classes.X.tilt.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
cost.classes.X.antenna.cost: This key is used to define the cost of changing the type of the antenna.
cost.classes.X.antenna.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
cost.classes.X.etilt.cost: This key is used to define the cost of changing the electrical tilt of the antenna.
cost.classes.X.etilt.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
cost.classes.X.height.cost: This key is used to define the cost of changing the antenna height.
cost.classes.X.height.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
cost.classes.X.power.cost: This key is used to define the cost of changing the power.
cost.classes.X.power.isSiteVisit: This key is set to "true" if this cost entails a site visit; "false" if it does not.
cost.classes.X.siteVisitCost: This key is used to define the cost of a site visit.
cost.classes.X.upgradeSiteCost: This key is used to define the cost of upgrading an existing site.
cost.classes.X.newSiteCost: This key is used to define the cost of creating a new site.
cost.classes.X.removeSiteCost: This key is used to define the cost of removing an existing site.
The following is an example of the keys for the first site class (numbered 0) called "Planned" in this example.
[ACPTplGeneralPage]
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
cost.classes.0.power.isSiteVisit=false
cost.classes.0.siteVisitCost = 2
cost.classes.0.upgradeSiteCost = 5
246
AT332_AM_E0
cost.classes.0.newSiteCost = 10
cost.classes.0.removeSiteCost = -5
11.2.2.19.2
[ACPCustomFieldExtraction]
site.costClass=[name of custom field in Site table]
The site class defined in the Sites table will be assigned automatically when an ACP optimisation is defined. For new candidate
sites which are located on an existing site, the site class is the same as the site on which the new candidate is located. For new
candidate sites which are not co-located on an existing site, the site class is set to "Default" and can be changed manually.
By defining the costs of each site class as explained in "Defining Automatic Site Classes" on page 246, the cost structure is
automatically defined as well.
11.2.2.20.1
There are two possible formats for defining the range of colours on maps:
1. Detailed format: The detailed format enables you to set a non-uniform range. The number of ranges is defined and,
for each range, the minimum and maximum value of the range followed by its RGB color representation.
[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.1=[-15.000000 -13.000000] RGB(0 128 255)
colormap.techno.quality.range.2=[-13.000000 -11.000000] RGB(0 196 196)
colormap.techno.quality.range.3=[-11.000000 -9.000000] RGB(0 224 0)
colormap.techno.quality.range.4=[-9.000000 -7.000000] RGB(128 255 0)
colormap.techno.quality.range.5=[-7.000000 -5.000000] RGB(255 224 0)
colormap.techno.quality.range.6=[-5.000000 -3.000000] RGB(255 128 0)
colormap.techno.quality.range.7=[-3.000000 99999.000000] RGB(255 0 0)
Uniform format description: A uniform format description using a range and step, in one of the following
intervals: [firstBreak startcolor] [lastBreak endColor]
-INF [firstBreak startcolor] [lastBreak endColor]
where interval starts from minus infinite to englobe all lower values and avoid transparent pixels for lower values.
[ACPMapDefault]
colormap.techno.quality.rangeDefinition=[-5 RGB(255 0 0)] [-20 RGB(0 0 255)] -5
colormap.techno.quality.rangeDefinition = -INF[-5 RGB(255 0 0)] [-20 RGB(0 0 255)] -5
247
Forsk 2016
These descriptions are used for default colormap and can easily be changed by the user. The settings are the same for the
various quality indicator in various technologies, where you replace:
In addition, a number of other colormaps can be defined for other types of maps, e.g: overlap maps, objective status maps,
electrical tilt maps, mechanical tilt maps, combined electrical/mechanical tilt maps, change maps, emf maps, etc.
248
AT332_AM_E0
[ACPMapDefault]
colormap.bestcell.etilt
colormap.bestcell.objective
colormap.bestcell.sector
colormap.bestcell.tilt
colormap.bestcell.ttilt
colormap.bestcellHeight
colormap.capacity
colormap.capacitygain
colormap.change.azimuth
colormap.change.cost
colormap.change.etilt
colormap.change.impr
colormap.change.power.cdma
colormap.change.power.gsm
colormap.change.power.lte
colormap.change.power.umts
colormap.change.power.wimax
colormap.change.power2.cdma
colormap.change.power2.umts
colormap.change.selectionType
colormap.change.tilt
colormap.change.ttilt
colormap.change.type
colormap.changeHeight
colormap.diff
colormap.emf
colormap.emf.badSector
colormap.emf.gain
colormap.gain
colormap.imprCoverage
colormap.objective
colormap.objective.gain
colormap.objective.weighting
colormap.overlap
colormap.overlapgain
11.2.2.20.2
249
Forsk 2016
[ACPMapPage]
config.showLegend = 1
# Defines whether the legend is displayed.
config.legendWidth = 40
# Defines the width of the legend in pixels.
config.legendFontSize = 11
# Defines the font used in points.
config.legendForeground = 0
# RGB code as integer: here black
The following option defines whether or not the axis will be displayed on the Quality tab:
[ACPMapPage]
config.showAxis = 1
The following options define the appearance of the histogram on the Quality tab:
[ACPMapPage]
config.showHistogram = 1
# Defines whether the histogram is displayed.
config.histogramHeight = 60
# Defines the width of the histogram in pixels.
The following options define the appearance of the selected zone on the Quality tab:
[ACPMapPage]
config.showZoneSelection = 1
# Defines whether the selected zone is displayed.
config.zoneLighterPercent = 70
# Defines how much lighter selected zone is displayed.
250
AT332_AM_E0
[ACPNewPredictionDlg]
showBestServerLayerPrediction = 1
#default = 0
Setting the following option allows you to create a prediction that displays the weight used for the traffic and for each zone.
[ACPNewPredictionDlg]
showObjectiveWeightPrediction = 1
#default = 0
Setting the following option allows you to create a prediction that displays the improvement in coverage.
[ACPNewPredictionDlg]
showchangeImprovementPrediction = 1
#default = 0
251
Forsk 2016
[ACPXmlReport]
enableXmlExport = 1
# Enable the XML report from the ResultStatPage
generateXmlSection = -1
# Bit combination of the 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 default stylesheet file.
# Set it empty to disable stylesheet processing instruction
Description
-2
The default value means that the propagation model will use the same number of threads as the
number of threads defined by computationThreadPoolSize.
-1
Auto configuration; the propagation model will use one thread for each CPU core.
Other
The defined numerical value indicates the number of threads that the propagation model can use.
252
AT332_AM_E0
memLimitNumPos: Memory use is determined to be excessive when the maximum number of pixels (as defined by
memLimitNumPos) is reached during a calculation. Setting memLimitNumPos to -1 deactivates this option.
memLimitMemory: Memory use is determined to be excessive when the estimated memory use in Mb (as defined by
memLimitMemory) is reached during a calculation. Setting memLimitMemory to -1 deactivates this option.
memLimitUseableMemory: Memory use is determined to be excessive when the estimated memory use exceeds the
percentage of the total memory available for Atoll, as defined in memLimitUseableMemory. Setting
memLimitUseableMemory to -1 deactivates this option.
If all three options are deactivated, ACP does not check excessive memory usage.
The abortIfMemLimitReach option defines how ACP reacts if the defined maximum memory use is reached. By default (with
abortIfMemLimitReach set to 0), ACP will attempt to allocate memory. If unable to successfully allocate memory, ACP displays
a message and the calculation is stopped. When using the option abortIfMemLimitReach, then ACP will not start if the
message indicating excessive memory use is displayed.
By default, excessive memory use is considered an estimate of 80% of the memory available to the process; ACP is not
prevented running even when 80% is exceeded.
When ACP estimates actual memory use (i.e., using either memLimitMemory or
memLimitUseableMemory), the memory estimate is only a rough estimate. Depending
on the project, actual memory usage can be quite different.
[ACPCore]
memLimitNumPos = -1
# -1 deactivates this option.
memLimitMemory = -1
# -1 deactivates this option.
memLimitUseableMemory = 80
# -1 deactivates this option.
abortIfMemLimitReach = 0
When the Progressive threshold check box is selected in the Thresholds Definition dialog box of a given objective, ACP
evaluates the amount of improvement or degradation of the that objective, leading to more intelligent decisions on
improvements that may cause degradations elsewhere in the network.
All other objectives (and the above objectives when the Progressive threshold check box is cleared) are evaluated by ACP on
a "fixed-threshold basis" on each pixel and in a logical manner, whether the objective is met or not.
If you want, you can remove the Progressive threshold check box from the Thresholds Definition dialog box by setting the
following option in the ACP.ini file:
[ACPCore]
useProgressiveThreshold = 0
#default = 1
253
Forsk 2016
The following options define the values used by ACP to control the curve shapes. Although you can modify these settings, they
are the recommended factory values:
[ACPCore]
gsm.signallevel.th.min = -120
gsm.signallevel.th.max = -50
gsmcnircocanal.th.min = 0
gsm.cinrcocanal.th.max = 20
umts.rscp.th.min
umts.rscp.th.max
umts.ecio.th.min
umts.ecio.th.max
=
=
=
=
-120
-60
-20
-6
lte.rsrp.th.min = -130
lte.rsrp.th.max = -70
lte.rscinr.th.min = -10
lte.rscinr.th.max = 30
lte.rsrq.th.min = -20
lte.rsrq.th.max = -8
lte.pdschcinr.th.min = -10
lte.pdschcinr.th.max = 40
wimax.signallevel.th.min = -120
wimax.signallevel.th.max = -50
wifi.signallevel.th.min = -120
wifi.signallevel.th.max = -50
lpwa.signallevel.th.min = -140
lpwa.signallevel.th.max = -50
Description
ACP does not take macro diversity gains into account.
For consistency with the Atoll platform, the following option must be set in the Atoll.ini file:
[CDMA]
AddPilotSHOGain = 0
Default. ACP takes macro diversity gains into account.
ACP uses the same value as the one defined for the AddPilotSHOGain option in the Atoll.ini file:
[CDMA]
AddPilotSHOGain = value
254
AT332_AM_E0
Value
Description
During calculations, ACP will read the altitudes from the DTM at the exact coordinates of each
transmitter considering the values entered for the DX and DY parameters.
Default. This is the value used by the Atoll platform (which uses either the user-defined site
altitudes from the Sites table or, if they are not defined, the site altitudes read from the DTM for
the site coordinates defined in the Sites table).
ACP uses the same value as the one defined for the useSiteAltitude option in the Atoll.ini file:
[Calculations]
useSiteAltitude = value
High Speed: Using the highest speed also uses the least memory although the final results might be slightly less
accurate.
Default: When no changes are made to the ACP.ini file, ACP uses the default settings. The default settings can be
overridden by changing the settings in this section.
High Precision: When the settings in this section are defined to give the results of the highest precision, calculating
the results will take the longest time and will use more memory.
The options described below are those used for the default operation mode.
The ACP.ini options that define how the selected mode works are described below:
255
Forsk 2016
maxMonitorCell: defines the maximum number of cells monitored. This option affects memory use and accuracy. The
analogous options for the high speed mode and the high precision mode are maxMonitorCellSpeed and
maxMonitorCellPrec, respectively.
threshLevelMonitorCell: defines the best server signal threshold (dB) in order to be monitored. This option affects
memory and accuracy.
The analogous options for the high speed mode and the high precision mode are threshLevelMonitorCellSpeed and
threshLevelMonitorCellPrec, respectively.
The following options define the values ACP uses for default mode:
[ACPCore]
maxMonitorCell = 32
threshLevelMonitorCell = 35
The following options define the values ACP uses for high speed mode:
[ACPCore]
maxMonitorCellSpeed = 30
threshLevelMonitorCellSpeed = 30
The following options define the values ACP uses for high precision mode:
[ACPCore]
maxMonitorCellPrec = 35
threshLevelMonitorCellPrec = 40
Other options in the ACP.ini file can be used to define additional offsets that will be used by the specific technology that ACP
is optimising:
[ACPCore]
threshLevelOffGsm = 0
maxMonitorOffGsm = 0
threshLevelOffUmts = 0
maxMonitorOffUmts = 0
threshLevelOffCdma = 0
maxMonitorOffCdma = 0
threshLevelOffLte = 10
maxMonitorOffLte = 10
threshLevelOffWimax = 5
maxMonitorOffWimax = 5
threshLevelOffWifi = 5
maxMonitorOffWifi = 5
threshLevelOffLpwa = 20
maxMonitorOffLpwa = 20
256
AT332_AM_E0
[ACPCore]
gisDataCacheStrategy = 1
# default = 1
When you set the following option, ACP will consider a mix or raster data and polygons for the DLU file (should be set to 1
when clutter classes are edited with the clutter editor):
[ACPCore]
gisDataClutterUsePoly = 0
# default = 0
When you set the following option, ACP creates multistorey points for areas where the DLU file is present (with default
heights) without the presence of DHM raster (clutter height). The default setting (TRUE) makes the ACP distribute vertical
points only where DHM is available:
[ACPCore]
multistorey.onlyDHM = TRUE|FALSE
# default = TRUE
11.2.3.14 Fixed Ratio Between Pilot Power and Max Power (UMTS)
When optimising the maximum cell power in UMTS, the ACP forces the ratio between pilot power and maximum power to
stay constant. You can remove this constraint using the following option:
[ACPCore]
umtsPilotPowerRatioFixed = 0
257
Forsk 2016
custom.count = 2
#default = 2
You can then set the following options to specify the data you want to show under each custom column.
custom.0.type=tabularDataColumn
custom.0.column=FOO
custom.0.label=FOO label of custom.0.column
custom.1.type=tabularDataColumn
custom.1.column=BAR
258
AT332_AM_E0
flagPixelFacadeDist = distance
flagPixelFacadeDist defines (in metres) the indoor distance from facade for a pixel to be considered as "indoor". When the
distance is 0, the outdoor pixels will be applied the indoor penetration loss specified in the Propagation Class Definition table
(Propagation page on the Optimisation tab).
To enable ("1") or disable ("0") the automatic check of the path loss matrix files (file location and file size) before a run:
autoCheckPathlossFileValidity = 0|1
autoCheckPathlossFileValidity is set to 1 by default.
To enable ("1") or disable ("0") the automatic recalculation of invalid path loss matrices before running an
optimisation setup:
autoPathlossRecomputation = 0|1
autoPathlossRecomputation is set to 1 by default.
To enable ("1") or disable ("0") the automatic check of active transmitter number:
autoCheckTxNumber = 0|1
autoCheckTxNumber is set to 1 by default.
259
260
Forsk 2016
AT332_AM_E0
A
acp.ini main options
Calculation Thread Pool Settings
computationThreadPoolSize 252
useComputationThreadPool 252
Custom columns on Transmitters and Remote tabs of Reconfiguration page
236
tx.custom.x.column 236
tx.custom.x.label 236
tx.custom.x.type 236
Default Values on the Antennas Tab
enableAedt 239
Default Values on the Optimisation Tab
cost.antenna.cost 227
cost.antenna.isSiteVisit 227
cost.azimuth.cost 227
cost.azimuth.isSiteVisit 227
cost.etilt.cost 227
cost.etilt.isSiteVisit 227
cost.height.cost 227
cost.height.isSiteVisit 227
cost.newSiteCost 227
cost.power.cost 227
cost.power.isSiteVisit 227
cost.removeSiteCost 227
cost.siteVisitCost 227
cost.tilt.cost 227
cost.tilt.isSiteVisit 227
cost.upgradeSiteCost 227
Default Values on the Patterns tab of the Antenna Tab
enableMTilt 239, 240
Default Values on the Reconfiguration Tab
233
defaultRepGainMax 233
defaultRepGainMin 233
defaultRepGainStep 233
defaultTxAzimuthMinInterSector 232
defaultTxAzimuthStep 232
defaultTxAzimuthVariation 232
defaultTxETiltMax 233
defaultTxETiltMin 232
defaultTxHeightMax 233
defaultTxHeightMax.feet 233
defaultTxHeightMin 233
defaultTxHeightMin.feet 233
defaultTxHeightStep 233
defaultTxHeightStep.feet 233
defaultTxTiltMax 232
defaultTxTiltMin 232
defaultTxTiltStep 232
etilt.relative.min.variation 233
showNbRemotes 233
tx.etilt.deltaLimitConstraint.show 233
tx.tilt.deltaLimitConstraint.show 233, 234
261
262
Forsk 2016
AT332_AM_E0
License, MW 191
License, TD-SCDMA 191
License, TimeBombNotice 190
License, UMTS 190
License, WiMAX 191
License, WiMAX_AFP 191
LOSArea, ResolutionMultFactor 197
LTE, ApplyDLLoadOnPDCCHInterf 218
LTE, CASchedulingMethod 220
LTE, CAWithinENB 219
LTE, CellEdgeMethod 220
LTE, DisplaySignalsPerSCInPtA 215
LTE, eICIConRS 219
LTE, EIRPfromRSEPRE 218
LTE, ExcludeCPFromUsefulPower 216
LTE, InterNeighbourIDCollisions 216
LTE, NR_CONTROL_MARGIN_MIN 219
LTE, OldBestServerMethodForCA 220
LTE, SameItf_PDSCH_RS_PDCCH 217
LTE, ServiceMBRDowngrading 218
LTE, ULNRControlMethod 219
LTE, ULNRControlPrecision 219
LTE, UseABSonCellEdgeOnly 219
MajorVersionChange, EnablePartialRefreshInMigration 195
Memory, DisplayMaximumWorkingSetSize 168
Memory, MaximumWorkingSetSize 168
MITAB, Coordinate system definition in the header file 172
MITAB, DisableNormalization 177
MITAB, EnableMessages 179
MITAB, OptimizedTABExport 177
MultiRAT, AllCodesAllocWithInterRATNeighbours 221
MultiRAT, UncheckTechnoChoices 222
MWCalculations, CCDP_XPIF 222
MWCalculations, HIDE_REC530_5 223
MWCalculations, ShieldingFactorOnWantedSignal 222
MWCalculations, UpdateOppositeHop 222
MWChannelArrangement, DefaultConfiguration 224
MWProfile, AlwaysDrawClutters 224
MWReport, DefaultTemplate 224
MWReport, DesignSummaryCfg 223
MWReport, LinkAnalysisCfg 223
MWReport, LinkInterferenceCfg 223
MWReport, LinksBudgetCfg 223
MWReport, LinksInterferenceCfg 223
MWReport, MultihopAnalysisCfg 223
MWReport, ReflectionAnalysisCfg 223
MWReport, RequiredMarginCfg 223
MWReport, tab 223
Neighbours, CandidatesMaxDistanceInImportanceCalculation
202
263
264
Forsk 2016
AT332_AM_E0
265
Head Office
7 rue des Briquetiers
31700 Blagnac, France
Tel: +33 562 747 210
Fax: +33 562 747 211
AT332_AM_E0
US Office
China Office
www.forsk.com
November 2016