Professional Documents
Culture Documents
v e r s i o n 3.1.0
AT310_AM_E2
Suite 3100
31700 Blagnac
Chicago, IL 60606
France
USA
sales_us@forsk.com
sales@forsk.com
enquiries@forsk.com.cn
support_us@forsk.com
support@forsk.com
atollsupport@forsk.com.cn
Monday - Friday
Monday - Friday
Monday - Friday
www.forsk.com
Atoll 3.1.0
Administrator Manual
Forsk 2011
AT310_AM_E2
Table of Contents
1
1.1
1.2
1.3
1.4
1.5
1.5.1
1.5.2
1.5.3
1.5.4
1.5.5
1.6
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
3
3.1
3.2
3.3
4
4.1
4.1.1
4.1.2
4.1.3
4.2
4.2.1
4.2.2
5
5.1
5.2
5.3
5.3.1
5.3.2
5.4
5.5
5.5.1
5.5.2
5.5.3
5.6
5.7
5.7.1
5.7.2
5.7.3
5.7.4
5.8
5.9
5.9.1
5.9.2
6
6.1
6.2
6.2.1
6.2.2
6.2.3
6.2.4
6.2.5
6.3
6.3.1
6.3.2
6.4
6.4.1
6.4.2
6.4.3
6.4.4
7
7.1
7.1.1
7.1.2
7.1.3
7.1.4
7.2
7.3
8
8.1
8.2
8.3
8.4
8.5
8.6
8.7
8.8
8.9
8.9.1
8.9.1.1
8.9.2
8.9.2.1
8.9.3
8.9.3.1
8.9.3.2
8.9.3.3
8.9.3.4
8.9.4
8.9.4.1
8.9.5
8.9.6
8.9.7
8.9.8
8.9.9
8.9.10
8.9.11
8.9.12
8.9.13
8.9.14
8.9.15
8.9.15.1
8.9.15.2
8.9.15.3
8.9.15.4
8.9.15.5
Forsk 2011
Multi-user Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Setting Up Multi-user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Components of Multi-user Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Master Atoll Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Master Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Shared Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Shared Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
User Atoll Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Managing User Accounts and Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Defining Database and Interface Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
Creating and Editing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Appendix 1: Checking Data Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Appendix 2: Database Regionalisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Appendix 3: Calculating Path Loss Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Appendix 4: Path Loss Matrices From Different Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Geographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Digital Terrain Model (DTM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Clutter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
Clutter Heights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Vector Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Population Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Custom Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Geographic Data File Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
BIL Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
HDR Header File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89
TIFF Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
TFW Header File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
BMP Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
BMP File Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
BMP Raster Data Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
Raster Data Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
BPW/BMW Header File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
PNG Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
PGW Header File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
DXF Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
SHP Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
MIF Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
TAB Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
ECW Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
Erdas Imagine Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
Planet EV/Vertical Mapper Geographic Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
ArcView Grid Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Other File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Generic Raster Header File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
Planet Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
DTM Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Clutter Class Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Vector Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Image Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Text Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
AT310_AM_E2
8.9.15.6
9
9.1
9.1.1
9.1.2
9.2
9.3
9.4
9.5
9.5.1
9.5.2
9.6
9.6.1
9.7
9.7.1
9.7.2
9.7.3
9.8
9.8.1
9.8.2
9.8.3
9.9
9.9.1
9.9.1.1
9.9.1.2
9.9.2
9.9.3
9.9.4
10
10.1
10.2
10.3
10.4
10.5
10.6
10.7
10.8
10.9
10.10
10.11
10.12
10.13
10.14
10.14.1
10.14.2
11
11.1
11.1.1
11.1.2
11.1.3
11.1.4
11.1.5
11.1.6
11.1.7
11.1.8
11.1.9
11.1.10
11.2
11.2.1
11.2.2
11.2.3
11.2.4
11.2.5
11.3
12
12.1
12.1.1
12.1.1.1
12.1.1.2
12.1.1.3
12.1.1.4
12.1.1.5
12.1.1.6
12.1.1.7
12.1.1.8
12.1.1.9
12.1.1.10
12.1.1.11
12.1.1.12
12.1.1.13
12.1.1.14
12.1.1.15
12.1.1.16
12.1.1.17
12.1.1.18
12.1.1.19
12.1.1.20
12.1.1.21
12.1.1.22
12.1.1.23
12.1.1.24
12.1.1.25
12.1.1.26
12.1.1.27
12.1.1.28
12.1.1.29
12.1.1.30
12.1.1.31
12.1.1.32
12.1.1.33
12.1.1.34
12.1.1.35
12.1.1.36
12.1.1.37
12.1.2
12.1.2.1
12.1.2.2
12.1.2.3
12.1.2.4
12.1.2.5
12.1.2.6
12.1.2.7
12.1.2.8
12.1.2.9
12.1.2.10
12.1.2.11
12.1.2.12
12.1.3
12.1.3.1
12.1.3.2
12.1.3.3
12.1.4
12.1.4.1
12.1.4.2
12.1.4.3
12.1.4.4
Forsk 2011
169
169
169
170
170
170
171
171
171
172
172
172
173
173
173
174
174
174
174
174
174
175
175
175
175
175
176
176
176
176
176
177
177
177
177
177
178
178
178
178
178
179
179
179
179
179
180
180
180
180
180
181
181
181
181
181
182
182
182
182
183
AT310_AM_E2
12.1.5
12.1.5.1
12.1.6
12.1.6.1
12.1.6.2
12.1.6.3
12.1.6.4
12.1.6.5
12.1.6.6
12.1.6.7
12.1.6.8
12.1.7
12.1.7.1
12.1.7.2
12.1.7.3
12.1.7.4
12.1.7.5
12.1.7.6
12.1.7.7
12.1.7.8
12.1.7.9
12.1.7.10
12.1.7.11
12.1.7.12
12.1.7.13
12.1.7.14
12.1.7.15
12.1.7.16
12.1.7.17
12.1.7.18
12.1.7.19
12.1.7.20
12.1.7.21
12.1.7.22
12.1.7.23
12.1.7.24
12.1.7.25
12.1.7.26
12.1.8
12.1.8.1
12.1.8.2
12.1.8.3
12.1.8.4
12.1.8.5
12.1.8.6
12.1.8.7
12.1.8.8
12.1.8.9
12.1.8.10
12.1.8.11
12.1.8.12
12.1.8.13
12.1.8.14
12.1.8.15
12.1.9
12.1.9.1
12.1.9.2
12.1.9.3
12.1.9.4
12.1.9.5
12.1.9.6
12.1.9.7
12.1.9.8
12.1.9.9
12.1.9.10
12.1.9.11
12.1.9.12
Forsk 2011
12.1.9.13
Adjusting the Working of the Proportional Fair Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.9.14
Displaying Ec/I0 of Rejected Mobiles in Simulation Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.9.15
Switching Back to the Old Best Server Determination Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.9.16
Displaying Automatic Allocation Cost Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.9.17
Selecting SC and PN Offset Allocation Strategies Available in the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.9.18
Defining a Fixed Interval Between Scrambling Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.9.19
Compressed Mode: Restricting Inter-carrier and Inter-technology Neighbour Allocation . . . . . . . . . . . . . . . . . . . . . . .
12.1.9.20
Setting the Maximum AS Size for SC Interference Prediction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.9.21
Displaying Uplink Total Losses in Coverage by Signal Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.9.22
Setting the Maximum UL Reuse Factor for HSUPA Users Noise Rise Estimation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10
WiMAX and LTE Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10.1
Blocking Access to IEEE Parameters in WiMAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10.2
Using Only Bearers Common Between the Terminals and Cells Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10.3
Disabling Multi-antenna Interference Calculation in LTE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10.4
Enabling Display of Signals per Subcarrier Point Analysis in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10.5
Enabling Multi-antenna Interference Calculation in WiMAX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10.6
Including Cyclic Prefix Energy in LTE Signal Level Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10.7
Excluding Cyclic Prefix Energy in WiMAX Signal Level Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10.8
Ignoring Inter-Neighbour Preamble Index Collision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10.9
Ignoring Inter-Neighbour Physical Cell ID Collision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10.10
Renaming OPUSC Zone to PUSC UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10.11
Deactivating Uniform Distribution of Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10.12
Activating Basic Preamble Index/Physical Cell ID Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10.13
Taking Second Order Neighbours into Account in the AFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.10.14
Setting PDCCH to 100% Loaded in LTE Interference Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.11
Microwave Radio Links Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.11.1
Excluding Near-field Interference from Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.11.2
Excluding Standby Channels from Interference Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.11.3
Updating A>>B and B>>A Profiles in Real-time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.11.4
Disabling Sheilding Factor on Wanted Signal at Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.11.5
Using Old Min C/I Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.11.6
Defining Channel Number Prefix and Suffix for Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.12
Measurement Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.12.1
Displaying Additional Information in Drive Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.12.2
Setting the Number of Transmitters per Drive Test Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.12.3
Recalculating Distances of Points From There Serving Cells at Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.12.4
Defining the BCCH and BSIC Columns for FMT Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1.12.5
Importing Drive Test Data with Scrambling Codes as Integers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2
ACP Initialisation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.1
Managing Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2
GUI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.1
Default Values on the Optimisation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.2
Automatically Creating Custom Zones on the Optimisation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.3
Default Values on the Objectives Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.4
Default Values on the Reconfiguration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.5
Default Values for EMF Exposure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.6
Default Values on the Antennas Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.7
Defining the Functionality of the ACP - Automatic Cell Planning Properties Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.7.1
Defining the Antenna Masking Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.8
Defining Reconfiguration Values in Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.8.1
Defining Reconfiguration Values for Transmitters and Repeaters Using Custom Atoll Fields. . . . . . . . . . . . . . . . . . .
12.2.2.8.2
Defining Reconfiguration Values for Cells Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.8.3
Defining Reconfiguration Values for Sites Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.8.4
Defining Reconfiguration Values for Antennas Using Custom Atoll Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.9
Defining Site Class Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.9.1
Defining Automatic Site Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.9.2
Automatically Assigning Site Classes in the ACP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.10
Defining the Appearance of the Optimisation Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.10.1
Defining the Colours in the Quality Analysis Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.10.2
Other Components of the Optimisation Dialogue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.11
Defining the Appearance of New Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.12
Defining the Functionality of the Commit Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.13
Defining the Appearance of the Overlay Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.14
Defining the Appearance of the Graph Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.15
Defining the Default Font . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2.16
Exporting Optimisation Results in XML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
198
198
198
199
199
199
199
199
200
200
200
200
200
201
201
201
201
201
202
202
202
202
202
203
203
203
203
203
203
203
204
204
204
204
204
204
205
205
205
205
206
206
206
207
211
213
214
214
214
215
215
216
217
217
218
218
219
219
219
220
221
221
221
221
221
222
AT310_AM_E2
12.2.3
12.2.3.1
12.2.3.2
12.2.3.3
12.2.3.4
12.2.3.4.1
12.2.3.4.2
12.2.3.5
12.2.3.6
12.2.3.7
12.2.3.8
12.2.3.9
12.2.3.10
12.2.3.11
12.2.3.12
12.2.3.13
12.2.3.14
12.2.3.15
12.2.4
12.2.5
12.2.5.1
13
13.1
13.1.1
13.1.2
13.2
13.3
13.4
13.5
13.6
13.7
13.8
13.9
13.10
13.11
13.12
13.13
13.14
13.15
13.16
13.17
13.18
13.19
13.20
13.21
13.22
13.23
13.24
13.25
13.26
13.27
13.28
13.29
13.30
13.31
13.32
13.33
13.34
13.35
13.36
13.37
13.38
13.39
13.40
13.41
11
13.42
13.43
13.44
13.45
13.46
13.47
13.48
13.49
13.50
13.51
13.52
13.53
13.54
13.55
13.56
13.57
13.58
13.59
13.60
13.61
13.62
13.63
14
14.1
14.1.1
14.1.2
14.2
14.3
14.4
14.5
14.6
14.7
14.8
14.9
14.10
14.11
14.12
14.13
14.14
14.15
14.16
14.17
14.18
14.19
14.20
14.21
14.22
14.23
14.24
14.25
14.26
14.27
14.28
14.29
14.30
14.31
14.32
14.33
14.34
14.35
14.36
14.37
14.38
14.39
14.40
12
Forsk 2011
Receivers Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RepeaterEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Repeaters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SecondaryAntennas Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SeparationRules Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Separations Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sites Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SitesLists Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SitesListsNames Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TMAEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TplTransmitters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transmitters Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TRGConfigurations Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TRGs Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TRXEquipments Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TRXs Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TRXTypes Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSConfigurationNames Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSConfigurations Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TxsLists Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TxsListsNames Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Units Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
249
249
250
250
251
251
251
252
252
252
252
254
256
257
259
259
260
260
260
261
261
261
266
266
267
268
268
269
270
271
271
272
273
273
273
274
274
274
274
275
275
276
276
276
276
277
277
277
278
278
279
279
280
280
280
281
282
282
282
282
283
283
283
284
AT310_AM_E2
14.41
14.42
14.43
14.44
14.45
14.46
14.47
14.48
14.49
14.50
14.51
14.52
14.53
14.54
14.55
14.56
15
15.1
15.1.1
15.1.2
15.2
15.3
15.4
15.5
15.6
15.7
15.8
15.9
15.10
15.11
15.12
15.13
15.14
15.15
15.16
15.17
15.18
15.19
15.20
15.21
15.22
15.23
15.24
15.25
15.26
15.27
15.28
15.29
15.30
15.31
15.32
15.33
15.34
15.35
15.36
15.37
15.38
15.39
15.40
15.41
15.42
15.43
15.44
15.45
15.46
13
15.47
15.48
15.49
16
16.1
16.2
16.3
16.4
16.5
17
17.1
17.1.1
17.1.2
17.2
17.3
17.4
17.5
17.6
17.7
17.8
17.9
17.10
17.11
17.12
17.13
17.14
17.15
17.16
17.17
17.18
17.19
17.20
17.21
17.22
17.23
17.24
17.25
17.26
17.27
17.28
17.29
17.30
17.31
17.32
17.33
17.34
17.35
17.36
17.37
17.38
17.39
17.40
17.41
17.42
17.43
17.44
17.45
17.46
17.47
17.48
17.49
17.50
17.51
17.52
14
Forsk 2011
325
326
327
329
331
338
338
339
340
340
340
341
342
342
343
344
344
344
345
345
345
345
346
346
346
346
347
347
347
348
348
349
349
349
350
350
350
351
351
352
352
352
353
353
353
356
357
357
357
357
358
358
358
360
360
361
362
362
362
AT310_AM_E2
18
18.1
18.1.1
18.1.2
18.2
18.3
18.4
18.5
18.6
18.7
18.8
18.9
18.10
18.11
18.12
18.13
18.14
18.15
18.16
18.17
18.18
18.19
18.20
18.21
18.22
18.23
18.24
18.25
18.26
18.27
18.28
18.29
18.30
18.31
18.32
18.33
18.34
18.35
18.36
18.37
18.38
18.39
18.40
18.41
18.42
18.43
18.44
18.45
18.46
18.47
18.48
18.49
18.50
18.51
18.52
18.53
18.54
18.55
18.56
18.57
18.58
18.59
18.60
15
19
19.1
19.1.1
19.1.2
19.2
19.3
19.4
19.5
19.6
19.7
19.8
19.9
19.10
19.11
19.12
19.13
19.14
19.15
19.16
19.17
19.18
19.19
19.20
19.21
19.22
19.23
19.24
19.25
19.26
19.27
19.28
19.29
19.30
19.31
19.32
19.33
19.34
19.35
19.36
19.37
19.38
19.39
19.40
19.41
19.42
19.43
19.44
19.45
19.46
19.47
19.48
19.49
20
20.1
20.1.1
20.1.2
20.1.3
20.1.4
20.2
20.3
20.4
20.5
20.6
20.7
20.8
16
Forsk 2011
401
401
405
405
405
406
407
407
407
408
408
408
409
409
409
410
410
411
412
412
413
413
413
414
414
415
415
415
416
416
416
416
419
420
420
420
421
421
421
421
423
423
423
424
424
424
425
426
426
427
427
429
429
432
433
433
435
436
436
437
437
437
437
AT310_AM_E2
20.9
20.10
20.11
20.12
20.13
20.14
20.15
20.16
20.17
20.18
20.19
20.20
20.21
20.22
20.23
20.24
20.25
20.26
20.27
20.28
20.29
20.30
20.31
20.32
20.33
20.34
20.35
20.36
20.37
20.38
17
18
Forsk 2011
Part 1
Getting Started
This part of the administrator manual provides the information
to install and set up Atoll and its components, and to
manage databases and multi-user environments.
AT310_AM_E2
1 Getting Started
Atoll is an open, scalable, and flexible multi-technology network design and optimisation platform that supports wireless
operators throughout the network lifecycle, from initial design to densification and optimisation. Atoll supports a wide range
of implementation scenarios, from standalone to enterprise-wide server-based configurations using distributed and multithreaded computing.
This manual explains how to install, configure, and deploy Atoll and how to set up back-end databases and manage users in a multiuser environment. Database structures of the different technology modules are also provided for reference.
In this chapter, the following are explained:
The physical location of databases varies according to the type of the database. The following table shows where the database
must be installed:
21
a.
Forsk 2011
Database
Server
Client computer
Microsoft Access
No
Yesa
Yes
No
Oracle
Yes
Sybase
Yes
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.
Standalone configuration
Atoll installed on each individual user computer with a fixed licence key plugged in each computer.
a.
Processor
Dual-core or better
RAM
2 GB or more
At least 10 GBa
Operating system
Other requirements
- Fixed licence: 1 USB port required to plug-in the fixed licence key
- Floating licence: nethasp.ini file in the Atoll installation folder
Depends on the size of the locally stored geographic data and path loss matrices, if any.
If you are working with an Oracle database, you must install Oracle client on the user computers as well. The Oracle client
version must correspond to the Oracle database installed on the database server.
22
Processor
Dual-core
RAM
3 GB or more
AT310_AM_E2
a.
120 GB or morea
Operating system
Microsoft Windows 2003 Server / Microsoft Windows 2008 Server / Unix / Linux
RDBMS
Oracle 10g or 11g / Microsoft SQL Server 2005 / Sybase Adaptive Server 12.5.0
RAM
1 GB per user
72 GB or more
Operating system
Citrix
The recommended bandwidth between Citrix servers and Citrix clients for satisfactory performance is 300 Kbps per user.
Must be accessible to all the user computers / Citrix servers on the network in order to provide licence tokens for Atoll
sessions.
Must have a steady and reliable network connection with user computers / Citrix servers.
Must have the HASP licence manager installed and running. For more information, see "Working with Floating
Licences" on page 39.
Must have the floating licence key plugged in.
Can be one of the Citrix servers.
Number of end-users: 40
In order to simulate the average activity of Atoll users, each user is assumed to carry out a "Routine Operation" 5 times during
a three-hour working period. The "Routine Operation" consists in modifying parameters for 40 cells in 30 minutes,
recalculating path loss matrices for these 40 cells, and calculating a best server coverage prediction.
23
Forsk 2011
Although a best server coverage prediction does not require a lot of computer resources for calculations, it requires Atoll to
load all the path loss matrices in memory. When the path loss matrices are stored on a file server, as recommended, this
operation creates a considerable data transfer activity over the network. The benchmark tests have been based on this
simulated data transfer activity.
Computer Network Architecture
A centralised network architecture is the most widely used network architecture by Atoll users. The figure below shows the
recommended architecture along with a per-user network bandwidth requirement between different network components.
24
Recommended Bandwidth
From
To
End-user
Citrix server
Citrix server
File server
AT310_AM_E2
You need administrator rights for installing Atoll and its components.
If you work with fixed licences, you must unplug the key before the installation and wait for the installation to finish
before inserting it 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 dialogue appears.
c. Choose Never notify.
d. Click OK.
1. Run the Atoll setup.
The setup program uses a wizard interface, with a step-wise description of the installation. You can,
25
Forsk 2011
26
AT310_AM_E2
If you work with fixed licences and you installed the Driver for Fixed Licence Keys, restart the computer. Restarting
the computer is necessary for the driver to work.
If you work with fixed licences, plug in the fixed licence key.
On the versions of Microsoft Windows that support UAC (disabled before the installation), run Atoll once using an
administrator account and with UAC disabled when the installation is complete.
If the following files do not already exist in the installation folder, empty ones are
created by the setup:
[Atoll installation folder]\Atoll.ini
[Atoll installation folder]\coordsystems\Favourites.cs
These files are not removed when Atoll is uninstalled.
If you have installed Atoll on a Citrix server, you must publish it to make it access to
users.
To restrict access to the Atoll installation folder, you can assign read/write access rights
to this folder to administrators and read-only rights to end-users.
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.
27
Forsk 2011
To disable UAC:
a. Go to Control Panel > User Accounts.
b. Select Change User Account Control settings. The User Account Control Settings dialogue appears.
c. Choose Never notify.
d. Click OK.
1. Run the Atoll C++ development kit setup.
The setup program uses a wizard interface, with a step-wise description of the installation. You can,
28
AT310_AM_E2
/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 2011
/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"
Best signal export add-in: "Addins\SignalsExport"
Driver for fixed licence keys: RainbowDongle
Distributed calculation server: Atoll_Server
Atoll Management Console: AMC
Example: To install Atoll, the distributed calculation server, and the driver for fixed licence keys:
/COMPONENTS="Atoll,Atoll_Server,RainbowDongle"
30
AT310_AM_E2
Add-ins installed by the Atoll setup are uninstalled when Atoll is uninstalled. To uninstall any other add-in by unregistering its
DLL:
1. Close Atoll.
2. Right-click the DLL file in Windows Explorer. The context menu appears.
3. Select Unregister. The DLL is unregistered.
You can also unregister the DLL from the command prompt using regsrv32.exe /u.
Lists of macros available in Atoll can be stored in user configuration files. Macros listed in the user configuration files are
added to Atoll when the user configuration files are loaded. For more information, refer to "Contents of User Configuration
Files" on page 142.
To remove a macro from Atoll:
1. In Atoll, select Tools > Add-ins and Macros. The Add-ins and Macros dialogue appears (see Figure 2.10 on page 30).
2. In the list of available macros, select the macro you wish to remove.
3. Click Delete.
Other commands available in the Add-ins and Macros dialogue are:
-log "logfilename"
Instructs Atoll to create a log file containing all the messages listed in the Events tab. This may 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 may 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 may 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.
-Provider providername
31
Forsk 2011
Instructs Atoll to use the mentioned providername to access the database server (Microsoft Access:
Microsoft.Jet.OLEDB.4.0, or Oracle: MSDAORA.1).
-DataSource server
Instructs Atoll to access the mentioned database server using the given provider.
-UserId username
Instructs Atoll to access the mentioned Oracle database server using the mentioned username.
-Password password
Instructs Atoll to access the mentioned Oracle database server using the mentioned password.
-Project projectaccount
Instructs Atoll to access the mentioned Oracle database server using the mentioned projectaccount.
The keywords Provider, Password, UserId, DataSource, and Project are case sensitive.
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 may require uninstall folders of older
patches to be available for their own installation.
Fixed licence keys cannot be used with "Server"-type operating systems. Therefore, you should not install the driver
for fixed licence keys on:
The current version of the driver for fixed licence keys (Sentinel SuperPro driver) installed with Atoll is the 7.6.1.
If Atoll is unable to access the fixed licence key, even after a clean installation, try reinstalling the Sentinel SuperPro
driver manually. The drivers setup program (SPI761.exe) is copied to the Sentinel subfolder in the Atoll installation
folder by the setup if you selected the Driver for Fixed Licence Keys component during the installation. You can also
download the driver from http://www.safenet-inc.com.
Restart the computer when asked by the setup. Restarting the computer is necessary for the driver for fixed licence
keys to work.
If you get a protection key error message, verify that the fixed licence key correctly plugged in and that the licence has
not expired.
In case the fixed or the floating licence key becomes unavailable, Atoll will ask the users currently accessing the key
to save their open documents before Atoll closes. If the key becomes available again, Atoll will let the users continue
working.
Do not change the computers date.
Citrix
If you have installed Atoll on a Citrix MetaFrame server, you must published it to make it available to the users.
32
You can get information about Atoll (version, build, type of licence and remaining time before expiration, etc.) by
selecting Help > About Atoll in the main menu in Atoll.
AT310_AM_E2
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:
Acknowledgement
Atoll uses Inno Setup for installation. For more information, see http://www.jrsoftware.org/isinfo.php.
Add-ins installed by the Atoll setup are uninstalled when Atoll is uninstalled.
33
34
Forsk 2011
AT310_AM_E2
35
Forsk 2011
36
AT310_AM_E2
4. Distributed calculation servers calculate the path loss matrices one by one.
Distributed calculation servers that have spare threads start the calculations using these threads. If no thread is
available, the request is placed in a queue to wait for a thread to become available.
5. For each calculated path loss matrix, a confirmation is sent to the Atoll session. Any error or warning messages
generated are passed back to the Atoll session and displayed in the Event Viewer.
If an error occurs on any of the distributed calculation servers, Atoll transfers the calculations back to the local
computer. However, to avoid memory saturation, Atoll uses one thread on the local computer and calculates the path
loss matrices one by one. It does not attempt creating more than one thread.
6. In order to reduce the amount of data flow in the network, distributed calculation servers send the results directly to
the storage location (which may also be on a file server, not necessarily on the users computer that requested the
calculations).
7. Atoll user may then request the path loss matrices from the file server if they are needed for coverage predictions.
37
38
Forsk 2011
AT310_AM_E2
4 Managing Licences
Atoll can be used on:
Computers with fixed licence keys plugged in to USB slots on the computers themselves, or
Computers connected to a licence server with a floating licence key plugged in to a USB port on the server.
The driver for fixed licence keys can be installed at the same time as Atoll. For more information, see "Installing Atoll and
Components" on page 25.
The software for managing floating licence keys must be installed on a server accessible to the computers on which Atoll is
going to be used. For more information, see "Working with Floating Licences" on page 39.
For information on the Atoll licence management utility, see "Using the Atoll Licence Manager" on page 41.
HASP floating licence key: Hardware key programmed with the numbers of tokens available for each module.
HASP licence manager: Interface between Atoll and the floating licence key.
HASP device driver: Interface between the HASP licence manager and floating licence key.
HASP monitor: Enables you to check the number of used and available tokens.
nhsrv.ini file: Installed on the floating licence server to enable computers to use tokens.
nethasp.ini file: Installed on the computers to facilitate access to the floating licence server.
nhsrv.ini and nethasp.ini files are used if they exist. Default settings are used otherwise.
You can download the HASP licence manager, the HASP device driver, and the HASP
monitor from http://www3.safenet-inc.com/support/hasp/hasp4/enduser.aspx.
Newer versions may be available for download at the website than those provided on
the Atoll installation disk.
When downloading setup files from the Aladdin website, remember to download
setup files for HASP4, not HASP HL.
The correct (recommended) version of the device driver setup to download is the one
that works with "HASP4 API v8.x or Envelope 12.x".
HASP hardware key is supported by Windows 2000 Server and Windows 2003 Server
with HASP Licence Manager 8.20 or above.
39
Forsk 2011
Do not plug the floating licence key in the server before installing the device drivers.
Wait for the HASP licence manager setup to indicate when to plug in the key.
If the floating licence server is protected by a firewall, port 475 must be open when
using the UDP or TCP protocols.
Once the HASP licence manager has been installed, the floating licence key must
always remain plugged in.
In case the fixed or the floating licence key becomes unavailable, Atoll will ask the
users currently accessing the key to save their open documents before Atoll closes. If
the key becomes available again, Atoll will let the users continue working.
The floating licence key may become unavailable and a key protection error message
appears in Atoll if the licence management server is heavily loaded. Check if there is
any application running on the server that might be causing the problem. If this is the
case, remove any such application from memory. If this is not possible, try changing
the latency associated to the HASP licence manager in accessing the key.
Once the device driver is successfully installed, plug in the floating licence key.
You may also copy (from the installation CD) or create the nhsrv.ini file on the floating licence server (in the HASP
licence manager installation folder). The HASP licence manager settings in this file can be modified according to the
your requirements. For more information on the contents of the nhsrv.ini file, see "nhsrv.ini File" on page 40.
To restrict access to the HASP licence manager installation folder, you can assign read/
write access rights to this folder to administrators and read-only rights to end-users.
40
AT310_AM_E2
File Contents
The following is a sample of the nhsrv.ini file that shows how to set a list of computers allowed access to the floating licence
server. Complete syntax may be found on the HASP installation CD or on the Aladdin website.
[NHS_SERVER]
;NHS_IP_LIMIT = <IpAddr0>[,<IpAddr1>,<IpAddr2>,...]
;Specifies the IP addresses of computers served by the licence manager
;Example: 10.1.1.1, 10.1.1.*
;For use, remove the semi-colon before NHS_IP_LIMIT
A nethasp.ini file located in the Atoll installation folder has priority over any nethasp.ini file located in the Windows folder,
which in turn has priority over any nethasp.ini file located in a folder listed in the system path variable.
Storing the nethasp.ini file in the Windows folder instead of the Atoll installation folder may be useful if you have more than
one version of Atoll installed, and you wish to access the same floating licence server. This avoids making a copy of the file in
each Atoll installation folder.
File Contents
The following is a sample of the nethasp.ini file with the minimum required information. Complete syntax may be found on
the HASP installation CD or on the Aladdin website.
[NH_COMMON]
NH_IPX = Disabled
NH_NETBIOS = Disabled
NH_TCPIP = Enabled
[NH_TCPIP]
NH_SERVER_ADDR = 3CT000J
NH_TCPIP_METHOD = UDP
NH_USE_BROADCAST = Disabled
a.
b.
Remove the NH_SESSION and NH_SEND_RCV entries from the nethasp.ini file if these
exist.
These fields define the timeout delays depending to the network. They may be useful
in slow networks and should be set only if required.
41
Forsk 2011
Under Selected key the following information is available for the selected key:
Number: Unique key number given by the key provider. This number must be communicated to Forsk, when
requested, for reprogramming the licence key.
Type: The type of key, Fixed licence or Floating licence.
Reference: Unique floating licence key reference provided by Forsk. This number must be communicated to Forsk,
when requested, for reprogramming the licence key. This reference is also printed on the sticker on the key.
Location (server): Name of the floating licence management server on which the floating licence key is plugged.
Under Modules and licences, all the Atoll modules available on the selected key are listed along with the numbers
of licence tokens of each.
Under Number of licences, the Modify buttons are reserved for Forsk use only.
Under Dates and durations, the following dates and durations are available:
42
Licence start
Licence end
Duration of validity
Time bomb
AT310_AM_E2
A purchased Atoll licence corresponds to a particular Atollversion. There is no time limit on using this version.
However, yearly maintenance must be purchased in order to access newer versions with updates and bug fixes.
When you purchase maintenance, Forsk reprograms your licence keys to allow access to new versions.
The Time bomb date is the end date for maintenance. When the time bomb date passes, the licence key stops
working. You may then choose to either purchase maintenance for the next year, and benefit from the new
features and bug fixes, or have the licence key reprogrammed without maintenance for the next year, in which
case users can continue working with the existing version.
Atoll can inform you about the approaching time bomb date 30 days in advance. This alert can be configured
through the Atoll.ini file.
Do not attempt to modify the Time bomb settings on the fixed licence key. Contact
Forsks customer support.
Do not change the computers date.
Under Profile signature, the PID (profile signature or ID) is the encrypted description of the user rights available
on the key. Each key has a unique PID.
Under Current profile summary, all of the above information is summarised.
43
44
Forsk 2011
AT310_AM_E2
5 Managing Databases
In Atoll, you can work with standalone documents, i.e., documents without any back-end database, or with documents
connected to databases. Standalone documents are more portable, however a back-end database is required when working
in a multi-user environment. In multi-user environments, several users work on the same project and a central data storage
is necessary for keeping the data modifications made by a team radio planning and optimisation engineers.
Atoll enables you create databases, upgrade them to newer versions, archive and refresh data with databases, manage and
resolve data conflicts, and create and work with multi-level databases.
A database server can store one or more database. For example, a GSM, a UMTS, and a microwave links database can be
stored on the same database server using the same RDBMS (Oracle, for example).
In this chapter, the following are explained:
The relationships in the database schema figures are represented by arrows. These
unidirectional arrows should be read as:
= n or
1
In the tables, primary keys are listed in bold and italic characters.
In the database schema figures, primary keys are in bold and underlined characters,
and required fields are in bold characters.
If you export the content of an ATL document which is already connected to a
database, to a another RDBMS (for example, if you export a document connected to
an Oracle database to Sybase or Microsoft Access), some field types will be converted
according to the above table but this conversion does not have an impact on the
document in Atoll.
The following table lists the types of fields used in Atoll database templates, their sizes, and the equivalent field types and
sizes in different RDBMS:
45
Forsk 2011
Field Type
Length
Field Type
Length
Field Type
Length
Field Type
Length
Microsoft
Access
Equivalent
Float
FLOAT
32
real
real
Single
Double
FLOAT
64
float
float
Double
Atoll
Oracle Equivalent
Sybase Equivalent
Integer
NUMBER
11
int
int
Long Integer
Short
NUMBER
tinyint
tinyint
Integer
Boolean
NUMBER
bit
bit
Yes/No
Text
Variable*
VARCHAR2
Variable*
varchar
Variable*
varchar
Variable*
Text*
Memo
Variable
VARCHAR2
2000
varchar
4000
text
Binary
Variable
LONG RAW
image
16
image
16
OLE Object
Memo
* Lengths for these fields are specified in parentheses in the database structure tables.
If you export the contents of an Atoll document, already connected to a database, to
another RDBMS (for example, if you export a document connected to an Oracle database
to SQL Server), some field types will be converted according to the above table. This
conversion does not have any impact on the document in Atoll.
For more information on the Atoll Management Console and upgrading databases, see "Atoll Management Console" on
page 46 and "Upgrading Existing Databases" on page 50, respectively.
Oracle
Microsoft SQL Server
The Atoll Management Console can be installed with Atoll. For more information, see "Installing Atoll and Components" on
page 25. You can run the Atoll Management Console from the Windows Start menu program group or by double-clicking
Atollmgmt.msc in the Atoll installation folder. The Atoll Management Console runs using the Microsoft Management Console
environment.
When the Atoll Management Console is run for the first time, you must register your database server in order to have the
databases installed on the server to be available in the Atoll Management Console.
To register a database server:
1. In the Atoll Management Console window, in the left pane, right-click the Database item under the Administration
Atoll. The context menu appears.
2. Select Register a New Server. The Data Link Properties dialogue appears.
3. Click the Provider tab. On the Provider tab, select the provider for your database server depending on whether it is
Oracle or SQL Server.
46
AT310_AM_E2
) or
The right pane lists the databases available on the connected database server currently selected in the left pane. The current
user may be the owner of one of the listed databases. The user name of the owner of a database appears in parentheses in
the title bar. One Oracle user can create and own one database. For each new database, you must create a new user owner
of the database.
The following details are available for databases created or upgraded using the Atoll Management Console:
) or a previous version (
A master database may have one or more project databases created from and connected to it. For more information
on master and project databases, see "Working With Multi-level Databases" on page 52.
General tab: The General tab displays the Name, Description, Owner, Type, and Version of the database.
Statistics tab: The Statistics tab displays the number of records in each table of the database.
47
Forsk 2011
48
AT310_AM_E2
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 may take a long time because the Atoll
Management Console must search for the data required for the upgrade in the whole database.
For more information on upgrading databases, see "Upgrading Existing Databases" on page 50.
All the tables in a database created using the Atoll Management Console (except the COORDSYS and UNITS tables) contain a
non-modifiable, integer DB_RECORD_ID field. This field is used to store the ID of every record in the table. It is not added to
Microsoft Access databases.
49
Forsk 2011
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.
You can use the ODBC interface (used by Sybase as well) to access all databases that
accept UDL files and the ODBC interface.
In order to be able to archive to and refresh data from a Sybase 12.5.0 database using the
ODBC driver:
1. Open the Windows registry using regedit.exe.
2. Add a "string" called "WorkArounds2" in:
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Sybase
Where "Sybase" represents the logical name used for the ODBC connection.
3. Assign the value "152" to "WorkArounds2", i.e., WorkArounds2 = 152.
The Microwave Radio Links template now supports Radio Series. Similar microwave
radios belong to the same radio series. In order to organise the microwave radios
(microwave equipment) in radio series before the database upgrade:
1. In Atoll 2.8.x, add a custom field named FAMILY of type Text (50) to the
MWEquipments table.
2. Enter the radio series names in this field for each radio, i.e., group the radios of
the same series under the same radio series name in the FAMILY field.
Without this manual organisation of the microwave radios into radio series, the database
upgrade will create one radio series for each microwave radio.
To upgrade a database using the Atoll Management Console:
1. In the Atoll Management Console window, in the right pane, right-click the database that you want to upgrade. The
context menu appears.
2. Select Upgrade Database. The Database Update Wizard dialogue appears.
The Database Upgrade Wizard displays the current database version and the version to which the database will be
upgraded.
50
AT310_AM_E2
It is possible to upgrade an existing database manually (not recommended) by adding and deleting tables and fields as
required by the new version. However, due to the complex nature of the upgrade process, it is highly recommended to use
the Atoll Management Console for upgrading existing databases. For information on manually upgrading a database, see
"Upgrading Databases Manually" on page 52.
51
Forsk 2011
52
AT310_AM_E2
For example, you may have a country-wide master database and more than one regional project databases. End-users can
here work with their local regions project database, and would not have to unnecessarily load country-wide data.
The probability of human error increases with the number of users who can modify data.
The probability of conflicts increases with the number of users accessing the database.
The performance is reduced because the entire network is loaded every time a user accesses the database.
For routine city-wide planning, an end-user does not require the entire countrys database to be loaded.
Project databases may be created using filters on sites, thus allowing users to work with regional databases. A possible
scenario is depicted in the figure below:
53
Forsk 2011
54
AT310_AM_E2
Select this option if you wish to create a project database that contains all the data of the master database.
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.
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
55
Forsk 2011
You can view the details stored in the ATOLL_ADMIN_PRJ table in the project database properties. To view the above details
of a project database:
1. In the right pane, right-click the project database in the list. The context menu appears.
2. Select Properties. The database Properties dialogue appears.
3. The Properties dialogue contains three tabs:
General tab: The General tab displays the Name, Description, Owner, Type, and Version of the database.
Project Database tab: Under Source master database, the Project Database tab displays the Connection settings
to and the Owner of the master database. Under Site selection, this tab displays the site filtering Method and
Settings used for creating the project database.
Statistics tab: The Statistics tab displays the number of records in each table of the project database.
The project database contains a copy of all the original tables of the master database. The names of the original tables are
prefixed with "O_". For example, the ANTENNAS table of the master database is stored in the project database under the
name O_ANTENNAS. The COORDSYS and UNITS are not copied to the project database because their contents cannot be
different from those of the master database.
All the tables in a project database contain a non-modifiable, integer O_RECORD_ID field and a Boolean O_CHANGED field.
The O_RECORD_ID field is used to locate records in the master database. Modified records are archived in master database
using the O_RECORD_ID of the project database and DB_RECORD_ID of the master database. The O_CHANGED field is set to
TRUE for records modified in the project database.
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 wish 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 wish 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 may 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.
56
AT310_AM_E2
Under Errors, Atoll Management Console displays errors that occurred during archive.
4. Once archive is complete, click Close.
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) may 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 may be granted for columns of the tables. For
example, custom fields may 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).
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" on page 67.
Tracked Tables
UMTS HSPA
LTE
57
Forsk 2011
Technology
Tracked Tables
WiMAX 802.16e
You can, however, enable or disable history management for table as required (see "Enabling/Disabling Data Modifications
History Management" on page 59 for more information). If you wish, you can also purge old data modifications history (see
"Purging Old Data Modifications History" on page 60 for more information).
The history management tool is available for Oracle databases.
The following section describes how to set up the history management tool for an Oracle database using the Atoll
Management Console.
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.
To set up data modifications history management for a database:
1. In the Atoll Management Console window, in the right pane, right-click the database for which you wish to set up data
modifications history management. The context menu appears.
2. Select Manage Data Modifications History. The Data Modifications History Management dialogue appears.
3. Click Yes when asked whether you wish to make your database compatible with the data modifications history tool.
The Atoll Management Console updates the database structure to make it compatible with the data modifications
history tool. Data modifications history is enabled for the database.
Once finished, it opens the Data Modifications History Management dialogue (Figure 5.9 on page 59). This dialogue
lists all the tables for which the data modifications history management has been enabled, the total numbers of
records in these tables, and the status of the history management.
All the modifications made in the tables listed in "Managing Data Modifications History" on page 57 are stored in the history
tables added to the database.
If you wish, you can disable the data modifications history management for any table. For more information, see "Enabling/
Disabling Data Modifications History Management" on page 59.
58
AT310_AM_E2
59
Forsk 2011
60
AT310_AM_E2
g. To create a new user, right-click the User folder in the Security folder and select Create.
h. Create a new user (project account) with administrator rights and privileges.
i.
Specify "Atoll" as the default tablespace and choose DBA for its privileges.
This account will be used to create Atoll document tables and will be the owner of these tables.
It is usually helpful to assign a name to the project account that indicates the type of
project that you want to store (GSM, UMTS, etc.).
6. Create database tables in the empty database "AtollDB" using the project account created in step 5.. For more
information, see "Creating a New Database Using Atoll" on page 49.
7. Create user accounts.
To create a project account:
a. Run DBA Studio on the database server (or a client computer with Oracle administration tools).
b. Open the Add Database to Tree dialogue.
c. In the Add Database To Tree dialogue, select Add selected databases from your local tnsnames.ora file.
d. Select the "AtollDB" service.
e. Open the connection dialogue for the "AtollDB" service.
f.
g. To create a new user, right-click the User folder in the Security folder and select Create.
h. Create new user accounts with appropriate rights and privileges. These user accounts do not own tables, but only
specify the access rights to the tables owned by the project account.
i.
Specify "Atoll" as the default tablespace for the new user accounts.
The database will be accessible through any of the user accounts from any client computer.
In some cases, Atoll displays too many decimal values for fields of type "Float" in
documents connected to Oracle databases. This type of display is not due to any error in
Atoll. You can fix this problem by:
In Atoll, setting the display precision of floating point values the Atoll.ini option
described in "Setting the Display Precision of Floating Point Values" on page 175.
In Oracle,
If the database is new and the fields are empty, changing the field type from Float
to Number and fix the number of decimal values for it in Oracle.
If the database fields contain data, updating the field data by rounding the values
stored in them:
UPDATE TABLE_NAME SET FIELD_NAME = ROUND(FIELD_NAME,2);
Once this is done, you have to refresh document data from the database in order to fix
the display problem in Atoll.
61
Forsk 2011
5.9 Appendices
The first appendix shows how to use SQL for Oracle database customisation and the second appendix shows how to set up
databases for co-planning taking the example of GSM and UMTS MS Access databases.
62
AT310_AM_E2
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, SQL Server, or Sybase:
1. Make backups of the GSM and UMTS documents.
2. Open the GSM document in Atoll.
3. Delete all the transmitters from the Transmitters table and all the sites from the Sites table.
63
Forsk 2011
4. Export the GSM document to the database by entering the user name and password for GSMUser.
5. Log in as GSMUser to the database.
6. Delete the Sites table.
7. Open the UMTS document in Atoll.
8. Export the UMTS document to the database by entering the user name and password for UMTSUser.
9. Log in as UMTSUser to the database.
10. Right-click the Sites table and select Create a View from the context menu. The Create View dialogue appears.
a. Enter Sites as the view name.
b. Enter GSMUser as the name of the schema which will contain the view.
c. Select Table as object type.
d. Enter UMTSUser as the name of the schema you want to use.
e. Select Sites as the object used to model the view.
11. Click Create. The view of the Sites table from UMTSUser is created in GSMUser. The GSMUser Sites table is now the
same as UMTSUser Sites table.
12. Set up user privileges for the Sites view in GSMUser to allow each user to Import, Update, Delete, and Select.
To set up a shared Sites table for a GSM-UMTS co-planning project in Microsoft Access:
1. Make backups of the GSM and UMTS documents.
2. Open the GSM document in Atoll.
3. Delete all the transmitters from the Transmitters table and all the sites from the Sites table.
4. Export the GSM document to a Microsoft Access database (GSM.mdb).
5. Open GSM.mdb in Microsoft Access.
6. Delete the Sites table.
7. Open the UMTS document in Atoll
8. Export the UMTS document to a Microsoft Access database (UMTS.mdb).
9. Open GSM.mdb in Microsoft Access.
10. In Microsoft Access 2003 and earlier, select File > Get External Data > Link Tables. In Microsoft Access 2007 and later,
select External Data > Access Database.
11. In Microsoft Access 2003 and earlier, the Link dialogue appears. Select UMTS.mdb. In Microsoft Access 2007 and later,
the Get External Data - Access Database dialogue appears, specify UMTS.mdb as data source and select Link to data
source by creating a linked table.
12. Click OK. The Link Tables dialogue appears.
13. Select the Sites table.
14. Click OK. Microsoft Access creates a Sites table in GSM.mdb which is linked to the Sites table in UMTS.mdb. The tables
contain the same data.
Once the linked Sites table has been created in the GSM database, you have to define the relations of this table with the other
tables in the database. Figure 13.1 on page 231 shows the relations of the Sites table with other tables in a GSM database.
The UMTS Sites table has more fields compared to the GSM Sites table. Therefore, we
propose to replace the GSM Sites table with the UMTS one.
64
AT310_AM_E2
6 Multi-user Environments
A multi-user environment is where more than one user work simultaneously on an Atoll project, sharing data over a network.
In large, structured multi-user environments, groups of users may work on specific parts of a common, large-scale project. For
example, different user groups may work on different regions of a country-wide network. In this chapter, the following are
explained:
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 71.
65
Forsk 2011
66
AT310_AM_E2
If users modify geographic data locally, for example edit clutter or traffic in their
respective projects, they should store these modified geographic data locally so that the
modifications do not impact other users.
Type
Description
ATOLL_USER
Text (50)
67
Forsk 2011
Field
Type
Description
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 68.
If interface access rights are not defined for a database, i.e., the GUIUserRights table does not exist, all the users have
unrestricted access to the Atoll interface.
If interface access rights are defined for a database, and a user creates a document from the database or opens a document
connected to the database, Atoll retrieves the interface access rights for the user when he enters his user name and password
to access the database.
If the database is not reachable, the user is not listed in the GUIUserRights table, or if the password is not correct, the users
interface access rights are set to read-only by default (for more information, see "Defining Database and Interface Access
Rights" on page 68). If the user is listed in the GUIUserRights table, his interface access rights are read and applied to the Atoll
interface (table grids and properties dialogues). A message is displayed in the Event Viewer window to inform the user of his
interface access rights. It is possible to remove interface access restrictions by disconnecting the document from the database.
However, a disconnected document cannot be reconnected to the database.
The GUIUserRights table is also stored in the Atoll document, and is updated when the document is saved. Hence, users can
work on their documents without actually being connected to the database, and still have their usual interface access rights
applied in the document.
Atoll does not ask for the user name and password when a document is opened using the
API. The interface access rights stored in the document are used.
When database connection properties are modified for a document, for example, when a different user enters his user name
and password in the connection properties, Atoll reads and applies the interface access rights defined for the new user.
68
AT310_AM_E2
Users who have database access rights in the selected database are marked with the green icon ( ). Users who do
not have any database access rights in the selected database (Category = No Access) are marked with the red icon
( ). Locked (deactivated) user accounts are marked with a yellow lock icon ( ). For more information on locked
user accounts, see "Creating and Editing User Accounts" on page 69.
You can use the Filter list to display:
), without access (
), or locked (
5. Under Database rights, you can select a database access Rights category:
No access: User without read and write access to the database. The database is not visible to these users and they
are not allowed to create Atoll documents based on this database.
Read-only: Users allowed to create Atoll documents from the database but without write permissions to any table
of the database, i.e., users cannot archive changes made in the Atoll document to the database.
Standard: Users with read and write access to some tables of the database. These tables include radio network
data tables including sites, transmitters, cells, subcells, repeaters, remote antennas, secondary antennas, intraand inter-technology neighbours and exceptional pairs, site and transmitter lists, microwave point-to-point, pointto-multipoint, and multi-hop links, microwave repeaters, microwave hubs.
Administrator: Users with read and write access to all the tables of the database.
Database access rights are stored in the user account properties in Oracle. If you are working with an RDBMS other
than Oracle, you will not be able to set database access rights. You can, however, still set interface access rights as
explained below.
6. Under Interface rights, you can select interface access rights for:
Database access rights and access rights to radio data in Atoll can be set
independently. For example, a user may have full access rights in the interface but not
allowed to archive changes to the database.
However, access rights in the interface should only be granted if the user has at least
read-only access to the database.
Access to predictions:
All: (CALCPARAMS = ALL) Users with read and write access to all coverage predictions and their properties.
Standard: (CALCPARAMS = STD) Users with access to customised coverage predictions only, and allowed to
modify coverage conditions and display settings.
Customised only: (CALCPARAMS = NONE) Users with access to customised coverage predictions only, but not
allowed to modify coverage conditions and display settings.
Password confirmation:
Yes: (PASSWORD = STD) Atoll will ask users for password when opening a document connected to this
database or creating a new document from this database.
No: (PASSWORD = NONE) Atoll will not ask users for password when opening a document connected to this
database or creating a new document from this database.
7. Click OK. The database and interface access rights of the selected user are saved in the database.
69
Forsk 2011
6.4 Appendices
The following appendices provide additional information on:
70
AT310_AM_E2
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,
and WiMAX. 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.
71
Forsk 2011
administrator, advanced user, read-only user, etc., and give examples of how to set up regions in the network and how
to assign user rights to each region.
Available in a format compatible with Atoll. File formats are described in "Path Loss Matrix File Format" on page 117.
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.
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.
72
AT310_AM_E2
Let us assume that the shared path loss matrices folder where Atoll stores the generated path loss matrices files is
C:\Path_Loss_Internal, and the folder where the other tool stores its path loss matrices is C:\Path_Loss_External.
The Pathloss.dbf file in the Path_Loss_Internal folder will store the path to the LOS files for each transmitter in the network.
This folder can be set as the shared path loss matrices folder in the ATL files of group A users.
To set up the shared path loss matrices folder for group B users, you must create a new folder with a Pathloss.dbf file in it.
This folder can be called C:\Path_Loss_Mixed. The Pathloss.dbf file in this folder can be a copy of the Pathloss.dbf file in the
Path_Loss_Internal folder with the paths to the LOS files modified. For example, if the path loss matrices generated by the
other tool include Transmitter_1, the Pathloss.dbf file in the Path_Loss_Mixed folder will have all the same entries as
Pathloss.dbf file in the Path_Loss_Internal folder except for the path for the Transmitter_1 path loss matrices file. Figure 6.4
on page 73 explains this concept.
Figure 6.4: Path Loss Architecture for Multiple Source Path Loss Matrices
Once the Pathloss.dbf file in the Path_Loss_Mixed folder is updated with the correct paths corresponding to the different
transmitters, the Path_Loss_Mixed folder can be set as the shared path loss matrices folder in the ATL files of group B users.
If a group B user changes some parameters which make some path loss matrices invalid, Atoll will recalculate the private path
loss matrices with the propagation models assigned to the transmitters. The external path loss matrix will no longer be used.
73
74
Forsk 2011
Part 2
Reference
This part of the administrator manual provides recommendations and
information on Atoll configuration and initialisation files.
AT310_AM_E2
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)
77
Forsk 2011
Ellipsoid
The ellipsoid is the pattern used to model the earth. It is defined by its geometric parameters.
Projection
The projection is the transformation applied to project the ellipsoid of the earth on to a plane. There are different projection
methods that use specific sets of parameters.
Projection Coordinate System
The projection coordinate system is the result of the application of a projection to a geographic coordinate system. It
associates a geographic coordinate system and a projection. Atoll enables you to choose the projection coordinate system
matching your geographic data.
If you are working in a multi-user environment, Atoll uses four coordinate systems:
78
AT310_AM_E2
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 82). Parameter with index 0 is the first one. Projection parameters are
delimited by commas.
For UTM projections, you must provide positive UTM zone numbers for north UTM zones and negative numbers for
south UTM zones.
You can add all other information as comments (such as usage or region).
Codes of units, data, projection methods, and ellipsoids, and projection parameter indices are listed in the tables below.
79
Forsk 2011
Unit Codes
Code
Cartographic Units
Code
Geographic Units
Metre
100
Radian
Kilometre
101
Degree
Foot
102
Grad
Link
103
ArcMinute
Chain
104
ArcSecond
Yard
Nautical mile
Mile
-1
Unspecified
-1
Unspecified
Code
Datum
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
201
Adindan
266
M'poraloko
202
267
203
268
NAD Michigan
204
269
205
Afgooye
270
Nahrwan 1967
206
Agadez
271
Naparima 1972
207
Lisbon
272
208
Aratu
273
NGO 1948
209
Arc 1950
274
Datum 73
210
Arc 1960
275
211
Batavia
276
NSWC 9Z-2
Datum Codes
80
212
Barbados
277
OSGB 1936
213
Beduaram
278
214
Beijing 1954
279
OS (SN) 1980
215
280
Padang 1884
216
Bermuda 1957
281
Palestine 1923
217
Bern 1898
282
Pointe Noire
218
Bogota
283
219
Bukit Rimpah
284
Pulkovo 1942
221
Campo Inchauspe
285
Qatar
222
Cape
286
Qatar 1948
223
Carthage
287
Qornoq
224
Chua
288
Loma Quintana
225
Corrego Alegre
289
Amersfoort
226
Cote d'Ivoire
290
RT38
227
Deir ez Zor
291
228
Douala
292
229
Egypt 1907
293
Schwarzeck
230
294
Segora
AT310_AM_E2
Code
Datum
Code
Datum
231
232
295
Serindung
Fahud
296
Sudan
233
Gandajika 1970
297
Tananarive 1925
234
Garoua
298
Timbalai 1948
235
Guyane Francaise
299
TM65
236
Hu Tzu Shan
300
TM75
237
301
Tokyo
238
302
Trinidad 1903
239
Indian 1954
303
240
Indian 1975
304
Voirol 1875
241
Jamaica 1875
305
242
Jamaica 1969
306
Bern 1938
243
Kalianpur
307
244
Kandawala
308
Stockholm 1938
245
Kertau
309
Yacare
247
La Canoa
310
Yoff
248
311
Zanderij
249
Lake
312
Militar-Geographische Institut
250
Leigon
313
251
Liberia 1964
314
Deutsche Hauptdreiecksnetz
252
Lome
315
Conakry 1905
253
Luzon 1911
322
WGS 72
254
326
WGS 84
255
Herat North
901
256
Mahe 1971
902
Nord de Guerre
903
Projection Method
Code
Projection Method
Undefined
Oblique Stereographic
10
11
257
Makassar
258
Mercator
12
Cassini-Soldner
13
Oblique Mercator
Transverse Mercator
14
UTM Projection
Ellipsoid Codes
Code
Name
Major Axis
Minor Axis
Airy 1830
6377563.396
6356256.90890985
6377340.189
6356034.44761111
6378160
6356774.71919531
Bessel 1841
6377397.155
6356078.96261866
Bessel Modified
6377492.018
6356173.50851316
Bessel Namibia
6377483.865
6356165.38276679
81
Forsk 2011
Code
Name
Major Axis
Minor Axis
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
82
AT310_AM_E2
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.
Metre is used as the internal measurement unit for the distance in all Atoll documents whether they are connected to
databases or not. The internal measurement unit is not stored in the database and cannot be changed.
83
Forsk 2011
If you are working in a multi-user environment, Atoll uses two type 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.
84
AT310_AM_E2
8 Geographic Data
Atoll supports several geographic data types; DTM (Digital Terrain Model), clutter, scanned images, vector data, traffic maps,
population, and custom geographic data. Atoll offers import/export filters for the most commonly used geographic data
formats. The different filters are:
File Format
Import and
Export in
Atoll
Geographic Data
Georeferencing
BIL
Both
Yes
(via HDRfiles)
TIFF
Both
Yes
(via TFW files)
Planet
Both
Yes
(via index files)
BMP
Both
Yes
(via BPW or BMW files)
DXF
Import
Yes
SHP
Both
Yes
MapInfo
(MIF, TAB)
Both
Yes
Erdas Imagine
(IMG)
Import
Yes
ArcView Grid
(TXT)
Export
Yes
(embedded in the data file)
Both
Yes
(embedded in the data file)
Vertical Mapper
(GRD, GRC)
Both
Yes
(embedded in the data file)
ECW
Import
Images
Yes
(via ERS files)
WLD files may be used for georeferencing for any type of binary raster file.
The smallest supported resolution for raster files is 1 m. There is no restriction on the
resolution of images.
DTM, clutter classes, and clutter height maps must have an integer resolution.
All the raster maps you want to import in an ATL document must be represented in
the same projection system.
85
Forsk 2011
Four points (hence, four altitude values) are necessary to describe a bin; these points are bin vertices. Therefore, a DTM file
that contains N x N bins requires N2 points (altitude values).
Altitudes may differ within a bin. The method used to calculate altitudes in Atoll is
described in the Technical Reference Guide.
To display a DTM map, Atoll takes the altitude of the southwest point of each bin to
assign a colour.
In Atoll, DEM (Digital Elevation Model) is the same as Digital Terrain Model (DTM). In
litterature, DEM and DTM may not have the same meaning. By definition, DEM refers
to the altitude above sea level including ground and clutter, while DTM refers to the
ground altitude above sea level alone.
86
AT310_AM_E2
BIL (8-bits)
TIFF (8-bits)
BMP (8-bit)
Erdas Imagine (8-bits)
Vertical Mapper (GRD, GRC)
Planet (16-bits)
The clutter code is the same inside a bin.
Atoll considers the clutter height of the nearest point in calculations. The method
used to determine clutter heights in Atoll is described in the Technical Reference
Guide.
To display a clutter height map, Atoll takes the altitude of the southwest point of each
bin to assign a colour.
MIF/TAB
SHP
DXF
Planet
AGD
User profile traffic maps based on user profile environments (raster traffic maps) support the following formats:
BIL (8-bits)
TIFF (8-bits)
BMP (8-bits)
Erdas Imagine (8-bits)
Vertical Mapper (GRD, GRC)
Planet (16-bits)
User density traffic maps (raster traffic maps) support the following formats:
87
Forsk 2011
MIF/TAB
SHP
DXF
Planet
AGD
8.6 Images
Images include air and satellite images. Images can be imported in Atoll for display and to provide information about the
geographic environment.
Image file formats supported by Atoll are:
MIF/TAB
SHP
Vertical Mapper (GRD, GRC)
AGD
88
AT310_AM_E2
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.
nrows
ncols
nbands
Number of spectral bands in the image, (1 for DTM and 8 bit pictures).
nbits
Number of bits per pixel per band; 8 or 16 for DTMs or Clutter heights
(altitude in metres), 8 for clutter classes file (clutter code), 16 for
path loss matrices (path loss in dB, field value in dBm, dBV and DBV/m).
byteorder Byte order in which image pixel values are stored. Accepted values are M
(Motorola byte order) or I (Intel byte order).
layout
Must be bil.
skipbytes Byte to be skipped in the image file in order to reach the beginning of
the image data. Default value is 0.
ulxmap
ulymap
xdim
ydim
Undefined
8, 16, 24 or 32 bits
SIGNEDINT
Integer
16 or 32 bits
FLOAT
Real
32 or 64 bits
89
Forsk 2011
Un
Undefined
In
Integer
Rn
Real
RGB24
Integer
valuescale
DTM Sample
Here, the data is 20 m.
nrows
1500
ncols
1500
nbands
nbits
8 or 16
byteorder M
layout
bil
skipbytes 0
ulxmap
975000
ulymap
1891000
xdim
20.00
ydim
20.00
1500
ncols
1500
nbands
nbits
byteorder M
layout
bil
skipbytes 0
ulxmap
975000
ulymap
1891000
xdim
20.00
ydim
20.00
90
AT310_AM_E2
a.
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.
BITMAPFILEHEADER (bmfh) contains some information about the bitmap file (about the file, not about the bitmap
itself).
BITMAPINFOHEADER (bmih) contains information about the bitmap (such as size, colours, etc.).
RGBQUAD contains a colour table.
BYTE contains the image data (whose format is specified by the bmih structure).
The following tables give exact information about the data structures. The Start-value is the position of the byte in the file at
which the explained data element of the structure starts, the Size-value contains the number of bytes used by this data
element, the Name column contains both generic name and the name assigned to this data element by the Microsoft API
documentation, and the Description column gives a short explanation of the purpose of this data element.
91
Forsk 2011
Start
Size
Name
Description
Generic
MS API
Signature
bfType
FileSize
bfSize
Reserved1
bfReserved1
Reserved2
bfReserved2
11
DataOffset
bfOffBits
Specifies the offset from the beginning of the file to the bitmap
raster data.
Start
Size
15
Name
Description
Generic
MS API
Size
biSize
19
Width
biWidth
23
Height
biHeight
biPlanes
biBitCount
27
29
Planes
BitCount
31
Compression
biCompression
35
ImageSize
biSizeImage
39
XpixelsPerM
biXPelsPerMeter
43
YpixelsPerM
biYPelsPerMeter
47
ColoursUsed
biClrUsed
51
ColoursImportant
biClrImportant
Specifies the number of colour that are 'important' for the bitmap. If
set to zero, all colours are considered important.
Start
Size
Name
Description
Generic
MS API
Blue
rgbBlue
Green
rgbGreen
Red
rgbRed
Reserved
rgbReserved
In a colour table (RGBQUAD), the specification for a colour starts with the blue byte,
while in a palette a colour always starts with the red byte.
Pixel data:
The interpretation of the pixel data depends on the BITMAPINFOHEADER structure. It is important to know that the
rows of a BMP are stored upside down meaning that the uppermost row which appears on the screen is actually the
92
AT310_AM_E2
lowermost row stored in the bitmap. Another important thing is that the number of bytes in one row must always be
adjusted by appending zero bytes to fit into the border of a multiple of four (16-bit or 32-bit rows).
Encoding type
BitCount Compression
1-bit
B&W images
Remarks
Every byte holds 8 pixels, its highest order bit representing the leftmost
pixel of these 8. There are 2 colour table entries. Some readers assume that
0 is black and 1 is white. If you are storing black and white pictures you
should stick to this, with any other 2 colours this is not an issue. Remember
padding with zeros up to a 32-bit boundary.
4-bit
16 colour images
Every byte holds 2 pixels, its high order 4 bits representing the left of those.
There are 16 colour table entries. These colours do not have to be the 16
MS-Windows standard colours. Padding each line with zeros up to a 32-bit
boundary will result in up to 28 zeros = 7 'wasted pixels'.
8-bit
256 colour
images
Every byte holds 1 pixel. There are 256 colour table entries. Padding each
line with zeros up to a 32-bit boundary will result in up to 3 bytes of zeros =
3 'wasted pixels'.
16-bit
High colour
images
16
Every 2 bytes hold 1 pixel. There are no colour table entries. Padding each
line with zeros up to a 16-bit boundary will result in up to 2 zero bytes.
24-bit
True colour
images
24
Every 4 bytes hold 1 pixel. The first holds its red, the second its green, and
the third its blue intensity. The fourth byte is reserved and should be zero.
There are no colour table entries. No zero padding necessary.
Pixel data is stored in 2-byte chunks. The first byte specifies the number of
consecutive pixels with the same pair of colour. The second byte defines
two colour indices. The resulting pixel pattern will have interleaved highorder 4-bits and low order 4 bits (ABABA...). If the first byte is zero, the
second defines an escape code. The End-of-Bitmap is zero padded to end on
a 32-bit boundary. Due to the 16bit-ness of this structure this will always be
either two zero bytes or none.
The pixel data is stored in 2-byte chunks. The first byte specifies the number
of consecutive pixels with the same colour. The second byte defines their
colour indices. If the first byte is zero, the second defines an escape code.
The End-of-Bitmap is zero padded to end on a 32-bit boundary. Due to the
16bit-ness of this structure this will always be either two zero bytes or none.
4-bit
16 colour images
8-bit
256 colour
images
Description
>0
any
n pixels to be drawn. The 1st, 3rd, 5th, ... pixels' colour is in c's high-order 4 bits, the even pixels'
colour is in c's low-order 4 bits. If both colour indices are the same, it results in just n pixels of colour
c.
End-of-line
End-of-Bitmap
Delta. The following 2 bytes define an unsigned offset in x and y direction (y being up). The skipped
pixels should get a colour zero.
>=3
The following c bytes will be read as single pixel colours just as in uncompressed files. Up to 12 bits
of zeros follow, to put the file/memory pointer on a 16-bit boundary again.
The following table provides the description of the raster data compression for 8-bit, 256 colour images:
93
Forsk 2011
n (Byte 1) c (Byte 2)
Description
>0
any
End-of-line
End-of-Bitmap
Delta. The following 2 bytes define an unsigned offset in x and y direction (y being up). The skipped
pixels should get a colour zero.
>=3
The following c bytes will be read as single pixel colours just as in uncompressed files. A zero
follows, if c is odd, putting the file/memory pointer on a 16-bit boundary again.
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
94
Line
Description
amount of translation
amount of rotation
AT310_AM_E2
95
Forsk 2011
Description
File "raster.bmp"
ulxmap
ulymap
llxmap
llymap
lrxmap
lrymap
urxmap
urymap
nrows
ncols
The image size expressed as the number of cells across and down
The number of bands (RGB images have three bands)
The image compression rate
The cell measurement units (meters, degrees or feet)
The size of each cell in measurement units
Coordinate space information (Projection, Datum etc.)
Atoll supports uncompressed as well as compressed (or partially compressed) IMG files for DTM.
You can create an MNU file to improve the clutter class map loading.
The colour-to-code association (raster maps) may be automatically imported from the IMG file.
These files are automatically geo-referenced, i.e., they do not require any additional file for geo-reference.
For image files, the number of supported bands is either 1 (colour palette is defined separately) or 3 (no colour palette but
direct RGB information for each pixel). In case of 3 bands, only 8 bit per pixel format is supported. Therefore, 8-bit images,
containing RGB information (three bands are provided: the first band is for Blue, the second one is for Green and the third for
Red), can be considered as 24 bit per pixel files. 32 bit per pixel files are not supported.
If you are using compressed Erdas Imagine files, performance may be improved by
either hiding the Status Bar or by hiding some of the information displayed in the
Status Bar (altitude, clutter class, or clutter height). For more information, see "Hiding
Information Displayed in the Status Bar" on page 179.
Compressed files can be exported to uncompressed files using Atoll.
96
Numerical continuous grids, which contain numerical information (such as DTM), and are stored in files with the GRD
extension.
AT310_AM_E2
Classified grids, which contain alphanumeric (characters) information, and are stored in files with the GRC extension.
Atoll is capable of supporting the Vertical Mapper Classified Grid (GRC) and Vertical Mapper Continuous Grid (GRD) file
formats in order to import and export:
GRD: DTM, image, population, traffic density, and other data types.
GRC: DTM, clutter classes, clutter heights, environment traffic, image, population, and other data types.
nrows XXX
xllcenter XXX
xllcorner XXX
OR
Significant value relative to the bin centre or corner.
yllcenter
yllcorner XXX
OR
Significant value relative to the bin centre or corner.
cellsize XXX
Grid resolution.
Sample
ncols 303
nrows 321
xllcorner 585300.000000
yllcorner 5615700.000000
cellsize 100.000000
nodata_value 0
...
97
Forsk 2011
Line
Description
amount of translation
amount of rotation
The index file structure is simple; it is an ASCII text file that holds position information about the file. It contains five
columns. You can open an index file using any ASCII text editor. The format of the index file is as follows:
Field
Type
Description
File name
Text
East min
Float
East max
Float
North min
Float
North max
Float
Square size
Float
The projection file provides information about the projection system used. This file is optional. It is an ASCII text file
with four lines maximum.
Line
Description
Spheroid
Zone
Projection
Central meridian
Latitude and longitude of projection central meridian and equivalent x and y coordinates in meters
(optional)
In the associated binary file, the value -9999 corresponds to No data which is supported
by Atoll.
Sample
Index file associated with height file (DTM data):
sydney1
98
AT310_AM_E2
The menu file, an ASCII text file, defines the feature codes for each type of clutter. It consists of as many lines (with
the following format) as there are clutter codes in the clutter data files. This file is optional.
Field
Type
Description
Clutter-code
Integer (>1)
Feature-name
Text (32)
The index file gives clutter spatial references. The structure of clutter index file is the same as the structure of DTM
index file.
In the associated binary file, the value -9999 corresponds to No data which is supported
by Atoll.
Sample
Menu file associated with the clutter file:
1
open
sea
inlandwater
residential
meanurban
denseurban
buildings
village
industrial
10
openinurban
11
forest
12
parks
13
denseurbanhigh
14
blockbuildings
15
denseblockbuild
16
rural
17
mixedsuburban
The menu file, an ASCII text file, lists the vector types stored in the database. The menu file is composed of one or
more records with the following structure:
Field
Type
Description
Integer (>0)
99
Forsk 2011
Field
Type
Description
Vector type
name
Text (32)
The index file, an ASCII text file, lists the vector files and associates each vector file with one vector type, and optionally
with one attribute file. The index file consists of one or more records with the following structure:
Field
Type
Description
Text (32)
Attribute file
name
Text (32)
Dimensions
Real
eastmin: minimum x-axis coordinate of all vector path points in the vector file
eastmax: maximum x-axis coordinate of all vector path points in the vector file
northmin: minimum y-axis coordinate of all vector path points in the vector file
northmax: maximum y-axis coordinate of all vector path points
Vector type
name
Text (32)
Name of the vector type with which the vector file is associated. This one must match
exactly a vector type name field in the menu file.
The attribute file stores the height and description properties of vector paths. This file is optional.
Sample
Index file associated with the vector files
sydney1.airport 313440 333021 6239426 6244784 airport
sydney1.riverlake 303900 342704 6227900 6267900 riverlake
sydney1.coastline 322837 343900 6227900 6267900 coastline
sydney1.railways 303900 336113 6227900 6267900 railways
sydney1.highways 303900 325155 6240936 6267900 highways
sydney1.majstreets 303900 342770 6227900 6267900 majstreets
sydney1.majorroads 303900 342615 6227900 6267900 majorroads
The text data files are ASCII text files with the following format:
Airport
637111.188 3094774.00
Airport
628642.688 3081806.25
Each file contains a line of text followed by easting and northing of that text, etc.
100
The index file, an ASCII text file, stores the position of each text file. It consists of one or more records with the
following structure:
Field
Type
Description
File name
Text (32)
East Min
Real
Minimum x-axis coordinate of all points listed in the text data file
East Max
Real
Maximum x-axis coordinate of all points listed in the text data file
AT310_AM_E2
Field
Type
Description
North Min
Real
Minimum y-axis coordinate of all points listed in the text data file
North Max
Real
Maximum y-axis coordinate of all points listed in the text data file
Text feature
Text (32)
The menu file, an ASCII text file, contains the text features. This file is optional.
Airport
Ferryport
Railway_Station
Type
Description
Class code
Integer (>0)
Class name
Text (50)
none
open
sea
inland_water
residential
meanurban
101
102
Forsk 2011
AT310_AM_E2
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, and WiMAX 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 transciever (TRX) can carry one ARFCN which may
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.
An index.xml file which contains the mapping between the data tables in Atoll and the XML file created for each table.
One XML file per data table which contains the data table format (schema) and the data.
When XML files are imported to a document, the table and field definitions are not modified, i.e., the Networks and
CustomFields tables are exported to XML file but are not imported.
The following sections describe the structures of the XML files created at export.
Description
Atoll_File_System
Corresponds to the SYSTEM_ field of the Networks table of the exported document
Atoll_File_Technology
Corresponds to the TECHNOLOGY field of the Networks table of the exported document
Atoll_File_Version
The index file also contains the mapping between the tables exported from Atoll and the XML files corresponding to each
table. This list is sorted in the order in which tables must be imported in Atoll.
The list is composed of <XML_Table.../> tags with the following attributes:
Attribute
Description
XML_File
Atoll_Table
103
Forsk 2011
104
AT310_AM_E2
Pattern
Discriptor 2
End
Co-polar Horizontal Diagram: Horizontal co-polar diagram (the second entry in the preceding descriptor is 0). The
format is space-separated angle attenuation pairs. For example, 0 0 1 0 2 0.1....
Co-polar Vertical Diagram: Vertical co-polar diagram (the first entry in the preceding descriptor is 1). The format is
space-separated angle attenuation pairs. For example, 0 0 1 0.1....
The format of 2D antenna patterns containing co-polar and cross-polar diagrams can be understood from Figure 9.2 on
page 106.
105
Forsk 2011
Pattern
Discriptor 1
Pattern
Discriptor 3
Pattern
Discriptor 2
Pattern
Discriptor 4
Co-polar Horizontal Diagram: Horizontal co-polar diagram (the second entry in the preceding descriptor is 0). The
format is space-separated angle attenuation pairs. For example, 0 0 1 0 2 0.1....
Co-polar Vertical Diagram: Vertical co-polar diagram (the first entry in the preceding descriptor is 1). The format is
space-separated angle attenuation pairs. For example, 0 0 1 0.1....
Cross-polar Horizontal Diagram: Horizontal cross-polar diagram (the second entry in the preceding descriptor is 0).
The format is space-separated angle attenuation pairs. For example, 0 0 1 0 2 0.1....
Cross-polar Vertical Diagram: Vertical cross-polar diagram (the first entry in the preceding descriptor is 1). The format
is space-separated angle attenuation pairs. For example, 0 0 1 0.1....
You may use a 3rd party software or develop a tool to to convert the contents of the DIAGRAM field into binary. In binary,
each antenna is described by a header and a list of value pairs.
The header is defined as follows:
Then follows the content of each of the defined diagrams, i.e., the diagrams whose sizes (siz0, siz1, siz2, siz3) are not zero.
Each diagram consists of a list of value pairs. The number of value pairs in a list depends on the value of the siz0, siz1, siz2,
and siz3 parameters. For example, siz2 = 5 means there are five value pairs in the third diagram.
The value pairs in each list are:
ang: (Short integer, 16 bits) The first component of the value pair is the angle in degrees multiplied by 100. For
example, 577 means 5.77 degrees.
loss: (Short integer, 16 bits) The second component of the value pair is the loss in dB for the given angle ang.
106
AT310_AM_E2
Header: The text file may contain a header with additional information. When you import the antenna pattern you
can indicate the row number in the file where the header ends and the antenna pattern begins.
Antenna Pattern: Each row contains three values to describe the 3D antenna pattern. The columns containing the
values can be in any order:
Azimuth: Allowed range of values is from 0 to 360. The smallest increment allowed is 1.
Tilt: Allowed range of values is from -90 to 90 or from 0 to 180. The smallest increment allowed is 1.
Attenuation: The attenuation in dB.
Pattern
Discriptor 2
Pattern
Discriptor 3
Pattern
Discriptor 4
Pattern
Discriptor 5
Pattern
Discriptor 6
Pattern
Discriptor 7
Pattern
Discriptor 8
Co-polar H-V Diagram: Co-polar H-V diagram (the second and third entries in the preceding descriptor are 0 1). The
format is space-separated angle attenuation pairs. For example, 0 0 1 0.5....
107
Forsk 2011
Fourth entry: The number of angle-attenuation pairs in the second co-polar diagram. For example, 360.
Co-polar H-H Diagram: Co-polar H-H diagram (the first and second entries in the preceding descriptor are 0 0). The
format is space-separated angle attenuation pairs. For example, 0 0 1 0.5....
Co-polar V-V Diagram: Co-polar V-V diagram (the first and second entries in the preceding descriptor are 1 1). The
format is space-separated angle attenuation pairs. For example, 0 0 1 0.5....
Co-polar V-H Diagram: Co-polar V-H diagram (the first and second entries in the preceding descriptor are 1 0). The
format is space-separated angle attenuation pairs. For example, 0 0 1 0.5....
Cross-polar H-V Diagram: Cross-polar H-V diagram (the second and third entries in the preceding descriptor are 0 1).
The format is space-separated angle attenuation pairs. For example, 0 0 1 0.5....
Cross-polar H-H Diagram: Cross-polar H-H diagram (the first and second entries in the preceding descriptor are 0 0).
The format is space-separated angle attenuation pairs. For example, 0 0 1 0.5....
Cross-polar V-V Diagram: Cross-polar V-V diagram (the first and second entries in the preceding descriptor are 1 1).
The format is space-separated angle attenuation pairs. For example, 0 0 1 0.5....
Cross-polar V-H Diagram: Cross-polar V-H diagram (the first and second entries in the preceding descriptor are 1 0).
The format is space-separated angle attenuation pairs. For example, 0 0 1 0.5....
108
Length
(Char)
Description
Antenna Manufacturer
30
Name under which the data was filed with the FCC
30
Full model number as used when the data was filed with the FCC
Comment
30
FCC ID number
16
16
AT310_AM_E2
Field
Length
(Char)
Description
Date of data
16
Manufacturer ID Number
16
Frequency range
16
This is to identify the full frequency range for which this pattern is valid and
agrees with the range as specified in the printed pattern. The frequency is in
Megahertz.
Mid-band gain
16
16
This is the included angle centered on the main beam of the antenna and
defines the angle where the antenna response falls -3 dB
Polarization
+Space
+Data count
+Space
Angle
+Space
+Antenna Response
+Space
7
7
7
7
Sample
MARK ANTENNA PRODUCTS Inc.
MHP-100A120D
(none)
M15028
M15027
11-25-85
NONE
10700-11700 MHZ
48.4 dB
0.6 Deg
HH 39
109
-180 -88
-160 -88
-150 -90
-97 -90
-66 -70
...
160 -88
180 -88
HV 33
-180 -89
-170 -89
...
180 -89
VV 39
-180 -88
-160 -88
...
150 -90
160 -88
180 -88
VH 33
-180 -89
-170 -89
-160 -90
...
180 -89
ELHH 7
-4 -36
-1.7 -30
...
4 -36
ELHV 11
-4.5 -63.4
...
4.5 -63.4
ELVV 7
-4 -36
...
4 -36
ELVH 11
-4.5 -63.4
...
4.5 -63.4
110
Forsk 2011
AT310_AM_E2
Field
Length
(Char)
Abbreviated
Name
Description
Revision Number
42
REVNUM
Revision Date
16
REVDAT
Comment1
80
COMNT1
Comment2
80
COMNT2
Antenna Manufacturer
42
ANTMAN
Model Number
42
MODNUM
Pattern ID Number
42
PATNUM
NSMA ID number
13
FILNUM
Used when more than one file is associated with a specific antenna
model number.
This field will contain the particular file number and the total
number of files associated with that model number. An example of
such a case would be a dual band antenna with two pattern files
associated with it.
Feed Orientation
13
FEDORN
Orientation of the feed hook when looking from the back of the
antenna in the direction of the mechanical boresite
Description1
80
DESCR1
Description2
80
DESCR2
Description3
80
DESCR3
Description4
80
DESCR4
Description5
80
DESCR5
Date of data
16
DTDATA
LOWFRQ
21
21
HGHFRQ
Gain Units
15
GUNITS
Gain unit
Low-band gain
12
LWGAIN
Gain of the antenna at the low frequency of the frequency band. The
gain is in units described in GUNITS
Mid-band gain
16
MDGAIN
Gain of the antenna at the mid frequency of the frequency band and
may include a full bandwidth tolerance. The gain is in units
described in GUNITS
High-band gain
12
HGGAIN
Mid-band Az Bmwdth
16
AZWIDT
Mid-band El Bmwdth
16
ELWIDT
Connector Type
80
CONTYP
VSWR
13
ATVSWR
Front-to-back Ratio(dB)
10
FRTOBA
Worst case power level in dB between the main lobe peak and the
peak of the antennas back lobe. The back lobe peak does not
necessarily point 180 degrees behind the main lobe.
ELTILT
16
111
112
Forsk 2011
Field
Length
(Char)
Abbreviated
Name
Description
13
RADCTR
12
POTOPO
17
MAXPOW
14
ANTLEN
Mechanical length of the antenna (m). This does not include the
antenna mount. For a circularly symmetric parabolic antenna this
would be the diameter.
14
ANTWID
Mechanical width of the antenna (m). This does not include the
antenna mount. For a circularly symmetric parabolic antenna this
would be the diameter.
14
ANTDEP
Mechanical depth antenna (m). This does not include the antenna
mount.
16
ANTWGT
Future Field
80
FIELD1
Future Field
80
FIELD2
Future Field
80
FIELD3
Future Field
80
FIELD4
Future Field
80
FIELD5
Pattern Type
16
PATTYP
10
NOFREQ
The number of pattern frequencies which comprise the full data set.
21
PATFRE
# Pattern cuts
11
NUMCUT
Pattern Cut
11
PATCUT
Polarization
15
POLARI
# Data Points
13
NUPOIN
25
FSTLST
The first and last angle (in degrees) of the antenna pattern data.
Pattern data shall be expressed monotonically, with respect to
angle. Azimuths shall be stated as either 180 to +180 or 0 to 360
degrees.
X-axis Orientation
53
XORIEN
Y-axis Orientation
53
YORIEN
Z-axis Orientation
53
ZORIEN
28/point
End of file
11
This field designates the end of the file with the characters EOF
AT310_AM_E2
Sample
REVNUM:,NSMA WG16.99.050
REVDAT:,19990520
ANTMAN:,RADIO WAVES INC
MODNUM:,HP4-64
DESCR1:,4 FT LOW SIDELOBE ANTENNA
PATNUM:,9005
DTDATA:,20030807
LOWFRQ:,6425
HGHFRQ:,7125
GUNITS:,DBI/DBR
LWGAIN:,35.5
MDGAIN:,35.9
HGGAIN:,36.3
AZWIDT:,2.8
ELWIDT:,2.8
ELTILT:,0
ANTLEN:,1.2,
PATTYP:,ENVELOPE,
NOFREQ:,NA,
PATFRE:,NA,
NUMCUT:,4,
PATCUT:,AZ,
POLARI:,H/H,
NUPOIN:,29,
FSTLST:,-180,180
-180,-60,
-100,-60,
-51,-42.3,
...
PATCUT:,AZ,
POLARI:,H/V,
NUPOIN:,11,
FSTLST:,-180,180
-180,-60,
-22,-60,
...
PATCUT:,AZ,
POLARI:,V/V,
NUPOIN:,33,
FSTLST:,-180,180
-180,-60,
...
PATCUT:,AZ,
POLARI:,V/H,
NUPOIN:,11,
FSTLST:,-180,180
-180,-60,
113
Forsk 2011
...
ENDFIL:,EOF,
114
Row
Description
File header. The file type indicates the data contained, the format
and the version of the format. For version 1.0 of the Equipment
format, this value must be EQUIP1.0.
Type of modulation
"DEVIATION", Deviation
"THRESH_ANA", Threshold for 30dB analog signalto-noise level, Threshold for 37dB analog signal-tonoise level
AT310_AM_E2
Row
Description
Dispersive fade margin (dB) at the specified BER (digital radio only) Not used by Atoll
"TX_FILTER",
115
Forsk 2011
Row
Description
Number of comments
"COMMENT", Description #1
Comment
"COMMENT", Description #2
Comment
"COMMENT", Description #n
Comment
File trailer. The file type indicates the data contained, the format
and the version of the format. For version 1.0 of the Equipment
format, this value must be EQUIP1.0.
Sample
"$HDR", "EQUIP1.0", "$"
"EQUIP_MFG", "Alcatel USA"
"MFG_MODEL", "MDR-6706-8"
"REV_NUM", "Version 1.0"
"REV_DATE", "03-01-1999"
"RADIO_ID", "JF6-9406"
"FCC_CODE",
"EQ_DATE", "02-24-1999"
"EMISSION", "2M50D7W"
"MAX_LOADING", 192
"DATA_RATE", 12.4
"RADIO_CAP", 8, "DS1"
"MODULATION", "128 TCM"
"DEVIATION",
"FREQ_RANGE", 5850, 7125
"POWER_OPTION", 15, 29, 31
"POWER_RANGE"
"STABILITY", 0.001
"ATPC_POWER", 10
"ATPC_STEP", 1
"ATPC_TRIG", -65
"THRESH_DIG", -79, -81
"THRESH_ANA"
"BRANCHING", "Non-Protected", 0, 0
"BRANCHING", "Monitored Hot-Standby", 0, 0.5, 10
"MAX_RSL", -10, -8
"DFM", 68, 70
"TX_SPECTRUM", 25
"CURVE_POINT", -3.12, -85.65
...
"CURVE_POINT", 3.12, -85.51
"TX_FILTER", 0
"FCC_BANDWIDTH", 2.5
"99%_BANDWIDTH", 2.48
"3DB_BANDWIDTH", 2.08
"T/T_FREQ_SEP", 49, 2.5, 28
"T/R_FREQ_SEP", 132, 105, 33
116
AT310_AM_E2
"T/R_FIXED"
"T/I_LIKE", 171
"CURVE_POINT", -125.000, -130.7
...
"CURVE_POINT", 125.000, -133.0
"T/I_CW", 171
"CURVE_POINT", -125.000, -152.9
...
"CURVE_POINT", 125.000, -143.0
"T/I_OTHER", "", 0, 0
"BB_FREQ"
"RX_RF_FILTER", 68
"CURVE_POINT", -125, -113.7
...
"CURVE_POINT", 125, -110.5
"RX_IF_FILTER", 0
"IF_FILTER_EXT", 0
"RX_BB_FILTER", 0
"COM_COUNT", 1
"COMMENT", "T/I Data for 6.425-7.125 GHz band"
"$TLR", "EQUIP1.0", "$"
DBF Structure
Byte
Description
0...n
n+1
1st record of fixed length (see next parts); 2nd record (see next part for size, byte10) ; last
record
last
Remarks
DBF Header
The DBF header size is variable and depends on the field count.
117
Forsk 2011
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
0x01
Encrypted
D4, D5
0x00
normal visible
All
15
16
12
0 (1)
D4,D5
28
0x01
Fp, D4, D5
0x00
All
language driver ID
D4, D5
29
30
32
n*32
+1
0x01
Fp
0x02
Fp
0x03
Fp
0xC8
codepage1250 Windows EE
Fp
0x00
ignored
0,0
reserved
All
all
all
0x0D
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
118
AT310_AM_E2
Byte
Size
24
31
Contents
Description
Applies to
0x00
ignored
0...0
reserved
all
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
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
Type
Description
TX_NAME
Text
FILE_NAME
Text
119
Field
Type
MODEL_NAME
Text
MODEL_SIG
Text
Signature (identity number) of model used in calculations. You may check it in the
propagation model properties (General tab).
The Model_SIG is used for the purpose of validity. A unique Model_SIG is assigned to
each propagation model. When model parameters are modified, the associated model
ID changes. This enables Atoll to detect path loss matrix invalidity. In the same way, two
identical propagation models in different projects do not have the same model IDa.
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
b.
c.
Description
NCOLS
Float
FREQUENCY
Float
Frequency band
TILT
Float
AZIMUTH
Float
TX_HEIGHT
Float
TX_POSX
Float
TX_POSY
Float
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.
Forsk 2011
In order to benefit from the calculation sharing feature, users must retrieve the propagation models from the same
central database. This can be done using the Open from database command for a new document or the Refresh
command for an existing one. Otherwise, Atoll generates different model_ID (even if same parameters are applied on
the same kind of model) and calculation sharing become unavailable due to inconsistency.
These coordinates enable Atoll to determine the area of calculation for each transmitter.
These coordinates enable Atoll to determine the rectangle including the computation zone.
120
AT310_AM_E2
Type
Description
TX_NAME
Text
FILE_NAME
Text
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.
121
Forsk 2011
In the following format descriptions and samples, lines starting with the "#" are considered as comments.
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.
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:
##------------#------------#------------#-----------#------------------#
122
AT310_AM_E2
| Probability
##------------#------------#------------#-----------#------------------#
#
# Warning, The parameter settings of this header can be wrong if
# the "export" is performed following an "import". They
# are correct when the "export" follows a "calculate".
#
# Service Zone Type is "Best signal level of the highest priority HCS layer".
# Margin is 5.
# Cell edge coverage probability 75%.
# Traffic spreading was Uniform
##---------------------------------------------------------------------#
1
TCH_INNER
8
9
a.
BCCH,TCHa
1
0.944
10
0.904
11
0.892
14
0.844
15
0.832
16
0.812
17
0.752
22
0.316
25
0.292
0.944
10
.904
13
0.872
14
0.84
17
0.772
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
123
Forsk 2011
The last four columns describe the interference matrix scope. One transmitter per line is described separated with a tab
character.
Sample
# Calculation Results Dictionary File.
# Version 2.1,
# Fields are:
##-----------#-----------#-----------#-----------#---------#---------#
#|Transmitter|Transmitter|BCCH during|BSIC during|% of vic'|% of int'|
#|Name
##-----------#-----------#-----------#-----------#---------#---------#
#
# Warning, The parameter settings of this header can be wrong if
# the "export" is performed following an "import". They
# are correct when the "export" follows a "calculate".
#
# Service Zone Type is "Best signal level per HCS layer".
# Margin is 5.
# Cell edge coverage probability is 75%.
# Traffic spreading was Uniform (percentage of interfered area)
##---------------------------#
Site0_0
-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
124
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.
AT310_AM_E2
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".
#
# 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
125
Forsk 2011
Column
Name
Description
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
Column5
Probability to have C/I the value specified in column 4 (C/I threshold). This
field must not be empty.
Sample
# Calculation Results Data File.
# Version 1.1, Tab separated format. Commented lines start with #.
# Remark:
# Fields are:
#-----------------------------------------------------------------------#Transmitter
Interferer
TRX type
C/I
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
##---------------------------------------------------------------------#
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
...
126
AT310_AM_E2
Column
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
# the "export" is performed following an "import". They
# are correct when the "export" follows a "calculate".
#
# Service Zone Type is "Best signal level of the highest priority HCS layer".
# Margin is 5.
# Cell edge coverage probability 75%.
# Traffic spreading was Uniform
##---------------------------------------------------------------------#
Site0_2
Site0_1
0.226667
0.024
Site0_2
Site0_3
0.27
0.024
Site0_3
Site0_1
0.276
0.02
Site0_3
Site0_2
0.226
0.028
The columns in the sample above are separated with a tab. These columns can also be separated with a semilcolon:
Site0_2;Site0_1;0.226667;0.024
Site0_2;Site0_3;0.27;0.024
Site0_3;Site0_1;0.276;0.02
Site0_3;Site0_2;0.226;0.028
127
128
Forsk 2011
AT310_AM_E2
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 may lead to hundreds of files describing the geographic data. Atoll is designed to
optimise memory consumption, which enables it to perform efficiently with regional tiles (1 tile/file per region). In
Atoll, Merging small tiles to build a regional tile can improve performance greatly.
To note as well:
Recommended Formats
In order to improve performance, it is recommended to use uncompressed DTM and clutter files, for example, BIL
files. Using compressed geographic data files, for example, compressed TIF or Erdas Imagine, can cause performance
reduction due to decompression of these files in real time. If you are using compressed geographic data files, it is
strongly recommended to:
Either, hide the status bar that displays geographic data information in real time. You can hide the status bar from
the View menu.
Or, disable the display of some of the information contained in the status bar, such as altitude, clutter class, and
clutter height using an option in the Atoll.ini file, see "Hiding Information Displayed in the Status Bar" on page 179.
The following table shows the recommended file formats for different geographic data:
Geographic data type
Scanned maps
ECW
Vectors
SHP
129
Forsk 2011
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 177.
Link or Embed
Only embed path loss matrices in ATL files if you wish to make a portable document. In all other cases, it is
recommended to link path loss matrices to the Atoll documents.
Externalising path loss matrices to shared or private path loss folders will keep the ATL file size reasonable, which will
result in less fragmentation. Externalising path loss matrices does not reduce the performance of display and
calculations in Atoll.
It is recommended to set the paths to the private and shared path loss matrices folders using the Universal Naming
Convention (UNC).
Following the UNC, an absolute path, such as "C:\Program Files\Forsk\PathLosses\...", is represented as
"\\Computer\C\Program Files\Forsk\PathLosses\...", where "Computer" is the computer name, and "C" is the share
name of disk C.
Example:
Absolute Path
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.
10.3 Databases
Database Upgrade
130
Table and field names should only use alphanumeric characters (A-Z, a-z, 0-9).
Table and field names must not start with a numeric character (0-9).
Table and field names must not contain an SQL or RDBMS-specific keyword, such as ORDER, DATE, etc.
AT310_AM_E2
Table and field names must not contain spaces or special characters, such as periods (.), exclamation marks (!),
interrogation marks (?), parentheses (()), brackets ({}), square brackets ([]), etc.
Boolean fields, system or user-defined, should always have default values assigned.
The CustomFields table enables you to define default values and choice lists for any field in any table in Atoll, including
user-defined fields that you add to the Atoll tables. The values defined in this table have priority over the internal predefined default values. If you define floating point default values, make sure that all the users have the same decimal
separator.
If you wish to add custom fields in the Atoll document, you should first add the field in the database, and then update
your Atoll document from the database.
When setting up your database for the first time, try to anticipate user requirements in terms of custom fields in Atoll
tables. Some requirements of the different user groups may be satisfied if a few general-purpose user-defined fields
are added in Atoll tables when setting up the database.
For example, if you add three user-defined fields (one of type integer, float, and text (limited size)) to the Sites and
Transmitters tables, users will be able to use these for sorting, filtering, grouping, or other purposes. This approach
may help the database function a long time before users require the addition of other custom fields.
To improver performance, if your projects allow it, reduce the size of the fields corresponding to the sites and
transmitters names.
To improver performance, unless absolutely necessary, do not add user-defined fields of Text type. Rather, use
numeric field types, which allow sorting and other functions. If you must add Text fields, allocate them the appropriate
size that would suffice. For example, a 255-character long Text type field would, for the most part, occupy disk space
for no purpose.
To improver performance, you should avoid adding custom fields to the neighbour management tables.
Atoll can process four simultaneous path loss matrices calculations, which means high CPU and RAM resource consumption,
and as path loss calculations share the amount of memory allocated to the Atoll session, the total memory requirement may
exceed the Microsoft Windows (32-bit editions) limit of 2 GB per process. This is especially the case with large Atoll
documents and propagation models that require considerable memory.
Troubleshooting and Solution
As the cause of this problem is resource saturation on the server, resource consumption should be controlled in order to avoid
memory and CPU overloading as follows:
To reduce the impact of a large number of simultaneous path loss calculations, a Distributed Calculation Server should
be set up. Using the Distributed Calculation Server, path loss calculations can be performed outside Atoll. Using the
Distribution Calculation Server has the following advantages:
Path loss calculations are limited to four parallel instances regardless of the number of Atoll sessions running on
the server. This notably improves the memory and CPU consumption.
A queuing system, integrated in the Distributed Calculation Server, manages the calculation requests from
different Atoll sessions.
A failover mechanism automatically switches and hands over the path loss calculations back to Atoll in case a
problem occurs.
Path loss calculations are carried out by a separate process (AtollSvr), which has its own memory allocation apart
from Atoll, i.e., the amount of memory needed for calculations does not impacts the Atoll memory allocation.
This set up can introduce considerable improvements in both the number of Atoll sessions per server and the calculations. A
server with four processors (eight threads with hyper-threading) can accommodate four simultaneous path loss calculations
and use the other four threads for Atoll sessions. Atolls interface will also be more efficient and the overall processing time
for various tasks will be improved.
131
Forsk 2011
In order to prevent users from deactivating the use of the Distributed Calculation Server,
and hence bypassing the resource control procedure established above, the Atoll.ini file
should be set made read-only for end-users.
Apart from the above setup, you can also make some other system improvements:
To avoid error messages caused by requesting a large number of files over the network, the following Microsoft
Windows registry parameter can be modified in order to dedicate more resources to network read/write operations:
IRQSTACKSIZE should be set to 30 instead of 11, for example.
To avoid out of memory problems, the Pagefile size should be increased so that the server does not run out of global
memory when supporting more than 10 Atoll sessions simultaneously. This is different from the 2 GB per process
limit. Virtual memory can be increased from 8 GB to 16 GB, for example.
For 32-bit Windows operating systems, you can also increase the default Windows memory allocation limit from 2 GB
to 3 GB as explained in "Process Memory" on page 132.
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 may be, for
example, groups of users working on different regions, groups of users working on different technologies, groups
of users focusing on certain operations (i.e., performing certain types of coverage predictions, performing the AFP,
etc.).
Coverage prediction studies can easily be duplicated within Atoll. Before creating study templates, and the XML
studies file, make sure that this study template is aimed at serving a number of users. This means, avoid creating study
templates unless these will be needed for a long time by a number of users. You can use the configuration files to store
your created coverage prediction studies locally. And, you can also use the study duplicate feature to create copies of
existing coverage prediction studies.
132
AT310_AM_E2
10.7 Printing
You should place different layers of geographic and radio data in a definite order when printing a project or a section of the
project. The following order should be followed:
1. Visible objects of the Data tab
All the visible objects of the Data tab are displayed above those in the Geo tab. However, it is strongly recommended
to place vector layers on the top of coverage prediction plots. You can do this by transferring these vector layers to
the Data tab using the context menu. For performance reasons, it is advised to place vector layers on top of raster
layers before printing a project. Sites and Transmitters must be on the very top, above all other layers. You should
place sites and sectors on the top, then vector layers, and then raster layers.
2. Unidimensional vectors (points)
3. Open polygonal vectors (lines, i.e., roads and other linear items, etc.)
4. Closed polygonal vectors (surfaces, i.e., zones and areas, etc.)
5. Multi-format maps (vector or raster maps, i.e., population, rain, generic maps, traffic, etc.)
6. Transparent raster maps (clutter class maps, etc.)
7. Non-transparent maps (images, DTM, clutter height maps, etc.)
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 may 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.
133
Forsk 2011
A Planet Index file contains the path to and the name of each antenna file available. Creating such an Index file when
there are hundreds of antenna patterns available can be a difficult task. You can easily create the index file from the
Microsoft Windows command prompt. You can open the Command Prompt window by selecting Start > Run, entering
"cmd" and pressing ENTER. In the Command Prompt window, navigate to the directory containing the antenna
pattern files, enter the following command and press ENTER:
dir /b > Index
This will create a file called "Index" in the same directory as the antenna patter files containing a list of all the antenna
pattern file names, with one name per line. The file will also contain a line with its own name, so, before importing
this file into Atoll, you should use a text editor to remove the line containing the file name "Index."
The electrical tilt, which can be defined in the antenna properties dialogues in Atoll, is an additional electrical downtilt.
It might be redundant to define an additional electrical downtilt for antennas whose patterns already include
electrical tilt. Users should verify whether the antenna patterns of the antennas in their projects, do not already
include the effect of an electrical tilt.
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.
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 MetaFrame environment, you should restart your Citrix server every week or fortnight.
The exact time should be determined by the administrator depending on the state of the network (LAN).
In certain cases, it might be more appropriate to start working on a completely fresh ATL file. If you have been working
on your existing ATL file for a long time, it might 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 141.
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.
134
AT310_AM_E2
Memory Allocation
If you have to open several large ATL files simultaneously on the same computer, it is better to open each in a separate
Atoll session rather than to open them all in the same Atoll window. Each Atoll session on the same computer has its
own memory space allocated by the operating system. Each computer consumes a single licence token independent
of the number of Atoll sessions opened simultaneously.
For 32-bit Windows operating systems, you can also increase the default Windows memory allocation limit from 2 GB
to 3 GB as explained in "Process Memory" on page 132.
File Size
Coverage predictions calculated over large areas require more memory. If you are working on an Atoll document
covering a large area, with coverage predictions calculated over the entire network, this document will require more
memory for loading all the coverage predictions. You can reduce memory consumption by making copies of your Atoll
document, and keeping a few coverage predictions in each copy. These ATL files will be faster to load and work with
compared to a single ATL file with all the coverage predictions.
Large coverage predictions can take up a considerable amount of memory even if they are not displayed on the map.
Externalise DTM, clutter, path loss matrices, and any other data that can be externalised, so that the ATL file size does
not become unnecessarily large.
Before starting path loss calculation, verify that the calculation radii and resolutions assigned to the different types of
transmitters are consistent. For example, calculating path loss matrices of picocells over large calculation radii would
only waste memory and disk space.
For calculating path loss matrices over large areas, you should use the dual resolution feature in Atoll. Define short
calculation radii and fine resolutions for the main path loss matrices, and large calculation radii and low resolutions
for extended path loss matrices. This approach decreases the calculation time significantly compared to calculating
just one matrix per transmitter using a fine resolution. The main path loss matrices should be calculated using the
same resolution as the resolution of the geographic data available. The extended path loss matrices can be calculated
using a lower resolution, e.g., twice the resolution of the geographic data.
Regionalisation
Use database regionalisation or site lists if you are working on smaller parts of a large network. Atoll loads only the
data necessary for your working area. If you load a large network, Atoll will load a lot of data that might not be
necessary all the time, such as the neighbour relation data.
Use regionalisation or site lists: If you load a large network, Atoll will be required to load a lot of data that might not
be necessary all of the time. For example, in a typical large GSM network, you might have around 10,000 transmitter
records, 20,000 subcell records, 50,000 TRX records, and up to 150,000 neighbour records.
Externalise embedded interference matrices: You can store interference matrices listed in the Interference Matrices
folder in external files. Atoll loads interference matrices from the external files to the memory only when needed. You
will also reduce the ATL file size by externalising the interference matrices.
Adapt calculation radii to the cell type and the EIRP: Before calculating path loss matrices, take care to correctly
associate calculation radii and resolutions to different types of cells. If you calculate path loss matrices for all types of
cells over a large calculation radius, it will unnecessarily burden the C/I and interference matrices computations.
Properly configure the interference thresholds: These thresholds indicate the level after which an interferer can be
ignored. The default value for this threshold (-130 dBm), defined in the Predictions tab of the Predictions folders
Properties dialogue, means that the computations will take into account all the interferers. However, if you set it too
high, you might lose important interference information. The proper value for this threshold depends on the
Reception Thresholds and the C/I Thresholds defined in the Subcells table. The optimum value would be
Min AllSubcells ( RT i CIT i M ) . Which means the minimum value of the factor RT i CIT i M computed for all
135
Forsk 2011
subcells, i. Where, RTi is the reception threshold of the subcell i, CITi the C/I threshold of this subcell, and M is a safety
margin.
Since this interference threshold is used both in interference matrices calculation and in interference predictions, it is
important to have at least a 3-dB margin for the interference energy aggregation in C/I studies. We recommend a
safety margin of 5 dB, which can be reduced if any problem is encountered.
Do not define very high C/I quality thresholds (Default values: 12 dB for BCCH and 9 dB for TCH). If you want a certain
TRX type to carry GPRS/EDGE traffic, you can add 1 or 2 dB to this value for that TRX type, and use the option of safety
margin in the AFP modules Cost tab. The 12 dB and 9 dB default values already include safety margins. If you
increment these values too much, it will unnecessarily load the interference matrix generation and the AFP.
Do not start an AFP session if the interference matrices report indicates problems: All the transmitters should have
interferers and very few of them (not more than 20%) should have more than 70 interferers. If there are too many or
too few entries in your interference matrices, the AFP plan will not be optimal.
If the memory-critical task is interference matrices generation: You can generate interference matrices in a piecewise
manner.
This means that you can generate nation-wide interference matrices with low resolutions based on the percentage of
interfered area (to improve computation time), with a cell edge coverage probability of 50% (which means no access
to clutter for reading standard deviation values), and an interference threshold of -112 dBm. This will provide rough
global interference matrices which can be locally improved. These interference matrices will be less memoryconsuming.
Then, use polygon or site list filters to focus on each important location, and calculate local interference matrices with
higher resolutions and reliabilities. Make sure that the computation zone in your project completely encompasses the
filtering zones that you define.
If the memory-critical task is the AFP session: Try to make the document lighter, e.g., remove coverage prediction
studies, exit and restart Atoll, and try to generate interference matrices with fewer entries.
If the memory-critical task is the traffic capture: You can use traffic load field of the Subcells table to provide traffic
loads directly to the AFP, and possibly skip this step.
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 63.
136
AT310_AM_E2
determined by the size of the planning area. In networks with a large number of sites, transmitters and cells, it is the number
of these network entities that governs this requirement. Pixel size plays an equally important role in all cases.
Network-Wide Input
The file sizes for raster maps (DTM, clutter heights, clutter classes, traffic density or environments, images, etc.) does not
depend on the number of cells, but only on the size of the planning area in pixels.
The following information can provide you with an estimate of disk usage for different geographic data:
Clutter class maps require 1 byte per pixel (2 bytes for Planet format).
Background images require from 1 to 3 bytes per pixel.
Traffic maps require 1 byte per pixel (2 bytes for Planet format).
DTM or clutter height maps require 2 bytes per pixel.
Population maps or other generic maps require from 1 to 4 bytes per pixel.
For one clutter map, one DTM map, one traffic map, and one background image, you may estimate 6 bytes per pixel of the
input area. This data can be shared between different planning alternatives of the same network.
If an embedded geographic data file is deleted from the project, Atoll automatically
compresses the ATL file to avoid file fragmentation.
Cell-Specific Results
For a project with a large number of cells, it is important to consider the disk space required by the propagation prediction
results of each cell. Here, the cell calculation area and the calculation resolution are important factors.
Cell-specific results require 2 bytes per pixel. For example, the propagation results for a sector with a calculation area of 1024
x 1024 pixels will require 2 MB disk space.
If there are different ATL files for planning the same part of the network in different ways, each ATL file will require the same
amount of disk space.
The same rule applies to extended path loss matrices as well.
If embedded path loss matrices are externalised, Atoll automatically compresses the ATL
file to avoid file fragmentation.
Network-Wide Output
Network-wide output (raster results) mainly depends on:
Coverage predictions may have a number of layers depending on the calculation criteria. There can be a single layer for the
entire network or a layer per transmitter, sector, or subcell. The resulting size depends on the number of layers and the
number of colours and thresholds. Therefore, Atoll coverage predictions may require between 1 bit and 2 bytes per pixel of
the calculation area.
Atoll can compress the coverage prediction results when saving a ATL file to avoid file
fragmentation.
You can consider 14 bytes per pixel as a rough estimate to determine the disk space
required for each individual ATL file.
137
Forsk 2011
Most of these parameters have minor influences and the actual requirements are mostly governed by the number of cells and
the number of mobiles generated.
Assuming that there are three carriers used and the number of transmitters and mobiles is high enough so that the other input
can be ignored, the required memory can be roughly approximated by:
R = 14.0 t + 3.25 m
R = 14.0 t + 4.3 m
138
Please note that this is the peak requirement. Less memory will be required once the
calculations are terminated.
This approximation also considers effects due to the operating system, such as
memory over-allocation due to fragmentation. It is a conservative approximation and
in most cases the actual RAM requirement will be below these calculated figures.
A more accurate estimation of the used and required memory for UMTS simulations is
available in the Source Traffic tab of the new simulation group dialogue. To activate
the memory estimation feature, you must add an option in the Atoll.ini file. For more
information, see "Estimating Required and Used Memory Size for UMTS Simulations"
on page 190.
AT310_AM_E2
Coverage Predictions
RAM required during coverage prediction calculations (network-wide raster result) is the same as the required additional disk
space, i.e., between 1 bit and 2 bytes per pixel of the calculation area. Apart from this, temporary memory is required for
calculations like "Coverage by transmitter" and "Coverage by signal level". For these, Atoll temporarily allocates an average
of 4 bytes more per pixel (8 bytes, if the best server margin is not zero) of the calculation area.
Example: The Paris region has a size of around 10 x 13 km. For a calculation resolution of 25 m, this equals 5.2 million pixels.
If a coverage prediction calculates the signal strength of the UMTS pilot in less than 16 colours, it would require a memory of
4 bits per pixel, or a total of 2.6 MB. During the calculation, Atoll would also require 4 more bytes per pixel, which equals
20.8 MB more apart from the 2.6 MB.
For large networks, to avoid loading the entire computation zone in memory, Atoll
divides the coverage prediction computations into smaller tiles, and carries out the
computations on them successively. This subdivision is invisible to the user.
139
140
Forsk 2011
AT310_AM_E2
11 Configuration Files
Configuration files can be used to store parameter and display settings. These files are optional, not required for working with
Atoll, but are useful means for making work easier.
This chapter describes the formats of these files in detail:
Projection and display coordinate systems are stored in the database, not in user
configuration files.
Simulation settings are not stored in user configuration files.
For more information on the contents of user configuration files, see "Contents of User Configuration Files" on
page 142.
A user configuration file may be automatically loaded when Atoll is run if:
a. The file is identified in the command line parameter -Cfg "cfgfilename" (see "Atoll Command Line Parameters" on
page 31 for more information), or
b. The file is named "Atoll.cfg" and is located in the Atoll installation folder. This file will be ignored if a user
configuration file is loaded through the command line parameter.
Additional configuration files (UTF-8 encoded XML-format CFG files or plain text INI files)
The following parameter settings can be stored in additional configuration files with a CFG extension:
For more information on the contents of additional configuration files, see "Contents of Additional Configuration
Files" on page 164.
141
Forsk 2011
142
<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>, 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.)
Displate type <type>, selected field <FieldSelector>, transparency level <Opacity>, visibility flag <visible>, and
visibility range between <minZoom> and <maxZoom>
<Items> properties, such as for each item: <Value>, <Min>, <Max>, <Legend>, <MainColor>,
<SecondaryColor>, <LineStyle>, <LineWidth>, and <FillStyle>
<AddToLegend>: Add to legend option checked or not
<Attributes>, such as: <records> and <fields>, which are,
Common: CODE, COLOR, NAME, HEIGHT
Under <GSM>: STDDEV, COVERI_STDDEV, INDOOR, TX_DIV_GAIN, ANT_HOP_GAIN
Under <UMTS>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, INDOOR, ALPHA, FORTHO,
SM_GAIN_FACTOR, STTD_GAIN_OFFSET
Under <1XRTT>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, INDOOR, ALPHA, FORTHO
Under <TD-SCDMA>: STDDEV, EC_IO_STDDEV, EB_NT_DL_STDDEV, EB_NT_UL_STDDEV, INDOOR,
FORTHO_UL, FORTHO_DL, ANGULAR_SPREAD
Under <IEEE_802.16e>: STDDEV, COVERI_STDDEV, INDOOR, MIMO_GAIN_FACTOR, STTD_OFFSET_DL,
STTD_OFFSET_UL
Under <LTE>: STDDEV, COVERI_STDDEV, INDOOR, MIMO_GAIN_FACTOR, DIV_GAIN_OFFSET_DL,
DIV_GAIN_OFFSET_UL
<DefaultValues>, for the fields stated above.
AT310_AM_E2
<Display>: (Different combinations of the following parameters exist in different display settings.)
Displate type <type>, selected field <FieldSelector>, transparency level <opacity>, visibility flag <visible>, and
visibility range between <minZoom> and <maxZoom>
<Items> properties, such as for each item: <Value>, <Min>, <Max>, <Legend>, <MainColor>,
<SecondaryColor>, <LineStyle>, <LineWidth>, and <FillStyle>
<AddToLegend>: Add to legend option checked or not
<File>: <Format> and <Path> to linked files, if any
Sample
143
<Type>800</Type>
<Integrable>1</Integrable>
</Type>
<Files/>
</Population> // or </GeoClimaticParams> or </Vectors>
<ClassifiedClutter UseOnlyDefault="0">
<Display>
<Type>ByIntervals</Type>
<FieldSelector>3</FieldSelector>
<Opacity>50</Opacity>
<Items>
<Item>
<Min>54.</Min>
<Max>56.</Max>
<Legend>54 <=Height (m) <56</Legend>
<MainColor>255 38 0</MainColor>
<SecondaryColor>255 38 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>10</LineWidth>
<FillStyle>1</FillStyle>
</Item>
</Items>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
</Display>
<Attributes>
<fields>
<field length="1" type="uint" name="CODE"/>
<field length="4" type="int" name="COLOR"/>
<field length="50" type="text" name="NAME"/>
<field length="4" type="real" name="HEIGHT"/>
</fields>
<records/>
</Attributes>
<Name>Clutter Classes</Name>
<AddToLegend>0</AddToLegend>
<DefaultValues>
</DefaultValues>
</ClassifiedClutter>
<Altitudes> // or <BuildingHeights>
<Name>Digital Terrain Model</Name> // or <Name>Clutter Heights</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
<Type>ByIntervals</Type>
<FieldSelector>0</FieldSelector>
<Opacity>50</Opacity>
144
Forsk 2011
AT310_AM_E2
<Items>
<Item>
<Min>900.</Min>
<Max>1000.</Max>
<Legend>900 <=Altitude <1 000</Legend>
<MainColor>255 96 0</MainColor>
<SecondaryColor>255 96 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>10</LineWidth>
<FillStyle>1</FillStyle>
</Item>
</Items>
</Display>
<AddToLegend>0</AddToLegend>
</Altitudes> // or </BuildingHeights>
</Geodataset>
</Atoll>
11.1.2 Zones
The user configuration files store the coordinates of the vertices of the filtering, focus, computation, printing, and geographic
export zone polygons, i.e., the points forming these polygons. The first and the last points have the same coordinates.
Sample
The following sample has rectangular computation and focus zones of the same size.
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<CalculationZone>
<Point>35950.000000 -15445.000000</Point>
<Point>33.000000 -15445.000000</Point>
<Point>33.000000 -33.000000</Point>
<Point>35950.000000 -33.000000</Point>
<Point>35950.000000 -15445.000000</Point>
</CalculationZone>
<FocusZone>
<Point>35950.000000 -15445.000000</Point>
<Point>33.000000 -15445.000000</Point>
<Point>33.000000 -33.000000</Point>
<Point>35950.000000 -33.000000</Point>
<Point>35950.000000 -15445.000000</Point>
</FocusZone>
<Atoll>
Sites folder:
<Name>: Name of the folder
<Display>:
Displate type <type>, selected field <FieldSelector>, visibility flag <Visible>, and visibility range between
<MinZoom> and <MaxZoom>
145
Forsk 2011
146
<SymbolFont> properties, such as font name <Name>, font size <Size>, font colour <Color>, background
colour <BackColor>, and font style <Style>
<LabelFont> properties, such as label font name <Name>, label font size <Size>, label font colour <Color>, label
font background colour <BackColor>, and label font style <Style>
<Items> properties, such as for each <Item>: <Value>, <Legend>, <MainColor>, <SecondaryColor>, <Symbol>,
and <SymbolSize>
<DataTips>: List of <items> displayed in tip texts
<Labels>: List of <items> displayed in labels
<AddToLegend>: Add to legend option checked or not
<DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration
<Filter>, <Groups>, and <Sort> criteria
<Configuration>: If any configuration exists for the folder, this tag contains the configuration <Name> and the
<Filter>, <Groups>, and <Sort> criteria
Antennas folder:
<Name>: Name of the folder
<DefaultConfiguration>: The default configuration for the folder, this tag contains the default configuration
<Filter>, <Groups>, and <Sort> criteria
<Configuration>: If any configuration exists for the folder, this tag contains the configuration <Name> and the
<Filter>, <Groups>, and <Sort> criteria
Links folder:
<Name>: Name of the folder
<Display>: Contains visibility flag <visible>, and visibility range between <minZoom> and <maxZoom>
<AddToLegend>: Add to legend option checked or not
<DefaultConfiguration>: The default configuration for the folder
<LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>, label
font background colour <BackColor>, and label font style <Style>
<SiteDisplay> properties, such as:
<SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, background
colour <BackColor>, and font style <Style>
<LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>,
label font background colour <BackColor>, and label font style <Style>
<Symbol>: Symbol used for microwave links
<ShowText>: Caption for microwave links shown or not
<RepeaterDisplay> properties, such as:
<SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, background
colour <BackColor>, and font style <Style>
CW Measurements folder:
<DefaultConfiguration>: The default configuration for the folder
<Distance>: The minimum <Min> and maximum <Max> distance for measurement filtering
<DistanceUnit>: The distance unit
<Measure>: The minimum <Min> and maximum <Max> measured level for filtering
<MeasureUnit>: The measurement unit
<Angle>: The minimum <Min> and maximum <Max> angle for measurement filtering
<Relative>: Whether the angle is relative to each transmitters azimuth or an absolute value
<Clutter>: For each <Class>, its <Code> and whether it is in the <Filter> or not
<Advanced>: Any advanced filter used for filtering
<PathLosses>: Path loss tuing parameters, i.e., <ParallelAxisRadius>, <PerpendicularAxisRadius>, <GlobalMargin>,
<LocalMargin>, and <Threshold>
<Display>:
AT310_AM_E2
Displate type <Type>, selected field <FieldSelector>, visibility flag <Visible>, and visibility range between
<MinZoom> and <MaxZoom>
<SymbolFont> properties, such as: font name <Name>, font size <Size>, font colour <Color>, background
colour <BackColor>, and font style <Style>
<LabelFont> properties, such as: label font name <Name>, label font size <Size>, label font colour <Color>,
label font background colour <BackColor>, and label font style <Style>
<Items> properties, such as for each <Item>: <Legend>, <MainColor>, <SecondaryColor>, <Symbol>, and
<SymbolSize>
<DataTips>: List of <items> displayed in tip texts
<Labels>: List of <items> displayed in labels
<AddToLegend>: Add to legend option checked or not
Sample
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<FoldersConfigurations>
<Sites>
<Name>Sites</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
<Type>ByValues</Type>
<FieldSelector>8</FieldSelector>
<SymbolFont>
<Name>Wingdings</Name>
<Size>-120</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>32</Style>
</SymbolFont>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-80</Size>
147
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>33</Style>
</LabelFont>
<Items>
<Item>
<Value>Vendor</Value>
<Legend>Vendor</Legend>
<MainColor>255 0 0</MainColor>
<SecondaryColor>255 255 255</SecondaryColor>
<Symbol>164</Symbol>
<SymbolSize>120</SymbolSize>
</Item>
</Items>
<DataTips>
<Item>0</Item>
</DataTips>
<Labels>
<Item>0</Item>
</Labels>
</Display>
<AddToLegend>1</AddToLegend>
<DefaultConfiguration>
<Groups>Type</Groups>
</DefaultConfiguration>
</Sites>
<Antennas>
<Name>Antennas</Name>
<DefaultConfiguration>
<Filter>([CONSTRUCTOR]= Kathrein)</Filter>
</DefaultConfiguration>
<Configuration>
<Name>Conf</Name>
<Filter>([CONSTRUCTOR]= Kathrein)</Filter>
</Configuration>
</Antennas>
<Transmitters> // or <MWMultiHops> // or <MWHubs>
<Name>Transmitters</Name> // or <Name>Multi-Hops</Name> //
or <Name>Point to Multipoint</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
<Type>ByValues</Type>
<FieldSelector>0</FieldSelector>
<Items>
</Items>
<DataTips>
<Item>0</Item>
148
Forsk 2011
AT310_AM_E2
</DataTips>
</Display>
<AddToLegend>1</AddToLegend>
<DefaultConfiguration/>
</Transmitters> // or </MWMultiHops> // or </MWHubs>
<MWLinks>
<Name>Links</Name>
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
</Display>
<AddToLegend>0</AddToLegend>
<DefaultConfiguration/>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-83</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</LabelFont>
<SiteDisplay>
<SymbolFont>
<Name>Wingdings</Name>
<Size>80</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-80</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</LabelFont>
</SiteDisplay>
<Symbol>65444</Symbol>
<ShowText>0</ShowText>
<RepeaterDisplay>
<SymbolFont>
<Name>Wingdings</Name>
<Size>80</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</SymbolFont>
</RepeaterDisplay>
</MWLinks>
149
<CWMeasurements>
<DefaultConfiguration>
<Distance>
<Min>0.</Min>
<Max>1000.</Max>
</Distance>
<DistanceUnit>0</DistanceUnit>
<Measure>
<Min>-105.</Min>
<Max>-90.</Max>
</Measure>
<MeasureUnit>0</MeasureUnit>
<Angle>
<Min>-180.</Min>
<Max>180.</Max>
</Angle>
<Relative>Yes</Relative>
<Clutter>
<Class>
<Code>1</Code>
<Filter>Yes</Filter>
</Class>
</Clutter>
<Advanced>([DIST]> 500)</Advanced>
</DefaultConfiguration>
<PathLosses>
<ParallelAxisRadius>200.</ParallelAxisRadius>
<PerpendicularAxisRadius>100.</PerpendicularAxisRadius>
<GlobalMargin>30.</GlobalMargin>
<LocalMargin>30.</LocalMargin>
<Threshold>-130.</Threshold>
</PathLosses>
<Display>
<Type>ByIntervals</Type>
<FieldSelector>Error (P-M) (dB)</FieldSelector>
<SymbolFont>
<Name>Wingdings</Name>
<Size>-120</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-83</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</LabelFont>
150
Forsk 2011
AT310_AM_E2
<Items>
<Item>
<Min>-20.</Min>
<Legend>Error (P-M) (dB) >=-20</Legend>
<MainColor>255 0 0</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<Symbol>167</Symbol>
<SymbolSize>100</SymbolSize>
</Item>
</Items>
<DataTips>
<Item>M (dBm)</Item>
</DataTips>
<Labels>
<Item>M (dBm)</Item>
</Labels>
</Display>
</CWMeasurements>
<TestMobileData>
<Techno>GSM</Techno>
<DefaultConfiguration>
<Clutter>
<Class>
<Code>1</Code>
<Filter>Yes</Filter>
</Class>
</Clutter>
<Advanced></Advanced>
</DefaultConfiguration>
<PathLosses>
<ParallelAxisRadius>200.</ParallelAxisRadius>
<PerpendicularAxisRadius>100.</PerpendicularAxisRadius>
<GlobalMargin>30.</GlobalMargin>
<LocalMargin>30.</LocalMargin>
<Threshold>-130.</Threshold>
</PathLosses>
<Display>
<Type>ByIntervals</Type>
<FieldSelector>Ec_I0</FieldSelector>
<SymbolFont>
<Name>Wingdings</Name>
<Size>-120</Size>
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</SymbolFont>
<LabelFont>
<Name>MS Shell Dlg</Name>
<Size>-83</Size>
151
Forsk 2011
<Color>0 0 0</Color>
<BackColor>255 255 255</BackColor>
<Style>0</Style>
</LabelFont>
<Items>
<Item>
<Min>-60.</Min>
<Legend>Ec_I0 >=-60</Legend>
<MainColor>255 0 0</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<Symbol>167</Symbol>
<SymbolSize>100</SymbolSize>
</Item>
</Items>
</Display>
</TestMobileData>
<PropagationModels> // or <SmartAntennasModels>
<Name>Propagation Models</Name> // or <Name>Smart Antenna Models</Name>
<DefaultConfiguration/>
</PropagationModels> // or </SmartAntennasModels>
</FoldersConfigurations>
</Atoll>
General tab:
<Techno>: Name of the technology
<Name>: Name of the folder
<Resolution>: Prediction resolution
<Configuration>: <Filter>, <Groups>, and <Sort> criteria for the prediction
<LockedStudy>: Locked or not
Conditions tab: Depend on technologies and prediction types.
<Reliability>: Cell edge coverage probability
<Indoor>: Indoor coverage checked or not
<WithShadowing>: Shadowing margin taken into account or not
...
Display tab:
<Display>: (Different combinations of the following parameters exist in different display settings.)
Display type <type>, selected field <FieldSelector>, visibility flag <visible>, opacity <Opacity>, 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
<DataTips>: List of <items> displayed in tip texts
Sample
GSM coverage by signal level
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<Studies>
<CoverageTRXStudy>
<Techno>GSM</Techno>
<Name>GSM: Coverage by Signal Level 0</Name>
152
AT310_AM_E2
<Display>
<minZoom>500</minZoom>
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
<Type>ByIntervals</Type>
<FieldSelector>80000008</FieldSelector>
<Opacity>50</Opacity>
<Items>
<Item>
<Min>-75.</Min>
<Legend>Best Signal Level (dBm) >=-75</Legend>
<MainColor>255 147 0</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>15</LineWidth>
<FillStyle>1</FillStyle>
</Item>
<Item>
<Min>-85.</Min>
<Legend>Best Signal Level (dBm) >=-85</Legend>
<MainColor>70 255 0</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>15</LineWidth>
<FillStyle>1</FillStyle>
</Item>
<Item>
<Min>-95.</Min>
<Legend>Best Signal Level (dBm) >=-95</Legend>
<MainColor>0 255 217</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>15</LineWidth>
<FillStyle>1</FillStyle>
</Item>
<Item>
<Min>-105.</Min>
<Legend>Best Signal Level (dBm) >=-105</Legend>
<MainColor>0 0 255</MainColor>
<SecondaryColor>0 0 0</SecondaryColor>
<LineStyle>5</LineStyle>
<LineWidth>15</LineWidth>
<FillStyle>1</FillStyle>
</Item>
</Items>
<DataTips>
<Item>c0000000</Item>
<Item>c0000001</Item>
</DataTips>
153
Forsk 2011
</Display>
<AddToLegend>1</AddToLegend>
<Resolution>50</Resolution>
<LockedStudy>0</LockedStudy>
<ComputeHisto>1</ComputeHisto>
<HistoPerTx>0</HistoPerTx>
<HistoLabel></HistoLabel>
<Conditions>
<FieldDbm>
<Min>-105.</Min>
</FieldDbm>
<Reliability>0.75</Reliability>
<TRXType>BCCH</TRXType>
<DefTrgThreshold>1</DefTrgThreshold>
<Indoor>0</Indoor>
<WithShadowing>0</WithShadowing>
</Conditions>
</CoverageTRXStudy>
</Studies>
</Atoll>
154
AT310_AM_E2
<UseGlobalThreshold>: Coverage conditions for WiMAX and LTE: Whether to use a global minimum preamble C/
N or RSRP, or per-cell values
Sample
UMTS HSPA inter-technology, intra-carrier neighbour allocation parameters:
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<ANP_options>
<Techno>UMTS</Techno>
<numMax>16</numMax>
<resolution>-1</resolution>
<minField>-10500</minField>
<margin>500</margin>
<useCoSite>1</useCoSite>
<useAdjacent>1</useAdjacent>
<traffic>0</traffic>
<symetric>0</symetric>
<keepNeighbs>0</keepNeighbs>
<MaxDist>10000</MaxDist>
<PercentCoverage>1000</PercentCoverage>
<UseShadowing>0</UseShadowing>
<reliability>7500</reliability>
<UseIndoor>0</UseIndoor>
<deltaMax>1200</deltaMax>
<applyConstraints>0</applyConstraints>
<covBased>1</covBased>
<minDistImportance>100</minDistImportance>
<maxDistImportance>1000</maxDistImportance>
<minCov>1000</minCov>
<maxCov>3000</maxCov>
<minAdj>3000</minAdj>
<maxAdj>6000</maxAdj>
<minCos>6000</minCos>
155
Forsk 2011
<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.
<allocType>: The parameters/resources to be allocated (memorised from the last AFP session)
<freezeState>: Last minute resource freezing options available in the AFP launch wizard
<numMinutes>: Target time alloted to the AFP
<useDTX>: Consider the effect of discontinuous transmission or not
<dtxVocalFactor>: Voice activity factor for discontinuous transmission
<AfpBasedOnInterference>: Load all potential interferers or not
<AfpBasedOnSeparations>: Load all the subcells potentially involved in separation constraints or not
<IM_calculate__WithTraffic>: Whether traffic spreading is uniform or based on the maps used in the default traffic
capture (for interference matrices calculation)
<IM_calculate__BestServerZoneMargin>: Margin in case of Best signal level per HCS layer (for interference matrices
calculation)
<IM_calculate__ServiceZoneType>: All or Best signal level per HCS layer (for interference matrices calculation)
<IM_calculate__reliability_X_10000>: Cell edge coverage probability (for interference matrices calculation)
<TakeTfFromCapt>: Whether traffic loads are read from the default traffic capture or from the Subcells table
<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>
<allocType>315</allocType>
<freezeState>0</freezeState>
<numMinutes>1000</numMinutes>
<useDTX>0</useDTX>
156
AT310_AM_E2
<dtxVocalFactor>70</dtxVocalFactor>
<AfpBasedOnInterference>1</AfpBasedOnInterference>
<AfpBasedOnSeparations>1</AfpBasedOnSeparations>
<IM_calculate__WithTraffic>0</IM_calculate__WithTraffic>
<IM_calculate__BestServerZoneMargin>5</IM_calculate__BestServerZoneMargin>
<IM_calculate__ServiceZoneType>1</IM_calculate__ServiceZoneType>
<IM_calculate__reliability_X_10000>7500</IM_calculate__reliability_X_10000>
<TakeTfFromCapt>1</TakeTfFromCapt>
<preferedSenario></preferedSenario>
</AFP_options>
</Atoll>
Sample
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<SCP_options>
<MinEcI0>-1500.</MinEcI0>
157
<margin>500.</margin>
<reliability>5000.</reliability>
<DistanceMin>200000.</DistanceMin>
<Strategy0>1</Strategy0>
<Strategy1>1</Strategy1>
<Strategy2>1</Strategy2>
<Strategy3>1</Strategy3>
<Strategy>0</Strategy>
<FromScratch>1</FromScratch>
<UseCurrentNghbs>1</UseCurrentNghbs>
<NghbOrder>1</NghbOrder>
<ComputeNghbs>0</ComputeNghbs>
<UseMaxCodes>1</UseMaxCodes>
<UseShadowing>1</UseShadowing>
<SameCodeForCarriers>0</SameCodeForCarriers>
<NbClusterPerSite>3</NbClusterPerSite>
<ClustNghbs>0</ClustNghbs>
<Clust2ndNghbs>0</Clust2ndNghbs>
<NbCodesPerCluster>8</NbCodesPerCluster>
<UseDistance>1</UseDistance>
<UseExcepPairs>1</UseExcepPairs>
<minField>-10500</minField>
<usePmax>0</usePmax>
<PerCentMaxPower>5000</PerCentMaxPower>
<Max1stNghbCost>100</Max1stNghbCost>
<Max2ndNghbCost>50</Max2ndNghbCost>
<Max3rdNghbCost>5</Max3rdNghbCost>
<CoplanCost>100</CoplanCost>
<MaxCoClusterCost>50</MaxCoClusterCost>
<MaxDistCost>100</MaxDistCost>
<ExcepPairCost>100</ExcepPairCost>
<UseIndoor>0</UseIndoor>
<UseCloseNghbs>1</UseCloseNghbs>
<CloseDistance>80000.</CloseDistance>
<CloseImportance>3000.</CloseImportance>
<MaxCloseCost>100</MaxCloseCost>
</SCP_options>
</Atoll>
158
Forsk 2011
AT310_AM_E2
Sample
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<PNO_options>
<DistanceMin>200000.</DistanceMin>
<Strategy0>1</Strategy0>
<Strategy1>1</Strategy1>
<Strategy2>1</Strategy2>
<Strategy>2</Strategy>
<FromScratch>1</FromScratch>
<UseCurrentNghbs>1</UseCurrentNghbs>
<NghbOrder>1</NghbOrder>
<ComputeNghbs>1</ComputeNghbs>
<SameCodeForCarriers>0</SameCodeForCarriers>
<PilotIncr>4</PilotIncr>
<PNClusterSize>3</PNClusterSize>
<UseDistance>1</UseDistance>
<UseExcepPairs>1</UseExcepPairs>
<UseMaxCodes>1</UseMaxCodes>
<MinEcI0>-1600.</MinEcI0>
<TDrop>-1800.</TDrop>
<reliability>6000.</reliability>
<UseShadowing>0</UseShadowing>
<minField>-10500</minField>
<usePmax>0</usePmax>
<PerCentMaxPower>5000</PerCentMaxPower>
<Max1stNghbCost>100</Max1stNghbCost>
<Max2ndNghbCost>50</Max2ndNghbCost>
<Max3rdNghbCost>5</Max3rdNghbCost>
<CoplanCost>100</CoplanCost>
<MaxDistCost>100</MaxDistCost>
<ExcepPairCost>100</ExcepPairCost>
<UseIndoor>0</UseIndoor>
159
Forsk 2011
</PNO_options>
</Atoll>
Sample
160
AT310_AM_E2
<maxZoom>20000000</maxZoom>
<visible>Yes</visible>
</Display>
<AddToLegend>0</AddToLegend>
<QualityModel>6</QualityModel>
<QualityObjective0>3</QualityObjective0>
<QualityObjective1>4</QualityObjective1>
<QualityObjective2>2</QualityObjective2>
<QualityObjective3>1</QualityObjective3>
<AvailabilityObjective0>3</AvailabilityObjective0>
<AvailabilityObjective1>2</AvailabilityObjective1>
<AvailabilityObjective2>1</AvailabilityObjective2>
<RainModel>5</RainModel>
<RBER>1.e-012</RBER>
<ALFA1>10</ALFA1>
<ALFA2>1</ALFA2>
<RefDelayM>6.30000019</RefDelayM>
<refDelayNM>6.30000019</refDelayNM>
<EquipPercent>33.</EquipPercent>
<RainPercent>33.</RainPercent>
<kMoy>1.33</kMoy>
<kMin>0.88</kMin>
<UseAtpc>0</UseAtpc>
<P0Method>1</P0Method>
<IgnoreXPD>1</IgnoreXPD>
<IgnorePR>0</IgnorePR>
<WhichBER>5</WhichBER>
<BER1>1.e-003</BER1>
<BER2>1.e-006</BER2>
<Rec838>1</Rec838>
<UseK1Global>1</UseK1Global>
<UseK2Global>1</UseK2Global>
<CALC_LINK_PORTS>selected</CALC_LINK_PORTS>
<MultilineShared>0</MultilineShared>
<NoAcm>1</NoAcm>
<InterferenceDistanceMax>50000.</InterferenceDistanceMax>
<InterferenceDropMin>1.</InterferenceDropMin>
<InterferenceDropMinGlobal>3.</InterferenceDropMinGlobal>
<InterferenceCalcGo>1</InterferenceCalcGo>
<InterferenceCalcReturn>1</InterferenceCalcReturn>
<InterferenceCalcUplink>0</InterferenceCalcUplink>
<InterferenceCalcDownlink>0</InterferenceCalcDownlink>
<InterferenceRainSurfCorrelation>100.</InterferenceRainSurfCorrelation>
<InterferenceAutoWeight>0</InterferenceAutoWeight>
<InterferenceUseAtpc>0</InterferenceUseAtpc>
<InterferenceWidth>250</InterferenceWidth>
<InterferenceOverShoot>0</InterferenceOverShoot>
<CochannelOnly>0</CochannelOnly>
<IgnoreIntraLinkInterference>1</IgnoreIntraLinkInterference>
161
<Resolution>50</Resolution>
<INTERF_DETAIL>both</INTERF_DETAIL>
<ClutterCategory0>0</ClutterCategory0>
<ClutterDryCategory0>B</ClutterDryCategory0>
<ClutterCategory1>1</ClutterCategory1>
<ClutterDryCategory1>B</ClutterDryCategory1>
<ClutterCategory2>1</ClutterCategory2>
<ClutterDryCategory2>B</ClutterDryCategory2>
<ClutterCategory3>1</ClutterCategory3>
<ClutterDryCategory3>B</ClutterDryCategory3>
<ClutterCategory4>0</ClutterCategory4>
<ClutterDryCategory4>B</ClutterDryCategory4>
<ClutterCategory5>1</ClutterCategory5>
<ClutterDryCategory5>B</ClutterDryCategory5>
<ClutterCategory6>2</ClutterCategory6>
<ClutterDryCategory6>B</ClutterDryCategory6>
<ClutterCategory7>2</ClutterCategory7>
<ClutterDryCategory7>B</ClutterDryCategory7>
<ClutterCategory8>2</ClutterCategory8>
<ClutterDryCategory8>B</ClutterDryCategory8>
<ClutterCategory9>4</ClutterCategory9>
<ClutterDryCategory9>B</ClutterDryCategory9>
<ClutterCategory10>2</ClutterCategory10>
<ClutterDryCategory10>B</ClutterDryCategory10>
<ClutterCategory11>2</ClutterCategory11>
<ClutterDryCategory11>B</ClutterDryCategory11>
<ClutterCategory12>2</ClutterCategory12>
<ClutterDryCategory12>B</ClutterDryCategory12>
<ClutterCategory13>2</ClutterCategory13>
<ClutterDryCategory13>B</ClutterDryCategory13>
<ClutterCategory14>2</ClutterCategory14>
<ClutterDryCategory14>B</ClutterDryCategory14>
<ClutterCategory15>1</ClutterCategory15>
<ClutterDryCategory15>E</ClutterDryCategory15>
<ClutterCategory16>1</ClutterCategory16>
<ClutterDryCategory16>E</ClutterDryCategory16>
<ClutterCategory17>0</ClutterCategory17>
<ClutterDryCategory17>E</ClutterDryCategory17>
<ClutterCategory18>1</ClutterCategory18>
<ClutterDryCategory18>E</ClutterDryCategory18>
<ClutterCategory19>1</ClutterCategory19>
<ClutterDryCategory19>E</ClutterDryCategory19>
<ClutterCategory20>1</ClutterCategory20>
<ClutterDryCategory20>E</ClutterDryCategory20>
<ClutterCategory21>1</ClutterCategory21>
<ClutterDryCategory21>E</ClutterDryCategory21>
<ClutterCategory22>1</ClutterCategory22>
<ClutterDryCategory22>E</ClutterDryCategory22>
<ClutterCategory23>1</ClutterCategory23>
162
Forsk 2011
AT310_AM_E2
<ClutterDryCategory23>E</ClutterDryCategory23>
<ClutterCategory24>1</ClutterCategory24>
<ClutterDryCategory24>E</ClutterDryCategory24>
<ClutterCategory25>1</ClutterCategory25>
<ClutterDryCategory25>E</ClutterDryCategory25>
<ClutterCategory26>1</ClutterCategory26>
<ClutterDryCategory26>A</ClutterDryCategory26>
<ClutterCategory27>1</ClutterCategory27>
<ClutterDryCategory27>A</ClutterDryCategory27>
<ClutterCategory28>1</ClutterCategory28>
<ClutterDryCategory28>A</ClutterDryCategory28>
<ClutterCategory29>1</ClutterCategory29>
<ClutterDryCategory29>A</ClutterDryCategory29>
<ClutterCategory30>1</ClutterCategory30>
<ClutterDryCategory30>A</ClutterDryCategory30>
<ClutterCategory31>1</ClutterCategory31>
<ClutterDryCategory31>E</ClutterDryCategory31>
<ClutterCategory32>1</ClutterCategory32>
<ClutterDryCategory32>E</ClutterDryCategory32>
<ClutterCategory33>1</ClutterCategory33>
<ClutterDryCategory33>E</ClutterDryCategory33>
<ClutterCategory34>1</ClutterCategory34>
<ClutterDryCategory34>E</ClutterDryCategory34>
<ClutterCategory35>1</ClutterCategory35>
<ClutterDryCategory35>E</ClutterDryCategory35>
<ClutterCategory36>1</ClutterCategory36>
<ClutterDryCategory36>E</ClutterDryCategory36>
</Microwave>
</Atoll>
11.1.10 Macros
The following parameters are saved for macros:
Sample
<?xml version="1.0" encoding="UTF-8"?>
<Atoll>
<Macros>
<File>
<Path>C:\TestsAddin\testEvents.vbs</Path>
<Language>VBScript</Language>
<Timeout>3600</Timeout>
</File>
</Macros>
</Atoll>
163
Forsk 2011
Sample
<?xml version="1.0" encoding="UTF-8"?>
<PrintConfiguration version="1">
<Page>
<Paper size="" orientation="1"/>
<Margins right="2000" left="2000" bottom="2000" top="2000"/>
<Scale fitToPage="1">12 495</Scale>
</Page>
<Map insideFZonly="1" rulers="1"/>
<Legend>
<LegendPos enable="0" majorPos="3" minorPos="0" insideMap="0"/>
</Legend>
<Comments>
<Position vPos="1" enable="0" hPos="1" insideMap="0"/>
<text></text>
<font height="14" weight="400" charset="1" face="MS Shell Dlg" italic="0"/>
</Comments>
<Logo>
<Position vPos="0" enable="1" hPos="0" insideMap="0"/>
<bitmap></bitmap>
<Dimensions width="46" height="18"/>
</Logo>
<Title>
<Position vPos="0" enable="0" hPos="1" insideMap="0"/>
164
AT310_AM_E2
<text></text>
<font height="14" weight="400" charset="1" face="MS Shell Dlg" italic="0"/>
</Title>
<LogoBottom>
<Position vPos="1" enable="0" hPos="0" insideMap="0"/>
<bitmap></bitmap>
<Dimensions width="46" height="18"/>
</LogoBottom>
<Footer>
<Position vPos="1" enable="0" hPos="1" insideMap="0"/>
<text></text>
<font height="14" weight="400" charset="1" face="MS Shell Dlg" italic="0"/>
</Footer>
</PrintConfiguration>
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>
165
Forsk 2011
</Field>
<Field>
<Title>% of Covered Area</Title>
</Field>
...
</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
166
Type
Index
Text
Integer
Real
Date
<Ignore>
AT310_AM_E2
Col5=0
...
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
167
Forsk 2011
Col4=4
...
168
AT310_AM_E2
12 Initialisation Files
Initialisation files can be used to store operational and working environment settings. These files are optional, not required
for working with Atoll, but are useful means for selecting required calculation methods and other settings.
This chapter describes the formats of these files in detail:
You can open the Atoll.ini file in the Atoll installation folder for editing by pressing
CTRL+SHIFT+i. If no Atoll.ini file exists, a blank Atoll.ini file is created.
You have to restart Atoll in order to take into account any modifications in the
Atoll.ini file.
169
Forsk 2011
Prefix = "newprefix"
Each new transmitter will be named newprefixN instead of Sitename_X (Sitename is the name of the site where the
transmitter is located and X is the transmitter sector number on this site). Not adding the above lines, or setting the prefix to
<Auto> (Prefix = "<AUTO>"), will instruct Atoll to keep the conventional naming method, i.e., each transmitter will be named
Sitename_X.
Furthermore, it is also possible to remove the underscore character "_" from the transmitters name, i.e., the transmitter can
be named SitenameX instead of Sitename_X. To do this, add the following line in the [Transmitter] section of the Atoll.ini file:
Underscore = 0 or 1
Setting this value to 0 means the underscore character will not be used when naming transmitters. The default value is 1. You
can also define whether the suffix X in the transmitters name should be a number or a letter. The following two lines define
this option in the Atoll.ini file:
SuffixIsNum = 0 or 1
FirstCharSuffix = "A"
When SuffixIsNum = 1, the default, the suffix X in the transmitter name Sitename_X will be a number. When it is set to 0, this
suffix will be a letter. The starting suffix in this case will be A by default but can be changed to any other character through
the second line.
If you are using number suffixes, you can also initialise the number suffix at any other number than 1. To do this, you can add
the following lines under the [Transmitter] section of the Atoll.ini file:
First = X
Where, X is a number.
170
AT310_AM_E2
You can also start Atoll, specifying a log file, by starting it with "Atoll.exe -log LogFile.log", either from the command line, or
by modifying the shortcut parameters. If you have a log file defined in the Atoll.ini file, and run Atoll with the -log option in
the command line, the command line log file will have priority over the one mentioned in the Atoll.ini file.
The option available in Atoll.ini is more suitable for running Atoll using macros. Apart from these options, you also have the
possibility to save the messages in the Event Viewer to a log file during an Atoll session (through the Event Viewer context
menu).
12.1.1.7 Restricting the List of Predictions for Creating Sector Traffic Maps
When you create a sector traffic map, i.e., traffic map based on cell coverage areas, Atoll uses an existing best server coverage
prediction in order to be able to distribute the live traffic data geographically. Atoll lets you select the best server coverage
prediction on which the traffic map will be based. In the list of available best server coverage predictions, Atoll lists all the best
server coverage prediction available in the Predictions folder, whether they were created using a margin or without.
If you want Atoll to list only the best server coverage predictions that were created without a margin, i.e., with 0 dB margin,
you can add the following lines to the Atoll.ini file:
[Studies]
SelectNullMarginOnly = 1
SelectNullMarginOnly is set to 0 by default, which means that Atoll lists all the best server coverage predictions available.
171
Forsk 2011
172
AT310_AM_E2
Enabling this option influences the export feature for all exportable vector fomats (MIF,
TAB, AGD, SHP, TXT). When this option is enabled, only the largest polygon is exported
for coverage layers having more than one polygon.
You can enable this feature by adding the following lines in the Atoll.ini file:
[Studies]
EnableLBS = 1
Setting EnableLBS to 1 adds a new coverage prediction export format "LBS Polygon Files (*.txt)" to Atoll. The polygons are
exported in a comma separated values format.
173
Forsk 2011
12.1.1.14 Setting the Precision for the Antenna Pattern Verification at Import
Atoll checks whether the vertical and horizontal patterns are correctly aligned at the extremities. The antenna patterns are
correctly aligned when:
the horizontal pattern attenuation at 0 is the same as the vertical pattern attenuation at the pattern electrical tilt
angle, and
the horizontal pattern attenuation at 180 is the same as the vertical pattern attenuation at the 180 less the pattern
electrical tilt angle.
By default, the option is inactive, i.e., the pattern attenuations are considered the same if they differ less than 100 dB. If you
want to change this default precision, add the following lines in the Atoll.ini file:
[Antenna]
PrecisionTimes10 = X
Where X is the required precision in dB multiplied by 10. For example, if you want to set the precision to 0.5 dB, X will be
0.5 10 = 5 .
174
AT310_AM_E2
12.1.1.23 Exporting BMP, TIF, and PNG Files with a TAB Reference File
When exporting BMP, TIF, and PNG files, Atoll can export the georeference information in a TAB file instead of the default
respective World files (BPW or BMW for BMP, TFW for TIF, and PGW for PNG). If you want Atoll to export the georeference
information in a TAB file when you export in BMP, TIF, and PNG formats, add the following lines in the Atoll.ini file:
[RasterExport]
GeorefWithTAB = 1
GeorefWithTAB is set to 0 by default.
175
Forsk 2011
12.1.1.26 Adding the Duplicate Site to the Original Sites Site List
When you duplicate a site, you can choose to add the duplicate site to the site list (if any) of the original site by adding the
following lines in the Atoll.ini file:
[Site]
AddToSiteListOnDuplicate = 1
AddToSiteListOnDuplicate is set to 0 by default.
176
AT310_AM_E2
Atoll deletes any corresponding invalid private path loss matrices and uses the valid shared ones for calculations if
Atoll.ini contains the following lines:
[Pathlosses]
FullResyncPrivShared = 0
Atoll deletes any corresponding valid and invalid private path loss matrices and uses the valid shared ones for
calculations if Atoll.ini contains the following lines:
[Pathlosses]
FullResyncPrivShared = 1
If you have private path loss matrices tuned using measurement data, setting FullResyncPrivShared to 1 will make
Atoll automatically delete them when calculations are run. You should set FullResyncPrivShared to 0 when working
with tuned private path loss matrices.
FullResyncPrivShared is set to 1 by default.
12.1.1.32 Filtering Predictions by Technology When Reading the XML Studies File
In the XML studies file, some common CDMA coverage predictions may be available for both CDMA2000 and UMTS, or some
common OFDMA coverage predictions may be available for both WiMAX and LTE. If you wish to filter the customized
predictions stored in the XML studies file by their technology, e.g., separate the WiMAX and LTE coverage predictions, and
only load the predictions specific to the technology of the current active Atoll document, add the following lines in the Atoll.ini
file:
[Studies]
CustomStudiesFilteredByTechno = 1
CustomStudiesFilteredByTechno is set to 0 by default. This option is only relevant for reading the XML studies file. Atoll always
writes the technology type in the XML studies file when customized coverage predictions are saved in it.
177
Forsk 2011
If you set ReportResolution to a very precise (low) value, the performance (calculation
speed) can be considerably decreased depending on the size of the population maps in
the document. It is recommended to set this parameter to an optimum value, i.e., just
precise enough to get the required accuracy.
= 1
ExportOnlyVisibleLevels is set to 0 by default, which means that when any coverage prediction is exported, Atoll exports all
its levels, visible or not.
Atoll exports only visible coverage predictions. If a coverage prediction consists of only
one level, the visibility check box of that level also controls the visibility check box of the
prediction itself. This means that if the visibility check box of the only level of such a
prediction is cleared, the prediction will itself be hidden and will not be exported.
178
AT310_AM_E2
179
Forsk 2011
[StatusBar]
DisplayZ = 0
DisplayClutterClass = 0
DisplayClutterHeight = 0
DisplayZ, DisplayClutterClass and DisplayClutterHeight respectively refer to the display of altitude, clutter class, and clutter
height.
12.1.2.8 Setting the Maximum Number of Lines in Coverage Prediction Tool Tips
If you have more than one coverage prediction displayed on the map, the tool tips display the tip text for all the coverage
predictions available at a pixel up to 30 lines by default. You can change this default number of tool tip text lines through the
following option in the Atoll.ini file:
[Studies]
MultiplePlotsTipTextLines = X
X is the number of lines to display in the tool tips. By default, MultiplePlotsTipTextLines is set to 30. If you set it to a very large
value, however, the tool tip might not display correctly.
DrawSingleElementPattern is set to 0 by default, in which case the displayed diagram is S R Avg S . When you set
H
180
AT310_AM_E2
Where X is the number of digits that the CELL_IDENTITY field should contain. For example, CellIDNbDigits = 5 means that Atoll
will display at least five digits in the CELL_IDENTITY field by adding leading zeros where required. This means that Atoll will
display "00678" in the above example. However, if the CELL_IDENTITY field contains a number that has more than X digits, all
the digits will still be displayed. For example, all seven digits in "9376562" will still be displayed even if CellIDNbDigits is set to
5.
This option works for both, application and service, modes of the distributed calculation server.
181
Forsk 2011
[RemoteCalculation]
DetectTimeOut = 5000
In this example, the detection time-out is set to 5000 ms.
Add
GSM = 0
UMTS HSPA
UMTS = 0
CDMA2000
CDMA = 0
TD-SCDMA
TD-SCDMA = 0
WiMAX 802.16e
WiMAX = 0
LTE
LTE = 0
MW = 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.
182
AT310_AM_E2
ACP_GSM = 0
ACP_UMTS = 0
ACP_WiMAX = 0
ACP_LTE = 0
GSM_AFP = 0
WiMAX_AFP = 0
LTE_AFP = 0
In order to carry out a combined GSM and UMTS optimisation using the ACP module, you must have access to both ACP
module licences, i.e., ACP_GSM and ACP_UMTS both must not be set to 0.
183
Forsk 2011
12.1.6.5 Setting the Sign for KClutter When Importing Data From Planet EV
Planet EV uses the opposite sign for the Kclutter parameter with respect to Planet DMS. If you are importing data from Planet
EV, you might have to change the sign of this parameter. You can instruct Atoll to change the sign for Kclutter when importing
data from Planet EV by adding the following lines to the Atoll.ini file:
[PlanetImport]
ChangeKclutterSign = 1
ChangeKclutterSign is set to 0 by default.
184
AT310_AM_E2
Username and password are stored in the ATL file in an encrypted form.
This option is only appropriate if the database connection string contains a password.
185
Forsk 2011
[Studies]
AutoLock = 0
This setting is read by Atoll without Atoll having to be restarted.
12.1.7.4 Setting a Default Value for the Cell Edge Coverage Probability
The default value of the cell edge coverage probability can be configured in the Atoll.ini file. If you enter the following lines in
the Atoll.ini file, Atoll will consider the value of the cell edge coverage probability defined in the Atoll.ini file as the default
value, and will take it into account when performing point analysis, in the shadowing margins calculator, and will propose it
as the default value for coverage prediction studies.
[Shadowing]
Reliability = 60
Reliability = 60 means 60 % cell edge coverage probability.
The value of cell edge coverage probability used for automatic neighbour allocation and
interference matrices calculation is stored in user configuration files (CFG).
12.1.7.6 Modifying the Resolution for the LOS Area Calculation Around a Site
The calculation of line of sight area around a given site uses the resolution of the geographic data as the default calculation
resolution. These calculations can be time-consuming if the geographic data is available with a very high resolution. You can
set the calculation resolution to a multiple of the resolution of the geographic data by adding the following lines in the Atoll.ini
file:
186
AT310_AM_E2
[LOSArea]
ResolutionMultFactor = X
Where X is an integer. Therefore, setting ResolutionMultFactor to 2 will double the calculation resolution and decrease the
time required for the calculation by half.
Use this option only if you are critically short of hard disk space. However, note that disabling temporary local copies might
decrease the performance as it adds file access delays over the network.
12.1.7.10 Warning About Prediction Vailidity When Display Options are Modified
Coverage predictions have to be recalculated if you modify their display options. Atoll displays a warning message when you
modify the display options for coverage predictions. To deactivate this warning message, add the following lines in the Atoll.ini
file:
[Studies]
RecomputationWarning = 0
RecomputationWarning is set to 1 by default.
187
Forsk 2011
[Calculations]
UseSiteAltitude = 0
UseSiteAltitude is set to 1 by default, which means that the altitude used in calculations will be the one which is either read
from the Sites table or from the DTM at the sites coordinates, if the user-defined altitude is not available in the Sites table.
Setting UseSiteAltitude to 0 means that, during calculations, Atoll will read the altitudes from the DTM at the exact
coordinates of each transmitter considering the values entered for the DX and DY parameters.
The above option is also valid for microwave links. In this case, setting UseSiteAltitude to 0 means that, during calculations,
Atoll will read the altitudes from the DTM at the exact coordinates of each microwave link considering the values entered for
the DX_A, DY_A, DX_B, and DY_B parameters.
With UseSiteAltitude = 0, if DX and DY are 0, i.e., for transmitters and microwave links
located at the site coordinates, Atoll will still use the altitudes defined per site, if any, or
the altitudes from the DTM otherwise
188
AT310_AM_E2
NumberOfProcessors is the maximum number of processors that can be used for calculations. If you set this option to
0, Atoll will use actual number of available processors.
NumberOfThreadsPathloss is the maximum number of threads that can be used for path loss calculations (4 by
default, 8 maximum)
NumberOfThreadsSimulation is the maximum number of threads that can be used for Monte Carlo simulation
calculations (4 by default, 8 maximum)
NumberOfThreadsStudy is the maximum number of threads that can be used for the calculation of coverage
predictions (4 by default, 8 maximum)
NumberOfThreadsStudyTile is the maximum number of threads that can be used per coverage prediction calculation
(0 by default, 8 maximum). If you set this option to 0, Atoll will use actual number of available threads.
NumberOfThreadsNeighbour is the maximum number of threads that can be used for automatic neighbour allocation
(4 by default, 8 maximum)
NumberOfThreadsMicrowave is the maximum number of threads that can be used for microwave link calculations (4
by default, 8 maximum)
All these options are upper limits per computer. Atoll supports a maximum of 64 parallel threads.
The parallel calculation of Monte Carlo simulations in TD-SCDMA, WiMAX 802.16d, WiMAX 802.16e, and LTE documents is
disabled by default. It shoud not be enabled in TD-SCDMA documents.
189
Forsk 2011
In order to make this coverage prediction available in Atoll, add the following lines in the Atoll.ini file:
[Studies]
AerialStudy = 1
12.1.7.20 Estimating Required and Used Memory Size for UMTS Simulations
Atoll can estimate the required and used memory sizes for UMTS simulations and display the estimates in the Source Traffic
tab of the new simulation group dialogue. Estimated memory size within the green region means low consumption, within
the yellow region means medium consumption, within the orange region means high consumption, and within the red region
means very high consumption, in which case the simulations might generate an out of memory error and not complete.
To activate the memory estimation feature, add the following lines in the Atoll.ini file:
[CDMA]
PredictSimuMemorySize = 1
PredictSimuMemorySize is set to 0 by default which means the feature is not active.
12.1.7.21 Disabling Calculations Over NoData Values for DTM and Clutter Classes
If you dont want Atoll to calculate path losses on the pixels located over nodata values defined in the DTM and clutter classes
files, add the following lines in the Atoll.ini file:
[FskPropagModels]
OptimOnNoData = 1
By default, OptimOnNoData is set to 0. This option only works with the propagation models available with Atoll by default.
190
AT310_AM_E2
If you set LinkedPredictionsComputationMode to any other value, the calculations are performed in parallel but without being
managed by a task list.
Calculations are carried out starting with the current document in the order of the coverage predictions in the Predictions
folder.
191
Forsk 2011
Worst Case Method: For each interference matrix relationship, the worst case value in all the active interference
matrices is taken into consideration.
First Value Method: For each interference matrix relationship, the first value found in any active interference matrix
is taken into consideration. The order in which the interference matrices are scanned to find the first value is the order
of the interference matrices in the Interference Matrices folder in the Explorer window, i.e. the first IM is the one at
the top.
The First Value method was the default method in earlier versions of Atoll which allowed multiple interference matrix import.
192
AT310_AM_E2
[Studies]
RemoveBadMultiCells = 0
RemoveBadMultiCells is set to 1 by default.
If you are not working with multi-band transmitters, i.e., MultiBandManagement is set to 0, Atoll does not automatically
delete such records. If you want Atoll to automatically delete such records when opening the document from a database, you
have to sett the following option in the Atoll.ini file:
[Studies]
CleanMultiCellManagement = 1
CleanMultiCellManagement is set to 0 by default.
12.1.8.7 Setting the Best Server Calculation Method in Same Priority HCS Layers
Atoll can calculate serving transmitters according to HCS layer priorities in coverage predictions. The signal level received from
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.
HCS
1st strategy: The serving transmitter is the one for which the difference between the received signal level and T Rec
HCS
is the highest. Where, T 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 in the Atoll.ini file:
[Studies]
UseThresholdForSameLayerPriorities = 0
UseThresholdForSameLayerPriorities is set to 1 by default.
193
Forsk 2011
12.1.8.15 Extending the Allowed Value Range for C/I and Reception Thresholds
Currently the subcell C/I threshold allows values from 0 to 24 dB and the rception threshold allows values from -116 to 50 dBm. If you wish to extend this range to 30 dB and -134 dBm for the C/I and reception thresholds respectively, add the
following lines in the Atoll.ini file:
[GSM]
WideRangeSubcellThresholds = 1
WideRangeSubcellThresholds is set to 0 by default, which corresponds to the default value ranges.
194
AT310_AM_E2
This is set to 0 by default, which means that cell names will follow the normal convention of Atoll, SiteN_X(C). If there is only
one carrier, meaning that C is unique, then this option can be set to 1. This will result in cell names which will be same as the
transmitter names, SiteN_X.
Not display the number of simultaneous HSDPA users in the simulation results.
Display the peak gross and peak application level throughputs per mobile and per cell in the simulation results.
Display the MUG table in the cell properties. Input from this are used to calculate the peak gross throughput per cell
when the scheduling algorithm is "Proportional Fair".
Display the average HSDPA throughput per user in the Cells tab of the simulation results.
HSDPA resource scheduling will not be carried out. The HSDPA throughput for each user will be calculated by taking into
account the MUG corresponding to the current number of connected HSDPA users.
In Average Simulation results, the average HSDPA throughput per user can be calculated excluding the simulations where no
HSDPA users were served. To do this, enter the following lines in the Atoll.ini file:
[CDMA]
HSDPAAvgSimuResults = 1
HSDPAAvgSimuResults = 0 by default.
195
Forsk 2011
If you set CQIDeltaWithPower to 1, the HS-PDSCH CQI will be calculated using the formula:
( CQI ) HS PDSCH = ( CQI ) pilot P pilot + P HS PDSCH
The above equations are in dB. Refer to the Technical Reference Guide for more details.
196
AT310_AM_E2
Where X is the number of times an HSDPA mobile should be rejected to be considered permanently rejected for the
simulation.
Improve = 1 (by default) means that Atoll will use the accurate rasterization method for small polygons. Improve = 0
means that the normal rasterization method will be used for all polygons. Setting this option to 1 implies that this
algorithm will not be used globally for all polygons, but only for small polygons which are defined by the options
SurfRatio or MaximumSurf.
Precision = 1 (by default) means that the rasterization resolution (step) used by the algorithm for small polygons is 1
metre. You can set it to a higher value if you observe performance degradation. The step of rasterization means the
size of the bin used to approximate the vector shape with bins.
197
Forsk 2011
SurfRatio = 20 (by default) means that the accurate algorithm will be used only for polygons whose size is smaller than
20 times the size of the normal raster bin. The normal raster bin size in an Atoll document is the finest resolution
among the geographic data available in the document.
If your Atoll document contains two geographic data files, one with a 20 m resolution and
the other with a 5 m resolution, and you remove the 5 m one from your document, Atoll
will still keep 5 m as the normal raster bin size.
MaximumSurf = 2500 (by default) means that a polygon will be considered small only if its surface area is less than or
equal to 2500 sq. m.
So, a polygon will be considered small, and will be rasterized using the accurate algorithm, if either the ratio of its surface area
to the surface area of the normal raster bin is equal to or less than SurfRatio, or if its surface area is less than MaximumSurf.
If you want to use just the MaximumSurf option, you can set the SurfRatio to 0.
198
AT310_AM_E2
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
199
Forsk 2011
[Studies]
SCActivesetMaxSize = X
Where X is the maximum number of transmitters in the active set. If you set SCActivesetMaxSize = 10, you will get the same
results in the coverage prediction as the SC Interference tab in the point analysis.
12.1.9.22 Setting the Maximum UL Reuse Factor for HSUPA Users Noise Rise
Estimation
In UMTS HSPA simulations, Atoll assumes a constant uplink reuse factor for estimating the maximum available noise rise per
HSUPA user. This may cause unnecessary rejection of some HSUPA users in very low traffic cases. You can set an upper limit
for the uplink reuse factor by adding the following lines in the Atoll.ini file:
[UMTSSimus]
MaxReuseFactor = X
MaxReuseFactor is set to 5 by default.
802.16d:
Under Channel Configuration in the Global Parameters tab of the Transmitters folders properties dialogue:
Number of Subchannels per Channel and Number of Subcarriers per Channel, i.e. Total, Used, and Data.
802.16e:
In the Permutation Zones table, the first DL PUSC permutation zone cannot be deactivated.
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 Frame Configurations table and in the General tab of the properties dialogue of the frame configurations:
Number of Preamble Subcarriers.
In the Frame Configurations table, the Total Number of Subcarriers changes into a combo box with the following
five values: 128, 256, 512, 1024, 2048.
12.1.10.2 Using Only Bearers Common Between the Terminals and Cells
Equipment
If you want Atoll to perform an intersection over the bearers supported by the cell equipment and by the terminal equipment,
add the following lines in the Atoll.ini file:
[OFDM]
200
AT310_AM_E2
UseCommonBearersOnly = 1
UseCommonBearersOnly is set to 0 by default. When UseCommonBearersOnly is set to 1, Atoll only uses the bearers for
which selection thresholds are defined in both the terminals and the cells equipment for both downlink and uplink bearer
selection.
DisplaySignalsPerSCInPtA is set to 0 by default. When the DisplaySignalsPerSCInPtA option is set to "0" or is absent, SS & PBCH
per subcarrier and PDCCH & PDSCH per subcarrier are not available options in a point analysis.
201
Forsk 2011
202
AT310_AM_E2
Basic_LTE_AFP = 1
203
Forsk 2011
ShieldingFactorOnWantedSignal = 0
ShieldingFactorOnWantedSignal is set to 1 by default, which means that the sheilding factor is taken into account at the
receiver when calculating interference. On the transmitter side, the sheilding factor is always taken into account when
calculating interference.
You have to add the following lines in the Atoll.ini file to display this information:
[TestMobileData]
ShowCoupleInfo = 1
Setting ShowCoupleInfo to 0 hides this information.
12.1.12.2 Setting the Number of Transmitters per Drive Test Data Path
By default, Atoll can import information about one serving transmitter (or cell in CDMA documents) and six neighbour
transmitters (or cells in CDMA documents) for drive test data paths. You can change the number of transmitters per drive test
data path by adding the following lines in the Atoll.ini file:
[TestMobileData]
NumberOfTestMobileTransmitters = X
Where X is the number of transmitters per drive test data path. The default value of NumberOfTestMobileTransmitters is 7.
204
AT310_AM_E2
[TestMobileData]
RecalcDist = 1 or 0
The default value of RecalcDist is 1, which means that Atoll will calculate the distance for each measurement point. The
nearest serving cell is the one closest to the measurement point which has the same (Scrambling Code, SC Group), (BSIC,
BCCH), or (PN Offset, PN Offset Group) pair as the point.
12.1.12.4 Defining the BCCH and BSIC Columns for FMT Import
The .fmt files generated by the TEMS Investigation GSM tool contain a number of columns. To define which of these columns
should be imported as the BCCH column and which one as the BSIC column in Atoll, you can add the following lines in the
Atoll.ini file:
[TestMobileDataImportFmt]
BCCHColumn = Column1
BSICColumn = Column2
Where, Column1 and Column2 are the titles of the two columns in the .fmt file corresponding to the BCCH and the BSIC
columns respectively.
In order for the ACP initialisation file to be used by Atoll, you should place the acp.ini file in the Atoll installation directory.
You can define a different location for the acp.ini file by setting the following option in the atoll.ini file:
[ACP]
iniFile = /path/to/the/ACP.ini
The following sections describe the options available in the acp.ini file.
205
Forsk 2011
The local settings, defined using the ACP - Automatic Cell Planning Properties
dialogue, take precedence over the same settings defined in the global acp.ini
file. The settings in the acp.ini file are read when you start a new project to
initialise the settings of the ACP.
When using the acp.ini file to define options, instead of using the ACP Automatic Cell Planning Properties dialogue, you can also define any other
settings even if they can not be set using the ACP - Automatic Cell Planning
Properties dialogue. These settings redefined locally have precedence over the
global settings.
206
AT310_AM_E2
zone.1.name=MyVectorZone2 # The name of the zone (in this case from SHP)
zone.1.file=c:\path\to\file.shp # Absolute path to the SHP file.
207
Forsk 2011
param.lte.overlap.minRxLevel=-105
param.lte.coverage.autoPrediction=yes
param.lte.coverage.isShadowing=no
param.lte.coverage.cellEdgeCov=0.75
param.lte.cinr.autoPrediction=yes
param.lte.cnir.isShadowing=no
param.lte.cnir.cellEdgeCov=0.75
param.lte.cnir.useFreqBand=1
param.lte.cnir.useSegmentation=1
The following options are used to define the default threshold for each objective rule:
quality.gsm.bcch.threshold=-85
quality.gsm.overlap.threshold=4
quality.umts.rscp.threshold=-85
quality.umts.ecio.threshold=-13
quality.umts.overlap.threshold=4
quality.cdma.rscp.threshold=-85
quality.cdma.ecio.threshold=-13
quality.cdma.overlap.threshold=4
quality.wimax.coverage.threshold=-85
quality.wimax.c.threshold=-85
quality.wimax.cn.threshold=20
quality.wimax.cinr.threshold=10
quality.wimax.overlap.threshold=5
quality.lte.coverage.threshold=-85
quality.lte.c.threshold=-85
quality.lte.cn.threshold=20
quality.lte.rsrp.threshold=-105
quality.lte.cinr.threshold=10
quality.lte.rsrq.threshold=-12
quality.lte.overlap.threshold=5
The following options are used to define the default objectives proposed by the ACP. All objectives defined with the option
"auto=yes" are automatically created during a new setup. Others are available on the context menu used for creating new
objectives.
For the setting "objective.X.conditions.X.operande," a value of "0" means "<" (less than)
and "1" means ">" (greater than).
objective.0.target.isAbsoluteCoverage=yes
208
AT310_AM_E2
objective.0.target.absoluteCoverage=90
objective.0.filter.count=0
;; The following objective should be defined separately for each layer
objective.1.name=GSM Cell Dominance # Name of objective "1" defined.
objective.1.conditions.operande=AND
objective.1.conditions.count=2
objective.1.conditions.0.layer=gsm
objective.1.conditions.0.quality=overlap
objective.1.conditions.0.operande=1 # "1" means ">" (greater than).
objective.1.conditions.0.threshold=0
objective.1.conditions.1.layer=gsm
objective.1.conditions.1.quality=overlap
objective.1.conditions.1.operande=0 # "0" means "<" (less than)
objective.1.conditions.1.threshold=4
objective.1.target.isAbsoluteCoverage=yes
objective.1.target.absoluteCoverage=100
objective.2.name=UMTS RSCP Coverage # Name of objective "2" defined.
objective.2.conditions.count=1
objective.2.conditions.0.layer=umts
objective.2.conditions.0.quality=rscp
objective.2.conditions.0.threshold=-85
objective.2.conditions.operande=OR
objective.3.name=UMTS EcIo # Name of objective "3" defined.
objective.3.conditions.count=1
objective.3.conditions.0.layer=umts
objective.3.conditions.0.quality=ecio
objective.3.conditions.0.threshold=-13
objective.3.conditions.operande=OR
objective.3.target.isAbsoluteCoverage=yes
objective.3.target.absoluteCoverage=100
objective.4.name=UMTS Pilot Pollution # Name of objective "4" defined.
objective.4.auto=false
objective.4.conditions.count=1
objective.4.conditions.0.layer=umts
objective.4.conditions.0.quality=overlap
objective.4.conditions.0.operande=0 # "0" means "<" (less than)
objective.4.conditions.0.threshold=4
objective.4.conditions.operande=AND
objective.4.target.isAbsoluteCoverage=yes
objective.4.target.absoluteCoverage=100
objective.5.name=UMTS Soft Handover # Name of objective "5" defined.
objective.5.auto=false
objective.5.conditions.count=2
objective.5.conditions.0.layer=umts
objective.5.conditions.0.quality=overlap
209
210
Forsk 2011
AT310_AM_E2
objective.10.conditions.0.threshold=-85
objective.10.conditions.operande=OR
objective.11.name=CDMA EcIo # Name of objective "11" defined.
objective.11.conditions.count=1
objective.11.conditions.0.layer=cdma
objective.11.conditions.0.quality=ecio
objective.11.conditions.0.threshold=-13
objective.11.conditions.operande=OR
objective.11.target.isAbsoluteCoverage=yes
objective.11.target.absoluteCoverage=100
objective.12.name=CDMA Pilot Pollution # Name of objective "12" defined.
objective.12.auto=false
objective.12.conditions.count=1
objective.12.conditions.0.layer=cdma
objective.12.conditions.0.quality=overlap
objective.12.conditions.0.operande=0 # "0" means "<" (less than)
objective.12.conditions.0.threshold=4
objective.12.conditions.0.threshold=4
objective.12.conditions.operande=AND
objective.12.target.isAbsoluteCoverage=yes
objective.12.target.absoluteCoverage=100
objective.13.name=CDMA Soft Handover # Name of objective "13" defined.
objective.13.auto=false
objective.13.conditions.count=2
objective.13.conditions.0.layer=cdma
objective.13.conditions.0.quality=overlap
objective.13.conditions.0.operande=1 # "0" means "<" (less than)
objective.13.conditions.0.threshold=1
objective.13.conditions.1.layer=cdma
objective.13.conditions.1.quality=overlap
objective.13.conditions.1.operande=0 # "0" means "<" (less than
objective.13.conditions.1.threshold=4
objective.13.conditions.operande=AND
objective.13.filters.count=1
objective.13.filters.0.layer=cdma
objective.13.filters.0.quality=coverage
objective.13.filters.0.operande=0
objective.13.filters.0.threshold=-95
211
Forsk 2011
[ACPTplReconfPage]
umts.disablePilotPowerOptimisation=1
umts.disableMaxPowerOptimisation=1
umts.SyncMultiCellPower=1
umts.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm
# around actual value. If 0, use fixed value 37-46
cdma.1xrtt.SyncMultiCellPower=1
cdma.1xevdo.SyncMultiCellPower=1
cdma.1xrtt.disablePilotPowerOptimisation=1
cdma.1xrtt.disableMaxPowerOptimisation=1
cdma.1xevdo.disableMaxPowerOptimisation=1
cdma.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm
# around actual value. If 0, use fixed value 37-46
gsm.disablePowerOptimisation=1
gsm.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm
# around actual value. If 0, use fixed value 37-46
wimax.disablePreamblePowerOptimisation=1
wimax.SyncMultiCellPower=1
wimax.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm
# around actual value. If 0, use fixed value 37-46
lte.disablePowerOptimisation=1
lte.SyncMultiCellPower=1
lte.defaultPowerAutoMinMax=3 # automatically set min/max power at an offset of 3dBm
# around actual value. If 0, use fixed value 37-46
The following options are used to define the default reconfiguration that will be done on transmitters and sites:
disableAntennaOptimization=1
disableETiltOptimization=1
disableAzimuthOptimization=1
disableMechTiltOptimization=1
disableSiteSelection=1
The following options are used to specify default values for the reconfiguration ranges:
defaultTxAzimuthVariation=20
defaultTxAzimuthStep=5
defaultTxAzimuthMinInterSector=0
defaultTxTiltMin=0
defaultTxTiltMax=5
defaultTxTiltStep=1
defaultTxETiltMin=0
defaultTxETiltMax=10
defaultTxHeightMin=0
defaultTxHeightMax=10
defaultTxHeightStep=5
defaultTxHeightMin.feet=0
defaultTxHeightMax.feet=30
defaultTxHeightStep.feet=15
212
AT310_AM_E2
umts.disablePilotPowerOptimization=0
umts.disableMaxPowerOptimization=0
213
Forsk 2011
eclass.0.linearBuildingStart=0
eclass.0.editionFlag=0
The following options enable you to map clutter classes to propagation classes. Each mapping is defined on two lines: the first
line defines the clutter class (by its code from the Description tab of the Clutter Classes Properties dialogue); the second line
defines the propagation class (by its ID under Propagation on the Optimisation tab of the ACP Setup dialogue). The default
propagation classes in the ACP are "Open" (ID "0"), "Vegetation" (ID "1"), and "Building" (ID "2"). Any additional propagation
classes will have an ID assigned when they are created.
clutterMapping.count=3
clutterMapping.0.clutterCode=10
clutterMapping.0.classCode=0
clutterMapping.1.clutterCode=4
clutterMapping.1.classCode=1
clutterMapping.2.clutterCode=6
clutterMapping.2.classCode=2
clutterMapping.3.clutterCode=7
clutterMapping.3.classCode=2
The following options define the default threshold and weight for the EMF exposure objective:
[ACPEMFage]
isPropClassesExtendable=1 # "1" enables user to create propagation classes.
12.2.2.7 Defining the Functionality of the ACP - Automatic Cell Planning Properties
Dialogue
You can set options in the ACP.ini file to define the functionality of the ACP - Automatic Cell Planning Properties dialogue.
12.2.2.7.1
214
AT310_AM_E2
implements the appropriate methods of Atolls API). Delegating calculation to the propagation model provides more accurate
tx.etilt.optimize=acp_etilt_use
results but might take longer. Additionally, it will use disk space to store the calculation results.
tx.etilt.min=acp_etilt_min
[ACPAntMaskModelPage]
tx.etilt.max=acp_etilt_max
advancedUI=1 # The default is "0"; the "Delegate Calculation to Model"
tx.tilt.optimize=acp_tilt_use
# feature is disabled.
tx.tilt.min=acp_tilt_min
tx.tilt.max=acp_tilt_max
The following option can be used to allow "Optimised" propagation models (i.e., propagation models that use the "Optimised"
mode) to use "Full Path Loss" mode:
tx.tilt.step=acp_tilt_step
tx.azimuth.optimize=acp_azim_use
nativeAllowFullPathLoss=1 # The# default
relativeisvalues
"0"; the
fromfeature
currentisazimuth
disabled.
tx.azimuth.deltamin=acp_azim_deltamin
12.2.2.8 tx.azimuth.deltamax=acp_azim_deltamax
Defining Reconfiguration Values in Custom Atoll Fields
tx.azimuth.min=acp_azim_min
# absolute
azimuth
angle
In the [ACPCustomFieldExtraction] section,
you can setvalue
options for
that will
enable ACP
to extract data from custom fields from
tables in the Atoll database. ACP will extract the values entered in the custom fields and use them as default reconfiguration
tx.azimuth.max=acp_azim_max
values when a new optimisation setup is created. The values extracted can be updated in the ACP setup, but ACP will not
tx.azimuth.step=acp_azim_step
update the Atoll tables with the new values.
tx.azimuth.minInterSector=acp_azim_inter
tx.height.optimize=acp_height_use
If a value is undefined in a custom field for a cell, ACP will use the default value for that
parameter.
tx.height.deltamin=acp_height_deltamin
# relative values from current height
tx.height.deltamax=acp_height_deltamax
# absolute value for height values
12.2.2.8.1 tx.height.min=acp_height_min
Defining Reconfiguration Values
for Transmitters and Repeaters Using Custom Atoll Fields
tx.height.max=acp_height_max
In the [ACPCustomFieldExtraction] section, you can set options that will enable ACP to extract data from custom fields from
tx.height.step=acp_height_step
the Transmitters and Repeaters tables in the Atoll database. The custom columns in the Transmitters or Repeaters tables
must match the column name defined in the acp.ini file. By default, the ACP does not extract custom fields.
tx.gsm.power.optimize=acp_gsmpower_use
tx.gsm.power.min=acp_gsmpower_min
[ACPCustomFieldExtraction]
tx.gsm.power.max=acp_gsmpower_max
# The name of the custom column in Transmitters and Repeaters table use to
# initialize the reconfiguration parameter for each transmitter or repeater.
tx.antenna.optimize=acp_ant_use
tx.antenna.group=acp_ant_group
215
Forsk 2011
tx.etilt.optimize=acp_etilt_use
tx.etilt.min=acp_etilt_min
tx.etilt.max=acp_etilt_max
tx.tilt.optimize=acp_tilt_use
tx.tilt.min=acp_tilt_min
tx.tilt.max=acp_tilt_max
tx.tilt.step=acp_tilt_step
tx.azimuth.optimize=acp_azim_use # relative values from current azimuth
tx.azimuth.deltamin=acp_azim_deltamin
tx.azimuth.deltamax=acp_azim_deltamax
tx.azimuth.min=acp_azim_min # absolute value for azimuth angle
tx.azimuth.max=acp_azim_max
tx.azimuth.step=acp_azim_step
tx.azimuth.minInterSector=acp_azim_inter
tx.height.optimize=acp_height_use
tx.height.deltamin=acp_height_deltamin # relative values from current height
tx.height.deltamax=acp_height_deltamax
tx.height.min=acp_height_min # absolute value for height values
tx.height.max=acp_height_max
tx.height.step=acp_height_step
tx.gsm.power.optimize=acp_gsmpower_use
tx.gsm.power.min=acp_gsmpower_min
tx.gsm.power.max=acp_gsmpower_max
12.2.2.8.2
216
AT310_AM_E2
wcell.power.max=acp_power_max
wcell.power.step=acp_power_step
The following options can be used to define the custom columns in the T4GCells table. These will be used for default
reconfiguration options for LTE cells. By default, the value of each is undefined; therefore the field will not be extracted.
[ACPCustomFieldExtraction]
lcell.power.optimize=acp_power_use
lcell.power.min=acp_power_min
lcell.power.max=acp_power_max
lcell.power.step=acp_power_step
12.2.2.8.3
Status of sites: By using the "site.status" option to define the name of the custom status column in the Sites table,
you can extract the status (candidate or existing) of sites for site selection. 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 sites with a
label other than the one defined by the "site.status.candidate" option will be considered as existing sites. By default,
all active sites are considered as existing sites.
[ACPCustomFieldExtraction]
site.status=ACP_STATUS # Name of the custom column in Sites table.
# Default value is 'ACP_STATUS'.
site.status.candidate=candidate # Name used to define a candidate site.
The following options can be used to define custom columns in the Sites table. These will be used for default reconfiguration
options for each site.
[ACPCustomFieldExtraction]
site.locked=acp_site_locked
site.removeable=acp_site_removable
site.cellsRemoveable=acp_site_cellsRemovable
site.azimLocked=acp_site_azimLocked
site.heightLocked=acp_site_heightLocked
12.2.2.8.4
217
Forsk 2011
The following option can be used to name the custom columns in the Antennas table to automatically define the AEDT
options.
To optimise AEDT, you must set the "enableAedt" option to "1" first, in order to activate
it.
[ACPCustomFieldExtraction]
# The name of the custom column in ANTENNA table of type 'bool' used to
# automatically generate patterns from the given aedt range
antenna.aedtUse=ACP_AEDT_USE
# The name of the custom column in ANTENNA table of type 'int', that defines the
# aedt range
antenna.aedtMin=ACP_AEDT_MIN
# The name of the custom column in ANTENNA table of type 'int', that defines the
# aedt range
antenna.aedtMax=ACP_AEDT_MAX
12.2.2.9.1
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.
cost.classes.0.name=Planned
cost.classes.0.azimuth.cost=1
218
AT310_AM_E2
cost.classes.0.azimuth.isSiteVisit=true
cost.classes.0.tilt.cost=1
cost.classes.0.tilt.isSiteVisit=true
cost.classes.0.antenna.cost=1
cost.classes.0.antenna.isSiteVisit=true
cost.classes.0.etilt.cost=0.1
cost.classes.0.etilt.isSiteVisit=false
cost.classes.0.height.cost=1
cost.classes.0.height.isSiteVisit=true
cost.classes.0.power.cost=0.1
cost.classes.0.power.isSiteVisit=false
cost.classes.0.siteVisitCost=2
cost.classes.0.upgradeSiteCost=5
cost.classes.0.newSiteCost=10
cost.classes.0.removeSiteCost=-5
12.2.2.9.2
[ACPCustomFieldExtraction]
site.costClass=[name of custom field in Site table]
The site class defined in the Sites table will be assigned automatically when an ACP optimisation is defined. For new candidate
sites which are located on an existing site, the site class is the same as the site on which the new candidate is located. For new
candidate sites which are not co-located on an existing site, the site class is set to "Default" and can be changed manually.
By defining the costs of each site class as explained in "Defining Automatic Site Classes" on page 218, the cost structure is
automatically defined as well.
12.2.2.10.1
219
Forsk 2011
There are two possible formats for defining the range of colours on maps:
1. Detailed format: The detailed format enables you to set a non-uniform range. The number of ranges is defined and,
for each range, the minimum and maximum value of the range followed by its RGB color representation.
colormap.<techno>.<quality>.nbRange=8 # Number of ranges to be defined
colormap.<techno>.<quality>.range.0=[-99999.000000 -15.000000] RGB(0 0 255)
colormap.<techno>.<quality>.range.1=[-15.000000 -13.000000] RGB(0 128 255)
colormap.<techno>.<quality>.range.2=[-13.000000 -11.000000] RGB(0 196 196)
colormap.<techno>.<quality>.range.3=[-11.000000 -9.000000] RGB(0 224 0)
colormap.<techno>.<quality>.range.4=[-9.000000 -7.000000] RGB(128 255 0)
colormap.<techno>.<quality>.range.5=[-7.000000 -5.000000] RGB(255 224 0)
colormap.<techno>.<quality>.range.6=[-5.000000 -3.000000] RGB(255 128 0)
colormap.<techno>.<quality>.range.7=[-3.000000 99999.000000] RGB(255 0 0)
2. Uniform format description: A uniform format description using a range and step: [firstBreak startcolor] [lastBreak
endColor] interval:
colormap.<techno>.<quality>.rangeDefinition=[-5 RGB(255 0 0)] [-20 RGB(0 0 255)] -5
These colormap descriptions are used for default colormap and can easily be changed by the user. The settings are the same
for the various quality indicator of the various technologies, where you replace:
In addition a number of other colormaps can be defined for other type of maps:
12.2.2.10.2
The following options define the pixel size used in the maps on the Quality Maps tab. You can let ACP automatically define the
pixel size or you can define the pixel size:
config.isAutoPixel=1 # Automatically calculate point size from coverage surface
config.pixelSize=1 # If autopixel is not set, use this number of pixels for each point
config.pixelCoverage=50 # If autopixel is set, calculate the pixel size of a point
to try to cover the set percentage of the used surface
config.maxPixelSize=6 # If autopixel is set, limit the pixel size to the set maximum.
The following options define the size of the map title on the Quality Maps tab:
config.titleHeight=16 # Title height in pixels
config.titleFontSize=16 # Size of title font in points
The following option defines the width of the margin in pixels on the Quality Maps tab:
config.margin=2
220
AT310_AM_E2
The following options define the appearance of the map legend on the Quality Maps tab:
config.showLegend=1 # Defines whether the legend is displayed.
config.legendWidth=40 # Defines the width of the legend in pixels.
config.legendFontSize=11 # Defines the font used in points.
config.legendForeground=0 # RGB code as integer: here black
The following option defines whether the axis is displayed on the Quality Maps tab:
config.showAxis=1
The following options define the appearance of the histogram on the Quality Maps tab:
config.showHistogram=1 # Defines whether the histogram is displayed.
config.histogramHeight=60 # Defines the width of the histogram in pixels.
The following options define the appearance of the focus zone on the Quality Maps tab:
config.showFocusZone=1 # Defines whether the focus zone is displayed.
config.focusLighterPercent=30 # Defines how much lighter the area outside the focus
zone is displayed.
221
Forsk 2011
# define the font used by grid, graph component and map component
DefaultFont=MS UI Gothic
# for grid only, define the used font size. 0 mean default size
DefaultGridFontSize=0
222
memLimitNumPos: Memory use is determined to be excessive when the maximum number of pixels, as defined in
"memLimitNumPos" is reached during a calculation. Setting "memLimitNumPos" to "-1" deactivates this option.
AT310_AM_E2
memLimitMemory: Memory use is determined to be excessive when the estimated memory use in Mb, as defined in
"memLimitMemory" is reached during a calculation. Setting "memLimitMemory" to "-1" deactivates this option.
memLimitUseableMemory: Memory use is determined to be excessive when the estimated memory use exceeds the
percentage of the total memory available for Atoll, as defined in "memLimitUseableMemory." Setting
"memLimitUseableMemory" to "-1" deactivates this option.
If all three options are deactivated, ACP does not check excessive memory usage.
The "abortIfMemLimitReach" option defines how ACP reacts if the defined maximum memory use is reached. By default (with
"abortIfMemLimitReach" set to "0"), ACP will attempt to allocate memory. If unable to successfully allocate memory, ACP
displays a message and the calculation is stopped. When using the option "abortIfMemLimitReach", then ACP will not start if
the message indicating excessive memory use is displayed.
By default, excessive memory use is considered an estimate of 80% of the memory available to the process; ACP is not
prevented running even when 80% is exceeded.
When ACP estimates actual memory use (i.e., using either "memLimitMemory" or
"memLimitUseableMemory"), the memory estimate is only a rough estimate. Depending
on the project, actual memory usage can be quite different.
12.2.3.4.1
Signal Level
You can define how ACP measures the signal level (UMTS RSCP, GSM BCCH Power, WiMAX Preamble Power, LTE Reference
signal Power, CDMA pilot power) using the "linkMode" option. The "linkMode" option can have one of the following values:
0: When "linkMode" is set to "0," ACP considers the signal level on the downlink and transmission losses are taken
into account. This is the default setting.
1: When "linkMode" is set to "1," ACP considers the signal level on the uplink and reception losses are taken into
account.
2: When "linkMode" is set to "2," ACP does not take reception or transmission losses into account.
12.2.3.4.2
0: When "addPilotSHOGain" is set to "0," ACP does not take macro diversity gain into account.
1: When "addPilotSHOGain" is set to "1," ACP takes macro diversity gain into account. This is the default value.
Any changes you make here must match corresponding changes in the atoll.ini file. When
"addPilotSHOGain" is set to "0," the ACP results will only match the results in Atoll if the
following settings are made in the [CDMA] section of the atoll.ini file: AddPilotSHOGain=0
0: When "useSiteAltitude" is set to "0," ACP uses the exact transmitter coordinates, including dx and dy offset.
1: When "useSiteAltitude" is set to "1," ACP uses only the coordinates of the site. This is the default value.
223
Forsk 2011
Any change you make here must match a corresponding change in the atoll.ini file. When
"useSiteAltitude" is set to "1," the ACP results will only match the results in Atoll if the
following setting is made in the atoll.ini file: useSiteAltitude=1
useSiteAltitude=1 # The default
High Speed: Using the highest speed also uses the least memory although the final results may 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:
maxMonitorCell: The "maxMonitorCell" defines the maximum number of cells monitored. This option affects memory
use and accuracy. The analogous options for the high speed mode and the high precision mode are
"maxMonitorCellSpeed" and "maxMonitorCellPrec", respectively.
threshLevelMonitorCell: The "threshLevelMonitorCell" defines the best server signal threshold (dB) in order to be
monitored. This option affects memory and accuracy.
The analogous options for the high speed mode and the high precision mode are "threshLevelMonitorCellSpeed" and
"threshLevelMonitorCellPrec", respectively.
The following options define the values ACP uses for default mode:
maxMonitorCell=32
threshLevelMonitorCell = 35
The following options define the values ACP uses for high speed mode:
maxMonitorCellSpeed=30
threshLevelMonitorCellSpeed = 30
The following options define the values ACP uses for high precision mode:
maxMonitorCellPrec=35
threshLevelMonitorCellPrec = 40
Other options in the acp.ini file can be used to define additional offsets that will be used by the specific technology that ACP
is optimising:
threshLevelOffUmts=0
maxMonitorOffUmts=0
threshLevelOffGsm=0
maxMonitorOffGsm=0
threshLevelOffWimax=5
maxMonitorOffWimax=5
threshLevelOffLte=10
maxMonitorOffLte=10
224
AT310_AM_E2
gisDataTechnoShared=0
Atoll ACP loads raster data with block-based processing to reduce memory usage. The maximum memory (in Mb) allowed for
this block processing in Mb is controlled with the following setting:
gisDataCacheMemMax=256
You can reduce this number if you experience issues with ACP failure due to memory allocation.
0: If this option is set to "0," ACP will access path loss matrices through Atoll.
1: If this option is set to "1," ACP will access path loss matrices directly. With this setting, the path loss matrices must
be stored externally; they can not be embedded.
2: If this option is set to "2," ACP will access path loss matrices directly if they are external, otherwise through Atoll if
they are embedded. This is the default value.
pathlossAccessMode=2
0: This value is intended for versions of Atoll up to and including version 2.7.1. If this option is set to "0," ACP will only
take preamble segmentation into account if the segmentation flag of cell frame configuration is set to ON.
1: This value is intended for versions of Atoll of 2.8.0 and up. If this option is set to "1," ACP always takes preamble
segmentation into account.
2: If this option is set to "2," ACP automatically detects the version of Atoll used. This is the default value.
wimaxPreambleSegmented=2
lteMultiAntennaInterference=2
wimaxMultiAntennaInterference=2
225
Forsk 2011
0: Included.
1: Excluded.
2: ACP automatically detects the version of Atoll used, and hence the value used by Atoll for this option. This is the
default value.
lteExcludeCPFromUsefulPower=2
0: Included.
1: Excluded.
2: ACP automatically detects the version of Atoll used, and hence the value used by Atoll for this option. This is the
default value.
wimaxExcludeCPFromUsefulPower=2
12.2.3.14 Fixed Ratio Between Pilot Power and Max Power (UMTS)
When optimising the maximum cell power in UMTS, the ACP forces the ratio between pilot power and maximum power to
stay constant. You can remove this constraint using the following option:
umtsPilotPowerRatioFixed=0
226
AT310_AM_E2
227
228
Forsk 2011
Part 3
Data Structures
This part of the administrator manual provides information on the
data structures of the Atoll technology modules.
AT310_AM_E2
231
Forsk 2011
232
AT310_AM_E2
Type
Description
Attributes
PHYSICAL_ANTENNA
Text (50)
CodecModeAdaptations Table
Field
Type
Description
Attributes
MAL_LENGTH
Integer
MAL length
233
Forsk 2011
CodecQualityTables Table
Field
Type
Description
Attributes
MAL_LENGTH
Integer
MAL length
CustomFields Table
Field
Type
Description
Attributes
CHOICE_TYPE
Integer
EGPRSQuality Table
Field
Type
Description
Attributes
MAL_LENGTH
Integer
MAL length
EGPRSServices Table
Field
Type
Description
Attributes
DL_ACTIVITY
Float
DL_MBR
Float
DL Maximum Throughput
REQ_AVERAGE_DL_RATE
Float
REQ_AVERAGE_UL_RATE
Float
UL_ACTIVITY
Float
UL_MBR
Float
UL Maximum Throughput
EGPRSTerminals Table
Field
Type
Description
Attributes
DTX
Boolean
TplTransmitters Table
Field
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
SHAREDMAST
Text (50)
Transmitters Table
Field
Type
Description
Attributes
SHAREDMAST
Text (50)
TRGConfigurations Table
Field
Type
Description
Attributes
TX_DIVERSITY_MODE_DL
Short
234
AT310_AM_E2
TRGs Table
Field
Type
Description
Attributes
BLOCKING_PROBA
Float
DTX_GAIN_DL
Float
TX_DIVERSITY_MODE_DL
Short
UL_TRAFFIC_LOAD
Float
Table
AntennasListsNames Table
Table
Neighbours Table
RANK
NeighboursConstraints Table
RANK
NeighboursConstraintsExt Table
RANK
NeighboursExt Table
RANK
TplTransmitters Table
ANTDIVGAIN
AVERAGE_8PSK_POWER_BACKOFF
COV_PROBA
Transmitters Table
ANTDIVGAIN
AVERAGE_8PSK_POWER_BACKOFF
COV_PROBA
Type
Description
Attributes
DATA
Binary
DESCRIPTION
Text
(255)
User defined
NAME
Text (50)
SIGNATURE
Text (40)
235
Forsk 2011
Field
Type
Description
Attributes
TYPE
Text (50)
Type
Description
Attributes
Beamwidth
Float
Antenna beamwidth
COMMENT_
Text
(255)
CONSTRUCTOR
Text (50)
DIAGRAM
Binary
ELECTRICAL_TILT
Float
FMax
Double
FMin
Double
GAIN
Float
NAME
Text (50)
Name of antenna
PHYSICAL_ANTENNA
Text (50)
The format of the binary field, DIAGRAM, is described in "RF 2D Antenna Pattern Format"
on page 105.
Type
Description
Attributes
NAME
Text (50)
236
Field
Type
Description
Attributes
DOMAIN_NAME
Text (50)
EXCLUDED
Text
(225)
List of BSICs to be excluded from the series defined by FIRST, LAST and
STEP (separated with commas)
EXTRA
Text
(225)
FIRST
Integer
AT310_AM_E2
Field
Type
Description
Attributes
LAST
Integer
NAME
Text (50)
STEP
Integer
The FIRST and LAST fields of this table are of type Integer in the template (.mdb) and in a
database (if connected to one). But these fields are of type Text when accessed or
retrieved from an add-in.
Type
Description
Attributes
CONFIG_DL_LOSSES
Float
CONFIG_UL_LOSSES
Float
NAME
Text (50)
NOISE_FIGURE
Float
RHO_FACTOR
Short
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
TX_DIV_GAIN
Float
Type
Description
Attributes
IDEAL_LINK_ADAPTATION
Boolean
237
Forsk 2011
Field
Type
Description
Attributes
IDEAL_QI_NAME
Text (20)
NAME
Text (50)
REFERENCE_NOISE
Float
Type
Description
Attributes
CODEC_EQT
Text (50)
CODEC_MODE
Text (50)
Codec mode
FREQUENCY_BAND
Text (20)
HOPPING
Short
MAL_LENGTH
Integer
MAL length
MIN_CIR
Float
C/(I+N) quality threshold for selecting this mode when there is no ideal
link adaptation
MOBILITY
Text (50)
Type
Description
Attributes
_8PSK_MODULATION
Boolean
Modulation is 8PSK
CODEC_TYPE
Text (50)
HR
Boolean
MAX_RATE
Float
NAME
Text (50)
SELECTION_PRIORITY
Short
238
Type
Description
Attributes
C_I_TABLE
Memo
QI = f(C/I) table
C_N_TABLE
Memo
QI = f(C/N) table
AT310_AM_E2
Field
Type
Description
Attributes
CODEC_EQT
Text (50)
CODEC_MODE
Text (50)
Codec mode
FREQUENCY_BAND
Text (20)
HOPPING
Short
MAL_LENGTH
Integer
MAL length
MOBILITY
Text (50)
QI_NAME
Text (20)
Type
Description
Attributes
CODE
Integer
Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768)
DATUM_CODE
Double
DATUM_ROTX
Double
Arc-seconds
DATUM_ROTY
Double
Arc-seconds
DATUM_ROTZ
Double
Arc-seconds
DATUM_SCALE
Double
DATUM_SHIFTX
Double
Meters
DATUM_SHIFTY
Double
Meters
DATUM_SHIFTZ
Double
Meters
ELLIPS_CODE
Integer
ELLIPS_RMAJOR
Double
Meters
ELLIPS_RMINOR
Double
Meters
NAME
Text (50)
PROJ_ANGLE
Double
Decimal degrees
PROJ_FALSE_EASTING
Double
Meters
PROJ_FALSE_NORTHING
Double
Meters
PROJ_FIRST_PARALLEL
Double
Decimal degrees
239
Forsk 2011
Field
Type
Description
Attributes
PROJ_LATITUDE_ORIGIN
Double
Decimal degrees
PROJ_LONGITUDE_ORIGIN
Double
Decimal degrees
PROJ_METHOD
Short
PROJ_SCALE_FACTOR
Double
PROJ_SECOND_PARALLEL
Double
Decimal degrees
PROJ_ZONE_NUMBER
Integer
Type
Description
Attributes
CAPTION
Text (50)
CHOICE_LIST
Memo
CHOICE_TYPE
Integer
COLUMN_NAME
Text (50)
DEFAULT_VALUE
Text (50)
GROUP_NAME
Text (50)
TABLE_NAME
Text (50)
See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.
240
Field
Type
Description
Attributes
CS_NUMBER
Short
DATA_CODING
Short
MAX_THROUGHPUT
Float
MODULATION
Short
NAME
Text (50)
TECHNOLOGY
Text (15)
AT310_AM_E2
Type
Description
Attributes
MAX_CHANNELS
Text (4)
MAX_TRXS_TO_ADD_FOR_P
ACKET
Integer
MIN_DEDICATED_PDCH
Integer
NAME
Text (50)
Service Name
PDCH_BLOCKING_PROBA_KP
I
Boolean
PDCH_DELAY_KPI
Boolean
PDCH_THROUGHPUT_MIN_K
PI
Boolean
QUEUING_MODEL
Text (50)
Type
Description
Attributes
DENSITY
Float
ENVIRONMENT
Text (50)
Environment name
MOBILITY
Text (50)
Type of mobility
USER_PROFILE
Text (50)
User profile
Type
Description
Attributes
Equipment name
NAME
Text (50)
REFERENCE_NOISE
Float
Reference noise of the equipment which has been used to produce the Null column allowed: Yes
curves
Default value: -113
TECHNOLOGY
Text (15)
GSM, GPRS or GPRS/EDGE. To allocate traffic to compatible transmitter Null column allowed: Yes
mobile pair.
Default value: GPRS
Type
Description
Attributes
NAME
Text (50)
SPEED
Float
241
Forsk 2011
Type
Description
Attributes
C_THRESHOLD
Float
C_THROUGHPUTS
Memo
COVERI_THRESHOLD
Float
COVERI_THROUGHPUTS
Memo
CS_NAME
Text (10)
EQUIPMENT
Text (50)
Type of equipment
FREQUENCY_BAND
Text (20)
HOPPING
Short
MAL_LENGTH
Integer
MAL length
MOBILITY
Text (50)
Hopping mode corresponding to the curves ( 1=NH; 2= ideal FH; empty = Null column allowed: Yes
all hopping modes)
Default value:
Type
Description
Attributes
AVAIL_CONNECTIONS
Float
DIMENSIONING_MODEL
Text (50)
LOAD_BLOCKING_PROBA
Memo
LOAD_DELAY
Memo
LOAD_RF
Memo
Type
Description
Attributes
DL_ACTIVITY
Float
DL_MBR
Float
DL Maximum Throughput
MAX_BLOCKING_RATE
Float
MAX_DELAY
Float
242
Maximum probability that a packet is blocked (delayed), GoS for circuit Null column allowed: Yes
switched services
Default value: 2
Maximum delay allowed for the service
AT310_AM_E2
Field
Type
Description
Attributes
MAX_TS_SUPPORT
Integer
MIN_THROUGHPUT
Float
MIN_THROUGHPUT_RATIO
Float
NAME
Text (50)
Service Name
REQ_AVERAGE_DL_RATE
Float
REQ_AVERAGE_UL_RATE
Float
TH_OFFSET
Float
TH_SCALE_FACTOR
Float
TYPE
Short
UL_ACTIVITY
Float
UL_MBR
Float
UL Maximum Throughput
Type
Description
Attributes
CALL_DURATION
Float
CALL_NUMBER
Float
DL_VOLUME
Float
SERVICE
Text (50)
TERMINAL
Text (50)
USER_PROFILE
Text (50)
Type
Description
Attributes
CODEC_EQUIPMENT
Text (50)
DL_AVAIL_CARRIERS
Short
DL_AVAIL_TIME_SLOT
Float
DTX
Boolean
243
Forsk 2011
Field
Type
Description
Attributes
EGPRS_EQUIPMENT
Text (50)
MAX_CS
Short
MAX_MCS
Short
NAME
Text (50)
Terminal name
NOISE_FIGURE
Float
PMAX
Float
PRIMARY_BAND
Text (50)
SAIC
Boolean
SECONDARY_BAND
Text (50)
TECHNOLOGY
Text (15)
Type
Description
Attributes
CLUTTER_WEIGHTS
Binary
NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
CONNECTOR_LOSSES_DL
Float
CONNECTOR_LOSSES_UL
Float
LOSS_PER_METER
Float
NAME
Text (50)
Name of Feeder
244
AT310_AM_E2
Type
Description
Attributes
CHANNEL_WIDTH
Double
EXCLUDED_CHANNELS
Text
(255)
FIRST_CHANNEL
Integer
FREQUENCY
Double
LAST_CHANNEL
Integer
MAX_CHANNEL_NUM
Integer
MULTIPLEX_FACTOR
Integer
NAME
Text (20)
Type
Description
Attributes
FREQUENCY_BAND_NAME
Text (50)
NAME
Text (50)
Name of domain
Type
Description
Attributes
DOMAIN_NAME
Text (50)
EXCLUDED
Text
(255)
List of frequencies to be excluded from the series defined by FIRST, LAST Null column allowed: Yes
and STEP (separated with commas)
Default value:
EXTRA
Text
(225)
Frequencies to be added. It is forbidden for EXTRA and EXLUDED to have Null column allowed: Yes
common numbers
Default value:
FIRST
Integer
LAST
Integer
NAME
Text (50)
STEP
Integer
245
Forsk 2011
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
DOMAIN_NAME
Text (50)
EXCLUDED
Text
(225)
List of HSNs to be excluded from the series defined by FIRST, LAST and
STEP (separated with commas)
EXTRA
Text
(225)
FIRST
Integer
LAST
Integer
NAME
Text (50)
STEP
Integer
Type
Description
Attributes
ICP
Memo
ITF_BW
Double
ITF_TECHNO
Text (50)
Interfering technology
V_BW
Double
Type
Description
Attributes
MAX_SPEED
Float
MIN_PRIORITY_POWER
Float
NAME
Text (50)
246
AT310_AM_E2
Field
Type
Description
Attributes
PRIORITY
Short
Type
Description
Attributes
IMPORTANCE
Float
NEIGHBOUR
Text (50)
REASON
Integer
TRANSMITTER
Text (50)
TYPE
Text (50)
Type
Description
Attributes
IMPORTANCE
Float
NEIGHBOUR
Text (50)
STATUS
Integer
TRANSMITTER
Text (50)
Type
Description
Attributes
IMPORTANCE
Float
NEIGHBOUR
Text (50) Second part of the unique key. List of neighbours from another project.
STATUS
Integer
TRANSMITTER
Text (50)
247
Forsk 2011
Field
Type
Description
Attributes
IMPORTANCE
Float
NEIGHBOUR
Text (50) Second part of the unique key. List of neighbours from another project
REASON
Integer
TRANSMITTER
Text (50)
TYPE
Text (50)
Type
Description
Attributes
DEFAULT_MODEL
Text (50)
DEFAULT_RESOLUTION
Float
DMAX
Float
INTERFERERS_RX_THRESH
Float
NAME
Text (50)
SHARED_RESULTS_FOLDER
Text
(255)
SYSTEM_
Text (50)
TECHNOLOGY
Text (10)
THERMAL_NOISE
Float
Thermal noise
Type
Description
Attributes
Data
Binary
Description
Text
(255)
User defined
Name
Text (50)
Signature
Text (40)
Type
Text (50)
248
AT310_AM_E2
Field
Type
Description
Attributes
CS_QI
Boolean
MEAS_PARAM
Short
NAME
Text (20)
PS_QI
Boolean
USE_INTERPOLATION
Boolean
Type
Description
Attributes
ADJ_CHANNEL_PROT
Float
ANTENNA
Text (50)
HEIGHT
Float
LOSS
Float
NAME
Text (50)
Receiver name
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
MANUFACTURER
Text (50)
MAX_AMPLIFIER_GAIN
Float
MAX_OUTPUT_DL
Float
MAX_OUTPUT_UL
Float
MIN_AMPLIFIER_GAIN
Float
NAME
Text (50)
NOISE_FIGURE
Float
STEP_AMPLIFIER_GAIN
Float
TIME_DELAY
Float
249
Forsk 2011
Type
Description
Attributes
AMPLIFIER_GAIN
Float
AZIMUT
Float
DONOR_CELLID
Text (50)
DONOR_LINK_LOSS
Float
DONOR_LINK_TYPE
Short
DONOR_PROPAG_MODEL
Text (50)
DOWNTILT
Float
EIRP
Float
EQUIPMENT_NAME
Text (50)
FEEDER_NAME
Text (50)
FEEDERLENGTH
Float
HEIGHT
Float
REC_ANTENNA
Text (50)
REC_FEEDERLENGTH_UL
Float
TX_ID
Text (50)
Repeater properties are saved in two tables: the donor-side parameters are in the
Repeaters table and the coverage-side parameters in the Transmitters table.
The repeater EIRP taken into account in calculations is stored in the Repeaters table
(the EIRP column of the Transmitters table is not used).
250
Field
Type
Description
Attributes
ANTENNA
Text (50)
AZIMUT
Float
PERCENT_POWER
Float
REDT
Float
TILT
Float
AT310_AM_E2
Field
Type
Description
Attributes
TX_ID
Text (50)
Type
Description
Attributes
DEFAULT_MIN_SEP
Short
RELATION_TYPE
Short
TRX_TYPE
Text (15)
TRX_TYPE_OTHER
Text (15)
Type
Description
Attributes
MIN_SEP
Integer
TRX_TYPE
Text (15)
TRX_TYPE_OTHER
Text (15)
TX_ID
Text (50)
TX_ID_OTHER
Text (50)
Type
Description
Attributes
ALTITUDE
Float
Real altitude
Unit: m
COMMENT_
Text
(255)
LATITUDE
Double
Y coordinate
LONGITUDE
Double
X coordinate
NAME
Text (50)
Site name
PYLON_HEIGHT
Float
SUPPORT_NATURE
Short
251
Forsk 2011
Type
Description
Attributes
LIST_NAME
Text (50)
SITE_NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
DL_LOSSES
Float
NAME
Text (50)
NOISE_FIGURE
Float
UL_GAIN
Float
Type
Description
Attributes
ACTIVE
Boolean
ANTENNA_NAME
Text (50)
AZIMUT
Float
BSIC_DOMAIN
Text (50)
BTS_NAME
Text (50)
CALC_RADIUS
Integer
CALC_RADIUS2
Integer
CALC_RESOLUTION
Integer
Calculation resolution
CALC_RESOLUTION2
Integer
CELL_RESELECT_OFFSET
Integer
252
A text field pointing to ResourceGroups.NAME. It limits the BSIC domain Null column allowed: Yes
of the site.
Default value:
AT310_AM_E2
Field
Type
Description
Attributes
CELL_SIZE
Float
Hexagon radius
Unit: m
CELL_TYPE
Text (50)
CODEC_EQUIPMENT
Text (50)
CODING_SCHEME_NUMBER
Short
COMMENT_
Text
(255)
Comments
EGPRS_EQUIPMENT
Text
(255)
EIRP
Float
ENABLE_EGPRS
Boolean
FEEDER_NAME
Text (50)
FEEDERLENGTH_DL
Float
FEEDERLENGTH_UL
Float
FN_OFFSET
Integer
HEIGHT
Float
LAYER
Text (50)
LAYER_RECEPTION_THRESH
OLD
Float
LOSSES
Float
MAX_EXT_NEIGHB_NUMBER
Short
MAX_NEIGHB_NUMBER
Short
MAX_RANGE
Integer
MIN_RANGE
Integer
MISCDLL
Float
MISCULL
Float
NAME
Text (50)
Template name
NUM_SECTORS
Integer
Number of sectors
PBCCH_CELL_RESELECT_OFF
SET
Integer
Cell reselection offset for GPRS cells with PBCCH in use (For future use)
PBCCH_IN_USE
Boolean
PBCCH_RECEPTION_THRESH
OLD
Float
Reception threshold value for GPRS cells with PBCCH in use (For future
use)
This field marks a set of records in the TRGConfigurations tables (all the
Null column allowed: Yes
records for which TRG_CONFIG has the same value.) Each of these
Default value:
records specifies a TRG that should exist in this transmitter.
253
Forsk 2011
Field
Type
Description
Attributes
POWER
Float
Transmitter power
PROPAG_MODEL
Text
(255)
PROPAG_MODEL2
Text
(255)
REDT
Float
REQ_CHANNELS
Integer
SHAREDMAST
Text (50)
TILT
Float
TMA_NAME
Text (50)
TRX_MAX_NUMBER
Short
TX_TYPE
Short
Type
Description
Attributes
ACTIVE
Boolean
ANTENNA_NAME
Text (50)
AZIMUT
Float
BSIC
Text (10)
BSIC colour code (Base Station Identity Code) assigned to the station
BSIC_DOMAIN
Text (50)
BSIC_FROZEN
Boolean
BTS_NAME
Text (50)
CALC_RADIUS
Integer
CALC_RADIUS2
Integer
CALC_RESOLUTION
Integer
Calculation resolution
CALC_RESOLUTION2
Integer
CELL_IDENTITY
Integer
Cell identity
CELL_RESELECT_OFFSET
Integer
CELL_SIZE
Float
Hexagon radius
Unit: m
254
AT310_AM_E2
Field
CELL_TYPE
Type
Description
Attributes
This field identifies a set of records in the TRGConfigurations tables (all Null column allowed: Yes
Text (50) the records that point to this cell-type) each of these records specifies a
Default value:
TRG that should exist in this transmitter.
DCS1800_N_Normal
CHANNELS
Text
(255)
CODEC_EQUIPMENT
Text (50)
CODING_SCHEME_NUMBER
Integer
COMMENT_
Text
(255)
CONTROL_CHANNEL
Integer
COST_FACTOR
Double
DX
Float
DY
Float
EGPRS_EQUIPMENT
Text (50)
EIRP
Float
ENABLE_EGPRS
Boolean
FBAND
Text (20)
FEEDER_NAME
Text (50)
FEEDERLENGTH_DL
Float
Length of feeder in DL
FEEDERLENGTH_UL
Float
Length of feeder in UL
FN_OFFSET
Integer
FROZEN
Boolean
Only TRXs that are not frozen and belong to non-frozen cells can be
assigned frequencies by the AFP.
HEIGHT
Float
HEXAGON_GROUP
Text (50)
HOP_MODE
Text (25)
HSN_FROZEN
Boolean
LAYER
Text (50)
LAYER_RECEPTION_THRESH
OLD
Float
LOSSES
Float
MAX_EXT_NEIGHB_NUMBER
Integer
MAX_NEIGHB_NUMBER
Integer
255
Forsk 2011
Field
Type
Description
Attributes
MAX_RANGE
Integer
MIN_RANGE
Integer
MISCDLL
Float
Miscellaneous DL loss
MISCULL
Float
Miscellaneous UL loss
NUM_TRX
Float
PBCCH_CELL_RESELECT_OFF
SET
Integer
Cell reselection offset for GPRS cells with PBCCH in use (For future use)
PBCCH_IN_USE
Boolean
PBCCH_RECEPTION_THRESH
OLD
Float
Reception threshold value for GPRS cells with PBCCH in use (For future
use)
POWER
Float
Transmitter power
PROPAG_MODEL
Text
(255)
PROPAG_MODEL2
Text
(255)
REDT
Float
REQ_CHANNELS
Integer
SHAREDMAST
Text (50)
SITE_NAME
Text (50)
Name of the site on which the transmitter is located (from the Sites
table)
TILT
Float
TMA_NAME
Text (50)
TRX_MAX_NUMBER
Short
TX_ID
Text (50)
Transmitter name
TX_TYPE
Short
256
Type
Description
Attributes
_8PSK_PWBCKFF
Float
ASSIGN_MODE
Text (25)
BAD_QUAL_UB
Float
AT310_AM_E2
Field
Type
Description
Attributes
C_OVER_I_MIN
Float
Minimum C/I
CELL_TYPE
Text (50)
COST_FACTOR
Float
DEF_DTX
Boolean
DEF_HOP_MODE
Text (25)
DEF_MIN_RECEPTION
Float
DEF_POWER_OFFSET
Float
DEF_TRX_EQUIPMENT
Text (25)
FREQUENCY_DOMAIN
Text (50)
HR_RATIO
Float
HSN_DOMAIN
Text (50)
HSN_FROZEN
Boolean
Only subcells that point to non-hsn_frozen configurations in nonhsn_frozen cells can by be assigned HSNs by the AFP.
MAXIMAL_MAL
Integer
MEAN_POWER_CONTROL
Float
TRAFFIC_OVERFLOW_TARGE
T
Float
TRX_TYPE
Text (15)
TS_CONFIGURATION_NAME
Text (50)
Timeslot configuration
TX_DIVERSITY_MODE_DL
Short
TX_DIVERSITY_NBANT
Short
TX diversity
Choice list: 1=No TX diversity; 2=TX diversity with 2 antennas;
Type
Description
Attributes
_8PSK_PWBCKFF
Float
AFP_BLOCKED_COST
Float
AFP_CONGESTION
Float
AFP_COST
Float
257
Forsk 2011
Field
Type
Description
Attributes
AFP_FREEZE_DIM
Boolean
Permit the AFP to not always respect the number of required TRXs
AFP_SEP_COST
Float
ASSIGN_MODE
Text (25)
BAD_QUAL_UB
Float
BLOCKING_PROBA
Float
C_OVER_I_MIN
Float
Minimum C/I
COST_FACTOR
Float
CS_ERLANGS
Float
DEF_TRX_EQUIPMENT
Text (25)
DTX
Boolean
DTX_GAIN_DL
Float
EFFECTIVE_TRAFFIC_OVERFL
OW
Float
EXCLUDED
Text
(250)
FREQUENCY_DOMAIN
Text (50)
HOP_MODE
Text (25)
HR_RATIO
Float
HSN
Integer
Assigned HSN.
HSN_DOMAIN
Text (50)
HSN_FROZEN
Boolean
Only subcells that point to non-hsn_frozen configurations in nonhsn_frozen cells can be assigned HSNs by the AFP.
MAXIMAL_MAL
Integer
MEAN_POWER_CONTROL
Float
MIN_RECEPTION
Float
POWER_OFFSET
Float
PREFERRED_FREQ_GROUP
Text (50)
PS_DATA_ERLANGS
Float
REQ_CHANNELS
Integer
SYNCHRO_NAME
Text (50)
258
Additional constraints on subcell quality (considered in AFP): maximum Null column allowed: Yes
probability to have C/I lower than C_OVER_I_MIN.
Default value: 1
All frequencies assigned to TRXs of this configuration must belong to this Null column allowed: Yes
domain. Domains contain grouping info as well.
Default value:
AT310_AM_E2
Field
Type
Description
Attributes
TRAFFIC_LOAD
Float
TRAFFIC_OVERFLOW_TARGE
T
Float
TRX_TYPE
Text (15)
TS_CONFIGURATION_NAME
Text (50)
Timeslot configuration
TX_DIVERSITY_MODE_DL
Short
TX_DIVERSITY_NBANT
Short
TX diversity
Choice list: 1=No TX diversity; 2=TX diversity with 2 antennas;
TX_ID
Text (50)
UL_TRAFFIC_LOAD
Float
Type
Description
Attributes
_8PSK_POWER
Float
COMMENT_
Text
(100)
Comments
GMSK_POWER
Float
MAX_CS
Short
MAX_MCS
Short
NAME
Text (25)
Type
Description
Attributes
_8PSK_PWBCKFF
Float
AFP_RANK
Short
CN_LIST
Text
(255)
DOWNLINK_EXTERNAL_NOIS
E_RISE
Float
FROZEN
Boolean
MAIO
Integer
TRX_EQUIPMENT
Text (25)
259
Forsk 2011
Field
Type
Description
Attributes
TRX_NUMBER
Integer
TRX_TYPE
Text (15)
The couple TX_ID, TRG_TYPE is the key of the TRGs table to which this
TRX belongs
TX_ID
Text (50)
UPLINK_EXTERNAL_NOISE_R
ISE
Float
UPLINK_NOISE_RISE
Float
Type
Description
Attributes
IS_BCCH
Boolean
IS_TCH_DEF
Boolean
Indicates that a TRG_TYPE is the default traffic carrier (the OUTER zone).
Tests in the code will verify that only one type is the default TCH.
NAME
Text (15)
Type of TRX
PRIORITY
Short
Priority of a certain type of TRX to carry traffic (largest value has the
highest priority)
TRAFFIC_POOL
Short
All TRXs of the same pool can exchange traffic if they need to balance
their loads. If they are in different pools, the load balancing might fail.
Type
Description
Attributes
NAME
Text (50)
260
Type
Description
Attributes
CIRCUIT_TS
Integer
COMPOSITE_TS
Integer
NAME
Text (50)
PACKET_TS
Integer
TRX_NUMBER
Integer
AT310_AM_E2
Type
Description
Attributes
LIST_NAME
Text (50)
TX_NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
BSIC_FORMAT
Integer
BSIC format
Choice list: 0=Decimal; 1=Octal;
COORD_SYSTEM
Integer
GAIN_UNIT
Integer
PROJECTION
Integer
RECEPTION_UNIT
Integer
TRANSMISSION_UNIT
Integer
261
262
Forsk 2011
AT310_AM_E2
263
Forsk 2011
264
AT310_AM_E2
265
Forsk 2011
Type
Description
Attributes
PHYSICAL_ANTENNA
Text (50)
Field
Type
Description
Attributes
LOCKED_SC
Boolean
MIMO_SUPPORT
Short
CdmaCells
CustomFields Table
Field
Type
Description
Attributes
CHOICE_TYPE
Integer
HSUPAUECategories
Field
Type
Description
Attributes
UE_CATEGORY_NAME
Text (50)
TplTransmitters
Field
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
MC_HSDPA_MUG
Memo
MC_HSDPA_SCHED_ALGO
Short
MULTI_CARRIER
Short
SHAREDMAST
Text (50)
Field
Type
Description
Attributes
MC_HSDPA_MUG
Memo
MC_HSDPA_SCHED_ALGO
Short
MULTI_CARRIER
Short
SHAREDMAST
Text (50)
Transmitters
266
AT310_AM_E2
UECategories
Field
Type
Description
Attributes
MULTI_CARRIER
Short
UE_CATEGORY_NAME
Text (50)
UMTSServices
Field
Type
Description
Attributes
ADPCH_ACTIVITY
Float
CARRIER_LIST
Text (50)
CARRIER_SUPPORT
Integer
CPC_SUPPORT
Short
Continuous packet connectivity support: None; DL DRX / UL DTX; HSSCCH Less operation; HS-FACH;
DL_GBR
Float
DL_MBR
Float
EDPCH_ACTIVITY
Float
UL_GBR
Float
UL_MBR
Float
UMTSTerminals
Field
Type
Description
Attributes
CPC_SUPPORT
Short
Continuous packet connectivity support: None; DL DRX / UL DTX; HSSCCH Less operation; HS-FACH
Table
AntennasListsNames Table
Table
Neighbours Table
RANK
NeighboursConstraints Table
RANK
NeighboursConstraintsExt Table
RANK
NeighboursExt Table
RANK
267
Forsk 2011
R99Bearers Table
DL_CODING_FACTOR
UL_CODING_FACTOR
TplTransmitters Table
COV_PROBA
Transmitters Table
COV_PROBA
UMTSServices Table
CARRIER
ENABLE_HSDPA
ENABLE_HSUPA
UMTSTerminals Table
HSUPA_DTX_SUPPORT
Type
Description
Attributes
Beamwidth
Float
Antenna beamwidth
COMMENT_
Text
(255)
CONSTRUCTOR
Text (50)
DIAGRAM
Binary
ELECTRICAL_TILT
Float
FMax
Double
FMin
Double
GAIN
Float
NAME
Text (50)
Name of antenna
PHYSICAL_ANTENNA
Text (50)
The format of the binary field, DIAGRAM, is described in the "RF 2D Antenna Pattern
Format" on page 105.
268
Field
Type
Description
Attributes
CONFIG_DL_LOSSES
Float
AT310_AM_E2
Field
Type
Description
Attributes
CONFIG_UL_LOSSES
Float
NAME
Text (50)
NOISE_FIGURE
Float
RHO_FACTOR
Short
Type
Description
Attributes
ACTIVE
Boolean
AS_THRESHOLD
Float
CARRIER
Integer
Carrier number
CELL_ID
Text (50)
CELL_IDENTITY
Integer
Cell identity
COMMENT_
Text
(255)
DOWNLINK_EXTERNAL_NOIS
E_RISE
Float
DYN_HS_SCCH_POWER_ALL
OC
Boolean
DYN_HSDPA_POWER_ALLOC
Boolean
HS_SCCH_POWER
Float
HSDPA_MAX_CODES
Short
HSDPA_MAX_USERS
Short
HSDPA_MIN_CODES
Short
HSDPA_MUG_TABLE
Memo
HSDPA_PWR
Float
HSDPA_SCHEDULER_ALGO
Short
Scheduling algo used for HSDPA users. 0=MAXC/I (MAx C/I), 1=RR
(Round Robin), 2=PF (Proportional Fair);
HSPA_SUPPORT
Short
HSUPA_DLPOWER
Float
HSUPA_MAX_USERS
Short
HSUPA_UL_LOAD
Float
Uplink cell load factor due to HSUPA users: calculated by the WCDMA
simulation algorithm
269
Forsk 2011
Field
Type
Description
Attributes
LOCKED_SC
Boolean
MAX_DL_LOAD
Float
MAX_EXT_NEIGHB_NUMBER
Integer
MAX_INTERCAR_NEIGHB_NB
Integer
MAX_NEIGHB_NUMBER
Integer
MAX_R99BEARER_DL_RATE
Float
MAX_R99BEARER_UL_RATE
Float
MAX_UL_LOAD
Float
MIMO_SUPPORT
Short
NUM_HS_SCCH
Short
NUM_HSDPA_USERS
Short
NUM_HSUPA_USERS
Short
OTHERS_CCH_POWER
Float
PILOT_POWER
Float
POWER_MAX
Float
PWR_HEADROOM
Float
REUSE_DIST
Float
SC_DOMAIN_NAME
Text (50)
SCH_POWER
Float
SCRAMBLING_CODE
Integer
Scrambling code.
TOTAL_POWER
Float
TX_ID
Text (50)
UL_LOAD
Float
UL_REUSE_FACTOR
Float
UPLINK_EXTERNAL_NOISE_R
ISE
Float
Maximum downlink load allowed (percentage of max power used). Used Null column allowed: Yes
in power control simulation
Default value: 50
270
AT310_AM_E2
Field
Type
Description
Attributes
BEARER_INDEX
Short
Cell identity
CHANNEL_ELTS_UL
Integer
EQUIPMENT
Text (50)
IUB_RATE_UL
Float
Type
Description
Attributes
CARRIER_SELECTION
Short
CES_OVERHEAD_DL
Integer
CES_OVERHEAD_UL
Integer
ENABLE_COMPRESSED_MOD
E
Boolean
IUB_E1_RATE
Float
IUB_HSDPA_PERCENT
Short
IUB_OVERHEAD_DL
Float
Iub Common Transport Channel Backhaul Overhead per cell (rate in kps)
MANUFACTURER
Text (50)
MUD_FACTOR
Float
NAME
Text (50)
Equipment name
RAKE_EFFICIENCY
Float
USE_NEIGHBOURS
Boolean
Type
Description
Attributes
CHANNEL_ELTS_DL
Integer
CHANNEL_ELTS_UL
Integer
EQUIPMENT
Text (50)
IUB_RATE_DL
Float
IUB_RATE_UL
Float
271
Forsk 2011
Field
Type
Description
Attributes
SERVICE
Text (50)
Type
Description
Attributes
CODE
Integer
Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768)
DATUM_CODE
Double
DATUM_ROTX
Double
Arc-seconds
DATUM_ROTY
Double
Arc-seconds
DATUM_ROTZ
Double
Arc-seconds
DATUM_SCALE
Double
DATUM_SHIFTX
Double
Meters
DATUM_SHIFTY
Double
Meters
DATUM_SHIFTZ
Double
Meters
ELLIPS_CODE
Integer
ELLIPS_RMAJOR
Double
Meters
ELLIPS_RMINOR
Double
Meters
NAME
Text (50)
PROJ_ANGLE
Double
Decimal degrees
PROJ_FALSE_EASTING
Double
Meters
PROJ_FALSE_NORTHING
Double
Meters
PROJ_FIRST_PARALLEL
Double
Decimal degrees
PROJ_LATITUDE_ORIGIN
Double
Decimal degrees
PROJ_LONGITUDE_ORIGIN
Double
Decimal degrees
PROJ_METHOD
Short
PROJ_SCALE_FACTOR
Double
PROJ_SECOND_PARALLEL
Double
272
AT310_AM_E2
Field
Type
Description
Attributes
PROJ_ZONE_NUMBER
Integer
Type
Description
Attributes
CAPTION
Text (50)
CHOICE_LIST
Memo
CHOICE_TYPE
Integer
COLUMN_NAME
Text (50)
DEFAULT_VALUE
Text (50)
GROUP_NAME
Text (50)
TABLE_NAME
Text (50)
See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.
Type
Description
Attributes
CONNECTOR_LOSSES_DL
Float
CONNECTOR_LOSSES_UL
Float
LOSS_PER_METER
Float
NAME
Text (50)
Name of Feeder
Type
Description
Attributes
BAND_WIDTH
Double
Bandwidth (MHz)
FIRST_CARRIER
Integer
FREQUENCY
Double
LAST_CARRIER
Integer
NAME
Text (50)
273
Forsk 2011
Field
Type
Description
Attributes
SPREADING_WIDTH
Double
Type
Description
Attributes
BEARER_INDEX
Short
HSPDSCH_NUM
Short
MODULATION
Short
RLC_PEAK_THROUGHPUT
Float
TRANSPORT_BL_SIZE
Integer
Type
Description
Attributes
BEST_BEARER_TABLE
Memo
Tables BEST_BEARER_INDEX=f(CQI_HSPDSCH)
CQI_TABLE
Memo
MOBILITY
Text (50)
UE mobility
RX_EQUIP
Text (50)
Type
Description
Attributes
BEARER_INDEX
Short
Bearer index
DL_QI_TABLE
Memo
QI=f(MEAS_PARAM)
MEAS_PARAM from QualityIndicators table
MOBILITY
Text (50)
UE mobility
QI_NAME
Text (50)
RX_EQUIP
Text (50)
274
AT310_AM_E2
Field
Type
Description
Attributes
DL_DIVERSITY_GAIN
Float
HSDPA_BEARER_INDEX
Short
MAX_MIMO_GAIN_TABLE
Memo
MIMO_RX_ANTENNAS
Short
MIMO_TX_ANTENNAS
Short
MOBILITY
Text (50)
UE mobility
RX_EQUIP
Text (50)
Type
Description
Attributes
BEARER_INDEX
Short
EDPDCH_NUM
Short
MIN_SF
Integer
MODULATION
Short
RLC_PEAK_RATE
Float
TRANSPORT_BL_SIZE
Integer
TTI_LENGTH
Float
Type
Description
Attributes
BEARER_INDEX
Short
EARLY_TERM_TABLE
Memo
EC_NT_REQ
Float
MOBILITY
Text (50)
Users mobility
REPEAT_NUM
Integer
RX_EQUIP
Text (50)
275
Forsk 2011
Type
Description
Attributes
BEARER_INDEX
Short
Bearer index
MOBILITY
Text (50)
Users mobility
QI_NAME
Text (50)
REPEAT_NUM
Integer
RX_EQUIP
Text (50)
UL_QI_TABLE
Memo
Type
Description
Attributes
MAX_BLOCK_SIZE_10MS
Integer
MAX_BLOCK_SIZE_2MS
Integer
MAX_EDPDCH_NUM
Short
MIN_SF
Integer
MODULATION
Short
TTI_2MS
Boolean
UE_CATEGORY
Short
UE_CATEGORY_NAME
Text (50)
Type
Description
Attributes
CARRIER1
Integer
First carrier
CARRIER2
Integer
Second carrier
FACTOR
Double
276
AT310_AM_E2
Field
Type
Description
Attributes
ICP
Memo
ITF_BW
Double
ITF_TECHNO
Text (50)
Interfering technology
V_BW
Double
Type
Description
Attributes
FORCE_HHO
Boolean
IMPORTANCE
Float
NEIGHBOUR
Text (50)
REASON
Integer
TRANSMITTER
Text (50)
TYPE
Text (50)
Type
Description
Attributes
FORCE_HHO
Boolean
IMPORTANCE
Float
NEIGHBOUR
Text (50)
STATUS
Integer
TRANSMITTER
Text (50)
Type
Float
Description
Attributes
Text (50) Second part of the unique key. List of neighbours from another project.
277
Forsk 2011
Field
Type
Description
Attributes
STATUS
Integer
TRANSMITTER
Text (50)
Type
Description
Attributes
IMPORTANCE
Float
NEIGHBOUR
Text (50) Second part of the unique key. List of neighbours from another project
REASON
Integer
TRANSMITTER
Text (50)
TYPE
Text (50)
Type
Description
Attributes
ADD_MRC_SOFTERSOFT
Boolean
If true, gain due to MRC is taken into account for softer/soft cases
COMPRESSED_DELTA_DL_Q
UAL
Float
COMPRESSED_DELTA_UL_Q
UAL
Float
COMPRESSED_ON_ECIO
Boolean
COMPRESSED_ON_RSCP
Boolean
COMPRESSED_THRESHOLD
Float
CQI_CPICH_BASED
Boolean
DEFAULT_HOGAIN_UL
Float
DEFAULT_MODEL
Text (50)
DEFAULT_ORTHO_FACTOR
Float
DEFAULT_RESOLUTION
Float
DMAX
Float
HSDPA_NTISNTOT
Boolean
Nt includes or not pilot's signal for HS-SCCH, HS-PDSCH and CPICH for
CQI determination
INTERFERERS_RX_THRESH
Float
278
AT310_AM_E2
Field
Type
Description
Attributes
IOISNTOT
Boolean
NAME
Text (50)
NTISNTOT
Boolean
POWERS_RELATIVE_TO_PILO
T
Boolean
Cell paging and Synchro powers, Service Allowed DL min and max TCH
powers are absolute values or relative to cell pilot power
PTOT_RELATIVE_TO_PMAX
Boolean
RSCP_COMPRESSED_THRESH
OLD
Float
SHARED_RESULTS_FOLDER
Text
(255)
SPREADING_WIDTH
Float
SYSTEM_
Text (50)
TECHNOLOGY
Text (10)
Type
Description
Attributes
Data
Binary
Description
Text
(255)
User defined
Name
Text (50)
Signature
Text (40)
Type
Text (50)
Type
Description
Attributes
CS_QI
Boolean
MEAS_PARAM
Short
NAME
Text (20)
PS_QI
Boolean
USE_INTERPOLATION
Boolean
279
Forsk 2011
Type
Description
Attributes
ACTIVE_SPREADING_FACTOR
_DL
Integer
DL_NOMINAL_BIT_RATE
Float
DPCCH_DPCH_RATIO_DL
Float
DPCCH_DPCH_RATIO_UL
Float
INACTIVE_SPREADING_FACT
OR_DL
Integer
NAME
Text (50)
Bearer name
PTCH_MAX
Float
PTCH_MIN
Float
TYPE
Short
UL_NOMINAL_BIT_RATE
Float
For DL part of Bearer: Minimum transmitter power on traffic channel for Null column allowed: Yes
the bearer not to exceed
Default value: -20
Type
Description
Attributes
ADJ_CHANNEL_PROT
Float
ANTENNA
Text (50)
HEIGHT
Float
LOSS
Float
NAME
Text (50)
Receiver name
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
MANUFACTURER
Text (50)
MAX_AMPLIFIER_GAIN
Float
MAX_OUTPUT_DL
Float
280
AT310_AM_E2
Field
Type
Description
Attributes
MAX_OUTPUT_UL
Float
MIN_AMPLIFIER_GAIN
Float
NAME
Text (50)
NOISE_FIGURE
Float
STEP_AMPLIFIER_GAIN
Float
TIME_DELAY
Float
Type
Description
Attributes
AMPLIFIER_GAIN
Float
AZIMUT
Float
DONOR_CELLID
Text (50)
DONOR_LINK_LOSS
Float
DONOR_LINK_TYPE
Short
DONOR_PROPAG_MODEL
Text (50)
DOWNTILT
Float
EQUIPMENT_NAME
Text (50)
FEEDER_NAME
Text (50)
FEEDERLENGTH
Float
HEIGHT
Float
REC_ANTENNA
Text (50)
REC_FEEDERLENGTH_UL
Float
TOTAL_GAIN
Float
TOTAL_GAIN_UL
Float
TX_ID
Text (50)
Repeater properties are saved in two tables: the donor-side parameters are in the
Repeaters table and the coverage-side parameters in the Transmitters table.
281
Forsk 2011
Type
Description
Attributes
DOMAIN_NAME
Text (50)
Type
Description
Attributes
DOMAIN_NAME
Text (50)
EXCLUDED
Text
(225)
List of codes to be excluded from the series defined by FIRST, LAST and
STEP (separated by blank characters)
EXTRA
Text
(225)
FIRST
Integer
LAST
Integer
NAME
Text (50)
First part of the unique key. Name of the scrambling code group
STEP
Integer
Type
Description
Attributes
ANTENNA
Text (50)
AZIMUT
Float
PERCENT_POWER
Float
REDT
Float
TILT
Float
TX_ID
Text (50)
282
Field
Type
Description
Attributes
TX_ID
Text (50)
First part of the unique key. First cell name in a symmetric relation
AT310_AM_E2
Field
Type
Description
Attributes
TX_ID_OTHER
Text (50)
Type
Description
Attributes
DL_QI_TABLE
Memo
MOBILITY
Text (50)
UE mobility
QI_NAME
Text (50)
RX_EQUIP
Text (50)
SERVICE
Text (50)
UL_QI_TABLE
Memo
Type
Description
Attributes
ALTITUDE
Float
Real altitude
Unit: m
CDMA_EQUIPMENT
Text (50)
CHANNEL_ELEMENTS_DL
Integer
CHANNEL_ELEMENTS_UL
Integer
COMMENT_
Text
(255)
LATITUDE
Double
Y coordinate
LONGITUDE
Double
X coordinate
MAX_IUB_RATE_DL
Float
MAX_IUB_RATE_UL
Float
NAME
Text (50)
Site name
PYLON_HEIGHT
Float
SUPPORT_NATURE
Short
283
Forsk 2011
Field
Type
Description
Attributes
LIST_NAME
Text (50)
SITE_NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
DL_LOSSES
Float
NAME
Text (50)
NOISE_FIGURE
Float
UL_GAIN
Float
284
Field
Type
Description
Attributes
ACTIVE
Boolean
ANTDIVGAIN
Float
ANTENNA_NAME
Text (50)
AS_THRESHOLD
Float
Max allowed difference with the best-server to enter the Active Set (dB)
AZIMUT
Float
BTS_NAME
Text (50)
CALC_RADIUS
Integer
CALC_RADIUS2
Integer
CALC_RESOLUTION
Integer
Calculation resolution
CALC_RESOLUTION2
Integer
CARRIERS
Text (50)
AT310_AM_E2
Field
Type
Description
Attributes
CDMA_EQUIPMENT
Text (50)
CDMA equipment
CELL_SIZE
Float
Hexagon radius
Unit: m
CELLS_POWER_SHARING
Boolean
CHANNEL_ELEMENTS_DL
Integer
CHANNEL_ELEMENTS_UL
Integer
COMMENT_
Text
(255)
Comments
DOWNLINK_EXTERNAL_NOIS
E_RISE
Float
DYN_HS_SCCH_POWER_ALL
OC
Boolean
DYN_HSDPA_POWER_ALLOC
Boolean
FBAND
Text (50)
Frequency band
FEEDER_NAME
Text (50)
FEEDERLENGTH_DL
Float
FEEDERLENGTH_UL
Float
HEIGHT
Float
HS_SCCH_POWER
Float
HSDPA_MAX_CODES
Short
HSDPA_MAX_USERS
Short
HSDPA_MIN_CODES
Short
HSDPA_MUG_TABLE
Memo
HSDPA_PWR
Float
HSDPA_SCHEDULER_ALGO
Short
Scheduling algo used for HSDPA users. 0=MAXC/I (MAx C/I), 1=RR
(Round Robin), 2=PF (Proportional Fair)
HSPA_SUPPORT
Short
HSUPA_DLPOWER
Float
HSUPA_MAX_USERS
Short
HSUPA_UL_LOAD
Float
MAX_DL_LOAD
Float
MAX_EXT_NEIGHB_NUMBER
Short
Maximum downlink load allowed (percentage of max power used). Used Null column allowed: Yes
in power control simulation
Default value:
Maximum number of inter-technology neighbours for the cell or the
transmitter
285
Forsk 2011
Field
Type
Description
Attributes
MAX_INTERCAR_NEIGHB_NB
Integer
MAX_IUB_RATE_DL
Float
MAX_IUB_RATE_UL
Float
MAX_NEIGHB_NUMBER
Short
MAX_R99BEARER_DL_RATE
Float
MAX_R99BEARER_UL_RATE
Float
MAX_UL_LOAD
Float
MC_HSDPA_MUG
Memo
MC_HSDPA_SCHED_ALGO
Short
MISCDLL
Float
MISCULL
Float
MULTI_CARRIER
Short
NAME
Text (50)
Template name
NOISE_FIGURE
Float
NUM_HS_SCCH
Short
NUM_HSDPA_USERS
Short
NUM_HSUPA_USERS
Short
NUM_RX_ANTENNAS
Short
NUM_SECTORS
Integer
Number of sectors
NUM_TX_ANTENNAS
Short
OTHERS_CCH_POWER
Float
PILOT_POWER
Float
POWER_MAX
Float
PROPAG_MODEL
Text
(255)
PROPAG_MODEL2
Text
(255)
PWR_HEADROOM
Float
REDT
Float
286
AT310_AM_E2
Field
Type
Description
Attributes
REUSE_DIST
Float
RXLOSSES
Float
SC_DOMAIN_NAME
Text (50)
SCH_POWER
Float
SHAREDMAST
Text (50)
TILT
Float
TMA_NAME
Text (50)
TOTAL_POWER
Float
TX_DIVERSITY_CFG
Integer
TX_MAX_POWER
Float
TXLOSSES
Float
UL_LOAD
Float
UL_REUSE_FACTOR
Float
UPLINK_EXTERNAL_NOISE_R
ISE
Float
Type
Description
Attributes
ACTIVE
Boolean
ANTDIVGAIN
Float
ANTENNA_NAME
Text (50)
AZIMUT
Float
BTS_NAME
Text (50)
CALC_RADIUS
Integer
CALC_RADIUS2
Integer
CALC_RESOLUTION
Integer
Calculation resolution
CALC_RESOLUTION2
Integer
CELL_SIZE
Float
Hexagon radius
Unit: m
287
Forsk 2011
Field
Type
Description
Attributes
CELLS_POWER_SHARING
Boolean
COMMENT_
Text
(255)
DX
Float
DY
Float
FBAND
Text (50)
Frequency band
FEEDER_NAME
Text (50)
FEEDERLENGTH_DL
Float
Length of feeder in DL
FEEDERLENGTH_UL
Float
Length of feeder in UL
HEIGHT
Float
HEXAGON_GROUP
Text (50)
MC_HSDPA_MUG
Memo
MC_HSDPA_SCHED_ALGO
Short
MISCDLL
Float
Miscellaneous DL loss
MISCULL
Float
Miscellaneous UL loss
MULTI_CARRIER
Short
NOISE_FIGURE
Float
NUM_RX_ANTENNAS
Short
NUM_TX_ANTENNAS
Short
PROPAG_MODEL
Text
(255)
PROPAG_MODEL2
Text
(255)
REDT
Float
RXLOSSES
Float
SHAREDMAST
Text (50)
SITE_NAME
Text (50)
Name of the site on which the transmitter is located (from the Sites
table)
TILT
Float
TMA_NAME
Text (50)
TX_DIVERSITY_CFG
Short
288
TX diversity configuration: 1=No TX diversity; 2=TX div. open loop; 3=TX Null column allowed: Yes
div. closed loop;
Default value: 0
AT310_AM_E2
Field
Type
Description
Attributes
TX_ID
Text (50)
Transmitter name
TX_MAX_POWER
Float
TXLOSSES
Float
Type
Description
Attributes
LIST_NAME
Text (50)
TX_NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
MAX_BLOCK_SIZE
Integer
MAX_HSPDSCH_NUM
Short
MIMO_SUPPORT
Short
MIN_INTERTTI_NUM
Short
MODULATION
Short
MULTI_CARRIER
Short
UE_CATEGORY
Short
UE_CATEGORY_NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
289
Forsk 2011
Type
Description
Attributes
DENSITY
Float
ENVIRONMENT
Text (50)
Environment name
MOBILITY
Text (50)
Type of mobility
USER_PROFILE
Text (50)
Type
Description
Attributes
HSSCCH_ECNT
Float
MEAN_SPEED
Float
NAME
Text (50)
Type of mobility
TADD
Float
290
Type
Description
Attributes
ADPCH_ACTIVITY
Float
BODY_LOSS
Float
Body loss
CARRIER_LIST
Text (50)
CARRIER_SUPPORT
Integer
CPC_SUPPORT
Short
Continuous packet connectivity support: None; DL DRX / UL DTX; HSSCCH Less operation; HS-FACH
DL_ACTIVITY
Float
DL_DP
Float
DL_DPC
Float
Reading time (distance) between two packet calls (ms) on the downlink
DL_GBR
Float
DL_MBR
Float
DL_NPC
Integer
AT310_AM_E2
Field
Type
Description
Attributes
DL_PACKET_EFFICIENCY
Float
DL_SP
Integer
DL_SPC_MAX
Float
DL_SPC_MIN
Float
EDPCH_ACTIVITY
Float
ENABLE_DOWNGRADING
Boolean
NAME
Text (50)
Service name
PRIORITY
Integer
R99BEARER
Text (50)
REQ_AVERAGE_DL_RATE
Float
REQ_AVERAGE_UL_RATE
Float
TH_OFFSET
Float
TH_SCALE_FACTOR
Float
TYPE
Short
UL_ACTIVITY
Float
UL_DP
Float
UL_DPC
Float
Reading time (distance) between two packet calls (ms) on the uplink
UL_GBR
Float
UL_MBR
Float
UL_NPC
Integer
UL_PACKET_EFFICIENCY
Float
UL_SP
Integer
UL_SPC_MAX
Float
UL_SPC_MIN
Float
USE_HANDOFF
Boolean
291
Forsk 2011
Field
Type
Description
Attributes
DL_TARGET_QUAL
Float
DL_TGT_QUAL_DIVCLOSED
Float
DL_TGT_QUAL_DIVOPEN
Float
MOBILITY
Text (50)
RX_EQUIP
Text (50)
Type of receiver
SERVICE
Text (50)
UL_TARGET_QUAL
Float
UL_TGT_QUAL_DIV2RX
Float
UL_TGT_QUAL_DIV4RX
Float
Type
Description
Attributes
CALL_DURATION
Float
CALL_NUMBER
Float
DL_VOLUME
Float
SERVICE
Text (50)
TERMINAL
Text (50)
UL_VOLUME
Float
USER_PROFILE
Text (50)
Type
Description
Attributes
ACTIVE_SET_SIZE
Short
CPC_SUPPORT
Short
Continuous packet connectivity support: None; DL DRX / UL DTX; HSSCCH Less operation; HS-FACH
ENABLE_COMPRESSED_MOD
E
Boolean
GAIN
Float
292
AT310_AM_E2
Field
Type
Description
Attributes
HSPA_SUPPORT
Short
HSUPA_UE_CATEGORY
Short
LOSS
Float
MUD_FACTOR
Float
NAME
Text (50)
Terminal name
NOISE_FACTOR
Float
NOISE_FACTOR_SEC
Float
NUM_RX_ANTENNAS
Short
PMAX
Float
PMIN
Float
PRIMARY_BAND
Text (50)
RAKE_EFFICIENCY
Float
RHO_FACTOR
Short
RX_EQUIP
Text (50)
SECONDARY_BAND
Text (50)
UE_CATEGORY
Short
Advanced Receiver Factor to model intra-cell interference reduction for Null column allowed: Yes
HSDPA terminals only
Default value: 0
Noise figure used to determine the thermal noise at the receiver (for the Null column allowed: Yes
secondary frequency band)
Default value: 8
Type
Description
Attributes
CLUTTER_WEIGHTS
Binary
NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
293
Forsk 2011
Field
Type
Description
Attributes
COORD_SYSTEM
Integer
GAIN_UNIT
Integer
PROJECTION
Integer
RECEPTION_UNIT
Integer
TRANSMISSION_UNIT
Integer
294
AT310_AM_E2
295
Forsk 2011
296
AT310_AM_E2
Type
Description
Attributes
PHYSICAL_ANTENNA
Text (50)
CustomFields Table
Field
Type
Description
Attributes
CHOICE_TYPE
Integer
FrequencyBands Table
Field
Type
Description
Attributes
GUARD_BAND
Float
297
Forsk 2011
Type
Description
Attributes
N_RB_GROUP0
Text
(255)
N_RB_GROUP1
Text
(255)
N_RB_GROUP2
Text
(255)
N_RB_TOTAL
Short
NAME
Text (50)
Type
Description
Attributes
DOMAIN_NAME
Text (50)
Type
Description
Attributes
DOMAIN_NAME
Text (50)
EXCLUDED
Text
(225)
List of IDs to be excluded from the series defined by FIRST, LAST and
STEP (separated by blank characters)
EXTRA
Text
(225)
FIRST
Integer
LAST
Integer
NAME
Text (50)
STEP
Integer
Neighbours Table
Field
Type
Description
Attributes
RELATION_TYPE
Short
Networks Table
298
Field
Type
Description
Attributes
BS_SELECTION
Short
SSF_CONFIG
Short
AT310_AM_E2
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
MANUFACTURER
Text (50)
MAX_AMPLIFIER_GAIN
Float
MAX_OUTPUT_DL
Float
MAX_OUTPUT_UL
Float
MIN_AMPLIFIER_GAIN
Float
NAME
Text (50)
NOISE_FIGURE
Float
STEP_AMPLIFIER_GAIN
Float
TIME_DELAY
Float
Type
Description
Attributes
AMPLIFIER_GAIN
Float
AZIMUT
Float
DONOR_CELLID
Text (50)
DONOR_LINK_LOSS
Float
DONOR_LINK_TYPE
Short
DONOR_PROPAG_MODEL
Text (50)
DOWNTILT
Float
EQUIPMENT_NAME
Text (50)
FEEDER_NAME
Text (50)
FEEDERLENGTH
Float
HEIGHT
Float
REC_ANTENNA
Text (50)
REC_FEEDERLENGTH_UL
Float
TOTAL_GAIN
Float
TOTAL_GAIN_UL
Float
299
Forsk 2011
Field
Type
Description
Attributes
TX_ID
Text (50)
T4GCells Table
Field
Type
Description
Attributes
AAS_RESULTS
Binary
AAS_USAGE
Float
FRAME_CONFIG
Text (50)
NUM_DL_USERS
Float
NUM_UL_USERS
Float
PCI_DOMAIN_NAME
Text (50)
T4GServices Table
Field
Type
Description
Attributes
DL_LOWEST_BEARER
Short
UL_LOWEST_BEARER
Short
T4GTerminals Table
Field
Type
Description
Attributes
UE_CATEGORY
Text (50)
UE category
Type
Description
Attributes
BEST_MODULATION
Short
DL_TBS_MAX
Float
MAX_MIMO_RX_ANTENNAS
Short
NAME
Text (50)
UE category name
UL_TBS_MAX
Float
TplTransmitters Table
300
Field
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
FRAME_CONFIG
Text (50)
PCI_DOMAIN_NAME
Text (50)
AT310_AM_E2
Field
Type
Description
Attributes
SA_NAME
Text (50)
SHAREDMAST
Text (50)
Transmitters Table
Field
Type
Description
Attributes
SA_NAME
Text (50)
SHAREDMAST
Text (50)
FORCE_HHO
NeighboursConstraints Table
FORCE_HHO
TplTransmitters Table
ANTDIVGAIN
CHANNEL
CHANNEL_STATUS
ID_STATUS
PHY_CELL_ID
Transmitters Table
ANTDIVGAIN
Type
Description
Attributes
Beamwidth
Float
Antenna beamwidth
COMMENT_
Text
(255)
CONSTRUCTOR
Text
(255)
DIAGRAM
Binary
ELECTRICAL_TILT
Float
FMax
Double
FMin
Double
GAIN
Float
NAME
Text (50)
301
Forsk 2011
Field
Type
Description
Attributes
PHYSICAL_ANTENNA
Text (50)
The format of the binary field, DIAGRAM, is described in "RF 2D Antenna Pattern Format"
on page 105.
Type
Description
Attributes
CONFIG_DL_LOSSES
Float
CONFIG_UL_LOSSES
Float
NAME
Text (50)
NOISE_FIGURE
Float
RHO_FACTOR
Float
302
Field
Type
Description
Attributes
CODE
Integer
Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768)
DATUM_CODE
Double
DATUM_ROTX
Double
Arc-seconds
DATUM_ROTY
Double
Arc-seconds
DATUM_ROTZ
Double
Arc-seconds
DATUM_SCALE
Double
DATUM_SHIFTX
Double
Meters
DATUM_SHIFTY
Double
Meters
DATUM_SHIFTZ
Double
Meters
ELLIPS_CODE
Integer
ELLIPS_RMAJOR
Double
Meters
ELLIPS_RMINOR
Double
Meters
NAME
Text (50)
AT310_AM_E2
Field
Type
Description
Attributes
PROJ_ANGLE
Double
Decimal degrees
PROJ_FALSE_EASTING
Double
Meters
PROJ_FALSE_NORTHING
Double
Meters
PROJ_FIRST_PARALLEL
Double
Decimal degrees
PROJ_LATITUDE_ORIGIN
Double
Decimal degrees
PROJ_LONGITUDE_ORIGIN
Double
Decimal degrees
PROJ_METHOD
Short
PROJ_SCALE_FACTOR
Double
PROJ_SECOND_PARALLEL
Double
Decimal degrees
PROJ_ZONE_NUMBER
Integer
Type
Description
Attributes
CAPTION
Text (50)
CHOICE_LIST
Memo
CHOICE_TYPE
Integer
COLUMN_NAME
Text (50)
DEFAULT_VALUE
Text (50)
GROUP_NAME
Text (50)
TABLE_NAME
Text (50)
See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.
Type
Description
Attributes
CONNECTOR_LOSSES_DL
Float
CONNECTOR_LOSSES_UL
Float
303
Forsk 2011
Field
Type
Description
Attributes
LOSS_PER_METER
Float
NAME
Text (50)
Name of Feeder
Type
Description
Attributes
ADJ_CHANNEL_PROT
Float
CHANNEL_WIDTH
Double
DL_FREQUENCY
Double
DUPLEXING_METHOD
Short
EXCLUDED_CHANNELS
Text
(255)
FIRST_CHANNEL
Short
GUARD_BAND
Float
LAST_CHANNEL
Short
N_RB
Integer
NAME
Text (50)
SAMPLING_FREQUENCY
Float
Sampling frequency
Unit: MHz
UL_FREQUENCY
Double
Type
Description
Attributes
ICP
Memo
ITF_BW
Double
ITF_TECHNO
Text (50)
Interfering technology
V_BW
Double
304
AT310_AM_E2
Field
Type
Description
Attributes
N_RB_GROUP0
Text
(255)
N_RB_GROUP1
Text
(255)
N_RB_GROUP2
Text
(255)
N_RB_TOTAL
Short
NAME
Text (50)
Type
DOMAIN_NAME
Text (50)
Description
Attributes
Type
Description
Attributes
DOMAIN_NAME
Text (50)
EXCLUDED
Text
(225)
List of IDs to be excluded from the series defined by FIRST, LAST and
STEP (separated by blank characters)
EXTRA
Text
(225)
FIRST
Integer
LAST
Integer
NAME
Text (50)
STEP
Integer
Type
Description
Attributes
MAX_CINR
Float
MOBILITY
Text (50)
MUG_TABLE
Memo
SCHEDULER_NAME
Text (30)
305
Forsk 2011
Type
Description
Attributes
IMPORTANCE
Float
Handover importance
NEIGHBOUR
Text (50)
Neighbour cell
REASON
Integer
RELATION_TYPE
Short
TRANSMITTER
Text (50)
Reference cell
TYPE
Text (50)
Type
Description
Attributes
IMPORTANCE
Float
Handover importance
NEIGHBOUR
Text (50)
Neighbour cell
STATUS
Integer
TRANSMITTER
Text (50)
Reference cell
Type
Description
Attributes
IMPORTANCE
Float
Handover importance
NEIGHBOUR
Text (50)
STATUS
Integer
TRANSMITTER
Text (50)
Reference cell
306
Type
Description
Attributes
IMPORTANCE
Float
Handover importance
NEIGHBOUR
Text (50)
Neighbour cell
AT310_AM_E2
Field
Type
Description
Attributes
REASON
Integer
TRANSMITTER
Text (50)
Reference cell
TYPE
Text (50)
Type
Description
Attributes
AMS_SEL_CRITERION
Short
AMS criterion
(0 - Reference signal C/N; 1 - Reference signal C/(I+N))
BS_SELECTION
Short
CELL_SELECTION
Short
DEFAULT_CP
Short
DEFAULT_MODEL
Text (50)
DEFAULT_RESOLUTION
Float
DMAX
Float
INTERFERERS_RX_THRESH
Float
NAME
Text (50)
Type of network
PDCCH_SYMBOLS
Short
POWER_CONTROL_MARGIN
Float
PUCCH_AVG_NRB
Float
RS_EPRE_DEFINITION
Short
SHARED_RESULTS_FOLDER
Text
(255)
SP_PERIODICITY
Short
SSF_CONFIG
Short
SYSTEM_
Text (50)
TECHNOLOGY
Text (10)
THERMAL_NOISE
Float
Thermal noise
307
Forsk 2011
Type
Description
Attributes
Data
Binary
Description
Text
(255)
User defined
Name
Text (50)
Signature
Text (40)
Type
Text (50)
Type
Description
Attributes
CS_QI
Boolean
Flag indicating whether the Quality Indicator is used for Voice (CS)
services
MEAS_PARAM
Short
NAME
Text (50)
PS_QI
Boolean
Flag indicating whether the Quality Indicator is used for Data (PS)
services
USE_INTERPOLATION
Boolean
Type
Description
Attributes
ANTENNA
Text (50)
HEIGHT
Float
LOSS
Float
NAME
Text (50)
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
MANUFACTURER
Text (50)
MAX_AMPLIFIER_GAIN
Float
308
AT310_AM_E2
Field
Type
Description
Attributes
MAX_OUTPUT_DL
Float
MAX_OUTPUT_UL
Float
MIN_AMPLIFIER_GAIN
Float
NAME
Text (50)
NOISE_FIGURE
Float
STEP_AMPLIFIER_GAIN
Float
TIME_DELAY
Float
Type
Description
Attributes
AMPLIFIER_GAIN
Float
AZIMUT
Float
DONOR_CELLID
Text (50)
DONOR_LINK_LOSS
Float
DONOR_LINK_TYPE
Short
DONOR_PROPAG_MODEL
Text (50)
DOWNTILT
Float
EQUIPMENT_NAME
Text (50)
FEEDER_NAME
Text (50)
FEEDERLENGTH
Float
HEIGHT
Float
REC_ANTENNA
Text (50)
REC_FEEDERLENGTH_UL
Float
TOTAL_GAIN
Float
TOTAL_GAIN_UL
Float
TX_ID
Text (50)
309
Forsk 2011
Repeater properties are saved in two tables: the donor-side parameters are in the
Repeaters table and the coverage-side parameters in the Transmitters table.
Type
Description
Attributes
BEARER_SELECTION
Short
NAME
Text (30)
SCHEDULING_METHOD
Short
TARGET_THROUGHPUT_DAT
A
Short
0 = Peak RLC Throughput; 1 = Effective RLC Throughput; 2 = Application Null column allowed: Yes
Throughput
Default value: 0
TARGET_THROUGHPUT_VOI
CE
Short
0 = Peak RLC Throughput; 1 = Effective RLC Throughput; 2 = Application Null column allowed: Yes
Throughput
Default value: 0
UL_BW_ALLOCATION
Short
Bearer Selection Criterion: 0 Bearer Index; 1 Peak RLC Throughput; 2 Null column allowed: Yes
Effective RLC Throughput
Default value: 0
Type
Description
Attributes
ANTENNA
Text (50)
AZIMUT
Float
PERCENT_POWER
Float
REDT
Float
TILT
Float
TX_ID
Text (50)
Transmitter name
310
Type
Description
Attributes
ALTITUDE
Float
COMMENT_
Text
(255)
LATITUDE
Double
Y coordinate
LONGITUDE
Double
X coordinate
NAME
Text (50)
Site name
AT310_AM_E2
Field
Type
Description
Attributes
PYLON_HEIGHT
Float
SUPPORT_NATURE
Short
Type
Description
Attributes
LIST_NAME
Text (50)
SITE_NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
BROADCAST_ANTENNA
Text (50)
COMMENT_
Text
(255)
Comments
NAME
Text (50)
SA_MODEL
Text (50)
Type
Description
Attributes
SA_DATA
Binary
SA_DESCRIPTION
Text (50)
SA_NAME
Text (50)
SA_SIGNATURE
Text (50)
SA_TYPE
Text (50)
311
Forsk 2011
Type
Description
Attributes
BEARER_INDEX
Short
Bearer index
MOBILITY
Text (50)
Mobility type
QI_CURVE
Memo
QI_NAME
Text (50)
RX_EQUIP
Text (50)
Type
Description
Attributes
BEARER_INDEX
Short
CODING_RATE
Float
Coding rate
MODULATION
Short
Modulation type
Choice list: 0=BPSK; 1=QPSK; 2=16QAM; 3=64QAM;
NAME
Text (50)
SPECTRAL_EFFICIENCY
Float
Type
Description
Attributes
BEARERS_REQUIRED_COVERI
Memo
MOBILITY
Text (50)
CPE mobility
RX_EQUIP
Text (50)
312
Field
Type
Description
Attributes
AAS_RESULTS
Binary
AAS_USAGE
Float
ACTIVE
Boolean
AMS_THRESHOLD
Float
AT310_AM_E2
Field
Type
Description
Attributes
CELL_ID
Text (50)
CHANNEL
Integer
Channel number
CHANNEL_STATUS
Short
COMMENT_
Text
(255)
DIVERSITY_SUPPORT
Short
DIVERSITY_SUPPORT_UL
Short
DL_FFR_USAGE
Float
Percentage of the downlink traffic load carried by the ICIC part of the
cell
DL_LOAD
Float
DOWNLINK_EXTERNAL_NOIS
E_RISE
Float
FBAND
Text (50)
FRAME_CONFIG
Text (50)
ICIC_DELTAPL_TH
Float
ICIC_SUPPORT
Short
ID_REUSE_MIN_DIST
Float
The minimum reuse distance for the AFP and physical cell ID allocation
ID_STATUS
Short
MAX_DL_LOAD
Float
MAX_EXT_NEIGHB_NUMBER
Integer
MAX_NEIGHB_NUMBER
Integer
MAX_NUMBER_OF_USERS
Integer
MAX_UL_LOAD
Float
NOISE_RISE_ICIC_UL
Float
NOISE_RISE_UL
Float
NUM_DL_USERS
Float
NUM_UL_USERS
Float
PBCH_POWER_OFFSET
Float
PCI_DOMAIN_NAME
Text (50)
PDCCH_POWER_OFFSET
Float
313
Forsk 2011
Field
Type
Description
Attributes
PDSCH_POWER_OFFSET
Float
PHY_CELL_ID
Integer
Physical cell ID
POWER
Float
RANK
Short
RS_EPRE
Float
RSRQ_THRES
Float
RX_EQUIPMENT
Text (50)
SCH_POWER_OFFSET
Float
SCHEDULER
Text (50)
SF_CONFIG
Short
TX_ID
Text (50)
UL_FPC_CINR_MAX
Float
UL_FPC_FACTOR
Float
UL_FPC_NR_MAX
Float
UL_LOAD
Float
UL_MU_SM_GAIN
Float
UPLINK_EXTERNAL_NOISE_R
ISE
Float
Type
Description
Attributes
DENSITY
Float
ENVIRONMENT
Text (50)
Environment name
MOBILITY
Text (50)
Type of mobility
USER_PROFILE
Text (50)
314
AT310_AM_E2
Field
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
BEARER_INDEX
Short
EQUIPMENT
Text (50)
MAX_BLER
Float
MAX_MIMO_GAIN
Memo
MIMO_RX_ANTENNAS
Short
MIMO_TX_ANTENNAS
Short
MOBILITY
Text(50)
User mobility
STTD_GAIN
Float
Type
Description
Attributes
MEAN_SPEED
Float
NAME
Text (50)
Type of mobility
Type
Description
Attributes
BODY_LOSS
Float
DL_ACTIVITY
Float
DL_DP
Float
DL_DPC
Float
DL_GBR
Float
DL_HIGHEST_BEARER
Float
DL_LOWEST_BEARER
Short
315
Forsk 2011
Field
Type
Description
Attributes
DL_MBR
Float
DL_NPC
Integer
DL_SP
Integer
DL_SPC_MAX
Float
DL_SPC_MIN
Float
NAME
Text (50)
Service name
PRIORITY
Short
REQ_AVERAGE_DL_RATE
Float
REQ_AVERAGE_UL_RATE
Float
TH_OFFSET
Float
TH_SCALE_FACTOR
Float
TYPE
Short
Service type
Choice list: 0=Voice; 1=Data;
UL_ACTIVITY
Float
UL_DP
Float
UL_DPC
Float
UL_GBR
Float
UL_HIGHEST_BEARER
Float
UL_LOWEST_BEARER
Short
UL_MBR
Float
UL_NPC
Integer
UL_SP
Integer
UL_SPC_MAX
Float
UL_SPC_MIN
Float
316
Type
Float
Description
Attributes
AT310_AM_E2
Field
Type
Description
Attributes
CALL_NUMBER
Float
DL_VOLUME
Float
SERVICE
Text (50)
Service (from the Service table) that the subscriber may request
TERMINAL
Text (50)
Type of terminal (from the Terminal table) used by the subscriber for
the service
UL_VOLUME
Float
USER_PROFILE
Text (50)
Type
Description
Attributes
ANTENNA
Text (50)
DIVERSITY_SUPPORT
Short
GAIN
Float
LOSS
Float
MIMO_RX_ANTENNAS
Short
MIMO_TX_ANTENNAS
Short
NAME
Text (50)
Terminal name
NOISE_FACTOR
Float
Noise figure used to determine the thermal noise at the receiver (dB)
PMAX
Float
PMIN
Float
RX_EQUIP
Text (50)
UE_CATEGORY
Text (50)
UE category
Type
Description
Attributes
CLUTTER_WEIGHTS
Binary
NAME
Text (50)
317
Forsk 2011
Type
Description
Attributes
BEST_MODULATION
Short
DL_TBS_MAX
Float
MAX_MIMO_RX_ANTENNAS
Short
NAME
Text (50)
UE category name
UL_TBS_MAX
Float
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
DL_LOSSES
Float
NAME
Text (50)
NOISE_FIGURE
Float
UL_GAIN
Float
318
Field
Type
Description
Attributes
ACTIVE
Boolean
AMS_THRESHOLD
Float
ANTENNA_NAME
Text (50)
AZIMUT
Float
BTS_NAME
Text (50)
CALC_RADIUS
Integer
CALC_RADIUS2
Integer
Calculation radius used to define each transmitter calculation area Unit: Null column allowed: Yes
m
Default value:
Second calculation radius
Unit: m
AT310_AM_E2
Field
Type
Description
Attributes
CALC_RESOLUTION
Integer
Calculation resolution
CALC_RESOLUTION2
Integer
CELL_SIZE
Float
CHANNEL_LIST
Text(255)
COMMENT_
Text
(255)
Comments
DIVERSITY_SUPPORT
Short
DIVERSITY_SUPPORT_UL
Short
DL_FFR_USAGE
Float
Percentage of the downlink traffic load carried by the ICIC part of the
cell
DL_LOAD
Float
DOWNLINK_EXTERNAL_NOIS
E_RISE
Float
FBAND
Text (50)
FEEDER_NAME
Text (50)
FEEDERLENGTH_DL
Float
FEEDERLENGTH_UL
Float
FRAME_CONFIG
Text (50)
HEIGHT
Float
ICIC_DELTAPL_TH
Float
ICIC_SUPPORT
Short
ID_REUSE_MIN_DIST
Float
The minimum reuse distance for the AFP and physical cell ID allocation
MAX_DL_LOAD
Float
MAX_EXT_NEIGHB_NUMBER
Integer
MAX_NEIGHB_NUMBER
Integer
MAX_NUMBER_OF_USERS
Integer
MAX_UL_LOAD
Float
MISCDLL
Float
MISCULL
Float
NAME
Text (50)
Template name
319
Forsk 2011
Field
Type
Description
Attributes
NOISE_FIGURE
Float
NOISE_RISE_ICIC_UL
Float
NOISE_RISE_UL
Float
NUM_SECTORS
Integer
Number of sectors
PBCH_POWER_OFFSET
Float
PCI_DOMAIN_NAME
Text (50)
PDCCH_POWER_OFFSET
Float
PDSCH_POWER_OFFSET
Float
PHY_CELLID_LIST
Text(255)
POWER
Float
PROPAG_MODEL
Text
(255)
PROPAG_MODEL2
Text
(255)
REDT
Float
RS_EPRE
Float
RSRQ_THRES
Float
RX_ANTENNAS_PORTS
Short
RX_EQUIPMENT
Text (50)
Reception equipment
RXLOSSES
Float
SA_NAME
Text (50)
SCH_POWER_OFFSET
Float
SCHEDULER
Text (30)
SF_CONFIG
Short
SHAREDMAST
Text (50)
TILT
Float
TMA_NAME
Text (50)
TX_ANTENNAS_PORTS
Short
TX_TYPE
Short
320
AT310_AM_E2
Field
Type
Description
Attributes
TXLOSSES
Float
UL_FPC_CINR_MAX
Float
UL_FPC_FACTOR
Float
UL_FPC_NR_MAX
Float
UL_LOAD
Float
UL_MU_SM_GAIN
Float
UPLINK_EXTERNAL_NOISE_R
ISE
Float
Type
Description
Attributes
ACTIVE
Boolean
ANTENNA_NAME
Text (50)
AZIMUT
Float
BTS_NAME
Text (50)
CALC_RADIUS
Integer
CALC_RADIUS2
Integer
CALC_RESOLUTION
Integer
Calculation resolution
CALC_RESOLUTION2
Integer
CELL_SIZE
Float
COMMENT_
Text
(255)
DX
Float
DY
Float
FEEDER_NAME
Text (50)
FEEDERLENGTH_DL
Float
FEEDERLENGTH_UL
Float
HEIGHT
Float
HEXAGON_GROUP
Text (50)
321
Forsk 2011
Field
Type
Description
Attributes
MISCDLL
Float
MISCULL
Float
NOISE_FIGURE
Float
POLARIZATION
Text (1)
PROPAG_MODEL
Text (50)
PROPAG_MODEL2
Text (50)
REDT
Float
RX_ANTENNAS_PORTS
Short
RXLOSSES
Float
SA_NAME
Text (50)
SHAREDMAST
Text (50)
SITE_NAME
Text (50)
Name of the site at which the transmitter is located (from the Sites
table)
TILT
Float
TMA_NAME
Text (50)
TX_ANTENNAS_PORTS
Short
TX_ID
Text (50)
Transmitter name
TX_TYPE
Short
TXLOSSES
Float
Type
Description
Attributes
LIST_NAME
Text (50)
TX_NAME
Text (50)
322
Field
Type
Description
Attributes
NAME
Text (50)
AT310_AM_E2
Type
Description
Attributes
COORD_SYSTEM
Integer
GAIN_UNIT
Integer
PROJECTION
Integer
RECEPTION_UNIT
Integer
TRANSMISSION_UNIT
Integer
323
324
Forsk 2011
AT310_AM_E2
Technology-specific tables
These tables are specific to technologies. There structures are the same as in single-technology documents. For the
list of these tables and their equivalent tables in single-technology documents, see "Technology-specific Tables" on
page 327.
a.
antennas
Antennas Table
btsequipments
BTSEquipments Table
coordsys
CoordSys Table
customfields
CustomFields Table
feederequipments
FeederEquipments Table
internetchprotect
InterNetChProtect Tablea
propagationmodels
PropagationModels Table
repeaterequipments
RepeaterEquipments Table
siteslists
SitesLists Table
siteslistsnames
SitesListsNames Table
smartantennasmodels
SmartAntennasModels Table
tmaequipments
TMAEquipments Table
Field
Type
Description
Attributes
V_TECHNO
Text (50)
Victim technology
325
Forsk 2011
Type
Description
Attributes
ADD_MRC_SOFTERSOFT
Boolean
If true, gain due to MRC is taken into account for softer/soft cases
AMS_SEL_CRITERION
Short
AMS criterion
(0 - Reference signal C/N; 1 - Reference signal C/(I+N))
BS_SELECTION
Short
CELL_SELECTION
Short
COMPRESSED_DELTA_DL_Q
UAL
Float
COMPRESSED_DELTA_UL_Q
UAL
Float
COMPRESSED_ON_ECIO
Boolean
COMPRESSED_ON_RSCP
Boolean
COMPRESSED_THRESHOLD
Float
CQI_CPICH_BASED
Boolean
DEFAULT_CP
Short
DEFAULT_HOGAIN_UL
Float
DEFAULT_MODEL
Text (50)
DEFAULT_ORTHO_FACTOR
Float
DEFAULT_RESOLUTION
Float
DMAX
Float
HSDPA_NTISNTOT
Boolean
Nt includes or not pilot's signal for HS-SCCH, HS-PDSCH and CPICH for
CQI determination
INTERFERERS_RX_THRESH
Float
IOISNTOT
Boolean
NAME
Text (50)
Type of network
NTISNTOT
Boolean
PDCCH_SYMBOLS
Short
POWER_CONTROL_MARGIN
Float
POWERS_RELATIVE_TO_PILO
T
Boolean
Cell paging and Synchro powers, Service Allowed DL min and max TCH
powers are absolute values or relative to cell pilot power
PTOT_RELATIVE_TO_PMAX
Boolean
326
AT310_AM_E2
Field
Type
Description
Attributes
PUCCH_AVG_NRB
Float
RS_EPRE_DEFINITION
Short
RSCP_COMPRESSED_THRESH
OLD
Float
SHARED_RESULTS_FOLDER
Text
(255)
SP_PERIODICITY
Short
SPREADING_WIDTH
Float
SSF_CONFIG
Short
SYSTEM_
Text (50)
TECHNOLOGY
Text (10)
THERMAL_NOISE
Float
Thermal noise
The networks table contains one record for each technology in the document. In each record, only parameters relevant for
the rows technology are used.
receivers Table
The final structure is the same as the GSM Receivers table (see "Receivers Table" on page 249).
sites Table
The final structure is the same as the UMTS Sites table (see "Sites Table" on page 283).
units Table
The final structure is the same as the GSM Units table (see "Units Table" on page 261).
gafpmodels
AfpModels Table
gbsicdomains
BSICDomains Table
gbsicgroups
BSICGroups Table
gcelltypes
CellTypes Table
gcodecequipments
CodecEquipments Table
gcodecmodeadapts
CodecModeAdaptations Table
gcodecmodes
CodecModes Table
gcodecqualtables
CodecQualityTables Table
gcodingschemes
EGPRSCodingSchemes Table
gcsequipments
EGPRSEquipments Table
gcsquality
EGPRSQuality Table
gdimensmodel
EGPRSDimensioningModel Table
gfreqdomains
FrequencyDomains Table
gfreqgroups
FrequencyGroups Table
gfrequencybands
FrequencyBands Table
327
Forsk 2011
ghsndomains
HSNDomains Table
ghsngroups
HSNGroups Table
glayers
Layers Table
gneighbours
Neighbours Table
gneighconstraints
NeighboursConstraints Table
gneighext
NeighboursExt Table
gneighextconstraints
NeighboursConstraintsExt Table
gqualityindicators
QualityIndicators Table
grepeaters
Repeaters Table
gsecondaryantennas
SecondaryAntennas Table
gseparationrules
SeparationRules Table
gseparations
Separations Table
gservicequality
EGPRSServiceQuality Table
gtpltransmitters
TplTransmitters Table
gtransmitters
Transmitters Table
gtrgconfigs
TRGConfigurations Table
gtrgs
TRGs Table
gtrxequipments
TRXEquipments Table
gtrxs
TRXs Table
gtrxtypes
TRXTypes Table
gtsconfignames
TSConfigurationNames Table
gtsconfigs
TSConfigurations Table
gtxslists
TxsLists Table
gtxslistsnames
TxsListsNames Table
328
ucells
CDMACells Table
uceuse
CDMAEquipmentsCEsUse Table
uequipments
CDMAEquipments Table
ufrequencybands
FrequencyBands Table
uhsdpabearers
HSDPABearers Table
uhsdpabearerselect
HSDPABearerSelectTables Table
uhsdpaqualtables
HSDPAQualityTables Table
uhspamimoconfigs
HSPAMIMOConfigs Table
uhsupabearers
HSUPABearers Table
uhsupabearerselect
HSUPABearerSelection Table
uhsupaqualtables
HSUPAQualityTables Table
uhsuparessuse
CdmaEqptsHSUPARssUse Table
uhsupauecategories
HSUPAUECategories Table
uinterfreducfactors
InterfReductionFactors Table
uneighbours
Neighbours Table
uneighconstraints
NeighboursConstraints Table
uneighext
NeighboursExt Table
uneighextconstraints
NeighboursConstraintsExt Table
upscdomains
ScramblingCodesDomains Table
upscforbidpairs
Separations Table
upscgroups
ScramblingCodesGroups Table
AT310_AM_E2
uqualityindicators
QualityIndicators Table
ur99bearers
R99Bearers Table
urepeaters
Repeaters Table
usecondaryantennas
SecondaryAntennas Table
uservicequaltables
ServiceQualityTables Table
uservicesquality
UMTSServicesQuality Table
utpltransmitters
TplTransmitters Table
utransmitters
Transmitters Table
utxslists
TxsLists Table
utxslistsnames
TxsListsNames Table
uuecategories
UECategories Table
uuerxequipments
UERxEquipments Table
lbearerqualitycurves
T4GBearerQualityCurves Table
lbearers
T4GBearers Table
lbearersrequiredci
T4GBearersRequiredCI Table
lcells
T4GCells Table
lequipments
T4GEquipments Table
lframeconfigs
lframeconfigs Table
lfrequencybands
FrequencyBands Table
lmimoconfigs
T4GMimoConfigs Table
lmugtables
MUGTables Table
lneighbours
Neighbours Table
lneighconstraints
NeighboursConstraints Table
lneighext
NeighboursExt Table
lneighextconstraints
NeighboursConstraintsExt Table
lpcidomains
lpcidomains Table
lpcigroups
lpcigroups Table
lqualityindicators
QualityIndicators Table
lrepeaters
Repeaters Table
lschedulers
Schedulers Table
lsecondaryantennas
SecondaryAntennas Table
lsmartantennas
SmartAntennas Table
ltpltransmitters
TplTransmitters Table
ltransmitters
Transmitters Table
ltxslists
TxsLists Table
ltxslistsnames
TxsListsNames Table
luecategories
T4GUECategories Table
Descritpion
guneighbours
guneighconstraints
glneighbours
329
Forsk 2011
Descritpion
glneighconstraints
ugneighbours
ugneighconstraints
ulneighbours
ulneighconstraints
lgneighbours
lgneighconstraints
luneighbours
luneighconstraints
Type
Description
Attributes
IMPORTANCE
Float
Handover importance
NEIGHBOUR
Text (50)
REASON
Integer
TRANSMITTER
Text (50)
TYPE
Text (50)
330
Field
Type
Description
Attributes
IMPORTANCE
Float
Handover importance
NEIGHBOUR
Text (50)
STATUS
Integer
TRANSMITTER
Text (50)
AT310_AM_E2
services Table
Field
Type
Description
Attributes
DL_ACTIVITY
Float
NAME
Text (50)
Service Name
REQ_AVERAGE_DL_RATE
Float
REQ_AVERAGE_UL_RATE
Float
TECHNO_PRIORITY
Text (50)
UL_ACTIVITY
Float
gservices Table
Same structure as the services table in GSM, except the DL_ACTIVITY, REQ_AVERAGE_DL_RATE,
REQ_AVERAGE_UL_RATE, and UL_ACTIVITY fields. See "EGPRSServices Table" on page 242.
uservices Table
Same structure as the services table in UMTS, except the DL_ACTIVITY, REQ_AVERAGE_DL_RATE,
REQ_AVERAGE_UL_RATE, and UL_ACTIVITY fields. See "UMTSServices Table" on page 290.
lservices Table
Same structure as the services table in LTE, except the DL_ACTIVITY, REQ_AVERAGE_DL_RATE,
REQ_AVERAGE_UL_RATE, and UL_ACTIVITY fields. See "T4GServices Table" on page 315.
331
Forsk 2011
Terminal Tables
terminals Table
Field
Type
Description
Attributes
NAME
Text (50)
Name of terminal
gterminals Table
Same structure as the terminals table in GSM. See "EGPRSTerminals Table" on page 243.
uterminals Table
Same structure as the terminals table in UMTS. See "UMTSTerminals Table" on page 292.
lterminals Table
Same structure as the terminals table in LTE. See "T4GTerminals Table" on page 317.
Mobility Tables
Field
mobility Table
Type
Description
Attributes
NAME
Text (50)
MEAN_SPEED
Float
332
umobility Table
AT310_AM_E2
Same structure as the mobilities table in UMTS, except the MEAN_SPEED field. See "UMTSMobility Table" on
page 290.
servicesusage Table
Same structure as services usage tables in all three technologies. See, for example, "EGPRSServicesUsage Table" on page 243.
environmentdefs Table
Same structure as environment definition tables in all three technologies. See, for example, "EGPRSEnvironmentDefs Table"
on page 241.
trafficenvs Table
Same structure as traffic environment tables in all three technologies. See, for example, "EGPRSTrafficEnvironments Table"
on page 244.
userprofiles Table
Same structure as user profiles tables in all three technologies. See, for example, "EGPRSUserProfiles Table" on page 244.
333
334
Forsk 2011
AT310_AM_E2
335
Forsk 2011
336
AT310_AM_E2
337
Forsk 2011
Type
Description
Attributes
PHYSICAL_ANTENNA
Text (50)
CdmaCells Table
Field
Type
Description
Attributes
LOCKED_PNO
Boolean
CustomFields Table
Field
Type
Description
Attributes
CHOICE_TYPE
Integer
DLBearersSelection Table
Field
Type
Description
Attributes
MODULATION
Short
TplTransmitters Table
Field
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
MC_MODE_MUG
Memo
MC_MODE_UL_ECNT_MIN
Float
MULTI_CARRIER
Short
0=None; 1=Multi-Carrier
SHAREDMAST
Text (50)
Transmitters Table
Field
Type
Description
Attributes
MC_MODE_MUG
Memo
MC_MODE_UL_ECNT_MIN
Float
MULTI_CARRIER
Short
0=None; 1=Multi-Carrier
SHAREDMAST
Text (50)
338
AT310_AM_E2
ULBearersSelection Table
Field
Type
Description
Attributes
MODULATION
Short
UMTSServices Table
Field
Type
Description
Attributes
MIN_RATE_DL
Float
MIN_RATE_UL
Float
UMTSTerminals Table
Field
Type
Description
Attributes
HANDOFF_TYPE
Short
MODULATION
Short
NUM_CARRIERS_MAX
Short
Table
AntennasListsNames Table
Table
Neighbours Table
RANK
NeighboursConstraints Table
RANK
NeighboursConstraintsExt Table
RANK
NeighboursExt Table
RANK
TplTransmitters Table
COV_PROBA
Transmitters Table
COV_PROBA
339
Forsk 2011
Type
Description
Attributes
Beamwidth
Float
Antenna beamwidth
COMMENT_
Text
(255)
CONSTRUCTOR
Text (50)
DIAGRAM
Binary
ELECTRICAL_TILT
Float
FMax
Double
FMin
Double
GAIN
Float
NAME
Text (50)
Name of antenna
PHYSICAL_ANTENNA
Text (50)
The format of the binary field, DIAGRAM, is described in "RF 2D Antenna Pattern Format"
on page 105.
Type
Description
Attributes
CONFIG_DL_LOSSES
Float
CONFIG_UL_LOSSES
Float
NAME
Text (50)
NOISE_FIGURE
Float
RHO_FACTOR
Short
340
Field
Type
Description
Attributes
CARRIER
Integer
Carrier number
TYPE
Short
Carrier type
AT310_AM_E2
Type
Description
Attributes
ACTIVE
Boolean
BCMCS_RATE
Float
BCMCS_TS_PCT
Float
CARRIER
Integer
Carrier number
CCH_TS_PCT
Float
CELL_ID
Text (50)
CELL_IDENTITY
Integer
Cell identity
COMMENT_
Text
(255)
DOWNLINK_EXTERNAL_NOIS
E_RISE
Float
DRC_ER_RATE
Float
IDLE_POWER_GAIN
Float
LOCKED_PNO
Boolean
MAX_DL_LOAD
Float
MAX_EVDO_USERS
Integer
MAX_EXT_NEIGHB_NUMBER
Integer
MAX_INTERCAR_NEIGHB_NB
Integer
MAX_NEIGHB_NUMBER
Integer
MAX_UL_LOAD
Float
MUG_TABLE
Memo
PAGING_POWER
Float
PILOT_POWER
Float
PN_DOMAIN_NAME
Text (50)
PN_OFFSET
Integer
PN Offset.
POOLED_PWR
Float
Amount of power which can be borrowed in the BTS power pool (dB)
POWER_MAX
Float
Maximum downlink load allowed (percentage of max power used). Used Null column allowed: Yes
in power control simulation
Default value: 50
341
Forsk 2011
Field
Type
Description
Attributes
REUSE_DIST
Float
ROT_RANGE
Float
ROT_TARGET
Float
SYNCHRO_POWER
Float
TADD
Float
TDROP
Float
TOTAL_POWER
Float
TX_ID
Text (50)
UL_LOAD
Float
UPLINK_EXTERNAL_NOISE_R
ISE
Float
Type
Description
Attributes
CARRIER_SELECTION
Short
CE_SHARED_ALL_SECTORS
Boolean
CES_OVERHEAD_DL
Integer
CES_OVERHEAD_UL
Integer
MANUFACTURER
Text (50)
MUD_FACTOR
Float
NAME
Text (50)
Equipment name
RAKE_EFFICIENCY
Float
SPP
Boolean
(Sector Power Pooling) If True, sectors' powers available for TCH can be
shared among all co-site sectors
USE_NEIGHBOURS
Boolean
342
Field
Type
Description
Attributes
CHANNEL_ELTS_DL
Float
AT310_AM_E2
Field
Type
Description
Attributes
CHANNEL_ELTS_UL
Float
EQUIPMENT
Text (50)
TERMINAL
Text (50)
Type
Description
Attributes
CODE
Integer
Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768)
DATUM_CODE
Double
DATUM_ROTX
Double
Arc-seconds
DATUM_ROTY
Double
Arc-seconds
DATUM_ROTZ
Double
Arc-seconds
DATUM_SCALE
Double
DATUM_SHIFTX
Double
Meters
DATUM_SHIFTY
Double
Meters
DATUM_SHIFTZ
Double
Meters
ELLIPS_CODE
Integer
ELLIPS_RMAJOR
Double
Meters
ELLIPS_RMINOR
Double
Meters
NAME
Text (50)
PROJ_ANGLE
Double
Decimal degrees
PROJ_FALSE_EASTING
Double
Meters
PROJ_FALSE_NORTHING
Double
Meters
PROJ_FIRST_PARALLEL
Double
Decimal degrees
PROJ_LATITUDE_ORIGIN
Double
Decimal degrees
PROJ_LONGITUDE_ORIGIN
Double
Decimal degrees
Short
PROJ_METHOD
343
Forsk 2011
Field
Type
Description
Attributes
PROJ_SCALE_FACTOR
Double
PROJ_SECOND_PARALLEL
Double
Decimal degrees
PROJ_ZONE_NUMBER
Integer
Type
Description
Attributes
CAPTION
Text (50)
CHOICE_LIST
Memo
CHOICE_TYPE
Integer
COLUMN_NAME
Text (50)
DEFAULT_VALUE
Text (50)
GROUP_NAME
Text (50)
TABLE_NAME
Text (50)
See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.
Type
Description
Attributes
BEARER_INDEX
Short
CI_REQ
Float
EARLY_TERM_TABLE
Memo
MOBILITY
Text (50)
UE mobility
MODULATION
Short
NUM_SLOTS
Integer
RX_EQUIP
Text (50)
344
AT310_AM_E2
Field
Type
Description
Attributes
BEARER_INDEX
Short
RLC_PEAK_RATE
Float
TRANSPORT_BLOCK_SIZE
Integer
Type
Description
Attributes
BEARER_INDEX
Short
RLC_PEAK_RATE
Float
TRANSPORT_BLOCK_SIZE
Integer
Type
Description
Attributes
BEARER_INDEX
Short
PROBA
Float
SERVICE
Text (50)
Type
Description
Attributes
AUX_PILOT_GAIN
Float
BEARER_INDEX
Short
HC_T2P_GAIN
Float
LL_T2P_GAIN
Float
TERMINAL
Text (50)
Terminal name
Type
Description
Attributes
CONNECTOR_LOSSES_DL
Float
345
Forsk 2011
Field
Type
Description
Attributes
CONNECTOR_LOSSES_UL
Float
LOSS_PER_METER
Float
NAME
Text (50)
Name of Feeder
Type
Description
Attributes
BAND_WIDTH
Double
Bandwidth (MHz)
FIRST_CARRIER
Integer
FREQUENCY
Double
LAST_CARRIER
Integer
NAME
Text (50)
SPREADING_WIDTH
Double
Type
Description
Attributes
CARRIER1
Integer
First carrier
CARRIER2
Integer
Second carrier
FACTOR
Double
Type
Attributes
ICP
Memo
ITF_BW
Double
ITF_TECHNO
Text (50)
Interfering technology
V_BW
Double
346
Description
AT310_AM_E2
Field
Type
Description
Attributes
FORCE_HHO
Boolean
IMPORTANCE
Float
NEIGHBOUR
Text (50)
REASON
Integer
TRANSMITTER
Text (50)
TYPE
Text (50)
Type
Description
Attributes
FORCE_HHO
Boolean
IMPORTANCE
Float
NEIGHBOUR
Text (50)
STATUS
Integer
TRANSMITTER
Text (50)
Type
Description
Attributes
IMPORTANCE
Float
NEIGHBOUR
Text (50) Second part of the unique key. List of neighbours from another project.
STATUS
Integer
TRANSMITTER
Text (50)
Type
Description
Attributes
IMPORTANCE
Float
NEIGHBOUR
Text (50) Second part of the unique key. List of neighbours from another project
347
Forsk 2011
Field
Type
Description
Attributes
REASON
Integer
TRANSMITTER
Text (50)
TYPE
Text (50)
Type
Description
Attributes
ADD_MRC_SOFTERSOFT
Boolean
If true, gain due to MRC is taken into account for softer/soft cases
AS_PARAMS_IN_CELL
Boolean
If true, TADD and TDROP are considered defined in the cells table. If
false, these parameters are defined in the mobility type.
DEFAULT_HOGAIN_UL
Float
DEFAULT_MODEL
Text (50)
DEFAULT_ORTHO_FACTOR
Float
DEFAULT_RESOLUTION
Float
DMAX
Float
INTERFERERS_RX_THRESH
Float
IOISNTOT
Boolean
NAME
Text (50)
NTISNTOT
Boolean
POWERS_RELATIVE_TO_PILO
T
Boolean
Cell paging and Synchro powers, Service Allowed DL min and max TCH
powers are absolute values or relative to cell pilot power
PTOT_RELATIVE_TO_PMAX
Boolean
SHARED_RESULTS_FOLDER
Text
(255)
SPREADING_WIDTH
Float
SYSTEM_
Text (50)
TECHNOLOGY
Text (10)
UC_PWC_ON_PILOT
Boolean
348
AT310_AM_E2
Field
Type
Description
Attributes
DOMAIN_NAME
Text (50)
Type
Description
Attributes
DOMAIN_NAME
Text (50)
EXCLUDED
Text
(225)
List of codes to be excluded from the series defined by FIRST, LAST and
STEP (separated by blank character)
EXTRA
Text
(225)
FIRST
Integer
LAST
Integer
NAME
Text (50)
STEP
Integer
Type
Description
Attributes
Data
Binary
Description
Text
(255)
User defined
Name
Text (50)
Signature
Text (40)
Type
Text (50)
Type
Description
Attributes
CS_QI
Boolean
MEAS_PARAM
Short
NAME
Text (20)
PS_QI
Boolean
349
Forsk 2011
Field
Type
Description
Attributes
USE_INTERPOLATION
Boolean
Type
Description
Attributes
ADJ_CHANNEL_PROT
Float
ANTENNA
Text (50)
HEIGHT
Float
LOSS
Float
NAME
Text (50)
Receiver name
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
MANUFACTURER
Text (50)
MAX_AMPLIFIER_GAIN
Float
MAX_OUTPUT_DL
Float
MAX_OUTPUT_UL
Float
MIN_AMPLIFIER_GAIN
Float
NAME
Text (50)
NOISE_FIGURE
Float
STEP_AMPLIFIER_GAIN
Float
TIME_DELAY
Float
350
Type
Description
Attributes
AMPLIFIER_GAIN
Float
AZIMUT
Float
AT310_AM_E2
Field
Type
Description
Attributes
DONOR_CELLID
Text (50)
DONOR_LINK_LOSS
Float
DONOR_LINK_TYPE
Short
DONOR_PROPAG_MODEL
Text (50)
DOWNTILT
Float
EQUIPMENT_NAME
Text (50)
FEEDER_NAME
Text (50)
FEEDERLENGTH
Float
HEIGHT
Float
REC_ANTENNA
Text (50)
REC_FEEDERLENGTH_UL
Float
TOTAL_GAIN
Float
TOTAL_GAIN_UL
Float
TX_ID
Text (50)
Repeater properties are saved in two tables: the donor-side parameters are in the
Repeaters table and the coverage-side parameters in the Transmitters table.
Type
Description
Attributes
ANTENNA
Text (50)
AZIMUT
Float
PERCENT_POWER
Float
REDT
Float
TILT
Float
TX_ID
Text (50)
351
Forsk 2011
Field
Type
Description
Attributes
TX_ID
Text (50)
First part of the unique key. First cell name in a symmetric relation
TX_ID_OTHER
Text (50)
Type
Description
Attributes
DL_QI_TABLE
Memo
MOBILITY
Text (50)
UE mobility
QI_NAME
Text (50)
RX_EQUIP
Text (50)
SERVICE
Text (50)
UL_QI_TABLE
Memo
Type
Description
Attributes
ALTITUDE
Float
Real altitude
Unit: m
CDMA_EQUIPMENT
Text (50)
CHANNEL_ELEMENTS_DL
Integer
CHANNEL_ELEMENTS_UL
Integer
COMMENT_
Text
(255)
EVDO_CES
Integer
LATITUDE
Double
Y coordinate
LONGITUDE
Double
X coordinate
NAME
Text (50)
Site name
PYLON_HEIGHT
Float
SUPPORT_NATURE
Short
352
AT310_AM_E2
Field
Type
Description
Attributes
LIST_NAME
Text (50)
SITE_NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
DL_LOSSES
Float
NAME
Text (50)
NOISE_FIGURE
Float
UL_GAIN
Float
Type
Description
Attributes
ACTIVE
Boolean
ANTDIVGAIN
Float
ANTENNA_NAME
Text (50)
AZIMUT
Float
BCMCS_RATE
Float
BCMCS_TS_PCT
Float
BTS_NAME
Text (50)
CALC_RADIUS
Integer
CALC_RADIUS2
Integer
CALC_RESOLUTION
Integer
Calculation resolution
CALC_RESOLUTION2
Integer
353
Forsk 2011
Field
Type
Description
Attributes
CARRIERS
Text (50)
CCH_TS_PCT
Float
CDMA_EQUIPMENT
Text (50)
CDMA equipment
CELL_SIZE
Float
Hexagon radius
Unit: m
CHANNEL_ELEMENTS_DL
Integer
CHANNEL_ELEMENTS_UL
Integer
COMMENT_
Text
(255)
Comments
DOWNLINK_EXTERNAL_NOIS
E_RISE
Float
DRC_ER_RATE
Float
EVDO_CES
Integer
FBAND
Text (50)
Frequency band
FEEDER_NAME
Text (50)
FEEDERLENGTH_DL
Float
FEEDERLENGTH_UL
Float
HEIGHT
Float
IDLE_POWER_GAIN
Float
MAX_DL_LOAD
Float
MAX_EVDO_USERS
Integer
MAX_EXT_NEIGHB_NUMBER
Short
MAX_INTERCAR_NEIGHB_NB
Integer
MAX_NEIGHB_NUMBER
Short
MAX_UL_LOAD
Float
MC_MODE_MUG
Memo
MC_MODE_UL_ECNT_MIN
Float
MISCDLL
Float
MISCULL
Float
MUG_TABLE
Memo
354
Maximum downlink load allowed (percentage of max power used). Used Null column allowed: Yes
in power control simulation
Default value:
AT310_AM_E2
Field
Type
Description
Attributes
MULTI_CARRIER
Short
0=None; 1=Multi-Carrier
NAME
Text (50)
Template name
NOISE_FIGURE
Float
NUM_SECTORS
Integer
Number of sectors
PAGING_POWER
Float
PILOT_POWER
Float
PN_DOMAIN_NAME
Text (50)
POOLED_PWR
Float
Amount of power which can be borrowed in the BTS power pool (dB)
POWER_MAX
Float
PROPAG_MODEL
Text
(255)
PROPAG_MODEL2
Text
(255)
REDT
Float
REUSE_DIST
Float
ROT_RANGE
Float
ROT_TARGET
Float
RXLOSSES
Float
SHAREDMAST
Text (50)
SYNCHRO_POWER
Float
TADD
Float
TDROP
Float
TILT
Float
TMA_NAME
Text (50)
TOTAL_POWER
Float
TXLOSSES
Float
UL_LOAD
Float
UPLINK_EXTERNAL_NOISE_R
ISE
Float
355
Forsk 2011
Type
Description
Attributes
ACTIVE
Boolean
ANTDIVGAIN
Float
ANTENNA_NAME
Text (50)
AZIMUT
Float
BTS_NAME
Text (50)
CALC_RADIUS
Integer
CALC_RADIUS2
Integer
CALC_RESOLUTION
Integer
Calculation resolution
CALC_RESOLUTION2
Integer
CELL_SIZE
Float
Hexagon radius
Unit: m
COMMENT_
Text
(255)
DX
Float
DY
Float
FBAND
Text (50)
Frequency band
FEEDER_NAME
Text (50)
FEEDERLENGTH_DL
Float
Length of feeder in DL
FEEDERLENGTH_UL
Float
Length of feeder in UL
HEIGHT
Float
HEXAGON_GROUP
Text (50)
MC_MODE_MUG
Memo
MC_MODE_UL_ECNT_MIN
Float
MISCDLL
Float
Miscellaneous DL loss
MISCULL
Float
Miscellaneous UL loss
MULTI_CARRIER
Short
0=None; 1=Multi-Carrier
NOISE_FIGURE
Float
356
AT310_AM_E2
Field
Type
Description
Attributes
PROPAG_MODEL
Text
(255)
PROPAG_MODEL2
Text
(255)
REDT
Float
RXLOSSES
Float
SHAREDMAST
Text (50)
SITE_NAME
Text (50)
Name of the site on which the transmitter is located (from the Sites
table)
TILT
Float
TMA_NAME
Text (50)
TX_ID
Text (50)
Transmitter name
TXLOSSES
Float
Type
Description
Attributes
LIST_NAME
Text (50)
TX_NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
Type
Short
Description
Attributes
357
Forsk 2011
Field
Type
Description
Attributes
EARLY_TERM_TABLE
Memo
HC_ECNT_REQ
Float
LL_ECNT_REQ
Float
MOBILITY
Text (50)
UE mobility
MODULATION
Short
NUM_SUBFRAMES
Integer
RX_EQUIP
Text (50)
Type
Description
Attributes
DENSITY
Float
ENVIRONMENT
Text (50)
Environment name
MOBILITY
Text (50)
Type of mobility
USER_PROFILE
Text (50)
Description
Attributes
Type
COVERI_THROUGHPUTS
Memo
DELTA_TADD
Float
DELTA_TDROP
Float
NAME
Text (50)
Type of mobility
UL_ECNT_MIN
Float
358
Type
Float
Description
Attributes
Body loss
AT310_AM_E2
Field
Type
Description
Attributes
CARRIER
Integer
Carrier supporting the service. -1 means that all carriers can be used.
DLFCH_ACTIVITYFACTOR
Float
DLRATE_16
Float
DLRATE_2
Float
DLRATE_4
Float
DLRATE_8
Float
DOWN_153K6_76K8
Float
DOWN_19K2_9K6
Float
DOWN_38K4_19K2
Float
DOWN_76K8_38K4
Float
ENABLE_DOWNGRADING
Boolean
EVDO_ULRATE_1
Float
MIN_RATE_DL
Float
MIN_RATE_UL
Float
NAME
Text (50)
Service name
PRIORITY
Integer
QOS_CLASS
Short
TCP_ACK_CURVE
Memo
TCP_SERVICE
Boolean
TH_OFFSET
Float
TH_SCALE_FACTOR
Float
TYPE
Short
UL_OPERATION_MODE
Short
ULFCH_ACTIVITYFACTOR
Float
ULRATE_16
Float
ULRATE_2
Float
359
Forsk 2011
Field
Type
Description
Attributes
ULRATE_4
Float
ULRATE_8
Float
UP_19K2_38K4
Float
UP_38K4_76K8
Float
UP_76K8_153K6
Float
UP_9K6_19K2
Float
USE_HANDOFF
Boolean
Type
Description
Attributes
Eb/Nt target on the downlink for each type of (mobility, SCH rate) pair
DL_TARGET_QUAL
Float
FCH2PILOT
Float
MOBILITY
Text (50)
UE mobility
PTCH_MAX
Float
PTCH_MIN
Float
RX_EQUIP
Text (50)
Type of receiver
SCH_RATE
Integer
SCH2PILOT
Float
SERVICE
Text (50)
TERMINAL
Text (50)
UL_ECNT_MIN
Float
UL_TARGET_QUAL
Float
Eb/Nt target on the uplink for each type of (mobility, SCH rate) pair
FCH power to Pilot power gain. Used if global flag UL_PWC_ON_PILOT is Null column allowed: Yes
set to True
Default value: 0
SCH power to Pilot power gain. Used if global flag UL_PWC_ON_PILOT is Null column allowed: Yes
set to True
Default value: 0
360
Field
Type
Description
Attributes
CALL_DURATION
Float
CALL_NUMBER
Float
AT310_AM_E2
Field
Type
Description
Attributes
SERVICE
Text (50)
TERMINAL
Text (50)
USER_PROFILE
Text (50)
Type
Description
Attributes
ACK_GAIN
Float
ACK gain
ACK_GAIN_DORA
Float
ACTIVE_SET_SIZE
Short
DRC_GAIN_NOHO
Float
DRC_GAIN_NOHO_DORA
Float
DRC_GAIN_SOFT
Float
DRC_GAIN_SOFT_DORA
Float
DRC_GAIN_SOFTER
Float
DRC_GAIN_SOFTER_DORA
Float
FWD_BASEDATARATE
Float
GAIN
Float
HANDOFF_TYPE
Short
LOSS
Float
MODULATION
Short
NAME
Text (50)
Terminal name
NOISE_FACTOR
Float
NOISE_FACTOR_SEC
Float
Noise figure used to determine the thermal noise at the receiver (for
secondary frequency band)
NUM_CARRIERS_MAX
Short
PILOT_POWER_PCT
Float
PMAX
Float
PMIN
Float
Maximum number of transmitters possibly connected with the receiver Null column allowed: Yes
for the fundamental channel (FCH)
Default value: 6
361
Forsk 2011
Field
Type
Description
Attributes
PRIMARY_BAND
Text (50)
RAKE_EFFICIENCY
Float
RAKE_NUM_FINGERS
Short
REV_BASEDATARATE
Float
RHO_FACTOR
Short
RRI_GAIN_DORA
Float
RX_EQUIP
Text (50)
SCH_AS_SIZE
Short
SECONDARY_BAND
Text (50)
SUPPORTED_TECHNO
Short
TRAFFIC_GAIN_153_6
Float
TRAFFIC_GAIN_19_2
Float
TRAFFIC_GAIN_38_4
Float
TRAFFIC_GAIN_76_8
Float
TRAFFIC_GAIN_9_6
Float
Maximum number of transmitters possibly connected with the receiver Null column allowed: Yes
for the supplementary channel (SCH)
Default value: 3
Type
CLUTTER_WEIGHTS
Binary
NAME
Text (50)
Description
Attributes
Type
Description
Attributes
NAME
Text (50)
362
AT310_AM_E2
Field
Type
Description
Attributes
COORD_SYSTEM
Integer
GAIN_UNIT
Integer
PROJECTION
Integer
RECEPTION_UNIT
Integer
TRANSMISSION_UNIT
Integer
363
364
Forsk 2011
AT310_AM_E2
365
Forsk 2011
366
AT310_AM_E2
367
Forsk 2011
Type
Description
Attributes
PHYSICAL_ANTENNA
Text (50)
Field
Type
Description
Attributes
DYN_EDCH_DL_POWER_ALL
OC
Boolean
EDCH_DL_POWER
Float
HSPA_SUPPORT
Short
HSUPA_MAX_USERS
Integer
LOCKED_SC
Boolean
MAX_R99BEARER_DL_RATE
Float
MAX_R99BEARER_UL_RATE
Float
NUM_HSDPA_USERS
Integer
Number of served HSDPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes
simulation algorithm
Default value:
NUM_HSUPA_USERS
Integer
Number of served HSUPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes
simulation algorithm
Default value:
CdmaCells
CdmaCellsTS
Field
Type
Description
Attributes
HSUPA_UL_LOAD
Float
UL_REUSE_FACTOR
Float
Field
Type
Description
Attributes
CHOICE_TYPE
Integer
CustomFields
HSDPABearers
Field
Type
Description
Attributes
MODULATION
Short
HSUPABearers (New)
368
Field
Type
Description
Attributes
BEARER_INDEX
Short
AT310_AM_E2
Field
Type
Description
Attributes
EPUCH_NUM
Short
MODULATION
Short
RLC_PEAK_THROUGHPUT
Float
TRANSPORT_BL_SIZE
Integer
TS_NUM
Short
UE_CATEGORY
Short
Associated UE category
HSUPABearerSelection (New)
Field
Type
Description
Attributes
BEARER_INDEX
Short
EARLY_TERM_TABLE
Memo
EPUCH_ECNT_REQ
Float
MAX_NUM_REP
Integer
MOBILITY
Text (50)
Users mobility
RX_EQUIP
Text (50)
UL_CRT_MARGIN
Float
HSUPAUECategories (New)
Field
Type
Description
Attributes
MAX_BLOCK_SIZE
Integer
MAX_EPUCH_CODES
Short
MAX_EPUCH_TS
Integer
MODULATION
Short
UE_CATEGORY
Short
UE_CATEGORY_NAME
Text (50)
TplTransmitters
Field
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
DYN_EDCH_DL_POWER_ALL
OC
Boolean
EDCH_DL_POWER
Float
369
Forsk 2011
Field
Type
Description
Attributes
HSPA_SUPPORT
Short
HSUPA_MAX_USERS
Integer
MAX_R99BEARER_DL_RATE
Float
MAX_R99BEARER_UL_RATE
Float
NUM_HSDPA_USERS
Integer
Number of served HSDPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes
simulation algorithm
Default value:
NUM_HSUPA_USERS
Integer
Number of served HSUPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes
simulation algorithm
Default value:
SHAREDMAST
Text (50)
Field
Type
Description
Attributes
SHAREDMAST
Text (50)
Transmitters
UECategories
Field
Type
Description
Attributes
MODULATION
Short
UE_CATEGORY_NAME
Text (50)
UMTSMobility
Field
Type
Description
Attributes
EDCH_DL_ECNT
Float
Field
Type
Description
Attributes
ADPCH_ACTIVITY
Float
CARRIER_LIST
Text (50)
CARRIER_SUPPORT
Integer
EDPCH_ACTIVITY
Float
UMTSServices
UMTSTerminals
Field
Type
Description
Attributes
HSPA_SUPPORT
Short
HSUPA_UE_CATEGORY
Short
HSUPA UE category
370
AT310_AM_E2
ENABLE_HSDPA
PWC_LIMIT
SCH_POWER
CdmaCellsTS Table
UL_ANGULAR_LOADS
HSDPABearers Table
USE_16QAM
Networks Table
CQI_CPICH_BASED
Neighbours Table
RANK
NeighboursConstraints Table
RANK
NeighboursConstraintsExt Table
RANK
NeighboursExt Table
RANK
Sites Table
CHANNEL_ELEMENTS_DL
CHANNEL_ELEMENTS_UL
TplTransmitters Table
CHANNEL_ELEMENTS_DL
CHANNEL_ELEMENTS_UL
COV_PROBA
ENABLE_HSDPA
MAX_DL_LOAD
MAX_UL_LOAD
PWC_LIMIT
SCH_POWER
TOTAL_POWER
UL_LOAD
Transmitters Table
COV_PROBA
UECategories Table
ENABLE_16QAM
MIN_INTERTTI_NUM
UMTSServices Table
CARRIER
ENABLE_HSDPA
371
Forsk 2011
UMTSTerminals Table
ENABLE_HSDPA
Type
Description
Attributes
Beamwidth
Float
Antenna beamwidth
COMMENT_
Text
(255)
CONSTRUCTOR
Text (50)
DIAGRAM
Binary
ELECTRICAL_TILT
Float
FMax
Double
FMin
Double
GAIN
Float
NAME
Text (50)
Name of antenna
PHYSICAL_ANTENNA
Text (50)
The format of the binary field, DIAGRAM, is described in "RF 2D Antenna Pattern Format"
on page 105.
Type
Description
Attributes
ANTENNA_NAME
Text (50)
LIST_NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
372
AT310_AM_E2
Field
Type
Description
Attributes
CONFIG_DL_LOSSES
Float
CONFIG_UL_LOSSES
Float
NAME
Text (50)
NOISE_FIGURE
Float
RHO_FACTOR
Short
Type
Description
Attributes
ACTIVE
Boolean
CARRIER
Integer
Carrier number
CARRIER_TYPE
Short
CELL_ID
Text (50)
CELL_IDENTITY
Integer
Cell identity
COMMENT_
Text
(255)
DOWNLINK_EXTERNAL_NOIS
E_RISE
Float
DWPCH_POWER
Float
DYN_EDCH_DL_POWER_ALL
OC
Boolean
DYN_HS_SCCH_POWER_ALL
OC
Boolean
DYN_HS_SICH_POWER_ALLO
C
Boolean
DYN_HSDPA_POWER_ALLOC
Boolean
EDCH_DL_POWER
Float
HS_SCCH_POWER
Float
HSDPA_MAX_CODES
Short
HSDPA_MAX_USERS
Short
HSDPA_MIN_CODES
Short
HSDPA_PWR
Float
HSDPA_SCHEDULER_ALGO
Short
Scheduling algo used for HSDPA users. 0 = MAX C/I, 1 = Round Robin, 2 = Null column allowed: Yes
Proportional Fair.
Default value: 2
373
Forsk 2011
Field
Type
Description
Attributes
HSPA_SUPPORT
Short
HSUPA_MAX_USERS
Integer
LOCKED_SC
Boolean
MAX_EXT_NEIGHB_NUMBER
Integer
MAX_NEIGHB_NUMBER
Integer
MAX_R99BEARER_DL_RATE
Float
MAX_R99BEARER_UL_RATE
Float
NUM_HS_SCCH
Short
NUM_HS_SICH
Short
NUM_HSDPA_USERS
Integer
Number of served HSDPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes
simulation algorithm
Default value:
NUM_HSUPA_USERS
Integer
Number of served HSUPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes
simulation algorithm
Default value:
OTHERS_CCH_POWER
Float
Power on the other common channels for TS0 (S-CCPCH, FPACH, PICH)
PILOT_POWER
Float
POWER_MAX
Float
PWR_HEADROOM
Float
REQ_DL_RUS
Short
REQ_UL_RUS
Short
REUSE_DIST
Float
RSCP_COMP
Float
SC_DOMAIN_NAME
Text (50)
SCRAMBLING_CODE
Integer
Scrambling code.
TS_CONFIG
Integer
Timeslot configuration
(1-DUDDDDD; 2-DUUDDDD; 3-DUUUDDD; 4-DUUUUDD; 5-DUUUUUD;
6-DUUUUUU;)
TX_ID
Text (50)
UPLINK_EXTERNAL_NOISE_R
ISE
Float
374
AT310_AM_E2
Type
Description
Attributes
BLOCKED
Boolean
Allow to block the timeslot: 'Yes' means that the timeslot is blocked
CELL_ID
Text (50)
DL_ANGULAR_POWERS
Binary
HSDPA_MAX_CODES
Short
HSDPA_MIN_CODES
Short
HSDPA_PWR
Float
HSUPA_UL_LOAD
Float
MAX_DL_LOAD
Float
MAX_UL_LOAD
Float
OTHERS_CCH_POWER
Float
RU_OVERHEAD
Short
TIME_SLOT
Short
TIME_SLOT_TYPE
Short
TOTAL_POWER
Float
UL_LOAD
Float
UL_REUSE_FACTOR
Float
Type
Description
Attributes
MANUFACTURER
Text (50)
MCJD_FACTOR
Float
MUD_FACTOR
Float
NAME
Text (50)
Equipment name
375
Forsk 2011
Field
Type
Description
Attributes
CHANNEL_ELTS_DL
Integer
CHANNEL_ELTS_UL
Integer
EQUIPMENT
Text (50)
SERVICE
Text (50)
Type
Description
Attributes
CODES_LIST
Text
(255)
NAME
Text (50)
Type
Description
Attributes
CODE
Integer
Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768)
DATUM_CODE
Double
DATUM_ROTX
Double
Arc-seconds
DATUM_ROTY
Double
Arc-seconds
DATUM_ROTZ
Double
Arc-seconds
DATUM_SCALE
Double
DATUM_SHIFTX
Double
Meters
DATUM_SHIFTY
Double
Meters
DATUM_SHIFTZ
Double
Meters
ELLIPS_CODE
Integer
ELLIPS_RMAJOR
Double
Meters
ELLIPS_RMINOR
Double
Meters
NAME
Text (50)
PROJ_ANGLE
Double
Decimal degrees
PROJ_FALSE_EASTING
Double
Meters
376
AT310_AM_E2
Field
Type
Description
Attributes
PROJ_FALSE_NORTHING
Double
Meters
PROJ_FIRST_PARALLEL
Double
Decimal degrees
PROJ_LATITUDE_ORIGIN
Double
Decimal degrees
PROJ_LONGITUDE_ORIGIN
Double
Decimal degrees
PROJ_METHOD
Short
PROJ_SCALE_FACTOR
Double
PROJ_SECOND_PARALLEL
Double
Decimal degrees
PROJ_ZONE_NUMBER
Integer
Type
Description
Attributes
CAPTION
Text (50)
CHOICE_LIST
Memo
CHOICE_TYPE
Integer
COLUMN_NAME
Text (50)
DEFAULT_VALUE
Text (50)
GROUP_NAME
Text (50)
TABLE_NAME
Text (50)
See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.
Type
Description
Attributes
CONNECTOR_LOSSES_DL
Float
CONNECTOR_LOSSES_UL
Float
LOSS_PER_METER
Float
NAME
Text (50)
Name of Feeder
377
Forsk 2011
Type
Description
Attributes
BAND_WIDTH
Double
Bandwidth (MHz)
FIRST_CARRIER
Integer
FREQUENCY
Double
LAST_CARRIER
Integer
NAME
Text (50)
SPREADING_WIDTH
Double
Type
Description
Attributes
BEARER_INDEX
Short
HSPDSCH_NUM
Short
MODULATION
Short
RLC_PEAK_THROUGHPUT
Float
TRANSPORT_BL_SIZE
Integer
TS_NUM
Short
UE_CATEGORY
Short
Type
Description
Attributes
BEARER_INDEX
Short
Bearer index
HSPDSCH_ECNT_REQ
Float
MOBILITY
Text (50)
UE mobility
RX_EQUIP
Text (50)
18.17 HSUPABearers
For HSUPA bearers.
378
AT310_AM_E2
Field
Type
Description
Attributes
BEARER_INDEX
Short
EPUCH_NUM
Short
MODULATION
Short
RLC_PEAK_THROUGHPUT
Float
TRANSPORT_BL_SIZE
Integer
TS_NUM
Short
UE_CATEGORY
Short
Associated UE category
18.18 HSUPABearerSelection
For HSUPA bearer selection graphs.
Field
Type
Description
Attributes
BEARER_INDEX
Short
EARLY_TERM_TABLE
Memo
EPUCH_ECNT_REQ
Float
MAX_NUM_REP
Integer
MOBILITY
Text (50)
Users mobility
RX_EQUIP
Text (50)
UL_CRT_MARGIN
Float
18.19 HSUPAUECategories
For HSUPA UE categories.
Field
Type
Description
Attributes
MAX_BLOCK_SIZE
Integer
MAX_EPUCH_CODES
Short
MAX_EPUCH_TS
Integer
MODULATION
Short
UE_CATEGORY
Short
UE_CATEGORY_NAME
Text (50)
379
Forsk 2011
Type
Description
Attributes
CARRIER1
Integer
First carrier
CARRIER2
Integer
Second carrier
FACTOR
Double
Type
Description
Attributes
ICP
Memo
ITF_BW
Double
ITF_TECHNO
Text (50)
Interfering technology
V_BW
Double
Type
Description
Attributes
FORCE_HHO
Boolean
IMPORTANCE
Float
NEIGHBOUR
Text (50)
REASON
Integer
TRANSMITTER
Text (50)
TYPE
Text (50)
380
Field
Type
Description
Attributes
FORCE_HHO
Boolean
IMPORTANCE
Float
NEIGHBOUR
Text (50)
AT310_AM_E2
Field
Type
Description
Attributes
STATUS
Integer
TRANSMITTER
Text (50)
Type
Description
Attributes
IMPORTANCE
Float
NEIGHBOUR
Text (50) Second part of the unique key. List of neighbours from another project.
STATUS
Integer
TRANSMITTER
Text (50)
Type
Description
Attributes
IMPORTANCE
Float
NEIGHBOUR
Text (50) Second part of the unique key. List of neighbours from another project
REASON
Integer
TRANSMITTER
Text (50)
TYPE
Text (50)
Type
Description
Attributes
DEFAULT_MODEL
Text (50)
DEFAULT_RESOLUTION
Float
DMAX
Float
DWPTS_CHIPS_NUMBER
Integer
EBNT_QUALITY_TARGET
Boolean
FRAME_TIME
Short
Duration of a frame in ms
381
Forsk 2011
Field
Type
Description
Attributes
GUARD_PERIOD_CHIPS_NU
MBER
Float
HSDPA_NTISNTOT
Boolean
HSDPA only: Nt includes or not pilot's signal for HS-SCCH, HS-PDSCH and
CPICH for CQI determination
INTERFERERS_RX_THRESH
Float
MIDAMBLE_CHIPS_NUMBER
Float
NAME
Text (50)
NTISNTOT
Boolean
PILOT_PROCESSING_GAIN
Float
POWERS_RELATIVE_TO_PILO
T
Boolean
Cell Paging and Synchro powers, Service Allowed DL min and max TCH
powers are absolute values (False) or relative to cell pilot power (True)
PTS_GUARD_PERIOD_CHIPS_
NUMBER
Integer
SHARED_RESULTS_FOLDER
Text
(255)
SPREADING_FACTOR_MAX
Integer
SPREADING_FACTOR_MIN
Integer
SPREADING_WIDTH
Float
SUBFRAME_TIME
Short
Duration of a subframe in ms
SYSTEM_
Text (50)
TECHNOLOGY
Text (10)
TS_DATA_CHIPS_NUMBER
Float
TS_NUMBER
Integer
Number of TS in a subframe
UPPTS_CHIPS_NUMBER
Integer
382
Field
Type
Description
Attributes
Data
Binary
Description
Text
(255)
User defined
Name
Text (50)
Signature
Text (40)
Type
Text (50)
AT310_AM_E2
Type
Description
Attributes
CS_QI
Boolean
MEAS_PARAM
Short
NAME
Text (20)
PS_QI
Boolean
USE_INTERPOLATION
Boolean
Type
Description
Attributes
DL_NOMINAL_BIT_RATE
Float
DL_PG
Float
NAME
Text (50)
PTCH_MAX
Float
PTCH_MIN
Float
TS_DL
Short
TS_UL
Short
TYPE
Short
UL_NOMINAL_BIT_RATE
Float
UL_PG
Float
Type
Description
Attributes
ADJ_CHANNEL_PROT
Float
ANTENNA
Text (50)
HEIGHT
Float
LOSS
Float
383
Forsk 2011
Field
Type
Description
Attributes
NAME
Text (50)
Receiver name
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
MANUFACTURER
Text (50)
MAX_AMPLIFIER_GAIN
Float
MAX_OUTPUT_DL
Float
MAX_OUTPUT_UL
Float
MIN_AMPLIFIER_GAIN
Float
NAME
Text (50)
NOISE_FIGURE
Float
STEP_AMPLIFIER_GAIN
Float
TIME_DELAY
Float
Type
Description
Attributes
AMPLIFIER_GAIN
Float
AZIMUT
Float
DONOR_CELLID
Text (50)
DONOR_LINK_LOSS
Float
DONOR_LINK_TYPE
Short
DONOR_PROPAG_MODEL
Text (50)
DOWNTILT
Float
EQUIPMENT_NAME
Text (50)
FEEDER_NAME
Text (50)
FEEDERLENGTH
Float
384
AT310_AM_E2
Field
Type
Description
Attributes
HEIGHT
Float
REC_ANTENNA
Text (50)
REC_FEEDERLENGTH_UL
Float
TOTAL_GAIN
Float
TOTAL_GAIN_UL
Float
TX_ID
Text (50)
Repeater properties are saved in two tables: the donor-side parameters are in the
Repeaters table and the coverage-side parameters in the Transmitters table.
Type
Description
Attributes
ANGULAR_SPREAD
Short
CIGAIN_CDF
Memo
SA_NAME
Text (50)
Type
Description
Attributes
DOMAIN_NAME
Text (50)
Type
Description
Attributes
DOMAIN_NAME
Text (50)
EXCLUDED
Text
(225)
List of codes to be excluded from the series defined by FIRST, LAST and
STEP (separated by blank characters)
EXTRA
Text
(225)
FIRST
Integer
LAST
Integer
385
Forsk 2011
Field
Type
Description
Attributes
NAME
Text (50)
First part of the unique key. Name of the scrambling code group
STEP
Integer
Type
Description
Attributes
ANTENNA
Text (50)
AZIMUT
Float
PERCENT_POWER
Float
REDT
Float
TILT
Float
TX_ID
Text (50)
Type
Description
Attributes
TX_ID
Text (50)
First part of the unique key. First cell name in a symmetric relation
TX_ID_OTHER
Text (50)
Type
Description
Attributes
DL_QI_TABLE
Memo
MOBILITY
Text (50)
UE mobility
QI_NAME
Text (50)
RX_EQUIP
Text (50)
SERVICE
Text (50)
UL_QI_TABLE
Memo
386
AT310_AM_E2
Field
Type
Description
Attributes
DIRECTION
Short
Uplink or downlink
Choice list: 1=DL; 2=UL;
NB_SF1
Short
NB_SF16
Short
NB_SF2
Short
NB_SF4
Short
NB_SF8
Short
SERVICE
Text (50)
Service name
TS_RANK
Short
Type
Description
Attributes
ALTITUDE
Float
Real altitude
Unit: m
CDMA_EQUIPMENT
Text (50)
COMMENT_
Text
(255)
LATITUDE
Double
Y coordinate
LONGITUDE
Double
X coordinate
NAME
Text (50)
Site name
PYLON_HEIGHT
Float
SUPPORT_NATURE
Short
Type
Description
Attributes
LIST_NAME
Text (50)
SITE_NAME
Text (50)
387
Forsk 2011
Field
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
ADAPTIVE_PATTERN_DL
Text (50)
ADAPTIVE_PATTERN_UL
Text (50)
COMMENT_
Text
(255)
ELTS_NUMBER
Integer
Number of elements
GEOMETRY_TYPE
Integer
GOB_PATTERN
Text (50)
GOB_PATTERN_UL
Text (50)
INTER_ELTS_DIST
Integer
MODELLING_TYPE
Short
NAME
Text (50)
PROBA_THRESHOLD
Integer
SA_MODEL
Text (50)
Modelling Type: 0- Dedicated Model, 1- Ideal Beam Steering, 2- Grid Of Null column allowed: Yes
Beams, 3- Statistical
Default value: 0
Type
Description
Attributes
SA_DATA
Binary
SA_DESCRIPTION
Text (50)
SA_NAME
Text (50)
SA_SIGNATURE
Text (50)
SA_TYPE
Text (50)
388
AT310_AM_E2
Field
Type
Description
Attributes
DL_LOSSES
Float
NAME
Text (50)
NOISE_FIGURE
Float
UL_GAIN
Float
Type
Description
Attributes
ACTIVE
Boolean
ANTDIVGAIN
Float
ANTENNA_NAME
Text (50)
AZIMUT
Float
BTS_NAME
Text (50)
CALC_RADIUS
Integer
CALC_RADIUS2
Integer
CALC_RESOLUTION
Integer
Calculation resolution
CALC_RESOLUTION2
Integer
CARRIERS
Text (50)
CDMA_EQUIPMENT
Text (50)
CDMA equipment
CELL_SIZE
Float
Hexagon radius
Unit: m
COMMENT_
Text
(255)
Comments
DOWNLINK_EXTERNAL_NOIS
E_RISE
Float
DWPCH_POWER
Float
DYN_EDCH_DL_POWER_ALL
OC
Boolean
DYN_HS_SCCH_POWER_ALL
OC
Boolean
DYN_HS_SICH_POWER_ALLO
C
Boolean
DYN_HSDPA_POWER_ALLOC
Boolean
EDCH_DL_POWER
Float
389
Forsk 2011
Field
Type
Description
Attributes
FBAND
Text (50)
Frequency band
FEEDER_NAME
Text (50)
FEEDERLENGTH_DL
Float
FEEDERLENGTH_UL
Float
HEIGHT
Float
HS_SCCH_POWER
Float
HSDPA_MAX_CODES
Short
HSDPA_MAX_USERS
Short
HSDPA_MIN_CODES
Short
HSDPA_PWR
Float
HSDPA_SCHEDULER_ALGO
Short
Scheduling algo used for HSDPA users. 0=MAXC/I (MAx C/I), 1=RR
(Round Robin), 2=PF (Proportional Fair)
HSPA_SUPPORT
Short
HSUPA_MAX_USERS
Integer
MAX_EXT_NEIGHB_NUMBER
Short
MAX_NEIGHB_NUMBER
Short
MAX_R99BEARER_DL_RATE
Float
MAX_R99BEARER_UL_RATE
Float
MAX_RANGE
Integer
MIN_RANGE
Integer
MISCDLL
Float
MISCULL
Float
N_FREQUENCY
Boolean
N-frequency mode. 'Yes' means that the transmitter has one master
carrier and slaves carriers; otherwise all its carriers are standalone
NAME
Text (50)
Template name
NOISE_FIGURE
Float
NUM_HS_SCCH
Short
NUM_HS_SICH
Short
NUM_HSDPA_USERS
Integer
390
Number of served HSDPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes
simulation algorithm
Default value:
AT310_AM_E2
Field
Type
Description
Attributes
NUM_HSUPA_USERS
Integer
NUM_RX_ANTENNAS
Short
NUM_SECTORS
Integer
Number of sectors
NUM_TX_ANTENNAS
Short
OTHERS_CCH_POWER
Float
PILOT_POWER
Float
POWER_MAX
Float
PROPAG_MODEL
Text
(255)
PROPAG_MODEL2
Text
(255)
PWR_HEADROOM
Float
REDT
Float
REQ_DL_RUS
Integer
REQ_UL_RUS
Integer
REUSE_DIST
Float
RXLOSSES
Float
SA_NAME
Text (50)
SC_DOMAIN_NAME
Text (50)
SHAREDMAST
Text (50)
TILT
Float
TMA_NAME
Text (50)
TS_CONFIG
Float
TX_DIVERSITY_CFG
Integer
TX diversity configuration
0=No TX diversity; 1=TX div. open loop; 2=TX div. closed loop
TXLOSSES
Float
UPLINK_EXTERNAL_NOISE_R
ISE
Float
Number of served HSUPA users in the cell: calculated by the TD-SCDMA Null column allowed: Yes
simulation algorithm
Default value:
Name of the associated smart antenna (if empty, the standard antenna Null column allowed: Yes
is used)
Default value:
391
Forsk 2011
Field
Type
Description
Attributes
ACTIVE
Boolean
ANTDIVGAIN
Float
ANTENNA_NAME
Text (50)
AZIMUT
Float
BTS_NAME
Text (50)
CALC_RADIUS
Integer
CALC_RADIUS2
Integer
CALC_RESOLUTION
Integer
Calculation resolution
CALC_RESOLUTION2
Integer
CELL_SIZE
Float
Hexagon radius
Unit: m
COMMENT_
Text
(255)
DX
Float
DY
Float
FBAND
Text (50)
Frequency band
FEEDER_NAME
Text (50)
FEEDERLENGTH_DL
Float
Length of feeder in DL
FEEDERLENGTH_UL
Float
Length of feeder in UL
HEIGHT
Float
HEXAGON_GROUP
Text (50)
MAX_RANGE
Integer
MIN_RANGE
Integer
MISCDLL
Float
Miscellaneous DL loss
MISCULL
Float
Miscellaneous UL loss
N_FREQUENCY
Boolean
N-frequency mode. 'Yes' means that the transmitter has one master
carrier and slaves carriers; otherwise all its carriers are standalone
NOISE_FIGURE
Float
NUM_RX_ANTENNAS
Short
NUM_TX_ANTENNAS
Short
392
AT310_AM_E2
Field
Type
Description
Attributes
PROPAG_MODEL
Text
(255)
PROPAG_MODEL2
Text
(255)
REDT
Float
RXLOSSES
Float
SA_NAME
Text (50)
SHAREDMAST
Text (50)
SITE_NAME
Text (50)
Name of the site on which the transmitter is located (from the Sites
table)
TILT
Float
TMA_NAME
Text (50)
TX_DIVERSITY_CFG
Short
TX_ID
Text (50)
Transmitter name
TXLOSSES
Float
Name of the associated smart antenna (if empty, the standard antenna Null column allowed: Yes
is used)
Default value:
Type
Description
Attributes
LIST_NAME
Text (50)
TX_NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
MAX_BLOCK_SIZE
Integer
MAX_HSPDSCH_NUM
Short
MAX_HSPDSCH_TS
Short
393
Forsk 2011
Field
Type
Description
Attributes
MODULATION
Short
UE_CATEGORY
Short
UE_CATEGORY_NAME
Text (50)
Type
NAME
Text (50)
Description
Attributes
Type
Description
Attributes
DENSITY
Float
ENVIRONMENT
Text (50)
Environment name
MOBILITY
Text (50)
Type of mobility
USER_PROFILE
Text (50)
394
Type
Description
Attributes
DWPCH_QUALITY
Float
DWPCH_RSCP
Float
EDCH_DL_ECNT
Float
HSSCCH_ECNT
Float
HSSICH_ECNT
Float
MEAN_SPEED
Float
NAME
Text (50)
Type of mobility
RSCP_DROP
Float
RSCP_MIN
Short
TADD
Float
AT310_AM_E2
Field
Type
Description
Attributes
UPPCH_RSCP
Float
Type
Description
Attributes
ADPCH_ACTIVITY
Float
BODY_LOSS
Float
Body loss
CARRIER_LIST
Text (50)
CARRIER_SUPPORT
Integer
DL_ACTIVITY
Float
DL_DP
Float
DL_DPC
Float
Reading time (distance) between two packet calls (ms) on the downlink
DL_NPC
Integer
DL_PACKET_EFFICIENCY
Float
DL_SP
Integer
DL_SPC_MAX
Float
DL_SPC_MIN
Float
EDPCH_ACTIVITY
Float
NAME
Text (50)
Service name
PRIORITY
Integer
R99BEARER
Text (50)
REQ_AVERAGE_DL_RATE
Float
REQ_AVERAGE_UL_RATE
Float
REQ_MIN_DL_RATE
Float
REQ_MIN_UL_RATE
Float
TH_OFFSET
Float
TH_SCALE_FACTOR
Float
TYPE
Short
395
Forsk 2011
Field
Type
Description
Attributes
UL_ACTIVITY
Float
UL_DP
Float
UL_DPC
Float
Reading time (distance) between two packet calls (ms) on the uplink
UL_NPC
Integer
UL_PACKET_EFFICIENCY
Float
UL_SP
Integer
UL_SPC_MAX
Float
UL_SPC_MIN
Float
Type
Description
Attributes
DL_TARGET_QUAL
Float
DL_TGT_QUAL_DIVCLOSED
Float
DL_TGT_QUAL_DIVOPEN
Float
MOBILITY
Text (50)
RX_EQUIP
Text (50)
Type of receiver
SERVICE
Text (50)
TCH_THRESHOLD_DL
Short
TCH_THRESHOLD_UL
Short
UL_TARGET_QUAL
Float
UL_TGT_QUAL_DIV2RX
Float
UL_TGT_QUAL_DIV4RX
Float
396
Field
Type
Description
Attributes
CALL_DURATION
Float
CALL_NUMBER
Float
AT310_AM_E2
Field
Type
Description
Attributes
DL_VOLUME
Float
SERVICE
Text (50)
TERMINAL
Text (50)
UL_VOLUME
Float
USER_PROFILE
Text (50)
Type
Description
Attributes
CARRIER_NUMBER
Short
GAIN
Float
HSPA_SUPPORT
Short
HSSICH_POWER
Float
HSUPA_UE_CATEGORY
Short
HSUPA UE category
LOSS
Float
MUD_FACTOR
Float
NAME
Text (50)
Terminal name
NOISE_FACTOR
Float
PMAX
Float
PMIN
Float
RHO_FACTOR
Short
RX_EQUIP
Text (50)
UE_CATEGORY
Float
UPPCH_POWER
Float
Advanced Receiver Factor to model intra-cell interference reduction for Null column allowed: Yes
HSDPA terminals only
Default value: 0
Type
Description
Attributes
CLUTTER_WEIGHTS
Binary
397
Forsk 2011
Field
Type
Description
Attributes
NAME
Text (50)
Type
NAME
Text (50)
Description
Attributes
Type
Description
Attributes
COORD_SYSTEM
Integer
GAIN_UNIT
Integer
PROJECTION
Integer
RECEPTION_UNIT
Integer
TRANSMISSION_UNIT
Integer
398
AT310_AM_E2
399
Forsk 2011
400
AT310_AM_E2
Type
PHYSICAL_ANTENNA
Text (50)
Description
Attributes
CustomFields Table
Field
Type
CHOICE_TYPE
Integer
Description
Attributes
FrameConfigurations Table
Field
UL_SEGMENTATION
Type
Boolean
Description
Attributes
401
Forsk 2011
FrequencyBands Table
Field
Type
Description
Attributes
GUARD_BAND
Float
Type
Description
Attributes
MAX_CINR
Float
MOBILITY
Text (50)
MUG_TABLE
Memo
SCHEDULER_NAME
Text (30)
Neighbours Table
Field
Type
Description
Attributes
RELATION_TYPE
Short
Networks Table
Field
Type
Description
Attributes
BS_SELECTION
Short
PermutationZones Table
Field
Type
Description
Attributes
ULSC_GROUPS_SEG0
Text
(255)
ULSC_GROUPS_SEG1
Text
(255)
ULSC_GROUPS_SEG2
Text
(255)
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
MANUFACTURER
Text (50)
MAX_AMPLIFIER_GAIN
Float
MAX_OUTPUT_DL
Float
MAX_OUTPUT_UL
Float
MIN_AMPLIFIER_GAIN
Float
NAME
Text (50)
NOISE_FIGURE
Float
402
AT310_AM_E2
Field
Type
Description
Attributes
STEP_AMPLIFIER_GAIN
Float
TIME_DELAY
Float
Type
Description
Attributes
AMPLIFIER_GAIN
Float
AZIMUT
Float
DONOR_CELLID
Text (50)
DONOR_LINK_LOSS
Float
DONOR_LINK_TYPE
Short
DONOR_PROPAG_MODEL
Text (50)
DOWNTILT
Float
EQUIPMENT_NAME
Text (50)
FEEDER_NAME
Text (50)
FEEDERLENGTH
Float
HEIGHT
Float
REC_ANTENNA
Text (50)
REC_FEEDERLENGTH_UL
Float
TOTAL_GAIN
Float
TOTAL_GAIN_UL
Float
TX_ID
Text (50)
TplTransmitters Table
Field
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
NOISE_RISE_UL_SEG
Float
PI_DOMAIN_NAME
Text (50)
SHAREDMAST
Text (50)
403
Forsk 2011
Transmitters Table
Field
Type
Description
Attributes
SHAREDMAST
Text (50)
WCells Table
Field
Type
Description
Attributes
DL_ZONE_PB
Integer
DL_ZONE_PB_STATUS
Short
LOCKED_SEGMENT
Short
NOISE_RISE_UL_SEG
Float
PI_DOMAIN_NAME
Text (50)
UL_ZONE_PB
Integer
UL_ZONE_PB_STATUS
Short
Type
Description
Attributes
DOMAIN_NAME
Text (50)
Type
Description
Attributes
DOMAIN_NAME
Text (50)
EXCLUDED
Text
(225)
EXTRA
Text
(225)
FIRST
Integer
LAST
Integer
NAME
Text (50)
STEP
Integer
List of indexes to be excluded from the series defined by FIRST, LAST and Null column allowed: Yes
STEP (separated by blank characters)
Default value:
WServices Table
Field
Type
Description
Attributes
DL_LOWEST_BEARER
Short
UL_LOWEST_BEARER
Short
404
AT310_AM_E2
FORCE_HHO
NeighboursConstraints Table
FORCE_HHO
TplTransmitters Table
AAS_USAGE
ANTDIVGAIN
CHANNEL
CHANNEL_STATUS
COV_PROBA
PI_STATUS
PREAMBLE_INDEX
Transmitters Table
ANTDIVGAIN
COV_PROBA
Type
Description
Attributes
Beamwidth
Float
Antenna beamwidth
COMMENT_
Text
(255)
CONSTRUCTOR
Text
(255)
DIAGRAM
Binary
ELECTRICAL_TILT
Float
FMax
Double
FMin
Double
GAIN
Float
NAME
Text (50)
PHYSICAL_ANTENNA
Text (50)
The format of the binary field, DIAGRAM, is described in "RF 2D Antenna Pattern Format"
on page 105.
405
Forsk 2011
Field
Type
Description
Attributes
CONFIG_DL_LOSSES
Float
CONFIG_UL_LOSSES
Float
NAME
Text (50)
NOISE_FIGURE
Float
RHO_FACTOR
Short
Type
Description
Attributes
CODE
Integer
Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768)
DATUM_CODE
Double
DATUM_ROTX
Double
Arc-seconds
DATUM_ROTY
Double
Arc-seconds
DATUM_ROTZ
Double
Arc-seconds
DATUM_SCALE
Double
DATUM_SHIFTX
Double
Meters
DATUM_SHIFTY
Double
Meters
DATUM_SHIFTZ
Double
Meters
ELLIPS_CODE
Integer
ELLIPS_RMAJOR
Double
Meters
ELLIPS_RMINOR
Double
Meters
NAME
Text (50)
PROJ_ANGLE
Double
Decimal degrees
PROJ_FALSE_EASTING
Double
Meters
PROJ_FALSE_NORTHING
Double
Meters
PROJ_FIRST_PARALLEL
Double
Decimal degrees
PROJ_LATITUDE_ORIGIN
Double
Decimal degrees
PROJ_LONGITUDE_ORIGIN
Double
Decimal degrees
406
AT310_AM_E2
Field
Type
Description
Attributes
PROJ_METHOD
Short
PROJ_SCALE_FACTOR
Double
PROJ_SECOND_PARALLEL
Double
Decimal degrees
PROJ_ZONE_NUMBER
Integer
Type
Description
Attributes
CAPTION
Text (50)
CHOICE_LIST
Memo
CHOICE_TYPE
Integer
COLUMN_NAME
Text (50)
DEFAULT_VALUE
Text (50)
GROUP_NAME
Text (50)
TABLE_NAME
Text (50)
See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.
Type
Description
Attributes
CONNECTOR_LOSSES_DL
Float
CONNECTOR_LOSSES_UL
Float
LOSS_PER_METER
Float
NAME
Text (50)
Name of Feeder
Type
Description
Attributes
Short
407
Forsk 2011
Field
Type
Description
Attributes
NAME
Text (50)
PREAMBLE_N_USED
Short
SEGMENTATION
Boolean
UL_SEGMENTATION
Boolean
Type
Description
Attributes
ADJ_CHANNEL_PROT
Float
CHANNEL_WIDTH
Double
DL_FREQUENCY
Double
DUPLEXING_METHOD
Short
EXCLUDED_CHANNELS
Text
(255)
FIRST_CHANNEL
Short
GUARD_BAND
Float
LAST_CHANNEL
Short
NAME
Text (50)
SAMPLING_FACTOR
Float
UL_FREQUENCY
Double
Type
Attributes
ICP
Memo
ITF_BW
Double
ITF_TECHNO
Text (50)
Interfering technology
V_BW
Double
408
Description
AT310_AM_E2
Field
Type
Description
Attributes
MAX_CINR
Float
MOBILITY
Text (50)
MUG_TABLE
Memo
SCHEDULER_NAME
Text (30)
Type
Description
Attributes
IMPORTANCE
Float
Handover importance
NEIGHBOUR
Text (50)
Neighbour cell
REASON
Integer
RELATION_TYPE
Short
TRANSMITTER
Text (50)
Reference cell
TYPE
Text (50)
Type
Description
Attributes
IMPORTANCE
Float
Handover importance
NEIGHBOUR
Text (50)
Neighbour cell
STATUS
Integer
TRANSMITTER
Text (50)
Reference cell
Type
Description
Attributes
IMPORTANCE
Float
Handover importance
NEIGHBOUR
Text (50)
STATUS
Integer
TRANSMITTER
Text (50)
Reference cell
409
Forsk 2011
Type
Description
Attributes
IMPORTANCE
Float
Handover importance
NEIGHBOUR
Text (50)
Neighbour cell
REASON
Integer
TRANSMITTER
Text (50)
Reference cell
TYPE
Text (50)
Type
Description
Attributes
AMS_SEL_CRITERION
Short
AMS criterion
(0 - Preamble C/N; 1 - Preamble C/(I+N))
BS_SELECTION
Short
CELL_SELECTION
Short
CYCLIC_PREFIX
Short
DEFAULT_MODEL
Text (50)
DEFAULT_RESOLUTION
Float
DEFAULT_RTG
Float
DEFAULT_TTG
Float
DL_RATIO_FORMAT
Short
DL_SYM_DURATIONS_NB
Short
DL_UL_RATIO
Float
DMAX
Float
FIX_DL_OVERHEAD
Short
FIX_UL_OVERHEAD
Integer
FRAME_DURATION
Short
INTERFERERS_RX_THRESH
Float
410
AT310_AM_E2
Field
Type
Description
Attributes
N_DATA
Short
N_FFT
Short
N_SUBCHANNELS_CH
Short
N_USED
Short
NAME
Text (50)
Type of network
POWER_CONTROL_MARGIN
Float
PZ_SEL_CRITERION
Short
SHARED_RESULTS_FOLDER
Text
(255)
SYSTEM_
Text (50)
TECHNOLOGY
Text (10)
THERMAL_NOISE
Float
Thermal noise
UL_SYM_DURATIONS_NB
Short
VARIABLE_DL_OVERHEAD
Float
VARIABLE_UL_OVERHEAD
Float
Type
Description
Attributes
AUTO_ACTIVATE
Boolean
DIVERSITY_SUPPORT
Short
FRAME_CONFIG
Text (50)
MAX_DISTANCE
Float
Coverage limit for the zone in terms of maximum distance from the cell
MAX_SPEED
Float
Highest user speed that can use this permutation zone (km/h)
N_DATA
Short
N_SUBCHANNELS_CH
Short
N_USED
Short
PRIORITY
Short
QUALITY_THRESHOLD
Float
411
Forsk 2011
Field
Type
Description
Attributes
SC_GROUPS_SEG0
Short
SC_GROUPS_SEG1
Short
SC_GROUPS_SEG2
Short
SUBCHANNEL_ALLOC_MODE
Short
SUBFRAME
Short
ULSC_GROUPS_SEG0
Text
(255)
ULSC_GROUPS_SEG1
Text
(255)
ULSC_GROUPS_SEG2
Text
(255)
USED_SC_GROUPS
Short
ZONE_ID
Short
The secondary subchannel groups used by the segmented DL PUSC zone Null column allowed: Yes
(Obsolete)
Default value:
Zone identifier
Choice list: 0 to 7 for DL; 0 to 2 for UL;
Type
Description
Attributes
Data
Binary
Description
Text
(255)
User defined
Name
Text (50)
Signature
Text (40)
Type
Text (50)
Type
Description
Attributes
CS_QI
Boolean
Flag indicating whether the Quality Indicator is used for Voice (CS)
services
MEAS_PARAM
Short
NAME
Text (50)
PS_QI
Boolean
Flag indicating whether the Quality Indicator is used for Data (PS)
services
USE_INTERPOLATION
Boolean
412
AT310_AM_E2
Type
Description
Attributes
ANTENNA
Text (50)
HEIGHT
Float
LOSS
Float
NAME
Text (50)
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
MANUFACTURER
Text (50)
MAX_AMPLIFIER_GAIN
Float
MAX_OUTPUT_DL
Float
MAX_OUTPUT_UL
Float
MIN_AMPLIFIER_GAIN
Float
NAME
Text (50)
NOISE_FIGURE
Float
STEP_AMPLIFIER_GAIN
Float
TIME_DELAY
Float
Type
Description
Attributes
AMPLIFIER_GAIN
Float
AZIMUT
Float
DONOR_CELLID
Text (50)
DONOR_LINK_LOSS
Float
DONOR_LINK_TYPE
Short
413
Forsk 2011
Field
Type
Description
Attributes
DONOR_PROPAG_MODEL
Text (50)
DOWNTILT
Float
EQUIPMENT_NAME
Text (50)
FEEDER_NAME
Text (50)
FEEDERLENGTH
Float
HEIGHT
Float
REC_ANTENNA
Text (50)
REC_FEEDERLENGTH_UL
Float
TOTAL_GAIN
Float
TOTAL_GAIN_UL
Float
TX_ID
Text (50)
Repeater properties are saved in two tables: the donor-side parameters are in the
Repeaters table and the coverage-side parameters in the Transmitters table.
Type
Description
Attributes
BEARER_SELECTION
Short
NAME
Text (30)
QOS_BIAS_FACTOR
Float
SCHEDULING_METHOD
Short
TARGET_THROUGHPUT_DAT
A
Short
TARGET_THROUGHPUT_VOI
CE
Short
UL_BW_ALLOCATION
Short
Bearer Selection Criterion: 0 Bearer Index; 1 Peak MAC Throughput; Null column allowed: Yes
2 Effective MAC Throughput
Default value: 0
0 = Proportional Fair; 1 = Proportional Demand; 2 = Biased (QoS Class); 3 Null column allowed: Yes
= Max Aggregate Throughput
Default value: 0
414
Type
Description
Attributes
Text (50)
AT310_AM_E2
Field
Type
Description
Attributes
AZIMUT
Float
PERCENT_POWER
Float
REDT
Float
TILT
Float
TX_ID
Text (50)
Transmitter name
Type
Description
Attributes
ALTITUDE
Float
COMMENT_
Text
(255)
LATITUDE
Double
Y coordinate
LONGITUDE
Double
X coordinate
NAME
Text (50)
Site name
PYLON_HEIGHT
Float
SUPPORT_NATURE
Short
Type
Description
Attributes
LIST_NAME
Text (50)
SITE_NAME
Text (50)
Type
Text (50)
Description
Attributes
415
Forsk 2011
Type
Description
Attributes
BROADCAST_ANTENNA
Text (50)
COMMENT_
Text
(255)
Comments
NAME
Text (50)
SA_MODEL
Text (50)
Type
Description
Attributes
SA_DATA
Binary
SA_DESCRIPTION
Text (50)
SA_NAME
Text (50)
SA_SIGNATURE
Text (50)
SA_TYPE
Text (50)
Type
Description
Attributes
DL_LOSSES
Float
NAME
Text (50)
NOISE_FIGURE
Float
UL_GAIN
Float
416
Field
Type
Description
Attributes
ACTIVE
Boolean
AMS_THRESHOLD
Float
ANTENNA_NAME
Text (50)
AZIMUT
Float
AT310_AM_E2
Field
Type
Description
Attributes
BTS_NAME
Text (50)
CALC_RADIUS
Integer
CALC_RADIUS2
Integer
CALC_RESOLUTION
Integer
Calculation resolution
CALC_RESOLUTION2
Integer
CELL_SIZE
Float
CHANNEL_LIST
Text(255)
COMMENT_
Text
(255)
Comments
DL_LOAD
Float
DOWNLINK_EXTERNAL_NOIS
E_RISE
Float
FBAND
Text (50)
FEEDER_NAME
Text (50)
FEEDERLENGTH_DL
Float
FEEDERLENGTH_UL
Float
FRAME_CONFIG
Text (50)
HEIGHT
Float
IDLE_PILOT_POWER_OFFSET
Float
MAX_DL_LOAD
Float
MAX_EXT_NEIGHB_NUMBER
Integer
MAX_NEIGHB_NUMBER
Integer
MAX_NUMBER_OF_USERS
Integer
MAX_UL_LOAD
Float
MIMO_RX_ANTENNAS
Short
MIMO_TX_ANTENNAS
Short
MISCDLL
Float
MISCULL
Float
NAME
Text (50)
Template name
Calculation radius used to define each transmitter calculation area Unit: Null column allowed: Yes
m
Default value:
Defines the subchannel, subcarrier, and permutation zone configuration Null column allowed: Yes
used at the cell
Default value:
417
Forsk 2011
Field
Type
Description
Attributes
NOISE_FIGURE
Float
NOISE_RISE_UL
Float
NOISE_RISE_UL_SEG
Float
NUM_SECTORS
Integer
Number of sectors
PI_DOMAIN_NAME
Text (50)
PI_LIST
Text(255)
PI_REUSE_MIN_DIST
Float
The minimum reuse distance for the AFP and preamble index allocation
PILOT_POWER_OFFSET
Float
POWER
Float
PREAMBLE_QUALITY_THRES
Float
PROPAG_MODEL
Text
(255)
PROPAG_MODEL2
Text
(255)
REDT
Float
RXLOSSES
Float
SA_NAME
Text (50)
SCHEDULER
Text (30)
SEGMENTATION_USAGE
Float
SHAREDMAST
Text (50)
TILT
Float
TMA_NAME
Text (50)
TRAFFIC_POWER_OFFSET
Float
TX_TYPE
Short
TXLOSSES
Float
UL_LOAD
Float
UL_MU_SM_GAIN
Float
UPLINK_EXTERNAL_NOISE_R
ISE
Float
WEQUIPMENT
Text (50)
Cell equipment
418
AT310_AM_E2
Type
Description
Attributes
ACTIVE
Boolean
ANTENNA_NAME
Text (50)
AZIMUT
Float
BTS_NAME
Text (50)
CALC_RADIUS
Integer
CALC_RADIUS2
Integer
CALC_RESOLUTION
Integer
Calculation resolution
CALC_RESOLUTION2
Integer
CELL_SIZE
Float
COMMENT_
Text
(255)
DX
Float
DY
Float
FEEDER_NAME
Text (50)
FEEDERLENGTH_DL
Float
FEEDERLENGTH_UL
Float
HEIGHT
Float
HEXAGON_GROUP
Text (50)
MIMO_RX_ANTENNAS
Short
MIMO_TX_ANTENNAS
Short
MISCDLL
Float
MISCULL
Float
NOISE_FIGURE
Float
POLARIZATION
Text (1)
PROPAG_MODEL
Text (50)
PROPAG_MODEL2
Text (50)
419
Forsk 2011
Field
Type
Description
Attributes
REDT
Float
RXLOSSES
Float
SA_NAME
Text (50)
SHAREDMAST
Text (50)
SITE_NAME
Text (50)
Name of the site at which the transmitter is located (from the Sites
table)
TILT
Float
TMA_NAME
Text (50)
TX_ID
Text (50)
Transmitter name
TX_TYPE
Short
TXLOSSES
Float
Type
Description
Attributes
LIST_NAME
Text (50)
TX_NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
COORD_SYSTEM
Integer
GAIN_UNIT
Integer
PROJECTION
Integer
RECEPTION_UNIT
Integer
TRANSMISSION_UNIT
Integer
420
AT310_AM_E2
Type
Description
Attributes
BEARER_INDEX
Short
Bearer index
MOBILITY
Text (50)
Mobility type
QI_CURVE
Memo
QI_NAME
Text (50)
RX_EQUIP
Text (50)
Type
Description
Attributes
BEARER_INDEX
Short
CODING_RATE
Float
Coding rate
MODULATION
Short
Modulation type
Choice list: 0=BPSK; 1=QPSK; 2=16QAM; 3=64QAM;
NAME
Text (50)
SPECTRAL_EFFICIENCY
Float
Type
Description
Attributes
BEARERS_REQUIRED_COVERI
Memo
MOBILITY
Text (50)
CPE mobility
RX_EQUIP
Text (50)
Type
Description
Attributes
AAS_RESULTS
Binary
AAS_USAGE
Float
ACTIVE
Boolean
AMS_THRESHOLD
Float
421
Forsk 2011
Field
Type
Description
Attributes
BSID
Text (50)
CELL_ID
Text (50)
CHANNEL
Integer
Channel number
CHANNEL_STATUS
Short
COMMENT_
Text
(255)
DL_LOAD
Float
DL_ZONE_PB
Integer
DL_ZONE_PB_STATUS
Short
DOWNLINK_EXTERNAL_NOIS
E_RISE
Float
FBAND
Text (50)
FRAME_CONFIG
Text (50)
IDLE_PILOT_POWER_OFFSET
Float
Offset (in dB) with respect to the preamble power for determining the
pilot power during the empty part of the frame
LOCKED_SEGMENT
Short
MAX_DL_LOAD
Float
MAX_EXT_NEIGHB_NUMBER
Integer
MAX_NEIGHB_NUMBER
Integer
MAX_NUMBER_OF_USERS
Integer
MAX_UL_LOAD
Float
NOISE_RISE_UL
Float
NOISE_RISE_UL_SEG
Float
PI_DOMAIN_NAME
Text (50)
PI_REUSE_MIN_DIST
Float
The minimum reuse distance for the AFP and preamble index allocation
PI_STATUS
Short
PILOT_POWER_OFFSET
Float
Offset (in dB) with respect to the preamble power for determining the
pilot power during the loaded part of the frame
POWER
Float
PREAMBLE_INDEX
Integer
PREAMBLE_QUALITY_THRES
Float
422
Defines the subchannel, subcarrier, and permutation zone configuration Null column allowed: Yes
used at the cell
Default value:
AT310_AM_E2
Field
Type
Description
Attributes
RANK
Short
SCHEDULER
Text (30)
SEGMENTATION_USAGE
Float
TRAFFIC_POWER_OFFSET
Float
Offset (in dB) with respect to the preamble power for determining the
traffic power
TX_ID
Text (50)
UL_LOAD
Float
UL_MU_SM_GAIN
Float
UL_ZONE_PB
Integer
UL_ZONE_PB_STATUS
Short
UPLINK_EXTERNAL_NOISE_R
ISE
Float
WEQUIPMENT
Text (50)
Type
Description
Attributes
DENSITY
Float
ENVIRONMENT
Text (50)
Environment name
MOBILITY
Text (50)
Type of mobility
USER_PROFILE
Text (50)
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
BEARER_INDEX
Short
MAX_BLER
Float
423
Forsk 2011
Field
Type
Description
Attributes
MAX_MIMO_GAIN
Memo
MIMO_RX_ANTENNAS
Short
MIMO_TX_ANTENNAS
Short
MOBILITY
Text (50)
User mobility
STTD_GAIN
Float
SUBCHANNEL_ALLOC_MODE
Short
WEQUIPMENT
Text (50)
Type
Description
Attributes
MEAN_SPEED
Float
NAME
Text (50)
Type of mobility
Type
Description
Attributes
DOMAIN_NAME
Text (50)
424
Type
Description
Attributes
DOMAIN_NAME
Text (50)
EXCLUDED
Text
(225)
EXTRA
Text
(225)
FIRST
Integer
LAST
Integer
NAME
Text (50)
STEP
Integer
List of indexes to be excluded from the series defined by FIRST, LAST and Null column allowed: Yes
STEP (separated by blank characters)
Default value:
AT310_AM_E2
Type
Description
Attributes
BODY_LOSS
Float
DL_ACTIVITY
Float
DL_DP
Float
DL_DPC
Float
DL_HIGHEST_BEARER
Float
DL_LOWEST_BEARER
Short
DL_MAXIMUM_LATENCY
Float
DL_MRTR
Float
DL_MSTR
Float
DL_NPC
Integer
DL_SP
Integer
DL_SPC_MAX
Float
DL_SPC_MIN
Float
MAXIMUM_BLOCKING_PRO
BA
Integer
NAME
Text (50)
Service name
PRIORITY
Short
QOS_CLASS
Short
Quality of Service class (In order of priority defined by the IEEE 802.16
standard)
Choice list: 0=UGS; 1=rtPS; 2=ErtPS; 3=nrtPS; 4=Best Effort;
REQ_AVERAGE_DL_RATE
Float
REQ_AVERAGE_UL_RATE
Float
TH_OFFSET
Float
TH_SCALE_FACTOR
Float
TYPE
Short
Service type
Choice list: 0=Voice; 1=Data;
UL_ACTIVITY
Float
UL_DP
Float
UL_DPC
Float
425
Forsk 2011
Field
Type
Description
Attributes
UL_HIGHEST_BEARER
Float
UL_LOWEST_BEARER
Short
UL_MAXIMUM_LATENCY
Float
UL_MRTR
Float
UL_MSTR
Float
UL_NPC
Integer
UL_SP
Integer
UL_SPC_MAX
Float
UL_SPC_MIN
Float
Type
Description
Attributes
CALL_DURATION
Float
CALL_NUMBER
Float
DL_VOLUME
Float
SERVICE
Text (50)
Service (from the Service table) that the subscriber may request
TERMINAL
Text (50)
Type of terminal (from the Terminal table) used by the subscriber for
the service
UL_VOLUME
Float
USER_PROFILE
Text (50)
Type
Description
Attributes
ANTENNA
Text (50)
DIVERSITY_SUPPORT
Short
GAIN
Float
LOSS
Float
MIMO_RX_ANTENNAS
Short
426
AT310_AM_E2
Field
Type
Description
Attributes
MIMO_TX_ANTENNAS
Short
NAME
Text (50)
Terminal name
NOISE_FACTOR
Float
Noise figure used to determine the thermal noise at the receiver (dB)
PMAX
Float
PMIN
Float
RX_EQUIP
Text (50)
Type
Description
Attributes
CLUTTER_WEIGHTS
Binary
NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
427
428
Forsk 2011
AT310_AM_E2
Type
CHOICE_TYPE
Integer
Description
Attributes
MWAntennas Table
Field
Type
RADOME_LOSS
Float
Description
Attributes
Radome loss to take into account when radomes are used on links
Type
Description
Attributes
FREQ_DIVERSITY
Boolean
HSB
Boolean
NAME
Text (50)
SPACE_DIVERSITY
Boolean
SYSTEM_CONFIG_M
Short
SYSTEM_CONFIG_N
Short
XPIC
Boolean
Type
Description
Attributes
AIR_LINK_RATE
Float
Data rate
NAME
Text (50)
Capacity name
MWEPO Table
Field
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
MAXIMUM_LENGTH
Double
MINIMUM_LENGTH
Double
429
Forsk 2011
MWEquipments Table
Field
Type
Description
Attributes
ACM_MODE
Short
CHANNEL_SPACING
Text (50)
DFM
Memo
EMISSION_DESIGNATOR
Text (20)
Normalized designator
FAMILY
Text (50)
Family name
MIN_PHASE_SIG_DEPTH
Memo
MIN_PHASE_SIG_WIDTH
Memo
NON_MIN_PHASE_SIG_DEPT
H
Memo
NON_MIN_PHASE_SIG_WID
TH
Memo
RX_OVERFLOW
Memo
Curve which defines the thresholds max value for any value of BER
WITH_EQUALIZER
Boolean
Used to calculate Kn
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
MANUFACTURER
Text (50)
Manufacturer name
NAME
Text (50)
Family name
Type
Description
Attributes
ACM_MODE
Integer
FAMILY
Text (50)
Family name
FREQ_BAND
Text (50)
Frequency band
Type
Description
Attributes
BRANCHING_CONFIG
Text (50)
FAMILY
Text (50)
Family name
430
AT310_AM_E2
Field
Type
Description
Attributes
FREQ_BAND
Text (50)
Frequency band
RX_BRLOSS
Float
RX_STANDBY_LOSS
Float
TX_BRLOSS
Float
Transmission loss
Type
Description
Attributes
CHANNEL_SPACING
Text (50)
FAMILY
Text (50)
Family name
FREQ_BAND
Text (50)
Frequency band
XS
Double
Type
Description
Attributes
ACM_MODE
Short
ATPC_MAX
Float
ATPC_STEP
Float
ATPC interval
DISCRETE_POWERS
Text
(255)
FAMILY
Text (50)
Family name
FREQ_BAND
Text (50)
Frequency bands
MAX_POWER
Float
Maximum power
MODULATION
Text (20)
Modulation
STD_POWER
Float
Standard power
MWLinks Table
Field
Type
Description
Attributes
ACTIVE_MODULATIONS_A
Text
(100)
ACTIVE_MODULATIONS_B
Text
(100)
BRANCHING_CONFIG_A
Text (50)
Branching configuration at A
BRANCHING_CONFIG_B
Text (50)
Branching configuration at B
RADOME_ON_A
Boolean
431
Forsk 2011
Field
Type
Description
Attributes
RADOME_ON_B
Boolean
RADOME2_ON_A
Boolean
RADOME2_ON_B
Boolean
RAIN_ZONE
Short
Rain zone
REFRACTIVITY_KE
Float
N-units /km
TERRAIN_TYPE
Integer
USE_STD_POWER_A
Boolean
USE_STD_POWER_B
Boolean
MWLinkTypes Table
Field
Type
Description
Attributes
TYPE
Short
Type
Description
Attributes
EB_N0
Memo
Eb/No graph
FULL_NAME
Text
(255)
Comments
NAME
Text (20)
Modulation
NSTATES
Integer
MWTplLinks Table
Field
Type
Description
Attributes
BRANCHING_CONFIG_A
Text (50)
Branching configuration at A
BRANCHING_CONFIG_B
Text (50)
Branching configuration at B
RAIN_ZONE
Short
Rain zone
REFRACTIVITY_KE
Float
N-units /km
TERRAIN_TYPE
Integer
432
Table
Field
Modification
MWEquipments
CAPACITY
AT310_AM_E2
Table
MWEquipments Table
ATPC_MAX
BM
BNM
EQ_TYPE
HSB
INCR_PORT_RX_LOSS
INCR_PORT_TX_LOSS
MANUF_CHANNEL_SPACING
MANUFACTURER
POWER
SYSTEM_CONFIG_M
SYSTEM_CONFIG_N
THRESHOLD_MAX
WM
WNM
MWLinks Table
DIVERSITY_A
DIVERSITY_B
XPIC
XPIC_B
MWLinkTypes Table
SDH
MWPorts Table
HSB
Remarks
MANUFACTURER
EQ_TYPE
CAPACITY
MODULATION
No change
433
Forsk 2011
Remarks
POWER
ATPC_MAX
THRESHOLD_MAX
WM
MIN_PHASE_SIG_WIDTH
field of the MWEquipments
table
WNM
MIN_PHASE_SIG_DEPTH
field of the MWEquipments
table
BM
BNM
SYSTEM_CONFIG_N
SYSTEM_CONFIG_N field of
the MWBranchingConfigs
table
SYSTEM_CONFIG_M
CI_MIN_BER3
No change
Obsolete
CI_MIN_BER6
No change
Obsolete
IFM
No change
Obsolete
MANUF_CHANNEL_SPACING
CHANNEL_SPACING field of
the MWEquipments table
MWLinks Table
434
Remarks
DIVERSITY_A
DIVERSITY_B
XPIC
XPIC_B
AT310_AM_E2
MWLinkTypes Table
Atoll 2.8 Field
Remarks
SDH
The TYPE field replaces the SDH field in order to have more than two possible
values. SDH False = TYPE 0 (PDH); SDH True = TYPE 1 (SDH); TYPE 2 (IP);
Type
Description
Attributes
CODE
Integer
Identification number of the coordinate system (the code of userdefined coordinate systems is an integer higher than 32768)
DATUM_CODE
Double
DATUM_ROTX
Double
Arc-seconds
DATUM_ROTY
Double
Arc-seconds
DATUM_ROTZ
Double
Arc-seconds
DATUM_SCALE
Double
DATUM_SHIFTX
Double
Meters
DATUM_SHIFTY
Double
Meters
DATUM_SHIFTZ
Double
Meters
ELLIPS_CODE
Integer
ELLIPS_RMAJOR
Double
Meters
ELLIPS_RMINOR
Double
Meters
NAME
Text (50)
PROJ_ANGLE
Double
Decimal degrees
PROJ_FALSE_EASTING
Double
Meters
PROJ_FALSE_NORTHING
Double
Meters
PROJ_FIRST_PARALLEL
Double
Decimal degrees
PROJ_LATITUDE_ORIGIN
Double
Decimal degrees
PROJ_LONGITUDE_ORIGIN
Double
Decimal degrees
PROJ_METHOD
Short
PROJ_SCALE_FACTOR
Double
435
Forsk 2011
Field
Type
Description
Attributes
PROJ_SECOND_PARALLEL
Double
Decimal degrees
PROJ_ZONE_NUMBER
Integer
Type
Description
Attributes
CAPTION
Text (50)
CHOICE_LIST
Memo
CHOICE_TYPE
Integer
COLUMN_NAME
Text (50)
DEFAULT_VALUE
Text (50)
GROUP_NAME
Text (50)
TABLE_NAME
Text (50)
See "Tables and Fields" on page 130 for recommendations and information on user-defined fields.
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
DIAMETER
Float
FREQ_BAND
Text (50)
GAIN
Float
Antenna gain
MANUFACTURER
Text (50)
NAME
Text (50)
PATTERN
Binary
RADOME_LOSS
Float
Radome loss to take into account when radomes are used on links
The format of the binary field, PATTERN, is described in "Microwave 2D Antenna Pattern
Format" on page 107.
436
AT310_AM_E2
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
FMAX
Double
Maximum frequency
FMIN
Double
Minimum frequency
NAME
Text (50)
Type
Description
Attributes
FREQ_DIVERSITY
Boolean
HSB
Boolean
NAME
Text (50)
SPACE_DIVERSITY
Boolean
SYSTEM_CONFIG_M
Short
SYSTEM_CONFIG_N
Short
XPIC
Boolean
Type
Description
Attributes
AIR_LINK_RATE
Float
Data rate
NAME
Text (50)
Capacity name
Type
Description
Attributes
ANTENNA
Text (50)
COMMENT_
Text
(255)
Comments
EQUIPMENT
Text (50)
437
Forsk 2011
Type
Description
Attributes
ANTENNA
Text (50)
COMMENT_
Text
(255)
Comments
GUIDE
Text (50)
Type
Description
Attributes
BANDWIDTH
Float
Channel bandwidth
CURVE_TYPE
Short
FREQ_BAND
Text (50)
Frequency band
INTERFERED
Text (50)
MANUFACTURER
Text (50)
Manufacturer
MODULATION
Text (20)
Modulation used
NAME
Text (50)
RATE
Float
Rate (Mbps)
VALUES_
Memo
Curve values
438
Type
Description
Attributes
Double
Double
COMMENT_
Text
(255)
Comments
EPO_PARAM
Text (5)
EPO_TYPE
Text (1)
LINK_CLASS
Text (50)
MAXIMUM_LENGTH
Double
AT310_AM_E2
Field
Type
Description
Attributes
MINIMUM_LENGTH
Double
NAME
Text (50)
EPO name
RATE_MAX
Float
RATE_MIN
Float
REC_UIT
Float
ITU Recommendations
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
LINK_CLASS
Text (5)
LINK_SUBCLASS
Text (5)
LMAX
Float
LMIN
Float
NAME
Text (50)
Type
Description
Attributes
ACM_MODE
Short
CAPACITY
Text (50)
Equipment capacity
CHANNEL_SPACING
Text (50)
CI_MIN_BER3
Float
CI_MIN_BER6
Float
DFM
Memo
EMISSION_DESIGNATOR
Text (20)
Normalized designator
FAMILY
Text (50)
Family name
FREQ_BAND
Text (50)
HSB_DELAY
Float
439
Forsk 2011
Field
Type
Description
Attributes
IFM
Float
KN
Float
Kn parameter
MIN_PHASE_SIG_DEPTH
Memo
MIN_PHASE_SIG_WIDTH
Memo
MODULATION
Text (20)
Modulation type
MTBF
Float
NAME
Text (50)
NF
Float
NON_MIN_PHASE_SIG_DEPT
H
Memo
NON_MIN_PHASE_SIG_WID
TH
Memo
RX_LOSS_PHYS
Float
RX_OVERFLOW
Memo
Curve which defines the thresholds max value for any value of BER
RX_PORT_1
Float
RX_PORT_2
Float
RX_PORT_3
Float
RX_PORT_4
Float
RX_PORT_5
Float
RX_PORT_6
Float
RX_PORT_7
Float
RX_PORT_8
Float
RX_PORT_9
Float
RX_PORT_10
Float
RX_SELECTIVITY
Memo
RX_SENSITIVITY
Memo
TI_CURVE
Memo
T/I curve
440
AT310_AM_E2
Field
Type
Description
Attributes
TX_LOSS_PHYS
Float
TX_MASK
Memo
TX_PORT_1
Float
TX_PORT_2
Float
TX_PORT_3
Float
TX_PORT_4
Float
TX_PORT_5
Float
TX_PORT_6
Float
TX_PORT_7
Float
TX_PORT_8
Float
TX_PORT_9
Float
TX_PORT_10
Float
WITH_EQUALIZER
Boolean
Used to calculate Kn
XPIF
Float
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
MANUFACTURER
Text (50)
Manufacturer name
NAME
Text (50)
Family name
Type
Description
Attributes
ACM_MODE
Integer
FAMILY
Text (50)
Family name
FREQ_BAND
Text (50)
Frequency band
441
Forsk 2011
Type
Description
Attributes
BRANCHING_CONFIG
Text (50)
FAMILY
Text (50)
Family name
FREQ_BAND
Text (50)
Frequency band
RX_BRLOSS
Float
RX_STANDBY_LOSS
Float
TX_BRLOSS
Float
Transmission loss
Type
Description
Attributes
CHANNEL_SPACING
Text (50)
FAMILY
Text (50)
Family name
FREQ_BAND
Text (50)
Frequency band
XS
Double
442
Type
Description
Attributes
ACM_MODE
Short
ATPC_MAX
Float
ATPC_STEP
Float
ATPC interval
DISCRETE_POWERS
Text
(255)
FAMILY
Text (50)
Family name
FREQ_BAND
Text (50)
Frequency bands
MAX_POWER
Float
Maximum power
MODULATION
Text (20)
Modulation
STD_POWER
Float
Standard power
AT310_AM_E2
Type
Description
Attributes
FREQ_BAND
Text (50)
GUIDE_TYPE
Integer
LOSS_PER_METER
Float
Linear loss
MANUFACTURER
Text (50)
Guide manufacturer
NAME
Text (50)
Type
Description
Attributes
ANTENNA
Text (50)
AZIMUTH
Float
COMMENT_
Text
(255)
Comments
DOWNTILT
Float
FREQ_BAND
Text (50)
HEIGHT
Float
NAME
Text (50)
PMP_TYPE
Short
SITE
Text (50)
Type
Description
Attributes
INTERFERED
Text (50)
Interfered equipment
INTERFERER
Text (50)
Interferer equipment
IRF
Memo
The IRF field represents a list of pairs of values. Each pair consists of:
443
Forsk 2011
Type
Description
Attributes
ACTIVE
Boolean
ACTIVE_MODULATIONS_A
Text
(100)
ACTIVE_MODULATIONS_B
Text
(100)
ANTENNA_A
Text (50)
ANTENNA_B
Text (50)
ANTENNA2_A
Text (50)
ANTENNA2_B
Text (50)
ATMOS_PRESSURE
Float
ATPC_A
Float
ATPC at site A
ATPC_B
Float
ATPC at site B
AZIMUTH_A
Float
Azimuth at site A
AZIMUTH_B
Float
Azimuth at site B
BER
Double
BER2
Double
BRANCHING_CONFIG_A
Text (50)
Branching configuration at A
BRANCHING_CONFIG_B
Text (50)
Branching configuration at B
C_FACTOR
Float
CHANNELS_A
Text (50)
CHANNELS_B
Text (50)
CLIMATE_ZONE
Short
COMMENT_
Text
(255)
Comments
DELTA_POW_A
Float
DELTA_POW_B
Float
DOWNTILT_A
Float
Downtilt at site A
DOWNTILT_B
Float
Downtilt at site B
444
AT310_AM_E2
Field
Type
Description
Attributes
DX_A
Float
DX_B
Float
DY_A
Float
DY_B
Float
ENVTYPE
Integer
Type of environment
EPO_CLASS
Text (50)
EQUIPMENT_A
Text (50)
Equipment at site A
EQUIPMENT_B
Text (50)
Equipment at site B
FREQ_A
Double
Frequency at site A
FREQ_B
Double
Frequency at site B
FREQ_BAND
Text (50)
FREQ_SUBBAND
Text (50)
FREQ_SUBBAND_B
Text (50)
GEOCLIM_FACTOR
Double
GUIDE_LG1
Float
Length of GUIDE1
GUIDE_LG2
Float
Length of GUIDE2
GUIDE_LG3
Float
Length of GUIDE3
GUIDE_LG4
Float
Length of GUIDE4
GUIDE_USE1
Integer
GUIDE_USE2
Integer
GUIDE_USE3
Integer
GUIDE_USE4
Integer
GUIDE1
Text (50)
GUIDE2
Text (50)
GUIDE3
Text (50)
GUIDE4
Text (50)
HEIGHT_A
Float
Height at site A
445
446
Forsk 2011
Field
Type
Description
Attributes
HEIGHT_B
Float
Height at site B
KQ_FACTOR
Float
MTTR
Float
NAME
Text
(120)
PARITY_A
Integer
Parity of site A
PARITY_B
Integer
Parity of site B
PL
Float
POLARIZATION_A
Text (1)
Polarization at site A
POLARIZATION_B
Text (1)
Polarization at site B
PROFILE
Binary
Link profile
PROPAG_IMODEL
Text (50)
PROPAG_MODEL
Text (50)
Propagation model
R001
Float
RADOME_ON_A
Boolean
RADOME_ON_B
Boolean
RADOME2_ON_A
Boolean
RADOME2_ON_B
Boolean
RAIN_HEIGHT
Float
RAIN_ZONE
Short
REFRACTIVITY
Float
REFRACTIVITY_KE
Float
N-units /km
REPEATER1
Text (50)
REPEATER2
Text (50)
RXLOSS_ATT_A
Float
RXLOSS_ATT_B
Float
SEPARATION_A
Float
SEPARATION_B
Float
AT310_AM_E2
Field
Type
Description
Attributes
SHIELDING_FACTOR_A
Float
Additional loss due to a natural or artificial obstacle in the vicinity of the Null column allowed: Yes
antenna A
Default value: 0
SHIELDING_FACTOR_B
Float
Additional loss due to a natural or artificial obstacle in the vicinity of the Null column allowed: Yes
antenna B
Default value: 0
SITE_A
Text (50)
SITE_B
Text (50)
TEMPERATURE
Float
Temperature
TERRAIN_TYPE
Integer
TXLOSS_ATT_A
Float
TXLOSS_ATT_B
Float
TXLOSS_BRANCHING_A
Float
TXLOSS_BRANCHING_B
Float
USE_STD_POWER_A
Boolean
USE_STD_POWER_B
Boolean
VAPOR
Float
Type
Description
Attributes
BER_SES
Double
BERses
BLOCK_SIZE
Integer
NAME
Text (50)
RATE
Float
SUP_RATE
Float
TYPE
Short
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
NAME
Text (50)
447
Forsk 2011
Type
Description
Attributes
EB_N0
Memo
Eb/No graph
FULL_NAME
Text
(255)
Comments
NAME
Text (20)
Modulation
NSTATES
Integer
Type
Description
Attributes
COMMENT_
Text
(255)
Comments
EPO_CLASS
Text (50)
NAME
Text (50)
Type
Description
Attributes
LINK
Text
(120)
MULTI_HOP
Text (50)
ORDER_
Short
Type
Description
Attributes
HUB
Text (50)
LINK
Text
(120)
448
Field
Type
Description
Attributes
CHANNEL
Short
Channel Number
LINK
Text
(120)
AT310_AM_E2
Field
Type
Description
Attributes
POLARIZATION
Text (1)
RX_ATTENUATION
Float
RX_PORT
Short
STATUS
Short
TX_ATTENUATION
Float
TX_PORT
Short
WAY
Short
Type
Description
Attributes
ANTENNA
Text (50)
Repeater antenna
ANTENNA_2
Text (50)
Used if type is Back to Back Antenna (from the antenna table) (point to
B)
AZIMUTH_A
Float
AZIMUTH_B
Float
DX
Float
DY
Float
FREQ_BAND
Text (50)
GUIDE
Text (50)
HEIGHT
Float
HEIGHT_2
Float
Height (pointed to B)
LG_GUIDE
Float
Guide length
NAME
Text (50)
REPEATER_TYPE
Short
REVERSE_POLAR
Boolean
SITE
Text (50)
SURFACE
Float
TILT_A
Float
449
Forsk 2011
HEIGHT
Float
HEIGHT_2
Float
Height (pointed to B)
LG_GUIDE
Float
Guide length
NAME
Text (50)
REPEATER_TYPE
Short
REVERSE_POLAR
Boolean
SITE
Text (50)
SURFACE
Float
TILT_A
Float
Type
Description
Attributes
EXCLUDE_L
Text
(250)
EXCLUDE_U
Text
(250)
F0
Double
Central frequency
FREQ_BAND
Text (50)
Frequency band
KL
Double
KU
Double
N_MAX
Integer
N_MIN
Integer
NAME
Text (50)
REC_UIT
Text
(255)
ITU Recommendations
STEP
Integer
XS
Double
Inter-channel space
450
AT310_AM_E2
Field
Type
Description
Attributes
ANTENNA_A
Text (50)
ANTENNA_B
Text (50)
ATMOS_PRESSURE
Float
BER
Double
BER2
Double
BRANCHING_CONFIG_A
Text (50)
Branching configuration at A
BRANCHING_CONFIG_B
Text (50)
Branching configuration at B
C_FACTOR
Float
CLIMATE_ZONE
Short
ENVTYPE
Integer
Type of environment
EPO_CLASS
Text (50)
EQUIPMENT_A
Text (50)
Equipment at site A
EQUIPMENT_B
Text (50)
Equipment at site B
FREQ_BAND
Text (50)
GUIDE_LG1
Float
Length of GUIDE1
GUIDE_LG2
Float
Length of GUIDE2
GUIDE_LG3
Float
Length of GUIDE3
GUIDE_LG4
Float
Length of GUIDE4
GUIDE_USE1
Integer
GUIDE_USE2
Integer
GUIDE_USE3
Integer
GUIDE_USE4
Integer
GUIDE1
Text (50)
GUIDE2
Text (50)
GUIDE3
Text (50)
GUIDE4
Text (50)
HEIGHT_A
Float
Height at site A
451
Forsk 2011
Field
Type
Description
Attributes
HEIGHT_B
Float
Height at site B
KQ_FACTOR
Float
MTTR
Float
NAME
Text
(120)
PL
Float
POLARIZATION_A
Text (1)
Polarisation of the descending link 'siteA - site B' (the site A and site B
are respectively transmitter and receiver)
POLARIZATION_B
Text (1)
Polarisation of the ascending link 'siteA-site B' (the site A and site B are
respectively receiver and transmitter)
PROPAG_IMODEL
Text (50)
PROPAG_MODEL
Text (50)
Propagation model
R001
Float
RAIN_HEIGHT
Float
RAIN_ZONE
Short
REFRACTIVITY
Float
REFRACTIVITY_KE
Float
N-units /km
RXLOSS_ATT_A
Float
RXLOSS_ATT_B
Float
TEMPERATURE
Float
Temperature
TERRAIN_TYPE
Integer
TXLOSS_ATT_A
Float
TXLOSS_ATT_B
Float
TXLOSS_BRANCHING_A
Float
TXLOSS_BRANCHING_B
Float
VAPOR
Float
452
Type
Text (50)
Description
Attributes
AT310_AM_E2
Field
Type
Description
Attributes
DEFAULT_RESOLUTION
Float
DMAX
Float
NAME
Text (50)
SHARED_RESULTS_FOLDER
Text
(255)
SYSTEM_
Text (50)
TECHNOLOGY
Text (10)
Type
Description
Attributes
Data
Binary
Description
Text
(255)
User defined
Name
Text (50)
Signature
Text (40)
Type
Text (50)
Type
Description
Attributes
ALTITUDE
Float
Real altitude
Unit: m
COMMENT_
Text
(255)
LATITUDE
Double
Y coordinate
LONGITUDE
Double
X coordinate
NAME
Text (50)
Site name
PYLON_HEIGHT
Float
SUPPORT_NATURE
Short
453
Forsk 2011
Field
Type
Description
Attributes
LIST_NAME
Text (50)
SITE_NAME
Text (50)
Type
Description
Attributes
NAME
Text (50)
Type
Description
Attributes
COORD_SYSTEM
Integer
GAIN_UNIT
Integer
PROJECTION
Integer
RECEPTION_UNIT
Integer
TRANSMISSION_UNIT
Integer
454
AT310_AM_E2
Atoll 3.1.0
Administrator Manual
455
Administrator
Manual
version 3.1.0
AT310_AM_E2
12 July 2011
Head Office
7, rue des Briquetiers
31700 Blagnac - France
Tel: +33 562 747 210
Fax: +33 562 747 211
US Office
200 South Wacker Drive - Suite 3100
Chicago, IL 60606 - USA
Tel: +1 312 674 4800
Fax: +1 312 674 4847
China Office
Suite 302, 3/F, West Tower,
Jiadu Commercial Building,
No. 66 Jianzhong Road,
Tianhe Hi-Tech Industrial Zone,
Guangzhou, 510665, P. R. of China
Tel: +86 20 8553 8938
Fax: +86 20 8553 8285
www.forsk.com