Beruflich Dokumente
Kultur Dokumente
~ ~
~
~
~
~
User Manual ~
v e r s i o n 2.8.0
AT280_UM_E0
Contact Information
Forsk (USA Office) 200 South Wacker Drive L sales_us@forsk.com Sales and pricing information
Suite 3100 " support_us@forsk.com Technical support
Chicago, IL 60606 +1 312 674 4846 General
USA +1 888 GoAtoll (+1 888 462 8655) Technical support
+1 312 674 4847 Fax
Forsk (China Office) Suite 302, 3/F, West Tower, www.forsk.com.cn Web
Jiadu Commercial Building, L enquiries@forsk.com.cn Information and enquiries
No.66 Jianzhong Road, +86 20 8553 8938 Telephone
Tianhe Hi-Tech Industrial Zone, +86 20 8553 8285 Fax (Guangzhou)
Guangzhou, 510665, +86 10 6513 4559 Fax (Beijing)
Peoples Republic of China
Table of Contents
6 Co-planning Features..............................................................................................................225
6.1 Starting a Co-planning Project ..............................................................................................225
6.1.1 Switching to Co-planning Mode ......................................................................................................225
6.1.2 Displaying Both Networks in the Same Atoll Document..................................................................226
6.2 GSM-UMTS Co-planning Process ......................................................................................226
6.2.1 Creating a UMTS Sector From a GSM Sector ................................................................................226
6.2.1.1 Synchronising Shared Common Physical Parameters..............................................................227
6.2.2 Updating GSM And UMTS Coverage Predictions...........................................................................228
6.2.3 Comparing GSM-UMTS Coverage Predictions...............................................................................228
6.2.4 Performing Inter-Technology Neighbour Allocation ........................................................................230
6.2.4.1 Setting Inter-Technology Exceptional Pairs ..............................................................................230
6.2.4.2 Displaying Inter-Technology Exceptional Pairs on the Map ......................................................231
6.2.4.3 Allocating Inter-Technology Neighbours Manually ....................................................................232
6.2.4.4 Allocating Inter-Technology Neighbours Automatically .............................................................234
6.2.4.5 Displaying Inter-Technology Neighbours on the Map ...............................................................235
6.2.5 Modelling Inter-Network Interferences ............................................................................................236
6.2.5.1 Interferences from external transmitters on the mobiles ...........................................................237
6.2.5.2 Interferences from external transmitters/mobiles on the transmitters .......................................238
6.2.5.3 Interferences from external mobiles on the mobiles..................................................................238
6.2.5.4 Effects of inter-technology interferences on predictions............................................................239
6.3 Tips and Tricks .............................................................................................................................240
6.3.1 Minimising Memory Consumption ...................................................................................................241
7.6.4.2 Creating Coverage Predictions from Test Mobile Data Paths ...................................................377
7.6.4.3 Extracting a Field From a Test Mobile Path for a Transmitter ...................................................379
7.6.4.4 Analysing Data Variations Along the Path.................................................................................380
7.6.5 Printing and Exporting the Test Mobile Data Window.....................................................................381
7.7 Advanced Configuration...........................................................................................................382
7.7.1 Defining Resource Ranges .............................................................................................................382
7.7.1.1 Frequencies...............................................................................................................................382
7.7.1.2 BSICs ........................................................................................................................................383
7.7.1.3 Defining HSN Domains and Groups..........................................................................................385
7.7.2 Setting HCS Layers.........................................................................................................................385
7.7.3 Comparing Service Areas in Calculations.......................................................................................386
7.7.4 Cell Types .......................................................................................................................................390
7.7.4.1 TRX Types ................................................................................................................................390
7.7.4.2 Creating a Cell Type..................................................................................................................390
7.7.4.3 Examples of Cell Types.............................................................................................................392
7.7.5 TRX Configuration...........................................................................................................................393
7.7.5.1 Creating or Importing TRX Configuration ..................................................................................394
7.7.6 Codec Configuration .......................................................................................................................394
7.7.6.1 Accessing the Codec Mode table ..............................................................................................394
7.7.6.2 Creating or Modifying Codec Configuration ..............................................................................395
7.7.6.3 Setting Codec Mode Adaptation Thresholds .............................................................................395
7.7.6.4 Setting Codec Mode Quality Thresholds ...................................................................................396
7.7.6.5 Using Codec Configurations in Transmitters and Terminals .....................................................396
7.7.7 Coding Scheme Configuration ........................................................................................................397
7.7.7.1 Accessing the Coding Scheme table.........................................................................................397
7.7.7.2 Creating or Modifying Coding Scheme Configuration ...............................................................397
7.7.7.3 Using Coding Scheme Configuration in Transmitters and Terminals........................................398
7.7.7.4 Adapting Coding Scheme Thresholds for a Maximum BLER....................................................399
7.7.7.5 Displaying Coding Scheme Throughput Graphs .......................................................................399
7.7.8 Timeslot Configurations ..................................................................................................................400
7.7.8.1 Creating or Modifying a Timeslot Configuration ........................................................................400
7.7.9 Advanced Transmitter Configuration Options .................................................................................400
7.7.9.1 Defining Extended Cells ............................................................................................................401
7.7.9.2 Advanced Modelling of Multi-Band Transmitters .......................................................................401
7.7.10 GSM/GPRS/EDGE Multi-Service Traffic Data ................................................................................403
7.7.10.1 Modelling GSM/GPRS/EDGE Services.....................................................................................404
7.7.10.2 Modelling GSM/GPRS/EDGE Mobility Types ...........................................................................404
7.7.10.3 Modelling GSM/GPRS/EDGE Terminals...................................................................................405
7.7.11 Defining the Interferer Reception Threshold ...................................................................................406
7.7.12 Taking Intermodulation Interference into Consideration in Calculations .........................................407
7.7.13 Modelling Shadowing ......................................................................................................................407
7.7.13.1 Displaying the Shadowing Margins per Clutter Class ...............................................................407
7.7.14 Modelling the Co-existence of Networks.........................................................................................408
9.3.2.3 Creating Traffic Maps per User Density (No. Users/km2) .........................................................517
9.3.2.4 Converting 2G Network Traffic ..................................................................................................518
9.3.2.5 Exporting Cumulated Traffic ......................................................................................................519
9.3.3 Exporting a Traffic Map ...................................................................................................................519
9.3.4 Calculating and Displaying Traffic Simulations ...............................................................................520
9.3.4.1 The Power Control Simulation Algorithm ..................................................................................520
9.3.4.2 Creating Simulations .................................................................................................................523
9.3.4.3 Displaying the Traffic Distribution on the Map ...........................................................................524
9.3.4.4 Displaying the User Active Set on the Map ...............................................................................526
9.3.4.5 Displaying the Results of a Single Simulation ...........................................................................527
9.3.4.6 Displaying the Average Results of a Group of Simulations .......................................................532
9.3.4.7 Updating Cell Values With Simulation Results ..........................................................................535
9.3.4.8 Adding New Simulations to an Atoll Document .........................................................................535
9.3.4.9 Estimating a Traffic Increase .....................................................................................................537
9.3.5 Analysing the Results of a Simulation.............................................................................................537
9.3.5.1 Making an AS Analysis of Simulation Results ...........................................................................538
9.3.5.2 Making Coverage Predictions Using Simulation Results ..........................................................538
9.4 Optimising and Verifying Network Capacity ...................................................................539
9.4.1 Importing a Test Mobile Data Path..................................................................................................539
9.4.2 Displaying Test Mobile Data ...........................................................................................................542
9.4.3 Defining the Display of a Test Mobile Data Path.............................................................................542
9.4.4 Network Verification ........................................................................................................................543
9.4.4.1 Filtering Incompatible Points Along Test Mobile Data Paths.....................................................543
9.4.4.2 Creating Coverage Predictions from Test Mobile Data Paths ...................................................544
9.4.4.3 Extracting a Field From a Test Mobile Path for a Transmitter ...................................................545
9.4.4.4 Analysing Data Variations Along the Path.................................................................................546
9.4.5 Printing and Exporting the Test Mobile Data Window.....................................................................548
9.5 Advanced Configuration...........................................................................................................548
9.5.1 Defining Inter-Carrier Interference ..................................................................................................548
9.5.2 Defining Frequency Bands..............................................................................................................549
9.5.3 The Global Transmitter Parameters................................................................................................549
9.5.3.1 The Options on the Global Parameters Tab..............................................................................549
9.5.3.2 Modifying Global Transmitter Parameters.................................................................................550
9.5.4 Radio Bearers .................................................................................................................................550
9.5.4.1 Defining R99 Radio Bearers......................................................................................................550
9.5.4.2 Defining HSDPA Radio Bearers ................................................................................................551
9.5.4.3 Defining HSUPA Radio Bearers ................................................................................................552
9.5.5 Site Equipment................................................................................................................................552
9.5.5.1 Creating Site Equipment ...........................................................................................................552
9.5.5.2 Defining Resource Consumption per UMTS Site Equipment and R99 Radio Bearer ...............553
9.5.5.3 Defining Resource Consumption per UMTS Site Equipment and HSUPA Radio Bearer .........553
9.5.6 Receiver Equipment........................................................................................................................554
9.5.6.1 Setting Receiver Height.............................................................................................................554
9.5.6.2 Creating or Modifying Reception Equipment .............................................................................554
9.5.6.3 HSDPA UE Categories..............................................................................................................555
9.5.6.4 HSUPA UE Categories..............................................................................................................556
9.5.7 Multiple Input Multiple Output Systems...........................................................................................556
9.5.8 Conditions for Entering the Active Set ............................................................................................557
9.5.9 Modelling Shadowing ......................................................................................................................557
9.5.9.1 Displaying the Shadowing Margins and Macro-diversity Gain per Clutter Class ......................558
Atoll
RF Planning and Optimisation Software
Chapter 1: The Working Environment
Toolbar
Workspace
Explorer window
(docked)
Panoramic window
(floating)
Click the Maximise button ( ) near the corner of the window. Depending on the position of the window, this
button can be in the upper-left or upper-right corner.
To minimise a window in its docking area:
Click the Minimise button ( ) near the corner of the window. Depending on the position of the window, this button
can be in the upper-left or upper-right corner.
You can leave a window in its docking area, or you can have it float over the working environment, allowing you to maxim-
ise the amount of area for document windows or other windows.
To float a window:
Double-click the docking window title bar. The docking window leaves the docking area and floats over the working
environment.
Note: You can move the docking window by clicking the title bar and dragging it. To prevent the
window from docking as you move it, press CTRL as you drag the docking window.
To dock a window:
To return the window to its previous docked location, double-click the docking window title bar.
Or
Click the title bar of the docking window and drag the window to a different docking area.
Note: The window positions for docking windows are not associated with the current document;
they remain the same no matter which document you open.
The Data tab: The Data tab allows you to manage radio data and calculations. Depending on the modules
installed with Atoll, the Data tab has the following folders:
- Sites
- Antennas
- Transmitters
- Predictions
- UMTS Parameters, CDMA2000 Parameters, or GSM/GPRS Parameters
- UMTS Simulations or CDMA2000 Simulations
- Traffic analysis (GSM/GPRS/EDGE projects only)
- Hexagonal design
- Microwave links
- CW Measurements and Test mobile data
The Geo tab: The Geo tab allows you to manage geographic data. The number of folders depends on the
number and types of geographical data types (vector data, scanned images, etc.) you import or create:
- Clutter classes
- Clutter heights
- Digital Terrain Model
- Population data
- Any other geo data map
- Traffic (GSM/GPRS/EDGE/TDMA, UMTS HSPA, CDMA2000)
The Modules tab: The Modules tab allows you to manage the propagation models and additional modules. It
contains:
- A Propagation Models folder with the following propagation models:
- Longley-Rice
- Okumura-Hata
- Cost-Hata
- Standard Propagation Model
- ITU 526-5
- ITU 370-7 (Vienna 93)
- ITU 1546
- WLL
Note: Hiding an object affects only its visibility in the map window; it will still be taken into
consideration during calculations.
2. Clear the check box ( ) immediately to the left of the object name. The check box appears cleared ( ) and the
object is no longer visible on the map.
Note: You can hide the contents of an entire folder by clearing the check box to the left of the
folder name. When the check box of a folder appears greyed ( ), it indicates that the
folder contains both visible and hidden objects.
Note: Before you print a map, you should pay attention to the arrangement of the layers. For
more information, see "Printing Recommendations" on page 61.
Note: In Atoll, objects such as sites or transmitters are named with default prefixes. Individual
objects are distinguished from each other by the number added automatically to the
default prefix. You can change the default prefix for sites, transmitters, and cells by editing
the atoll.ini file. For more information, see the Administrator Manual.
Tip: When you are selecting data objects on the map, it can be difficult to ensure that the
correct object has been selected. When a site is selected, the site (and its name) is
surrounded by a black frame ( ). When a transmitter is selected, both ends of its icon
have a green point ( ). When there is more than one transmitter or microwave link
with with the same azimuth, clicking the transmitters in the map window opens a context
menu allowing you to select the transmitter you want (see "Selecting One of Several
Transmitters or Microwave Links" on page 30).
2. Select Properties from the context menu. The Properties dialogue appears.
You can switch between the Properties dialogues of items (transmitters, antennas, sites, services, user profiles, etc.) in
the same folder or subfolder in the Explorer window by using the browse buttons ( ) in the lower-left
corner of each Properties dialogue:
To select one of several transmitter or microwave link with the same azimuth:
1. In the map window, click the transmitters or links. A context menu appears with a list of the transmitters or links
with the same azimuth (see Figure 1.3 and Figure 1.4).
- When you select a microwave link, both ends appear white and the link itself appears outlined ( ).
Tip: While this method allows you to place a site quickly, you can adjust the location more
precisely by editing the coordinates on the General tab of the Site Properties dialogue.
For information on the Site Properties dialogue, see "Site Description" on page 247.
1. On the map, click the antenna whose azimuth you want to modify.
2. Move the pointer to the end of the antenna with a green circle ( ). An arc
with an arrow appears under the pointer.
3. Click the green circle and drag it to change the antennas azimuth.
The current azimuth of the antenna is displayed in the far left of the status
bar.
4. Release the mouse when you have set the azimuth to the desired angle.
The antennas azimuth is modified on the Transmitter tab of the Transmitter
Properties dialogue.
You can also modify the azimuth on the map for all the antennas on a base station using the mouse.
To modify the azimuth of all the antennas on a base station using the mouse:
1. On the map, click one of the antennas whose azimuth you want to modify.
2. Move the pointer to the end of the antenna with a green circle ( ). An arc
with an arrow appears under the pointer.
3. Hold CTRL and, on the map, click the green circle and drag it to change the
antennas azimuth.
The current azimuth of the antenna is displayed in the far left of the status
bar.
4. Release the mouse when you have set the azimuth of the selected antenna
to the desired angle.
The azimuth of the selected antenna is modified on the Transmitter tab of the
Transmitter Properties dialogue. The azimuth of the other antennas on the
base station is offset by the same amount as the azimuth of the selected
antenna.
Note: If you make a mistake when changing the azimuth, you can undo your changes by using
Undo (by selecting Edit > Undo or by pressing CTRL+Z) to undo the changes made.
Note: If you make a mistake when changing the position of the transmitter, you can undo your
changes by using Undo (by selecting Edit > Undo or by pressing CTRL+Z) to undo the
changes made.
When you access the Properties dialogue of an individual object, the Display tab will only show the options applicable to
an individual object (see Figure 1.6).
5. Click OK.
Depending on the object selected, you can choose from the following display types: unique, discrete values, value inter-
vals, or automatic.
To change the display type:
1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 33.
2. Select the display type from the Display Type list:
- Unique: defines the same symbol for all objects of this type. By defining a unique symbol for an object type,
objects of different types, for example, sites or transmitters, are immediately identifiable.
i. To modify the appearance of the symbol, click the symbol in the table below. The Symbol Style dialogue
appears.
ii. Modify the symbol as desired.
iii. Click OK to close the Symbol Style dialogue.
- Discrete values: defines the display of each object according to the value of a selected field. This display type
can be used to distinguish objects of the same type by one characteristic. For example, you could use this
display type to distinguish transmitter by antenna type, or to distinguish inactive from active sites.
i. Select the name of the Field by which you want to display the objects.
ii. You can click the Actions button to access the Actions menu. For information on the commands availa-
ble, see "Using the Actions Button" on page 34.
iii. To modify the appearance of a symbol, click the symbol in the table below. The Symbol Style dialogue
appears.
iv. Modify the symbol as desired.
v. Click OK to close the Symbol Style dialogue.
- Value intervals: defines the display of each object according to set ranges of the value of a selected field.
This display type can be used, for example, to distinguish population density, signal strength, or the altitude
of sites.
i. Select the name of the Field by which you want to display the objects.
ii. Define the ranges directly in the table below. For an example, see Figure 1.8 on page 37.
iii. You can click the Actions button to access the Actions menu. For information on the commands availa-
ble, see "Using the Actions Button" on page 34.
iv. To modify the appearance of a symbol, click the symbol in the table. The Symbol Style dialogue appears.
v. Modify the symbol as desired.
vi. Click OK to close the Symbol Style dialogue.
- Automatic: only available for transmitters; Atoll automatically assigns a colour to each transmitter, ensuring
that each transmitter has a different colour than the transmitters surrounding it.
i. Click the symbol in the table below. The Symbol Style dialogue appears.
ii. Modify the symbol as desired.
iii. Click OK to close the Symbol Style dialogue.
Notes:
When you create a new map object, for example, a new site or a new transmitter, you must
click the Refresh button ( ) for Atoll to assign a colour to newly created object according to
the set display type.
You can define the default symbol used for sites and how it is displayed by editing an option in
the atoll.ini file. For more information, see the Administrator Manual.
The Actions button on the Display tab of the Properties dialogue allows you to modify the display type as defined in
"Defining the Display Type" on page 34.
To access the Actions menu:
1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 33.
2. Click the Actions button. The Actions menu gives you access to the following commands:
- Select all: Atoll selects all the values in the table.
- Delete: Atoll removes selected value from the table.
- Insert before: When the selected display type is value intervals, Atoll inserts a new threshold in the table
before the threshold selected in the table.
- Insert after: When the selected display type is value intervals, Atoll inserts a new threshold in the table after
the threshold selected in the table.
- Properties: Atoll opens the Display dialogue where you may change the colour and style.
- Shading: Atoll opens the Shading dialogue. When "Value Intervals" is the selected display type, you select
Shading to define the number of value intervals and configure their colour. Enter the upper and lower limits
of the value in the First Break and Last Break boxes respectively, and enter a value in the Interval box.
Define the colour shading by choosing a Start Colour and an End Colour. The value intervals will be deter-
mined by the set values and coloured by a shade going from the set start colour to the set end colour.
When "Discrete Values" is the selected display type, you select Shading to choose a Start Colour and an
End Colour.
- Configuration: Select Import if you want to import an existing display configuration. Select Export if you want
to export the display settings of the current object to a configuration file, so that you can share them with other
users or use them in other documents.
You can change the transparency of some objects, such as predictions, and some object types, such as clutter classes,
to allow objects on lower layers to be visible on the map.
To change the transparency:
1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 33.
2. Move the Transparency slider to the right to make the object or object type more transparent or to the left to make
it less transparent.
You can define a visibility range for object types. An object is visible only if the scale, as displayed on the zoom toolbar, is
within this range. This can be used to, for example, prevent the map from being cluttered with symbols when you are at a
certain scale.
Visibility ranges are taken into account for screen display, and for printing and previewing printing. They do not affect which
objects are considered during calculations.
To define an object visibility range:
1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 33.
2. Enter a Visibility Scale minimum in the between 1: text box.
3. Enter a Visibility Scale maximum in the and 1: text box.
For most object types, such as sites and transmitters, you can display information about each object in the form of a label
that is displayed with the object. You can display information from every field in that object types data table, including from
fields that you add.
To define a label for an object type:
1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 33.
2. Click the Browse button ( ) beside the Label box. The Field Selection dialogue appears (see Figure 1.7).
c. To change the order of the fields, select a field and click or to move it up or down in the list. The objects
will be grouped in the order of the fields in the Selected Fields list, from top to bottom.
4. Click OK to close the Field Selection dialogue and click OK to close the Properties dialogue.
Note: For most object types, you can also display object information in the form of a tool tip that
is only visible when you move the pointer over the object. This option has the advantage
of not filling the map window with text. For more information on tool tips, see "Defining the
Object Type Tip Text" on page 36.
For most object types, such as sites and transmitters, you can display information about each object in the form of a tool
tip that is only visible when you move the pointer over the object. You can display information from every field in that object
types data table, including from fields that you add.
To define tip text for an object type:
1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 33.
2. Click the Browse button ( ) beside the Tip Text box. The Field Selection dialogue appears (see Figure 1.7).
3. Select the fields which you want to display in the tool tip:
a. To select a field to be displayed in the label for the object type, select the field in the Available Fields list and
Note: For most object types, you can also display object information in the form of a label that is
displayed with the object. This option has the advantage of keep object-related
information permanently visible. For more information on tool tips, see "Defining the
Object Type Label" on page 35.
Once you have defined the tool tips, you must activate the tool tip function before they appear.
To activate the tool tip function:
Click the Display Tips button ( ) on the toolbar. Tool tips will now appear when the pointer is over the object.
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 a maximum of 30 lines. You can change this default maximum through an option in
the atoll.ini file. For more information, see the Administrator Manual.
You can display the information defined by the display type (see "Defining the Display Type" on page 34) in your Atoll
documents legend. Only visible objects appear in the Legend window. For information on displaying or hiding objects,
see "Displaying or Hiding Objects on the Map Using the Explorer" on page 28.
In Figure 1.8, on the Display tab of a signal level prediction, the intervals defined are:
Signal level >= -65 red
-65 > Signal level >= -105 shading from red to blue (9 intervals)
Signal level < -105 not shown in the coverage.
The entries in the Legend column will appear in the Legend window.
With value intervals, you can enter information in the Legend column to be displayed on the legend. If there is no infor-
mation entered in this column, the maximum and minimum values are displayed instead.
1. Access the Display tab of the Properties dialogue as explained in "Display Properties of Objects" on page 33.
2. Check the Add to legend box. The defined display will appear on the legend.
To display the Legend window:
Select View > Legend. The Legend window appears.
When doing a best server prediction, Atoll calculates, for each pixel on the map, which server is best received. If the
selected display type for transmitters is "Automatic," Atoll colours each pixel on the map according to the colour of the
transmitter that is best received on that pixel. This way, you can identify immediately which transmitter is best received on
each pixel. The following two figures show the results of the same best server area and handover margin study.
In Figure 1.9, the transmitter display type is "Discrete Values," with the site name as the chosen value. The difference in
colour is insufficient to make clear which transmitter is best received on each pixel. In Figure 1.10, the transmitter display
type is "Automatic." Because Atoll ensures that each transmitter has a different colour than the transmitters surrounding
it, the study results are also immediately visible.
Figure 1.9: Value interval display type Figure 1.10: Automatic display type
To display the results of a server coverage study with the transmitters set to the Automatic display type:
1. Right-click the Transmitters folder in the Explorer window. The context menu appears.
2. Select Properties from the context menu. The Properties dialogue appears.
3. Select the Display tab.
4. Select "Automatic" as the Display Type.
5. Click OK.
6. Click the Refresh button ( ) to update the display of the study results.
Atoll displays the results of a signal level study as value intervals. On the map, these value intervals appear as differences
of shading. You can use the Shading command to define the appearance of these value intervals to make the results
easier to read or more relevant to your needs. For example, you can change the range of data displayed, the interval
between each break, or you can change the colours to make the intervals more visible.
In this example, Figure 1.11 shows the results of the best signal level plot from -60 dBm to -105 dBm. However, if you are
more interested in reception from -80 dBm to -105 dBm, you can change the shading to display only those values. The
result is visible in Figure 1.12.
Figure 1.11: Shading from -60 dBm to -105 dBm Figure 1.12: Shading from -80 dBm to -105 dBm
1. Click the Zoom icon ( ) on the Zoom toolbar (or press CTRL+Q).
2. Click the map where you want to zoom in.
Note: You can also zoom in by pressing CTRL+A, by selecting Zoom In from the View menu, or
by holding down the CTRL key and rotating the mouse wheel button forward.
1. Click the Zoom icon ( ) on the Zoom toolbar (or press CTRL+Q).
2. Right-click the map where you want to zoom out.
Note: You can also zoom out by pressing CTRL+R, by selecting Zoom Out from the View
menu, or holding down the CTRL key and rotating the mouse wheel button backward.
1. Click the Zoom Area icon ( ) on the Zoom toolbar (or press CTRL+W).
2. Click in the map on one of the four corners of the area you want to select.
3. Drag to the opposite corner. When you release the mouse button, Atoll zooms in on the selected area.
1. Click the arrow next to the scale box ( ) on the Zoom toolbar.
2. Select the scale from the list.
If the scale value you want is not in the list:
Click the Previous Zoom button ( ) to return to a zoom level you have already used.
Once you have returned to a previous zoom level, click the Next Zoom button ( ) to return to the latest zoom
level.
Tip: If you want to quickly find an object, such as a site, on the map, you can select it in the
Explorer window and then select the Centre in the Map Window command.
To display rulers:
1. Select Tools > Options.
2. In the Options dialogue, click the Coordinates tab.
3. Under Display rulers, select where you want the rulers to be displayed in the map window.
4. Click OK.
Important: Zones are taken into account whether or not they are visible. In other words, if you have
drawn a zone, it will be taken into account whether or not its visibility check box in the
Zones folder of the Geo tab in the Explorer window is selected.
For example, if you have filtered the sites using a filtering zone, the sites outside the
filtering zone will not be taken into consideration in coverage predictions, even if you have
cleared the filtering zones visibility check box. You will have to delete the zone if you no
longer want to select sites using a filtering zone.
4. From the context menu, select Draw. The pointer changes to the polygon drawing pointer ( ).
5. Click on the map to start drawing the filter polygon. Click each time you change the angle on the border defining
the outside of the polygon.
6. Close the polygon by clicking twice. The data objects outside of the selected zone are filtered out. On the Data tab
of the Explorer window, any folder whose content is affected by the filtering zone appears with a special icon
( ), to indicate that the folder contents have been filtered.
You can also create a filtering zone as follows:
Existing polygon: You can use any existing polygon on the map as a filtering zone by right-clicking it and
selecting Use as Filtering Zone from the context menu.
Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a filtering zone. You can import it by right-clicking the Filtering Zone
folder on the Geo tab and selecting Import from the context menu.
Fit to Map Window: You can create a filtering zone the size of the map window by selecting Fit to Map Window
from the context menu.
Once you have created a filtering zone, you can use Atolls polygon editing tools to edit it. For more information on the
polygon editing tools, see "Using Polygon Zone Editing Tools" on page 44.
Note: You can export the filtering zone as a polygon, so that you can use it in a different Atoll
document, by right-clicking the Filtering Zone folder on the Data tab of the Explorer
window and selecting Export from the context menu.
Once you have created a computation zone, you can use Atolls polygon editing tools to edit it. For more information on
the polygon editing tools, see"Using Polygon Zone Editing Tools" on page 44.
Note: You can save the computation zone, so that you can use it in a different Atoll document,
in the following ways:
- Saving the computation zone in the user configuration: For information on export-
ing the computation zone in the user configuration, see "Exporting a User Configura-
tion" on page 75.
- Exporting the computation zone: You can export the computation zone by right-
clicking the Computation Zone folder on the Data tab of the Explorer window and
selecting Export from the context menu.
You can also create a focus or hot spot zone in one of the following ways:
Existing polygon: You can use any existing polygon on the map as a focus zone by right-clicking it and selecting
Use as Focus Zone from the context menu.
Note: You can only create a focus zone, and not a hot spot zone, from an existing polygon.
Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus
Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot
spot zones, you can import the name (in text format) given to each zone as well. Additionally, because you can
have several hot spot zones, you can import more than one polygon into the Hot Spot folder, with each as a sep-
arate hot spot zone.
Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map
Window from the context menu.
Note: You can save the focus zone or hot spot zones to use in a different Atoll document:
- You can save the focus zone in the user configuration. For information on exporting the
focus zone in the user configuration, see "Exporting a User Configuration" on page 75.
- You can right-click the Focus Zone folder or the Hot Spot Zones folder on the Data
tab of the Explorer window and select Export from the context menu.
Tip: You can also activate the vector tools by selecting the polygon zone to edit from the
Vector Edition toolbar list.
You can now edit the polygon zone as explained in the following sections:
"Editing the Points of a Polygon Zone" on page 44
"Editing Polygon Zones Using the Toolbar" on page 44
"Editing Polygon Zones Using the Context Menu" on page 45.
i. Position the pointer over the point you want to move. The pointer changes ( ).
ii. Drag the point to its new position.
- Adding a point to the polygon zone:
i. Position the pointer over the polygon zone border where you want to add a point. The pointer changes
( ).
ii. Right-click and select Insert Point from the context menu. A point is added to the polygon zone border at
the position of the pointer.
- Deleting a point from a polygon zone:
i. Position the pointer over the point you want to delete. The pointer changes ( ).
ii. Right-click and select Delete Point from the context menu. The point is deleted.
In Atoll, you can create complex polygon zones by using the tools on the Vector Edition toolbar. The filtering, computa-
tion, and focus zone polygons can contain holes. The holes within polygonal areas are differentiated from overlaying poly-
gons by the order of the coordinates of their vertices. The coordinates of the vertices of polygonal areas are in clockwise
order, whereas the coordinates of the vertices of holes within polygonal areas are in counter-clockwise order.
To edit a polygon zone using the icons on the Vector Edition toolbar:
1. Put the polygon zone in editing mode as explained in "Editing Polygon Zones" on page 44.
2. Click the contour to edit. The Vector Edition toolbar has the following buttons:
When you are editing polygon zones, you can access certain commands using the context menu.
To edit a polygon zone using the context menu:
1. Click the polygon zone you want to edit.
2. Right-click the polygon zone to display the context menu and select one of the following:
- Properties: Select Properties to open the Properties dialogue of the selected polygon zone. The Properties
dialogue gives the coordinates of each point that defines the position and shape of the polygon zone.
- Insert Point: Select Insert Point to add a point to the border of the contour at the position of the pointer.
- Move:
i. Select Move from the context menu to move the contour, line, or point on the map.
ii. Move the contour, line, or point.
iii. Click to place the contour, line, or point.
- Quit edition: Select Quit Edition to exit editing mode.
- Delete: Select Delete to remove the selected contour, line, or point from the map.
Tip: You can also delete it by right-clicking its border on the map and selecting Delete from
the context menu.
Once you have created a coverage export zone, you can use Atolls polygon editing tools to edit it. For more information
on the polygon editing tools, see "Using Polygon Zone Editing Tools" on page 44.
Note: You can save the coverage export zone so that you can use it in a different Atoll
document in the following ways:
- Saving the coverage export zone in the user configuration: For information on ex-
porting the coverage export zone in the user configuration, see "Exporting a User Con-
figuration" on page 75.
- Exporting the coverage export zone: You can export the coverage export zone by
right-clicking the Coverage Export Zone folder on the Data tab of the Explorer
window and selecting Export from the context menu.
Important: The coverage export zone can only export in raster format. You can not export in raster
format if the coverage prediction was made per transmitter (for example, coverage
predictions with the display type set by transmitter, by a transmitter attribute, by signal
level, by path loss, or by total losses). Only the coverage area of a single transmitter can
be exported in raster format.
Note: The coverage prediction must be displayed in the map window before it can be exported.
For information on displaying objects in the map window, see "Displaying or Hiding
Objects on the Map Using the Explorer" on page 28.
3. Select Export the Coverage from the context menu. The Save As dialogue appears.
4. In the Save As dialogue, enter the File name and select the vector format from the Save as type list.
If you have chosen to export the prediction coverage in a vector format other than in AGD format:
a. If desired, under Coordinate Systems, change the reference coordinate system for the file being exported.
b. If desired, change the Resolution of the exported coverage. The default resolution is the resolution of the cov-
erage prediction results (as set in the coverage prediction Properties dialogue).
c. If desired, move the Smoothing slider, or enter the percentage in the text box, to define how much Atoll
smooths the exported coverage.
5. Click Save to export the coverage prediction results.
Note: The coverage prediction must be displayed in the map window before it can be exported.
For information on displaying objects in the map window, see "Displaying or Hiding
Objects on the Map Using the Explorer" on page 28.
3. You can export the entire coverage prediction, the coverage export zone, or part of the coverage prediction.
To export the entire coverage prediction:
- The Coverage Export Zone to export the rectangle defined by the coverage export zone.
b. If desired, move the Smoothing slider, or enter the percentage in the text box, to define how much Atoll
smooths the exported coverage.
c. Click OK to finish exporting the coverage prediction results.
Notes
When selecting a coordinate system different than the one initially defined in Atoll, the file is
converted using the selected coordinate system.
You can not export in raster format if the coverage prediction was made per transmitter (for
example, coverage predictions with the display type set by transmitter, by a transmitter
attribute, by signal level, by path loss, or by total losses). Only the coverage area of a single
transmitter can be exported in raster format.
Important: If you wish to use the exported file as a digital terrain model, you must define the size of
the exported image by pixel size. Atoll then creates a geo-reference file for the exported
image.
7. Click OK.
Note: You can also select Bitmap to paste the selection without rulers, or Text to paste the
upper left and lower right coordinates of the selection.
10. Click OK. The area of the map, including the rulers, is pasted as an image into the new document.
The polygon drawing pointer indicates you can draw a zone to filter either sites
or transmitters, to draw computation/focus/hot spot/filtering zones, or to draw
Polygon drawing
vector or raster polygons on the map. To draw a polygon, click once to start,
pointer and each time you change angles on the border defining the outside of the
polygon. Close the polygon by clicking twice.
Hand The hand pointer indicates you can move the visible part of the displayed map.
The zoom pointer indicates you can click to zoom in and right-click to zoom out
Zoom tool
at the location of the mouse pointer
The zoom area pointer indicates you can zoom in on an area of the by clicking
Zoom area
and dragging to define the area.
The transmitter pointer indicates you can place a transmitter on the map where
New transmitter you click. You can place more than one station by pressing CTRL as you click
on the map.
The point analysis pointer indicates that you have selected the Point Analysis
Point analysis
tool and have not yet chosen the first point.
The point placed pointer indicates the position of the receiver on the map that is
Point placed
used for the point-to-point analysis. The results are displayed in the CW
(Receiver) Measurements or Point Analysis window.
The pencil pointer indicates you can create a polygonal clutter zone, by clicking
Pencil once to start the polygon, once to create each corner, and by double-clicking to
close the polygon.
The deletion pointer indicates that you can delete a newly created polygonal
Deletion
clutter zone by clicking its border.
The position indicator pointer indicates you can select the border of a polygon.
Position
Right-clicking the polygon border opens a context menu allowing you to add a
indicator point, delete the polygon, or centre the map on the polygon.
The select/create points pointer indicates you can modify the polygon in the
map window. You can add a new point and modify the polygon contour by
Select/create
clicking on one of the edges and dragging. You can move an existing point by
points clicking and dragging an existing point. You can right-click to open a context
menu to delete a point, delete the polygon, or centre the map on the polygon.
Placing a CW
The first CW measurement point pointer indicates you can click a point on the
measurement
map to create the first point of a CW measurement path.
point
Placing points in
The next CW measurement point pointer indicates the first CW measurement
a CW
point has been set and you can now click other points on the map. Double-click
measurement to end the CW measurement path.
path
Microwave link The microwave link pointer indicates you can click a point on the map to create
start the first point of a microwave link. Once you have created the first point, the
End microwave link pointer changes and the next click ends the link.
Multi-hop or The multihop and multipoint pointer indicates you can click once to create the
first point of a multi-hop link or the hub of a point-to-multipoint link. In the case
point-to-
of a multihop link, each subsequent click creates another point in the link. In the
multipoint case of a point-to-multipoint, each subsequent link creates anew point,
microwave link connected to the hub by a link.
The terrain section pointer indicates that you can create a terrain section by
clicking once on the map to create the first point and once more to create the
Terrain section
second point. The terrain profile between the two points is displayed in the
Point Analysis window and stored under Terrain Sections in the Geo tab.
Note: User or custom fields are for information only and are not taken into account in any
calculation. You can find these fields in the Other Properties tab of an object types
Properties dialogue.
Caution: All data stored in the field will be lost when you delete the field itself. Make sure that you
are not deleting important information.
1. Access the object types table fields as explained in "Accessing an Object Types Table Fields" on page 50.
2. Select the custom field that you want to delete.
Tip: Some fields can not be deleted. If you select a field and the Delete button remains
unavailable, the selected field is not a custom field and can not be deleted.
3. Click Delete. The field is deleted from the object types data table.
Tip: If a list of options has been defined for a field, you can select a value from the list (see
Figure 1.17) or enter a new value.
Note: You can also open the Record Properties dialogue by double-clicking the record. To
avoid editing the record when you double-click, double-click the left margin of the record
instead of the record itself.
1. Open the data table as explained in "Opening a Data Table" on page 50.
2. Select Format > Header Format. The Format dialogue appears.
3. The Format dialogue has the following tabs:
- Font: You can select the Font, Outline (the font style), font Size, Effects, and Text Colour.
- Colour: You can select the background colour (Interior) of the column headers, by selecting a Foreground
colour, a Background colour, and a pattern from the list box. You can also select a 3D Effect for the header.
- Borders: You can select the Border, the Type, and the Colour for each column header.
- Alignment: You can select both the Horizontal and Vertical alignment of the column header text.
4. Click OK.
1. Open the data table as explained in "Opening a Data Table" on page 50.
2. Select Format > Column Format. The Format dialogue appears.
3. The Format dialogue has the following tabs:
- Font: You can select the Font, Outline (the font style), font Size, Effects, and Text Colour.
- Colour: You can select the background colour (Interior) of the column headers, by selecting a Foreground
colour, a Background colour, and a pattern from the list box. You can also select a 3D Effect for the header.
- Borders: You can select the Border, the Type, and the Colour for each column header.
- Alignment: You can select both the Horizontal and Vertical alignment of the column header text.
4. Click OK.
You can change the column width and row height in a data table. When you change the column width, you change the
width only for the selected column. When you change the row height, however, you change the row height for every row
in the table.
To change the column width:
1. Open the data table as explained in "Opening a Data Table" on page 50.
2. Click the border separating two column headers and drag to change the column width (see Figure 1.18).
To change the row height:
1. Open the data table as explained in "Opening a Data Table" on page 50.
2. Click the border separating two rows and drag to change the row height (see Figure 1.19).
Tip: You can also hide a column by right-clicking on its header and selecting Hide Columns
from the context menu. You can hide more than one column by pressing CTRL while
selecting the columns and then selecting Hide Columns from the context menu.
5. Click Close.
Note: You can also right-click the data table and select the Display Columns or Hide Columns
command from the context menu.
In Atoll, you can freeze one or more columns of a data table so that they always remain visible as you scroll horizontally
through the table. For example, while scrolling through the Sites table, you might want to have the Name column always
visible. You can keep this column, or any other column visible, by freezing it.
To freeze a column:
1. Open the data table as explained in "Opening a Data Table" on page 50.
2. Select the header of the column you want to freeze. Click and drag over several headers to select more than one
column to freeze.
3. Right-click the selected header or headers and select Freeze columns from the context men.
To unfreeze columns:
Select Format > Unfreeze columns.
Moving Columns
In Atoll, you can change the column order so that you can group similar columns or present data in a determined order.
To move a column:
1. Open the data table as explained in "Opening a Data Table" on page 50.
2. Select the header of the column you want to move. Click and drag over several headers to select more than one
column to move.
Note: You can only move several columns at the same time when they are adjacent.
3. Click again on the selected column and drag to the desired area. As you drag the column, the position the column
will occupy is indicated by a red line (see Figure 1.21).
Note: It may be necessary to click Refresh in the Zoom toolbar for your changes to appear.
4. Click in the left margin of the table row marked with the New Row icon ( ) to select the entire row.
5. Select Edit > Paste to paste the copied data into the new row. Atoll, creates a new element from the copied data.
The name of the new element is the same as that of the copied element, preceded by "Copy of." You can edit this
name.
- To copy the contents of the bottom cell of the selection into the other cells, select Edit > Fill > Up (see
Figure 1.24).
4. Select the Header check box if you want to export the names of the columns with the data.
5. Select a Decimal Symbol from the list.
6. Select a Field Separator from the list.
7. Define which fields (displayed as columns in the table) you want to export:
a. To select a field to be exported, select the field in the Available Fields box and click to move it
to the Exported Fields list. All fields in the Exported Fields list will be exported.
b. To remove a field from the list of Exported Fields, select the field in the Exported Fields list and click
to remove it.
c. To change the order of the fields, select a field and click or to move it up or down in the list. The fields
at the top of the Exported Fields appear at the left of the exported table.
Note: You can save the choices you have made in the Export dialogue as a configuration file by
clicking the Save button at the top of the dialogue and entering a name for the file in the
Save As dialogue that appears. The next time you export a data table, you can click Load
in the Export dialogue to open your configuration file with the same settings you used this
time.
Note: Atoll compares the values in the left-most column of the data to be imported with the
values in the same column of the data table to see if records already exist. The values of
these records are replaced when the Update Records check box is selected. If the
Update Records check box is not selected, these records are not imported.
Tip: You can change the width of the columns to make the contents easier to work with. See
"Changing Column Width or Row Height" on page 54.
Note: You can save the choices you have made in the Import dialogue as a configuration file by
clicking the Save button at the top of the dialogue and entering a name for the file in the
Save As dialogue that appears. The next time you export a data table, you can click Load
in the Import dialogue to open your configuration file with the same settings you used this
time.
10. Click Import. The contents are imported in the current Atoll data table.
For information on exporting the information in a data table into a text file, see "Exporting Tables to Text Files" on page 58.
Note: Tables are imported in the same order they appear in the index.xml file. Do not modify the
order of tables in the index.xml file because the order in which the data is imported is very
important; some data must be imported before other data. For example, antennas used
by transmitters must be imported before the transmitters themselves.
During the import procedure, existing data in the tables are overwritten by the data from the XML files. Once the import is
complete, Atoll performs a database integrity check, and a duplicate records check to ensure that the import did not create
database problems.
For information on exporting the data tables in your document to XML files, see "Exporting Tables to XML Files" on
page 60.
4. If you want to print only a selected area, choose Selected in the Print dialogue.
5. Click OK to print.
Important: Printing graphics is a memory-intensive operation and can make heavy demands on your
printer. Before printing for the first time, you should review the "Printing
Recommendations" on page 61 to avoid any memory-related problems.
To print a map:
1. Select the document window containing the map.
2. You now have the following options before printing the map:
- You can select a print area ("Defining the Printing Zone" on page 61) or create a focus zone ("Drawing a Focus
Zone or Hot Spot Zones" on page 43).
- You can modify the print layout ("Defining the Print Layout" on page 62).
- You can see how the map will appear once printed (see "Previewing Your Printing" on page 64).
3. Select File > Print.
4. Click OK.
Once you have created a printing zone, you can change its size by dragging the edges of the zone displayed on the rulers
of the map window. You can also use Atolls polygon editing tools to edit the printing zone. For more information on the
polygon editing tools, see "Using Polygon Zone Editing Tools" on page 44.
Note: You can save the printing zone, so that you can use it in a different Atoll document, in the
following ways:
- Saving the printing zone in the user configuration: For information on exporting the
printing zone in the user configuration, see "Exporting a User Configuration" on
page 75.
- Exporting the printing zone: You can export the printing zone by right-clicking the
Printing Zone folder on the Data tab of the Explorer window and selecting Export
from the context menu.
Note: If you have previously defined a configuration file containing all the necessary settings,
you can click the Import button under Configuration to import those settings.
2. Click the Page tab. On the Page tab, you can define the page size, margins, and orientation and the scale of the
printed map:
a. Under Orientation, select whether the page should be printed in Portrait or Landscape.
b. Under Paper, select the Size of the paper and, optionally, the Source of the paper.
c. Under Scaling, define the scale of the printed image either by selecting Fit to page, or by selecting Scale and
defining the scale.
d. Under Margins, set the margins of the page in millimetres.
3. Click the Components tab.
a. Under Map, you can define the appearance of the printed map:
- Select the Rulers check box if you want to print the map with a scale around it.
- Select the Area inside focus zone only check box if you only want to print the part of the map inside the
focus zone.
b. Under Legend, you can define the placement of the legend.
- Select the Legend check box if you want to print the map with a scale around it.
4. Click the Header/Footer tab. On the Header/Footer tab, you can set the position of graphic elements.
5. Select the Map Title check box if you want to define a title for the map and set its Position. Clicking the Properties
button opens a dialogue where you can enter text and set variables such as the current time and date. If you want
the title to appear on the map (and not outside of it), select the On the map check box.
6. Under Logo 1 and Logo 2, you can define graphics that appear for the map. The graphics can be a company logo
or other information, such as copyright information, in the form of a BMP graphic.
a. For the selected check box, click the Properties button. The Logo dialogue appears.
By default, Atoll searches for the header and footer logos in the Atolls installation folder. If a file named lo-
go.bmp is present in this folder, it is considered as the default header logo. However, you can select a different
file.
Note: Only BMP graphics can be used as logos. If your logo is in a different format, you must
first convert it using a graphics programme to the BMP format.
Note: You can save the current settings as a configuration file by clicking the Export button
under Configuration. This enables you to re-use the same settings the next time by
importing them.
Note: If the range of properties available in the Group By submenu has been configured as
explained in "Configuring the Group By Submenu" on page 65, you can select additional
properties by selecting More Fields from the Group By submenu. For information on
using the dialogue that appears, see "Configuring the Group By Submenu" on page 65.
6. Select the fields you want to appear in the Group By submenu. You can display all the fields belonging to a table
by clicking the Expand button ( ) to the left of the table name. You can select contiguous fields by clicking the
first field, pressing SHIFT and clicking the last field. You can select non-contiguous fields by pressing CTRL and
clicking each fields separately.
- To select a field to appear in the Group By submenu, select the field in the Available Fields list and click
to remove it.
- To change the order of the fields, select a field and click or to move it up or down in the list. The objects
will be grouped in the order of the fields in the Grouping Fields list, from top to bottom.
7. Click OK to close the Configuration dialogue and click OK to close the Properties dialogue. The Group By sub-
menu will now contain only the fields you selected.
6. Select the fields by which you want to group the objects. You can select contiguous fields by clicking the first field,
pressing SHIFT and clicking the last field. You can select non-contiguous fields by pressing CTRL and clicking
each fields separately.
- To select a field to be used to group the objects, select the field in the Available Fields list and click
- To change the order of the fields, select a field and click or to move it up or down in the list. The objects
will be grouped in the order of the fields in the Group these fields in this order list, from top to bottom.
7. Click OK to close the Group dialogue and click OK to close the Properties dialogue and group the objects.
To undo the grouping:
1. Click the Data tab in the Explorer window.
2. Right-click the folder or subfolder whose objects you have grouped.
3. From the context menu, select from the Group By > None.
You can only sort in a table by adjacent columns. If you want to sort by columns that are not adjacent, you can move the
columns first as explained in "Moving Columns" on page 55.
Tip: If you want to sort data by several columns without moving the columns, you can use the
Sort function on the Properties dialogue. For information, see "Advanced Sorting" on
page 69.
Tip: You can also access the Filter dialogue by clicking the Filter button of the Properties
dialogue.
Note: Making selections on the Filter tab of the Filter dialogue is the equivalent of filtering by
selection as explained in "Filtering in Data Tables by Selection" on page 70.
b. Underneath each column name, enter the criteria on which the column will be filtered as explained in the fol-
lowing table:
5. Click OK to filter the data according to the criteria you have defined.
Filters are combined first horizontally, then vertically.
See "Advanced Filtering: Examples" on page 72.
The objective of this example is to use filter criteria to find antennas manufactured by Kathrein with a beamwidth between
50 and 100. To do this, the following filter syntax is entered in the Advanced tab of the Filter dialogue (for information on
the Advanced tab, see "Advanced Data Filtering" on page 71):
The first criterion, as shown in Figure 1.38, is all antennas made by a manufacturer with a name beginning with a
"K" ("=K*"). While you could write in the entire name ("=Kathrein"), it is not necessary because there is only one
manufacturer with a "K."
The second criterion is all antennas with a beamwidth under 100.
The third criterion is all antennas with a beamwidth over 50.
The combination of these criteria is all antennas from manufacturers with a name beginning with "K" and with a beamwidth
under 100 but over 50.
The result of this advanced filter can be seen in the second pane of Figure 1.38.
As previously stated, the objective of this example was to use filter criteria to find antennas manufactured by Kathrein with
a beamwidth between 50 and 100. However, because the second criterion (beamwidth under 100 and over 50) is
malformed, with "> 50" placed under "< 100", it functioned as an OR condition and not as an AND condition. The resulting
filter searched for all antennas manufactured by Kathrein with a beamwidth under 100, or all antennas over 50; all anten-
nas are displayed.
As previously stated, the objective of this example was to use filter criteria to find antennas manufactured by Kathrein with
a beamwidth between 50 and 100. However, because the second criterion is malformed, the filter only generates an error
message and no antennas are filtered out.
Important: If you export the geographic data set in a user configuration file, the coordinate system of
any vector geographic data must be the same as that of the raster geographic data.
Computation and Focus Zones: The computation and focus zone in the current document.
Folder configurations: Sorting, grouping and filtering settings (those saved by the user and the current settings,
even if not saved), the filtering zone, and the display settings of radio data folders (including measurement display
settings).
Automatic Neighbour Allocation Parameters: The input parameters of the automatic neighbour allocation.
Automatic Scrambling Code Allocation Parameters: The parameters of the automatic scrambling code alloca-
tion (this option applies to UMTS documents only).
Prediction List: The general information (name, comments, group, and sorting and filtering settings), prediction
coverage conditions, and display settings of coverage predictions that have been created.
AFP Configuration: Calculation options selected when starting an AFP session as well as calculation parameters
used for interference histograms (this option applies to GSM documents only).
Automatic PN Offset Allocation Parameters: The parameters of the automatic PN offset allocation. (this option
applies to CDMA2000 documents only).
Microwave Link Parameters: The settings of microwave links.
Macros: The complete path of any macros. Because a macro is linked to an Atoll session, and not to a specific
Atoll document, you can export the macros in a user configuration even if you do not have an Atoll document
open.
For a detailed description of the user configuration file, see the Administrator Manual.
In this section, the following are explained:
"Exporting a User Configuration" on page 75
"Importing a User Configuration" on page 75.
2. Select the check boxes of the information you want to export as part of the user configuration.
3. Click OK. The Save As dialogue appears.
4. Enter a File name for the user configuration file and click Save. The folder configuration has been saved.
In a multi-user environment, site lists can be stored in the database. When you open a document from a database, you
can select the sites to load according to any defined site lists. In a large radio-planning project, this allows you to more
effectively manage your resources by reducing the unnecessary data you retrieve from the database.
In this section, the following are explained:
"Creating a Site or Transmitter List" on page 76
"Adding a Site or Transmitter to a List from the Explorer Window" on page 76
"Adding a Site or Transmitter to a List from the Map Window" on page 76
"Adding Sites or Transmitters to a List Using a Zone" on page 77
"Editing a Site or Transmitter List" on page 77
"Filtering on a Site or Transmitter List" on page 77.
3. Enter the name of the new list in the row marked with the New Row icon ( ).
- Select Add Site to a List from the context menu. A dialogue appears.
Transmitter list: if you want to add a transmitter to a list.
- Select Add Transmitter to a List from the context menu. A dialogue appears.
4. Select the name of the list from the dialogue.
Tip: You can create a new list by entering a name in the list instead of selecting the name
from the list. The selected site or transmitter will be added to the new list.
Tip: You can quickly create a complete list by first filtering the contents of the Sites or
Transmitters folder as explained in "Filtering Data" on page 70. Then, by right-clicking
the Sites or Transmitters folder and selecting Site Lists > Add Sites to a List or
Transmitter Lists > Add Transmitters to a List from the context menu, you can add the
filtered contents of folder to the list you select.
- Select Add Site to a List from the context menu. A dialogue appears.
Transmitter list: if you want to add a transmitter to a list.
- Select Add Transmitter to a List from the context menu. A dialogue appears.
Tip: You can create a new list by entering a name in the list instead of selecting the name
from the list. The selected site or transmitter will be added to the new list.
Tip: You can create a new list by entering a name in the list instead of selecting the name
from the list. The selected site or transmitter will be added to the new list.
4. Click OK. The sites or transmitters contained in the zone are added to the selected list.
- Select the name of the site or transmitter in the row marked with the New Row icon ( ).
To delete a site or transmitter from the list:
a. Click in the left margin of the row containing the site or transmitter to select it.
b. Press DEL to delete the site or transmitter from the list.
5. Click OK when you have finished editing the site or transmitter list.
Note: For transmitters, there is a default folder configuration called Same as Sites Folder. You
can apply this configuration to arrange the transmitters in the Transmitters folder with the
same parameters as those defined for sites.
Caution: When you delete a folder configuration, Atoll will not ask for confirmation; it is deleted
immediately.
Tip: If you have created several subfolders, you can rename each one to give it a more
descriptive name. For information on renaming an object, see "Renaming an Object" on
page 29.
Once you have performed the actions on each subfolder, you can compare the differences, by displaying in turn each
subfolder, with its grouping, sorting, or filtering settings, on the map. For more information on display properties, see
"Display Properties of Objects" on page 33.
To compare subfolders:
1. In the Data tab of the Explorer window, clear the check boxes to the left of each subfolder. The data objects are
not displayed on the map.
2. Select the check box of one of the subfolders, leaving the check boxes of the other subfolders cleared. The data
objects of the selected subfolder, with its associated grouping, sorting, or filtering settings, are displayed on the
map.
3. Clear this check box and select the check box of a different subfolder. How the objects are displayed on the map
will change, depending on the different grouping, sorting, or filtering settings of the selected subfolder.
You can remove subfolders by deleting them. When you delete a subfolder, the data contained are not deleted. When you
delete the last subfolder, the data reappear under the initial folder.
To delete a subfolder:
Right-click the subfolder to be deleted and select Delete from the context menu.
Tip: If, after deleting the last subfolder, the data do not reappear under the initial folder, you
can refresh the display by right-clicking the folder and selecting Group By > None from
the context menu.
Note: You can change the Find toolbar to a floating window by double-clicking it.
2. From the Find list, choose the map object you are searching for:
- Site
- Transmitter
- Repeater
- Link
3. Enter the name of the object in the Named box. You can use an asterisk ("*")as a wild card in the following ways:
- *X* names which contain X
- X* names which start with X
- *X names which end with X
4. Press ENTER. Atoll selects the object and centres it in the map window.
Note: You can also search for a map object by its name by using the Location Finder. For
information, see "Searching for a Map Object using Any Text Property" on page 81.
1. Click the Location Finder button ( ) on the toolbar. The Location Finder dialogue appears.
2. From the Find list, choose the map object you are searching for:
- Site
- Transmitter
- Repeater
- Link
- Vector
3. If you wish to search all the sites in the search, including sites that are presently filtered out, select the Include all
the sites in the search (filtered or not) check box.
4. Under Criteria, select a Field to be searched and enter the value of the field. You can use an asterisk as a wild
card in the following ways:
- *X* text objects which contain X
- X* text objects which start with X
5. Click OK. Atoll selects the site and centres it in the map window.
1. Click the Location Finder button ( ) on the toolbar. The Location Finder dialogue appears.
2. From the Find list, choose Point.
3. Enter the x and y coordinates of the point, using the same units as defined under Display on the Coordinates tab
of the Options dialogue (see "Projection and Display Coordinate Systems" on page 92).
4. Click OK. Atoll marks the point ( ) and centres it in the map window.
Note: To remove the point icon ( ), select it and then select Delete from the context menu.
Create a new group of hexagons based on the currently selected station template ( indicates that no hexa-
gon radius is defined)
Note: A new hexagon group is created in the Hexagonal Design folder if the check box to the
left of this folder is selected when you create a new station or a group of stations. If the
check box is not selected, you can create a new station without creating a corresponding
hexagon group.
Create a new repeater or remote antenna for the currently selected transmitter
Calculate only invalid matrices, unlocked coverages, and pending simulations (F7)
Force the calculation of all matrices, unlocked coverages, and pending simulations (CTRL+F7)
Stop the calculation of all matrices, unlocked coverages, and pending simulations (ESC)
Select area
Zoom in on the map and centre on the cursor location (CTRL+A) and zoom out on the map and centre on the
cursor location (CTRL+R)
Location finder
Create a new vector layer (in either the Geo or the Data tab)
Draw points
Note: When you place the cursor over an icon, a tool tip appears, giving a short description.
- CTRL+R: Zoom out on the map (toolbar: select and Right-click the map)
- F7: Calculate only invalid matrices, unlocked coverages, and pending simulations (toolbar: select )
- CTRL+F7: Force the calculation of all matrices, unlocked coverages, and pending simulations (toolbar: select
)
Tip: Menus and commands can be also accessed by pressing the ALT key and typing the
underlined letter in the menu or command name.
Atoll
RF Planning and Optimisation Software
Atoll User Manual
From an existing database: When you create a new Atoll document from a database, the database you connect
to has been created with the technology and data you need. Working with a database allows several users to share
the same data while at the same time managing data consistency. The exact procedure for creating a new Atoll
document from a database differs, depending on the database containing the data. Atoll can work with several
common databases. For information on starting a document from a database, see "Creating a New Atoll Document
from a Database" on page 95.
Figure 2.2: New Atoll document Geo tab Figure 2.3: New Atoll document Modules tab
When you create an Atoll document from a template, the document is not connected to a database.
To verify whether the document is connected to a database:
Select File > Database > Connection Properties. The dialogue in Figure 2.4 appears.
Figure 2.5: NTF (Paris)/France II tendue system used with WGS 72 system
Notes: All imported raster geographic files must be use the same cartographic system. If not, you
must convert them to a single cartographic system.
2. On the Coordinates tab, click the Browse button ( ) to the right of the Projection field. The Coordinate Sys-
tems dialogue appears.
3. In the Coordinate Systems dialogue, select a catalogue from the Find in list. For the projection system, only car-
tographic systems (identified by the symbol) are available.
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.
Tip: If you frequently use a particular coordinate system you can add it to a catalogue of
favourites by clicking Add to Favourites.
5. Click OK. The selected coordinate system appears in the Projection field and, by default, in the Display field as
well.
6. If you wish to set a different coordinate system for the display, click the Browse button ( ) to the right of the
Display field and repeat step 3. to step 5. For the display system, both cartographic systems (identified by the
symbol) and geographic systems (identified by the symbol) are available.
Note: The degree format options apply only to the geographic coordinate systems.
User Documents: Individual user documents are initialised by the administrator but are later worked upon and
managed by each user. User documents are Atoll files which are connected to the central database, load only the
required part of the geographic data (as defined by the CFG file, for example), and have access to the shared path
loss matrices folder.
Note: For information on creating and maintaining the database, see the Administrator Manual.
Note: Additional dialogues may open asking you to choose which project in the database to load
or which site list to load.
4. Click OK. The Data to Load dialogue appears, allowing you to select the data to load into Atoll as a new document
(see "Selecting the Data to Load From the Database" on page 95).
Note: The new document may open with no site displayed in the map window. This is because
the north-west point of the project is by default the axis origin. You can re-centre the
document on the data displayed in the Data tab by expanding the Sites folder, right-
clicking on any site, and selecting Centre in the map window from the context menu.
Figure 2.10: New Atoll document Geo tab Figure 2.11: New Atoll document Modules tab
When you create an Atoll document from a database, you can view the characteristics of the database connection.
To view the characteristics of the database connection:
1. Select File > Database > Connection Properties. The Database Connection dialogue appears (see
Figure 2.12).
2. You can now:
- Disconnect your document from the database.
Caution: If you disconnect your document from the database, it will be become a stand-alone
document and you will not be able to reconnect it to the database.
Notes:
If you chose Refresh unmodified data only or Cancel your changes and reload database,
Atoll proceeds without asking for confirmation.
If you chose Archive your changes in the database, the Archive dialogue appears. For infor-
mation on using the Archive dialogue, see "Archiving the Modifications of an Atoll Document
in the Database" on page 98.
3. Under Take into account, you can select the neighbour lists, Intra-technology Neighbours and Inter-tech-
nology Neighbours, to refresh.
4. Under Modifications Since the Last Refresh, you can generate a report for the refresh process.
5. Click OK. The document is refreshed according to the selected options.
If you selected to generate a report, Atoll creates a text file in CSV (Comma Separated Values) format in the temporary
files system folder, and opens it. You can then rename the file and save it where you wish. The report lists all the modifi-
cations (deletions, additions, and updates) that were stored in the database since the last time you refreshed or opened
your document.
3. If some of the data has been modified on the database since you last refreshed, Atoll stops the archiving process
and asks you to resolve the conflict. For information on managing conflicts, see "Resolving Data Conflicts" on
page 99.
4. When you are finished archiving, click Close.
- If you want to overwrite the database value with the value of the same field in your document, select the
check box next to the highlighted change and click Archive. Your modification will be written to the data-
base, overwriting the value there.
- If you want to accept the value of the field in the database, clear the check box next to the highlighted
change and click Archive. Your modification will be lost and the value in the database will remain un-
changed.
- On a deleted record: You are in the process of archiving your modifications on the database and another
user has deleted a record since you last archived or refreshed your data. For information, see "Resolving Data
Conflicts" on page 99.
Atoll displays a message explaining that the record you are trying to update has been deleted from the data-
base (see Figure 2.16). Select one of the following:
- Yes: Select Yes to store your modifications in the database, thereby recreating the deleted record.
- No: Select No to abandon your modifications to this record and delete this record from your document.
- Cancel: Select Cancel to cancel.
2. Click Close to close the Archive dialogue.
To resolve all the data conflicts:
1. In the Pending Changes pane of the Archive dialogue, select any conflict and click Resolve All. Atoll displays
a message explaining how Resolve All works (see Figure 2.17). Select one of the following:
- Yes: Select Yes to accept all the modifications made by other users in the database and update your docu-
ment with values from the database.
- No: Select No to overwrite the modifications made by other users in the database with the values from your
document.
- Cancel: Select Cancel to cancel.
2. Click Close to close the Archive dialogue.
Important: You should only resolve all the data conflicts when you are certain about the
modifications.
Note: It can take a long time to back up large documents. Therefore, you should set a
correspondingly larger interval between backups when working with large documents in
order to optimise the process.
5. Click OK.
If you selected the Prompt before starting automatic backup check box, Atoll prompts you each time before backing
up the document. If you click OK, Atoll proceeds to back up all open documents. If you click Cancel, Atoll skips the
backup once.
The automatci backup timer is stopped while the prompt is displayed. Atoll displays a message in the Event Viewer every
time a backup file is updated. If you are performing calculations, i.e., coverage predictions or simulations, the automatic
backup is delayed until the calculations have ended. The timer starts again once the calculations are over. If you save the
original document manually, the timer is reset to 0.
Important: If you just remove the BAK extension, your backup file will have the same file name as
the original file and Windows will not allow you to rename the file. Therefore, it is safer to
give a new name to the backup file and keep the original file until you are sure which
version is most recent.
3. Open the renamed backup document in Atoll. You will be able to recover all the work up to the last time the backup
was saved.
- A copy of the ATL file with the same name as the name of the archive (ZIP file).
The ATL file added to the archive contains all the data that might be embedded in it (path loss matrices, geo-
graphic data, coverage predictions, simulation results, measurement data, etc.).
- A ".losses" folder containing a pathloss.dbf file and a LowRes subfolder which contains the pathloss.dbf file
corresponding to the extended path loss matrices.
Externally stored path loss matrices are not added to the archive because they are not necessary for making
a portable document as they can be recalculated based on the network and geographic data in the ATL file.
The pathloss.dbf files are stored in the archive because they are needed when reopening the archive in Atoll.
- A "Geo" folder with all the linked geographic data available in the Geo tab of the Explorer window for the Atoll
document.
This folder contains subfolders with the same names as the folders in the Geo tab. Geographic data present
outside folders in the Geo tab are stored in files under the Geo folder, and data present within folders in the
Geo tab are stored inside their respective folders. If the geographic data files linked to the document are lo-
cated on a remote computer, such as a file server over a network, they are first copied to the local computer
in the Windows temporary files folder and then added to the archive.
Once the portable archive is created, you can open it directly from Atoll without first having to extract it using another tool.
To open an archive containing an ATL file and all linked geographic data files:
1. Select File > Extract and Open. The Open dialogue appears.
2. Select the ZIP file that contains the ATL file and linked geographic data files.
3. Click Open. The Browse For Folder dialogue appears.
4. Select the folder where you want to extract the contents of the ZIP file.
5. Click OK. Atoll extracts all the files from the archive to the selected folder. If necessary, it creates the subfolders
required for extracting the contents of the Geo folder. Once Atoll has finished extracting files from the archive, it
opens the extracted ATL file. Geographic data extracted from the archive are linked to the ATL file.
Notes:
It is not required to have any compression utility, like WinZip or WinRAR, installed on the com-
puter for this feature.
The highest compression level is used when creating the archive.
Atoll
RF Planning and Optimisation Software
Atoll User Manual
The DTM describes the elevation of the ground over sea level. You can display the DTM in different ways: by single value,
discrete values, or by value intervals (see "Display Properties of Objects" on page 33).
The DTM is automatically taken into account by the propagation model during computations.
Clutter Classes
The clutter class geo data file describes land cover or land use. Clutter classes are taken into account by the propagation
model during computations.
Each pixel in a clutter class file contains a code (from a maximum of 256 possible classes) which corresponds to a clutter
class, or in other words to a certain type of ground use or cover. The height per class can be defined as part of the clutter
class, however, the height will be defined as an average height for each clutter class. For information on defining the height
per clutter class, see "Defining Clutter Class Properties" on page 115. Clutter heights can also be defined by a separate
clutter heights file (see "Clutter Heights" on page 106). A clutter height map can represent height much more accurately
because it allows a different height to be assigned for each pixel of the map.
Clutter Heights
Clutter height maps describe the altitude of clutter over the DTM with one altitude defined per pixel. Clutter height maps
can offer more precise information than defining an altitude per clutter class because, in a clutter height file, it is possible
to have different heights within a single clutter class.
When clutter altitude is defined both in clutter classes and in a clutter height map, clutter altitude is taken from the clutter
height map.
You can display the clutter height map in different ways: by single value, discrete values, or by value intervals (see "Display
Properties of Objects" on page 33).
Note: The only propagation models that can take clutter heights into account in calculations are
the Standard Propagation Model and WLL model.
Atoll supports contours, lines, and points to represent polygons such as regions, or lines such as roads or coastlines, or
points. They are used for display only and have no effect on computations. Contours can also be used to create filtering
polygons or computation or focus zones.
Scanned Images
Scanned images are geographic data files which represent the actual physical surroundings, for example, road maps or
satellite images. They are used to provide a precise background for other objects or for less precise maps and are used
only for display; they have no effect on calculations.
Population Maps
Population maps contain information on population density or on the total number of inhabitants. Population maps can be
used in prediction reports in order to display, for example, the absolute and relative numbers of the population covered.
Population maps have no effect on prediction and simulation results.
Geoclimatic Maps
Geoclimatic maps are vector files containing information on climatic conditions such as rain density, vapour density,
temperature, and refractivity. Geoclimatic maps are used in microwave link documents to calculate radio wave attenuation.
Traffic data maps contain information on capacity and service use per geographic area. Traffic data maps are used for
network capacity analyses.
You can import many different types of files for, for example, revenue, rainfall, or socio-demographic data. You could use
the imported data in prediction reports. For example, you could display the predicted revenue for defined coverage.
These imported data have no effect on prediction and simulation results.
Clutter height files in the following formats: TIF (8 or 16-bit), BIL (8 or 16-bit), IST (8 or 16-bit), Planet, BMP (8-bit),,
GRC Vertical Mapper (8 or 16-bit), and Erdas Imagine (8 or 16-bit)
Clutter class and traffic files in the following formats: TIF (8-bit), BIL (8-bit), IST (8-bit), BMP (8-bit), Planet, GRC
Vertical Mapper (8-bit), and Erdas Imagine (8-bit)
Vector data files in the following formats: AGD, DFX, Planet, SHP, MIF, and TAB.
Vector traffic files in the following formats: AGD, DFX, Planet, SHP, MIF, and TAB.
Scanned image files in the following formats: TIF (1 to 24-bit), BIL (1 to 24-bit), IST (1 to 24-bit), BMP (1 to 24-bit),
Planet, Erdas Imagine (1 to 24-bit), GRC Vertical Mapper (1 to 24-bit), and ECW (8 or 24-bit)
Population files in the following formats: TIF (16-bit), BIL (16-bit), IST (16-bit), Planet, BMP (16-bit), Erdas Imagine
(16-bit), GRD/GRC Vertical Mapper (16-bit), AGD, DXF, SHP, MIF, and TAB.
Geoclimatic files in the following formats: AGD, DXF, SHP, MIF, and TAB.
Other data in the following formats: TIF (16-bit), BIL (16-bit), IST (16-bit), Planet, BMP (16-bit), Erdas Imagine
(16-bit), GRD/GRC Vertical Mapper (16-bit), AGD, DXF, SHP, MIF, and TAB.
Caution: All raster maps imported must have the same projection coordinate system.
Note: The instructions in this section do not apply to custom geo data maps. For information on
importing or creating an custom geo data map, see "Custom Geo Data Maps" on
page 121.
Tip: You can use the drag-and-drop feature to import geo data files into a document. The
format is automatically recognized and Atoll presents you with the appropriate dialogue.
3. Click Open. The File Import dialogue appears (see Figure 3.1).
Note: If the Vector Import dialogue appears, go to "Importing a Vector-format Geo Data File"
on page 108.
Depending on the type of geo data file you are importing, choose one of the following options:
i. Select Population from the Data Type list. The Use as list becomes available.
ii. Select from the Use as list whether the imported data are to be interpreted as a Density (number of in-
habitants per square kilometre) or as a Value (number of inhabitants).
- Custom Geo Data: See "Custom Geo Data Maps" on page 121.
- Traffic Data Maps: Select Traffic Density from the Data Type list.
4. By default, the imported file is linked to the Atoll document. To embed the data file in the Atoll document, select
the Embed in Document check box. For information on embedding files, see "Embedding Geographic Data" on
page 113.
5. Click Import. The geo data file is imported and listed in the Geo tab of the Explorer window.
When you import a traffic data map, the traffic maps Properties dialogue appears:
a. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages
must equal 100.
b. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must
equal 100.
c. Under Services (%), enter the percentage of each service type used in the map. The total percentages must
equal 100.
d. Under Clutter Distribution, enter for each clutter class the percentage of indoor users.
An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to
define a clutter weighting for traffic density maps because the traffic is provided in terms of user density per
pixel.
e. For UMTS and CDMA, select whether the users are active in the Uplink/Downlink, only in the Downlink, or
only in the Uplink.
f. Click OK.
3. Click Open. The Vector Import dialogue appears (see Figure 3.4).
Note: If the File Import dialogue appears, go to "Importing a Raster-format Geo Data File" on
page 107.
Depending on the type of geo data file you are importing, choose one of the following options:
- Vector Data:
- Select Geo from the Import to list.
- Population:
i. Select Population from the Import to list.
ii. Under Fields to be imported, the first list contains the attributes of the population vector data file that you
are importing, and the second list lets you select whether the attribute corresponds to population density
or to a number of inhabitants.
iii. Select from the first list which field is to be imported and from the second list whether the imported field is
a Density (number of inhabitants per square kilometre for polygons, or number of inhabitants per kilome-
tre for lines) or a Value (number of inhabitants) (see Figure 3.2 and Figure 3.3).
- Geoclimatic File:
i. Select Geoclimatic Parameters from the Import to list.
ii. Under Fields to be imported, select from the first list which field is to be imported and select Value from
the second list.
- Custom Geo Data:
- See "Custom Geo Data Maps" on page 121.
- Traffic Data Maps: Select Traffic from the Import to list.
4. By default, the imported file is linked to the Atoll document. To embed the data file in the Atoll document, select
the Embed in Document check box. For information on embedding files, see "Embedding Geographic Data" on
page 113.
5. Click Import. The geo data file is imported and listed in the Geo tab of the Explorer window.
Notes:
You can import ellipses and arcs from MapInfo files (MIF and TAB). Rectangles are interpreted
as polygons.
You can define mappings between the coordinate system used for the MapInfo/ESRI vector
files, defined in the corresponding MIF/PRJ files, and Atoll. This way, when you import a vector
file, Atoll can detect the correct coordinate system automatically. For more information about
defining the mapping between coordinate systems, please refer to the Administrator Manual.
3. Select the type of geo data you are importing and select the Embed check box if you want to embed the data in
the current Atoll document.
4. Click OK to import the geo data into the current Atoll document.
c. To locate the MSI Planet index file, click . The Open dialogue appears.
d. Select the MSI Planet index file and click Open. The path and name of the file appears in the corresponding
field of the Planet Data to Be Imported dialogue.
4. When you have selected all the types of data you want to import, click OK. The data is imported into the current
Atoll document.
Note: The list of WMS servers that appears in the Server URL list are defined by entries in the
atoll.ini file. For information on defining these entries, see the Administrator Manual.
4. Click the Connect button. Atoll connects to the URL of the WMS server and displays the information available
along with a description of the service (Figure 3.7 on page 112).
5. In the left pane of the Web Map Services Data Import dialogue, navigate to the item you want to import by clicking
the Expand button ( ) to open each level.
6. Select either the image you want to import, or the image group, i.e., a group preceded by an Expand button ( ).
7. Click for each image you want to import. The files you want to import appear in the right pane of the Web Map
Services Data Import dialogue.
Note: You can remove an image or group of images from the images to be imported by
selecting it in the right pane and clicking .
8. Arrange the order in which you want the images to appear by selecting each image in the right pane and clicking
to move it towards the top or to move it toward the bottom. The images will be imported as a single object
and their appearance will depend on the order you define here.
9. The Web Map Import dialogue appears. The following information is given about the imported WMS data:
- Data Types: "Image or Scan" is selected.
- Geographic Coordinates: The geographic coordinates are the WMS data are given.
10. The Name suggested is the name of the lowest layer to be imported. If desired, you can modify this name.
11. Click Import. The image is imported by reference into the Atoll document. You can not embed a WMS image in
your document.
If you had selected more than one image or an image group, Atoll imports the group as a single object. You can
not modify this object. If you want to remove one of the images or add another one you will go through the import
process again.
Note: If you want to import your file to the Data tab, you can select New folder in Data.
4. Enter a name for the folder in Folder Name box and click OK.
5. Click Import. Your file is imported into the newly created folder.
You can now import other geo data files into this folder by selecting it from the Data Type list (on the File Import dialogue)
or the Import To list (on the Vector Import dialogue) when you import.
Note: You can transfer geo data that has been imported from the Geo tab to the Data tab, or
vice versa. Right-click the data in the Explorer window and select Transfer to Data or
Transfer to Geo.
Important: If you are using distributed calculations, you must link your geo data files. Distributed
calculations can not work with embedded geo data files. For information, see the
Administrator Manual.
To embed a geo data file in the current Atoll document while you are importing:
Select the Embed in Document check box on the File Import or Vector Import dialogue box.
To embed a geo data file that is already linked to the current Atoll document:
1. Click the Geo tab in the Explorer window.
2. Right-click the file you want to embed in the current document.
3. Select Properties from the context menu.
4. Click the General tab of the Properties dialogue.
5. Click Embed.
6. Click OK. The geo data file is now embedded in the current Atoll document.
You can also repair the link to the geo data file from within the Atoll document.
To repair a broken link from within the Atoll document:
1. Click the Geo tab in the Explorer window.
- If the geo data file is in a folder, such as the Clutter Classes, Traffic, or DTM folder, click to expand the
folder.
2. Right-click on the geo data file whose link you want to repair. The context menu appears.
3. Select Properties from the context menu.
4. On the General tab of the Properties dialogue, click the Find button.
5. Browse to the geo data file, select it and click OK.
Important: If the Height field is left blank, propagation models which use the height information of
clutter classes will assume a clutter height of "0" if there is no clutter height map.
6. If desired, you can enter a value for each of the following fields applicable to the current document:
- For all Atoll documents:
- Model Standard Deviation (dB): to calculate shadowing losses on the path loss, as related to a user-
defined cell edge coverage probability.
- Indoor Loss (dB): to be applied to the path loss and used in coverage predictions, point analysis or in
Monte Carlo simulations.
- For GSM/GPRS/EGPRS documents:
- C/I Standard Deviation (dB): to calculate shadowing losses on the C/I values, as related to a user-de-
fined cell edge coverage probability.
- For UMTS HSPA, IS-95 cdmaOne, and CDMA2000 1xRTT 1xEV-DO documents:
- Ec/Io Standard Deviation (dB): to calculate shadowing losses on the Ec/Io values, as related to a user-
defined cell edge coverage probability.
- Eb/Nt Standard Deviation DL (dB): to calculate shadowing losses on the Eb/Nt values, as related to a
user-defined cell edge coverage probability.
- Eb/Nt Standard Deviation UL (dB): to calculate shadowing losses on the Eb/Nt values, as related to a
user-defined cell edge coverage probability.
- % Pilot Finger: to be used in the Ec/Io calculations. This factor represents the percentage of energy
received by the mobile pilot finger. Mobile user equipment has one searcher finger for pilot. The searcher
finger selects one path and only energy from this path is considered as signal; energy from other multip-
aths is considered as interference. For example, if 70% of the total energy is in one path and 30% of the
energy is in other multipaths, then the signal energy is reduced to 70% of total energy).
- Orthogonality Factor: to be used to evaluate DL Eb/Nt. This parameter indicates the remaining orthog-
onality at the receiver; it can be modelled by a value from 0, indicating no remaining orthogonality because
of multi-path, to 1, indicating perfect orthogonality.
- Spatial Multiplexing Gain Factor: to apply to the spatial multiplexing gain read from the Max Spatial
Multiplexing Gain graphs in the MIMO tab of reception equipment.
- Additional Transmit Diversity Gain (dB): to add to the users downlink HS-PDSCH Ec/Nt, if the user
and its reference cell support transmit diversity.
- For TD-SCDMA documents:
- P-CCPCH Eb/Nt or C/I Standard Deviation (dB): to calculate shadowing losses on the P-CCPCH Eb/Nt
or C/I values, as related to a user-defined cell edge coverage probability.
- DL Eb/Nt or C/I Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt or C/I values, as
related to a user-defined cell edge coverage probability.
- UL Eb/Nt or C/I Standard Deviation (dB): to calculate shadowing losses on the Eb/Nt or C/I values, as
related to a user-defined cell edge coverage probability.
- DL Orthogonality Factor: to be used to evaluate DL Eb/Nt or C/I. This parameter indicates the remaining
orthogonality at the receiver; it can be modelled by a value from 0, indicating no remaining orthogonality
because of multi-path, to 1, indicating perfect orthogonality.
- UL Orthogonality Factor: to be used to evaluate UL Eb/Nt or C/I. This parameter indicates the remaining
orthogonality at the receiver; it can be modelled by a value from 0, indicating no remaining orthogonality
because of multi-path, to 1, indicating perfect orthogonality.
- Spreading Angle (): to be used in determining the cumulative distribution of C/I gains for statistical smart
antenna modelling.
- For WiMAX 802.16d and WiMAX 802.16e documents:
- C/I Standard Deviation (dB): to calculate shadowing losses on the C/(I+N) values, as related to a user-
defined cell edge coverage probability.
- SU-MIMO Gain Factor: to apply to the spatial multiplexing gain read from the Max SU-MIMO Gain graphs
in the MIMO tab of reception equipment.
- Additional STTD/MRC Gain (DL) (dB): to add to the users downlink C/(I+N), if the user and its reference
cell support STTD/MRC.
- Additional STTD/MRC Gain (UL) (dB): to add to the users uplink C/(I+N), if the user and its reference
cell support STTD/MRC.
- For LTE documents:
- C/I Standard Deviation (dB): to calculate shadowing losses on the C/(I+N) values, as related to a user-
defined cell edge coverage probability.
- SU-MIMO Gain Factor: to apply to the spatial multiplexing gain read from the Max SU-MIMO Gain graphs
in the MIMO tab of reception equipment.
- Additional Transmit Diversity Gain (dB): to add to the users downlink C/(I+N), if the user and its refer-
ence cell support transmit diversity.
- Additional Receive Diversity Gain (dB): to add to the users uplink C/(I+N), if the user and its reference
cell support receive diversity.
7. Click the Default Values tab. Enter default values for each field. For information about each field, see the descrip-
tions in the previous step.
The values entered on the Default Values tab are used if no clutter map is available. Even if there is a clutter
classes map, you can select the Use default values only check box on the Default Values tab to make Atoll use
the values specified in this tab instead of the values defined per clutter class.
8. Click the Display tab to define the display properties for clutter classes. In addition to the Display tab options
described in "Display Properties of Objects" on page 33, each clutter class display type has a visibility check box.
By selecting or clearing the visibility check box, you can display or hide clutter class display types individually.
Note: Selecting white as the colour for a clutter class value or value interval will cause that
clutter class value or value interval to be displayed as transparent.
9. Click OK.
Tip: You can copy the description table into a new Atoll document after importing the clutter
classes file. To copy the description table, select the entire table by clicking the cell in the
upper-left corner of the table and press CTRL+C. On the Description tab of the clutter
classes Properties dialogue in the new Atoll document, press CTRL+V to paste the
values in the table.
5. In the blank row marked with at the bottom of the table, enter an unused number from 1 to 255 in the Code
column.
6. Fill in the remainder of the fields as described in step 5. and step 6. of "Defining Clutter Class Properties" on
page 115.
7. Click OK.
You can now use the new clutter class when modifying the clutter class map. For information on modifying the clutter class
map, see "Creating a Clutter Polygon" on page 129.
Si
% of I = -------------- 100
Sk
k
The clutter height of the current pointer position as given in the clutter height file or in the clutter classes is displayed in the
status bar.
Note: You can manage the display of an individual vector object by right-clicking the vector
object in the vector layer folder and selecting Properties from the context menu.
All the vector objects of a vector layer and their attributes are listed in the vector table.
To open the vector layer table:
1. On the Explorer window tab containing the vector layer, right-click the vector layer folder. The context menu
appears.
2. Select Open Table from the context menu. The vector table appears.
You can edit the contents of this table using the commands from the context menu or from the Edit, Format, and Records
menus. For more information on editing tables in Atoll, see "Working with Data Tables" on page 50.
The vector layer Properties dialogue has three tabs: a General tab, a Table tab, and a Display tab.
To open the Properties dialogue of a vector layer:
1. On the Explorer window tab containing the vector layer, right-click the vector layer folder. The context menu
appears.
2. Select Properties from the context menu.
3. Click the General tab. The following options are available:
- Name: The name of the vector layer. You can rename the vector layer using this field.
- Source File: The complete path of the vector layer file if the file is linked to the Atoll document; otherwise the
file is described as embedded.
- Find: Click the Find button to redefine the path when the files location has changed.
- Embed: Click the Embed button to embed a linked vector layer file in the Atoll document.
- Coordinate System: When a vector layer is linked, the coordinate system used is the files, as specified when
the file was imported. When the a vector layer is embedded, the coordinate system used is documents, as
specified when the file was embedded.
- Change: Click the Change button to change the coordinate system of the vector layer.
- Sort: Click the Sort button to sort the data contained in the vector layer. For information on sorting, see
"Advanced Sorting" on page 69.
- Filter: Click the Filter button to filter the data contained in the vector layer. For information on filtering, see
"Advanced Data Filtering" on page 71.
4. Click the Table tab. You can use the Table tab to manage the vector layer table content. For information on the
Table tab, see "Adding, Deleting, and Editing Data Table Fields" on page 50.
5. Click the Display tab. You can use the Display tab to manage the vector layer display. For information on the Table
tab, see "Display Properties of Objects" on page 33.
You can transfer the vector layer back to the Geo tab by right-clicking it in the Data tab and selecting Transfer to the Geo
tab from the context menu. For more information about display priority in Atoll, see "Setting the Priority of Geo Data" on
page 124.
To import an index
1. Select File > Import.
2. Select the index file and click Open. The File Import dialogue appears (see Figure 3.1).
3. Select Image or Scan from the Data Type list.
4. Click Import. The image files imported and listed in the Geo tab of the Explorer window.
Note: Vector points added to a vector population map are not displayed if the map is displayed
by population density.
Note: Statistics are displayed only for visible data. See "Displaying or Hiding Objects on the
Map Using the Explorer" on page 28.
Note: Statistics are displayed only for visible data. See "Displaying or Hiding Objects on the
Map Using the Explorer" on page 28.
Important: If you do not select all the formats you need now, you will not be able to add a format later.
6. Under Supported Input Formats, select the check box corresponding to the type of value of the present file and
all other files that will constitute the new custom geo data map:
- Classes (8 bits): to create a map of value classes (such as clutter classes) with classes from 0 to 255.
- Short Integer (16 bits): to create a map with whole values.
- Long Integer (32 bits): to create a map with whole values.
- Float (32 bits): to create a map with decimal values.
- Double (64 bits): to create a map with decimal values.
7. Select the Integrable check box if you want to be able to use imported data as a surface density value and show
cumulative custom geo data in prediction reports.
Important:
To use imported data as a surface density value, you must select the Integrable check box.
You can not change the integrable setting once you have created your custom geo data map.
8. Click OK.
9. If the imported file is a raster file, the File Import dialogue appears (see Figure 3.1 on page 108); if the imported
file is a vector file, the Vector Import dialogue appears (see Figure 3.4 on page 109):
- File Import dialogue: From the Use as list, select whether the new data is to be used a Density or as a Value.
- Vector Import dialogue: Under Fields to be imported, select from the first list which field is to be imported
and from the second list whether the imported field is a Density or a Value (see Figure 3.2 on page 109 and
Figure 3.3 on page 109).
Important: If the file you first import when you create your custom geo data map is an 8-bit raster
map, the Use as and Fields to be imported boxes will not be available for any file that is
imported into your new custom geo data map. The values in 8-bit maps are codes and not
values such as densities.
10. .Click Import. A new folder is created on the Geo tab of the Explorer window containing the geo data file you
imported.
Important:
If the file you first imported when you created your custom geo data map was an 8-bit raster
map, the Use as and Fields to be imported boxes will not be available for any file that is
imported into your new custom geo data map.
To use imported data as a surface density value, you must select the Integrable check box.
3. Click Import. The file is added to the custom geo data file on the Geo tab of the Explorer window containing the
geo data file you imported.
In the Field list, display by value is not permitted if the custom geo data map has:
For information on using the display tab, see "Display Properties of Objects" on page 33.
Note: Statistics are displayed only for visible data. See "Displaying or Hiding Objects on the
Map Using the Explorer" on page 28.
Note: All objects on the Data tab, such as transmitters, antennas, and predictions, are displayed
over all objects on the Geo tab. Vector geo data, however, can be transferred to the Data
tab, where they can be placed over data such as predictions. In this way, you can ensure
that certain vector geo data, for example, major geographical features, roads, etc., remain
visible in the map window For more information, see "Moving a Vector Layer to the Data
Tab" on page 118.
The transparency of objects: You can change the transparency of some objects, such as predictions, and some
object types, such as clutter classes, to allow objects on lower layers to be visible on the map. For more informa-
tion, see "Defining the Transparency of Objects and Object Types" on page 35.
The visibility range of objects: You can define a visibility range for object types. An object is visible only in the
map window if the scale, as displayed on the zoom toolbar, is within this range. For more information, see "Defining
the Visibility Scale" on page 35.
In Figure 3.12, vector data (including the linear vectors HIGHWAYS, COASTLINE, RIVERLAKE, MAJORROADS,
MAJORSTREETS, RAILWAYS and AIRPORT), clutter classes, DTM and scanned image have been imported and a
UMTS environment traffic map has been edited inside the computation zone. In the map window, the linear objects
(ROADS, RIVERLAKE, etc.) are visible both inside and outside the computation zone. The clutter class layer is visible in
the area where there is no traffic data (outside the computation zone). On the other hand, the DTM layer which is beneath
the clutter class layer and the scanned map which is beneath the DTM layer, are not visible.
Note: The visibility in the context of calculations must not be confused with the display check
box ( ). Even if the display check box of an object is cleared ( ), so that the object is
not displayed on the map, it will still be taken into consideration for calculations. The only
cases where clearing the display check box means that the data will not be used are for
population data in reports, and for custom geo data maps.
Object folders, for example, the DTM, clutter classes, clutter heights, and traffic density folders, can contain more than one
data object. These objects can represent different areas of the map or the same parts of the map with the same or different
resolutions. Therefore for each folder, you should place the objects with the best data at the top. These are normally the
objects which cover the least area but have the highest resolution. For example, when calculating coverage in an urban
area, you might have two clutter class files: one with a higher resolution for the downtown core, where the density of users
is higher, and one with a lower resolution but covering the entire area. In this case, by placing the clutter class file for the
downtown core over the file with the lower resolution, Atoll can base its calculations for the downtown core on the clutter
class file with the higher resolution, using the second file for all other calculations.
Population maps and custom geo data maps, both of which can be used in prediction reports follow the same rules of
calculation priority.
The following sections give several examples to better illustrate how data are used in Atoll:
"Example 1: Two DTM Maps Representing Different Areas" on page 126
"Example 2: Clutter Classes and DTM Maps Representing the Same Area" on page 126
"Example 3: Two Clutter Class Maps Representing a Common Area" on page 126.
Case 1
DTM
DTM 2 (20m)
DTM 1 (50m)
Case 2
DTM
DTM 1 (50m)
DTM 2 (20m)
Figure 3.13Multi-layer management in calculations two DTM maps representing different areas
3.12.2.2 Example 2: Clutter Classes and DTM Maps Representing the Same Area
In this example, there are two imported maps:
A clutter class map called Clutter.
A DTM map called DTM.
Independently of the order of the two maps in the Explorer window, Atoll uses both the clutter and DTM data in calcula-
tions. In Case 1, the clutter class map is on top of the DTM map. In Case 2, the DTM map is on top of the clutter class
map. In both Case 1 and Case 2, Atoll will use both the clutter and DTM data in calculations.
Clutter classes
Clutter
DTM
DTM
Case 2
DTM
DTM
Clutter classes
Clutter
Figure 3.14Multi-layer management in calculations Clutter and DTM maps representing the same area
"Clutter 2." In Case 2, "Clutter 1" is on top and completely covers "Clutter 2." Therefore, Atoll will only use the data from
"Clutter 1."
Case 1
Clutter classes
Clutter 2 (20m)
Clutter 1 (50m)
Case 2
Clutter classes
Clutter 2 (50m)
Clutter 1 (20m)
Figure 3.15Multi-layer management in calculations two clutter maps representing the same area
Note: Tool tips only appear when the Display Tips button ( ) on the toolbar has been
selected.
Note: You can export and import other types of information with user configuration files as well.
For information, see the Administrator Manual.
Important: Vectors must be in the same coordinate system as the raster maps.
4. In the User Configuration dialogue, select the check boxes of the items you want to import.
5. If you already have geographic data in your current Atoll document and would like to replace it with any imported
data, select the Delete existing geo data check box.
If you do not want to replace existing geo data with imported data, clear the Delete existing geo data check box.
6. Click OK.
Note: You can automatically start Atoll with a user configuration file by naming the file "atoll.cfg"
and placing it in the same folder as the Atoll executable. You can also edit the Windows
shortcut to Atoll and add "-cfg <.cfg_file>" where is the complete path to the user
configuration file.
4. From the list, select the clutter class for the polygon you want to create.
Note: Clutter classes are defined on the Descriptions tab of the clutter classes Properties
dialogue.
Note: You can copy the exact coordinates of a closed polygon by right-clicking it on the map and
selecting Properties from the context menu.
i. Position the pointer over the point you want to move. The pointer changes ( ).
ii. Drag the point to its new position.
- Adding a point:
i. Position the pointer over the polygon border where you want to add a point. The pointer changes ( ).
ii. Right-click and select Insert Point from the context menu. A point is added to the border at the position
of the pointer.
- Deleting a point:
i. Position the pointer over the point you want to delete. The pointer changes ( ).
ii. Right-click and select Delete Point from the context menu. The point is deleted.
Note: You can select and copy the coordinates displayed in the Properties dialogue of the
polygon.
3. Click the New Vector Layer button ( ) on the Vector Edition toolbar. Atoll creates a folder called Vectors on
the Geo tab of the Explorer window. The new Vectors folder can be seen in the list of vector layers:
.
Tip: You can also activate the vector tools by selecting the vector layer to edit from the Vector
Edition toolbar list. Because Atoll names all new vector layers "Vectors" by default, it
might be difficult to know which Vectors folder you are selecting. By renaming each
vectors folder, you can ensure that you select the correct folder. For information on
renaming objects, see "Renaming an Object" on page 29.
If the Vector Edition toolbar is not visible, select View > Vector Edition Toolbar.
- New Polygon:
i. Click once on the map where you want to begin drawing the contour.
ii. Click each time you change angles on the border defining the outside of the contour.
iii. Double-click to close the contour.
- New Line:
i. Click once on the map where you want to begin the line.
ii. Click each time you change angles on the line.
iii. Double-click to end the line.
- New Point: Click once on the map where you want to place the point.
4. Press ESC to deselect the currently selected button on the Vector Edition toolbar.
Tip: You can also activate the vector tools by selecting the vector layer to edit from the Vector
Edition toolbar list.
You can now edit a object in the vector layer as explained in the following sections:
"Editing the Points of Contours and Lines" on page 131
"Editing Contours Using the Toolbar" on page 132
"Editing Contours, Lines, and Points Using the Context Menu" on page 132.
i. Position the pointer over the point you want to move. The pointer changes ( ).
ii. Drag the point to its new position.
- Adding a point to a contour or a line:
i. Position the pointer over the contour border or line where you want to add a point. The pointer changes
( ).
ii. Right-click and select Insert Point from the context menu. A point is added to the contour border or line
at the position of the pointer.
- Deleting a point from a contour or a line:
i. Position the pointer over the point you want to delete. The pointer changes ( ).
ii. Right-click and select Delete Point from the context menu. The point is deleted.
Editing a Point
To edit a point:
1. Put the vector layer containing the point in editing mode as explained in "Editing Contours, Lines, and Points" on
page 131.
2. Select the point. You can now edit by:
- Moving:
ii. Right-click and select Delete from the context menu. The point is deleted.
In Atoll, you can create complex contours by using the tools on the Vector Edition toolbar.
To edit a vector object using the icons on the Vector Edition toolbar:
1. Put the vector layer containing the contour in editing mode as explained in "Editing Contours, Lines, and Points"
on page 131.
2. Click the contour to edit. The Vector Edition toolbar has the following buttons:
When you are editing contours, lines, and points, you can access certain commands using the context menu.
To edit a vector object using the context menu:
1. Click the vector object you want to edit.
2. Right-click the vector object to display the context menu and select one of the following:
- Delete: Select Delete to remove the selected contour, line, or point from the map.
- Convert to Line: Select Convert to Line to convert the selected contour to a line.
- Convert to Polygon: Select Convert to Polygon to convert the selected line to a contour.
- Open Line: Select Open Line to remove the segment between the last and the first point.
- Close Line: Select Close Line to add a segment between the last and the first point of the line.
- Insert Point: Select Insert Point to add a point to the border of the contour at the position of the pointer.
- Move:
i. Select Move from the context menu to move the contour, line, or point on the map.
ii. Move the contour, line, or point.
iii. Click to place the contour, line, or point.
- Quit edition: Select Quit Edition to exit editing mode.
- Properties: Select Properties to open the Properties dialogue of the selected contour, line, or point. The
Properties dialogue has two tabs:
- General: The General tab gives the name of the vector Layer, the Surface of the object, and any Prop-
erties of the contour, line, or point.
- Geometry: This tab gives the coordinates of each point that defines the position and shape of the contour,
line, or point.
Note: Only the commands relevant to the selected contour, line, or point are displayed in the
context menu.
Tip: You can also activate the vector tools by selecting the vector layer to edit from the Vector
Edition toolbar list. Because Atoll names all new vector layers "Vectors" by default, it
might be difficult to know which Vectors folder you are selecting. By renaming each
vectors folder, you can ensure that you select the correct folder. For information on
renaming objects, see "Renaming an Object" on page 29.
7. Press ESC to deselect the New Polygon button ( ) on the Vector Edition toolbar.
8. For Atoll to consider the new vector layer as part of the data map, you must map the vector layer. Right-click the
the Geoclimatic Parameters, the Population, or the Custom Data folder. The context menu appears.
9. Select Properties from the context menu. The Properties dialogue appears.
10. Click the Data Mapping tab. For the following geo data:
- Population Map:
i. In the Field column, "Population" is selected by default.
ii. If the vector layer contains a population density, select the check box in the Density column. If the vector
layer indicates the number of inhabitants, and not the population density, clear the check box in the
Density column.
- Geoclimatic Parameters:
- In the Field column, "Rain" is selected by default.
- Custom Data Map: The data you map will depend on the type of custom data map you created.
Tip: You can also activate the vector tools by selecting the vector layer to edit from the Vector
Edition toolbar list.
You can now edit a object in the vector layer as explained in the following sections:
"Editing the Points of Contours" on page 134
"Editing Contours Using the Toolbar" on page 132
"Editing Contours Using the Context Menu" on page 135.
i. Position the pointer over the point you want to move. The pointer changes ( ).
ii. Drag the point to its new position.
- Adding a point to a contour:
i. Position the pointer over the contour border where you want to add a point. The pointer changes ( ).
ii. Right-click and select Insert Point from the context menu. A point is added to the contour border at the
position of the pointer.
- Deleting a point from a contour:
i. Position the pointer over the point you want to delete. The pointer changes ( ).
ii. Right-click and select Delete Point from the context menu. The point is deleted.
In Atoll, you can create complex contours by using the tools on the Vector Edition toolbar.
To edit a vector object using the icons on the Vector Edition toolbar:
1. Put the vector layer containing the contour in editing mode as explained in "Editing Contours on the Vector Layer"
on page 134.
2. Click the contour to edit. The Vector Edition toolbar has the following buttons:
ii. Click once on the map where you want to begin drawing the contour that will overlap the selected one.
iii. Click each time you change angles on the border defining the outside of the contour.
iv. Double-click to close the contour. Atoll creates a new contour of the overlapping area of the two contours
and deletes the parts of the contours that do not overlap.
When you are editing contours, you can access certain commands using the context menu.
To edit a vector object using the context menu:
1. Click the vector object you want to edit.
2. Right-click the vector object to display the context menu and select one of the following:
- Delete: Select Delete to remove the selected contour from the map.
- Insert Point: Select Insert Point to add a point to the border of the contour at the position of the pointer.
- Move:
i. Select Move from the context menu to move the contour, line, or point on the map.
ii. Move the contour, line, or point.
iii. Click to place the contour, line, or point.
- Quit edition: Select Quit Edition to exit editing mode.
- Properties: Select Properties to open the Properties dialogue of the selected contour. The Properties dia-
logue has two tabs:
- General: The General tab gives the name of the vector Layer, the Surface of the object, and any Prop-
erties of the contour.
- Geometry: This tab gives the coordinates of each point that defines the position and shape of the contour.
Once you save a vector layer, the exported file replaces the vector layer as a linked file. You can embed the file afterwards
(see "Embedding Geographic Data" on page 113).
To export a vector layer:
1. On the Explorer window tab containing the vector layer, right-click the vector layer folder. The context menu
appears.
2. Select Save As from the context menu. The Save As dialogue appears.
3. In the Save As dialogue, browse to the folder where you want to save the file, enter a name for the file, and select
the file format from the Save as type list. You can select from one of the following file formats:
- AGD: The Atoll Geographic Data format is an Atoll-specific format. As a format created for Atoll, Atoll can
read AGD files faster than the other supported vector formats.
- SHP: The ArcView vector format should be used for vector layers containing only polygons; it cannot save
vectors made of lines or points. If you have a vector layer with vector lines or points, use either the AGD, the
MIF or the TAB format.
- MIF and TAB: MapInfo formats.
4. Click Save in the Save As dialogue. The Vector Export dialogue appears, displaying the current coordinate
system and allowing you to change the coordinate system by clicking Change.
5. Click Export. The vector layer is saved in the format and with the name you specified and the exported file
replaces the vector layer in the current document as a linked file.
Caution: You will not be warned that you are replacing the current file. Therefore, ensure that you
want to replace the current file before proceeding to the following step. If you do not want
to replace the current file, you can save your changes to an external file ("Exporting an
Edited Vector Layer in Vector-Format File" on page 136).
a. The Vector Export dialogue displays the coordinate system of the file. To change the coordinate system used
for the exported file, click Change. The Coordinate Systems dialogue appears. For information on the Co-
ordinate Systems dialogue, see "Setting a Coordinate System" on page 92.
b. Click Export. The geo data file is exported with the selected coordinate system.
If the geo data file is a raster file, the Export dialogue appears (see Figure 3.20).
Geoclimatic maps
To create a new file from a section of a larger file:
1. Click the Geo tab in the Explorer window.
2. Right-click the folder of the embedded geo data file you want to export. The context menu appears.
3. Select Save As from the context menu. The Save As dialogue appears.
4. Enter a File name and select a file type from the Save as type list.
5. Click OK. The Export dialogue appears (see Figure 3.19).
6. Under Region, select The Computation Zone. This option allows you to export the geo data contained by a rec-
tangle encompassing the computation zone, whether or not the computation zone is visible. The exported geo
data file will be added as a new object to the selected geo data folder.
7. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1.
8. Click OK. The selected data is saved as a new file.
Atoll
RF Planning and Optimisation Software
Chapter 4: Antennas and Equipment
Tip: When you create a new antenna, you can copy the horizontal and vertical antenna
patterns from a spreadsheet or word processor.
To create an antenna:
1. Click the Data tab in the Explorer window.
2. Right-click on the Antennas folder. The context menu opens.
3. Select New from the context menu. A properties dialogue appears.
4. Click the General tab. You can enter information in the following fields:
- Name: Atoll automatically enters a default name for each new antenna. You can modify the name Atoll enters
if you wish.
- Manufacturer: The name of the antenna manufacturer.
- Gain: The antennas isotropic gain.
- Pattern Electrical Tilt: The antennas electrical tilt. This field is for information only; for an antennas electrical
tilt to be taken into consideration in calculations, it must be integrated into the horizontal and vertical patterns.
Atoll automatically calculates the pattern electrical tilt if the Pattern Electrical Tilt field is left blank or has a
value of "0."
Note: If you use the same antenna several times but with a different electrical tilt, you must
create a new antenna with corresponding patterns for each electrical tilt.
d. Switch to Atoll.
e. Click the upper-left cell of the horizontal pattern.
f. Press CTRL+V to paste the data in the table.
- If there are some blank rows in your data sheet, Atoll will interpolate the values in order to obtain a com-
plete and realistic pattern.
- When performing a calculation along an angle for which no data is available, Atoll calculates a linear inter-
polation from the existing pattern values.
g. Click Apply to display the pattern.
6. Click the Vertical Pattern tab. The Vertical Pattern tab has a table describing the vertical antenna pattern in terms
of the attenuation in dB (Att.) per Angle and a graphical representation of the pattern. Atoll allows you to enter
antenna pattern attenuations for as many as 720 angles. Therefore, attenuation values can also be defined for
angles other than integer values from 0 to 359. If you have the vertical pattern in a spreadsheet or text document,
you can copy the data directly into the table as described in step 5.
7. Click the Other Properties tab. You can define the following fields (not used in any calculation):
- Beamwidth: In a plane containing the direction of the maximum lobe of the antenna pattern, the angle
between the two directions in which the radiated power is one-half the maximum value of the lobe. Translated
in terms of dB, half power corresponds to -3 dB. In this window, you may enter this angle in degrees.
- FMin: The minimum frequency that the antenna is capable of emitting.
- FMax: The maximum frequency that the antenna is capable of emitting.
8. Click OK.
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.
Field Definition
FRONT_TO_BACK The ratio of forward antenna gain at 0 and 180 degree elevation
For more information on working with databases, see The Administrator Manual.
To import Planet-format antennas:
1. Select the Data tab in the Explorer window.
2. Right-click the Antennas folder. The context menu appears.
3. Select Import from the context menu. The Open dialogue appears.
4. Select "Planet 2D Antenna Files (index)" from the Files of type list.
5. Select the index file you want to import and click Open. The antennas are imported.
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.
6. If you already have an import configuration defining the data structure of the imported file, you can select it from
the Configuration list. If you do not have an import configuration, continue with step 7.
a. Under Configuration, select an import configuration from the Configuration list.
b. Continue with step 10.
7. Under Name, you can define a name for the imported antenna pattern. This name will appear in the Antennas
folder on the Data tab. If no name is defined, Atoll will use the file name as the name of the antenna:
- If the name of the antenna is in the file, check the Value read in the file check box and enter a Keyword
identifying the name value in the file.
- If you want to enter a name for the antenna, clear the Value read in the file check box and enter a name.
8. Under Gain, you can define the antenna gain. If no gain is defined, Atoll will assume that the gain is "0."
- If the gain of the antenna is in the file, check the Value read in the file check box and enter a Keyword iden-
tifying the gain value in the file.
- If you want to enter a gain for the antenna, clear the Value read in the file check box and enter a gain value.
9. Under Diagram, you define the structure of the antenna pattern file. As you modify the parameters, the results are
displayed in the table.
- 1st Pattern: Select the first row of the file containing data on the antenna pattern.
- File Tilt Range: Select the tilt range in the file. The tilt range can be measured from top to bottom or from
bottom to top and from 0 to 180 or from -90 to 90.
- Field Separator: Select the character that is used in the file to separate fields (" ", "<tab>", ";")
- Decimal Symbol: Select the decimal symbol.
10. In the table under Diagram, click the title in each column in the table and select the data type: Azimuth, Tilt,
Attenuation, or <Ignore>. As you modify the parameters, the results are displayed in the table.
Note: You can save the choices you have made in the Setup dialogue as a configuration file by
clicking the Save button at the top of the dialogue and entering a name for the
configuration. The next time you import a three-dimensional antenna pattern file, you can
select the same settings from the Configuration File list.
11. Click Import. The antenna patterns are imported into the current Atoll document.
Important: You should make a copy of the antenna before smoothing its vertical pattern. You can
make a copy of the antenna by opening the Antennas table and copying and pasting the
antenna data into a new row. For information on data tables, see "Working with Data
Tables" on page 50.
4.2.4 Updating the Values for Total Losses and the BTS Noise Fig-
ure for Transmitters
Once equipment is defined and assigned to a transmitter, Atoll can evaluate downlink and uplink total losses and the total
noise figure.
Atoll uses the entry of the BTS as the reference point when evaluating total losses and the total noise figure. The BTS
noise figure used by Atoll is the one specified in the BTS properties. Transmitter reception losses include feeder reception
losses, connector reception losses, miscellaneous reception losses, antenna diversity gain, TMA benefit gain (as calcu-
lated using the Friis equation), and an additional loss modelling the noise rise generated from repeaters (if any). Trans-
mitter transmission losses include feeder transmission losses, connector transmission losses, miscellaneous transmission
losses, and TMA transmission losses. For more information on the total noise figure and on transmitter reception and
transmission losses, see the Technical Reference Guide.
You can assign equipment to a transmitter:
Using the Equipment Specifications dialogue, available by clicking the Equipment button on the Transmitter tab
of the transmitters Properties dialogue, or
Using the Transmitters table, available by right-clicking the Transmitters folder on the Data tab of the Explorer
window and selecting Open Table from the context menu.
When you assign equipment to a transmitter using the Equipment Specifications dialogue, Atoll updates the real values
when you click OK and close the dialogue. When you assign equipment to a transmitter using the Transmitters table,
Atoll does not update the real values automatically.
To update the real values (total losses and the BTS noise figure) with the computed values of all transmitters:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Equipment > Recalculate Losses and Noise Figure from the context menu.
To update the real values (total losses and the BTS noise figure) with the computed values of a group of transmitters:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select from the Group by submenu of the context menu the property by which you want to group the transmitters.
The objects in the folder are grouped by that property.
4. Click the Expand button ( ) to expand the Transmitters folder.
5. Right-click the group of transmitters whose real values you want to update. The context menu appears.
6. Select Open Table from the context menu. The Transmitters table appears with the transmitters from the
selected group.
7. In the Transmitters table, select the values you want to update in the following columns and press DEL:
- Transmission Loss (dB)
- Reception Loss (dB)
- BTS Noise Figure (dB)
Atoll automatically recalculates and updates these values.
Tip: When you create a new antenna, you can copy the horizontal and vertical antenna
patterns from a spreadsheet or word processor.
To create an antenna:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to the left of the Microwave Radio Links folder to expand the folder.
3. Right-click the Links folder. The context menu appears.
4. Select Antennas > New from the context menu. The MW Antennas New Element Properties dialogue appears.
5. Click the General tab. You can enter information in the following fields:
- Name: Atoll automatically enters a default name for each new antenna. You can modify the name Atoll enters
if you wish.
- Manufacturer: The name of the antenna manufacturer.
- Frequency Band: The frequency band that this antenna will be used with.
- Gain: The antennas isotropic gain.
- Diameter: The diameter of the antenna.
- Under Cross Polar Discrimination (XPD), displays the cross polar discriminations for horizontal and vertical
polarisations.
- Horizontal: The ratio of power received in the cross-polar section to the power received in the co-polar
section, for the horizontal polarisation.
- Vertical: The ratio of power received in the cross-polar section to the power received in the co-polar
section, for the vertical polarisation.
- Comments: Any additional information on the antenna.
6. Define the co-polar and cross-polar sections for each plane of the antenna.
A microwave antenna is defined by 8 radiation patterns. On each of the four tabs of the antenna properties
dialogue, you can define the co-polar and cross-polar sections for each plane of the antenna:
- Horizontal polarisation - Horizontal plane:
- Co-polar section: Horizontal polarised port response to a horizontally polarised signal in the horizontal
plane.
- Cross-polar section: Vertical polarised port response to a horizontally polarised signal in the horizontal
plane.
- Horizontal polarisation - Vertical plane:
- Co-polar section: Horizontal polarised port response to a horizontally polarised signal in the vertical plane.
- Cross-polar section: Vertical polarised port response to a horizontally polarised signal in the vertical plane.
- Vertical polarisation - Horizontal plane:
- Co-polar section: Vertical polarised port response to a vertically polarised signal in the horizontal plane.
- Cross-polar section: Horizontal polarised port response to a vertically polarised signal in the horizontal
plane.
- Vertical polarisation - Vertical plane:
- Co-polar section: Vertical polarised port response to a vertically polarised signal in the vertical plane.
- Cross-polar section: Horizontal polarised port response to a vertically polarised signal in the vertical plane.
a. Switch to the document containing the horizontal pattern.
b. Select the columns containing the angles and attenuation values of the horizontal pattern.
c. Copy the selected data.
d. Switch to Atoll.
e. Click the upper-left cell of the horizontal pattern.
f. Paste the data in the table.
- If there are some blank rows in the data sheet, Atoll will interpolate the values in order to obtain a complete
and realistic pattern.
- When performing a calculation along an angle for which no data is available, Atoll calculates a linear inter-
polation from the existing pattern values.
g. Click Apply to display the pattern.
7. Click OK.
If some values are missing in the data sheet, Atoll interpolates the values in order to obtain a complete and realistic pattern
around the antenna. When you paste the data into the MW Antennas New Element Properties dialogue, Atoll removes
blank rows in the pattern table when you press the Apply button. When you calculate along an angle for which no data is
available, Atoll calculates a linear interpolation from existing pattern values.
6. Click the Browse button ( ) to navigate to the file or the folder to be imported.
7. Select the file or folder to be imported and click Open.
8. Click Import. The file or folders are imported.
Atoll does not stop the import process if an error occurs. Atoll continues until all files are imported and then displays in
the Events viewer how many files have been successfully and unsuccessfully imported.
For more information on importing microwave antennas in the Planet format, see the Administrator Manual.
Note: You can display antenna patterns with either linear or logarithmic axes. You can define
the display by right-clicking the pattern window and choosing the either Linear display or
Logarithmic display from the context menu.
Atoll enables you to copy antenna patterns within the MW Antennas table. By copying and pasting patterns in the MW
Antennas table you can assign antenna patterns from one antenna to another.
To open the MW Antennas table:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to the left of the Microwave Radio Links folder to expand the folder.
3. Right-click the Links folder. The context menu appears.
4. Select Antennas > Open Table from the context menu. The MW Antennas table appears.
1. For further information about the standard NSMA format (recommendation WG16.99.050), see the following web
site:
http://www.fcc.gov/oet/info/software/nsma/nsma-intrp.html.
By resizing row height and column width, you can view all antenna patterns in order to be able to compare them
(see Figure 4.4).
5. In the row of the antenna with the pattern you want to copy, select the cell with the pattern.
6. Select Edit > Copy to copy the cell.
7. In the row of the antenna you want to copy the pattern to, select the cell with the pattern.
8. Select Edit > Paste to paste the antenna pattern.
Atoll replaces the old pattern with the new one in the MW Antennas table.
Notes:
You can also copy an antenna pattern by right-clicking the pattern on the tab of the antennas
Properties dialogue and selecting Copy from the context menu.
Patterns are displayed in the MW Antennas table with either linear or logarithmic axes as
defined in the Properties dialogue of an individual antenna. You can define the display by
right-clicking the pattern of an antenna and choosing either Linear display or Logarithmic
display from the context menu.
The IDU is the termination point of the end-user equipment that generates the data to be carried by the microwave link. It
consists of the following components:
The radio modem that converts the digital signal into a form suitable for modulation on the radio carrier signal
The power supply for the Outdoor Unit (ODU)
The ODU converts the modulated signal from its low frequency form to a high frequency radio signal in the appropriate
radio band and channel for radio transmission.
Antenna
The antenna is the part of the microwave link that transmits electromagnetic energy from transmission lines into the air
and receives transmitted electromagnetic energy from the air to be then sent on transmission lines. The antenna can be
in one of many different shapes (for example, horn, parabolic, flat or planar, lens, yagi, or array) to achieve its specific
objectives.
The main characteristics of the microwave antenna are the following:
Directivity: In practical terms, directivity is defined as:
- The ability to send the transmitted power in only the desired direction
- The ability to reject undesired signals coming from other directions.
Gain: The gain is the amount of power radiated in a given direction using only the RF power at the input terminals
of the antenna.
Front-to-Back Ratio (FBR): The FBR is the ratio of the power radiated in the desired direction to the power radi-
ated in the opposite direction, typically between 35 and 50 dB. In general, the higher the gain of the antenna, the
higher the FBR.
Radiation pattern: The radiation pattern is a diagram showing the direction of the radiated power. The portion of
the pattern where the maximum gain occurs is often referred to as the main lobe of the pattern
Polarisation: Polarisation is the ability to transmit only one of the two electromagnetic vector components of the
wave (either the horizontal component or the vertical component). Using polarisation enables the same radio fre-
quency to be used by different radio systems in physical proximity to one another.
Cross Polarisation Discrimination (XPD): The XPD is the ratio of power received in the desired polarisation to
the power received in undesired polarisation. XPD is a design parameter that is maximized in the main lobe of the
antenna pattern.
- Enter the maximum power (Max Power) and the Noise Figure.
- Enter the power range reserved for Adaptive Transmission Power Control (Max ATPC) and the maximum
improvement factor reserved for cross-polarisation reduction (XPIF).
The Max ATPC is used by the transmitter to adjust power by increasing or reducing it in order to maintain sig-
nal quality in case of multipath or rain fading that temporarily attenuates the received signal. Max ATPC also
enables the transmitter to respond to increased interference levels resulting from ATPC on other links. The
Max ATPC can be optionally taken into consideration during calculations.
The maximum improvement factor reserved for cross-polarisation reduction (XPIF) is used only when an XPIC
(cross-polarized interference canceller) is present. It is used to reduce the scattering of interference from the
undesired polarisation into the desired polarisation due to rain fading by increasing the cross-polarisation dis-
crimination factor (XPD). XPIF is generally within the range of 15-20 dB.
- Specify the System Configuration (i.e., the equipment protection configuration). The system configuration is
defined in the form of "n + m" where "n" is the number of active channels and "m" is the number of standby
channels. Standby channels are inactive and used only when active channels fail. Switching to the standby
channel in case of failure can be automatic and is then referred to a "hot" standby system. If the system must
be manually switched to the standby channel, the system is called a "cold" standby system. If a hot standby
system is available, you must select the Hot Standby Available check box. For a hot standby system, the
standby channel frequency must be the same as one of the active channels. For cold standby systems, the
standby channel frequency can be different from active channels. Frequencies allocated to active and standby
channels are defined in the microwave link properties dialogue.
1 + 1 redundancy mode is modelled as shown below:
In this system configuration, only the main equipment is active and on. The other equipment, which will serve
as a back-up in case the main equipment fails, is not turned on.
1 + 1 redundancy mode with monitored hot standby (Hot Standby Available) is modelled as shown below:
In this system configuration, both the main and standby equipment are on, but only the main equipment is ac-
tive. The standby equipment will be automatically put into service immediately if the main equipment fails.
- Under Radio Signature, choose the method to be used to predict outage times (dispersive fade margin) due
to multipath fading.
Note: The radio signature parameters are not used by all types of receiver equipment.
This method will characterise the ability of a receiving equipment to perform successfully (i.e., produce accept-
able errors rates) in the presence of frequency-selective fading.
- Normalised: For a normalised signature, select Normalised and enter a value for the Kn Parameter. The
Kn parameter is mostly dependant on the modulation used.
Modulation Kn
64-QAM 15.4
16-QAM 5.5
8-PSK 7
4-PSK 1
- Rummler Model: If you want to use the Rummler model to predict outage times, select Rummler model,
and define the frequency shift (Width) and Depth for both minimum and non-minimum phases. For more
information, see studies by C.W. Lundgren and W.D. Rummler1 and the ITU P.530 recommendation.
6. On the Hierarchy and Rate tab of Properties dialogue, set the following parameters:
- Under Digital Hierarchy, select the digital hierarchy type (SDH/SONET or PDH).
- Under Rate, select the Capacity (i.e., the number of trunks) and the trunk type from the list.
The rate is calculated by the capacity per trunk multiplied by the number of trunks:
The minimal and standardised channel bandwidth resulting from the parameters defined on the Hierarchy and
Rate tab is displayed under Channel Bandwidth. You can enter the channel bandwidth defined by the man-
ufacturer in the From manufacturer text box.
1. C.W. Lundgren and W.D. Rummler, "Digital radio outage due to selective fading- observation vs. prediction from
laboratory simulations," Bell System Technical Journal, pp. 1073-1100, May-June 1979.
W.D. Rummler, "Characterizing the effects of multipath dispersion on digital radios," IEEE Globecom Proceedings, pp.
1727-1732, 1988.
- User-defined C/I min.: If you want to define a minimum CI, select User-defined C/I min., and define an
interference margin in the For a Margin Against Interference Of text box, as well as the quality required
for a BER of 10-3 and 10-6 in the For a BER of 1e-3 and the For a BER of 1e-3 text boxes.
- For each circulator present on this piece of equipment, set the Port it is attached to, and define the losses on
Transmission and Reception.
10. On the Transmitter Mask tab of Properties dialogue, define the transmitter spectral mask either by clicking the
Initialise from standard graphs button, to let Atoll create the mask from standard values, or by defining an atten-
uation in dB (Att.) for each frequency shift in MHz (Delta F). This information is provided by the equipment man-
ufacturer.
The resulting transmitter mask is displayed in the graph window on the right.
11. On the Receiver Mask tab of Properties dialogue, define a receiver mask either by clicking the Initialise from
standard graphs button, to let Atoll create the mask from standard values, or by defining an attenuation in dB
(Att.) for each frequency shift in MHz (Delta F). This information is provided by the equipment manufacturer.
The resulting receiver mask is displayed in the graph window on the right.
12. On the TI Curve tab of Properties dialogue, define a threshold-to-interference (TI) curve either by clicking the
Initialise from standard graphs button, to let Atoll create the curve from standard values, or by defining an atten-
uation in dB (Att.) for each frequency shift in MHz (Delta F). This information is provided by the equipment man-
ufacturer.
The threshold-to-interference (T/I) ratio is used to calculate the interference fade margin (IFM) which defines the
vulnerability to co-channel and adjacent channel interference. It is provided by the manufacturer. The T/I curve
defines the curve of maximum interfering power levels for different frequency separations between the transmitter
and victim receivers. For each interfering transmitter, the received power level in dB is compared to the maximum
power level to determine whether the interference is acceptable. This is done instead of calculating C/I values and
comparing them to the published objectives.
6. Click the Browse button ( ) to navigate to the file or the folder to be imported.
7. Select the file or folder to be imported and click Open.
8. Click Import. The file or folders are imported.
Notes: Atoll does not stop the import process when an error occurs. It continues until all the files
have been imported and then displays in the Events viewer how many files have been
successfully and unsuccessfully imported.
Atoll has a set of default trunk type definitions available, but you can create new trunk types and set their parameters.
Note: If you are creating a large number of different trunk types from manufacturers data, it can
take a long time. However, if you have the data available in tabular format, you can copy it
from the spreadsheet or word processor and paste the data into the Trunk Type table.
5. For each trunk type you define, add the following data:
- Trunk Type: The name of the trunk type that will model the digital hierarchy.
- SDH/SONET: If the check box is selected ( ), the digital hierarchy being modelled is SDH or SONET. If the
check box is not selected ( ), the digital hierarchy being modelled is PDH.
- Binary Rate (Mbit/s): The binary rate is the gross data rate of the frame if all the bits are used for traffic.
- Binary Rate Supported (Mbit/s): The binary rate supported is the payload rate (i.e., the rate of the useful bits
not including the overheads bits).
- No. Bits/Block: The number of bits per block corresponds to the number of bits per frame (i.e., the useful bits
plus the overheads bits).
- BERses: BERses corresponds to Bit Error Rate (BER) as documented in Annex 2, Table 2) of the ITU-R
P.530-8 recommendation.
You can also define the properties of a trunk type in its Properties dialogue.
To open a trunk types Properties dialogue:
Double-click the trunk type in the left margin of the Trunk Types table. The trunk types Properties dialogue
appears (see Figure 4.9).
the equipment if available, or the theoretical "TI" graphs if not (for more information on the theoretical graphs, see
"Theoretical Graphs" on page 162).
2. If the equipment manufacturer, capacity, or modulation are not the same, Atoll merges the transmitter mask and
the receiver mask of equipment in order to determine the IRF graph. Atoll uses either the graphs defined for the
equipment if available, or the theoretical graphs if not.
In this section, the following are explained:
"Defining IRF Graphs Manually" on page 160
"Defining IRF Graphs with the Assistant" on page 161.
The following sections describe the modelling of IRF in Atoll.
You can define IRF graphs using the IRF table. These IRF graphs will be used to reduce the interference between victim
and interferer microwave equipment when calculating interference.
To create or modify an IRF graph:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Microwave Radio Links folder
3. Right-click on the Links folder. The context menu appears.
4. Select Equipment > IRF > Open Table from the context menu. The Trunk Types table appears (see
Figure 4.10).
Note: If you are creating a new IRF graph, use the row marked with the New Row icon ( )
7. Double-click in the left margin of the record to open its Properties dialogue (see Figure 4.11).
8. Under Protection values in the Properties dialogue, enter a protection level (in dB) for each delta frequency (in
MHz). The resulting graph is displayed on the right of the Properties dialogue.
9. Click OK.
Atoll provides an assistant to allow you to define IRFs between transmission and reception transceiver equipment. When
you select a frequency band and the equipment manufacturers with equipment that operate in the same frequency band,
Atoll presents the entries where the transmission and reception equipment present the possibility of interference.
To use the assistant to define IRFs:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Microwave Radio Links folder
3. Right-click on the Links folder. The context menu appears.
4. Select Equipment > IRF > Edit Grid from the context menu. The IRF Setting dialogue appears (see Figure 4.10).
5. Select the Frequency Band from the menu. Only equipment operating in the selected frequency band is displayed
in the grid.
6. Select the TX Equipment Manufacturer from the menu. Only equipment manufactured by the selected manufac-
turer are displayed in the grid.
7. Select the RX Equipment Manufacturer from the menu. Only equipment manufactured by the selected manufac-
turer are displayed in the grid.
8. You can now define an IRF graph, delete an IRF graph, or create an IRF graph using equipment graphs or theo-
retical graphs:
a. Right-click on the cell of the grid that coincides with both entries. The context menu appears.
b. Select Add Record from the context menu. A dialogue appears.
c. Under Enter graph values, enter a protection level (in dB) for each delta frequency (in MHz). The resulting
graph is displayed on the right of the dialogue.
d. Click OK.
To delete an IRF graph between the transmission and reception equipment:
a. Right-click on the cell of the grid that coincides with both entries. The context menu appears.
b. Select Delete from the context menu.
To create an IRF graph between the transmission and reception equipment using equipment graphs or theoretical
graphs:
a. Right-click on the cell of the grid that coincides with both entries. The context menu appears.
b. Select Calculate from Masks from the context menu. The IRF Calculation dialogue appears.
c. Under Transmitter Filter, select either "As Equipment" to use the transmission spectrum graph defined for
the equipment, or select a theoretical "transmission spectrum" graph compatible with the operating frequency
band of the transmission equipment.
d. Under Reception Filter, select either "As Equipment" to use the receiver selectivity graph defined for the
equipment, or select a theoretical "receiver selectivity" graph compatible with the operating frequency band of
the reception equipment.
e. Define the calculation step stated in frequency spacing (MHz).
f. Click Run to calculate the IRF graph.
g. Click OK.
9. Click OK to close the IRF Setting dialogue.
A theoretical graph contains information on the behaviour of microwave transceiver equipment under different conditions
of C/I. It represents the changes in the Bit Error Rate as a function of the level of interference.
To create a theoretical graph:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Microwave Radio Links folder.
3. Right-click the Links folder. The context menu appears.
4. Select Equipment > Theoretical Graphs from the context menu. The Theoretical Graphs table appears.
5. Right-click the theoretical graph you want to modify. The context menu appears.
6. Select Record Properties from the context menu. The theoretical graphs Properties dialogue appears.
Note: You can create a new theoretical graph by entering a name in the row marked with the
New Row icon ( ) and pressing ENTER.
1. T/I curves have been found at the web address http://www.radio.gov.uk and transmitter and receiver masks have
been found at http:\\www.ero.dk.
9. Click OK.
In Atoll, microwave waveguides and cables are characterised by the loss a signal undergoes per 100m of their length.
Once a microwave waveguide or cable has been defined, you can assign it to a microwave link for both transmission and
reception.
Note: If you are creating a large number of waveguides and cables based on manufacturers
data, it can take a long time. However, if you have the data available in tabular format, you
can copy it from the spreadsheet or word processor and paste the data into the
MWGuides table. For information on the MWGuides table, see "Modifying a Microwave
Waveguide or Cable" on page 164.
In Atoll, you can access and modify any defined microwave waveguide or cable using the MWGuides table.
To modify a microwave waveguide or cable:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Microwave Radio Links folder.
3. Right-click the Links folder. The context menu appears.
4. Select Waveguides and Cables > Open Table from the context menu. The Waveguides and Cables table
appears.
5. Right-click the record in the Waveguides and Cables table that you want to modify. The context menu appears.
6. Select Record Properties from the context menu. The records Properties dialogue appears.
7. For the waveguide or cable, you can modify the following parameters:
- Name: The name of the waveguide or cable.
- Frequency Band: Select the frequency band from the list. Clicking the Browse button ( ) opens the Prop-
erties dialogue of the selected frequency band.
- Manufacturer: Select the manufacturer from the list. Clicking the Browse button ( ) opens the Properties
dialogue of the selected manufacturer.
- Signal Loss: Enter the signal loss in dB per 100 m.
- Type: Select the type of waveguide or cable. You can select from Cable, Circular, Elliptic, Other, or Rectan-
gular.
8. Click OK.
Note: If you have a large number of antenna/equipment compatibility pairs to enter, you can
import them by right-clicking on the table and selecting Import from the context menu, or
you can paste them into the Antenna/Guides Compatibility table.
Note: If you have a large number of antenna/equipment compatibility pairs to enter, you can
import them by right-clicking on the table and selecting Import from the context menu, or
you can paste them into the Antenna/Equipment Compatibility table.
8. You can now define the compatibility between an antenna and a waveguide or delete a defined compatible
antenna-waveguide pair:
a. Right-click on the cell of the grid that coincides with both entries. The context menu appears.
b. Select Add Record from the context menu. The cell is marked in green to indicate that the antenna and
waveguide are compatible.
To delete a defined compatible antenna-waveguide pair:
a. Right-click on the cell of the grid that coincides with both entries. The context menu appears.
b. Select Delete from the context menu. The cell is no longer marked in green.
9. Click OK.
You can use the Fill (Up, Down, Right, Left) and the Copy and Paste commands to create or delete compatible antenna-
waveguide pairs.
8. You can now define the compatibility between an antenna and equipment, delete a defined compatible antenna-
equipment pair, or define compatibility with an antenna, a piece of equipment, and waveguides:
a. Right-click on the cell of the grid that coincides with both entries. The context menu appears.
b. Select Add Record from the context menu. The cell is marked in green to indicate that the antenna and equip-
ment are compatible.
To delete a defined compatible antenna-equipment pair:
a. Right-click on the cell of the grid that coincides with both entries. The context menu appears.
b. Select Delete from the context menu. The cell is no longer marked in green.
To define compatibility with an antenna, a piece of equipment, and waveguides:
a. Right-click on the cell of the grid that coincides with the entries for the antenna and the equipment. The context
menu appears.
b. Select Add Record from the context menu. The cell is marked in green to indicate that the antenna and equip-
ment are compatible.
c. Right-click on the square and select Record Properties from the context menu. The properties dialogue
opens.
d. In the properties dialogue, under List of the Compatible Guides, select the waveguides that you want to
make compatible with this antenna/equipment pair. If you have previously defined compatible antenna/
waveguide pairs, these are taken into account and, by default, the waveguides compatible with the corre-
sponding antenna are selected.
e. Click OK to close the properties dialogue.
9. Click OK.
You can use the Fill (Up, Down, Right, Left) and the Copy and Paste commands to create or delete compatible antenna-
equipment pairs.
Atoll
RF Planning and Optimisation Software
Atoll User Manual
Frequency
Model Geo Data Taken into Account Recommended Use
Band
Longley-Rice - Flat areas
~ 40 MHz - Terrain profile
(theoretical) - Very low frequencies
- Fixed receivers
- Terrain profile
WLL 30 10000 MHz > Microwave links
- Deterministic clutter
> WiMAX
1 < d < 20 km
- Terrain profile > GSM 900
Okumura-Hata 150 1000 MHz
- Statistical clutter (at the receiver) > CDMA2000
> LTE
1 < d < 20 km
- Terrain profile > GSM 1800
Cost-Hata 1500 2000 MHz
- Statistical clutter (at the receiver) > UMTS
> LTE
Frequency
Model Geo Data Taken into Account Recommended Use
Band
1 < d < 100 km
- Terrain profile > GSM 900
ITU 529-3 300 1500 MHz
- Statistical clutter (at the receiver) > CDMA2000
> LTE
1 < d < 20 km
> GSM 900
> GSM 1800
Standard Propagation - Terrain profile > UMTS
150 3500 MHz
Model - Statistical clutter > CDMA2000
> WiMAX
> LTE
(Automatic calibration available)
1 < d < 20 km
- Terrain profile
Sakagami Extended 3000 8000 MHz > WiMAX
- Statistical clutter
(Automatic calibration available)
where:
These parameters can be defined on the tabs (Parameters, and Clutter) of the Standard Propagation Model Properties
dialogue. You can also calibrate the Standard Propagation Model using a wizard. For information on the Automatic Cali-
bration Wizard, see the Measurements and Model Calibration Guide.
In this section, the following are explained:
"Recommendations for Working with the Standard Propagation Model" on page 172
"Calculating Diffraction With the SPM" on page 172
"Sample Values for SPM Formulas" on page 173
"Calculating f(clutter) with the Standard Propagation Model" on page 173
"Modelling Fixed Receivers" on page 174
"Defining the Parameters of the Standard Propagation Model" on page 174.
Note: Because the Standard Propagation Model is a statistical propagation model, using this
approach is recommended.
Approach #2: If you consider clutter altitudes, do not define any loss per clutter class. In this case, f(clutter) will
be "0;" losses due to clutter will only be taken into account in the calculated diffraction. This approach is recom-
mended if the clutter altitude information is semi-deterministic (i.e., where the clutter is roughly defined with an
average altitude per clutter class) or deterministic (i.e., where the clutter is sharply defined with an average altitude
per clutter class or where there is a clutter height file).
If the clutter height information is an average height defined for each clutter class, you must specify a receiver
clearance per clutter class. Both ground and clutter altitude are considered along the whole transmitter-receiver
profile except over a specific distance around the receiver (clearance), in which Atoll bases its calculations only
on the DTM. The clearance information is used to model streets because it is assumed that the receiver is in the
street.
It is not necessary to define receiver clearance if the height information is from a clutter height file. In this case,
the clutter height information is accurate enough to be used without additional information such as clearance; Atoll
calculates the path loss if the receiver is in the street (if the receiver height is higher than the clutter height). If the
receiver height is lower than the clutter height, the receiver is assumed to be inside a building. In this case, Atoll
does not consider any diffraction for the building (or any clearance) but takes into account the clutter class indoor
loss as an additional penetration loss. Nevertheless, Atoll does consider diffraction caused by surrounding build-
ings. In Figure 5.1 on page 172 this diffraction is displayed with a green line.
Important: In order to consider indoor losses inside a building when only using a deterministic clutter
map (i.e., a clutter height map), you must clear the Indoor Coverage check box when
creating a prediction or indoor losses will be added twice (once for the entire reception
clutter class and once as indoor losses).
Figure 5.1: Diffraction caused by surrounding buildings when the receiver is indoors
For detailed information on each method, see the Technical Reference Guide. The methods for calculating diffraction are
based on the general method for one or more obstacles described in the ITU 526-5 recommendations. The calculations
take the curvature of the earth into account. Along the transmitter-receiver profile, you can choose to take either the ground
altitude only or both the ground altitude and the clutter height into account. If you choose to take clutter height into account,
Atoll uses the clutter height information in the clutter heights file. Otherwise, it uses average clutter height specified for
each clutter class in the clutter classes. When the clutter height information is statistical, Atoll also uses clearance values
per clutter class to model streets.
To take heights into account when calculating diffraction:
1. Click the Modules tab of the Explorer window.
2. Click the Expand button ( ) to expand the Propagation Models folder.
3. Right-click Standard Propagation Model. The context menu appears.
4. Select Properties from the context menu. The Properties dialogue appears.
5. Click the Clutter tab.
6. Under Heights, select one of the following for Clutter taken into account in diffraction:
- 1 - Yes: Select "1 - Yes" if you want heights from the clutter heights to be taken into account on top of the DTM
when calculating diffraction.
- 0 - No: Select "0 - No" if you want diffraction to be calculated using only the DTM.
7. Click OK.
K2 20 44.9 70
K3 -20 5.83 20
K4 0 0.5 0.8
K5 -10 -6.55 0
K6 -1 0 0
K7 -10 0 0
K1 is a constant; its value depends on the radio frequency and on the radio technology. The following table gives some
possible values for K1.
1xRTT 1900 23
2300 24.7
2500 25.4
3300 27.8
3500 28.3
Its value is heavily influenced by the values given to losses per clutter class.
f ( clutter ) = Li wi
i=1
where
L: loss due to clutter.
w: weight.
n: number of points taken into account over the profile.
The losses due to clutter are calculated for the maximum distance from the receiver, defined as Maximum Distance on
the Clutter tab of the Standard Propagation Model Properties dialogue. When the Maximum Distance is defined as
"0", Atoll only considers the losses on the pixel where the receiver is located. On the Clutter tab, each clutter class is
assigned losses and a weighting function, enabling Atoll to give a weight to each point. For more information, see the
Technical Reference Guide.
Note: The losses per clutter class can be calculated using the Automatic Calibration Wizard.
For information on the Automatic Calibration Wizard, see the Measurements and Model
Calibration Guide.
The following table gives typical values for losses (in dB) per clutter class:
Woodland from 2 to 3
Urban 0
Suburban from -5 to -3
Industrial from -5 to -3
Note: The Standard Propagation Model is based on Hata formulas, which are valid for an urban
environment. The values above are consistent with an urban environment because losses
of 0 dB are indicated for an urban clutter class, with positive values for more dense clutter
classes and negative values for less dense clutter classes.
Note: Default values have been assigned to the multiplying factors. The default values
correspond to the rural (quasi-open) Okumura-Hata formula valid for a frequency of
935 MHz. The values for K values can be calculated using an automatic or assisted
calibration method. For more information, see the Measurements and Model Calibration
Guide.
4. Select Properties from the context menu. The Properties dialogue appears.
5. Click the Parameters tab (see Figure 5.2).
- Maximum Distance: Set the maximum distance for a receiver to be considered near the transmitter. If the
distance between the receiver and the transmitter is greater than the set distance, the receiver is considered
far from the transmitter.
- K1 - los and K2 - los: Enter the K1 and K2 values that will be used for calculations when the receiver is in the
transmitter line of sight.
- K1 - nlos and K2 - nlos: Enter the K1 and K2 values that will be used for calculations when the receiver is not
in the transmitter line of sight.
Under Far from Transmitter, the values you set will be used for all receivers whose distance from the transmitter
is greater than the distance specified in Maximum Distance under Near Transmitter. You can set the following
parameters:
- K1 - los and K2 - los: Enter the K1 and K2 values that will be used for calculations when the receiver is in the
transmitter line of sight.
- K1 - nlos and K2 - nlos: Enter the K1 and K2 values that will be used for calculations when the receiver is not
in the transmitter line of sight.
Under Effective Antenna Height, you can set the following parameters:
- Method: Select the method that will be used to calculate HTxeff, the effective antenna height.
Note: You can use the Automatic Calibration Wizard to select the best method for calculating
the effective Tx antenna height. For information on the Automatic Calibration Wizard,
see the Measurements and Model Calibration Guide.
- Distance min. and Distance max.: The Distance min. and Distance max. are set to 3,000 m and 15,000 m
(according to ITU recommendations) for frequencies under 500 MHz and to 0 m and 15,000 m (according to
ITU recommendations) for high frequency mobile communications. These values are only used for the "Abs
Spot Ht" and the "Enhanced Slope at Receiver" methods. For more information on how these values are used,
see the Technical Reference Guide.
- K3: Enter the K3 value.
Under Diffraction, you can set the following parameters:
Under Clutter Taken into Account, you can set the following parameters under Heights:
- Clutter taken into account in diffraction: Select "1 - Yes" if you want the clutter heights to be taken into
account when calculating diffraction.
- Receiver on top of clutter: Select "1 - Yes" if you want the receiver to be considered to be located on top of
clutter. This option can be used where fixed receivers are located on top of buildings.
Under Clutter Taken into Account, you can set the following parameters under Range:
- Max. distance: Set the maximum distance from a receiver to be considered when calculating f(clutter).
- Weighting function: Select a weighting function to be used when calculating f(clutter). It enables you to
weight losses for each pixel between a receiver and a maximum distance. For more information on weighting
functions, see the Technical Reference Guide.
Under Parameters per clutter class, you can set the following parameters for each clutter class:
- Losses: Enter, if desired, losses for each clutter class to be considered when calculating f(clutter).
- Clearance: Enter, if desired, a clearance around each receiver for each clutter class. The clearance informa-
tion is used to model streets because it is assumed that the receiver is in the street. The clearance is used
when calculating diffraction when statistical clutter is taken into account.
- Rx Height: Enter, if desired, a specific receiver height for each clutter class. Or, you can select "(default)" for
the receiver height. When creating a coverage prediction, Atoll will then read the receiver height on the
Receiver tab of the Properties dialogue for the Predictions folder.
7. Click OK.
7. For each clutter class under Formulas related to clutter classes, select the corresponding row. Under this grid,
choose the appropriate formula in the formula scrolling list and an optional correction (in dB). This correction acts
as an additional loss on the loss calculated by the chosen formula.
For information on modifying the selected formula, see "Creating or Modifying Environment Formulas (Okumura-
Hata)" on page 178.
8. Click OK.
Note: Correction terms can be evaluated using the Automatic Calibration Wizard. For
information on the Automatic Calibration Wizard, see the Measurements and Model
Calibration Guide.
8. Click OK.
Notes:
You can weight the diffraction loss by setting the diffraction multiplying factor within the range
]0;1].
Constant values and diffraction multiplying factor can be evaluated using the Automatic Cali-
bration Wizard for each environment formula. For information on the Automatic Calibration
Wizard, see the Measurements and Model Calibration Guide.
7. For each clutter class under Formulas related to clutter classes, select the corresponding row. Under this grid,
choose the appropriate formula in the formula scrolling list and an optional correction (in dB). This correction acts
as an additional loss on the loss calculated by the chosen formula.
For information on modifying the selected formula, see "Creating or Modifying Environment Formulas (Cost-Hata)"
on page 179.
8. Click OK.
Notes:
You can weight the diffraction loss by setting the diffraction multiplying factor within the range
]0;1].
Constant values and diffraction multiplying factor can be evaluated using the Automatic Cali-
bration Wizard for each environment formula. For information on the Automatic Calibration
Wizard, see the Measurements and Model Calibration Guide.
7. For each clutter class under Formulas related to clutter classes, select a formula from the list.
For information on modifying the selected formula, see "Creating or Modifying Environment Formulas (ITU 529-3)"
on page 180.
8. Click OK.
Note: When using the ITU 370-7 model, do not define the cell edge coverage probability in the
coverage prediction properties with a value other than 50%, or cell edge coverage
probability will be considered twice.
7. For each clutter class under Formulas related to clutter classes, select a formula from the list.
For information on modifying the selected formula, see "Creating or Modifying Environment Formulas (Erceg-
Greenstein (SUI))" on page 182.
8. Click OK.
Along the Tx-Rx profile, both ground altitude and clutter height are considered to calculate diffraction losses. Atoll takes
clutter height information in clutter heights file if available in the ATL document. Otherwise, it considers average clutter
height specified for each clutter class in the clutter classes file description. If the ATL document does not contain any clutter
height file and no average height per clutter class is specified, Atoll will consider ground altitude only.
To set the parameters on the WLL propagation model:
1. Click the Modules tab of the Explorer window.
2. Click the Expand button ( ) to expand the Propagation Models folder.
3. Right-click WLL. The context menu appears.
4. Select Properties from the context menu. The Properties dialogue appears.
5. Click the Parameters tab. You can set the following parameters:
- Free space loss: You can modify the parameters of the formula used to calculate path loss in free space.
- Line of sight only: If the Line of sight only option is selected, Atoll checks for each pixel if the receiver is
in the transmitter line of sight. The receiver is considered to be in the transmitter line of sight if 100% of the
Fresnel half-ellipsoid is clear, in other words, if no obstacle is on the transmitter-receiver profile. If the receiver
is not in the transmitter line of sight, no results at all will be displayed. If the Line of sight only option is not
selected, Atoll calculates the path loss for each pixel, using the formula defined in the dialogue.
Important: If you select the Line of sight only option and the receiver is not in the transmitter line of
sight, no results at all will be displayed because Atoll will only show results for the line of
sight.
- Transmitter clearance: You can set the clearance around the transmitter. This clearance can be used, for
example, to model streets in areas where the clutter class file does not show enough detail. It will be taken
into consideration when calculating diffraction. The default value is 20 m.
- Receiver default clearance: You can set the default clearance around the receiver. This default clearance
will be used for each clutter class where the receiver clearance is not specified. This clearance will be taken
into consideration when calculating diffraction. The default value is 20 m.
- Receiver height per clutter class: You can set a height for the receiver for each clutter class. Because the
WLL propagation model is designed for networks with immobile receivers, the receivers are often on top of
buildings. This option allows you to specify a height which will be added to the clutter class.
- Receiver clearance per clutter class: You can set a clearance around the receiver for each clutter class.
This clearance will be taken into consideration when calculating diffraction.
6. Click OK.
K
Value Assigned
Coefficient
K1 65.4 (calculated for 3.5 GHz)
K2 40
K3 -30
K4 0
K5 0
K6 0
K7 -5
For more information on working with the Standard Propagation Model, see "The Standard Propagation Model" on
page 171.
- Name: The name of the propagation model, as displayed in the Propagation Models folder
- Signature: The signature is assigned to the propagation model by Atoll. Each time you modify the param-
eters of the selected propagation model, Atoll changes the signature. The signature of the propagation
model used to calculate a set of path loss matrices is stored with the matrices. This enables Atoll to verify
the validity of the path loss matrices.
- When path loss matrices are not embedded in the Atoll document but are stored externally, the signature
is found in the MODEL_SIG field of the Pathloss.dbf file. The name of the propagation model used is found
in the MODEL_NAME field of the Pathloss.dbf file.
- Description: You can enter a description or comments in this field.
- Duplicate: The selected propagation model is duplicated. It appears in the Propagation Models folder with
the same name, preceded by "Copy of."
- Copy: The selected propagation model is copied. You can paste it, with its current settings into a new Atoll
document by opening the document, clicking the Modules tab of the Explorer window and pressing CTRL+V.
Note: If there is already a propagation model in the Atoll document with the same name as the
one you are trying to paste, Atoll will display a warning and will not allow you to overwrite
the existing propagation model.
Note: When creating coverage predictions, you can define a coverage resolution that is different
from the resolution defined for the path loss matrices.
Note: You can group transmitters by several properties by using the Group By button on the
Properties dialogue. For more information, see "Advanced Grouping" on page 66.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
Tip: By setting an option in the atoll.ini file, you can set Atoll to use the currently defined
default resolution if you clear the value entered in the Resolution text box when you
create a coverage prediction. That way, if you have many coverage predictions, you can
change their resolution by changing the default resolution and recalculating the coverage
predictions. Atoll will then calculate them using the updated resolution. For information
on changing entries in the atoll.ini file, see the Administrator Manual.
6. Click OK.
When you calculate a coverage prediction, Atoll calculates only the non-existent and invalid path loss matrices that inter-
sect the rectangle containing the computation zone, whether or not the computation zone is visible. When you manually
calculate the path loss matrices as described in this section, Atoll does not take the computation zone into consideration;
it calculates all non-existent and invalid path loss matrices of active and filtered transmitters.
To calculate path loss matrices:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Calculations > Calculate Path Loss Matrices from the context menu. Atoll calculates all non-existent
and invalid path loss matrices of active and filtered transmitters.
You can calculate the non-existent and invalid path loss matrices for all transmitters, for a single transmitter, or for a
defined group of transmitters, by expanding the Transmitters folder right-clicking either the single transmitter or the
defined group of transmitters and selecting Calculations > Calculate Path Loss Matrices from the context menu.
Note: You can prevent Atoll from calculating one or more path loss matrices by locking them.
You can lock path loss matrices using the Propagation tab of the Transmitters dialogue.
You can lock a single path loss matrix by selecting the check box in the Locked column,
or more than one by selecting several path loss matrices and then selecting Lock from
the context menu.
Click the Stop Calculations button ( ) in the toolbar. Atoll immediately stops all ongoing calculations. The
results of calculations that have already been completed, however, will be saved.
Click the button beside the Private Directory ( ) and select Embedded to save the path loss matrices in
the Atoll document, or Share to select a directory where Atoll can save the path loss matrices externally.
Caution: When you save the path loss files externally, the external files are updated as soon as
calculations are performed and not only when you save the Atoll document. In order to
keep consistency between the Atoll document and the stored calculations, you should
save the Atoll document before closing it, if you have updated the path loss matrices.
5. Click OK.
This folder is shared by all users and read only. When the user changes his radio data and recalculates the path loss matri-
ces, the changes to the path loss matrices are stored locally; the common path loss matrices are not modified. In other
words, the user can read the information from the shared path loss matrices but any changes he makes will be stored
locally, either in the ATL file or in a private external folder. Centralised path loss matrices will be recalculated by the admin-
istrator and will take into consideration the changes made by all users to the radio data.
For information on calculating path loss matrices, see "Calculating Path Loss Matrices" on page 187.
For information on setting the storage location for local path loss matrices, see "Setting the Storage Location of
Path Loss Matrices" on page 188.
For information on working in a multi-user environment, see the Administrator Manual.
To use pre-calculated path loss matrices:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for the shared path loss
matrices:
- Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a
database and the common path loss matrices are stored in a directory that is accessible to all users. Any
changes you make will not be saved to this directory; they will be saved in the location indicated in Private
Directory. The path loss matrices in the shared directory are updated by a user with administrator rights based
on the updated information in the database. For more information on shared directories, see The Administrator
Manual.
Caution: The shared path loss matrices must be unlocked in order for users to be able to work with
them. The administrator can check whether shared path loss matrices are unlocked or
not in the Propagation tab of the Transmitters folders Properties dialogue.
5. Click OK.
Important: When you use measurement data to tune path loss matrices, the results are stored
locally. If you are using shared path loss matrices, these results will be automatically
deleted when you make a calculation if the FullResyncPrivShared option is set in the
atoll.ini file. If you are using shared path loss matrices, you should disable this option
before tuning path loss matrices using measurement data. For more information, see the
Administrator Manual.
When using measurement data to tune path loss matrices, you need to have valid path loss matrices (for more information
on path loss matrix validity, see "Managing Path Loss Matrices" on page 187):
1. Define the elliptical area around the measurement point as explained in "Defining the Area to be Tuned" on
page 190.
2. Select the measurement data to be used to tune the path loss matrices:
- CW Measurements: You select the CW measurements from the CW Measurements folder as explained in
"Tuning Path Loss Matrices Using CW Measurements" on page 191. The selected CW measurements will be
used to tune the path loss matrices calculated for the site on which the CW measurements were made.
- Test Mobile Data: You select the test mobile data path from the Test Mobile Data folder as explained in
"Tuning Path Loss Matrices Using Test Mobile Data" on page 192. The selected measurements from test
mobile data path will be used to tune the path loss matrices calculated for the selected transmitter.
Atoll replaces existing path loss matrices with the tuned matrices which remain valid as long as the radio configuration of
the network does not change. Atoll creates an external folder containing the catalogue of all the tuning paths as explained
in "Managing the Tuning Path Loss Matrices Catalogue" on page 193. By activating or deactivating the tuning paths, you
can select the tuning path to be applied to the existing path loss matrices. Therefore, even if the path loss is recalculated,
the path loss is automatically retuned using the active tuning paths.
Figure 5.5: Defining the ellipse for tuning path loss matrices
c. Under Measurement Paths, select the option beside the list of CW measurements.
d. Select the check box corresponding to each transmitter for which you want to tune the path loss matrices.
For some transmitters, more than one CW measurement may exist. In this case, selecting the check box for
the transmitter will select all the CW measurements. If you do not want to use all CW measurements, click the
Expand button ( ) to expand the transmitter list and then select the single CW measurements you want to
use.
e. Click OK. Atoll begins optimising the path loss matrices for all transmitters on which CW measurements are
available. The progress is displayed in the Event Viewer window.
Note: In the case of repeaters, Atoll also tunes the path loss matrix of both the donor transmitter
and the repeater. The contribution of the repeater and donor to the measured value is
calculated based on the ratio of calculated values between the repeater signal and the
donor signal. Each evaluated contribution is then used as input to tune the path loss
matrix of each element. For more information, please refer to the Technical Reference
Guide.
a. Click the Expand button ( ) to expand the Test Mobile Data folder.
b. Right-click the test mobile data path you want to use to tune the path loss matrices. The context menu ap-
pears.
c. Select Tune Path Loss Matrices from the context menu. The Path Loss Tuning dialogue appears (see
Figure 5.7).
a. Right-click the Test Mobile Data folder. The context menu appears.
b. Select Tune Path Loss Matrices from the context menu. The Measurement Path Selection dialogue ap-
pears (see Figure 5.8).
c. Under Measurement Paths, select the option beside the list of test mobile data paths.
d. Select the check box corresponding to the test mobile data you want to use to tune the path loss matrices.
e. Click the For the Transmitters list. The list opens.
f. Select the check box for each transmitter whose path loss matrix you want to tune.
g. Click the Field Corresponding to the Measurements list. The list opens.
h. For each transmitter selected fromthe For the Transmitters list, select the check box for each measured sig-
nal strength that will be used to tune the path loss matrices.
i. Click OK. Atoll begins optimising the path loss matrices for the transmitter on which the CW measurement
was made. The progress is displayed in the Event Viewer window.
Note: In the case of repeaters, Atoll also tunes the path loss matrix of both the donor transmitter
and the repeater. The contribution of the repeater and donor to the measured value is
calculated based on the ratio of calculated values between the repeater signal and the
donor signal. Each evaluated contribution is then used as input to tune the path loss
matrix of each element. For more information, please refer to the Technical Reference
Guide.
Note: When path loss tuning entries are changed (e.g., activated or deleted) Atoll suggests
deleting the corresponding path loss matrices.
1. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
If a transmitter was already selected on the map, a line appears connecting the selected transmitter and the
receiver.
Note: You can open the Point Analysis Tool window without starting a point analysis by
selecting View > Point Analysis Tool.
2. Select the tab of the Point Analysis Tool window corresponding to the type of point prediction you want to make.
For information on the tabs available in the Point Analysis Tool window, see "The Tabs of the Point Analysis Tool
Window" on page 196.
The Profile tab of the Point Analysis Tool window displays the profile between a reference transmitter and the
receiver. As well, Atoll displays the strength of the received signal from the selected transmitter. This is calculated
in real time.
The Reception tab of the Point Analysis Tool window displays the predicted signal level from different transmit-
ters in the form of a bar chart, from the highest predicted signal level on the top to the lowest one on the bottom.
The calculations are based on the path loss matrices. Each bar is displayed in the colour of the transmitter it repre-
sents.
In the map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they
represent. The best server is indicated by a thick black line from the pointer to the server. The best server for the
pointer is the transmitter from which the pointer receives the highest signal level. If you let the pointer rest, the
signal level received from the corresponding transmitter at the pointer location is displayed in the tooltip.
The AS Analysis tab displays information on the pilot quality (EcI0), which is the main parameter used to define
the mobile active set, the connection status, and the active set of the probe mobile.
The best server is indicated by a thick black line from the pointer to the server. The best server for the pointer is
the transmitter from which the pointer receives the highest signal level. If you let the pointer rest, the signal level
received from the corresponding transmitter at the pointer location is displayed in the tooltip.
The Interference tab:
The Interference tab is available in the Point Analysis Tool window for GSM/GPRS/EDGE projects.
The Interference tab displays, in the form of a bar graph, the signal level of the selected transmitter, a black bar
indicating the total interference experienced by the receiver, and bars representing the interference received from
each interferer.
In the map window, arrows from the receiver towards each transmitter are also displayed in the colour of the trans-
mitters they represent. If you let the pointer rest, the interference level received from the corresponding transmitter
at the receiver location will be displayed in the tooltip along with information on the channel being interfered and
the type of interference, i.e., co- or adjacent channel.
The PN Offset Interference tab of the Point Analysis window gives you information on the reception for any point
on the map where there is PN Offset interference.
The Results tab displays the current position and height of the receiver, the clutter class it is situated on, the
received signal level from each transmitter, the distance of the receiver from each transmitter, and, in GSM/GPRS/
EDGE projects, the interference and C/I from each transmitter in decreasing order.
In the map window, arrows from the receiver towards each transmitter are also displayed in the colour of the trans-
mitters they represent. The C/I levels at the receiver from transmitters are displayed as titles for the arrows. The
best server is indicated by a thick black line from the pointer to the server. The best server for the pointer is the
transmitter from which the pointer receives the highest signal level.If you let the pointer rest on an arrow, the inter-
ference level received from the corresponding transmitter at the receiver location will be displayed in the tooltip
along with information on the channel being interfered and the type of interference, i.e., co- or adjacent channel.
1. Right-click the receiver ( ) in the map window. The context menu appears.
2. Select Coordinates from the context menu. The Receiver Position dialogue appears.
3. Enter or paste the X and Y coordinates of the position and click OK. The receiver moves to the specified position.
To place the receiver on a selected site:
1. Right-click the receiver ( ) in the map window. The context menu appears.
2. Select Target Site from the context menu. The Target Site dialogue appears.
3. Select the site on which you want to place the receiver from the Name list and click OK. The receiver moves to
the specified position.
- From Model: Atoll uses the model standard deviation to calculate the results for the Profile, Reception, or
Signal Analysis tabs (WiMAX and LTE).
- CI: Atoll uses the CI standard deviation to calculate the results for the Interference tab (GSM/GPRS/EDGE)
and detailed results in Signal Analysis tab (WiMAX and LTE).
For UMTS, CDMA and TD-SCDMA projects:
- From Model: Atoll uses the model standard deviation to calculate the results for the Profile or Reception tabs.
Atoll also uses the model standard deviation, along with the other defined standard deviations, to calculate
the results for the AS Analysis tab (UMTS and CDMA only). Atoll also uses the model standard deviation,
along with the EcI0 defined standard deviations, to calculate the results for the PN Offset Interference tab
(CDMA) and SC Interference tab (UMTS)
- P-CCPCH Eb/Nt: Atoll uses the P-CCPCH EbNt standard deviation to calculate the results for the Profile or
Reception tabs (TD-SCDMA only).
- EcI0: Atoll uses the EcI0 standard deviation, along with the model defined standard deviations, to calculate
the results for the PN Offset Interference tab (CDMA) and SC Interference tab (UMTS).
- EbNt UL: Atoll uses the EbNt UL standard deviation, along with the other defined standard deviations, to
calculate the results for the AS Analysis tab (UMTS and CDMA only).
- EbNt DL: Atoll uses the EbNt DL standard deviation, along with the other defined standard deviations, to
calculate the results for the AS Analysis tab (UMTS and CDMA only).
Note: The standard deviation chosen from the Shadowing Margin list is for information only; it
is used only to display the value used by Atoll and does not change the standard
deviation used to calculate the displayed results.
- Condition tab: You can define the parameters of the coverage prediction.
- Display tab: You can define how coverage prediction results will be displayed.
5. Click OK to save your settings. The newly created coverage prediction appears in the Predictions folder. If you
wish, you can create another coverage prediction and calculate all coverage predictions at the same time.
For information on calculating coverage predictions, see "Calculating Coverage Predictions" on page 200.
Note: You can not store externally the results of coverage predictions that are calculated by
transmitter instead of by level.
5. On the General tab, click the button beside Folder ( ) and select the storage location of the results:
- Saving in the Atoll document: To store the results in the document, select Embedded.
- Saving externally: To store the results externally, select the external storage location. Atoll creates a folder
for the results in the same folder with the Atoll document and gives it the name of the document, with the
extension "studies."
- Sharing the results of another coverage prediction: To display the results of a coverage prediction that
was calculated in a different document, select Connect to Results to navigate to the XML file describing the
coverage prediction results.
Externally stored coverage prediction results can be imported as coverage prediction templates. For more information on
importing coverage prediction templates, see "Saving Defined Coverage Predictions" on page 202. For a detailed descrip-
tion of the XML file, see Studies.XML in the Administrator Manual.
When you calculate coverage predictions, only unlocked coverage predictions are calculated. Unlocked coverage predic-
tions are displayed in the Predictions folder with the unlocked icon ( ). For information on locking and unlocking cover-
age predictions, see "Locking Coverage Predictions" on page 201.
To calculate created coverage predictions:
Click the Calculate button ( ) in the toolbar. When you click the Calculate button, Atoll first calculates non-
existent and invalid path loss matrices and then, unlocked coverage predictions in the Predictions folder.
The progress of the calculations is displayed in the Event Viewer window.
After calculation, the results are displayed in the map window, if the coverage predictions visibility check box has
been selected.
After calculation, the results are displayed in the map window, if the coverage predictions visibility check box has
been selected.
Click the Force Calculate button ( ) in the toolbar. When you click the Force Calculate button, Atoll first
removes existing path loss matrices, recalculates them and then calculates unlocked coverages predictions.
After calculation, the results are displayed in the map window, if the coverage predictions visibility check box has
been selected.
Click the Stop Calculations button ( ) in the toolbar. Atoll immediately stops all ongoing calculations. The
results of calculations that have already been completed, however, will be saved.
Note: To prevent Atoll from automatically locking coverage predictions after calculating them,
you can set an option in the atoll.ini file. For information on setting options in the atoll.ini
file, see the Administrator Manual.
Unlocked coverage predictions are displayed in the Predictions folder with the unlocked icon ( ).
The icon changes to the locked icon ( ) and the Study Locked item in the context menu now appears checked.
The coverage prediction is now locked and will not be calculated when the Calculate button in the toolbar is
clicked. However, if you select Calculate from the coverage predictions context menu, Atoll will first unlock the
coverage prediction and then calculate it.
You can lock all unlocked coverage predictions using the Predictions folders context menu.
Locked coverage predictions are displayed in the Predictions folder with the locked icon ( ).
The icon changes to the unlocked icon ( ) and the Study Locked item in the context menu is no longer selected.
You can unlock all locked coverage predictions using the Predictions folders context menu.
5. Click Save. Atoll saves the template in the selected XML file.
The next time you create a new coverage prediction, the template will be available at the bottom of the list, under the full
path and file name of the XML file (see Figure 5.11). If you have other XML template files, you can click the Browse button
and select it in the Open dialogue.
In a multi-user environment, the administrator can make templates available for all the users by saving the XML file in the
Atoll installation directory. For more information, see the Administrator Manual.
- Clutter Taken into Account in Diffraction: Select "1 - Yes" to have Atoll take clutter height information into
account when calculating diffraction. Otherwise, select "0 - No". If you choose to take clutter height into
account, Atoll uses the clutter height information in the clutter heights file if available. Otherwise, it uses
average clutter height specified for each clutter class in the clutter classes.
Under LOS Attenuation, you can set the following parameters:
- K1, K2, and K3: Enter the K1, K2, and K3 values that will be used to calculate free space losses.
Under Diffraction, you can set the following parameters:
- Method: Select the method that will be used to calculate tropospheric scattering:
- No attenuation: No attenuation will be calculated.
- ITU-R P617-1: Attenuation will be calculated according to the ITU-R P617-1 recommendations for 50%,
90%, or 99.99% of the time.
- ITU-R P452: Attenuation will be calculated according to the ITU-R P452 recommendations.
- Simplified Method: Attenuation will be estimated using an Atoll-specific equation.
- N0: Enter the value for N0, which is the surface refractivity of the centre of the path.
- Ktropo: Enter the value for the weight factor. Atoll multiplies the loss given by the selected method to calcu-
late the tropospheric scatter loss.
Under Vegetation, you can set the following parameters:
- Method: Select the method that will be used to calculate attenuation due to vegetation:
- No attenuation: No attenuation will be calculated.
- ITU-R P.833-4: Attenuation will be calculated according to ITU-R P.833-4 recommendations.
- A1: Enter the value of the A1 coefficient.
- Alpha: Enter the value of the Alpha coefficient. A1 and Alpha coefficients are used to calculate the maximum
attenuation experienced by a transmitter or a receiver site located within a vegetation area. The maximum
attenuation is taken into consideration to calculate the attenuation due to vegetation.
The attenuation due to vegetation is calculated and displayed in link budget and interference reports for informa-
tion only. It is not taken into account when calculating the total attenuation.
Under Clutter Consideration, you can set the following parameters for each clutter class:
- Clearance per clutter class: Define a clearance (in metres) around each transmitter and each receiver site
for each clutter class. The clearance information is used when clutter is taken into account in diffraction. Both
ground altitude and clutter height are considered along the whole profile except over a specific distance
around the transmitter and the receiver sites (i.e., the clearance), where Atoll bases its calculations only on
the DTM.
- Clutter categories: Select a clutter category for each clutter class. Clutter categories are taken into consid-
eration when studying reflections and must be defined in order to analyse reflections along the profile. Clutter
categories are ITU-standardised clutter classes. The following are the available clutter categories:
- Rural open
- Pastures, grassland
- Low crop fields
- High crop fields
- Park land
- Tree covered
- Irregularly spaced sparse trees
- Orchards
- Deciduous trees (irregularly spaced)
- Deciduous trees (regularly spaced)
- Coniferous trees (irregularly spaced)
- Coniferous trees (regularly spaced)
- Mixed tree forest
- Tropical rain forest
7. Click OK.
For more information on the parameters of the Microwave Propagation Model, see the Technical Reference Guide.
- Clutter Taken into Account in Diffraction: Select "1 - Yes" to have Atoll take clutter height information into
account when calculating diffraction. Otherwise, select "0 - No". If you choose to take clutter height into
account, Atoll uses the clutter height information in the clutter heights file if available. Otherwise, it uses
average clutter height specified for each clutter class in the clutter classes.
Under Tropospheric Scattering, you can set the following parameters:
- N0: Enter the value for N0, which is the surface refractivity of the centre of the path.
- Time percentage: Enter the percentage of time during which the basic propagation loss is not exceeded.
6. Click the Clutter tab (see Figure 5.15).
Under Clutter Consideration, you can set the following parameters for each clutter class:
- Clearance per clutter class: Define a clearance (in metres) around each transmitter and each receiver site
for each clutter class. The clearance information is used when clutter is taken into account in diffraction. Both
ground altitude and clutter height are considered along the whole profile except over a specific distance
around the transmitter and the receiver sites (i.e., the clearance), where Atoll bases its calculations only on
the DTM.
7. Click OK.
For more information on the parameters of the Microwave ITU-R P.452 Model, see the Technical Reference Guide.
Note: Consecutive Severely Errored Seconds can result in periods of unavailability, especially
when there are no backup or standby procedures. Periods of consecutive Severely
Errored Seconds persisting for T seconds, where 2 = T < 10 (sometimes referred to as
"failures"), can have a severe impact on service, leading to the disconnection of switched
services. The frequency of these events can be limited by limiting the SESR.
Background Block Error (BBE): The BBE is an errored block not occurring as part of an SES.
The total observation time (Stotal) is split into two parts, namely, the time for which the connection is deemed to be available
(Savail) and the time when it is unavailable (Sunavail). Error performance should only be evaluated while the connection is
in the available state. The parameters are:
Errored Second Ratio (ESR): The ESR is the ratio of ES to total seconds in available time during a fixed meas-
urement interval.
Severely Errored Second Ratio (SESR): The SESR is the ratio of SES to total seconds in available time during
a fixed measurement interval.
Background Block Error Ratio (BBER): The BBER is the ratio of Background Block Errors (BBE) to total blocks
in available time during a fixed measurement interval. The count of total blocks excludes all blocks during SESs.
In Atoll, you can define microwave link classes and performance objectives based on these error performance parame-
ters. Atoll also includes default lists of microwave link classes and performance objectives based on the ITU G.821 and
G.826 recommendations.
Note: The availability objectives are global objectives. They consist of three partial objectives as
microwave link unavailability can be either due to rain, due to equipment failure, or
random.
Atoll includes by default the availability objectives defined in the ITU G.821 and ITU G.826 recommendations. You can
also define customised availability objectives.
To modify pre-defined ITU G.821 and ITU G.826 availability objectives or to create a new availability objective:
1. Click the Data tab in the Explorer window.
2. Right-click the Microwave Radio Links folder. The context menu appears.
3. Select Performance Targets > Availability from the context menu. The Availability Objectives dialogue
appears.
You can either edit a default ITU G.821 and ITU G.826 availability objective or create a new availability objective.
- To edit a ITU G.821 and ITU G.826 availability objective: Select the appropriate tab (ITU G.821 or ITU
G.826) and modify the properties of the availability objective.
- To create a new customised quality objective: Select the Customised tab and enter the parameters in the
row marked with the New Row icon ( ).
4. Click OK.
- K factor: Select the K factor (the earth curvature factor) to be used in link analyses:
- Median value for each link: If you select this option, a median value for the K factor will be used for each
link in link analyses.
- Same value for all links: If you select this option, the value you enter will be used as the K factor for all
links in link analyses.
- Power control on the useful signal: Select the Power control on the useful signal check box if power control
on the transmitted signal is to be considered.
Under Results, you can define the following parameters:
- The link direction to be analysed: Select the link direction to be analysed: either A >> B, B >> A, or both.
- Calculated Port: Under Calculated Port, select which channel should be displayed the results of a link
analysis:
- All: If you select All, Atoll performs the link analysis and displays the results for all channels.
- Worst channel engineering: If you select Worst channel engineering, Atoll performs the link analysis
for each channel and displays the results for the worst channel in terms of margin (i.e., the channel with
the lowest margin).
- Specific port engineering: If you select Specific port engineering, Atoll performs the link analysis and
displays the result for the channel specified individually for Site A and Site B.
Under BER, you can define what value for BER will be used in link analyses:
- Values defined for each link: If you select Values defined for each link, Atoll performs the link analysis
using the values for BER1 and BER2 defined in the properties of each link.
- Same value for all links: If you select Same value for all links, you can define a value for BER 1 and BER 2
that Atoll will use for all links.
5. Click the Interference tab. On the Interference tab, the parameters you define will be used for interference calcu-
lation.
Under Interferer Filtering, you can define the following parameters:
- Max. Distance: Enter the maximum distance in metres that Atoll will search around each site to find poten-
tially interfering sites.
- Interfered Bandwidth: Enter the percentage of the bandwidth that Atoll should consider when searching for
interferers. If you want Atoll to take into account all potential interferers, set the parameter to 3000%.
- Interference via repeaters: Select how interference caused by repeaters should be taken into consideration.
Under Calculation Parameters, you can define the following parameters:
- Power Control: Define whether automatic transmission power control is to be considered always on, always
off or is to be calculated according to geometric correlation.
- Correlation Area: Enter the surface in km2 of the correlation area.
- Ignore decoupling reduction when cross polarisation is not defined at the receiver: Select this option if
you want Atoll to ignore decoupling reduction when cross polarisation is not defined at the receiver.
Under Result filtering, you can define the following parameters:
- Min. Threshold Degradation: Enter the minimum degradation threshold. Results that do not meet the
threshold will not be displayed.
- Calculation Details: Select the interference to be displayed in the results: none, on the uplink or downlink, or
on both the uplink and downlink.
6. Click the Models tab. On the Models tab, the parameters you define will be used for quality and availability
analysis.
Under Availability, you can define the following parameters:
- Method: Select the method to be used to calculate availability. Six availability analysis methods (Crane and
those based on different implemented ITU recommendations, 530-5, 530-8, 530-10, 530-11 and 530-12) are
available.
- Rain Model: Select the model to be used to calculate rain attentuation. Two attenuation models for rain (ITU
recommendations, 838-1 and 838-3) are available.
Under Quality, you can define the following parameters:
- Method: Select the method to be used to calculate quality: Vigants-Barnett, K.Q factor, ITU-R P.530-5, ITU-R
P.530-8, ITU-R P.530-10, ITU-R P.530-11, or ITU-R P.530-12.
If you select a method based on one of the ITU-R P.530 recommendations, you can set further parameters
under ITU-R P.530.
- Multipath Occurence: If you select recommendation ITU-R P.530-10, ITU-R P.530-11, or ITU-R P.530-12,
you can use either a simplified method or a method taking roughness into account to calculate the geoclimatic
factor (K).
- ITU-R P.530: If you selected a method based on one of the ITU-R P.530 recommendations under Method,
you can set the following parameters:
Multi-Path Propagation: Under Multi-Path Propagation, select the Ignore Signal Enhancements check
box if you want to ignore signal enhancements and XPD reduction in multi-path propagation. Reduction of
XPD is taken into consideration when calculating unavailability due to multi-path and unavailability due to rain
whereas signal enhancements have an impact on unavailability due to multi-path only.
Selective Fadings: Under Selective Fadings you can define reference delay values for the secondary signal
t (tau) for minimum and non minimum phase conditions.
Erroneous Blocks: Under Erroneous Blocks you can define athe network level consideration values for the
Residual Bit Error Rate (RBER), number of errors per burst for Bit Error Rate between 10-3 and BERSES and
for Bit Error Rate between BERSES and RBER.
- K.Q. Method: If you selected K.Q. method based under Method, you can set the following parameters:
Frequency Exponent: Under K.Q. Method, define the exponent of the frequency.
7. Click the Objectives tab. On the Objectives tab, the parameters you define will select objectives.
Under Performance Objectives Selection, you can define how quality and availability objectives are selected.
The objectives can be selected according to the microwave link rate and the type of the objective (from ITU-T
G.821 or ITU-T G.826 recommendations or a customised objective). Clicking the Browse button ( ) beside
the Quality or Availability field opens a dialogue where you can define a priority for each selection criterion.
Under Availability Objectives Apportionment, you can define the ratio between the different objectives consid-
ered in the global availability objective. Microwave link unavailability can be due either to rain (with its impact on
propagation), to equipment failure, or it can be random. Therefore, the global availability objective consists of three
partial objectives for which you can define a weight. These weights are taken into consideration when calculating
the performance objectives to be considered when analysing the microwave link unavailability due to rain and the
unavailability due to equipment failures
8. Click OK.
Note: You can also access a links Properties dialogue by right-clicking the transmitter on the
map and selecting Properties from the context menu.
The microwave link Properties dialogue has several tabs: General, Radio, Connections, Geoclimatic, Reliability,
Propagation, and Display. The link settings that affect calculations are on the Geoclimatic, Reliability, and Propa-
gation tabs and are described here. For an explanation of the options available on the General, Radio, Connec-
tions, and Display tabs, see "Chapter 15: Microwave Link Project Management".
7. On the Geoclimatic tab, you can define climate-related settings affecting the microwave link:
- Current Methods: Under Current Methods, you can see the calculation methods used to analyse the micro-
wave link quality and availability. The methods displayed are those set on the Models tab of the Microwave
Radio Links Properties dialogue.
- Atmospheric and Climatic Conditions: Under Atmospheric and Climatic Conditions, you can define the
conditions under which the microwave operates:
- Climatic Zone: Select the climatic zone that best describes the climate in which the microwave link oper-
ates. For dry areas, you can select from Polar (Dry), Polar (Moderate), Cold (Dry), Temperate Continental
(Dry), and Subtropical Arid (Dry). For continental areas, you can select from Cold (Moderate), Temperate
Continental (Moderate). For humid areas, you can select from Temperate Continental (Wet) correspond
to continental areas and Temperate Maritime, Subtropical Wet, Tropical Moderate, and Tropical.
The climate zone is taken into consideration by all calculation methods.
- Temperature: Set the average temperature of the zone in which the microwave link operates. Clicking the
button ( ) beside the Temperature text box opens a dialogue where you can select the temperature
based on Rec. ITU-R P.1510-0, ITU-R P.835-3 (and select a season), or the temperature set in the geocli-
matic file.
- Rec. ITU-R P.530: The parameters found under Rec. ITU-R P.530 are those recommended by ITU-R
P.530 to calculate the availability of the microwave link:
Water Vapour Density: Set the water vapour density in grams per cubic metre. Clicking the button ( )
beside the Water Vapour Density text box opens a dialogue where you can select the water vapour den-
sity based on Rec. ITU-R P.836-3 (and select the percentage of the average year where the defined water
vapour density is exceeded), or based on Rec. ITU-R P.835-3 (and select a season), or the water vapour
density set in the geoclimatic file. The dialogue also displays the water vapour pressure in hectopascals
(hPa) calculated using your data and based on Rec. ITU-R P.836-3.
Rainfall exceeded 0.01% of the average year: Set the rainfall exceeded 0.01% of the average year (or,
in other words, the rainfall observed 99.99% of the average year). Clicking the button ( ) beside the
Rainfall exceeded 0.01% of the average year text box opens a dialogue where you can select the rainfall
exceeded 0.01% of the average year based on Rec. ITU-R P.837-4 or the rainfall exceeded 0.01% of the
average year set in the geoclimatic file.
Atmospheric Pressure: Set the atmospheric pressure in grams per cubic metre. Clicking the button
( ) beside the Atmospheric Pressure text box opens a dialogue where you can select the atmospher-
ic pressure based on Rec. ITU-R P.835-3 (and select a season), or the atmospheric pressure set in the
geoclimatic file.
Relative Humidity: The Relative Humidity displayed is calculated using the defined water vapour den-
sity.
Rec. ITU-R P.530-12: Under ITU-R P.530-12, you can enter the Rain Height (0C Isotherm) in metres.
The rain height is the height of the top of the rain column above mean sea level from the 0C isotherm.
Clicking the button ( ) beside the Rain Height text box opens a dialogue where you can select the rain
height based on Rec. ITU-R P.839-3 (and select a season), or the rain height set in the geoclimatic file.
- Refractivity: Under Refractivity, you can define the Refractivity gradient near the earths surface in
N-units per km. Clicking the button ( ) beside the Refractivity gradient near the earths surface text box
opens a dialogue where you can select the refractivity gradient based on Rec. ITU-R P.453-9, using a user-
defined reference altitude, or the refractivity gradient for less than 65 m., as well as the percentage of the year
that N is not exceeded, or the refractivity gradient set in the geoclimatic file.
Under Refractivity, the k factor median value, calculated using the set parameters, is displayed.
- Geoclimatic Factor: The parameters under Geoclimatic Factor are used to calculate the quality of the
microwave link and are broken down by calculation method. Under Geoclimatic Factor, you can set the fol-
lowing parameters:
- ITU-R P.530-5, -8 and Vigants-Barnett: Under ITU-R P.530-5, -8 and Vigants-Barnett, you can select
the Terrain Type: "Plain Zone" for terrestrial microwave links where the height of the lowest antenna in
the link is lower than 700 m; "Mountain Zone" for terrestrial microwave links where the height of the lowest
antenna in the link is higher than 700 m; "Lake Zone" for microwave links over an expanse of water and
"Link over the water" for microwave links over an extended expanse of water.
This information is taken into account when using ITU-R P.530-5, ITU-R P.530-8 and Vigants-Barnett cal-
culation methods.
- ITU-R P.530-5, -8: Under ITU-R P.530-5, -8, you can define the PL factor. PL is the percent of time the
relative refractivity gradient is less than -100 NKm. The PL factor can be found on the ITU-R maps.
This parameter is taken into account when using ITU-R P.530-5 and ITU-R P.530-8 calculation methods.
- K.Q. Method: Under K.Q. Method, you can define K.Q. for the K.Q method. K models geo-climatic and
terrain effects on climate while Q is the factor for variables other than those dependent on distance and
frequency.
- ITU-R P.530: Under ITU-R P.530, you can define the K factor. K models geo-climatic and terrain effects
on climate. Clicking the button ( ) beside the K text box opens a dialogue where you can select the K
factor based on Rec. ITU-R P. 530-5 or Rec. ITU-R P. 530-8 (and select a terrain type and enter a value
for C0 and for the percentage of time the refractivity gradient (< 100 m.) is less than -100 N-unitskm for
the worst average month) or based on Rec. ITU-R P. 530-10 and above (and select the simplified method
where you also define the refractivity gradient (< 65 m.) not exceeded during 1% of the average year or
select the method with terrain roughness taken into account where you define the refractivity gradient and
the terrain roughness).
- Vigants-Barnett: Factor C: Under Vigants-Barnett: Factor C, you can define C, the propagation condi-
tion factor for Vigants-Barnett method. You can either select Real and enter a value, or select Terrain
Type and the C factor will be calculated from the terrain.
8. Click the Reliability tab (see Figure 5.17).
Clicking the Browse button ( ) opens the Properties dialogue of the selected link class.
Clicking the Objectives button opens a dialogue where you can view and modify the performance objectives
of the selected link class.
- Bit Error Rate: Under Bit Error Rate, you can set the values for BER 1 and BER 2. Atoll displays the
resulting sensitivity for each BER.
If the value for BER that you enter is not defined in the properties of the equipment, Atoll will interpolate to
determine the corresponding sensitivity.
- Availability: Under Availability, you can set the MTTR (mean time to repair). The MTTR is taken into account
when calculating unavailability due to failures if the microwave link is not equipped with a hot standby channel
system.
10. Click the Propagation tab (see Figure 5.18).
- Geoclimatic tab:
- Environment Type
- R001 (mm/h)
- Geoclimatic Factor (K)
- PL (%)
- Water Vapour (g/m3)
- Temperature (C)
- Factor K.Q
- Rain Height (m)
- Atmospheric Pressure (hPa)
- Refractivity
- Factor C
- Climatic Zone
- Reliability tab:
- Class (EPO)
- Hot Standby
- BER
- 2nd BER
- MTTR (h)
- Propagation tab:
- Propagation Model
- Interference Model
6. For each cell with a calculation parameter that you have already modified, copy the values into all cells above the
modified cell:
b. Drag upwards to select the cells into which you want to copy the data.
The contents of the modified cell are copied into all cells selected.
7. Repeat the procedure to copy the modified values into the remaining cells above the modified microwave link.
8. For each cell with a calculation parameter that you have already modified, copy the values into the cells below the
modified cell:
b. Drag downwards to select the cells into which you want to copy the
data.
The contents of the modified cell are copied into all cells selected.
9. Repeat the procedure to copy the modified values into the remaining cells below the modified microwave link.
To select the microwave links to which you want to copy the calculation parameters by grouping:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the Microwave Radio Links folder.
3. Right-click the Links folder. The context menu appears.
4. From the Group By submenu, select the property by which you want to group the microwave links. Ensure that
you chose a property that all the microwave links you want to modify and the link with the modified calculation
parameters have in common.
The microwave links in the folder are grouped in separate folders by that property.
Note: If the range of properties available in the Group By submenu has been configured as
explained in "Configuring the Group By Submenu" on page 65, you can select additional
properties by selecting More Fields from the Group By submenu. For information on
using the dialogue that appears, see "Configuring the Group By Submenu" on page 65.
5. Right-click the folder with the grouped microwave links. The context menu appears.
6. Select Open Table from the context menu. The Links Table appears.
7. Copy the calculation parameters from the modified microwave link to the other microwave links in the group as
explained in "Defining Calculation Parameters for All Microwave Links" on page 215.
Once you have finished copying the calculation parameters, you can ungroup the links by right-clicking the Links folder
and selecting Group By > None from the context menu.
To sort the microwave links to which you want to copy the calculation parameters:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the Microwave Radio Links folder.
3. Right-click the Links folder. The context menu appears.
4. Select Open Table from the context menu. The Links Table appears.
5. Right-click the table column with the parameter you want to sort on. The context menu appears.
6. Select either Sort Ascending or Sort Descending from the context menu.
7. Locate the row in the Links Table with the microwave link whose calculation parameters you just updated.
In the Links Table, the column names corresponding to the calculation parameters on the tabs of the microwave
links Properties dialogue are:
- Geoclimatic tab:
- Environment Type
- R001 (mm/h)
- Geoclimatic Factor (K)
- PL (%)
- Water Vapour (g/m3)
- Temperature (C)
- Factor K.Q
- Rain Height (m)
- Atmospheric Pressure (hPa)
- Refractivity
- Factor C
- Climatic Zone
- Reliability tab:
- Class (EPO)
- Hot Standby
- BER
- 2nd BER
- MTTR (h)
- Propagation tab:
- Propagation Model
- Interference Model
8. For each cell with a calculation parameter that you have already modified, copy the values into all cells in the group
above the modified cell:
b. Drag upwards to select the cells into which you want to copy the data.
Important: Ensure that you only select the cells of the microwave links you want to modify.
The contents of the modified cell are copied into all cells selected.
9. Repeat the procedure to copy the modified values into the remaining cells in the group above the modified micro-
wave link.
10. For each cell with a calculation parameter that you have already modified, copy the values into the cells in the
group below the modified cell:
b. Drag downwards to select the cells into which you want to copy the data.
Important: Ensure that you only select the cells of the microwave links you want to modify.
c. Drag downwards to select the cells into which you want to copy the
data.
The contents of the modified cell are copied into all cells selected.
To filter the microwave links to which you want to copy the calculation parameters:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the Microwave Radio Links folder.
3. Right-click the Links folder. The context menu appears.
4. Select Open Table from the context menu. The Links Table appears.
You can now filter on a value in the table. You can either use a value that all microwave links to which you want
to copy calculation parameters have in common with the microwave link you previously modified, or you can use
a value these microwave links do not have.
5. Select the value to filter on. To select more than one value, press CTRL as you click the other values.
6. Right-click the cell and select one of the following from the context menu:
- Filter by Selection: All microwave links with the selected value or values are displayed. You can now modify
these microwave links as you would normally do with the entire Links table (see Figure 5.19 on page 220).
- Filter Excluding Selection: All microwave links without the selected value or values are displayed. You can
now modify these records or make calculations on them as you would normally do with the entire Links table
(see Figure 5.20 on page 221).
Figure 5.20: Filtering excluding selection (Sub-Band A>> B: 18 GHz, 220 MHz)
Note: You can use advanced data filtering to combine several criteria in different fields to create
complex filters. For more information on advanced filtering, see "Advanced Data Filtering"
on page 71.
7. Copy the calculation parameters from the modified microwave link to the other microwave links in the group as
explained in "Defining Calculation Parameters for All Microwave Links" on page 215.
Atoll
RF Planning and Optimisation Software
Chapter 6: Co-planning Features
6 Co-planning Features
Atoll is a multi-technology radio network planning tool. You can work on several technologies at the same time, and
several network scenarios can be designed for any given area; a country, a region, a city, etc. For example, you can design
a GSM and a UMTS network for the same area in Atoll, and then work with Atolls co-planning features to study the mutual
impacts of the two networks. Atoll allows you to co-plan any two technologies, be it GSM-UMTS, GSM-CDMA2000, GSM-
WiMAX, UMTS-LTE, GSM-LTE, etc.
This chapter contains detailed procedures and instructions for the RF planner on co-planning using Atoll. This chapter
takes the most common co-planning scenario as reference, i.e., GSM-UMTS co-planning. However, the procedures
described in this chapter are valid for any possible co-planning scenario.
Important: Before starting a co-planning project in Atoll, the Atoll administrator must perform the
pre-requisite tasks that are relevant for your project as described in the Setting Up Atoll
for Co-planning chapter in the Administrator Manual.
The sectors of both networks can share the same sites database. You can display base stations (sites and transmitters),
geographic data, and coverage predictions, etc., of one network in the other networks Atoll document. You can also study
inter-technology handovers by performing inter-technology neighbour allocations, manually or automatically. Inter-tech-
nology neighbours are allocated on criteria such as the distance between sectors or coverage overlaps. In addition, you
can model the intereferences of a network over another one.
Atoll supports MS Access, MS SQL Server, Oracle, and Sybase databases. Therefore, you can work with Atoll docu-
ments connected to databases.
This chapter explains the following topics:
"Starting a Co-planning Project" on page 225.
"GSM-UMTS Co-planning Process" on page 226.
Note: Before starting a co-planning project, make sure that your main and linked documents
have the same geographic coordinate systems.
If you close the linked document, Atoll displays a warning icon ( ) in the main documents Explorer window, and the
linked folders and items are no longer accessible from the main document. You can load the linked document in Atoll
again by right-clicking the linked folder or item in the Explorer window of the main document, and selecting Load Target.
The administrator can create and set a configuration file for the display parameters of GSM and UMTS transmitters in order
to allow you to distinguish them on the map and to be able to select them on the map using the mouse. If such a configu-
ration file has not been set up, you can choose different symbols, sizes and colours for the GSM and the UMTS transmit-
ters. For more information on folder configurations, see "Folder Configurations" on page 78. You can also set the contents
of the tool tips to easily interpret the objects and data displayed on the map. For more information on tool tips, see "Defining
the Object Type Tip Text" on page 36.
In order to easily view differences between networks, you can also change the order of the folders or items in the Explorer
window.
Figure 6.1 shows UMTS transmitters with labels and GSM transmitters data summed up in tool tips.
Note: This feature is useful for deploying UMTS on existing GSM sites, especially when the new
UMTS sector is supposed to share the main antenna with the GSM sector.
Figure 6.2: New UMTS Transmitter Before and After Applying the Configuration
Note: The azimuths and mechanical tilts of secondary antennas or remote antennas are not
included in the copy and have to be set up manually.
Important: Before running the macro, make sure that the main and the linked documents are both open
in Atoll, and, that the user-defined field SharedMast has been added to the Transmitters table of both
the documents. Ask the Atoll administrator to add this field to the databases if you are working with
documents connected to databases. Verify as well that the SharedMast field in the main and the linked
documents contains the same information for the transmitters that share common physical parameters.
The field should be left blank for transmitters that do not share common physical parameters.
Note: If the Propagate Changes macro icon is not available in Atoll, ask the Atoll administrator
to check whether this macro has been installed in silent mode or has not been installed. If
the macro has been installed in silent mode, the changes you make to the common
shared parameters are updated and saved when you save your Atoll documents.
Click the Calculate button ( ) in the toolbar. When you click the Calculate button, Atollfirst calculates non-
existent and invalid path loss matrices and then, unlocked coverage predictions in the main and linked Predic-
tions folders.
The progress of the calculations is displayed in the Event Viewer window.
If you want, you can make Atoll recalculate all path loss matrices, including valid ones, before calculating unlocked cover-
age predictions defined in the main and linked Predictions folders.
To force Atoll to recalculate all path loss matrices before calculating coverage predictions:
Click the Force Calculate button ( ) in the toolbar. When you click the Force Calculate button, Atoll first
removes existing path loss matrices, recalculates them and then calculates unlocked coverages predictions
defined in the main and linked Predictions folders.
Note: To prevent Atoll from calculating coverage predictions defined in the main and linked
Predictions folders, you can set an option in the atoll.ini file. For information on setting
options in the atoll.ini file, see the Administrator Manual.
Note: The common physical parameters include Dx and Dy, antenna height, azimuth, and
mechanical tilt.
Following is the recommended process for comparing GSM and UMTS coverage predictions.
1. Create and calculate a coverage prediction by transmitter (Best Server) and a coverage prediction by signal level
in the GSM document.
2. Create and calculate a coverage by transmitter (Pilot Best server) and a coverage prediction by Ec/Io level in the
UMTS document.
3. Carefully choose display settings for the coverage predictions and tool tip contents in order to easily interpret the
predictions displayed in the Map window. This can be very helpful in quickly assessing information graphically and
using the mouse.
4. Make the two GSM coverage predictions accessible in the UMTS document.
Figure 6.4: UMTS Coverage Prediction (Pilot Best Server) Pink Contours With no Interior
Figure 6.5: GSM Coverage Prediction (Best Server) High Transparency With Full Interior Coloured According to BCCH
With BCCH/BSIC Information Available in Tooltips
5. Select Compare With > [linked coverage prediction] from the context menu, where [linked coverage predic-
tion] is the GSM coverage prediction you want to compare with the UMTS coverage prediction. The Comparison
Properties dialogue opens.
6. Select the display parameters of the comparison and add a comment if you wish.
7. Click OK.
The two coverage predictions are compared and a comparison coverage prediction is added to the main documents
Predictions folder.
2. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
3. Select Display Options from the context menu. The Visual Management dialogue appears.
4. Under Inter-technology Neighbours, select the Display Links check box.
5. Under Advanced, select which exceptional pair links to display:
- Outwards Non-Symmetric: Shows an exceptional pair link for each UMTS cell that has an exceptional pair
with a GSM transmitter. These links are represented with straight dashed lines of the same colour as the
UMTS transmitters.
- Inwards Non-Symmetric: Shows an exceptional pair link for each GSM transmitter that has an exceptional
pair with a UMTS cell. These links are represented with straight dashed lines of the same colour as the GSM
transmitters.
- Symmetric: Shows an exceptional pair link for each UMTS cell that has an exceptional pair with a GSM trans-
mitter only if the GSM transmitter also has this UMTS cell in its exceptional pair list. These links are repre-
sented with straight black lines.
6. Click the context menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The context
menu appears.
7. Select Forced Neighbours or Forbidden Neighbours from the menu. The exceptional pair of a cell will be dis-
played when you select a transmitter.
8. Click the Visual Management button ( ) in the Radio toolbar. The exceptional pair display on the map is acti-
vated. The exceptional pair display remains activated until you click the Visual Management button again.
9. Click a transmitter on the map to show its exceptional pair links. When there is more than one cell on the trans-
mitter, clicking the transmitter in the map window opens a context menu allowing you to select the cell you want
(see "Selecting One of Several Transmitters or Microwave Links" on page 30).
You can also define exceptional pairs of UMTS cells for GSM transmitters. However, in GSM, neighbours and exceptional
pairs are allocated by transmitter (i.e., by sector) whereas in UMTS, neighbours and exceptional pairs are allocated by cell.
The exceptional pair links can be displayed even if you do not have neighbours allocated. If you select the Display Links
check box under Intra-technology Neighbours, Atoll displays both inter-technology and intra-technology exceptional
pairs on the map.
6.2.4.2.1 Adding and Removing Inter-Technology Exceptional Pairs Using the Mouse
You can set inter-technology exceptional pairs using the mouse. Atoll adds or removes forced or forbidden exceptional
pairs depending on the display option set, i.e., Forced Neighbours or Forbidden Neighbours.
Before you can add or remove exceptional pairs using the mouse, you must activate the display of exceptional pairs on
the map as explained in "Displaying Inter-Technology Exceptional Pairs on the Map" on page 231.
To add a symmetric forced or forbidden exceptional pair:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter with which you want to set an exceptional pair. Atoll adds both transmitters
to the inter-technology exceptional pairs list of the other transmitter.
To remove a symmetric forced or forbidden exceptional pair:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter that you want to remove from the list of exceptional pairs. Atoll removes
both transmitter from the inter-technology exceptional pairs list of the other transmitter.
To add an outwards forced or forbidden exceptional pair:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter with which you want to set an exceptional pair. Atoll adds the reference
transmitter to the inter-technology exceptional pairs list of the other transmitter.
Note: When there is more than one cell on the transmitter, clicking the transmitter in the map
window opens a context menu allowing you to select the cell you want (see "Selecting
One of Several Transmitters or Microwave Links" on page 30).
a. In the row marked with the New Row icon ( ), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column.
c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column and sets the Type to "manual".
Note: You can add or delete either some forced neighbours or some forbidden neighbours using
the Exceptional Pairs of Inter-Technology Neighbours table. You can open this table,
select the exceptional pairs to be considered, right-click the table and select Force
Exceptional Pairs in the context menu.
- Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by the reference cell.
- Min. Ec/Io: Enter the minimum Ec/Io which must be provided by reference cell in the area of coverage
overlapping. The reference cell must also be the best server in terms of pilot quality. You can also define
a Max Ec/Io.
- Ec/Io Margin: Enter the Ec/Io margin to define the area of coverage overlapping between UMTS cells.
- Power Contributing to Io: You can let Atoll base the interference ratio on the Total Power Used (as
defined in the cell properties) or on a percentage of the maximum power (% Max Power).
- Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and
enter a Cell Edge Coverage Probability.
In the GSM Coverage Conditions dialogue, you can change the following parameters:
- Min. BCCH Signal Level: Enter the minimum BCCH signal level which must be provided by the GSM
transmitter.
- Margin: Enter the margin to define the area of coverage overlapping between GSM transmitters.
- Shadowing Taken into Account: If desired, select the Shadowing taken into account check box and
enter a Cell Edge Coverage Probability.
- Resolution: You can enter the resolution used to calculate the coverage areas of transmitters (GSM) and cells
(UMTS) for the automatic neighbour allocation.
- % Min. Covered Area: Enter the minimum percentage of the cells coverage area that the GSM transmitters
coverage area should also cover to be considered as a neighbour.
- Calculation Options:
- Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers;
Atoll will allocate neighbours to cells using the selected carriers.
- Force co-site as neighbours: Selecting this check box will include the co-site GSM transmitters in the
neighbour list of the UMTS cell.
- Force exceptional pairs: Selecting this check box will apply the inter-technology exceptional pair criteria
on the neighbours list of the UMTS cell.
- Reset neighbours: Selecting this option will delete all the existing neighbours in the neighbours list and
perform a clean neighbour allocation. If the box is left unchecked, Atoll keeps the existing neighbours in
the list.
6. Click the Run button to start calculations
7. Once the calculations finish, Atoll displays the list of neighbours in the Results section. The results include the
names of the neighbours, the number of neighbours of each cell, and the reason they are included in the neigh-
bours list. The reasons include:
Force co-site as
Co-site The neighbour is located at the UMTS cells site.
neighbours is selected
Use Coverage
The neighbour is within the maximum distance from the reference
Distance Overlapping is not
transmitter.
selected
8. Select the check box in the Commit column of the Results section to choose the inter-technology neighbours you
want to assign to cells.
9. Click the Commit button. The allocated neighbours are saved in the Intra-technology Neighbours tab of each cell.
10. Click Close.
2. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
3. Select Display Options from the context menu. The Visual Management dialogue appears.
4. Under Inter-technology Neighbours, select the Display Links check box.
5. Under Advanced, select the neighbour links to display:
- Outwards Non-Symmetric: Shows a neighbour link for each UMTS cell that has a GSM neighbour trans-
mitter. These links are represented with straight dashed lines of the same colour as the UMTS transmitters.
- Inwards Non-Symmetric: Shows a neighbour link for each GSM transmitter that has a UMTS neighbour cell.
These links are represented with straight dashed lines of the same colour as the GSM transmitters.
- Symmetric: Shows a neighbour link for each UMTS cell that has a GSM neighbour transmitter only if the GSM
transmitter also has this UMTS cell as neighbour. These links are represented with straight black lines.
6. Click the context menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The context
menu appears.
8. Click the Visual Management button ( ) in the Radio toolbar. The neighbour display on the map is activated.
The Neighbour display remains active until you lick the Visual Management button again.
9. Click a transmitter on the map to show its neighbour links. When there is more than one cell on the transmitter,
clicking the transmitter in the map window opens a context menu allowing you to select the cell you want (see
"Selecting One of Several Transmitters or Microwave Links" on page 30)
You can also define UMTS neighbours for GSM transmitters. However, in GSM, neighbours are allocated by transmitter
(i.e., by sector) whereas in UMTS, neighbours are allocated by cell.
If you select the Display Links check box under Intra-technology Neighbours, Atoll displays both inter-technology and
intra-technology neighbours on the map. The figure below shows the intra- and inter-technology neighbours of the trans-
mitter Site22_2.
Note: When there is more than one cell on the transmitter, clicking the transmitter in the map
window opens a context menu allowing you to select the cell you want (see "Selecting
One of Several Transmitters or Microwave Links" on page 30).
taking it into account in interference modelling, the radio planner can limit the capacity reduction by ooptimising the
settingss of the network.
4 types of inter-network interferences can be modelled in Atoll:
Interferences from external transmitters on the mobiles of the current project: this interferences can be caused the
effect of adjacent channels, wideband noise (thermal noise, phase noise, modulation products and spurious trans-
missions) and intermodulation. In Atoll, these interferences can be modelled on mobiles in GSM/GPRS/EGPRS,
CDMA and WiMAX technologies.
Interferences from external transmitters on the transmitters of the current project: In the case of a limited separa-
tion between the external downlink frequency bands and the uplink frequency band or in the case of an interfering
TDD network, some transmitter to transmitter interferences may occur. In Atoll, because uplink transmission is
not modelled in GSM/GPRS/EGPRS projects, these interferences can be modelled on transmitters in CDMA and
WiMAX technologies.
Interferences from external mobiles on the transmitters of the current project: In the case of a limited separation
between the external uplink frequency bands and the uplink frequency band or in the case of an interfering TDD
network, some mobile to transmitter interferences may occur. In Atoll, because uplink transmission is not mod-
elled in GSM/GPRS/EGPRS projects, these interferences can be modelled on transmitters in CDMA and WiMAX
technologies. Assuming the position of external mobiles is not known, the source of uplink interferences is not dis-
tinguished if they are due to external transmitters of mobiles. Modelling is treated in the same way.
Interferences from external mobiles on the mobiles of the current project: In the case of a limited separation
between the external uplink frequency bands and the downlink frequency band, some mobile to mobile interfer-
ences may occur. In Atoll, these interferences can be modelled on mobiles in GSM/GPRS/EGPRS, CDMA and
WiMAX technologies.
For more information concerning the interference calculation methods, please refer to the technical reference guide.
For every pair that is not defined, Atoll assumes that there is no inter-technology interferences.
e. Press ENTER to create the carrier pair and to create a new row in the table.
When the projects are linked and when the technology types and channel bandwidth are consistent with the ones defined
in the inter-technology IRFs, Atoll add these inter-technology interferences to the DL interferences at the receiver.
The effect of these DL interferences (used commonly with interferences from external mobiles on the mobiles) can be
seen:
In the interference studies in GSM/GPRS/EGPRS projects both in coverage predictions and in the point analysis
(Interference and Results tab) as explained in "GSM/GPRS/EGPRS Interfered networks" on page 239
in a new coverage prediction called "Inter-technology DL interferences" in UMTS and CDMA projects as explained
in "Downlink studies" on page 239
In any prediction for which DL interferences may have an effect.
In any prediction study where DL interferences are evaluated, Atoll automatically integrate in their calculation external DL
interferences. In addition, a specific study "Inter-technology DL interferences" is available.
Interferences come from the powers of transmitting base stations (See "Interferences from external transmitters on the
mobiles" on page 237) and powers of interfering mobiles defined by inter-technology donwlink noises at the cell level in
UMTS/HSPA, CDMA and WiMAX technologies (See "UMTS/HSPA, CDMA and WiMAX networks" on page 238) or at the
TRX level in GSM/GPRS/EDGE technology (See "GSM/GPRS/EDGE networks" on page 238)
To make an Inter-technology DL interferences coverage prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Inter-technology DL interferences and click OK. The coverage prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab.
Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on
load conditions taken from a simulation.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal and a Service. You must also select which Carrier(s) is to be considered. If you want
the prediction to consider shadowing, you can select the Shadowing taken into account check box and enter a
percentage in the Cell Edge Coverage Probability text box.
7. You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
Click the Display tab.
For a downlink total noise or downlink noise rise prediction, the Display Type "Value Intervals" is selected by
default. The Field you choose determines which information the downlink total noise or downlink noise rise predic-
tion makes available.
- Downlink total noise prediction: When making a downlink total noise prediction, select one of the following
in the Field list:
- Min. Noise Level
- Average Noise Level
- Max Noise Level
- Downlink noise rise prediction: When making a downlink noise rise prediction, select one of the following
in the Field list:
- Min. Noise Rise
- Average Noise Rise
- Max Noise Rise
For information on defining display properties, see "Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the downlink total noise or downlink noise rise
prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Uplink studies
In any prediction study where UL interferences are evaluated, Atoll automatically integrate in their calculation external UL
interferences.
Interferences come from the powers of transmitting base stations (See "Interferences from external transmitters on the
mobiles" on page 237) and powers of interfering mobiles defined by inter-technology uplink noises at the cell level in
UMTS/HSPA, CDMA and WiMAX technologies (See "Interferences from external mobiles on the mobiles" on page 238
Atoll
RF Planning and Optimisation Software
Chapter 7: GSM/GPRS/EDGE Networks
7 GSM/GPRS/EDGE Networks
Atoll enables you to create and modify all aspects of a GSM/GPRS/EDGE network. Once you have created the network,
Atoll offers many tools to let you verify the network. Based on the results of your tests, you can modify any of the param-
eters defining the network.
The process of planning and creating a GSM/GPRS/EDGE network is outlined in "Designing a GSM/GPRS/EDGE
Network" on page 245. Creating the network of base stations is explained in "Planning and Optimising GSM/GPRS/EDGE
Base Stations" on page 246. Allocating neighbours is also explained. In this section, you will also find information on how
you can display information on base stations on the map and how you can use the tools in Atoll study base stations.
In "Studying Network Capacity" on page 305, using traffic maps to study network capacity is explained. Creating traffic
captures using the traffic map information and dimensioning the network using these results is also explained.
Using test mobile data paths to verify the network is explained in "Optimising and Verifying Network Capacity" on
page 373. How to filter imported test mobile data paths, and how to use the data in coverage predictions is also explained.
1
Open an Existing Project
or Create a New One
2
Network Configuration
- Add Network Elements
- Change Parameters
3
Basic Predictions
(Best Server, Signal Level)
4
Neighbour Allocation
5a 5b 5c
Traffic Maps Dimensioning User-defined values
Required number 5
of TRXs
6a 6b
Automatic Frequency Allocation (AFP) Manual Frequency Allocation
List of 6
Frequencies
7 7a
GSM/GPRS/EDGE Predictions Prediction Study Reports
8
Frequency Plan Analysis
The steps involved in planning a GSM/GPRS/EDGE network are described below. The numbers refer to Figure 7.1.
- "Studying Signal Level Coverage" on page 269 and "Signal Level Coverage Predictions" on page 278
- You can import or create traffic maps ( 5a ) and use them as a basis for dimensioning 5b ) (see "Studying
Network Capacity" on page 305).
- You can define them manually either on the TRXs tab of each transmitters Properties dialogue or in the Sub-
cells table (see "Modifying a Subcell" on page 256) ( 5c ).
6. Once you have the required number of TRXs, manually or automatically create a frequency plan ( 6 ).
- "Allocating Frequencies and BSICs Manually" on page 320
- "Allocating Frequencies and BSICs Using an AFP Module" on page 323.
- Name: Atoll automatically enters a default name for each new site. You can modify the default name here. If
you want to change the default name that Atoll gives to new sites, see the Administrator Manual.
- Position: By default, Atoll places the new site at the centre of the map window. You can modify the location
of the site here.
Tip: While this method allows you to place a site with precision, you can also place sites using
the mouse and then position them precisely with this dialogue afterwards. For information
on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 31.
- Altitude: The altitude, as defined by the DTM for the location specified under Position, is given here. You can
specify the actual altitude under Real, if you wish. If an altitude is specified here, Atoll will use this value for
calculations.
- Comments: You can enter comments in this field if you wish.
For information on the site Properties dialogue, see "Site Description" on page 247. You can click the New
button to create a new site on which the transmitter will be located.
- Under HCS Layer
- You can select the HCS Layer (Hierarchical Cell Structure layer) for the transmitter.
- Once you have selected the HCS layer, you can click the Browse button ( ) to open the properties of
the HCS layer.
- You can enter a specific HCS Layer Threshold for this transmitter. The threshold defined in the HCS Layer
properties is considered only if no value is entered in this field.
For information on the HCS layer Properties dialogue, see "Setting HCS Layers" on page 385.
- Position relative to the site: You can modify the Position relative to the site, if you wish.
The Transmitter tab (see Figure 7.3):
- Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are dis-
played in red in the Transmitters folder of the Data tab.
Note: Only active transmitters are taken into consideration during calculations.
- Transmitter Type: If you want Atoll to consider the transmitter as a potential server as well as an interferer,
set the transmitter type to Intra-Network (Server and Interferer). If you want Atoll to consider the transmitter
only as an interferer, set the type to Extra-Network (Interferer Only). No coverage for an Interferer Only
transmitter will be calculated for coverage predictions.
This feature enables you to model the co-existence of different networks in the same geographic area. For
more information on how to study interference between co-existing networks, see "Modelling the Co-existence
of Networks" on page 408.
- Transmission: Under Transmission, you can select to enter either Power and Total Losses or EIRP (Effec-
tive Isotropically Radiated Power). If you select EIRP, you can enter the value yourself, without defining power
and losses for the transmitter.
If you select Power and Total Losses, Atoll calculates losses and noise according to the characteristics of
the equipment assigned to the transmitter. Equipment can be assigned using the Equipment Specifications
dialogue which appears when you click the Equipment button. Atoll will calculate the EIRP with the following
formula:
- On the Equipment Specifications dialogue (see Figure 7.4), the equipment you select and the gains and
losses you define are used to initialise total transmitter DL losses. UL losses are not modelled in GSM/GPRS/
EDGE projects.
- TMA: You can select a tower-mounted amplifier (TMA) from the list. You can click the Browse button
( ) to access the properties of the TMA. For information on creating a TMA, see "Defining TMA Equip-
ment" on page 147.
- Feeder: You can select a feeder cable from the list. You can click the Browse button ( ) to access the
properties of the feeder. For information on creating a feeder cable, see "Defining Feeder Cables" on
page 147.
- BTS: You can select a base transceiver station (BTS) equipment from the BTS list. In GSM, only the
downlink losses are modelled. You can click the Browse button ( ) to access the properties of the BTS.
For information on creating a BTS, see "Defining BTS Equipment" on page 148.
- Feeder Length: You can enter the feeder length at transmission.
- Miscellaneous Losses: You can enter miscellaneous losses at transmission.
- Receiver Antenna Diversity Gain: This field is not used for GSM/GPRS/EDGE projects.
- Loss Related to Repeater Noise Rise: This field is not used for GSM/GPRS/EDGE projects.
Note: You can modify the Total Losses at transmission if you wish. Any value you enter must
be positive.
- Antennas:
- Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added
to the altitude of the site as given by the DTM. If the transmitter is situated on a building, the height entered
must include the height of building.
- Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the
Browse button ( ) to access the properties of the antenna. The other fields, Azimuth, Mechanical
Downtilt, and Additional Electrical Downtilt, display additional antenna parameters.
- Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power, which is
the percentage of power reserved for this particular antenna. For example, for a transmitter with one
secondary antenna, if you reserve 40% of the total power for the secondary antenna, 60% is available for
the main antenna.
For information on working with data tables, see "Working with Data Tables" on page 50.
- Under GPRS/EDGE Properties, you must select the GPRS/EDGE Transmitter check box if the transmitter
is going to be a packet-switched capable transmitter. You can select Coding Scheme Configuration from
the list. You can click the Browse button ( ) to access the properties of the configuration. For information
on creating Coding Scheme Configuration, see "Coding Scheme Configuration" on page 397.
Note: The modelling of EDGE Evolution on the transmitter side has to consider:
- The support of high order modulations and the use of turbo codes in specific coding
schemes which can be found in the appropriately selected GPRS/EDGE Configuration
In addition, EDGE Evolution can be modelled on the terminal side through (See "Creating
or Modifying a GSM/GPRS/EDGE Terminal" on page 405):
- The support of dual antenna terminals (Mobile Station Receive Diversity) and en-
hanced single antenna terminals (Single Antenna Interference Cancellation). Atoll a
statistical modelling of these through the use of an EDGE evolution configuration, with
the effect of SAIC or diversity already included both in the coding scheme admission
thresholds and on the Throughput vs C (resp. C/I) graphs.
- The support of multi-carriers which can be setup on the terminal side
- Under GSM Properties, you can select Codec Configuration from the list. You can click the Browse button
( ) to access the properties of the Codec Configuration assigned to the GSM transmitter. For information
on creating Coding Scheme Configuration, see "Codec Configuration" on page 394.
- Max. Range: You can enter the maximum range from the transmitter of its coverage.
Note: Although coverage is restricted from the set minimum range to the maximum range,
interference is calculated from the base station location to the maximum range.
Under Identification:
- BSIC Domain: You can select the BSIC (Base Station Identity Code) domain from the list. You can click the
Browse button ( ) to access the properties of the selected BSIC domain. For information on BSIC
domains, see "Defining BSIC Domains and Groups" on page 384.
- BSIC: The BSIC (Base Station Identity Code) colour code is associated with a defined BCCH so that a mobile
can identify the base station to which both a particular BCCH and BSIC are assigned. The BSIC is derived
from the NCC (Network Colour Code) and the BCC (BTS Colour Code).
To assign a BSIC number to the current transmitter, you can assign a number from the BSIC Domain by se-
lecting it from the list. You can also enter the BSIC number in the format NCC-BCC. When you click Apply,
Atoll converts the entered NCC-BCC number into the single-number BSIC format. For information on the
BSIC, see "Defining the BSIC Format" on page 384.
- BCCH: The BCCH text box displays the frequency of the BCCH (TS0 of the BCCH TRX) of the current trans-
mitter. If the BCCH subcell, under Subcell (TRX Groups) Settings on the TRXs tab, is in synthesized fre-
quency hopping (SFH) mode, you can enter the MAL channel which will be TS0.
- NCC-BCC: The NCC (Network Colour Code), identifying the operator, and the BCC (BTS Colour Code), iden-
tifying the base station are displayed in the NCC-BCC text box. The NCC and BCC are integers from 0 to 7.
Under Subcell (TRX Groups) Settings, the table lists each TRX group defined in the cell type selected under Cell
Type on the TRXs tab. The initial settings are from the selected cell type; you can modify them, with the exception
of the TRX Type:
- TRX Type: The TRX Type can be one of the default TRX types available in the GSM/GPRS/EDGE project
template:
- BCCH: The broadcast control channel (BCCH) carrier
- TCH: The default traffic (TCH) carrier
- TCH_EGPRS: The EDGE traffic (TCH_EGPRS) carrier.
- TCH_INNER: The inner traffic (TCH_INNER) carrier.
You can not modify the value in the TRX Type column.
- Frequency Domain: The frequency domain assigned to the TRX group. Only channels belonging to this fre-
quency domain will be allocated to TRXs of this group during manual or automatic frequency planning.
Note: The frequency domains assigned to the BCCH subcell and to the TCH subcell must
reference the same frequency band, unless you are modelling dual-band transmitters. For
information on dual-band transmitters, see "Advanced Modelling of Multi-Band
Transmitters" on page 401.
- Excluded Channels: The defined frequency domain may have, as part of its definition, a list of excluded chan-
nels. Addition excluded channels for this subcell can be added in the Excluded Channels column.
- Required TRXs: The number of TRXs required for the subcell. For subcells with the BCCH TRX Type, the
number of requested TRXs must be "1," the default value. For subcells with the TCH, TCH_EGPRS or
TCH_INNER TRX Type, the value in the Required TRXs column is a result of network dimensioning, which
depends on the traffic demand and the required quality.
- Traffic Load: The Traffic Load indicates the usage rate of TRXs; its value must be from 0 to 1. The value in
the Traffic Load column can be either user-defined or the result of network dimensioning, in which case it will
be the same value for all subcells covering the same area.
The traffic load is used to calculate interference and in automatic frequency planning.
- Circuit Demand: The circuit demand indicates the amount of Erlangs necessary to absorb the circuit-
switched demand. This value can be either user-defined or the result of a traffic capture.
- Packet Demand: The packet demand indicates the amount of timeslots necessary to absorb the packet-
switched demand. This value can be either user-defined or the result of a traffic capture.
- DL Power Reduction: The reduction of power relative to the transmitter power. The DL Power Reduction is
used to model the power reduction of TCH TRXs, TCH_EGPRS and of TCH_INNER TRXs. TCH_INNER
TRXs are concentric subcells, in other words, subcells that transmit a power lower than that used by the BCCH
TRX and by TCH TRXs.
Note: DL power reduction can also be used to model in a simple way the coverage reduction of
a 1800 subcell compared to the BCCH 900 subcell, assuming that all subcells are
transmitting at the same power. Atoll also enables advanced multi-band transmitter
modelling. For more information, see "Advanced Modelling of Multi-Band Transmitters" on
page 401 and the Administrator Manual.
- Mean Power Control Gain (dB): The average reduction in interference due to power control in downlink. This
gain is used when calculating interference generated by the subcell. Interference generated by the subcell is
reduced by this value during C/I calculations.
- Reception Threshold (dBm): The reception threshold defines the minimum reception level for the subcell. I
can be used as the minimum subcell reception sensitivity if the link budget is correctly defined.
- C/I Threshold (dB): The minimum signal quality for the TRX Type. The C/I Threshold can be used in inter-
ference studies and in the AFP.
- DTX Supported: The DTX Supported check box is selected if the subcell supports DTX (Discontinuous
Transmission) technology. Subcells supporting DTX can reduce the interference they produce by the defined
voice activity factor.
- Timeslot Configuration: The timeslot configuration defines the distribution of circuit, packet and shared
timeslots for the subcell. For information on timeslot configurations, see "Timeslot Configurations" on
page 400.
- Half-Rate Traffic Ratio (%): The percentage of half-rate voice traffic in the subcell. This value is used to cal-
culate the number of timeslots required to respond to the voice traffic demand.
- Target Rate of Traffic Overflow (%): The target rate of traffic overflow is used during traffic analysis to dis-
tribute the traffic between subcells and layers. The value is the percentage of candidate traffic overflowing to
a subcell with a lower priority. It has an impact on the traffic capture between inner and outer subcells, and
between micro and macro layers. In other words, The target rate of traffic overflow can be considered to an
estimation of the percentage of traffic rejected from subcells or layers of higher priority to subcells or layers of
lower subcells.
If the traffic overflow target is set to a value lower than the grade of service, it means that the traffic rejected
(according to the queuing model selected in the dimensioning model: Erlang B or Erlang C) will be lost and
will not overflow to other subcells.
Important: The target rate of traffic overflow and the half-rate traffic ratio must be the same for BCCH
and TCH subcells. If the values are different for BCCH and TCH subcells, Atoll will use
the values for the target rate of traffic overflow and the half-rate traffic ratio from the
BCCH subcell.
- Effective Rate of Traffic Overflow (%): The percentage of traffic overflowing from a subcell. The effective
rate of traffic overview is a result of the calculation of key performance indicators.
- Hopping Mode: The frequency hopping mode supported by the selected TRX type. The hopping mode can
be either "Base Band Hopping mode (BBH)" or "Synthesized Hopping mode (SFH)." If frequency hopping is
not supported, select "Non Hopping."
- Allocation Strategy: The allocation strategy used during manual or automatic frequency planning. There are
two available allocation strategies:
- Free: Any of the channels belonging to the frequency domain can be assigned to TRXs.
- Group Constrained: Only channels belonging to a same frequency group in the frequency domain can
be assigned. You can use the Preferred Frequency Group to define the preferred group of frequencies
when using the AFP.
- Max. MAL Length: The maximum length of the mobile allocation list (MAL), in other words, the maximum
number of channels allocated to the TRXs of the subcell during automatic frequency planning if the Hopping
Mode is either SFH (Synthesized Frequency Hopping) or BBH (Base Band Hopping) and if the Allocation
Strategy is Free.
- HSN Domain: Only hopping sequence numbers (HSN) belonging to the selected HSN domain will be allo-
cated to subcells during manual or automatic frequency planning. The HSNs are allocated if the Hopping
Mode is either SFH (Synthesized Frequency Hopping) or BBH (Base Band Hopping).
- HSN: The hopping sequence number (HSN) of the subcell. All TRXs of the subcell have the same HSN. The
HSN can be entered manually or allocated automatically. This parameter is used if the Hopping Mode is
either SFH (Synthesized Frequency Hopping) or BBH (Base Band Hopping).
- Freeze HSN: When the Freeze HSN check box is selected, the subcells currently assigned HSN is kept when
a new AFP session is started.
- Synchronisation: The value entered in the Synchronisation column is used during frequency hopping; fre-
quency hopping is synthesized among all TRXs of subcells with the same string of characters in the Synchro-
nisation column. By default, the name of the site is used as the value in the Synchronisation column,
synchronising frequency hopping for all TRXs on the same site. However, you can, for example, enter different
values for each subcell to define synchronisation at the subcell level, or different values for each group of sites
to define synchronisation by sites group.
- AFP Weight: Enter an AFP weight. The AFP weight is used to increase or decrease the importance of a sub-
cell during automatic frequency planning. The value must be a real number. The higher the AFP weight is, the
higher the constraint on the TRX type. The AFP weight artificially mulitplies the cost which has to be minimised
by the AFP.
- % Max. Interference: The maximum level of interference allowable during automatic frequency planning. The
interference is defined as a percentage of area or traffic, as defined during the calculation of the interference
matrices.
- Preferred Frequency Group: When the Group Constrained allocation strategy is selected, in any hopping
mode (including non-hopping), the AFP tries to assign frequencies from the preferred group during automatic
allocation. The preferred frequency group is a soft constraint used by the AFP to assign frequencies to TRXs.
When the AFP is unable to assign a frequency from the preferred group, and allocates a frequency from out-
side the group, a corresponding cost is taken into account. The preferred group can also be the result of allo-
cation if the AFP model is able to allocate patterns based on the azimuth.
- Default TRX Configuration: The default TRX Configuration selected in this column is applied to all TRXs
belonging to the subcell. By selecting the default TRX Configuration, the maximum number of coding schemes
in GPRS and in EDGE is set at the TRX type level. You can also define the TRX Configuration for each TRX.
- AFP Congestion: This value may be an output of an AFP model which can estimate the level of congestion
for a pool of subcells (e.g. BCCH and TCH are considered as a pool of subcells since they are managed
together). In other words, an highly congested pool of subcells will be the source of high interferences. This
value can be commited to subcell pools when assigning a frequency plan.
- AFP Cost: This value may be an output of an AFP model for which the frequency plan quality is based on a
cost function. This value can be commited to subcell pools when assigning a frequency plan.
- AFP Blocking Cost: This value may be an output of an AFP model for which the frequency plan quality is
based on a cost function, and represents a part of the cost where the traffic is considered as blocked, as an
opposite to the correctly served traffic which has to be maximised by the AFP model. This value can be com-
mited to subcell pools when assigning a frequency plan.
- AFP Separation Cost: This value may be an output of an AFP model for which the frequency plan quality is
based on a cost function. It represents the component of the cost which is incremented when the separation
rules are not respected between subcell pools. As a consequence, if separation constraints are violated, this
has a direct effect on the interference level. This value can be commited to subcell pools when assigning a
frequency plan.
- EDGE Power Backoff (dB): The average power reduction for EDGE transmitters due to 8PSK, 16QAM and
32QAM modulations in EDGE. This has an impact on the EDGE service zone which can be seen in traffic anal-
ysis and EDGE predictions.
- Number of Antennas (Transmission Diversity): The number of antennas the subcell can use for transmis-
sion. In most cases, a transmitter will transmit with only one antenna, however, some transmitters are capable
of transmission diversity. By transmitting on more than one antenna, the signal experiences a gain of 3 dB. An
additional transmission diversity gain can be defined per clutter class in order to correctly model gain due to
the environment.
- Freeze the number of required TRXs: This option may be used by an AFP model which has the capability
to optimise the number of required TRXs (increase or decrease) with the only aim to maximise the amount of
correctly served traffic. In other words, you may have less TRXs than required if these ones are not subject to
any interferences and the amount of correctly served traffic will be larger. When you select this option, the
functionality is blocked on the considered subcell.
Note: If some subcell fields are empty (e.g., HSN domain, frequency domain, C/I Threshold),
Atoll uses the default values of the selected Cell type. For more information, see
"Creating a Cell Type" on page 390.
Note: The TRXs of the entire GSM/GPRS/EDGE document are found in the TRX Table. You
can access the TRX Table by right-clicking the Transmitters folder in the Data tab of the
Explorer window and then selecting Network Settings > TRXs from the context menu.
d. Select Properties from the context menu. The sites Properties dialogue appears.
3. Modify the parameters described in "Site Description" on page 247.
4. Click OK.
Tip: If you are creating several sites at the same time, or modifying several existing sites, you
can do it quickly by editing or pasting the data directly in the Sites table. You can open
the Sites table by right-clicking the Sites folder on the Data tab of the Explorer window
and selecting Open Table from the context menu. For information on copying and
pasting data, see "Copying and Pasting in Tables" on page 56.
Tips:
If you are creating several transmitters at the same time, or modifying several existing trans-
mitters, you can do it more quickly by editing or pasting the data directly in the Transmitters
table. You can open the Transmitters table by right-clicking the Transmitters folder on the
Data tab of the Explorer window and selecting Open Table from the context menu. For infor-
mation on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
If you want to add a transmitter to an existing site on the map, you can add the transmitter by
right-clicking the site and selecting New Transmitter from the context menu.
Tip: If you are applying a new cell type to several transmitters at the same time, or modifying
several existing transmitters, you can do it more quickly by editing or pasting the data
directly in the Transmitters table. You can open the Transmitters table by right-clicking
the Transmitters folder on the Data tab of the Explorer window and selecting Open
Table from the context menu. For information on copying and pasting data, see "Copying
and Pasting in Tables" on page 56.
Tip: If you are creating several subcells at the same time, or modifying several existing
subcells, you can do it more quickly by editing or pasting the data directly in the Subcells
table. You can open the Subcells table by right-clicking the Transmitters folder on the
Data tab of the Explorer window and selecting Subcells > Open Table from the context
menu. For information on copying and pasting data, see "Copying and Pasting in Tables"
on page 56.
Tip: If you are creating several TRXs at the same time, or modifying several existing TRXs,
you can do it more quickly by editing or pasting the data directly in the TRXs table. You
can open the TRXs table by right-clicking the Transmitters folder on the Data tab of the
Explorer window and selecting Subcells > TRXs from the context menu. For information
on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
3. In the map window, move the pointer over the map to where you would like
to place the new station. The exact coordinates of the pointers current loca-
tion are visible in the Status bar.
Tips:
To place the station more accurately, you can zoom in on the map before you click the New
Station button. For information on using the zooming tools, see "Changing the Map Scale" on
page 38.
If you let the pointer rest over the station you have placed, Atoll displays its tip text with its
exact coordinates, allowing you to verify that the location is correct.
You can also place a series of stations using a Atoll template. You do this by defining an area on the map where you want
to place the stations. Atoll calculates the placement of each station according to the defined hexagonal subcell radius in
the station template. For information on defining the subcell radius, see "Creating or Modifying a Station Template" on
page 258.
To place a series of stations within a defined area:
1. In the Radio toolbar, select a template from the list.
2. Click the Hexagonal Design button ( ), to the left of the template list. A hexagonal design is a group of stations
created from the same station template.
Note: If the Hexagonal Design button is not available ( ), the hexagonal subcell radius for
this template is not defined. For information on defining the cell radius, see "Creating or
Modifying a Station Template" on page 258.
3. Draw a zone delimiting the area where you want to place the series of stations:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
Atoll fills the delimited zone with new stations and their hexagonal shapes. Station objects such as sites and trans-
mitters are also created and placed into their respective folders.
You can work with the sites and transmitters in these stations as you work with any station object, adding, for example,
another antenna to a transmitter.
When you place a new station using a station template as explained in "Placing a New Station Using a Station Template"
on page 256, the site is created at the same time as the station. However, you can also place a new station on an existing
site.
To place a station on an existing site:
1. On the Data tab, clear the display check box beside the Hexagonal Design folder.
2. In the Radio toolbar, select a template from the list.
- Under Main Antenna, you can modify the following: the antenna Model, 1st Sector Azimuth, from which the
azimuth of the other sectors are offset to offer complete coverage of the area, the Height of the antenna from
the ground (i.e., the height over the DTM; if the transmitter is situated on a building, the height entered must
include the height of building), the Mechanical Downtilt, and the Additional Electrical Downtilt.
- Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both
the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Managing
Calculations in Atoll.
5. Click the Transmitter tab. In this tab (see Figure 7.10), you can modify the following:
- Under Transmission, you can select to enter either Power and Total Losses or EIRP (Effective Isotropically
Radiated Power). If you select EIRP, you can enter the value yourself, without defining power and losses for
the transmitter.
If you select Power and Total Losses, Atoll calculates losses and noise according to the characteristics of
the equipment assigned to the transmitter. Equipment can be assigned using the Equipment Specifications
dialogue which appears when you click the Equipment button. Atoll will calculate the EIRP with the following
formula:
For information on the Equipment Specifications dialogue, see "Transmitter Description" on page 247.
If you want transmitters created with this station template to be active by default, select the Active check box.
- Transmitter Type: If you want Atoll to consider the transmitter(s) as potential server(s) as well as inter-
ferer(s), set the transmitter type to Intra-Network (Server and Interferer). If you want Atoll to consider trans-
mitter(s) only as interferer(s), set the type to Extra-Network (Interferer Only). No coverage for an Interferer
Only transmitter will be calculated for coverage predictions.
This feature enables you to model the co-existence of different networks in the same geographic area. For
more information on how to study interference between co-existing networks, see "Modelling the Co-existence
of Networks" on page 408.
6. Click the Configurations tab. In this tab (see Figure 7.11), you select the configuration used for GSM and GPRS/
EDGE stations.
- Under GPRS/EDGE Properties, you must select the GPRS/EDGE Transmitter check box if the transmitters
are going to be packet-switched capable transmitters, select Coding Scheme Configuration from the list. For
information on creating Coding Scheme Configuration, see "Coding Scheme Configuration" on page 397.
Note: The modelling of EDGE Evolution on the station side has to consider:
- The support of high order modulations and the use of turbo codes in specific coding
schemes which can be found in the appropriately selected GPRS/EDGE Configuration
In addition, EDGE Evolution can be modelled on the terminal side through (See "Creating
or Modifying a GSM/GPRS/EDGE Terminal" on page 405):
- The support of dual antenna terminals (Mobile Station Receive Diversity) and en-
hanced single antenna terminals (Single Antenna Interference Cancellation). Atoll a
statistical modelling of these through the use of an EDGE evolution configuration, with
the effect of SAIC or diversity already included both in the coding scheme admission
thresholds and on the Throughput vs C (resp. C/I) graphs.
- The support of multi-carriers which can be setup on the terminal side
- For all transmitters, you can select Codec Configuration from the list. For information on creating Coding
Scheme Configuration, see "Codec Configuration" on page 394.
7. Click the Neighbours tab. In this tab (see Figure 7.12), you can modify the Max Number of Intra-Technology
Neighbours and the Max Number of Inter-Technology Neighbours. For information on defining neighbours,
see "Planning Neighbours" on page 294.
8. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the
Sites table, or if you have defined an additional field in the Station Template Properties dialogue.
9. When you have finished setting the parameters for the station template, click OK to close the dialogue and save
your changes.
5. In the map window, move the pointer over the map to where you would like to place the new base station. The
exact coordinates of the pointers current location are visible in the Status bar.
Tips:
To place the base station more accurately, you can zoom in on the map before you select
Duplicate from the context menu. For information on using the zooming tools, see "Changing
the Map Scale" on page 38.
If you let the pointer rest over the station you have placed, Atoll displays its tip text with its
exact coordinates, allowing you to verify that the location is correct.
You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to
place each duplicate base station.
For more information on the site, transmitter, subcell, and TRX properties, see "Definition of a Base Station" on page 247.
Note: When you import data into your current Atoll document, the coordinate system of the
imported data must be the same as the display coordinate system used in the document.
If you cannot change the coordinate system of your source data, you can temporarily
change the display coordinate system of the Atoll document to match the source data.
For information on changing the coordinate system, see "Setting a Coordinate System"
on page 92.
base stations by copying and pasting data, you must copy and paste site data in the Sites table, transmitter data
in the Transmitters table, and subcell data in the Subcells table, in that order.
Important: The table you copy data from must have the same column layout as the table you are
pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
Importing data: If you have data in text or comma-separated value (CSV) format, you can import it into the tables
in the current document. If the data is in another Atoll document, you can first export it in text or CSV format and
then import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select
what values you import into which columns of the table.
When you create a group of base stations by importing data, you must import site data in the Sites table, trans-
mitter data in the Transmitters table, and subcell data in the Subcells table, in that order.
For information on exporting table data, see "Exporting Tables to Text Files" on page 58. For information on
importing table data, see "Importing Tables from Text Files" on page 59.
Note: You can quickly create a series of base stations for study purposes using the Hexagonal
Design tool on the Radio toolbar. For information, see "Placing a New Station Using a
Station Template" on page 256.
( and ). For information on defining the transmitter symbol, see "Defining the Display Type" on page 34.
Note: Broad-band repeaters are not modelled. Atoll assumes that all carriers from the 3G donor
transmitter are amplified.
4. To create repeater equipment, enter the following in the row marked with the New Row icon ( ):
a. Enter a Name and Manufacturer for the new equipment.
b. Enter minimum and maximum repeater amplification gains in the Min. Gain and Max Gain columns. These
parameters enable Atoll to ensure that the user-defined amplifier gain is consistent with the limits of the equip-
ment if there are any.
c. Enter a Gain Increment. Atoll uses the increment value when you increase or decrease the repeater amplifier
gain using the buttons to the right of the Amplification box ( ) on the General tab of the repeater Properties
dialogue.
d. Enter a Max. Downlink Power. This parameter is used to ensure that the downlink power is not exceeded
after amplification by the repeater.
Note: Uplink losses and noise figures are not modelled in GSM/GPRS/EDGE so any value
entered into the Max. Uplink Power column will not be used. The column is included to
ensure consistency with other technologies.
e. If desired, enter an Internal Delay and Comments. These fields are for information only and are not used in
calculations.
5. To modify repeater equipment, change the parameters in the row containing the repeater equipment you wish to
modify.
2. Click the arrow next to New Repeater or Remote Antenna button ( ) on the Radio toolbar.
3. Select Repeater from the menu.
4. Click the map to place the repeater. The repeater is placed on the map, represented by a symbol ( ) in the
same colour as the donor transmitter or repeater. By default, the repeater has the same azimuth as the donor
transmitter or repeater. Its tooltip and label display the same information as displayed for the donor transmitter or
repeater. As well, its tooltip and label identify the repeater and the donor transmitter or repeater.
For information on defining the properties of the new repeater, see "Defining the Properties of a Repeater" on
page 264.
Note: You can see to which base station the repeater is connected by clicking it; Atoll displays
a link to the donor transmitter or repeater.
Important: The table you copy data from must have the same column layout as the table you are
pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
Important: If you want to create a remote antenna, you must select Optical Fibre Link.
- If you selected Air Link under Donor-Repeater Link, enter the following information under Antenna:
i. Select a Model from the list. You can click the Browse button ( ) to access the properties of the
antenna.
ii. Enter the height off the ground of the antenna in the Height/Ground box. This will be added to the altitude
of the transmitter as given by the DTM.
iii. Enter the Azimuth and the Mechanical Downtilt.
Note: You can click the Calculate button to update azimuth and downtilt values after changing
the repeater donor side antenna height or the repeater location. If you choose another site
or change site coordinates in the General tab, click Apply before clicking the Calculate
button.
- If you selected Air Link under Donor-Repeater Link, enter the following information under Feeders:
i. Select a Type of feeder from the list. You can click the Browse button ( ) to access the properties of
the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
5. Click the Coverage Side tab. You can modify the following parameters:
- Select the Active check box. Only active repeaters (displayed in red in the Transmitters folder in the Data
tab of the Explorer window) are calculated.
- Under Transmission, enter the a value for EIRP (Effective Isotropically Radiated Power) or click Calculate
to determine the actual gains. Atoll calculates the EIRP with the following formula:
EIRP = Power + Gain - Losses
ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( ) to access the
properties of the antenna. Then, enter the Azimuth, the Mechanical Downtilt, and, if applicable, the Ad-
ditional Electrical Downtilt. By default, the characteristics (antenna, azimuth, height, etc.) of the repeater
coverage side correspond to the characteristics of the donor transmitter.
iii. Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power. For infor-
mation on working with data tables, see "Working with Data Tables" on page 50.
- Under Feeders, you can modify the following information:
i. Select a Type of feeder from the list. You can click the Browse button ( ) to access the properties of
the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
- Under Losses, Atoll displays the Loss Related to Repeater Noise Rise.
6. Click the Propagation tab. Since repeaters are taken into account during calculations, you must set the propaga-
tion parameters. On the Propagation tab, you can modify the following: the Propagation Model, Radius, and Res-
olution for both the Main Matrix and the Extended Matrix. By default, the propagation characteristics of the
repeater (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For infor-
mation on propagation models, see Chapter 5: Managing Calculations in Atoll.
Note: Ensure that the remote antennas donor transmitter does not have any antennas.
2. Click the arrow next to New Repeater or Remote Antenna button ( ) on the Radio toolbar.
3. Select Remote Antenna from the menu.
4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol
( ) in the same colour as the donor transmitter. By default, the remote antenna has the same azimuth as the
donor transmitter. Its tooltip and label display the same information as displayed for the donor transmitter. As well,
its tooltip and label identify the remote antenna and the donor transmitter.
For information on defining the properties of the new remote antenna, see "Defining the Properties of a Remote
Antenna" on page 266.
Note: You can see to which base station the remote antenna is connected by clicking it; Atoll
displays a link to the donor transmitter.
Important: The table you copy data from must have the same column layout as the table you are
pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
- You can change the Site on which the remote antenna is located. Clicking the Browse button ( ) opens
the Properties dialogue of the site.
- You can enter a Position relative to site location, if the remote antenna is not located on the site itself.
4. Click the Donor Side tab. You can modify the following parameters:
- Under Donor-Repeater Link, select Optical Fibre Link and enter the Fibre Losses.
5. Click the Coverage Side tab. You can modify the following parameters:
- Select the Active check box. Only active remote antennas (displayed in red in the Transmitters folder in the
Data tab of the Explorer window) are calculated.
- Under Transmission, enter the a value for EIRP (Effective Isotropically Radiated Power) or click Calculate
to determine the actual gains. Atoll calculates the EIRP with the following formula:
EIRP = Power + Gain - Losses
ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( ) to access the
properties of the antenna. Then, enter the Azimuth, the Mechanical Downtilt, and, if applicable, the Ad-
ditional Electrical Downtilt. By default, the characteristics (antenna, azimuth, height, etc.) of the repeater
coverage side correspond to the characteristics of the donor transmitter.
iii. Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power. For infor-
mation on working with data tables, see "Working with Data Tables" on page 50.
- Under Feeders, you can modify the following information:
i. Select a Type of feeder from the list. You can click the Browse button ( ) to access the properties of
the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
6. Click the Propagation tab. Since remote antennas are taken into account during calculations, you must set prop-
agation parameters, as with transmitters. On the Propagation tab, you can modify the following: the Propagation
Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. By default, the propagation
characteristics of the remote antenna (model, calculation radius, and grid resolution) are the same as those of the
donor transmitter. For information on propagation models, see Chapter 5: Managing Calculations in Atoll.
It is important not to confuse the computation zone and the focus zone or hot spot zone. The computation zone
defines the area where Atoll computes path loss matrices, coverage predictions, interference matrices, etc., while
the focus zone or hot spot zone is the area taken into consideration when generating reports and results.
For information on the computation zone, see "Creating a Computation Zone" on page 276.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be
studied.
2. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the fol-
lowing:
- Move the receiver to change the current position.
- Click to place the receiver at the current position. You can move the receiver again by clicking it a second time.
- Right-click the receiver to choose one of the following commands from the context menu:
- Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates.
- Target Site: Select a site from the list to place the receiver directly on a site.
4. Click the Profile tab.
5. The profile analysis appears in the Profile tab of the Point Analysis Tool window. The altitude (in metres) is
reported on the vertical axis and the receiver-transmitter distance on the horizontal axis. A blue ellipsoid indicates
the Fresnel zone between the transmitter and the receiver, with a green line indicating the line of sight (LOS). Atoll
displays the angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an
obstacle, this causes attenuation with diffraction displayed by a red vertical line (if the propagation model used
takes diffraction mechanisms into account). The main peak is the one that intersects the most with the Fresnel
ellipsoid. With some propagation models using a 3 knife-edge Deygout diffraction method, the results may display
two additional attenuations peaks. The total attenuation is displayed above the main peak.
The results of the analysis are displayed at the top of the Profile tab:
You can change the following options at the top of the Profile tab:
Note: You can use the same procedure to study the signal level coverage of several sites by
grouping the transmitters. For information on grouping transmitters, see "Grouping Data
Objects by a Selected Property" on page 65.
Tip: If you wish to study only sites by their status, at this step you could group them by status.
c. Select Open Table from the context menu. A table appears with the properties of the selected group of trans-
mitters.
d. In the table, you can configure two propagation models: one for the main matrix, with a shorter radius and a
higher resolution, and another for the extended matrix, with a longer radius and a lower resolution. By calcu-
lating two matrices you can reduce the time of calculation by using a lower resolution for the extended matrix
and you can obtain more accurate results by using propagation models best suited for each distance for the
main and extended matrices.
e. In the Main Matrix column:
- Select a Propagation Model
- Enter a Radius and Resolution.
f. If desired, in the Extended Matrix column:
- Select a Propagation Model
- Enter a Radius and Resolution.
g. Close the table.
4. Right-click the object either in the Explorer window or on the map. The context menu appears.
5. In the Transmitters folder, right-click the group of transmitters you want to study and select Calculations >
Create a New Study from the context menu. The Study Types dialogue appears.
The Study Types dialogue lists the studies available. They are divided into Standard Studies, supplied with
Atoll, and Customized Studies. Unless you have already created some customized studies, the Customized
Studies list will be empty.
6. Select Coverage by Signal Level and click OK. The coverage prediction Properties dialogue appears.
7. You can configure the following parameters in the Properties dialogue:
- General tab: You can change the assigned Name of the coverage prediction, the Resolution, and you can
add a Comment. The resolution you set is the display resolution, not the calculation resolution.
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:
City Centre 5m
City 20 m
County 50 m
State 100 m
Note: If you create a new coverage prediction from the context menu of either the Transmitters
or Predictions folder, you can select the sites using the Group By, Sort, and Filter
buttons under Configuration. Because you already selected the target sites, however,
only the Filter button is available.
- Condition tab: The coverage prediction parameters on the Conditions tab allow you to define the signals that
will be considered for each pixel (see Figure 7.15).
- At the top of the Condition tab, you can set the range of signal level to be considered. You can click the
arrow button ( ) and select Subcell Reception Threshold if you want to use the reception threshold
specified for each subcell (including the defined power reduction) as the lower end of the signal level range
or Specified Reception Threshold if you want to enter a threshold to be used for all subcells as the lower
end of the signal level range.
- In Figure 7.15, a Specified Reception Threshold less than or equal to -105 dBm will be considered.
- Under Server, select "All" to consider all servers.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage
Probability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select which TRX type to consider by selecting it from the Reception from Subcells list.
- Display tab: You can modify how the results of the coverage prediction will be displayed.
- Under Display Type, select "Value Intervals."
- Under Field, select "Best signal level." Selecting "All" or "Best signal level" on the Conditions tab will give
you the same results because Atoll displays the results of the best server in either case. Selecting "Best
signal level" necessitates, however, the longest time for calculation.
- You can change the value intervals and their displayed colour. For information on changing display prop-
erties, see "Display Properties of Objects" on page 33.
- You can create a tooltip with information about the coverage prediction by clicking the Browse button
( ) next to the Tip Text box and selecting the fields you want to display in the tooltip.
- You can select the Add to Legend check box to add the displayed value intervals to the legend.
Note: If you change the display properties of a coverage prediction after you have calculated it,
you may make the coverage prediction invalid. You will then have to recalculate the
coverage prediction to obtain valid results.
8. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The signal level
coverage prediction can be found in the Predictions folder on the Data tab. Atoll automatically locks the results of a cover-
age prediction as soon as it is calculated, as indicated by the icon ( ) beside the coverage prediction in the Predictions
folder. When you click the Calculate button ( ), Atoll only calculates unlocked coverage predictions ( ).
Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices
using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main prop-
agation model with a shorter radius (displayed with a blue square in Figure 7.16) and a higher resolution and an extended
propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate
higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower reso-
lution path loss matrices outside the area covered by the main propagation model.
In this section, the following are explained:
"Path Loss Matrices" on page 272
"Assigning a Propagation Model" on page 274
"The Calculation Process" on page 276
"Creating a Computation Zone" on page 276
"Setting Transmitters as Active" on page 277
"Signal Level Coverage Predictions" on page 278
"Analysing a Coverage Prediction" on page 286
"Printing and Exporting Coverage Prediction Results" on page 294.
Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matri-
ces in the Atoll document results in a more portable but significantly larger document. in the case of large radio-planning
projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case
of large radio-planning projects, saving your path loss matrices externally will help reduce the size of the file and the use
of computer resources.
The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same
radio-planning document and share the path loss matrices. In this case, the radio data is stored in a database and the path
loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and
recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path
loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to
radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual.
When you save the path loss matrices to an external directory, Atoll creates:
One file per transmitter with the extension LOS for its main path loss matrix
A DBF file with validity information for all the main matrices.
A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
To set the storage location of the path loss matrices:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss
matrices and the location for the shared path loss matrices:
- Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are
loading path loss matrices from a shared location, where you store your changes to shared path loss matrices.
Click the button beside the Private Directory ( ) and select Embedded to save the path loss matrices in
the Atoll document, or Share to select a directory where Atoll can save the path loss matrices externally.
Note: Path loss matrices you calculate locally are not stored in the same directory as shared
path loss matrices. Shared path loss matrices are stored in a read-only directory. In other
words, you can read the information from the shared path loss matrices but any changes
you make will be stored locally, either embedded in the ATL file or in a private external
folder, depending on what you have selected in Private Directory.
Caution: When you save the path loss files externally, the external files are updated as soon as
calculations are performed and not only when you save the Atoll document. In order to
keep consistency between the Atoll document and the stored calculations, you should
save the Atoll document before closing it if you have updated the path loss matrices.
- Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a
database and the common path loss matrices are stored in a directory that is accessible to all users. Any
changes you make will not be saved to this directory; they will be saved in the location indicated in Private
Directory. The path loss matrices in the shared directory are updated by a user with administrator rights based
on the updated information in the database. For more information on shared directories, see the Administrator
Manual.
5. Click OK.
Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want,
you can check whether the path loss matrices are valid without creating a coverage prediction.
To check if the path loss matrices are valid:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Propagation tab. The Available Results table lists the following information for the path loss matrix for
each transmitter:
5. Click the Propagation tab. The path loss matrix information is listed in the Available Results table.
6. Select one of the following display options:
- Display all the matrices: All path loss matrices are displayed.
- Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available Results table lists the following information for each displayed path loss matrix:
2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation
Model to All Transmitters" on page 274, this is the propagation model that will be used for all transmitters, except
for those to which you will assign a propagation model either individually or as part of a group.
3. If you have assigned a default propagation model for coverage predictions, as described in "Assigning a Default
Propagation Model for Coverage Predictions" on page 276, this is the propagation model that will be used for all
transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model
chosen as the main propagation model, that is the propagation model that will be used.
In this section, the following methods of assigning a propagation model are explained:
"Assigning a Propagation Model to All Transmitters" on page 274
"Assigning a Propagation Model to a Group of Transmitters" on page 275
"Assigning a Propagation Model to One Transmitter" on page 275
"Assigning a Default Propagation Model for Coverage Predictions" on page 276.
Note: If you are modelling multi-band transmitters, you can assign a different propagation model
to each frequency band. For more information, see "Advanced Modelling of Multi-Band
Transmitters" on page 401.
Note: If you set a different main or extended matrix on an individual transmitter as explained in
"Assigning a Propagation Model to One Transmitter" on page 275 after having assigned a
propagation model to all transmitters, you will override this entry.
Transmitters that share the same parameters and environment will usually use the same propagation model and settings.
In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common
parameters and then assigning the propagation model.
To define a main and extended propagation model for a defined group of transmitters:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select from the Group By submenu of the context menu the property by which you want to group the transmitters.
The objects in the folder are grouped by that property.
Note: You can group transmitters by several properties by using the Group By button on the
Properties dialogue. For more information, see "Advanced Grouping" on page 66.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model
to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmit-
ters.
When you assign a main and extended propagation model to a single transmitter, it overrides any changes you have previ-
ously made globally. The propagation model settings apply to all the subcells on the same transmitter. For example, if the
BCCH is a 900 MHz subcell, the same propagation model is also assigned to a TCH_INNER 1800 MHz subcell. By defin-
ing a multi-band transmitter, you can assign propagation model-related settings that are optimised to the frequency band
of each subcell when more than one frequency band is used on a transmitter. For more information on multi-band trans-
mitters, see "Advanced Modelling of Multi-Band Transmitters" on page 401.
To define a main and extended propagation model for all transmitters:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Transmitters folder.
3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu
appears.
4. Select Properties from the context menu. The Properties dialogue appears.
5. Click the Propagation tab.
You can assign a default propagation model for coverage predictions. This propagation model is used as for all transmit-
ters whose main propagation model is "(Default model)."
To assign a default propagation model for coverage predictions:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Predictions tab.
5. Select a Default Propagation Model from the list.
6. Enter a Default Resolution. When you create a new coverage prediction, the default resolution is the value you
enter here.
Tip: By making the necessary entry in the atoll.ini file, if you clear the value entered in the
Resolution box when you create a coverage prediction, Atoll will calculate the coverage
prediction using the currently defined default resolution. That way, if you have many
coverage predictions, you can change their resolution by changing the default resolution
and recalculating the coverage predictions. Atoll will then calculate them using the
updated resolution. For information on changing entries in the atoll.ini file, see the
Administrator Manual.
7. Click OK. The selected propagation model will be used for coverage predictions for all transmitters whose main
propagation model is "(Default model)."
2. If the path loss matrices do not exist or are not valid, Atoll calculates them. There has to be at least one unlocked
coverage prediction in the Predictions folder. If not Atoll will not calculate the path loss matrices when you click
the Calculate button ( ).
3. Atoll calculates all unlocked coverage predictions in the Predictions folder. Atoll automatically locks the results
of a coverage prediction as soon as it is calculated, as indicated by the icon ( ) beside the coverage prediction
in the Predictions folder.
Notes:
You can stop any calculations in progress by clicking the Stop Calculations button ( ) in
the toolbar.
When you click the Force Calculation button ( ) instead of the Calculate button, Atoll cal-
culates all path loss matrices, unlocked coverages, and pending simulations.
You can also create a computation zone using one of the following methods:
Existing polygon: You can use any existing polygon on the map as a computation zone by right-clicking it and
selecting Use as Computation Zone from the context menu.
Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a computation zone. You can import it by right-clicking the Computa-
tion Zone folder on the Geo tab and selecting Import from the context menu.
Fit to Map Window: You can create a computation zone the size of the map window by selecting Fit to Map
Window from the context menu.
Once you have created a computation zone, you can use Atolls polygon editing tools to edit it. For more information on
the polygon editing tools, see "Using Polygon Zone Editing Tools" on page 44.
Note: You can save the computation zone, so that you can use it in a different Atoll document,
in the following ways:
- By saving the computation zone in the user configuration. For information on exporting
the computation zone in the user configuration, see "Exporting a User Configuration"
on page 75.
- By right-clicking the Computation Zone folder on the Data tab of the Explorer window
and selecting Export from the context menu.
Note: For information on grouping data objects, see "Grouping Data Objects" on page 65.
3. Select Activate Transmitters from the context menu. The selected transmitters are set as active.
To set more than one transmitter as active using the Transmitters table:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Open Table. The Transmitters table appears with each transmitters parameters in a second row.
4. For each transmitter that you want to set as active, select the check box in the Active column.
To set transmitters as active using a zone:
1. Click the Geo tab of the Explorer window.
2. Click the Expand button ( ) to the left of Zones folder to expand the folder.
3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears.
Note: If you do not yet have a zone containing the transmitters you want to set as active, you
can draw a zone as explained in "Using Zones in the Map Window" on page 41.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active.
Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on
choosing and configuring a propagation model, see Chapter 5: Managing Calculations in Atoll.
Calculating path loss matrices can be extremely time and resource intensive when you are working on larger projects.
Consequently, Atoll offers you the possibility of distributing path loss calculations on several computers. You can install
the Atoll computing server application on other workstations or on servers. Once the computing server application is
installed on a workstation or server, the computer is available for distributed path loss calculation to other computers on
the network. For information on distributed calculations, see the Administrator Manual.
6. Click the Condition tab (see Figure 7.18). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow
button ( ) and select one of the following thresholds:
- Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception
threshold specified for each subcell (including the defined power reduction) as the lower end of the signal
level range.
- Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold
to be used for all subcells as the lower end of the signal level range.
- In Figure 7.18, a Specified Reception Threshold less than or equal to -105 dBm will be considered.
- Under Server, select "All" to consider all servers.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select which TRX type to consider by selecting it from the Reception from Subcells list.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 7.19).
Note: You can also display the best idle mode reselection criterion (C2) by selecting "Best C2"
on the Display tab. This allows you to compare the coverage in idle mode with the
coverage in dedicated mode. For more information on coverage predictions in idle mode,
See "Making a Coverage Prediction by Transmitter Based on the Best Idle Mode
Reselection Criterion (C2)" on page 283.
When you base a coverage prediction by transmitter on the best signal level, Atoll will consider the best signal level on
each pixel. A coverage prediction by transmitter based on the best signal level is more suitable for a network that does not
have HCS layers. If the network has HCS layers, a coverage prediction by transmitter based on the best signal level can
give misleading results as the best signal on any pixel will usually be on a macro layer, although not all users will neces-
sarily connect to it.
To make a coverage prediction by transmitter based on the best signal level:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Transmitter and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 7.20). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow
button ( ) and select one of the following thresholds:
- Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception
threshold specified for each subcell (including the defined power reduction) as the lower end of the signal
level range.
- Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold
to be used for all subcells as the lower end of the signal level range.
In Figure 7.20, a Specified Reception Threshold less than or equal to -105 dBm will be considered.
- Under Server, select "Best Signal Level" to take the best signal level from all servers on all layers into consid-
eration (for more information, see "Comparing Service Areas in Calculations" on page 386).
- Enter a hand-over margin in the With a Margin text box. The default value is "4 dB."
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select which TRX type to consider by selecting it from the Reception from Subcells list.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Note: You can also predict which server is the second best server on each pixel by selecting
"Second Best Signal Level" on the Conditions tab and setting "Discrete Values" as the
Display Type and "Transmitter" as the Field on the Display tab.
Making a Coverage Prediction by Transmitter Based on the Best Signal Level by HCS Layer
When you base a coverage prediction by transmitter on the best signal level by HCS layer, Atoll will consider the best
signal level by HCS layer on each pixel. Grouping the results by HCS layer will allow you to quickly select which HCS layer
is displayed.
To make a coverage prediction by transmitter based on the best signal level per HCS layer:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Transmitter and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
- Under Configuration on the General tab, click the Click the Group By button. The Group dialogue appears.
- Select "HCS Layers" in the Available Fields list and click to move it to the Group these fields
in this order list.
- Click OK to close the Group dialogue.
6. Click the Condition tab (see Figure 7.20). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow
button ( ) and select one of the following thresholds:
- Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception
threshold specified for each subcell (including the defined power reduction) as the lower end of the signal
level range.
- Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold
to be used for all subcells as the lower end of the signal level range.
In Figure 7.20, a Specified Reception Threshold less than or equal to -105 dBm will be considered.
- Under Server, select "Best Signal Level per HCS Layer" to take the best signal level from all servers on each
HCS layer into consideration (for more information, see "Comparing Service Areas in Calculations" on
page 386).
- Enter a hand-over margin in the With a Margin text box. The default value is "4 dB."
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select which TRX type to consider by selecting it from the Reception from Subcells list.
7. Click the Display tab.
For a coverage prediction by transmitter, the Display Type "Discrete Values" based on the Field "Transmitter" is
selected by default. Each coverage zone will then be displayed with the same colour as that defined for each trans-
mitter. For information on defining transmitter colours, see "Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. You can select
which HCS layer to display by clicking the Expand button ( ) to expand the coverage prediction in the Predictions folder
and the selecting only the visibility check box of the HCS layer you want to display
Note: You can also predict which server is the second best server per HCS layer on each pixel
by selecting "Second Best Signal Level per HCS Layer" on the Conditions tab and setting
"Discrete Values" as the Display Type and "Transmitter" as the Field on the Display tab.
When you base a coverage prediction by transmitter on HCS servers, Atoll will consider the best signal level by HCS layer
on each pixel, assuming the cell edge of each layer is defined by the HCS threshold.
To make a coverage prediction by transmitter on HCS servers:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Transmitter and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 7.20). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow
button ( ) and select one of the following thresholds:
- Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception
threshold specified for each subcell (including the defined power reduction) as the lower end of the signal
level range.
- Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold
to be used for all subcells as the lower end of the signal level range.
In Figure 7.20, a Specified Reception Threshold less than or equal to -105 dBm will be considered.
- Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer
level or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations"
on page 386).
- Enter a HO margin in the With a Margin text box. The default value is "4 dB."
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select which TRX type to consider by selecting it from the Reception from Subcells list.
7. Click the Display tab.
For a coverage prediction by transmitter, the Display Type "Discrete Values" based on the Field "Transmitter" is
selected by default. Each coverage zone will then be displayed with the same colour as that defined for each trans-
mitter. For information on defining transmitter colours, see "Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
When you base a coverage prediction by transmitter for highest priority HCS servers, Atoll will consider the best signal
level of the highest priority on each pixel, assuming priority is a combination of the priority field and the minimum threshold
per HCS layer.
To make a coverage prediction by transmitter for highest priority HCS servers:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Transmitter and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 7.20). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow
button ( ) and select one of the following thresholds:
- Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception
threshold specified for each subcell (including the defined power reduction) as the lower end of the signal
level range.
- Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold
to be used for all subcells as the lower end of the signal level range.
In Figure 7.20, a Specified Reception Threshold less than or equal to -105 dBm will be considered.
- Under Server, select "Highest priority HCS server" to take the best signal level of all the severs on the highest
priority HCS layer into consideration, assuming the priority of the layer is defined by its priority field and its
signal level exceeds the minimum HCS threshold defined either at the HCS layer level or specifically for each
transmitter (for more information, see "Comparing Service Areas in Calculations" on page 386).
- Enter a hand-over margin in the With a Margin text box. The default value is "4 dB."
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select which TRX type to consider by selecting it from the Reception from Subcells list.
7. Click the Display tab.
For a coverage prediction by transmitter, the Display Type "Discrete Values" based on the Field "Transmitter" is
selected by default. Each coverage zone will then be displayed with the same colour as that defined for each trans-
mitter. For information on defining transmitter colours, see "Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Making a Coverage Prediction by Transmitter Based on the Best Idle Mode Reselection Criterion
(C2)
When you base a coverage prediction by transmitter on the best C2, Atoll will consider the best signal level in idle mode.
Such type of coverage can be used:
to compare idle and dedicated mode best servers for voice traffic
to display the GPRS/EDGE best server (based on the GSM idle mode)
The path loss criterion C1 used for cell selection and reselection is defined by:
C1 = Reception level - Reception Threshold
The path loss criterion (GSM03.22) is satisfied if C1>0. The reselection criterion C2 is used for cell reselection only and is
defined by:
C2= C1+ Cell Reselect Offset
To make a coverage prediction by transmitter based on the best signal level:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Transmitter and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 7.21). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow
button ( ) and select one of the following thresholds:
- Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception
threshold specified for each subcell (including the defined power reduction) as the lower end of the signal
level range.
- Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold
to be used for all subcells as the lower end of the signal level range.
In Figure 7.21, a Specified Reception Threshold less than or equal to -105 dBm will be considered.
- Under Server, select "Best Idle Mode Reselection Criterion (C2)" to consider the best C2 from all servers.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select which TRX type to consider by selecting it from the Reception from Subcells list.
Figure 7.21: Condition settings for a coverage prediction by transmitter based on Best C2
9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
6. Click the Condition tab (see Figure 7.22). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered. You can click the arrow
button ( ) and select one of the following thresholds:
- Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception
threshold specified for each subcell (including the defined power reduction) as the lower end of the signal
level range.
- Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold
to be used for all subcells as the lower end of the signal level range.
In Figure 7.22, a Specified Reception Threshold less than or equal to -105 dBm will be considered.
- Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming the signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer
level or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations"
on page 386).
- Enter a HO margin in the With a Margin text box. The default value is "4 dB."
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select which TRX type to consider by selecting it from the Reception from Subcells list.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Note: By changing the parameters selected on the Condition tab and by selecting different
results to be displayed on the Display tab, you can calculate and display information other
than that which has been explained in the preceding sections.
1. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
2. At the bottom of the Point Analysis Tool window, click the Reception tab (see Figure 7.24).
The predicted signal level from different transmitters is reported in the Reception tab in the form of a bar chart,
from the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the
colour of the transmitter it represents. In the map window, arrows from the pointer to each transmitter are displayed
in the colour of the transmitters they represent. A thick black line from the pointer to its best server is also displayed
in the map window. The best server of the pointer is the transmitter from which the pointer receives the highest
signal level. If you let the pointer rest, the signal level received from the corresponding transmitter at the pointer
location is displayed in the tooltip.
At the top of the Reception tab, you can select the Subcell and the HCS Layer to be analysed. If you select nothing
from the HCS Layer list, the signals from all HCS layers will be studied.
3. Right-click the Reception tab and select Properties from the context menu. The Analysis Properties dialogue
appears.
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and
select "From Model" from the Shadowing Margin list.
- Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class.
7.2.10.7.4 Creating a Focus or Hot Spot Zone for a Coverage Prediction Report
The focus and hot spot zones define an area on which statistics can be drawn and on which reports are made. While you
can only have one focus zone, you can define several hot spot zones in addition to the focus zone. Focus and hot spot
zones are taken into account whether or not they are visible.
It is important not to confuse the computation zone and the focus and hot spot zones. The computation zone defines the
area where Atoll computes path loss matrices, coverage studies, etc., while the focus and hot spot zones are the areas
taken into consideration when generating reports and results. When you create a coverage prediction report, it gives the
results for the focus zone and for each of the defined hot spot zones.
To define a focus zone or hot spot zone:
1. Click the Geo tab in the Explorer window.
2. Click the Expand button ( ) to expand the Zones folder.
3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or
a hot spot. The context menu appears.
4. Select Draw from the context menu.
5. Draw the focus or hot spot zone:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zones
visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but
will still be taken into account.
Note: You can only create a focus zone, and not a hot spot zone, from an existing polygon.
Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus
Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot
spot zones, you can import the name given to each zone as well.
Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map
Window from the context menu.
Once you have created a focus or hot spot zone, you can use Atolls polygon editing tools to edit it. For more information
on the polygon editing tools, see "Using Polygon Zone Editing Tools" on page 44.
Note: You can save the focus or hot spot zones so that you can use them in a different Atoll
document:
- You can save the focus zone in the user configuration. For information on exporting the
focus zone in the user configuration, see "Exporting a User Configuration" on page 75.
- You can right-click the Focus Zone folder or the Hot Spot Zones folder on the Data
tab of the Explorer window and select Export from the context menu.
You can include population statistics in the focus or hot spot zone by importing a
population map. For information on importing maps, see "Importing a Raster-format Geo
Data File" on page 107.
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
a. Under Configuration, click the Import button. The Open dialogue appears.
b. Select the configuration you want to import and click Open. The imported report configuration is applied
6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed
dialogue. The coverage prediction report table appears. The report is based on the hot spot zones and on the
focus zone if available or on the hot spot zones and computation zone if there is no focus zone.
To display a report on all coverage predictions:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
a. Under Configuration, click the Import button. The Open dialogue appears.
b. Select the configuration you want to import and click Open. The imported report configuration is applied
5. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed
dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in
the same order as in the Predictions folder. The report is based on the focus zone if available or on the calculation
zone if there is no focus zone.
You can include population statistics in the focus zone or hot spot zone by importing a population map. For information on
importing maps, see "Importing a Raster-format Geo Data File" on page 107. Normally, Atoll takes all geo data into
consideration, whether it is displayed or not. However, for the population statistics to be used in a report, the population
map has to be displayed.
To include population statistics in the focus zone or hot spot zone:
1. Ensure that the population geo data is visible. For information on displaying geo data, see "Displaying or Hiding
Objects on the Map Using the Explorer" on page 28.
2. Display the report as explained above.
3. Select Format > Display Columns. The Columns to Be Displayed dialogue appears.
4. Select the following columns, where "Population" is the name of the folder on the Geo tab containing the popula-
tion map:
- "Population" (Population): The number of inhabitants covered.
- "Population" (% Population): The percentage of inhabitants covered.
- "Population" (Population [total]): The total number of inhabitants inside the zone.
Note: Depending on display settings, you can create a report showing population thresholds, as
well.
Atoll saves the names of the columns you select and will automatically select them the next time you create a
coverage prediction report.
5. Click OK.
If you have created a custom data map with integrable data, the data can be used in prediction reports. The data will be
summed over the coverage area for each item in the report (for example, by transmitter or threshold). The data can be
value data (revenue, number of customers, etc.) or density data (revenue/km, number of customer/km, etc.). Data is
considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example,
socio-demographic classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable
Versus Non Integrable Data" on page 124.
6. Compare the original coverage prediction with the new coverage prediction. Atoll displays differences in coverage
between them.
In this section, the following examples are explained:
"Example 1: Studying the Effect of a New Base Station" on page 291
"Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 293.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how you can verify if a newly added base station improves coverage.
A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal
Level" on page 278. The results are displayed in Figure 7.26. An area with poor coverage is visible on the right side of the
figure.
A new base station is added, either by creating the site and adding the transmitters, as explained in "Creating a GSM/
GPRS/EDGE Base Station" on page 246, or by placing a station template, as explained in "Placing a New Station Using
a Station Template" on page 256. Once the new site base station been added, the original coverage prediction can be
recalculated, but then it will be impossible to compare the two predictions. Instead, the original signal level coverage
prediction can be copied by selecting Duplicate from its context menu. The copy is then calculated to show the effect of
the new site (see Figure 7.27).
Figure 7.27: Signal level coverage prediction of network with new base station
4. Click the Display tab. On the Display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes adding a new base station made, you should choose Difference.
5. Click OK to create the comparison. The comparison in Figure 7.28, shows clearly the area covered only by the
new base station.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how modifying transmitter tilt can improve coverage.
A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by
Transmitter" on page 280. The results are displayed in Figure 7.29. The coverage prediction shows that one transmitter is
covering its area poorly. The area is indicated with a red oval in the figure.
[
Figure 7.29: Coverage prediction by transmitter of existing network
You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed
by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and
electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue.
Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it will be
impossible to compare the two predictions. Instead, the original coverage prediction by can be copied by selecting Dupli-
cate from its context menu. The copy is then calculated to show how modifying the antenna tilt has affected coverage (see
Figure 7.30).
[
Figure 7.30: Coverage prediction by transmitter of network after modifications
As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change
in propagation, you can compare the two predictions.
To compare two predictions:
1. Right-click one of the two predictions. The context menu appears.
2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you
want to compare with the first. The Comparison Properties dialogue appears.
3. Click the General tab. You can change the Name of the comparison and add Comments.
The General tab contains information about the coverage predictions being compared, including their name and
resolution.
4. Click the Display tab. On the Display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes modifying the antenna tilt made, you can choose Union. This will display all pixels
covered by both predictions in one colour and all pixels covered by only one predictions in another colour. The
increase in coverage, seen in only the second coverage prediction, will be immediately clear.
5. Click OK to create the comparison. The comparison in Figure 7.31, shows clearly the increase in coverage due to
the change in antenna tilt.
[
Figure 7.31: Comparison of both transmitter coverage predictions
7. Under Exceptional Pairs, create a new exceptional pair in the row marked with the New Row icon ( ):
a. Select the transmitter from the list in the Neighbours column.
b. In the Status column, select one of the following:
- Forced: The selected cell will always be a neighbour of the reference cell.
- Forbidden: The selected cell will never be a neighbour of the reference cell.
8. Click elsewhere in the table when you have finished creating the new exceptional pair.
9. Click OK.
Notes: You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology
Neighbours table. You can open this table by right-clicking the Transmitters folder and
selecting Neighbours > Intra-Technology Exceptional Pairs.
- Min. BCCH Signal Level: Enter the minimum signal level which must be provided by reference cell A and
possible neighbour cell B.
- Handover Start: Enter the signal level which indicates the beginning of the handover margin. The hando-
ver start must be outside of the best server area of the reference transmitter (see Figure 7.32).
- Handover End: Enter the signal level which indicates the end of the handover margin. The handover end
must exceed the value entered for the Handover Start. The higher the value entered for the Handover
End, the longer the list of candidate neighbours (see Figure 7.32). The area between the Handover Start
and the Handover End constitutes the area in which Atoll will search for neighbours.
- Shadowing Taken into Account: If desired, select the Shadowing Taken into Account check box and
enter a Cell Edge Coverage Probability.
- Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses defined per
clutter class in the calculations.
Handover end
Handover start
candidateB
Best server area
of candidateB
referenceA
Best server area of
referenceA
SA SB
[
Figure 7.32: The handover area between the reference transmitter and the potential candidate
- Resolution: You can enter the resolution used to calculate the coverage areas of transmitters for the auto-
matic neighbour allocation.
- Take into account: You can define whether Atoll selects potential candidates by whose handover zone
shared with the reference transmitter has the greatest surface area or greatest circuit traffic. The importance
of this parameter can be defined in step 6. Select one of the following options:
- Covered Area: If you select Covered Area, Atoll will select the potential candidates whose handover
zone shared with the reference transmitter has the greatest surface area.
- Covered Traffic: If you select Covered Traffic, Atoll will select the potential candidates whose handover
zone shared with the reference transmitter covers the most circuit traffic (Erlangs). Atoll considers the traf-
fic maps used for the default traffic analysis to calculate the covered traffic.
- % Min. Covered Area: Enter, in percentage, the amount of covered area or traffic of the reference trans-
mitters coverage that another transmitter must cover to be considered as a potential candidate. The % Min.
Covered Area is the percentage of the area described by S A S B in Figure 7.32.
- Adjacency Factor: If you have selected the Force adjacent transmitters as neighbours check box in
step 5., set the minimum and maximum importance of a possible neighbour transmitter being adjacent to the
reference transmitter.
- Co-site Factor: If you have selected the Force co-site transmitters as neighbours check box in step 5., set
the minimum and maximum importance of a possible neighbour transmitter being located on the same site as
reference transmitter.
7. Click Run. Atoll begins the process of allocating intra-technology neighbours. Atoll first checks to see whether
the path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalcu-
lates them.
Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays
new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is
cleared, the Results table will be empty.
Notes
A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already
exists and the Delete existing neighbours check box is cleared when you start the new allo-
cation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint
on the forbidden neighbour will be ignored by the algorithm because the neighbour already
exists.
When the options Force exceptional pairs and Force symmetry are selected, Atoll con-
siders the constraints between exceptional pairs in both directions in order to respect sym-
metry. On the other hand, if the neighbour relation is forced in one direction and forbidden in
the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the
Event Viewer.
You can save automatic neighbour allocation parameters in a user configuration. For informa-
tion on saving automatic neighbour allocation parameters in a user configuration, see
"Exporting a User Configuration" on page 75.
1. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
2. Select Display Options from the context menu. The Visual Management dialogue appears.
3. Under Intra-technology Neighbours, select the Display Links check box.
4. Click the Browse button ( ) beside the Display Links check box.
5. The Intra-technology Neighbour Display dialogue appears.
6. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a transmitter
with a unique colour.
- Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you
want Atoll to colour the transmitters neighbour links according to a value from the Intra-technology Neigh-
bours table, or according to the neighbour cell type, the neighbour HCS layer or the neighbour frequency
band.
- Value Intervals: Select "Value Intervals" to colour the transmitters neighbour links according the value
interval of the value selected from the Field list. For example, you can choose to display a transmitters neigh-
bours according to their rank, in terms of automatic allocation, or according to the importance, as determined
by the weighting factors.
Tip: You can display the number of handoff attempts for each transmitter-neighbour pair by
first creating a new field of Type "Integer" in the Intra-Technology Neighbour table for
the number of handoff attempts. Once you have imported or entered the values in the
new column, you can select this field from the Field list along with "Value Intervals" as the
Display Type. For information on adding a new field to a table, see "Adding a Field to an
Object Types Data Table" on page 51.
Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you
can display or hide neighbour link display types individually.
For information on changing display properties, see "Display Properties of Objects" on page 33.
7. Select the Add to Legend check box to add the displayed neighbour links to the legend.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each neighbour link.
9. Click OK to save your settings.
10. Under Advanced, select which neighbour links to display:
- Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations
where the selected transmitter is the reference transmitter and where the neighbour relation is not symmetric.
- Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations
where the selected transmitter is neighbour and where the neighbour relation is not symmetric.
- Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the
selected transmitter and the neighbour.
11. Click OK to save your settings.
12. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
13. Select Neighbours from the menu. The neighbours of a transmitter will be displayed when you select a trans-
mitter.
14. Click a transmitter on the map to display the neighbour relations. When there is more than one transmitter with the
same azimuth on the site, clicking the transmitter in the map window opens a context menu allowing you to select
the transmitter you want (see "Selecting One of Several Transmitters or Microwave Links" on page 30).
Atoll displays the following information (see Figure 7.33) on the selected transmitter:
- The symmetric neighbour relations of the selected (reference) transmitter are indicated by a line.
- The outward neighbour relations are indicated with a line with an arrow pointing at the neighbour (e.g. see
Site1_2(0)) in Figure 7.33.).
- The inward neighbour relations are indicated with a line with an arrow pointing at the selected transmitter
(e.g. see Site9_3(0)) in Figure 7.33.).
In Figure 7.33, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward
neighbour links are coloured as the corresponding neighbour transmitters and the inward neighbour link is
coloured as the reference transmitter as it is neighbour of Site9_3(0) here.
[
Figure 7.33: Neighbours of Site 22
In Figure 7.34, neighbour links are displayed according to the neighbour frequency band. You can view 900-900
and 900-1800 neighbour links. Here, all neighbour relations are symmetric.
Note: You can use the same procedure to display either forced neighbours or forbidden
neighbours by clicking the menu button ( ) of the Visual Management button ( ) in
the Radio toolbar and selecting either Forced Neighbours or Forbidden Neighbours.
2. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
3. Select Display Options from the context menu. The Visual Management dialogue appears.
4. Under Intra-technology Neighbours, select the Display Coverage Areas check box.
5. Click the Browse button ( ) beside the Display Coverage Areas check box.
6. The Intra-technology Neighbour Display dialogue appears.
7. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage areas of a transmitters
neighbours with a unique colour.
- Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you
want Atoll to colour the coverage areas of a transmitters neighbours according to a value from the Intra-tech-
nology Neighbours table.
- Value Intervals: Select "Value Intervals" to colour the coverage areas of a transmitters neighbours according
the value interval of the value selected from the Field list. For example, you can choose to display a trans-
mitters neighbours according to their rank, in terms of automatic allocation, or according to the importance,
as determined by the weighting factors.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each coverage area.
9. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
10. Select Neighbours from the menu. The neighbours of a transmitter will be displayed when you select a trans-
mitter.
13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( ) in the
Radio toolbar.
Allocating or Deleting Neighbours Using the Intra-Technology Neighbours Tab of the Transmitter
Properties Dialogue
To allocate or delete GSM/GPRS/EDGE neighbours using the Intra-Technology Neighbours tab of the transmitters Prop-
erties dialogue:
1. On the map, right-click the transmitter whose neighbours you want to change. The context menu appears.
2. Select Properties from the context menu. The transmitters Properties dialogue appears.
3. Click the Intra-Technology Neighbours tab.
4. If desired, you can enter the maximum number of neighbours in the Max Number of Neighbours text box.
5. To allocate a new neighbour:
a. Under List, select the transmitter from the list in the Neighbour column in the row marked with the New Row
icon ( ).
b. Click elsewhere in the table to complete creating the new neighbour.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
Note: For information on working with data tables, see "Working with Data Tables" on page 50.
4. To allocate a neighbour:
a. In the row marked with the New Row icon ( ), select a reference transmitter in the Transmitter column.
b. Select the neighbour in the Neighbour column.
c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
5. To create a symmetric neighbour relation:
a. Right-click the neighbour in the Neighbour column. The context menu appears.
b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the transmitter
in the Neighbour column and the transmitter in the Transmitter column.
6. To make several neighbour relations symmetric:
a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select
contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contig-
uous rows by pressing CTRL and clicking each rows separately.
b. Right-click the Neighbours table. The context menu appears.
c. Select Symmetrise from the context menu.
7. To take into consideration all exceptionnal pairs:
a. Right-click the Neighbours table. The context menu appears.
b. Select Force Exceptional Pairs from the context menu.
Note: You can add or delete either some forced neighbours or some forbidden neighbours using
the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table,
select the exceptional pairs to be considered, right-click the table and select Force
Exceptional Pairs in the context menu.
c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation be-
tween the transmitter in the Neighbour column and the transmitter in the Transmitter column is deleted.
9. To delete several symmetric neighbour relations:
a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select
contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contig-
uous rows by pressing CTRL and clicking each rows separately.
b. Right-click the Neighbours table. The context menu appears.
c. Select Delete Link and Symmetric Relation from the context menu.
10. To delete a neighbour:
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Press DEL to delete the neighbour.
You can allocate or delete intra-technology neighbours directly on the map using the mouse.
To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neigh-
bours on the map as explained in "Displaying Neighbour Relations on the Map" on page 298.
To add a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters
to the intra-technology neighbours list.
To remove a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both trans-
mitters from the intra-technology neighbours.
To add an outward neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference
transmitter to the intra-technology neighbour list of the reference transmitter.
To remove an outward neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference
transmitter from the intra-technology neighbours list of the reference transmitter.
To add an inward neighbour relation:
Click the reference transmitter on the map. Atoll displays its neighbour relations.
- If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other trans-
mitter. Atoll converts the symmetric relation to an inward non-symmetric inter-technology neighbour relation.
- If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour rela-
tion between the two transmitters, and then press CTRL and click the other transmitter. Atoll converts the
symmetric relation to an inwards non-symmetric inter-technology neighbour relation.
To remove an inwards neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the trans-
mitter from the intra-technology neighbours list of the reference transmitter.
Notes:
When there is more than one transmitter with the same azimuth on a site, clicking the trans-
mitter in the map window opens a context menu allowing you to select the transmitter you want
(see "Selecting One of Several Transmitters or Microwave Links" on page 30).
You can add or delete either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting either
Forced Neighbours or Forbidden Neighbours.
- Take into account the adjacency factor: Select the Take into account the adjacency factor check box
to verify that neighbours are adjacent to their reference transmitters when calculating importance.
- Take into account the co-site factor: Select the Take into account the co-site factor check box to ver-
ify that neighbours are located on the same site as their reference cell when calculating importance.
- Click Weighting to set the relative importance of possible neighbours:
- Coverage Factor: Set the minimum and maximum importance of a neighbour satisfying the coverage
conditions.
- Adjacency Factor: If you have selected the Take into account the adjacency factor check box, set the
minimum and maximum importance of a possible neighbour transmitter being adjacent to the reference
transmitter.
- Co-site Factor: If you have selected the Take into account the co-site factor check box, set the mini-
mum and maximum importance of a possible neighbour transmitter being located on the same site as
reference transmitter.
- Coverage Conditions: Under Coverage Conditions, you can set the coverage conditions between neigh-
bours and their reference cells. Clicking Define opens the Coverage Conditions dialogue. In the Coverage
Conditions dialogue, you can change the following parameters:
- Min. BCCH Signal Level: Enter the minimum signal level which must be provided by the reference trans-
mitter and the neighbour.
- Handover Start: Enter the signal level which indicates the beginning of the handover margin. The hando-
ver start must be outside of the best server area of the reference transmitter (see Figure 7.32).
- Handover End: Enter the signal level which indicates the end of the handover margin. The handover end
must exceed the value entered for the Handover Start (see Figure 7.32). The higher the value entered
for the Handover End, the longer the list of candidate neighbours (see Figure 7.32). The area between
the Handover Start and the Handover End constitutes the area in which Atoll will search for neighbours.
- Shadowing Taken into Account: If desired, select the Shadowing Taken into Account check box and
enter a Cell Edge Coverage Probability.
- Take into account: You can select whether Atoll defines the importance of neighbours by the size of the
handover zone shared with the reference transmitter or by the amount of circuit traffic. Select one of the fol-
lowing options:
- Covered Area: If you select Covered Area, Atoll defines importance according to the size of the hand-
over zone shared with the reference transmitter
- Covered Traffic: If you select Covered Traffic, Atoll defines importance according to the amount of
circuit traffic (in Erlangs).
- Resolution: You can enter the resolution used to calculate the coverage areas of transmitters for the calcua-
tion of neighbour importance values.
Atoll indicates the number of neighbours to be calculated and displays the neighbours with their initial attributes
(importance and reason) in a table.
Notes: You can use many of Atolls table shortcuts, such as filtering and sorting. For information
on working with data tables, see "Working with Data Tables" on page 50. In addition, by
clicking Filter, you can define advanced filtering conditions to restrict the neighbours to be
calculated.
5. Click Run. Atoll begins the process of calculating the importance of the neighbours displayed in the table. Atoll
first checks to see whether the path loss matrices are valid before calculating the importance. If the path loss
matrices are not valid, Atoll recalculates them.
Once Atoll has finished calculating importance, the results are displayed in the table.
- Coverage
- Coverage: The amount of reference transmitters coverage area that the neighbour overlaps, in percentage
and in square kilometres.
- Adjacency: The area of the reference transmitter, in percentage and in square kilometres, where the neigh-
bour transmitter is best server or second best server.
The importance values and the reasons for allocation are automatically committed in the Neighbours table when
you close the dialogue.
Note: If the field Maximum number of neighbours in the Transmitters table is empty, the Full
Lists check and the Lists > Max Number check use the Default Max. Number value
defined in the audit dialogue.
- Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan.
Syntax: |TRANSMITTER| |NEIGHBOUR|
- Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan.
Syntax: |TRANSMITTER| |NEIGHBOUR| |TYPE| |REASON|
- Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan.
Syntax: |TRANSMITTER| |NEIGHBOUR|
- Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan.
Syntax: |TRANSMITTER| |NEIGHBOUR| |TYPE| |REASON|
over the best server coverage area of each transmitter and each coverage area is assigned either Erlangs for
circuit-switched services and kBps for packet-switched services. For more information, see "Creating a Traffic Map
per Sector" on page 306.
Traffic map per user profile can be used if you have marketing-based traffic data.
Traffic maps per density of user profiles, where each vector (polygon, line or point) describes subscriber densities
(or numbers of subscribers for points) with user profiles and mobility types, and traffic maps per environment of
user profiles, where each pixel has an assigned environment class. For more information, see "Importing a Traffic
Map Based on Densities of User Profiles" on page 308, "Importing a Traffic Map Based on Environments of User
Profiles" on page 310, and "Creating a Traffic Map Based on Environments of User Profiles" on page 310.
Traffic maps per density (number of users per km2) can be used if you have population-based traffic data,
or 2G network statistics.
Each pixel has an actual user density assigned. Either the value includes all activity statuses, or it corresponds to
a particular activity status. For more information, see "Importing a Traffic Map per User Density" on page 311,
"Creating a Traffic Map per per User Density" on page 311, "Converting 2G Network Traffic" on page 312 and
"Exporting Cumulated Traffic" on page 312.
Note: You can also import a traffic map from a file by clicking the Import button. You can import
AGD (Atoll Geographic Data) format files that you have exported from an other Atoll
document.
6. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter.
7. In the row marked with the New Row icon ( ), select the name of the transmitter from the TX_ID list.
8. For the transmitter in the TX_ID column, enter the throughput for each service in the appropriate column:
- For packet services, enter the throughput in kbps.
- For circuit services (voice), enter value in Erlangs.
Note: You can also import a text file containing the data by clicking the Actions button and
selecting Import Table from the menu. For more information on importing table data, see
"Importing Tables from Text Files" on page 59.
4. Select Update from the context menu. The Map per Sector dialogue appears.
Select the updated coverage prediction by transmitter and define traffic values for the new transmitter(s) listed at
the bottom of the table. Deleted or deactivated transmitters are automatically removed from the table.
You can model variations in user behaviour by creating different profiles for different times of the day or for different circum-
stances. For example, a user may be considered a business user during the day, with video conferencing and voice, but
no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and
web browsing.
To create a user profile:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the GSM/GPRS/EDGE Parameters folder.
3. Right-click the User Profiles folder. The context menu appears.
4. Select New from the context menu. The User Profiles New Element Properties dialogue appears.
Note: You can modify the properties of an existing user profile by right-clicking the user profile in
the User Profiles folder and selecting Properties from the context menu.
Note: In order for all the services defined for a user profile to be taken into account during traffic
scenario elaboration, the sum of activity probabilities must be lower than 1.
- Duration: For circuit-switched services, enter the average duration of a call in seconds. For packet-switched
services, this field is left blank.
- DL Volume: For packet-switched services, enter the average downlink volume per session in kilobytes.
Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a
given density (i.e., the number of subscribers with the same profile per km). To get an appropriate user distribution, you
can assign a weight to each clutter class for each environment class.
To create or modify a GSM/GPRS/EDGE environment:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the GSM/GPRS/EDGE Parameters folder.
3. Right-click the Environments folder. The context menu appears.
4. Select New from the context menu. The Environments New Element Properties dialogue appears.
Note: You can modify the properties of an existing environment by right-clicking the
environment in the Environments folder and selecting Properties from the context
menu.
7. In the row marked with the New Row icon ( ), set the following parameters for each user profile/mobility com-
bination that this GSM/GPRS/EDGE environment will describe:
- User: Select a user profile.
- Mobility: Select a mobility type.
- Density (Subscribers/km2): Enter a density in terms of subscribers per square kilometre for the combination
of user profile and mobility type.
8. Click the Clutter Weighting tab.
9. For each clutter class, enter a weight that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk Sk
N k = N Area --------------------------
Wi Si
i
where:
For example: An area of 10 km with a subscriber density of 100/km. Therefore, in this area, there are 1000
subscribers. The area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1"
and for Building is "4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter
class and 800 in the Building clutter class.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 310.
- User Profile: If you want to import user profile information from the file, under Defined, select "By field" and
select the source field from the Choice column. If you want to assign a user profile from the GSM/GPRS/
EDGE Parameters folder of the Data tab, under Defined, select "By value" and select the user profile in the
Choice column.
- Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select
the source field from the Choice column. If you want to assign a mobility type from the GSM/GPRS/EDGE
Parameters folder of the Data tab, under Defined, select "By value" and select the mobility type in the Choice
column.
- Density: If you want to import density information from the file, under Defined, select "By field" and select the
source field from the Choice column. If you want to assign a density, under Defined, select "By value" and
enter a density in the Choice column for the combination of user profile and mobility type. In this context, the
term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kil-
ometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers
when the map consists of points.
Important: When you import user profile or mobility information from the file, the values in the file
must be exactly the same as the corresponding names in the GSM/GPRS/EDGE
Parameters folder of the Data tab. If the imported user profile or mobility does not match,
Atoll will display a warning.
12. Under Clutter Distribution, enter a weight for each class that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk Sk
N k = N Area --------------------------
Wi Si
i
where:
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 310.
7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, BIL, IST,
BMP, PlaNET, GRC Vertical Mapper, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic maps Properties dialogue appears.
11. Select the Description tab.
In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the
Code column.
12. For each Code, select the environment it corresponds to from the Name column.
The environments available are those available in the Environments folder, under GSM/GPRS/EDGE Parame-
ters on the Data tab of the Explorer window. For more information, see "Modelling Environments" on page 308.
13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects"
on page 33.
7. Select the environment class from the list of available environment classes.
8. Click the Draw Polygon button ( ) to draw the polygon on the map for the selected environment class.
9. Click the Delete Polygon button ( ) and click the polygon to delete the environment class polygon on the map.
10. Click the Close button to close the Environment Map Editor toolbar and end editing.
5. Click Close.
If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per
clutter class.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 310.
6. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP,
PlaNET, TIF, ISTAR, and Erdas Imagine.
7. Click Open. The File Import dialogue appears.
8. Select Traffic from the Data Type list.
9. Click Import. Atoll imports the traffic map. The traffic maps Properties dialogue appears.
10. Select the Traffic tab.
11. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must
equal 100.
12. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must
equal 100.
13. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal
100.
14. Click OK. Atoll creates the traffic map in the Traffic folder.
3. Select New Map from the context menu. The New Traffic Map dialogue appears.
16. In the table, enter a traffic density value (i.e. the number of users per km2) for each contour you have drawn.
17. Right-click the item. The context menu appears.
18. Select Edit from the context menu to end editing.
Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains
at "0" and no data will be exported.
8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic
data to be exported.
- Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal.
- Service: Select the service that will be exported, or select "Circuit services" to export traffic using any circuit
service, or select "Packet services" to export traffic using any packet service.
- Mobility: Select the mobility type that will be exported or select "All" to export all mobility types.
9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the
cumulated traffic.
10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.
- Select Traffic Maps to Be Used: Select the traffic maps you want to use for the traffic capture. You must
select at least one traffic map.
You can select traffic maps of any type. However, if you have several different types of traffic maps and want
to make a traffic capture on a specific type of traffic map, you must ensure that you select only traffic maps of
the same type. For information on the types of traffic maps, see "Creating a Traffic Map" on page 305.
6. Click the Condition tab. The parameters on the Condition tab define how the service zone for each transmitter and
the number of time slots for circuit and packet services will be calculated.
7. Under Coverage Conditions, set the following parameters to define how the service area of each transmitter will
be calculated:
- Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer
level or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations"
on page 386).
- Enter a hand-over margin in the With a Margin text box. The default value is "4 dB."
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability. Shadowing margins (depending on the entered cell edge coverage probability and the model standard
deviation per clutter class) are applied to the values for C.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
Note: If shadowing is taken into account, the CI standard deviation per clutter class is used to
estimate the shadowing losses on the calculated CI values.
8. Under GPRS/EDGE, you can set the parameters to define how the number of time slots for circuit and packet serv-
ices will be calculated. Select one of the following to define how the calculations in the traffic capture are going to
be made:
- Select Calculations Based on C if you want to base the traffic capture on CN. Continue to step 14.
- Select Calculations Based on CI and continue with the following step.
9. Select the DTX taken into account check box and enter the percentage of time during which a user is talking in
the Voice Activity Factor text box, if you want discontinuous transmission mode for TRXs which support it taken
into account.
10. Select in the Interference Sources scrolling box whether the interference should be calculated from adjacent chan-
nels, co-channels, or from both. The adjacent channel effect on the concerned victim channel, i.e., the interfer-
ence, is decreased by the adjacent channel protection level.
You may even select interferences coming from an external project using another technology. For more informa-
tion, see "GSM/GPRS/EGPRS Interfered networks" on page 239.
If you want Atoll to take interference due to intra-technology third order intermodulation into consideration when
calculating the total interference, you must set up your document and database as explained in "Taking Intermod-
ulation Interference into Consideration in Calculations" on page 407.
11. Select the Traffic Load that will be used to calculate interference:
- 100 %: The maximum traffic load (subcells entirely loaded).
- From subcell table: The subcell traffic load as user-defined or as calculated during dimensioning.
12. Select the Ideal Link Adaptation check box if you want the coding scheme that offers the highest throughput for
a given C or CI to be selected. Otherwise, Atoll will choose the coding scheme by considering only the coding
scheme admission threshold in terms of C and/or CI.
13. Select the Thermal Noise Taken into Account check box if you want Atoll to consider thermal noise.
- Average demand (Timeslots): The average number of timeslots needed to match the demand in circuit-
switched and packet-switched traffic.
The demand in packet timeslots depends on the maximum throughput that a timeslot can support. Therefore,
it depends on the average timeslot capacity within the transmitter coverage area, which in turn depends on
the propagation conditions.
For more information on how the results are calculated and on the formulas used, see the Technical Reference Guide.
Caution: The traffic capture is deleted immediately; there is no opportunity to confirm or cancel the
action.
- Queuing Model: Enter the queuing model for GSM voice calls (Erlang B or Erlang C).
Under Packet:
- Min. number of packet-dedicated timeslots per transmitter: Enter the minimum number of dedicated
packet-switched timeslots that must be reserved for each transmitter.
- Max. number of additional TRXs for packet services: Enter the maximum number of TRXs that can be
added for the subcell to satisfy the demand for packet-switched services after Atoll has dimensioned the cir-
cuit-switched services.
- KPIs to Take into Account: Select the key performance indicators you want taken into account during dimen-
sioning. The values of the key performance indicators are defined by the quality graphs on the Quality Graphs
tab of the dimensioning model Properties dialogue.
- Min. Throughput: Select the Min. Throughput check box if you want to take minimum required through-
put into account when performing dimensioning.
From the point of view of a GPRS/EDGE user, throughput is the average maximum throughput experi-
enced by the mobile terminal during a data call. If there is more than one user multiplexed on the same
timeslot, which occurs when the system accommodates many users, each multiplexed user will experi-
ence a reduction in throughput. This reduction in throughput is described by the reduction factor defined
in the reduction factor graph. A reduction factor of 1, or almost 1, means that each user has the maximum
throughput that a timeslot can offer in a given environment (the maximum throughput per timeslot, in turn,
depends on the carrier power and/or CI ratio at a given location). As the system load increases, the re-
duction factor starts decreasing, corresponding to the decrease in throughput per user.
- Max. Blocking Rate: Select the Max. Blocking Rate check box if you want to take blocking probability
into account when performing dimensioning.
The blocking probability and the delay in the GPRS/EDGE system are closely related. A user starts to ex-
perience more delay in service when the system is near saturation and the incoming packets are placed
in a waiting queue as there are no resources available for immediate transfer. This buffering of packets is
related to the load of the system. The blocking probability is the probability that an incoming packet be
placed in a queue. The delay is the average delay the packet will undergo due to blocking as it waits its
turn to be transmitted when resources are available.
Note: In GPRS and EDGE, the term "system load" refers to the ratio of the number of used
packet timeslots to the number of packet switching (shared and dedicated) timeslots
available in the system.
- Max. Delay: Select the Max. Delay check box if you want to take delay into account when performing
dimensioning.
The delay is the average delay the packet will undergo due to blocking as it waits its turn to be transmitted
when resources are available.
The delay can be restricted to an allowed maximum in the properties of the service.
Note: If the dimensioning model takes into account all three KPIs, the following conditions are
satisfied when the number of TRXs to add for packet service is calculated:
- The throughput must be greater than the minimum throughput even if a reduction factor
is applied to the throughput.
- The delay and the blocking rate must be lower than the maximum delay and maximum
blocking rate, respectively.
4. Click the Quality Charts tab. The Quality Charts tab displays the throughput reduction factor, delay, and blocking
probability graphs used for dimensioning packet switched traffic. The graphs are calculated as a function of the
system load, which is defined as the ratio of the number of used packet timeslots to the number of packet switching
(shared and dedicated) timeslots available in the system.
You can modify or replace the quality graphs with graphs generating using a third-party simulator.
Caution: If the quality graphs are modified incorrectly, the dimensioning and quality analysis
results that are based on the quality graphs will also be incorrect.
Notes
For the moment, Atoll does not provide a default delay graph; if desired, you can enter your
own values.
The blocking rate graph is based on a user multiplexing factor of 8. The user multiplexing factor
corresponds to the number of timeslots on a GSM/GPRS/EDGE frame.
5. Click OK.
Note: If you have modified the traffic map, traffic parameters, or transmitter properties (e.g.,
calculation area, Coding Scheme Configuration, etc.), since creating the traffic capture,
you must recalculate the traffic capture before dimensioning.
A dimensioning model (for information on creating a or modifying a dimensioning model, see "Defining a GSM/
GPRS/EDGE Dimensioning Model" on page 316).
To dimension a GSM/GPRS/EDGE network:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the Traffic Analysis folder.
3. Right-click the Traffic Capture on which you want to base the dimensioning. The context menu appears.
4. Select Dimensioning from the context menu. The Dimensioning dialogue appears (see Figure 7.37).
5. Under Dimensioning Parameters, select the dimensioning model from the Model list.
6. Click Calculate to dimension the network.
The output of the dimensioning appears in the Dimensioning dialogue, under Results. Some columns are hidden
by default. You can select which columns to display by clicking the Displayed Columns button and selecting or
clearing the check box of the columns. The following results are given for each transmitter in the Transmitter
column:
- TRX Type: For each transmitter, the results are given by TRX type (e.g., BCCH, TCH, TCH_EGPRS and
TCH_INNER). Together, the Transmitter and TRX Type columns identify the subcell.
- Required Number of TRXs: The number of TRXs required to satisfy both the subcell's circuit-switched and
packet-switched traffic, while taking into account the quality of service criterion assigned for each.
The required number of TRXs is the most important result of the dimensioning process. If the number of re-
quired TRXs exceeds the maximum number of TRXs per transmitter, Atoll displays the results for the subcell
in red.
- Load (%): The average demand in timeslots (packet and circuit), divided by the total number of timeslots avail-
able. It represents the average occupancy of the TRXs. This parameter is one of the principal results of dimen-
sioning along with the number of TRXs. It is assigned to subcell pools when committing the results of
dimensioning.
- Multiplexing Factor: The user or Temporary Block Flow (TBF) multiplexing factor. The multiplexing factor is
an input of the dimensioning process. It corresponds to the number of packet switched service users that can
be multiplexed onto the same timeslot in GPRS and EDGE.
- Maximum Number of TRXs per Transmitter: The maximum number of TRXs that a transmitter can support
is an input of the dimensioning process. This parameter is provided by the equipment manufacturer. The value
can be set for each transmitter or taken from the dimensioning model for transmitters where this value is not
set.
- Target Rate of Traffic Overflow (%): This input parameter defines the percentage of traffic that is allowed to
overflow from one subcell to another in case the traffic assigned to this subcell is greater than the maximum
traffic that it can accommodate. It can be considered an anticipation of the percentage of traffic that will be
rejected from higher priority subcells or layers to lower ones. The value is specified for each subcell.
- Half-rate Traffic Ratio (%): This input parameter is defined per subcell and indicates the percentage of sub-
cell traffic that uses half-rate access.
If the values are different for BCCH and TCH subcells, Atoll will use the values for the target rate of traffic
overflow and the half-rate traffic ratio from the BCCH subcell.
- Packet demand (kbps): The Packet Traffic Demand is the total traffic demand in kilobits per second gener-
ated by packet switched service users within the coverage area of the transmitter. This parameter comes from
the traffic capture. It is assigned to subcell pools when committing the results of dimensioning.
- Packet average demand (Timeslots): The number of timeslots needed to satisfy the packet traffic demand
depends on the maximum throughput that a packet timeslot can support.
- Circuit Demand (Erlangs): The Circuit Traffic Demand is the total traffic demand in Erlangs generated by
circuit-switched-service users within the coverage area of the transmitter. This parameter comes from the
traffic capture. It is assigned to subcell pools when committing the results of dimensioning.
Note: For concentric cell types, the traffic demand on TCH subcells is different from the one
calculated during the traffic capture. For concentric cell types, the traffic demand on TCH
subcells is calculated from the traffic demand of the capture and the effective rate of traffic
overflow.
- Circuit average demand (Timeslots): The Average Demand in Circuit Timeslots is calculated taking into
account the effect of half-rate circuit-switched traffic: two half-rate users are equivalent to one full-rate user.
- Served Circuit Traffic (Erlangs): The Served Circuit Traffic is the circuit-switched traffic in Erlangs that the
subcell can potentially serve, if the dimensioning results are applied. The served circuit-switched traffic is cir-
cuit traffic demand less the effective overflowed circuit traffic.
- Served Packet Traffic (kbps): The Served Packet Traffic is the packet-switched traffic in kilobits per second
that the subcell can potentially serve, if the dimensioning results are applied. The served packet-switched
traffic is packet traffic demand less the effective overflowed packet traffic.
- Effective Rate of Traffic Overflow (%): The Effective Rate of Traffic Overflow is the actual rate of traffic
that is rejected by the subcell and overflows because of a lack of packet timeslots. In a GSM network, the value
is the same as the blocking probability. In a more complex network, this value includes the traffic overflow from
all services.
For Erlang B, the effective rate of traffic overflow corresponds to the effective blocking rate. This value is cal-
culated from the required number of circuit timeslots (both shared and circuit timeslots) and the circuit traffic
demand in Erlang B tables.
For Erlang C, the effective rate of traffic overflow is zero except if the maximum number of TRXs is exceeded.
The effective blocking rate is inferred from the required number of circuit timeslots (both shared and circuit
timeslots) and the circuit traffic demand in Erlang C tables.
- Circuit Blocking Rate (/Delay) (%): The Circuit Blocking Rate is the grade of service (GoS) indicator for
circuit-switched traffic. It can be either the rate at which calls are blocked (Erlang B) or delayed (Erlang C),
depending on which queuing model the dimensioning model uses.
- Minimum Throughput Reduction Factor (%): The Minimum Throughput Reduction Factor is the lowest
throughput reduction factor that can still guarantee service availability. The Minimum Throughput Reduction
Factor is one of the criteria for packet-switched traffic dimensioning. It is calculated using the parameters
defined for the services: the minimum service throughput; the maximum number of timeslots per connection;
the required availability; and the per pixel timeslot capacity of the subcell coverage area. This parameter is
calculated when making the traffic capture on which the dimensioning is based.
- Throughput Reduction Factor (%): The Throughput Reduction Factor is calculated from the quality charts
using the packet load and available connections for each subcell. This reduction factor must be greater than
the minimum throughput reduction factor for packet-switched services for these services to be satisfactorily
available in the subcell.
- Maximum Delay (s): The Maximum Delay is the defined delay in seconds that must not be exceeded for the
service quality to be considered satisfactory.
- Delay (s): The Delay is a key performance indicator (KPI) calculated using the quality graphs, the load, and
the number of connections available . This dimensioning output must not exceed the maximum delay defined
for the service for service availability to be considered satisfactory.
- Maximum Packet Blocking Rate (/Delay) (%): The Maximum Packet Blocking Rate is defined for each
packet service and is the highest probability that the service will be blocked that is acceptable in terms of
service availability.
- Packet Blocking Rate (Delay) (%): The Packet Blocking Rate is a dimensioning output and must not
exceed the Maximum Packet Blocking Rate defined for the service for service availability to be considered
satisfactory.
Note: You can also access a transmitters Properties dialogue by right-clicking the transmitter
in the map window and selecting Properties from the context menu.
6. Under Identification, select the BSIC Domain from the list. You can click the Browse button ( ) to access the
properties of the selected BSIC domain.
7. Click OK.
Note: You can also access a transmitters Properties dialogue by right-clicking the transmitter
in the map window and selecting Properties from the context menu.
Note: You can enter a value in the BSIC field, however, it must be a BSIC that is part of the
selected BSIC Domain and in the correct BSIC format (for information on the BSIC
format, see "Defining the BSIC Format" on page 384). As well, you can enter a BSIC in
the format of a NCC-BCC. When you click OK or Apply, Atoll will convert it into the
single-digit BSIC format.
7. Click OK.
Note: You can also access a transmitters Properties dialogue by right-clicking the transmitter
in the map window and selecting Properties from the context menu.
5. Select the TRXs tab. Under Subcell (TRX Groups) Settings, the table lists each TRX group defined in the cell
type selected under Cell Type on the TRXs tab.
6. Select a Frequency Domain from the list. Only channels belonging to this frequency domain will be allocated to
TRXs of this group during automatic or manual frequency planning.
Note: The frequency domains assigned to the BCCH subcell and to the TCH subcell must
reference the same frequency band. If the transmitter has more than one subcell with the
TRX type TCH, only one must reference the same frequency band as the BCCH subcell.
7. If desired, add Excluded Channels. The defined frequency domain may have, as part of its definition, a list of
excluded channels. Addition excluded channels for this subcell can be added in the Excluded Channels column.
8. Click OK.
Note: If you are defining frequency domains for several transmitters, you can group them by
frequency band (for information on grouping transmitters, see "Grouping Data Objects" on
page 65) and then open the Transmitters table for the selected transmitters and assign
the frequency domain to all transmitters at the same time. For information on working with
data tables, see "Working with Data Tables" on page 50.
Note: If you want to import the BSIC at the same time, you can also import the frequency list into
the Transmitters table, which you can open by right-clicking the Transmitters folder and
selecting Open Table from the context menu.
If you are modifying the frequency list of a single transmitter, it is easier to modify the
information directly on the TRXs tab of the transmitters Properties dialogue. For
information, see "Subcell Definition" on page 250.
To add TRXs using the TRXs tab of the transmitter Properties dialogue:
1. In the map window, select the transmitter to which you want to add a TRX.
Note: You can also select the transmitter in the Transmitters folder on the Data tab of the
Explorer window.
5. Under TRXs, in the row marked with the New Row icon ( ), enter the parameters described in "TRX Definition"
on page 253.
6. Click OK.
If you are adding TRXs to several transmitters, it is easier to use the TRX table.
To add TRXs using the TRX table:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Subcells > TRXs from the context menu. The TRXs table appears.
4. Scroll down to the row marked with the New Row icon ( ).
5. In the Transmitter column, select the transmitter to which the TRXs will be added.
6. Enter the parameters described in "TRX Definition" on page 253.
will be calculated without taking interference into consideration, i.e., without considering one of the two important
constraints.
In this section, the following are explained:
"Prerequisites for an Automatic Frequency Allocation" on page 324
"Interference Matrices" on page 324
"Defining Required Channel Separations" on page 331
"Automatic Frequency Allocation" on page 334
"Interactive Frequency Allocation" on page 345.
Note: The mean power control gains are not taken into account when calculating interference
matrices. They are only applied when interference matrices are read in order to be used in
calculations (IFP, AFP, etc.). If the mean power control gain of a subcell is G PC , the gain
G PC 10
applied to the interference cost of this subcell will be f 10 . Where f is a
multiplicative factor that depends on the frequency hopping mode used. f = 1 3 in case
of no frequency hopping, and f = 1 3 + Min ( 0.02 L V L I, 2 3 ) with hopping. L V and
L I are the lengths of the MALs used by the interfered and interfering subcells
respectively.
In this example, Tx1 (BCCH) and Tx2 (BCCH) are the victim and interferer subcells, respectively. The service areas have
been defined with a best server of 0 dB margin and the interference probability is stated as a percentage of the interfered
area.
In Figure 7.38, you can see that the probability of CI (BCCH of Tx2 on the BCCH of Tx1 ) being greater than 0 is 100%
(which is normal because Tx1 is best server ). The probability of having a value of CI of at least equal to 31 is 31.1%. If
the required CI level on the BCCH of Tx1 is 12, the percentage of areas in the service area of the BCCH of Tx1 interfered
by the BCCH of TX2 is 6.5%, because the probability that the CI is at least equal to 12 is 93.5%.
Figure 7.38: The probability of having at least the given C/I level for a pair of subcells
Note: When you calculate an interference matrix, Atoll calculates it on all transmitters in the
computation zone, whether or not the computation zone is visible. For information on
creating a computation zone, see "Creating a Computation Zone" on page 276. If you
wish, you can calculate an interference matrix on all transmitters or on a group of
transmitters by right-clicking the Transmitters folder or the subfolder in the Transmitters
folder and selecting Interference Matrices > Calculate from the context menu.
4. On the Interference Calculation dialogue, set the following options under Service Zone:
- Server: Select "HCS Servers" to consider all potential servers.
Interference matrices can also be calculated for all servers, servers with the best signal level per HCS layer
and a margin, and servers with the best idle mode reselection criterion (C2). For more information, see "Com-
paring Service Areas in Calculations" on page 386.
- With a Margin: Enter a handover margin in the With a Margin text box. The default value is "4 dB."
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
5. Under Traffic Spreading, you can select whether you want to calculate interference on the percentage of inter-
fered traffic or on the percentage of interfered area:
- Based on the maps used in the default traffic capture: if you choose this option, Atoll will calculate inter-
ference on the interfered traffic for each pair of subcells (interfered-interferer). This method takes into account
both traffic maps and the traffic load, either user-defined or as calculated by the dimensioning process.
- Uniform (probability expressed in % of interfered area): if you choose this option, Atoll will calculate inter-
ference on the interfered areas for each pair of subcells (interfered-interferer). This method cannot accurately
take areas of heavy traffic into consideration, but is faster than calculating interference based on maps.
6. Click OK to start the calculation.
The results of the calculation can be found in a new item in the Interferences Matrices folder on the Data tab of
the Explorer window. By default, the new interference matrix is active.
Caution: Changing certain transmitter or subcell properties, such as power reduction, reception
threshold, and transmitter power or EIRP will make interference matrices invalid. If you
change transmitter or subcell properties, you will have to recalculate the interference
matrices.
Calculating interference matrices is very resource intensive. If you have an extremely large network, calculating an inter-
ference matrix that covers the entire network can require more computer resources than are available.
If you have to calculate an interference matrix for a large network, you can reduce the load it places on computer resources
by calculating individual interference matrices for parts of the network. Under most circumstances, including 1,000 to 2,000
transmitters in each individual interference matrix is the most efficient. After you have calculated an interference matrix for
each part of the network, Atoll will combine them when you run the AFP.
To calculate interference matrices for a large network:
1. Create a computation zone that covers part of the network. For information on creating a computation zone, see
"Creating a Computation Zone" on page 276. In Figure 7.39, the computation zone is indicated by the red outline.
2. Calculate an interference matrix for the area covered by the computation zone as explained earlier.
3. Create a new computation zone that partly overlaps the area covered by the first computation zone. In Figure 7.40,
the area covered by the first computation zone is indicated by the black outline.
4. Calculate an interference matrix for the area covered by the computation zone.
5. Repeat step 1. to step 4. until have created interference matrices for the entire network, as shown in the following
figures.
Note: As indicated in the figures, each calculation zones must partially overlap the preceding
calculation zone, in order to assure that the calculated interference matrices also overlap
and thereby give results for the entire network. How the interference matrices are
combined depends on the AFP used.
Atoll supports IM0, IM1, IM2, and CLC interference matrix files. Atoll also supports a simplified format that gives the inter-
fered subcell, the interfering subcell, the co-channel interference probability, and the adjacent channel probability. For
more information on the simplified format, see the Technical Reference Guide.
When you import several interference matrices that describe the same interfered-interferer pairs, Atoll only takes the first
description of the pair. When descriptions of the same interfered-interferer pair are found in subsequent files, the descrip-
tion is ignored.
Atoll does not perform a validity check on the imported interference file; you must therefore ensure that the imported infor-
mation is consistent with the current configuration. Furthermore, Atoll only imports interference matrices for active trans-
mitters.
To import interference matrices:
1. Click the Data tab of the Explorer window.
2. Right-click the Interference Matrices folder. The context menu appears.
3. Select Import from the context menu. The Open dialogue appears.
4. Select the file type from the Files of Type list.
5. Select the file to import.
If you are importing a CLC file, Atoll looks for the associated DCT file in the same directory. When this file is
unavailable, Atoll assumes that the transmitter identifiers in the CLC file are the same as the transmitter names.
6. Click Open. A message appears asking whether Atoll should merge the imported interference matrix into the
GSM/GPRS/EDGE document:
- Click Yes to save the imported interference matrix in the GSM/GPRS/EDGE document.
When you save an imported interference matrix in the GSM/GPRS/EDGE document, you can still choose to
save it to an external file linked to the GSM/GPRS/EDGE document. For information, see "Storing Interference
Matrices Externally" on page 327.
- Click No to store the interference matrix externally, but linked to the GSM/GPRS/EDGE document.
7. The interference matrices are imported into the current Atoll document and appear as new items in the Interfer-
ence Matrices folder.
You can save interference matrices to external files that are linked to the GSM/GPRS/EDGE document. Linking interfer-
ence matrices to the GSM/GPRS/EDGE document can reduce file size when the Atoll document is extremely large.
Atoll supports IM0, IM1, IM2, and CLC interference matrix files.
To export interference matrices:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the Interference Matrices folder.
3. Right-click the interference matrix you want to export. The context menu appears.
4. Select Export from the context menu. The Save As dialogue appears.
5. Select the file type from the Save as Type list.
6. Enter the File name and click Save. The interference matrix is exported.
- Transmitters with the same BSIC and BCCH can not be differentiated.
- Transmitters having the same BCCH will never have an interference entry.
- Information is lost when more than 6 interferers exist at any location.
- If many interferers share the same BCCH, they increase each others interference levels.
- HCS layers may cause problems because there are more servers at any point, macro layer servers are
stronger, or a correction margin might be introduced for some equipment, etc.
This type of interference matrix can be created using an extended neighbours list.
Note: Matrices based on propagation can store addtional information, such as server selection
or the HO margin value, if shadowing has been taken into account for their calculation
and, if so, the cell edge coverage probability. This information can then be used by the
AFP for some calculations. For more information, see "The Atoll AFP Cost Tab" on
page 421 and "The Atoll AFP Advanced Tab" on page 427.
Note: You can also select a transmitter by clicking its symbol in the map window.
i. Under Traffic Loads, indicate whether the AFP should take traffic loads From the Subcells Table or use
loads Based on the Default Traffic Capture Results
ii. If you want the AFP to consider discontinuous transmission mode for TRXs which support it in calculating
the interference, select the DTX check box and enter the Voice Activity Factor.
iii. Select the Load all the subcells involved in separation constraints check box if you want all subcells
potentially involved to be loaded.
iv. Select the Load all the potential interferers check box if you want all potential interferers to be loaded.
If this check box is not selected, the cost function will consist only of the separation violation cost.
- Separation Rules: For information on the options, see "Defining Required Channel Separations" on
page 331.
- Exceptional Pairs: For information on the options, see "Defining Required Channel Separations" on
page 331.
- Intra-Technology Neighbours: For information on the options, see "Planning Neighbours" on page 294.
7. Click Run. The interference probability values are displayed in the right-most column of the Interference Matrix
Analysis tab.
The tool calculates and displays interference probabilities using the active interference matrices available in the
Interference Matrices folder on the Data tab of the Explorer window. If the interference matrices in the Interfer-
ence Matrices folder are inactive or interference matrices are not available, the analysis tool only calculates and
displays the interference from a transmitter and its TRXs on itself.
In the map window, arrows from the studied transmitter to each interfered or interfering transmitter are displayed.
The colour of the arrow is the same as the colour of the studied transmitter. The probabilities of interference are
displayed as captions for the arrows. The thickness of the arrows are indicate the interference probability.
In order to generate a report on all the interference matrices in the Interference Matrices folder:
1. Click the Data tab of the Explorer window.
2. Right-click the Interference Matrices folder. The context menu appears.
3. Select Generate Report from the context menu. The Interference Matrix Scope dialogue appears with the report
details:
- A table with the number of times the listed transmitter has been interfered
- The total number of entries in the selected interference matrices
- The number of transmitters covered by the interference matrices
- The average number of interferers per interfered subcell in the interference matrices.
Note: When you have several active interference matrices in a project, only those intersecting
the AFP scope will be loaded, in order to avoid consuming more memory than necessary
during the AFP process. The "RAM Consumption" field in the Interference Matrix property
dialogue indicates how much memory the interference matrix will take. In the case of
embedded matrices, the AFP loads them only during the AFP process, so the "RAM
Consumption" field will always be zero. In case of matrices saved externally, the AFP
reads them to check their scope and then decides if they are to be loaded into memory or
not, so, the "RAM Consumption" field will always be a non-zero value (after running the
AFP). As a result, it is recommended to embed interference matrices as long as the
document file size is lower than 2 Gb.
4. In the row marked with the New Row icon ( ), select the following parameters for each separation rule you want
to define:
- Type of Relation: Select the type of relation, co-transmitter, co-site, or neighbour, between the two TRXs.
- TRX Type: Select the first TRX type.
- TRX Type 2: Select the second TRX type.
- Default Min. Separation: Enter the minimum difference in channels that must exist between the two TRX
types. Entering "0" means that they can use the same channel.
4. In the row marked with the New Row icon ( ), select the following parameters for each separation rule you want
to define:
- Transmitter: Select the transmitter on which the TRX in TRX Type is located.
- TRX Type: Select the first TRX type.
- Transmitter 2: Select the transmitter on which the TRX in TRX Type 2 is located.
- TRX Type 2: Select the second TRX type.
- Separation: Enter the minimum difference in channels that must exist between the two TRX types. Entering
"0" means that they can use the same channel.
Note: When you select "All" as either Transmitter 1 TRX Type or Transmitter 2 TRX Type,
Atoll does not display all TRX types. Rather it displays only exceptional frequency
separations for which the TRX type constraint is defined as "All."
5. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
6. Select Exceptional Pairs (AFP) from the context menu.
7. Click the left side of the Visual Management button ( ) in the Radio toolbar.
8. Click a transmitter on the map to display the exceptional frequency separations. If the selected transmitter has
defined exceptional frequency separations that fit the display options, Atoll displays the following information (see
Figure 7.41):
- The exceptional frequency separations of the selected transmitter are indicated by a heavy line in the same
colour as the other transmitter in the defined pair.
- The defined minimum channel separation is indicated beside the line linking the two transmitters.
9. In order to restore colours and cancel the neighbour display, click the left side of the Visual Management icon
( ) again.
Tip: You can define exceptional pairs directly on the map. For information, see "Adding or
Removing Exceptional Frequency Separations Using the Mouse" on page 333.
5. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
6. Select Exceptional Pairs (AFP) from the context menu.
- To add an exceptional frequency separation: Press CTRL and click on the second transmitter. A dialogue
appears where you enter the minimum separation between the transmitters. When you click OK, the excep-
tional frequency separation is created and indicated by a heavy line in the same colour as the second trans-
mitter. The minimum separation is indicated next to the link. The exceptional separation constraint is
automatically added to the Exceptional Separation Constraints table.
- To remove an exceptional frequency separation: Press CTRL and click on the second transmitter of an
existing exceptional frequency separation. The exceptional frequency separation is removed from the map
and from the Exceptional Separation Constraints table.
9. In order to restore colours and cancel the neighbour display, click the left side of the Visual Management icon
( ) again.
Tip: You can display the coverage areas of exceptional pairs in much the same way as you
would display the coverage of a transmitters neighbours, with the exception that you
select Exceptional Pairs (AFP) when you click the menu button ( ) of Visual
Management button ( ) in the Radio toolbar. For more information, see "Displaying
the Coverage of Each Neighbour of a Transmitter" on page 300.
sioning process can be used by an advanced AFP model to optimise the number of TRXs and maximise the
amount of correctly served traffic.
C/I Threshold (dB): The minimum signal quality for the TRX Type, under which the subcell interface is taken into
consideration.
Reception Threshold (dBm): The minimum received signal for the TRX Type.
Frequency Domain: (including excluded channels), from which the AFP tool can choose frequencies. The Rele-
vant Frequency Band used by the model when assigning cell types to transmitters is also visible on the TRXs
tab, but is a parameter of the cell type and can not be changed here. For information on frequencies, see "Fre-
quencies" on page 382.
The other AFP-relevant parameters under Subcell (TRX Groups) Settings on the TRXs tab of the transmitters Proper-
ties dialogue are:
Allocation Strategy: The allocation strategy used during manual or automatic frequency planning. There are two
available allocation strategies:
- Free: Any of the channels belonging to the frequency domain can be assigned to TRXs.
- Group Constrained: Only channels belonging to the same frequency group in the frequency domain can be
assigned. You can use the Preferred Frequency Group to define the preferred group of frequencies when
using the AFP.
Preferred Frequency Group: When the Group Constrained allocation strategy is selected, in any hopping mode
(including non-hopping), the AFP tries to assign frequencies from the preferred group during automatic allocation.
The preferred frequency group is a soft constraint used by the AFP to assign frequencies to TRXs. When the AFP
is unable to assign a frequency from the preferred group and allocates a frequency from outside the group, a cor-
responding cost is taken into account. The preferred group can also be the result of allocation if the AFP model is
able to allocate patterns based on azimuth.
Max. MAL Length: The maximum length of the mobile allocation list (MAL), in other words, the maximum number
of channels allocated to the TRXs of the subcell during automatic frequency planning if the Hopping Mode is
either SFH (Synthesized Frequency Hopping) or BBH (Base Band Hopping) and if the Allocation Strategy is
Free.
Hopping Mode: The frequency hopping mode supported by the selected TRX type. The hopping mode can be
either "Base Band Hopping mode (BBH)" or "Synthesized Hopping mode (SFH)." If frequency hopping is not sup-
ported, select "Non Hopping."
Note: If SFH is the frequency hopping mode, the settings in the AFP module must match the
settings in the subcell. For information on configuring the optional Atoll AFP module, see
Chapter 8: The Atoll AFP Module.
Synchronisation: The Synchronisation is used during frequency hopping; frequency hopping is synchronised
among all TRXs of subcells with the same string of characters in the Synchronisation column. By default, the
name of the site is used as the value in the Synchronisation column, synchronising frequency hopping for all
TRXs on the same site.
DTX Supported: The DTX Supported check box is selected if the subcell supports DTX (Discontinuous Trans-
mission) mode. Subcells supporting DTX can reduce interference they produce according to the defined voice
activity factor. DTX does not apply to the BCCH since it is assumed that the BCCH is always on air.
Freeze the number of required TRXs: This option may be used by an AFP model which has the capability to
optimise the number of required TRXs (increase or decrease) with the only aim to maximise the amount of cor-
rectly served traffic. In other words, you may have less TRXs than required if these ones are not subject to any
interferences and the amount of correctly served traffic will be larger. When you select this option, the functionality
is blocked on the considered subcell.
Although you can manually set the values of the following required timeslot numbers, these values are calculated during
the dimensioning process:
On the AFP tab of a transmitters Properties dialogue, you can set the weight to be used for the selected transmitter during
the AFP:
AFP Weight: Enter an AFP weight. The AFP weight is used to increase or decrease the importance of a subcell
during automatic frequency planning. The value must be a real number. The higher the AFP weight is, the higher
the constraint on the TRX type. The AFP weight artificially mulitplies the cost function which has to be minimised
by the AFP.
If certain resources have already been allocated, on the AFP tab of a transmitters Properties dialogue you can choose
to freeze the resources that have already been allocated to the selected transmitter. During automatic frequency planning,
these resources, which can be allocated as part of the process, will not be changed.
Freeze Channels and MAIO: When the Freeze Channels and MAIO check box is selected, the transmitters cur-
rently assigned channels and MAIO are kept when a new AFP session is started. On the TRXs tab, under TRXs,
you can freeze the channels and MAIO for individual TRXs assigned to the transmitter.
Freeze HSN: When the Freeze HSN check box is selected, the transmitters currently assigned HSN is kept when
a new AFP session is started. On the TRXs tab, under Subcell (TRX Groups) Settings, you can freeze the HSN
for individual subcells assigned to the transmitter.
Freeze BSIC: When the Freeze BSIC check box is selected, the transmitters currently assigned BSIC is kept
when a new AFP session is started.
Under Exceptional separation constraints with other transmitters, on the AFP tab of a transmitters Properties
dialogue, you can enter exceptional separation constraints with other transmitters. Exceptional separation constraints you
enter here also appear in the Exceptional Separation Constraints table. For information on creating exceptional sepa-
ration constraints, see "Defining Exceptional Frequency Separations" on page 332.
The third and last dialogue of the AFP interface allows you to:
a. Select an AFP Module from the list. You can click the Browse button ( ) to access the properties of the
selected AFP module.
b. Under Resources to Allocate, select the check boxes of the resources you want to allocate. The selections
you make will depend on the hopping mode of your network:
- MAL: The MAL is used by subcells that have either the BBH or the SFH hopping mode. You must also
allocate MAIO, HSN, and channels in this case.
- MAIO: The MAIO is used by subcells that have either the BBH or the SFH hopping mode. You must also
allocate MAL, HSN, and channels in this case.
- Channels: All subcells must be allocated channels, independently of their hopping mode.
- HSN: The HSN is used by subcells that have either the BBH or the SFH hopping mode. You must also
allocate MAL, MAIO, and channels in this case.
- BSIC: The BSIC is used by all transmitters, independently of the hopping mode.
c. Under Strategies, select the check boxes of the strategies to base the current allocation:
- Azymuth-oriented allocation (Pattern 1/X): This functionality is used by all subcells, independently of
the hopping mode, but which are in Group Constrained allocation mode, using frequency domains with a
sufficient number of groups. The pattern allocation is only possible on non-omni transmitters, and if trans-
mitters participating in the pattern are on the same HCS layer and use the same frequency band.
- Optimisation of the number of TRXs: In case of weakly traffic-loaded subcells, The AFP may reduce
the number of TRXs compared to the number of required TRXs in order to reduce the AFP cost, and so
on, the level of interferences. In the same way, for highly traffic-loaded subcells, the AFP may increase
the number of TRXs compared to what is required in order to reduce the blocked traffic. This strategy may
also affect the initial subcell loads and KPIs would have to be recalculated after the automatic frequency
planning process (See "Calculating Key Performance Indicators of a GSM/GPRS/EDGE Network" on
page 370 for more information).
Note: Atoll will not create TRXs without channels. Therefore, if you do not allocate MAL and
MAIO, all the SFH subcells are considered "locked" and no TRXs will be created for them.
By the same token, if you allocate only MAL and MAIO, all NH and BBH subcells will be
considered "locked" and no TRXs will be created.
d. Under Indicators to Allocate, select the check boxes of the indicators you want to allocate. Depending on
the selected AFP module, you can allocate:
- AFP Rank: The AFP rank indicates how often a frequency has been allocated. The higher the AFP rank,
the more often a frequency has been allocated and therefore the higher the risk of interference.
- Subcells indicators: AFP cost, congestion, blocking and separation cost can be estimated by the AFP
model per pool of subcells (e.g. (BCCH, TCH) pool). These indicators are a way to precisely estimate the
allocation quality at the subcell level and provide some directions to improve the plan, if necessary.
- Total Costs and Separation Costs: Total costs and separation costs can be displayed for TRXs, trans-
mitters, or sites if you add the appropriate custom field (AFP_COST and AFP_SEP_COST of type
SINGLE for the total and separation costs, respectively) to the corresponding table.
e. The Load all the subcells involved in separation constraints check box is automatically selected. In that
case, all subcells potentially involved will be loaded.
f. Select the Load all interferers propagating in the focus zone check box if you want all potential interferers
to be loaded. If this check box is not selected, the cost function will consist only of the separation violation cost.
5. Click the Next > button at the bottom of the dialogue. The Separations tab appears.
On the Separations tab:
a. Click the Exceptional Pairs button to open the Exceptional Separation Constraints dialogue and define
exceptional frequency separations to define channel separations that apply to specific pairs of TRXs. During
automatic frequency planning, the separation rules are first considered, but they can be overridden by specific
entries in the Exceptional Separation Constraints table. For information on defining exceptional separation
constraints, see "Defining Exceptional Frequency Separations" on page 332.
b. When you have finished entering exceptional separation constraints, click Close to close the Exceptional
Separation Constraints dialogue.
c. In the table on the Separations tab, enter or modify the separation rules. The separation rules set the channel
separation that should exist between pairs of TRXs on the same transmitter, same site, or between neigh-
bours. For information on defining separation rules, see "Defining Separation Rules" on page 332.
6. Click the Next > button at the bottom of the dialogue. The Global Parameters tab appears.
On the Global Parameters tab, you can select the subcells and TRXs to which frequencies will be allocated and
you can define certain input parameters:
a. Under Allocation of subcells of type, select the check boxes of the TRX types on which you want to run the
allocation. If all check boxes are checked, resources will be allocated for all subcell types. At least one box
must be selected.
b. Under Freezing of existing TRXs of type, select the check boxes of the existing allocated TRX types you do
not want to change. If one of the check boxes is selected, existing TRXs of the selected type are frozen, but
missing TRXs of the same type can still be allocated.
c. Under Subcell Traffic and Target Rate of Traffic Overflow, indicate where the AFP should take traffic loads
from:
- From the Subcell Table
- Based on the Default Traffic Capture Results
d. If you want the AFP to consider discontinuous transmission mode for TRXs which support it in calculating the
interference, check the DTX check box and enter the Voice Activity Factor.
7. Click Validate to load the network. Atoll loads and verifies the following (see Figure 7.43):
- The transmitters to be allocated (TBA transmitters): The TBA transmitters are the active and filtered trans-
mitters belonging to the transmitters folder from which the AFP was started and that are located within the
focus zone. If no focus zone exists, Atoll uses the computation zone. Only TBA transmitters are allocated
resources, however, all loaded transmitters are taken into account when calculating cost.
- The potential interferers: The potential interferers are loaded and verified if the option "Load all the potential
interferers" was selected. Potential interferers are transmitters whose calculation radius intersects the calcu-
lation radius of any TBA transmitter.
- Transmitters involved in the separation conditions with TBA transmitters: These are neighbours, co-site
transmitters, transmitters or subcells of exceptional pairs and, in case of BSIC allocation, neighbours of neigh-
bours.
Once loaded, Atoll verifies network consistency and reports any problems, such as inconsistencies in the existing
allocation. Inconsistent values, for example, a traffic load of 100, will be replaced by Atoll in order to avoid blocking
the AFP process. However, in some cases, such as an empty HSN domain when HSN allocation is requested, the
AFP process stops and informs the user of the steps to take to correct the situation.
Caution: You must read the information in the event viewer carefully before proceeding.
8. Enter the Target Computation Time in minutes. The AFP will use the target computation time to select the
method best suited to finding a suitable allocation solution. This means that you should not consider the results to
be optimised before the end of the target time. The AFP might stop before the end of the target computation time
but if the AFP has not found a solution by the end of the target computation time, it will continue improving the
frequency plan.
9. If desired, change the value set for Generator Initialisation.
The generator initialisation number lets you choose between random and deterministic sequences for the AFP
process. When the generator initialisation number is set to 0, calculations will be random. For any other generator
initialisation, the computations will be deterministic. Therefore, whenever the AFP is launched for the same
network with the same non-zero value set for the generator initialisation, the same results will be obtained.
Note: It should be noted that all AFP calculations are deterministic at the start, even if the
generator initialisation number is set to 0. The effect of the random seed can only be
observed after a certain time (5 to 15% of the target computation time). If you want to the
automatic allocation process to show the effect of random allocation, you must let the AFP
calculate until the target time has elapsed.
10. Click Run to start the AFP process. The AFP Progress dialogue appears (see Figure 7.44).
The AFP Progress dialogue has the following sections:
- Progress: The Progress section gives you the elapsed time in comparison with the target computation time
and the number of solutions evaluated so far.
- General Information and Interference Matrix Report: This section displays either the current status of the
AFP process or the interference matrix report. You can switch the display between general information and
the interference matrix report by clicking the button in the top-right corner of this section ( ).
- Event Viewer: The Event Viewer displays a description of each event along with the time it occurred.
- Best Frequency Plan Costs: The Best Frequency Plan Costs section displays the costs and components
of each solution. You can select what information is displayed in the table by clicking the Display Options
button. The following options are available:
- All the Summed Costs (Network, Separation, Blocking, Additional, Taxes, etc...)
- All the Modifiable Costs
- All the Frozen Costs
- Plan Comparison: The Plan Comparison section allows you to display histograms of the frequency cost and
usage distribution for both the initial plan and best plan. The histogram represents the channels as a function
of the frequency of their use. Moving the pointer over the histogram displays the cost or frequency of use of
each channel. The results are highlighted simultaneously in the Detailed Results list.
11. If you want to pause the AFP process or stop it, click the Pause/Stop button. The Results dialogue appears. For
information on the Results dialogue, see "Automatic Frequency Allocation Results" on page 340.
You can continue the AFP process, if you wish, by clicking the Resume button.
The Allocation tab (See Figure 7.46) show the results of the allocation and are given by transmitter, TRX type, and TRX
and are coded by colour:
Light blue: The resource is frozen and has not been modified.
Red: The resource has been modified but there is a separation constraint violation.
Green: The resource has been modified respecting separation constraints.
Black: The resource has been not modified.
Blue: The resource has been created respecting separation constraints.
Purple: The resource has been created but there is a separation constraint violation.
Brown: The resource has not been modified but there is still a separation constraint violation.
When you move the pointer over a resource in the table, a tooltip displays gives the reason for the status indicated by the
colour (see Figure 7.47).
Under Display, for each transmitter (Transmitter column)/subcell (TRX Type column)/TRX (Index column) combination,
Atoll displays the following columns, depending on the resources you selected to allocate (see "Running an Automatic
Frequency Allocation" on page 336):
BSIC
HSN
Channels
In addition, you can choose or not to display the AFP indicators if you chose to calculate them during the AFP session.
3 differents plans can be shown in this grid:
The plan to be committed: it represents the results obtained from the AFP and your possible modifications (dele-
tion of allocated resources, rollback to initial values, etc...). Only this plan can be committed to the network.
The AFP Plan: it shows the gross results of the AFP session, in other words the final results of the best plan. When
this plan is displayed, the Commit button can be reached. To make it available, select the Plan to be commited
display option.
The initial Plan: it shows the network frequency plan before the AFP session. This plan is the current one before
you commit any AFP results. In other words, this is the currently commited plan.
Any separation constraint violations are listed in the Separation Violations column. You can display details about sepa-
ration constraint violations in the following ways:
By right-clicking the separation constraint violation and selecting Separation Constraint Violations from the con-
text menu. A message box appears displaying details about the separation constraint violation (see Figure 7.48).
By clicking the Display Options button and selecting Display detailed constraint violations. The following addi-
tional columns are displayed:
- With the TRX: The TRX with which this separation constraint violation occurs is indicated in the With the TRX
column in the form of a button. Clicking the button brings you to that TRX in the table.
- Co-channel: The probability of collision with the same channel on the TRX indicated in the With the TRX
column.
- Adjacent: The probability of collision with an adjacent channel on the TRX indicated in the With the TRX
column.
By clicking the Display Options button and selecting Display violations only. This filters out resources which do
not have separation violations.
By clicking the Display Options button and selecting Co-Transmitter Violations. This filters out resources which
do not have co-transmitter separation violations.
By clicking the Display Options button and selecting Co-Site Violations. This filters out resources which do not
have co-site separation violations.
By clicking the Display Options button and selecting Neighbour Violations. This filters out resources which do
not have neighbour separation violations.
By clicking the Display Options button and selecting Exceptional Pair Violations. This filters out resources
which do not have exceptional pair separation violations.
The AFP Rank column indicates the quality of the TRX in that subcell. The higher the AFP rank, the higher the cost, in
terms of the risk of interference. In other words, when you are trying to improve the solution proposed by the AFP tool, you
must concentrate on the TRXs with the highest AFP rank first. You can hide the AFP Rank column by clicking the Display
Options button and selecting Display the AFP Indicators.
The bottom of the Results window displays the messages related to the last solution (which may not be the best solution)
as well as potential related allocation problems.
The Subcells tab (See Figure 7.49) show the subcells indicators, the variation of the number of required TRXs (and corre-
sponding traffic loads), and the allocated preferred frequency groups estimated by the AFP model, in case you selected
this options when starting the AFP. For each parameter, this grid indicates the initial and final results. When commiting
them, they are assigned to the corresponding objects (subcells).
This tab may also indicates the preferred groups assigned to subcells in the case the AFP has been run with the azymuth-
oriented allocation strategy.
In the Results dialogue, you can resolve the displayed separation constraint violations using the Channel Assignment
column. The Channel Assignment column displays whether the value assigned is a new value or the initial value. The
Channel Assignment column enables you resolve separation constraint violations by re-assigning the values from the
original frequency plan, returning to the AFP-assigned value, or deleting the TRX.
To resolve separation constraint violations:
Click the entry in the Channel Assignment column corresponding to the TRX where the separation constraint
violation occurs and select one of the following:
- New Value: The value assigned by the AFP process. By default, only new values are displayed in the results
window. This option is not available if the value was not changed during the AFP process.
- Initial Value: The value before running the AFP or after changing the assigned value.
- Delete the TRX: The TRX will be deleted when you click the Commit button.
When you select one of options in the Channel Assignment column, Atoll updates not only the TRX affected, but also
the separation constraint violations of all other TRXs affected by the change.
As you modify the current frequency allocation plan, you can display the AFP plan as it appeared before modifications or
the initial frequency plan, if there was one.
To change the displayed plan:
Click the Display Options button and select one of the following:
- Display the Current Plan: When you select this option, Atoll displays the frequency plan as it now stands,
in other words, Atoll displays the AFP plan with your modifications. You can only modify the entries in the
Channel Assignment column in the current plan.
- Display the AFP Plan: When you select this option, Atoll displays the AFP plan as it stood before you began
making modifications.
- Display the Initial Plan: When you select this option, Atoll displays the frequency plan as it was after the AFP
stopped, in other words, Atoll displays the AFP plan without your modifications.
You can cancel all the modifications you have made to the current AFP plan.
To cancel all the modifications you have to the current AFP plan:
Clicking the Actions button and select Reset channel allocations.
You can automatically resolve separation constraint violations by clicking the Actions button and selecting Constraint
Violations Resolution. For more information, see "Resolving Separation Constraint Violations Automatically" on
page 344.
You can also resolve the separation constraint violations automatically. When you resolve separation constraint violations
automatically, Atoll deletes the TRXs that respond to set criteria and that are involved in the violations.
To resolve separation constraint violations automatically:
1. Click the Actions button and select Constraint Violations Resolution. The Constraint Violations Resolution
dialogue appears (see Figure 7.50).
2. Under TRXs to take into account, select one of the following:
- All the TRXs: Atoll will delete all TRXs that do not respect the separation constraints.
- Only the TRXs modified by the AFP: Atoll will delete only TRXs that were modified by that AFP that do not
respect the separation constraints.
3. Under Violation types to consider, select the check boxes corresponding to the separation constraint violations
that you want Atoll to take into consideration:
- Co-Transmitters: TRXs on the same transmitter.
- Co-Sites: TRXs on the same site.
- Neighbours: TRXs on neighbouring transmitters.
- Exceptional Pairs: TRXs on transmitters that are part of an exceptional pair.
4. Under Collision Probabilities, select the collision probability you want Atoll to take into consideration:
- If you want Atoll to take into consideration all co-channel and adjacent channel collision probabilities, select
All.
- If you want Atoll to take into consideration co-channel collision probabilities greater than or equal to a defined
value, select If the co-channel probability is >= and enter a value.
- If you want Atoll to take into consideration co-channel and adjacent collision probabilities greater than or equal
to a defined value, select If the co- or adjacent channel probability is >= and enter a value.
5. Under TRX Types, select the check boxes of the TRX types you want Atoll to take into consideration:
- Apply to Control Channel TRXs: If you select this check box, control channel TRXs (i.e., BCCH TRXs) will
be deleted.
- Apply to other TRXs: If you select this check box, TRXs on non-control channel TRX types (i.e., TCH,
TCH_EGPRS or TCH_INNER) will be deleted.
6. Click OK. Atoll deletes the TRXs that are involved in the separation constraint violations and that respond to set
criteria.
Once you have made the necessary modifications to the frequency plan, you can commit the frequency plan.
To commit the currently displayed frequency plan:
1. Ensure that the currently displayed frequency plan is the one you want to commit by clicking the Display Options
button and selecting the desired frequency plan
- Display the Current Plan: When you select this option, Atoll displays the frequency plan as it now stands,
in other words, Atoll displays the AFP plan with your modifications. You can only modify the entries in the
Channel Assignment column in the current plan.
- Display the AFP Plan: When you select this option, Atoll displays the AFP plan as it stood before you began
making modifications.
- Display the Initial Plan: When you select this option, Atoll displays the frequency plan as it was after the AFP
stopped, in other words, Atoll displays the AFP plan without your modifications.
2. Click Commit.
You can also export the currently displayed frequency plan.
To export the currently displayed frequency plan:
1. Ensure that the currently displayed frequency plan is the one you want to export by clicking the Display Options
button and selecting the desired frequency plan:
- Display the Current Plan: When you select this option, Atoll displays the frequency plan as it now stands,
in other words, Atoll displays the AFP plan with your modifications. You can only modify the entries in the
Channel Assignment column in the current plan.
- Display the AFP Plan: When you select this option, Atoll displays the AFP plan as it stood before you began
making modifications.
- Display the Initial Plan: When you select this option, Atoll displays the frequency plan as it was after the AFP
stopped, in other words, Atoll displays the AFP plan without your modifications.
2. Click the Actions button and select Export Results. The Export dialogue appears.
3. Export the frequency plan as explained in "Exporting Tables to Text Files" on page 58.
Note: If you are not satisfied with the current frequency plan, you can click the Resume button
to restart the AFP process from the last proposed solution in order to try to improve it.
Whereas an automatic frequency planning module (AFP) provides the final solution in terms of allocated channels, i.e.,
the best frequency allocation that provides the lowest overall cost, the IFP lets you use your knowledge of the network to
improve the frequency plan proposed by the AFP.
To allocate frequencies interactively using the IFP:
1. Click View > Interactive Frequency Planning Tool. The Interactive Frequency Planning Tool window
appears.
2. Select the Channel Allocation and Analysis tab.
3. Select a transmitter from the Transmitter list.
Note: You can also select a transmitter by clicking its symbol in the map window.
i. Under Traffic Loads, indicate whether the AFP should take traffic loads From the Subcells Table or use
loads Based on the Default Traffic Capture Results.
ii. If you want the AFP to consider discontinuous transmission mode for TRXs which support it in calculating
the interference, select the DTX check box and enter the Voice Activity Factor.
iii. Select the Load all the subcells involved in separation constraints check box if you want all subcells
potentially involved to be loaded.
iv. Select the Load all interferers propagating in the focus zone check box if you want all potential inter-
ferers to be loaded. If this check box is not selected, the cost function will consist only of the separation
violation cost.
- Separation Rules: For information on the options, see "Defining Required Channel Separations" on page 331.
- Exceptional Pairs: For information on the options, see "Defining Required Channel Separations" on page 331.
- Intra-Technology Neighbours: For information on the options, see "Planning Neighbours" on page 294.
7. Click Run. The IFP calculates and displays the cost of the current channel allocation for the selected transmitter.
The tool calculates and displays interference probabilities using the active interference matrices available in the
Interference Matrices folder on the Data tab of the Explorer window. If the interference matrices in the Interfer-
ence Matrices folder are inactive or interference matrices are not available, the analysis tool only calculates and
displays the interference from a transmitter and its TRXs on itself.
In the map window, arrows from the studied transmitter to each interfered or interfering transmitter are displayed.
The colour of the arrow is the same as the colour of the studied transmitter. The probabilities of interference are
displayed as captions for the arrows. The thickness of the arrows indicate the interference probability.
Different information and options are available depending on the hopping mode of the selected transmitters TRXs:
- Non-hopping mode:
The first column displays the number of existing and required TRXs and lists the existing TRXs of the selected
type for the transmitter being studied along with the frequency assigned to them and the cost of the allocation.
The second column displays the number of candidate channels available, and lists these channels along with
the costs for the channels if they were allocated to the selected transmitter.
The Filter column lets you select the interference information to be displayed in the fourth column, the Prob-
ability column. You can display the High Separation Violations, Separation Violations, Interference Vio-
lations, or the Neighbour Violations of the selected transmitter. You can choose more than one of these
options by pressing and holding CTRL and clicking each option.
The Probability column displays the interference probabilities between the TRX of the selected transmitter
and the interfering TRXs using the selected options in the Filter column.
The second column displays the number of candidate channels available, and lists these channels along with
the MALs and costs if they were allocated to the selected transmitter.
The Filter column lets you select the interference information to be displayed in the fourth column, the Prob-
ability column. You can display the High Separation Violations, Separation Violations, Interference Vio-
lations, or the Neighbour Violations of the selected transmitter. You can choose more than one of these
options by pressing and holding CTRL and clicking each option.
The Probability column displays the interference probabilities between the TRX of the selected transmitter
and the interfering TRXs using the selected options in the Filter column.
The Filter column lets you select the interference information to be displayed in the fourth column, the Prob-
ability column. You can display the High Separation Violations, Separation Violations, Interference Vio-
lations, or the Neighbour Violations of the selected transmitter. You can choose more than one of these
options by pressing and holding CTRL and clicking each option.
The Probability column displays the interference probabilities between the TRX of the selected transmitter
and the interfering TRXs using the selected options in the Filter column.
Using the IFP, you can create a new TRX and assign a channel to it, delete an existing TRX, and replace the current chan-
nel assigned to an existing TRX.
To create a new TRX and assign a channel to it:
1. Select New TRX from the list of TRXs in the first column.
2. Select a channel from the list of candidate channels in the second column.
3. Click Create. A new TRX is created in the selected transmitter with the channel you selected.
To delete an existing TRX:
1. Select the TRX that you want to delete from the list of TRXs in the first column.
2. Click Delete. The selected TRX is deleted from the transmitter.
To replace the current channel assigned to an existing TRX:
1. Select the TRX to which you want to assign a different channel from the list of TRXs in the first column.
2. Select a channel from the list of candidate channels in the second column.
3. Click Replace. The candidate channel will be assigned to the existing TRX.
The changes that you make are taken into account in real time and updated results are displayed.
6. Click the Condition tab (see Figure 7.51). On the Condition tab, you can define the signals that will be considered
for each pixel.
- Click the arrow button ( ) and select one of the following thresholds:
- Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception
threshold specified for each subcell (including the defined power reduction) as the lower end of the signal
level range.
- Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold
to be used for all subcells as the lower end of the signal level range.
- Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer
level or specifically for each transmitter. When you select "HCS Servers" or "All," there might be areas where
several transmitters experience interference. On these pixels, several CI values are calculated. Therefore, on
the Display tab, you select to display either the lowest CI level or the highest CI level (for more information,
see "Comparing Service Areas in Calculations" on page 386).
- Enter a hand-over margin in the With a Margin text box. The default value is "4 dB."
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability. Shadowing margins (depending on the entered cell edge coverage probability and the model standard
deviation per clutter class) are applied only to the values for C.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
8. Under Interference Condition, set the following parameters:
- You can select which TRX type to consider as potential victim by selecting it from the Interfered Subcells list.
- Click the arrow button ( ) and select one of the following thresholds:
- Subcell C/I Threshold: Select Subcell C/I Threshold if you want to use the CI threshold specified for
each subcell (including the defined power reduction) as the lower end of the CI range.
- Specified C/I Threshold: Select Specified C/I Threshold if you want to enter a threshold to be used for
all subcells as the lower end of the CI range.
- Select either CI or C(I+N).
- Click the arrow button ( ) and select one of the following thresholds:
- Subcell C/I Threshold: Select Subcell C/I Threshold if you want to use the CI threshold specified for
each subcell (including the defined power reduction) as the upper end of the CI range.
- Specified C/I Threshold: Select Specified C/I Threshold if you want to enter a threshold to be used for
all subcells as the upper end of the CI range.
Notes: The defined CI values define the range of CI values to be displayed. Values outside of
this range are not displayed.
You can not select Subcell C/I Threshold as both the lower and the upper end of the CI
range to be considered.
- Select whether you want the defined CI or CI+N condition to be Satisfied By:
- At least one TRX: When you select the option At least one TRX, the defined interference condition must
be satisfied by at least one TRX on a given pixel for the results to be displayed on that pixel.
- The worst TRX: When you select the option The worst TRX, Atoll selects the worst results for each pixel.
If the worst results do not satisfy the defined interference condition, the results will not be displayed on
that pixel.
Note: These options are available only if a lower C/I Threshold is set.
- If you have selected "C/(I+N)", you can define the value to be added to the interference. The defined noise
figure is added to the thermal noise value (defined by default at -121 dBm) to calculate the value of N. Select
one of the following:
- Based on Terminal: Select Based on Terminal if you want to use the noise figure defined for a terminal
and select the terminal from the list.
- Fixed Value: Select Fixed Value if you want to enter a value and then enter the noise figure in the text
box.
9. If you want discontinuous transmission mode for TRXs which support it taken into account during the calculation
of interference, select the DTX taken into account check box and enter the percentage of time during which a
user is talking in the Voice Activity Factor text box.
10. Select the Traffic Load that will be used to calculate interference:
- 100 %: The maximum traffic load (subcells entirely loaded).
- From subcell table: The subcell traffic load as defined or as calculated during dimensioning.
11. Select in the Interference Sources scrolling box whether the interference should be calculated from adjacent chan-
nels, co-channels, or from both. The adjacent channel effect on the concerned victim channel, i.e., the interfer-
ence, is decreased by the adjacent channel protection level.
You may even select interferences coming from an external project using another technology. For more informa-
tion, see "GSM/GPRS/EGPRS Interfered networks" on page 239.
If you want Atoll to take interference due to intra-technology third order intermodulation into consideration when
calculating the total interference, you must set up your document and database as explained in "Taking Intermod-
ulation Interference into Consideration in Calculations" on page 407.
12. Select the Detailed Results check box if you want to display detailed results per transmitter. The results displayed
depend on the subcell frequency hopping mode:
- Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
- Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping
mode.
- Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in syn-
thesised frequency hopping mode.
13. Click the Display tab.
For a coverage prediction by CI levels, the Display Type "Value Intervals" based on the Field "CI level (dB)" is
selected by default.
If you selected "HCS Servers" or "All" from the Server list on the Condition tab, there may be areas where several
transmitters experience interference. On these pixels, several CI values are calculated. Therefore, you can base
the results displayed on either the Field "Min. CI level (dB)" or "Max. CI level (dB)" as well as the "CI level (dB)"
Field.
For information on defining display properties, see "Display Properties of Objects" on page 33.
15. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Note: By changing the parameters selected on the Condition tab and by selecting different
results to be displayed on the Display tab, you can calculate and display information other
than that which has been explained in the preceding sections.
6. Click the Condition tab (see Figure 7.52). On the Condition tab, you can define the signals that will be considered
for each pixel.
- Click the arrow button ( ) and select one of the following thresholds:
- Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception
threshold specified for each subcell (including the defined power reduction) as the lower end of the signal
level range.
- Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold
to be used for all subcells as the lower end of the signal level range.
- In Figure 7.51, a Specified Reception Threshold less than or equal to -105 dBm will be considered.
- Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer
level or specifically for each transmitter (for more information, see "Comparing Service Areas in Calculations"
on page 386).
- Enter a hand-over margin in the With a Margin text box. The default value is "4 dB."
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability. Shadowing margins (depending on the entered cell edge coverage probability and the CI standard
deviation per clutter class) are applied only to the values for C. Shadowing margins are not taken into account
in determining the values for interference.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
8. Under Interference Condition, set the following parameters:
- You can select which TRX type to consider as potential victim by selecting it from the Interfered Subcells list.
- Click the arrow button ( ) and select one of the following thresholds:
- Subcell C/I Threshold: Select Subcell C/I Threshold if you want to use the CI threshold specified for
each subcell (including the defined power reduction) as the lower end of the CI range.
- Specified C/I Threshold: Select Specified C/I Threshold if you want to enter a threshold to be used for
all subcells as the lower end of the CI range.
- Select either CI or C(I+N).
- Click the arrow button ( ) and select one of the following thresholds:
- Subcell C/I Threshold: Select Subcell C/I Threshold if you want to use the CI threshold specified for
each subcell (including the defined power reduction) as the upper end of the CI range.
- Specified C/I Threshold: Select Specified C/I Threshold if you want to enter a threshold to be used for
all subcells as the upper end of the CI range.
- If you have selected "C/(I+N)", you can define the value to be added to the interference. The defined noise
figure is added to the thermal noise value (defined at -121 dBm) to calculate the value of N. Select one of the
following:
- Based on Terminal: Select Based on Terminal if you want to use the noise figure defined for a terminal
and select the terminal from the list.
- Fixed Value: Select Fixed Value if you want to enter a value and then enter the noise figure in the text
box.
9. If you want discontinuous transmission mode for TRXs which support it taken into account during the calculation
of interference, select the DTX taken into account check box and enter the percentage of time during which a
user is talking in the Voice Activity Factor text box.
10. Select the Traffic Load that will be used to calculate interference:
- 100 %: The maximum traffic load (subcells entirely loaded).
- From subcell table: The subcell traffic load as defined or as calculated during dimensioning.
11. Select in the Interference Sources scrolling box whether the interference should be calculated from adjacent chan-
nels, co-channels, or from both. The adjacent channel effect on the concerned victim channel, i.e., the interfer-
ence, is decreased by the adjacent channel protection level.
You may even select interferences coming from an external project using another technology. For more informa-
tion, see "GSM/GPRS/EGPRS Interfered networks" on page 239.
If you want Atoll to take interference due to intra-technology third order intermodulation into consideration when
calculating the total interference, you must set up your document and database as explained in "Taking Intermod-
ulation Interference into Consideration in Calculations" on page 407.
12. Select the Detailed Results check box if you want to display detailed results per transmitter. The results displayed
depend on the subcell frequency hopping mode:
- Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
- Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping
mode.
- Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in syn-
thesised frequency hopping mode.
13. Click the Display tab.
For a coverage prediction by interfered zones, the Display Type "Discrete Values" based on the Field "Transmit-
ter" is selected by default. On the Data tab of the Explorer window, the coverage prediction results are arranged
by interfered transmitter.
You can also define the display to display the quality received on each interfered area:
- The quality received on each interfered area: Select "Value Intervals" as the Display Type and "C/I Level
(dB)" as the Field. On the Data tab of the Explorer window, the coverage prediction results are first arranged
by interfered transmitter and then by C/I level.
For information on defining display properties, see "Display Properties of Objects" on page 33.
15. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Notes: By changing the parameters selected on the Condition tab and by selecting different
results to be displayed on the Display tab, you can calculate and display information other
than that which has been explained in the preceding sections.
As explained in "Displaying a Coverage Prediction Report" on page 288, you can display
a prediction report on the interfered studies indicating the amount of correctly served
traffic out of the total traffic covered by the study. To enable this, select the option Traffic
(Erlangs - based on Traffic Load) after having run the prediction report.
2. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the fol-
lowing:
- Move the receiver to change the current position.
- Click to place the receiver at the current position. You can move the receiver again by clicking it a second time.
- Right-click the receiver to choose one of the following commands from the context menu:
- Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates.
- Target Site: Select a site from the list to place the receiver directly on a site.
4. Click the Interference tab.
The Interference tab displays, in the form of a bar graph, the signal level of the selected transmitter, a black bar
indicating the total interference experienced by the receiver, and bars representing the interference received from
each interferer. The information displayed in the bar graph depends on the hopping mode of the subcell identified
in the left margin of the graph:
- In Non-Hopping Mode, you can study the interference level on either a specific channel or on the most inter-
fered one of either of a specific subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER) or all of the selected
transmitter.
- In Base Band Hopping Mode, you can study the interference level on either a specific MAL or on the most
interfered one of either of a specific subcell (BCCH, TCH, TCH_EGPRS or TCH_INNER) or all of the selected
transmitter.
- In Synthesised Frequency Hopping Mode, you can study the interference level on either a specific MAL-
MAIO pair or on the most interfered one of either of a specific subcell (BCCH, TCH, TCH_EGPRS or
TCH_INNER) or all of the selected transmitter.
Figure 7.53 on page 354 gives an example of the Interference tab. The signal level of the transmitter, Site10_3, is
-95.61 dB and is indicated by a red bar. The black bar indicates the total interference experienced by the receiver
(-98.65 dB). The seven interferers are responsible for -102.69 dB (olive green), -103.06 dB (yellow), -107.31 dB
(purple), -111.56 dB (olive green), -115.38 dB (green), -115.50 dB (pink), and -117.13 dB (olive green). The bars
indicating the interference caused by Site17_1 and Site15_1 are only partially filled. The entire bar indicates the
interference that could potentially be caused by the transmitter whereas the filled part of the bar indicates the
actual interference caused. A transmitters actual interference can be lower than its potential interference:
- If it uses synthesised frequency hopping mode (reduction due to fractional load)
- If it uses adjacent channels (reduction due to adjacent channel protection)
- If the subcell it is modelling is a TRX_INNER subcell (reduction due to lower offset).
In the map window, arrows from the receiver to each transmitter are displayed in the colour of the transmitters they
represent. The interference levels at the receiver from transmitters are displayed as captions for these arrows. If
you let the pointer rest on an arrow, the interference level received from the corresponding transmitter at the
receiver location will be displayed in the tooltip along with information on the channel being interfered and the type
of interference, i.e., co-channel or adjacent channel interference.
If you want Atoll to take interference due to intra-technology third order intermodulation into consideration when
calculating the total interference, you must set up your document and database as explained in "Taking Intermod-
ulation Interference into Consideration in Calculations" on page 407.
5. You can change the following options at the top of the Interference tab:
- Transmitter: Select the transmitter from the list. The transmitters in the list are sorted in the order of
decreasing signal level received at the pointer location.
- TRXs: Select the Subcell type (or ALL) to be analysed.
- Select whether you want the interference to be studied on a specific item (channel, MAL or MAL-MAIO
according to the hopping mode) or the most interfered item.
- I: Select whether the interference should be calculated from adjacent channels, co-channels, or from both.
You may even select interferences coming from an external project using another technology. For more infor-
mation, see "GSM/GPRS/EGPRS Interfered networks" on page 239.
- Interference Method: Select whether the interference is calculated by CI or by C(I+N).
6. Right-click the Interference tab and select Properties to display the Analysis Properties dialogue. This dialogue
is available from the context menu on all tabs of the Point Analysis Tool window. You can change the following:
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and
select "From Model" from the Shadowing Margin list.
- Select Signal Level, Path loss, and Total losses from the Result Type list.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
7. Click the Results tab.
The Results tab displays the current position and height of the receiver, the clutter class it is situated on, the
received signal level from each transmitter, the distance of the receiver from each transmitter, and the interference
and C/I from each transmitter in decreasing order.
In the map window, arrows from the receiver to each transmitter are displayed in the colour of the transmitters they
represent. The interference levels at the receiver from transmitters are displayed as captions for these arrows. A
thick black line from the pointer to its best server is also displayed in the map window. The best server of the
pointer is the transmitter from which the pointer receives the highest signal level. If you let the pointer rest on an
arrow, the interference level received from the corresponding transmitter at the receiver location will be displayed
in the tooltip along with information on the channel being interfered and the type of interference, i.e., co-channel
or adjacent channel.
If you want Atoll to take interference due to intra-technology third order intermodulation into consideration when
calculating the total interference, you must set up your document and database as explained in "Taking Intermod-
ulation Interference into Consideration in Calculations" on page 407.
8. You can change the following options at the top of the Results tab:
the interference caused by Site17_1 and Site15_1 are only partially filled. An entire bar indicates the interference
that could potentially be caused by the transmitter whereas a filled part of the bar indicates the actual interference
caused.
If interference due to intra-technology third order intermodulation is taken into consideration, Atoll also displays
the interference level as a bar and the source in the format "Interferer Name: I3 (first channel, second channel)".
At the top of the Interference tab, the name of the most interfered channel on Site10_3 is channel 540 and the C/I received
is 3.03 dB. An analysis of the interferers gives the following information:
The bars representing Site14_3, Site19_2, Site12_3, Site16_2, and Site13_1 are full. On four out of five transmit-
ters, channel 540 is assigned to the TCH TRX of the transmitter. On the last transmitter, channel 540 is assigned
to the BCCH TRX of the transmitter. They are, therefore, co-channel interferers. No power reduction is defined,
therefore the interference is not reduced.
The bars representing Site17_1 and Site15_1 are partly full. The bars are only partly full because the interference
is reduced: on these transmitters, channel 540 is not assigned; channel 541 is assigned to the TCH TRX of
Site17_1 and channel 539 is assigned to the TCH TRX of Site15_1. They are, therefore, adjacent channel inter-
ferers and their interference is reduced by the adjacent channel protection level of 18 dB (the default value defined
in the Predictions folder properties). No power reduction is defined for this subcell. If a power reduction of 3 dB
had been defined for this subcell, the interference would have been reduced by an additional 3 dB. A fractional
load might be another reason for reduced interference.
Figure 7.54: Condition settings for a coverage prediction by GPRS/EDGE coding schemes
Note: If, under GPRS/EDGE, you select C and not CI for the coverage prediction, the only
option you need to select under Interference Condition is the TRX type to consider from
the TRXs list.
If you want Atoll to take interference due to intra-technology third order intermodulation into consideration
when calculating the total interference, you must set up your document and database as explained in "Taking
Intermodulation Interference into Consideration in Calculations" on page 407.
- Select the Detailed Results check box if you want to display detailed results per transmitter. The results dis-
played depend on the subcell frequency hopping mode:
- Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
- Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping
mode.
- Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in
synthesised frequency hopping mode.
9. Under GPRS/EDGE, set the following parameters:
- From the Coding Schemes list, select the technology on which the coding scheme calculation will be based:
- All: If you select All, both GPRS coding schemes and EDGE coding schemes will be used.
- GPRS: If you select GPRS, only GPRS coding schemes will be used.
- EDGE: If you select EDGE, only EDGE coding schemes will be used. Depending on the selected GPRS/
EDGE configurations, EDGE coding schemes may be of type EGPRS (Standard EDGE) or EGPRS2
(EDGE Evolution).
- Select whether you want to base the coverage prediction on C or CI. If you select C, the only option you need
to select under Interference Condition is the TRX type to consider from the TRXs list.
- If desired, select which Terminal you want to base the coding scheme coverage prediction on. When you
restrict the coverage prediction to a selected terminal, Atoll bases the coverage prediction on the C and CI
graphs for the selected terminal, as well as on its noise figure. As well, Atoll respects the terminals defined
coding scheme limit.
- If desired, select which Mobility you want to base the coding scheme coverage prediction on. When you select
a mobility, Atoll considers which transmitters have the Coding Scheme Configuration that can support the
selected mobility and relative threshold.
- Enter a Noise Figure. By default, a noise figure of 8 dB is used if no terminal is selected.
- Select the Thermal Noise Taken into Account check box if you want Atoll to consider thermal noise.
- Select the Ideal Link Adaptation check box if you want the coding scheme that offers the highest throughput
to be selected. Otherwise, Atoll will choose the coding scheme according to signal level and quality.
10. Click the Display tab.
For a coverage prediction by coding schemes, the Display Type "Discrete Values" based on the Field "Coding
Schemes" is selected by default. If desired, you can base the display in "Value Intervals" the Field "Best Coding
Schemes," in which case, Atoll displays the best coding scheme for each pixel.
For information on defining display properties, see "Display Properties of Objects" on page 33.
11. Click OK to save your settings.
12. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 7.55). On the Condition tab, you can define the signals that will be considered
for each pixel.
Figure 7.55: Condition settings for a RLC/MAC throughput per timeslot coverage prediction
Note: If, under GPRS/EDGE, you select Based on C for the coverage prediction, the only
option you need to select under Interference Condition is the TRX type to consider from
the TRXs list.
- You can select which TRX type to consider as potential victim by selecting it from the Interfered Subcells list.
- If you want discontinuous transmission mode for TRXs which support it taken into account, select the DTX
taken into account check box and enter the percentage of time during which a user is talking in the Voice
Activity Factor text box.
- Select the Traffic Load that will be used to calculate interference:
- 100 %: The maximum traffic load (subcells entirely loaded).
- From subcell table: The subcell traffic load as defined or as calculated during dimensioning.
- Select in the Interference Sources scrolling box whether the interference should be calculated from adjacent
channels, co-channels, or from both. The adjacent channel effect on the concerned victim channel, i.e., the
interference, is decreased by the adjacent channel protection level.
You may even select interferences coming from an external project using another technology. For more infor-
mation, see "GSM/GPRS/EGPRS Interfered networks" on page 239.
If you want Atoll to take interference due to intra-technology third order intermodulation into consideration
when calculating the total interference, you must set up your document and database as explained in "Taking
Intermodulation Interference into Consideration in Calculations" on page 407.
- Select the Detailed Results check box if you want to display detailed results per transmitter. The results dis-
played depend on the subcell frequency hopping mode:
- Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
- Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping
mode.
- Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in
synthesised frequency hopping mode.
9. Under GPRS/EDGE, set the following parameters:
- From the Coding Schemes list, select the technology for which the packet throughput per timeslot calculation
will be calculated:
- All: If you select All both GPRS coding schemes and EDGE coding schemes will be used.
- GPRS: If you select GPRS only GPRS coding schemes will be used.
- EDGE: If you select EDGE only EDGE coding schemes will be used. Depending on the selected GPRS/
EDGE configurations, EDGE coding schemes may be of type EGPRS (Standard EDGE) or EGPRS2
(EDGE Evolution).
- Select Based on C if you want to base the coverage prediction on C. If you select Based on C, the only option
you need to select under Interference Condition is the TRX type to consider from the TRXs list. Otherwise,
select Based on CI.
- If desired, select which Terminal you want to base the coverage prediction on. When you restrict the coverage
prediction to a selected terminal, Atoll bases the coverage prediction on the C and CI graphs for the selected
terminal. As well, Atoll respects the terminals defined coding scheme limit and noise figure.
- If desired, select which Mobility you want to base the coding scheme coverage prediction on. When you select
a mobility, Atoll considers which transmitters have the Coding Scheme Configuration that can support the
selected mobility.
- Enter a Noise Figure. By default, the noise figure is 8 dB.
- Select the Thermal Noise Taken into Account check box if you want Atoll to consider thermal noise.
- Select the Ideal Link Adaptation check box if you want the coding scheme that offers the highest throughput
for a given C or CI to be selected. Otherwise, Atoll will choose the coding scheme by considering only the
coding scheme admission threshold in terms of C and/or CI.
10. If desired, under Throughput/Timeslot, you can change the type of packet throughput per timeslot coverage pre-
diction by changing the selection:
- RLC/MAC Throughput/Timeslot: Select RLC/MAC Throughput/Timeslot if you want to base the coverage
prediction on the RLC/MAC throughput per timeslot. The RLC/MAC throughput per timeslot is the throughput
extracted from the coding schemes.
- Application Throughput/Timeslot: Select Application Throughput/Timeslot Based on Service if you
want to base the coverage prediction on the application throughput per timeslot and choose the packet-based
Service on which to base the coverage prediction.
11. Click the Display tab.
For a coverage prediction by packet throughput per timeslot, the Display Type "Value Intervals" based on the
Field "Throughput/Timeslot" is selected by default. If desired, you can change the values displayed by selecting
one of the following values from the Field list:
- Throughput/Timeslot: Each layer shows the throughput that a transmitter can carry on one timeslot.
- Best Throughput/Timeslot: The resulting coverage gives the best throughput/timeslot per pixel from the pre-
vious display.
- Average Throughput/Timeslot: Gives the average throughput that the transmitter can carry on one timeslot
per pixel. If there are different coverage areas for different TRXs, this study will calculate the union of these
coverages and display the average values over these coverage areas. While the other coverages for
throughput/timeslot perform an intersection over these coverage zones keeping the minimum value of
throughput per pixel.
For information on defining display properties, see "Display Properties of Objects" on page 33.
13. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
The BLER is determined after Atoll determines which coding scheme is to be selected for a given C or CI. When the
coding scheme has been determined, 1 - BLER represents the efficiency factor applied to the maximum throughput of the
coding scheme to obtain the served throughput. The BLER can be determined for each pixel.
You can make a BLER coverage prediction for either GPRS, for EDGE, or for both. As well, you can restrict the coverage
prediction to a selected terminal or mobility or to a combination of terminal and mobility. When you restrict the coverage
prediction to a selected terminal, Atoll bases the coverage prediction on the C and CI graphs for the selected terminal.
As well, Atoll respects the terminals defined coding scheme limit. When you select a mobility, Atoll considers which trans-
mitters have the Coding Scheme Configuration that can support the selected mobility. Atoll can use the noise figure
defined for the selected terminal or a user-defined noise figure if no terminal is selected or if the calculations are based on
an interpolation of the values for CI and C(I+N). For information on defining a terminal, see "Modelling GSM/GPRS/EDGE
Terminals" on page 405.
To make a BLER coverage prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select one of the following and click OK:
- RLC/MAC Throughput/Timeslot: Select RLC/MAC Throughput/Timeslot if you want to base the coverage
prediction on the RLC/MAC throughput per timeslot. The option RLC/MAC Throughput/Timeslot, under
Throughput/Timeslot on the Condition tab, is chosen automatically.
- Application Throughput/Timeslot: Select Application Throughput/Timeslot if you want to base the cov-
erage prediction on the application throughput per timeslot. The option Application Throughput/Timeslot
Based on Service, under Throughput/Timeslot on the Condition tab, is chosen automatically. You can then
choose the packet-based service on which to base the coverage prediction.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 7.56). On the Condition tab, you can define the signals that will be considered
for each pixel.
- Enter a hand-over margin in the With a Margin text box. The default value is "4 dB."
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability. Shadowing margins (depending on the entered cell edge coverage probability and the model standard
deviation per clutter class) are applied to the values for C.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
8. Under Interference Condition, you can define how Atoll will calculate CI for the BLER coverage prediction.
Note: If, under GPRS/EDGE, you select Based on C for the coverage prediction, the only
option you need to select under Interference Condition is the TRX type to consider from
the TRXs list.
- You can select which TRX type to consider as potential victim by selecting it from the Interfered Subcells list.
- If you want discontinuous transmission mode for TRXs which support it taken into account, select the DTX
taken into account check box and enter the percentage of time during which a user is talking in the Voice
Activity Factor text box.
- Select the Traffic Load that will be used to calculate interference:
- 100 %: The maximum traffic load (subcells entirely loaded).
- From subcell table: The subcell traffic load as defined or as calculated during dimensioning.
- Select in the Interference Sources scrolling box whether the interference should be calculated from adjacent
channels, co-channels, or from both. The adjacent channel effect on the concerned victim channel, i.e., the
interference, is decreased by the adjacent channel protection level.
You may even select interferences coming from an external project using another technology. For more infor-
mation, see "GSM/GPRS/EGPRS Interfered networks" on page 239.
If you want Atoll to take interference due to intra-technology third order intermodulation into consideration
when calculating the total interference, you must set up your document and database as explained in "Taking
Intermodulation Interference into Consideration in Calculations" on page 407.
- Select the Detailed Results check box if you want to display detailed results per transmitter. The results dis-
played depend on the subcell frequency hopping mode:
- Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
- Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping
mode.
- Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in
synthesised frequency hopping mode.
9. Under GPRS/EDGE, set the following parameters:
- From the Coding Schemes list, select the technology for which the packet throughput per timeslot calculation
will be calculated:
- All: If you select All both GPRS coding schemes and EDGE coding schemes will be used.
- GPRS: If you select GPRS only GPRS coding schemes will be used.
- EDGE: If you select EDGE only EDGE coding schemes will be used. Depending on the selected GPRS/
EDGE configurations, EDGE coding schemes may be of type EGPRS (Standard EDGE) or EGPRS2
(EDGE Evolution).
- Select Based on C if you want to base the coverage prediction on C. If you select Based on C, the only option
you need to select under Interference Condition is the TRX type to consider from the TRXs list. Otherwise,
select Based on CI.
- If desired, select which Terminal you want to base the coverage prediction on. When you restrict the coverage
prediction to a selected terminal, Atoll bases the coverage prediction on the C and CI graphs for the selected
terminal, as well as on its noise figure. As well, Atoll respects the terminals defined coding scheme limit.
- If desired, select which Mobility you want to base the coding scheme coverage prediction on. When you select
a mobility, Atoll considers which transmitters have the Coding Scheme Configuration that can support the
selected mobility and relative threshold.
- Enter a Noise Figure. By default, a noise figure of 8 dB is used if no terminal is selected.
- Select the Thermal Noise Taken into Account check box if you want Atoll to consider thermal noise.
- Select the Ideal Link Adaptation check box if you want the coding scheme that offers the highest throughput
to be selected. Otherwise, Atoll will chose the coding scheme according to signal level and quality.
10. If desired, under Throughput/Timeslot, you can change the type of packet throughput per timeslot coverage pre-
diction by changing the selection:
- RLC/MAC Throughput/Timeslot: Select RLC/MAC Throughput/Timeslot if you want to base the coverage
prediction on the RLC/MAC throughput per timeslot.
- Application Throughput/Timeslot: Select Application Throughput/Timeslot Based on Service if you
want to base the coverage prediction on the application throughput per timeslot and choose the packet-based
Service on which to base the coverage prediction.
11. Click the Display tab.
For a BLER coverage prediction, the Display Type "Value Intervals" is selected by default. Select one of the
following values from the Field list:
- BLER (%): The coverage is coloured according to the block error rate measured per transmitter. If the
throughput per timeslot is greater than the maximum throughput per timeslot, the BLER is 0%.
- Max BLER: Gives the coverage according to the maximum block error rate per pixel for each transmitter.
For information on defining display properties, see "Display Properties of Objects" on page 33.
13. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
6. Click the Condition tab (see Figure 7.57). On the Condition tab, you can define the signals that will be considered
for each pixel.
Note: If, under Quality Indicators Calculation, you select Calculations Based on CN for the
coverage prediction, the only option you need to select under Interference Condition is
the TRX type to consider from the TRXs list.
- You can select which TRX type to consider as potential victim by selecting it from the Interfered Subcells list.
- If you want discontinuous transmission mode for TRXs which support it taken into account, select the DTX
taken into account check box and enter the percentage of time during which a user is talking in the Voice
Activity Factor text box.
- Select the Traffic Load that will be used to calculate interference:
- 100 %: The maximum traffic load (subcells entirely loaded).
- From subcell table: The subcell traffic load as defined or as calculated during dimensioning.
- Select in the Interference Sources scrolling box whether the interference should be calculated from adjacent
channels, co-channels, or from both. The adjacent channel effect on the concerned victim channel, i.e., the
interference, is decreased by the adjacent channel protection level.
You may even select interferences coming from an external project using another technology. For more infor-
mation, see "GSM/GPRS/EGPRS Interfered networks" on page 239.
If you want Atoll to take interference due to intra-technology third order intermodulation into consideration
when calculating the total interference, you must set up your document and database as explained in "Taking
Intermodulation Interference into Consideration in Calculations" on page 407.
- Select the Detailed Results check box if you want to display detailed results per transmitter. The results dis-
played depend on the subcell frequency hopping mode:
- Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
- Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping
mode.
- Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in
synthesised frequency hopping mode.
9. Under Quality Indicators Calculation, set the following parameters:
- Select Calculations Based on CN if you want to base the coverage prediction on CN. If you select Calcu-
lations Based on CN for the coverage prediction, the only option you need to select under Interference Con-
dition is the TRX type to consider from the TRXs list. The codec mode is selected only according to signal
level.
- Select Calculations Based on C(I+N) if you want to base the coverage prediction on C(I+N).
- If desired, select which Terminal you want to base the coverage prediction on. When you restrict the coverage
prediction to a selected terminal and the terminal type and the transmitter have different Codec Configuration,
Atoll determines the intersection of the codec modes contained in the transmitter and terminal Codec Config-
uration. The codec mode is then selected according to the calculated CN or CI + N on each pixel. For a given
quality or a given codec mode, look-up tables defined in Codec Configuration provide the circuit quality indi-
cator (BER, FER, or MOS) displayed as a result.
- If desired, select which Mobility you want to base the coding scheme coverage prediction on. When you select
a mobility, Atoll considers the codec mode applicable for the selected mobility on the Codec Configuration.
- Enter a Noise Figure. By default, a noise figure of 8 dB is used if no terminal is selected.
10. Click the Display tab.
For a circuit quality indicator coverage prediction, the Display Type "Value Intervals" is selected by default. Select
one of the following values from the Field list:
- BER: The coverage is coloured according to the bit error rate measured per transmitter.
- FER: The coverage is coloured according to the frame erasure rate measured per transmitter.
- MOS: The coverage is coloured according to the mean opinion score measured per transmitter.
- Max BER: The coverage is coloured according to the maximum bit error rate per pixel of the covering trans-
mitters.
- Max FER: The coverage is coloured according to the maximum frame erasure rate per pixel of the covering
transmitters.
- Max MOS: The coverage is coloured according to the maximum mean opinion score per pixel of the covering
transmitters.
For information on defining display properties, see "Display Properties of Objects" on page 33.
12. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The results of
circuit quality indicator coverage predictions based on BER, FER, or MOS are broken down by transmitter, as you can see
by clicking the Expand button ( ) to expand the results of the coverage prediction after you have calculated it. The results
of circuit quality indicator coverage predictions based on Max BER, Max FER, or Max MOS are broken down by threshold.
Note: You must have a computation zone defined to use the Sector-to-Sector Interference
Tool. For information on creating a computation zone, see "Creating a Computation
Zone" on page 276.
- Select the transmitter whose signal is interfered from the Victim list or click the Victim button ( ) and select
the transmitter by clicking it on the map.
- Select the transmitter whose signal is interfering from the Interferer list or click the Interferer button ( ) and
select the transmitter by clicking it on the map.
The victim and interferer transmitters are displayed on the map with specific icons ( and respectively).
3. Under Coverage Conditions, select what you are going to base the interference calculation on:
- Signal Level: Enter a signal threshold.
- Based on Study: Select the coverage prediction on which you want to base the interference calculation on.
4. Click Calculate. The interference will be displayed on the map if you have selected the Visible check box (see
Figure 7.58).
The results are listed in a table by transmitter, TRX type, and TRX and are coded by colour. Channels in black present no
separation violations. Channels in red present separation violations.
Any separation constraint violations are listed in the Separation Violations column. You can display details about sepa-
ration constraint violations by right-clicking the separation constraint violation and selecting Separation Constraint Viola-
tions from the context menu. A message box appears displaying details about the separation constraint violation (see
Figure 7.60). You can navigate to the TRX with which the current TRX has a separation violation by clicking the button in
the With the TRX column.
Note: By including the BCCH, BSIC, and channel list of each transmitter in the transmitter label,
the search results will be easier to understand. For information on defining the label, see
"Defining the Object Type Label" on page 35.
You can use the Search Tool to search for a channel. You can search in all channels, in control channels, or in non-control
channels.
To find a channel using the Search Tool:
1. Click View > Search Tool. The Search Tool window appears.
2. Select the Channel tab.
3. Enter a Channel.
4. Select from the As list what type of channels you want Atoll to search:
- All: all channels
- BCCH: control channels
- Non-BCCH: non-control channels
5. If you only want the channel entered in the Channel box to be displayed, select the Co-channel Only check box.
6. Click Search.
Transmitters with the same channel are displayed in red. Transmitters with two adjacent channels (i.e., a channel
higher and a channel lower) are displayed in yellow. Transmitters with a lower adjacent channel are displayed in
green; transmitters with a higher adjacent channel are displayed in green. Any transmitter with the same channel
is displayed in red, even if it also has adjacent channels. All other transmitters are displayed in grey.
If you selected the Co-channel Only check box, transmitters using the same channel are displayed in red; all
others, including transmitters with adjacent channels, are displayed in grey.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
You can use the Search Tool to search for a combination of TRX and subcell parameters: a channel, BSIC or NCC-BCC,
as well as HSN and MAIO.
To find a combination of TRX and subcell parameters using the Search Tool:
1. Click View > Search Tool. The Search Tool window appears.
2. Select the Channel/BSIC/HSN/MAIO tab.
3. Select the parameters on which you want to search:
- Channel: Select one of the following and enter, if desired, a specific channel number. If you do not enter a
channel number, Atoll will search all specified channels according to the other parameters.
- All: Atoll will search all channels.
- BCCH: Atoll will only search BCCH channels.
- Not BCCH: Atoll will only search channels that are not BCCH channels.
- BSIC or NCC-BCC: Select one of the following:
- BSIC: If you select BSIC, enter a value for the BSIC.
- NCC: If you select NCC, enter a value for the NCC and for the BCC.
- HSN: Enter, if desired, an HSN.
- MAIO: Enter, if desired, a MAIO.
4. Click Search.
Transmitters that match the defined search parameters are displayed in red. All other transmitters are displayed
in grey.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
- BCCH: To display the BCCH of a transmitters subcells, select "BCCH" from the Label or Tip Text Field Def-
inition dialogue.
- BSIC: To display the BSIC of a transmitter, select "BSIC" from the Label or Tip Text Field Definition dia-
logue.
- Channels: To display the channels allocated to a transmitter, select "Channels" from the Label or Tip Text
Field Definition dialogue.
- HSN: To display the HSN allocated to a transmitters subcells, select "HSN" from the Label or Tip Text Field
Definition dialogue.
- MAIO: To display the MAIO allocated to a transmitters subcells, select "MAIO" from the Label or Tip Text
Field Definition dialogue.
- Cell type: To display the cell type allocated to a transmitter, select "Cell type" from the Label or Tip Text Field
Definition dialogue.
- Required TRXs per Transmitter or Subcell: To display the number of required TRXs per transmitter or per
subcell, select "Required TRXs" or "Subcell: Required TRXs," respectively, from the Label or Tip Text Field
Definition dialogue.
- Number of TRXs Assigned: To display the number of TRXs assigned to a transmitter, select "Number of
TRXs" from the Label or Tip Text Field Definition dialogue.
- Frequency Band: To display the frequency band assigned to a transmitter, select "Frequency Band" from the
Label or Tip Text Field Definition dialogue.
- GPRS/EDGE: To display which transmitters are GPRS/EDGE-capable, select "GPRS/EDGE" from the Label
or Tip Text Field Definition dialogue.
- Coding Scheme Configuration: To display the Coding Scheme Configuration assigned to a transmitter,
select "Coding Scheme Configuration" from the Label or Tip Text Field Definition dialogue.
- Codec Configuration: To display the Codec Configuration assigned to a transmitter, select "Codec Configu-
ration" from the Label or Tip Text Field Definition dialogue.
Note: Because labels are always displayed, you should avoid displaying too much information
at the same time.
5. Click OK.
For information on display options, see "Display Properties of Objects" on page 33.
- Frequency band
- Channels
6. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to
the list of parameters on which the transmitters will be grouped.
7. If you do not want the transmitters to be sorted by a certain parameter, select it in the Group these fields in this
order list and click . The selected parameter is removed from the list of parameters on which the transmitters
will be grouped.
8. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters
to be grouped:
- Copy: Click the Copy button to copy the histogram to the clipboard. You can paste the histogram as a
graphic into another application, for example, a word-processor.
- Print: Click the Print button to print the histogram.
5. Under Dimensioning Parameters, select the dimensioning model that will be used for the KPI calculation from
the Model list. You can access the parameters of the selected dimensioning model by clicking the Browse button
( ).
6. Click Calculate to run the KPI calculation.
The output of the calculation appears in the KPI Calculation dialogue under Results. You can select which
columns to display by clicking the Displayed Columns button and selecting or clearing the check box of the
columns. The following results are given for each transmitter in the Transmitter column:
- TRX Type: For each transmitter, the results are given by TRX type (e.g., BCCH, TCH, TCH_EGPRS and
TCH_INNER). Together, the Transmitter and TRX Type columns identify the subcell.
- Number of TRXs: The number of TRXs assigned for both the subcell's circuit-switched and packet-switched
traffic, while taking into account the quality of service criterion assigned for each.
- Load (%): The average demand in timeslots (packet and circuit), divided by the total number of timeslots avail-
able. It represents the average occupancy of the TRXs. This parameter is one of the principal results of dimen-
sioning along with the number of TRXs. In addition, this parameter may have been updated by an AFP model
which is capable of optimising (reduce or increase) the number of required TRXs. The consequence is a mod-
ification in term of subcell load.
- Multiplexing Factor: The user or Temporary Block Flow (TBF) multiplexing factor. The multiplexing factor
corresponds to the number of timeslots per frame.
- Maximum Number of TRXs per Transmitter: The maximum number of TRXs that a transmitter can support
is an input of the KPI calculation. This parameter is provided by the equipment manufacturer. The value can
be set for each transmitter or taken from the dimensioning model for transmitters where this value is not set.
- Target Rate of Traffic Overflow (%): This input parameter defines the percentage of traffic that is allowed to
overflow from one subcell to another in case the traffic assigned to this subcell is greater than the maximum
traffic that it can accommodate. It can be considered an anticipation of the percentage of traffic that will be
rejected from higher priority subcells or layers to lower ones. The value is specified for each subcell.
- Half-rate Traffic Ratio (%): This input parameter is defined per subcell and indicates the percentage of sub-
cell traffic that uses half-rate access.
If the values are different for BCCH and TCH subcells, Atoll will use the values for the target rate of traffic
overflow and the half-rate traffic ratio from the BCCH subcell.
- Packet demand (kbps): The Packet Traffic Demand is the total traffic demand in kilobits per second gener-
ated by packet-switched service users within the coverage area of the transmitter.
- Packet average demand (timeslots): The number of timeslots needed to satisfy the packet traffic demand
depends on the maximum throughput that a packet timeslot can support.
- Average Number of Timeslots per Connection (Packet): This input parameter defines the average number
of timeslots used by packet-switched-traffic users while accessing services. Packet-switched services allow
up to eight timeslots per connection. The average number of timeslots per connection corresponds to the
average number of downlink timeslots (multiplied by the number of simultaneous carriers in EDGE Evolution,
if any) over which a single mobile terminal can communicate at one time.
- Circuit Demand (Erlangs): The Circuit Traffic Demand is the total traffic demand in Erlangs generated by
circuit-switched-service users within the coverage area of the transmitter.
Note: For concentric cell types, the traffic demand on TCH subcells is different from the one
calculated during the traffic capture. For concentric cell types, the traffic demand on TCH
subcells is calculated from the traffic demand of the capture and the effective rate of traffic
overflow.
- Circuit average demand (timeslots): The Average Demand in Circuit Timeslots is calculated taking into
account the effect of half-rate circuit-switched traffic: two half-rate users are equivalent to one full-rate user.
- Average Number of Timeslots per Connection (Circuit): The Average Number of Timeslots per Con-
nection (Circuit) is an input parameter. The number of timeslots per connection is "1" for full-rate traffic, oth-
erwise it depends on the half-rate traffic ratio.
At present, Atoll only models circuit calls using 1 timeslot per connection; this parameter is for forward com-
patibility.
- Served Circuit Traffic (Erlangs): The Served Circuit Traffic is the circuit-switched traffic in Erlangs that the
subcell can serve.
The served circuit-switched traffic is circuit traffic demand less the effective overflowed circuit traffic.
- Served Packet Traffic (kbps): The Served Packet Traffic is the packet-switched traffic in kilobits per second
that the subcell can serve.
- The served packet-switched traffic is packet traffic demand less the effective overflowed packet traffic.
- Effective Rate of Traffic Overflow (%): The Effective Rate of Traffic Overflow is the actual rate of traffic
that is rejected by the subcell and overflows because of a lack of packet timeslots. In a GSM network, the value
is the same as the blocking probability. In a more complex network, this value includes the traffic overflow from
all services.
In case of Erlang B, the effective rate of traffic overflow corresponds to the effective blocking rate. This value
is calculated from the required number of circuit timeslots (both shared and circuit timeslots) and the circuit
traffic demand in Erlang B tables.
In case of Erlang C, the effective rate of traffic overflow is zero except if the maximum number of TRXs is ex-
ceeded. The effective blocking rate is inferred from the required number of circuit timeslots (both shared and
circuit timeslots) and the circuit traffic demand in Erlang C tables.
- Probability of Circuit Blocking Rate (or Delay) (%): The Circuit Blocking Rate is the grade of service
(GoS) indicator for circuit-switched traffic. It can be either the rate at which calls are blocked (Erlang B) or
delayed (Erlang C), depending on which queuing model the dimensioning model uses.
- Minimum Throughput Reduction Factor (%): The Minimum Throughput Reduction Factor is the lowest
throughput reduction factor that can still guarantee service availability. The Minimum Throughput Reduction
Factor is one of the criteria for packet-switched traffic dimensioning. It is calculated using the parameters
defined for the services: the minimum service throughput; the maximum number of timeslots per connection;
the required availability; and the per pixel timeslot capacity of the subcell coverage area. This parameter is
calculated when making the traffic capture on which the KPI calculation is based.
- Throughput Reduction Factor (%): The Throughput Reduction Factor is calculated from the quality charts
using the packet load and available connections for each subcell. This reduction factor must be greater than
the minimum throughput reduction factor for packet-switched services for these services to be satisfactorily
available in the subcell.
- Maximum Packet Delay (s): The Maximum Packet Delay is the defined delay in seconds that must not be
exceeded for the service quality to be considered satisfactory.
- Packet Delay (s): The Delay is a key performance indicator (KPI) calculated using the quality graphs, the
load, and the number of connections available . This dimensioning output must not exceed the maximum delay
defined for the service for service availability to be considered satisfactory.
- Maximum Probability of Packet Delay (%): The Maximum Probability of Packet Delay is defined for each
packet service and is the highest probability that the service will be blocked that is acceptable in terms of
service availability.
- Probability of Packet Delay (Delay) (%): The Probability of Packet Delay is a dimensioning output and
must not exceed the Maximum Probability of Packet Delay defined for the service for service availability to
be considered satisfactory.
7. Click Commit to assign the load and the effective rate of traffic overflow to the subcells.
Note: KPI calculation is based on a traffic capture. Modifications to traffic maps, traffic
parameters, and transmitter properties (e.g., calculation area, Coding Scheme
Configuration, etc.) have an influence on the traffic capture. Therefore, if you modify some
of these data, you must recalculate the traffic capture before calculating KPIs.
Note: If you are importing more than one file, you can select contiguous files by clicking the first
file you want to import, pressing SHIFT and clicking the last file you want to import. You
can select non-contiguous files by pressing CTRL and clicking each file you want to
import.
Note: Files with the extension PLN, as well as some FMT files (created with previous versions of
TEMS) are imported directly into Atoll; you will not be asked to define the data structure
using the Import of Measurement Files dialogue.
6. If you already have an import configuration defining the data structure of the imported file or files, you can select
it from the Configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have
an import configuration, continue with step 7.
a. Under Configuration, select an import configuration from the Configuration list.
b. Continue with step 10.
Notes:
When importing a test mobile data path file, existing configurations are available in the Files
of type list of the Open dialogue, sorted according to their date of creation. After you have
selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises
the extension. In case several configurations are associated with an extension, Atoll chooses
the first configuration in the list.
The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in
the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see
the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters:
- Name: By default, Atoll names the new test mobile data path after the imported file. You can change this
name if desired.
- Under Receiver, set the Height of the receiver antenna and the Gain and Losses.
- Under Measurement Conditions,
- Units: Select the measurement units used.
- Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document.
If the coordinates used in the file you are importing are different than the coordinates used in the Atoll
document, you must click the Browse button ( ) and select the coordinate system used in the test
mobile data file. Atoll will then convert the data imported to the coordinate system used in the Atoll docu-
ment.
8. Click the Setup tab (see Figure 7.62).
Figure 7.62: The Setup tab of the Import of Measurement Files dialogue
a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Dec-
imal Symbol used in the file.
b. Click Setup to link file columns and internal Atoll fields. The Test Mobile Data Configuration dialogue ap-
pears.
c. Select the columns in the imported file that give the X-Coordinates and the Y-Coordinates of each point in
the test mobile data file.
Note: You can also identify the columns containing the XY coordinates of each point in the test
mobile data file by selecting them from the Field row of the table on the Setup tab.
d. In the BCCH Identifier box, enter a string that must be found in the column names identifying the BCCH of
the scanned subcells. For example, if the string "BCCH" is found in the column names identifying the scram-
bling code group of scanned cells, enter it here. Atoll will then search for columns with this string in the column
name.
If there is BCCH information contained in the test mobile data file, leave the BCCH Identifier box empty.
e. In the BSIC Identifier box, enter a string that must be found in the column names identifying the BSIC of the
scanned subcells. For example, if the string "BSIC" is found in the column names identifying the BSIC of the
scanned subcells, enter it here. Atoll will then search for columns with this string in the column name.
f. From the BSIC Format list, select the scrambling code format, either "Decimal" or "Octal."
g. Click OK to close the Test Mobile Data Configuration dialogue.
Important:
If you have correctly entered the information under File on the Setup tab, and the necessary
values in the Test Mobile Data Configuration dialogue, Atoll should recognize all columns in
the imported file. If not, you can click the name of the column in the table in the Field row and
select the column name. For each field, you must ensure that each column has the correct data
type in order for the data to be correctly interpreted. The default value under Type is "<Ignore>".
If a column is marked with "<Ignore>", it will not be imported.
The data in the file must be structured so that the columns identifying the BCCH and the BSIC
are placed before the data columns for each subcell. Otherwise Atoll will not be able to properly
import the file.
9. If you wish to save the definition of the data structure so that you can use it again, you can save it as an import
configuration:
a. On the Setup tab, under Configuration, click Save. The Configuration dialogue appears.
b. By default, Atoll saves the configuration in a special file called "NumMeasINIfile.ini" found in Atolls installa-
tion folder. In case you cannot write into that folder, you can click Browse to choose a different location.
c. Enter a Configuration Name and an Extension of the files that this import configuration will describe (for ex-
ample, "*.csv").
d. Click OK.
Atoll will now select this import configuration automatically every time you import a test mobile data path file
with the selected extension. If you import a file with the same structure but a different extension, you will be
able to select this import configuration from the Configuration list.
Notes:
You do not have to complete the import procedure to save the import configuration and have
it available for future use.
When importing a CW measurement file, you can expand the NumMeasINIfile.ini file by clicking
the button ( ) in front of the file in the Setup part to display all the available import configura-
tions. When selecting the appropriate configuration, the associations are automatically made
in the table at the bottom of the dialogue.
You can delete an existing import configuration by selecting the import configuration under
Setup and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The
mobile data are imported into the current Atoll document.
Notes:
Fast Display forces Atoll to use the lightest symbol to display points. Fast Display is
useful when you have a very large amount of points which would require a great amount of
computer resources to display.
Using Multiple Shading on symbols is possible only if the Fast Display check box is
cleared.
You can sort test mobile data paths in alphabetical order on the Data tab of the Explorer
by selecting Sort Alphabetically from the Test Mobile Data context menu.
You can export the display settings of a test mobile data path. Colours, symbols, and other
display settings can be saved in a .cfg file to make them available for use on another test
mobile data path. To access the import/export interface, click the Actions button on the
Display tab of the path property dialogue. You can then import the configuration file by
selecting Tools > User Configuration > Import.
Note: You can permanently delete the points located in the clutter classes whose check boxes
you clear by selecting the Delete Points Outside Filter check box.
4. Select Properties from the context menu. The Properties dialogue appears.
5. Click the Filter tab.
6. Click More. The Filter dialogue appears.
7. Click the Filter tab:
a. Select a Field from the list.
b. Under Values to Include, you will find all the values represented in the selected field. Select the check boxes
next to the values you want to include in the filter. Click Clear All to clear all check boxes.
8. Click the Advanced tab:
a. In the Column row, select the name of the column to be filtered on from the list. Select as many columns as
you want (see Figure 7.63).
b. Underneath each column name, enter the criteria on which the column will be filtered as explained in the fol-
lowing table:
9. Click OK to filter the data according to the criteria you have defined.
Combinations of filters are first made horizontally, then vertically. For more information on filters, see "Advanced
Data Filtering" on page 71.
Note: The Refresh Geo Data option available in the context menu of Test Mobile Data paths
enables you to update heights (Alt DTM, Clutter height, DTM+Clutter) and the clutter class
of test mobile data points after adding new geographic maps or modifying existing ones.
a. Click the Condition tab. At the top of the Condition tab, you can set the range of signal level to be considered.
You can click the arrow button ( ) and select one of the following thresholds:
- Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception
threshold specified for each subcell (including the defined power reduction) as the lower end of the signal
level range.
- Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold
to be used for all subcells as the lower end of the signal level range.
b. Under Server, select "All" to consider all servers.
c. If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
d. You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
e. You can select which TRX type to consider by selecting it from the Reception from Subcells list.
Coverage by C/I:
a. Click the Condition tab. On the Condition tab, you can define the signals that will be considered for each pixel.
You can click the arrow button ( ) and select one of the following thresholds:
- Subcell Reception Threshold: Select Subcell Reception Threshold if you want to use the reception
threshold specified for each subcell (including the defined power reduction) as the lower end of the signal
level range.
- Specified Reception Threshold: Select Specified Reception Threshold if you want to enter a threshold
to be used for all subcells as the lower end of the signal level range.
b. Under Server, select "HCS servers" to take the best signal level by HCS layer on each pixel into consideration,
assuming this signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer
level or specifically for each transmitter. When you select "Best Signal Level per HCS Layer" or "All," there
might be areas where several transmitters experience interference. On these pixels, several CI values are
calculated. Therefore, on the Display tab, you select to display either the lowest CI level or the highest CI level
(for more information, see "Comparing Service Areas in Calculations" on page 386).
c. Enter a hand-over margin in the With a Margin text box. The default value is "4 dB."
d. If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability. Shadowing margins (depending on the entered cell edge coverage probability and the model standard
deviation per clutter class) are applied to the values for C.
e. You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
f. Under Interference Condition, You can select which TRX type to consider as potential victim by selecting it
from the Interfered Subcells list. Click the arrow button ( ) and select one of the following thresholds:
- Subcell C/I Threshold: Select Subcell C/I Threshold if you want to use the CI threshold specified for
each subcell (including the defined power reduction) as the lower end of the CI range.
- Specified C/I Threshold: Select Specified C/I Threshold if you want to enter a threshold to be used for
all subcells as the lower end of the CI range.
g. Select either CI or C(I+N).
h. Click the arrow button ( ) and select one of the following thresholds:
- Subcell C/I Threshold: Select Subcell C/I Threshold if you want to use the CI threshold specified for
each subcell (including the defined power reduction) as the upper end of the CI range.
- Specified C/I Threshold: Select Specified C/I Threshold if you want to enter a threshold to be used for
all subcells as the upper end of the CI range.
Note: You can not select Subcell C/I Threshold as both the lower and the upper end of the CI
range to be considered.
i. Select whether you want the defined interference condition to be Satisfied By:
- At least one TRX: When you select the option At least one TRX, the defined interference condition must
be satisfied by at least one TRX on a given pixel for the results to be displayed on that pixel.
- The worst TRX: When you select the option The worst TRX, Atoll selects the worst results for each pixel.
If the worst results do not satisfy the defined interference condition, the results will not be displayed on
that pixel.
j. If you have selected "C/(I+N)", you can define the value to be added to the interference. The defined noise
figure is added to the thermal noise value (defined at -121 dBm) to calculate the value of N. Select one of the
following:
- Based on Terminal: Select Based on Terminal if you want to use the noise figure defined for a terminal
and select the terminal from the list.
- Fixed Value: Select Fixed Value if you want to enter a value and then enter the noise figure in the text
box.
k. If you want discontinuous transmission mode for TRXs which support it taken into account during the calcula-
tion of interference, select the DTX taken into account check box and enter the percentage of time during
which a user is talking in the Voice Activity Factor text box.
l. Select the Traffic Load that will be used to calculate interference:
- 100 %: The maximum traffic load (subcells entirely loaded)..
- From subcell table: The subcell traffic load as defined or as calculated during dimensioning.
m. Select in the Interference Sources scrolling box whether the interference should be calculated from adjacent
channels, co-channels, or from both. The adjacent channel effect on the concerned victim channel, i.e., the
interference, is decreased by the adjacent channel protection level.
You may even select interferences coming from an external project using another technology. For more infor-
mation, see "GSM/GPRS/EGPRS Interfered networks" on page 239.
If you want Atoll to take interference due to intra-technology third order intermodulation into consideration
when calculating the total interference, you must set up your document and database as explained in "Taking
Intermodulation Interference into Consideration in Calculations" on page 407.
n. Select the Detailed Results check box if you want to display detailed results per transmitter. The results dis-
played depend on the subcell frequency hopping mode:
- Non-Hopping Mode: The results are displayed for one channel of each TRX in non-hopping mode.
- Base Band Hopping Mode: The results are displayed for the MAL of each subcell in base band hopping
mode.
- Synthesised Frequency Hopping Mode: The results are displayed for the MAL-MAIO of each subcell in
synthesised frequency hopping mode.
6. When you have finished setting the parameters for the coverage prediction, click OK.
You can create a new coverage prediction by repeating the procedure from step 1. to step 6. for each new cover-
age prediction.
7. When you have finished creating new coverage predictions for these test mobile data, right-click the test mobile
data. The context menu appears.
8. Select Calculations > Calculate All the Studies from the context menu.
A new column for each coverage prediction is added in the table for the test mobile data. The column contains the
predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned
to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Managing Calcu-
lations in Atoll).
You can display the information in these new columns in the Test Mobile Data window. For more information on
the Test Mobile Data window, see "Analysing Data Variations Along the Path" on page 380.
Note: Atoll can display the seven servers per point. If you want to display for example, the point
signal level, remember to select the check box for the point signal level for all servers in
the For the Fields list. The new column will then display the point signal level for the
selected transmitter for all servers if a value exists.
8. Click OK. Atoll creates a new column in the test mobile path data table for the selected transmitters and with the
selected values.
5. Click Display at the top of the Test Mobile Data window. The Display Parameters dialogue appears (see
Figure 7.65).
Note: You can change the display status or the colour of more than one field at a time. You can
select contiguous fields by clicking the first field, pressing SHIFT and clicking the last field
you want to import. You can select non-contiguous fields by pressing CTRL and clicking
each field. You can then change the display status or the colour by right-clicking on the
selected fields and selecting the choice from the context menu.
The selected fields are displayed in the Test Mobile Data window.
7. You can display the data in the test mobile path in two ways:
- Click the values in the Test Mobile Data window.
- Click the points on the test mobile path in the map window.
The test mobile data path appears in the map window as an arrow pointing towards the serving cell, with a number
identifying the best server (see on page 380). If the transmitter display type is "Automatic," both the number and
the arrow are displayed in the same colour as the transmitter. For information on changing the display type to
"Automatic," see "Defining the Display Type" on page 34.
8. You can display a second Y-axis on the right side of the window in order to display the values of a variable with
different orders of magnitude than the ones selected in the Display Parameters dialogue. You can select the sec-
ondary Y-axis from the right-hand list on the top of the Test Mobile Data window. The selected values are dis-
played in the colours defined for this variable in the Display Parameters dialogue.
9. You can change the zoom level of the Test Mobile Data window display in the Test Mobile Data window in the
following ways:
- Zoom in or out:
i. Right-click the Test Mobile Data window.
ii. Select Zoom In or Zoom Out from the context menu.
- Select the data to zoom in on:
i. Right-click the Test Mobile Data window on one end of the range of data you want to zoom in on.
ii. Select First Zoom Point from the context menu.
iii. Right-click the Test Mobile Data window on the other end of the range of data you want to zoom in on.
iv. Select Last Zoom Point from the context menu. The Test Mobile Data window zooms in on the data be-
tween the first zoom point and the last zoom point.
10. Click the data in the Test Mobile Data window to display the selected point in the map window. Atoll will recentre
the map window on the selected point if it is not presently visible.
Tip: If you open the table for the test mobile data you are displaying in the Test Mobile Data
window, Atoll will automatically display in the table the data for the point that is displayed
in the map and in the Test Mobile Data window (see Figure 7.64 on page 380).
a. Select Print from the context menu. The Print dialogue appears.
b. Click OK to print the contents of the Test Mobile Data window.
7.7.1.1 Frequencies
In GSM/GPRS/EDGE projects, you can manage frequencies by defining frequency domains and groups based on stand-
ard frequency bands. A frequency domain consists of one or several frequency groups. The frequency domain in turn
belongs to a frequency band. A frequency group is a set of channels. A frequency group can belong to one or several
frequency domains.
Frequency planning, both manual and automatic, is based on the frequency domains assigned to the TRX types in defined
cell types.
In this section, the following are explained:
"Defining Frequency Bands" on page 382
"Defining Frequency Domains and Groups" on page 383.
4. In the row marked with the New Row icon ( ), enter the following parameters to define a frequency band (for
information on working with data tables, see "Working with Data Tables" on page 50):
- Name: Enter a name for the frequency, for example, "GSM 1900." This name will appear in other dialogues
when you select a frequency band.
- Frequency (MHz): Enter the average frequency.
- Channel Width (kHz): Enter the width, in kHz, that each channel will cover.
- First Channel: Enter the number of the first channel in this frequency band.
- Last Channel: Enter the number of the last channel in this frequency band.
- Excluded Channels: Enter the channels that will not be included in this frequency band, even though they
are between the first and last channels.
- Multiplexing Factor: Enter the multiplexing factor of the frequency band. The user multiplexing factor corre-
sponds to the number of timeslots in a GSM/GPRS/EDGE frame.
- Max Channel Number: Enter the maximum channel number after which the channel number count restarts
at 0. The GSM 900 frequency band in Atoll includes the P-GSM (primitive GSM), R-GSM (GSM for railways),
and E-GSM (extended GSM) bands, i.e., channels from 1 to 124 (P-GSM), from 955 to 974 (R-GSM), and
from 975 to 1023 and 0 (E-GSM). The channel numbers 0 and 1023 will be considered adjacent if you enter
a Max Channel Number of 1024 for this frequency band.
Notes: You can also modify the properties of a frequency band using its Properties dialogue.
You can open the frequency band Properties dialogue by selecting the frequency band in
the Frequency Bands table and clicking the Properties button. The frequency band
Properties dialogue has a General tab which allows you to modify the properties
described above, a Frequency Domains tab which indicates the frequency domains that
belong to the frequency band, and, if user-defined fields have been added to the
Frequency Bands table, an Other Properties tab.
The absolute radio frequency channel numbers are determined in Atoll with the following equation:
ARFCN of X = First Channel Number + (Channel Frequency of X - First Channel Frequency) / 200 kHz
4. In the row marked with the New Row icon ( ), enter the following parameters to define a frequency domain (for
information on working with data tables, see "Working with Data Tables" on page 50):
- Name: Enter a name for the frequency domain, for example, "GSM 1900 domain." This name will appear in
other dialogues when you select a frequency domain.
- Frequency Band: Select the frequency band the domain will belong to from the list.
5. Select the row containing the frequency domain and click the Properties button. The frequency domains Prop-
erties dialogue appears.
In the frequency domains Properties dialogue, you can modify the properties of the frequency domain and create
frequency groups.
6. Under Groups, in the row marked with the New Row icon ( ), enter the following parameters to define a fre-
quency group (for information on working with data tables, see "Working with Data Tables" on page 50):
- Name: Enter a name for the frequency group, for example, "GSM 1900 domain Group1." This name will
appear in other dialogues when you select a frequency group.
- Min.: Enter the number of the first channel in this frequency group.
- Max.: Enter the number of the last channel in this frequency group.
- Step: Enter the value interval between channels in this frequency group.
- Excluded: Enter the channels that you do not want to use in this frequency group. You can enter or paste a
list of channels; the values must be separated with either a comma, or a semi-colon, or a space. You can also
enter a range of channels to be excluded from this group, by entering the first and last channel of the range
separated by a hyphen. For example, entering 520-525 corresponds to entering 520 521 522 523 524 525.
- Extra: Enter the additional channels, outside the first and last channels of the group, that you want to use in
this frequency group. You can enter or paste a list of channels; the values must be separated with either a
comma, or a semi-colon, or a space. You can also enter a range of channels to be excluded from this group,
by entering the first and last channel of the range separated by a hyphen. For example, entering 520-525 cor-
responds to entering 520 521 522 523 524 525.
7. Click OK to close the frequency domains Properties dialogue.
8. Click Close to close the Frequency Domains table.
Notes: You can associate frequency groups to frequency domains using the Frequency Groups
table. You can open the Frequency Groups table by right-clicking the Transmitters
folder and selecting Network Settings > Frequencies > Groups from the context menu.
Although each group name in a single frequency domain must be unique, you can use the
same group name in different frequency domains.
7.7.1.2 BSICs
In GSM/GPRS/EDGE, the Base Station Identity Code (BSIC) is assigned to a BCCH to identify the transmitter on which
the BCCH is located. BSICs are made available according to country and area. The mobile uses the BSIC, which can be
in either decimal or octal format, to distinguish one BCCH from BCCHs on nearby transmitters. The BSIC is composed of
a Network Colour Code (NCC) and a BTS Colour Code (BCC). BSICs are modelled using domains and groups which can
be defined and modified:
A domain consists of one or more groups.
A group is a defined set of BSICs. A BSIC group can belong to one or more BSIC domains.
The resulting value is the BSIC in decimal format. For example, the NCC-BCC pair 3-2 results in a decimal BSIC
value of 26.
Octal format: Both the NCC and the BCC are already in octal format (using the numbers from 0 to 7), so they can
be combined directly to express the resulting BSIC. For example, the NCC-BCC pair 3-2 results in an octal BSIC
value of 32. The octal format is more commonly used than the decimal format.
In Atoll, you define the format globally for the entire GSM/GPRS/EDGE document.
Important: When you import test mobile data, you must ensure that the defined BSIC format is the
same as that of the test mobile data before you import the data.
4. In the row marked with the New Row icon ( ), enter the name of the new BSIC domain.
5. Select the row containing the BSIC domain and click the Properties button. The BSIC domains Properties dia-
logue appears.
In the BSIC domains Properties dialogue, you can modify the properties of the BSIC domain and create BSIC
groups.
6. Under Groups, in the row marked with the New Row icon ( ), enter the following parameters to define a BSIC
group (for information on working with data tables, see "Working with Data Tables" on page 50):
Important: When defining the BSIC group, ensure that the entered values are consistent with the
defined BSIC format (see "Defining the BSIC Format" on page 384).
- Name: Enter a name for the BSIC group. This name will appear in other dialogues when you select a BSIC
group.
- Min.: Enter the first BSIC in this BSIC group.
- Max.: Enter the last BSIC in this BSIC group.
- Step: Enter the value interval between BSICs in this BSIC group.
- Excluded: Enter the BSICs that you do not want to use in this BSIC group. You can enter or paste a list of
BSICs; the values must be separated with either a comma, or a semi-colon, or a space. You can also enter a
range of BSICs to be excluded from this group, by entering the first and last BSIC of the range separated by
a hyphen. For example, entering 0-5 corresponds to entering 0 1 2 3 4 5.
- Extra: Enter the additional BSICs, outside the first and last BSICs of the group, that you want to use in this
BSIC group. You can enter or paste a list of BSICs; the values must be separated with either a comma, or a
semi-colon, or a space. You can also enter a range of BSICs to be excluded from this group, by entering the
first and last BSIC of the range separated by a hyphen. For example, entering 0-5 corresponds to entering 0
1 2 3 4 5.
7. Click OK to close the BSIC domains Properties dialogue.
8. Click Close to close the BSIC Domains table.
Note: You can associate frequency groups to frequency domains using the BSIC Groups table.
You can open the BSIC Groups table by right-clicking the Transmitters folder and
selecting Network Settings > BSICs > Groups from the context menu.
4. In the row marked with the New Row icon ( ), enter the name of the new HSN domain.
5. Select the row containing the HSN domain and click the Properties button. The HSN domains Properties dia-
logue appears.
In the HSN domains Properties dialogue, you can modify the properties of the HSN domain and create HSN
groups.
6. Under Groups, in the row marked with the New Row icon ( ), enter the following parameters to define a HSN
group (for information on working with data tables, see "Working with Data Tables" on page 50):
- Name: Enter a name for the HSN group. This name will appear in other dialogues when you select a HSN
group.
- Min.: Enter the first HSN in this HSN group.
- Max.: Enter the last HSN in this HSN group.
- Step: Enter the value interval between HSNs in this HSN group.
- Excluded: Enter the HSNs that you do not want to use in this HSN group. You can enter or paste a list of
HSNs; the values must be separated with either a comma, or a semi-colon, or a space. You can also enter a
range of HSNs to be excluded from this group, by entering the first and last HSN of the range separated by a
hyphen. For example, entering 0-5 corresponds to entering 0 1 2 3 4 5.
- Extra: Enter the additional HSNs, outside the first and last HSNs of the group, that you want to use in this HSN
group. You can enter or paste a list of HSNs; the values must be separated with either a comma, or a semi-
colon, or a space. You can also enter a range of HSNs to be excluded from this group, by entering the first
and last HSN of the range separated by a hyphen. For example, entering 0-5 corresponds to entering 0 1 2 3
4 5.
7. Click OK to close the HSN domains Properties dialogue.
8. Click Close to close the HSN Domains table.
Note: You can associate frequency groups to frequency domains using the HSN Groups table.
You can open the HSN Groups table by right-clicking the Transmitters folder and
selecting Network Settings > HSNs > Groups from the context menu.
The priority and layer reception threshold are used to determine the best server on each pixel. When there are several
possible transmitters, the best server will be determined by the priority. If there are transmitters on different layers having
the same priority, the transmitter for which the difference between the received signal level and the layer reception thresh-
old will be selected as the best server. Transmitters whose received signal level is below the layer reception threshold will
be ranked by signal level, but will not be chosen as best server. The HCS layer reception threshold is considered only if
no specific HCS layer reception threshold has been defined at the transmitter level (on the General tab of the transmitters
Properties dialogue).
Note: You can set Atoll to select the transmitter with the highest received signal level as the
serving transmitter by changing an option in the atoll.ini file. For more information on
changing options in the atoll.ini file, see the Administrator Manual.
The maximum speed is used to select HCS layer users according to the speed defined in the mobility.
To define HCS layers:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Network Settings > HCS Layers. The HCS Layers table appears.
4. In the row marked with the New Row icon ( ), enter the following parameters to define a HCS layer (for infor-
mation on working with data tables, see "Working with Data Tables" on page 50):
- Name: Enter a name for the HCS layer. This name will appear in other dialogues when you select a HCS layer.
- Priority: Enter a priority for the HCS layer. "0" is the lowest priority.
- Max. Speed (km/h): Enter a maximum mobility speed for the HCS layer.
- Layer Reception Threshold (dBm): Enter a default layer reception threshold in dBm. This threshold may be
used as a border for the considered HCS layer in some studies when the HCS server option is selected.
Name Priority (0:Lowest) Max Speed (km/h) Layer Reception Threshold (dBm)
Macro Layer 2 100 -90
The subcell reception threshold is -102 dBm for the micro cells and -105 dBm for the macro and the umbrella cells. Three
mobility types are defined in this project: Pedestrian (3km/h), 50 km/h and 90 km/h
The resulting services areas are displayed in the following graphics for each selection.
All: All servers are taken into consideration
Composite Coverage
Figure 7.66 shows the service areas of all the transmitters without any layers taken into consideration. Each cell is consid-
ered individually and the limit of its coverage is defined by its subcell reception thresholds. Overlapping is possible between
transmitters and between HCS layers.
Best Signal Level: The best signal level from all servers on all layers is taken into consideration.
Composite Coverage
Figure 7.67 shows the service areas of the transmitters having the best signal level on each pixel, without any layer taken
into consideration. Cells are in competition if their calculated signal level is higher than the subcell reception thresholds.
Overlapping between transmitters and between HCS layers is not possible.
Best Signal Level per HCS Layer: The best signal level from all servers on each HCS layer is taken into consid-
eration.
Composite Coverage
Figure 7.68 shows the service areas of the transmitters having the best signal level on each pixel, for each HCS layer.
Cells are in competition per layer if their computed signal level is higher than its subcell reception thresholds. Overlapping
between HCS layers is possible, but overlapping between transmitters on a given HCS layer is not possible.
HCS Servers: The best signal level by HCS layer on each pixel is taken into consideration, assuming the signal
level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level or specifically for
each transmitter.
Composite Coverage
Figure 7.69 shows the service areas of the transmitters having the best signal level on each pixel, for each HCS layer.
Cells are in competition per layer assuming their calculated signal level is higher than the subcell reception thresholds and
the HCS layer reception threshold. Overlapping between HCS layers is possible, but overlapping between transmitters on
a given HCS layer is not possible.
In the case above, the micro layer overlaps the macro layer and its borders are defined by the max between the subcell
reception thresholds (-102 dBm) and the micro layer threshold (-84 dBm), i.e. -84 dBm. In addition, the macro layer over-
laps the umbrella layer and its borders are defined by the max between the subcell reception thresholds (-105 dBm) and
the macro layer threshold (-90 dBm), i.e. -90 dBm. The umbrella layer is displayed when its signal level exceeds the max
between the subcell reception thresholds and the umbrella layer threshold, i.e. -105 dBm.
Highest Priority HCS Server: The best signal level of all the severs on the highest priority HCS layer are taken
into consideration, assuming the priority of the layer is defined by its priority field and its signal level exceeds the
minimum HCS threshold defined either at the HCS layer level or specifically for each transmitter.
Composite Coverage
Figure 7.70 shows the service areas of the transmitters having the best signal level on each pixel, on the highest priority
HCS layer. The priority HCS layer is the layer for which the priority value is the highest and for which the calculated signal
level is higher than its subcell reception thresholds and the HCS layer reception threshold. Overlapping between HCS
layers and between transmitters of a given HCS layer is not possible.
Note: If two layers have the same priority, the traffic is served by the transmitter for which the
difference between the received signal strength and the HCS threshold is the highest. The
way competition is managed between layers with the same priority can be modified. For
more information, see the Administrator Manual.
Grouped HCS Servers: The best signal level by HCS layer on each pixel is taken into consideration, assuming
the signal level on each layer exceeds the minimum HCS threshold defined either at the HCS layer level or spe-
cifically for each transmitter. The server selection mode is similar to HCS Servers except that If a mobility is sup-
ported by several layers, the traffic is served on the layer with the highest priority
This functionality is not available by default. To add the "Grouped HCS Servers" option in the server scrolling list in the
predictions, the traffic capture and the interference matrix computations, add the following lines in the atoll.ini file:
[TMP]
ExtraServZone = 1
Composite Coverage
Figure 7.69 shows the service areas of the transmitters having the best signal level on each pixel, for each HCS layer.
Cells are in competition per layer assuming their calculated signal level is higher than the subcell reception thresholds and
the HCS layer reception threshold. Overlapping between HCS layers is possible, but overlapping between transmitters on
a given HCS layer is not possible.
In the case above, the micro layer overlaps the macro layer because it has the highest priority with the 3 km?h mobility
and the macro layer has a higher priority than the umbrella layer with mobilities 50 km?h and 90 km?h (which are not
supported by the micro layer). The umbrella layer is displayed when both the micro and the macro layer does not provide
enough signal strength to fulfil the reception threshold conditions
4. In the row marked with the New Row icon ( ), enter the name of the new cell type. This name will appear in
other dialogues when you select a cell type.
5. Select the row containing the cell type and click the Properties button. The cell types Properties dialogue
appears.
In the cell types Properties dialogue, you can add and define the TRX types that will constitute the cell type.
6. Under TRX Types, in the row marked with the New Row icon ( ), enter the following parameters to define a
TRX type (for information on working with data tables, see "Working with Data Tables" on page 50):
- TRX Type: Select a TRX type from the list.
- Frequency Domain: Select a frequency domain from the list. Only channels belonging to this frequency
domain will be allocated to TRXs of this TRX type during automatic or manual frequency planning.
- DL Power Reduction: Enter a value for the reduction of power relative to the transmitter power. The downlink
power reduction can be used to model inner subcells.
- Reception Threshold (dBm): Enter a minimum received signal for this TRX type.
- C/I Threshold (dB): Enter a minimum signal quality for this TRX type. The C/I Threshold can be used in inter-
ference studies and in the AFP.
- DTX Supported: If the TRX type supports DTX (Discontinuous Transmission) technology, select the DTX
Supported check box. Subcells supporting DTX can reduce interference they produce according to the
defined voice activity factor. This option has no impact on BCCH TRX type.
- Timeslot Configuration: Select a timeslot configuration from the list. The timeslot configuration defines the
distribution of circuit, packet and shared timeslots for the subcell, respecting the number of TRXs.
- Half-Rate Traffic Ratio (%): Enter the percentage of half-rate voice traffic in for this TRX type. This value is
used to calculate the number of timeslots required to respond to the voice traffic demand.
Important: The target rate of traffic overflow and the half-rate traffic ratio must be the same for BCCH
and TCH TRX types. If the values are different for BCCH and TCH TRX types, Atoll will
use the values for the target rate of traffic overflow and the half-rate traffic ratio from the
BCCH TRX type.
- Target Rate of Traffic Overflow (%): Enter the target rate of traffic overflow. The target rate of traffic overflow
is used during traffic analysis to distribute the traffic between subcells and layers. The value is the percentage
of candidate traffic overflowing to a subcell with a lower priority. It has an impact on the traffic capture between
inner and outer subcells, and between micro and macro layers. In other words, The target rate of traffic over-
flow can be considered to an estimation of the allowed percentage of traffic rejected from subcells or layers of
higher priority to subcells or layers of lower subcells (see Figure 7.7).
Note: If the traffic overflow target is set to a value lower than the grade of service, it means that
the traffic rejected (according to the queuing model selected in the dimensioning model:
Erlang B or Erlang C) will be lost and will not overflow to other subcells.
- Hopping Mode: Select the frequency hopping mode supported by this TRX type. The hopping mode can be
either "Base Band Hopping mode (BBH)" or "Synthesized Hopping mode (SFH)." If frequency hopping is not
supported, select "Non Hopping."
- Allocation Strategy: Select the allocation strategy used during manual or automatic frequency planning.
There are two available allocation strategies:
- Free: Any of the channels belonging to the frequency domain can be assigned to TRXs.
- Group Constrained: Only channels belonging to a same frequency group in the frequency domain can
be assigned. You can use the Preferred Frequency Group to define the preferred group of frequencies
when using the AFP.
- Max. MAL Length: Enter the maximum length of the mobile allocation list (MAL), in other words, the maximum
number of channels allocated to the TRXs of subcells based on this TRX type during automatic frequency
planning if the Hopping Mode is either SFH (Synthesized Frequency Hopping) or BBH (Base Band Hopping)
and if the Allocation Strategy is Free.
- HSN Domain: Select the HSN domain for this TRX type. Only hopping sequence numbers (HSN) belonging
to the selected HSN domain will be allocated to subcells during automatic or manual frequency planning. The
HSNs are allocated if the Hopping Mode is either SFH (Synthesized Frequency Hopping) or BBH (Base Band
Hopping).
- Freeze HSN: If the HSN assigned to this TRX type is to be kept when a new AFP session is started, select
the Freeze HSN check box.
- AFP Weight: Enter an AFP weight. The AFP weight is used to increase or decrease the importance of a sub-
cell during automatic frequency planning. The value must be a real number. The higher the AFP weight is, the
higher the constraint on the TRX type. The AFP weight artificially mulitplies the cost function which has to be
minimised by the AFP.
- % Max. Interference: Enter the maximum level of interference allowable during automatic frequency plan-
ning. The interference is defined as a percentage of area or traffic, as defined during the calculation of the
interference matrices.
- Mean Power Control Gain (dB): The average reduction in interference due to power control in downlink. This
gain is used when calculating interference generated by the subcell. Interference generated by the subcell is
reduced by this value during C/I calculations.
- Default TRX Configuration: Select the default TRX Configuration for this TRX type. It will apply to all TRXs
belonging to a subcell based on this TRX type. By selecting the default TRX Configuration, the maximum
number of GPRS and EDGE coding schemes is set at the TRX type level. You can also define the TRX Con-
figuration for each TRX.
- EDGE Power Backoff (dB): Enter the average power reduction for EDGE transmitters due to 8PSK, 16QAM
and 32QAM modulations in EDGE. This has an impact on the EDGE service zone which can be seen in traffic
analysis and EDGE predictions.
- Number of Antennas (Transmission Diversity): Enter the number of antennas subcells based on this TRX
type can use for transmission. In most cases, a transmitter will transmit with only one antenna, however, some
transmitters are capable of transmission diversity. By transmitting on more than one antenna, the signal expe-
riences a gain of 3 dB. An additional transmission diversity gain can be defined per clutter class in order to
correctly model gain due to the environment.
Notes: An Other Properties tab is available if user-defined fields have been added to the Cell
Types table.
Interference studies,
Min. C/I x x x
Automatic frequency planning
Traffic analysis,
EDGE Power Backoff x x x
Packet studies
Interference studies,
Min. C/I x x x
Automatic frequency planning
The coding scheme index number is an input in traffic captures (and, therefore, in dimensioning) and in GPRS coverage
predictions. It is important to keep in mind that, before dimensioning, in other words, before TRXs have been allocated to
transmitters, the TRX Configuration defined per subcell is used in calculations. However, once TRXs have been allocated,
the value for TRX Configuration is read from the TRXs. The TRX Configuration, and any parameters or limitations, will
have be defined again for the TRXs. Otherwise, the configuration will not be taken into account during calculations.
In this section, the following is described:
"Creating or Importing TRX Configuration" on page 394.
4. In the row marked with the New Row icon ( ), enter the following parameters to create TRX Configuration (for
information on working with data tables, see "Working with Data Tables" on page 50):
- Name: Select a TRX type from the list.
- Max. GPRS CS: Enter the maximum number of coding schemes that the GPRS-compatible configuration can
use.
- Max. EDGE CS: Enter the maximum number of coding schemes that the EDGE-compatible configuration can
use.
- Comments: You can enter comments in this field if you wish.
If you have TRX Configuration data in text or comma-separated value (CSV) format, you can import it into the TRX config-
uration table in the current document. If the data is in another Atoll document, you can first export it in text or CSV format
and then import it into the TRX configuration table of your current Atoll document. When you are importing, Atoll allows
you to select what values you import into which columns of the table.
To import new TRX Configuration:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Network Settings > TRX Configuration. The TRX configuration table appears. The HSN Domains table
contains a entry called "Standard."
4. Right-click the TRX configuration table. The context menu appears.
5. Select Import from the context menu. For information on importing table data, see "Importing Tables from Text
Files" on page 59.
3. Select Network Settings >Codec Modes >Open Table. The Codec Mode table appears. It shows the following
information:
- Name: Displays the name of the Codec Mode
- Codec Type: Defines a specific type of a speech Coding algorithm, applied on a specific radio access tech-
nology (e.g. FR or AMR)
- Half Rate: yes when selected.
- Power Backoff: yes when selected.
- Max Rate (kbps): Displays the max rate per timeslot corresponding to the selected codec mode.
- Priority: For a given quality,in a non Ideal Link Adaptation Mode, if several codec modes are possible, the
one with the highest priority (highest number) is retained.
Note: You can add new fields to the Codec configuration table by right-clicking the table and
selecting Table Fields from the context menu. The new fields will appear in the Codec
configuration table and on the Other Properties tab of the selected Codec
Configurations Properties dialogue.
- Frequency Hopping: The type of frequency hopping to which this configured codec mode applies. You can
select "All" if you want the adaptation threshold to apply to any type of frequency hopping.
- Frequency Band: The frequency band to which this configured codec mode applies. You can select "All" if
you want it to apply to any frequency band.
- Adaptation Threshold (dB): Enter the adaptation threshold that will be used when the Codec Configuration
does not have the capacity for ideal link adaptation.
Note: You can create a new adaptation threshold by entering the parameters in the row marked
with the New Row icon ( ).
7. Click OK.
Note: You can create a new quality indicator threshold by entering the parameters in the row
marked with the New Row icon ( ).
7. Click OK.
3. Right-click the transmitter to which you want to assign the Codec Configuration. The context menu appears.
4. Select Properties from the context menu. The transmitters Properties dialogue appears.
Note: You can also access a transmitters Properties dialogue by right-clicking the transmitter
on the map and selecting Properties from the context menu.
3. Select Network Settings >Coding Schemes >Coding Scheme Configurations. The Coding Scheme config-
uration table appears.
4. If you are creating new Coding Scheme Configuration, enter the name of the Coding Scheme Configuration in the
row marked with the New Row icon ( ). This name will appear in other dialogues when you select Coding
Scheme Configuration.
If you are modifying existing Coding Scheme Configuration, continue with the following step.
Note: You can add new fields to the Coding Scheme configuration table by right-clicking the
table and selecting Table Fields from the context menu. The new fields will appear in the
Coding Scheme configuration table and on the Other Properties tab of the selected
Coding Scheme Configurations Properties dialogue.
6. In the Coding Scheme configuration table, right-click the record describing the Coding Scheme Configuration
for which you want to define adaptation thresholds. The context menu appears.
7. Select Record Properties from the context menu. The Coding Scheme Configuration Properties dialogue
appears. The Coding Scheme Configuration Properties dialogue has a General tab which allows you to modify
the properties described above.
8. Select the Thresholds tab. Each coding scheme threshold has the following parameters:
- Coding Scheme: The coding scheme.
- Reception Threshold (dBm): The signal level admission threshold for the corresponding coding scheme
when the ideal link adaptation option is cleared in GPRS/EDGE coverage predictions.
- C/I Threshold (dB): The C/I admission threshold for the corresponding coding scheme when the ideal link
adaptation option is cleared in GPRS/EDGE coverage predictions.
- Throughput = f(C) (kbps): The values of the graph defining the throughput per timeslot as a function of C.
You can view the graph and edit its values by selecting the row containing the coding scheme and clicking the
C Graph button.
- Throughput = f(C/I) (kbps): The values of the graph defining the throughput per timeslot as a function of CI.
You can view the graph and edit its values by selecting the row containing the coding scheme and clicking the
CI Graph button.
If interference due to intra-technology third order intermodulation is taken into consideration, Atoll assumes
that the CI graphs include the effect of this interference whereas the C graphs do not.
- Max. Throughput (kbps): The maximum throughput per timeslot using this coding scheme.
- 8PSK Modulation: The 8PSK Modulation check box is selected if this coding scheme supports it. This has
an impact on the EDGE service zone which can be seen in traffic analysis and EDGE predictions.
- EDGE: The EDGE check box is selected if this coding scheme supports EDGE.
- Frequency Hopping: The type of frequency hopping to which this coding scheme applies. You can select
"All" if you want it to apply to all types of frequency hopping.
- Mobility: The mobility to which this coding scheme applies. You can select "All" if you want it to apply to all
mobilities.
- Frequency Band: The frequency band to which this coding scheme applies. You can select "All" if you want
it to apply to all frequency bands.
Note: You can create a new coding scheme threshold by entering the parameters in the row
marked with the New Row icon ( ).
9. Click OK.
Notes
The throughput per timeslot graphs are defined for given frequency hopping mode, mobility
type and frequency band. These graphs will be taken into account in a prediction study if these
parameters correspond to the ones defined in that study. Otherwise, Atoll will use the graphs
for which none of these parameters has been defined. If no such graph exists, Atoll will con-
sider that the corresponding coding scheme is not defined during the calculations.
Note: You can also access a transmitters Properties dialogue by right-clicking the transmitter
on the map and selecting Properties from the context menu.
5. Select Record Properties from the context menu. The Coding Scheme Configuration Properties dialogue
appears.
6. Select the Thresholds tab.
7. Select the coding scheme for which you want to display a throughput graph and click one of the following:
- C Graph: Click the C Graph button to display a graph defining the throughput as a function of C.
- C/I Graph: Click the C/I Graph button to display a graph defining the throughput as a function of CI.
If interference due to intra-technology third order intermodulation is taken into consideration, Atoll assumes that
the CI graphs include the effect of this interference whereas the C graphs do not.
5. Select the row containing the timeslot configuration and click the Properties button. The timeslot configurations
Properties dialogue appears.
Under Mapping between TRX numbers and timeslot configurations, each row corresponds to a distribution of
timeslots and is identified by an index number. During dimensioning, Atoll determines the number of circuit and
packet timeslots required to meet the traffic demand. Atoll uses the timeslot configuration to determine how many
TRXs are needed to meet the need in timeslots. If, during dimensioning, there are not enough index numbers in
the timeslot configuration, Atoll reuses the last index number in the timeslot configuration.
6. In the timeslot configurations Properties dialogue, enter the following information for each index number:
- Number of Shared Timeslots: The number of timeslots that can be used for both circuit-switched (GSM) and
packet-switched (GPRS and EDGE) services.
- Number of Circuit Timeslots: The number of timeslots that can be used only for both circuit-switched (GSM)
services.
- Number of Packet Timeslots: The number of timeslots that can be used only for packet-switched (GPRS
and EDGE) services.
Note: In GSM/GPRS/EDGE the total number of timeslots per index number must not exceed 8
for timeslot configurations intended for TCH TRXs and 7 for timeslot configurations
intended for BCCH TRXs.
Note: You can also access a transmitters Properties dialogue by right-clicking the transmitter
on the map and selecting Properties from the context menu.
Note: You can also access a transmitters Properties dialogue by right-clicking the transmitter
on the map and selecting Properties from the context menu.
8. Click the Antennas tab. You can set the following parameters:
- Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added to
the altitude of the site as given by the DTM. If the transmitter is situated on a building, the height entered must
include the height of building.
- Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the
Browse button ( ) to access the properties of the antenna. The other fields, Azimuth, Mechanical Down-
tilt, and Additional Electrical Downtilt, display additional antenna parameters.
- Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column and
enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power, which is the per-
centage of power reserved for this particular antenna. For example, for a transmitter with one secondary
antenna, if you reserve 40% of the total power for the secondary antenna, 60% is available for the main
antenna.
9. Click the Propagation tab. On the Propagation tab, you can modify the following: the Propagation Model, Radius,
and Resolution for both the Main Matrix and the Extended Matrix.
10. Click OK.
Note: To create a multi-band template, you must have an appropriate multi-band cell type to
assign to the template. If you have not already created a multi-band cell type, you must do
so before creating the template. For information on creating a cell type, see "Creating a
Cell Type" on page 390.
It is assumed that you have already set the multi-band transmitter option in the atoll.ini file and restarted Atoll before begin-
ning this procedure.
To create a multi-band template:
1. In the Radio toolbar, click the arrow to the right of the list of templates.
2. Select Manage Templates from the list. The Station Template Properties dialogue appears.
3. Under Station Templates, select the station template that most closely resembles the station template you want
to create and click Add. The Properties dialogue appears.
4. Create the multi-band template:
a. Click the General tab of the Properties dialogue.
b. In the Name text box, give the template a descriptive name.
c. From the Cell Type list, select the multi-band cell type that corresponds to the type of station template you are
creating.
d. Make any other necessary changes to the station template parameters. For information on the parameters
available, see "Creating or Modifying a Station Template" on page 258.
e. When you have finished setting the parameters for the station template, click OK to close the dialogue and
save your changes.
5. Set the propagation parameters for each frequency band in the multi-band template:
a. Select the multi-band template you have just created and click Add. Because the station template you select-
ed is a multi-band template, the New Station Template dialogue appears with the following options (see
Figure 7.72):
- Add a new station template: If you select this option and click OK, Atoll creates a new station template
based on the selected one.
- Add a new multi-band station template for the frequency band: If you select this option and click OK,
Atoll allows you to set the propagation parameters for the selected frequency band.
b. Select Add a new multi-band station template for the frequency band, choose a frequency band from the
list and click OK. A properties dialogue appears where you can set the antenna and propagation parameters
for the selected frequency band (see Figure 7.73):
- Under Main Antenna, you can modify the following: the antenna Model, 1st Sector Azimuth, from which
the azimuth of the other sectors are offset to offer complete coverage of the area, the Height of the an-
tenna from the ground (i.e., the height over the DTM; if the transmitter is situated on a building, the height
entered must include the height of building), the Mechanical Downtilt, and the Additional Electrical
Downtilt.
- Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for
both the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5:
Managing Calculations in Atoll.
6. Click OK. The properties defined for the frequency band appear in the Station Template Properties dialogue with
a name composed of the multi-band template they belong to followed by the frequency band, separated by "@".
7. Repeat step 5. for every frequency band modelled by the multi-band template.
Note: You can modify the properties of an existing service by right-clicking the service in the
Services folder and selecting Properties from the context menu.
Note: You can modify the properties of an existing mobility type by right-clicking the mobility
type in the Mobility Types folder and selecting Properties from the context menu.
Note: You can modify the properties of an existing terminal by right-clicking the terminal in the
Terminals folder and selecting Properties from the context menu.
- Coding Scheme Configuration: If the terminal is GPRS or EDGE-compatible, select the GPRS configuration
for the terminal. This parameter is optional.
- Max. GPRS CS: If the terminal is GPRS-compatible, the maximum number of coding schemes that the ter-
minal can use.
- Max. EDGE CS: If the terminal is EDGE-compatible, the maximum number of coding schemes that the ter-
minal can use.
Note: The highest number of GPRS (resp. EDGE) coding schemes available to the terminal is
limited by the maximum number of GPRS (resp. EDGE) coding schemes defined for the
TRX Configuration assigned to a transmitter.
- Number of DL Timeslots: If the terminal is GPRS or EDGE-compatible, you can enter the maximum number
of downlink timeslots the terminal can use. Terminals using only circuit-switched services will use only one
downlink timeslot. Using more than DL timeslot has an effect in the dimensioning process (See "Dimensioning
a GSM/GPRS/EDGE Network" on page 317 for more information).
- Number of Simultaneous Carriers: If the terminal is EDGE evolution compatible (EGPRS2), you can enter
the maximum number of simultaneous carriers the terminal can use. Terminals using either circuit-switched
services, GPRS or EGPRS packet-switched will use only one carrier at a time. Using more than one carrier
has an effect in the dimensioning process (See "Dimensioning a GSM/GPRS/EDGE Network" on page 317
for more information).
Note: The modelling of EDGE Evolution on the terminal side has to consider:
- The support of high order modulations and the use of turbo codes in specific coding
schemes which can be found in the appropriately selected GPRS/EDGE Configuration
- The support of multi-carriers which can be setup on the terminal side
- The support of dual antenna terminals (Mobile Station Receive Diversity) and
enhanced single antenna terminals (Single Antenna Interference Cancellation). Atoll
a statistical modelling of these through the use of an EDGE evolution configuration,
with the effect of SAIC or diversity already included both in the coding scheme admis-
sion thresholds and on the Throughput vs C (resp. C/I) graphs.
6. Click OK.
Atoll
RF Planning and Optimisation Software
Chapter 8: The Atoll AFP Module
Note: The AFP cost always starts from the previously calculated cost. For example, once the
AFP results have been committed, if you start a new AFP session with the same settings,
its initial cost will be the final cost of the previous AFP session.
Note: You can also open the Atoll AFP module Properties dialogue by selecting Frequency
Plan > Automatic Allocation from the Transmitters folder on the Data tab of Explorer
window.
The AFP Properties dialogue consists of 10 tabs: General, Cost, Separation Weights, Interference Matrices, HSN, MAL,
Execution, Spacing, Protections, Advanced. The Cost, Separation Weights, Interference Matrices, Protections and
Advanced tabs include parameters that are taken into account when estimating the cost. The Execution tab provides
options on how the AFP should run. The other tabs are used to define the allocation strategies for HSN, MAL, MAIO, and
BSICs assigned by the AFP.
You can make copies of the AFP module and set different parameters for each copy. All copies will be available in AFP
sessions. In other words, you will be able to choose from the list of all AFP modules, each with its own defined parameters.
The settings of each AFP module are saved in the Atoll document but they can also be archived in the database so that
all users connected to the same centralised database can use them.
Note: Using this option leads to longer calculation times. Consequently, using the Intermediate
or Flexible option instead when defining interference will reduce the calculation time.
S12 denotes the required separation between transmitters Tx and Tx in a network. If f is assigned to Tx and f to Tx ,
1 2 1 1 2 2
and if
f1 f2 < S12 then the separation requirement has not been fulfilled.
,
The violation of a separation constraint can be considered as strong or weak. For example, the pair of frequencies (1, 2)
breaks a separation requirement of 3. The pair of frequencies (1, 3) breaks this requirement as well but is still a better
solution than (1, 2), since the separation is 2. Therefore, the second pair should entail a lower cost than the first one.
Furthermore, frequencies that are part of a MAL with a low fractional load and that violate a separation requirement should
not be weighted the same as for a non-hopping separation violation. Therefore, the cost is weighted by the burst collision
probability, which is the multiplication of the victim and interferer fractional loads, and the interferer diversity gain.
For each TRX, separation constraint violations are summed up. The sum is limited to 100% of the TRX traffic. The same
limitation holds true for the interference cost component, i.e., it can cumulate the amount of impaired traffic up to 100% of
the TRX traffic. This means that a TRX with many separation constraint violations is considered 100% impaired and has
a cost component due to interference equal to 0.
Note: The TRX traffic depends on the number of circuit and shared timeslots available and the
TRX traffic load. These parameters are defined in the subcell properties.
For more information, see the AFP Reference Guide.
To set the separation violation cost weights of different types of separation violations:
1. Click the Modules tab in the Explorer window.
2. Click the Expand button ( ) to expand the AFP Modules folder.
3. Right-click the Atoll AFP Module. The context menu appears.
4. Select Properties from the context menu. The Atoll AFP module Properties dialogue appears.
5. Click the Separation Weights tab.
6. Assign weights to Co-transmitter, Co-site, Neighbour, and Exceptional Pair.
7. Under Partial Separation Constraint Violations, part, scroll in the list displaying the requested separation
s,
8. Click on the reached separation k and enter the desired cost value.
Notes:
The higher the violation is, the greater the cost should be.
If the same TRX is involved in several separation violations, its cost will be limited to 100%
(100% of its traffic is interfered).
The separation component can be weighted in the global cost value.
If you want, you can get Atoll to display total and separation costs per TRX, transmitter, and site by adding the following
custom fields to the TRX table, Transmitters table, and Sites table:
Total costs: add the custom field AFP_COST, of type SINGLE to each table you want the costs to appear.
Separation costs: add the custom field AFP_SEP_COST, of type SINGLE to each table you want the costs to
appear.
For information on adding a field to a data table, see "Adding a Field to an Object Types Data Table" on page 51. Once
you have added the custom fields, the total and separation costs can be selected as results from the AFP wizard, under
AFP Indicators.
For each missing or extra TRX compared to the number of required TRXs, Atoll considers that, by default, 100% of the
TRX traffic is impaired. The tax for each missing or extra TRX can be modified in the Cost tab of the Atoll AFP module
Properties dialogue (See "The Atoll AFP Cost Tab" on page 421 for more information).
Consider a transmitter involved in AFP session (not a transmitter to be allocated any resource, TBA) for which the number
of required TRXs is 5. Suppose that this transmitter currently has 3 assigned TRXs. This means that the two missing or
undefined TRXs will have to be considered for this allocation as they would have an effect on the current frequency plan,
if allocated.
Under Tax per TRX, you can indicate the tax to consider when a TRX is missing or in excess. The default tax for a missing
TRX is "1." You can clear the Active check box if you do not want to take this component into account in the global cost.
The value of this tax has a strong effect on the optimisation of the number of required TRXs. This functionality which can
increase or reduce the number of TRXs compared to the number of required TRXs has been implemented in order to
maximise the amount o correctly served traffic. In other words, one may prefer to serve the traffic on perfectly interference
free TRXs than on highly interfered ones. In theory, the Atoll AFP module may reduce the number of TRXs for highly
loaded subcells, and increase this number of subcells having a weak load. If the tax imposed on missing or extra TRXs is
too high, this strategy may not be preferred compared to the other constraints. So, to permit the optimisation of the number
of TRXs, you have to assign a small value to that tax.
The range of frequencies which are permitted for a TRX allocation is defined in the corresponding subcell in the frequency
domain field. In other words, a TRX cannot be assigned channels which do not belong to its subcell. If some TRXs are
assigned such channels, these have to be penalised with a Tax.
By default, Atoll considers 50% of the TRX traffic as cost. The tax for each TRX having frequencies out of its subcell
domain can be modified in the Cost tab of the Atoll AFP module Properties dialogue (See "The Atoll AFP Cost Tab" on
page 421 for more information).
Under Tax per TRX, you can indicate the tax to consider when a TRX is corrupted. The default tax for a TRX having
frequencies out of its subcell domain is 0.5. This value is of course waighted by the fractional load in case of frequency
hopping. You can clear the Active check box if you do not want to take this component into account in the global cost.
When you increase this cost, the AFP minimises the number of TRXs for which a change is made. The goal is to maintain
the existing plan when it is good enough and to concentrate on the TRXs for which the problems have more to do with the
other constraints.
This option is not selected by default and has to be activated in order to be taken into account in the global cost. If this
component is set to active, a multiplicative factor is applied to the TRX traffic (number of timeslots weighted by its traffic
load). The value of this parameter can be modified in the Cost tab of the Atoll AFP module Properties dialogue (See "The
Atoll AFP Cost Tab" on page 421 for more information).
As an example, lets have a network of 90 transmitters out of which 15 are frozen and the number of required TRXs is 257.
193 TRXs are already allocated assuming that their quality is satisfactory. 64 TRXs must be created or allocated with as
little influence as possible on the other 193 TRXs.
The effects of the modified TRX cost can be seen in the following table:
0.3 129
0.1 139
0 162
For a hopping or non-hopping mode, you can set the Group Constrained allocation mode at the subcell level. Introducing
such a constraint forces the Atoll AFP module to assign a complete frequency group to a TRX when the mode is Synthe-
sized Frequency Hopping. The addition to the Preferred Group option defined with its relative cost component weight
guides the AFP module in the choice of a specific frequency group inside the frequency domain of the considered subcell.
In hopping, the frequency set assigned to a TRX is tested to ensure it belongs to the preferred group of the subcell (if
defined). If only a certain percentage of the frequency belongs to this group then an interference event of (1-X/100) will
increment the AFP cost of the TRX.
This option is selected by default but can be deactivated if you do not want to take it into account in the global cost. If this
component is set to active, a multiplicative factor is applied to the TRX traffic (number of timeslots weighted by its traffic
load). The value of this parameter can be modified in the Cost tab of the Atoll AFP module Properties dialogue (See "The
Atoll AFP Cost Tab" on page 421 for more information). The default value for a TRX out of its subcell preferred group is
0.14.
Note: This component is identically used if you choose to assign channels within user-defined
preferred groups or if you try to allocate azymuth-oriented preferred groups (Pattern 1/X).
This strategy has to be selected when starting the AFP session (See "Running an
Automatic Frequency Allocation" on page 336) and the pattern is defined in the
Separation tab of Atoll AFP module Properties dialogue (See "The Atoll AFP Separation
Weights Tab" on page 422 for more information). The value of this component will
encourage or not the possibility to follow (or not) the azymuth-oriented allocation
compared to the other constraints, assuming the AFP algorithm always allocates the best
frequency plan possible by following the user guidelines and its corresponding
compromises to reach it.
Note: The Interferences and Separation components in the Cost tab of the Atoll AFP Module
cannot be deactivated. Nevertheless, the interference cost is only evaluated in the global
AFP cost if some interference matrices are used in the AFP session.
The tab is described in "The Atoll AFP Cost Tab" on page 421.
Example:
For example, in a simple network having only two TRXs, TRXi assigned (MAL)i is interfered by TRXj assigned (MAL)j.
TRXi and TRXj have a separation requirement of 2. Their MAL lengths are 5 and 4 respectively. Unfortunately, they share
the same frequency (separation = 0). Therefore, the cost of the separation violation is 90 for each TRX. The interferer
diversity gain is 1.4 for a MAL of length 5 and 1.2 for a MAL of length 4.
In the interference matrices of the interfered TRXi (or TRXj), the entrance point is shifted by 1.4 dB (or 1.2 dB).
For TRXi with a gain of 1.4 dB, the effect on the separation cost is given by the linear value 10(1.4 10 ) 1.38 . The contri-
bution of the MAL length of 5 divides the separation cost for this interfered MAL by 1.38. When the initial separation cost
( )
and the interference diversity gain are taken into consideration, the separation cost of of 90 1.38 = 65.21 is reached.
If the fractional load (considering the fact that only one channel of each TRX causes interference with (MAL length)i = 5
and (MAL length)j = 4) is now taken into consideration, the collision probability is 1 20 . The separation violation cost to
consider for TRXi is therefore 3.25%.
By the same token, the separation violation cost to consider for TRXj is:
1 90
= 3.41%
20 110.2
10
.
In order to calculate the separation violation cost on each TRX, the current values have to be multiplied by the number of
timeslots dedicated to traffic (by default, 7 in BCCH and 8 for TCH) and by its related traffic load (given in units of Erlangs/
timeslot).
Important: Take care not to mix up voice activity factor in DTX and traffic load. Traffic load represents
the average occupancy of TRXs and is always applied to the value of the cost function (as
defined per subcell during dimensioning).
Notes:
The AFP module will always assign the same MAL to all TRXs in the same subcell.
The Group constrained assignment mode is used for SFH only if no preferred group is
selected per subcell. Otherwise, the assignment mode is free for NH and BBH.
The quality is almost as good as with free assignment when many groups are defined.
You should consider certain trade-offs if you want to get the best results. For example:
When assigning the same HSN and MAL to synchronised subcells, the lowest bound of the MAL length is
increased since it must be equal to or greater than the total number of TRXs sharing the same HSN.
When assigning the same HSN and MAL to synchronised subcells, the choice of the MAL frequencies is limited.
When assigning the same HSN and MAL to synchronised subcells, we may gain more on interference and fre-
quency diversity.
In order to understand how to work with the AFP module, some notions are detailed below.
An atom is a set of synchronised subcells sharing the same HSN, the same frequency domain, and the same MAL. The
MAIO assignment of an atom manages the frequency collisions between the MALs in it. If an atom contains more than one
subcell, the AFP may assign partially different MALs to it.
Working at the atom level, and with the definition of a user-defined synchronisation reference (subcell table), the AFP
module is able to fully support the benefits of synchronisation in a GSM network.
Note: The following constraints will prevent the Atoll AFP module from complying with certain
options:
- If two synchronised subcells on the same site have different maximum MAL lengths they
cannot be assigned the same HSN.
- If two synchronised subcells on the same site have different frequency domains (maybe
due to forbidden channels), they cannot be assigned the same HSN.
- If two synchronised subcells on the same site have different assignment modes (free or
grouped), they cannot be assigned the same HSN.
Both the MAL size determination and the HSN assignment are carried out so as to obtain a user defined frequency reuse,
whose value can be edited.
The frequency reuse ratio represents the ratio between the MAL length and the total number of frequencies in the domain.
The reuse ratio is not directly linked to the reuse pattern. Nevertheless, we can assume that a 1x1 reuse pattern has a
frequency reuse ratio of 1. A 4x12 reuse pattern can have a reuse ratio between 1/4 and 1/12, depending on whether all
TRXs sharing the same sites have the same MAL (and HSN) or not (considering synchronisation at the site level).
Notes:
This directive is meaningless in NH and BBH.
This directive is used only if the option Adjust MAL length is selected. Otherwise, the specified
value is not taken into account.
It is possible to choose a MAL size strategy when allocating different MALs to the TRXs of an atom. You may decide to
use either a short MAL strategy or a long MAL strategy.
A long MAL strategy enables the AFP module to profit from the hopping gains. On the other hand, it may be harder to find
frequencies for these MALs.
Notes:
This directive is meaningless in NH and BBH.
This directive is considered only if the option Adjust MAL length is checked.
Both the MAL size determination and the HSN assignment are performed so as to obtain a user defined fractional load.
The value of the target fractional load parameter can be edited.
A fractional load of is obtained if the number of TRXs using a certain MAL is only times the size of this MAL. (Atoll's notion
of fractional load does not require taking into account the traffic load. It is always smaller or equal to 1. It equals 1 in NH
or BBH modes).
The target fractional load cannot be always obtained. Atoll AFP module considers this parameter as a guideline rather
than as a constraint. When it can be reached, the AFP module will choose a MAL length 1/ times higher than the number
of TRXs in the biggest subcell of the atom.
Notes:
This directive is meaningless in NH and BBH.
The target frequency reuse directive has a higher priority than the target fractional load direc-
tive.
This directive is used only if the option Adjust MAL length is checked. Otherwise, the specified
value is not taken into account.
The value of this parameter can be auto-calibrated by the AFP module if you check the box
Automatic adjustment.
lowing BSIC in the list (cyclically). I.e. if the BSIC 1 is allocated to the first transmitter, Atoll will try to allocate
the BSIC 2 to the second transmitter. If BSIC 2 does not satisfy the criteria, then Atoll will try to allocate BSIC
3, and so on. In this way the BSIC domain is used uniformly.
The tab is described in "The Atoll AFP Spacing Tab" on page 425.
Hard and Soft criteria are defined as follows:
Hard criterion: Two transmitters having a N relationship and the same BCCH will not be allocated the same BSIC. A N
relationship means the non-directional second order relationship based on the neighbour relationship (simple neighbour,
neighbour of neighbour, 2 transmitters having a common neighbour, etc.).
Soft criterion: Two transmitters which interfere or have a N relationship, and have adjacent or co-channel BCCH will not
be allocated the same BSIC. Hard criterion has to be satisfied in order to proceed with soft criterion.
BSIC allocation is based on neighbourhood links between cells defined in the Neighbours table.
Example: Assume three transmitters, A, B and C.
1st case: A has two neighbours, B and C. The AFP module assigns different BSICs to A, B and C if they have the
same BCCH.
2nd case: A is neighbour of B and C. The AFP module assigns different BSICs to A, B and C if they have the same
BCCH.
A A
N N N N
B C B C
If the interference matrices are correctly managed in Atoll, no further parametrisation (weighting) is required.
The Interference Matrices tab (see Figure 8.3) available in the Atoll AFP Module properties dialogue lets you set up the
interference matrix combination by defining its three weighting components.
The interference matrix combination is carried out as follows:
1. The Atoll AFP Module asks Atoll to load a subset of the active interference matrices of the document. This subset
is determined by comparing each interference matrix scope with the AFP scope. Only the interference matrices
whose scope intersects the AFP scope are loaded.
2. The Atoll AFP Module then reads the scope and context information of each loaded interference matrix.
At a given pixel, the interference, p(i, v, x), of subcell i (interferer) on subcell v (victim) for a given C/I level x, can
be read from more than one interference matrix.
3. The Atoll AFP Module combines all the values of p(i, v, x) by performing a weighted average. Therefore, it calcu-
lates as many weights as the number of p(i, v, x) entries for a pixel. These "reliability weights" are calculated by
multiplying the following three components, which are defined in the Interference Matrices tab of the Atoll AFP
Module properties dialogue:
a. Component quantifying the membership to the AFP scope:
VictimCoverage(Transmitter(v)) x InterfererCoverage(Transmitter(i))
For interference matrices based on OMC statistics, if the scope indicates that both i and v had the same
BCCH, the component will be 0.
Note: In Atoll version 2.5.2, the AFP considered the first value of p(i, v, x). And in Atoll version
2.6.0, the AFP worked with the highest value of p(i, v, x).
This tab enables you to set the different components composing the global cost value. Each component may or may not
be considered (components are not considered by the AFP if their weight or tax = 0 or if the Active flag is not selected).
Through the Taxes section, you can assign tax for each missing (or extra), corrupted, or out of domain TRX.
TRXs having out of domain frequencies can be interfered and can interfere as well. A TRX with out of domain channels
assigned, but having correct ARFCNs, will have a double influence on the cost:
The normal cost of interference/separation/modification.
A cost of being out of domain, multiplied by the number of frequencies that are out of domain and divided by length
of the MAL.
The effects of missing, corrupted and out of domain TRXs on the total AFP cost can be scaled by manipulating
these values.
The Components section deals with the TRXs that are neither missing, corrupted. nor out of their domain. Here you can
set the weighted cost factors for Separation, Interference, Modified or Out of Preferred Frequency Group TRXs.
The definition of the interference and separation cost are respectively explained in "Defining Interference Cost" on
page 412 and "Defining Separation Constraint Violation Cost" on page 413.
Taxes and other components taken into account in the AFP cost are described in "Other Costs Involved in the AFP Cost
Function" on page 413.
A quality target, the percentage max of interference, is specified for each subcell (Subcell properties), which enables the
AFP to differentiate small and large amounts of interference. It is more useful to handle small and large amounts of inter-
ference in different manners. For example, it is better to have 10 transmitters with up to 2% of interfered traffic rather than
having two transmitters with up to 10% of interfered traffic.
Selecting the option Take into account all the TRXs will tell the AFP to take into account the cost of all the TRXs, exceed-
ing or not this quality target. If you clear this box, the AFP will only take into account the costs of the TRXs which do not
fulfill the quality thresholds defined in their corresponding subcells. In other words, in that case, the AFP dismisses any
TRX whose quality do not reach the quality target.
The bottom part of this tab refers to a strategy which has to be selected by user when starting the AFP (See "Running an
Automatic Frequency Allocation" on page 336) called Optimisation of the number of TRXs . When this option is selected,
the AFP may reduce the number of TRXs compared to the number of required TRXs in order to maximise the amount of
correctly served traffic, and consequently, reduce the level of interferences, for weakly traffic-loaded subcells. In the same
way, for highly traffic-loaded subcells, the AFP may increase the number of TRXs compared to what is required in order
to reduce the blocked traffic.
To estimate the blocking probability which has to be miminimised, the circuit and packet demand are the two main inputs.
They can be either directly extracted from the subcell table (or coming from the default traffic capture) or be re-estimated
by the the Atoll AFP Module itself. In this default method, the model uses the current traffic load of the subcells and extract
from this the traffic demand with respect to a maximum blocking rate.
Whatever the method is, when the traffic demand is known, the Atoll AFP Module may vary the number of TRXs in
subcells and for each try, calculates:
The blocking probability
The served circuit and packet traffic
The resulting traffic loads.
The goal of the AFP is to determine the best trade-off between the blocking due to interferences (also called soft blocking)
and the blocking due to traffic (also called hard blocking) by the optimisation of the number of TRXs.
In order to control the process of optimising the number of TRxs, you can play with the parameters as follows:
Increasing the missing TRX tax influences the Atoll AFP Module to respect the number of required TRXs.
Increasing the interference weight influences the creation of a small number of TRXs
In the case of high values of traffic loads (which forces the Atoll AFP Module to create extra TRXs), reducing the
maximum blocking rate limits the number of extra TRXs.
This strategy may also affect the initial subcell loads and KPIs would have to be recalculated after the automatic frequency
planning process.
This tab enables you to define Separation Constraints Violation weights for different types for Separation Constraints and
partial Separation Constraints Violation costs.
Here, you can assign Separation Constraints Violation weights between 0 and 1 to the following types of Separation
Constraints:
Co-cell Separation Violations
Co-site Separation Violations
Neighbourhood Separation Violations
Exceptional pair Separation Violations
The Partial Separation Constraints Violations section enables you to define the costs for separations of 'k', when 's' is
required. You can define the percentage of each TRX traffic to be considered in the case of a partial separation constraint
violation. You can also add and remove different separations using the corresponding buttons.
This tab enables you to define weights applied to interference matrices according to their type as explained in "Interference
Matrix Combination in Atoll AFP Module" on page 420.
This tab enables you to define an allocation strategy in the case of frequency hopping.
In case of SFH or BBH, you may specify HSN Allocation directives, such as:
By Subcell,
By Transmitter,
By Site, or
Free.
This tab enables you to inform the AFP about the Mobile Allocation List patterns and length priorities in the case of
frequency hopping.
In the case of synchronised set, you may choose from the following MAL Pattern directives:
Allocation of the same MAL for all the subcells of a synchronised set, or
Allocation of different MALs within a synchronised set.
In the case of SFH, you may define the MAL Length Priority directives:
1. Group Constrained mode limits the choice of MAL lengths.
2. Maximum MAL lengths or adjusted MAL lengths.
3. MAL length per domain size should be less than a defined value.
4. Long or Short MAL Strategy (with the option of keeping MAL long enough to allow a certain pattern).
5. Assign a Target Fractional Load and choose whether the AFP has the possibility of modifying this value in order
to adjust it automatically for optimisation.
The Execution tab has two parts: Target Computation Time and Result Assignment.
When you define a target calculation time when running an AFP session, it can be used in two different ways. With the
default option Directive Duration, the duration is used by the module to estimate the methods which will be used to find
the best solution. For a sufficiently long duration, the model may even adapt its internal parameter in order to be calibrated
accordingly to the network which is being allocated. For a short duration, the AFP will select a restricted number of meth-
ods and will not calibrate its internal parameters. The duration is purely indicative since it might be exceeded if conver-
gence has not been reached. This directive corresponds to the minimum time you reserve for the AFP to let it find the best
solution.
If you select the Fixed Duration option, the AFP module will stop when this time is elapsed. If a stable solution has been
found prior to this limit, the allocation will stop.
The second part of the dialogue deals with result assignment when the module has stopped. With the default option
(Manual Assignment), the Atoll AFP Module lets you analyse the allocation and manually assign if desired the results to
the network. The second option (Automatic Assignment) automatically assigns the best calculated plan to the network.
This tab enables you to declare an allocation strategy in the case of free MAL assignments.
The Pattern part is used to assign frequency groups to sectors, assuming there are more than "n" groups, where the
pattern is defined by "1/n," are defined in the considered frequency domain. When used, and prior to all the other assign-
ments, the AFP assigns the preferred groups. As a result of the AFP, preferred groups can be allocated to subcells.
The assignment of the preferred groups, in other words, the pattern is based on the azimuth, and uses the n largest groups
in the domain.
In case less then n groups are defined in the frequency domain, the pattern assignment is dismissed.
In addition, it is possible to choose from the three available Channel Spacing directives (any hopping or non-hopping
mode):
Automatic: Directs the AFP to optimise the channel spacing so as to minimize the cost.
Max: Directs the AFP to use the entire spectrum available.
Min: Directs the AFP to use a limited spectrum.
This tab also enables you to choose the BSIC usage diversity strategy in the case of frequency hopping.
You may set the BSIC usage diversity to either:
Minimum usage diversity, or
Maximum and homogeneous usage diversity.
As well, this tab enables you to choose a MAIO allocation strategy if frequency hopping is used.
For SFH, you can choose from the following MAIO allocation preferences:
Staggered
Free.
This tab enables you to define the strategies in term of additional protections in the evaluation of the interferences.
Under Additional Protection against the Adjacent Channel Reuse on the Protections tab, the option influences the esti-
mate of the interference cost created by adjacent channels. Compared to a co-channel, the effect of an adjacent channel
is by default decreased by 18 dB, following GSM specifications. In order to increase, if desired, the impact of adjacent
channels in interference, you can chose one of the following three options for adjacent channel protection:
None: no additional protection is added to the initial protection. The resulting adjacent channel protection level
used to estimate the impact of adjacent channels in interferences is 18 dB.
Weak: a fixed-size shift of 1.5 dB is applied to the initial protection. The resulting adjacent channel protection level
used to estimate the impact of adjacent channels in interferences is 16.5 dB.
Strong: a fixed-size shift of 2.5 dB is applied to the initial protection. The resulting adjacent channel protection
level used to estimate the impact of adjacent channels in interferences is 15.5 dB.
Note: For interference matrices based on propagation, Atoll can determine whether they have
been calculated with a handover margin. If the margin has not been used, the AFP can
adapt its settings to more realistically model the network. In other words, if you do not take
the handover margin into consideration when calculating the interference matrix, Atoll
can automatically change the adjacent channel additional protection from none to weak,
or even to strong.
The Interference definition according to the required quality threshold section enables you to set a C/I weighting margin
around the required quality threshold in order for the AFP to consider the traffic having close-to-threshold C/I conditions
as neither 100% satisfactory nor 100% corrupted. This is explained in detail in "Defining Interference Cost" on page 412.
Note: For interference matrices based on propagation, Atoll can determine whether they have
been calculated with a shadowing. If shadowing has not been taken into account, the AFP
can adapt its settings to more realistically model the network. In other words, if you do not
take shadowing into consideration when calculating the interference matrix, Atoll can
automatically change its definition of interference from rigid to intermediate, or even to
flexible.
This tab enables you to define the Interference and Frequency diversity gains in the case of frequency hopping.
You may set:
the interferer diversity gain,
the frequency diversity gain,
the gain depending on the timeslot use ratio.
The interferer diversity and the frequency diversity gains are defined for different MAL lengths. All of the parameters avail-
able in this tab are used to evaluate the interference cost component. Only the interferer diversity gain has an influence
on the separation cost component.
The Atoll AFP module is implemented using simulated annealing, taboo search, graph heuristics and machine learning.
It manages its time resources to match the user time directives. If given a lot of time, the module will use a major part of
this time to learn the network. During the learning phase, the module adjusts its internal parameters. At the end of the
user-defined time period, the AFP switches to a randomised combinatorial search phase according to the initialisation
number set when starting the AFP.
Network learning is performed by executing many fast and deterministic instances of the AFP. The one which gains the
best performance can be memorised both in the document and in the database (after having been archived) depending
on the selected option (Experience Conserved/Not Conserved). If this experience is conserved, the next time that an AFP
will be executed it will start where the learning process ended it will use the parameter profile of the best solution stored
in the Atoll document.
Atoll
RF Planning and Optimisation Software
Chapter 9: UMTS HSPA Networks
1
Open an Existing Project
or Create a New One
2
Network Configuration
- Add Network Elements
- Change Parameters
3
Basic Predictions
(Best Server, Signal Level)
4
Neighbour Allocation
5a 5b 5c
Traffic Maps Monte-Carlo User-defined values
Simulations 5
Cell Load
Conditions
6 6a
UMTS/HSPA Predictions Prediction Study Reports
7
Scrambling Code Plan
The steps involved in planning a UMTS HSPA network are described below. The numbers refer to Figure 9.1.
5. Before making more advanced coverage predictions, you need to define cell load conditions ( 5 ).
You can define cell load conditions in the following ways:
- You can generate realistic cell load conditions by creating a simulation based on a traffic map ( 5a and 5b )
(see "Studying Network Capacity" on page 511).
- You can define them manually either on the Cells tab of each transmitters Properties dialogue or in the Cells
table (see "Creating or Modifying a Cell" on page 440) ( 5c ).
6. Make UMTS-specific coverage predictions using the defined cell load conditions ( 6 ).
- "UMTS-Specific Studies" on page 474
- "HSDPA Coverage Prediction" on page 489
- "HSUPA Coverage Prediction" on page 491.
Antenna
- Azimuth
- Mechanical tilt
TMA
Antenna
- Height
Feeder Cable
BTS
- BTS noise figure
- Power
Site
- X, Y coordinates
Atoll lets you create one site, transmitter, or cell at a time, or create several at once by creating a station template. Using
a station template, you can create one or more base stations at the same time. In Atoll, a base station refers to a site with
its transmitters, antennas, equipment, and cells.
Atoll allows you to make a variety of coverage predictions, such as signal level or transmitter coverage predictions. The
results of calculated coverage predictions can be displayed on the map, compared, or studied.
Atoll enables you to model network traffic by allowing you to create services, users, user profiles, environments, and termi-
nals. This data can be then used to make quality studies, such as effective service area, noise, or handover status predic-
tions, on the network.
In this section, the following are explained:
"Creating a UMTS Base Station" on page 433
"Creating a Group of Base Stations" on page 447
"Modifying Sites and Transmitters Directly on the Map" on page 447
"Display Tips for Base Stations" on page 447
"Creating a Dual-Band UMTS Network" on page 448
"Creating a Repeater" on page 448
"Creating a Remote Antenna" on page 451
- Name: Atoll automatically enters a default name for each new site. You can modify the default name here. If
you want to change the default name that Atoll gives to new sites, see the Administrator Manual.
- Position: By default, Atoll places the new site at the centre of the map window. You can modify the location
of the site here.
Tip: While this method allows you to place a site with precision, you can also place sites using
the mouse and then position them precisely with this dialogue afterwards. For information
on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 31.
- Altitude: The altitude, as defined by the DTM for the location specified under Position, is given here. You can
specify the actual altitude under Real, if you wish. If an altitude is specified here, Atoll will use this value for
calculations.
- Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are dis-
played in red in the Transmitters folder of the Data tab.
Note: Only active transmitters are taken into consideration during calculations.
- Transmission/Reception: Under Transmission/Reception, you can see the total losses and the noise
figure of the transmitter. Atoll calculates losses and noise according to the characteristics of the equipment
assigned to the transmitter. Equipment can be assigned by using the Equipment Specifications dialogue
which appears when you click the Equipment button.
- On the Equipment Specifications dialogue (see Figure 9.5), the equipment you select and the gains and
losses you define are used to initialise total transmitter UL and DL losses:
- TMA: You can select a tower-mounted amplifier (TMA) from the list. You can click the Browse button
( ) to access the properties of the TMA. For information on creating a TMA, see "Defining TMA Equip-
ment" on page 147.
- Feeder: You can select a feeder cable from the list. You can click the Browse button ( ) to access the
properties of the feeder. For information on creating a feeder cable, see "Defining Feeder Cables" on
page 147.
- BTS: You can select a base transceiver station (BTS) equipment from the BTS list. You can click the
Browse button ( ) to access the properties of the BTS. For information on creating a BTS, see "Defin-
ing BTS Equipment" on page 148.
- Feeder Length: You can enter the feeder length at transmission and reception.
- Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value
you enter must be positive.
- Receiver Antenna Diversity Gain: You can enter a receiver antenna diversity gain. The value you enter
must be positive.
Note: Any loss related to the noise due to a transmitters repeater is included in the calculated
losses. Atoll always considers the values in the Real boxes in prediction studies even if
they are different from the values in the Computed boxes. The information in the real
BTS Noise Figure reception box is calculated from the information you entered in the
Equipment Specifications dialogue. You can modify the real Total Losses at
transmission and reception and the real BTS Noise Figure at reception if you wish. Any
value you enter must be positive.
- Antennas:
- Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added
to the altitude of the site as given by the DTM. If the transmitter is situated on a building, the height entered
must include the height of building.
- Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the
Browse button ( ) to access the properties of the antenna. The other fields, Azimuth, Mechanical
Downtilt, and Additional Electrical Downtilt, display additional antenna parameters.
- Under Diversity, you can select the number of transmission and reception antenna ports used for MIMO
(No. of ports). MIMO systems are supported by some HSDPA bearers (improvements introduced by the
release 7 of the 3GPP UTRA specifications, referred to as HSPA+). For more information on how the
number of antenna ports are used, see "Multiple Input Multiple Output Systems" on page 556.
R99 bearers only support transmit and receive diversities. You can define the transmit diversity method
from the Transmission list when more than one transmission antenna port are available. The receive di-
versity method depends on the number of reception antenna ports selected (2RX for two reception anten-
na ports and 4RX for four reception antenna ports).
- Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power, which is
the percentage of power reserved for this particular antenna. For example, for a transmitter with one
secondary antenna, if you reserve 40% of the total power for the secondary antenna, 60% is available for
the main antenna.
For information on working with data tables, see "Working with Data Tables" on page 50.
When you select Inter-Carrier Power Sharing and you define a maximum shared power, the Max Power of each
cell is used to determine the percentage of the transmitter power that the cell cannot exceed.
The most common scenario is where you have R99-only cells that are not using 100% of their power and can share
it with an HSDPA carrier. To use power sharing efficiently, you should set the Max Power of the HSDPA cells to
the same value as the Maximum Shared Power. For example, if the Maximum Shared Power is defined as
43 dBm, the Max Power of all HSDPA cells should be set to 43 dBm in order to be able to use 100% of the avail-
able power. In this case, all of an R99 cells unused power can be allocated to the HSDPA cell.
Name: By default, Atoll names the cell after its transmitter, adding the carrier number in parentheses. If you
change transmitter name or carrier, Atoll does not update the cell name. You can enter a name for the cell, but
for the sake of consistency, it is better to let Atoll assign a name. If you want to change the way Atoll names cells,
see the Administrators Manual.
ID: You can enter an ID for the cell. This is a user-definable network-level parameter for cell identification.
Carrier: The number of the carrier.
Active: If this cell is to be active, you must select the Active check box.
Max Power (dBm): The maximum available downlink power for the cell.
Pilot Power (dBm): The pilot power.
SCH power (dBm): The average power of both the synchronisation channels (P-SCH and S-SCH).
Note: The SCH power is only transmitted 110 of the time. Consequently, the value entered for
the SCH power should only be 110 of its value when transmitted, in order to respect its
actual interference on other channels.
Other CCH power (dBm): The power of other common channels (P-CCPCH, S-CCPCH, AICH).
AS Threshold (dB): The active set threshold. It is the EcI0 margin in comparison with the EcI0 of the best server.
It is used to determine which cells, apart from the best server, will be part of the active set.
DL Peak Rate per User (kbps): The downlink peak rate per user in kbps. The DL peak rate per user is the max-
imum connection rate in the downlink for a user. The DL and UL peak rates are taken into account during power
control simulation.
UL Peak Rate per User (kbps): The uplink peak rate per user in kbps. The UL peak rate per user is the maximum
connection rate in the uplink for a user. The DL and UL peak rates are taken into account during power control
simulation.
Max DL Load (% Pmax): The percentage of the maximum downlink power (set in Max Power) not to be
exceeded. This limit will be taken into account during the simulation if the option DL Load is selected. If the DL
load option is not selected during a simulation, this value is not taken into consideration.
Max UL Load Factor (%): The maximum uplink load factor not to be exceeded. This limit can be taken into
account during the simulation.
Total Power (dBm or %): The total transmitted power on downlink is the total power necessary to serve R99 and
HSDPA users. This value can be a simulation result or can be entered by the user.
Note: By default, the total power is set as absolute value. You can set this value as a
percentage of the maximum power of the cell by right-clicking the Transmitters folder on
the Data tab of the Explorer window and selecting Properties from the context menu.
Then, on the Global Parameters tab of the Properties dialogue, under DL Load, you can
select % Pmax. The total power value is automatically converted and set as a percentage
of the maximum power.
UL Load Factor (%): The uplink cell load factor. This factor corresponds to the ratio between the uplink total inter-
ference and the uplink total noise. This value can be a simulation result or can be entered by the user.
UL Reuse Factor: The uplink reuse factor is determined from uplink intra and extra-cell interference (signals
received by the transmitter respectively from intra and extra-cell terminals). This is the ratio between the total
uplink interference and the intra-cell interference. This value can be a simulation result or can be entered by the
user.
Scrambling Code Domain: The scrambling code domain to which the allocated scrambling code belongs. This
and the scrambling code reuse distance are used by the scrambling code planning algorithm.
SC Reuse Distance: The scrambling code reuse distance. This and the scrambling code domain are used by the
scrambling code planning algorithm.
Primary Scrambling Code: The primary scrambling code.
Comments: If desired, you can enter any comments in this field.
Max Number of Intra-carrier Neighbours: The maximum number of intra-carrier neighbours for this cell. This
value is used by the intra-carrier neighbour allocation algorithm.
Max Number of Inter-carrier Neighbours: The maximum number of inter-carrier neighbours for this cell. This
value is used by the inter-carrier neighbour allocation algorithm.
Max Number of Inter-technology Neighbours: The maximum number of inter-technology neighbours for this
cell. This value is used by the inter-technology neighbour allocation algorithm.
Neighbours: You can access a dialogue in which you can set both intra-technology (intra-carrier and inter-carrier)
and inter-technology neighbours by clicking the Browse button ( ). For information on defining neighbours, see
"Planning Neighbours" on page 492.
Tip: The Browse button ( ) might not be visible in the Neighbours box if this is a new cell.
You can make the Browse button appear by clicking Apply.
HSPA Support: The HSPA functionality supported by the cell. You can choose between None (i.e. R99 only),
HSDPA, HSPA (i.e HSDPA and HSUPA), HSPA+ with transmit diversity or HSPA+ with spatial multiplexing.
When HSDPA functionality is supported, the following fields are available:
- HSDPA Dynamic Power Allocation: If you are modelling dynamic power allocation, the HSDPA Dynamic
Power Allocation should be checked. During a simulation, Atoll first allocates power to R99 users and then
dynamically allocates the remaining power of the cell to the HS-PDSCH and HS-SCCH of HSDPA users. At
the end of the simulation, you can commit the calculated HSDPA power and total power values to each cell.
Note: In the context of dynamic power allocation, the total power equals the maximum power
minus the power headroom.
- Available HSDPA Power (dBm): When you are modelling static power allocation, the HSDPA Dynamic
Power Allocation check box is cleared and the available HSDPA power is entered in this box. This is the
power available for the HS-PDSCH and HS-SCCH of HSDPA users.
- Power Headroom (dB): The power headroom is a reserve of power that Atoll keeps for Dedicated Physical
Channels (DPCH) in case of fast fading. During simulation, HSDPA users will not be connected if the cell
power remaining after serving R99 users is less than the power headroom value.
- HS-SCCH Dynamic Power Allocation: If you are modelling dynamic power allocation the HS-SCCH
Dynamic Power Allocation check box should be checked and a value should be entered in HS-SCCH Power
(dBm). During power control, Atoll will control HS-SCCH power in order to meet the minimum quality
threshold (as defined for each mobility type). The value entered in HS-SCCH Power (dBm) is the maximum
power available for each HS-SCCH channel. The calculated power for each HSDPA user during the simulation
cannot exceed this maximum value.
- HS-SCCH Power (dBm): The value for each HS-SCCH channel will be used if you are modelling dynamic
power allocation. If you have selected the HS-SCCH Dynamic Power Allocation check box and modelling
dynamic power allocation, the value entered here represents a maximum for each HSDPA user. If you have
not selected the HS-SCCH Dynamic Power Allocation check box and are modelling static power allocation,
the value entered here represents the actual HS-SCCH power per HS-SCCH channel.
- Number of HS-SCCH Channels: The maximum number of HS-SCCH channels for this cell. Each HSDPA
user consumes one HS-SCCH channel. Therefore, at any given time (over a time transmission interval), the
number of HSDPA users cannot exceed the number of HS-SCCH channels per cell.
- Min. Number of HS-PDSCH Codes: The minimum number of OVSF codes available for HS-PDSCH chan-
nels. This value will be taken into account during simulations in order to find a suitable bearer.
- Max Number of HS-PDSCH codes: The maximum number of OVSF codes available for HS-PDSCH chan-
nels. This value will be taken into account during simulations and coverage predictions in order to find a suit-
able bearer.
- Max Number of HSDPA Users: The maximum number of HSDPA bearer users (HSDPA and HSUPA users)
that this cell can support at any given time.
- Number of HSDPA Users: The number of HSDPA bearer users (HSDPA and HSUPA users) is an average
and can be used for certain coverage predictions. You can enter this value yourself, or have the value calcu-
lated by Atoll using a simulation.
- HSDPA Scheduler Algorithm: The scheduling technique that will be used to rank the HSDPA users to be
served:
- Max C/I: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined) are
scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descend-
ing order by the channel quality indicator (CQI).
- Round Robin: HSDPA users are scheduled in the same order as in the simulation (i.e., in random order).
- Proportional Fair: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users
defined) are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted
in descending order according to a random parameter which corresponds to a combination of the user
rank in the simulation and the channel quality indicator (CQI).
Note: The random parameter is calculated by giving both the user simulation rank and the CQI a
weight of 50%. You can change the default weights by setting the appropriate options in
the atoll.ini file. For more information, see the Administrator Manual.
When HSUPA functionality is supported, the following fields are also available:
- DL HSUPA Power: The power (in dBm) allocated to HSUPA DL channels (E-AGCH, E-RGCH, and E-HICH).
This value must be entered by the user.
- Max Number of HSUPA Users: The maximum number of HSUPA users that this cell can support at any given
time.
- UL Load Factor Due to HSUPA (%): The uplink cell load contribution due to HSUPA. This value can be a
simulation result or can be entered by the user.
- Number of HSUPA Users: The number of HSUPA users is an average and can be used for certain coverage
predictions. This value can be a simulation result or can be entered by the user.
Note: By default, the SCH power, the CCH power, the HS-SCCH power and the HSUPA power
are set as absolute values. You can set these values as relative to the pilot power by
right-clicking the Transmitters folder on the Data tab of the Explorer window and
selecting Properties from the context menu. Then, on the Global Parameters tab of the
Properties dialogue, under DL Powers, you can select Relative to Pilot. The SCH
power, the CCH power, the HS-SCCH power and the HSUPA power values are
automatically converted and set as relative to the pilot power.
MBMS: You can access a dialogue in which you can set MBMS channel powers and channel data rates by clicking
the Browse button ( ). This option is only available if the optional MBMS feature has been activated. Activating
this optional feature requires data structure modifications (for more information, see the Administrator Manual).
If an MBMS SCCPCH is not used, you should leave the field corresponding to its transmission power empty. The
MBMS channel powers are used to calculate the optional MBMS service area Eb/Nt coverage prediction, and are
taken into account in other calculations in the same way as the other common control channel power, i.e., for the
calculation of interference.
Tip: The Browse button ( ) might not be visible in the MBMS box if this is a new cell. You
can make the Browse button appear by clicking Apply.
Tip: If you are creating several sites at the same time, or modifying several existing sites, you
can do it quickly by editing or pasting the data directly in the Sites table. You can open
the Sites table by right-clicking the Sites folder on the Data tab of the Explorer window
and selecting Open Table from the context menu. For information on copying and
pasting data, see "Copying and Pasting in Tables" on page 56.
Tips:
If you are creating several transmitters at the same time, or modifying several existing trans-
mitters, you can do it more quickly by editing or pasting the data directly in the Transmitters
table. You can open the Transmitters table by right-clicking the Transmitters folder on the
Data tab of the Explorer window and selecting Open Table from the context menu. For infor-
mation on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
If you want to add a transmitter to an existing site on the map, you can add the transmitter by
right-clicking the site and selecting New Transmitter from the context menu.
Tips:
If you are creating or modifying several cells at the same time, you can do it more quickly by
editing the data directly in the Cells table. You can open the Cells table by right-clicking the
Transmitters folder on the Data tab of the Explorer window and selecting Cells > Open
Table from the context menu. You can either edit the data in the table, paste data into the table
(see "Copying and Pasting in Tables" on page 56), or import data into the table (see "Importing
Tables from Text Files" on page 59).
If you want to add a cell to an existing transmitter on the map, you can add the cell by right-
clicking the transmitter and selecting New Cell from the context menu.
3. In the map window, move the pointer over the map to where you would like to
place the new station. The exact coordinates of the pointers current location
are visible in the Status bar.
Tips:
To place the station more accurately, you can zoom in on the map before you click the New
Station button. For information on using the zooming tools, see "Changing the Map Scale" on
page 38.
If you let the pointer rest over the station you have placed, Atoll displays its tip text with its
exact coordinates, allowing you to verify that the location is correct.
You can also place a series of stations using a Atoll template. You do this by defining an area on the map where you want
to place the stations. Atoll calculates the placement of each station according to the defined hexagonal cell radius in the
station template. For information on defining the cell radius, see "Creating or Modifying a Station Template" on page 442.
To place a series of stations within a defined area:
1. In the Radio toolbar, select a template from the list.
2. Click the Hexagonal Design button ( ), to the left of the template list. A hexagonal design is a group of stations
created from the same station template.
Note: If the Hexagonal Design button is not available ( ), the hexagonal cell radius for this
template is not defined. For information on defining the cell radius, see "Creating or
Modifying a Station Template" on page 442.
3. Draw a zone delimiting the area where you want to place the series of stations:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
Atoll fills the delimited zone with new stations and their hexagonal shapes. Station objects such as sites and trans-
mitters are also created and placed into their respective folders.
You can work with the sites and transmitters in these stations as you work with any station object, adding, for example,
another antenna to a transmitter.
When you place a new station using a station template as explained in "Placing a New Station Using a Station Template"
on page 440, the site is created at the same time as the station. However, you can also place a new station on an existing
site.
To place a station on an existing site:
1. On the Data tab, clear the display check box beside the Hexagonal Design folder.
2. In the Radio toolbar, select a template from the list.
- Under Main Antenna, you can modify the following: the antenna Model, 1st Sector Azimuth, from which the
azimuth of the other sectors are offset to offer complete coverage of the area, the Height of the antenna from
the ground (i.e., the height over the DTM; if the transmitter is situated on a building, the height entered must
include the height of building), the Mechanical Downtilt, and the Additional Electrical Downtilt.
- Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both
the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Managing
Calculations in Atoll.
5. Click the Transmitter tab. On this tab (see Figure 9.8), if the Active check box is selected, you can modify the fol-
lowing:
- Under Transmission/Reception, you can click the Equipment button to open the Equipment Specifica-
tions dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or base transceiver station
(BTS). For information on the Equipment Specifications dialogue, see "Transmitter Description" on
page 434.
- The information in the real Total Losses in transmission and reception boxes is calculated from the informa-
tion you entered in the Equipment Specifications dialogue (see Figure 9.5 on page 436). Any loss related to
the noise due to a transmitters repeater is included in the calculated losses. Atoll always considers the values
in the Real boxes in prediction studies even if they are different from the values in the Computed boxes. You
can modify the real Total Losses at transmission and reception if you wish. Any value you enter must be pos-
itive.
- The information in the real BTS Noise Figure reception box is calculated from the information you entered in
the Equipment Specifications dialogue. You can modify the real BTS Noise Figure at reception if you wish.
Any value you enter must be positive.
- Under Diversity, you can select the number of transmission and reception antenna ports used for MIMO (No.
of ports). MIMO systems are supported by some HSDPA bearers (improvements introduced by the release
7 of the 3GPP UTRA specifications, referred to as HSPA+). For more information on how the number of
antenna ports are used, see "Multiple Input Multiple Output Systems" on page 556.
R99 bearers only support transmit and receive diversities. You can define the transmit diversity method from
the Transmission list when more than one transmission antenna port are available. The receive diversity
method depends on the number of reception antenna ports selected (2RX for two reception antenna ports and
4RX for four reception antenna ports).
6. Click the W-CDMA/UMTS tab. In this tab (see Figure 9.9), you modify the Carriers (each corresponding to a cell)
that this station supports. For information on carriers and cells, see "Cell Definition" on page 436.
- You can select the Carriers for this template.
- Under Power, you can select the Power Shared Between Cells check box. As well, you can modify the Pilot,
the SCH, the Other CCH powers, and the AS Threshold.
- Under Simulation Constraints, you can modify the Max Power, the Max DL Load (defined as a percentage
of the maximum power), the DL Peak Rate/User, the Max UL Load Factor, and the UL Peak Rate/User.
- Under Load Conditions, you can modify the Total Transmitted Power, the UL Load Factor, and the UL
Reuse Factor.
- You can also modify the Number of Uplink and Downlink Channel Elements, the Max Iub Uplink and
Downlink Backhaul Throughputs and select the Equipment.
- You can modify the DL Power, the UL Load, the Max Number of Users, and the Number of Users.
8. Click the Neighbours tab. In this tab (see Figure 9.11), you can modify the Max Number of Intra- and Inter-Car-
rier Neighbours and the Max Number of Inter-Technology Neighbours. For information on defining neigh-
bours, see "Planning Neighbours" on page 492.
9. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the
Sites table, or if you have defined an additional field in the Station Template Properties dialogue.
10. When you have finished setting the parameters for the station template, click OK to close the dialogue and save
your changes.
Choice list, by entering the possible selections directly in the Choice list window and pressing ENTER
after each one.
vi. Enter, if desired, a Default value for the new field.
vii. Click OK to close the Field Definition dialogue and save your changes.
- Delete: To delete a user-defined field:
i. Select the user-defined field you want to delete.
ii. Click the Delete button. The user-defined field appears in strikeout. It will be definitively deleted when you
close the dialogue.
- Properties: To modify the properties of a user-defined field:
i. Select the user-defined field you want to modify.
ii. Click the Properties button. The Field Definition dialogue appears.
iii. Modify any of the properties as desired.
iv. Click OK to close the Field Definition dialogue and save your changes.
6. Click OK.
5. In the map window, move the pointer over the map to where you would like to place the new base station. The
exact coordinates of the pointers current location are visible in the Status bar.
Tips:
To place the station more accurately, you can zoom in on the map before you select Duplicate
from the context menu. For information on using the zooming tools, see "Changing the Map
Scale" on page 38.
If you let the pointer rest over the station you have placed, Atoll displays tip text with its exact
coordinates, allowing you to verify that the location is correct.
A new base station is placed on the map. The site, transmitters, and cells of the new base station have the same
names as the site, transmitters, and cells of the original base station with each name marked as "Copy of." The
site, transmitters, and cells of the duplicate base station have the same settings as those of the original base
station. All the remote antennas and repeaters of any transmitter on the original site are also duplicated.
You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to
place each duplicate station.
For more information on the site, transmitter, subcell, and TRX properties, see "Definition of a Base Station" on page 433.
Note: When you import data into your current Atoll document, the coordinate system of the
imported data must be the same as the display coordinate system used in the document.
If you cannot change the coordinate system of your source data, you can temporarily
change the display coordinate system of the Atoll document to match the source data.
For information on changing the coordinate system, see "Setting a Coordinate System"
on page 92.
Important: The table you copy data from must have the same column layout as the table you are
pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
Importing data: If you have data in text or comma-separated value (CSV) format, you can import it into the tables
in the current document. If the data is in another Atoll document, you can first export it in text or CSV format and
then import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select
what values you import into which columns of the table.
When you create a group of base stations by importing data, you must import site data in the Sites table, trans-
mitter data in the Transmitters table, and cell data in the Cells table, in that order.
For information on exporting table data, see "Exporting Tables to Text Files" on page 58. For information on
importing table data, see "Importing Tables from Text Files" on page 59.
Note: You can quickly create a series of base stations for study purposes using the Hexagonal
Design tool on the Radio toolbar. For information, see "Placing a New Station Using a
Station Template" on page 440.
The following tools can be used to display information about base stations:
Label: You can display information about each object, such as each site or transmitter, in the form of a label that
is displayed with the object. You can display information from every field in that object types data table, including
from fields that you add. The label is always displayed, so you should choose information that you would want to
always be visible; too much information will lead to a cluttered display. For information on defining the label, see
"Defining the Object Type Label" on page 35.
Tooltips: You can display information about each object, such as each site or transmitter, in the form of a tooltip
that is only visible when you move the pointer over the object. You can choose to display more information than
in the label, because the information is only displayed when you move the pointer over the object. You can display
information from every field in that object types data table, including from fields that you add. For information on
defining the tooltips, see "Defining the Object Type Tip Text" on page 36.
Transmitter colour: You can set the transmitter colour to display information about the transmitter. For example,
you can select "Discrete Values" to distinguish transmitters by antenna type, or to distinguish inactive from active
sites. You can also define the display type for transmitters as "Automatic." Atoll then automatically assigns a
colour to each transmitter, ensuring that each transmitter has a different colour than the transmitters surrounding
it. For information on defining the transmitter colour, see "Defining the Display Type" on page 34.
Transmitter symbol: You can select one of several symbols to represent transmitters. For example, you can
select a symbol that graphically represents the antenna half-power beamwidth ( ). If you have two transmit-
ters on the same site with the same azimuth, you can differentiate them by selecting different symbols for each
( and ). For information on defining the transmitter symbol, see "Defining the Display Type" on page 34.
Note: Broad-band repeaters are not modelled. Atoll assumes that all carriers from the 3G donor
transmitter are amplified.
4. To create repeater equipment, enter the following in the row marked with the New Row icon ( ):
a. Enter a Name and Manufacturer for the new equipment.
b. Enter a Noise Figure. The repeater causes a rise in noise at the donor transmitter, so the noise figure is used
to calculate the UL loss to be added to the donor transmitter UL losses. The noise figure must be a positive
value.
c. Enter minimum and maximum repeater amplification gains in the Min. Gain and Max Gain columns. These
parameters enable Atoll to ensure that the user-defined amplifier gain is consistent with the limits of the equip-
ment if there are any.
d. Enter a Gain Increment. Atoll uses the increment value when you increase or decrease the repeater amplifier
gain using the buttons to the right of the Amplification box ( ) on the General tab of the repeater Properties
dialogue.
e. Enter the maximum power that the equipment can transmit on the downlink in the Maximum Downlink Power
column. This parameter enables Atoll to ensure that the downlink power after amplification does not exceed
the limit of the equipment.
f. If desired, enter a Maximum Uplink Power, an Internal Delay and Comments. These fields are for informa-
tion only and are not used in calculations.
5. To modify repeater equipment, change the parameters in the row containing the repeater equipment you wish to
modify.
2. Click the arrow next to New Repeater or Remote Antenna button ( ) on the Radio toolbar.
3. Select Repeater from the menu.
4. Click the map to place the repeater. The repeater is placed on the map, represented by a symbol ( ) in the
same colour as the donor transmitter or repeater. By default, the repeater has the same azimuth as the donor
transmitter or repeater. Its tooltip and label display the same information as displayed for the donor transmitter or
repeater. As well, its tooltip and label identify the repeater and the donor transmitter or repeater.
For information on defining the properties of the new repeater, see "Defining the Properties of a Repeater" on
page 449.
Note: You can see to which base station the repeater is connected by clicking it; Atoll displays
a link to the donor transmitter or repeater.
Important: The table you copy data from must have the same column layout as the table you are
pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
- You can change the Amplification gain. The amplification gain is used in the link budget to evaluate the
repeater total gain.
4. Click the Donor Side tab. You can modify the following parameters:
- Under Donor-Repeater Link, select a Link Type.
- If you select Microwave Link, enter the Propagation Losses and continue with step 5.
- If you select Air Link, select a Propagation Model and enter the Propagation Losses or click Calculate
to determine the actual propagation losses between the donor and the repeater. If you do not select a
propagation model, the propagation losses between the donor transmitter and the repeater are calculated
using the ITU 526-5 propagation model.
When you create an off-air repeater, it is assumed that the link between the donor transmitter and the re-
peater has the same frequency as the network.
Important: If you want to create a remote antenna, you must select Optical Fibre Link.
- If you selected Air Link under Donor-Repeater Link, enter the following information under Antenna:
i. Select a Model from the list. You can click the Browse button ( ) to access the properties of the
antenna.
ii. Enter the height off the ground of the antenna in the Height/Ground box. This will be added to the altitude
of the transmitter as given by the DTM.
iii. Enter the Azimuth and the Mechanical Downtilt.
Note: You can click the Calculate button to update azimuth and downtilt values after changing
the repeater donor side antenna height or the repeater location. If you choose another site
or change site coordinates in the General tab, click Apply before clicking the Calculate
button.
- If you selected Air Link under Donor-Repeater Link, enter the following information under Feeders:
i. Select a Type of feeder from the list. You can click the Browse button ( ) to access the properties of
the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
5. Click the Coverage Side tab. You can modify the following parameters:
- Select the Active check box. Only active repeaters (displayed in red in the Transmitters folder in the Data
tab of the Explorer window) are calculated.
- Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual
gains. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply
before clicking the Calculate button. Atoll uses the DL total gain values to calculate the signal level received
from the repeater. The UL total gain value is considered in UL Eb/Nt service area studies.
The DL total gain is applied to each power (pilot power, SCH power, etc.). It takes into account losses between
the donor transmitter and the repeater, donor characteristics (donor antenna gain, reception feeder losses),
amplification gain, and coverage characteristics (coverage antenna gain and transmission feeder losses).
The UL total gain is applied to each terminal power. It takes into account losses between the donor transmitter
and the repeater, donor part characteristics (donor antenna gain, transmission feeder losses), amplification
gain and coverage part characteristics (coverage antenna gain and reception feeder losses).
ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( ) to access the
properties of the antenna. Then, enter the Azimuth, the Mechanical Downtilt, and, if applicable, the Ad-
ditional Electrical Downtilt. By default, the characteristics (antenna, azimuth, height, etc.) of the repeater
coverage side correspond to the characteristics of the donor transmitter.
iii. Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power. For infor-
mation on working with data tables, see "Working with Data Tables" on page 50.
- Under Feeders, you can modify the following information:
i. Select a Type of feeder from the list. You can click the Browse button ( ) to access the properties of
the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
- Under Losses, Atoll displays the Loss Related to Repeater Noise Rise.
6. Click the Propagation tab. Since repeaters are taken into account during calculations, you must set the propaga-
tion parameters. On the Propagation tab, you can modify the following: the Propagation Model, Radius, and Res-
olution for both the Main Matrix and the Extended Matrix. By default, the propagation characteristics of the
repeater (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For infor-
mation on propagation models, see Chapter 5: Managing Calculations in Atoll.
Note: You can prevent Atoll from updating the UL and DL total gains of selected repeaters by
creating a custom field called "FreezeTotalGain" in the Repeaters table and setting the
value of the field to "True." Afterwards, when you select Repeaters > Calculate Gains
from the Transmitters context menu, Atoll will only update the UL and DL total gains for
repeaters with the custom field "FreezeTotalGain" set to "False."
You can update the propagation losses of all off-air repeaters by selecting Repeaters > Calculate Donor Side
Propagation Losses from the Transmitters context menu.
You can select a repeater on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using
the Mouse" on page 32) or its position relative to the site (see "Changing the Position of the Transmitter Relative
to the Site" on page 32).
Note: Ensure that the remote antennas donor transmitter does not have any antennas.
2. Click the arrow next to New Repeater or Remote Antenna button ( ) on the Radio toolbar.
3. Select Remote Antenna from the menu.
4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol
( ) in the same colour as the donor transmitter. By default, the remote antenna has the same azimuth as the
donor transmitter. Its tooltip and label display the same information as displayed for the donor transmitter. As well,
its tooltip and label identify the remote antenna and the donor transmitter.
For information on defining the properties of the new remote antenna, see "Defining the Properties of a Remote
Antenna" on page 452.
Note: You can see to which base station the remote antenna is connected by clicking it; Atoll
displays a link to the donor transmitter.
Important: The table you copy data from must have the same column layout as the table you are
pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
4. Click the Donor Side tab. You can modify the following parameters:
- Under Donor-Repeater Link, select Optical Fibre Link and enter the Fibre Losses.
5. Click the Coverage Side tab. You can modify the following parameters:
- Select the Active check box. Only active remote antennas (displayed in red in the Transmitters folder in the
Data tab of the Explorer window) are calculated.
- Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual
gains. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply
before clicking the Calculate button. Atoll uses the DL total gain values to calculate the signal level received
from the remote antenna. The UL total gain value is considered in UL EbNt service area studies.
The DL total gain is applied to each power (pilot power, SCH power, etc.). It takes into account losses between
the donor transmitter and the remote antenna.
The UL total gain is applied to each terminal power. It takes into account losses between the donor transmitter
and the remote antenna.
ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( ) to access the
properties of the antenna. Then, enter the Azimuth and the Mechanical Downtilt.
iii. Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power. For infor-
mation on working with data tables, see "Working with Data Tables" on page 50.
- Under Feeders, you can modify the following information:
i. Select a Type of feeder from the list. You can click the Browse button ( ) to access the properties of
the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
6. Click the Propagation tab. Since remote antennas are taken into account during calculations, you must set prop-
agation parameters, as with transmitters. On the Propagation tab, you can modify the following: the Propagation
Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. By default, the propagation
characteristics of the remote antenna (model, calculation radius, and grid resolution) are the same as those of the
donor transmitter. For information on propagation models, see Chapter 5: Managing Calculations in Atoll.
Note: You can prevent Atoll from updating the UL and DL total gains of selected remote
antennas by creating a custom field called "FreezeTotalGain" in the Remote Antennas
table and setting the value of the field to "True." Afterwards, when you select Remote
Antennas > Calculate Gains from the Transmitters context menu, Atoll will only update
the UL and DL total gains for remote antennas with the custom field "FreezeTotalGain"
set to "False."
You can select a remote antenna on the map and change its azimuth (see "Changing the Azimuth of the Antenna
Using the Mouse" on page 32) or its position relative to the site (see "Changing the Position of the Transmitter
Relative to the Site" on page 32).
It is important not to confuse the computation zone and the focus zone or hot spot zone. The computation zone
defines the area where Atoll computes path loss matrices, coverage studies, Monte Carlo, power control simula-
tions, etc., while the focus zone or hot spot zone is the area taken into consideration when generating reports and
results.
For information on the computation zone, see "Creating a Computation Zone" on page 461.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be
studied.
2. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the fol-
lowing:
- Move the receiver to change the current position.
- Click to place the receiver at the current position. You can move the receiver again by clicking it a second time.
- Right-click the receiver to choose one of the following commands from the context menu:
- Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates.
- Target Site: Select a site from the list to place the receiver directly on a site.
4. Click the Profile tab.
5. The profile analysis appears in the Profile tab of the Point Analysis Tool window. The altitude (in metres) is
reported on the vertical axis and the receiver-transmitter distance on the horizontal axis. A blue ellipsoid indicates
the Fresnel zone between the transmitter and the receiver, with a green line indicating the line of sight (LOS). Atoll
displays the angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an
obstacle, this causes attenuation with diffraction displayed by a red vertical line (if the propagation model used
takes diffraction mechanisms into account). The main peak is the one that intersects the most with the Fresnel
ellipsoid. With some propagation models using a 3 knife-edge Deygout diffraction method, the results may display
two additional attenuations peaks. The total attenuation is displayed above the main peak.
The results of the analysis are displayed at the top of the Profile tab:
Note: You can use the same procedure to study the signal level coverage of several sites by
grouping the transmitters. For information on grouping transmitters, see "Grouping Data
Objects by a Selected Property" on page 65.
Tip: If you wish to study only sites by their status, at this step you could group them by status.
5. Select Coverage by Signal Level and click OK. A study properties dialogue appears.
City Centre 5m
City 20 m
County 50 m
State 100 m
Note: If you create a new coverage prediction from the context menu of either the Transmitters
or Predictions folder, you can select the sites using the Group By, Sort, and Filter
buttons under Configuration. Because you already selected the target sites, however,
only the Filter button is available.
- Condition tab: The coverage prediction parameters on the Conditions tab allow you to define the signals that
will be considered for each pixel (see Figure 9.14).
- At the top of the Condition tab, you can set the signal level range to be considered. In Figure 9.14, a signal
level less than or equal to -120 dBm will be considered.
- Under Server, select "All" to consider signal levels from all servers.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage
Probability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select the Carrier to be studied, or select "All" to have all carriers taken into account. The cover-
age prediction displays the strength of the received pilot signal.
- Display tab: You can modify how the results of the coverage prediction will be displayed.
- Under Display Type, select "Value Intervals."
- Under Field, select "Best Signal Level." Selecting "All" or "Best Signal Level" on the Conditions tab will
give you the same results because Atoll displays the results of the best server in either case. Selecting
"Best Signal Level" necessitates, however, the longest time for calculation.
- You can change the value intervals and their displayed colour. For information on changing display prop-
erties, see "Display Properties of Objects" on page 33.
- You can create a tooltip with information about the coverage prediction by clicking the Browse button
( ) next to the Tip Text box and selecting the fields you want to display in the tooltip.
- You can select the Add to Legend check box to add the displayed value intervals to the legend.
Note: If you change the display properties of a coverage prediction after you have calculated it,
you may make the coverage prediction invalid. You will then have to recalculate the
coverage prediction to obtain valid results.
7. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The signal level
coverage prediction can be found in the Predictions folder on the Data tab. Atoll automatically locks the results of a cover-
age prediction as soon as it is calculated, as indicated by the icon ( ) beside the coverage prediction in the Predictions
folder. When you click the Calculate button ( ), Atoll only calculates unlocked coverage predictions ( ).
Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices
using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main prop-
agation model with a shorter radius (displayed with a blue square in Figure 9.15) and a higher resolution and an extended
propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate
higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower reso-
lution path loss matrices outside the area covered by the main propagation model.
In this section, the following are explained:
"Path Loss Matrices" on page 458
"Assigning a Propagation Model" on page 459
Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matri-
ces in the Atoll document results in a more portable but significantly larger document. in the case of large radio-planning
projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case
of large radio-planning projects, saving your path loss matrices externally will help reduce the size of the file and the use
of computer resources.
The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same
radio-planning document and share the path loss matrices. In this case, the radio data is stored in a database and the path
loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and
recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path
loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to
radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual.
When you save the path loss matrices to an external directory, Atoll creates:
One file per transmitter with the extension LOS for its main path loss matrix
A DBF file with validity information for all the main matrices.
A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
To set the storage location of the path loss matrices:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss
matrices and the location for the shared path loss matrices:
- Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are
loading path loss matrices from a shared location, where you store your changes to shared path loss matrices.
Click the button beside the Private Directory ( ) and select Embedded to save the path loss matrices in
the Atoll document, or Share to select a directory where Atoll can save the path loss matrices externally.
Note: Path loss matrices you calculate locally are not stored in the same directory as shared
path loss matrices. Shared path loss matrices are stored in a read-only directory. In other
words, you can read the information from the shared path loss matrices but any changes
you make will be stored locally, either embedded in the ATL file or in a private external
folder, depending on what you have selected in Private Directory.
Caution: When you save the path loss files externally, the external files are updated as soon as
calculations are performed and not only when you save the Atoll document. In order to
keep consistency between the Atoll document and the stored calculations, you should
save the Atoll document before closing it, if you have updated the path loss matrices.
- Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a
database and the common path loss matrices are stored in a directory that is accessible to all users. Any
changes you make will not be saved to this directory; they will be saved in the location indicated in Private
Directory. The path loss matrices in the shared directory are updated by a user with administrator rights based
on the updated information in the database. For more information on shared directories, see The Administrator
Manual.
5. Click OK.
Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want,
you can check whether the path loss matrices are valid without creating a coverage prediction.
To check whether the path loss matrices are valid:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table.
5. Select one of the following display options:
- Display all the matrices: All path loss matrices are displayed.
- Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available Results table lists the following information for each displayed path loss matrix:
2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation
Model to All Transmitters" on page 460, this is the propagation model that will be used for all transmitters, except
for those to which you have assigned a propagation model either individually or as part of a group.
Important: When you assign a propagation model globally, you override any selection you might
have made to an individual transmitter or to a group of transmitters.
3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default
Propagation Model" on page 187, this is the propagation model that will be used for all transmitters whose main
propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main prop-
agation model, that is the propagation model that will be used.
Transmitters that share the same parameters and environment will usually use the same propagation model and settings.
In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common
parameters and then assigning the propagation model.
To define a main and extended propagation model for a defined group of transmitters:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select from the Group by submenu of the context menu the property by which you want to group the transmitters.
The objects in the folder are grouped by that property.
Note: You can group transmitters by several properties by using the Group By button on the
Properties dialogue. For more information, see "Advanced Grouping" on page 66.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model
to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmit-
ters.
When you assign a main and extended propagation model to a single transmitter, it overrides any changes made globally.
To define a main and extended propagation model for all transmitters:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Transmitters folder.
3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu
appears.
4. Select Properties from the context menu. The Properties dialogue appears.
5. Click the Propagation tab.
6. Under Main Matrix:
- Select a Propagation Model
- Enter a Radius and Resolution.
7. If desired, under Extended Matrix:
- Select a Propagation Model
- Enter a Radius and Resolution.
8. Click OK. The selected propagation models will be used for the selected transmitter.
Notes:
You can stop any calculations in progress by clicking the Stop Calculations button ( ) in
the toolbar.
When you click the Force Calculation button ( ) instead of the Calculate button, Atoll cal-
culates all path loss matrices, unlocked coverages, and pending simulations.
Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a computation zone. You can import it by right-clicking the Computa-
tion Zone folder on the Geo tab and selecting Import from the context menu.
Fit to Map Window: You can create a computation zone the size of the map window by selecting Fit to Map
Window from the context menu.
Note: You can save the computation zone in the user configuration. For information on
exporting the computation zone in the user configuration, see "Exporting a User
Configuration" on page 75.
Note: If you do not yet have a zone containing the transmitters you want to set as active, you
can draw a zone as explained in "Using Zones in the Map Window" on page 41.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active.
Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on
choosing and configuring a propagation model, see Chapter 5: Managing Calculations in Atoll.
Calculating path loss matrices can be extremely time and resource intensive when you are working on larger projects.
Consequently, Atoll offers you the possibility of distributing path loss calculations on several computers. You can install
the Atoll computing server application on other workstations or on servers. Once the computing server application is
installed on a workstation or server, the computer is available for distributed path loss calculation to other computers on
the network. For information on distributed calculations, see the Administrator Manual.
6. Click the Condition tab (see Figure 9.17). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered. In Figure 9.17, a signal
level less than or equal to -120 dBm will be considered.
- Under Server, select "All" to consider all servers.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select the Carrier to be studied, or select "All" to have all carriers taken into account. The coverage
prediction displays the strength of the received pilot signal.
10. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 9.18).
6. Click the Condition tab (see Figure 9.19). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered. In Figure 9.19, a signal
level less than or equal to -120 dBm or greater then -85 dBm will be considered.
- Under Server, select "Best signal level."
You can also define a Margin. Atoll will then consider the best signal level on each pixel and any other signal
level within the defined margin of the best one.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select the Carrier to be studied, or select "All" to have all carriers taken into account.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Note: You can also predict which server is the second best server on each pixel by selecting
"Second best signal level" on the Conditions tab setting "Discrete Values" as the Display
Type and "Transmitter" as the Field on the Display tab.
6. Click the Condition tab (see Figure 9.20). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered. In Figure 9.20, a signal
level less than or equal to -120 dBm will be considered.
- Under Server, select "Best signal level" and define a Margin. Atoll will then consider the best signal level on
each pixel and any other signal level within the defined margin of the best one.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select the Carrier to be studied, or select "All" to have all carriers taken into account. The coverage
prediction displays the strength of the received pilot signal.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Note: By changing the parameters selected on the Condition tab and by selecting different
results to be displayed on the Display tab, you can calculate and display information other
than that which has been explained in the preceding sections.
1. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
2. At the bottom of the Point Analysis Tool window, click the Reception tab (see Figure 9.22).
The predicted signal level from different transmitters is reported in the Reception tab in the form of a bar chart,
from the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the
colour of the transmitter it represents. In the map window, arrows from the pointer to each transmitter are displayed
in the colour of the transmitters they represent. A thick black line from the pointer to its best server is also displayed
in the map window. The best server of the pointer is the transmitter from which the pointer receives the highest
signal level. If you let the pointer rest, the signal level received from the corresponding transmitter at the pointer
location is displayed in the tooltip.
4. Right-click the Reception tab and select Properties from the context menu. The Analysis Properties dialogue
appears.
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and,
select "From Model" from the Shadowing Margin list.
- Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class.
9.2.10.7.4 Creating a Focus or Hot Spot Zone for a Coverage Prediction Report
The focus and hot spot zones define an area on which statistics can be drawn and on which reports are made. While you
can only have one focus zone, you can define several hot spot zones in addition to the focus zone.
It is important not to confuse the computation zone and the focus and hot spot zones. The computation zone defines the
area where Atoll computes path loss matrices, coverage studies, Monte Carlo, power control simulations, etc., while the
focus and hot spot zones are the areas taken into consideration when generating reports and results. When you create a
coverage prediction report, it gives the results for the focus zone and for each of the defined hot spot zones.
To define a focus zone or hot spot zone:
1. Click the Geo tab in the Explorer window.
2. Click the Expand button ( ) to expand the Zones folder.
3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or
a hot spot. The context menu appears.
4. Select Draw from the context menu.
5. Draw the focus or hot spot zone:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zones
visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but
will still be taken into account.
Note: You can only create a focus zone, and not a hot spot zone, from an existing polygon.
Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus
Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot
spot zones, you can import the name given to each zone as well.
Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map
Window from the context menu.
Note: You can save the focus or hot spot zones so that you can use them in a different Atoll
document:
- You can save the focus zone in the user configuration. For information on exporting the
focus zone in the user configuration, see "Exporting a User Configuration" on page 75.
- You can right-click the Focus Zone folder or the Hot Spot Zones folder on the Data
tab of the Explorer window and select Export from the context menu.
You can include population statistics in the focus or hot spot zone by importing a
population map. For information on importing maps, see "Importing a Raster-format Geo
Data File" on page 107.
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
a. Under Configuration, click the Import button. The Open dialogue appears.
b. Select the configuration you want to import and click Open. The imported report configuration is applied
6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed
dialogue. The coverage prediction report table appears. The report is based on the hot spot zones and on the
focus zone if available or on the hot spot zones and computation zone if there is no focus zone.
To display a report on all coverage predictions:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Define the format and content of the report:
You can select the columns that will be displayed in the report and define the order they are in:
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
a. Under Configuration, click the Import button. a appears.
b. Select the configuration you want to import and click Open. The imported report configuration is applied
4. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed
dialogue. The coverage prediction report table appears. The report shows all displayed coverage predictions in
the same order as in the Predictions folder. The report is based on the focus zone if available or on the calculation
zone if there is no focus zone.
You can include population statistics in the focus zone or hot spot zone by importing a population map. For information on
importing maps, see "Importing a Raster-format Geo Data File" on page 107. Normally, Atoll takes all geo data into
consideration, whether it is displayed or not. However, for the population statistics to be used in a report, the population
map has to be displayed.
To include population statistics in the focus zone or hot spot zone:
1. Ensure that the population geo data is visible. For information on displaying geo data, see "Displaying or Hiding
Objects on the Map Using the Explorer" on page 28.
2. Display the report as explained above.
3. Select Format > Display Columns. The Columns to Be Displayed dialogue appears.
4. Select the following columns, where "Population" is the name of the folder on the Geo tab containing the popula-
tion map:
- "Population" (Population): The number of inhabitants covered.
- "Population" (% Population): The percentage of inhabitants covered.
- "Population" (Population [total]: The total number of inhabitants inside the zone.
Atoll saves the names of the columns you select and will automatically select them the next time you create a
coverage prediction report.
5. Click OK.
If you have created a custom data map with integrable data, the data can be used in prediction reports. The data will be
summed over the coverage area for each item in the report (for example, by transmitter or threshold). The data can be
value data (revenue, number of customers, etc.) or density data (revenue/km, number of customer/km, etc.). Data is
considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example,
socio-demographic classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable
Versus Non Integrable Data" on page 124.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how you can verify if a newly added base station improves coverage.
A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal
Level" on page 463. The results are displayed in Figure 9.24. An area with poor coverage is visible on the right side of the
figure.
A new base station is added, either by creating the site and adding the transmitters, as explained in "Creating a UMTS
Base Station" on page 433, or by placing a station template, as explained in "Placing a New Station Using a Station
Template" on page 440. Once the new site base station been added, the original coverage prediction can be recalculated,
but then it would be impossible to compare the results. Instead, the original signal level coverage prediction can be copied
by selecting Duplicate from its context menu. The copy is then calculated to show the effect of the new site (see
Figure 9.25).
Figure 9.25: Signal level coverage prediction of network with new base station
4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes adding a new base station made, you should choose Difference.
5. Click OK to create the comparison. The comparison in Figure 9.26, shows clearly the area covered only by the
new base station.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how modifying transmitter tilt can improve coverage.
A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by
Transmitter" on page 464. The results are displayed in Figure 9.27. The coverage prediction shows that one transmitter is
covering its area poorly. The area is indicated with a red oval in the figure.
You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed
by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and
electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue.
Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it would be
impossible to compare the results. Instead, the original coverage prediction by can be copied by selecting Duplicate from
its context menu. The copy is then calculated, to show how modifying the antenna tilt has affected coverage (see
Figure 9.28).
As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change
in coverage, you can compare the two predictions.
To compare two predictions:
1. Right-click one of the two predictions. The context menu appears.
2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you
want to compare with the first. The Comparison Properties dialogue appears.
3. Click the General tab. You can change the Name of the comparison and add Comments.
The General tab contains information about the coverage predictions being compared, including their name and
resolution.
4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes modifying the antenna tilt made, you can choose Union. This will display all pixels
covered by both predictions in one colour and all pixels covered by only one prediction in another colour. The
increase in coverage, seen in only the second coverage prediction, will be immediately clear.
5. Click OK to create the comparison. The comparison in Figure 9.29, shows clearly the increase in coverage due to
the change in antenna tilt.
In this section, the UMTS-specific coverage predictions will be calculated using UL load factor and DL total power param-
eters defined at the cell level. For the purposes of these studies, each pixel is considered a non-interfering user with a
defined service, mobility type, and terminal.
Before making a coverage prediction, you will have to set the UL load factor and DL total power and the parameters that
define the services and users. These are explained in the following sections:
"Setting the UL Load Factor and the DL Total Power" on page 475.
"Service and User Modelling" on page 475.
Several different types of UMTS-specific coverage predictions are explained in this section. The following quality studies
are explained:
"Making a Pilot Signal Quality Prediction" on page 480
"Studying Service Area (EbNt) Downlink or Uplink" on page 481
"Studying Effective Service Area" on page 482.
The following noise studies, also coverage predictions, are explained:
"Studying Downlink Total Noise" on page 485
"Calculating Pilot Pollution" on page 486.
Another type of coverage prediction, the handover study, is also explained:
"Making a Handover Status Coverage Prediction" on page 487.
You can also make a point analysis using the Point Analysis window. The analysis is calculated using UL load factor and
DL total power parameters defined at the cell level and provided for a user-definable probe receiver which has a terminal,
a mobility and a service:
"Making an AS Analysis" on page 488.
You can define a RSCP threshold to further define how results are displayed. Atoll uses the RSCP threshold to calculate
coverage predictions and to make the AS analysis. Atoll checks which pixels have a pilot signal level which exceeds the
defined RSCP threshold. Defining the RSCP threshold is explained in the following section:
"Defining the RSCP Threshold" on page 479
Interferences coming from an external project can also be modelled and is explained in "Modelling Inter-Network Interfer-
ences" on page 236.
5. To enter the same values in one column for all cells in the table:
a. Enter the value in the first row in the column.
b. Select the entire column.
c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
Modelling Services
Services are the various services available to subscribers. These services can be either circuit-switched or packet-
switched services. This section explains how to create a service. However, only the following parameters are used in
predictions:
R99 bearer parameters
Downgrading capabilities
Handover capabilities
HSPA capabilities
Body loss
HSPA application throughput parameters
Before you can model services, you must have defined R99 bearers. For information on defining R99 radio bearers, see
"Defining R99 Radio Bearers" on page 550.
To create or modify a service:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the UMTS Parameters folder.
3. Right-click the Services folder. The context menu appears.
4. Select New from the context menu. The Services New Element Properties dialogue appears.
Note: You can modify the properties of an existing service by right-clicking the service in the
Services folder and selecting Properties from the context menu.
5. You can edit the fields on the General tab to define the new service. Some fields depend on the Type of service
you choose. You can change the following parameters:
- Name: Atoll proposes a name for the new service, but you can change the name to something more descrip-
tive.
- R99 Radio Bearer: Select an R99 radio bearer from the list. If you want to edit the settings of the selected
R99 radio bearer, click the Browse button ( ) to open the bearers Properties dialogue.
- Type: You can select either Circuit or Packet as the service type.
If you want the service to be able to use HSDPA channels, select Packet and the HSDPA check box.
Note: The HSDPA service is linked to a R99 bearer in order to manage the connection to the
R99-dedicated channel A-DPCH
For packet services that can use HSDPA channels, you have the following options:
- A-DPCH Activity Factor: The uplink and downlink A-DPCH activity factors (for services that support
HSDPA) are used to estimate the average power on A-DPCH channels.
- Average Requested Rate: You can enter the average requested rate for uplink and downlink. This rate
is the requested average rate which guarantees a minimum average downlink rate during an HSDPA call.
It is used twice in a simulation: once during user distribution generation in order to calculate the number
of HSDPA users attempting a connection and then during power control as a quality target to be compared
to the real obtained average throughput.
- Application Throughput: Under Application Throughput, you can set a Scaling Factor between the
application throughput and the RLC (Radio Link Control) throughput and a throughput Offset. These
parameters model the header information and other supplementary data that does not appear at the appli-
cation level.
If you want the service to be able to use HSUPA channels, select Packet, the HSDPA check box, and the
HSUPA check box. For packet services that can use HSUPA channels, you have the following options:
- E-DPCCH Activity Factor: The uplink and downlink E-DPCCH activity factors (for services that support
HSUPA) are used to estimate the average power on E-DPCCH channels.
- Average Requested Rate: You can enter the average requested rate for uplink and downlink. This rate
is the requested average rate which guarantees a minimum average rate during an HSUPA call. It is used
twice in a simulation: once during user distribution generation in order to calculate the number of HSUPA
users attempting a connection and then during power control as a quality target to be compared to the real
obtained average throughput.
- Application Throughput: Under Application Throughput, you can set a Scaling Factor between the
application throughput and the RLC (Radio Link Control) throughput and a throughput Offset. These
parameters model the header information and other supplementary data that does not appear at the appli-
cation level.
If you select Packet to create R99-bearer packet services that do not use HSDPA or HSUPA, you have the
following option:
- Efficiency Factor: The uplink and downlink efficiency factors are used to determine duration of usage by
the user during Monte-Carlo simulations. It does this by determining the average usage of the network by
the user. This paremeter is used when working with traffic maps per user profile only.
- Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity
for each user during Monte-Carlo simulations. This parameter is used when working with traffic maps per
sector and traffic maps per user density.
- Average Requested Rate: You can enter the average requested rate for uplink and downlink. This rate
is the average rate obtained by a user of the service. It is used in simulations during user distribution
generation to calculate the number of users attempting a connection and to determine their activity status.
If you select Circuit, you have the following options.
- Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity
for each user during Monte-Carlo simulations.
- Average Requested Rate: You can enter the average requested rate for uplink and downlink. This rate
is the average rate obtained by a user of the service. It is used in simulations during user distribution
generation to calculate the number of users attempting a connection and to determine their activity status.
- Preferred Carrier: You can select one of the available carriers or all carriers. The specified carrier is consid-
ered in simulation when admitting a transmitter to the mobile active set. If the transmitter uses the specified
carrier, Atoll selects it. Otherwise, it will choose another one, using the carrier selection mode defined in the
site equipment properties. The carrier specified for the service is not used in predictions (i.e., AS analysis and
coverage predictions). In predictions, Atoll considers the carrier selection mode defined in the site equipment
properties. If no preferred carrier is specified in the service properties, it will consider the carrier selection
mode defined in the site equipment properties.
- Rate Downgrading: Select the Rate Downgrading check box if the service supports rate downgrading on
uplink and downkink.
- Soft Handoff Allowed: Select the Soft Handoff Allowed check box if you want the network to be able to use
soft handoff with this service.
- Priority: Enter a priority for this service. "0" is the lowest priority.
- Body Loss: Enter a body loss for the service. The body loss is the loss due to the body of the user. For
example, in a voice connection the body loss, due to the proximity of the users head, is estimated to be 3dB.
6. If you selected Circuit as the Type in step 5., continue to step 7. If you selected Packet as the Type in step 5.,
an additional tab, the Packet tab, appears. Click the Packet tab.
In the Packet tab, you can set the following parameters for packet switched services:
In UMTS, information about receiver mobility is important to efficiently manage the active set: a mobile used by someone
travelling a certain speed and a mobile used by a pedestrian will not necessarily be connected to the same transmitters.
EcI0 requirements and Eb/Nt targets per radio bearer and per link (up and down) are largely dependent on mobile speed.
The following parameters are used in predictions:
EcI0 threshold
HS-SCCH EcNt Threshold
To create or modify a mobility type:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the UMTS Parameters folder.
3. Right-click the Mobility Types folder. The context menu appears.
4. Select New from the context menu. The Mobility Types New Element Properties dialogue appears.
Note: You can modify the properties of an existing mobility type by right-clicking the mobility
type in the Mobility Types folder and selecting Properties from the context menu.
5. On the General tab, you can enter or modify the following parameters in the Mobility Types New Element Prop-
erties dialogue:
- Name: Enter or modify the descriptive name for the mobility type.
- Average Speed: Enter or modify an average speed for the mobility type. This field is for information only; the
average speed is not used by any calculation.
- EcI0 Threshold: Enter or modify the minimum EcI0 required from a transmitter to enter the active set. This
value must be verified for the best server.
- HS-SCCH EcNt Threshold: Enter or modify the minimum quality required in order for the HSDPA link to be
available. This parameter is used by Atoll to determine the HS-SCCH power when the user has selected
dynamic allocation in the cell properties. For static allocation, Atoll calculates the HS-SCCH EcNt from the
HS-SCCH power set in the cell properties and compares it to this threshold. This field is only used with
HSDPA.
6. On the MBMS tab, you can enter the Eb/Nt vs. Throughput graph in the Eb/Nt = f(Throughput) field. Clicking the
Graph button opens a dialogue in which you can view and edit the Eb/Nt vs. Throughput graph.
This tab is only available if the optional MBMS feature has been activated. Activating this optional feature requires
data structure modifications (for more information, see the Administrator Manual).
7. Click OK.
Modelling Terminals
In UMTS, a terminal is the user equipment that is used in the network, for example, a mobile phone, a PDA, or a cars on-
board navigation device.
The following parameters are used in predictions:
Receiver equipment
Main and secondary bands
Maximum terminal power
Gain and losses
Noise figures
Active set size
DL rake factor
Rho factor
Compressed mode capability
HSPA capability and HSPA-specific categories:
- UE category
- Number of reception antenna ports
- MUD factor (for HSDPA only).
To create or modify a terminal:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the UMTS Parameters folder.
3. Right-click the Terminals folder. The context menu appears.
4. Select New from the context menu. The Terminals New Element Properties dialogue appears.
Note: You can modify the properties of an existing terminal by right-clicking the terminal in the
Terminal folder and selecting Properties from the context menu.
5. Click the General tab. You can modify the following parameters:
- Name: You can change the name of the terminal.
- Reception Equipment: Select a type of reception equipment from the list. You can create a new type of
reception equipment by opening the Reception Equipment table. To open the Reception Equipment table,
right-click the Terminals folder in the UMTS Parameters folder on the Data tab and select Reception Equip-
ment from the context menu.
- Main Band: Select the frequency band with which the terminal is compatible and enter the terminal Noise
Figure for the main frequency.
- Secondary Band: Select a second frequency band with which the terminal is compatible and enter the ter-
minal Noise Figure for the second frequency. Leave the Secondary Band field empty if the terminal works
only on one frequency band.
Note: There are two different ways of defining dual-band terminals. Depending on the
configuration, Atoll processes dual-band terminal users differently in the Monte-Carlo
simulation.
- The first one consists of defining main and secondary frequency bands. This enables
you to give a higher priority to one frequency band in the Monte-Carlo simulation (the
main frequency band will have the higher priority). A user with such a dual-band termi-
nal will be connected to transmitters using the main frequency band if carriers on this
frequency band are not overloaded. In case of overloading, he will be connected to
transmitters using the secondary frequency band.
- The second consists of selecting "All" as main frequency band. This means that the
terminal works on any frequency band without any priority. In this case, the user can
be connected to transmitters using any frequency band.
In coverage predictions, both configurations give the same results. The priority of frequen-
cy bands is not taken into account.
- Min. Power: Set the minimum transmission power. The minimum and maximum transmission power make up
the dynamic range for uplink power control.
- Max Power: Set the maximum transmission power.
- Gain: Set the antenna gain.
- Losses: Set the reception losses.
- Active Set Size: Set the active set size. The active set size is the maximum number of transmitters to which
a terminal can be connected at one time.
- DL Rake Factor: Set the DL rake factor. This enables Atoll to model the rake receiver on DL.
Note: The rake efficiency factor, used for calculating recombination in uplink has to be set in the
site equipment properties. For information on setting site equipment properties, see
"Creating Site Equipment" on page 552.
- Rho factor (%): This parameter enables Atoll to take into account the self-interference produced by the ter-
minal. Because hardware equipment is not perfect, the input signal experiences some distortion which affects,
in turn, the output signal. This factor defines how much distortion the system generates. Entering 100% means
the system is perfect (there is no distortion) and the output signal will be 100% equal to the input signal. On
the other hand, if you specify a value different than 100%, Atoll considers that the transmitted energy is not
100% signal and contains a small percentage of interference generated by the equipment, i.e., self-interfer-
ence. Atoll considers this parameter to calculate the signal to noise ratio in the uplink.
- Compressed Mode: Check the Compressed Mode check box if the terminal uses compressed mode. Com-
pressed mode is generally used to prepare hard-handover of users with single receiver terminals.
6. Click the HSPA tab.
You can define if the terminal supports HSPA functionality. You can choose between None (i.e. R99 support only),
HSDPA or HSPA (i.e HSDPA and HSUPA).
- UE Category: Select a user equipment category. HSDPA user equipment capabilities are standardised into
12 different categories according to 3GPP specifications.
- MUD Factor: Enter a multi-user detection factor (MUD). MUD is based on an algorithm used to improve
mobile receiver capacity. It reduces intra-cell interference and allows for higher EcNt. MUD is modelled by a
coefficient from 0 to 1; this factor is considered in calculating DL interference. If MUD is not supported, enter
"0."
- Number of Reception Antenna Ports: Select the number of reception antenna ports available on the ter-
minal for MIMO.
If you have selected the HSDPA supported check box, you can modify the following parameters under HSDPA:
- UE Category: Select a user equipment category. HSUPA user equipment capabilities are standardised into
6 different categories according to 3GPP specifications.
7. Click OK.
Note: A table listing quality indicators (BER, BLER, etc.) to be analysed is available. Quality
studies proposed by Atoll depend on quality indicators specified in this table.
A pilot signal quality prediction enables you to identify areas where there is at least one transmitter whose pilot quality is
received sufficiently well to be added to the probe mobile active set.
Atoll calculates the best pilot quality received on each pixel. Then, depending on the coverage prediction definition, it
compares this value either to the EcI0 threshold defined for the selected mobility type, or to user-defined EcI0 thresholds.
The pixel is coloured if the condition is fulfilled (in other words, if the best EcI0 is higher than the EcI0 mobility threshold
or specified EcI0 thresholds).
To make a pilot signal quality prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Pilot Reception Analysis (Ec/I0) and click OK. The coverage prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 475. You
must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or
for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you
can make the coverage prediction on a specific carrier or on all carriers of any frequency band for the selected
terminal, or for all the carriers of all the frequency bands.
If you want the pilot signal quality prediction to consider shadowing, you can select the Shadowing taken into
account check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
Figure 9.30: Load condition settings for a coverage prediction on pilot quality
- Where at least one transmitter is in the active set: Select "Unique" as the Display Type.
- Where at least one transmitter is in the active set, with information on the best server: Select "Discrete
Value" as the Display Type and "Transmitter" as the Field.
- The pilot quality relative to the EcI0 threshold: Select "Value Intervals" as the Display Type and "EcI0
margin (dB)" as the Field.
8. Click OK to save your settings.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the pilot signal quality prediction. The progress
of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Atoll calculates the traffic channel quality (as defined by EbNt) when using the maximum power allowed, i.e., the maxi-
mum traffic channel power allowed per cell for downlink and the maximum terminal power for uplink. In the coverage
prediction, the downlink or uplink service area is limited by the maximum power allowed and by the pilot quality. If the
received pilot quality is insufficient, Atoll will not display the traffic channel quality. The mobile handover status is taken in
consideration to evaluate the downlink and uplink traffic channel quality (EbNt). Atoll combines the signal from each trans-
mitter in the probe mobile active set.
To make a coverage prediction on service area (Eb/Nt) downlink or uplink:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select one of the following studies and click OK:
- Service Area (Eb/Nt) Downlink
- Service Area (Eb/Nt) Uplink
The prediction Properties dialogue appears.
Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on
load conditions taken from a simulation. Atoll will calculate the coverage prediction using the UL load factor and
the DL total power defined in the cell properties.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 475. You
must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or
for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you
can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected
terminal, or for all carriers of all the frequency bands.
If you want the service area (EbNt) coverage prediction to consider shadowing, you can select the Shadowing
taken into account check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
You can select the Downgrading Allowed check box if you want the service area (EbNt) prediction to take into
consideration circumstances when the R99 bearer is downgraded. When downgrading is enabled and if the
selected service supports rate downgrading, Atoll will consider only the lowest radio bearer.
- The traffic channel quality relative to the EbNt threshold: Select "Value Intervals" as the Display Type
and "EbNt Margin (dB)" as the Field.
- The power required to reach the EbNt threshold: Select "Value Intervals" as the Display Type and
"Required Power (dB)" as the Field.
- Where traffic channel quality exceeds the EbNt threshold for each mobility type: On the Condition tab,
select "All" as the Mobility Type. The parameters on the Display tab are automatically set.
For a service area (EbNt) uplink coverage prediction, you can also display the following result:
- The gain due to soft handover: Select "Value Intervals" as the Display Type and "Soft Handover Gain" as
the Field.
8. Click OK to save your settings.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the service area (EbNt) coverage prediction.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
The effective service area is the intersection zone between the pilot reception area, and the uplink and downlink service
areas. In other words, the effective service area prediction calculates where a service actually is available for the probe
mobile.
To make an effective service area prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Effective Service Area and click OK. The coverage prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 475. You
must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or
for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you
can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected
terminal, or for all carriers of all the frequency bands.
If you want the effective service area prediction to consider shadowing, you can select the Shadowing taken into
account check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
You can select the Downgrading Allowed check box if you want the effective service area prediction to take into
consideration circumstances when the R99 bearer is downgraded. When downgrading is enabled and if the
selected service supports rate downgrading, Atoll will consider only the lowest radio bearer.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the effective service area prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
This coverage prediction is only available if the optional MBMS feature has been activated. Activating this optional feature
requires data structure modifications (for more information, see the Administrator Manual).
MBMS, Multimedia Broadcast and Multicast Service, offers a solution for broadcasting television channels over SCCPCH
channels in UMTS. SCCPCH (FACH) does not perform power control in order to cover the entire cell area. Atoll calculates
the MBMS channel quality (as defined by EbNt) using the MBMS power defined for an MBMS SCCPCH channel. In the
coverage prediction, the MBMS service area is limited by the maximum power allowed and by the pilot quality. If the
received pilot quality is insufficient, Atoll will not display the MBMS channel quality.
To make a coverage prediction on MBMS service area (Eb/Nt) :
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Service Area (Eb/Nt) MBMS and click OK. The prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 170. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 57.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal and Mobility, as defined in "Service and User Modelling" on page 475. The coverage
prediction is calculated for an MBMS service. You must also select which Carrier is to be considered. You can
make the coverage prediction for a specific carrier or for all carriers of the main frequency band for the selected
terminal. If you have selected a dual-band terminal, you can make the coverage prediction for a specific carrier or
for all carriers of any frequency band for the selected terminal, or for all carriers of all the frequency bands. You
must also select an MBMS Channel.
If you want the service area (EbNt) coverage prediction to consider shadowing, you can select the Shadowing
taken into account check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the service area (EbNt) coverage prediction.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
You can create a quality study based on a given quality indicators (BER, BLER, or FER). The coverage prediction will show
for each pixel the measurement of the selected quality indicator.
This type of coverage prediction is not available in the list of standard studies; you can, however, use quality indicators in
a study by first ensuring that the parameters of the quality indicators have been correctly set and then creating a coverage
prediction, selecting display parameters that use these quality indicators.
Before you define the quality study, you must ensure that the parameters of the quality indicators have been correctly set.
To check the parameters of the quality indicators:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the UMTS Parameters folder.
3. Right-click the Services folder. The context menu appears.
4. Select Quality Indicators from the context menu. The Quality Indicators table appears.
For each quality indicator in the Name column, you can set the following parameters:
- Used for Packet Services: Select the Used for Packet Services check box if the quality indicator is to be
used for packet services.
- Used for Circuit Services: Select the Used for Circuit Services check box if the quality indicator is to be
used for circuit services.
- Measured Parameter for QI: From the list, select the parameter that will be measured to indicate quality.
- QI Interpolation: Select the QI Interpolation check box if you want Atoll to interpolate between two existing
QI values. Clear the QI Interpolation check box if you want Atoll to take the closest QI value.
5. Close the Quality Indicators table.
6. In the UMTS Parameters folder, right-click the Terminals folder. The context menu appears.
7. Select Reception Equipment from the context menu. The Reception Equipment table appears.
"Standard" is the default reception equipment type for all terminals.
8. Double-click the reception equipment type for which you want to verify the correspondence between the measured
quality and the quality indicator. The reception equipment types Properties dialogue appears.
9. Click the Quality Graphs tab.
10. Ensure that a Quality Indicator has been chosen for each R99 Bearer. You can edit the values in the DL and
UL Quality Indicator Tables by clicking directly on the table entry, or by selecting the Quality Indicator and
clicking the Downlink Quality Graphs or the Uplink Quality Graphs buttons.
11. Click OK to close the reception equipment types Properties dialogue.
Once you have ensured that the parameters of the quality indicators have been correctly set, you can use the measured
quality to create a quality study. How you define a coverage prediction according to the measured quality indicator,
depends several parameters:
The settings made in the Quality Indicators table
The service you want to study
The quality indicator you want to use (BER, BLER, or FER)
The coverage prediction you want to use (Pilot Reception Analysis, the Service Area Downlink, or Service Area
Uplink).
In the following example, you will create a quality study showing BLER, for a user on foot, and with mobile internet access.
To create a quality study showing BLER for a user on foot, and with mobile internet access:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Service Area (EbNt) Downlink and click OK. the coverage prediction Properties dialogue appears.
5. Click the General tab. On the General tab, you can change the default Name and Resolution of the service area
(EbNt) downlink prediction, and add some Comments. Under Configuration, you can create a Filter to select
which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab.
Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on
load conditions taken from a simulation. Atoll will calculate the coverage prediction using the UL load factor and
the DL total power defined in the cell properties.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
- Terminal: Select the appropriate terminal for mobile Internet access from the Terminal list.
- Service: Select "Mobile Internet Access" from the Service list.
- Mobility: Select "Pedestrian" from the Mobility list.
- Carrier: Select a carrier of a frequency band or a frequency band if you want to study a specific carrier or all
the carriers of a frequency band for the selected terminal. Otherwise, select "All."
If you want the service area (EbNt) downlink prediction to consider shadowing, you can select the Shadowing
taken into account check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
You can select the Downgrading Allowed check box if you want the service area (EbNt) downlink prediction to
take into consideration circumstances when the R99 bearer is downgraded. When downgrading is enabled and if
the selected service supports rate downgrading, Atoll will consider only the lowest radio bearer.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the effective service area prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Atoll calculates for each pixel the DL traffic channel quality (EbNt) (provided when using the maximum traffic channel
power allowed). Then, it calculates the corresponding BLER value from the quality graph (BLER=f(DL EbNt)). The pixel
is coloured if the condition is fulfilled (i.e., if BLER is evaluated as being higher than the specified threshold).
In the downlink total noise prediction, Atoll calculates and displays the areas where the downlink total noise or the down-
link noise rise exceeds a set threshold.
To make a downlink total noise or downlink noise rise prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Downlink Total Noise and click OK. The coverage prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 475. You
must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or
for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you
can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected
terminal, or for all carriers of all the frequency bands.
If you want the downlink total noise or downlink noise rise prediction to consider shadowing, you can select the
Shadowing taken into account check box and enter a percentage in the Cell Edge Coverage Probability text
box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- Downlink total noise prediction: When making a downlink total noise prediction, select one of the following
in the Field list:
- Min. Noise Level
- Average Noise Level
- Max Noise Level
- Downlink noise rise prediction: When making a downlink noise rise prediction, select one of the following
in the Field list:
- Min. Noise Rise
- Average Noise Rise
- Max Noise Rise
For information on defining display properties, see "Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the downlink total noise or downlink noise rise
prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
A transmitter which fulfils all the criteria to enter a mobiles active set but which is not admitted because the active set limit
has already been reached is considered a polluter.
In the pilot pollution prediction, Atoll calculates and displays the areas where the probe mobile is interfered by the pilot
signal from polluter transmitters.
To make a pilot pollution prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Pilot Pollution and click OK. The coverage prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 475. You
must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or
for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you
can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected
terminal, or for all carriers of all the frequency bands.
If you want the pilot pollution prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
For a pilot pollution prediction, the Display Type "Value Intervals" and the Field "Number of Polluters" are
selected by default. For information on defining display properties, see "Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the pilot pollution prediction. The progress of
the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 475. You
must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier or
for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal, you
can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected
terminal, or for all carriers of all the frequency bands.
If you want the downlink total noise or downlink noise rise prediction to consider shadowing, you can select the
Shadowing taken into account check box and enter a percentage in the Cell Edge Coverage Probability text
box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage pre-
diction will display.
To display the handover status:
9. Click the Calculate button ( ) in the Radio toolbar to calculate the handover status coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
1. Click the Point Analysis button ( ) on the toolbar. The Point Analysis Tool window appears (see
Figure 9.32).
2. Click the AS Analysis tab.
3. At the top of the AS Analysis tab, select "Cells Table" from Load Conditions.
4. If you are making an AS analysis to verify a coverage prediction, you can recreate the conditions of the coverage
prediction:
a. Select the same Terminal, Service, and Mobility studied in the coverage prediction.
b. Select the Carrier to be considered. You can make the AS analysis for a specific carrier or for all carriers of
the main frequency band of the selected terminal. If you have selected a dual-band terminal, you can make
the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected terminal,
or for all carriers of all the frequency bands.
c. Select the Rate Downgrading check box if rate downgrading was selected in the coverage prediction. When
downgrading is enabled and if the selected service supports rate downgrading, Atoll will consider only the low-
est radio bearer.
d. Right-click the Point Analysis window and select Properties from the context menu. The Properties dia-
logue appears.
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and,
select "EcI0" from the Shadowing Margin list.
- Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class.
e. Click OK to close the Properties dialogue.
5. Move the pointer over the map to make an active set analysis for the current location of the pointer.
As you move the pointer, Atoll indicates on the map which is the best server for the current position (see
Figure 9.31).
Information on the current position is given on the AS Analysis tab of the Point Analysis window. See Figure 9.32
on page 489 for an explanation of the displayed information.
6. Click the map to leave the point analysis pointer at its current position.
To move the pointer again, click the point analysis pointer on the map and drag it to a new position.
7. Click the Point Analysis button ( ) on the toolbar again to end the point analysis.
Select the load conditions to use in This vertical bar represents the lower boundary of the
this analysis (DL Power, UL Load, Select the parameters of the probe user to active set (defined as the signal value of the best
etc.) from simulations or from the be studied. server at the current point minus the AS_Threshold -
Cells table. defined in the properties of the best server).
The pilot reception in terms of active set components for the set This vertical bar The connection status (pilot and uplink
conditions. The active set is displayed in grey. Solid bars represents the EcI0 and downlink traffic) for the current point.
indicate the cells which respect the active set constraints. Even threshold to become the
if more cells respect the constraints, the active set size is limited best server (threshold : successful connection
to the number defined in the terminal properties and is a function defined in the mobility
: failed connection
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Mobility, as defined in "Service and User Modelling" on page 475. For an HSDPA coverage
prediction, under Terminal, you must chose an HSDPA-capable terminal and, under Service, you must chose a
service with HSDPA.
You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier
or for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal,
you can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected
terminal, or for all carriers of all the frequency bands.
Under HSDPA Radio Bearer, select either "All" to consider all possible HSDPA radio bearers in the study or an
HSDPA radio bearer index to calculate the study for a certain bearer. Display options available in the Display tab
depend on what you have selected here.
If you want to consider shadowing, you can select the Shadowing taken into account check box and enter a
percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage pre-
diction will display.
If you have selected "All" as the HSDPA Radio Bearer in the Condition tab, you can set the following parameters:
- The HS-PDSCH Ec/Nt relative to the EcNt threshold: Select "HS-PDSCH Ec/Nt" as the Field. Atoll cal-
culates the best HS-PDSCH EcNt on each pixel.
- The channel quality indicator (CQI) relative to the EcNt threshold: Select "CQI" as the Field. Atoll
displays either the CPICH CQI or the HS-PDSCH CQI, depending on the option selected under HSDPA
on the Global Parameters tab of the Transmitter Properties dialogue (see "Creating or Modifying a
Transmitter" on page 439).
- The MAC rate relative to the threshold: Select "MAC Rate (kbps)" as the Field. Atoll calculates the
MAC rate from the transport block size of the selected HSDPA bearer.
- The MAC throughput relative to the threshold: Select "MAC Throughput (kbps)" as the Field. The MAC
throughput is calculated from the MAC rate.
- The RLC peak rate relative to the threshold: Select "RLC Peak Rate (kbps)" as the Field. Atoll displays
the RLC peak rate that the selected HSDPA bearer can be supplied with. The RLC peak rate is a charac-
teristic of the HSDPA bearer.
- The RLC peak throughput relative to the threshold: Select "RLC Peak Throughput (kbps)" as the
Field. Atoll calculates the RLC peak throughput from the RLC peak rate.
- The average RLC throughput relative to the threshold: Select "Average RLC Throughput (kbps)" as
the Field.
- The application throughput relative to the threshold: Select "Application Throughput (kbps)" as the
Field. Using the RLC peak rate, the BLER, the HSDPA service scaling factor, and the throughput offset,
Atoll calculates the application throughput. The application throughput represents the net throughput with-
out coding (redundancy, overhead, addressing, etc.).
Atoll can consider several HSDPA users per pixel. When the coverage prediction is not based on a simulation,
this value is taken from the cell properties. Atoll considers the defined number of HSDPA users on each pixel
and determines the best HSDPA bearer that each user can obtain. The coverage prediction results displayed
are the average results for one user. The HSDPA power of the cell is shared between the HSDPA users. You
can display the following results:
- The average MAC throughput per mobile relative to the threshold: Select "MAC Throughput per
Mobile (kbps)" as the Field. Atoll calculates the average MAC throughput per mobile from the from the
MAC throughput of each user.
- The average RLC throughput per mobile relative to the threshold: Select "RLC Throughput per
Mobile (kbps)" as the Field. Atoll calculates the average RLC throughput per mobile from the RLC
throughput of each user.
- The average application throughput per mobile relative to the threshold: Select "Application
Throughput per Mobile (kbps)" as the Field. Using the RLC peak rate, the BLER, the HSDPA service scal-
ing factor, and the throughput offset, Atoll calculates the average application throughput per mobile from
the application throughput of each user.
If you have selected an HSDPA radio bearer index as the HSDPA Radio Bearer on the Condition tab, you can
define settings to display:
- Where a certain RLC peak rate is available with different cell edge coverage probabilities: On the Con-
dition tab, do not consider shadowing and select an HSDPA radio bearer index. On the Display tab, the Dis-
play Type "Value Intervals" based on the Field "Cell Edge Coverage Probability (%)" is selected by default.
When no value is defined in the Cells table for the total transmitted power and the number of HSDPA users, Atoll
uses the following default values:
- Total transmitted power = 50 % of the maximum power (i.e, 40 dBm if the maximum power is set to
43 dBm)
- Number of HSDPA users = 1
On the other hand, no default value is used for the HSDPA power; this parameter must be defined by the user.
For information on selecting the best bearer, see the Technical Reference Guide. For information on defining
display properties, see "Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the handover status coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Mobility, as defined in "Service and User Modelling" on page 475. For an HSUPA coverage
prediction, under Terminal, you must chose an HSUPA-capable terminal and, under Service, you must chose a
service with HSUPA.
You must also select which Carrier is to be considered. You can make the coverage prediction for a specific carrier
or for all carriers of the main frequency band for the selected terminal. If you have selected a dual-band terminal,
you can make the coverage prediction for a specific carrier or for all carriers of any frequency band for the selected
terminal, or for all carriers of all the frequency bands.
HSUPA Resources: Atoll can calculate the HSUPA coverage prediction in one of two ways:
- For a single user: After allocating capacity to all R99 users, the entire remaining load will be allocated to a
single HSUPA user.
- Shared by HSUPA users defined or calculated per cell: After allocating capacity to all R99 users, the
remaining load of the cell will be shared equally between all the HSUPA users. When the coverage prediction
is not based on a simulation, the number of HSUPA users is taken from the cell properties. The displayed
results of the coverage prediction will be for one user.
When no value is defined in the Cells table, Atoll uses the following default values:
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage pre-
diction will display. You can set parameters to display the following results:
- The required E-DPDCH EcNt relative to the threshold: Select "Required E-DPDCH EcNt (dB)" as the
Field. Atoll selects the best HSUPA bearer whose required E-DPDCH EcNt does not exceed the maximum
E-DPDCH EcNt allowed. The required E-DPDCH EcNt is a property of the selected HSUPA bearer.
- The power required for the selected terminal relative to the threshold: Select "Required Terminal Power
(dBm)" as the Field. Atoll calculates the required terminal power from the required E-DPDCH Ec/Nt.
- The MAC Rate relative to the threshold: Select "MAC Rate (kbps)" as the Field. Atoll calculates the MAC
rate from the transport block size of the selected HSUPA bearer.
- The RLC peak rate relative to the threshold: Select "RLC Peak Rate (kbps)" as the Field. Atoll displays
the RLC peak rate that the selected HSUPA bearer can supply. The RLC peak rate is a property of the HSUPA
bearer.
- The guaranteed RLC throughput relative to the threshold: Select "Min RLC Throughput (kbps)" as the
Field.
- The average RLC throughput relative to the threshold: Select "Average RLC Throughput (kbps)" as the
Field. Atoll calculates the average RLC throughput on the uplink using the early termination probabilities,
defined in the terminals reception equipment, to model HARQ (Hybrid Automatic Repeat Request).
- The application throughput relative to the threshold: Select "Application Throughput (kbps)" as the Field.
Using the RLC peak rate, the BLER, the HSUPA service scaling factor, and the throughput offset, Atoll cal-
culates the application throughput. The application throughput represents the net throughput without coding
(redundancy, overhead, addressing, etc.).
- The average application throughput relative to the threshold: Select "Average Application Throughput
(kbps)" as the Field. Atoll calculates the average application throughput on the uplink using the early termi-
nation probabilities, defined in the terminals reception equipment, to model HARQ (Hybrid Automatic Repeat
Request).
For information on selecting the best bearer, see the Technical Reference Guide. For information on defining
display properties, see "Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the handover status coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
information on creating a focus zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on
page 468. For information on grouping transmitters in the Explorer window, see "Grouping Data Objects" on page 65.
Atoll supports the following neighbour types in a UMTS network:
Intra-technology Neighbours: Intra-technology neighbours are cells defined as neighbours that also use UMTS.
Intra-technology neighbours can be divided into:
- Intra-carrier Neighbours: Cells defined as neighbours which perform handover using the same carrier.
- Inter-carrier Neighbours: Cells defined as neighbours which perform handover using a different carrier.
Inter-technology Neighbours: Inter-technology neighbours are cells defined as neighbours that use a tech-
nology other than UMTS.
In this section, the following are explained:
"Importing Neighbours" on page 493
"Defining Exceptional Pairs" on page 493
"Allocating Neighbours Automatically" on page 493
"Checking Automatic Allocation Results" on page 497
"Allocating and Deleting Neighbours per Cell" on page 499
"Checking the Consistency of the Neighbour Allocation Plan" on page 501
"Exporting Neighbours" on page 502.
7. Under Exceptional Pairs, create a new exceptional pair in the row marked with the New Row icon ( ):
a. Select the cell from the list in the Neighbours column.
b. In the Status column, select one of the following:
- Forced: The selected cell will always be a neighbour of the reference cell.
- Forbidden: The selected cell will never be a neighbour of the reference cell.
8. Click elsewhere in the table when you have finished creating the new exceptional pair.
9. Click OK.
Notes: You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology
Neighbours table. You can open this table by right-clicking the Transmitters folder and
selecting Cells > Neighbours > Intra-Technology Exceptional Pairs.
3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Alloca-
tion dialogue appears.
4. Click the Intra-Carrier Neighbours tab. You can set the following parameters:
- Max. Inter-site Distance: Set the maximum distance between the reference cell and a possible neighbour.
- Max. Number of Neighbours: Set the maximum number of intra-carrier neighbours that can be allocated to
a cell. This value can be either set here for all transmitters, or specified for each transmitter in the Cells table.
- Coverage Conditions: The coverage conditions must be respected for a cell to be considered as a neighbour.
Click Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the
following parameters:
- Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by reference cell A
and possible neighbour cell B.
- Min. EcI0: Enter the minimum EcI0 which must be provided by reference cell A in an overlapping area.
Reference cell A must also be the best server in terms of pilot quality in the overlapping area.
- EcI0 Margin: Enter the maximum difference of EcI0 between reference cell A and possible neighbour
cell B in the overlapping area.
- DL Load Contributing to I0: You can let Atoll base the interference ratio on the total power used as
defined in the properties for each cell (Defined per Cell) or on a percentage of the maximum power
(Global Value).
- Shadowing taken into account: If desired, select the Shadowing taken into account check box and
enter a Cell Edge Coverage Probability.
- Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses defined per
clutter class in the calculations.
- Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic
neighbour allocation.
- % Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cells coverage area must
overlap the reference cells coverage area.
5. Select the desired calculation parameters:
- Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers
(Atoll will allocate neighbours to cells using the selected carriers).
- Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want
cells located on the same site as the reference cell to be automatically considered as neighbours.
- Force adjacent cells as neighbours: Select the Force adjacent cells as neighbours check box if you want
cells that are adjacent to the reference cell to be automatically considered as neighbours. A cell is considered
adjacent if there is at least one pixel in the reference cells coverage area where the possible neighbour cell
is the best server, or where the possible neighbour cell is the second best server in the reference cells active
set (respecting the handover margin).
- Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In
other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neigh-
bour list of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from
the list of neighbours of the reference cell.
- Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or
forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see
"Defining Exceptional Pairs" on page 493.
- Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete
all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check
box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new
neighbours to the list.
6. Click the Importance Weighting button to set the relative importance of possible neighbours:
- Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage
reasons.
- Adjacency Factor: If you have selected the Force adjacent cells as neighbours check box in step 5., set
the minimum and maximum importance of a possible neighbour cell being adjacent to the reference cell.
- Co-site Factor: If you have selected the Force co-site cells as neighbours check box in step 5., set the
minimum and maximum importance of a possible neighbour cell being located on the same site as reference
cell.
7. Click Run. Atoll begins the process of allocating intra-carrier neighbours. Atoll first checks to see whether the
path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates
them.
Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays
new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is
cleared, the Results table will be empty.
- Co-site
- Adjacency
- Symmetry
- Coverage
- Existing
- Coverage: The amount of reference cells coverage area that the neighbour overlaps, in percentage and in
square kilometres.
- Adjacency: The area of the reference cell, in percentage and in square kilometres, where the neighbour cell
is best server or second best server.
8. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atolls table
shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data
Tables" on page 50.
9. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neigh-
bours are listed in the Intra-technology Neighbours tab of each cells Properties dialogue.
To automatically allocate inter-carrier UMTS neighbours:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Alloca-
tion dialogue appears.
4. Click the Inter-Carrier Neighbours tab. You can set the following parameters:
- Max. Inter-site Distance: Set the maximum distance between the reference cell and a possible neighbour.
- Max. Number of Neighbours: Set the maximum number of inter-carrier neighbours that can be allocated to
a cell. This value can be either set here for all transmitters, or specified for each transmitter in the Cells table.
- Coverage Conditions: The coverage conditions must be respected for a cell to be considered as a neighbour.
Click Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the
following parameters:
- Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by reference cell A
and possible neighbour cell B.
- Min. EcI0: Enter the minimum EcI0 which must be provided by reference cell A and possible neighbour B
in an overlapping area. Possible neighbour B must also be the best server in terms of pilot quality in the
overlapping area.
- EcI0 Margin: Enter the EcI0 margin relative to the EcI0 of the reference cell A. See the Technical Refer-
ence Guide for an explanation of how the EcI0 margin is used in different inter-carrier handover scenarios.
- DL Load Contributing to I0: You can let Atoll base the interference ratio on the total power used as
defined in the properties for each cell (Defined per Cell) or on a percentage of the maximum power
(Global Value).
- Shadowing taken into account: If desired, select the Shadowing taken into account check box and
enter a Cell Edge Coverage Probability.
- Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic
neighbour allocation.
- % Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cells coverage area must
overlap the reference cells coverage area.
5. Select the desired calculation parameters:
- Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers
(Atoll will allocate neighbours to cells using the selected carriers).
- Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want
cells located on the same site as the reference cell to be automatically considered as neighbours.
- Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In
other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neigh-
bour list of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from
the list of neighbours of the reference cell.
- Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or
forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see
"Defining Exceptional Pairs" on page 493.
- Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete
all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check
box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new
neighbours to the list.
6. Click the Importance Weighting button to set the relative importance of possible neighbours:
- Coverage Factor: Set the minimum and maximum importance of the minimum percentage of shared cov-
erage between the possible neighbour cell and the reference cell.
- Co-site Factor: If you have selected the Force co-site cells as neighbours check box in step 5., set the
minimum and maximum importance of a possible neighbour cell being located on the same site as reference
cell.
7. Click Run. Atoll begins the process of allocating inter-carrier neighbours. Atoll first checks to see whether the
path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates
them.
Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays
new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is
cleared, the Results table will be empty.
Notes
A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already
exists and the Delete existing neighbours check box is cleared when you start the new allo-
cation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint
on the forbidden neighbour will be ignored by the algorithm because the neighbour already
exists.
When the options Force exceptional pairs and Force symmetry are selected, Atoll con-
siders the constraints between exceptional pairs in both directions in order to respect sym-
metry. On the other hand, if the neighbour relation is forced in one direction and forbidden in
the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the
Event Viewer.
You can save automatic neighbour allocation parameters in a user configuration. For informa-
tion on saving automatic neighbour allocation parameters in a user configuration, see
"Exporting a User Configuration" on page 75.
1. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
2. Select Display Options from the context menu. The Visual Management dialogue appears.
3. Under Intra-technology Neighbours, select the Display Links check box.
4. Click the Browse button ( ) beside the Display Links check box.
5. The Intra-technology Neighbour Display dialogue appears.
6. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a cell with a
unique colour.
- Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you
want Atoll to colour the cells neighbour links according to a value from the Intra-technology Neighbours
table, or according to the neighbour carrier. In this case, you can view on the map intra-carrier and inter-carrier
neighbour relations.
- Value Intervals: Select "Value Intervals" to colour the cells neighbour links according the value interval of the
value selected from the Field list. For example, you can choose to display a cells neighbours according to
their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting
factors.
Tip: You can display the number of handoff attempts for each cell-neighbour pair by first
creating a new field of Type "Integer" in the Intra-Technology Neighbour table for the
number of handoff attempts. Once you have imported or entered the values in the new
column, you can select this field from the Field list along with "Value Intervals" as the
Display Type. For information on adding a new field to a table, see "Adding a Field to an
Object Types Data Table" on page 51.
Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you
can display or hide neighbour link display types individually.
For information on changing display properties, see "Display Properties of Objects" on page 33.
7. Select the Add to Legend check box to add the displayed neighbour links to the legend.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each neighbour link.
9. Click OK to save your settings.
10. Under Advanced, select which neighbour links to display:
- Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations
where the selected cell is the reference cell and where the neighbour relation is not symmetric.
- Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations
where the selected cell is neighbour and where the neighbour relation is not symmetric.
- Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the
selected cell and the neighbour.
11. Click OK to save your settings.
12. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
- The symmetric neighbour relations of the selected (reference) cell are indicated by a line.
- The outward neighbour relations are indicated with a line with an arrow pointing at the neighbour (e.g. see
Site1_2(0)) in Figure 9.33.).
- The inward neighbour relations are indicated with a line with an arrow pointing at the selected cell (e.g. see
Site9_3(0)) in Figure 9.33.).
In Figure 9.33, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward
neighbour links are coloured as the corresponding neighbour transmitters and the inward neighbour link is
coloured as the reference transmitter as it is neighbour of Site9_3(0) here.
Figure 9.33: Intra-carrier Neighbours of Site 22_3(0) - Display According to the Neighbour
In Figure 9.34, neighbour links are displayed according to the neighbour carrier. You can view intra-carrier and
inter-carrier neighbour links. Here, all neighbour relations are symmetric.
Note: You can display either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting
either Forced Neighbours or Forbidden Neighbours.
2. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
3. Select Display Options from the context menu. The Visual Management dialogue appears.
4. Under Intra-technology Neighbours, select the Display Coverage Areas check box.
5. Click the Browse button ( ) beside the Display Coverage Areas check box.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each coverage area.
9. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( ) in the
Radio toolbar.
Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete UMTS neighbours using the Cells tab of the transmitters Properties dialogue:
1. On the map, right-click the transmitter whose neighbours you want to change. The context menu appears.
2. Select Properties from the context menu. The transmitters Properties dialogue appears.
3. Click the Cells tab.
4. On the Cells tab, there is a column for each cell. Click the Browse button ( ) beside Neighbours in the cell for
which you want to allocate or delete neighbours. The cells Properties dialogue appears.
5. Click the Intra-technology Neighbours tab.
6. If desired, you can enter the maximum number of neighbours in the following boxes:
- Max Number Inter-Carrier
- Max Number Intra-Carrier
7. To allocate a new neighbour:
a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon
( ).
b. Click elsewhere in the table to complete creating the new neighbour.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
Note: For information on working with data tables, see "Working with Data Tables" on page 50.
4. To allocate a neighbour:
a. In the row marked with the New Row icon ( ), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column.
c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
Note: You can add or delete either some forced neighbours or some forbidden neighbours using
the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table,
select the exceptional pairs to be considered, right-click the table and select Force
Exceptional Pairs in the context menu.
c. Select Delete Link and Symmetric Relation from the context menu.
10. To delete a neighbour:
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Press DEL to delete the neighbour.
You can allocate or delete intra-technology neighbours directly on the map using the mouse.
To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neigh-
bours on the map as explained in "Displaying Neighbour Relations on the Map" on page 497.
To add a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters
to the intra-technology neighbours list.
To remove a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both trans-
mitters from the intra-technology neighbours.
To add an outward neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference
transmitter to the intra-technology neighbour list of the reference transmitter.
To remove an outward neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference
transmitter from the intra-technology neighbours list of the reference transmitter.
To add an inward neighbour relation:
Click the reference transmitter on the map. Atoll displays its neighbour relations.
- If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other trans-
mitter. Atoll converts the symmetric relation to an inward non-symmetric inter-technology neighbour relation.
- If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour rela-
tion by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then
press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric
inter-technology neighbour relation.
To remove an inwards neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the trans-
mitter from the intra-technology neighbours list of the reference transmitter.
Notes:
When there is more than one cell on the transmitter, clicking the transmitter in the map window
opens a context menu allowing you to select the cell you want (see "Selecting One of Several
Transmitters or Microwave Links" on page 30).
You can add or delete either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting either
Forced Neighbours or Forbidden Neighbours.
- Empty Lists: Select the Empty Lists check box if you want to verify which cells have no neighbours (in other
words, which cells have an empty neighbour list).
- Full Lists: Which cells having the maximum number of neighbours allowed (in other words, which cells have
a full neighbour list). The maximum number of neighbours can be either set here for all transmitters, or spec-
ified for each transmitter in the Cells table.
- Lists > Max Number: Which cells having more than the maximum number of neighbours allowed. The max-
imum number of neighbours can be either set here for all transmitters, or specified for each transmitter in the
Cells table.
- Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site
neighbours.
- Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have non-
symmetric neighbour relations.
- Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced
neighbours or forbidden neighbours.
5. Click OK to perform the audit. Atoll displays the results of the audit in a new text file:
- Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the
plan audited.
- Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list)
Syntax: |CELL|
- Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours
listed in their respective neighbours lists.
Syntax: |CELL| |NUMBER| |MAX NUMBER|
- Lists > Max Number (default max number = Y): x/X; x number of cells out of a total of X having more than
Y number of neighbours listed in their respective neighbours lists.
Syntax: |CELL| |NUMBER| |MAX NUMBER|
Note: If the field Maximum number of neighbours in the Transmitters table is empty, the Full
Lists check and the Lists > Max Number check use the Default Max Number value
defined in the audit dialogue.
- Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
- Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
Notes
Within the context of primary scrambling code allocation, "neighbours" refer to intra-carrier
neighbours.
According to 3GPP specifications, the 512 possible scrambling codes can be broken down into
groups, each containing 8 codes. Because the term "group" in Atoll refers to user-defined sets
of scrambling codes, these groups of 8 codes each are referred to as "clusters" in Atoll. As
well, Atoll allows you to change the number of codes in a cluster.
4. In the row marked with the New Row icon ( ), enter a Name for the new domain.
5. Click in another cell of the table to create the new domain and add a new blank row to the table.
6. Double-click the domain to which you want to add a group. The domains Properties dialogue appears.
7. Under Groups, enter the following information for each group you want to create.
- Name: Enter a name for the new scrambling code group.
- Min.: Enter the lowest available primary scrambling code in this groups range. The minimum and maximum
scrambling codes must be entered in the format, decimal or hexadecimal, set for the Atoll document (for infor-
mation on setting the scrambling code format, see "Defining the Scrambling Code Format" on page 503).
- Max: Enter the highest available primary scrambling code in this groups range.
- Step: Enter the separation interval between each primary scrambling code.
- Excluded: Enter the scrambling codes in this range that you do not want to use.
- Extra: Enter any additional scrambling codes (i.e., outside the range defined by the Min. and Max fields) you
want to add to this group. You can enter a list of codes separated by either a comma, semi-colon, or a space.
You can also enter a range of scrambling codes separated by a hyphen. For example, entering, "1, 2, 3-5"
means that the extra scrambling codes are "1, 2, 3, 4, 5."
8. Click in another cell of the table to create the new group and add a new blank row to the table.
4. In the row marked with the New Row icon ( ), select one cell of the new exceptional pair in the Cell column
and the second cell of the new exceptional pair from the Cell_2 column.
5. Click in another cell of the table to create the new exceptional pair and add a new blank row to the table.
You can define the costs of the different types of constraints used in the automatic scrambling code allocation algorithm.
The allocation algorithm enables you to automatically allocate primary scrambling codes to cells in the current network.
You can choose among several automatic allocation strategies (for more information, see the Technical Reference Guide):
Clustered: The purpose of this strategy is to choose for a group of mutually constrained cells, scrambling codes
among a minimum number of clusters. In this case, Atoll will preferentially allocate all the codes from same
cluster.
Distributed per Cell Allocation: This strategy consists in using as many clusters as possible. Atoll will preferen-
tially allocate codes from different clusters.
One Cluster per Site: This strategy allocates one cluster to each base station, then, one code of the cluster to
each cell of each base station. When all the clusters have been allocated and there are still base stations
remaining to be allocated, Atoll reuses the clusters at another base station.
Distributed per Site: This strategy allocates a group of adjacent clusters to each base station in the network, then,
one cluster to each transmitter of the base station according to its azimuth and finally one code of the cluster to
each cell of each transmitter. The number of adjacent clusters per group depends on the number of transmitters
per base station you have in your network; this information is required to start allocation based on this strategy.
When all the groups of adjacent clusters have been allocated and there are still base stations remaining to be allo-
cated, Atoll reuses the groups of adjacent clusters at another base station.
To automatically allocate primary scrambling codes:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Primary Scrambling Codes > Automatic Allocation. The Primary Scrambling Codes dialogue
appears.
- Under Constraints, you can set the constraints on automatic scrambling code allocation.
- Existing Neighbours: Select the Existing Neighbours check box if you want to consider intra-carrier
neighbour relations and then choose the neighbourhood level to take into account:
Neighbours of a cell are referred to as the first order neighbours, neighbours neighbours are referred to
as the second order neighbours and neighbours neighbours neighbours as the third order neighbours.
First Order: No cell will be allocated the same scrambling code as its neighbours.
Second Order: No cell will be allocated the same scrambling code as its neighbours or its second order
neighbours.
Third Order: No cell will be allocated the same scrambling code as its neighbours or its second order
neighbours or its third order neighbours.
Atoll can only consider neighbour relations if neighbours have already been allocated. For information on
allocating neighbours, see "Planning Neighbours" on page 492.
Note: Atoll can take into account inter-technology neighbour relations as constraints when
allocating scrambling codes to the UMTS neighbours of a GSM transmitter. In order to
consider inter-technology neighbour relations in scrambling code allocation, you must
make the Transmitters folder of the GSM Atoll document accessible in the UMTS Atoll
document. For information on making links between GSM and UMTS Atoll documents,
see "Creating a UMTS Sector From a GSM Sector" on page 226
- Additional Overlapping Conditions: Select the Additional Overlapping Conditions check box, if you
want to set overlapping coverage criteria. If cells meet the overlapping conditions to enter the reference
cells active set, they will be not allocated the same scrambling code as the reference cell. Click Define to
change the overlapping conditions. In the Coverage Conditions dialogue, you can change the following
parameters:
Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by reference cell A
and possible neighbour cell B.
Min. EcI0: Enter the minimum EcI0 which must be provided by reference cell A in an area with overlap-
ping coverage. Reference cell A must also be the best server in terms of pilot quality in the area with over-
lapping coverage.
EcI0 Margin: Enter the maximum difference of EcI0 between reference cell A and possible neighbour
cell B in the area with overlapping coverage.
DL Load Contributing to I0: You can let Atoll base the interference ratio on the total power used as de-
fined in the properties for each cell (Defined per Cell) or on a percentage of the maximum power (Global
Value).
Shadowing taken into account: If desired, select the Shadowing taken into account check box and
enter a Cell Edge Coverage Probability.
Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses defined per
clutter class in the calculations.
- Reuse Distance: Select the Reuse Distance check box, if you want to the automatic allocation process
to consider the reuse distance constraint. Enter the Default reuse distance within which two cells on the
same carrier cannot have the same primary scrambling code.
Note: A reuse distance can be defined at the cell level (in the cell Properties dialogue or in the
Cells table). If defined, a cell-specific reuse distance will be used instead of the value
entered here.
- Exceptional Pairs: Select the Exceptional Pairs check box, if you want to the automatic allocation proc-
ess to consider the exceptional pair constraints.
- Under Strategy, you can select an automatic allocation strategy:
- Clustered
- Distributed per Cell
- One Cluster per Site
- Distributed per Site
- Carrier: Select the Carrier on which you want to run the allocation. You may choose one carrier (Atoll will
assign primary scrambling codes to transmitters using the selected carrier) or all of them.
- No. of Codes per Cluster: According to 3GPP specifications, the number of codes per cluster is 8. If you wish,
you can change the number of codes per cluster.
- Use a Max of Codes: Select the Use a Max of Codes check box to make Atoll use the maximum number of
codes. For example, if there are two cells using the same domain with two scrambling codes, Atoll will assign
the remaining code to the second cell even if there are no constraints between these two cells (for example,
neighbour relations, reuse distance, etc.). If you do not select this option, Atoll only checks the constraints,
and allocates the first ranked code in the list.
- Delete Existing Codes: Select the Delete Existing Codes check box if you want Atoll to delete currently
allocated scrambling codes and recalculate all scrambling codes. If you do not select this option, Atoll will
keep currently allocated scrambling codes and will only allocate scrambling codes to cells that do not yet have
codes allocated.
- Allocate Carriers Identically: Select the Allocate Carriers Identically check box if you want Atoll to allocate
the same primary scrambling code to each carrier of a transmitter. If you do not select this option, Atoll allo-
cates scrambling codes independently for each carrier.
4. Click Run. Atoll begins the process of allocating scrambling codes.
Once Atoll has finished allocating scrambling codes, the codes are visible under Results. Atoll only displays
newly allocated scrambling codes.
Note: You can save automatic scrambling code allocation parameters in a user configuration.
For information on saving automatic scrambling code allocation parameters in a user
configuration, see "Exporting a User Configuration" on page 75.
Tips:
If you need to allocate scrambling codes to the cells on a single transmitter, you can allocate
them automatically by selecting Allocate Scrambling Codes from the transmitters context
menu.
If you need to allocate scrambling codes to all the cells on group of transmitters, you can allo-
cate them automatically by selecting Cells > Primary Scrambling Codes > Automatic Allo-
cation from the transmitter groups context menu.
When you allocate scrambling codes to a large number of cells, it is easiest to let Atoll allocate scrambling codes auto-
matically, as described in "Automatically Allocating Scrambling Codes to UMTS Cells" on page 505. However, if you want
to add a primary scrambling code to one cell or to modify the primary scrambling code of a cell, you can do it by accessing
the properties of the cell.
To allocate a scrambling code to a UMTS cell manually:
1. On the map, right-click the transmitter to whose cell you want to allocate a scrambling code. The context menu
appears.
2. Select Properties from the context menu. The transmitters Properties dialogue appears.
3. Select the Cells tab.
4. Enter a Primary Scrambling Code in the cells column.
5. Click OK.
In Atoll, you can search for scrambling codes and scrambling code groups using the Search Tool. Results are displayed
in the map window in red.
If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results
displayed by transmitter, the search results will be displayed by transmitter coverage. Scrambling codes and scrambling
code groups and any potential problems will then be clearly visible. For information on coverage predictions by transmitter,
see "Making a Coverage Prediction by Transmitter" on page 464.
To find scrambling codes or scrambling code groups using the Search Tool:
1. Create, calculate, and display a coverage prediction by transmitter. For information on coverage predictions by
transmitter, see "Making a Coverage Prediction by Transmitter" on page 464.
2. Click View > Search Tool. The Search Tool window appears.
The Search Tool window is a docking window. For information on docking windows, see "Docking or Floating an
Atoll Window" on page 26.
3. You can search either for a specific scrambling code or scrambling code group:
To search for a scrambling code:
a. Select SC Group.
b. Select a scrambling code group from the list.
4. Select the carrier you wish to search on from the For the Carrier list, or select "(All)" to search for the scrambling
code or scrambling code group in all carriers.
5. Click Search. Transmitters with cells matching the search criteria are displayed in red. Transmitters that do not
match the search criteria are displayed in grey.
To restore the initial transmitter colours and symbols, click the Reset Display button in the Search Tool window.
You can use the display characteristics of transmitters to display scrambling code-related information.
To display scrambling code-related information on the map:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Display tab.
You can display the following information per transmitter:
- Primary scrambling code: To display the primary scrambling code of a transmitters cell, select "Discrete
values" as the Display Type and "Cells: Primary Scrambling Code" as the Field.
- Ranges of primary scrambling codes: To display ranges of primary scrambling codes, select "Value inter-
vals" as the Display Type and "Cells: Primary Scrambling Code" as the Field.
- Scrambling code domain: To display the scrambling code domain of a transmitters cell, select "Discrete
values" as the Display Type and "Cells: Scrambling Code Domain" as the Field.
You can display the following information in the transmitter label or tooltip:
- Primary scrambling code: To display the primary scrambling code of a transmitters cell in the transmitter
label or tooltip, "Cells: Primary Scrambling Code" from the Label or Tip Text Field Definition dialogue.
- Scrambling code domain: To display the primary scrambling code domain of a transmitters cell in the trans-
mitter label or tooltip, "Cells: Scrambling Code Domain" from the Label or Tip Text Field Definition dialogue.
- Scrambling code reuse distance: To display the scrambling code reuse distance of a transmitters cell in the
transmitter label or tooltip, "Cells: SC Reuse Distance" from the Label or Tip Text Field Definition dialogue.
5. Click OK.
For information on display options, see "Display Properties of Objects" on page 33.
You can group transmitters on the Data tab of the Explorer window by their primary scrambling code, their scrambling
code domain, or by their scrambling code reuse distance.
To group transmitters by scrambling code:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the General tab, click Group by. The Group dialogue appears.
5. Under Available Fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
7. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to
the list of parameters on which the transmitters will be grouped.
8. If you do not want the transmitters to be sorted by a certain parameter, select it in the Group these fields in this
order list and click . The selected parameter is removed from the list of parameters on which the transmitters
will be grouped.
9. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters
to be grouped:
Note: If a transmitter has more than one cell, Atoll cannot arrange the transmitter by cell.
Transmitters that cannot be grouped by cell are arranged in a separate folder under the
Transmitters folder.
You can use a histogram to analyse the use of allocated scrambling codes in a network. The histogram represents the
scrambling codes or scrambling code clusters as a function of the frequency of their use.
To display the scrambling code histogram:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Primary Scrambling Codes > Scrambling Code Distribution. The Distribution Histograms
dialogue appears.
Each bar represents a scrambling code or a cluster, its height depending on the frequency of its use.
4. Select Scrambling Codes to display scrambling code use and Clusters to display scrambling code cluster use.
5. Move the pointer over the histogram to display the frequency of use of each scrambling code or cluster. The results
are highlighted simultaneously in the Detailed Results list.
You can make a scrambling code interference zone prediction to view areas covered by cells using the same scrambling
code. Atoll checks on each pixel whether the best server and other servers satisfying the conditions to enter the user
active set have the same scrambling code. If so, Atoll considers that there is scrambling code interference.
To make a scrambling code interference zone prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Scrambling Zone Interference Zones and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 475. You
must also select which Carrier is to be considered.
If you want the scrambling code interference zone prediction to consider shadowing, you can select the Shadow-
ing taken into account check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- The number of interferers for each transmitter: Select "Value Intervals" as the Display Type and "Number
of Interferers per Transmitter" as the Field. In the Explorer window, the coverage prediction results are
arranged by interfered transmitter.
- The total number of interferers on one pixel: Select "Value Intervals" as the Display Type and "Number of
Interferers" as the Field. In the Explorer window, the coverage prediction results are arranged according to
the number of interferers.
8. Click the Calculate button ( ) in the Radio toolbar to calculate the scrambling code interference zone predic-
tion. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
The SC Interference tab of the Point Analysis window gives you information on reception for any point on the map where
there is scrambling code interference. Scrambling code interference occurs when the best server and other servers satis-
fying the conditions to enter the user active set have the same scrambling code. When there is scrambling code interfer-
ence, Atoll displays the pilot quality (EcI0) received from interfered and interferer transmitters.
The analysis is based on the UL load percentage and the DL total power of each cell. The analysis is provided for a user-
definable probe receiver which has a terminal, a mobility, and a service.
You can make a scrambling code interference analysis to verify a scrambling code interference zone prediction. In this
case, before you make the scrambling code interference analysis, ensure the coverage prediction you want to use in the
scrambling code interference analysis is displayed on the map.
To make a scrambling code interference analysis:
1. Click the Point Analysis button ( ) on the toolbar. The Point Analysis Tool window appears.
2. Click the SC Interference tab.
3. At the top of the SC Interference tab, select "Cells Table" from Load Conditions.
4. If you are making a scrambling code interference analysis to verify a coverage prediction, you can recreate the
conditions of the coverage prediction:
a. Select the same Terminal, Service, and Mobility studied in the coverage prediction.
b. Select the Carrier studied in the coverage prediction.
c. Right-click the Point Analysis window and select Properties from the context menu. The Properties dia-
logue appears.
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and,
select "EcI0" from the Shadowing Margin list.
- Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class.
d. Click OK to close the Properties dialogue.
Note: If you are making a scrambling code interference analysis to make a prediction on a
defined point, you can use the instructions in this step to define a user.
5. Move the pointer over the map to make a scrambling code interference analysis for the current location of the
pointer.
6. Click the map to leave the point analysis pointer at its current position.
To move the pointer again, click the point analysis pointer on the map and drag it to a new position.
7. Click the Point Analysis button ( ) on the toolbar again to end the point analysis.
Traffic map per user profile can be used if you have marketing-based traffic data.
Traffic maps per density of user profiles, where each vector (polygon, line or point) describes subscriber densities
(or numbers of subscribers for points) with user profiles and mobility types, and traffic maps per environment of
user profiles, where each pixel has an assigned environment class. For more information, see "Importing a Traffic
Map Based on Densities of User Profiles" on page 514, "Importing a Traffic Map Based on Environments of User
Profiles" on page 516, and "Creating a Traffic Map Based on Environments of User Profiles" on page 516.
Traffic maps per density (number of users per km2) can be used if you have population-based traffic data,
or 2G network statistics.
Each pixel has an actual user density assigned. Either the value includes all activity statuses, or it corresponds to
a particular activity status. For more information, see "Importing a Traffic Map per User Density" on page 517,
"Creating a Traffic Map per per User Density" on page 518, "Converting 2G Network Traffic" on page 518 and
"Exporting Cumulated Traffic" on page 519.
Note: You can also import a traffic map from a file by clicking the Import button. You can import
AGD (Atoll Geographic Data) format files that you have exported from an other Atoll
document.
7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter.
8. Enter the data required in the Map per Sector dialogue:
- If you have selected Throughputs in Uplink and Downlink, enter the throughput demands in the uplink and
downlink for each sector and for each listed service.
- If you have selected Total Number of Users (All Activity Statuses), enter the number of connected users
for each sector and for each listed service.
- If you have selected Number of Users per Activity Status, enter the number of inactive users, the number
of users active in the uplink, in the downlink and in the uplink and downlink, for each sector and for each
service.
Note: You can also import a text file containing the data by clicking the Actions button and
selecting Import Table from the menu. For more information on importing table data, see
"Importing Tables from Text Files" on page 59.
You can model variations in user behaviour by creating different profiles for different times of the day or for different circum-
stances. For example, a user may be considered a business user during the day, with video conferencing and voice, but
no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and
web browsing.
To create or modify a user profile:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the UMTS Parameters folder.
3. Right-click the User Profiles folder. The context menu appears.
4. Select New from the context menu. The User Profiles New Element Properties dialogue appears.
Note: You can modify the properties of an existing user profile by right-clicking the user profile in
the User Profiles folder and selecting Properties from the context menu.
Note: In order for all the services defined for a user profile to be taken into account during traffic
scenario elaboration, the sum of activity probabilities must be lower than 1.
- Duration: For circuit-switched services, enter the average duration of a call in seconds. For packet-switched
services, this field is left blank.
- UL Volume: For packet-switched services, enter the average uplink volume per session in kilobytes.
- DL Volume: For packet-switched services, enter the average downlink volume per session in kilobytes.
Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a
given density (i.e., the number of subscribers with the same profile per km). To get an appropriate user distribution, you
can assign a weight to each clutter class for each environment class. You can also specify the percentage of indoor
subscribers for each clutter class. In a Monte-Carlo simulation, an additional loss (as defined in the clutter class properties)
will be added to the indoor users path loss.
To create or modify a UMTS environment:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the UMTS Parameters folder.
3. Right-click the Environments folder. The context menu appears.
4. Select New from the context menu. The Environments New Element Properties dialogue appears.
Note: You can modify the properties of an existing environment by right-clicking the
environment in the Environments folder and selecting Properties from the context
menu.
7. In the row marked with the New Row icon ( ), set the following parameters for each user profile/mobility com-
bination that this UMTS environment will describe:
- User: Select a user profile.
- Mobility: Select a mobility type.
- Density (Subscribers/km2): Enter a density in terms of subscribers per square kilometre for the combination
of user profile and mobility type.
8. Click the Clutter Weighting tab.
9. For each clutter class, enter a weight that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk Sk
N k = N Area --------------------------
Wi Si
i
where:
For example: An area of 10 km with a subscriber density of 100/km. Therefore, in this area, there are 1000
subscribers. The area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1"
and for Building is "4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter
class and 800 in the Building clutter class.
10. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte-Carlo simu-
lation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map per per User
Density" on page 518.
- User Profile: If you want to import user profile information from the file, under Defined, select "By field" and
select the source field from the Choice column. If you want to assign a user profile from the UMTS Parame-
ters folder of the Data tab, under Defined, select "By value" and select the user profile in the Choice column.
- Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select
the source field from the Choice column. If you want to assign a mobility type from the UMTS Parameters
folder of the Data tab, under Defined, select "By value" and select the mobility type in the Choice column.
- Density: If you want to import density information from the file, under Defined, select "By field" and select the
source field from the Choice column. If you want to assign a density, under Defined, select "By value" and
enter a density in the Choice column for the combination of user profile and mobility type. In this context, the
term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kil-
ometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers
when the map consists of points.
Important: When you import user profile or mobility information from the file, the values in the file
must be exactly the same as the corresponding names in the UMTS Parameters folder of
the Data tab. If the imported user profile or mobility does not match, Atoll will display a
warning.
12. Under Clutter Distribution, enter a weight for each class that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk Sk
N k = N Area --------------------------
Wi Si
i
where:
13. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte-Carlo simu-
lation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
14. Click OK to finish importing the traffic map.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 516.
7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, BIL, IST,
BMP, PlaNET, GRC Vertical Mapper, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears.
11. Select the Description tab.
In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the
Code column.
12. For each Code, select the environment it corresponds to from the Name column.
The environments available are those available in the Environments folder, under UMTS Parameters on the
Data tab of the Explorer window. For more information, see "Modelling Environments" on page 513.
13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects"
on page 33.
7. Select the environment class from the list of available environment classes.
8. Click the Draw Polygon button ( ) to draw the polygon on the map for the selected environment class.
9. Click the Delete Polygon button ( ) and click the polygon to delete the environment class polygon on the map.
10. Click the Close button to close the Environment Map Editor toolbar and end editing.
5. Click Close.
If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per
clutter class.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map per per User
Density" on page 518.
7. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP,
PlaNET, TIF, ISTAR, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears.
11. Select the Traffic tab.
12. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must
equal 100.
13. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must
equal 100.
14. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal
100.
15. Under Clutter Distribution, enter for each clutter class the percentage of indoor users.
An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define
a clutter weighting for traffic maps per user density because the traffic is provided in terms of user density per pixel.
16. Click OK. Atoll creates the traffic map in the Traffic folder.
12. Click OK. Atoll creates the traffic map in the Traffic folder.
13. Right-click the traffic map. The context menu appears.
14. Select Edit from the context menu.
15. Use the tools available in the Vector Edition toolbar in order to draw contours. For more information on how to edit
contours, see "Editing Contours, Lines, and Points" on page 131. Atoll creates an item called Density values in
the User Density Map folder.
16. Right-click the item. The context menu appears.
17. Select Open Table from the context menu.
18. In the table, enter a traffic density value (i.e. the number of users per km2) for each contour you have drawn.
19. Right-click the item. The context menu appears.
20. Select Edit from the context menu to end editing.
Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains
at "0" and no data will be exported.
8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic
data to be exported.
- Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal.
- Service: Select the service that will be exported, or select "Circuit services" to export traffic using any circuit
service, or select "Packet services" to export traffic using any packet service.
- Mobility: Select the mobility type that will be exported or select "All" to export all mobility types.
- Activity: Select one of the following:
- All Activity Statuses: Select All Activity Statuses to export all users without any filter by activity status.
- Uplink: Select Uplink to export mobiles active in the uplink only.
- Downlink: Select Downlink to export mobiles active in the downlink only.
- Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity.
- Inactive: Select Inactive to export only inactive mobiles.
9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the
cumulated traffic.
10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.
Finally, another random trial determines user positions in their respective traffic zone (possibly according to the
clutter weighting and the indoor ratio per clutter class).
2. Modelling network power control: Atoll uses a power control algorithm for R99 server users, and an algorithm
mixing A-DPCH power control and fast link adaptation for HSDPA users and an additional loop modelling noise
rise scheduling for HSUPA users. The power control simulation algorithm is described in "The Power Control Sim-
ulation Algorithm" on page 520.
Initialisation
R99 part
HSDPA part
Mobile Scheduling
HSUPA part
Admission Control
Convergence Study
As shown in Figure 9.37, the simulation algorithm is divided in three parts. All users are evaluated by the R99 part of the
algorithm. HSDPA and HSUPA users, unless they have been rejected during the R99 part of the algorithm, are then eval-
uated by the HSDPA part of the algorithm. Finally, HSUPA users, unless they have been rejected during the R99 or
HSDPA parts of the algorithm, are then evaluated by the HSUPA part of the algorithm.
The R99 part of the algorithm simulates power control, congestion and radio resource control performed for R99 bearers
for both R99, HSDPA and HSUPA users. Atoll considers each user in the order established during the generation of the
user distribution, determines his best server and his active set. Atoll first calculates the required terminal power in order
to reach the EbNt threshold requested by the R99 bearer on UL, followed by the required traffic channel power in order
to reach the EbNt threshold requested by the R99 bearer on DL. After calculating power control, Atoll updates the cell
load parameters. Atoll then carries out congestion and radio resource control, verifying the cell UL load, the total power
transmitted by the cell, the number of channel elements, the Iub throughput and OVSF codes consumed by the cell.
At this point, R99, HSDPA and HSUPA users can be either connected or rejected. They are rejected if:
The signal quality is not sufficient:
- On the downlink, the pilot quality is not high enough (no cell in the user active set): status is "EcI0 < (EcI0)min"
- On the downlink, the power required to reach the user is greater than the maximum allowed: the status is
"Ptch > PtchMax"
- On the uplink, there is not enough power to transmit: the status is "Pmob > PmobMax"
Even if constraints above are respected, the network may be saturated:
- The maximum uplink load factor is exceeded (at admission or congestion): the status is either "Admission
rejection" or "UL load saturation"
- There are not enough channel elements on site: the status is "channel element saturation"
- The maximum Iub backhaul throughput on site is exceeded: the status is "Iub Throughput Saturation"
- There is not enough power for cells: the status is "DL load saturation"
- There are no more OVSF codes available: the status is "Code saturation"
In the HSDPA part, Atoll processes all HSDPA bearer users, i.e., HSDPA and HSUPA users. The HSDPA part of the algo-
rithm simulates fast link adaptation, the scheduling of HSDPA users, and radio resource control on downlink. Two fast link
adaptations are done, one before mobile scheduling and one after.
HSDPA bearer selection is based on look-up tables, available by double-clicking the corresponding entry in the Reception
Equipment table, under the Terminals context menu and it depends on reported CQI, UE and cell capabilities as detailed
below.
[
Figure 9.38: HSDPA bearer selection
The HSDPA and HS-SCCH powers of a cell are evaluated before calculating HS-PDSCH EcNt. The HSDPA power (the
power dedicated to HS-SCCH and HS-PDSCH of HSDPA bearer users) of a cell can be either fixed (statically allocated)
or dynamically allocated. If it is dynamically allocated, the power allocated to HSDPA depends on how much power is
required to serve R99 traffic. In other words, the power available after all common channels (including the power for down-
link HSUPA channels) and all R99 traffic have been served is allocated to HS-PDSCH and HS-SCCH of HSDPA bearer
users. Similarly, the power per HS-SCCH can be either fixed or dynamically allocated in order to attain the HS-SCCH EcNt
threshold. Using the HS-SCCH and HSDPA powers, Atoll evaluates the HS-PDSCH power (the difference between the
HSDPA power and the HS-SCCH power), calculates the HS-PDSCH EcNt and, from that, the corresponding CQI (from
the graph CQI=f(HS-PDSCH EcNt) defined for the terminal reception equipment and the user mobility). Then, Atoll
selects the HSDPA bearer associated to this CQI (in the table Best Bearer=f(HS-PDSCH CQI) defined for the terminal
reception equipment and the user mobility) and compatible with the user equipment and cell capabilities.
Before mobile scheduling, each user is processed as if he is the only user in the cell. This means that Atoll determines
the HSDPA bearer for each HSDPA and HSUPA user by considering for each the entire HSDPA power available of the
cell.
During scheduling, cell radio resources are shared between HSDPA and HSUPA users by the scheduler. The scheduler
simultaneously manages the maximum number of users within each cell and ranks them according to the selected sched-
uling technique:
Max C/I: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined) are sched-
uled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order by
the channel quality indicator (CQI).
Round Robin: HSDPA users are scheduled in the same order as in the simulation (i.e., in random order).
Proportional Fair: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined)
are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending
order according to a random parameter which corresponds to a combination of the user rank in the simulation and
the channel quality indicator (CQI).
After mobile scheduling, Atoll carries out a second fast link adaptation. HSDPA and HSUPA users are processed in the
order defined by the scheduler and the cells HSDPA power is shared among them.
Then, Atoll checks to see if enough codes and Iub backhaul throughput are available for the HSDPA bearer assigned to
the user (taking into account the maximum number of OVSF codes defined for the cell and the maximum Iub backhaul
throughput allowed on the site in the downlink). If not, Atoll allocates a lower HSDPA bearer ("downgrading") which needs
fewer OVSF codes and consumes lower Iub backhaul throughput. If no OVSF codes are available, the user is delayed.
On the same hand, if the maximum Iub backhaul throughput allowed on the site in the downlink is still exceeded even by
using the lowest HSDPA bearer, the user is delayed.
At this point, HSDPA bearer users can be connected, rejected, or delayed. They are rejected if the maximum number of
HSDPA users per cell is exceeded (status is "HSDPA scheduler saturation") and delayed if:
They cannot obtain the lower HSDPA bearer (bearer index 5): the status is "HSDPA Delayed"
The HS-SCCH signal quality is not sufficient: the status is "HSDPA Delayed"
There are no more HS-SCCH channels available: the status is "HSDPA Delayed"
There are no more OVSF codes available: the status is "HSDPA Delayed"
The maximum Iub backhaul throughput allowed on the site in the downlink is exceeded: the status is "HSDPA
Delayed"
In the HSUPA part, Atoll processes all the HSUPA users who are connected to an HSDPA bearer or were delayed in the
previous step. It considers each user in the order established during the generation of the user distribution without exceed-
ing the maximum number of HSUPA users within each cell. The HSUPA part of the algorithm simulates an admission
control on these HSUPA users followed by noise rise scheduling. The happy bit mechanism is modelled as well and radio
resource control is performed at the end of the HSUPA part of the simulation.
Atoll first selects a list of HSUPA bearers that are compatible with the user equipment capabilities for each HSUPA user.
Then, during admission control, it checks that the lowest compatible bearer in terms of the required E-DPDCH EcNt does
not require a terminal power higher than the maximum terminal power allowed.
Then, Atoll begins noise rise scheduling. The noise rise scheduling algorithm attempts to evenly share the remaining cell
load between the users admitted in admission control; in terms of HSUPA, each user is allocated a right to produce inter-
ference. The remaining cell load factor on uplink depends on the maximum load factor allowed on uplink and how much
uplink load is produced by the served R99 traffic. From this value, Atoll calculates the maximum E-DPDCH EcNt allowed
and can select an HSUPA bearer. The HSUPA bearer is selected based on the values in a look-up table, and depends on
the maximum E-DPDCH EcNt allowed and on UE capabilities.
Note: You can open the HSUPA Bearer Selection table by right-clicking Terminals on the Data
tab of the Explorer window and selecting Reception Equipment. Then, double-clicking
the entry in the Reception Equipment table opens the Properties dialogue from which
you can select the HSUPA Bearer Selection tab.
Atoll selects the best HSUPA bearer from the HSUPA compatible bearers, in other words, the HSUPA bearer with the
highest potential throughput where the required E-DPDCH Ec/Nt is lower than the maximum E-DPDCH EcNt allowed and
the required terminal power is lower than the maximum terminal power. In this section, the potential throughput refers to
the ratio between the RLC peak rate and the number of retransmissions. When several HSUPA bearers are available,
Atoll selects the one with the lowest required E-DPDCH EcNt.
Then, Atoll checks that each user has obtained the average requested rate (defined in the properties of the service). A
user is considered as "happy" if the RLC peak rate provided by the HSUPA bearer exceeds the average requested rate
and "unhappy" if not. Atoll collects the unused load of "happy" users and redistributes it among the "unhappy" users. This
process is repeated until there is no more available load.
Finally, Atoll carries out radio resource control, verifying the uplink load of all the cells and performs a new distribution of
the load if cells are overloaded. Atoll also checks to see if enough channel elements and Iub backhaul throughput are
available for the HSUPA bearer assigned to the user (taking into account the maximum number of channel elements
defined for the site and the maximum Iub backhaul throughput allowed on the site in the uplink). If not, Atoll allocates a
lower HSUPA bearer ("downgrading") which needs fewer channel elements and consumes lower Iub backhaul throughput.
If no channel elements are available, the user is rejected. On the same hand, if the maximum Iub backhaul throughput
allowed on the site in the uplink is still exceeded even by using the lowest HSDPA bearer, the user is rejected.
At this point, HSUPA users can be either connected, or rejected. They are rejected if:
The maximum number of HSUPA users per cell is exceeded (the status is "HSUPA scheduler saturation")
The terminal power required to obtain the lowest compatible HSUPA bearer exceeds the maximum terminal power
in the admission control (the status is "HSUPA Admission Rejection").
There are no more channel elements available: the status is "Ch. Elts Saturation"
The maximum Iub backhaul throughput allowed on the site in the uplink is exceeded: the status is "Iub Throughput
Saturation".
Bearer Downgrading
If you select the option "Rate Downgrading," when creating a simulation, R99, HSDPA and HSUPA service users can be
downgraded under certain circumstances. When the downgrading is allowed, Atoll does not reject R99, HSDPA and
HSUPA users directly; it downgrades them beforehand.
The R99 to R99 bearer downgrading occurs when:
The cell resources are insufficient when the user is admitted
- The maximum uplink load factor is exceeded
The cell resources are insufficient during congestion control
- The maximum uplink load factor is exceeded
Note: Execute Later enables you to automatically calculate UMTS coverage predictions after
simulations with no intermediary step by creating your simulations, creating your
predictions, and then clicking the Calculate button ( ).
- Information to retain: You can select the level of detail that will be available in the output:
- Only the Average Simulation and Statistics: None of the individual simulations are displayed or avail-
able in the group. Only an average of all simulations and statistics is available.
Note: Some calculation and display options available for coverage predictions are not available
when the option "Only the Average Simulation and Statistics" is selected.
- No Information About Mobiles: All the simulations are listed and can be displayed. For each of them, a
properties window containing simulation output, divided among four tabs Statistics, Sites, Cells, and
Initial conditions is available.
- Standard Information About Mobiles: All the simulations are listed and can be displayed. The properties
window for each simulation contains an additional tab with output related to mobiles.
- Detailed Information About Mobiles: All the simulations are listed and can be displayed. The properties
window for each simulation contains additional mobile-related output on the Mobiles and Mobiles (Shad-
owing values) tabs.
Tip: When you are working on very large radio-planning projects, you can reduce memory
consumption by selecting Only the Average Smulation and Statistics under
Information to retain.
6. Under Cell Load Constraints on the General tab, you can set the constraints that Atoll must respect during the
simulation:
- Number of Channel Elements: Select the Number of Channel Elements check box if you want Atoll to
respect the number of channel elements defined for each site.
- Iub Throughputs: Select the Iub Throughputs check box if you want Atoll to respect the maximum Iub back-
haul throughputs defined for each site.
- Number of Codes: Select the Number of Codes check box if you want Atoll to respect the number of OVSF
codes available each cell.
- UL Load Factor: If you want the UL load factor to be considered in the simulation, select the UL Load Factor
check box.
- Max UL Load Factor: If you want to enter a global value for the maximum uplink cell load factor, click the
button ( ) beside the box and select Global Threshold. Then, enter a maximum uplink cell load factor. If
you want to use the maximum uplink cell load factor as defined in the properties for each cell, click the button
( ) beside the box and select Defined per Cell.
- DL Load (% Pmax): If you want the DL load to be considered in the simulation, select the DL Load (% Pmax)
check box and enter a maximum downlink cell load in the Max DL Load box.
- Max DL Load (% Pmax): If you want to enter a global value for the maximum downlink cell load, as a per-
centage of the maximum power, click the button ( ) beside the box and select Global Threshold. Then,
enter a maximum downlink cell load, as a percentage of the maximum power. If you want to use the maximum
downlink cell load factor as defined in the properties for each cell, click the button ( ) beside the box and
select Defined per Cell.
7. Under Bearer Negotiation on the General tab, check the Rate Downgrading check box if you want to permit
bearer downgrading during the simulation. When a constraint is not respected, user radio bearers with services
supporting rate downgrading are downgraded. If the constraint is still not satisfied after downgrading, users are
rejected. If downgrading is not selected, users will be rejected immediately, starting with users with the lowest
service priority, if a constraint can not be respected.
8. On the Source Traffic tab, enter the following:
- Global Scaling Factor: If desired, enter a scaling factor to increase user density.
The global scaling factor enables you to increase user density without changing traffic parameters or traffic
maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscrib-
ers (for environment and user profile traffic maps) or the rates/users (for live traffic maps per sector).
- Select Traffic Maps to Be Used: Select the traffic maps you want to use for the simulation.
You can select traffic maps of any type. However, if you have several different types of traffic maps and want
to make a simulation on a specific type of traffic map, you must ensure that you select only traffic maps of the
same type. For information on the types of traffic maps, see "Creating a Traffic Map" on page 511.
9. Click the Advanced tab.
10. Under Generator Initialisation, enter an integer as the generator initialisation value. If you enter "0", the default,
the user and shadowing error distribution will be random. If you enter any other integer, the same user and shad-
owing error distribution will be used for any simulation using the same generator initialisation value.
Tip: Using the same generated user and shadowing error distribution for several simulations
can be useful when you want to compare the results of several simulations where only one
parameter changes.
For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 33.
In this section are the following examples of traffic distribution:
"Displaying the Traffic Distribution by Handover Status" on page 525
"Displaying the Traffic Distribution by Connection Status" on page 525
"Displaying the Traffic Distribution by Service" on page 526.
Tip: You can make the traffic distribution easier to see by hiding geo data and predictions. For
information, see "Displaying or Hiding Objects on the Map Using the Explorer" on
page 28.
The Statistics tab: The Statistics tab contains the following two sections:
- Request: Under Request, you will find data on the connection requests:
- Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; power control has not yet finished. The result depends on the traffic description and traffic input.
- During the first random trial, each user is assigned a service and an activity status. The number of users
per activity status and the UL and DL rates that all active users could theoretically generate are provided.
- The breakdown per service (total number of users, number of users per activity status, and UL and DL
rates) is given.
- Results: Under Results, you will find data on connection results:
- The number of iterations that were run in order to converge.
- The number and the percentage of non-connected users is given along with the reason for rejection.
These figures include rejected and delayed users. These figures are determined at the end of the simula-
tion and depend on the network design.
- The number and percentage of R99 bearer users connected to a cell, the number of users per frequency
band for a dual-band network, the number of users per activity status, and the UL and DL total rates they
generate. These figures include R99 users as well as HSDPA and HSUPA users (since all of them request
an R99 bearer); they are determined in the R99 part of the algorithm. These data are also given per serv-
ice.
- The total number and the percentage of connected users with an HSDPA bearer, the number of users per
frequency band for a dual-band network, the number of users per activity status, and the DL total rate that
they generate. Both HSDPA and HSUPA users are considered since they both request an HSDPA bearer.
- The total number of connected HSUPA users and the percentage of users with an HSUPA bearer, the
number of users per frequency band for a dual-band network, the number of users per activity status, and
the UL total rate they generate. Only HSUPA users are considered.
The Sites tab: The Sites tab contains the following information per site:
- Max No. of DL and UL CEs: The maximum number of channel elements available on uplink and downlink for
R99 bearers requested by R99, HSDPA and HSUPA users.
- No. of DL and UL CEs Used: The number of channel elements required on uplink and downlink for R99
bearers to handle the traffic of current simulation.
- No. of DL and UL CEs Due to SHO Overhead: The number of extra channel elements due to soft handover,
on uplink and downlink.
- Carrier Selection: The carrier selection method defined on the site equipment.
- Downlink and Uplink Overhead CEs/Cell: The overhead channel elements per cell on the downlink and on
the uplink, defined on the site equipment.
- AS Restricted to Neighbours: Whether the active set is restricted to neighbours of the reference cell. This
option is selected on the site equipment.
- Rake Factor: The rake factor, defined on the site equipment, enables Atoll to model a rake receiver on down-
link.
- MUD Factor: The multi-user detection factor, defined on the site equipment, is used to decrease intra-cell
interference on uplink.
- Compressed Mode: Whether compressed mode is supported. This option is defined on the site equipment.
- Max Iub Downlink and Uplink Backhaul Throughput (kbps): The maximum Iub backhaul throughput in the
downlink and uplink .
- Iub Downlink and Uplink Backhaul Throughput (kbps): The Iub backhaul throughput required on downlink
and uplink to handle the traffic of current simulation.
- Overhead Iub Throughput (kbps):the Iub throughput required by the site for common channels in the down-
link. It corresponds to the overhead Iub throughput per cell (defined on the site equipment) multiplied by the
number of cells on the site.
- HSDPA Iub Backhaul Overhead (%): This parameter is defined on the site equipment. It corresponds to the
percentage of the HSDPA bearer RLC peak rate to be added to the RLC peak rate. The total value corre-
sponds to the Iub backhaul throughput required by the HSDPA user for HS Channels in the downlink.
- Nb of Recommended E1/T1/Ethernet Link: The number of E1/T1/Ethernet links required to provide the total
Iub backhaul throughput.
- Instantaneous HSDPA Rate (kbps): The Instantaneous HSDPA Rate (kbps).
- Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps).
- HSUPA Rate (kbps): The HSUPA peak rate in kbps.
- DL and UL Throughput for Each Service: The R99 throughput in kbitss for each service. The result is
detailed on the downlink and uplink only when relevant.
The Cells tab: The Cells tab contains the following information, per site, transmitter, and carrier:
- Max Power (dBm): The maximum power as defined in the cell properties.
- Pilot Power (dBm): The pilot power as defined in the cell properties.
- SCH power (dBm): The SCH power as defined in the cell properties.
- Other CCH power (dBm): The power of other common channels. It includes the other CCH power and the
DL HSUPA power as defined in the cell properties.
- Available HSDPA Power (dBm): The available HSDPA power as defined in the cell properties. This is the
power available for the HS-PDSCH and HS-SCCH of HSDPA users. The value is either fixed by the user when
the HSDPA power is allocated statically, or by a simulation when the option HSDPA Power Dynamic Alloca-
tion is selected.
- AS Threshold (dB): The active set threshold as defined in cell properties
- Gain (dBi): The gain as defined in the antenna properties for that transmitter.
- Reception Loss (dB): The reception loss as defined in the transmitter properties.
- Transmission Loss (dB): The transmission loss as defined in the transmitter properties.
- BTS Noise Figure (dB): The BTS noise figure as defined in the transmitter properties
- Total Transmitted R99 Power (dBm): The total transmitted R99 power is the power transmitted by the cell
on common channels (Pilot, SCH, other CCH), HSUPA channels (E-AGCH, E-RGCH, and E-HICH) and R99
traffic-dedicated channels.
- Total Transmitted Power (dBm): The total transmitted power of the cell is the sum of the total transmitted
R99 power and the available HSDPA power. If HSDPA power is allocated statically, this total transmitted
power must be lower than or equal to the maximum power. If HSDPA power is allocated dynamically, the total
transmitted power equals the maximum power minus the power headroom. In other words, the HSDPA power
corresponds to the difference between the total transmitted power and the R99 transmitted power.
Note: When the constraint "DL load" is set and HSDPA power is statically allocated, the total
transmitted power cannot exceed the maximum DL load (defined either in the cell
properties, or in the simulation). On the other hand, if HSDPA power is allocated
dynamically, the control is carried out on the R99 transmitted power, which cannot exceed
the maximum DL load.
- UL Total Noise (dBm): The uplink total noise takes into account the total signal received at the transmitter on
a carrier from intra and extra-cell terminals using the same carrier and adjacent carriers (uplink total interfer-
ence) and the thermal noise.
- Max UL Load Factor (%): The maximum uplink load factor that the cell can support. It is defined either in the
cell properties, or in the simulation creation dialogue.
- Max DL Load (% Pmax): The maximum percentage of power that the cell can use. It is defined either in the
cell properties, or in the simulation creation dialogue.
- UL load factor (%): The uplink cell load factor corresponds to the ratio between the uplink total interference
and the uplink total noise. If the constraint "UL load factor" has been selected, UL cell load factor is not allowed
to exceed the user-defined maximum UL load factor (either in the cell properties, or in the simulation creation
dialogue).
- DL Load Factor (%): The DL load factor of the cell i corresponds to the ratio (DL average interference [due
to transmitter signals on the same and adjacent carriers] for terminals in the transmitter i area) (DL average
total noise [due to transmitter signals and to thermal noise of terminals] for terminals in the transmitter i area).
- UL and DL Noise Rise (dB): The uplink and downlink noise rises are calculated from uplink and downlink
load factors. These data indicate signal degradation due to cell load (interference margin in the link budget).
- DL R99 Load (% Pmax): The percentage of power used for R99 channels is determined by the total trans-
mitted R99 power-maximum power ratio (power stated in W). When the constraint "DL load" is set and HSDPA
power is allocated dynamically, the DL R99 Load can not exceed the user-defined Max DL Load (defined
either in the cell properties, or in the simulation).
- Reuse Factor (UL): The uplink reuse factor is the ratio between the uplink total interference and the intra-cell
interference.
- Reuse Efficiency Factor (UL): The uplink reuse efficiency factor is the reciprocal of the uplink reuse factor.
- Number of UL and DL Radio Links: The number of radio links corresponds to the number of user-transmitter
links on the same carrier. This data is calculated on uplink and on downlink and indicates the number of users
connected to the cell on uplink and downlink. Because of handover, a single user can use several radio links.
- Connection Success Rate (%): The connection success rate gives the ratio of connected users over the total
number of users in the cell.
- HSDPA Application Throughput (kbps): This is the net HSDPA throughput without coding (redundancy,
overhead, addressing, etc.).
- Min. HSDPA RLC Peak Rate (kbps): The minimum HSDPA RLC peak rate corresponds to the lowest of RLC
peak rates obtained by HSDPA bearer users connected to the cell.
- Max HSDPA RLC Peak Rate (kbps): The maximum HSDPA RLC peak rate corresponds to the highest of
RLC peak rates obtained by HSDPA bearer users connected to the cell.
- Avg. Instantaneous HSDPA Throughput (kbps): The average instantaneous HSDPA rate (kbps) is the
average number of kbits per second that the cell supports on downlink to provide one connected user with an
HSDPA bearer.
- Instantaneous HSDPA Rate (kbps): The instantaneous HSDPA rate (kbps) is the number of kbits per
second that the cell supports on downlink to provide simultaneous connected users with an HSDPA bearer.
- Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps) that
the cell carries.
- No. of Simultaneous HSDPA Users: The number of simultaneous HSDPA users corresponds to the number
of HSDPA bearer users that the cell supports at one time, i.e. within one time transmission interval. All these
users are connected to the cell at the end of the HSDPA part of the simulation; they have a connection with
the R99 bearer (ADPCH-UL64 for HSDPA users and ADPCH-EDPCCH bearer for HSUPA users) and an
HSDPA bearer.
Note: The number of HSDPA bearer users cannot exceed the number of HS-SCCH channels
per cell at any given moment (within a time transmission interval).
- No. of HSDPA Users: The number of HSDPA users including the connected and delayed HSDPA bearer
users.
- No. of HSUPA Users: The number of HSUPA users connected to the cell.
- HSUPA Application Throughput (kbps): This is the net HSUPA throughput without coding (redundancy,
overhead, addressing, etc.).
- HSUPA UL Load Factor (%): The uplink cell load contribution due to HSUPA traffic.
- No. of Codes (512 Bits): The number of 512-bit OVSF codes used per cell.
- The types of handover as a percentage: Atoll estimates the percentages of handover types for each trans-
mitter. Atoll only lists the results for the following handover status, no handover (11), softer (12), soft (22),
softer-soft (23) and soft-soft (33) handovers; the other handover status (other HO) are grouped.
- R99 UL and DL Throughput (kbps): The uplink and downlink R99 throughputs represent the numbers of
kbits per second delivered by the cell respectively on uplink and on downlink to supply HSUPA, HSDPA, and
R99 users with a R99 bearer. All the radio links in the cell, i.e., links due to handover, are taken into account
in the throughput calculation.
- R99 UL and DL Throughput Without HO (kbps): The uplink and downlink R99 throughputs represent the
numbers of kbits per second delivered by the cell respectively on uplink and on downlink to supply HSUPA,
HSDPA, and R99 users with a R99 bearer. Only the links with the best server are taken into account in the
calculation of throughput.
- Min TCH Pwr (dBm): The minimum power allocated to a traffic channel to supply services.
- Max TCH Pwr (dBm): The maximum power allocated to a traffic channel to supply services.
- Avg TCH Pwr (dBm): The average power allocated to a traffic channel to supply services.
- Rejected users: The number of rejected users per cell are sorted by the following values: Pmob > PmobMax,
Ptch > PtchMax, EcIo < (EcIo)min., UL Load Saturation, Ch. Elts Saturation, DL Load Saturation, Mul-
tiple Causes, Code Saturation, Admission Rejection, HSDPA Delayed, HSDPA Scheduler Saturation,
HSUPA Scheduler Saturation and Iub Throughput Saturation.
The Mobiles tab: The Mobiles tab contains the following information:
Note: The Mobiles tab only appears if, when creating the simulation as explained in "Creating
Simulations" on page 523, you select either "Standard information about mobiles" or
"Detailed information about mobiles" under Information to Retain.
- X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the
second random trial).
- Service: The service assigned during the first random trial during the generation of the user distribution.
- Terminal: The assigned terminal. Atoll uses the assigned service and activity status to determine the terminal
and the user profile.
- User: The assigned user profile. Atoll uses the assigned service and activity status to determine the terminal
and the user profile.
- Mobility: The mobility type assigned during the first random trial during the generation of the user distribution.
- Activity: The activity status assigned during the first random trial during the generation of the user distribution.
- Carrier: The carrier used for the mobile-transmitter connection.
- Frequency Band: the frequency band used for the mobile-transmitter connection.
- DL and UL Total Requested Rate (kbps): For an R99 user, the DL and UL total requested rates correspond
to the DL and UL nominal rates of the R99 bearer associated to the service.
For an HSDPA user, the uplink total requested rate corresponds to the nominal rate of ADPCH-UL64 R99
bearer and the downlink total requested rate is the sum of the ADPCH-UL64 radio bearer nominal rate and
the RLC peak rate that the selected HSDPA radio bearer can provide. Here, the HSDPA user is treated as if
he is the only user in the cell and then, Atoll determines the HSDPA bearer the user would obtain by consid-
ering the entire HSDPA power available of the cell.
For an HSUPA user, the uplink total requested rate is equal to the sum of the ADPCH-EDPCCH radio bearer
nominal rate and the RLC peak rate of the requested HSUPA radio bearer. The requested HSUPA radio bear-
er is selected from the HSUPA bearers compatible with the user equipment. Here, the HSUPA user is treated
as if he is the only user in the cell and then, Atoll determines the HSUPA bearer the user would obtain by
considering the entire remaining load of the cell. The downlink total requested rate is the sum of the ADPCH-
EDPCCH radio bearer nominal rate and the RLC peak rate that the requested HSDPA radio bearer can pro-
vide. The requested HSDPA bearer is determined as explained in the previous paragraph.
- DL and UL Total Obtained Rate (kbps): For an R99 user, the DL or UL total obtained rate is the same as
the DL or UL total requested rate if he is connected without being downgraded. Otherwise, the total obtained
rate is lower (it corresponds to the nominal rate of the selected R99 bearer). If the user was rejected, the total
obtained rate is zero.
For an HSDPA user connected to an HSDPA bearer, the uplink total obtained rate equals the requested one
and the downlink total obtained rate corresponds to the instantaneous rate; this is the sum of the ADPCH-
UL64 radio bearer nominal rate and the RLC peak rate provided by the selected HSDPA radio bearer after
scheduling and radio resource control. If the HSDPA user is delayed (he is only connected to an R99 radio
bearer), uplink and downlink total obtained rates correspond to the uplink and downlink nominal rates of AD-
PCH-UL64 radio bearer. Finally, if the HSDPA user is rejected either in the R99 part or in the HSDPA part (i.e.,
because the HSDPA scheduler is saturated), the uplink and downlink total obtained rates are zero.
For a connected HSUPA user, on uplink, if the user is connected to an HSUPA bearer, the uplink total obtained
rate is the sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate provided by the se-
lected HSUPA radio bearer after noise rise scheduling. On downlink, if the user is connected to an HSDPA
bearer, the downlink total obtained rate corresponds to the instantaneous rate. The instantaneous rate is the
sum of the ADPCH-EDPCCH radio bearer nominal rate and the RLC peak rate provided by the selected HSD-
PA radio bearer after scheduling and radio resource control. If the user is delayed, the downlink total obtained
rate corresponds to the downlink nominal rate of ADPCH-EDPCCH radio bearer. If the HSUPA user is reject-
ed, the uplink and downlink total obtained rates are "0."
- Mobile Total Power (dBm): The mobile total power corresponds to the total power transmitted by the ter-
minal.
- Connection Status: The connection status indicates whether the user is connected, delayed or rejected at
the end of the simulation. If connected, the connection status corresponds to the activity status. If rejected, the
rejection cause is given. If delayed (for HSDPA users only), the status is "HSDPA delayed."
- Best Server: The best server among the transmitters in the mobile active set.
- HO Status (Sites/No. Transmitters Act. Set): The HO status is the number of sites compared to the number
of transmitters in the active set.
- AS1, AS2, AS3, AS4: The name of the cell that is the best server, the second-best server, and so on is given
in a separate column for each cell in the active set.
- Ec/I0 AS1, AS2, AS3, AS4, (dB): EcI0 is given in a separate column for each cell in the active set. The Ec/
I0 AS 1 column lists the Ec/I0 from the best server for the rejected mobiles as well.
- Indoor: This field indicates whether indoor losses have been added or not.
- Active Compressed Mode: This field indicates whether active compressed mode is supported by the mobile
or not.
The following columns only appear if, when creating the simulation as explained in "Creating Simulations" on
page 523, you select "Detailed information about mobiles" under Information to Retain:
- DL and UL Requested RLC Peak Rates (kbps): For an R99 user, the DL and UL requested RLC peak rates
are 0. For an HSDPA user, the uplink RLC peak rate is 0 and the downlink requested RLC pear rate is the rate
that the selected HSDPA radio bearer can provide.
For an HSUPA user, the requested uplink RLC peak rate is the rate of the requested HSUPA radio bearer. If
the user is connected to an HSDPA bearer in the downlink, the downlink requested RLC peak rate is the rate
that the requested HSDPA radio bearer can provide.
- DL and UL Obtained RLC Peak Rate (kbps): For an R99 user, the DL and UL obtained RLC peak rates are
0. For an HSDPA user connected to an HSDPA bearer, the uplink obtained RLC peak rate is 0, and the down-
link obtained RLC peak rate is the rate provided by the selected HSDPA radio bearer after scheduling and
radio resource control.
For a connected HSUPA user, on uplink, if the user is connected to an HSUPA bearer, the obtained uplink
RLC peak rate is the rate provided by the selected HSUPA radio bearer after noise rise scheduling. On down-
link, if the user is connected to an HSDPA bearer, the downlink obtained RLC peak rate is the rate provided
by the selected HSDPA radio bearer after scheduling and radio resource control.
- HSDPA Application Throughput (kbps): The HSDPA application throughput is the net HSDPA throughput
without coding (redundancy, overhead, addressing, etc.). It is calculated from the instantaneous HSDPA rate
(i.e., the DL obtained rate), the BLER, the HSDPA service scaling factor and the throughput offset.
- Served HSDPA Power: This is the HSDPA power required to provide the HSDPA bearer user with the down-
link obtained rate.
- Required HSDPA Power: The required HSDPA power is the HSDPA power required to provide the HSDPA
bearer user with the downlink requested rate. If the HSDPA bearer allocated to the user is the best one, the
required HSDPA power corresponds to the available HSDPA power of the cell. On the other hand, if the
HSDPA has been downgraded in order to be compliant with cell and UE capabilities, the required HSDPA
power will be lower than the available HSDPA power of the cell.
- No. of HSUPA Retransmissions (Required): The number of retransmissions for the requested HSUPA radio
bearer.
- No. of HSUPA Retransmissions (Obtained): The number of retransmissions for the obtained HSUPA radio
bearer.
- HSUPA Application Throughput (kbps): The HSUPA application throughput is the net HSUPA throughput
without coding (redundancy, overhead, addressing, etc.). It is calculated from the UL obtained rate, the BLER,
the HSUPA service scaling factor and the throughput offset.
- Cell TCH Power AS1, AS2, AS3, AS4 (DL) (dBm): The cell power transmitted on the downlink is given for
each link between the mobile and a transmitter in the active set.
- DL Ntot AS1, AS2, AS3, AS4 (dBm): The total noise on the downlink for each link between the mobile and
a transmitter in the \active set.
- Load Factor AS1, AS2, AS3, AS4 (DL) (%): The load factor on the downlink for each link between the mobile
and a transmitter in the active set. It corresponds to the ratio between the total interference on the downlink
and total noise at the terminal.
- Noise Rise AS1, AS2, AS3, AS4 (DL) (dB): The noise rise on the downlink for each link between the mobile
and a transmitter in the active set.
- Reuse Factor AS1, AS2, AS3, AS4 (DL): The DL reuse factor for each link between the mobile and a trans-
mitter in the active set. It is calculated from the interference received at the terminal from the intra cell area
and the total interference received at the terminal from all the transmitters (intra and extra-cell and inter-car-
rier).
- Iintra AS1, AS2, AS3, AS4 (DL) (dBm): The intra-cell interference for each cell (I) of the active set.
I int ra = P DL
DL
tot
(ic ) Fortho P DL
tot
(ic ) PSCH
i i LT
- Iextra AS1, AS2, AS3, AS4 (DL) (dBm): The extra-cell interference for each cell (I) of the active set.
I extra =
DL
P DL
tot
(ic ) Fortho P DL
tot
(ic ) PSCH
Tx ,iTx LT
- Total Loss AS1, AS2, AS3, AS4 (dB): The total attenuation for each link between the mobile and a trans-
mitter in the active set.
- Iub UL Backhaul Throughput (kbps): The Iub backhaul throughput consumed on the uplink by the mobile.
- Iub DL Backhaul Throughput (kbps): The Iub backhaul throughput consumed on the downlink by the
mobile.
- No. of UL CEs: The number of channel elements consumed on the uplink by the mobile.
- No. of DL CEs: The number of channel elements consumed on the downlink by the mobile.
- Name: The name of the mobile, as assigned during the random user generation.
- Clutter: The clutter class on which the mobile is located.
- Orthogonality Factor: The orthogonality factor used in the simulation. The orthogonality factor is the
remaining orthogonality of the OVSF codes at reception. The value used is the orthogonality factor set in the
clutter classes.
- % Pilot Finger: The percentage pilot finger used in the simulation, defined per clutter class or globally for all
clutter classes.
- UL SHO Gain (dB): The uplink soft handover gain is calculated if mobile receivers are connected either on
DL or on UL and DL.
- DL SHO Gain (dB): The downlink soft handover gain is calculated if mobile receivers are connected either on
DL or on UL and DL.
- No. of Codes (512 Bits): The number of OVSF codes used per mobile.
The Mobiles (Shadowing Values) tab: The Mobiles (Shadowing Values) tab contains information on the shad-
owing margin for each link between the receiver and up to ten closest potential transmitters:
Note: The Mobiles (Shadowing Values) tab only appears if, when creating the simulation as
explained in "Creating Simulations" on page 523, you select "Detailed information about
mobiles" under Information to Retain.
- Value at Receiver (dB): The value of the shadowing margin at the receiver.
- Clutter: The clutter class on which the mobile is located.
- Path To: The name of the potential transmitter.
- Value (dB): The shadowing value for the potential link in the corresponding Path To column. These values
depend on the model standard deviation per clutter type on which the receiver is located and are randomly
distributed on a gaussian curve.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
The Statistics tab: The Statistics tab contains the following two sections:
- Request: Under Request, you will find data on the connection requests:
- Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; power control has not yet finished. The result depends on the traffic description and traffic input.
- During the first random trial, each user is assigned a service. The UL and DL rates that all users could
theoretically generate are provided.
- The breakdown per service (total number of users, number of users per activity status, and UL and DL
rates) is given.
- Results: Under Results, you will find data on the connection results:
- The number of iterations that were run in order to converge.
- The number and the percentage of non-connected users is given along with the reason for rejection.
These figures include rejected and delayed users. These figures are determined at the end of the simula-
tion and depend on the network design.
- The number and percentage of R99 bearer users connected to a cell, the number of users per frequency
band for dual-band networks, the number of users per activity status, and the total UL and DL rates they
generate. These figures include R99 users as well as HSDPA and HSUPA users (since all of them request
an R99 bearer); they are determined in the R99 part of the algorithm. These data are also given per serv-
ice.
- The total number and the percentage of connected users with an HSDPA bearer, the number of users per
frequency band for dual-band networks, the number of users per activity status, and DL total rate that they
generate. Both HSDPA and HSUPA users are considered since they both request an HSDPA bearer.
- The total number of connected HSUPA users and the percentage of users with an HSUPA bearer, the
number of users per frequency band for dual-band networks, the number of users per activity status, and
UL and DL total rates they generate. Only HSUPA users are considered.
The Sites (Average) and Sites (Standard Deviation) tabs: The Sites (Average) and Sites (Standard Deviation)
tabs contains the following average and standard deviation information, respectively, per site:
- Max No. of DL and UL CEs: The maximum number of channel elements available on uplink and downlink for
R99 bearers requested by R99, HSDPA and HSUPA users.
- No. of DL and UL CEs Used: The number of channel elements required on uplink and downlink for R99
bearers to handle the traffic of current simulation.
- No. of DL and UL CEs Due to SHO Overhead: The number of extra channel elements due to soft handover,
on uplink and downlink.
- Carrier Selection: The carrier selection method defined on the site equipment.
- Downlink and Uplink Overhead CEs/Cell: The overhead channel elements per cell on the downlink and on
the uplink, defined on the site equipment.
- AS Restricted to Neighbours: Whether the active set is restricted to neighbours of the reference cell. This
option is selected on the site equipment.
- Rake Factor: The rake factor, defined on the site equipment, enables Atoll to model a rake receiver on down-
link.
- MUD Factor: The multi-user detection factor, defined on the site equipment, is used to decrease intra-cell
interference on uplink.
- Compressed Mode: Whether compressed mode is supported. This option is defined on the site equipment.
- Max Iub Downlink and Uplink Backhaul Throughput (kbps): The maximum Iub backhaul throughput in the
downlink and uplink .
- Iub Downlink and Uplink Backhaul Throughput (kbps): The Iub backhaul throughput required on downlink
and uplink to handle the traffic of current simulation.
- Overhead Iub Throughput/Cell (kbps):the Iub throughput required by the cell for common channels in the
downlink, defined on the site equipment.
- HSDPA Iub Backhaul Overhead (%): This parameter is defined on the site equipment. It corresponds to the
percentage of the HSDPA bearer RLC peak rate to be added to the RLC peak rate. The total value corre-
sponds to the Iub backhaul throughput required by the HSDPA user for HS Channels in the downlink.
- Nb of Recommended E1/T1/Ethernet Link: The number of E1/T1/Ethernet links required to provide the total
Iub backhaul throughput.
- Instantaneous HSDPA Rate (kbps): The Instantaneous HSDPA Rate (kbps).
- Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps).
- HSUPA Rate (kbps): The HSUPA peak rate in kbps.
- DL and UL Throughput for Each Service: The R99 throughput in kbitss for each service.
The Cells (Average) and Cells (Standard Deviation) tabs: The Cells (Average) and Cells (Standard Deviation)
tabs contains the following average and standard deviation information, respectively, per site, transmitter, and
carrier:
- Max Power (dBm): The maximum power as defined in the cell properties.
- Pilot Power (dBm): The pilot power as defined in the cell properties.
- SCH power (dBm): The SCH power as defined in the cell properties.
- Other CCH power (dBm): The power of other common channels. It includes the other CCH power and the
DL HSUPA power as defined in the cell properties.
- Available HSDPA Power (dBm): The available HSDPA power as defined in the cell properties. This is the
power available for the HS-PDSCH and HS-SCCH of HSDPA bearer users. The value is either fixed by the
user when the HSDPA power is allocated statically, or by a simulation when the option HSDPA Power
Dynamic Allocation is selected.
- AS Threshold (dB): The active set threshold as defined in cell properties
- Gain (dBi): The gain as defined in the antenna properties for that transmitter.
- Reception Loss (dB): The reception loss as defined in the transmitter properties.
- Transmission Loss (dB): The transmission loss as defined in the transmitter properties.
- BTS Noise Figure (dB): The BTS noise figure as defined in the transmitter properties
- Total Transmitted R99 Power (dBm): The total transmitted R99 power is the power transmitted by the cell
on common channels (Pilot, SCH, other CCH), HSUPA channels (E-AGCH, E-RGCH, and E-HICH) and R99
traffic-dedicated channels.
- Total Transmitted Power (dBm): The total transmitted power of the cell is the sum of the total transmitted
R99 power and the available HSDPA power. If HSDPA power is allocated statically, this total transmitted
power must be lower than or equal to the maximum power. If HSDPA power is allocated dynamically, the total
transmitted power equals the maximum power minus the power headroom. In other words, the HSDPA power
corresponds to the difference between the total transmitted power and the R99 transmitted power.
Note: When the constraint "DL load" is set and HSDPA power is statically allocated, the total
transmitted power cannot exceed the maximum DL load (defined either in the cell
properties, or in the simulation). On the other hand, if HSDPA power is allocated
dynamically, the control is carried out on the R99 transmitted power, which cannot exceed
the maximum DL load.
- UL Total Noise (dBm): The uplink total noise takes into account the total signal received at the transmitter on
a carrier from intra and extra-cell terminals using the same carrier and adjacent carriers (uplink total interfer-
ence) and the thermal noise.
- Max UL Load Factor (%): The maximum uplink load factor that the cell can support. It is defined either in the
cell properties, or in the simulation creation dialogue.
- Max DL Load (% Pmax): The maximum percentage of power that the cell can use. It is defined either in the
cell properties, or in the simulation creation dialogue.
- UL Load Factor (%): The uplink cell load factor corresponds to the ratio between the uplink total interference
and the uplink total noise. If the constraint "UL load factor" has been selected, UL cell load factor is not allowed
to exceed the user-defined maximum UL load factor (either in the cell properties, or in the simulation creation
dialogue).
- UL Load Factor due to HSUPA (%): The uplink cell load caused by HSUPA traffic.
- DL Load Factor (%): The DL load factor of the cell i corresponds to the ratio (DL average interference [due
to transmitter signals on the same carrier] for terminals in the transmitter i area) (DL average total noise [due
to transmitter signals and to thermal noise of terminals] for terminals in the transmitter i area).
- UL and DL Noise Rise (dB): The uplink and downlink noise rises are calculated from uplink and downlink
load factors. These data indicate signal degradation due to cell load (interference margin in the link budget).
- DL R99 Load (% Pmax): The percentage of power used for R99 channels is determined by the total trans-
mitted R99 power-maximum power ratio (power stated in W). When the constraint "DL load" is set and HSDPA
power is allocated dynamically, the DL R99 Load can not exceed the user-defined Max DL Load (defined
either in the cell properties, or in the simulation).
- Reuse Factor (UL): The uplink reuse factor is the ratio between the uplink total interference and the intra-cell
interference.
- Reuse Efficiency Factor (UL): The uplink reuse efficiency factor is the reciprocal of the uplink reuse factor.
- Number of UL and DL Radio Links: The number of radio links corresponds to the number of user-transmitter
links on the same carrier. This data is calculated on uplink and on downlink and indicates the number of users
connected to the cell on uplink and downlink. Because of handover, a single user can use several radio links.
- Connection Success Rate (%): The connection success rate gives the ratio of connected users over the total
number of users in the cell.
- HSDPA Application Throughput (kbps): The HSDPA application throughput is the net HSDPA throughput
without coding (redundancy, overhead, addressing, etc.). It is calculated from the instantaneous HSDPA rate
(i.e., the DL obtained rate), the BLER, the HSDPA service scaling factor and the throughput offset.
- Min. HSDPA RLC Peak Rate (kbps): The minimum HSDPA RLC peak rate corresponds to the lowest of RLC
peak rates obtained by HSDPA bearer users connected to the cell.
- Max HSDPA RLC Peak Rate (kbps): The maximum HSDPA RLC peak rate: It corresponds to the highest of
RLC peak rates obtained by HSDPA bearer users connected to the cell.
- Avg. Instantaneous HSDPA Throughput (kbps): The average instantaneous HSDPA rate (kbps) is the
average number of kbits per second that the cell supports on downlink to provide one connected user with an
HSDPA bearer.
- Instantaneous HSDPA Rate (kbps): The instantaneous HSDPA rate (kbps) is the number of kbits per
second that the cell supports on downlink to provide simultaneous connected users with an HSDPA bearer.
- Instantaneous HSDPA MAC Throughput (kbps): The Instantaneous HSDPA MAC throughput (kbps) that
the cell carries.
- No. of Simultaneous HSDPA Users: The number of simultaneous HSDPA users corresponds to the number
of HSDPA bearer users that the cell supports at a time, i.e. within one time transmission interval. All these
users are connected to the cell at the end of the simulation HSDPA part; they have a connection with the R99
bearer (ADPCH-UL64 for HSDPA users and ADPCH-EDPCCH bearer for HSUPA users) and an HSDPA
bearer. At any given moment in time (within a time transmission interval), the number of simultaneous HSDPA
users cannot exceed the number of HS-SCCH channels per cell.
- No. of HSDPA Users: The number of HSDPA users include the connected and delayed HSDPA bearer users.
- No. of HSUPA Users: The number of HSUPA users connected to the cell.
- HSUPA Application Throughput (kbps): This is the net HSUPA throughput without coding (redundancy,
overhead, addressing, etc.).
- HSUPA UL Load Factor (%): The uplink cell load caused by HSUPA traffic.
- No. of Codes (512 Bits): The number of OVSF codes used per cell.
- The types of handover as a percentage: Atoll estimates the percentages of handover types for each trans-
mitter. Atoll only lists the results for the following handover status, no handover (11), softer (12), soft (22),
softer-soft (23) and soft-soft (33) handovers; the other handover status (other HO) are grouped.
- R99 UL and DL Throughput (kbps): The uplink and downlink R99 throughputs represent the numbers of
kbits per second delivered by the cell respectively on uplink and on downlink to supply HSUPA, HSDPA, and
R99 users with a R99 bearer. All the radio links in the cell, i.e., links due to handover, are taken into account
in the throughput calculation.
- R99 UL and DL Throughput Without HO (kbps): The uplink and downlink R99 throughputs represent the
numbers of kbits per second delivered by the cell respectively on uplink and on downlink to supply HSUPA,
HSDPA, and R99 users with a R99 bearer. Only the links with the best server are taken into account in the
calculation of throughput.
- Min TCH Pwr (dBm): The minimum power allocated to a traffic channel to supply services.
- Max TCH Pwr (dBm): The maximum power allocated to a traffic channel to supply services.
- Avg TCH Pwr: The average power allocated to a traffic channel to supply services.
- Rejected users: The number of rejected users per cell are sorted by the following values: Pmob > PmobMax,
Ptch > PtchMax, EcIo < (EcIo)min., UL Load Saturation, Ch. Elts Saturation, DL Load Saturation, Mul-
tiple Causes, Code Saturation, Admission Rejection, HSDPA Delayed, HSDPA Scheduler Saturation,
HSUPA Scheduler Saturation and Iub Throughput Saturation.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
Replaying a group: When you replay an existing group of simulations, Atoll reuses the same user distribution
(users with a service, a mobility and an activity status) as the one used to calculate the initial simulation. The shad-
owing error distribution between simulations is different. Traffic parameter changes (such as, maximum and min-
imum traffic channel powers allowed, Eb/Nt thresholds, etc.) may be taken into account or not. Finally, radio data
modifications (new transmitters, changes to the antenna azimuth, etc.) are always taken into account during the
power control (or rate/power control) simulation.
To replay a group of simulations, see "Replaying a Simulation or Group of Simulations" on page 536.
Using the Generator Initialisation Number: When you create groups of simulations using the same generator
initialisation number (which must be an integer other than 0) Atoll generates the same user and shadowing error
distributions (user with a service, a mobility, an activity status and a shadowing error) in all groups using the same
number. However, any modifications to traffic parameters (such as, maximum and minimum traffic channel powers
allowed, EbNt thresholds, etc.) and radio data (new transmitter, azimuth, etc.) are taken into account during the
power control simulation.
By creating and calculating one group of simulations, making a change to the network and then creating and calcu-
lating a new group of simulations using the same generator initialisation number, you can see the difference your
parameter changes make.
To create a new simulation to a group of simulations using the generator initialisation number, see "Creating a
New Simulation or Group of Simulations Using the Generator Initialisation Number" on page 537.
Duplicating a Group: When you duplicate a group, Atoll creates a group of simulations with the same simulation
parameters as those used to generate the group of simulations. You can then modify the simulation parameters
before calculating the group.
To duplicate a group of simulations, see "Duplicating a Simulation or Group of Simulations" on page 537.
Note: When adding a simulation to an existing group of simulations, the parameters originally
used to calculate the group of simulations are used for the new simulations.
Consequently, few parameters can be changed for the added simulation.
5. On the General tab of the dialogue, if desired, change the Name and Comments for this group of simulations.
6. Under Execution on the General tab, you can set the following parameters:
- Number of Simulations: Enter the number of simulations to added to this group of simulations.
- Execute Later: If you select the Execute Later check box, the simulation will not be carried out until you click
the Calculate button ( ). If the Execute Later check box is not selected, the simulation will be carried out
as soon as you click OK and close the dialogue.
7. Click OK. Atoll immediately begins the simulation unless you selected the Execute Later check box on the Gen-
eral tab.
Note: When replaying an existing group of simulations, some parameters originally used to
calculate the group of simulations are reused for the replayed group. Consequently, few
parameters can be changed for the replayed group.
5. In the General tab of the dialogue, you can set the following parameters:
- Select the level of detail as explained in "Creating Simulations" on page 523 that will be available in the output
from the Information to retain list.
- Under Cell Load Constraints, you can set the constraints as explained in "Creating Simulations" on page 523
that Atoll must respect during the simulation.
- Under Bearer Negotiation, check the Rate Downgrading check box if you want to permit bearer down-
grading during the simulation.
6. In the Source Traffic tab of the dialogue, check the Refresh Traffic Parameters check box if you want to take into
account traffic parameter changes (such as, maximum and minimum traffic channel powers allowed, Eb/Nt thresh-
olds, etc.) in the replayed simulation.
7. In the Advanced tab, you can set the following parameters:
- Max Number of Iterations: Enter the maximum number of iterations that Atoll should run to make conver-
gence.
- UL Convergence Threshold: Enter the relative difference in terms of interference and connected users on
the uplink that must be reached between two iterations.
- DL Convergence Threshold: Enter the relative difference in terms of interference and connected users on
the downlink that must be reached between two iterations.
8. Click OK. Atoll immediately begins the simulation unless you selected the Execute Later check box on the Gen-
eral tab.
Creating a New Simulation or Group of Simulations Using the Generator Initialisation Number
To create a new simulation or group of simulations using the generator initialisation number:
1. Click the Data tab in the Explorer window.
2. Right-click the UMTS Simulations folder. The context menu appears.
3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears.
4. Click the Advanced tab.
5. Under Generator Initialisation, enter an integer as the generator initialisation value. The integer must be the
same generator initialisation number as used in the group of simulations with the user and shadowing error distri-
butions you want to use in this simulation or group of simulations. If you enter "0", the default, the user and shad-
owing error distribution will be random. If you enter any other integer, the same user and shadowing error
distribution will be used for any simulation using the same generator initialisation value.
6. For information on setting other parameters, see "Creating Simulations" on page 523.
Tip: You can create a new group of simulations with the same parameters as the original group
of simulations by duplicating an existing one as explained in "Duplicating a Simulation or
Group of Simulations" on page 537.
Note: The AS analysis does not take possible network saturation into account. Therefore, there
is no guarantee that a simulated mobile with the same receiver characteristics can verify
the point analysis, simply because the simulated network may be saturated.
1. Click the Point Analysis button ( ) on the toolbar. The Point Analysis window appears. (see Figure 9.13).
2. Click the AS Analysis tab.
3. At the top of the AS Analysis tab, select from the Load Conditions list, the simulation or group of simulations you
want to base the AS analysis on.
4. Select the Terminal, Service, and Mobility.
5. Right-click the Point Analysis window and select Properties from the context menu. The Properties dialogue
appears.
6. Select or clear the following options:
- Whether shadowing is to be taken into account (and, if so, the cell edge coverage probability and shadowing
margin).
- Whether indoor coverage is to be taken into account.
- Whether downgrading is allowed.
7. Click OK to close the Properties dialogue.
8. Move the pointer over the map to make an active set analysis for the current location of the pointer.
As you move the pointer, Atoll indicates on the map which is the best server for the current position (see
Figure 9.31 on page 488).
Information on the current position is given on the AS Analysis tab of the Point Analysis window. See Figure 9.32
on page 489 for an explanation of the displayed information.
9. Click the map to leave the point analysis pointer at its current position.
To move the pointer again, click the point analysis pointer on the map and drag it to a new position.
10. Click the Point Analysis button ( ) on the toolbar again to end the point analysis.
- Effective Service Area: For information on making a effective service area analysis, see "Studying Effective
Service Area" on page 482.
Coverage predictions on noise and interference:
- Downlink Total Noise: For information on making a downlink total noise coverage prediction, see "Studying
Downlink Total Noise" on page 485.
- Pilot Pollution: For information on making a pilot pollution coverage analysis, see "Calculating Pilot Pollution"
on page 486.
A handover status coverage prediction to analyse macro-diversity performance:
- Handoff Status: For information on making a handover status coverage prediction, see "Making a Handover
Status Coverage Prediction" on page 487.
An HSDPA coverage prediction to analyse A-DPCH qualities, HS-SCCH power or quality per HS-SCCH channel
and to model fast link adaptation.
- HSDPA Coverage Prediction: For information on making an HSDPA coverage prediction, see "HSDPA Cov-
erage Prediction" on page 489.
An HSUPA coverage prediction to analyse the required E-DPDCH Ec/Nt, the required terminal power, and the
obtained HSUPA bearer.
- HSUPA Coverage Prediction: For information on making an HSUPA coverage prediction, see "HSUPA Cov-
erage Prediction" on page 491.
The procedures for the coverage predictions assume that simulation results are not available. When no simulations are
available, you select "(Cells Table)" from the Load Conditions list, on the Condition tab. However, when simulations are
available you can base the coverage prediction on one simulation or a group of simulations.
To base a coverage prediction on a simulation or group of simulations, when setting the parameters:
1. Click the Condition tab.
2. From the Load Conditions list, select the simulation or group of simulations on which you want to base the cov-
erage prediction.
3. If you select a group of simulations from the Load Conditions list, select one of the following:
- All: If you select All to make a statistical analysis of all simulations based on the defined Probability (the prob-
ability must be from 0 to 1). This will make a global analysis of all simulations in a group and with an evaluation
of the network stability in terms of fluctuations in traffic.
- Average: Select Average make the coverage prediction on the average of the simulations in the group.
Note: If you are importing more than one file, you can select contiguous files by clicking the first
file you want to import, pressing SHIFT and clicking the last file you want to import. You
can select non-contiguous files by pressing CTRL and clicking each file you want to
import.
Note: Files with the extension PLN, as well as some FMT files (created with previous versions of
TEMS) are imported directly into Atoll; you will not be asked to define the data structure
using the Import of Measurement Files dialogue.
6. If you already have an import configuration defining the data structure of the imported file or files, you can select
it from the Configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have
an import configuration, continue with step 7.
a. Under Configuration, select an import configuration from the Configuration list.
b. Continue with step 10.
Notes:
When importing a test mobile data path file, existing configurations are available in the Files
of type list of the Open dialogue, sorted according to their date of creation. After you have
selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises
the extension. In case several configurations are associated with an extension, Atoll chooses
the first configuration in the list.
The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in
the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see
the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters:
- Name: By default, Atoll names the new test mobile data path after the imported file. You can change this
name if desired.
- Under Receiver, set the Height of the receiver antenna and the Gain and Losses.
- Under Measurement Conditions,
- Units: Select the measurement units used.
- Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document.
If the coordinates used in the file you are importing are different than the coordinates used in the Atoll
document, you must click the Browse button ( ) and select the coordinate system used in the test
mobile data file. Atoll will then convert the data imported to the coordinate system used in the Atoll docu-
ment.
8. Click the Setup tab (see Figure 9.43).
Figure 9.43: The Setup tab of the Import of Measurement Files dialogue
a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Dec-
imal Symbol used in the file.
b. Click Setup to link file columns and internal Atoll fields. The Test Mobile Data Configuration dialogue ap-
pears.
c. Select the columns in the imported file that give the X-Coordinates and the Y-Coordinates of each point in
the test mobile data file.
Note: You can also identify the columns containing the XY coordinates of each point in the test
mobile data file by selecting them from the Field row of the table on the Setup tab.
d. In the SC Group Identifier box, enter a string that must be found in the column names identifying the scram-
bling code group of scanned cells. For example, if the string "SC_Group" is found in the column names iden-
tifying the scrambling code group of scanned cells, enter it here. Atoll will then search for columns with this
string in the column name.
If there is no scrambling code group information contained in the test mobile data file, leave the SC Group
Identifier box empty.
e. In the SC Identifier box, enter a string that must be found in the column names identifying the scrambling code
of scanned cells. For example, if the string "SC" is found in the column names identifying the scrambling code
of scanned cells, enter it here. Atoll will then search for columns with this string in the column name.
f. From the SC Format list, select the scrambling code format, either "Decimal" or "Hexadecimal."
g. Click OK to close the Test Mobile Data Configuration dialogue.
Important:
If you have correctly entered the information under File on the Setup tab, and the necessary
values in the Test Mobile Data Configuration dialogue, Atoll should recognize all columns in
the imported file. If not, you can click the name of the column in the table in the Field row and
select the column name. For each field, you must ensure that each column has the correct data
type in order for the data to be correctly interpreted. The default value under Type is "<Ignore>".
If a column is marked with "<Ignore>", it will not be imported.
The data in the file must be structured so that the columns identifying the scrambling code group
and the scrambling code are placed before the data columns for each cell. Otherwise Atoll will
not be able to properly import the file.
9. If you wish to save the definition of the data structure so that you can use it again, you can save it as an import
configuration:
a. On the Setup tab, under Configuration, click Save. The Configuration dialogue appears.
b. By default, Atoll saves the configuration in a special file called "NumMeasINIfile.ini" found in Atolls installa-
tion folder. In case you cannot write into that folder, you can click Browse to choose a different location.
c. Enter a Configuration Name and an Extension of the files that this import configuration will describe (for ex-
ample, "*.csv").
d. Click OK.
Atoll will now select this import configuration automatically every time you import a test mobile data path file
with the selected extension. If you import a file with the same structure but a different extension, you will be
able to select this import configuration from the Configuration list.
Notes:
You do not have to complete the import procedure to save the import configuration and have
it available for future use.
When importing a CW measurement file, you can expand the NumMeasINIfile.ini file by clicking
the button ( ) in front of the file in the Setup part to display all the available import configura-
tions. When selecting the appropriate configuration, the associations are automatically made
in the table at the bottom of the dialogue.
You can delete an existing import configuration by selecting the import configuration under
Setup and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The
mobile data are imported into the current Atoll document.
You can, for example, display a signal level in a certain colour, choose a symbol type for Transmitter 1 (a circle, triangle,
cross, etc.) and a symbol size according to the altitude.
Notes:
Fast Display forces Atoll to use the lightest symbol to display the points. This is particularly useful
when you have a very large number of points.
You can not use Multiple Shadings if the Fast Display check box has been selected.
You can sort test mobile data paths in alphabetical order on the Data tab of the Explorer window by
right-clicking the Test Mobile Data Path folder and selecting Sort Alphabetically from
the context menu.
You can export the display settings of a test mobile data path in a configuration file to make them
available for future use. You can export the display settings or import display settings by
clicking the Actions button on the Display tab of the test mobile data paths Properties
dialogue and selecting Export or Import from the menu.
Note: You can permanently delete the points located in the clutter classes whose check boxes
you clear by selecting the Delete points outside the filter check box.
b. Underneath each column name, enter the criteria on which the column will be filtered as explained in the fol-
lowing table:
9. Click OK to filter the data according to the criteria you have defined.
Filters are combined first horizontally, then vertically. For more information on filters, see "Advanced Data Filtering"
on page 71.
Note: The Refresh Geo Data option available in the context menu of Test Mobile Data paths
enables you to update heights (Alt DTM, Clutter height, DTM+Clutter) and the clutter class
of test mobile data points after adding new geographic maps or modifying existing ones.
- At the top of the Condition tab, you can set the range of signal level to be calculated. Under Server, you
can select whether to calculate the signal level from all transmitters, or only the best or second-best signal.
If you choose to calculate the best or second-best signal, you can enter a Margin. If you select the Shad-
owing taken into account check box, you can change the Cell Edge Coverage Probability. You can
select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class.
Finally, you can select the Carrier to be studied.
- Pilot Reception Analysis (EcI0): Click the Condition tab.
- On the Condition tab, you can select which simulation to study in the Load Conditions list. Or you can
select a group of simulations and either select All to perform an average analysis of all simulations in the
group based on a Probability (from 0 to 1) or select Average to perform statistical analysis of all simula-
tions.
- If you want to perform the coverage prediction without a simulation, you can select "(Cells Table)" from
Load Conditions. In this case, Atoll calculates the coverage prediction using the UL load factor and the
DL total power defined in the cell properties.
- You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on
page 475. You must also select which Carrier is to be considered.
- If you want the pilot signal quality prediction to consider shadowing, you can select the Shadowing taken
into account check box and enter a percentage in the Cell Edge Coverage Probability text box.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- Service Area (EbNt) Downlink: Click the Condition tab.
- On the Condition tab, you can select which simulation to study in the Load Conditions list. Or you can
select a group of simulations and either select All to perform an average analysis of all simulations in the
group based on a Probability (from 0 to 1) or select Average to perform statistical analysis of all simula-
tions.
- If you want to perform the coverage prediction without a simulation, you can select "(Cells Table)" from
Load Conditions. In this case, Atoll calculates the coverage prediction using the UL load factor and the
DL total power defined in the cell properties.
- You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on
page 475. You must also select which Carrier is to be considered.
- If you want the service area (Eb/Nt) coverage prediction to consider shadowing, you can select the Shad-
owing taken into account check box and enter a percentage in the Cell Edge Coverage Probability
text box.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- Service Area (EbNt) Uplink: Click the Condition tab.
- On the Condition tab, you can select which simulation to study in the Load Conditions list. Or you can
select a group of simulations and either select All to perform an average analysis of all simulations in the
group based on a Probability (from 0 to 1) or select Average to perform statistical analysis of all simula-
tions.
- If you want to perform the coverage prediction without a simulation, you can select "(Cells Table)" from
Load Conditions. In this case, Atoll calculates the coverage prediction using the UL load factor and the
DL total power defined in the cell properties.
- You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on
page 475. You must also select which Carrier is to be considered.
- If you want the service area (Eb/Nt) coverage prediction to consider shadowing, you can select the Shad-
owing taken into account check box and enter a percentage in the Cell Edge Coverage Probability
text box.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
6. When you have finished setting the parameters for the coverage prediction, click OK.
You can create a new coverage prediction by repeating the procedure from step 1. to step 6. for each new cover-
age prediction.
7. When you have finished creating new coverage predictions for these test mobile data, right-click the test mobile
data. The context menu appears.
8. Select Calculations > Calculate All the Studies from the context menu.
A new column for each coverage prediction is added in the table for the test mobile data. The column contains the
predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned
to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Managing Calcu-
lations in Atoll).
You can display the information in these new columns in the Test Mobile Data window. For more information on
the Test Mobile Data window, see "Analysing Data Variations Along the Path" on page 546.
Note: Atoll can display the best server and up to six other servers in the active set. If you want
to display for example, the point signal level, remember to select the check box for the
point signal level for all servers in the For the Fields list. The new column will then display
the point signal level for the selected transmitter for all servers if a value exists.
8. Click OK. Atoll creates a new column in the test mobile path data table for the selected transmitters and with the
selected values.
5. Click Display at the top of the Test Mobile Data window. The Display Parameters dialogue appears (see
Figure 9.46).
Note: You can change the display status or the colour of more than one field at a time. You can
select contiguous fields by clicking the first field, pressing SHIFT and clicking the last field
you want to import. You can select non-contiguous fields by pressing CTRL and clicking
each field. You can then change the display status or the colour by right-clicking on the
selected fields and selecting the choice from the context menu.
The selected fields are displayed in the Test Mobile Data window.
7. You can display the data in the test mobile path in two ways:
- Click the values in the Test Mobile Data window.
- Click the points on the test mobile path in the map window.
The test mobile data path appears in the map window as an arrow pointing towards the serving cell, with a number
identifying the best server (see Figure 9.45 on page 546). If the transmitter display type is "Automatic," both the
number and the arrow are displayed in the same colour as the transmitter. For information on changing the display
type to "Automatic," see "Defining the Display Type" on page 34.
8. You can display a second Y-axis on the right side of the window in order to display the values of a variable with
different orders of magnitude than the ones selected in the Display Parameters dialogue. You can select the sec-
ondary Y-axis from the right-hand list on the top of the Test Mobile Data window. The selected values are dis-
played in the colours defined for this variable in the Display Parameters dialogue.
9. You can change the zoom level of the Test Mobile Data window display in the Test Mobile Data window in the
following ways:
- Zoom in or out:
i. Right-click the Test Mobile Data window.
ii. Select Zoom In or Zoom Out from the context menu.
- Select the data to zoom in on:
i. Right-click the Test Mobile Data window on one end of the range of data you want to zoom in on.
ii. Select First Zoom Point from the context menu.
iii. Right-click the Test Mobile Data window on the other end of the range of data you want to zoom in on.
iv. Select Last Zoom Point from the context menu. The Test Mobile Data window zooms in on the data be-
tween the first zoom point and the last zoom point.
10. Click the data in the Test Mobile Data window to display the selected point in the map window. Atoll will recentre
the map window on the selected point if it is not presently visible.
Tip: If you open the table for the test mobile data you are displaying in the Test Mobile Data
window, Atoll will automatically display in the table the data for the point that is displayed
in the map and in the Test Mobile Data window (see Figure 9.45 on page 546).
a. Select Print from the context menu. The Print dialogue appears.
b. Click OK to print the contents of the Test Mobile Data window.
For every pair of carriers that is not defined, Atoll assumes that there is no inter-carrier interference.
d. Press ENTER to create the carrier pair and to create a new row in the table.
Important: When you have more than one frequency band, the carriers must be numbered
sequentially, contiguously (i.e., you cannot skip numbers in a range of carriers, and the
range of carriers in one band cannot overlap the range of carriers in another), and
uniquely (i.e., you can only use each number once).
For example:
Band 2100: First carrier: 0; Last carrier 1 and Band 900: First carrier: 2 and Last carrier: 2
with a compressed-mode-capable equipment and either the pilot RSCP, or the received EcI0, or both of them are
lower than the defined activation thresholds.
- RSCP Activation Threshold: You can select the RSCP Active check box and enter a RSCP Activation
Threshold.
- EcI0 Activation Threshold: You can select the EcI0 Active check box and enter a EcI0 Activation
Threshold.
Note: You must select either the RSCP Active check box or the EcI0 Active check box or both.
- EbNt UL and DL Target Increase: When compressed mode is activated, EbNt requirements in UL and DL
are increased. In order to take this into account, Atoll adds UL and DL EbNt target increase values to the UL
and DL EbNt requirements set for each radio bearer.
HSDPA: Under HSDPA, you can define how total noise is calculated and how the CQI (Channel Quality Indicator)
is evaluated for HSDPA.
- Nt: You can select "Total noise" and Atoll will calculate Nt as the noise generated by all transmitters plus
thermal noise or you can select "Without useful signal" and Atoll will calculate Nt as the total noise less the
signal of the studied cell.
- CQI: You can select Based on CPICH quality and Atoll will measure the CQI based on the pilot EcNt or you
can select Based on HS-PDSCH quality and Atoll will measure the CQI based on the HS-PDSCH EcNt.
Depending on the option selected, you will have to define either a CQI=f(CPICH Ec/Nt) graph, or a CQI=f(HS-
PDSCH Ec/Nt) graph in the Properties dialogue of the terminal equipment. The calculated CQI will be used
to determine the best bearer.
- UL DPCCH/DPCH Power Ratio: Enter or modify the uplink DPCCH (Dedicated Physical Control Channel)/
DPCH (Dedicated Physical Channel) power ratio. The DPCH power is the combination of the DPCCH and the
DPDCH (Dedicated Physical Data Channel) power.
- DL DPCCH/DPCH Power Ratio: Enter or modify the downlink DPCCH (Dedicated Physical Control Channel)/
DPCH (Dedicated Physical Channel) power ratio.
- DL Spreading Factor (Active Users): Enter or modify the downlink spreading factor for active users. This
parameter is used to estimate the number of OVSF codes required by an active user using the R99 radio
bearer.
- DL Spreading Factor (Inactive Users): Enter or modify the downlink spreading factor for inactive users. This
parameter is used to estimate the number of OVSF codes required by an inactive user with the R99 radio
bearer.
- Min. TCH Power (dBm): Enter or modify the minimum traffic channel power. The minimum and maximum
traffic channel power make up the dynamic range for downlink power control.
- Max TCH Power (dBm): Enter or modify the maximum traffic channel power.
Note: The maximum and minimum traffic channel powers can be either absolute values or
values relative to the pilot power; this depends on the option defined on the Global
Parameters tab of the Transmitters Properties dialogue. These values have to be
manually modified when the option is changed.
6. When you have finished entering or modifying the R99 radio bearer parameters, double-click the row of the R99
radio bearer to open the bearers Properties dialogue. The Properties dialogue appears.
7. Click the EbNt tab. On the EbNt tab, you can define downlink and uplink EbNt requirements. These are the
thresholds (in dB) that must be reached to provide users with the service. These parameters depend on the
mobility type and reception equipment; these parameters must be defined for each possible combination of
mobility type and reception equipment.
Using transmit (Tx) and receive (Rx) diversity results in a quality gain on received downlink and uplink EbNt. In
Atoll, this is modelled by reducing the downlink and uplink EbNt requirements. Therefore, in addition to downlink
and uplink EbNt requirements, you can specify gains on received downlink and uplink EbNt for each possible
diversity configuration. Atoll will consider them when Tx or Rx diversity configurations are assigned to transmit-
ters.
Note: The rake efficiency factor used to model the recombination in downlink can be set in
terminal properties.
- Carrier selection: Carrier selection refers to the carrier selection method used during the transmitter admis-
sion control in the mobile active set. The selected strategy is used in simulations when no carrier is specified
in the properties of the service (all the carriers can be used for the service) or when the carrier specified for
the service is not used by the transmitter. On the other hand, the specified carrier selection mode is always
taken into account in predictions (AS analysis and coverage studies). Choose one of the following:
- Min. UL Load Factor: The carrier with the minimum UL noise (carrier with the lowest UL load factor) is
selected.
- Min. DL Total Power: The carrier with the minimum DL total power is selected.
- Random: The carrier is randomly chosen.
- Sequential: Carriers are sequentially loaded. The first carrier is selected as long as it is not overloaded.
Then, when the maximum uplink load factor is reached, the second carrier is chosen and so on.
- Overhead uplink and downlink CEs: The overhead uplink and downlink channel elements (CEs) correspond
to the numbers of channel elements that a cell uses for common channels in the uplink and downlink. This
setting is also used for OVSF code allocation; it indicates the number of OVSF codes to be allocated to control
channels per cell.
- AS restricted to neighbours: Select this option if you want the other transmitters in the active set to belong
to the neighbour list of the best server.
- Compressed Mode: If you select this option, cells located on sites with this equipment are able to manage
compressed mode when radio conditions require it. Compressed mode is generally used to prepare the hard
handover of users with single receiver terminals.
- Overhead Iub Throughput/Cell (kbps): The overhead Iub throughput per cell corresponds to the Iub
throughput required by the cell for common channels in the downlink.
- HSDPA Iub Backhaul Overhead (%): The HSDPA Iub backhaul overhead corresponds to the percentage of
the HSDPA bearer RLC peak rate to be added to the RLC peak rate. The total value corresponds to the Iub
backhaul throughput required by the HSDPA user for HS Channels in the downlink.
- Throughput Supported per E1/T1/Ethernet Link (kbps): The throughput supported per E1/T1/Ethernet link
corresponds to the throughput carried by an E1/T1/Ethernet link. This parameter is used to calculate the
required Iub capacity, i.e. the number of E1/T1/Ethernet links required to provide the total throughput.
5. Click the Close button ( ) to close the table.
9.5.5.2 Defining Resource Consumption per UMTS Site Equipment and R99 Ra-
dio Bearer
The number of channel elements and the Iub backhaul throughput consumed by a R99 bearer user depend on the site
equipment, on the R99 radio bearer, and the link direction (up or down). The number of channel elements and the Iub
backhaul throughput consumed can be defined for UMTS simulations.
To define channel element and Iub backhaul throughput consumption during UMTS simulations:
1. Click the Data tab in the Explorer window.
2. Right-click the Sites folder. The context menu appears.
3. Select Equipment > R99 Resource Consumption from the context menu. The R99 Resource Consumption
table appears.
4. For each equipment-R99 radio bearer pair, enter in the R99 Resource Consumption table the number of UL and
DL channel elements and the UL and DL Iub backhaul throughputs that Atoll will consume during the power con-
trol simulation.
5. Click the Close button ( ) to close the table.
9.5.5.3 Defining Resource Consumption per UMTS Site Equipment and HSUPA
Radio Bearer
The number of channel elements and the Iub backhaul throughput consumed by a HSUPA bearer user in the uplink direc-
tion depend on the site equipment and on the HSUPA radio bearer. The number of channel elements and the Iub backhaul
throughput consumed can be defined for UMTS simulations.
To define channel element and Iub backhaul throughput consumption during UMTS simulations:
1. Click the Data tab in the Explorer window.
2. Right-click the Sites folder. The context menu appears.
3. Select Equipment > HSUPA Resource Consumption from the context menu. The HSUPA Resource Con-
sumption table appears.
4. For each equipment-HSUPA radio bearer pair, enter in the HSUPA Resource Consumption table the number of
UL channel elements and the UL Iub backhaul throughput that Atoll will consume during the power control simu-
lation.
5. Click the Close button ( ) to close the table.
5. Double-click the reception equipment type you want to modify. The reception equipment types Properties dia-
logue appears.
Note: You can create a new reception equipment type by entering a name in the row marked
with the New Row icon ( ) and pressing ENTER.
The Best HSDPA Bearer table describes the index of the best HSDPA bearer as a function of the HS-PDSCH
CQI.
The CQI graphs and best bearer graphs are used in the simulation and in the HSDPA prediction study to model
fast link adaptation (selection of the HSDPA bearer).
The supplier RRM (radio resource management) strategy can be taken into account using the Best HSDPA
Bearer table, for example:
- You can define several pieces of reception equipment with a separate table for each. You can reserve low
bearer indexes for poor-performance reception equipment and higher bearer indexes for high-performance
equipment.
- You can specify a graph for each mobility. Here, you can reserve low bearer indexes for high speeds and
higher bearer indexes for low speeds.
- You can also give priority to either one user by assigning him a high bearer index or to all users by assigning
them low bearer indexes.
10. Click the HSDPA Quality Graphs tab.
11. Ensure that a Quality Indicator has been chosen for each Radio Bearer Index. You can edit the values in the
DL Quality Indicator Table by clicking directly on the table entry, or by selecting the Quality Indicator and
clicking the Downlink Quality Graph button.
The Downlink Quality table describes the variation of the BLER as a function of the HS-PDSCH EcNt. It is used
to calculate the application throughput for the HSDPA coverage prediction.
The Early Termination Probabilities table describes the variation of the early termination probability as a function
of the number of retransmissions. It is used in the HSUPA prediction to calculate the average RLC throughput and
the average application throughput when HARQ (Hybrid Automatic Repeat Request) is used.
TX RX
Note: No MIMO gain (diversity, spatial multiplexing) is applied if N Ant = N Ant = 1 .
Transmit or receive diversity uses more than one transmission or reception antenna to send or receive more than one copy
of the same signal. The signals are constructively combined (using optimum selection or maximum ratio combining) at the
receiver to extract the useful signal. As the receiver gets more than one copy of the useful signal, the signal level at the
receiver after combination of all the copies is more resistant to interference than a single signal would be. Therefore, diver-
sity improves the quality at the receiver. It is often used for the regions of a cell that have bad quality conditions.
In Atoll, you can set whether a cell supports transmit diversity by selecting HSPA+ (Transmit Diversity) in cell properties
(see "Cell Definition" on page 436). Diversity gains on downlink can be defined in the reception equipment for different
numbers of transmission and reception antenna ports, mobility types and HSDPA bearers. For more information on down-
link diversity gains, see "Creating or Modifying Reception Equipment" on page 554. Additional gain values can be defined
per clutter class. For information on setting the additional downlink diversity gain for each clutter class or for all clutter
classes, see "Defining Clutter Class Properties" on page 115.
During calculations in Atoll, a user (mobile, pixel, or point receiver) using a MIMO-capable terminal, and connected to a
cell that supports HSPA+ with transmit diversity, will benefit from the downlink diversity HS-PDSCH Ec/Nt gain.
Spatial Multiplexing
Spatial multiplexing uses more than one transmission antenna to send different signals (data streams) on each antenna.
The receiver can also have more than one antenna for receiving different signals. Using spatial multiplexing with M trans-
mission and N reception antenna ports, the throughput over the transmitter-receiver link can be theoretically increased M
or N times, depending on which is smaller, M or N. Spatial multiplexing improves the throughput (channel capacity) for a
given HS-PDSCH Ec/Nt, and is used for the regions of a cell that have sufficient HS-PDSCH Ec/Nt conditions.
In Atoll, you can set whether a cell supports spatial multiplexing by selecting HSPA+ (Spatial Multiplexing) in cell prop-
erties (see "Cell Definition" on page 436). Spatial multiplexing capacity gains can be defined in the reception equipment
for different numbers of transmission and reception antenna ports, mobility types and HSDPA bearers. For more informa-
tion on spatial multiplexing gains, see "Creating or Modifying Reception Equipment" on page 554.
During calculations in Atoll, a user (mobile, pixel, or point receiver) using a MIMO-capable terminal, and connected to a
cell that supports HSPA+ with spatial multiplexing, will benefit from the spatial multiplexing gain in its throughput depending
on its HS-PDSCH Ec/Nt.
As spatial multiplexing improves the channel capacity or throughputs, the HS-PDSCH Ec/Nt of a user is first determined.
Once the HS-PDSCH Ec/Nt is known, Atoll determines the corresponding CQI and calculates the user throughput based
on the bearer available at the user location. The obtained user throughput is then increased according to the spatial multi-
plexing capacity gain and the Spatial Multiplexing Gain Factor of the users clutter class. The capacity gains defined in
Max Spatial Multiplexing Gain graphs are the maximum theoretical capacity gains using spatial multiplexing. Spatial
multiplexing requires rich multipath environment, without which the gain is reduced. In the worst case, there is no gain.
Therefore, you can define a Spatial multiplexing Gain Factor per clutter class whose value can vary from 0 to 1 (0 = no
gain, 1 = 100 % gain). For information on setting the Spatial multiplexing Gain Factor for each clutter class or for all
clutter classes, see "Defining Clutter Class Properties" on page 115.
The spatial multiplexing capacity gain vs. HS-PDSCH Ec/Nt graphs available in Atoll by default have been generated
based on the maximum theoretical spatial multiplexing capacity gains obtained using the following equations:
CC MIMO
G MIMO = ---------------------
-
CC SISO
Ec
-------
TX RX Nt HS PDSCH
Where CC MIMO = Min ( N Ant, N Ant ) Log 2 1 + ------------------------------------------ is the channel capacity at a given HS-PDSCH Ec/Nt for
TX RX
Min ( N Ant, N Ant )
Ec
a MIMO system using N Ant transmission and N Ant reception antenna ports. CC SISO = Log 2 1 + ------- is
TX RX
Nt HS PDSCH
the channel capacity for a single antenna system at a given HS-PDSCH Ec/Nt. HS-PDSCH Ec/Nt is used as a ratio (not
dB) in these formulas. You can replace the default spatial multiplexing capacity gain graphs with graphs extracted from
simulated or measured values.
9.5.9.1 Displaying the Shadowing Margins and Macro-diversity Gain per Clutter
Class
To display the shadowing margins and macro-diversity gain per clutter class:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Shadowing Margins from the context menu. The Shadowing Margins and Gains dialogue appears (see
Figure 9.47).
4. You can set the following parameters:
- Cell Edge Coverage Probability: Enter the probability of coverage at the edge of the cell. The value you enter
in this dialogue is for information only.
- Standard Deviation: Select the type of standard deviation to be used to calculate the shadowing margin or
macro-diversity gains:
- From Model: The model standard deviation. Atoll will display the shadowing margin of the signal level.
- EcI0: The EcI0 standard deviation. Atoll will display the EcI0 shadowing margin and the resulting DL pilot
macro-diversity gains. The macro-diversity gains will be calculated using the values you enter in 1st - 2nd
Best Signal Difference and 2nd - 3rd Best Signal Difference.
- UL EbNt: The EbNt UL standard deviation. Atoll will display the EbNt UL shadowing margin and the
resulting UL macro-diversity gains. The macro-diversity gains will be calculated using the values you enter
in 1st - 2nd Best Signal Difference and 2nd - 3rd Best Signal Difference.
- DL EbNt: The EbNt DL standard deviation. Atoll will display the EbNt DL shadowing margin.
5. If you select "EcI0" or "EbNt UL" as the standard deviation under Standard Deviation, you can enter the differ-
ences that will be used to calculate the macro-diversity gain under Macro-Diversity Parameters:
- 1st - 2nd Best Signal Difference: If you selected "EcI0" as the standard deviation under Standard Devia-
tion, enter the allowed EcI0 difference between the best server and the second one. This value is used to
calculate DL macro-diversity gains. If you selected "EbNt UL" as the standard deviation under Standard Devi-
ation, enter the allowed Eb/Nt difference between the best server and the second one. This value is used to
calculate UL macro-diversity gains.
- 2nd - 3rd Best Signal Difference: If you selected "EcI0" as the standard deviation under Standard Devia-
tion, enter the allowed EcI0 difference between the second-best server and the third one. This value is used
to calculate DL macro-diversity gains. If you selected "EbNt UL" as the standard deviation under Standard
Deviation, enter the allowed Eb/Nt difference between the second-best server and the third one. This value
is used to calculate UL macro-diversity gains.
6. Click Calculate. The calculated shadowing margin is displayed. If you selected "EcI0" or "EbNt UL" as the
standard deviation under Standard Deviation, Atoll also displays the macro-diversity gains for two links and for
three links.
7. Click Close to close the dialogue.
Atoll
RF Planning and Optimisation Software
Atoll User Manual
Note: It is recommended to define a computation zone. ACP uses the computation zone as the
area in which the quality figures (RSCP, EcIo) are calculated and improved during
optimisation. Additionally, the zone defined by ACP might take into account areas outside
of actual traffic boundaries.
Important: The ACP does not take Atoll's hot spot zones into consideration. If you want to use the
hot spot zones defined in the Atoll document with ACP, you must first export them as
ArcView SHP files and then import them in ACP.
Note: ACP automatically considers all the cells that have an effect on the computation or focus
zone, and ignores the rest (for example, cells that are far enough away to have no impact
on the selected cells). It is nonetheless recommended to use a filtering zone to speed up
initial data extraction from the Atoll document.
ACP enables you to define a resolution to extract the data from traffic maps. The resolution should usually be the same
as the resolution of the traffic maps. To increase the accuracy of the data-extraction process, you can increase the reso-
lution defined in the Extract traffic with resolution text box.
In the ACP, each traffic map is converted into one or more traffic profiles. A traffic profile is a combination of:
a service (UMTS), terminal, and mobility
a traffic distribution
a relative load (expressed in Erlangs).
Note: For the moment, traffic profiles are only used to evaluate the traffic weighting to apply to
each pixel (by adding the load-scaled traffic distribution on each traffic profile). This
information will also be used in the future to better manage cell load (and the evaluation of
network quality).
Note: You can set ACP to not take macro-diversity gains into consideration by setting the
appropriate option in the acp.ini file. You will need to update the corresponding
parameters in the atoll.ini file as well. For information on modifying the atoll.ini file, see the
Technical Reference Guide.
Note: Pilot power optimisation and site selection (without reconfiguration) are made
independently of the method used to determine changes to path loss attenuation.
DEM file
Atoll Standard Propagation Model Clutter Height file (optional)
Clutter file (optional)
Because the path loss information is not stored in the ACP optimisation setup but in the Atoll document where it is
accessed by ACP, changes in the Atoll document can cause inconsistency between the optimisation results and the actual
state of the network, for example, when transmitters are modified in the document. ACP deals with this situation by locking
optimisation results. An optimisation can not be rerun on locked results if the path loss data are not consistent with the
internal state of the optimisation. The results are automatically unlocked if the state of the Atoll document again becomes
consistent with the ACP optimisation. The same mechanism applies when settings produced by an optimisation run are
committed to the Atoll network. The results are locked after being committed and will be unlocked if the network is rolled
back to the state on which the optimisation was based.
Notes: Precalculated path loss matrices can only be used when optimising the antenna type and
azimuth. Optimising the mechanical tilt is not currently supported.
- Global Configuration: The Global Configuration is the configuration file set up by the administrator. This
configuration provides the same default settings to everyone on the network.
- User Configuration: Click the Browse button ( ) to select a user configuration file containing the settings
you want to be the default settings for the ACP module.
5. Click the User Preferences tab. On the User Preferences tab (see Figure 10.2), you can define settings that are
saved to the acp.ini configuration file found in the ACP installation folder. These settings will be applied every time
you run a new configuration.
- Show advanced optimisation settings: Select the Show advanced optimisation settings check box if you
want the ACP to display the Advanced tab when you define an optimisation setup. When the Advanced tab is
available, you can set a few additional options related to services, terminals, clutter, and propagation models.
- Calculation setting: Adjust the slider to define whether you want ACP to provide its results more quickly, at
the expense of precision, or whether you want ACP to provide more accurate results, at the expense of speed.
By selecting a higher speed, you will cause ACP to reduce the number of cells monitored for each pixel, some
of which might only create a bit of interference at first, but which could possibly create significantly more inter-
ference after antenna parameters are changed during the optimisation process. Selecting a higher precision
avoids this problem at the expense of more time and computer resources.
Under Result Preferences: You can define the following setting for report maps:
- Default map transparency: Define the default map transparency with the slider.
6. Click OK.
- Global Configuration: The Global Configuration indicates the configuration file set up by the administrator.
This configuration provides the same default settings to everyone on the network.
- User Configuration: Click the Browse button ( ) to select a user configuration file containing the settings
you want to be the default settings for the ACP module.
5. Click the Save Configuration File button under Saving Default Settings to save settings to a user configuration
file.
Note: The settings you save to a user configuration file are from an ACP optimisation from the
current Atoll document. If you have not yet used ACP for an optimisation in the current
document, the Save Configuration File button is not available.
When you click the Save Configuration File button, the Save Configuration File dialogue opens (see
Figure 10.3).
6. From the Save setting based on setup list, select the ACP setup on whose parameters you want to base the
user configuration file.
7. Click the Browse button ( ) next to To configuration file to select where you will save the user configuration
file.
8. Under Sections to save, select the check boxes of the types of parameters whose settings you want to save to
the user configuration file.
9. Click Save.
a. Under the Window menu, select the second document. The documents
Map window becomes active and the Explorer window shows the con-
tents of the selected document.
b. In the Explorer window, right-click the Sites folder. The context menu appears.
c. Select Make Available In from the context menu and select the name of the document in which you will run
the optimisation. The Sites folder is now available in the document in which you will run the optimisation.
d. Under the Window menu, select the second document. The documents
Map window becomes active and the Explorer window shows the con-
tents of the selected document.
e. In the Explorer window, right-click the Transmitters folder. The context menu appears.
f. Select Make Available In from the context menu and select the name of the document in which you will run
the optimisation. The Transmitters folder is now available in the document in which you will run the optimi-
sation
The transmitters and sites of the second document are now displayed in the document in which you will run the optimisa-
tion. The next step is to create a new co-planning optimisation setup.
4. After defining the optimisation setup, click the Create Setup button to save the defined optimisation.
The optimisation setup has now been created. The next step is to add the second radio technology to the ACP optimisation
setup you have just created.
ACP displays a dialogue enabling you to define which traffic will be used for the document you are importing.
button ( )
- Following traffic maps: Select Following traffic maps if you have traffic maps available and then select the
check boxes corresponding to the traffic maps you want to use.
6. Click OK. The setup has been modified to include the second technology.
You can modify the parameters for the optimisation setup by right-clicking it on the Data tab of the Explorer window and
selecting Properties from the context menu. For information on the parameters available, see "Defining Optimisation
Parameters" on page 568.
After defining the co-planning optimisation setup:
Click the Run button to run the optimisation immediately. For information on the optimisation results, see "Viewing
Optimisation Results" on page 588.
Click the Create Setup button to save the defined optimisation. For information on running the optimisation, see
"Running an Existing Optimisation Setup" on page 566.
- Order: You can change the order in which the layers will be optimised, by clicking the layers number in
the Order column and then clicking the Up button ( ) or the Down button ( ).
- Use: You can select which layers are to be optimised by selecting its check box in the Use column. The
layers whose check boxes are not selected in the Use column will not be optimised.
- Name: You can change the name of the layer by clicking it and entering a new name.
- Weight: You can change the weight assigned to the layer during the optimisation by clicking it and enter-
ing a new weight.
- Reconfiguration: If you want the layer to be taken into consideration for reconfiguration, you can select
the check box in the Reconfiguration column.
- Site Selection: If you want the layer to be taken into consideration for site selection, you can select the
check box in the Site Selection column.
The following columns give information about the layer; they can not be edited:
- Filtering Zones: Select the Computation Zone check box to optimise sites inside the computation zone
and the Focus Zone check box to optimise sites inside the focus zone.
- Hot Spots: For each new hot spot, enter a Name in the row marked with the New Row icon ( ) and
Important: The ACP does not take Atoll's hot spot zones into consideration. If you want to use the
hot spot zones defined in the Atoll document with ACP, you must first export them and
then import them in ACP as ArcView SHP files.
You can change the order in which the Hot Spots will be taken into consideration, by clicking the layers
number in the Order column and then clicking the Up button ( ) or the Down button ( ).
- No cost control: If you select No cost control, ACP will not take cost into consideration when optimising
the network.
- Maximum cost: If you select Maximum cost, you can enter a maximum cost not to be exceeded and
define the costs under Cost Setting.
- Quality/Cost trade-off: If you select Quality/Cost trade-off, you can enter a maximum cost not to be
exceeded and define the costs under Cost Setting.
- In the Reconfiguration Cost section, under Cost Setting, define the individual costs for each reconfigu-
ration option. If reconfiguring an option can only be done at the physical location of the transmitter, select
the check box in the Site Visit column. The cost will be increased by the defined Site Visit value.
- In the Site Selection Cost section, under Cost Setting, define the individual costs for each site selection
option.
3. Under Criteria, you can set the following objective-related objectives and parameters.
For UMTS:
a. Under Objective, click RSCP Coverage to define the RSCP coverage parameters.
- Computation zone: Select the check box in the Use column if you want ACP to calculate RSCP coverage
in the computation zone and define a Minimum threshold (dBm). Under Area Coverage, you can define
the percentage by which the current RSCP coverage should be improved (Improve current coverage
(+-)) or a target RSCP coverage (Target coverage (%)).
- Focus zone: Select the check box in the Use column if you want ACP to calculate RSCP coverage in the
focus zone and define a Minimum threshold (dBm). Under Area Coverage, you can define the percent-
age by which the current RSCP coverage should be improved (Improve current coverage (+-)) or a
target RSCP coverage (Target coverage (%)).
- Clutter: Select the check box in the Use column if you want to define a Minimum threshold (dBm) for
each clutter class.
b. Under Objective, click Parameters under RSCP Coverage to define how ACP will calculate RSCP coverage.
From the Base prediction settings on list, you can select the coverage prediction ACP will use to calculate
RSCP coverage, or you can select Manual Configuration and define the settings yourself.
Important: If you want to use a coverage prediction, the coverage prediction must have already been
calculated.
If you selected Manual Configuration from the Base prediction settings on list, define the following options:
- Select the Enable Shadowing Margin check box if you want to enable a shadowing margin and define a
Cell edge coverage probability.
When selected, the shadowing margin will be taken into account using the defined Cell edge coverage
probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is
available, default values are used. Macro diversity is also taken into account during RSCP calculation.
- Select the Enable Indoor Coverage check box if you want to enable indoor coverage. By default, all
pixels are considered as indoors when the Enable indoor coverage check box is selected. The indoor
loss per clutter class will be applied or, if no clutter classes are available, a default value will be applied.
You can adjust the indoor coverage losses by modifying the indoor losses per clutter class on the
Advanced tab. For more information on modifying the advanced parameters, see "Setting Advanced
Parameters" on page 585.
c. Under Objective, click EcIo Coverage to define the EcIo coverage parameters.
- Computation zone: Select the check box in the Use column if you want ACP to calculate EcIo coverage
in the computation zone and define a Minimum threshold (dBm). Under Area Coverage, you can define
the percentage by which the current EcIo coverage should be improved (Improve current coverage (+-))
or a target EcIo coverage (Target coverage (%)).
- Focus zone: Select the check box in the Use column if you want ACP to calculate EcIo coverage in the
focus zone and define a Minimum threshold (dBm). Under Area Coverage, you can define the percent-
age by which the current EcIo coverage should be improved (Improve current coverage (+-)) or a target
EcIo coverage (Target coverage (%)).
- Clutter: Select the check box in the Use column if you want to define a Minimum threshold (dBm) for
each clutter class.
d. Under Objective, click Parameters under EcIo Coverage to define how ACP will calculate EcIo coverage.
From the Base prediction settings on list, you can select the coverage prediction ACP will use to calculate
EcIo coverage, or you can select Manual Configuration and define the settings yourself.
Important: If you want to use a coverage prediction, the coverage prediction must have already been
calculated.
If you selected Manual Configuration from the Base prediction settings on list, define the following options:
- Select the Enable Shadowing Margin check box if you want to enable a shadowing margin and define a
Cell edge coverage probability.
When selected, the shadowing margin will be taken into account using the defined Cell edge coverage
probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is
available, default values are used. Macro diversity is also taken into account during EcIo calculation.
- Select the Enable Indoor Coverage check box if you want to enable indoor coverage. By default, all
pixels are considered as indoors when the Enable indoor coverage check box is selected. The indoor
loss per clutter class will be applied or, if no clutter classes are available, a default value will be applied.
You can adjust the indoor coverage losses by modifying the indoor losses per clutter class on the
Advanced tab. For more information on modifying the advanced parameters, see "Setting Advanced
Parameters" on page 585.
- Select a Service and a Terminal. The service and terminal specified are used during the calculation of
EcIo through gain and losses (i.e., the service body loss, the gain and loss of the terminal antenna, and
terminal noise factor).
e. Under Objective, the Network Quality is improved by reducing interference. You can define the importance
of reducing interference, and thereby of improving network quality, under Weighting.
4. Under Criteria, click Weighting to set the importance of the objectives (see Figure 10.8).
a. Under Objective Weighting, move the slider to set the relative importance of EcIo and RSCP coverage. You
can set meeting one objective as more important than meeting the other, or you can set meeting only the EcIo
or RSCP objective as necessary.
b. Under Perform interference minimization, move the slider to set the importance of reducing interference
and thereby improving network quality.
c. Under Zone weighting, define the weight given to the computation zone and the focus zone.
f. Under Objective, click BCCH Coverage to define the BCCH coverage parameters.
- Computation zone: Select the check box in the Use column if you want ACP to calculate BCCH coverage
in the computation zone and define a Minimum threshold (dBm). Under Area Coverage, you can define
the percentage by which the current BCCH coverage should be improved (Improve current coverage
(+-)) or a target BCCH coverage (Target coverage (%)).
- Focus zone: Select the check box in the Use column if you want ACP to calculate BCCH coverage in the
focus zone and define a Minimum threshold (dBm). Under Area Coverage, you can define the percent-
age by which the current BCCH coverage should be improved (Improve current coverage (+/)) or a
target RSCP coverage (Target coverage (%)).
- Clutter: Select the check box in the Use column if you want to define a Minimum threshold (dBm) for
each clutter class.
g. Under Objective, click Parameters under RSCP Coverage to define how ACP will calculate BCCH coverage.
From the Base prediction settings on list, you can select the coverage prediction ACP will use to calculate
BCCH coverage, or you can select Manual Configuration and define the settings yourself.
Important: If you want to use a coverage prediction, the coverage prediction must have already been
calculated.
If you selected Manual Configuration from the Base prediction settings on list, define the following options:
- Select the Enable Shadowing Margin check box if you want to enable a shadowing margin and define a
Cell edge coverage probability.
When selected, the shadowing margin will be taken into account using the defined Cell edge coverage
probability. The standard deviations defined in the Atoll clutter are used or, if no clutter information is
available, default values are used.
- Select the Enable Indoor Coverage check box if you want to enable indoor coverage. By default, all
pixels are considered as indoors when the Enable indoor coverage check box is selected. The indoor
loss per clutter class will be applied or, if no clutter classes are available, a default value will be applied.
You can adjust the indoor coverage losses by modifying the indoor losses per clutter class on the
Advanced tab. For more information on modifying the advanced parameters, see "Setting Advanced
Parameters" on page 585.
h. Under Objective, click Cell Dominance to define the cell dominance parameters.
- Enter the Number of allowed servers and the Overlap margin.
i. If you want to define the coverage to be respected while meeting this BCCH objective, select the check box
at the bottom of the tab (see Figure 10.9) and select one of the following options:
- Minimum area coverage: Select Minimum area coverage and define the minimum coverage as a per-
centage.
- Keep current coverage within: Select Keep current coverage within and define the range to be
respected.
For UMTS:
3. Under Traffic Generated From, select one of the following methods for defining non-uniform traffic:
- Maps based on traffic densities: If you select Maps based on traffic densities, you can define the traffic
weighting and traffic profiles.
- Under Traffic Parameters, select if you want traffic weighting to be applied to the optimisation of EcIo or
RSCP coverage or both.
- Under Traffic Profiles, for each traffic profile, define a Traffic Name, a Terminal, and select a Traffic
4. If you want to view the traffic profiles without running the optimisation setup, click Create Setup. ACP will then
create the traffic profiles based on the traffic maps selected and the traffic parameters defined.
For GSM:
5. Under Traffic Generated From, select one of the following methods for defining non-uniform traffic:
- Maps based on traffic densities: If you select Maps based on traffic densities, you can define the traffic
weighting and traffic profiles.
- Under Traffic Parameters, select if you want traffic weighting to be applied to the optimisation of Cell
Dominance or BCCH coverage or both.
- Under Traffic Profiles, for each traffic profile, define a Traffic Name, a Terminal, and select a Traffic
than the resolution of the traffic maps. To increase the accuracy of the data-extraction process, you can
enter a higher resolution.
- Under Traffic Parameters, select if you want traffic weighting to be applied to the optimisation of Cell
Dominance or BCCH coverage or both.
- Under Traffic Profiles, the traffic profiles will be displayed after ACP has extracted them from the selected
traffic maps.
When using traffic maps, Network Quality is always optimised using traffic weighting.
6. If you want to view the traffic profiles without running the optimisation setup, click Create Setup. ACP will then
create the traffic profiles based on the traffic maps selected and the traffic parameters defined.
3. Select the Pilot power check box for the pilot power of each selected cell to be set within a defined minimum and
maximum value and in the defined number of steps.
4. Define the pilot power settings for each cell.
- Use: Select the Use check box corresponding to the cell to include it in the optimisation of the pilot power.
- Current: The current pilot power for the cell.
- Min. and Max.: Set a minimum and maximum pilot power to be respected during the optimisation process.
- Step (dB): Set a Step in dB that ACP should use with attempting to find the optimal pilot power.
Note: For pilot power optimisation, the pilot range defined with minimum, maximum and step
values. Note that there is an absolute maximum possible pilot power which depends on
the other powers used in the cell (for control, traffic, and max cell power).
You can make the same changes to several cells by making the change for one item, selecting the others starting
from the changed item and using the Fill Up (CTRL+U) or Fill Down (CTRL+D) commands. For more information
on the Fill Up or Fill Down commands, see "Pasting the Same Data into Several Cells" on page 56.
You can select the cells to which the reconfiguration options are going to be applied using the Advanced section
of the Site Selection tab. For more information, see "Selecting Sites for Reconfiguration" on page 582.
You can sort the contents of any column by right-clicking the column and selecting Sort Ascending or Sort
Descending from the context menu.
Caution: Cells that have been filtered out, either by zone or by clearing their check box in the table,
will not be optimised but are still present in the network and, therefore, continue to
generate interference.
Atoll enables you to export the current network reconfiguration options, edit them in a different application and then reim-
port them into the Reconfiguration tab. For information on importing network reconfiguration options, see "Importing
Network Reconfiguration Parameters" on page 579.
Note: If you want ACP to display more information on each transmitter, you can select the Show
Advanced Grid check box. ACP will then display, for each transmitter, the propagation
model used, the transmitter, height, and the name and status of the site the transmitter is
located on. The propagation model displayed is extracted from the Atoll document but
can be changed if the propagation model is not recognised by ACP (for more information,
see "Propagation Models and ACP" on page 562).
You can select the cells to which the reconfiguration options are going to be applied using the Advanced section
of the Site Selection tab. For more information, see "Selecting Sites for Reconfiguration" on page 582.
You can sort the contents of any column by right-clicking the column and selecting Sort Ascending or Sort
Descending from the context menu.
Caution: Cells that have been filtered out, either by zone or by clearing their check box in the table,
will not be optimised but are still present in the network and, therefore, continue to
generate interference.
If the Antenna type check box is selected under Optimise Control, the Antenna Type column is displayed in the
table with the following values and options:
- Use: Select the Use check box corresponding to the cell to include it in the optimisation of the antenna type.
- Group: Assign an antenna group to the cell. During the optimisation procedure, ACP will select the best
antenna assigned to that antenna group. The "Default" antenna group is a group containing all antennas in
that Atoll document. You can define antenna groups using the Antenna Groups tab. For information on the
Antenna Groups tab, see "Defining Antenna Groups" on page 583.
Tip: If you click the Auto-Allocate Antenna Group button, ACP will allocate to each cell the
smallest group containing the currently assigned transmitter.
If the Electrical Tilt check box is selected, the Electrical Tilt (deg) column is displayed in the table with the follow-
ing values and options:
- Use: Select the Use check box corresponding to the cell to include it in the optimisation of the antenna azi-
muth.
- Current: The currently defined antenna azimuth.
- Min.: Enter the minimum electrical tilt.
- Max.: Enter the maximum electrical tilt.
If the Azimuth check box is selected, the Azimuth (deg) column is displayed in the table with the following values
and options:
- Use: Select the Use check box corresponding to the cell to include it in the optimisation of the antenna azi-
muth.
- Current: The currently defined antenna azimuth.
- Variation: Enter range in degrees. ACP will search within this range on either side of the currently defined
azimuth.
- Step (): Enter the number of steps to be tested within the defined range. For example, if the current azimuth
is 120, with the Variation set to "10" and the number of Steps set to "6", the azimuth will be tested in the
range from 110 to 130, with the following values: 110, 114, 118, 122, 126, 130.
- Min. Inter Sector (): Enter minimum difference in degrees between sectors (UMTS only)
If the Mechanical Tilt check box is selected, the Mechanical Tilt (deg) column is displayed in the table with the
following values and options:
- Use: Select the Use check box corresponding to the cell to include it in the optimisation of the mechanical tilt.
- Current: The currently defined antenna azimuth.
- Min. and Max.: Set a minimum and maximum mechanical tilt to be respected during the optimisation process.
- Step (): Set a Step in degrees that ACP should use with attempting to find the optimal mechanical tilt.
In the Propagation Model column, the propagation model for each cell is displayed. The propagation model
displayed is extracted from the Atoll document but can be changed if the propagation model is not recognised by
ACP (for more information, see "Propagation Models and ACP" on page 562).
In the Cell Power column, the current cell power settings are indicated for information.
Atoll enables you to export the current network reconfiguration options, edit them in a different application and then reim-
port them into the Reconfiguration tab. For information on importing network reconfiguration options, see "Importing
Network Reconfiguration Parameters" on page 579.
When you are reconfiguring transmitters in multi-layer environments, you can link transmitters in the same location but in
different layers to ensure that ACP applies the same reconfiguration to them.
To use link transmitters:
1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 566.
2. Click the Reconfiguration tab and, on the left-hand side of the Reconfiguration tab, click the Transmitters tab.
3. Click Advanced at the bottom of the Reconfiguration tab. The Advanced options appear.
4. Under Advanced, click the Multi-layer Management tab. On the Multi-layer Management tab, you can link trans-
mitters (see Figure 10.13).
5. Link transmitters:
To link transmitters in the same location but on different layers:
a. Hold CTRL and click the first transmitter in the table above and then the second transmitter. The Link button
on the Multi-layer Management tab is now available.
b. Click the Link button. The two transmitters are now linked and ACP will apply the same reconfiguration to them
both.
To unlink linked transmitters:
a. Select the transmitters in the table The Unlink button on the Multi-layer Management tab is now available.
b. Click the Unlink button. The transmitters are no longer linked.
To unlink all linked transmitters:
- Click the Unlink All button. ACP resets all linked transmitters.
To automatically all transmitters in the same location but on different layers:
- Click the Auto Link button. ACP links all transmitters that have the same position, azimuth and mechanical tilt.
When the propagation model used is not one natively supported by ACP, for complex ray-tracing propagation models, ACP
can use precalculated path loss matrices to calculate attenuation. When you use precalculated path loss matrices, ACP
does not need information about the internal workings of the propagation model, it works by recalculating all the path loss
matrices for all possible parameter combinations to be tested.
To use precalculated path loss matrices to calculate path loss attenuation:
1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 566.
2. Click the Reconfiguration tab (see Figure 10.12).
3. Click Advanced at the bottom of the Reconfiguration tab. The Advanced options appear.
4. Under Advanced, click the Antenna Masking Method tab.
5. Select the Use precalculated path loss matrices check box.
6. If necessary, enter a storage path for the path loss matrices under ACP path loss matrix storage or click the
Important: When you use precalculated path loss matrices, they must be stored externally. For
information on storing path loss matrices externally, see "Setting the Storage Location of
Path Loss Matrices" on page 188.
7. In the table on the Reconfiguration tab, select the check box in the Precalculated Path Loss Matrices column
for each entry in the Tx Name column that uses a propagation model that is not natively supported by ACP (see
Figure 10.14).
Atoll enables you to export the current network reconfiguration options, edit them in a different application and then reim-
port them into the Reconfiguration tab.
To import reconfiguration parameters:
1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 566.
2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the desired tab.
3. Right-click the table and select Export as Text from the context menu. The Save As dialogue appears.
4. Enter a name in the File name box and click Save. The file will be saved as a tab-delimited text file.
5. Open the text file in another application, for example, in a spreadsheet application, and make the modifications
desired.
6. Save the file as a text file and return to Atoll.
7. Click Advanced at the bottom of the Reconfiguration tab. The Advanced options appear.
8. Under Advanced, click the Import Facility tab.
9. Click the Import from File button. The Open dialogue appears.
10. Browse to the file and click Open. The Import Data dialogue appears (see Figure 10.15).
11. Under Format Parameters, enter the number of the first row with data in the First Imported Row box, select the
data Separator, and select the Decimal Symbol used in the file.
12. If you want only the cells in the imported list to be used on the Reconfiguration tab, select the Use Only Cells in
List check box. The Use check box will be cleared for all cells that are not in the imported file and they will not be
affected by reconfiguration options.
13. In the table, ensure that the column names from the imported file (the Source file) match the column names on
the Reconfiguration tab (Destination). You can change the Destination column by clicking the column name and
selecting the name from the list.
Note: Any values in the imported file for current values can not be imported.
14. Click the Import button to import the file and replace the settings in the Reconfiguration tab.
You can use the Reconfiguration tab to select the sites that will be added or removed to improve existing or new networks.
To set site selection parameters:
1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 566.
2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab (see
Figure 10.16).
3. Select the Site Selection check box to enable site selection. You can then define how sites will be added or
removed.
4. In the table, define how each site will be treated during site selection:
a. Select the Locked check box for each site that is not to be affected by site selection.
Tip: If you have many sites that you do not want to be affected by site selection, you can
select and lock them with the Advanced section. For more information on the options in
the Advanced section, see "Selecting Sites for Reconfiguration" on page 582.
Important: Only active sites are loaded by ACP. If you want inactive sites to be taken into account
during site selection, you must set them as active first in Atoll. When you commit the
results of the ACP run, all sites and sectors disabled by the ACP will be set to inactive in
Atoll.
- Existing: An "Existing" site is considered as being active in the initial network. ACP will remove an existing
site if the Site Removable check box has been checked and if removing the site will improve network qual-
ity. If the Sectors Removable check box has been checked, one or more sectors might be removed if
removing them will improve network quality.
- Candidate: A "Candidate" site is considered as being inactive in the initial network. ACP will add the site
during the optimisation process if adding the site will improve network quality. If the Sectors Removable
check box has been checked, only one or more sectors might be added if adding them will improve
network quality.
c. Select the Sectors Removable check box for each site that can have sectors removed to improve network
quality.
d. Select the Site Removable check box for each site that can be removed to improve network quality.
e. If desired, assign a candidate site to a Group by selecting it from the list. If a candidate site does not belong
to a group, no further constraints are imposed on ACP during optimisation. If a candidate site belongs to a
group, ACP must respect the constraints of the group.
Notes:
You can use ACP to select the antenna height using site groups by creating in Atoll several
similar sites with different antenna heights but at same location. If you place them in one group
where the minimum and maximum occurrence is set to "1," ACP will be forced to select only
one of the alternatives.
If a site group has no sites belonging to it, it is automatically deleted.
To create a group:
i. Under Group, click the field and select New from the list. The New Site Group dialogue appears (see
Figure 10.17).
ii. Enter a Group Name and define the minimum and maximum number of sites (from this group that must
be respected by ACP during optimisation (Minimum Site Occurrence and Maximum Site Occurrence,
respectively). If there is no minimum or maximum that ACP must respect, leave the field blank.
iii. Click OK to create the group and return to the Site Selection tab.
Note: You can change the values for Minimum Site Occurrence and Maximum Site
Occurrence, as well as change a group name, under Group Management, found on the
Global Change tab of the Advanced section. After you have displayed Group
Management by clicking Advanced, you can select the group name from the list and
then add new values for the Name, or Min or Max site occurrence values. Clicking the
Apply button will update the group with the modifications.
You can use the Reconfiguration tab to select the sites to which some or all of the reconfiguration options selected on the
Reconfiguration tab will be applied. For more information on the Reconfiguration tab, see "Setting Network Reconfiguration
Parameters" on page 575.
To select sites for reconfiguration:
1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 566.
2. Click the Reconfiguration tab. On the left-hand side of the Reconfiguration tab, select the Sites tab.
3. Select the Site Selection check box.
4. Click Advanced to display the Advanced area (see Figure 10.18).
6. Select the sites you want to apply the reconfiguration options to:
- For entire table: Select For entire table if you want any reconfiguration options to be applied to all sites in
the table.
- With status: Select With status and then select the status from the list if you want any reconfiguration options
to be applied to all sites with that status.
- With technology: Select With technology and then select the technology from the list if you want any recon-
figuration options to be applied to all sites using that technology.
- For selected rows: If you want the selected reconfiguration options to a series of rows in the table, select the
rows and then select For selected rows under Advanced. You can select contiguous rows by clicking the
first field, pressing SHIFT and clicking the last field. You can select non-contiguous rows by pressing CTRL
and clicking each field separately.
Note: If you want to lock the selected sites, you can select the Set "Locked" check box and
click Apply. The locked sites will not be affected by the site addition or removal options.
3. Click the New button to create a new group under Physical Antenna. You can change the name of the new group
or of any group by clicking the group name twice under Physical Antenna and entering the new name.
You can delete one group by selecting it under Physical Antenna and clicking the Delete button. You can delete
all groups by clicking the Clear All Groups button.
b. Select the antenna under Antenna Pattern Table and click the right arrow between the columns ( ) to as-
sign it to the selected group. Antennas under Antenna Pattern Table that have been assigned to a group are
indicated with an icon ( ).
You can assign the same antenna to more than one group.
You can remove an antenna from a group by selecting it in the group under Physical Antenna and clicking
the left arrow between the columns ( ).
Note: When you have created the antenna groups, you can back up the configuration by
clicking the Backup Configuration button. In future ACP sessions, the antenna groups
are then automatically created according to this definition.
You can create antenna groups automatically using a regular expression, or "regex." The regular expression is retained
from one Atoll session to the next. Therefore, once you have set the regular expression for the given antenna naming
convention, you will not have to set again for the next Atoll session. The default regex pattern is overwritten when you
change it. You can return to the default regular expression by clearing the text box and clicking OK. You can change the
default regular expression by editing the appropriate entry in the ACP.ini file.
Important: It is recommended to identify both the antenna type and the electrical tilt in the antenna
name in Atoll and to separate the antenna type and electrical tilt with a special character,
for example, "_". This will make it easier to create antenna groups automatically using a
regular expression.
Tip: Clicking the tooltip button ( ) displays a tooltip with an explanation of common regular
expressions.
4. Click the Build from expression button to create antenna groups according to the defined regular expression.
Note: When you have created the antenna groups, you can back up the configuration by
clicking the Backup Configuration button. In future ACP sessions, the antenna groups
are then automatically created according to this definition.
When you have grouped antennas according to their physical characteristics as explained in "Creating Antenna Groups
Individually" on page 583 and "Creating Antenna Groups Automatically" on page 584, they are displayed on the Radome
tab of the Antenna tab, grouped according to their frequency band.
You can merge these groups to create groups of antennas that are multi-band antennas.
To define multi-band antennas:
1. Open the dialogue used to define the optimisation as explained in "Creating an Optimisation Setup" on page 566.
2. Click the Antenna tab. On the left-hand side of the Antenna tab, select the Radome tab (see Figure 10.19 on
page 583).
4. Under Antenna Masking Method, you can set parameters. The parameters available depend on the propagation
model.
- Use clutter height: You can select the Use clutter height check box if you want ACP to take clutter height
information from the clutter heights file, if available, or from the clutter classes file.
- Receiver on top of clutter: You can select the Receiver on top of clutter check box. The receiver height
will then be sum of the clutter height and the receiver height. This option can be used, for example, to model
receivers on top of buildings.
- Use radial method: You can select the Use radial method check box if you want ACP to use the radial
method to extract the profile between the transmitter and the receiver.
5. In the left column, click the Expand button ( ) to expand the Parameters folder.
6. In the Parameters folder, select Services. In the Services section, the service-related parameters of the Atoll
document are displayed. In a GSM/UMTS co-planning document, there will be a Services folder for each tech-
nology.
7. Under Services, define the body loss for each of the services defined in the Atoll document.
8. In the Parameters folder, select Terminals. In the Terminals section, the terminal-related parameters of the Atoll
document are displayed. In a GSM/UMTS co-planning document, there will be a Terminals folder for each tech-
nology.
For UMTS:
9. Under UMTS Terminals, define the Antenna Gain, the Loss, and the Noise Factor for each terminal.
For GMS:
10. Under GSM Terminals, define the Noise Factor for each terminal.
11. In the Parameters folder, select Clutter Classes. In the Clutter Classes section, the clutter-related parameters
of the Atoll document that affect optimisation are displayed. In a GSM/UMTS co-planning document, there will be
a Clutter Classes folder for each technology.
For UMTS:
12. Under UMTS Clutter Classes, you can set the following parameters for each clutter class:
- Height: You can set the Height for each clutter class.
- Indoor Loss (dB): You can set the Indoor Loss (dB) for each clutter class. The indoor loss is used to calcu-
late shadowing losses on the path loss, as related to the cell edge coverage probability.
- % Pilot Finger: You can set the % Pilot Finger for each clutter class. The percentage of the pilot finger is
used in the Ec/Io calculations.
- Model Standard Deviation (dB): You can set the Model Standard Deviation (dB) for each clutter class. The
model standard deviation is used to calculate shadowing losses on the path loss, as related to the cell edge
coverage probability.
- Ec/Io Standard Deviation (dB): You can set the Ec/Io Standard Deviation (dB) for each clutter class. The
EcIo standard deviation is used to calculate shadowing losses on the EcIo values, as related to the cell edge
coverage probability.
- Is Indoor: You can define the clutter class as being inside by selecting the Is Indoor check box.
Note: You can set default values for all clutter classes for each of these parameters except for
height.
For GMS:
13. Under GSM Clutter Classes, you can set the following parameters for each clutter class:
- Height: You can set the Height for each clutter class.
- Indoor Loss (dB): You can set the Indoor Loss (dB) for each clutter class. The indoor loss is used to calcu-
late shadowing losses on the path loss, as related to the cell edge coverage probability.
- % Pilot Finger: You can set the % Pilot Finger for each clutter class. The percentage of the pilot finger is
used in the Ec/Io calculations.
- Model Standard Deviation (dB): You can set the Model Standard Deviation (dB) for each clutter class. The
model standard deviation is used to calculate shadowing losses on the path loss, as related to the cell edge
coverage probability.
- C/I Standard Deviation (dB): You can set the Ec/Io Standard Deviation (dB) for each clutter class. The CI
standard deviation is used to calculate shadowing losses on the C/I values, as related to the cell edge cov-
erage probability.
- Transmission Diversity Gain: You can set the Transmission Diversity Gain for each clutter class.
- Is Indoor: You can define the clutter class as being inside by selecting the Is Indoor check box.
Note: You can set default values for all clutter classes for each of these parameters except for
height.
4. Select Run from the context menu. The optimisation setup runs.
As the optimisation setup runs, ACP displays the current status of the process (see Figure 10.21) allowing you to observe
the progress. You can pause the optimisation if you desire or stop the optimisation early,
The Optimisation dialogue has two tabs:
Graphs: The Graphs tab displays a graph with the iterations on the X axis and the optimisation objectives (RSCP,
EcIo, and network quality) on the Y axis (see Figure 10.21). The values displayed are indicated with a legend.
Quality Maps: The Quality Maps tab displays coverage quality maps for RSCP (Ec) and EcIo improvement. The
maps display the computation zone with the network improvement performed to that point.
When the optimisation has finished, the results are stored in the optimisation folder on the Data tab of the Explorer
window. By default, Atoll calls the optimisation folder a "Setup" folder. Each setup folder contains one or more optimisation
processes. Each optimisation process folder contains the results of that optimisation. For information on viewing optimi-
sation results, see "Viewing Optimisation Results" on page 588.
Note: You can perform an optimisation on a network that has already been optimised. After
running the first optimisation and committing the results, you can create and run a second
optimisation, with different parameters on the optimised network.
Caution: If you have changed some data in Atoll, for example, if you added transmitters or change
some of the transmitter settings, the data that optimisation results are based on may
differ from the current Atoll data. If you run a optimisation based on settings made before
the changes, it will not take the changed data into consideration.
ACP normally detects changes in the Atoll document data and can lock a group if it is
impossible to run an optimisation that is coherent with existing data. ACP can lock a
group if, for example, when you commit optimisation results after the path losses have
been recalculated and are no longer consistent with the data used to run the optimisation.
When this happens you will either have to:
- Create a new optimisation as explained in "Creating a New Optimisation Setup" on
page 566.
- Duplicate an existing optimisation which will create a new optimisation with the same
configuration but with updated parameters.
- Roll back the previously committed parameters as explained in "The Commit Tab" on
page 595.
- Delete: Selecting Delete deletes the defined optimisation setup and any results.
Storing optimisation results and the group configuration increase the size of the Atoll file. Deleting unused
setups in the ACP - Automatic Cell Planning folder will decrease the size of the Atoll file.
- Load Configuration: Selecting Load Configuration displays the Open dialogue. You can then select a PRJ
file based on the settings of a different optimisation. When you load a configuration based on a different Atoll
document, only the settings that are not specific to that document are loaded.
- Save Configuration: Selecting Save Configuration displays the Save As dialogue. You can then save the
optimisation settings in a PRJ file. You can then use this PRJ file to quickly configure an optimisation.
Tip: Saving a configuration is a quick way to save the settings you have made in an external
file. you can then easily create new configurations using these same settings as a basis
without having to recreate them.
- Statistics: The Statistics tab displays a synthesized view of the optimisation results of the quality figures
(RSCP quality, EcIo quality, and network quality for UMTS and BCCH and cell dominance for GSM). For more
information on the Statistics tab, see "The Statistics Tab" on page 589.
- Sectors: The Sectors tab displays a table with the reconfigured cells in green, sites and sectors which have
been added or removed, and the RSCP and EcIo coverage quality (UMTS) and BCCH and cell dominance
(GSM) per cell before and after optimisation. For more information on the Statistics tab, see "The Sectors Tab"
on page 590.
- Graph: The Graph tab displays a graph with the iterations on the X axis and the optimisation objectives (RSCP
quality, EcIo quality, and network quality for UMTS and BCCH and cell dominance for GSM) on the Y axis.
The values displayed are indicated with a legend. For more information on the Graph tab, see "The Graph
Tab" on page 592.
- Quality: The Quality tab displays the computation zone with coverage quality maps for RSCP (Ec) and EcIo
(UMTS) and BCCH (GSM) before and after optimisation. For more information on the Quality tab, see "The
Quality Tab" on page 593.
- Change Details: The Change Details tab enables you to analyse the improvement caused by each reconfig-
uration option. For more information on the Change Details tab, see "The Change Details Tab" on page 593.
- Commit: The Commit tab enables you to commit the set of selected changes. For more information on the
Commit tab, see "The Commit Tab" on page 595.
For the RSCP and EcIo coverage quality (for UMTS) and BCCH and cell dominance (for GSM), both the initial and final
figures are given, as well as the absolute improvement. These figures are given both for the computation zone and the
focus zone.
For the network quality (for UMTS), the relative improvement is given. This improvement measures the overall decrease
of interference in the network, which can be loosely equated to the overall capacity increase in the network.
You can see more detailed information by clicking the links (see Figure 10.25):
Show Change Statistics: The change statistics showing the reconfiguration and site selection statistics.
Show Detailed HotSpot/Clutter Results: The detailed quality figures on each hotspot and by each clutter class.
Show Input: The input settings of this optimisation.
You can export the results by clicking the Export button. The Save As dialogue that appears allows you to select the
format in which you want to save the results.
The cell results are displayed in a table. You can access options such as sorting, exporting data using the context menu
(see Figure 10.27) sort, column hiding, export, etc.
Figure 10.29: The Graph tab with the values displayed on the selected point
The maps are displayed with a range of values displayed on the right. This range can be modified using a dialogue
accessed through the tool bar (see Figure 10.31).
In addition of the map, a histogram is provided for quick evaluation of improvement seen across the entire range of values.
This histogram displays the statistics within the focus zone if selected. It should be also noted that the statistics are given
using traffic weighting when traffic maps are used. They can therefore be different from similar statistics obtained through
the Generate Report tool in Atoll which only uses uniform weighting.
Note: The default colour range used for display can be changed using the ACP.INI preference
configuration file.
You can select a subset of all changes using a slider and view the corresponding performance improvement on the graph.
This can enable you to achieve two goals:
To select a subset of changes to be implemented. For example, you might find that implementing only one-third
of the recommended changes will provide 80% of the benefit. You could then chose to commit only those changes
to the Atoll document.
To find the optimal order in which to apply these changes in the field, while at the same time avoiding less than
optimal performance, or even degrading the performance, during the implementation phase.
Before selecting a subset of recommended changes, it is important to understand that ACP calculates the set of recom-
mendations globally and that these changes are interdependent. During the finalisation step, ACP calculates the ordered
list of changes displayed on the Change Details tab by starting from the initial network configuration and iteratively select-
ing the change that will have the most effect on the network. If you select a subset of the recommended changes, it is
highly likely that the improvement of the network quality will not be as great as projected. It is therefore highly recom-
mended to follow the proposed configuration.
Important: The data displayed on the other tabs takes all the proposed changes into consideration. If
you select only a subset of the proposed changes on the Change Details tab, the
statistics displayed on other tabs do not change.
When you commit the optimisation changes, ACP will only commit the proposed changes selected on the Change Details
tab. For information on committing the optimisation changes, see "The Commit Tab" on page 595.
When you commit the optimisation results, all existing configuration setups are locked because the network state on which
the configuration setup was based is not coherent with the current path losses. ACP automatically detects any incoherence
and prevents you from running an optimisation on incoherent data. ACP will unlock the optimisation setups when it
becomes possible, for example, when you roll back the data to restore the Atoll state to be coherent with the network state
on which the configuration setup was based.
It is important to remember that you can commit or roll back other optimisation results even when the setup is locked.
The maps available in the ACP Map Types dialogue are organised by category.
6. Select the category of maps or click the Expand button ( ) to expand the category and then select the sub-cat-
egory or map.
7. Click OK to create the maps. The maps are created and inserted into the folder of the setup containing the opti-
misation results (see Figure 10.35).
You can display a map by selecting its check box in the folder of the setup containing the optimisation results. The display
properties can be changed for a single map or for all maps. For information on the display properties for ACP maps, see
"Changing the Display Properties of ACP Maps" on page 600.
The following sections provide more information on the maps:
"The Quality Analysis Maps" on page 596
"The Coverage Analysis Maps" on page 597
"The Change Analysis Maps" on page 598
"Best Server Analysis" on page 599
"Comparing Maps" on page 599.
any decision to commit the optimisation results on the maps produced by ACP, you should keep the following recommen-
dations in mind:
You should verify the results with a different Atoll coverage prediction, such as the pilot pollution prediction.
ACP generated maps are generated using the entire set of proposed changes. They do not take into account the
change subset defined on the Change Details tab.
Multi-carrier is not supported by ACP; the maps are only provided for the requested carrier.
Even after committing the optimisation results, differences can remain between the ACP maps and the maps
resulting from Atoll coverage predictions.
You can view the exact RSCP and EcIo values on any pixel by letting the pointer rest over the pixel. The RSCP or EcIo
value is then displayed in a tooltip.
For the overlapping zones map, you can set the best server threshold on the User Preferences tab of the ACP Properties
dialogue (see "Configuring the Default Settings" on page 564) or by setting the CellOverlap parameter in the acp.ini file.
Figure 10.36: Examples of an overlapping zones map (left) and an EcIo variation map (right)
For each network quality study, ACP offers a map showing the initial network state, the final network state, and a map
showing the changes between the initial and final state.
Figure 10.37: Example of final cell coverage (left) and EcIo coverage improvement (right)
You can define how the coverage analysis maps will be displayed.
3. Select the Display tab. On the Display tab, you can select the colour used to display RSCP coverage, EcIo cov-
erage, and both. As well, you can use the slider to adjust the Transparency.
4. Select the Thresholds tab. On the Thresholds tab, you can set the thresholds to be used for the map. For both
RSCP and EcIo, you can use the same thresholds as you used when you calculated the optimisation, or you can
set a different threshold.
Note: The electrical tilt values are calculated using the vertical antenna pattern. The Change of
Electrical Tilt map is made available even when the change was to the antenna type.
Figure 10.39: Example of antenna type change (left) and electrical tilt change (right)
To a map compare with a map from a different map type or from a different optimisation:
1. After creating and inserting the coverage analysis maps into the folder of the setup containing the optimisation
results as explained in "Viewing Optimisation Results in the Map Window" on page 595, right-click the map you
want to compare. The context menu appears.
2. From the context menu, select Compare With > Others. The ACP Compare Map dialogue appears (see
Figure 10.41). By default, the ACP Compare Map dialogue displays only maps from the same optimisation as the
map you want to compare.
ACP provides a legend that displays the range of values of the optimisation map currently displayed in the map window.
The legend window is shared among all the ACP maps.
To display the ACP legend:
1. On the Data tab of the Explorer window, right-click the optimisation that contains the map for which you want to
display the legend. The context menu appears.
2. Select Shared Legend from the context menu. The ACP Legend window appears.
3. Click the map displayed in the map window. The legend of the map appears in the ACP Legend window.
If you display a different map in the map window, the contents of the ACP Legend window will not change until
you click the map. If you have more than one map displayed, remember that Atoll displays objects in the order
they appear in the Explorer window. Therefore, you will either have to move the second map above the first one
in the Explorer window or deselect the check box next to it, so that only the map you want displayed is visible.
Atoll
RF Planning and Optimisation Software
Chapter 11: CDMA2000 Networks
11 CDMA2000 Networks
Atoll enables you to create and modify all aspects of CDMA2000 1xRTT (1st eXpansion Radio Telephone Technology)
and CDMA2000 1xEV-DO (1xEvolution Data Only) Rev.0 and Rev.A networks. Once you have created the network, Atoll
offers many tools to let you verify the network. Based on the results of your tests, you can modify any of the parameters
defining the network.
Planning the CDMA network and creating the network of base stations is explained in "Planning and Optimising CDMA
Base Stations" on page 605. Allocating neighbours is explained in "Planning Neighbours" on page 663 and allocating PN
offset codes is explained in "Planning PN Offsets" on page 673. In this section, you will also find information on how you
can display information on base stations on the map and how you can use the tools in Atoll to study base stations.
In "Studying Network Capacity" on page 680, using traffic maps to study network capacity is explained. Creating simula-
tions using the traffic map information and analysing the results of simulations is also explained.
Using test mobile data paths to verify the network is explained in "Verifying and Optimising Network Quality" on page 706.
How to filter imported pilot mobile data paths, and how to use the data in coverage predictions is also explained.
The terminology used in CDMA is slightly different from the standard terminology used in Atoll. Therefore, the terminology
used in explanations reflects the standard CDMA terminology with the equivalent Atoll terminology given when references
are made to the user interface.
CDMA Atoll
handoff handover
Antenna
- Azimuth
- Mechanical tilt
TMA
Antenna
- Height
Feeder Cable
BTS
- BTS noise figure
- Power
Site
- X, Y coordinates
Atoll lets you create one site, transmitter, or cell at a time, or create several at once by creating a station template. Using
a station template, you can create one or more base stations at the same time. In Atoll, a base station refers to a site with
its transmitters, antennas, equipment, and cells.
Atoll allows you to make a variety of coverage predictions, such as signal level or transmitter coverage predictions. The
results of calculated coverage predictions can be displayed on the map, compared, or analysed.
Atoll enables you to model network traffic by allowing you to create services, users, user profiles, environments, and termi-
nals. This data can be then used to make quality studies, such as effective service area, noise, or handoff status predic-
tions, on the network.
In this section, the following are explained:
"Creating a CDMA Base Station" on page 606
"Creating a Group of Base Stations" on page 618
"Modifying Sites and Transmitters Directly on the Map" on page 619
"Display Tips for Base Stations" on page 619
"Creating a Repeater" on page 619
"Creating a Remote Antenna" on page 622
"Setting the Working Area of an Atoll Document" on page 624
"Studying a Single Base Station" on page 625
"Studying Base Stations" on page 628
"Planning Neighbours" on page 663
"Planning PN Offsets" on page 673.
- Name: Atoll automatically enters a default name for each new site. You can modify the default name here. If
you want to change the default name that Atoll gives to new sites, see the Administrator Manual.
- Position: By default, Atoll places the new site at the centre of the map window. You can modify the location
of the site here.
Tip: While this method allows you to place a site with precision, you can also place sites using
the mouse and then position them precisely with this dialogue afterwards. For information
on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 31.
- Altitude: The altitude, as defined by the DTM for the location specified under Position, is given here. You can
specify the actual altitude under Real, if you wish. If an altitude is specified here, Atoll will use this value for
calculations.
- Comments: You can enter comments in this field if you wish.
The Equipment tab:
- Max Number of Uplink Channel Elements per Carrier: The maximum number of physical radio resources
on the reverse link per carrier for the current site. By default Atoll enters the maximum possible (256).
- Max Number of Downlink Channel Elements per Carrier: The maximum number of physical radio
resources on the forward link per carrier for the current site. By default Atoll enters the maximum possible
(256).
- Max Number of EV-DO Channel Elements per Carrier: The maximum number of EV-DO radio resources
on the reverse link per carrier for the current site. This parameter is used only with CDMA2000 1xEV-DO. By
default Atoll enters the maximum possible (96).
With 1xEV-DO, only one user on the forward link can be served at a given time. This user consumes only one
channel element. On the reverse link, there can be more than one user with each user consuming one channel
element, therefore, the maximum number of EV-DO radio resources applies only to the reverse link.
- Equipment: You can select equipment from the list. To create new site equipment, see "Creating Site Equip-
ment" on page 719.
If no equipment is assigned to the site, Atoll considers the following default values:
- Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are dis-
played in red in the Transmitters folder of the Data tab.
Note: Only active transmitters are taken into consideration during calculations.
- Transmission/Reception: Under Transmission/Reception, you can define the total losses and the noise
figure in the Real text boxes. Atoll can calculate losses and noise according to the characteristics of the equip-
ment assigned to the transmitter; the calculated values are indicated in the Computed text boxes. Atoll
always considers the values in the Real boxes in prediction studies even if they are different from the values
in the Computed boxes. You can update the values in the Real boxes with the values in the Computed text
boxes. For information, see "Updating the Values for Total Losses and the BTS Noise Figure for Transmitters"
on page 148.
You can assign equipment by using the Equipment Specifications dialogue which appears when you click
the Equipment button.
- On the Equipment Specifications dialogue (see Figure 11.4), the equipment you select and the gains and
losses you define are used to set the transmitter noise figure and the total transmitter reverse link and forward
link losses:
- TMA: You can select a tower-mounted amplifier (TMA) from the list. You can click the Browse button
( ) to access the properties of the TMA. For information on creating a TMA, see "Defining TMA Equip-
ment" on page 147.
- Feeder: You can select a feeder cable from the list. You can click the Browse button ( ) to access the
properties of the feeder. For information on creating a feeder cable, see "Defining Feeder Cables" on
page 147.
- BTS: You can select a base transceiver station (BTS) equipment from the BTS list. You can click the
Browse button ( ) to access the properties of the BTS. For information on creating a BTS, see "Defin-
ing BTS Equipment" on page 148.
- Feeder Length: You can enter the feeder length at transmission and reception.
- Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value
you enter must be positive.
- Receiver Antenna Diversity Gain: You can enter a receiver antenna diversity gain. The value you enter
must be positive.
Note: Any loss related to the noise due to a transmitters repeater is included in the calculated
reception losses.
- Antennas:
- Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added
to the altitude of the site as given by the DTM. If the transmitter is situated on a building, the height entered
must include the height of building.
- Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the
Browse button ( ) to access the properties of the antenna. The other fields, Azimuth, Mechanical
Downtilt, and Additional Electrical Downtilt, display additional antenna parameters.
- Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power, which is
the percentage of power reserved for this particular antenna. For example, for a transmitter with one
secondary antenna, if you reserve 40% of the total power for the secondary antenna, 60% is available for
the main antenna.
For information on working with data tables, see "Working with Data Tables" on page 50.
Note: By default, the synchronisation power and paging power are set as absolute values. You
can set these values as relative to the pilot power by right-clicking the Transmitters folder
on the Data tab of the Explorer window and Properties from the context menu. Then, on
the Global Parameters tab of the Properties dialogue, under DL Powers, you can select
Relative to Pilot. The synchronisation power and paging power values are automatically
converted and set as relative to the pilot power.
- Max DL Load (% Pmax): The percentage of the maximum forward link power (set in Max Power) not to be
exceeded. This limit will be taken into account during the simulation if the options DL Load and Max DL Load
defined per cell are selected. If these options are not selected during a simulation, this value is not taken into
consideration.
- Max UL Load Factor (%): The maximum reverse link load factor not to be exceeded. This limit can be taken
into account during the simulation. This limit will be taken into account during the simulation if the options UL
Load Factor and Max UL Load Factor defined per cell are selected. If these options are not selected during
a simulation, this value is not taken into consideration.
- Total Power (dBm or %): The total transmitted power on forward link. This value can be a simulation result
or can be entered by the user.
Note: By default, the total power is set as absolute value. You can set this value as a
percentage of the maximum power of the cell by right-clicking the Transmitters folder on
the Data tab of the Explorer window and selecting Properties from the context menu.
Then, on the Global Parameters tab of the Properties dialogue, under DL Load, you can
select % Pmax. The total power value is automatically converted and set as a percentage
of the maximum power.
- UL Load Factor (%): The reverse link cell load factor. This factor corresponds to the ratio between the reverse
link total interference and the reverse link total noise. This value can be a simulation result or can be entered
by the user.
- Max Number of Intra-carrier Neighbours: The maximum number of intra-carrier neighbours for this cell. This
value is used by the intra-carrier neighbour allocation algorithm.
- Max Number of Inter-carrier Neighbours: The maximum number of inter-carrier neighbours for this cell. This
value is used by the inter-carrier neighbour allocation algorithm.
- Max Number of Inter-technology Neighbours: The maximum number of inter-technology neighbours for
this cell. This value is used by the inter-technology neighbour allocation algorithm.
- Neighbours: You can access a dialogue in which you can set both intra-technology (intra-carrier and inter-
carrier) and inter-technology neighbours by clicking the Browse button ( ). For information on defining
neighbours, see "Planning Neighbours" on page 663.
Tip: The Browse button ( ) might not be visible in the Neighbours box if this is a new cell.
You can make the Browse button appear by clicking Apply.
- PN Offset Domain: The Pseudo Noise (PN) offset domain to which the cell belongs. The PN offset domain is
a set of groups, with each group containing several PN offsets.
- Co-PN Reuse Distance (m): The distance within which the PN offset defined for this cell can be reused.
- PN Offset: The PN offset is a time offset used by a cell to shift a Pseudo Noise sequence.
- Power Reserved for Pooling (dB): The power reserved for pooling is the maximum amount of power that
can be allocated to this cell by other transmitters on the site using the same carrier. This value is only used if
the site equipment allows power pooling between transmitters.
- Ec/I0 Threshold (dB): Enter the minimum EcI0 required from the cell to be the best server in the active set.
- T_Drop: Enter the minimum EcI0 required from the cell not to be rejected from the active set.
The following options are valid for 1xEV-DO carriers:
- Active: If this cell is active, you must select the Active check box.
- Max Power (dBm): The power transmitted by a 1xEV-DO cell when there is at least one user. For 1xEV-DO
carriers, the BTS always transmits at maximum power (the DL maximum power) unless it has no user to sup-
port. When there is no user, the BTS transmits a very low level of power during idle traffic slots (DL maximum
power + Idle gain).
- Idle Power Gain (dB): The gain applied to the DL power when there is no active user connected to the cell.
It must be a negative value.
- MUG Table = f(No. Users): You can access the MUG (Multi-User Gain) table by clicking the Browse button
( ). The MUG table is a graph of gain as a function of the number of users. The average cell throughput is
higher with multiple users than with a single user. This is modelled by the MUG graph.
- Noise Rise Threshold (dB): The noise rise threshold. The noise rise threshold and the acceptable noise rise
margin are considered in the simulation during reverse link congestion. Atoll ensures that the cell reverse link
noise rise is within a range defined by the noise rise threshold plus the margin and the noise rise threshold
minus the margin.
- Acceptable Noise Rise Margin (dB): The acceptable noise rise margin.
- DRC Error Rate (%): The error rate as a percentage received by the cell on the Data Rate Control (DRC)
channel. The cell may receive the DRC channel from a mobile incorrectly. If this happens, the mobile will not
be scheduled for data transmission. This value is taken into account during rate control when Atoll calculates
the average cell throughput on the forward link.
- EV-DO Timeslots Dedicated to BCMCS (%): The percentage of timeslots dedicated to Broadcast/Multicast
Services (BCMCS). This parameter is taken into account during rate control when Atoll calculates the cell
average forward link throughput.
- EV-DO Timeslots Dedicated to Control Channels (%): The percentage of timeslots dedicated to control
channels (control, pilot, and ACK channels). This parameter is taken into account during rate control when
Atoll calculates the cell average forward link throughput.
- BCMCS Throughput (kbps): The BCMCS throughput. Two throughput values are available: 204.8 kbps and
409.6 kbps. This parameter is taken into account during rate control when Atoll calculates the cell average
forward link throughput.
- Max UL Load Factor (%): The maximum reverse link load factor not to be exceeded. This limit can be taken
into account during the simulation.
- Total Power (dBm): The total transmitted power on forward link. This value can be a simulation result or can
be entered by the user.
- UL Load Factor (%): The reverse link cell load factor. This factor corresponds to the ratio between the reverse
link total interference and the reverse link total noise. This value can be a simulation result or can be entered
by the user.
- Max Number of Intra-carrier Neighbours: The maximum number of intra-carrier neighbours for this cell. This
value is used by the intra-carrier neighbour allocation algorithm.
- Max Number of Inter-carrier Neighbours: The maximum number of inter-carrier neighbours for this cell. This
value is used by the inter-carrier neighbour allocation algorithm.
- Max Number of Inter-technology Neighbours: The maximum number of inter-technology neighbours for
this cell. This value is used by the inter-technology neighbour allocation algorithm.
- Neighbours: You can access a dialogue in which you can set both intra-technology (intra-carrier and inter-
carrier) and inter-technology neighbours by clicking the Browse button ( ). For information on defining
neighbours, see "Planning Neighbours" on page 663.
Tip: The Browse button ( ) might not be visible in the Neighbours box if this is a new cell.
You can make the Browse button appear by clicking Apply.
- PN Offset Domain: The Pseudo Noise (PN) offset domain to which the cell belongs. The PN offset domain is
a set of groups, with each group containing several PN offsets.
- Co-PN Reuse Distance (m): The distance within which the PN offset defined for this cell can be reused.
- PN Offset: The PN offset is a time offset used by a cell to shift a Pseudo Noise sequence.
- Max No. of EV-DO Users: The maximum number of EV-DO carrier users that this cell can support at any
given time.
- Ec/I0 Threshold (dB): Enter the minimum EcI0 required from the cell to be the best server in the active set.
- T_Drop: Enter the minimum EcI0 required from the cell not to be rejected from the active set.
Tips:
If you are creating several transmitters at the same time, or modifying several existing trans-
mitters, you can do it more quickly by editing or pasting the data directly in the Transmitters
table. You can open the Transmitters table by right-clicking the Transmitters folder on the
Data tab of the Explorer window and selecting Open Table from the context menu. For infor-
mation on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
If you want to add a transmitter to an existing site on the map, you can add the transmitter by
right-clicking the site and selecting New Transmitter from the context menu.
Tips:
If you are creating or modifying several cells at the same time, you can do it more quickly by
editing the data directly in the Cells table. You can open the Cells table by right-clicking the
Transmitters folder on the Data tab of the Explorer window and selecting Cells > Open
Table from the context menu. You can either edit the data in the table, paste data into the table
(see "Copying and Pasting in Tables" on page 56), or import data into the table (see "Importing
Tables from Text Files" on page 59).
If you want to add a cell to an existing transmitter on the map, you can add the cell by right-
clicking the transmitter and selecting New Cell from the context menu.
3. In the map window, move the pointer over the map to where you would like to
place the new station. The exact coordinates of the pointers current location
are visible in the Status bar.
Tips:
To place the station more accurately, you can zoom in on the map before you click the New
Station button. For information on using the zooming tools, see "Changing the Map Scale" on
page 38.
If you let the pointer rest over the station you have placed, Atoll displays its tip text with its
exact coordinates, allowing you to verify that the location is correct.
You can also place a series of stations using a station template. You do this by defining an area on the map where you
want to place the stations. Atoll calculates the placement of each station according to the defined hexagonal cell radius
in the station template. For information on defining the cell radius, see "Creating or Modifying a Station Template" on
page 614.
To place a series of stations within a defined area:
1. In the Radio toolbar, select a template from the list.
2. Click the Hexagonal Design button ( ), to the left of the template list. A hexagonal design is a group of stations
created from the same station template.
Note: If the Hexagonal Design button is not available ( ), the hexagonal cell radius for this
template is not defined. For information on defining the cell radius, see "Creating or
Modifying a Station Template" on page 614.
3. Draw a zone delimiting the area where you want to place the series of stations:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
Atoll fills the delimited zone with new stations and their hexagonal shapes. Station objects such as sites and trans-
mitters are also created and placed into their respective folders.
Once you have created one or more stations, the hexagons describing their cell radius remain visible. You can choose not
to display them.
To hide the hexagons after creating stations using the Hexagonal Design button ( ) or the New Station button ( ):
On the Data tab, clear the display check box beside the Hexagonal Design folder.
You can work with the sites and transmitters in these stations as you work with any station object, adding, for example,
another antenna to a transmitter.
When you place a new station using a station template as explained in "Placing a New Station Using a Station Template"
on page 612, the site is created at the same time as the station. However, you can also place a new station on an existing
site.
- Under Main Antenna, you can modify the following: the antenna Model, 1st Sector Azimuth, from which the
azimuth of the other sectors are offset to offer complete coverage of the area, the Height of the antenna from
the ground (i.e., the height over the DTM; if the transmitter is situated on a building, the height entered must
include the height of building), the Mechanical Downtilt, and the Additional Electrical Downtilt.
- Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both
the Main Matrix and the Extended Matrix. For information on propagation models, see "Assigning a Propa-
gation Model to One Transmitter" on page 632.
5. Click the Transmitter tab. In this tab (see Figure 11.7). You can modify the following:
- Active: If the transmitters in this station template are to be active, you must select the Active check box.
Active transmitters are displayed in red in the Transmitters folder of the Data tab.
- Transmission/Reception: Under Transmission/Reception, you can define the total losses and the noise
figure in the Real text boxes. Atoll can calculate losses and noise according to the characteristics of the equip-
ment assigned to the transmitter; the calculated values are indicated in the Computed text boxes. Atoll
always considers the values in the Real boxes in prediction studies even if they are different from the values
in the Computed boxes. You can update the values in the Real boxes with the values in the Computed text
boxes. For information, see "Updating the Values for Total Losses and the BTS Noise Figure for Transmitters"
on page 148.
You can assign equipment by using the Equipment Specifications dialogue which appears when you click
the Equipment button. For information on the Equipment Specifications dialogue, see "Transmitter Descrip-
tion" on page 607.
6. Click the CDMA tab. In this tab (see Figure 11.8), you modify the specifications of the Carriers (each corre-
sponding to a cell) that each transmitter supports. For information on carriers and cells, see "Cell Definition" on
page 609.
- You can select the Carriers used by each transmitter.
- Under PN Offset, you can define the Reuse Distance and the Domain of the pseudo noise offset.
- Under Power, you can define the Pilot, the Paging, and the Synchro powers, and the Idle Power Gain.
- Under Simulation Constraints, you can modify the Max Power, the Max DL Load (defined as a percentage
of the maximum power), and the Max UL Load Factor.
- Under Load Conditions, you can modify the Total Transmitted Power and the UL Load Factor.
- Under Active Set, you can modify the Min Ec/Io and the T-Drop.
- You can also modify the Number of Uplink and Downlink Channel Elements and select the Equipment.
7. Click the CDMA2000 tab. In this tab (see Figure 11.9), you modify additional specifications of the Carriers (each
corresponding to a cell) that each transmitter supports. For information on carriers and cells, see "Cell Definition"
on page 609.
- You can set the Power Reserved for Pooling.
- Under 1xRTT, you can modify the Pilot Power, the Paging Power, and the Synchro Power.
- Under 1xEV-DO, you can modify the Idle Power Gain, the Max. Number of EV-DO Channel Elements per
Carrier, and you can modify the MUG (multi-user gain) table.
- Under 1xEV-DO, for rev.0, you can set the Noise Rise Threshold, the Acceptable Noise Rise Margin, and
the DRC Error Rate.
- Under 1xEV-DO, for rev.A, you can set the Timeslot BCMCS, the Timeslot Control Channels, and the
BCMCS Throughput.
8. Click the Neighbours tab. In this tab (see Figure 11.10), you can modify the Max Number of Intra- and Inter-Car-
rier Neighbours and the Max Number of Inter-Technology Neighbours. For information on defining neigh-
bours, see "Planning Neighbours" on page 663.
9. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the
Sites table, or if you have defined an additional field in the Station Template Properties dialogue.
10. When you have finished setting the parameters for the station template, click OK to close the dialogue and save
your changes.
- Add: If you want to add a user-defined field to the station templates, you must have already added it to the
Sites table (for information on adding a user-defined field to a table, see "Adding a Field to an Object Types
Data Table" on page 51) for it to appear as an option in the station template properties. To add a new field:
i. Click the Add button. The Field Definition dialogue appears.
ii. Enter a Name for the new field. This is the name that will be used in database.
iii. If desired, you can define a Group that this custom field will belong to. When you open an Atoll document
from a database, you can then select a specific group of custom fields to be loaded from the database,
instead of loading all custom fields.
iv. In Legend, enter the name for the field that will appear in the Atoll document.
v. For Type, you can select from Text, Short integer, Long integer, Single, Double, True/False, Date/
Time, and Currency. If you choose text, you can also set the field Size (in characters), and create a
Choice list, by entering the possible selections directly in the Choice list window and pressing ENTER
after each one.
vi. Enter, if desired, a Default value for the new field.
vii. Click OK to close the Field Definition dialogue and save your changes.
- Delete: To delete a user-defined field:
i. Select the user-defined field you want to delete.
ii. Click the Delete button. The user-defined field appears in strikeout. It will be definitively deleted when you
close the dialogue.
- Properties: To modify the properties of a user-defined field:
i. Select the user-defined field you want to modify.
ii. Click the Properties button. The Field Definition dialogue appears.
iii. Modify any of the properties as desired.
iv. Click OK to close the Field Definition dialogue and save your changes.
6. Click OK.
Tips:
To place the station more accurately, you can zoom in on the map before you select Duplicate
from the context menu.. For information on using the zooming tools, see "Changing the Map
Scale" on page 38.
If you let the pointer rest over the station you have placed, Atoll displays tip text with its exact
coordinates, allowing you to verify that the location is correct.
You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to
place each duplicate base station.
For more information on the site, transmitter, and cell properties, see "Definition of a Base Station" on page 606.
Note: When you import data into your current Atoll document, the coordinate system of the
imported data must be the same as the display coordinate system used in the document.
If you cannot change the coordinate system of your source data, you can temporarily
change the display coordinate system of the Atoll document to match the source data.
For information on changing the coordinate system, see "Setting a Coordinate System"
on page 92.
Important: The table you copy from must have the same column layout as the table you are pasting
data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
Importing data: If you have data in text or comma-separated value (CSV) format, you can import it into the tables
in the current document. If the data is in another Atoll document, you can first export it in text or CSV format and
then import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select
what values you import into which columns of the table.
When you create a group of base stations by importing data, you must import site data in the Sites table, trans-
mitter data in the Transmitters table, and cell data in the Cells table, in that order.
For information on exporting table data, see "Exporting Tables to Text Files" on page 58. For information on
importing table data, see "Importing Tables from Text Files" on page 59.
Note: You can quickly create a series of base stations for study purposes using the Hexagonal
Design tool on the Radio toolbar. For information, see "Placing a New Station Using a
Station Template" on page 612.
( and ). For information on defining the transmitter symbol, see "Defining the Display Type" on page 34.
Note: Broad-band repeaters are not modelled. Atoll assumes that all carriers from the 3G donor
transmitter are amplified.
4. To create repeater equipment, enter the following in the row marked with the New Row icon ( ):
a. Enter a Name and Manufacturer for the new equipment.
b. Enter a Noise Figure. The repeater causes a rise in noise at the donor transmitter, so the noise figure is used
to calculate the reverse link loss to be added to the donor transmitter reverse link losses. The noise figure must
be a positive value.
c. Enter minimum and maximum repeater amplification gains in the Min. Gain and Max Gain columns. These
parameters enable Atoll to ensure that the user-defined amplifier gain is consistent with the limits of the equip-
ment if there are any.
d. Enter a Gain Increment. Atoll uses the increment value when you increase or decrease the repeater amplifier
gain using the buttons to the right of the Amplification box ( ) on the General tab of the repeater Properties
dialogue.
e. Enter the maximum power that the equipment can transmit on the downlink in the Maximum Downlink Power
column. This parameter enables Atoll to ensure that the downlink power after amplification does not exceed
the limit of the equipment.
f. If desired, enter a Maximum Uplink Power, an Internal Delay and Comments. These fields are for informa-
tion only and are not used in calculations.
5. To modify repeater equipment, change the parameters in the row containing the repeater equipment you wish to
modify.
2. Click the arrow next to New Repeater or Remote Antenna button ( ) on the Radio toolbar.
3. Select Repeater from the menu.
4. Click the map to place the repeater. The repeater is placed on the map, represented by a symbol ( ) in the
same colour as the donor transmitter or repeater. By default, the repeater has the same azimuth as the donor
transmitter or repeater. Its tooltip and label display the same information as displayed for the donor transmitter or
repeater. As well, its tooltip and label identify the repeater and the donor transmitter or repeater. In the Explorer
window, the repeater is found in the Transmitters folder of the Data tab under its donor transmitter.
For information on defining the properties of the new repeater, see "Defining the Properties of a Repeater" on
page 621.
Note: You can see to which base station the repeater is connected by clicking it; Atoll displays
a link to the donor transmitter or repeater.
Important: The table you copy data from must have the same column layout as the table you are
pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
Important: If you want to create a remote antenna, you must select Optical Fibre Link.
- If you selected Air Link under Donor-Repeater Link, enter the following information under Antenna:
i. Select a Model from the list. You can click the Browse button ( ) to access the properties of the
antenna.
ii. Enter the height off the ground of the antenna in the Height/Ground box. This will be added to the altitude
of the transmitter as given by the DTM.
iii. Enter the Azimuth and the Mechanical Downtilt.
Note: You can click the Calculate button to update azimuth and downtilt values after changing
the repeater donor side antenna height or the repeater location. If you choose another site
or change site coordinates in the General tab, click Apply before clicking the Calculate
button.
- If you selected Air Link under Donor-Repeater Link, enter the following information under Feeders:
i. Select a Type of feeder from the list. You can click the Browse button ( ) to access the properties of
the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
5. Click the Coverage Site tab. You can modify the following parameters:
- Select the Active check box. Only active repeaters (displayed in red in the Transmitters folder in the Data
tab of the Explorer window) are calculated.
- Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual
gains. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply
before clicking the Calculate button. Atoll uses the forward link total gain values to calculate the signal level
received from the repeater. The reverse link total gain value is considered in reverse link EbNt service area
studies.
The forward link total gain is applied to each power (pilot power, SCH power, etc.). It takes into account losses
between the donor transmitter and the repeater, donor characteristics (donor antenna gain, reception feeder
losses), amplification gain, and coverage characteristics (coverage antenna gain and transmission feeder
losses).
The reverse link total gain is applied to each terminal power. It takes into account losses between the donor
transmitter and the repeater, donor part characteristics (donor antenna gain, transmission feeder losses), am-
plification gain and coverage part characteristics (coverage antenna gain and reception feeder losses).
ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( ) to access the
properties of the antenna. Then, enter the Azimuth and the Mechanical Downtilt. By default, the char-
acteristics (antenna, azimuth, height, etc.) of the repeater coverage side correspond to the characteristics
of the donor transmitter.
iii. Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power. For infor-
mation on working with data tables, see "Working with Data Tables" on page 50.
- Under Feeders, you can modify the following information:
i. Select a Type of feeder from the list. You can click the Browse button ( ) to access the properties of
the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
- Under Losses, Atoll displays the Loss Related to Repeater Noise Rise.
6. Click the Propagation tab. Since repeaters are taken into account during calculations, you must set the propaga-
tion parameters. On the Propagation tab, you can modify the following: the Propagation Model, Radius, and Res-
olution for both the Main Matrix and the Extended Matrix. By default, the propagation characteristics of the
repeater (model, calculation radius, and grid resolution) are the same as those of the donor transmitter. For infor-
mation on propagation models, see "Chapter 5: Managing Calculations in Atoll".
Note: You can prevent Atoll from updating the UL and DL total gains of selected repeaters by
creating a custom field called "FreezeTotalGain" in the Repeaters table and setting the
value of the field to "True." Afterwards, when you select Repeaters > Calculate Gains
from the Transmitters context menu, Atoll will only update the UL and DL total gains for
repeaters with the custom field "FreezeTotalGain" set to "False."
You can update the propagation losses of all off-air repeaters by selecting Repeaters > Calculate Donor Side
Propagation Losses from the Transmitters context menu.
You can select a repeater on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using
the Mouse" on page 32) or its position relative to the site (see "Changing the Position of the Transmitter Relative
to the Site" on page 32).
Note: Ensure that the remote antennas donor transmitter does not have any antennas.
2. Click the arrow next to New Repeater or Remote Antenna button ( ) on the Radio toolbar.
3. Select Remote Antenna from the menu.
4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol
( ) in the same colour as the donor transmitter. By default, the remote antenna has the same azimuth as the
donor transmitter. Its tooltip and label display the same information as displayed for the donor transmitter. As well,
its tooltip and label identify the remote antenna and the donor transmitter. In the Explorer window, the remote
antenna is found in the Transmitters folder of the Data tab under its donor transmitter.
For information on defining the properties of the new remote antenna, see "Defining the Properties of a Remote
Antenna" on page 623.
Note: You can see to which base station the remote antenna is connected by clicking it; Atoll
displays a link to the donor transmitter.
Important: The table you copy from must have the same column layout as the table you are pasting
data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
4. Click the Donor Side tab. You can modify the following parameters:
- Under Donor-Repeater Link, select Optical Fibre Link and enter the Cable Losses.
5. Click the Coverage Site tab. You can modify the following parameters:
- Select the Active check box. Only active remote antennas (displayed in red in the Transmitters folder in the
Data tab of the Explorer window) are calculated.
- Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual
gains. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply
before clicking the Calculate button. Atoll uses the forward link total gain values to calculate the signal level
received from the remote antenna. The reverse link total gain value is considered in reverse link EbNt service
area studies.
The forward link total gain is applied to each power (pilot power, SCH power, etc.). It takes into account losses
between the donor transmitter and the remote antenna.
The reverse link total gain is applied to each terminal power. It takes into account losses between the donor
transmitter and the remote antenna.
ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( ) to access the
properties of the antenna. Then, enter the Azimuth and the Mechanical Downtilt.
iii. Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power. For infor-
mation on working with data tables, see "Working with Data Tables" on page 50.
- Under Feeders, you can modify the following information:
i. Select a Type of feeder from the list. You can click the Browse button ( ) to access the properties of
the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
6. Click the Propagation tab. Since remote antennas are taken into account during calculations, you must set prop-
agation parameters, as with transmitters. On the Propagation tab, you can modify the following: the Propagation
Model, Radius, and Resolution for both the Main Matrix and the Extended Matrix. By default, the propagation
characteristics of the remote antenna (model, calculation radius, and grid resolution) are the same as those of the
donor transmitter. For information on propagation models, see "Chapter 5: Managing Calculations in Atoll".
Note: You can prevent Atoll from updating the UL and DL total gains of selected remote
antennas by creating a custom field called "FreezeTotalGain" in the Remote Antennas
table and setting the value of the field to "True." Afterwards, when you select Remote
Antennas > Calculate Gains from the Transmitters context menu, Atoll will only update
the UL and DL total gains for remote antennas with the custom field "FreezeTotalGain"
set to "False."
You can select a remote antenna on the map and change its azimuth (see "Changing the Azimuth of the Antenna
Using the Mouse" on page 32) or its position relative to the site (see "Changing the Position of the Transmitter
Relative to the Site" on page 32).
zone also limits the resulting calculated coverage. The computation zone is taken into account whether or not it is
visible.
It is important not to confuse the computation zone and the focus zone or hot spot zone. The computation zone
defines the area where Atoll calculates path loss matrices, coverage studies, Monte Carlo, power control simula-
tions, etc., while the focus zone or hot spot zone is the area taken into consideration when generating reports and
results.
For information on the computation zone, see "Creating a Computation Zone" on page 633.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be
studied.
2. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the fol-
lowing:
- Move the receiver to change the current position.
- Click to place the receiver at the current position. You can move the receiver again by clicking it a second time.
- Right-click the receiver to choose one of the following commands from the context menu:
- Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates.
- Target Site: Select a site from the list to place the receiver directly on a site.
4. Click the Profile tab.
In CDMA2000, 1xEV-DO always transmits at full power, unlike 1xRTT. Therefore, if you do a point analysis on all
carriers, the values displayed will always be for the maximum power transmitted by the cell, in other words, the
power for the 1xEV-DO carrier. In order to display the values of the 1xRTT carrier, you must select it. When you
select the 1xRTT carrier, the point analysis displays the strength of the received pilot signal.
The results of the analysis are displayed at the top of the Profile tab:
- The shadowing margin and the cell edge coverage probability used for calculating it
- The distance between the transmitter and the receiver.
You can change the following options at the top of the Profile tab:
Note: You can use the same procedure to study the signal level coverage of several sites by
grouping the transmitters. For information on grouping transmitters, see "Grouping Data
Objects by a Selected Property" on page 65.
Tip: If you wish to study only transmitters by their status, at this step you could group them by
status.
5. Select Coverage by Signal Level and click OK. A study properties dialogue appears.
6. You can configure the following parameters in the Properties dialogue:
- General tab: You can change the assigned Name of the coverage prediction, the Resolution, and you can
add a Comment. The resolution you set is the display resolution, not the calculation resolution.
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:
City Centre 5m
City 20 m
County 50 m
State 100 m
- Condition tab: The coverage prediction parameters on the Conditions tab allow you to define the signals that
will be considered for each pixel (see Figure 11.13).
- At the top of the Condition tab, you can set the signal level range to be considered. In Figure 11.13, a sig-
nal level greater than or equal to -120 dBm will be considered.
- Under Server, select "All" to consider signal levels from all servers.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage
Probability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select the Carrier to be studied, or select "All" to have all carriers taken into account. In
CDMA2000, 1xEV-DO always transmits at full power, unlike 1xRTT. Therefore, if you select "All", the
values displayed will always be for the maximum power transmitted by the cell, in other words, the power
for the 1xEV-DO carrier. In order to make a coverage prediction on the transmitted power of the 1xRTT
carrier, you must select the carrier. When you select the 1xRTT carrier, the coverage prediction displays
the strength of the received pilot signal.
- Display tab: You can modify how the results of the coverage prediction will be displayed.
- Under Display Type, select "Value Intervals."
- Under Field, select "Best signal level." Selecting "All" or "Best signal level" on the Conditions tab will give
you the same results because Atoll displays the results of the best server in either case. Selecting "Best
signal level" necessitates, however, the longest time for calculation.
- You can change the value intervals and their displayed colour. For information on changing display prop-
erties, see "Display Properties of Objects" on page 33.
- You can create a tooltip with information about the coverage prediction by clicking the Browse button
( ) next to the Tip Text box and selecting the fields you want to display in the tooltip.
- You can select the Add to Legend check box to add the displayed value intervals to the legend.
Note: If you change the display properties of a coverage prediction after you have calculated it,
you may make the coverage prediction invalid. You will then have to recalculate the
coverage prediction to obtain valid results.
7. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The signal level
coverage prediction can be found in the Predictions folder on the Data tab. Atoll automatically locks the results of a cover-
age prediction as soon as it is calculated, as indicated by the icon ( ) beside the coverage prediction in the Predictions
folder. When you click the Calculate button ( ), Atoll only calculates unlocked coverage predictions ( ).
Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices
using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main prop-
agation model with a shorter radius (displayed with a blue square in Figure 11.14) and a higher resolution and an extended
propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate
higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower reso-
lution path loss matrices outside the area covered by the main propagation model.
In this section, the following are explained:
"Path Loss Matrices" on page 629
"Assigning a Propagation Model" on page 631
"The Calculation Process" on page 633
"Creating a Computation Zone" on page 633
"Setting Transmitters or Cells as Active" on page 634
"Signal Level Coverage Predictions" on page 634
"Analysing a Coverage Prediction" on page 639
"CDMA-Specific Coverage Predictions" on page 646
"Printing and Exporting Coverage Prediction Results" on page 663.
Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matri-
ces in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning
projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case
of large radio-planning projects, saving your path loss matrices externally will help reduce the size of the file and the use
of computer resources.
The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same
radio-planning document and share the path loss matrices. In this case, the radio data is stored in a database and the path
loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and
recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path
loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to
radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual.
When you save the path loss matrices to an external directory, Atoll creates:
One file per transmitter with the extension LOS for its main path loss matrix
A DBF file with validity information for all the main matrices.
A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
To set the storage location of the path loss matrices:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss
matrices and the location for the shared path loss matrices:
- Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are
loading path loss matrices from a shared location, where you store your changes to shared path loss matrices.
Click the button beside the Private Directory ( ) and select Embedded to save the path loss matrices in
the Atoll document, or Share to select a directory where Atoll can save the path loss matrices externally.
Note: Path loss matrices you calculate locally are not stored in the same directory as shared
path loss matrices. Shared path loss matrices are stored in a read-only directory. In other
words, you can read the information from the shared path loss matrices but any changes
you make will be stored locally, either embedded in the ATL file or in a private external
folder, depending on what you have selected in Private Directory.
Caution: When you save the path loss files externally, the external files are updated as soon as
calculations are performed and not only when you save the Atoll document. In order to
keep consistency between the Atoll document and the stored calculations, you should
save the Atoll document before closing it, if you have updated the path loss matrices.
- Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a
database and the common path loss matrices are stored in a directory that is accessible to all users. Any
changes you make will not be saved to this directory; they will be saved in the location indicated in Private
Directory. The path loss matrices in the shared directory are updated by a user with administrator rights based
on the updated information in the database. For more information on shared directories, see the Administrator
Manual.
If you are working in a multi-user Atoll environment, ensure that the path to the Shared Directory is correct.
5. Click OK.
Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want,
you can check if the path loss matrices are invalid without creating a coverage prediction.
To check whether the path loss matrices are valid:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. You have the
following display options:
- Display all the matrices: All path loss matrices are displayed.
- Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available Results table lists the following information for each displayed path loss matrix:
2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation
Model to All Transmitters" on page 631, this is the propagation model that will be used for all transmitters, except
for those to which you have assigned a propagation model either individually or as part of a group.
Important: When you assign a propagation model globally, you override any selection you might
have made to an individual transmitter or to a group of transmitters.
If, after assigning a propagation model to an individual transmitter or to a group of transmitters, you assign a prop-
agation model globally, you will override the propagation models that you had assigned to individual transmitters
or to a group of transmitters.
3. If you have assigned a default propagation model for coverage predictions, as described in "Assigning a Default
Propagation Model for Coverage Predictions" on page 633, this is the propagation model that will be used for all
transmitters whose main propagation model is "(Default model)." If a transmitter has any other propagation model
chosen as the main propagation model, that is the propagation model that will be used.
In this section, the following methods of assigning a propagation model are explained:
"Assigning a Propagation Model to All Transmitters" on page 631
"Assigning a Propagation Model to a Group of Transmitters" on page 632
"Assigning a Propagation Model to One Transmitter" on page 632
"Assigning a Default Propagation Model for Coverage Predictions" on page 633.
Transmitters that share the same parameters and environment will usually use the same propagation model and settings.
In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common
parameters and then assigning the propagation model.
To define a main and extended propagation model for a defined group of transmitters:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select from the Group by submenu of the context menu the property by which you want to group the transmitters.
The objects in the folder are grouped by that property.
Note: You can group transmitters by several properties by using the Group By button on the
Properties dialogue. For more information, see "Advanced Grouping" on page 66.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model
to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmit-
ters.
When you assign a main and extended propagation model to a single transmitter, it overrides any changes made globally.
To define a main and extended propagation model for all transmitters:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Transmitters folder.
3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu
appears.
4. Select Properties from the context menu. The Properties dialogue appears.
5. Click the Propagation tab.
6. Under Main Matrix:
- Select a Propagation Model
- Enter a Radius and Resolution.
7. If desired, under Extended Matrix:
- Select a Propagation Model
- Enter a Radius and Resolution.
8. Click OK. The selected propagation models will be used for the selected transmitter.
You can assign a default propagation model for coverage predictions. This propagation model is used as for all transmit-
ters whose main propagation model is "(Default model)."
To assign a default propagation model for coverage predictions:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Predictions tab.
5. Select a Default Propagation Model from the list.
6. Enter a Default Resolution. When you create a new coverage prediction, the resolution by default is the value
you have entered here.
Tip: By making the necessary entry in the atoll.ini file, if you clear the value entered in the
Resolution box when you create a coverage prediction, Atoll will calculate the coverage
prediction using the currently defined default resolution. That way, if you have many
coverage predictions, you can change their resolution by changing the default resolution
and recalculating the coverage predictions. Atoll will then calculate them using the
updated resolution. For information on changing entries in the atoll.ini file, see the
Administrator Manual.
7. Click OK. The selected propagation model will be used for coverage predictions for all transmitters whose main
propagation model is "(Default model)."
Notes:
You can stop any calculations in progress by clicking the Stop Calculations button ( ) in
the toolbar.
When you click the Force Calculation button ( ) instead of the Calculate button, Atoll cal-
culates all path loss matrices, unlocked coverages, and pending simulations.
Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a computation zone. You can import it by right-clicking the Computa-
tion Zone folder on the Geo tab and selecting Import from the context menu.
Fit to Map Window: You can create a computation zone the size of the map window by selecting Fit to Map
Window from the context menu.
Note: You can save the computation zone in the user configuration. For information on
exporting the computation zone in the user configuration, see "Exporting a User
Configuration" on page 75.
Note: If you do not yet have a zone containing the transmitters you want to set as active, you
can draw a zone as explained in "Using Zones in the Map Window" on page 41.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active.
Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on
choosing and configuring a propagation model, see "Chapter 5: Managing Calculations in Atoll".
Calculating path loss matrices can be extremely time and resource intensive when you are working on larger projects.
Consequently, Atoll offers you the possibility of distributing path loss calculations on several computers. You can install
the Atoll computing server application on other workstations or on servers. Once the computing server application is
installed on a workstation or server, the computer is available for distributed path loss calculation to other computers on
the network. For information on distributed calculations, see the Administrator Manual.
Once you have created a coverage prediction, you can use the coverage predictions context menu to make the coverage
prediction into a template which will appear in the Study Types dialogue. You can also select Duplicate from the cover-
age predictions context menu to create a copy. By duplicating an existing coverage prediction that has the parameters
you wish to study, you can create a new coverage prediction more quickly. If you clone a coverage prediction, by selecting
Clone from the context menu, you can create a copy of the coverage prediction with the calculated coverage. You can
then change the display, providing that the selected parameter does not invalidate the calculated coverage prediction.
You can also save the list of all defined coverage predictions in a user configuration, allowing you or other users to import
it into a new Atoll document. When you save the list in a user configuration, the parameters of all existing coverage predic-
tions are saved; not just the parameters of calculated or displayed ones. For information on exporting user configurations,
see "Exporting a User Configuration" on page 75.
The following standard coverage predictions are explained in this section:
"Making a Coverage Prediction by Signal Level" on page 635
"Making a Coverage Prediction by Transmitter" on page 636
"Making a Coverage Prediction on Overlapping Zones" on page 637.
6. Click the Condition tab (see Figure 11.16). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered. In Figure 11.16, a signal
level greater than or equal to -120 dBm will be considered.
- Under Server, select "All" to consider all servers.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select the Carrier to be studied, or select "All" to have all carriers taken into account. In CDMA2000,
1xEV-DO always transmits at full power, unlike 1xRTT. Therefore, if you select "All", the values displayed will
always be for the maximum power transmitted by the cell, in other words, the power for the 1xEV-DO carrier.
In order to make a coverage prediction on the transmitted power of the 1xRTT carrier, you must select the
carrier. When you select the 1xRTT carrier, the coverage prediction displays the strength of the received pilot
signal.
10. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 11.17).
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Transmitter and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 11.16). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered. In Figure 11.16, a signal
level greater than or equal to -120 dBm or greater then -85 dBm will be considered.
- Under Server, select "Best signal level."
You can also define a Margin. Atoll will then consider the best signal level on each pixel and any other signal
level within the defined margin of the best one.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select the Carrier to be studied, or select "All" to have all carriers taken into account.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Note: You can also predict which server is the second best server on each pixel by selecting
"Second best signal level" on the Conditions tab setting "Discrete Values" as the Display
Type and "Transmitter" as the Field on the Display tab.
6. Click the Condition tab (see Figure 11.19). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered. In Figure 11.19, a signal
level greater than or equal to -120 dBm will be considered.
- Under Server, select "Best signal level" and define a Margin. Atoll will then consider the best signal level on
each pixel and any other signal level within the defined margin of the best one.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- You can select the Carrier to be studied, or select "All" to have all carriers taken into account. In CDMA2000,
1xEV-DO always transmits at full power, unlike 1xRTT. Therefore, if you select "All", the values displayed will
always be for the maximum power transmitted by the cell, in other words, the power for the 1xEV-DO carrier.
In order to make a coverage prediction on the transmitted power of the 1xRTT carrier, you must select the
carrier. When you select the 1xRTT carrier, the coverage prediction displays the strength of the received pilot
signal.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Note: By changing the parameters selected on the Condition tab and by selecting different
results to be displayed on the Display tab, you can calculate and display information other
than that which has been explained in the preceding sections.
1. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
2. At the bottom of the Point Analysis Tool window, click the Reception tab (see Figure 11.21).
3. Right-click the Reception tab and select Properties from the context menu. The Analysis Properties dialogue
appears.
4. Recreate the conditions of the coverage prediction using the options in the Analysis Properties dialogue:
- Shadowing taken into account: If the coverage prediction using shadowing, select the Shadowing taken
into account check box and enter a Cell Edge` Coverage Probability and select "From Model" from the
Shadowing Margin list.
- Indoor Coverage: If the coverage prediction calculated indoor coverage, select the Indoor Coverage check
box to add indoor losses. Indoor losses are defined per clutter class.
You can also use the Analysis Properties dialogue to:
- Change the X and Y coordinates to change the present position of the receiver.
The predicted signal level from different transmitters is reported in the Reception tab in the form of a bar chart,
from the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the
colour of the transmitter it represents. In the Map window, arrows from the pointer to each transmitter are displayed
in the colour of the transmitters they represent. A thick black line from the pointer to its best server is also displayed
in the map window. The best server of the pointer is the transmitter from which the pointer receives the highest
signal level. If you let the pointer rest, the signal level received from the corresponding transmitter at the pointer
location is displayed in the tool-tip.
11.1.10.7.4 Creating a Focus or Hot Spot Zone for a Coverage Prediction Report
The focus and hot spot zones define an area on which statistics can be drawn and on which reports are made. While you
can only have one focus zone, you can define several hot spot zones in addition to the focus zone.
It is important not to confuse the computation zone and the focus and hot spot zones. The computation zone defines the
area where Atoll computes path loss matrices, coverage studies, Monte Carlo, power control simulations, etc., while the
focus and hot spot zones are the areas taken into consideration when generating reports and results. When you create a
coverage prediction report, it gives the results for the focus zone and for each of the defined hot spot zones.
To define a focus zone or hot spot zone:
1. Click the Geo tab in the Explorer window.
2. Click the Expand button ( ) to expand the Zones folder.
3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or
a hot spot. The context menu appears.
4. Select Draw from the context menu.
5. Draw the focus or hot spot zone:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zones
visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but
will still be taken into account.
Note: You can only create a focus zone, and not a hot spot zone, from an existing polygon.
Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus
Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot
spot zones, you can import the name given to each zone as well.
Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map
Window from the context menu.
Notes: You can save the focus or hot spot zones so that you can use them in a different Atoll
document:
- You can save the focus zone in the user configuration. For information on exporting the
focus zone in the user configuration, see "Exporting a User Configuration" on page 75.
- You can right-click the Focus Zone folder or the Hot Spot Zones folder on the Data
tab of the Explorer window and select Export from the context menu.
You can include population statistics in the focus or hot spot zone by importing a
population map. For information on importing maps, see "Importing a Raster-format Geo
Data File" on page 107.
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
a. Under Configuration, click the Import button. The Open dialogue appears.
b. Select the configuration you want to import and click Open. The imported report configuration is applied
6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed
dialogue. The coverage prediction report table appears. The report is based on the hot spot zones and on the
focus zone if available or on the hot spot zones and computation zone if there is no focus zone.
To display a report on all coverage predictions:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears.
4. Define the format and content of the report:
You can select the columns that will be displayed in the report and define the order they are in:
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
5. Click OK.
If you have created a custom data map with integrable data, the data can be used in prediction reports. The data will be
summed over the coverage area for each item in the report (for example, by transmitter or threshold). The data can be
value data (revenue, number of customers, etc.) or density data (revenue/km, number of customer/km, etc.). Data is
considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example,
socio-demographic classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable
Versus Non Integrable Data" on page 124.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how you can verify if a newly added base station improves coverage.
A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal
Level" on page 635. The results are displayed in Figure 11.23. An area with poor coverage is visible on the right side of
the figure.
A new site is added, either by creating the site and adding the transmitters, as explained in "Creating a CDMA Base
Station" on page 606, or by placing a station template, as explained in "Placing a New Station Using a Station Template"
on page 612. Once the new base station has been added, the original coverage prediction can be recalculated, but then
it would be impossible to compare the results. Instead, the original signal level coverage prediction can be copied by
selecting Duplicate from its context menu. The copy is then calculated to show the effect of the new base station (see
Figure 11.24).
Figure 11.24: Signal level coverage prediction of network with new base station
4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes adding a new base station made, you should choose Difference.
5. Click OK to create the comparison. The comparison in Figure 11.25, shows clearly the area covered only by the
new site.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how modifying transmitter tilt can improve coverage.
A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by
Transmitter" on page 636. The results are displayed in Figure 11.26. The coverage prediction shows that one transmitter
is covering its area poorly. The area is indicated with a red oval in the figure.
You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed
by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and
electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue.
Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it would be
impossible to compare the results. Instead, the original coverage prediction by can be copied by selecting Duplicate from
its context menu. The copy is then calculated, to show how modifying the antenna tilt has affected coverage (see
Figure 11.27).
As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change
in coverage, you can compare the two predictions.
To compare two predictions:
1. Right-click one of the two predictions. The context menu appears.
2. From the context menu, select Compare with and, from the menu that opens, select the coverage prediction you
want to compare with the first. The Comparison Properties dialogue appears.
3. Click the General tab. You can change the Name of the comparison and add Comments.
The General tab contains information about the coverage predictions being compared, including their name and
resolution.
4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes modifying the antenna tilt made, you can choose Union. This will display all pixels
covered by both predictions in one colour and all pixels covered by only one prediction in another colour. The
increase in coverage, seen in only the second coverage prediction, will be immediately clear.
5. Click OK to create the comparison. The comparison in Figure 11.28, shows clearly the increase in coverage due
at the change in antenna tilt.
In this section, the CDMA-specific coverage predictions will be calculated using reverse link load factor and forward link
total power parameters defined at the cell level. For the purposes of these studies, each pixel is considered a non-inter-
fering user with a defined service, mobility type, and terminal.
Before making a prediction, you will have to set the reverse link load factor and forward link total power and the parameters
that define the services and users. These are explained in the following sections:
"Setting the Reverse Link Load Factor and the Forward Link Total Power" on page 647.
"Service and User Modelling" on page 647.
Several different types of CDMA-specific coverage predictions are explained in this section. The following quality studies
are explained:
"Making a Pilot Signal Quality Prediction" on page 653
"Studying Service Area (EbNt) Uplink and Downlink for 1xRTT" on page 655
"Studying Service Area (EbNt) Reverse Link for EV-DO" on page 656
"Studying Effective Service Area" on page 657.
The following noise studies, also coverage predictions, are explained:
"Studying Forward Link Total Noise" on page 659
"Calculating Pilot Pollution" on page 660.
Another type of coverage prediction, the handoff study, is also explained:
"Making a Handoff Status Coverage Prediction" on page 661.
You can also make a point analysis using the Point Analysis window. The analysis is calculated using reverse link load
factor and forward link total power parameters defined at the cell level and provided for a user-definable probe receiver
which has a terminal, a mobility and a service:
"Making an AS Analysis" on page 662.
You can define a RSCP threshold to further define how results are displayed. Atoll uses the RSCP threshold to calculate
coverage predictions and to make the AS analysis. Atoll checks which pixels have a pilot signal level which exceeds the
defined RSCP threshold. Defining the RSCP threshold is explained in the following section:
"Defining the RSCP Threshold" on page 653
Interferences coming from an external project can also be modelled and is explained in "Modelling Inter-Network Interfer-
ences" on page 236.
11.1.10.8.1 Setting the Reverse Link Load Factor and the Forward Link Total Power
If you are setting the reverse link load factor and the forward link total power for a single transmitter, you can set these
parameters on the Cells tab of the transmitters Properties dialogue. However, you can set the reverse link load factor
and the forward link total power for all cells using the Cells table.
To set the reverse link load factor and the forward link total power using the Cells table:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Open Table from the context menu. The Cells table appears.
4. Enter a value in the following columns:
- Total Power (dBm)
- UL Load Factor (%)
For a definition of the values, see "Cell Definition" on page 609.
5. To enter the same values in one column for all cells in the table:
a. Enter the value in the first row in the column.
b. Select the entire column.
c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
Note: You must define 1xEV-DO Rev. A radio bearers before you can model services using
them. For information on defining 1xEV-DO Rev. A radio bearers, see "The 1xEV-DO
Rev. A Radio Bearers" on page 718.
The CDMA2000 1xEV-DO Rev. 0 reverse link traffic channel allows five data rates. The CDMA2000 1xEV-DO Rev. A
reverse link traffic channel can have many more different data rates. In Atoll, the CDMA2000 1xEV-DO Rev. A traffic chan-
nels are modelled using radio bearers. You must define 1xEV-DO Rev. A radio bearers before you can model services
using them.
In this section, the following are explained:
"Modelling Services" on page 648
"Creating a Mobility Type" on page 651
"Modelling Terminals" on page 651.
Modelling Services
Services are the various services available to subscribers. CDMA2000 can provide voice using 1xRTT, and data using
1xRTT or 1xEV-DO.
This section explains how to create a service. The options available depend on the type of service you create.
Only the following parameters are used in coverage predictions:
Voice-specific parameters:
- Handoff capabilities
- Max TCH Power (dBm)
- UL Target (dB)
- DL Target (dB)
- Reception Equipment
- UL Pilot Threshold (dB)
- UL FCH/Pilot Offset (dB)
- Body loss
1xRTT-specific parameters:
- Handoff capabilities
- Max TCH Power (dBm)
- UL Target (dB)
- DL Target (dB)
- Reception Equipment
- UL Pilot Threshold (dB)
- UL FCH/Pilot Offset (dB)
- UL SCH/Pilot Offset (dB)
- Body loss
1xEV-DO-specific parameters:
- Body loss
To create or modify a service:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Parameters folder.
3. Right-click the Services folder. The context menu appears.
4. Select New from the context menu. The Services New Element Properties dialogue appears.
Note: You can modify the properties of an existing service by right-clicking the service in the
Services folder and selecting Properties from the context menu.
constant activity during connection. The activity factor is used to calculate the average power transmitted
on the FCH.
- Application Throughput: The application throughput is not used for services with the type Speech.
- Body Loss: Enter a body loss for the service. The body loss is the loss due to the body of the user. For
example, in a voice connection the body loss, due to the proximity of the users head, is estimated to be
3dB.
- 1xRTT Data: Only available for CDMA2000 projects. The following options are available for services with the
type 1xRTT Data:
- Preferred Carrier: Select the preferred carrier for the service. This is the carrier that will be used during
simulations, if the transmitter supports it. If the preferred carrier is not available, Atoll will choose another
carrier using the carrier selection mode defined in the site equipment properties.
- Priority: Enter a priority for the service. A priority of "0" gives the lowest priority. The priority is used during
simulations to decide which terminal will be rejected when the network is overloaded.
- Soft Handoff Allowed: Select the Soft Handoff Allowed check box if this service can have a soft hand-
off.
- Activity Factor FCH: Enter an activity factor for the FCH on the uplink (reverse link) and on the downlink
(forward link). The activity factor can be from "0," indicating no activity during connection, to "1," indicating
constant activity during connection. The activity factor is used to calculate the average power transmitted
on the FCH.
- Application Throughput: The application throughput is not used for services with the type Speech.
- Rate Probabilities SCH: Under Rate Probabilities SCH, you can enter the probability of the service
having the specified rate, from 2 to 16 times the nominal rate (defined in the terminal properties), on the
uplink (reverse link) and on the downlink (forward link). The sum of the probabilities must be lower than or
equal to 1. The rate probabilities are used during simulations to determine the throughput requested by
each user.
- Body Loss: Enter a body loss for the service. The body loss is the loss due to the body of the user. For
example, in a voice connection the body loss, due to the proximity of the users head, is estimated to be
3dB.
- 1xEV-DO Rev. 0 Data: Only available for CDMA2000 projects. The following options are available for services
with the type 1xEV-DO Rev. 0 Data:
- Preferred Carrier: Select the preferred carrier for the service. This is the carrier that will be used during
simulations, if the transmitter supports it. If the preferred carrier is not available, Atoll will choose another
carrier using the carrier selection mode defined in the site equipment properties.
- Priority: Enter a priority for the service. A priority of "0" gives the lowest priority. The priority is used during
simulations to decide which terminal will be rejected when the network is overloaded.
- Downgrading Supported: Select the Downgrading Supported check box if the service supports down-
grading on the reverse link.
- Application Throughput: Under Application Throughput, enter a Scaling Factor between the appli-
cation throughput and the RLC (Radio Link Control) throughput and a throughput Offset in kilobits per
second. The application throughput is calculated by multiplying the RLC throughput by the scaling factor
and subtracting the offset.
- Rate Probabilities UL: Under Rate Probabilities UL, you can enter the probability of the service having
the specified rate on the reverse link. The sum of the probabilities of the service having the specified rate
must be lower than or equal to 1. The rate probabilities are used during simulations to determine the
throughput requested by each user.
If the service supports rate downgrading, you can define the probability of the service being upgraded or
downgraded on the uplink (reverse link) for each 1xEV-DO Rev. 0 data rates. The probabilities are taken
into account during the uplink load control part of simulations in order to determine if a user with a certain
rate can be upgraded or downgraded. User rate downgrading and upgrading occurs when the cell is over-
or underloaded.
The following table shows the data rate changes that are possible when a data rate is upgraded or down-
graded. The probabilities are defined with a number from 1 to 255 for each rate.
Note: If you want the algorithm to process 1xEV-DO Rev. 0 users as in previous versions of
Atoll (i.e., downgrading 1xEV-DO Rev. 0 users with the highest rates, upgrading
1xEV-DO Rev. 0 users with the lowest rates) during uplink load control, you must enter
255 as the probability for each 1xEV-DO Rev. 0 data rate.
- UL Throughput Due to TCP Acknowledgement: If the Transmission Control Protocol (TCP) is used on
the downlink (forward link), check the TCP Used check box. When TCP is used, reverse link traffic due to
acknowledgements is generated. The traffic generated is calculated using the graph which describes the
reverse link traffic due to TCP acknowledgements as a function of the forward link application throughput.
The generated traffic is taken into account in simulation during the reverse link power control.
- Body Loss: Enter a body loss for the service. The body loss is the loss due to the body of the user. For
example, in a voice connection the body loss, due to the proximity of the users head, is estimated to be
3dB.
- 1xEV-DO Rev. A Data: Only available for CDMA2000 projects. The following options are available for serv-
ices with the type 1xEV-DO Rev. A Data:
- Uplink Mode: The Uplink Mode describes the type of radio resource management required on uplink for
that service. Select either "Low Latency" for real-time applications, or "High Capacity" for non-real-time
applications
- Preferred Carrier: Select the preferred carrier for the service. This is the carrier that will be used during
simulations, if the transmitter supports it. If the preferred carrier is not available, Atoll will choose another
carrier using the carrier selection mode defined in the site equipment properties.
- Priority: Enter a priority for the service. A priority of "0" gives the lowest priority. The priority is used during
simulations to decide which terminal will be rejected when the network is overloaded.
- Downgrading Supported: Select the Downgrading Supported check box if the service supports down-
grading on the reverse link.
- Application Throughput: Under Application Throughput, enter a Scaling Factor between the appli-
cation throughput and the RLC (Radio Link Control) throughput and a throughput Offset in kilobits per
second. The application throughput is calculated by multiplying the RLC throughput by the scaling factor
and subtracting the offset.
- Rate Probabilities UL: Under Rate Probabilities UL, you can enter the probability of the service having
the specified rate. In the column marked with the New Column icon ( ), select a Radio Bearer Index
and enter a Usage Probability. Atoll automatically creates a new blank column. The sum of the proba-
bilities must be lower than or equal to 1. The rate probabilities are used during simulations to determine
the throughput requested by each user. If the bearer is not defined under Rate Probabilities UL, it is
assumed that there are no users using the bearer.
- UL Throughput Due to TCP Acknowledgement: If the Transmission Control Protocol (TCP) is used on
the downlink (forward link), check the TCP Used check box. When TCP is used, reverse link traffic due to
acknowledgements is generated. The traffic generated is calculated using the graph which describes the
reverse link traffic due to TCP acknowledgements as a function of the forward link application throughput.
The generated traffic is taken into account in simulation during the reverse link power control.
- Body Loss: Enter a body loss for the service. The body loss is the loss due to the body of the user. For
example, in a voice connection the body loss, due to the proximity of the users head, is estimated to be
3dB.
8. If you selected "1xEV-DO Rev. 0 Data" or "1xEV-DO Rev. A Data" as the Type in step 5., continue to step 9. If
you selected "Speech" or "1xRTT Data" as the Type in step 5., an additional tab, the EbNt tab, is available.
Click the EbNt tab. In the EbNt tab, you must define each possible combination of radio configuration and SCH
factor. The SCH factor is the multiplying factor of the terminal nominal rate used to calculate the data rate. The
following table lists the SCH factors available and the corresponding data rates.
For each combination, you must define the thresholds, targets, and gains:
- UL Pilot Threshold (dB): Enter the pilot EcNt required on the reverse link. The value defined for the UL Pilot
Threshold is only used when the reverse link power control is based on pilot quality as set on the Global
Parameters tab of the Transmitters Properties dialogue.
- UL FCH/Pilot Offset (dB): Enter the FCH gain on the reverse link relative to the pilot. The value defined for
the UL FCH/Pilot Offset is only used when the reverse link power control is based on pilot quality as set on
the Global Parameters tab of the Transmitters Properties dialogue.
- UL SCH/Pilot Offset (dB): Enter the SCH gain on the reverse link relative to the pilot. The value defined for
the UL SCH/Pilot Offset is only used when the reverse link power control is based on pilot quality as set on
the Global Parameters tab of the Transmitters Properties dialogue. This value is not used for services of
Type "Speech."
- Mobility: Select the mobility type for which the thresholds, targets, and gains are defined. If you leave it blank,
the thresholds, targets, and gains will be considered valid for all mobility types.
9. Click OK.
In CDMA, information about receiver mobility is important to efficiently manage the active set: a mobile used by someone
travelling a certain speed and a mobile used by a pedestrian will not necessarily be connected to the same transmitters.
EcI0 requirements and the Ec/Nt threshold (used only by 1xEV-DO Rev 0) are largely dependent on mobile speed.
The following parameters are used in coverage predictions:
Delta Min. Ec/I0
Delta T_Drop
Min. EcNt (UL)
To create or modify a mobility type:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Parameters folder.
3. Right-click the Mobility Types folder. The context menu appears.
4. Select New from the context menu. The Mobility Types New Element Properties dialogue appears.
Note: You can modify the properties of an existing mobility type by right-clicking the mobility
type in the Mobility Types folder and selecting Properties from the context menu.
5. You can enter or modify the following parameters in the Mobility Types New Element Properties dialogue:
- Name: Enter or modify the descriptive name for the mobility type.
- Under Active Set Management, enter or modify the following parameters in order to make the user active set
dependent on the mobility type:
- Delta Min. EcI0: Enter a positive value in order to increase the minimum EcI0 required from a transmitter
to be the best server in the active set, or a negative value to decrease it.
- Delta T_Drop: Enter a positive value in order to increase the minimum EcI0 required from a transmitter
not to be rejected from the active set, or a negative value to decrease it.
- Under 1xEV-DO (Rev 0), enter or modify the following parameters:
- Min. EcNt (UL): Enter or modify the minimum EcNt required on the reverse link. This parameter is only
used for CDMA2000 1xEV-DO Rev 0. This parameter is considered during reverse link power control in
order to calculate the required reverse link pilot power.
- Max Rate = f(CI) (Rev 0): The graph of the data rate on the forward link as a function of (CI). This param-
eter is only used for CDMA2000 1xEV-DO Rev 0.
6. Click OK.
Modelling Terminals
In CDMA, a radio configuration is the user equipment that is used in the network, for example, a mobile phone, a PDA, or
a cars on-board navigation device. In Atoll, radio configurations are modelled using terminals.
The following parameters are used in coverage predictions:
Reception equipment
Main and secondary bands
Maximum terminal power
Gain and losses
Noise figures
Rho factor
Voice and 1xRTT-specific parameters:
- Active set size on FCH and SCH
- Number of fingers
- DL rake factor
- Pilot power percentage
- Nominal rate
1xEV-DO Rev. 0-specific parameters:
- Acknowledgement (ACK) channel gain
- Data Rate Control (DRC) channel gains
- Data channel gains
1xEV-DO Rev. A-specific parameters:
- Acknowledgement (ACK) channel gain
- Radio Reverse Indicator (RRI) channel gain
- Data Rate Control (DRC) channel gains
- Data channel and Auxiliary pilot gains
To create or modify a terminal:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Parameters folder.
3. Right-click the Terminals folder. The context menu appears.
4. Select New from the context menu. The Terminals New Element Properties dialogue appears.
Note: You can modify the properties of an existing terminal by right-clicking the terminal in the
Terminal folder and selecting Properties from the context menu.
5. Click the General tab. You can modify the following parameters:
- Name: You can change the name of the terminal.
- Type: You can change the type of equipment.
- Reception Equipment: Select a type of reception equipment from the list. You can create a new type of
reception equipment by opening the Reception Equipment table. To open the Reception Equipment table,
right-click the Terminals folder in the CDMA/CDMA2000 Parameters folder on the Data tab and select
Reception Equipment from the context menu.
- Main Band: Select the frequency band with which the terminal is compatible and enter the terminal Noise
Figure for the main frequency.
- Secondary Band: Select a second frequency band with which the terminal is compatible and enter the ter-
minal Noise Figure for the second frequency. Leave the Secondary Band field empty if the terminal works
only on one frequency band.
Note: There are two different ways of defining dual-band terminals. Depending on the
configuration, Atoll processes dual-band terminal users differently in the Monte-Carlo
simulation.
- The first one consists of defining main and secondary frequency bands. This enables
you to give a higher priority to one frequency band in the Monte-Carlo simulation (the
main frequency band will have the higher priority). A user with such a dual-band termi-
nal will be connected to transmitters using the main frequency band if carriers on this
frequency band are not overloaded. In case of overloading, he will be connected to
transmitters using the secondary frequency band.
- The second consists of selecting "All" as main frequency band. This means that the
terminal works on any frequency band without any priority. In this case, the user can
be connected to transmitters using any frequency band.
In coverage predictions, both configurations give the same results. The priority of frequen-
cy bands is not taken into account.
- Min. Power: Set the minimum transmission power. The minimum and maximum transmission power make up
the dynamic range for reverse link power control in simulations.
- Max Power: Set the maximum transmission power.
- Gain: Set the antenna gain.
- Losses: Set the reception losses.
- Noise Figure: Set the terminal noise figure.
- Rho factor (%): This parameter enables Atoll to take into account the self-interference produced by the ter-
minal. Because hardware equipment is not perfect, the input signal experiences some distortion which affects,
in turn, the output signal. This factor defines how much distortion the system generates. Entering 100% means
the system is perfect (there is no distortion) and the output signal will be 100% equal to the input signal. On
the other hand, if you specify a value different than 100%, Atoll considers that the transmitted energy is not
100% signal and contains a small percentage of interference generated by the equipment, i.e., self-interfer-
ence. Atoll considers this parameter to calculate the signal to noise ratio in the reverse link.
6. Click the 1xRTT tab. You can modify the following parameters:
- DL Rake Factor: Set the forward link rake factor. This enables Atoll to model the rake receiver on the forward
link.
- Active Set Size: Set the active set size for both the fundamental channel (FCH) and the supplementary
channel (SCH). The active set size is the maximum number of transmitters to which a terminal can be con-
nected at one time.
Note: For EV-DO-capable terminals, the FCH active set size also determines the active set size
on the reverse link.
- Number of Fingers: Enter the maximum number of signals that the terminal can recombine. The value of this
field must be lower than the value of the active set size. The value in this field is the same for both FCH and
SCH.
- Nominal Rate: Set the nominal rate on both the Downlink and the Uplink.
- Pilot Power Percentage: Enter the percentage of the total mobile power that is dedicated to the reverse link
pilot power. This parameter is used during the reverse link power control (if based on traffic quality) in order
to calculate the mobile power.
7. Click the 1xEV-DO Rev 0 tab (available only for CDMA2000). The values on this tab are relative to the reverse link
pilot power. They are added to the required reverse link pilot power in order to calculate power on the ACK, DRC,
and traffic data channels. You can modify the following parameters:
- Acknowledgement Channel Gain: Enter the gain on the acknowledgement (ACK) channel.
- Data Rate Control Channel Gains (DRC): Under Data Rate Control Channel Gains (DRC), enter the gain
for the following handoff types: No Handoff, Softer, and Soft handoff.
- Data Channel Gains (dB): Under Data Channel Gains, enter the gain for each supported reverse link rate
on the traffic data channel.
8. Click the 1xEV-DO Rev A tab (available only for CDMA2000). The values on this tab are relative to the reverse
link pilot power. They are added to the required reverse link pilot power in order to calculate power on the ACK,
RRI, DRC, and traffic data channels. You can modify the following parameters:
- Acknowledgement Channel Gain: Enter the gain on the acknowledgement (ACK) channel.
- Radio Reverse Indicator (RRI) Channel Gain: Enter the gain on the radio reverse indicator channel.
- Data Rate Control Channel Gains (DRC): Under Data Rate Control Channel Gains (DRC), enter the gain
for the following handoff types: No Handoff, Softer, and Soft handoff.
- Data Channels/Auxiliary Pilot Gains: Under Data Channels/Auxiliary Pilot Gains, enter the gains on the
traffic data channel for both low latency and high capacity services and the gain on the auxiliary pilot channel
according to the radio bearer index. The auxiliary pilot is only used the highest rates.
9. Click OK.
Note: A table listing quality indicators (BER, BLER, etc.) to be analysed is available. Quality
studies proposed by Atoll depend on quality indicators specified in this table.
A pilot signal quality prediction enables you to identify areas where there is at least one transmitter whose pilot quality is
received sufficiently well to be added to the probe mobile active set.
Atoll calculates the best pilot quality received on each pixel. Then, Atoll compares this value to the EcI0 threshold
required to be the best server (Min Ec/I0 defined for the given cell plus the Delta Min Ec/I0 value defined for the selected
mobility type). The pixel is coloured if the condition is fulfilled (in other words, if the best EcI0 is higher than the EcI0 thresh-
old.
To make a pilot signal quality prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Pilot Reception Analysis (Ec/I0) and click OK. The coverage prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 647. You
must also select which Carrier is to be considered.
If you want the pilot signal quality prediction to consider shadowing, you can select the Shadowing taken into
account check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
Figure 11.29: Load condition settings for a coverage prediction on pilot quality
- Where at least one transmitter is in the active set: Select "Unique" as the Display Type.
- Where at least one transmitter is in the active set, with information on the best server: Select "Discrete
Value" as the Display Type and "Transmitter" as the Field.
- The pilot quality relative to the EcI0 threshold: Select "Value Intervals" as the Display Type and "EcI0
Margin (dB)" as the Field.
8. Click OK to save your settings.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the pilot signal quality prediction. The progress
of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Atoll calculates the traffic channel quality on FCH (as defined by EbNt) when using the maximum power allowed.
In the coverage prediction, the forward link service area is limited by the maximum traffic channel power allowable on FCH
per cell and by the pilot quality. The reverse link service area is limited by the maximum terminal power allowable on FCH
and by the pilot quality. On both the forward and reverse links, if the received pilot is below the set threshold on a given
pixel, Atoll will not display the traffic channel quality. Mobile macro-diversity is taken in consideration to evaluate the traffic
channel quality (EbNt). Atoll combines the signal from each transmitter in the probe mobile active set.
To make a coverage prediction on service area (Eb/Nt) forward link or reverse link:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select one of the following studies and click OK:
- Service Area (Eb/Nt) Uplink
- Service Area (Eb/Nt) Downlink
The coverage prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a 1xRTT-capable Terminal, a 1xRTT Service, and a Mobility, as defined in "Service and User
Modelling" on page 647. You must also select a 1xRTT Carrier.
If you want the service area (EbNt) coverage prediction to consider shadowing, you can select the Shadowing
taken into account check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- The traffic channel quality relative to the EbNt threshold: Select "Value Intervals" as the Display Type
and "EbNt Margin (dB)" as the Field.
- The power required to reach the EbNt threshold: Select "Value Intervals" as the Display Type and
"Required Power (dB)" as the Field.
- Where traffic channel quality exceeds the EbNt threshold for each mobility type: On the Condition tab,
select "All" as the Mobility Type. The parameters on the Display tab are automatically set.
- The throughput on the forward or reverse link: Select "Discrete values" as the Display Type and "Rate
(Kbps)" as the Field.
8. Click OK to save your settings.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the service area (EbNt) coverage prediction.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Atoll calculates the pilot channel quality (as defined by EcNt) and, using the calculated EcNt, Atoll calculates the maxi-
mum data rate that can be supplied.
To make a forward link EV-DO throughput coverage prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Service Area (Eb/Nt) Downlink and click OK. The coverage prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select an EV-DO-capable Terminal, an EV-DO Service, and a Mobility, as defined in "Service and
User Modelling" on page 647. You must also select an EV-DO Carrier.
If you want the coverage prediction to calculate and display the average EV-DO Rev. A throughput on the forward
link, select an EV-DO Rev. A-capable Terminal and an EV-DO Rev. A Service. Atoll will calculate and display
the average EV-DO Rev. A throughput on the forward link using the early termination probabilities, defined in the
terminals reception equipment, to model HARQ (Hybrid Automatic Repeat Request.)
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
7. Click the Display tab.
By default, the Display Type "Value Intervals" based on the Field "Max EbNt (dB)" is selected when you make a
service area (Eb/Nt) coverage prediction. For a forward link EV-DO throughput coverage prediction, you can,
however, change the display to one of the following:
- The EcNt ratio: Select "Value Intervals" as the Display Type and "CI (dB)" as the Field.
- The throughput on the forward link: Select "Discrete values" as the Display Type and "Rate (Kbps)" as the
Field.
- The average EV-DO Rev. A throughput on the forward link: Select "Discrete values" as the Display Type
and "Average Rate (Kbps)" as the Field.
For information on defining display properties, see "Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the service area (EbNt) coverage prediction.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Atoll calculates the reverse link EV-DO traffic channel quality (EbNt) with an uplink data channel rate of 9.6 kbps. The
service area is limited by the maximum terminal power allowed and by the pilot quality. Mobile macro-diversity is taken in
consideration to evaluate the traffic channel quality (EbNt). Atoll combines the signal from each transmitter in the probe
mobile active set.
To make a coverage prediction on service area (Eb/Nt) reverse link:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Service Area (Eb/Nt) Uplink and click OK. The coverage prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select an EV-DO-capable Terminal, an EV-DO Service, and a Mobility, as defined in "Service and
User Modelling" on page 647. You must also select an EV-DO Carrier.
If you want the coverage prediction to calculate and display the average EV-DO Rev. A throughput, select an
EV-DO Rev. A-capable Terminal and an EV-DO Rev. A Service. Atoll will calculate and display the average
EV-DO Rev. A throughput using the early termination probabilities defined in the terminals reception equipment
to model HARQ (Hybrid Automatic Repeat Request).
If you want the service area (EbNt) coverage prediction to consider shadowing, you can select the Shadowing
taken into account check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the service area (EbNt) coverage prediction.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
The effective service area is the intersection zone between the pilot reception area, and the reverse link and forward link
service areas. In other words, the effective service area prediction calculates where a service actually is available for the
probe mobile.
To make an effective service area prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Effective Service Area and click OK. the coverage prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 647. You
must also select which Carrier is to be considered.
If you want the effective service area prediction to consider shadowing, you can select the Shadowing taken into
account check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the effective service area prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
You can create a quality study based on a given quality indicators (BER, BLER, or FER). The coverage prediction will show
for each pixel the measurement of the selected quality indicator.
This type of coverage prediction is not available in the list of standard studies; you can, however, use quality indicators in
a study by first ensuring that the parameters of the quality indicators have been correctly set and then creating a coverage
prediction, selecting display parameters that use these quality indicators.
Before you define the quality study, you must ensure that the parameters of the quality indicators have been correctly set.
To check the parameters of the quality indicators:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Parameters folder.
3. Right-click the Services folder. The context menu appears.
4. Select Quality Indicators from the context menu. The Quality Indicators table appears.
For each quality indicator in the Name column, you can set the following parameters:
- Used for Packet Services: Select the Used for Packet Services check box if the quality indicator is to be
used for data services (i.e., 1xRTT, 1xEV-DO Rev. 0, or 1xEV-DO Rev. A).
- Used for Circuit Services: Select the Used for Circuit Services check box if the quality indicator is to be
used for voice services.
- Measured Parameter for QI: From the list, select the parameter that will be measured to indicate quality.
- QI Interpolation: Select the QI Interpolation check box if you want Atoll to interpolate between two existing
QI values. Clear the QI Interpolation check box if you want Atoll to take the closest QI value.
5. Close the Quality Indicators table.
6. In the CDMA/CDMA2000 Parameters folder, right-click the Terminals folder. The context menu appears.
7. Select Reception Equipment from the context menu. The Reception Equipment table appears.
"Standard" is the default reception equipment type for all terminals.
8. Double-click the reception equipment type for which you want to verify the correspondence between the measured
quality and the quality indicator. The reception equipment types Properties dialogue appears.
9. Click the Quality Graphs tab.
10. Ensure that a Quality Indicator has been chosen for each Service. You can edit the values in the DL and UL
Quality Indicator Tables by clicking directly on the table entry, or by selecting the Quality Indicator and clicking
the Downlink Quality Graphs or the Uplink Quality Graphs buttons. The graph gives the variation of the quality
indicator as a function of the measured parameter.
11. Click OK to close the reception equipment types Properties dialogue.
Once you have ensured that the parameters of the quality indicators have been correctly set, you can use the measured
quality to create a quality study. How you define a coverage prediction according to the measured quality indicator,
depends several parameters:
The settings made in the Quality Indicators table
The service you want to study
The quality indicator you want to use (BER, BLER, or FER)
The coverage prediction you want to use (Pilot Reception Analysis, the Service Area Downlink, or Service Area
Uplink).
In the following example, you will create a quality study showing BLER, for a user on foot, and with a 1xRTT data service.
To create a quality study showing BLER for a user on foot, and with a 1xRTT data service:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Service Area (EbNt) Downlink and click OK. The coverage prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 11.29).
Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on
load conditions taken from a simulation. Atoll will calculate the coverage prediction using the reverse link load
factor and the forward link total power defined in the cell properties.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
- Terminal: Select the appropriate radio configuration for mobile Internet access from the Terminal list.
- Service: Select "1xRTT Data" from the Service list.
- Mobility: Select "Pedestrian" from the Mobility list.
- Carrier: Select "1xRTT" from the Carrier list.
If you want the service area (EbNt) downlink prediction to consider shadowing, you can select the Shadowing
taken into account check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the effective service area prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Atoll calculates for each pixel the forward link traffic channel quality (EbNt) (provided when using the maximum traffic
channel power allowed). Then, it calculates the corresponding BLER value from the quality graph (BLER=f(DL EbNt)).
The pixel is coloured if the condition is fulfilled (i.e., if BLER is evaluated as being higher than the specified threshold).
In the forward link total noise prediction, Atoll calculates and displays the areas where the forward link total noise or the
forward link noise rise exceeds a set threshold.
To make a forward link total noise or forward link noise rise prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Downlink Total Noise and click OK. the coverage prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on
load conditions taken from a simulation. Atoll will calculate the coverage prediction using the reverse link load
factor and the forward link total power defined in the cell properties.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 647.
If you want the forward link total noise or forward link noise rise prediction to consider shadowing, you can select
the Shadowing taken into account check box and enter a percentage in the Cell Edge Coverage Probability
text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the forward link total noise or forward link noise
rise prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
A transmitter which fulfils all the criteria to enter a mobiles active set but which is not admitted because the active set limit
has already been reached is considered a polluter.
In the pilot pollution prediction, Atoll calculates and displays the areas where the probe mobile is interfered by the pilot
signal from polluter transmitters. For 1xRTT, pilot pollution is the same on the forward and on the reverse links because
1xRTT can be connected to more than one transmitter on both the forward and on the reverse links. EV-DO, on the other
hand, can only be connected to one transmitter on the forward link, but several on the reverse link. Therefore, pilot pollution
for EV-DO will be different on the forward link and on the reverse link. The pilot pollution coverage prediction only calcu-
lates pilot pollution on the forward link.
To make a pilot pollution prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Pilot Pollution and click OK. the coverage prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility as defined in "Service and User Modelling" on page 647. You
must also select which Carrier is to be considered.
If you want the pilot pollution prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the pilot pollution prediction. The progress of
the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 647.
If you want the forward link total noise or forward link noise rise prediction to consider shadowing, you can select
the Shadowing taken into account check box and enter a percentage in the Cell Edge Coverage Probability
text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage pre-
diction will display.
- To display the handoff status:
i. Select "Discrete Values" from the Display Type list.
ii. Select "Status" from the Field list. The coverage prediction will display the number of cells the probe mo-
bile is connected to and the number of sites these cells are located on.
- To display the number of potential active transmitters:
i. Select "Value Intervals" from the Display Type list.
ii. Select "Potential active transmitter nb" from the Field list. the coverage prediction will display the number
of potential active transmitters.
For information on defining display properties, see "Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the handoff status coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
1. Click the Point Analysis button ( ) on the toolbar. The Point Analysis Tool window appears (see
Figure 11.31).
2. Click the AS Analysis tab.
3. At the top of the AS Analysis tab, select "Cells Table" from Load Conditions.
4. If you are making an AS analysis to verify a coverage prediction, you can recreate the conditions of the coverage
prediction:
a. Select the same Terminal, Service, Mobility, Carrier, DL Rate, and UL Rate studied in the coverage predic-
tion.
If the coverage prediction was for 1xRTT, you must select "FCH" for both the DL Rate and UL Rate. If the
coverage prediction was for EV-DO, you must select "9.6 kbps" for the UL Rate.
b. Right-click the Point Analysis window and select Properties from the context menu. The Properties dia-
logue appears.
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and
select "EcI0" from the Shadowing Margin list.
- Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class.
c. Click OK to close the Properties dialogue.
Note: If you are making an AS analysis to make a prediction on a defined point, you can use the
instructions in this step to define a user.
5. Move the pointer over the map to make an active set analysis for the current location of the pointer.
As you move the pointer, Atoll indicates on the map which is the best server for the current position (see
Figure 11.30).
Information on the current position is given on the AS Analysis tab of the Point Analysis window. See
Figure 11.31 on page 663 for an explanation of the displayed information.
6. Click the map to leave the point analysis pointer at its current position.
To move the pointer again, click the point analysis pointer on the map and drag it to a new position.
7. Click the Point Analysis button ( ) on the toolbar again to end the point analysis.
Select the load conditions (DL Power Select the parameters of the probe user to
and UL Load from a simulation or be studied. Ec/I0 threshold to enter the active set
user-defined values) to use in this as best server (Min Ec/I0 as defined
analysis. in the serving cell + Delta Min Ec/I0 as
defined in the Mobility type).
The pilot reception in terms of active set components for the set Lower boundary of the The connection status (pilot and uplink
conditions. The active set is displayed in grey. Solid bars active set (T_Drop as and downlink traffic) for the current point.
indicate the cells which respect the active set constraints. Even defined for the serving cell
if more cells respect the constraints, the active set size is limited + Delta T_Drop as defined : successful connection
to the number defined in the terminal properties and is a function in the Mobility type)
of the current service. : failed connection
- Inter-carrier Neighbours: Cells defined as neighbours which perform handoff using a different carrier.
Inter-technology Neighbours: Inter-technology neighbours are cells defined as neighbours that use a tech-
nology other than CDMA.
In this section, the following are explained:
"Importing Neighbours" on page 664
"Defining Exceptional Pairs" on page 664
"Allocating Neighbours Automatically" on page 664
"Checking Automatic Allocation Results" on page 667
"Allocating and Deleting Neighbours per Cell" on page 670
"Checking the Consistency of the Neighbour Allocation Plan" on page 672
"Exporting Neighbours" on page 673.
4. In the row marked with the New Row icon ( ), select the cell for which you want to define neighbour constraints
from the Cell column.
5. From the Neighbour column, select the second cell of the exceptional pair.
6. In the Status column, select one of the following:
- Forced: The selected cell will always be a neighbour of the reference cell.
- Forbidden: The selected cell will never be a neighbour of the reference cell.
7. Click elsewhere in the table when you have finished creating the new exceptional pair.
Notes: You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology
Neighbours table. You can open this table by right-clicking the Transmitters folder and
selecting Cells > Neighbours > Intra-Technology Exceptional Pairs.
- Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by reference cell A
and possible neighbour cell B.
- Min. Ec/I0: Enter or modify the minimum EcI0 required from a transmitter to enter the active set as best
server.
- T_Drop: Enter or modify the minimum EcI0 required from a transmitter not to be rejected from the active
set.
- DL Load Contributing to I0: You can let Atoll base the interference ratio on the total power used as
defined in the properties for each cell (Defined per Cell) or on a percentage of the maximum power
(Global Value).
- Shadowing taken into account: If desired, select the Shadowing taken into account check box and
enter a Cell Edge Coverage Probability.
- Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses defined per
clutter class in the calculations.
- Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic
neighbour allocation.
- % Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cells coverage area must
overlap the reference cells coverage area.
5. Select the desired calculation parameters:
- Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers;
Atoll will allocate neighbours to cells using the selected carriers.
- Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want
cells located on the same site as the reference cell to be automatically considered as neighbours.
- Force adjacent cells as neighbours: Select the Force adjacent cells as neighbours check box if you want
cells that are adjacent to the reference cell to be automatically considered as neighbours. A cell is considered
adjacent if there is at least one pixel in the reference cells coverage area where the possible neighbour cell
is the best server, or where the possible neighbour cell is the second best server in the reference cells active
set.
- Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In
other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neigh-
bour list of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from
the list of neighbours of the reference cell.
- Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or
forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see
"Defining Exceptional Pairs" on page 664.
- Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete
all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check
box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new
neighbours to the list.
6. Click the Importance Weighting button to set the relative importance of possible neighbours:
- Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage
reasons.
- Adjacency Factor: If you have selected the Force adjacent cells as neighbours check box in step 5., set
the minimum and maximum importance of a possible neighbour cell being adjacent to the reference cell.
- Co-site Factor: If you have selected the Force co-site cells as neighbours check box in step 5., set the
minimum and maximum importance of a possible neighbour cell being located on the same site as reference
cell.
7. Click Run. Atoll begins the process of allocating intra-carrier neighbours. Atoll first checks to see whether the
path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates
them.
Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays
new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is
cleared, the Results table will be empty.
8. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atolls table
shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data
Tables" on page 50.
9. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neigh-
bours are listed in the Intra-technology Neighbours tab of each cells Properties dialogue.
To automatically allocate inter-carrier CDMA neighbours:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Neighbours > Automatic Allocation from the context menu. The Automatic Neighbour Alloca-
tion dialogue appears.
4. Click the Inter-Carrier Neighbours tab. You can set the following parameters:
- Max. Inter-site Distance: Set the maximum distance between the reference cell and a possible neighbour.
- Max. Number of Neighbours: Set the maximum number of inter-carrier neighbours that can be allocated to
a cell. This value can be either set here for all transmitters, or specified for each transmitter in the Cells table.
- Coverage Conditions: The coverage conditions must be respected for a cell to be considered as a neighbour.
Click Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the
following parameters:
- Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by reference cell A
and possible neighbour cell B.
- Margin: Enter the signal margin relative to the pilot signal of the reference cell A. See the Technical Refer-
ence Guide for an explanation of how the margin is used in different inter-carrier handoff scenarios.
- Shadowing taken into account: If desired, select the Shadowing taken into account check box and
enter a Cell Edge Coverage Probability.
- Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic
neighbour allocation.
- % Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cells coverage area must
overlap the reference cells coverage area.
5. Select the desired calculation parameters:
- Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers;
Atoll will allocate neighbours to cells using the selected carriers.
- Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want
cells located on the same site as the reference cell to be automatically considered as neighbours.
- Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In
other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neigh-
bour list of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from
the list of neighbours of the reference cell.
- Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or
forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see
"Defining Exceptional Pairs" on page 664.
- Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete
all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check
box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new
neighbours to the list.
6. Click the Importance Weighting button to set the relative importance of possible neighbours:
- Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage
reasons.
- Co-site Factor: If you have selected the Force co-site cells as neighbours check box in step 5., set the
minimum and maximum importance of a possible neighbour cell being located on the same site as reference
cell.
7. Click Run. Atoll begins the process of allocating inter-carrier neighbours. Atoll first checks to see whether the
path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates
them.
Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays
new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is
cleared, the Results table will be empty.
- Existing
- Coverage: The amount of reference cells coverage area that the neighbour overlaps, in percentage and in
square kilometres.
8. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atolls table
shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data
Tables" on page 50.
9. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neigh-
bours are listed in the Intra-technology Neighbours tab of each cells Properties dialogue.
Notes:
A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already
exists and the Delete existing neighbours check box is cleared when you start the new allo-
cation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint
on the forbidden neighbour will be ignored by the algorithm because the neighbour already
exists.
When the options Force exceptional pairs and Force symmetry are selected, Atoll con-
siders the constraints between exceptional pairs in both directions in order to respect sym-
metry. On the other hand, if the neighbour relation is forced in one direction and forbidden in
the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the
Event Viewer.
You can save automatic neighbour allocation parameters in a user configuration. For informa-
tion on saving automatic neighbour allocation parameters in a user configuration, see
"Exporting a User Configuration" on page 75.
1. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
2. Select Display Options from the context menu. The Visual Management dialogue appears.
3. Under Intra-technology Neighbours, select the Display Links check box.
4. Click the Browse button ( ) beside the Display Links check box.
Tip: You can display the number of handoff attempts for each cell-neighbour pair by first
creating a new field of Type "Integer" in the Intra-Technology Neighbour table for the
number of handoff attempts. Once you have imported or entered the values in the new
column, you can select this field from the Field list along with "Value Intervals" as the
Display Type. For information on adding a new field to a table, see "Adding a Field to an
Object Types Data Table" on page 51.
Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you
can display or hide neighbour link display types individually.
For information on changing display properties, see "Display Properties of Objects" on page 33.
7. Select the Add to Legend check box to add the displayed neighbour links to the legend.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each neighbour link.
9. Click OK to save your settings.
10. Under Advanced, select which neighbour links to display:
- Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations
where the selected cell is the reference cell and where the neighbour relation is not symmetric.
- Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations
where the selected cell is neighbour and where the neighbour relation is not symmetric.
- Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the
selected cell and the neighbour.
11. Click OK to save your settings.
12. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
- The symmetric neighbour relations of the selected (reference) cell are indicated by a line.
- The outward neighbour relations are indicated with a line with an arrow pointing at the neighbour (e.g. see
Site1_2(0)) in Figure 11.32.).
- The inward neighbour relations are indicated with a line with an arrow pointing at the selected cell (e.g. see
Site9_3(0)) in Figure 11.32.).
In Figure 11.32, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward
neighbour links are coloured as the corresponding neighbour transmitters and the inward neighbour link is
coloured as the reference transmitter as it is neighbour of Site9_3(0) here.
In Figure 11.33, neighbour links are displayed according to the neighbour carrier. You can view intra-carrier and
inter-carrier neighbour links. Here, all neighbour relations are symmetric.
Note: You can display either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting
either Forced Neighbours or Forbidden Neighbours.
2. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
3. Select Display Options from the context menu. The Visual Management dialogue appears.
4. Under Intra-technology Neighbours, select the Display Coverage Areas check box.
5. Click the Browse button ( ) beside the Display Coverage Areas check box.
6. The Intra-technology Neighbour Display dialogue appears.
7. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage area of a cells neigh-
bours with a unique colour.
- Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you
want Atoll to colour the coverage area of a cells neighbours according to a value from the Intra-technology
Neighbours table.
- Value Intervals: Select "Value Intervals" to colour the coverage area of a cells neighbours according the
value interval of the value selected from the Field list. For example, you can choose to display a cells neigh-
bours according to their rank, in terms of automatic allocation, or according to the importance, as determined
by the weighting factors.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each coverage area.
9. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( ) in the
Radio toolbar.
Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete CDMA neighbours using the Cells tab of the transmitters Properties dialogue:
1. On the map, right-click the transmitter whose neighbours you want to change. The context menu appears.
2. Select Properties from the context menu. The transmitters Properties dialogue appears.
3. Click the Cells tab.
4. On the Cells tab, there is a column for each cell. Click the Browse button ( ) beside Neighbours in the cell for
which you want to allocate or delete neighbours. The cells Properties dialogue appears.
5. Click the Intra-technology Neighbours tab.
6. To allocate a new neighbour:
a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon
( ).
b. Click elsewhere in the table to complete creating the new neighbour.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
9. To delete a neighbour:
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Press DEL to delete the neighbour.
10. Click OK.
Note: For information on working with data tables, see "Working with Data Tables" on page 50.
4. To allocate a neighbour:
a. In the row marked with the New Row icon ( ), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column.
c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
5. To create a symmetric neighbour relation:
a. Right-click the neighbour in the Neighbour column. The context menu appears.
b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the
Neighbour column and the cell in the Cell column.
6. To make several neighbour relations symmetric:
a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select
contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contig-
uous rows by pressing CTRL and clicking each rows separately.
b. Right-click the Neighbours table. The context menu appears.
c. Select Symmetrise from the context menu.
7. To take into consideration all exceptionnal pairs:
a. Right-click the Neighbours table. The context menu appears.
b. Select Force Exceptional Pairs from the context menu.
Note: You can add or delete either some forced neighbours or some forbidden neighbours using
the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table,
select the exceptional pairs to be considered, right-click the table and select Force
Exceptional Pairs in the context menu.
You can allocate or delete intra-technology neighbours directly on the map using the mouse.
To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neigh-
bours on the map as explained in "Displaying Neighbour Relations on the Map" on page 667.
To add a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters
to the intra-technology neighbours list.
To remove a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both trans-
mitters from the intra-technology neighbours.
To add an outward neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference
transmitter to the intra-technology neighbour list of the reference transmitter.
To remove an outward neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference
transmitter from the intra-technology neighbours list of the reference transmitter.
To add an inward neighbour relation:
Click the reference transmitter on the map. Atoll displays its neighbour relations.
- If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other trans-
mitter. Atoll converts the symmetric relation to an inward non-symmetric inter-technology neighbour relation.
- If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour rela-
tion between the two transmitters, and then press CTRL and click the other transmitter. Atoll converts the
symmetric relation to an inwards non-symmetric inter-technology neighbour relation.
To remove an inwards neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the trans-
mitter from the intra-technology neighbours list of the reference transmitter.
Notes:
When there is more than one cell on the transmitter, clicking the transmitter in the map window
opens a context menu allowing you to select the cell you want (see "Selecting One of Several
Transmitters or Microwave Links" on page 30).
You can add or delete either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting either
Forced Neighbours or Forbidden Neighbours.
- Missing Co-sites: Select the Missing Co-sites check box if you want to verify which cells have no co-site
neighbours.
- Missing Symmetrics: Select the Missing Symmetrics check box if you want to verify which cells have non-
symmetric neighbour relations.
- Exceptional Pairs: Select the Exceptional Pairs check box if you want to verify which cells have forced
neighbours or forbidden neighbours.
5. Click OK to perform the audit. Atoll displays the results of the audit in a new text file:
- Average Number of Neighbours: X; where, X is the average number of neighbours (integer) per cell for the
plan audited.
- Empty Lists: x/X; x number of cells out of a total of X having no neighbours (or empty neighbours list)
Syntax: |CELL|
- Full Lists (default max number = Y): x/X; x number of cells out of a total of X having Y number of neighbours
listed in their respective neighbours lists.
Syntax: |CELL| |NUMBER| |MAX NUMBER|
- Lists > Max Number (default max number = Y): x/X; x number of cells out of a total of X having more than
Y number of neighbours listed in their respective neighbours lists.
Syntax: |CELL| |NUMBER| |MAX NUMBER|
- Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
- Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
Note: Within the context of PN offset allocation, "neighbours" refer to intra-carrier neighbours.
4. In the row marked with the New Row icon ( ), select one cell of the new exceptional pair in the Cell column
and the second cell of the new exceptional pair from the Cell_2 column.
5. Click in another cell of the table to create the new exceptional pair and add a new blank row to the table.
You can define the costs of the different types of constraints used in the automatic PN offset allocation algorithm.
To define the different constraint costs:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > PN Offsets > Constraint Costs. The Allocation Constraint Costs dialogue appears. In this dia-
logue you can define the following costs of constraint violations for the automatic allocation process (the cost is a
value from 0 to 1):
- Max 1st, 2nd, and 3rd Order Neighbours: Enter the maximum costs for 1st, 2nd, and 3rd order neighbour
constraint violations.
- Co-planning Share: Enter the cost for inter-technology neighbour constraint violations.
- Max Reuse Distance: Enter the maximum cost for reuse distance constraint violations.
- Exceptional Pair: Enter the cost for exceptional pair constraint violations.
4. Click OK. The allocation constraint costs are stored and will be used in the automatic allocation.
The allocation algorithm enables you to automatically allocate PN offsets to cells in the current network. You can choose
among several automatic allocation strategies (for more information, see the Technical Reference Guide):
PN Offset per Cell: The purpose of this strategy is to reduce the spectrum of allocated PN offsets the maximum
possible. Atoll will allocate the first possible PN offsets in the domain.
Adjacent PN-Clusters per Site: This strategy consists of allocating one cluster of adjacent PN offsets to each
base station, then, one PN offset of the cluster to each cell of each transmitter according to its azimuth. When all
the clusters have been allocated and there are still base stations remaining to be allocated, Atoll reuses the clus-
ters at another base station.
Distributed PN-Clusters per Site: This strategy consists of allocating one cluster of PN offsets to each base sta-
tion in the network, then, one PN offset of the cluster to each cell of each transmitter according to its azimuth. With
this strategy, the cluster is made of PN offsets separated as much as possible. When all the clusters have been
allocated and there are still base stations remaining to be allocated, Atoll reuses the clusters at another base sta-
tion.
Note: Within the context of PN offset allocation, the term "PN-cluster" refers to a sub-group of
PN offsets that Atoll assigns to base stations during the allocation process. Atoll allows
you to change the number of PN offsets in a PN-cluster.
The following example explains the difference between "Adjacent PN-clusters" and "Dis-
tributed PN-clusters".
The PILOT_INC has been set to 4 and the PN-cluster size to 3. There are:
- 128 PN offsets that can be allocated: they are from 4 to 508 with a separation interval
of 4.
- Each PN-cluster consists of three PN offsets. Therefore, there are 42 PN-clusters
available.
If you select "Adjacent PN-cluster per site" as allocation strategy, Atoll will consider PN-
clusters consisted of adjacent PN offsets (e.g., {4,8,12}, {16,20,24}, ..., {496,500,504}).
If you select "Distributed PN-cluster per site" as allocation strategy, Atoll will consider PN-
clusters consisted of PN offsets separated as much as possible (e.g., {4,172,340},
{8,176,344}, ..., {168,336,504}).
- Existing Neighbours: Select the Existing Neighbours check box if you want to consider intra-carrier
neighbour relations and then choose the neighbourhood level to take into account:
Neighbours of a cell are referred to as the first order neighbours, neighbours neighbours are referred to
as the second order neighbours and neighbours neighbours neighbours as the third order neighbours.
First Order: No cell will be allocated the same PN Offset as its neighbours.
Second Order: No cell will be allocated the same PN Offset as its neighbours or its second order neigh-
bours.
Third Order: No cell will be allocated the same PN Offset as its neighbours or its second order neighbours
or third order neighbours.
Atoll can only consider neighbour relations if neighbours have already been allocated. For information on
allocating neighbours, see "Planning Neighbours" on page 663.
Note: Atoll can take into account inter-technology neighbour relations as constraints when
allocating PN offsets to the CDMA2000 neighbours of a GSM transmitter. In order to
consider inter-technology neighbour relations in PN offset allocation, you must make the
Transmitters folder of the GSM Atoll document accessible in the CDMA2000 Atoll
document. For information on making links between GSM and CDMA2000 Atoll
documents, see "Creating a UMTS Sector From a GSM Sector" on page 226
- Additional Overlapping Conditions: Select the Additional Overlapping Conditions check box, if you
want to set overlapping coverage criteria. If cells meet the overlapping conditions to enter the reference
cells active set, they will be not allocated the same PN offset as the reference cell. Click Define to change
the overlapping conditions. In the Coverage Conditions dialogue, you can change the following param-
eters:
Min. Pilot Signal Level: Enter the minimum pilot signal level which must be provided by reference cell A
and possible neighbour cell B.
Min. EcI0: Enter the minimum EcI0 which must be provided by reference cell A in an area with overlap-
ping coverage. Reference cell A must also be the best server in terms of pilot quality in the area with over-
lapping coverage.
T_Drop: Enter or modify the minimum EcI0 required from a transmitter not to be rejected from the active
set.
DL Load Contributing to I0: You can let Atoll base the interference ratio on the total power used as de-
fined in the properties for each cell (Defined per Cell) or on a percentage of the maximum power (Global
Value).
Shadowing taken into account: If desired, select the Shadowing taken into account check box and
enter a Cell Edge Coverage Probability.
Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses defined per
clutter class in the calculations.
- Reuse Distance: Select the Reuse Distance check box if you want to the automatic allocation process
to consider the reuse distance constraint. Enter the Default reuse distance within which two cells on the
same carrier cannot have the same PN offset.
Note: A reuse distance can be defined at the cell level (in the cell Properties dialogue or in the
Cells table). If defined, a cell-specific reuse distance will be used instead of the value
entered here.
- Exceptional Pairs: Select the Exceptional Pairs check box if you want the automatic allocation process
to consider the exceptional pair constraints.
- Under Strategy, you can select an automatic allocation strategy:
- PN Offset per Cell
- Adjacent PN-Clusters per Site
- Distributed PN-Clusters per Site
- Carrier: Select the Carrier on which you want to run the allocation. You may choose one carrier (Atoll will
assign PN offsets to transmitters using the selected carrier) or all of them.
- PN-Cluster Size: The number of PN offsets per cluster. This parameter is used only by the Adjacent PN-Clus-
ters per Site and Distributed PN-Clusters per Site allocation strategies. It should correspond to the average
number of transmitters located on a site.
- Delete Existing PN Offsets: Select the Delete Existing PN Offsets check box if you want Atoll to delete
currently allocated PN offsets and recalculate all PN offsets. If you do not select this option, Atoll will keep
currently allocated PN offsets and will only allocate PN offsets to cells that do not yet have PN offsets allo-
cated.
- Allocate Carriers Identically: Select the Allocate Carriers Identically check box if you want Atoll to allocate
the same PN Offset to each carrier of a transmitter. If you do not select this option, Atoll allocates PN Offsets
independently for each carrier.
5. Click Run. Atoll begins the process of allocating PN offsets.
Once Atoll has finished allocating PN offsets, they are visible under Results. Atoll only displays newly allocated
PN offsets.
Note: You can save automatic PN offset allocation parameters in a user configuration. For
information on saving automatic PN offset allocation parameters in a user configuration,
see "Exporting a User Configuration" on page 75.
Tips:
If you need to allocate PN offsets to the cells on one transmitter, you can allocate them auto-
matically by selecting Allocate PN Offsets from the transmitters context menu.
If you need to allocate PN offsets to all the cells on group of transmitters, you can allocate them
automatically by selecting Cells > PN Offsets > Automatic Allocation from the transmitter
groups context menu.
When you allocate PN offsets to a large number of cells, it is easiest to let Atoll allocate PN offsets automatically, as
described in "Automatically Allocating PN Offsets to CDMA Cells" on page 674. However, if you want to add a PN offset
to one cell or to modify the PN offset of a cell, you can do it by accessing the properties of the cell.
In Atoll, you can search for PN offsets and PN offset groups using the Search Tool. Results are displayed in the map
window in red.
If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results
displayed by transmitter, the search results will be displayed by transmitter coverage. PN offsets and PN offset groups and
any potential problems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a
Coverage Prediction by Transmitter" on page 636.
To find PN offsets or PN offset groups using the Search Tool:
1. Create, calculate, and display a coverage prediction by transmitter. For information on coverage predictions by
transmitter, see "Making a Coverage Prediction by Transmitter" on page 636.
2. Click View > Search Tool. The Search Tool window appears.
The Search Tool window is a docking window. For information on docking windows, see "Docking or Floating an
Atoll Window" on page 26.
a. Select PN Offset.
b. Enter a PN offset in the text box.
You can use the display characteristics of transmitters to display PN offset-related information.
To display PN offset-related information on the map:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Display tab.
You can display the following information per transmitter:
- PN offset: To display the PN offset of a transmitters cell, select "Discrete values" as the Display Type and
"Cells: PN Offset" as the Field.
- Ranges of PN offsets: To display ranges of PN offsets, select "Value intervals" as the Display Type and
"Cells: PN Offset" as the Field.
- PN offset domain: To display the PN offset domain of a transmitters cell, select "Discrete values" as the Dis-
play Type and "Cells: PN Offset Domain" as the Field.
You can display the following information in the transmitter label or tooltip:
- PN offset: To display the PN offset of a transmitters cell in the transmitter label or tooltip, "Cells: PN Offset"
from the Label or Tip Text Field Definition dialogue.
- PN offset domain: To display the PN offset domain of a transmitters cell in the transmitter label or tooltip,
"Cells: PN Offset Domain" from the Label or Tip Text Field Definition dialogue.
5. Click OK.
For information on display options, see "Display Properties of Objects" on page 33.
You can group transmitters on the Data tab of the Explorer window by their PN offset or by their PN offset domain.
To group transmitters by PN offset:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the General tab, click Group by. The Group dialogue appears.
5. Under Available Fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
- PN Offset
- PN Offset Domain
7. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to
the list of parameters on which the transmitters will be grouped. For more information on grouping objects, see
"Advanced Grouping" on page 66.
8. Click OK to save your changes and close the Group dialogue.
Note: If a transmitter has more than one cell, Atoll cannot arrange the transmitter by cell.
Transmitters that cannot be grouped by cell are arranged in a separate folder under the
Transmitters folder.
You can use a histogram to analyse the use of allocated PN offsets in a network. The histogram represents the PN offsets
as a function of the frequency of their use.
You can make a PN offset interference zone prediction to view areas covered by cells using the same PN offset. Atoll
checks on each pixel if the best server and other servers satisfying the conditions to enter the user active set have the
same PN Offset. If so, Atoll considers that there is PN Offset interference.
To make a PN Offset interference zone prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select PN Offset Interference Zones and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, Service, and Mobility, as defined in "Service and User Modelling" on page 647. You
must also select which Carrier is to be considered.
If you want the PN Offset interference zone prediction to consider shadowing, you can select the Shadowing
taken into account check box and enter a percentage in the Cell Edge Coverage Probability text box.
You can also select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- The number of interferers for each transmitter: Select "Value Intervals" as the Display Type and "Number
of Interferers per Transmitter" as the Field. In the Explorer window, the coverage prediction results are
arranged by interfered transmitter.
- The total number of interferers on one pixel: Select "Value Intervals" as the Display Type and "Number of
Interferers" as the Field. In the Explorer window, the coverage prediction results are arranged according to
the number of interferers.
8. Click the Calculate button ( ) in the Radio toolbar to calculate the PN offset interference zone coverage pre-
diction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
The PN Offset Interference tab of the Point Analysis window gives you information on the reception for any point on the
map where there is PN Offset interference. PN Offset interference occurs when the best server and other servers satisfying
the conditions to enter the user active set have the same PN Offset. When there is PN Offset interference, Atoll displays
the pilot quality (EcI0) received from interfered and interferer transmitters.
Analysis is based on the UL load percentage and the DL total power of cells. The analysis is provided for a user-definable
probe receiver which has a terminal, a mobility and a service.
You can make a PN Offset interference analysis to review the PN Offset interference zone coverage prediction. In this
case, before you make the PN Offset interference analysis, you should ensure that the coverage prediction you want to
use in the PN Offset interference analysis is displayed on the map.
To make a PN Offset interference analysis:
1. Click the Point Analysis button ( ) on the toolbar. The Point Analysis Tool window appears.
2. Click the PN Offset Interference tab.
3. At the top of the PN Offset Interference tab, select "Cells Table" from Load Conditions.
4. If you are making a PN Offset interference analysis to verify a coverage prediction, you can recreate the conditions
of the coverage prediction:
a. Select the Terminal, Service, and Mobility studied in the coverage prediction.
b. Right-click the Point Analysis window and select Properties from the context menu. The Properties dia-
logue appears.
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability and
select "EcI0" from the Shadowing Margin list.
- Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class.
c. Click OK to close the Properties dialogue.
Note: If you are making a PN Offset interference analysis to make a coverage prediction on a
defined point, you can use the instructions in this step to define a user.
5. Move the pointer over the map to make a PN Offset interference analysis for the current location of the pointer.
6. Click the map to leave the point analysis pointer at its current position.
To move the pointer again, click the point analysis pointer on the map and drag it to a new position.
7. Click the Point Analysis button ( ) on the toolbar again to end the point analysis.
Mobility type: In CDMA, information about receiver mobility is important to efficiently manage the active set: a
mobile used by a driver moving quickly or a pedestrian will not necessarily be connected to the same transmitters.
EcI0 requirements and EbNt targets per radio bearer and per link (forward or reverse) are largely dependent on
mobile speed. For information on creating a mobility type, see "Creating a Mobility Type" on page 651.
Radio configuration: In CDMA, a radio configuration is the user equipment that is used in the network, for
example, a mobile phone, a PDA, or a cars on-board navigation device. In Atoll, radio configurations are modelled
using terminals. For information on creating a terminal, see "Modelling Terminals" on page 651.
Traffic map per user profile can be used if you have marketing-based traffic data.
Traffic maps per density of user profiles, where each vector (polygon, line or point) describes subscriber densities
(or numbers of subscribers for points) with user profiles and mobility types, and traffic maps per environment of
user profiles, where each pixel has an assigned environment class. For more information, see "Importing a Traffic
Map Based on Densities of User Profiles" on page 684, "Creating a Traffic Map Based on Environments of User
Profiles" on page 686, and "Importing a Traffic Map Based on Environments of User Profiles" on page 685.
Traffic maps per density (number of users per km2) can be used if you have population-based traffic data,
or 2G network statistics.
Each pixel has an actual user density assigned. Either the value includes all activity statuses, or it corresponds to
a particular activity status. For more information, see "Importing a Traffic Map per User Density" on page 686,
"Creating a Traffic Map per User Density" on page 687, "Converting 2G Network Traffic" on page 688 and "Export-
ing Cumulated Traffic" on page 688.
Note: Because each of the CDMA technologies has capabilities and services that are specific to
it, it is recommended to create a separate traffic map for:
- voice
- 1xRTT data
- EV-DO data
Note: You can also import a traffic map from a file by clicking the Import button. You can import
AGD (Atoll Geographic Data) format files that you have exported from an other Atoll
document.
7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter.
8. Enter the data required in the Map per Sector dialogue:
- If you have selected Throughputs in Uplink and Downlink, enter the throughput demands in the reverse
and forward links for each sector and for voice and each 1xRTT data service. As only one EV-DO data service
user is served at a time, all EV-DO users are considered as active in the forward link. Therefore, you can only
enter the throughput demand in the reverse link for each sector and for each EV-DO data service.
- If you have selected Total Number of Users (All Activity Statuses), enter the number of connected users
for each sector and for each listed service.
- If you have selected Number of Users per Activity Status, enter the number of inactive users, the number
of users active in the reverse link, in the forward link, and in the reverse and forward links, for each sector and
for voice and each 1xRTT data service. As only one EV-DO data service user is served at a time, all EV-DO
users are considered as active in the forward link. Therefore, you can only enter the number of inactive users
(in the reverse link) and the number of users active in the reverse link for each sector and for each EV-DO
data service.
Note: You can also import a text file containing the data by clicking the Actions button and
selecting Import Table from the menu. For more information on importing table data, see
"Importing Tables from Text Files" on page 59.
You can model variations in user behaviour by creating different profiles for different times of the day or for different circum-
stances. For example, a user may be considered a business user during the day, with video conferencing and voice, but
no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and
web browsing.
To create or modify a user profile:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Parameters folder.
3. Right-click the User Profiles folder. The context menu appears.
4. Select New from the context menu. The User Profiles New Element Properties dialogue appears.
Note: You can modify the properties of an existing user profile by right-clicking the user profile in
the User Profiles folder and selecting Properties from the context menu.
Note: In order for all the services defined for a user profile to be taken into account during traffic
scenario elaboration, the sum of activity probabilities must be lower than 1.
Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a
given density (i.e., the number of subscribers with the same profile per km). To get an appropriate user distribution, you
can assign a weight to each clutter class for each environment class. You can also specify the percentage of indoor
subscribers for each clutter class. In a Monte-Carlo simulation, an additional loss (as defined in the clutter class properties)
will be added to the indoor users path loss.
To create or modify a CDMA environment:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the CDMA/CDMA2000 Parameters folder.
3. Right-click the Environments folder. The context menu appears.
4. Select New from the context menu. The Environments New Element Properties dialogue appears.
Note: You can modify the properties of an existing environment by right-clicking the
environment in the Environments folder and selecting Properties from the context
menu.
7. In the row marked with the New Row icon ( ), set the following parameters for each user profile/mobility com-
bination that this CDMA environment will describe:
- User: Select a user profile.
- Mobility: Select a mobility type.
- Density (Subscribers/km2): Enter a density in terms of subscribers per square kilometre for the combination
of user profile and mobility type.
8. Click the Clutter Weighting tab.
9. For each clutter class, enter a weight that will be used to distribute users on the map.
The number of users per clutter class is calculated using the following equation:
Wk Sk
N k = N Area --------------------------
Wi Si
i
where:
For example: An area of 10 km with a subscriber density of 100/km. Therefore, in this area, there are 1000
subscribers. The area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1"
and for Building is "4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter
class and 800 in the Building clutter class.
10. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte-Carlo simu-
lation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue.
7. Select the file to import. The file must be in one of the following supported vector formats: DXF format (DXF), Atoll
Geographic Data File (AGD), ArcView format (SHP), MapInfo file (MIF or TAB), or Planet Data File (index).
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears.
11. Select the Traffic tab (see Figure 11.34). Under Traffic Fields, you can specify the user profiles to be considered,
their mobility type (kmh), and their density. If the file you are importing has this data, you can define the traffic
characteristics by identifying the corresponding fields in the file. If the file you are importing does not have data
describing the user profile, mobility, or density, you can assign values. When you assign values, they apply to the
entire map.
- User Profile: If you want to import user profile information from the file, under Defined, select "By field" and
select the source field from the Choice column. If you want to assign a user profile from the CDMA/
CDMA2000 Parameters folder of the Data tab, under Defined, select "By value" and select the user profile
in the Choice column.
- Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select
the source field from the Choice column. If you want to assign a mobility type from the CDMA/CDMA2000
Parameters folder of the Data tab, under Defined, select "By value" and select the mobility type in the Choice
column.
- Density: If you want to import density information from the file, under Defined, select "By field" and select the
source field from the Choice column. If you want to assign a density, under Defined, select "By value" and
enter a density in the Choice column for the combination of user profile and mobility type. In this context, the
term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kil-
ometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers
when the map consists of points.
Important: When you import user profile or mobility information from the file, the values in the file
must be exactly the same as the corresponding names in the CDMA/CDMA2000
Parameters folder of the Data tab. If the imported user profile or mobility does not match,
Atoll will display a warning.
12. Under Clutter Distribution, enter a weight for each class that will be used to distribute users on the map.
The user distribution per clutter class is calculated using the following equation:
Wk Sk
N k = N Area --------------------------
Wi Si
i
where:
13. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte-Carlo simu-
lation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
14. Click OK to finish importing the traffic map.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 686.
7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, BIL, IST,
BMP, PlaNET, GRC Vertical Mapper, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears.
11. Select the Description tab.
In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the
Code column.
12. For each Code, select the environment it corresponds to from the Name column.
The environments available are those available in the Environments folder, under CDMA/CDMA2000 Parame-
ters on the Data tab of the Explorer window. For more information, see "Modelling Environments" on page 683.
13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects"
on page 33.
7. Select the environment class from the list of available environment classes.
8. Click the Draw Polygon button ( ) to draw the polygon on the map for the selected environment class.
9. Click the Delete Polygon button ( ) and click the polygon to delete the environment class polygon on the map.
10. Click the Close button to close the Environment Map Editor toolbar and end editing.
5. Click Close.
If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per
clutter class.
Note: Because each of the CDMA technologies has capabilities and services that are specific to
it, it is recommended to create a separate traffic map per user density for:
- voice
- 1xRTT data
- EV-DO data
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue.
7. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP,
PlaNET, TIF, ISTAR, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears.
11. Select the Traffic tab.
12. Select whether the users are active in the Uplink/Downlink, only in the Downlink, or only in the Uplink.
13. Under Terminals (%), enter the percentage of each type of radio configuration used in this map. The total per-
centage must equal 100 for this map.
14. Under Mobilities (%), enter the percentage of each mobility type used in this map. The total percentage must
equal 100 for this map.
15. Under Services (%), enter the percentage of each service type used in this map. The total percentage must equal
100.
16. Under Clutter Distribution, enter for each clutter class the percentage of indoor users.
An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define
a clutter weighting for traffic maps per user density because the traffic is provided in terms of user density per pixel.
17. Click OK. Atoll creates the traffic map in the Traffic folder.
- Active in Uplink and Downlink: Select Active in Uplink and Downlink if the map you are importing provides
a density of users with both uplink and downlink activity.
- Inactive: Select Inactive if the map you are importing provides a density of inactive users.
6. Click the Create button. The traffic maps property dialogue appears.
7. Select the Traffic tab.
8. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must
equal 100.
9. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must
equal 100.
10. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal
100.
11. Under Clutter Distribution, enter for each clutter class the percentage of indoor users.
An additional loss will be counted for indoor users during the Monte-Carlo simulations. You do not have to define
a clutter weighting for traffic maps per user density because the traffic is provided in terms of user density per pixel.
12. Click OK. Atoll creates the traffic map in the Traffic folder.
13. Right-click the traffic map. The context menu appears.
14. Select Edit from the context menu.
15. Use the tools available in the Vector Edition toolbar in order to draw contours. For more information on how to edit
contours, see "Editing Contours, Lines, and Points" on page 131. Atoll creates an item called Density values in
the User Density Map folder.
16. Right-click the item. The context menu appears.
17. Select Open Table from the context menu.
18. In the table, enter a traffic density value (i.e. the number of users per km2) for each contour you have drawn.
19. Right-click the item. The context menu appears.
20. Select Edit from the context menu to end editing.
Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains
at "0" and no data will be exported.
8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic
data to be exported.
- Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal.
- Service: Select the service that will be exported, or select "Circuit services" to export speech type traffic, or
select "Packet services" to export data type traffic.
- Mobility: Select the mobility type that will be exported or select "All" to export all mobility types.
- Activity: Select one of the following:
- All Activity Statuses: Select All Activity Statuses to export all users without any filter by activity status.
- Uplink: Select Uplink to export mobiles active in the uplink only.
- Downlink: Select Downlink to export mobiles active in the downlink only.
- Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity.
- Inactive: Select Inactive to export only inactive mobiles.
9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the
cumulated traffic.
10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.
The user activity status is an important output of the random trial and has direct consequences on the next step
of the simulation and on network interference. A user may be either active or inactive. Both active and inactive
users consume radio resources and create interference.
Additionally, each 1xEV-DO Rev. 0 user is assigned a transition flag ("True" or "False") for each possible rate tran-
sition (from 9.6 to 19.2 kbps, 19.2 to 38.4 kbps, 38.4 to 76.8 kbps, and 76.8 to 153.6 kbps for rate upgrading and
from 153.6 to 76.8 kbps, 76.8 to 38.4 kbps, 38.4 to 19.2 kbps, and 19.2 to 9.6 kbps for rate downgrading). These
transition flags are based on the rate downgrading and upgrading probabilities. If a transition flag is "True," the
user rate can be downgraded or upgraded if necessary.
Then, Atoll randomly assigns a shadowing error to each user using the probability distribution that describes the
shadowing effect.
Finally, another random trial determines user positions in their respective traffic zone (possibly according to the
clutter weighting and the indoor ratio per clutter class).
2. Modelling network power control: Atoll uses a power control algorithm for CDMA2000 1xRTT users, and per-
forms the forward link power control on the FCH and SCH and the reverse link power control on either the pilot
channel or on the FCH and SCH for 1xRTT users. For users of 1xEV-DO, Atoll performs the reverse link power
control on the pilot channel. On the forward link, Atoll performs rate control based on the CI ratio calculated for
the mobile. The power control simulation algorithm is described in "The Power Control Simulation Algorithm" on
page 690.
The CDMA2000 1xRTT power control simulation algorithm (see Figure 11.36) simulates the power control, congestion,
and radio resource control performed for CDMA2000 1xRTT users. Atoll considers each user in the order established
during the generation of the user distribution, determines his best server and his active set. Atoll performs the forward link
power control on the FCH and SCH and the reverse link power control on either the pilot channel or on the FCH and SCH,
depending on the option selected under UL 1xRTT Power Control Based On on the Global Parameters tab of the Trans-
mitter Properties dialogue (see "Creating or Modifying a Transmitter" on page 611).
After performing power control, Atoll updates the reverse link load factor and the total forward link transmitted power. Atoll
then carries out congestion and radio resource control, verifying the cell reverse link load, the forward link load, and the
number of channel elements and Walsh codes consumed by the cell.
The SCH rate on the forward and the reverse links can be downgraded. Atoll will downgrade the forward link SCH rate
until:
The required forward link quality level on SCH is reached,
The total forward link power of a cell is lower than the maximum power allowed,
The number of channel elements consumed on the forward link by a site is lower than the maximum number of
channel elements allowed,
The number of Walsh codes used by a cell is lower than the maximum number of Walsh codes available per cell.
Atoll will downgrade the reverse link SCH rate until:
The required reverse link quality level on SCH or on pilot is reached,
The number of channel elements consumed on the reverse link by a site is lower than the maximum number of
channel elements allowed.
Downgraded SCH rates cannot be lower than the FCH nominal rate. When downgrading the SCH rate does not solve the
problem, the SCH is not allocated to the mobile. In this case, if the requirements of a mobile cannot be met by using the
FCH alone, the mobile is rejected.
At this point, users can be either connected or rejected. They are rejected if:
The signal quality is not sufficient:
- On the forward link, the pilot quality is not high enough (no cell in the user active set): status is "EcI0 pilot <
EcI0 min. pilot."
- On the reverse link, there is not enough power to transmit: the status is "Pmob > Pmob max."
- On the forward link, the quality of the received signal is not high enough on the traffic channel: the status is
"Ptch > Ptch max."
The network is saturated:
- The maximum reverse link load factor is exceeded (at admission or during congestion control): the status is
either "Admission rejection" or "UL load saturation."
- There are not enough available channel elements on the site: the status is "channel element saturation."
- There is not enough power for cells: the status is "DL load saturation."
- There are no more Walsh codes available: the status is "code saturation."
The CDMA2000 1xEV-DO simulation algorithm (see Figure 11.37) simulates the power and rate controls, congestion, and
radio resource control performed for CDMA2000 1xEV-DO users. Atoll considers each user in the order established
during the generation of the user distribution, determines his best server and his active set. Atoll performs the reverse link
power control on the pilot channel. On the forward link, there is no power control; the transmitter transmits at full power.
Instead, Atoll performs rate control based on the CI ratio calculated for the mobile.
After performing rate and power control, Atoll updates the reverse link load factor. Atoll then carries out congestion and
radio resource control, verifying the cell reverse link load and the number of channel elements and MAC indexes
consumed by the cell.
During reverse link power control, if the service supports downgrading, Atoll may downgrade the rate on the reverse link
traffic data channel until the required reverse link quality level is reached. If downgrading does not allow the quality level
to be reached, the mobile is rejected.
During congestion control, if the service supports downgrading, Atoll may adjust the rate on the reverse link traffic data
channel of mobiles until the reverse link cell noise rise is between the noise rise threshold plus the acceptable noise rise
margin and the noise rise threshold minus the acceptable noise rise margin. Atoll starts downgrading or upgrading 1xEV-
DO Rev. 0 users and then if necessary, it continues with 1xEV-DO Rev. A users. If the noise rise is too high, Atoll down-
grades all 1xEV-DO Rev. 0 users that can be downgraded. Then, if the noise rise is still too high, it downgrades 1xEV-DO
Rev. A users, starting with the users with the highest rates. When the noise rise is too low, Atoll upgrades all 1xEV-DO
Rev. 0 users that can be upgraded. Then, if the noise rise is still too low, it upgrades 1xEV-DO Rev. A users starting with
the users with the lowest rates. A 1xEV-DO Rev. 0 user can be downgraded or upgraded if the transition flag of his rate
was set to "True" during the generation of the user distribution.
At this point, users can be either connected or rejected. They are rejected if:
The signal quality is not sufficient:
- On the forward link, the pilot quality is not high enough (no cell in the user active set): status is "EcI0 pilot <
EcI0 min. pilot."
- On the reverse link, there is not enough power to transmit: the status is "Pmob > Pmob max."
The network is saturated:
- The maximum reverse link load factor is exceeded (at admission or during congestion control): the status is
either "Admission rejection" or "UL load saturation."
- There are not enough available channel elements on the site: the status is "channel element saturation."
- There are not enough MAC indexes per cell or the maximum number of EV-DO users per cell is exceeded
during the radio resource control: the status is "1xEV-DO resources saturation."
Note: Execute Later enables you to automatically calculate CDMA coverage predictions after
simulations with no intermediary step by creating your simulations, creating your
predictions, and then clicking the Calculate button ( ).
- Information to retain: You can select the level of detail that will be available in the output:
- Only the Average Simulation and Statistics: None of the individual simulations are displayed or avail-
able in the group. Only an average of all simulations and statistics is available.
Note: Some calculation and display options available for prediction studies are not available
when the option "Only the average simulation and statistics" is selected.
- No Information About Mobiles: All the simulations are listed and can be displayed. For each of them, a
properties window containing simulation output, divided among four tabs Statistics, Sites, Cells, and
Initial conditions is available.
- Standard Anformation About Mobiles: All the simulations are listed and can be displayed. The proper-
ties window for each simulation contains an additional tab with output related to mobiles.
- Detailed Information About Mobiles: All the simulations are listed and can be displayed. The properties
window for each simulation contains additional mobile-related output on the Mobiles and Mobiles (Shad-
owing values) tabs.
Tip: When you are working on very large radio-planning projects, you can reduce memory
consumption by selecting Only the Average Simulation and Statistics under
Information to retain.
6. Under Cell Load Constraints on the General tab, you can set the constraints that Atoll must respect during the
simulation:
- Number of Channel Elements: Select the Number of Channel Elements check box if you want Atoll to
respect the maximum number of channel elements defined for each site.
- Number of Codes: Select the Number of Codes check box if you want Atoll to respect the number of Walsh
codes available for each cell.
- UL Load Factor: If you want the reverse link load factor to be verified in the simulation and not to exceed the
Max UL Load Factor, select the UL Load Factor check box and define a value for the Max UL Load Factor.
- Max UL Load Factor: If you want to enter a global value for the maximum reverse link cell load factor, click
the button ( ) beside the box and select Global Threshold. Then, enter a maximum reverse link cell load
factor. If you want to use the maximum reverse link cell load factor as defined in the properties for each cell,
click the button ( ) beside the box and select Defined per Cell.
- DL Load (% Pmax): If you want the forward link load to be verified in the simulation and not to exceed the
Max DL Load, select the DL Load (% Pmax) check box and enter a maximum forward link cell load in the
Max DL Load box.
- Max DL Load (% Pmax): If you want to enter a global value for the maximum forward link cell load, as a per-
centage of the maximum power, click the button ( ) beside the box and select Global Threshold. Then,
enter a maximum forward link cell load, as a percentage of the maximum power. If you want to use the max-
imum forward link cell load as defined in the properties for each cell, click the button ( ) beside the box and
select Defined per Cell.
7. On the Source Traffic tab, enter the following:
- Global Scaling Factor: If desired, enter a scaling factor to increase user density.
The global scaling factor enables you to increase user density without changing traffic parameters or traffic
maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscrib-
ers (for environment and user profile traffic maps) or the rates/users (for live traffic maps per sector).
- Select Traffic Maps to Be Used: Select the traffic maps you want to use for the simulation.
You can select traffic maps of any type. However, if you have several different types of traffic maps and want
to make a simulation on a specific type of traffic map, you must ensure that you select only traffic maps of the
same type. For information on the types of traffic maps, see "Creating a Traffic Map" on page 681.
Tip: Using the same generated user and shadowing error distribution for several simulations
can be useful when you want to compare the results of several simulations where only one
parameter changes.
Tip: You can make the traffic distribution easier to see by hiding geo data and predictions. For
information, see "Displaying or Hiding Objects on the Map Using the Explorer" on
page 28.
on one site. "23" would mean that the mobile is connected to three different transmitters on two sites. If a mobile
is not connected, the handoff status is given as "00".
5. Click OK. The traffic distribution is now displayed by handoff status (see Figure 11.38).
The Statistics tab: The Statistics tab contains the following two sections:
- Request: Under Request, you will find data on the connection requests:
- Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; power control has not yet started. The result depends on the traffic description and traffic input.
- During the first random trial, each user is assigned a service and an activity status. The number of users
per activity status and the reverse link and forward link rates that all users could theoretically generate are
provided.
- The breakdown per service (total number of users, number of users per activity status, and reverse link
and forward link rates) is given.
- Results: Under Results, you will find data on the connection results:
- The number of iterations that were run in order to converge.
- The number and the percentage of rejected users is given along with the reason for rejection. These
figures are determined at the end of the simulation and depend on the network design.
- The number and percentage of users connected to a cell, the number of users per frequency band for a
dual-band network, the number of users per activity status, and the reverse link and forward link total rates
they generate.
- The breakdown per service (total number of users, number of users per frequency band for a dual-band
network, number of users per activity status, and reverse link and forward link rates) is given.
The Sites tab: The Sites tab contains the following information per site:
- Max No. of DL and UL CEs per Carrier: The maximum number of channel elements available per 1xRTT
carrier on the forward and reverse links.
- Max No. of EV-DO CEs per Carrier: The maximum number of channel elements available per 1xEV-DO car-
rier.
- No. of DL and UL FCH CEs: The number of channel elements used by the FCH on the forward and reverse
links by the site.
- No. of DL and UL SCH CEs: The number of channel elements used by the SCH on the forward and reverse
links by the site.
- No. EV-DO CEs: The number of channel elements used by EV-DO users.
- No. of DL and UL FCH CEs Due to SHO Overhead: The number of extra channel elements due to soft
handoff, on reverse link and forward link for CDMA2000 1xRTT users.
- No. of DL and UL SCH CEs Due to SHO Overhead: The number of extra channel elements due to soft
handoff, on reverse link and forward link for CDMA2000 1xRTT users.
- No. of EV-DO CEs Due to SHO Overhead: The number of extra channel elements due to soft handoff, on
reverse link and forward link for CDMA2000 1xEV-DO users.
- Carrier Selection: The carrier selection method defined on the site equipment.
- AS Restricted to Neighbours: Whether the active set is restricted to neighbours of the reference cell. This
option is selected on the site equipment.
- Rake Factor: The rake factor, defined on the site equipment, enables Atoll to model a rake receiver on the
reverse link.
- MUD Factor: The multi-user detection factor, defined on the site equipment, is used to decrease intra-cell
interference on the reverse link.
- Service kbps Throughput FCH (Uplink and Downlink): The throughput in kbitss for each service on the
FCH. The result is detailed on the forward and reverse link only when relevant.
- Service kbps Throughput SCH (Uplink and Downlink): The throughput in kbitss for each service on the
SCH. The result is detailed on the forward and reverse link only when relevant.
The Cells (1xRTT) tab: The Cells (1xRTT) tab contains the following information, per site, transmitter, and 1xRTT
carrier:
- Max Power (dBm): The maximum power as defined in the cell properties.
- Pilot Power (dBm): The pilot power as defined in the cell properties.
- Synchro Power (dBm): The synchro power as defined in the cell properties.
- Paging Power (dBm): The paging power as defined in the cell properties.
- Gain (dBi): The gain as defined in the antenna properties for that transmitter.
- Reception Loss (dB): The reception loss as defined in the transmitter properties.
- Transmission Loss (dB): The transmission loss as defined in the transmitter properties.
- BTS Noise Figure (dB): The BTS noise figure as defined in the transmitter properties
- Total Transmitted DL Power (dBm): The total transmitted power on the forward link.
- Total Transmitted DL FCH Power (dBm): The total power used on the forward link for the FCH.
- Total Transmitted DL SCH Power (dBm): The total power used on the forward link for the SCH.
- UL Total Noise (dBm): The total noise on the reverse link.
- UL Load Factor (%): The cell load factor on the reverse link corresponds to the ratio between the total inter-
ference on the reverse link and the total noise on the reverse link. If the constraint "UL Load Factor" has been
selected, the cell load factor on the reverse link is not allowed to exceed the user-defined maximum load factor
on the reverse link (defined either in the cell properties, or in the simulation creation dialogue).
- DL Load Factor (%): The load factor of the cell i on the forward link corresponds to the ratio (average inter-
ference on the forward link [due to transmitter signals on the same carrier] for terminals in the transmitter i
area) (average total noise on the forward link [due to transmitter signals and to thermal noise of terminals] for
terminals in the transmitter i area).
- DL Noise Rise (dB): The noise rise on the forward link is calculated from the load factor on the forward link.
These data indicate signal degradation due to cell load (interference margin in the link budget).
- DL Load (% Pmax): The percentage of power used is determined by the total transmitted power-maximum
power ratio (power stated in W). When the constraint "DL load" is set, the DL Load can not exceed the user-
defined Max DL Load (defined either in the cell properties, or in the simulation).
- Number of UL and DL Radio Links: The number of radio links corresponds to the number of user-transmitter
links on the same carrier. This data is calculated on the forward and reverse links and indicates the number
of users connected to the cell on the forward and reverse links. Because of handover, a single user can use
several radio links.
- Connection Success Rate (%): The connection success rate gives the ratio of connected users over the total
number of users in the cell.
- UL Noise Rise (dB): The noise rise on the reverse link is calculated from the load factor on the reverse link.
These data indicate signal degradation due to cell load (interference margin in the link budget).
- Reuse Factor (UL): The reverse link reuse factor is the ratio between the reverse link total interference and
the intra-cell interference.
- Reuse Efficiency Factor (UL): The reuse efficiency factor on the reverse link is the reciprocal of the reuse
factor on the reverse link.
- No. of Codes (128 bits): The total number of 128-bit Walsh codes used by cell.
- No. of FCH Codes (128 bits): The total number of 128-bit Walsh codes used by the FCH of the cell.
- No. of SCH Codes (128 bits): The total number of 128-bit Walsh codes used by the SCH of the cell.
- The Types of Handoff as a Percentage: Atoll estimates the percentages of handoff types for each trans-
mitter. Atoll only lists the results for the following handoff status, no handoff (11), softer (12), soft (22), softer-
soft (23) and soft-soft (33) handoffs; the other handoff status (other HO) are grouped.
- No. of DL and UL FCH CEs: The number of channel elements used by the FCH on the forward and reverse
links.
- No. of DL and UL SCH CEs: The number of channel elements used by the SCH on the forward and reverse
links.
- Kbps Throughput (FCH Uplink and Downlink): The throughput of the FCH on the forward and reverse links.
- Kbps Throughput (SCH Uplink and Downlink): The throughput of the SCH on the forward and reverse links.
- Min TCH Pwr (dBm): The minimum power allocated to a traffic channel for supplying services.
- Max TCH Pwr (dBm): The maximum power allocated to a traffic channel for supplying services.
- Avg TCH Pwr (dBm): The average power allocated to a traffic channel for supplying services.
- Rejected Users: The number of rejected users per cell are sorted by the following reasons: Pmob >
PmobMax, Ptch > PtchMax, EcIo < (EcIo)min, UL Load Saturation, Ch. Elts Saturation, DL Load Satu-
ration, Multiple Causes, Code Saturation, and Admission Rejection.
The Cells (1xEV-DO) tab: The Cells (1xEV-DO) tab contains the following information, per site, transmitter, and
1xEV-DO carrier:
- Max Power (dBm): The maximum power as defined in the cell properties.
- Idle Power Gain (dB): The idle power gain as defined in the cell properties.
- Gain (dBi): The gain as defined in the antenna properties for that transmitter.
- Reception Loss (dB): The reception loss as defined in the transmitter properties.
- Transmission Loss (dB): The transmission loss as defined in the transmitter properties.
- Noise Figure (dB): The BTS noise figure as defined in the transmitter properties.
- UL Total Noise (dBm): The total noise received by the cell on the reverse link.
- UL Load Factor (%): The cell load factor on the reverse link corresponds to the ratio between the total inter-
ference on the reverse link and the total noise on the reverse link. If the constraint "UL Load Factor" has been
selected, the cell load factor on the reverse link is not allowed to exceed the user-defined maximum load factor
on the reverse link (defined either in the cell properties or in the simulation creation dialogue).
- UL Noise Rise (dB): The noise rise on the reverse link is calculated from the load factor on the reverse link.
These data indicate signal degradation due to cell load (interference margin in the link budget).
- UL Reuse Factor: The reverse link reuse factor is the ratio between the reverse link total interference and the
intra-cell interference.
- UL Reuse Efficiency Factor: The reuse efficiency factor on the reverse link is the reciprocal of the reuse
factor on the reverse link.
- Number of UL Radio Links: The number of radio links on the reverse link.
- No. of Active Users: The number of active users connected to the cell.
- No. of Inactive Users: The number of inactive users among the users connected to the cell.
- DL Noise Rise (dB): The noise rise on the forward link is calculated from the load factor on the forward link.
These data indicate signal degradation due to cell load (interference margin in the link budget).
- Connection Success Rate (%): The percentage of connections that are successfully made.
- The Types of Handoff as a Percentage: Atoll estimates the percentages of handoff types for each trans-
mitter on the reverse link. Atoll only lists the results for the following handoff status, no handoff (11), softer
(12), soft (22), softer-soft (23) and soft-soft (33) handoffs; the other handoff status (other HO) are grouped.
- UL and DL Throughput (kbps): The throughput on the forward and reverse links.
- Rejected Users: The number of rejected users per cell are sorted by the following reasons: Pmob >
PmobMax, Ptch > PtchMax, EcIo < (EcIo)min, UL Load Saturation, Ch. Elts Saturation, DL Load Satu-
ration, Multiple Causes, Code Saturation, Admission Rejection, and 1xEV-DO Resources Saturation.
The Mobiles (1xRTT) tab: The Mobiles (1xRTT) tab contains the following information for CDMA2000 1xRTT
users:
Note: The Mobiles (1xRTT) tab only appears if, when creating the simulation as explained in
"Creating Simulations" on page 692, you select either "Standard information about
mobiles" or "Detailed information about mobiles" under Information to Retain.
- X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the
second random trial).
- Service: The service assigned during the first random trial during the generation of the user distribution.
- Terminal: The assigned radio configuration.
- User: The assigned user profile.
- Mobility: The mobility type assigned during the first random trial during the generation of the user distribution.
- Activity: The activity status assigned during the first random trial during the generation of the user distribution.
- DL and UL Total Requested Rate (kbps): The downlink and uplink total requested rates correspond to the
forward and reverse data rates requested by the user before power control.
- DL and UL Total Obtained Rate (kbps): The total obtained rates are the same as the total requested rates
if the user is connected without being downgraded. If the user has been downgraded, the throughput is calcu-
lated using the downgrading factor. If the user was rejected, the total obtained rate is zero.
- Carrier: The carrier used for the mobile-transmitter connection.
- Frequency Band: the frequency band used for the mobile-transmitter connection.
- Mobile Total Power (dBm): This value corresponds to the total power transmitted by the terminal.
- Uplink Pilot Power: The power transmitted by the terminal on the reverse pilot channel.
- Mobile FCH Power: The power transmitted by the terminal on the FCH channel.
- Mobile SCH Power: power transmitted by the terminal on the SCH channel.
- Connection Status: The connection status indicates whether the user is connected or rejected at the end of
the simulation. If connected, the connection status corresponds to the activity status. If rejected, the rejection
cause is given.
- Best Server: The best server among the transmitters in the mobile active set.
- HO Status (Sites/No. Transmitters Act. Set): The HO status is the number of sites compared to the number
of transmitters in the active set.
- AS1, AS2, AS3, AS4, AS5, AS6: The name of the cell that is the best server, the second-best server, and so
on is given in a separate column for each cell in the active set.
- Ec/I0 AS1, AS2, AS3, AS4, AS5, AS6 (dB): EcI0 is given in a separate column for each cell in the active set.
The Ec/I0 AS1 column lists the Ec/I0 from the best server for the rejected mobiles as well.
- Indoor: This field indicates whether indoor losses have been added or not.
The following columns only appear if, when creating the simulation as explained in "Creating Simulations" on
page 692, you select "Detailed Information About Mobiles" under Information to retain:
- DL and UL Downgrading Factor (SCH): The downgrading factor for the SCH on both the forward and the
reverse links. The downgrading factor is used to calculated how much the SCH rate will be downgraded if the
requested rate cannot be provided.
- DL Ntot AS1, AS2, AS3, AS4, AS5, AS6 (dBm): The total noise on the forward link for each link between the
mobile and a transmitter in the active set.
- Cell FCH Power AS1, AS2, AS3, AS4, AS5, AS6 (DL) (dBm): The cell power transmitted on the FCH forward
link is given for each link between the mobile and a transmitter in the active set.
- Cell SCH Power AS1, AS2, AS3, AS4, AS5, AS6 (DL) (dBm): The cell power transmitted on the SCH forward
link is given for each link between the mobile and a transmitter in the active set.
- Load Factor AS1, AS2, AS3, AS4, AS5, AS6 (DL) (%): The load factor on the forward link for each link
between the mobile and a transmitter in the active set. It corresponds to the ratio between the total interference
on the forward link and total noise at the terminal.
- Noise Rise AS1, AS2, AS3, AS4, AS5, AS6 (DL) (dB): The noise rise on the forward link for each link
between the mobile and a transmitter in the active set.
- Reuse Factor AS1, AS2, AS3, AS4, AS5, AS6 (DL): The forward link reuse factor is the ratio between the
forward link total interference and the intra-cell interference. It is calculated for each link between the mobile
and a transmitter in the active set.
- Iintra AS1, AS2, AS3, AS4, AS5, AS6 (DL) (dBm): The intra-cell interference on the forward link for each cell
(I) of the active set.
DL DL
I Intra ( ic ) = ( 1 F Ortho ) P tot ( ic )
txi
- Iextra AS1, AS2, AS3, AS4, AS5, AS6 (DL) (dBm): The extra-cell interference on the forward link for each
cell (I) of the active set.
DL DL
I extra ( ic ) = P tot ( ic )
txj, j i
- Total Loss AS1, AS2, AS3, AS4, AS5, AS6 (dB): The total attenuation for each link between the mobile and
a transmitter in the active set.
- Name: The name of the mobile, as assigned during the random user generation.
- Clutter: The clutter class on which the mobile is located.
- Orthogonality Factor: The orthogonality factor used in the simulation. The orthogonality factor is the
remaining orthogonality of the Walsh codes at reception. The value used is the orthogonality factor set in the
clutter classes.
- % Pilot Finger: The percentage pilot finger used in the simulation, defined per clutter class or globally for all
clutter classes.
- DL and UL FCH SHO Gain (dB): The soft handoff gain for the FCH on the forward and the reverse link. The
soft handoff gain on the forward link is calculated if mobile receivers are connected either on the forward link
or on the forward link and the reverse link.
- DL and UL SCH SHO Gain (dB): The soft handoff gain for the SCH on the forward and the reverse link. The
soft handoff gain on the forward link is calculated if mobile receivers are connected either on the forward link
or on the forward link and the reverse link.
The Mobiles (1xEV-DO) tab: The Mobiles (1xEV-DO) tab contains the following information for CDMA2000
1xEV-DO users:
Note: The Mobiles (1xEV-DO) tab only applies to CDMA2000 projects and only appears if,
when creating the simulation as explained in "Creating Simulations" on page 692, you
select either "Standard information about mobiles" or "Detailed information about mobiles"
under Information to Retain.
- X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the
second random trial).
- Service: The service assigned during the first random trial during the generation of the user distribution.
- Terminal: The assigned radio configuration.
- User: The assigned user profile.
- Mobility: The mobility type assigned during the first random trial during the generation of the user distribution.
- Activity: The activity status assigned during the first random trial during the generation of the user distribution.
- UL Total Requested Rate (kbps): The UL Total Requested Rate corresponds to the data rate, including the
control channel rate, requested by the user before power control.
- UL Total Obtained Rate (kbps): The total obtained rate is the same as the total requested rate if the user is
connected without being downgraded. If the user has been downgraded, the throughput is calculated using
the downgrading factor. If the user was rejected, the total obtained rate is zero.
- DL Max Data Rate: The maximum data rate on the forward link depends on the value of CI at the terminal.
Atoll calculates this value from the Max rate=f(CI) graph specified in the mobility type properties.
- Carrier: The carrier used for the mobile-transmitter connection.
- Frequency Band: the frequency band used for the mobile-transmitter connection.
- Mobile Total Power (dBm): The mobile total power corresponds to the total power transmitted by the ter-
minal.
- Connection Status: The connection status indicates whether the user is connected or rejected at the end of
the simulation. If connected, the connection status corresponds to the activity status. If rejected, the rejection
cause is given.
- Best Server: The best server among the transmitters in the mobile active set.
- HO Status (Sites/No. Transmitters Act. Set): The HO status is the number of sites compared to the number
of transmitters in the active set.
- AS1, AS2, AS3, AS4, AS5, AS6: The name of the cell that is the best server, the second-best server, and so
on is given in a separate column for each cell in the active set.
- Ec/I0 AS1, AS2, AS3, AS4, AS5, AS6 (dB): EcI0 is given in a separate column for each cell in the active set.
The Ec/I0 AS1 column lists the Ec/I0 from the best server for the rejected mobiles as well.
- Indoor: This field indicates whether indoor losses have been added or not.
The following columns only appear if, when creating the simulation as explained in "Creating Simulations" on
page 692, you select "Detailed information about mobiles" under Information to Retain:
- Requested UL Data Peak Rate (kbps): The uplink requested data peak rate corresponds to the data rate
requested by the user before power control.
- Obtained UL Data Peak Rate (kbps): The uplink obtained data peak rate is the same as the requested data
peak rate if the user is connected without being downgraded. If the user has been downgraded, the throughput
is calculated using the downgrading factor. If the user was rejected, the obtained data peak rate is zero.
- UL Downgrading Factor: The downgrading factor on the reverse link. The downgrading factor is used to cal-
culated how much the data rate will be downgraded if the requested rate cannot be provided.
- UL Throughput Due to TCP (kbps): The traffic on the reverse link generated due to Transmission Control
Protocol (TCP) acknowledgements.
- DL CI (Pilot) (dB): CI for the pilot on the forward link.
- DL Ntot (Data) (dBm): The total noise on the forward link.
- DL Load Factor (%): The load factor on the forward link. It corresponds to the ratio between the total interfer-
ence on the forward link and total noise at the terminal.
- DL Noise Rise (dB): The noise rise on the forward link.
- Total Loss AS1, AS2, AS3, AS4, AS5, AS6 (dB): The total attenuation for each link between the mobile and
a transmitter in the active set.
- Name: The name of the mobile, as assigned during the random user generation.
- Clutter: The clutter class on which the mobile is located.
- Orthogonality Factor: The orthogonality factor used in the simulation. The orthogonality factor is the
remaining orthogonality of the Walsh codes at reception. The value used is the orthogonality factor set in the
clutter classes.
- % Pilot Finger: The percentage pilot finger used in the simulation, defined per clutter class or globally for all
clutter classes.
- UL SHO Gain (dB): The soft handoff gain on the reverse link.
- Transition flags (Upgrading 9.6k->19.2k, Upgrading 19.2k->38.4k, Upgrading 38.4k->76.8k, Upgrading
76.8k->153.6k, Downgrading 19.2k->9.6k, Downgrading 38.4k->19.2k, Downgrading 76.8k->38.4k,
Downgrading 153.6k->76.8k): The boolean transition flags ("True" or "False") generated by Atoll for each
rate transition and for each 1xEV-DO user. If the flag for a rate transition is "True," the rate can be upgraded
or downgraded if necessary during the uplink load control.
The Mobiles (Shadowing Values) tab: The Mobiles (Shadowing Values) tab contains information on the shad-
owing margin for each link between the receiver and up to ten potential transmitters. Atoll selects the transmitters
which have the receiver in their propagation zone and have the lowest path losses. The ten transmitters with the
lowest path losses are selected and sorted in ascending order by path loss.
Note: The Mobiles (Shadowing Values) tab only appears if, when creating the simulation as
explained in "Creating Simulations" on page 692, you select "Detailed information about
mobiles" under Information to Retain.
The Statistics tab: The Statistics tab contains the following two sections:
- Request: Under Request, you will find data on the connection requests:
- Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; power control has not yet started. The result depends on the traffic description and traffic input.
- During the first random trial, each user is assigned a service and an activity status. The number of users
per activity status and the reverse link and forward link rates that all users could theoretically generate are
provided.
- The breakdown per service (total number of users, number of users per activity status, and reverse link
and forward link rates) is given.
- Results: Under Results, you will find data on the connection results:
- The number of iterations that were run in order to converge.
- The number and the percentage of rejected users is given along with the reason for rejection. These
figures are determined at the end of the simulation and depend on the network design.
- The number and percentage of users connected to a cell, the number of users per frequency band for
dual-band networks, the number of users per activity status, and the reverse link and forward link total
rates they generate.
- The breakdown per service (total number of users, number of users per frequency band for dual-band
networks, number of users per activity status, and reverse link and forward link rates) is given.
The Cells (Average - 1xRTT) and Cells (Standard Deviation - 1xRTT) tabs: The Cells (Average - 1xRTT) and
Cells (Standard Deviation - 1xRTT) tabs contain the following average and standard deviation information, respec-
tively, per site, transmitter, and 1xRTT carrier:
- UL Total Noise (dBm): The total noise on the reverse link takes into account the total signal received at the
transmitter on a carrier from intra and extra-cell terminals using the same carrier and adjacent carriers (total
interference on the reverse link) and the thermal noise.
- UL Load Factor (%): The cell load factor on the reverse link corresponds to the ratio between the total inter-
ference on the reverse link and the total noise on the reverse link. If the constraint "UL Load Factor" has been
selected, the cell load factor on the reverse link is not allowed to exceed the user-defined maximum load factor
on the reverse link (defined either in the cell properties, or in the simulation creation dialogue).
- UL Noise Rise (dB): The noise rise on the reverse link is calculated from the load factor on the reverse link.
These data indicate signal degradation due to cell load (interference margin in the link budget).
- UL Reuse Factor: The reverse link reuse factor is the ratio between the reverse link total interference and the
intra-cell interference.
- UL Reuse Efficiency Factor: The reverse link reuse efficiency factor is the reciprocal of the reverse link reuse
factor.
- DL Load Factor (%): The forward link load factor of the cell i corresponds to the ratio (forward link average
interference [due to transmitter signals on the same carrier] for terminals in the transmitter i area) (forward
link average total noise [due to transmitter signals and to thermal noise of terminals] for terminals in the trans-
mitter i area).
- DL Noise Rise (dB): The forward link noise rise is calculated from the forward link load factor. These data
indicate signal degradation due to cell load (interference margin in the link budget).
- Total Transmitted DL Power (dBm): The total power transmitted on the forward link.
- DL Load (% Pmax): The percentage of power used is determined by the total transmitted power-maximum
power ratio (power stated in W). When the constraint "DL load" is set, the DL Load can not exceed the user-
defined Max DL Load (defined either in the cell properties, or in the simulation).
- Number of UL and DL Radio Links: The number of radio links corresponds to the number of user-transmitter
links on the same carrier. This data is calculated on the forward and reverse links and indicates the number
of users connected to the cell on the forward and reverse links. Because of handover, a single user can use
several radio links.
- Connection Success Rate (%): The connection success rate gives the ratio of connected users over the total
number of users in the cell.
- No. of Codes (128 bits): The average number of 128-bit Walsh codes used per cell.
- The types of handoff as a percentage: Atoll estimates the percentages of handoff types for each trans-
mitter. Atoll only lists the results for the following handoff status, no handoff (11), softer (12), soft (22), softer-
soft (23) and soft-soft (33) handoffs; the other handoff status (other HO) are grouped.
- Min TCH Pwr (dBm): The minimum power allocated to a traffic channel for supplying services.
- Max TCH Pwr (dBm): The maximum power allocated to a traffic channel for supplying services.
- Avg TCH Pwr (dBm): The average power allocated to a traffic channel for supplying services.
- Rejected Users: The number of rejected users per cell are sorted by the following reasons: Pmob >
PmobMax, Ptch > PtchMax, EcIo < (EcIo)min, UL Load Saturation, Ch. Elts Saturation, DL Load Satu-
ration, Multiple Causes, Code Saturation, and Admission Rejection.
The Cells (Average - 1xEV-DO) and Cells (Standard Deviation - 1xEV-DO) tabs: The Cells (Average -
1xEV-DO) and Cells (Standard Deviation - 1xEV-DO) tabs contain the following average and standard deviation
information, respectively, per site, transmitter, and 1xEV-DO carrier:
- UL Total Noise (dBm): The total noise on the reverse link takes into account the total signal received at the
transmitter on a carrier from intra and extra-cell terminals using the same carrier and adjacent carriers (total
interference on the reverse link) and the thermal noise.
- UL Load Factor (%): The cell load factor on the reverse link corresponds to the ratio between the total inter-
ference on the reverse link and the total noise on the reverse link. If the constraint "UL Load Factor" has been
selected, the cell load factor on the reverse link is not allowed to exceed the user-defined maximum load factor
on the reverse link (defined either in the cell properties, or in the simulation creation dialogue).
- UL Noise Rise (dB): The noise rise on the reverse link is calculated from the load factor on the reverse link.
These data indicate signal degradation due to cell load (interference margin in the link budget).
- UL Reuse Factor: The reverse link reuse factor is the ratio between the reverse link total interference and the
intra-cell interference.
- UL Reuse Efficiency Factor: The reverse link reuse efficiency factor is the reciprocal of the reverse link reuse
factor.
- Number of UL Radio Links: The number of radio links on the reverse link.
- No. of Active Users: The number of active users connected to the cell.
- No. of Inactive Users: The number of inactive users among the users connected to the cell.
- Connection Success Rate (%): The percentage of connections that are successfully made.
- The types of handoff as a percentage: Atoll estimates the percentages of handoff types for each trans-
mitter. Atoll only lists the results for the following handoff status, no handoff (11), softer (12), soft (22), softer-
soft (23) and soft-soft (33) handoffs; the other handoff status (other HO) are grouped.
- UL and DL Throughput (kbps): The throughput on the forward and reverse links.
- Rejected Users: The number of rejected users per cell are sorted by the following reasons: Pmob >
PmobMax, Ptch > PtchMax, EcIo < (EcIo)min, UL Load Saturation, Ch. Elts Saturation, DL Load Satu-
ration, Multiple Causes, Code Saturation, Admission Rejection, and 1xEV-DO Resources Saturation.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
Replaying a group: When you replay an existing group of simulations, Atoll reuses the same user distribution
(users with a service, a mobility and an activity status) as the one used to calculate the initial simulation. The shad-
owing error distribution between simulations is different. Traffic parameter changes (such as, maximum and min-
imum traffic channel powers allowed, Eb/Nt thresholds, etc.) may be taken into account or not. Finally, radio data
modifications (new transmitters, changes to the antenna azimuth, etc.) are always taken into account during the
power control (or rate/power control) simulation.
To replay a group of simulations, see "Replaying a Group of Simulations" on page 703.
Using the Generator Initialisation Number: When you create groups of simulations using the same generator
initialisation number (which must be an integer other than 0) Atoll generates the same user and shadowing error
distributions (user with a service, a mobility, an activity status and a shadowing error) in all groups using the same
number. However, any modifications to traffic parameters (such as, maximum and minimum traffic channel powers
allowed, EbNt thresholds, etc.) and radio data (new transmitter, azimuth, etc.) are taken into account during the
power control simulation.
By creating and calculating one group of simulations, making a change to the network and then creating and calcu-
lating a new group of simulations using the same generator initialisation number, you can see the difference your
parameter changes make.
To create a new simulation to a group of simulations using the generator initialisation number, see "Adding a Simu-
lation to a Group of Simulations" on page 703.
Duplicating a Group: When you duplicate a group, Atoll creates a group of simulations with the same simulation
parameters as those used to generate the group of simulations. You can then modify the simulation parameters
before calculating the group.
To duplicate a group of simulations, see "Duplicating a Group of Simulations" on page 704.
Note: When adding a simulation to an existing group of simulations, the parameters originally
used to calculate the group of simulations are used for the new simulations.
Consequently, few parameters can be changed for the added simulation.
5. On the General tab of the dialogue, if desired, change the Name and Comments for this group of simulations.
6. Under Execution on the General tab, you can set the following parameters:
- Number of Simulations: Enter the number of simulations to added to this group of simulations.
- Execute Later: If you select the Execute Later check box, the simulation will not be carried out until you click
the Calculate button ( ). If the Execute Later check box is not selected, the simulation will be carried out
as soon as you click OK and close the dialogue.
7. Click OK. Atoll immediately begins the simulation unless you selected the Execute Later check box on the Gen-
eral tab.
Note: When replaying an existing group of simulations, some parameters originally used to
calculate the group of simulations are reused for the replayed group. Consequently, few
parameters can be changed for the replayed group.
5. In the General tab of the dialogue, you can set the following parameters:
- Select the level of detail as explained in "Creating Simulations" on page 692 that will be available in the output
from the Information to retain list.
- Under Cell Load Constraints, you can set the constraints as explained in "Creating Simulations" on page 692
that Atoll must respect during the simulation.
6. In the Source Traffic tab of the dialogue, check the Refresh Traffic Parameters check box if you want to take into
account traffic parameter changes (such as, maximum and minimum traffic channel powers allowed, Eb/Nt thresh-
olds, etc.) in the replayed simulation.
7. In the Advanced tab, you can set the following parameters:
- Max Number of Iterations: Enter the maximum number of iterations that Atoll should run to make conver-
gence.
- UL Convergence Threshold: Enter the relative difference in terms of interference and connected users on
the uplink that must be reached between two iterations.
- DL Convergence Threshold: Enter the relative difference in terms of interference and connected users on
the downlink that must be reached between two iterations.
8. Click OK. Atoll immediately begins the simulation unless you selected the Execute Later check box on the Gen-
eral tab.
Tip: You can create a new group of simulations with the same parameters as the original group
of simulations by duplicating an existing one as explained in "Duplicating a Group of
Simulations" on page 704.
Note: The AS analysis does not take possible network saturation into account. Therefore, there
is no guarantee that a simulated mobile with the same receiver characteristics can verify
the point analysis, simply because the simulated network may be saturated.
1. Click the Point Analysis button ( ) on the toolbar. The Point Analysis window appears. (see Figure 11.12).
2. Click the AS Analysis tab.
3. At the top of the AS Analysis tab, select from the Load Conditions list, the simulation or group of simulations you
want to base the AS analysis on.
4. Select the Terminal, Service, Mobility, Carrier, and DL and UL Rates.
5. Right-click the Point Analysis window and select Properties from the context menu. The Properties dialogue
appears.
6. Select or clear the following options:
- Whether shadowing is to be taken into account (and, if so, the cell edge coverage probability and shadowing
margin).
- Whether indoor coverage is to be taken into account.
7. Click OK to close the Properties dialogue.
8. Move the pointer over the map to make an active set analysis for the current location of the pointer.
As you move the pointer, Atoll indicates on the map which is the best server for the current position (see
Figure 11.30 on page 662).
Information on the current position is given on the AS Analysis tab of the Point Analysis window. See
Figure 11.31 on page 663 for an explanation of the displayed information.
9. Click the map to leave the point analysis pointer at its current position.
To move the pointer again, click the point analysis pointer on the map and drag it to a new position.
10. Click the Point Analysis button ( ) on the toolbar again to end the point analysis.
Note: If you are importing more than one file, you can select contiguous files by clicking the first
file you want to import, pressing SHIFT and clicking the last file you want to import. You
can select non-contiguous files by pressing CTRL and clicking each file you want to
import.
Note: Files with the extension PLN, as well as some FMT files (created with previous versions of
TEMS) are imported directly into Atoll; you will not be asked to define the data structure
using the Import of Measurement Files dialogue.
6. If you already have an import configuration defining the data structure of the imported file or files, you can select
it from the Configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have
an import configuration, continue with step 7.
a. Under Configuration, select an import configuration from the Configuration list.
b. Continue with step 10.
Notes:
When importing a test mobile data path file, existing configurations are available in the Files
of type list of the Open dialogue, sorted according to their date of creation. After you have
selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises
the extension. In case several configurations are associated with an extension, Atoll chooses
the first configuration in the list.
The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in
the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see
the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters:
- Name: By default, Atoll names the new test mobile data path after the imported file. You can change this
name if desired.
- Under Receiver, set the Height of the receiver antenna and the Gain and Losses.
- Under Measurement Conditions,
- Units: Select the measurement units used.
- Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document.
If the coordinates used in the file you are importing are different than the coordinates used in the Atoll
document, you must click the Browse button ( ) and select the coordinate system used in the test
mobile data file. Atoll will then convert the data imported to the coordinate system used in the Atoll docu-
ment.
8. Click the Setup tab (see Figure 11.42).
Figure 11.42: The Setup tab of the Import of Measurement Files dialogue
a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Dec-
imal Symbol used in the file.
b. Click Setup to link file columns and internal Atoll fields. The Test Mobile Data Configuration dialogue ap-
pears.
c. Select the columns in the imported file that give the X-Coordinates and the Y-Coordinates of each point in
the test mobile data file.
Note: You can also identify the columns containing the XY coordinates of each point in the test
mobile data file by selecting them from the Field row of the table on the Setup tab.
d. In the PN Group Identifier box, enter a string that must be found in the column names identifying the PN offset
group of scanned cells. For example, if the string "PN_Group" is found in the column names identifying the PN
offset group of scanned cells, enter it here. Atoll will then search for columns with this string in the column
name.
If there is no PN offset group information contained in the test mobile data file, leave the PN Group Identifier
box empty.
e. In the PN Offset Identifier box, enter a string that must be found in the column names identifying the PN offset
of scanned cells. For example, if the string "PN" is found in the column names identifying the PN offset of
scanned cells, enter it here. Atoll will then search for columns with this string in the column name.
f. Ensure that the PN offset format selected in the PN Offset Format list is "Decimal."
g. Click OK to close the Test Mobile Data Configuration dialogue.
Important:
If you have correctly entered the information under File on the Setup tab, and the necessary
values in the Test Mobile Data Configuration dialogue, Atoll should recognize all columns in
the imported file. If not, you can click the name of the column in the table in the Field row and
select the column name. For each field, you must ensure that each column has the correct data
type in order for the data to be correctly interpreted. The default value under Type is "<Ignore>".
If a column is marked with "<Ignore>", it will not be imported.
9. If you wish to save the definition of the data structure so that you can use it again, you can save it as an import
configuration:
a. On the Setup tab, under Configuration, click Save. The Configuration dialogue appears.
b. By default, Atoll saves the configuration in a special file called "NumMeasINIfile.ini" found in Atolls installa-
tion folder. In case you cannot write into that folder, you can click Browse to choose a different location.
c. Enter a Configuration Name and an Extension of the files that this import configuration will describe (for ex-
ample, "*.csv").
d. Click OK.
Atoll will now select this import configuration automatically every time you import a test mobile data path file
with the selected extension. If you import a file with the same structure but a different extension, you will be
able to select this import configuration from the Configuration list.
Notes:
You do not have to complete the import procedure to save the import configuration and have
it available for future use.
When importing a CW measurement file, you can expand the NumMeasINIfile.ini file by clicking
the button ( ) in front of the file in the Setup part to display all the available import configura-
tions. When selecting the appropriate configuration, the associations are automatically made
in the table at the bottom of the dialogue.
You can delete an existing import configuration by selecting the import configuration under
Setup and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The
mobile data are imported into the current Atoll document.
Notes:
Fast Display forces Atoll to use the lightest symbol to display the points. This is particularly useful
when you have a very large number of points.
You can not use Multiple Shadings if the Fast Display check box has been selected.
You can sort test mobile data paths in alphabetical order on the Data tab of the Explorer window by
right-clicking the Test Mobile Data Path folder and selecting Sort Alphabetically from
the context menu.
You can export the display settings of a test mobile data path in a configuration file to make them
available for future use. You can export the display settings or import display settings by
clicking the Actions button on the Display tab of the test mobile data paths Properties
dialogue and selecting Export or Import from the menu.
Note: You can permanently delete the points located in the clutter classes whose check boxes
you clear by selecting the Delete points outside the filter check box.
b. Underneath each column name, enter the criteria on which the column will be filtered as explained in the fol-
lowing table:
9. Click OK to filter the data according to the criteria you have defined.
Filters are combined first horizontally, then vertically. For more information on how filters work, see "Advanced
Data Filtering" on page 71.
Note: You can permanently delete the points that do not fulfil the filter conditions by selecting
the Delete points outside the filter check box.
7. When you have finished creating new coverage predictions for these test mobile data, right-click the test mobile
data. The context menu appears.
8. Select Calculations > Calculate All the Studies from the context menu.
A new column for each coverage prediction is added in the table for the test mobile data. The column contains the
predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned
to the transmitter for the main matrix (for information on the propagation model, see "Chapter 5: Managing Calcu-
lations in Atoll").
You can display the information in these new columns in the Test Mobile Data window. For more information on
the Test Mobile Data window, see "Analysing Data Variations Along the Path" on page 713.
11.3.4.4 Extracting Data From a Test Mobile Path for a Selected Transmitter
When you have test mobile path data, you can extract the data from a selected field for a specific transmitter from each
test mobile path data point where measurements for that transmitter exist. The extracted information will be added to a
new column in the table for the test mobile data.
For example, if you wanted to know the pilot strength for the transmitter named "site15_2", you could extract the data from
every point on which the pilot strength from that particular transmitter was measured. In the table for that test mobile path,
Atoll adds a new column, identifying both the field selected and the transmitter.
To extract a field from a test mobile path:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Test Mobile Data folder.
3. Right-click the test mobile data from which you want to extract a field. The context menu appears.
4. Select Focus on a Transmitter from the context menu. The Field Select for a Given Transmitter dialogue
appears.
5. Select a transmitter from the On the Transmitter list.
6. Click the For the Fields list. The list opens.
7. Select the check box beside the field you want to extract for each of the transmitters measured.
Note: A test mobile data path contains the same measurements on each point for several
different transmitters. If you want to extract the maximum data for the selected
transmitter, you must select the same field for all the transmitters, because the selected
transmitter could be "Transmitter 1" for some test mobile data points, but "Transmitter 2"
or any other for other points.
8. Click OK. The column is added to the data table for the test mobile data path.
After you have extracted the data for the selected transmitter, you can display the table for the test mobile data path with
the extracted data.
To display the test mobile path table:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Test Mobile Data folder.
3. Right-click the test mobile data whose data table you want to display. The context menu appears.
4. Select Open Table from the context menu. The test mobile data table appears with a new column containing the
measurements extracted for the selected transmitter.
5. Click Display at the top of the Test Mobile Data window. The Display Parameters dialogue appears (see
Figure 11.45).
Note: You can change the display status or the colour of more than one field at a time. You can
select contiguous fields by clicking the first field, pressing SHIFT and clicking the last field
you want to import. You can select non-contiguous fields by pressing CTRL and clicking
each field. You can then change the display status or the colour by right-clicking on the
selected fields and selecting the choice from the context menu.
The selected fields are displayed in the Test Mobile Data window.
7. You can display the data in the test mobile path in two ways:
- Click the values in the Test Mobile Data window.
- Click the points on the test mobile path in the map window.
The test mobile data path appears in the map window as an arrow pointing towards the serving cell, with a number
identifying the best server (see Figure 11.44 on page 714). If the transmitter display type is "Automatic," both the
number and the arrow are displayed in the same colour as the transmitter. For information on changing the display
type to "Automatic," see "Defining the Display Type" on page 34.
8. You can display a second Y-axis on the right side of the window in order to display the values of a variable with
different orders of magnitude than the ones selected in the Display Parameters dialogue. You can select the sec-
ondary Y-axis from the right-hand list on the top of the Test Mobile Data window. The selected values are dis-
played in the colours defined for this variable in the Display Parameters dialogue.
9. You can change the zoom level of the Test Mobile Data window display in the Test Mobile Data window in the
following ways:
- Zoom in or out:
i. Right-click the Test Mobile Data window.
ii. Select Zoom In or Zoom Out from the context menu.
- Select the data to zoom in on:
i. Right-click the Test Mobile Data window on one end of the range of data you want to zoom in on.
ii. Select First Zoom Point from the context menu.
iii. Right-click the Test Mobile Data window on the other end of the range of data you want to zoom in on.
iv. Select Last Zoom Point from the context menu. The Test Mobile Data window zooms in on the data be-
tween the first zoom point and the last zoom point.
10. Click the data in the Test Mobile Data window to display the selected point in the map window. Atoll will recentre
the map window on the selected point if it is not presently visible.
Tip: If you open the table for the test mobile data you are displaying in the Test Mobile Data
window, Atoll will automatically display in the table the data for the point that is displayed
in the map and in the Test Mobile Data window (see Figure 11.44 on page 714).
a. Select Print from the context menu. The Print dialogue appears.
b. Click OK to print the contents of the Test Mobile Data window.
For every pair of carriers that is not defined, Atoll assumes that there is no inter-carrier interference.
d. Press ENTER to create the carrier pair and to create a new row in the table.
Important: When you have more than one frequency band, the carriers must be numbered
sequentially, contiguously (i.e., you cannot skip numbers in a range of carriers, and the
range of carriers in one band cannot overlap the range of carriers in another), and
uniquely (i.e., you can only use each number once).
For example:
Band 1900: First carrier: 0; Last carrier 1 and Band 700: First carrier: 2 and Last carrier: 2
5. Click the Carrier Types button. The Carrier Types table appears.
6. In the table, define the carriers and whether the carrier is 1xRTT or 1xEV-DO.
7. When you have finished describing carriers, click Close.
8. When you have finished adding frequency bands, click Close.
3 X N FCH 3 X N FCH
5 X N FCH 5 X N FCH
For 1xRTT, N FCH can be 9.6 or
14.4 kbps on either the forward or 9 X N FCH 9 X N FCH
reverse link.
17 X N FCH 17 X N FCH
19.2 76.8
76.8 307.6
153.6 614.4
921.6
1228.8
1843.2
2457.6
9.6 9.6
19.2 19.2
38.4 38.4
76.8 76.8
115.2 115.2
153.6 153.6
230.4 230.4
307.2 307.2
460.8 460.8
614.4 614.4
921.6 921.6
1228.8 1228.8
1848.2 1848.2
2457.6
3072.0
- RLC Peak Rate (bps): Enter or modify the RLC peak rate in bits per second.
- Packet Size (bits): Enter or modify the packet size in bits transmitted in one timeslot.
Note: The rake efficiency factor used to model the recombination on the forward link can be set
in terminal properties.
- Carrier Selection: Carrier selection refers to the carrier selection method used during the transmitter admis-
sion control in the mobile active set. The selected strategy is used in simulations when no carrier is specified
in the properties of the service (when all the carriers can be used for the service) or when the carrier specified
for the service is not used by the transmitter. On the other hand, the specified carrier selection mode is always
taken into account in coverage predictions (AS analysis and coverage studies). Choose one of the following:
- Min. UL Load Factor: The carrier with the minimum reverse link noise (carrier with the lowest reverse link
load factor) is selected.
- Min. DL Total Power: The carrier with the minimum forward link total power is selected.
- Random: The carrier is randomly chosen.
- Sequential: Carriers are sequentially loaded. The first carrier is selected as long as it is not overloaded.
Then, when the maximum reverse link load factor is reached, the second carrier is chosen and so on.
- Overhead Downlink and Uplink CEs: The overhead reverse link and forward link channel elements (CEs)
correspond to the numbers of channel elements that a cell uses for common channels in the forward and the
reverse link. This setting is also used for Walsh code allocation; it indicates the number of Walsh codes to be
allocated to control channels per cell.
- AS Restricted to Neighbours: Select this option if you want the other transmitters in the active set to belong
to the neighbour list of the best server.
- Pool of Shared CEs: Select this option if you want all cells on the site to share channel elements.
- Power Pooling Between Transmitters: Select this option if you want all cells on the site to share power on
the traffic channels.
5. Click the Close button ( ) to close the table.
11.4.6.2 Defining Channel Element Consumption per CDMA Site Equipment and
Radio Configuration
The number of channel elements consumed by a user depends on the site equipment, on the radio configuration, and the
link direction (forward or reverse). The number of channel elements consumed can be defined for CDMA simulations.
To define channel element consumption during CDMA simulations:
1. Click the Data tab in the Explorer window.
2. Right-click on the Sites folder. The context menu appears.
3. Select Equipment > Channel Element Consumption from the context menu. The CE Consumption table
appears.
4. For each equipment-radio configuration pair, enter in the CE Consumption table the number of reverse link and
forward link channel elements that Atoll will consume during the power control simulation.
5. Click the Close button ( ) to close the table.
5. Double-click the reception equipment type you want to modify. The reception equipment types Properties dia-
logue appears.
Note: You can create a new reception equipment type by entering a name in the row marked
with the New Row icon ( ) and pressing ENTER.
The DL and UL Quality Indicator tables describe the variation of the quality indicator as a function of the meas-
ured parameter (as defined in the Quality Indicators table). The Uplink and Downlink Quality Graphs are used
for quality studies.
Shadowing can be taken into consideration when Atoll calculates the signal level, EcI0, and EbNt for:
A point analysis (see "Making a Point Analysis to Study the Profile" on page 625)
A coverage prediction (see "Studying Signal Level Coverage" on page 626).
Atoll always takes shadowing into consideration when calculating a Monte-Carlo-based CDMA simulation.
You can display the shadowing margins and the macro-diversity gain per clutter class. For information, see "Displaying
the Shadowing Margins and Macro-diversity Gain per Clutter Class" on page 722.
11.4.9.1 Displaying the Shadowing Margins and Macro-diversity Gain per Clutter
Class
To display the shadowing margins and macro-diversity gain per clutter class:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Shadowing Margins from the context menu. The Shadowing Margins and Gains dialogue appears (see
Figure 11.46).
4. You can set the following parameters:
- Cell Edge Coverage Probability: Enter the probability of coverage at the edge of the cell. The value you enter
in this dialogue is for information only.
- Standard Deviation: Select the type of standard deviation to be used to calculate the shadowing margin or
macro-diversity gains:
- From Model: The model standard deviation. Atoll will display the shadowing margin of the signal level.
- EcI0: The EcI0 standard deviation. Atoll will display the EcI0 shadowing margin and the resulting forward
link pilot macro-diversity gains. The macro-diversity gains will be calculated using the values you enter in
1st - 2nd Best Signal Difference and 2nd - 3rd Best Signal Difference.
- UL EbNt: The EbNt reverse link standard deviation. Atoll will display the EbNt reverse link shadowing
margin and the resulting reverse link macro-diversity gains. The macro-diversity gains will be calculated
using the values you enter in 1st - 2nd Best Signal Difference and 2nd - 3rd Best Signal Difference.
- DL EbNt: The EbNt forward link standard deviation. Atoll will display the EbNt forward link shadowing
margin.
5. If you select "EcI0" or "EbNt UL" as the standard deviation under Standard Deviation, you can enter the differ-
ences that will be used to calculate the macro-diversity gain under Macro-Diversity Parameters:
- 1st - 2nd Best Signal Difference: If you selected "EcI0" as the standard deviation under Standard Devia-
tion, enter the allowed EcI0 difference between the best server and the second one. This value is used to
calculate forward link macro-diversity gains. If you selected "EbNt UL" as the standard deviation under
Standard Deviation, enter the allowed Eb/Nt difference between the best server and the second one. This
value is used to calculate reverse link macro-diversity gains.
- 2nd - 3rd Best Signal Difference: If you selected "EcI0" as the standard deviation under Standard Devia-
tion, enter the allowed EcI0 difference between the second-best server and the third one. This value is used
to calculate forward link macro-diversity gains. If you selected "EbNt UL" as the standard deviation under
Standard Deviation, enter the allowed EbNt difference between the second-best server and the third one.
This value is used to calculate reverse link macro-diversity gains.
6. Click Calculate. The calculated shadowing margin is displayed. If you selected "EcI0" or "EbNt UL" as the
standard deviation under Standard Deviation, Atoll also displays the macro-diversity gains for two links and for
three links.
7. Click Close to close the dialogue.
4. In the row marked with the New Row icon ( ), enter a Name for the new domain.
5. Click in another cell of the table to create the new domain and add a new blank row to the table.
6. Double-click the domain to which you want to add a group. The domains Properties dialogue appears.
7. Under Groups, enter the following information for each group you want to create. The definition of the group must
be consistent with the default domain defined using the PILOT_INC parameter.
- Group: Enter a name for the new PN offset group.
- Min.: Enter the lowest available PN offset in this groups range.
- Max: Enter the highest available PN offset in this groups range.
- Step: Enter the separation interval between each PN offset. It must be the same as the PILOT_INC value.
- Excluded: Enter the PN offsets in this range that you do not want to use.
- Extra: Enter any additional PN offsets (i.e., outside the range defined by the Min. and Max fields) you want to
add to this group. You can enter a list of PN offsets separated by either a comma, semi-colon, or a space. You
can also enter a range of PN offsets separated by a hyphen. For example, entering, "1, 2, 3-5" means that the
extra PN offsets are "1, 2, 3, 4, 5."
8. Click in another cell of the table to create the new group and add a new blank row to the table.
Atoll
RF Planning and Optimisation Software
Chapter 12: TD-SCDMA Networks
12 TD-SCDMA Networks
Atoll enables you to create and modify all aspects of a TD-SCDMA network. Once you have created the network, Atoll
offers many tools to let you verify it. Based on the results of your tests, you can modify any of the parameters defining the
network.
The process of planning and creating a TD-SCDMA network is outlined in "Designing a TD-SCDMA Network" on page 727.
Creating the network of base stations is explained in "Planning and Optimising TD-SCDMA Base Stations" on page 728.
Allocating neighbours and scrambling codes is also explained. In this section, you will also find information on how you
can display information about base stations on the map and how you can use the tools in Atoll to study base stations.
In "Studying Network Capacity" on page 816, using traffic maps to study network capacity is explained. Creating simula-
tions using traffic map information and analysing the results of simulations is also explained.
Using test mobile data paths to verify the network is explained in "Optimising and Verifying Network Capacity" on
page 844. How to filter imported test mobile data paths, and how to use the data in coverage predictions is also explained.
The steps involved in planning a TD-SCDMA network are described below. The numbers refer to Figure 12.1.
5. Before making more advanced coverage predictions, you need to define cell load conditions ( 5 ).
You can define cell load conditions in the following ways:
- You can generate realistic cell load conditions by creating a simulation based on a traffic map ( 5a and 5b )
(see "Studying Network Capacity" on page 816).
- You can define them manually either on the Cells tab of each transmitters Properties dialogue or in the Cells
table (see "Creating or Modifying a Cell" on page 736) ( 5c ).
6. Make TD-SCDMA-specific coverage predictions using the defined cell load conditions ( 6 ).
- "Signal Quality Coverage Predictions" on page 774
- "HSDPA Coverage Prediction" on page 793.
- Name: Atoll automatically enters a default name for each new site. You can modify the name here. If you want
to change the default name that Atoll gives to new sites, see the Administrator Manual.
- Position: By default, Atoll places the new site at the centre of the map window. You can modify the location
of the site here.
Tip: While this method allows you to place a site with precision, you can also place sites using
the mouse and then position them precisely with this dialogue afterwards. For information
on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 31.
- Altitude: The altitude, as defined by the DTM for the location specified under Position, is given here. You can
specify the actual altitude under Real, if you want. If an altitude is specified here, Atoll will use this value for
calculations.
- Comments: You can enter comments in this field if you want.
The Equipment tab:
- Equipment: You can select equipment from the list. To create new site equipment, see "Creating Site Equip-
ment" on page 860. If no equipment is assigned to the site, Atoll considers that the JD factor and MCJD factor
have a value of "0".
- Frequency Band: You can select a Frequency Band for the transmitter. Once you have selected the fre-
quency band, you can click the Browse button ( ) to access the properties of the frequency band. For infor-
mation on the frequency band Properties dialogue, see "Defining Frequency Bands" on page 852.
- Position relative to the site: You can modify the Position relative to the site, if you want.
The Transmitter tab (see Figure 12.3):
- Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are dis-
played in red in the Transmitters folder of the Data tab.
Note: Only active transmitters are taken into consideration during calculations.
- TransmissionReception: Under TransmissionReception, you can see the total losses and the noise figure
of the transmitter. Atoll calculates losses and noise according to the characteristics of the equipment assigned
to the transmitter. Equipment can be assigned by using the Equipment Specifications dialogue which
appears when you click the Equipment button.
- On the Equipment Specifications dialogue (see Figure 12.4), the equipment you select and the gains and
losses you define are used to provide initial values for total transmitter UL and DL losses:
- TMA: You can select a tower-mounted amplifier (TMA) from the list. You can click the Browse button
( ) to access the properties of the TMA. For information on creating a TMA, see "Defining TMA Equip-
ment" on page 147.
- Feeder: You can select a feeder cable from the list. You can click the Browse button ( ) to access the
properties of the feeder. For information on creating a feeder cable, see "Defining Feeder Cables" on
page 147.
- BTS: You can select a base transceiver station (BTS) equipment from the BTS list. You can click the
Browse button ( ) to access the properties of the BTS. For information on creating a BTS, see "Defin-
ing BTS Equipment" on page 148.
- Feeder Length: You can enter the feeder length at transmission and reception.
- Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value
you enter must be positive.
- Receiver Antenna Diversity Gain: You can enter a receiver antenna diversity gain. The value you enter
must be positive.
Note: Any loss related to the noise due to a transmitters repeater is included in the calculated
losses. Atoll always considers the values in the Real boxes in coverage predictions even
if they are different from the values in the Computed boxes. The information in the real
BTS Noise Figure reception box is calculated from the information you entered in the
Equipment Specifications dialogue. You can modify the real Total Losses at
transmission and reception and the real BTS Noise Figure at reception if you want. Any
value you enter must be positive.
- Diversity: Under Diversity, you can select the type of diversity from the Transmission and Reception lists.
- Antennas:
- HeightGround: The HeightGround box gives the height of the antenna above the ground. This is added
to the altitude of the site as given by the DTM. If the transmitter is situated on a building, the height entered
must include the height of building.
- Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the
Browse button ( ) to access the properties of the antenna. The other fields, Azimuth, Mechanical
Downtilt, and Additional Electrical Downtilt, display additional antenna parameters.
Antenna models that you have added to an antenna list in order to create Grids of Beams are excluded
from the list of antennas available for the main antenna model. For more information on Grid of Beams
modelling, see "Grid of Beams (GOB) Modelling" on page 854.
- Smart Antenna: Under Smart Antenna, the available smart antenna equipment are visible in the Equip-
ment list. You can click the Browse button ( ) to access the properties of the smart antenna equip-
ment. When you click the Browse button ( ), the Smart Antenna Equipment Properties dialogue
appears. If you are using a grid of beams or an adaptive beam, under Smart Antenna Model, clicking the
Parameters button opens the Grid of Beams (GOB) Modelling or Adaptive Beam Modelling dialogue.
Under Patterns, clicking the Combined button opens a dialogue displaying the combined antenna
patterns of all the smart antenna beams and the main antenna (see Figure 12.5).
For more information on smart antenna equipment, see "Smart Antenna Equipment" on page 857. The
smart antenna has the same height and tilt as the main antenna.
If you have smart antenna equipment based on Grid of Beams (GOB) or Adaptive Beam modelling, it is
recommended to verify that the smart antenna beams be consistent with the main antenna pattern.
You can use the combined antenna pattern display to understand any inconsistencies in smart antenna
results. If the gird of beams and the main antenna do not have the same gains, the smart antenna could
provide worse results than the main antenna for traffic timeslots.
- Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power, which is
the percentage of power reserved for this particular antenna. For example, for a transmitter with one
secondary antenna, if you reserve 40 % of the total power for the secondary antenna, 60 % is available
for the main antenna.
For information on working with data tables, see "Working with Data Tables" on page 50.
The main antenna is used to transmit the pilot signals. Coverage predictions based on the P-CCPCH signal are
performed using the main antenna. It is also used for traffic signals if there is no smart antenna equipment selected
for the transmitter.
If there is smart antenna equipment assigned to the transmitter, traffic data is transmitted and received using the
smart antenna, while the pilot and other common channels are transmitted using the main antenna.
Important: Transmitters that are using smart antenna equipment should not be assigned any
secondary antennas, remote antennas, or repeaters.
P-CCPCH Power [TS0] (dBm): The power of the P-CCPCH channel transmitted on TS0.
Other CCH power [TS0] (dBm): The average power of the control channels (including S-CCPCH) that are not
transmitted continuously on TS0. For example, if P dBm is transmitted during 1 s over a period of 10 s , you
should enter P/10 dBm in order to correctly represent the average interference from these channels.
P-CCPCH RSCP T_Comp [TS0] (dB): The P-CCPCH RSCP comparative threshold for determining the transmit-
ters to keep in the list of potential servers. This parameter is used in the baton handover coverage prediction along
with P-CCPCH RSCP T_Add and P-CCPCH RSCP T_Drop parameters set for different mobility types.
DwPCH Power [DwPTS] (dBm): The power transmitted on the DwPTS timeslot.
Note: By default, the DwPCH power and the Other CCH power are set as absolute values. You
can set these values as relative to the pilot power by right-clicking the Transmitters folder
on the Data tab of the Explorer window and selecting Properties from the context menu.
Then, on the Global Parameters tab of the Properties dialogue, under DL Powers, you
can select Relative to Pilot. The DwPCH power and the Other CCH power values are
automatically converted and set as relative to the pilot power.
Max Difference Between 2 Transmit Powers (dB): The maximum difference between the powers transmitted
by this cell on two DCH. This parameter is used during Monte Carlo simulations in order to avoid too much differ-
ence between users in the same cell.
Scrambling Code Domain: The scrambling code domain to which the allocated scrambling code belongs. This
and the scrambling code reuse distance are used by the automatic scrambling code allocation algorithm.
SC Reuse Distance: The scrambling code reuse distance. This and the scrambling code domain are used by the
scrambling code planning algorithm.
Scrambling Code: The scrambling code allocated to the cell.
Timeslot Configuration: The configuration of the traffic timeslots in the frame. When the UpPCH channel is
present in the UpPTS timeslot, you can select from five possible timeslot configurations, i.e., (D)UDDDDD,
(D)UUDDDD, (D)UUUDDD, (D)UUUUDD, and (D)UUUUUD. When the UpPCH is shifted to TS1, you can select
from two more timeslot configurations, i.e., (D)UpUDDDD, (D)UpUUDDD. When UpPCH is shifted, TS1 is
blocked, i.e., it is not used to carry traffic. For more information on UpPCH shifting and studying the interference
on the UpPCH, see "Studying UpPCH Interference" on page 790.
There are two switching points in the frame, one after the first mandatory downlink timeslot (D), and the other can
be after 1 to 5 uplink timeslots. The symmetric configuration is selected by default.
Required UL Resource Units: The number of resource units required in the uplink.
Required DL Resource Units: The number of resource units required in the downlink. Atoll can calculate the
number of required resource units in the uplink and downlink. For information on calculating network capacity, see
"TD-SCDMA Network Capacity" on page 816.
Comments: If desired, you can enter any comments in this field.
HSDPA: The HSDPA check box is selected if the cell has HSDPA functionality. When the HSDPA check box is
selected, the following fields are also available:
- HS-PDSCH Dynamic Power Allocation: If you are modelling dynamic power allocation, you should select
the HS-PDSCH Dynamic Power Allocation check box and enter a value in Available HS-PDSCH Power
per DL TS (dBm). The HS-PDSCH power calculated for any downlink timeslot during a simulation cannot
exceed the value defined in Available HS-PDSCH Power per DL TS (dBm). During simulations, Atoll first
allocates power to R99 users and then dynamically allocates the remaining power of the cell to the HS-PDSCH
channels of HSDPA users. At the end of the simulation, you can commit the calculated HS-PDSCH power and
total power values to each cell and timeslot.
Note: In the context of dynamic power allocation, the total power is the maximum power minus
the power headroom.
- Available HS-PDSCH Power per DL TS (dBm): When you are modelling static power allocation, the HS-
PDSCH Dynamic Power Allocation check box is cleared and the HS-PDSCH power available for each
downlink timeslot is entered in this box. This is the default value of power available per timeslot for the HS-
PDSCH channels of HSDPA users. In case of dynamic HS-PDSCH power allocation, the value entered here
represents the maximum power for the HS-PDSCH of HSDPA users per timeslot.
- Power Headroom (dB): The power headroom is a reserve of power that Atoll keeps for Dedicated Physical
Channels (DPCH) in case of fast fading. During simulation, HSDPA users will not be connected if the cell
power remaining after serving R99 users is less than the power headroom value.
- HS-SCCH Dynamic Power Allocation: If you are modelling dynamic power allocation, you should select the
HS-SCCH Dynamic Power Allocation check box and enter a value in HS-SCCH Power (dBm). The HS-
SCCH power calculated for HS-SCCH channel during a simulation cannot exceed the value defined in
HS-SCCH Power (dBm). During power control, Atoll controls HS-SCCH power in order to meet the minimum
quality threshold (as defined for each mobility type).
- HS-SCCH Power (dBm): When you are modelling static power allocation, the HS-SCCH Dynamic Power
Allocation check box is cleared and the actual power per HS-SCCH channel is entered in this box. In case of
dynamic HS-SCCH power allocation, the value entered here represents the maximum power for the HS-
SCCH channel per HSDPA user.
- Number of HS-SCCH Channels: The maximum number of HS-SCCH channels for this cell. Each HSDPA
user consumes one HS-SCCH channel. Therefore, at any given time (over a transmission time interval), the
number of HSDPA users cannot exceed the number of HS-SCCH channels per cell.
- HS-SICH Dynamic Power Allocation: If you are modelling dynamic power allocation, you should select the
HS-SICH Dynamic Power Allocation check box. During power control, Atoll controls HS-SICH power of the
HSDPA-capable terminal in order to meet the minimum quality threshold (as defined for each mobility type) in
the uplink.
- Number of HS-SICH Channels: The maximum number of HS-SICH channels for this cell. Each HSDPA user
consumes one HS-SICH channel. Therefore, at any given time (over a transmission time interval), the number
of HSDPA users cannot exceed the number of HS-SICH channels per cell.
- Min. Number of HS-PDSCH Codes: The minimum number of OVSF codes available for HS-PDSCH chan-
nels. This value will be taken into account during simulations in order to find a suitable bearer.
- Max Number of HS-PDSCH codes: The maximum number of OVSF codes available for HS-PDSCH chan-
nels. This value will be taken into account during simulations and coverage predictions in order to find a suit-
able bearer.
- Max Number of HSDPA Users: The maximum number of HSDPA bearer users that this cell can support at
any given time.
- HSDPA Scheduler Algorithm: The scheduling technique that will be used to rank the HSDPA users to be
served:
- Max C/I: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined) are
scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descend-
ing order by the channel quality indicator (CQI).
- Round Robin: HSDPA users are scheduled in the same order as in the simulation (i.e., in random order).
- Proportional Fair: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users
defined) are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted
in descending order according to a random parameter which corresponds to a combination of the user
rank in the simulation and the channel quality indicator (CQI).
Note: The random parameter is calculated by giving both the user simulation rank and the CQI a
weight of 50 %. You can change the default weights by setting the appropriate options in
the atoll.ini file. For more information, see the Administrator Manual.
Max Number of Intra-technology Neighbours: The maximum number of intra-technology neighbours for this
cell. This value is used by the intra-technology neighbour allocation algorithm.
Max Number of Inter-technology Neighbours: The maximum number of inter-technology neighbours for this
cell. This value is used by the inter-technology neighbour allocation algorithm.
Neighbours: You can access a dialogue in which you can set both intra-technology and inter-technology neigh-
bours by clicking the Browse button ( ). For information on defining neighbours, see "Planning Neighbours" on
page 797.
Timeslots: You can access information about the cells traffic timeslots, i.e, for each of the six traffic timeslots, by
clicking the Browse button ( ) (see Figure 12.6).
Tip: The Browse buttons ( ) might not be visible in the Neighbours and Timeslot boxes if
this is a new cell. You can make the Browse buttons appear by clicking Apply.
- Blocked: If this timeslot is to be blocked, i.e., not used for traffic, you must select the Blocked check box. A
blocked timeslot is not used by the Dynamic Channel Allocation (DCA) algorithm and does not carry any traffic.
- Timeslot Type: The type of traffic that the timeslot can carry, i.e., only R99 users, only HSDPA users, or R99
and HSDPA users.
- Other CCH power (dBm): The power of other common channels (S-CCPCH, FPACH, and PICH) on the
traffic timeslot. Other common control channels can be transmitted on a downlink traffic timeslot using the
main antenna.
- DL Traffic Power (dBm): The traffic power transmitted on downlink is the power necessary to serve R99 or
HSDPA users on the downlink timeslots. This value can be a simulation result or can be entered by the user.
- Max DL Load (% Pmax): The percentage of the maximum downlink power (set in Max Power [Traffic TS])
not to be exceeded. This limit will be taken into account during simulations if the option DL Load is selected.
If the DL load option is not selected during a simulation, this value is not taken into consideration.
- Available HS-PDSCH Power (dBm): When you are modelling static power allocation, the HS-PDSCH
Dynamic Power Allocation check box in the Cells tab is cleared and the available HS-PDSCH power for the
timeslot is entered in this box. This is the power available for the HS-PDSCH channels of HSDPA users. If no
value is defined here, the value defined in Available HS-PDSCH Power per DL TS for the cell is considered
for the timeslot. In case of dynamic HS-PDSCH power allocation, the value entered here represents the max-
imum power for HS-PDSCH of HSDPA users.
- Min. Number of HS-PDSCH Codes: The minimum number of OVSF codes available for HS-PDSCH chan-
nels. This value will be taken into account during simulations in order to find a suitable bearer. If no value is
defined here, the value defined for the cell is considered for the timeslot.
- Max Number of HS-PDSCH codes: The maximum number of OVSF codes available for HS-PDSCH chan-
nels. This value will be taken into account during simulations and coverage predictions in order to find a suit-
able bearer. If no value is defined here, the value defined for the cell is considered for the timeslot.
- UL Load Factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between
the uplink total interference and the uplink total noise. This value can be a simulation result or can be entered
by the user.
- Max UL Load Factor (%): The maximum uplink load factor not to be exceeded. This limit can be taken into
account during the simulation.
- Angular Distribution of UL and DL Loads: The angular distribution of downlink transmitted power and uplink
loads calculated for cells whose transmitters have smart antenna equipment. This value is a simulation result.
- Resource Units Overhead: The number of resource units corresponding to overhead. You can enter the
Resource Units Overhead, which is taken into consideration during network dimensioning. For information
on calculating network capacity, see "TD-SCDMA Network Capacity" on page 816.
MBMS: You can access a dialogue in which you can set MBMS channel powers, channel data rates, and the
timeslots allocated to MBMS channels by clicking the Browse button ( ). This option is only available if the
optional MBMS feature has been activated. Activating this optional feature requires data structure modifications
(for more information, see the Administrator Manual).
If an MBMS SCCPCH is not used, you should leave the field corresponding to its transmission power empty. The
MBMS channel powers are used to calculate the optional MBMS service area Eb/Nt coverage prediction, and are
taken into account in other calculations in the same way as the other common control channel power, i.e., for the
calculation of interference.
Tip: The Browse button ( ) might not be visible in the MBMS box if this is a new cell. You
can make the Browse button appear by clicking Apply.
4. Click OK.
Tips:
If you are creating several transmitters at the same time, or modifying several existing trans-
mitters, you can do it more quickly by editing or pasting the data directly in the Transmitters
table. You can open the Transmitters table by right-clicking the Transmitters folder on the
Data tab of the Explorer window and selecting Open Table from the context menu. For infor-
mation on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
If you want to add a transmitter to an existing site on the map, you can add the transmitter by
right-clicking the site and selecting New Transmitter from the context menu.
Tips:
If you are creating or modifying several cells at the same time, you can do it more quickly by
editing the data directly in the Cells table. You can open the Cells table by right-clicking the
Transmitters folder on the Data tab of the Explorer window and selecting Cells > Global >
Open Table from the context menu. You can either edit the data in the table, paste data into
the table (see "Copying and Pasting in Tables" on page 56), or import data into the table (see
"Importing Tables from Text Files" on page 59).
If you want to add a cell to an existing transmitter on the map, you can add the cell by right-
clicking the transmitter and selecting New Cell from the context menu.
3. In the map window, move the pointer over the map to where you would like to
place the new station. The exact coordinates of the pointers current location
are visible in the Status bar.
Tips:
To place the base station more accurately, you can zoom in on the map before you click the
New Station button. For information on using the zooming tools, see "Changing the Map
Scale" on page 38.
If you let the pointer rest over the base station you have placed, Atoll displays its tip text with
its exact coordinates, allowing you to verify that the location is correct.
You can also place a series of base stations using a station template. You do this by defining an area on the map where
you want to place the base stations. Atoll calculates the placement of each base station according to the defined hexag-
onal cell radius in the station template. For information on defining the cell radius, see "Creating or Modifying a Station
Template" on page 738.
To place a series of base stations within a defined area:
1. In the Radio toolbar, select a template from the list.
2. Click the Hexagonal Design button ( ), to the left of the template list. A hexagonal design is a group of base
stations created from the same station template.
Note: If the Hexagonal Design button is not available ( ), the hexagonal cell radius for this
template is not defined. For information on defining the cell radius, see "Creating or
Modifying a Station Template" on page 738.
3. Draw a zone delimiting the area where you want to place the series of base stations:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
Atoll fills the delimited zone with new base stations and their hexagonal shapes. Base station objects such as
sites and transmitters are also created and placed into their respective folders.
You can work with the sites and transmitters in these base stations as you work with any base station object, adding, for
example, another antenna to a transmitter.
When you place a new base station using a station template as explained in "Placing a New Base Station Using a Station
Template" on page 736, the site is created at the same time as the base station. However, you can also place a new base
station on an existing site.
To place a base station on an existing site:
1. On the Data tab, clear the display check box beside the Hexagonal Design folder.
2. In the Radio toolbar, select a template from the list.
4. Move the pointer to the site on the map. When the frame appears around the site, indicating it is selected, click to
place the base station.
- Smart Antenna: Under Smart Antenna, the available smart antenna equipment are visible in the Equip-
ment list.
- Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both
the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Managing
Calculations in Atoll.
5. Click the Transmitter tab. On this tab (see Figure 12.9), if the Active check box is selected, you can modify the
following:
- Under TransmissionReception, you can click the Equipment button to open the Equipment Specifica-
tions dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or base transceiver station
(BTS). For information on the Equipment Specifications dialogue, see "Transmitter Description" on
page 729.
The information in the real Total Losses in transmission and reception boxes is calculated from the informa-
tion you entered in the Equipment Specifications dialogue (see Figure 12.4 on page 731). Any loss related
to the noise due to a transmitters repeater is included in the calculated losses. Atoll always considers the
values in the Real boxes in coverage predictions even if they are different from the values in the Computed
boxes. You can modify the real Total Losses at transmission and reception if you want. Any value you enter
must be positive.
The information in the real BTS Noise Figure reception box is calculated from the information you entered in
the Equipment Specifications dialogue. You can modify the real BTS Noise Figure at reception if you want.
Any value you enter must be positive.
- Under Diversity, you can select the diversity from the Transmission and Reception lists.
6. Click the TD-SCDMA tab. On this tab (see Figure 12.10), you modify the Carriers (each corresponding to a cell)
that this base station supports. For information on carriers and cells, see "Cell Description" on page 732.
- You can select whether the transmitters created with this template are compatible with N-Frequency Mode
or not. If you select the N-Frequency Mode check box, the transmitters created using this station template
will have at least one master carrier with P-CCPCH, DwPCH, and Other CCH powers. If there is more than
one carrier on the transmitters, the rest of the carriers will be slave carriers. Slave carriers will not have any
P-CCPCH, DwPCH, or Other CCH powers. If you do not select the N-Frequency Mode check box, the trans-
mitters created using this template will have stand-alone carriers.
- You can select the Carrier numbers for each sector of the station template. To select the carriers to be added
to the sectors of a base station created using this station template:
i. Click the Browse button ( ). The Carriers per Sector dialogue appears.
ii. In the Carriers per Sector dialogue, select the carriers to be created for each sector of the station.
iii. Click OK.
- Under Power, you can modify the Max, P-CCPCH, DwPCH, and the Other CCH powers.
- You can select a default Timeslot Configuration for the cells.
- You can also select the default Equipment for the sites.
7. Click the HSDPA tab. On this tab (see Figure 12.11), if the HSDPA Supported check box is selected, you can
modify the following (for more information on the fields, see "Cell Description" on page 732):
- Under HSDPA,
- You can define a Power Headroom.
- Under HS-SICH,
- You can select either Static or Dynamic Allocation Strategy for HS-SICH power.
- You can define the Number of Channels for HS-SICH.
- Under HS-PDSCH,
- You can select either Static or Dynamic Allocation Strategy for HS-PDSCH power.
- You can enter the Fixed Power, if you selected Static power allocation.
- You can enter the Min. and Max Number of Codes for HS-PDSCH.
- Under HS-SCCH,
- You can select either Static or Dynamic Allocation Strategy for HS-SCCH power.
- You can enter the Fixed Power for HS-SCCH, if you selected Static power allocation.
- You can define the Number of Channels for HS-SCCH.
- Under Scheduler,
- You can select the scheduler Algorithm.
- You can enter the Max Number of Users.
When you create an HSDPA-capable base station using a station template, the timeslots of all the cells created
automatically are by default set to support R99 and HSDPA.
9. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the
Sites table, or if you have defined an additional field in the Station Template Properties dialogue.
10. When you have finished setting the parameters for the station template, click OK to close the dialogue and save
your changes.
v. For Type, you can select from Text, Short integer, Long integer, Single, Double, TrueFalse,
DateTime, and Currency. If you choose text, you can also set the field Size (in characters), and create
a Choice list, by entering the possible selections directly in the Choice list window and pressing ENTER
after each one.
vi. Enter, if desired, a Default value for the new field.
vii. Click OK to close the Field Definition dialogue and save your changes.
- Delete: To delete a user-defined field:
i. Select the user-defined field you want to delete.
ii. Click the Delete button. The user-defined field appears in strikethrough. It will be definitively deleted when
you close the dialogue.
- Properties: To modify the properties of a user-defined field:
i. Select the user-defined field you want to modify.
ii. Click the Properties button. The Field Definition dialogue appears.
iii. Modify any of the properties as desired.
iv. Click OK to close the Field Definition dialogue and save your changes.
6. Click OK.
Tips:
To place the station more accurately, you can zoom in on the map before you select Duplicate
from the context menu. For information on using the zooming tools, see "Changing the Map
Scale" on page 38.
If you let the pointer rest over the station you have placed, Atoll displays tip text with its exact
coordinates, allowing you to verify that the location is correct.
You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to
place each duplicate base station.
For more information on the site, transmitter, cell, and timeslot properties, see "Definition of a Base Station" on page 729.
Note: When you import data into your current Atoll document, the coordinate system of the
imported data must be the same as the display coordinate system used in the document.
If you cannot change the coordinate system of your source data, you can temporarily
change the display coordinate system of the Atoll document to match the source data.
For information on changing the coordinate system, see "Setting a Coordinate System"
on page 92.
Important: The table you copy data from must have the same column layout as the table you are
pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
Importing data: If you have data in text or comma-separated value (CSV) format, you can import it into the tables
in the current document. If the data is in another Atoll document, you can first export it in text or CSV format and
then import it into the tables of your current Atoll document. When you are importing, Atoll allows you to select
what values you import into which columns of the table.
When you create a group of base stations by importing data, you must import site data in the Sites table, trans-
mitter data in the Transmitters table, and cell data in the Cells table, in that order.
For information on exporting table data, see "Exporting Tables to Text Files" on page 58. For information on
importing table data, see "Importing Tables from Text Files" on page 59.
Note: You can quickly create a series of base stations for study purposes using the Hexagonal
Design tool on the Radio toolbar. For information, see "Placing a New Base Station
Using a Station Template" on page 736.
( and ). For information on defining the transmitter symbol, see "Defining the Display Type" on page 34.
Notes:
It is advised not to assign repeaters to transmitters that have smart antenna equipment
assigned to them.
Broadband repeaters are not modelled. Atoll assumes that all carriers of 3G donor transmitters
are amplified.
3. Select Repeaters > Equipment from the context menu. The Repeater Equipment table appears.
4. To create repeater equipment, enter the following in the row marked with the New Row icon ( ):
a. Enter a Name and Manufacturer for the new equipment.
b. Enter a Noise Figure. The repeater causes a rise in noise at the donor transmitter, so the noise figure is used
to calculate the UL loss to be added to the donor transmitter UL losses. The noise figure must be a positive
value.
c. Enter minimum and maximum repeater amplification gains in the Min. Gain and Max Gain columns. These
parameters enable Atoll to ensure that the user-defined amplifier gain is consistent with the limits of the equip-
ment if there are any.
d. Enter a Gain Increment. Atoll uses the increment value when you increase or decrease the repeater amplifier
gain using the buttons to the right of the Amplification box ( ) on the General tab of the repeater Properties
dialogue.
e. Enter the maximum power that the equipment can transmit on the downlink in the Maximum Downlink Power
column. This parameter enables Atoll to ensure that the downlink power after amplification does not exceed
the limit of the equipment.
f. If desired, enter a Maximum Uplink Power, an Internal Delay and Comments. These fields are for informa-
tion only and are not used in calculations.
5. To modify repeater equipment, change the parameters in the row containing the repeater equipment you want to
modify.
2. Click the arrow next to New Repeater or Remote Antenna button ( ) on the Radio toolbar.
3. Select Repeater from the menu.
4. Click the map to place the repeater. The repeater is placed on the map, represented by a symbol ( ) in the
same colour as the donor transmitter or repeater. By default, the repeater has the same azimuth as the donor
transmitter or repeater. Its tooltip and label display the same information as displayed for the donor transmitter or
repeater. As well, its tooltip and label identify the repeater and the donor transmitter or repeater.
For information on defining the properties of the new repeater, see "Defining the Properties of a Repeater" on
page 745.
Note: You can see to which base station the repeater is connected by clicking it; Atoll displays
a link to the donor transmitter or repeater.
Important: The table you copy data from must have the same column layout as the table you are
pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
- You can change the Donor transmitter by selecting it from the Donor list. Clicking the Browse button ( )
opens the Properties dialogue of the donor transmitter.
- You can change the Site on which the repeater is located. Clicking the Browse button ( ) opens the Prop-
erties dialogue of the site.
- You can enter a Position relative to site location, if the repeater is not located on the site itself.
- You can select equipment from the Equipment list. Clicking the Browse button ( ) opens the Properties
dialogue of the equipment.
- You can change the Amplification gain. The amplification gain is used in the link budget to evaluate the
repeater total gain.
4. Click the Donor Side tab. You can modify the following parameters:
- Under Donor-Repeater Link, select a Link Type.
- If you select Microwave Link, enter the Propagation Losses and continue with step 5.
- If you select Air Link, select a Propagation Model and enter the Propagation Losses or click Calculate
to determine the actual propagation losses between the donor and the repeater. If you do not select a
propagation model, the propagation losses between the donor transmitter and the repeater are calculated
using the ITU 526-5 propagation model.
When you create an off-air repeater, it is assumed that the link between the donor transmitter and the re-
peater has the same frequency as the network.
Important: If you want to create a remote antenna, you must select Optical Fibre Link.
- If you selected Air Link under Donor-Repeater Link, enter the following information under Antenna:
i. Select a Model from the list. You can click the Browse button ( ) to access the properties of the
antenna.
ii. Enter the height off the ground of the antenna in the HeightGround box. This will be added to the altitude
of the transmitter as given by the DTM.
iii. Enter the Azimuth and the Mechanical Downtilt.
Note: You can click the Calculate button ( ) to update azimuth and downtilt values after
changing the repeater donor side antenna height or the repeater location. If you choose
another site or change site coordinates in the General tab, click Apply before clicking the
Calculate button.
- If you selected Air Link under Donor-Repeater Link, enter the following information under Feeders:
i. Select a Type of feeder from the list. You can click the Browse button ( ) to access the properties of
the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
5. Click the Coverage Side tab. You can modify the following parameters:
- Select the Active check box. Only active repeaters (displayed in red in the Transmitters folder in the Data
tab of the Explorer window) are calculated.
- Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual
gains. If you have modified any parameter in the General, Donor Side, or Coverage Side tabs, click Apply
before clicking the Calculate button. Atoll uses the DL total gain values to calculate the signal level received
from the repeater. The UL total gain value is considered in UL EbNt or CI service area coverage predictions.
The DL total gain is applied to each power (P-CCPCH power, DwPCH power, etc.). It takes into account losses
between the donor transmitter and the repeater, donor characteristics (donor antenna gain, reception feeder
losses), amplification gain, and coverage characteristics (coverage antenna gain and transmission feeder
losses).
The UL total gain is applied to each terminal power. It takes into account losses between the donor transmitter
and the repeater, donor part characteristics (donor antenna gain, transmission feeder losses), amplification
gain and coverage part characteristics (coverage antenna gain and reception feeder losses).
ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( ) to access the
properties of the antenna. Then, enter the Azimuth, the Mechanical Downtilt, and the Additional Elec-
trical Downtilt. By default, the characteristics (antenna, azimuth, height, etc.) of the repeater coverage
side correspond to the characteristics of the donor transmitter.
iii. Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power. For infor-
mation on working with data tables, see "Working with Data Tables" on page 50.
i. Select a Type of feeder from the list. You can click the Browse button ( ) to access the properties of
the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
- Under Losses, Atoll displays the Loss Related to Repeater Noise Rise.
6. Click the Propagation tab. Since repeaters are taken into account during calculations, you must set the propaga-
tion parameters. On the Propagation tab, you can modify the Propagation Model, Radius, and Resolution for
both the Main Matrix and the Extended Matrix. By default, the propagation characteristics of the repeater (model,
calculation radius, and grid resolution) are the same as those of the donor transmitter. For information on propa-
gation models, see Chapter 5: Managing Calculations in Atoll.
Note: You can prevent Atoll from updating the UL and DL total gains of selected repeaters by
creating a custom field called "FreezeTotalGain" in the Repeaters table and setting the
value of the field to "True." Afterwards, when you select Repeaters > Calculate Gains
from the Transmitters context menu, Atoll will only update the UL and DL total gains for
repeaters with the custom field "FreezeTotalGain" set to "False."
You can update the propagation losses of all off-air repeaters by selecting Repeaters > Calculate Donor Side
Propagation Losses from the Transmitters context menu.
You can select a repeater on the map and change its azimuth (see "Changing the Azimuth of the Antenna Using
the Mouse" on page 32) or its position relative to the site (see "Changing the Position of the Transmitter Relative
to the Site" on page 32).
Note: You should not assign remote antennas to transmitters that have smart antenna
equipment assigned to them.
Note: Ensure that the remote antennas donor transmitter does not have any antennas.
2. Click the arrow next to New Repeater or Remote Antenna button ( ) on the Radio toolbar.
3. Select Remote Antenna from the menu.
4. Click the map to place the remote antenna. The remote antenna is placed on the map, represented by a symbol
( ) in the same colour as the donor transmitter. By default, the remote antenna has the same azimuth as the
donor transmitter. Its tooltip and label display the same information as displayed for the donor transmitter. As well,
its tooltip and label identify the remote antenna and the donor transmitter.
For information on defining the properties of the new remote antenna, see "Defining the Properties of a Remote
Antenna" on page 748.
Note: You can see to which base station the remote antenna is connected by clicking it; Atoll
displays a link to the donor transmitter.
Important: The table you copy data from must have the same column layout as the table you are
pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
4. Click the Donor Side tab. You can modify the following parameters:
- Under Donor-Repeater Link, select Optical Fibre Link and enter the Cable Losses.
5. Click the Coverage Side tab. You can modify the following parameters:
- Select the Active check box. Only active remote antennas (displayed with in red in the Transmitters folder in
the Data tab of the Explorer window) are calculated.
- Under Total Gains, enter the gains in the Downlink and Uplink or click Calculate to determine the actual
gains. If you have modified any parameter on the General, Donor Side, or Coverage Side tabs, click Apply
before clicking the Calculate button. Atoll uses the DL total gain values to calculate the signal level received
from the remote antenna. The UL total gain value is considered in UL EbNt or CI service area coverage pre-
dictions.
The DL total gain is applied to each power (P-CCPCH power, DwPCH power, etc.). It takes into account losses
between the donor transmitter and the remote antenna.
The UL total gain is applied to each terminal power. It takes into account losses between the donor transmitter
and the remote antenna.
ii. Under Main Antenna, select a Model from the list. You can click the Browse button ( ) to access the
properties of the antenna. Then, enter the Azimuth, the Mechanical Downtilt, and the Additional Elec-
trical Downtilt.
iii. Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power. For infor-
mation on working with data tables, see "Working with Data Tables" on page 50.
- Under Feeders, you can modify the following information:
i. Select a Type of feeder from the list. You can click the Browse button ( ) to access the properties of
the feeder.
ii. Enter the Length of the feeder cable at Transmission and at Reception.
6. Click the Propagation tab. Since remote antennas are taken into account during calculations, you must set prop-
agation parameters as with transmitters. On the Propagation tab, you can modify the Propagation Model,
Radius, and Resolution for both the Main Matrix and the Extended Matrix. By default, the propagation charac-
teristics of the remote antenna (model, calculation radius, and grid resolution) are the same as those of the donor
transmitter. For information on propagation models, see Chapter 5: Managing Calculations in Atoll.
Note: You can prevent Atoll from updating the UL and DL total gains of selected remote
antennas by creating a custom field called "FreezeTotalGain" in the Remote Antennas
table and setting the value of the field to "True." Afterwards, when you select Remote
Antennas > Calculate Gains from the Transmitters context menu, Atoll will only update
the UL and DL total gains for remote antennas with the custom field "FreezeTotalGain"
set to "False."
You can select a remote antenna on the map and change its azimuth (see "Changing the Azimuth of the Antenna
Using the Mouse" on page 32) or its position relative to the site (see "Changing the Position of the Transmitter
Relative to the Site" on page 32).
It is important not to confuse the computation zone and the focus zone or hot spot zone. The computation zone
defines the area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo power control simu-
lations, etc., while the focus zone or hot spot zone is the area taken into consideration when generating reports
and results.
For information on creating a computation zone, see "Creating a Computation Zone" on page 758.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be
studied.
2. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the fol-
lowing:
- Move the receiver to change the current position.
- Click to place the receiver at the current position. You can move the receiver again by clicking it a second time.
- Right-click the receiver to choose one of the following commands from the context menu:
- Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates.
- Target Site: Select a site from the list to place the receiver directly on a site.
4. Click the Profile tab.
The profile analysis appears in the Profile tab of the Point Analysis Tool window. The altitude (in metres) is
reported on the vertical axis and the receiver-transmitter distance on the horizontal axis. A blue ellipsoid indicates
the Fresnel zone between the transmitter and the receiver, with a green line indicating the line of sight (LOS). Atoll
displays the angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an obsta-
cle, this causes attenuation with diffraction displayed by a red vertical line (if the propagation model used takes
diffraction mechanisms into account). The main peak is the one that intersects the most with the Fresnel ellipsoid.
With some propagation models using a 3 knife-edge Deygout diffraction method, the results may display two addi-
tional attenuations peaks. The total attenuation is displayed above the main peak.
Details of the analysis are displayed at the top of the Profile tab:
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and
select "From Model" from the Shadowing Margin list.
- Select Signal Level, Path loss, and Total losses from the Result Type list.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- Link Budget: Select Link Budget to display a dialogue with the link budget.
- Model Details: Select Model Details to display a text document with details on the displayed profile analysis.
Model details are only available for the standard propagation model.
Note: You can use the same procedure to study the signal level coverage of several sites by
grouping the transmitters. For information on grouping transmitters, see "Grouping Data
Objects by a Selected Property" on page 65.
Tip: If you want to study only sites by their status, at this step you could group them by status.
5. Select Coverage by P-CCPCH RSCP and click OK. A coverage prediction properties dialogue appears.
6. You can configure the following parameters in the Properties dialogue:
- General tab: You can change the assigned Name of the coverage prediction, the Resolution, and you can
add a Comment. The resolution you set is the display resolution, not the calculation resolution.
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:
City Centre 5m
City 20 m
County 50 m
State 100 m
Note: If you create a new coverage prediction from the context menu of either the Transmitters
or Predictions folder, you can select the sites using the Group By, Sort, and Filter
buttons under Configuration. Because you already selected the target sites, however,
only the Filter button is available.
- Condition tab: The coverage prediction parameters on the Conditions tab allow you to define the signals that
will be considered for each pixel (see Figure 12.15). You can set:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the
terminal properties are used.
- Service: The R99 or HSDPA service to be considered in the coverage prediction. The body loss defined
in the service properties is used.
- Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP T_Add (P-
CCPCH RSCP threshold) defined in the mobility properties is used as the minimum requirement for the
coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier
with the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible
transmitters. Afterwards, the coverage prediction is calculated for the selected carrier. If the selected car-
rier does not exist in a transmitter, there will not be any pixels covered by this transmitter. If you select
"All," Atoll will display the coverage prediction for the preferred carrier of the selected service. If no pre-
ferred carrier is defined in the service properties, Atoll will display the coverage prediction for the carrier
with the highest P-CCPCH power, or the master carrier in case of N-frequency mode compatible transmit-
ters.
- Display tab: You can modify how the results of the coverage prediction will be displayed.
- Under Display Type, select "Value Intervals."
- Under Field, select "Best Signal Level."
- You can change the value intervals and their displayed colour. For information on changing display prop-
erties, see "Display Properties of Objects" on page 33.
- You can create a tooltip with information about the coverage prediction by clicking the Browse button
( ) next to the Tip Text box and selecting the fields you want to display in the tooltip.
- You can select the Add to Legend check box to add the displayed value intervals to the legend.
Note: If you change the display properties of a coverage prediction after you have calculated it,
you may make the coverage prediction invalid. You will then have to recalculate the
prediction to obtain valid results.
7. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The coverage
prediction by P-CCPCH RSCP can be found in the Predictions folder on the Data tab. Atoll automatically locks the results
of a coverage prediction as soon as it is calculated, as indicated by the icon ( ) beside the coverage prediction in the
Predictions folder. When you click the Calculate button ( ), Atoll only calculates unlocked coverage predictions ( ).
Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices
using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main prop-
agation model with a shorter radius (displayed with a blue square in Figure 12.16) and a higher resolution and an extended
propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate
higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower reso-
lution path loss matrices outside the area covered by the main propagation model.
In this section, the following are explained:
"Path Loss Matrices" on page 754.
"Assigning a Propagation Model" on page 756.
"The Calculation Process" on page 758.
"Creating a Computation Zone" on page 758.
"Setting Transmitters or Cells as Active" on page 758.
"Signal Level Coverage Predictions" on page 759.
"Analysing a Coverage Prediction" on page 767.
"Signal Quality Coverage Predictions" on page 774.
"HSDPA Coverage Prediction" on page 793.
"Printing and Exporting Coverage Prediction Results" on page 795.
Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matri-
ces in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning
projects, embedding the matrices can lead to large documents which use a large amount of memory. Therefore, in the
case of large radio-planning projects, saving your path loss matrices externally will help reduce the size of the file and the
use of computer resources.
The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same
radio-planning document and share the path loss matrices. In this case, the radio data is stored in a database and the path
loss matrices are read-only and are stored in a location accessible to all users. When the user changes his radio data and
recalculates the path loss matrices, the calculated changes to the path loss matrices are stored locally; the common path
loss matrices are not modified. These will be recalculated by the administrator taking into consideration the changes to
radio data made by all users. For more information on working in a multi-user environment, see the Administrator Manual.
When you save the path loss matrices to an external directory, Atoll creates:
One file per transmitter with the extension LOS for its main path loss matrix.
A DBF file with validity information for all the main matrices.
A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
Click the button beside the Private Directory ( ) and select Embedded to save the path loss matrices in
the Atoll document, or Share to select a directory where Atoll can save the path loss matrices externally.
Note: Path loss matrices you calculate locally are not stored in the same directory as shared
path loss matrices. Shared path loss matrices are stored in a read-only directory. In other
words, you can read the information from the shared path loss matrices but any changes
you make will be stored locally, either embedded in the ATL file or in a private external
folder, depending on what you have selected in Private Directory.
Caution: When you save the path loss files externally, the external files are updated as soon as
calculations are performed and not only when you save the Atoll document. In order to
keep consistency between the Atoll document and the stored calculations, you should
save the Atoll document before closing it, if you have updated the path loss matrices.
- Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a
database and the common path loss matrices are stored in a directory that is accessible to all users. Any
changes you make will not be saved to this directory; they will be saved in the location indicated in Private
Directory. The path loss matrices in the shared directory are updated by a user with administrator rights based
on the updated information in the database. For more information on shared directories, see the Administrator
Manual.
5. Click OK.
Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want,
you can check whether the path loss matrices are valid without creating a coverage prediction.
To check whether the path loss matrices are valid:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. You have the
following display options:
- Display all the matrices: All path loss matrices are displayed.
- Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available Results table lists the following information for each displayed path loss matrix:
2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation
Model to All Transmitters" on page 756, this is the propagation model that will be used for all transmitters, except
for those to which you have assigned a propagation model either individually or as part of a group.
Important: When you assign a propagation model globally, you override any selection you might
have made to an individual transmitter or to a group of transmitters.
3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default
Propagation Model" on page 187, this is the propagation model that will be used for all transmitters whose main
propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main prop-
agation model, that is the propagation model that will be used.
In this section, the following are explained:
"Assigning a Propagation Model to All Transmitters" on page 756.
"Assigning a Propagation Model to a Group of Transmitters" on page 757.
"Assigning a Propagation Model to One Transmitter" on page 757.
For more information about the available propagation models, see Chapter 5: Managing Calculations in Atoll.
In Atoll, you can choose a propagation model for a single transmitter or globally for all transmitters.
To define a main and extended propagation model for all transmitters:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Propagation tab.
5. Under Main Matrix:
- Select a Propagation Model
- Enter a Radius and Resolution.
6. If desired, under Extended Matrix:
- Select a Propagation Model
- Enter a Radius and Resolution.
7. Click OK. The selected propagation models will be used for all transmitters.
Transmitters that share the same parameters and environment will usually use the same propagation model and settings.
In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common
parameters and then assigning the propagation model.
To define a main and extended propagation model for a defined group of transmitters:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select from the Group By submenu of the context menu the property by which you want to group the transmitters.
The objects in the folder are grouped by that property.
Note: You can group transmitters by several properties by using the Group By button on the
Properties dialogue. For more information, see "Advanced Grouping" on page 66.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model
to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmit-
ters.
When you assign a main and extended propagation model to a single transmitter, it overrides any changes made globally.
To define a main and extended propagation model for all transmitters:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Transmitters folder.
3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu
appears.
4. Select Properties from the context menu. The Properties dialogue appears.
5. Click the Propagation tab.
6. Under Main Matrix:
- Select a Propagation Model
- Enter a Radius and Resolution.
7. If desired, under Extended Matrix:
- Select a Propagation Model
- Enter a Radius and Resolution.
8. Click OK. The selected propagation models will be used for the selected transmitter.
Notes:
You can stop any calculations in progress by clicking the Stop Calculations button ( ) in
the toolbar.
When you click the Force Calculation button ( ) instead of the Calculate button, Atoll cal-
culates all path loss matrices, unlocked coverages, and pending simulations.
Note: You can save the computation zone in the user configuration. For information on
exporting the computation zone in the user configuration, see "Exporting a User
Configuration" on page 75.
Note: If you do not yet have a zone containing the transmitters you want to set as active, you
can draw a zone as explained in "Using Zones in the Map Window" on page 41.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active.
Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on
choosing and configuring a propagation model, see Chapter 5: Managing Calculations in Atoll.
Calculating path loss matrices can be time and resource intensive when you are working on large projects. Consequently,
Atoll offers you the possibility of distributing path loss calculations on several computers. You can install the Atoll comput-
ing server application on other workstations or servers. Once the computing server application is installed on a workstation
or server, the computer is available for distributed path loss calculation to other computers on the network. For information
on distributed calculations, see the Administrator Manual.
6. Click the Condition tab (see Figure 12.18). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set the following:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used.
- Service: The R99 or HSDPA service to be considered in the coverage prediction. The body loss defined in
the service properties is used.
- Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP T_Add
(P-CCPCH RSCP threshold) defined in the mobility properties is used as the minimum requirement for the
coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
on a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display
the coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The coverage prediction by P-CCPCH RSCP is performed for TS0.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- RSCP Margin: Select "Value Intervals" as the Display Type and "RSCP Margin" as the Field. RSCP Margin
is the margin between the calculated P-CCPCH RSCP and the P-CCPCH RSCP T_Add given for the selected
mobility.
- Cell Edge Coverage Probability: Select "Value Intervals" as the Display Type and "Cell Edge Coverage
Probability" as the Field.
8. Click OK to save your settings.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 12.19).
6. Click the Condition tab (see Figure 12.18). On the Condition tab, you can define the signals that will be considered
for each pixel. On the Condition tab, you can set:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used.
- Service: The R99 or HSDPA service to be considered in the coverage prediction. The body loss defined in
the service properties is used.
- Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP T_Add
(P-CCPCH RSCP threshold) defined in the mobility properties is used as the minimum requirement for the
coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The coverage prediction by P-CCPCH best server is performed for TS0.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
Figure 12.20: Condition settings for a coverage prediction by P-CCPCH best server
9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 12.21).
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used.
- Service: The R99 or HSDPA service to be considered in the coverage prediction. The body loss defined in
the service properties is used.
- Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP T_Add
(P-CCPCH RSCP threshold) defined in the mobility properties is used as the minimum requirement for the
coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 12.23).
Note: By changing the parameters selected on the Condition tab and by selecting different
results to be displayed on the Display tab, you can calculate and display information other
than that which has been explained in the preceding sections.
6. Click the Condition tab (see Figure 12.24). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used.
- Service: The R99 or HSDPA service to be considered in the coverage prediction. The body loss defined in
the service properties is used.
- Mobility: The mobility type to be considered in the coverage prediction. The DwPCH RSCP threshold defined
in the mobility properties is used as the minimum requirement for the coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The coverage prediction by DwPCH RSCP is performed for DwPTS timeslot.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- RSCP Margin: Select "Value Intervals" as the Display Type and "RSCP Margin" as the Field. RSCP Margin
is the margin between the calculated DwPCH RSCP and the DwPCH RSCP threshold given for the selected
mobility.
- Cell Edge Coverage Probability: Select "Value Intervals" as the Display Type and "Cell Edge Coverage
Probability" as the Field.
8. Click OK to save your settings.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 12.25).
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 12.26). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set:
- Terminal: The terminal to be considered in the coverage prediction. The UpPCH power, gains, and losses
defined in the terminal properties are used.
- Service: The R99 or HSDPA service to be considered in the coverage prediction. The body loss defined in
the service properties is used.
- Mobility: The mobility type to be considered in the coverage prediction. UpPCH RSCP threshold defined in
the mobility properties is used as the minimum requirement for the coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The coverage prediction by UpPCH RSCP is performed for UpPTS timeslot.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- RSCP Margin: Select "Value Intervals" as the Display Type and "RSCP Margin" as the Field. RSCP Margin
is the margin between the calculated UpPCH RSCP and the UpPCH RSCP threshold given for the selected
mobility.
- Cell Edge Coverage Probability: Select "Value Intervals" as the Display Type and "Cell Edge Coverage
Probability" as the Field.
8. Click OK to save your settings.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 12.27).
1. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
2. At the bottom of the Point Analysis Tool window, click the Reception tab (see Figure 12.29).
The predicted signal level from different transmitters is reported in the Reception tab in the form of a bar chart,
from the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the
colour of the transmitter it represents. In the map window, arrows from the pointer to each transmitter are displayed
in the colour of the transmitters they represent. A thick black line from the pointer to its best server is also displayed
in the map window. The best server of the pointer is the transmitter from which the pointer receives the highest
signal level. If you let the pointer rest, the signal level received from the corresponding transmitter at the pointer
location is displayed in the tooltip.
At the top of the Reception tab, you can select the carrier to be analysed.
3. Right-click the Reception tab and select Properties from the context menu. The Analysis Properties dialogue
appears.
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and
select "From Model" from the Shadowing Margin list.
- Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class.
12.2.10.7.4 Creating a Focus or Hot Spot Zone for a Coverage Prediction Report
The focus and hot spot zones define an area on which statistics can be drawn and on which reports are made. While you
can only have one focus zone, you can define several hot spot zones in addition to the focus zone.
It is important not to confuse the computation zone and the focus and hot spot zones. The computation zone defines the
area where Atoll computes path loss matrices, coverage predictions, Monte Carlo, power control simulations, etc., while
the focus and hot spot zones are the areas taken into consideration when generating reports and results. When you create
a coverage prediction report, it gives the results for the focus zone and for each of the defined hot spot zones.
To define a focus zone or hot spot zone:
1. Click the Geo tab in the Explorer window.
2. Click the Expand button ( ) to expand the Zones folder.
3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or
a hot spot. The context menu appears.
4. Select Draw from the context menu.
5. Draw the focus or hot spot zone:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zones
visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but
will still be taken into account.
You can also create a focus or hot spot zone as follows:
Existing polygon: You can use any existing polygon on the map as a focus zone by right-clicking it and selecting
Use as Focus Zone from the context menu.
Note: You can only create a focus zone, and not a hot spot zone, from an existing polygon.
Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus
Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot
spot zones, you can import the name given to each zone as well.
Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map
Window from the context menu.
Notes: You can save the focus or hot spot zones so that you can use them in a different Atoll
document:
- You can save the focus zone in the user configuration. For information on exporting the
focus zone in the user configuration, see "Exporting a User Configuration" on page 75.
- You can right-click the Focus Zone folder or the Hot Spot Zones folder on the Data
tab of the Explorer window and select Export from the context menu.
You can include population statistics in the focus or hot spot zone by importing a
population map. For information on importing maps, see "Importing a Raster-format Geo
Data File" on page 107.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
a. Under Configuration, click the Import button. The Open dialogue appears.
b. Select the configuration you want to import and click Open. The imported report configuration is applied
6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed
dialogue. The coverage prediction report table appears. The report is based on the hot spot zones and on the
focus zone if available or on the hot spot zones and computation zone if there is no focus zone.
To display a report on all coverage predictions:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
5. Click OK.
If you have created a custom data map with integrable data, the data can be used in prediction reports. The data will be
summed over the coverage area for each item in the report (for example, by transmitter or threshold). The data can be
value data (revenue, number of customers, etc.) or density data (revenuekm, number of customerkm, etc.). Data is
considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example,
socio-demographic classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable
Versus Non Integrable Data" on page 124.
- Under Histogram Based on Covered Areas, you can select to view a histogram, CDF, or inverse CDF based
on area or percentage.
- The Detailed Results section displays the covered area values, or the percentage of the covered area, along
the y-axis against the coverage criterion along the x-axis.
- You can copy the graph by clicking the Copy button.
- You can print the graph by clicking the Print button.
- Under Statistics Based on Study Conditions, you can view the mean and standard deviation of the cov-
erage criteria calculated during the coverage calculations, if available.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how you can verify if a newly added base station improves coverage.
A coverage prediction by P-CCPCH RSCP for the current network is made as described in "Making a Coverage Prediction
by P-CCPCH RSCP" on page 760. The results are displayed in Figure 12.31. An area with poor coverage is visible on the
right side of the figure.
A new base station is added, either by creating the site and adding the transmitters, as explained in "Creating a TD-
SCDMA Base Station" on page 728, or by using a station template, as explained in "Placing a New Base Station Using a
Station Template" on page 736. Once the new base station has been added, the original coverage prediction can be recal-
culated, but then it would be impossible to compare the results. Instead, the original coverage prediction by P-CCPCH
RSCP can be copied by selecting Duplicate from its context menu. The copy is then calculated to show the effect of the
new base station (see Figure 12.32).
Figure 12.32: Coverage prediction by P-CCPCH RSCP of the network with a new base station
4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes adding a new base station made, you should choose Difference.
5. Click OK to create the comparison. The comparison in Figure 12.33, shows clearly the area covered only by the
new base station.
If you have an area in a network that is poorly covered by current transmitters, you have several options for improving
coverage. In this example, we will look at how modifying transmitter tilt can improve coverage.
A coverage prediction by P-CCPCH best server for the current network is made as described in "Making a Coverage
Prediction by P-CCPCH Best Server" on page 761. The results are displayed in Figure 12.34. The coverage prediction
shows that one transmitter is covering its area poorly. The area is indicated with a red oval in the figure.
Figure 12.34: Coverage prediction by P-CCPCH best server for the existing network
You can try modifying the tilt on the transmitter to improve the coverage. You can access the properties of the transmitter
by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and
electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue.
Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it would be
impossible to compare the results. Instead, the original coverage prediction by can be copied by selecting Duplicate from
its context menu. The copy is then calculated, to show how modifying the antenna tilt has affected coverage (see
Figure 12.35).
Figure 12.35: Coverage prediction by P-CCPCH best server of the network after modifications
As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change
in coverage, you can compare the two predictions.
To compare two predictions:
1. Right-click one of the two predictions. The context menu appears.
2. From the context menu, select Compare with and, from the menu that opens, select the prediction you want to
compare with the first. The Comparison Properties dialogue appears.
3. Click the General tab. You can change the Name of the comparison and add Comments.
The General tab contains information about the coverage predictions being compared, including their name and
resolution.
4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes modifying the antenna tilt made, you can choose Union. This will display all pixels
covered by both predictions in one colour and all pixels covered by only one prediction in another colour. The
increase in coverage, seen in only the second coverage prediction, will be immediately clear.
5. Click OK to create the comparison. The comparison in Figure 12.36, shows clearly the increase in coverage due
at the change in antenna tilt.
The following coverage predictions are available for determining and studying interference:
To study the interference between cells in the case of asymmetric and different timeslot configurations used for
different cells, see "Studying Cell to Cell Interference" on page 789.
To study the interference on UpPCH when the UpPCH is shifted to a traffic timeslot, see "Studying UpPCH Inter-
ference" on page 790.
Making another type of coverage prediction, the baton handover coverage prediction, is also explained:
"Making a Baton Handover Coverage Prediction" on page 792.
You can define the minimum RSCP threshold for your network in order to limit the calculation range and optimise the calcu-
lation time. For all the calculations, Atoll only considers the pixels where the P-CCPCH RSCP exceeds the minimum
RSCP threshold. Defining the minimum RSCP threshold for the network is explained in the following section:
"Defining the Minimum P-CCPCH RSCP Threshold" on page 778.
Modelling Services
Services are the various services available to subscribers. These services can be either circuit-switched or packet-
switched services. This section explains how to create a service. However, only the following parameters are used in
predictions:
R99 radio bearer parameters
Body loss
HSDPA application throughput parameters
Before you model services, you must have defined R99 radio bearers. For more information on defining R99 radio bearers,
see "Defining R99 Radio Bearers" on page 859.
To create or modify a service:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.
3. Right-click the Services folder. The context menu appears.
4. Select New from the context menu. The Services New Element Properties dialogue appears.
Note: You can modify the properties of an existing service by right-clicking the service in the
Services folder and selecting Properties from the context menu.
5. You can edit the fields on the General tab to define the new service. Some fields depend on the Type of service
you choose. You can change the following parameters:
- Name: Atoll proposes a name for the new service, but you can change the name to something more descrip-
tive.
- R99 Radio Bearer: Select an R99 radio bearer from the list. If you want to edit the settings of the selected
R99 radio bearer, click the Browse button ( ) to open the bearers Properties dialogue.
- Type: You can select either Circuit or Packet as the service type.
If you want the service to be able to use HSDPA channels, select Packet and the HSDPA check box. For pack-
et services that can use HSDPA channels, you have the following options:
- A-DPCH Activity Factor: The uplink and downlink A-DPCH activity factors (for services that support
HSDPA) are used to estimate the average power on A-DPCH channels.
- Average Requested Rate: You can enter the average requested rate for uplink and downlink. This rate
is the average requested HS-PDSCH rate which guarantees a minimum average downlink rate during an
HSDPA call. It is used twice in a simulation: once during user distribution generation in order to calculate
the number of HSDPA users attempting a connection and then once during power control as a quality
target to be compared to the real obtained average throughput.
- Application Throughput: Under Application Throughput, you can set a Scaling Factor between the
application throughput and the RLC (Radio Link Control) throughput and a throughput Offset. These
parameters model the header information and other supplementary data that does not appear at the appli-
cation level.
If you select Packet to create a service that does not use HSDPA, you have the following option:
- Efficiency Factor: The uplink and downlink efficiency factors are used to determine duration of usage by
the user during Monte-Carlo simulations. It does this by determining the average usage of the network by
the user. This paremeter is used when working with traffic maps per user profile only.
If you select Circuit, you have the following options.
- Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity
for each user during Monte-Carlo simulations.
- Preferred Carrier: You can select one of the available carriers or all carriers. The specified carrier is
considered in simulations when connecting a mobile user to a transmitter. If the transmitter uses the
preferred carrier of the service, Atoll selects it. Otherwise, it chooses another one, based on the DCA
(Dynamic Channel Allocation) method selected when creating the simulation. If no preferred carrier is
specified in the service properties, Atoll will consider the carrier selection mode of the selected DCA
method. Similarly, coverage predictions that are calculated for "All" carriers are calculated for the preferred
carrier of the selected service. If no preferred carrier is defined in the service properties, Atoll preforms
the coverage prediction for the carrier with the highest P-CCPCH power, or the master carrier in case of
N-frequency mode compatible transmitters.
- Priority: Enter a priority for this service. "0" is the lowest priority.
- Body Loss: Enter the body loss for the service. The body loss is the loss due to the body of the user. For
example, in a voice connection the body loss, due to the proximity of the users head, is estimated to be 3 dB.
6. If you selected Circuit as the Type in step 5., continue to step 7. If you selected Packet as the Type in step 5.,
an additional tab, the Packet tab, appears. Click the Packet tab.
In the Packet tab, you can set the following parameters for packet switched services:
Radio propagation conditions as well as connection properties and criteria vary with the speed the user is travelling. A
mobile user travelling at a high speed and a pedestrian will not necessarily be connected to the same transmitters and
both users will not experience the same service characteristics. EcI0 requirements and EbNt or C/I targets per radio
bearer and per link (up and down) are largely dependent on mobile speed.
The following parameters are used in predictions:
P-CCPCH RSCP T_Add (RSCP P-CCPCH Threshold)
P-CCPCH RSCP T_Drop
DwPCH RSCP Threshold
UpPCH RSCP Threshold
P-CCPCH EbNt Threshold or P-CCPCH CI Threshold
DwPCH CI Threshold
HS-SCCH EcNt Threshold (DL)
HS-SICH EcNt Threshold (UL)
Note: You can select whether the P-CCPCH thresholds you define are Eb/Nt or C/I thresholds
by selecting the corresponding option in the Global Parameters tab of the Transmitters
folders properties dialogue. For more information, see "The Global Transmitter
Parameters" on page 852.
Note: You can modify the properties of an existing mobility type by right-clicking the mobility
type in the Mobility Types folder and selecting Properties from the context menu.
5. On the General tab, you can enter or modify the following parameters in the Mobility Types New Element Prop-
erties dialogue:
- Name: Enter or modify the descriptive name for the mobility type.
- Average Speed: Enter or modify an average speed for the mobility type. This field is for information only; the
average speed is not used in any calculation.
- Under Baton Handover Parameters, you can set the minimum required pilot signal levels from transmitters for
entering and exiting the list of potential servers.
- P-CCPCH RSCP T_Add (P-CCPCH RSCP Threshold): The minimum pilot signal level from transmitters
required for entering the list of potential servers.
- P-CCPCH RSCP T_Drop: The signal level from transmitters below which a transmitter cannot enter the
list of potential servers.
- DwPCH RSCP Threshold: Enter or modify the minimum signal level required for the DwPTS coverage. This
value is used as the minimum requirement limit for the Coverage by DwPCH RSCP.
- UpPCH RSCP Threshold: Enter or modify the minimum signal level required for the UpPTS coverage. This
value is used as the minimum requirement limit for the Coverage by UpPCH RSCP.
- HS-SCCH EcNt Threshold (DL): Enter or modify the minimum quality required for the HSDPA link to be avail-
able. Atoll calculates the HS-SCCH EcNt from the HS-SCCH power set in the cell properties and compares
it to this threshold. This field is used only with HSDPA.
- HS-SICH EcNt Threshold (UL): Enter or modify the minimum quality required for the HSDPA link to be avail-
able. Atoll calculates the HS-SICH EcNt from the HS-SICH power set in the terminal properties and compares
it to this threshold. This field is used only with HSDPA.
- P-CCPCH EbNt Threshold or P-CCPCH CI Threshold: Enter or modify the minimum P-CCPCH EbNt or CI
quality. This value is used as the minimum requirement limit for the P-CCPCH Reception Analysis (EbNt)
or P-CCPCH Reception Analysis (CI) coverage prediction.
- DwPCH CI Threshold: Enter or modify the minimum DwPCH CI quality. This value is used as the minimum
requirement limit for the DwPCH Reception Analysis (CI) coverage prediction.
6. On the MBMS tab, you can enter the Eb/Nt vs. Throughput graph in the Eb/Nt = f(Throughput) field. Clicking the
Graph button opens a dialogue in which you can view and edit the Eb/Nt vs. Throughput graph.
This tab is only available if the optional MBMS feature has been activated. Activating this optional feature requires
data structure modifications (for more information, see the Administrator Manual).
7. Click OK.
Modelling Terminals
In TD-SCDMA, a terminal is the user equipment that is used in the network, for example, a mobile phone, a PDA, or a cars
on-board navigation device.
The following parameters are used in predictions:
Reception equipment
Number of carriers supported
Maximum terminal power
UpPCH power
Gain and losses
Noise figure
JD factor
Rho factor
HSDPA capability, UE category, and HS-SICH power.
Note: You can modify the properties of an existing terminal by right-clicking the terminal in the
Terminal folder and selecting Properties from the context menu.
A pilot signal quality prediction enables you to identify areas where there is at least one transmitter whose pilot quality is
received sufficiently well.
Atoll calculates the best pilot quality received on each pixel. Then, depending on the prediction definition, it compares this
value either to the P-CCPCH EbNt or CI threshold defined for the selected mobility type. The pixel is coloured if the condi-
tion is fulfilled (in other words, if the received pilot quality is better than the P-CCPCH EbNt or CI threshold). The total
noise, Nt, includes the pilot power (P-CCPCH power). The processing gain used for the EbNt coverage prediction is the
one defined on the Global Parameters tab of the Transmitters Properties dialogue. For more information on the global
parameters, see "The Global Transmitter Parameters" on page 852. The coverage prediction is limited by the P-CCPCH
RSCP threshold of the selected mobility type.
To make a pilot signal quality prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select P-CCPCH Reception Analysis (EbNt) or P-CCPCH Reception Analysis (CI) and click OK. The predic-
tion Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 12.37). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used.
- Service: The R99 or HSDPA service to be considered in the coverage prediction. The body loss defined in
the service properties is used.
- Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH EbNt threshold or
P-CCPCH CI threshold defined in the mobility properties is used as the minimum requirement for the coverage
prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The P-CCPCH reception analysis predictions are performed for TS0.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
Figure 12.37: Condition settings for a P-CCPCH reception analysis (EbNt) coverage prediction
9. Click the Calculate button ( ) in the Radio toolbar to calculate the pilot signal quality prediction. The progress
of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 12.38).
Atoll calculates the best DwPCH signal quality received on each pixel. Then, depending on the prediction definition, it
compares this value with the DwPCH CI threshold defined for the selected mobility type. The pixel is coloured if the condi-
tion is fulfilled (in other words, if the received DwPCH signal quality is better than the DwPCH CI threshold). The coverage
prediction is limited by the DwPCH RSCP threshold of the selected mobility type.
To make a DwPCH signal quality prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select DwPCH Reception Analysis (CI) and click OK. The prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 12.37). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used.
- Service: The R99 or HSDPA service to be considered in the coverage prediction. The body loss defined in
the service properties is used.
- Mobility: The mobility type to be considered in the coverage prediction. The DwPCH CI threshold defined in
the mobility properties is used as the minimum requirement for the coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All", Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The DwPCH reception analysis (CI) predictions are performed for DwPTS.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
Figure 12.39: Condition settings for a DwPCH reception analysis (CI) coverage prediction
9. Click the Calculate button ( ) in the Radio toolbar to calculate the DwPCH signal quality prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 12.38).
Atoll calculates the received traffic channel power on the uplink or on the downlink taking into consideration the effect of
any smart antenna equipment assigned to transmitters, and the smart antenna simulation results stored for the selected
timeslot. The coverage prediction is limited by the P-CCPCH RSCP threshold of the selected mobility type.
To make an effective service area prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select one of the following coverage predictions and click OK:
- Coverage by Downlink TCH RSCP
- Coverage by Uplink TCH RSCP
The prediction Properties dialogue appears.
6. Click the Condition tab (see Figure 12.41). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used. For the uplink traffic channel coverage prediction, Atoll calculates the RSCP using
the maximum power defined for the selected terminal.
- Service: The R99 service to be considered in the coverage prediction. The uplink TCH RSCP threshold or
downlink TCH RSCP threshold defined in the properties of the R99 radio bearer of the service is used as the
minimum requirement for the coverage prediction. The body loss defined in the service properties is also used.
For the downlink traffic channel, Atoll calculates the RSCP using the maximum allowed downlink traffic
channel power defined for the R99 bearer of the selected service.
- Mobility: The mobility type to be considered in the coverage prediction. The uplink TCH RSCP threshold or
the downlink TCH RSCP threshold defined in the selected services R99 bearer and corresponding to the
selected mobility type is used as the minimum requirement for the coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The coverage predictions by TCH RSCP can be performed for any downlink or uplink timeslot.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
Figure 12.41: Condition settings for a downlink RSCP TCH coverage prediction
- RSCP Margin: Select "Value Intervals" as the Display Type and "RSCP Margin" as the Field. The RSCP
margin is the margin between the calculated DL or UL TCH RSCP and the DL or UL TCH RSCP threshold,
respectively, given for the selected services R99 bearer.
- Cell Edge Coverage Probability: Select "Value Intervals" as the Display Type and "Cell Edge Coverage
Probability" as the Field.
8. Click OK to save your settings.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the effective service area prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 12.42 and
Figure 12.43).
Atoll calculates the traffic channel quality, as defined by EbNt or CI, on the uplink or on the downlink considering the effect
of any smart antenna equipment assigned to transmitters, and the smart antenna simulation results stored for the selected
timeslot. The coverage prediction is limited by the P-CCPCH RSCP threshold of the selected mobility type.
To make a prediction on downlink or uplink service area (EbNt or CI):
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select one of the following coverage predictions and click OK:
- Service Area (EbNt) Downlink
- Service Area (CI) Downlink
- Service Area (EbNt) Uplink
- Service Area (CI) Uplink
The prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 12.44). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used. For the uplink service area coverage prediction, Atoll calculates the EbNt or CI
using the maximum power defined for the selected terminal.
- Service: The R99 service to be considered in the coverage prediction. The uplink TCH EbNt threshold and
downlink TCH EbNt threshold (or uplink TCH CI threshold and downlink TCH CI threshold) defined for the
services R99 radio bearer are used as the minimum requirement for the coverage prediction. The body loss
defined in the service properties is also used. For the downlink traffic channel, Atoll calculates the EbNt or CI
using the maximum allowed downlink traffic channel power defined for the R99 bearer of the selected service.
The processing gains are also used for the EbNt coverage predictions.
- Mobility: The mobility type to be considered in the coverage prediction. The uplink and downlink TCH EbNt
thresholds (or uplink or downlink TCH CI thresholds), defined in the service selected above, corresponding to
the selected mobility type are used as the minimum requirement for the coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The service area coverage predictions can be performed for any downlink or uplink timeslot.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
Figure 12.44: Condition settings for a downlink service area (EbNt) coverage prediction
9. Click the Calculate button ( ) in the Radio toolbar to calculate the service area prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 12.45 and
Figure 12.46).
The aim of this coverage prediction is to identify the areas where there might be coverage problems for a service either
on the downlink or on the uplink.
Atoll calculates the traffic channel quality, as defined by EbNt or CI, on the uplink and on the downlink taken into consid-
eration the effect of any smart antenna equipment assigned to transmitters, and the smart antenna simulation results
stored for the selected timeslot. The effective service area is the intersection zone between the uplink and downlink service
areas. The coverage prediction is limited by the P-CCPCH RSCP threshold of the selected mobility type.
To make an effective service area prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Effective Service Area (EbNt) or Effective Service Area (CI) and click OK. The prediction Properties
dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 12.47). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used. For the uplink, Atoll calculates the EbNt or CI using the maximum power defined
for the selected terminal.
- Service: The R99 service to be considered in the coverage prediction. The uplink TCH EbNt threshold and
downlink TCH EbNt threshold (or uplink TCH CI threshold and downlink TCH CI threshold) defined for the
services R99 radio bearer are used as the minimum requirement for the coverage prediction. The body loss
defined in the service properties is also used. For the downlink traffic channel, Atoll calculates the EbNt or CI
using the maximum allowed downlink traffic channel power defined for the R99 bearer of the selected service.
The processing gains are also used for the EbNt coverage predictions.
- Mobility: The mobility type to be considered in the coverage prediction. The uplink TCH EbNt threshold and
downlink TCH EbNt threshold (or uplink TCH CI threshold and downlink TCH CI threshold), defined in the
selected services R99 bearer, corresponding to the selected mobility type are used as the minimum require-
ment for the coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The effective service area coverage predictions are performed for all downlink and uplink timeslots.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
Figure 12.47: Condition settings for an effective service area (EbNt) coverage prediction
9. Click the Calculate button ( ) in the Radio toolbar to calculate the effective service area prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 12.48).
This coverage prediction is only available if the optional MBMS feature has been activated. Activating this optional feature
requires data structure modifications (for more information, see the Administrator Manual).
MBMS, Multimedia Broadcast and Multicast Service, offers a solution for broadcasting television channels over SCCPCH
channels in TD-SCDMA. SCCPCH (FACH) does not perform power control in order to cover the entire cell area. Atoll
calculates the MBMS channel quality (as defined by EbNt) using the MBMS power defined for an MBMS SCCPCH chan-
nel and timelslot. The coverage prediction is limited by the P-CCPCH RSCP threshold of the selected mobility type.
To make a coverage prediction on MBMS service area (Eb/Nt) :
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Service Area (Eb/Nt) MBMS and click OK. The prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 170. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 57.
6. Click the Condition tab. The coverage prediction parameters on the Conditions tab allow you to define the signals
that will be considered for each pixel. You can set:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used.
- Service: The MBMS Eb/Nt coverage prediction is calculated for an MBMS service.
- Mobility: The mobility type to be considered in the coverage prediction. The EbNt vs. Throughput graph
defined for the mobility is used in the coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The MBMS service area coverage prediction can be performed for timeslots allocated to the MBMS
SCCPCH channels.
- MBMS Channel: You must also select an MBMS Channel.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
7. Click the Display tab.
For the MBMS service area (Eb/Nt) coverage prediction, the Display Type "Value Intervals" based on the Field
"EbNt (dB)" is selected by default. Each pixel is displayed in a colour corresponding to the MBMS channel quality.
For information on defining display properties, see "Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the service area (EbNt) coverage prediction.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
6. Click the Condition tab (see Figure 12.49). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used.
- Service: The R99 or HSDPA service to be considered in the coverage prediction. The body loss defined in
the service properties is used.
- Mobility: The downlink total noise calculation does not depend on the mobility type.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All", Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The downlink total noise coverage predictions can be performed for any downlink timeslot.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
Figure 12.49: Condition settings for a downlink total noise coverage prediction
9. Click the Calculate button ( ) in the Radio toolbar to calculate the downlink total noise or downlink noise rise
prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 12.50).
If different cells have different timeslot configurations assigned to them, the difference of switching point between the uplink
and the downlink parts of the subframe may cause interference between the two links, up and down, i.e., on the same
timeslot, a cell receiving data in the uplink is interfered by nearby cells transmitting in the downlink.
The Cell to Cell Interference Zones coverage prediction displays the level of interference received by a cell. The cover-
age prediction sums the interfering signals in the downlink received by the victim cell in the uplink over the selected times-
lot. Interference is calculated using the total transmitted power of the timeslot.
To make a cell-to-cell interference zones coverage prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Cell to Cell Interference Zones and click OK. The prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 12.51). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used.
- Service: The R99 or HSDPA service to be considered in the coverage prediction. The body loss defined in
the service properties is used.
- Mobility: The mobility type to be considered in the coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The cell to cell interference coverage prediction can be performed for any timeslot.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
Figure 12.51: Condition settings for a cell to cell interference zones coverage prediction
8. Click the Calculate button ( ) in the Radio toolbar to calculate the cell-to-cell coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window.
UpPCH is used for uplink synchronisation (SYNC_UL). This channel is usually carried by the UpPTS timeslot. However,
if the interference on UpPTS is high, there is a risk of uplink synchronisation failure, i.e., the SYNC_UL might not be
detected. Unsynchronised DwPTS or TS0 timeslots of other cells might cause interference on UpPTS. Lack of synchroni-
sation between the DwPTS or TS0 and UpPTS occurs in wide and flat areas where there are no obstacles to wave prop-
agation. For cells located in such areas, it is possible to shift the UpPCH channel from the UpPTS to any other uplink
timeslot which might be less interfered. This is called UpPCH shifting.
Without shifting, the UpPCH, or UpPTS, starts at the 96th chip after the DwPCH on DwPTS. The UpPCH can be shifted
to TS1, TS2, or TS3. However, in Atoll, the UpPCH can only be shifted to TS1 on the uplink. It can be shifted by selecting
the corresponding timeslot configuration at cell level.
If some cells in a network use UpPCH shifting, you can use this coverage prediction to study the interference generated
by traffic on other cells, in other words, the mobiles connected to the TS1 uplink timeslot of other cells, on the shifted
UpPCH of these cells. Atoll calculates and displays the areas where the interference on the TS1 uplink timeslot, which is
used for the UpPCH, exceeds a set threshold.
To make an UpPCH interference zones prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select UpPCH Interference Zones and click OK. The prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 12.52). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set:
- Terminal: The terminal to be considered in the coverage prediction.
- Service: The R99 or HSDPA service to be considered in the coverage prediction.
- Mobility: The mobility type to be considered in the coverage prediction.
The terminal, service, and mobility type are not used for the calculation of interference. The gains and losses
defined for these parameters are used to calculate the P-CCPCH coverage of the cells that are using UpPCH
shifting.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The UpPCH interference coverage predictions are performed for TS1 uplink timeslot for UpPCH
shifting.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
Figure 12.52: Condition settings for an UpPCH interference zones coverage prediction
9. Click the Calculate button ( ) in the Radio toolbar to calculate the UpPCH interference prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 12.53).
6. Click the Condition tab (see Figure 12.54). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used.
- Service: The R99 or HSDPA service to be considered in the coverage prediction. The body loss defined in
the service properties is used.
- Mobility: The mobility type to be considered in the coverage prediction. P-CCPCH RSCP T_Add, and P-
CCPCH RSCP T_Drop defined in the mobility properties are used to define the signal level range for transmit-
ters to enter the preliminary handover set.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
Figure 12.54: Condition settings for a baton handover zones coverage prediction
7. Click the Display tab. The settings you select on the Display tab determine the information that the prediction will
display.
For a baton handover analysis, the Display Type "Value Intervals" and the Field "Number of Potential Neigh-
bours" are selected by default. You can also display only the baton handover coverage surface area by selecting
"Unique" as the Display Type. For information on defining display properties, see "Display Properties of Objects"
on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the handover status coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 12.55).
6. Click the Condition tab (see Figure 12.56). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set:
- Terminal: The HSDPA-compatible terminal to be considered in the coverage prediction. The gain, losses, and
HSDPA UE category defined in the terminal properties are used.
- Service: The HSDPA-compatible service to be considered in the coverage prediction. The body loss defined
in the service properties is used.
- Mobility: The mobility type to be considered in the coverage prediction. The downlink HS-SCCH EcNt
threshold defined in the mobility properties is used as the minimum requirement for the coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The HSDPA coverage prediction can be performed for any downlink or all timeslots. If you select
"All" timeslots, you can select an HSDPA bearer for which the prediction will be carried out.
- HSDPA Radio Bearer: The HSDPA bearer for which the coverage prediction is to be performed. Accessing
an HSDPA radio bearer requires at least two timeslots. Therefore, this option can only be selected when "All"
timeslots are selected.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage pre-
diction will display.
If you have selected "All" timeslots in the Condition tab, you can set the following parameters:
- The HS-PDSCH RSCP relative to the RSCP threshold: Select one of the following in the Field list:
- Min. HS-PDSCH RSCP
- Average HS-PDSCH RSCP
- Max HS-PDSCH RSCP
- The HS-PDSCH EcNt relative to the EcNt threshold: Select one of the following in the Field list:
- Min. HS-PDSCH EcNt
- Average HS-PDSCH EcNt
- Max HS-PDSCH EcNt
- The RLC peak rate relative to the threshold: Select "RLC Peak Rate (kbps)" as the Field. Atoll displays
the RLC peak rate that the selected HSDPA bearer can provide. The RLC peak rate is a characteristic of the
HSDPA bearer.
- The MAC rate relative to the threshold: Select "MAC Rate (kbps)" as the Field. Atoll calculates the MAC
rate from the transport block size of the selected HSDPA bearer.
If you have selected a particular timeslot in the Condition tab, you can set the following parameters:
- The uplink and downlink A-DPCH qualities: Select one of the following in the Field list:
- Max DL A-DPCH EbNt (dB): Atoll determines downlink A-DPCH quality at the receiver for the maximum
traffic channel power allowed for the selected timeslot.
- Max UL A-DPCH EbNt (dB): Atoll determines uplink A-DPCH quality at the receiver for the maximum
terminal power allowed.
- The HS-SCCH power, reception level, or quality: Select one of the following in the Field list:
- HS-SCCH Power: Atoll determines the HS-SCCH power required per pixel to get an HS-SCCH Ec/Nt bet-
ter than the minimum required HS-SCCH Ec/Nt. The coverage is limited by the HS-SCCH Ec/Nt threshold
defined for the selected mobility type.
- HS-SCCH RSCP: Atoll determines the HS-SCCH RSCP using the HS-SCCH power required per pixel to
get an HS-SCCH Ec/Nt better than the minimum required HS-SCCH Ec/Nt. The coverage is limited by the
HS-SCCH Ec/Nt threshold defined for the selected mobility type.
- HS-SCCH Ec/Nt: Atoll determines the HS-SCCH Ec/Nt per pixel. The coverage is limited by the HS-
SCCH Ec/Nt threshold defined for the selected mobility type.
- The HS-SICH power, reception level, or quality: Select one of the following in the Field list:
- HS-SICH Power: Atoll determines the HS-SICH power required per pixel to get an HS-SICH Ec/Nt better
than the minimum required HS-SICH Ec/Nt. The coverage is limited by the HS-SICH Ec/Nt threshold de-
fined for the selected mobility type.
- HS-SICH RSCP: Atoll determines the HS-SICH RSCP using the HS-SICH power required per pixel to get
an HS-SICH Ec/Nt better than the minimum required HS-SICH Ec/Nt. The coverage is limited by the HS-
SICH Ec/Nt threshold defined for the selected mobility type.
- HS-SICH Ec/Nt: Atoll determines the HS-SICH Ec/Nt per pixel. The coverage is limited by the HS-SICH
Ec/Nt threshold defined for the selected mobility type.
- The HS-PDSCH reception level or quality: Select one of the following in the Field list:
- HS-PDSCH RSCP: Atoll determines the HS-PDSCH RSCP using the HS-PDSCH power of the timeslot.
- HS-PDSCH Ec/Nt: Atoll determines the HS-PDSCH Ec/Nt using the HS-PDSCH power of the timeslot.
For information on defining display properties, see "Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the handover status coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the prediction, the results are displayed in the map window.
6. Click Commit to apply the allocation to the transmitters listed in the Transmitters column.
7. Click Close to close the Automatic Frequency Allocation dialogue.
3. Select Cells > Global > N-Frequency Mode > Audit from the context menu. The N-Frequency Mode Audit dia-
logue appears.
4. The audit checks the following points:
- For Master Carriers:
- Transmitters in N-Frequency Mode: The transmitters that are not N-frequency mode compatible.
- One Master Carrier per Transmitter: The transmitters that have either no or more than one master
carrier.
- Defined P-CCPCH Power: The transmitters whose master carriers do not have a P-CCPCH power
defined.
- For Stand-alone Carriers:
- Defined P-CCPCH Power: The transmitters whose stand-alone carriers do not have a P-CCPCH power
defined.
- For Slave Carriers:
- Linked to a Master Carrier: The transmitters whose slave carriers are not linked to any master carrier.
In other words, the transmitters that do not have any master carrier, but have slave carriers.
- P-CCPCH, DwPCH, and Other CCH Fields Empty: The transmitters whose slave carriers have
P-CCPCH, DwPCH, and other CCH powers defined.
- Timeslot Configurations, Scrambling Codes, and Neighbours Same as the Master Carrier: Select
this check box if you want the audit to check for slave carriers that do not have the same timeslot config-
urations, scrambling codes, and neighbours as the master carrier.
5. Click Run. Atoll performs the audit and lists the results under Problems occurred during the audit: X transmit-
ters have inconsistencies, where X is the number of transmitters with problems. The list includes:
- Several Master Carriers: Transmitters that have more than one master carrier.
- Master P-CCPCH Power Not Defined: Transmitters whose master carrier does not have a P-CCPCH power
defined.
- Stand-alone P-CCPCH Power Not Defined: Transmitters whose stand-alone carriers do not have P-CCPCH
powers defined.
- Slaves Without Masters: Transmitters that have only slave carriers and no master carrier.
- Slave Power Defined: Transmitters whose slave carriers have P-CCPCH, DwPCH, or other CCH powers
defined.
- Master-Slave Attribute Differences: Transmitters whose slave carriers have different timeslot configura-
tions, scrambling codes, and neighbours than the master carrier.
- Inconsistency: N-Frequency ModeCarrier Types: Transmitters that are not N-frequency mode compatible.
6. Click Resolve to resolve the inconsistencies found by the audit. Atoll makes the timeslot configurations and
scrambling codes of the slave carriers the same as the master carrier. It also empties the neighbour list of the slave
carriers.
7. Click Close to close the N-Frequency Mode Audit dialogue.
- Inter-carrier Neighbours: Cells defined as neighbours which perform handover using a different carrier. Inter-
carrier neighbours in TD-SCDMA are based on the hard handover principle. Hard handovers are performed
based on overlapping surface areas between cells based on the P-CCPCH RSCP.
For N-frequency mode compatible transmitters, inter-carrier neighbours are only calculated for master carri-
ers. If two transmitters have different master carriers, they can only be inter-carrier neighbours and not intra-
carrier neighbours.
For N-frequency mode compatible transmitters, neighbours are only stored for the master carriers. The slave
carriers have the same neighbours as their master carrier.
Inter-technology Neighbours: Inter-technology neighbours are cells defined as neighbours that use a tech-
nology other than TD-SCDMA.
In this section, the following are explained:
"Defining Exceptional Pairs" on page 798
"Allocating Neighbours Automatically" on page 798
"Checking Automatic Allocation Results" on page 801
"Importing Neighbours" on page 804
"Allocating and Deleting Neighbours per Cell" on page 804
"Checking the Consistency of the Neighbour Allocation Plan" on page 807
"Exporting Neighbours" on page 808.
7. Under Exceptional Pairs, create a new exceptional pair in the row marked with the New Row icon ( ):
a. Select the cell from the list in the Neighbours column.
b. In the Status column, select one of the following:
- Forced: The selected cell will always be a neighbour of the reference cell.
- Forbidden: The selected cell will never be a neighbour of the reference cell.
8. Click elsewhere in the table when you have finished creating the new exceptional pair.
9. Click OK.
Note: You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology
Neighbours table. You can open this table by right-clicking the Transmitters folder and
selecting Cells > Global > Neighbours > Intra-Technology Exceptional Pairs.
- P-CCPCH RSCP T_Drop: Enter the P-CCPCH RSCP T_Drop, which defines the minimum P-CCPCH
RSCP required for cells to enter a preliminary handover set. All the cells whose P-CCPCH RSCP is higher
than the P-CCPCH RSCP T_Drop are added to the set.
- P-CCPCH RSCP T_Comp: Enter the P-CCPCH RSCP T_Comp, which defines the handover set limit.
From among the cells listed in the preliminary handover set using the P-CCPCH RSCP T_Drop, only the
cells whose P-CCPCH RSCP is within the range defined by the P-CCPCH RSCP from the best server and
the P-CCPCH RSCP T_Comp margin are kept in the handover set.
- Shadowing taken into account: If desired, select the Shadowing taken into account check box and
enter a Cell Edge Coverage Probability.
- Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses defined per
clutter class in the calculations.
- Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic
neighbour allocation.
- % Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cells coverage area must
overlap the reference cells coverage area.
5. Select the desired calculation parameters:
- Carriers: Select the carriers on which you want to run the allocation. You can choose one or more car-
riers; Atoll will allocate neighbours to cells using the selected carriers.
- Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want
cells located on the same site as the reference cell to be automatically considered as neighbours.
- Force adjacent cells as neighbours: Select the Force adjacent cells as neighbours check box if you want
cells that are adjacent to the reference cell to be automatically considered as neighbours. A cell is considered
adjacent if there is at least one pixel in the reference cells coverage area where the possible neighbour cell
is the best server.
- Force symmetry: Select the Force symmetry check box if you want neighbour relationships to be reciprocal.
In other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the
neighbour list of any cell is full, the reference cell will not be added as a neighbour and that possible neighbour
cell will be removed from the list of neighbours of the reference cell.
- Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or
forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see
"Setting up N-Frequency Mode" on page 795.
- Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete
all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check
box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new
neighbours to the list.
6. Click the Importance Weighting button to set the relative importance of possible neighbours:
- Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage
reasons.
- Adjacency Factor: If you selected the Force adjacent cells as neighbours check box in step 5., set the min-
imum and maximum importance of a possible neighbour cell being adjacent to the reference cell.
- Co-site Factor: If you selected the Force co-site cells as neighbours check box in step 5., set the minimum
and maximum importance of a possible neighbour cell being located on the same site as reference cell.
7. Click Run. Atoll begins the process of allocating intra-carrier neighbours. Atoll first checks to see whether the
path loss matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates
them.
Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays
new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is
cleared, the Results table will be empty.
9. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neigh-
bours are listed in the Intra-technology Neighbours tab of each cells Properties dialogue.
To automatically allocate inter-carrier TD-SCDMA neighbours:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Global > Neighbours > Automatic Allocation from the context menu. The Automatic Neigh-
bour Allocation dialogue appears.
4. Click the Inter-Carrier Neighbours tab. You can set the following parameters:
- Max Inter-site Distance: Set the maximum distance between the reference cell and a possible neighbour.
- Max No. of Neighbours: Set the maximum number of inter-carrier neighbours that can be allocated to a cell.
This value can be either set here for all transmitters, or specified for each transmitter in the Cells table.
- Coverage Conditions: The coverage conditions must be respected for a cell to be considered as a neighbour.
Click Define to change the coverage conditions. In the Coverage Conditions dialogue, you can change the
following parameters:
- Min. P-CCPCH RSCP: Enter the minimum P-CCPCH RSCP which must be provided by reference cell A
and possible neighbour cell B.
- Handover Start: Enter the handover start margin which must be provided by reference cell A in an over-
lapping area. Reference cell A must also be the best server in terms of P-CCPCH RSCP in the overlapping
End Start
area. P-CCPCH RSCP Highest M HO < P-CCPCH RSCP Cell A < P-CCPCH RSCP Highest M HO
- Handover End: Enter the handover end margin between reference cell A and possible neighbour cell B
in the overlapping area.
- Shadowing taken into account: If desired, select the Shadowing taken into account check box and
enter a Cell Edge Coverage Probability.
- Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic
neighbour allocation.
- % Min. Covered Area: Enter the minimum, in percentage, that a possible neighbour cells coverage area must
overlap the reference cells coverage area.
5. Select the desired calculation parameters:
- Carriers: Select the carriers on which you want to run the allocation. You can choose one or more carriers;
Atoll will allocate neighbours to cells using the selected carriers.
- Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want
cells located on the same site as the reference cell to be automatically considered as neighbours.
- Force symmetry: Select the Force symmetry check box if you want neighbour relationships to be reciprocal.
In other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the
neighbour list of any cell is full, the reference cell will not be added as a neighbour and that possible neighbour
cell will be removed from the list of neighbours of the reference cell.
- Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or
forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see
"Setting up N-Frequency Mode" on page 795.
- Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete
all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check
box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new
neighbours to the list.
6. Click the Importance Weighting button to set the relative importance of possible neighbours:
- Coverage Factor: Set the minimum and maximum importance of the minimum percentage of shared cov-
erage between the possible neighbour cell and the reference cell.
- Co-site Factor: If you have selected the Force co-site cells as neighbours check box in step 5., set the
minimum and maximum importance of a possible neighbour cell being located on the same site as reference
cell.
7. Click Run. Atoll begins the process of allocating inter-carrier neighbours. Atoll first checks whether the path loss
matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates them.
Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays
new neighbours. If no new neighbours have been found and if the Delete existing neighbours check box is
cleared, the Results table will be empty.
- Coverage: The amount of reference cells coverage area that the neighbour overlaps, in percentage and in
square kilometres or miles.
8. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atolls table
shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data
Tables" on page 50.
9. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neigh-
bours are listed in the Intra-technology Neighbours tab of each cells Properties dialogue.
Notes:
A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already
exists and the Delete existing neighbours check box is cleared when you start the new allo-
cation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint
on the forbidden neighbour will be ignored because the neighbour already exists.
When the options Force exceptional pairs and Force symmetry are selected, Atoll con-
siders the constraints between exceptional pairs in both directions in order to respect sym-
metry. On the other hand, if the neighbour relation is forced in one direction and forbidden in
the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the
Event Viewer.
You can save automatic neighbour allocation parameters in a user configuration. For informa-
tion on saving automatic neighbour allocation parameters in a user configuration, see
"Exporting a User Configuration" on page 75.
When you create a new base station, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of
the new base station and other cells whose coverage area intersects the coverage area of the cells of the new base station.
To allocate neighbours to a new base station:
1. On the Data tab of the Explorer window, group the transmitters by site, as explained in "Grouping Data Objects"
on page 65.
2. In the Transmitters folder, right-click the new base station. The context menu appears.
3. Select Cells > Global > Neighbours > Automatic Allocation from the context menu. The Automatic Neigh-
bour Allocation dialogue appears.
4. Define the automatic neighbour allocation parameters as described in "Allocating Frequencies Automatically" on
page 795.
When you add a new transmitter, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the
new transmitters and other cells whose coverage area intersects the coverage area of the cells of the new transmitter.
To allocate neighbours to a new transmitter:
1. Click the Data tab of the Explorer window.
2. In the Transmitters folder, right-click the new transmitter. The context menu appears.
3. Select Allocate Neighbours from the context menu. The Automatic Neighbour Allocation dialogue appears.
4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on
page 798.
1. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
2. Select Display Options from the context menu. The Visual Management dialogue appears.
3. Under Intra-technology Neighbours, select the Display Links check box.
4. Click the Browse button ( ) beside the Display Links check box.
5. The Intra-technology Neighbour Display dialogue appears.
6. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a cell with a
unique colour.
- Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you
want Atoll to colour the cells neighbour links according to a value from the Intra-technology Neighbours
table, or according to the neighbour carrier. In this case, you can view on the map intra-carrier and inter-carrier
neighbour relations.
- Value Intervals: Select "Value Intervals" to colour the cells neighbour links according the value interval of the
value selected from the Field list. For example, you can choose to display a cells neighbours according to
their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting
factors.
Tip: You can display the number of handoff attempts for each cell-neighbour pair first creating
a new field of Type "Integer" in the Intra-Technology Neighbour table for the number of
handoff attempts. Once you have imported or entered the values in the new column, you
can select this field from the Field list along with "Value Intervals" as the Display Type.
For information on adding a new field to a table, see "Adding a Field to an Object Types
Data Table" on page 51.
Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you
can display or hide neighbour link display types individually.
For information on changing display properties, see "Display Properties of Objects" on page 33.
7. Select the Add to Legend check box to add the displayed neighbour links to the legend.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each neighbour link.
9. Click OK to save your settings.
10. Under Advanced, select which neighbour links to display:
- Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations
where the selected cell is the reference cell and where the neighbour relation is not symmetric.
- Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations
where the selected cell is neighbour and where the neighbour relation is not symmetric.
- Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the
selected cell and the neighbour.
11. Click OK to save your settings.
12. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
- The symmetric neighbour relations of the selected (reference) cell are indicated by a line.
- The outward neighbour relations are indicated with a line with an arrow pointing at the neighbour (e.g. see
Site1_2(0)) in Figure 12.57.).
- The inward neighbour relations are indicated with a line with an arrow pointing at the selected cell (e.g. see
Site9_3(0)) in Figure 12.57.).
In Figure 12.57, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward
neighbour links are coloured as the corresponding neighbour transmitters and the inward neighbour link is
coloured as the reference transmitter as it is neighbour of Site9_3(0) here.
In Figure 12.58, neighbour links are displayed according to the neighbour carrier. You can view intra-carrier and
inter-carrier neighbour links. Here, all neighbour relations are symmetric.
Note: You can display either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting
either Forced Neighbours or Forbidden Neighbours.
2. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
3. Select Display Options from the context menu. The Neighbour Display dialogue appears.
4. Under Intra-technology Neighbours, select the Display Coverage Areas check box.
5. Click the Browse button ( ) beside the Display Coverage Areas check box.
6. The Intra-technology Neighbour Display dialogue appears.
7. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage area of a cells neigh-
bours with a unique colour.
- Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you
want Atoll to colour the coverage area of a cells neighbours according to a value from the Intra-technology
Neighbours table.
- Value Intervals: Select "Value Intervals" to colour the coverage area of a cells neighbours according the
value interval of the value selected from the Field list. For example, you can choose to display a cells neigh-
bours according to their rank, in terms of automatic allocation, or according to the importance, as determined
by the weighting factors.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each coverage area.
9. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( ) in the
Radio toolbar.
Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete TD-SCDMA neighbours using the Cells tab of the transmitters Properties dialogue:
1. On the map, right-click the transmitter whose neighbours you want to change. The context menu appears.
2. Select Properties from the context menu. The transmitters Properties dialogue appears.
3. Click the Cells tab. On the Cells tab, there is a column for each cell.
4. Click the Browse button ( ) beside Neighbours in the cell for which you want to allocate or delete neighbours.
The cells Properties dialogue appears.
5. Click the Intra-technology Neighbours tab.
6. If desired, you can enter the maximum number of neighbours in the following boxes:
- Max Number Inter-Carrier
- Max Number Intra-Carrier
To allocate or delete TD-SCDMA neighbours using the Cells tab of the Transmitter Properties dialogue:
1. Select the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appear.
3. Select Cells > Global > Neighbours > Intra-technology Neighbours from the context menu. The Neighbours
table appears.
Note: For information on working with data tables, see "Working with Data Tables" on page 50.
4. To allocate a neighbour:
a. In the row marked with the new row icon ( ), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column.
c. Click another cell of the table to create the new neighbour and add a new blank row to the table.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
Note: You can add or delete either some forced neighbours or some forbidden neighbours using
the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table,
select the exceptional pairs to be considered, right-click the table and select Force
Exceptional Pairs in the context menu.
You can allocate or delete intra-technology neighbours directly on the map using the mouse.
To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neigh-
bours on the map as explained in "Displaying Frequency Allocation on the Map" on page 796.
To add a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters
to the intra-technology neighbours list.
To remove a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both trans-
mitters from the intra-technology neighbours.
To add an outward neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference
transmitter to the intra-technology neighbour list of the reference transmitter.
To remove an outward neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference
transmitter from the intra-technology neighbours list of the reference transmitter.
To add an inward neighbour relation:
Click the reference transmitter on the map. Atoll displays its neighbour relations.
- If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other trans-
mitter. Atoll converts the symmetric relation to an inward non-symmetric inter-technology neighbour relation.
- If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour rela-
tion by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then
press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric
inter-technology neighbour relation.
To remove an inwards neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the trans-
mitter from the intra-technology neighbours list of the reference transmitter.
Notes:
When there is more than one cell on the transmitter, clicking the transmitter in the map window
opens a context menu allowing you to select the cell you want (see "Selecting One of Several
Transmitters or Microwave Links" on page 30).
You can add or delete either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting either
Forced Neighbours or Forbidden Neighbours.
- Full Lists (default max number = Y): xX; x number of cells out of a total of X have Y number of neighbours
listed in their respective neighbours lists.
Syntax: |CELL| |NUMBER| |MAX NUMBER|
- Lists > max number (default max number = Y): xX; x number of cells out of a total of X have more than Y
number of neighbours listed in their respective neighbours lists.
Syntax: |CELL| |NUMBER| |MAX NUMBER|
Note: If the field Maximum number of neighbours in the Cells table is empty, the above two
checks take into account the Default Max Number value defined in the audit dialogue.
- Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Non symmetric links: X; total number of non-symmetric neighbour links in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
- Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
Note: Within the context of scrambling code allocation, "neighbours" refer to intra-carrier
neighbours.
You can convert a hexadecimal value to a decimal value with the following equation, where X, Y, and Z are decimal values
within the hexadecimal index ranges:
2
X 16 + Y 16 + Z
For example, the hexadecimal value "3Fh" would be calculated as shown below:
2
0 16 + 3 16 + 15 = 63
4. In the row marked with the New Row icon ( ), enter a Name for the new domain.
5. Click another cell of the table to create the new domain and add a new blank row to the table.
6. Double-click the domain to which you want to add a group. The domains Properties dialogue appears.
7. Under Groups, enter the following information for each group you want to create.
- Name: Enter a name for the new scrambling code group.
- Min.: Enter the lowest available scrambling code in this groups range. The minimum and maximum scram-
bling codes must be entered in the format, decimal or hexadecimal, set for the Atoll document. For information
on setting the scrambling code format, see "Defining the Scrambling Code Format" on page 808.
- Max: Enter the highest available scrambling code in this groups range.
- Step: Enter the separation interval between each scrambling code.
- Excluded: Enter the scrambling codes within the range defined by the Min. and Max fields that you do not
want to use.
- Extra: Enter any additional scrambling codes (i.e., outside the range defined by the Min. and Max fields) you
want to add to this group. You can enter a list of codes separated by either a comma, semi-colon, or a space.
You can also enter a range of scrambling codes separated by a hyphen. For example, entering, "1, 2, 36"
means that the extra scrambling codes are "1, 2, 3, 4, 5, 6".
8. Click another cell of the table to create the new group and add a new blank row to the table.
4. In the row marked with the New Row icon ( ), select one cell of the new exceptional pair in the Cell column
and the second cell of the new exceptional pair from the Cell_2 column.
5. Click another cell of the table to create the new exceptional pair and add a new blank row to the table.
You can define the costs of the different types of constraints used in the automatic scrambling code allocation algorithm.
To define the different constraint costs:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Global > Scrambling Codes > Constraint Costs. The Allocation Constraint Costs dialogue
appears. In this dialogue you can define the following costs of constraint violations for the automatic allocation
process (the cost is a value from 0 and 1):
- Max 1st, 2nd, and 3rd Order Neighbours: Enter the maximum costs for 1st, 2nd, and 3rd order neighbour
constraint violations.
- Max Cluster Share: Enter the maximum cost for the case where 1st or 2nd order neighbours have the same
cluster assigned when the Distributed per Site strategy is used.
- Co-planning Share: Enter the cost for inter-technology neighbour constraint violations.
- Max Reuse Distance: Enter the maximum cost for reuse distance constraint violations.
- Exceptional Pair: Enter the cost for exceptional pair constraint violations.
4. Click OK. The allocation constraint costs are stored and will be used in the automatic allocation.
The allocation algorithm enables you to automatically allocate scrambling code to cells in the current network. You can
choose among several automatic allocation strategies (for more information, see the Technical Reference Guide):
Clustered: The purpose of this strategy is to choose for a group of mutually constrained cells, scrambling codes
among a minimum number of clusters. In this case, Atoll will preferentially allocate all the codes from same
cluster.
Distributed per Cell: This strategy consists in using as many clusters as possible. Atoll will preferentially allocate
codes from different clusters.
One SYNC_DL Code per Site: This strategy allocates one SYNC_DL code to each base station, then, one code
of the cluster associated with the SYNC_DL code to each cell of each base station. When all the SYNC_DL codes
have been allocated and there are still base stations remaining to be allocated, Atoll reuses the SYNC_DL codes
at another base station. Select this strategy if you want to allocate the same scrambling code to the master and
the slave carriers. For more information on master and slave carriers, see "Planning Frequencies" on page 795.
Distributed per Site: This strategy allocates a group of adjacent clusters to each base station in the network, then,
one cluster to each transmitter of the base station, according to its azimuth, and finally one code of the cluster to
each cell of each transmitter. The number of adjacent clusters per group depends on the number of transmitters
per base station you have in your network; this information is required to start allocation based on this strategy.
When all the groups of adjacent clusters have been allocated and there are still base stations remaining to be allo-
cated, Atoll reuses the groups of adjacent clusters at another base station.
To automatically allocate scrambling codes:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Global > Scrambling Codes > Automatic Allocation. The Scrambling Codes and SYNC_DL
Codes dialogue appears.
4. Set the following parameters in the Scrambling Codes and SYNC_DL Codes dialogue:
- Under Constraints, you can set the constraints on automatic scrambling code allocation.
- Existing Neighbours: Select the Existing Neighbours check box if you want to consider neighbour re-
lations and then choose the neighbourhood level to take into account:
Neighbours of a cell are referred to as first order neighbours, neighbours neighbours are referred to as
second order neighbours and neighbours neighbours neighbours as third order neighbours.
First Order: No cell will be allocated the same scrambling code as its neighbours.
Second Order: No cell will be allocated the same scrambling code as its neighbours or its second order
neighbours.
Third Order: No cell will be allocated the same scrambling code as its neighbours or its second order
neighbours or its third order neighbours.
Atoll can only consider neighbour relations if neighbours have already been allocated. For information on
allocating neighbours, see "Planning Neighbours" on page 797.
Note: Atoll can take into account inter-technology neighbour relations as constraints to allocate
different scrambling codes to the TD-SCDMA neighbours of a GSM transmitter. In order
to consider inter-technology neighbour relations in scrambling code allocation, you must
make the Transmitters folder of the GSM Atoll document accessible in the TD-SCDMA
Atoll document. For information on making links between GSM and TD-SCDMA Atoll
documents, see "Creating a UMTS Sector From a GSM Sector" on page 226.
- Reuse Distance: Select the Reuse Distance check box, if you want to the automatic allocation process
to consider the reuse distance constraint. Enter the Default reuse distance within which two cells on the
same carrier cannot have the same scrambling code.
Note: A reuse distance can be defined at the cell level (in the cell Properties dialogue or in the
Cells table). If defined, a cell-specific reuse distance will be used instead of the value
entered here.
- Exceptional Pairs: Select the Exceptional Pairs check box if you want to the automatic allocation proc-
ess to consider the exceptional pair constraints.
- Under Strategy, you can select an automatic allocation strategy:
- Clustered
- Distributed per Cell
- One SYNC_DL Code per Site
- Distributed per Site
- Carrier: Select the carrier on which you want to run the allocation. You may choose one carrier (Atoll will
assign scrambling codes to transmitters using the selected carrier) or all of them.
- No. of Codes per SYNC_DL: According to 3GPP specifications, the number of scrambling codes per
SYNC_DL is 4. If you want, you can change the number of codes per SYNC_DL.
- Use a Max of Codes: Select the Use a Max of Codes check box to make Atoll use the maximum number of
codes. For example, if there are two cells using the same domain with two scrambling codes, Atoll will assign
the remaining code to the second cell even if there are no constraints between these two cells (for example,
neighbour relations, reuse distance, etc.). If you do not select this option, Atoll only checks the constraints,
and allocates the first ranked code in the list.
- Delete Existing Codes: Select the Delete Existing Codes check box if you want Atoll to delete currently
allocated scrambling codes and recalculate all scrambling codes. If you do not select this option, Atoll keeps
the currently allocated scrambling codes and only allocates scrambling codes to cells that do not yet have
codes allocated.
5. Click Run. Atoll begins the process of allocating scrambling codes.
If you have selected the Distributed per Site allocation strategy, a Distributed per Site Allocation Parameters
dialogue appears.
a. In the Distributed per Site Allocation Parameters dialogue, enter the Max Number of Transmitters per
Site.
b. Select the Neighbours in Other SYNC_DL or Secondary Neighbours in Other SYNC_DL check boxes in
the Additional Constraints section, if you want the automatic allocation to consider constraints related to first
order and second order neighbours.
c. Click OK.
Once Atoll has finished allocating scrambling codes, the codes are visible under Results. Atoll only displays
newly allocated scrambling codes.
Note: Atoll allocates the same scrambling code to each carrier of a transmitter.
6. Click Commit. The scrambling codes are stored in the cell properties.
Note: You can save automatic scrambling code allocation parameters in a user configuration.
For information on saving automatic scrambling code allocation parameters in a user
configuration, see "Exporting a User Configuration" on page 75.
Tips:
If you need to allocate scrambling codes to the cells on a single transmitter, you can allocate
them automatically by selecting Allocate Scrambling Codes from the transmitters context
menu.
If you need to allocate scrambling codes to all the cells in a group of transmitters, you can allo-
cate them automatically by selecting Cells > Global > Scrambling Codes > Automatic Allo-
cation from the transmitter groups context menu.
When you allocate scrambling codes to a large number of cells, it is easiest to let Atoll allocate scrambling codes auto-
matically, as described in "Automatically Allocating Scrambling Codes to TD-SCDMA Cells" on page 810. However, if you
want to add a scrambling code to one cell or to modify the scrambling code of a cell, you can do it by accessing the prop-
erties of the cell.
After allocation, you can use the audit tool to check the reuse scrambling code distances between cells and the compati-
bility of the domains of the cells for each base station.
To allocate a scrambling code to a TD-SCDMA cell manually:
1. On the map, right-click the transmitter to whose cell you want to allocate a scrambling code. The context menu
appears.
2. Select Properties from the context menu. The transmitters Properties dialogue appears.
3. Select the Cells tab.
4. Enter a Scrambling Code in the cells column.
5. Click OK.
In Atoll, you can search for scrambling codes and scrambling code groups using the Search Tool. Results are displayed
in the map window in red.
If you have already calculated and displayed a coverage prediction by transmitter based on the best server P-CCPCH,
with the results displayed by transmitter, the search results will be displayed by transmitter coverage. Scrambling codes
and scrambling code groups and any potential problems will then be clearly visible.
To find scrambling codes or scrambling code groups using the Search Tool:
1. Create, calculate, and display a coverage prediction by P-CCPCH best server. For information, see "Making a
Coverage Prediction by P-CCPCH Best Server" on page 761.
2. Click View > Search Tool. The Search Tool window appears.
3. You can search either for a specific scrambling code or for a scrambling code group:
To search for a scrambling code:
You can use the display characteristics of transmitters to display scrambling code-related information.
To display scrambling code-related information on the map:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Display tab.
You can display the following information per transmitter:
- Scrambling code: Select "Discrete values" as the Display Type and "Cells: Scrambling Code" as the Field.
- Ranges of scrambling codes: Select "Value intervals" as the Display Type and "Cells: Scrambling Code"
as the Field.
- Scrambling code domain: Select "Discrete values" as the Display Type and "Cells: Scrambling Code
Domain" as the Field.
You can display the following information in the transmitter label or tooltip:
- Scrambling code: Select "Cells: Scrambling Code" from the Label or Tip Text Field Definition dialogue.
- Scrambling code domain: Select "Cells: Scrambling Code Domain" from the Label or Tip Text Field Defi-
nition dialogue.
5. Click OK.
For information on display options, see "Display Properties of Objects" on page 33.
You can group transmitters on the Data tab of the Explorer window by their scrambling code or scrambling code domain.
To group transmitters by scrambling code:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the General tab, click Group by. The Group dialogue appears.
5. Under Available Fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
- Scrambling Code Domain
- Scrambling Code
7. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to
the list of parameters on which the transmitters will be grouped.
8. If you do not want the transmitters to be sorted by a certain parameter, select it in the Group these fields in this
order list and click . The selected parameter is removed from the list of parameters on which the transmitters
will be grouped.
9. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters
to be grouped:
10. Click OK to save your changes and close the Group dialogue.
Note: If a transmitter has more than one cell, Atoll cannot arrange the transmitter by cell.
Transmitters that cannot be grouped by cell are arranged in a separate folder under the
Transmitters folder.
You can use a histogram to analyse the use of allocated scrambling codes in a network. The histogram represents the
scrambling codes or SYNC_DLs as a function of the frequency of their use.
To display the scrambling code histogram:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Global > Scrambling Codes > Code Distribution. The Distribution Histograms dialogue
appears.
Each bar represents a scrambling code or a SYNC_DL code, its height depending on the frequency of its use.
4. Select Scrambling Codes to display scrambling code use and Clusters to display SYNC_DL code use.
5. Move the pointer over the histogram to display the frequency of use of each scrambling code or SYNC_DL. The
results are highlighted simultaneously in the Detailed Results list.
You can make a scrambling code interference zones coverage prediction to view areas covered by cells using the same
scrambling code. The coverage prediction displays areas where transmitters other than the best server, whose received
signal level is within the Pollution Margin set in the coverage prediction properties, interfere the best server signal. The
interfered pixels are coloured according to the interfered scrambling code.
To make a scrambling code interference zone coverage prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Scrambling Code Interference Zones and click OK. The prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 12.59). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used.
- Service: The R99 or HSDPA service to be considered in the coverage prediction. The body loss defined in
the service properties is used.
- Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP threshold
defined in the mobility properties is used as the minimum requirement for the coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The scrambling code interference coverage prediction is performed for TS0.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- Pollution Margin: The margin for determining which signals to consider. Atoll considers signal levels which
are within the defined margin of the best signal level.
Figure 12.59: Condition settings for a scrambling code interference zones coverage prediction
9. Click the Calculate button ( ) in the Radio toolbar to calculate the scrambling code interference zone coverage
prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 12.60).
Figure 12.60: Condition settings for a scrambling code interference zones coverage prediction
A specific colour is assigned to areas where more than one scrambling code has interference. You can analyse these
areas in more detail using the Search Tool. For more information on using the Search Tool for scrambling code interfer-
ence analysis, see "Using the Search Tool to Display Scrambling Code Allocation" on page 813.
UUDDDD 32 64
UUUDDD 48 48
UUUUDD 64 32
UUUUUD 80 16
UpUDDDD 16 64
UpUUDDD 32 48
Assuming ideal dynamic channel allocation (DCA), all the resource units within a subframe, i.e., 6 x 16 = 96, can be allo-
cated and used. TS0 is not used for traffic. TS1 is not used for traffic either in case of UpPCH shifting. The total resource
units in a network, i.e., the network capacity, is given by:
Network Capacity = Number of Timeslots per Subframe Number of Codes per Timeslot Number of Carriers
Resource units from different carriers can be shared and allocated to the same mobile connected to an N-frequency mode
compatible transmitter.
This section explains the network capacity and network dimensioning analysis tools:
"Calculating Available Network Capacity" on page 816.
"Calculating Required Network Capacity" on page 818.
The uplink and downlink Resource Units Overhead defined for each timeslot per cell is considered when calculat-
ing the number of available resource units.
You can create a coverage prediction by P-CCPCH best server in order to display the available network capacity, i.e., the
number of available resource units in uplink or downlink.
To display the available cell and network capacity on the map:
1. Create a coverage by P-CCPCH best server, as explained in "Making a Coverage Prediction by P-CCPCH Best
Server" on page 761, with the following display parameters:
- In step 7., set the Display Type "Value intervals" based on the Field "Available DL Resource Units" or "Avail-
able DL Resource Units" according to what you would like to display. Each coverage zone will then be dis-
played according to the number of available resource units for the carrier used for the coverage prediction.
Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 12.62).
- Global Scaling Factor: If desired, enter a scaling factor to increase user density.
The global scaling factor enables you to increase user density without changing traffic parameters or traffic
maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of users
(for environment and user profile traffic maps) or the rates per users (for live traffic maps per sector).
- Select Traffic Maps to be Used: Select the traffic maps you want to use for dimensioning.
- Under Coverage, select the P-CCPCH best server Coverage to be used to distribute the traffic among
the cells of the network.
4. Click Calculate. Atoll distributes the traffic among cells using the information from traffic maps and the coverage
prediction, calculates the capacity of each cell, and displays the results in the Results per Cell tab.
The Results per Cell tab has five columns which list the names of the cells in the network, and the numbers of
uplink and downlink resource units available and required per cell. The last row in this dialogue displays the total
uplink and downlink resource units, required and available. Cells for which the required resource units exceed the
available units are displayed in red.
The uplink and downlink resource units overhead defined for each timeslot per cell is considered when calculating
the number of available resource units.
5. Click Commit to store the number of required resource units per cell in the Cells table.
6. Click Close to close the dialogue.
Changing transmitter parameters does not affect the dimensioning results if you have not updated the coverage by
P-CCPCH best server used for the dimensioning calculations. If you want to compare dimensioning results after modifying
some transmitter parameters, you will have to (re)calculate a coverage by P-CCPCH best server, and run the dimensioning
calculations based on the new coverage prediction.
You can create a coverage by P-CCPCH best server in order to display the required network capacity, i.e., the number of
required resource units in uplink or downlink, of your TD-SCDMA network on the map. The number of required resource
units is an output of network dimensioning stored in the Cells table. For more information, see "Calculating Required
Network Capacity" on page 818.
To display the required cell and network capacity on the map:
1. Create a coverage by P-CCPCH best server, as explained in "Making a Coverage Prediction by P-CCPCH Best
Server" on page 761, with the following display parameters:
- In step 7., set the Display Type "Value intervals" based on the Field "Cells: Required DL Resource Units" or
"Cells: Required UL Resource Units" according to what you would like to display. Each coverage zone will then
be displayed according to the number of required resource units for the cell (carrier used for the coverage pre-
diction).
Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 12.64).
You can create a coverage by P-CCPCH best server in order to display the usage of resource units, i.e., the percentage
of available resource units which are effectively used by the traffic in uplink or downlink, of your TD-SCDMA network on
the map.
To display the usage of resource units on the map:
1. Create a coverage by P-CCPCH best server, as explained in "Making a Coverage Prediction by P-CCPCH Best
Server" on page 761, with the following display parameters:
- In step 7., set the Display Type "Value intervals" based on the Field "Required DL Resource Units (%)" or
"Required UL Resource Units (%)" according to what you would like to display. Each coverage zone will then
be displayed according to the percentage of available resource units that are used in each cell (carrier used
for the coverage prediction).
Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 12.66).
Traffic map per user profile can be used if you have marketing-based traffic data.
Traffic maps per density of user profiles, where each vector (polygon, line or point) describes subscriber densities
(or numbers of subscribers for points) with user profiles and mobility types, and traffic maps per environment of
user profiles, where each pixel has an assigned environment class. For more information, see "Importing a Traffic
Map Based on Densities of User Profiles" on page 824, "Importing a Traffic Map Based on Environments of User
Profiles" on page 825 and "Creating a Traffic Map Based on Environments of User Profiles" on page 825.
Traffic maps per density (number of users per km2) can be used if you have population-based traffic data,
or 2G network statistics.
Each pixel has an actual user density assigned. For more information, see "Importing a Traffic Map per User
Density" on page 826, "Creating a Traffic Map per User Density" on page 827, see "Converting 2G Network Traf-
fic" on page 828 and "Exporting Cumulated Traffic" on page 828.
Note: You can also import a traffic map from a file by clicking the Import button. You can import
AGD (Atoll Geographic Data) format files that you have exported from another Atoll
document.
7. Select a coverage prediction by P-CCPCH best server from the list of available coverage predictions.
8. Enter the data required in the Map per Sector dialogue:
- If you have selected Throughputs in Uplink and Downlink, enter the throughput demands in the uplink and
downlink for each sector and for each listed service.
- If you have selected Number of Users per Activity Status, enter the number of inactive users, the number
of users active in the uplink, in the downlink and in the uplink and downlink, for each sector and for each
service.
Note: You can also import a text file containing the data by clicking the Actions button and
selecting Import Table from the menu. For more information on importing table data, see
"Importing Tables from Text Files" on page 59.
11. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must
equal 100.
12. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must
equal 100.
13. Under Clutter Distribution, for each clutter class, enter:
- A weight to spread the traffic over the vector.
- The percentage of indoor users. An additional loss will be counted for indoor users during Monte Carlo simu-
lations.
14. Click OK. Atoll creates the traffic map in the Traffic folder.
You can update the information, throughput demands, and the number of users, on the map afterwards. You can update
Live traffic per sector maps if you add or remove a base station. You must first recalculate the coverage prediction by P-
CCPCH best server. For more information, see "Making a Coverage Prediction by P-CCPCH Best Server" on page 761.
Once you have recalculated the coverage prediction, you can update the traffic map.
To update the traffic map:
1. Click the Geo tab of the Explorer window.
2. Click the Expand button ( ) to expand the Traffic folder.
3. Right-click the sector traffic map that you want to update. The context menu appears.
4. Select Update from the context menu. The Map per Sector dialogue appears.
Select the updated coverage prediction by P-CCPCH best server and define traffic values for the new transmit-
ter(s) listed at the bottom of the table. Deleted or deactivated transmitters are automatically removed from the
table.
You can model variations in user behaviour by creating different profiles for different times of the day or for different circum-
stances. For example, a user may be considered a business user during the day, with video conferencing and voice, but
no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and
web browsing.
To create or modify a user profile:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.
3. Right-click the User Profiles folder. The context menu appears.
4. Select New from the context menu. The User Profiles New Element Properties dialogue appears.
Note: You can modify the properties of an existing user profile by right-clicking the user profile in
the User Profiles folder and selecting Properties from the context menu.
- CallsHour: For circuit-switched services, enter the average number of calls per hour for the service. The calls
per hour is used to calculate the activity probability. For circuit-switched services, one call lasting 1000 sec-
onds presents the same activity probability as two calls lasting 500 seconds each.
For packet-switched services, the CallsHour value is defined as the number of sessions per hour. A session
is like a call in that it is defined as the period of time between when a user starts using a service and when he
stops using a service. In packet-switched services, however, he may not use the service continually. For ex-
ample, with a web-browsing service, a session starts when the user opens his browsing application and ends
when he quits the browsing application. Between these two events, the user may be downloading web pages
and other times he may not be using the application or he may be browsing local files, but the session is still
considered as open. A session, therefore, is defined by the volume transferred in the uplink and downlink and
not by the time.
Note: In order for all the services defined for a user profile to be taken into account during traffic
scenario elaboration, the sum of activity probabilities must be lower than 1.
- Duration: For circuit-switched services, enter the average duration of a call in seconds. For packet-switched
services, this field is left blank.
- UL Volume: For packet-switched services, enter the average uplink volume per session in kilobytes.
- DL Volume: For packet-switched services, enter the average downlink volume per session in kilobytes.
Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a
given density (i.e., the number of subscribers with the same profile per km). To get an appropriate user distribution, you
can assign a weight to each clutter class for each environment class. You can also specify the percentage of indoor
subscribers for each clutter class. In a Monte Carlo simulation, an additional loss (as defined in the clutter class properties)
will be added to the indoor users path loss.
To create or modify a TD-SCDMA environment:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.
3. Right-click the Environments folder. The context menu appears.
4. Select New from the context menu. The Environments New Element Properties dialogue appears.
Note: You can modify the properties of an existing environment by right-clicking the
environment in the Environments folder and selecting Properties from the context
menu.
7. In the row marked with the New Row icon ( ), set the following parameters for each user profilemobility com-
bination that this TD-SCDMA environment will describe:
- User: Select a user profile.
- Mobility: Select a mobility type.
- Density (Subscriberskm2): Enter a density in terms of subscribers per square kilometre for the combination
of user profile and mobility type.
8. Click the Clutter Weighting tab.
9. For each clutter class, enter a weight that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk Sk
N k = N Area --------------------------
Wi Si
i
where:
For example: An area of 10 km with a subscriber density of 100km. Therefore, in this area, there are 1000
subscribers. The area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1"
and for Building is "4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter
class and 800 in the Building clutter class.
10. If you want you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simu-
lation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 825.
- User Profile: If you want to import user profile information from the file, under Defined, select "By field" and
select the source field from the Choice column. If you want to assign a user profile from the TD-SCDMA
Parameters folder of the Data tab, under Defined, select "By value" and select the user profile in the Choice
column.
- Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select
the source field from the Choice column. If you want to assign a mobility type from the TD-SCDMA Parame-
ters folder of the Data tab, under Defined, select "By value" and select the mobility type in the Choice column.
- Density: If you want to import density information from the file, under Defined, select "By field" and select the
source field from the Choice column. If you want to assign a density, under Defined, select "By value" and
enter a density in the Choice column for the combination of user profile and mobility type. In this context, the
term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kil-
ometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers
when the map consists of points.
Important: The name of the imported user profile or mobility type must match the corresponding
name in the TD-SCDMA Parameters folder of the Data tab. If the names do not match,
Atoll will display a warning and will not import the file.
12. Under Clutter Distribution, enter a weight for each class that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk Sk
N k = N Area --------------------------
Wi Si
i
where:
13. If you want, you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo sim-
ulation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
14. Click OK to finish importing the traffic map.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 825.
7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, BIL, IST,
BMP, PlaNET, GRC Vertical Mapper, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears.
11. Select the Description tab.
In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the
Code column.
12. For each Code, select the environment it corresponds to from the Name column.
The environments available are those available in the Environments folder, under TD-SCDMA Parameters on
the Data tab of the Explorer window. For more information, see "Modelling Environments" on page 823.
13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects"
on page 33.
6. Select the environment class from the list of available environment classes.
7. Click the Draw Polygon button ( ) to draw the polygon on the map for the selected environment class.
8. Click the Delete Polygon button ( ) and click the polygon to delete the environment class polygon on the map.
9. Click the Close button to close the Environment Map Editor toolbar and end editing.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 825.
7. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP,
PlaNET, TIF, ISTAR, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears.
11. Select the Traffic tab.
12. Select whether the users are active in the UplinkDownlink, only in the Downlink, or only in the Uplink.
13. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must
equal 100.
14. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must
equal 100.
15. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal
100.
16. Under Clutter Distribution, enter for each clutter class the percentage of indoor users.
An additional loss will be counted for indoor users during the Monte Carlo simulations. You do not have to define
a clutter weighting for traffic maps per user density because the traffic is provided in terms of user density per pixel.
17. Click OK. Atoll creates the traffic map in the Traffic folder.
18. In the table, enter a traffic density value (i.e. the number of users per km2) for each contour you have drawn.
Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains
at "0" and no data will be exported.
8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic
data to be exported.
- Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal.
- Service: Select the service that will be exported, or select "Circuit services" to export traffic using any circuit
service, or select "Packet services" to export traffic using any packet service.
- Mobility: Select the mobility type that will be exported or select "All" to export all mobility types.
- Activity: Select one of the following:
- All Activity Statuses: Select All Activity Statuses to export all users without any filter by activity status.
- Uplink: Select Uplink to export mobiles active in the uplink only.
- Downlink: Select Downlink to export mobiles active in the downlink only.
- Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity.
- Inactive: Select Inactive to export only inactive mobiles.
9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the
cumulated traffic.
10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.
4. Select Save As from the context menu. The Save As dialogue appears.
5. Enter a file name and select a file format for the traffic map.
6. Click Save.
If you are exporting a raster traffic map, you have to define:
The user activity status is an important output of the random trial and has direct consequences on the next step
of the simulation and on the network interferences. A user may be either active or inactive. Both active and inactive
users consume radio resources and create interference.
Then, Atoll randomly assigns a shadowing error to each user using the probability distribution that describes the
shadowing effect.
Finally, another random trial determines user positions in their respective traffic zone (according to the clutter
weighting and the indoor ratio per clutter class).
2. Modelling dynamic channel allocation and power control: Atoll performs dynamic channel allocation and
power control for mobiles generated in the previous step. The power control simulation algorithm is described in
"The Monte Carlo Simulation Algorithm" on page 829.
As shown in Figure 12.69, the simulation algorithm is divided in two parts. All users are evaluated by the R99 part of the
algorithm. HSDPA users, unless they have been rejected during the R99 part of the algorithm, are then evaluated by the
HSDPA part of the algorithm.
The R99 part of the algorithm simulates power control, congestion and radio resource control performed for R99 bearers
for both R99 and HSDPA users. Atoll considers each user in the order in which the users are generated, and determines
his best server. Atoll then selects the cell and the timeslot to be allocated to each user as follows:
Atoll selects the preferred carrier defined in the properties of the service being used by the user if the preferred
carrier is available on the best server and if there are enough resources available on it to accommodate the user.
Otherwise, Atoll selects the carrier according to the selected DCA strategy.
Load: The least loaded cell or timeslot is selected.
- Cell: Atoll calculates the ISCP (Interference Signal Code Power) for all the timeslots of all the cells of the
users best server considering the effect of smart antenna equipment, if any. Next, Atoll selects the carrier
with the lowest ISCP and the lowest load that has enough free timeslots to support the users service.
- Timeslot: Atoll selects the least loaded timeslots that have enough free OVSF codes for the users service.
Available RUs: The cell or timeslot with the most available resource units is selected.
- Cell: Atoll calculates the number of available resource units for all the timeslots of all the cells of the users
best server. Next, Atoll selects the carrier with most number of available resource units.
- Timeslot: Atoll selects the timeslots with the most available resource units.
Direction of Arrival: The cell or timeslot selected is the one which does not have an interfering mobile located
nearby at the same angle as the direction of arrival of the targeted mobile.
- Cell: Atoll calculates the number of interfering mobiles which are located in the same direction as the targeted
user for all the timeslots of all the cells of the users best server. Next, Atoll selects the carrier with the lowest
number of interfering mobiles in the direction of the targeted user.
- Timeslot: Atoll selects the timeslots with the lowest number of interfering mobiles in the direction of the tar-
geted user.
Sequential: Cells and timeslots are selected in a sequential order.
- Cell: Atoll allocates the carriers to users one by one. For example, if there are 3 carriers, Atoll allocates car-
rier 0 to user 0, carrier 1 to user 1, carrier 2 to user 2, carrier 0 to user 3, and so on.
- Timeslot: Atoll allocates timeslots to users one by one.
DCA reduces interference and maximises the usage of resource units. Resource units from different carriers can be
shared and allocated to the same mobile connected to an N-frequency mode compatible transmitter.
In TD-SCDMA networks, interference for a given timeslot can be of the following four types:
DL DL: Cell A and cell B both transmitting in downlink.
UL UL: Cell A and cell B both receiving in uplink.
DL UL: Cell A receiving in uplink and cell B transmitting in downlink.
UL DL: Cell A transmitting in downlink and cell B receiving in uplink.
Next, Atoll performs uplink and downlink power control considering the effect of smart antenna equipment, if any. Atoll
first calculates the required terminal power in order to reach the EbNt or CI threshold required by the service in the uplink,
followed by the required traffic channel power in order to reach the EbNt or CI threshold required by the service in the
downlink. Atoll updates the downlink and uplink ISCP for all the users.
After carrying out power control, Atoll updates the cell load parameters. For each cell whose transmitter has smart
antenna equipment assigned, Atoll updates the geometrical distribution of power transmitted using the smart antenna in
the downlink for each timeslot, which has to be updated for each user. Atoll also saves the geometrical distribution of
uplink loads calculated using the smart antenna in the uplink.
Atoll then carries out congestion and radio resource control, verifying the UL load, the total transmitted power, the number
of resource units, and OVSF codes consumed considering the services which require several timeslots.
At this point, the users can be either connected or rejected. They are rejected if:
The signal quality is not sufficient:
- On the downlink, the P-CCPCH RSCP is not high enough: status is " P-CCPCH RSCP < Min. P-CCPCH
RSCP"
- On the downlink, the power required to reach the user is greater than the maximum allowed: the status is
"Ptch > Max Ptch"
- On the uplink, there is not enough power to transmit: the status is "Pmob > Max Pmob"
Even if constraints above are respected, the network (cell and timeslot) may be saturated:
- The maximum uplink load factor is exceeded (at admission or congestion): the status is either "Admission
Rejection" or "UL Load Saturation"
- There are not enough resource units in the cell: the status is "RU Saturation"
- There is not enough power for cells: the status is "DL Load Saturation"
In the HSDPA part, Atoll processes all HSDPA bearer users. The HSDPA part of the algorithm simulates fast link adap-
tation, the scheduling of HSDPA users, and radio resource control on downlink. Two fast link adaptations are done, one
before mobile scheduling and one after.
HSDPA bearer selection is based on look-up tables available in the HSDPA Bearer Selection tab of the reception equip-
ment properties. The HSDPA and HS-SCCH powers of a cell are evaluated before calculating HS-PDSCH EcNt. The
HSDPA power (the power dedicated to HS-SCCH and HS-PDSCH of HSDPA bearer users) of a cell can be either fixed
(statically allocated) or dynamically allocated. If it is dynamically allocated, the power allocated to HSDPA depends on how
much power is required to serve R99 traffic. In other words, the power available after all common channels and all R99
traffic have been served is allocated to HS-PDSCH and HS-SCCH of HSDPA bearer users. Similarly, the power per
HS-SCCH can be either fixed or dynamically allocated in order to attain the HS-SCCH EcNt threshold. Using the
HS-SCCH and HSDPA powers, Atoll evaluates the HS-PDSCH power (the difference between the HSDPA power and the
HS-SCCH power), calculates the HS-PDSCH EcNt and, from that, the HSDPA bearer defined for the terminal reception
equipment and the user mobility).
Similarly, the terminal power per HS-SICH in the uplink can be either fixed or dynamically allocated in order to attain the
HS-SICH EcNt threshold. Before mobile scheduling, each user is processed as if he is the only user in the cell. This means
that Atoll determines the HSDPA bearer for each HSDPA user by considering the entire HSDPA power available of the
cell.
During scheduling, cell radio resources are shared between HSDPA users by the scheduler. The scheduler simultaneously
manages the maximum number of users within each cell and ranks them according to the selected scheduling technique:
Max C/I: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined) are sched-
uled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order by
the HS-PDSCH EcNt.
Round Robin: HSDPA users are scheduled in the same order as in the simulation (i.e., in random order).
Proportional Fair: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined)
are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending
order according to a random parameter which corresponds to a combination of the user rank in the simulation and
the HS-PDSCH EcNt.
After mobile scheduling, Atoll carries out a second fast link adaptation. HSDPA users are processed in the order defined
by the scheduler and the cells HSDPA power is shared among them.
Note: Execute Later enables you to automatically calculate TD-SCDMA coverage predictions
after simulations with no intermediary step by creating your simulations, creating your
predictions, and then clicking the Calculate button ( ).
- Information to retain: You can select the level of detail that will be available in the output:
- Only the Average Simulation and Statistics: None of the individual simulations are displayed or avail-
able in the group. Only an average of all simulations and statistics is available.
Note: Some calculation and display options available for coverage predictions are not available
when the option "Only the average simulation and statistics" is selected.
- No Information About Mobiles: All the simulations are listed and can be displayed. For each of them, a
properties window containing simulation output, divided among four tabs Statistics, Sites, Cells, and
Initial Conditions is available.
- Standard Information About Mobiles: All the simulations are listed and can be displayed. The properties
window of each simulation contains an additional tab with output related to mobiles.
- Detailed Information About Mobiles: All the simulations are listed and can be displayed. The properties
window for each simulation contains additional mobile-related output on the Mobiles and Mobiles (Shad-
owing values) tabs.
Tip: When you are working on very large radio-planning projects, you can reduce memory
consumption by selecting Only the Average Simulation and Statistics under
Information to retain.
6. Under Cell Load Constraints on the General tab, you can set the constraints that Atoll must respect during the
simulation:
- UL Load Factor: If you want the UL load factor to be considered in the simulation, select the UL Load Factor
check box.
- Max UL Load Factor: If you want to enter a global value for the maximum uplink load factor, click the button
( ) beside the box and select Global Threshold. Then, enter a maximum uplink load factor. If you want to
use the maximum uplink load factor defined for each timeslot in a cell, click the button ( ) beside the box
and select Defined per Cell.
- DL Load (% Pmax): If you want the DL load to be considered in the simulation, select the DL Load (% Pmax)
check box and enter a maximum downlink load in the Max DL Load box.
- Max DL Load (% Pmax): If you want to enter a global value for the maximum downlink load as a percentage
of the maximum power, click the button ( ) beside the box and select Global Threshold. Then, enter a max-
imum downlink load as a percentage of the maximum power. If you want to use the maximum downlink load
defined for each timeslot in a cell, click the button ( ) beside the box and select Defined per Cell.
7. On the TD-SCDMA tab of the dialogue, under Settings, enter an Angular Step in degrees which is used to build
the geometrical distributions of uplink and downlink loads. Angular step in used with grid of beams, statistical, and
adaptive beam modelling. For more information on the different smart antenna models, see "Types of Smart
Antenna Modelling" on page 854.
8. Under DCA Strategies, select the strategy to be used for selecting carriers and timeslots during the simulations.
There are four different strategies available:
- Load: The least loaded cell or timeslot is selected.
- Available RUs: The cell or timeslot with the most available resource units is selected.
- Direction of Arrival: The cell or timeslot selected is the one which does not have an interfering mobile located
nearby at the same angle as the direction of arrival of the targeted mobile.
- Sequential: Cells and timeslots are selected in a sequential order.
For more information about the DCA strategies, see "The Monte Carlo Simulation Algorithm" on page 829.
9. Select the Calculate Interference Between Mobiles check box and enter a maximum distance to consider
between interfering mobiles in the Max Distance field.
10. On the Source Traffic tab, enter the following:
- Global Scaling Factor: If desired, enter a scaling factor to increase user density.
The global scaling factor enables you to increase user density without changing traffic parameters or traffic
maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscrib-
ers (for environment and user profile traffic maps) or the rates or users (for live traffic maps per sector).
- Select Traffic Maps to Be Used: Select the traffic maps you want to use for the simulation.
You can select traffic maps of any type. However, if you have several different types of traffic maps and want
to make a simulation based on a specific type of traffic map, you must ensure that you select only traffic maps
of the same type. For information on the types of traffic maps, see "Creating a Traffic Map" on page 821.
Tip: Using the same generated user and shadowing error distribution for several simulations
can be useful when you want to compare the results of several simulations where only one
parameter changes.
Tip: You can make the traffic distribution easier to see by hiding geo data and predictions. For
information, see "Displaying or Hiding Objects on the Map Using the Explorer" on
page 28.
The Statistics tab: The Statistics tab contains the following two sections:
- Request: Under Request, you will find data on the connection requests:
- Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; power control has not yet finished. The result depends on the traffic description and traffic input.
- During the first random trial, each user is assigned a service and an activity status. The number of users
per activity status and the UL and DL rates that all users could theoretically generate are provided.
- The breakdown per service (total number of users, number of users per activity status, and UL and DL
rates) is given.
- Results: Under Results, you will find data on the connection results:
- The number of iterations that were run in order to converge.
- The number and the percentage of non-connected users is given along with the reason for rejection.
These figures include rejected and delayed users. These figures are determined at the end of the simula-
tion and depend on the network design.
- The number and percentage of R99 bearer users connected to a cell, the number of users per activity
status, and the UL and DL total rates they generate. These figures include R99 users as well as HSDPA
users (since all of them request an R99 bearer); they are determined in the R99 part of the algorithm.
These data are also given per service.
- The total number and the percentage of connected users with an HSDPA bearer, the number of users per
activity status, and the DL total rate that they generate.
The Sites tab: The Sites tab contains the following information per site:
- JD Factor: The joint detection factor, defined in the site equipment, is used to decrease intra-cellular interfer-
ence in uplink.
- MCJD Factor: The multi-cell joint detection factor, defined in the site equipment, is used to decrease uplink
interference from mobiles in other cells.
- Instantaneous HSDPA Rate (kbps): The instantaneous HSDPA rate in kbps.
- DL Throughput (kbps): For each service, the aggregate downlink throughput of all the transmitters at each
site.
- UL Throughput (kbps): For each service, the aggregate uplink throughput of all the transmitters at each site.
The Cells tab: Cell level results are determined from the results calculated per timeslot. The Cells tab contains
the following information, per site, transmitter, carrier:
- Max Power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties.
- P-CCPCH Power [TS0] (dBm): The P-CCPCH power as defined in the cell properties.
- DwPCH Power [DwPTS] (dBm): The DwPCH power as defined in the cell properties.
- Other CCH power [DL Traffic TS] (dBm): The power of other common channels per timeslot.
- Gain (dBi): The gain as defined in the antenna properties for that transmitter.
- Reception Loss (dB): The reception loss as defined in the transmitter properties.
- Transmission Loss (dB): The transmission loss as defined in the transmitter properties.
- Noise Figure (dB): The noise figure as defined in the transmitter properties.
- DL Traffic Power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic
timeslot.
- DL Load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total trans-
mitted power and the maximum power (powers stated in W). When the constraint "DL Load" is set, the DL
PTimeslot
Used Used
Load cannot exceed the user-defined Max DL Load. P Cell =
i
i DL
- UL Load Factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between
UL Load UL Load
the uplink total interference and the uplink total noise. F Cell = Avg ( F Timeslot )
i
i UL
- UL Noise Rise (dB): The uplink noise rise is calculated from the uplink load factor. It indicates the signal deg-
radation due to cell load (interference margin in the link budget).
- DL Load Factor (%): The downlink load factor for downlink timeslots. This factor corresponds to the ratio
DL Load DL Load
between the downlink total interference and the downlink total noise. F Cell = Avg ( F Timeslot )
i
i DL
- DL Noise Rise (dB): The downlink noise rise is calculated from the downlink load factor. It indicates the signal
degradation due to cell load (interference margin in the link budget).
- Number of DL Radio Links: The number of downlink radio links corresponds to the number of user-trans-
mitter links on the same carrier (i.e., the sum of the number of connected mobiles and the number of inactive
mobiles). This data indicates the number of users connected to the cell on the downlink.
- Number of UL Radio Links: The number of uplink radio links corresponds to the number of user-transmitter
links on the same carrier (i.e., the sum of the number of connected mobiles and the number of inactive
mobiles). This data indicates the number of users connected to the cell on the uplink.
- Connection Success Rate (%): The percentage of users able to connect to the cell with respect to the total
number of users attempting to connect. It is the ratio between the number of connected mobiles and the
number of connected and rejected mobiles.
- UL Total Requested Rate (kbps): The sum of all the uplink throughputs requested by the mobiles attempting
to connect to a carrier.
- DL Total Requested Rate (kbps): The sum of all the downlink throughputs requested by mobiles attempting
to connect to a carrier.
- UL Total Obtained Rate (kbps): The traffic carried by the cell in terms of throughput in the uplink.
- DL Total Obtained Rate (kbps): The traffic carried by the cell in terms of throughput in the downlink.
- Required UL Resource Units: The number of resource units required to carry the traffic demand in the uplink.
- UL Resource Units: The number of resource units used in the cell in the uplink.
- Required DL Resource Units: The number of resource units required to carry the traffic demand in the down-
link.
- DL Resource Units: The number of resource units used in the cell in the downlink.
The Timeslots tab: The Timeslots tab contains the following information, per site, transmitter, carrier, and time-
slot:
- Max Power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties.
- P-CCPCH Power [TS0] (dBm): The P-CCPCH power as defined in the cell properties.
- Other CCH power (dBm): The power of other common channels per timeslot.
- Gain (dBi): The gain as defined in the antenna properties for that transmitter.
- Reception Loss (dB): The reception loss as defined in the transmitter properties.
- Transmission Loss (dB): The transmission loss as defined in the transmitter properties.
- Noise Figure (dB): The noise figure as defined in the transmitter properties.
- DL Traffic Power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic
timeslot.
- Angular Distribution of UL and DL Loads: The angular distribution of downlink transmitted power and uplink
loads computed for cells whose transmitters have smart antenna equipment. This field contains binary data if
you are using a third-party smart antenna model.
- Max DL Load (% Pmax): The maximum percentage of downlink power that a cell can use. It is defined either
in the cell properties or in the simulation creation dialogue.
- DL Load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total trans-
mitted power and the maximum power (powers stated in W). When the constraint "DL Load" is set, the DL
Load cannot exceed the user-defined Max DL Load.
- Max UL Load Factor (%): The maximum uplink load factor not to be exceeded. This limit is taken into account
during the simulation if the option UL Load is selected. If the UL load option is not selected during a simula-
tion, this value is not taken into consideration.
- UL Load Factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between
the uplink total interference and the uplink total noise.
- UL Noise Rise (dB): The uplink noise rise is calculated from the uplink load factor. It indicates the signal deg-
radation due to cell load (interference margin in the link budget).
- DL Load Factor (%): The downlink load factor for downlink timeslots. This factor corresponds to the ratio
between the downlink total interference and the downlink total noise.
- DL Noise Rise (dB): The downlink noise rise is calculated from the downlink load factor. It indicates the signal
degradation due to cell load (interference margin in the link budget).
- Resource Units: The number of resource units on a timeslot for carrying traffic. Each timeslot can have a
maximum of 16 resource units.
- Available HS-PDSCH Power (dBm): The available HS-PDSCH power as defined in the timeslot properties.
This is the power available for the HS-PDSCH of HSDPA users. The value is either defined when the HS-
PDSCH power is allocated statically, or determined by a simulation when the option HS-PDSCH Dynamic
Power Allocation is selected.
- Transmitted HSDPA Power (dBm): The power transmitted by the cell to serve users connected to HSDPA
radio bearers. If HSDPA power is allocated statically, the transmitted HSDPA power is equal to the available
HSDPA power. If HSDPA power is allocated dynamically, the transmitted HSDPA power is the remaining
power after allocation of power to the users connected to R99 radio bearers, and the power headroom.
The Mobiles tab: The Mobiles tab contains the following information:
- Name: The name of the mobile as assigned during the random user generation.
- X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the
second random trial).
- Service: The service assigned during the first random trial, during the generation of the user distribution.
- Terminal: The assigned terminal. Atoll uses the assigned service and activity status to determine the terminal
and the user profile.
- User: The assigned user profile. Atoll uses the assigned service and activity status to determine the terminal
and the user profile.
- Mobility: The mobility type assigned during the first random trial during the generation of the user distribution.
- DL Activity: The activity status on the downlink assigned during the first random trial, during the generation
of the user distribution.
- UL Activity: The activity status on the uplink assigned during the first random trial, during the generation of
the user distribution.
- Indoor: This field indicates whether indoor losses have been added or not.
- Connection Status: The connection status indicates whether the user is connected or rejected at the end of
the simulation. If connected, the connection status corresponds to the activity status. If rejected, the rejection
cause is given.
- HSDPA Connection Status: The connection status indicates whether the user is connected to an HSDPA
radio bearer, delayed, or rejected at the end of the simulation.
- Best Server: The users best server.
- P-CCPCH RSCP: The received signal code power on the P-CCPCH pilot channel.
- UL Total Requested Rate (kbps): For an R99 user, the uplink total requested rate corresponds to the uplink
nominal rate of the R99 bearer associated to the service. For an HSDPA user, the uplink total requested rate
corresponds to the nominal rate of ADPCH-UL64 R99 bearer.
- DL Total Requested Rate (kbps): For an R99 user, the downlink total requested rate corresponds to the
downlink nominal rate of the R99 bearer associated to the service. For an HSDPA user, the downlink total
requested rate is the sum of the ADPCH-UL64 radio bearer nominal rate and the RLC peak rate that the
selected HSDPA radio bearer can provide.
- UL Total Obtained Rate (kbps): For an R99 user, the total obtained rate is the same as the total requested
rate if he is connected. If the user was rejected, the total obtained rate is zero.
For an HSDPA user connected to an HSDPA bearer, the uplink total obtained rate equals the total requested
rate. If the HSDPA user is delayed (he is only connected to an R99 radio bearer), the uplink total obtained rate
corresponds to the uplink nominal rate of ADPCH-UL64 radio bearer. Finally, if the HSDPA user is rejected
either in the R99 part or in the HSDPA part (because the HSDPA scheduler is saturated), the uplink total ob-
tained rate is zero.
- DL Total Obtained Rate (kbps): For an R99 user, the total obtained rate is the same as the total requested
rate if he is connected. If the user was rejected, the total obtained rate is zero.
For an HSDPA user connected to an HSDPA bearer, the downlink total obtained rate corresponds to the in-
stantaneous rate; this is the sum of the ADPCH-UL64 radio bearer nominal rate and the RLC peak rate pro-
vided by the selected HSDPA radio bearer after scheduling and radio resource control. If the HSDPA user is
delayed (he is only connected to an R99 radio bearer), the downlink total obtained rate corresponds to the
downlink nominal rate of ADPCH-UL64 radio bearer. Finally, if the HSDPA user is rejected either in the R99
part or in the HSDPA part (because the HSDPA scheduler is saturated), the downlink total obtained rate is
zero.
- 1st, 2nd, 3rd DL TS Rank (Carrier): A mobile can have at most three timeslots allocated for traffic. These
timeslots can be located on different carriers (cells) of the same transmitter. These columns list the numbers
of the 1st, 2nd, and 3rd timeslot assigned to a user, and the carrier number on which the timeslots are located.
For example, if a user is assigned two downlink timeslots, 4 and 6, on the carriers 0 and 2, the 1st DL TS Rank
(Carrier) will be "4 (0)" and 2nd DL TS Rank (Carrier) will be "6 (2)".
- 1st, 2nd, 3rd UL TS Rank (Carrier): A mobile can have at most three timeslots allocated for traffic. These
timeslots can be located on different carriers (cells) of the same transmitter. These columns list the numbers
of the 1st, 2nd, and 3rd timeslot assigned to a user, and the carrier number on which the timeslots are located.
For example, if a user is assigned two uplink timeslots, 2 and 3, on the carriers 0 and 2, the 1st UL TS Rank
(Carrier) will be "2 (0)" and 2nd UL TS Rank (Carrier) will be "3 (2)".
- 1st, 2nd, 3rd TS Mobile Total Power (UL) (dBm): The total mobile power corresponds to the total power
transmitted by the terminal on the uplink and on the timeslots assigned to the mobile.
- 1st, 2nd, 3rd TS Cell Total Power (DL) (dBm): The cell traffic power corresponds to the power transmitted
by the cell on the downlink for a mobile on the timeslots assigned to the mobile.
The following columns only appear if, when creating the simulation as explained in "Creating Simulations" on
page 831, you select "Detailed information about mobiles" under Information to Retain:
- 1st, 2nd, 3rd TS Extra Interference of UL Mobiles (DL) (dBm): The interference received on downlink
timeslots from mobiles transmitting in the uplink. This interference is calculated if you select the Calculate
Interference Between Mobiles option when creating the simulation.
- 1st, 2nd, 3rd TS Required HSDPA Power (dBm): This is the HSDPA power required to provide the HSDPA
bearer user with the downlink requested rate.
- 1st, 2nd, 3rd TS Obtained HSDPA Power (dBm): This is the HSDPA power required to provide the HSDPA
bearer user with the downlink obtained rate.
- 1st, 2nd, 3rd HSDPA TS Rank (Carrier): These columns list the numbers of the 1st, 2nd, and 3rd timeslot
assigned to an HSDPA user, and the carrier number on which the timeslots are located.
- Requested HSDPA Bearer Index: The HSDPA bearer requested by an HSDPA user.
- Obtained HSDPA Bearer Index: The HSDPA bearer assigned to an HSDPA user by the DCA and resource
allocation algorithm.
- Clutter: The clutter class on which the mobile is located.
- DL and UL Orthogonality Factor: The orthogonality factor used in the simulation. The orthogonality factor is
the remaining orthogonality of the OVSF codes at reception. The value used is the orthogonality factor set in
the clutter classes.
- Spreading Angle (): The spreading angle used in the simulation. The value used is the spreading angle set
in the clutter classes.
The Mobiles (Shadowing Values) tab: The Mobiles (Shadowing Values) tab contains information on the shad-
owing margin for each link between the receiver and up to ten closest potential transmitters:
Note: The Mobiles (Shadowing Values) tab only appears if, when creating the simulation as
explained in "Creating Simulations" on page 831, you select "Detailed information about
mobiles" under Information to Retain.
- The parameters defined per clutter class, such as the uplink and downlink orthogonality factors, indoor
loss, spreading angle, and the various standard deviations (Model, P-CCPCH EbNt or CI, DL EbNt or CI,
and UL EbNt or CI).
- The parameters related to the clutter classes, including the default values.
The Statistics tab: The Statistics tab contains the following two sections:
- Request: Under Request, you will find data on the connection requests:
- Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; power control has not yet finished. The result depends on the traffic description and traffic input.
- During the first random trial, each user is assigned a service and an activity status. The number of users
per activity status and the UL and DL rates that all users could theoretically generate are provided.
- The breakdown per service (total number of users, number of users per activity status, and UL and DL
rates) is given.
- Results: Under Results, you will find data on the connection results:
- The number of iterations that were run in order to converge.
- The number and the percentage of non-connected users is given along with the reason for rejection.
These figures include rejected and delayed users. These figures are determined at the end of the simula-
tion and depend on the network design.
- The number and percentage of R99 bearer users connected to a cell, the number of users per activity
status, and the UL and DL total rates they generate. These figures include R99 users as well as HSDPA
users (since all of them request an R99 bearer); they are determined in the R99 part of the algorithm.
These data are also given per service.
- The total number and the percentage of connected users with an HSDPA bearer, the number of users per
activity status, and the DL total rate that they generate.
The Sites (Average) and Sites (Standard Deviation) tabs: The Sites (Average) and Sites (Standard Deviation)
tabs contain the following average and standard deviation information, respectively, per site:
- JD Factor: The joint detection factor, defined in the site equipment, is used to decrease intra-cellular interfer-
ence in uplink.
- MCJD Factor: The multi-cell joint detection factor, defined in the site equipment, is used to decrease uplink
interference from mobiles in other cells.
- Instantaneous HSDPA Rate (kbps): The instantaneous HSDPA rate in kbps.
- DL Throughput (kbps): For each service, the aggregate downlink throughput of all the transmitters at each
site.
- UL Throughput (kbps): For each service, the aggregate uplink throughput of all the transmitters at each site.
The Cells (Average) and Cells (Standard Deviation) tabs: The Cells (Average) and Cells (Standard Deviation)
tabs contain the following average and standard deviation information, respectively, per site, transmitter, and
carrier:
- Max Power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties.
- P-CCPCH Power [TS0] (dBm): The P-CCPCH power as defined in the cell properties.
- DwPCH Power [DwPTS] (dBm): The DwPCH power as defined in the cell properties.
- Other CCH power [DL Traffic TS] (dBm): The power of other common channels per timeslot.
- Gain (dBi): The gain as defined in the antenna properties for that transmitter.
- Reception Loss (dB): The reception loss as defined in the transmitter properties.
- Transmission Loss (dB): The transmission loss as defined in the transmitter properties.
- Noise Figure (dB): The noise figure as defined in the transmitter properties.
- DL Traffic Power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic
timeslot.
- DL Load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total trans-
mitted power and the maximum power (powers stated in W). When the constraint "DL Load" is set, the DL
Load cannot exceed the user-defined Max DL Load.
- UL Load Factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between
the uplink total interference and the uplink total noise.
- Number of DL Radio Links: The number of downlink radio links corresponds to the number of user-trans-
mitter links on the same carrier. This data indicates the number of users connected to the cell on the downlink.
- Number of UL Radio Links: The number of uplink radio links corresponds to the number of user-transmitter
links on the same carrier. This data indicates the number of users connected to the cell on the uplink.
- Connection Success Rate (%): The percentage of users able to connect to the cell with respect to the total
number of users attempting to connect.
- UL Requested Rate (kbps): The traffic demand in terms of throughput in the uplink.
- UL Obtained Rate (kbps): The traffic carried by the cell in terms of throughput in the uplink.
- DL Requested Rate (kbps): The traffic demand in terms of throughput in the downlink.
- DL Obtained Rate (kbps): The traffic carried by the cell in terms of throughput in the downlink.
- Required UL Resource Units: The number of resource units required to carry the traffic demand in the uplink.
- UL Resource Units: The number of resource units available in the cell in the uplink.
- Required DL Resource Units: The number of resource units required to carry the traffic demand in the down-
link.
- DL Resource Units: The number of resource units available in the cell in the downlink.
The Timeslots (Average) and Timeslots (Standard Deviation) tabs: The Timeslots (Average) and Timeslots
(Standard Deviation) tabs contain the following average and standard deviation information, respectively, per site,
transmitter, carrier, and timeslot:
- Max Power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties.
- P-CCPCH Power [TS0] (dBm): The P-CCPCH power as defined in the cell properties.
- Other CCH power (dBm): The power of other common channels per timeslot.
- Gain (dBi): The gain as defined in the antenna properties for that transmitter.
- Reception Loss (dB): The reception loss as defined in the transmitter properties.
- Transmission Loss (dB): The transmission loss as defined in the transmitter properties.
- Noise Figure (dB): The noise figure as defined in the transmitter properties.
- DL Traffic Power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic
timeslot.
- Angular Distribution of UL and DL Loads: The angular distribution of downlink transmitted power and uplink
loads calculated for cells whose transmitters have smart antenna equipment. This field contains binary data if
you are using a third-party smart antenna model.
- Max DL Load (% Pmax): The maximum percentage of downlink power that a cell can use. It is defined either
in the cell properties or in the simulation creation dialogue.
- DL Load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total trans-
mitted power and the maximum power (powers stated in W). When the constraint "DL Load" is set, the DL
Load cannot exceed the user-defined Max DL Load.
- Max UL Load Factor (%): The maximum uplink load factor not to be exceeded. This limit is taken into account
during the simulation if the option UL Load is selected. If the UL load option is not selected when the simula-
tion is defined, this value is not taken into consideration.
- UL Load Factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between
the uplink total interference and the uplink total noise.
- UL Noise Rise (dB): The uplink noise rise is calculated from the uplink load factor. It indicates the signal deg-
radation due to cell load (interference margin in the link budget).
- DL Load Factor (%): The downlink load factor for downlink timeslots. This factor corresponds to the ratio
between the downlink total interference and the downlink total noise.
- DL Noise Rise (dB): The downlink noise rise is calculated from the downlink load factor. It indicates the signal
degradation due to cell load (interference margin in the link budget).
- Resource Units: The number of resource units on a timeslot for carrying traffic. Each timeslot can have a
maximum of 16 resource units.
- Available HS-PDSCH Power (dBm): The available HS-PDSCH power as defined in the timeslot properties.
This is the power available for the HS-PDSCH of HSDPA users. The value is either fixed by the user when the
HS-PDSCH power is allocated statically, or by a simulation when the option HS-PDSCH Dynamic Power
Allocation is selected.
- Transmitted HSDPA Power (dBm): The power transmitted by the cell to serve users connected to HSDPA
radio bearers. If HSDPA power is allocated statically, the transmitted HSDPA power is equal to the available
HSDPA power. If HSDPA power is allocated dynamically, the transmitted HSDPA power is the remaining
power after allocation of power to the users connected to R99 radio bearers, and the power headroom.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
Replaying a group: When you replay an existing group of simulations, Atoll reuses the same user distribution
(users with a service, a mobility and an activity status) as the one used to calculate the initial simulation. The shad-
owing error distribution between simulations is different. Traffic parameter changes (such as, maximum and min-
imum traffic channel powers allowed, EbNt or CI thresholds, etc.) may be taken into account or not. Finally, radio
data modifications (new transmitters, changes to the antenna azimuth, etc.) are always taken into account during
the power control (or rate/power control) simulation.
To replay a group of simulations, see "Replaying a Simulation or Group of Simulations" on page 842.
Using the Generator Initialisation Number: When you create groups of simulations using the same generator
initialisation number (which must be an integer other than 0), Atoll generates the same user and shadowing error
distributions (user with a service, a mobility, an activity status, and a shadowing error) in all groups using the same
number. However, any modifications to traffic parameters (such as, maximum and minimum traffic channel powers
allowed, EbNt or CI thresholds, etc.) and radio data (new transmitter, azimuth, etc.) are taken into account during
the power control simulation.
By creating and calculating one group of simulations, making a change to the network and then creating and calcu-
lating a new group of simulations using the same generator initialisation number, you can see the difference your
parameter changes make.
To create a new simulation to a group of simulations using the generator initialisation number, see "Adding a Simu-
lation to a Group of Simulations" on page 842.
Duplicating a Group: When you duplicate a group, Atoll creates a group of simulations with the same simulation
parameters as those used to generate the group of simulations. You can then modify the simulation parameters
before calculating the group.
To duplicate a group of simulations, see "Duplicating a Group of Simulations" on page 843.
Note: When adding a simulation to an existing group of simulations, the parameters originally
used to calculate the group of simulations are used for the new simulations.
Consequently, few parameters can be changed for the added simulation.
5. On the General tab of the dialogue, if desired, change the Name and Comments for this group of simulations.
6. Under Execution on the General tab, you can set the following parameters:
- Number of Simulations: Enter the number of simulations to added to this group of simulations.
- Execute Later: If you select the Execute Later check box, the simulation will not be carried out until you click
the Calculate button ( ). If the Execute Later check box is not selected, the simulation will be carried out
as soon as you click OK and close the dialogue.
7. Click OK. Atoll immediately begins the simulation unless you selected the Execute Later check box on the Gen-
eral tab.
Note: When replaying an existing group of simulations, some parameters originally used to
calculate the group of simulations are reused for the replayed group. Consequently, few
parameters can be changed for the replayed group.
5. In the General tab of the dialogue, you can set the following parameters:
- Select the level of detail as explained in "Creating Simulations" on page 831 that will be available in the output
from the Information to retain list.
- Under Cell Load Constraints, you can set the constraints as explained in "Creating Simulations" on page 831
that Atoll must respect during the simulation.
6. In the Source Traffic tab of the dialogue, check the Refresh Traffic Parameters check box if you want to take into
account traffic parameter changes (such as, maximum and minimum traffic channel powers allowed, Eb/Nt thresh-
olds, etc.) in the replayed simulation.
7. In the Advanced tab, you can set the following parameters:
- Max Number of Iterations: Enter the maximum number of iterations that Atoll should run to make conver-
gence.
- UL Convergence Threshold: Enter the relative difference in terms of interference and connected users on
the uplink that must be reached between two iterations.
- DL Convergence Threshold: Enter the relative difference in terms of interference and connected users on
the downlink that must be reached between two iterations.
- Under Quality Threshold Type, select whether the simulations will be carried out using the Eb/Nt or C/I. For
more information on the quality threshold type selection, see "The Global Transmitter Parameters" on
page 852.
8. In the TD-SCDMA tab, you can set the following parameters:
- Angular Step: The angle in degrees used to build the geometrical distributions of uplink and downlink loads.
The angular step in used with grid of beams, statistical, and adaptive beam modelling. For more information
on the different smart antenna models, see "Types of Smart Antenna Modelling" on page 854.
- Carrier Selection and Timeslot Selection: The DCA strategies to be used for selecting carriers and timeslots
during the simulations. For more information about the DCA strategies, see "The Monte Carlo Simulation Algo-
rithm" on page 829.
- Calculate Interference Between Mobiles: Select the check box and enter a maximum distance to be con-
sidered between interfering mobiles in the Max Distance field.
9. Click OK. Atoll immediately begins the simulation unless you selected the Execute Later check box on the Gen-
eral tab.
Creating a New Simulation or Group of Simulations Using the Generator Initialisation Number
To create a new simulation or group of simulations using the generator initialisation number:
1. Click the Data tab in the Explorer window.
2. Right-click the TD-SCDMA Simulations folder. The context menu appears.
3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears.
4. Click the Advanced tab.
5. Under Generator Initialisation, enter an integer as the generator initialisation value. The integer must be the
same generator initialisation number as used in the group of simulations with the user and shadowing error distri-
butions you want to use in this simulation or group of simulations. If you enter "0", the default, the user and shad-
owing error distribution will be random. If you enter any other integer, the same user and shadowing error
distribution will be used for any simulation using the same generator initialisation value.
6. For information on setting other parameters, see "Creating Simulations" on page 831.
Tip: You can create a new group of simulations with the same parameters as the original group
of simulations by duplicating an existing one as explained in "Duplicating a Group of
Simulations" on page 843.
- DwPCH Reception Analysis (CI): For information on making a DwPCH reception analysis, see "Making a
DwPCH Signal Quality Prediction" on page 780.
- Service Area (EbNt) Downlink or Service Area (CI) Downlink: For information on making a coverage pre-
diction the downlink service area, see "Studying Downlink and Uplink Service Areas" on page 783.
- Service Area (CI) Uplink: For information on making a coverage prediction the uplink service area, see
"Studying Downlink and Uplink Service Areas" on page 783.
- Effective Service Area (EbNt) or Effective Service Area (CI): For information on making a coverage anal-
ysis for the effective service area, see "Studying Effective Service Area" on page 785.
Coverage predictions on noise and interference:
- Downlink Total Noise: For information on making a downlink total noise coverage prediction, see "Studying
Downlink Total Noise" on page 787.
- Cell to Cell Interference Zones: For information on making a coverage analysis for cell-to-cell interference,
see "Studying Cell to Cell Interference" on page 789.
- UpPCH Interference Zones: For information on making a coverage analysis for UpPCH interference in case
of UpPCH shifting, see "Studying UpPCH Interference" on page 790.
A coverage prediction for baton handover analysis:
- Baton Handover: For information on making a baton handover coverage prediction, see "Making a Baton
Handover Coverage Prediction" on page 792.
An HSDPA coverage prediction to analyse HS-PDSCH quality and HSDPA data rate:
- HSDPA Coverage Prediction: For information on making an HSDPA coverage prediction, see "HSDPA Cov-
erage Prediction" on page 793.
Note: Files with the extension PLN, as well as some FMT files (created with previous versions of
TEMS) are imported directly into Atoll; you will not be asked to define the data structure
using the Import of Measurement Files dialogue.
6. If you already have an import configuration defining the data structure of the imported file or files, you can select
it from the Configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have
an import configuration, continue with step 7.
a. Under Configuration, select an import configuration from the Configuration list.
b. Continue with step 10.
Notes:
When importing a test mobile data path file, existing configurations are available in the Files
of type list of the Open dialogue, sorted according to their date of creation. After you have
selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises
the extension. In case several configurations are associated with an extension, Atoll chooses
the first configuration in the list.
The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in
the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see
the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters:
- Name: By default, Atoll names the new test mobile data path after the imported file. You can change this
name if desired.
- Under Receiver, set the Height of the receiver antenna and the Gain and Losses.
- Under Measurement Conditions,
- Units: Select the measurement units used.
- Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document.
If the coordinates used in the file you are importing are different than the coordinates used in the Atoll
document, you must click the Browse button ( ) and select the coordinate system used in the test
mobile data file. Atoll will then convert the data imported to the coordinate system used in the Atoll docu-
ment.
8. Click the Setup tab (see Figure 12.74).
Figure 12.74: The Setup tab of the Import of Measurement Files dialogue
a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Dec-
imal Symbol used in the file.
b. Click Setup to link file columns and internal Atoll fields. The Test Mobile Data Configuration dialogue ap-
pears.
c. Select the columns in the imported file that give the X-Coordinates and the Y-Coordinates of each point in
the test mobile data file.
Note: You can also identify the columns containing the XY coordinates of each point in the test
mobile data file by selecting them from the Field row of the table on the Setup tab.
d. In the SC Group Identifier box, enter a string that must be found in the column names identifying the scram-
bling code group of scanned cells. For example, if the string "SC_Group" is found in the column names iden-
tifying the scrambling code group of scanned cells, enter it here. Atoll will then search for columns with this
string in the column name.
If there is no scrambling code group information contained in the test mobile data file, leave the SC Group
Identifier box empty.
e. In the SC Identifier box, enter a string that must be found in the column names identifying the scrambling code
of scanned cells. For example, if the string "SC" is found in the column names identifying the scrambling code
of scanned cells, enter it here. Atoll will then search for columns with this string in the column name.
f. From the Scramb. Code Format list, select the scrambling code format, either "Decimal" or "Hexadecimal."
g. Click OK to close the Test Mobile Data Configuration dialogue.
Important:
If you have correctly entered the information under File on the Setup tab, and the necessary
values in the Test Mobile Data Configuration dialogue, Atoll should recognize all columns in
the imported file. If not, you can click the name of the column in the table in the Field row and
select the column name. For each field, you must ensure that each column has the correct data
type in order for the data to be correctly interpreted. The default value under Type is "<Ignore>".
If a column is marked with "<Ignore>", it will not be imported.
The data in the file must be structured so that the columns identifying the scrambling code group
and the scrambling code are placed before the data columns for each cell. Otherwise Atoll will
not be able to properly import the file.
9. If you want to save the definition of the data structure so that you can use it again, you can save it as an import
configuration:
a. On the Setup tab, under Configuration, click Save. The Configuration dialogue appears.
b. By default, Atoll saves the configuration in a special file called "NumMeasINIfile.ini" found in Atolls installa-
tion folder. In case you cannot write into that folder, you can click Browse to choose a different location.
c. Enter a Configuration Name and an Extension of the files that this import configuration will describe (for ex-
ample, "*.csv").
d. Click OK.
Atoll will now select this import configuration automatically every time you import a test mobile data path file
with the selected extension. If you import a file with the same structure but a different extension, you will be
able to select this import configuration from the Configuration list.
Notes:
You do not have to complete the import procedure to save the import configuration and have
it available for future use.
When importing a CW measurement file, you can expand the NumMeasINIfile.ini file by clicking
the button ( ) in front of the file in the Setup part to display all the available import configura-
tions. When selecting the appropriate configuration, the associations are automatically made
in the table at the bottom of the dialogue.
You can delete an existing import configuration by selecting the import configuration under
Setup and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The
mobile data are imported into the current Atoll document.
Notes:
Fast Display forces Atoll to use the lightest symbol to display the points. This is useful when
you have a very large number of points.
You can not use Multiple Shadings if the Fast Display check box has been selected.
You can sort test mobile data paths in alphabetical order on the Data tab of the Explorer window
by right-clicking the Test Mobile Data Path folder and selecting Sort Alphabetically from the
context menu.
You can export the display settings of a test mobile data path in a configuration file to make them
available for future use. You can export the display settings or import display settings by clicking
the Actions button on the Display tab of the test mobile data paths Properties dialogue and
selecting Export or Import from the menu.
6. By default, the data in all clutter classes is displayed. Clear the check box of each clutter class whose points you
do not want to use.
Note: You can permanently delete the points located in the clutter classes whose check boxes
you clear by selecting the Delete points outside the filter check box.
b. Underneath each column name, enter the criterion on which the column will be filtered as explained in the fol-
lowing table:
9. Click OK to filter the data according to the criteria you have defined.
Filters are combined first horizontally, then vertically. For more information on filters, see "Advanced Data Filtering"
on page 71.
Note: The Refresh Geo Data option available in the context menu of Test Mobile Data paths
enables you to update heights (DTM, clutter heights, DTM + clutter) and the clutter class
of test mobile data points after adding new geographic maps or modifying existing ones.
Note: Atoll can display the best server. If you want to display, for example, the point signal
level, remember to select the check box for the point signal level for all servers in the For
the Fields list. The new column will then display the point signal level for the selected
transmitter for all servers if a value exists.
8. Click OK. Atoll creates a new column in the test mobile path data table for the selected transmitters and with the
selected values.
5. Click Display at the top of the Test Mobile Data window. The Display Parameters dialogue appears (see
Figure 12.77).
Note: You can change the display status or the colour of more than one field at a time. You can
select contiguous fields by clicking the first field, pressing SHIFT and clicking the last field
you want to import. You can select non-contiguous fields by pressing CTRL and clicking
each field. You can then change the display status or the colour by right-clicking on the
selected fields and selecting the choice from the context menu.
The selected fields are displayed in the Test Mobile Data window.
7. You can display the data in the test mobile path in two ways:
- Click the values in the Test Mobile Data window.
- Click the points on the test mobile path in the map window.
The test mobile data path appears in the map window as an arrow pointing towards the serving cell, with a number
identifying the best server (see Figure 12.76 on page 850). If the transmitter display type is "Automatic," both the
number and the arrow are displayed in the same colour as the transmitter. For information on changing the display
type to "Automatic," see "Defining the Display Type" on page 34.
8. You can display a second Y-axis on the right side of the window in order to display the values of a variable with
different orders of magnitude than the ones selected in the Display Parameters dialogue. You can select the sec-
ondary Y-axis from the right-hand list on the top of the Test Mobile Data window. The selected values are dis-
played in the colours defined for this variable in the Display Parameters dialogue.
9. You can change the zoom level of the Test Mobile Data window display in the following ways:
- Zoom in or out:
i. Right-click the Test Mobile Data window.
ii. Select Zoom In or Zoom Out from the context menu.
- Select the data to zoom in on:
i. Right-click the Test Mobile Data window on one end of the range of data you want to zoom in on.
ii. Select First Zoom Point from the context menu.
iii. Right-click the Test Mobile Data window on the other end of the range of data you want to zoom in on.
iv. Select Last Zoom Point from the context menu. The Test Mobile Data window zooms in on the data be-
tween the first zoom point and the last zoom point.
10. Click the data in the Test Mobile Data window to display the selected point in the map window. Atoll will recentre
the map window on the selected point if it is not presently visible.
Tip: If you open the table for the test mobile data you are displaying in the Test Mobile Data
window, Atoll will automatically display in the table the data for the point that is displayed
in the map and in the Test Mobile Data window (see Figure 12.76 on page 850).
a. Select Print from the context menu. The Print dialogue appears.
b. Click OK to print the contents of the Test Mobile Data window.
d. Press ENTER to create the carrier pair and to create a new row.
Important: When you have more than one frequency band, the carriers must be numbered
sequentially, contiguously (i.e., you cannot skip numbers in a range of carriers, and the
range of carriers in one band cannot overlap the range of carriers in another), and
uniquely (i.e., you can only use each number once).
For example:
Band 2010: First carrier: 0; Last carrier 1 and Band 900: First carrier: 2; Last carrier: 2
- Frame: The duration of a TD-SCDMA frame (10 ms). A frame includes two subframes of equal duration.
- Number of Chips per Timeslot: Under Number of Chips per Timeslot, you have the number of chips cor-
responding to the data, midamble, and the guard periods.
- Guard Period: The number of chips in the guard period of each timeslot (16).
- Data: The number of data chips in each timeslot (704).
- Midamble: The number of midamble chips in each timeslot (144).
The subframe duration, the number of timeslots per subframe, and the numbers of chips per timeslot are used
to calculate the processing gain for each service (see example below).
- Number of Pilot Chips: Under Number of Pilot Chips, you have the description of the pilot timeslot:
- Guard Period: The number of chips in the guard period between DwPTS and UpPTS (96).
- DwPTS: The Total number of chips used in the DwPTS timeslot (96), which are divided into a Guard
Period (32) and a Synch period (64).
- UpPTS: The Total number of chips used in the UpPTS timeslot (160), which are divided into a Guard
Period (32) and a Synch period (128).
The parameters that can be modified include:
DL Powers: Under DL Powers, you can define whether the power values on the downlink are Absolute or Relative
to Pilot. The power values affected are the DwPCH powers and other common channel powers defined in the cell
properties for TS0 and for each timeslot, as well as the minimum and maximum traffic channel powers defined for
services. Atollautomatically converts the power values defined in the cell properties (i.e. DwPCH and other
common channel powers) when changing the option. On the other hand, the values for the minimum and max-
imum traffic channel powers have to be modified manually.
Quality Threshold Type: Under Quality Threshold Type, you can select whether the signal quality thresholds
entered in the mobility types and radio bearers are EbNt or C(I+N).
Note: Atoll ensures consistency between the quality threshold parameter and the parameter
which is calculated during coverage predictions and Monte Carlo simulations. For
example, if you set the Quality Threshold Type to EbNt in the Global Parameters tab, all
the signal quality thresholds are considered to be defined in terms of EbNt. If you
calculate a CI-based coverage prediction or simulation, Atoll converts the thresholds
from EbNt to CI, by removing the processing gain from the EbNt values, in order to
calculate and compare CI. Similarly, if the Quality Threshold Type is set to CI, and the
calculations are performed for Eb/Nt, Atoll converts all CI thresholds to EbNt for the
calculations.
Spreading Rate: The chip rate used in TD-SCDMA for spreading the user signals (1.28 Mcps by default).
P-CCPCH Processing Gain: The processing gain is the ratio of the spread bandwidth to the unspread bandwidth.
It is set to 13.8 dB (= 24 times) by default.
Spreading Factor: Under Spreading Factor, you have the minimum and maximum spreading factors allowed in
TD-SCDMA:
- Min.: The lowest spreading factor that can be used (1).
- Max: The highest spreading factor that can be used (16).
Interferences: Under Interferences, you can define the parameter used to calculate interference on the downlink.
- Nt: You can select "Total noise" and Atoll will calculate Nt as the noise generated by all transmitters plus
thermal noise, or you can select "Without useful signal" and Atoll will calculate Nt as the total noise less the
signal of the studied cell.
HSDPA: Under HSDPA, you can define how total noise is calculated for HSDPA.
- Nt: You can select "Total noise" and Atoll will calculate Nt as the noise generated by all transmitters plus
thermal noise or you can select "Without useful signal" and Atoll will calculate Nt as the total noise less the
signal of the studied cell.
The processing gain is the ratio between the chip rate transmitted on the air interface and the data rate of a service. The
processing gains on the uplink and downlink are calculated from the uplink and downlink data rates defined in the proper-
ties of the service that you have set. The following example shows how the processing gains are calculated for different
services.
W
G P = Processing Gain = -----
R
Where W is the chip rate for TD-SCDMA, and R is the data rate per timeslot of the service.
The chip rate is calculated from the number of data chips per timeslot and the subframe duration:
TS
N Data Chips 704
W = -------------------------- = --------------- = 140800 bps
D Subframe 0.005
TS
Where N Data Chips is the number of data chips per timeslot (704), and D Subframe is the subframe duration (5 ms).
Taking the service "Mobile Internet Access" for example, the service data rates per timeslot in uplink and downlink are
calculated to be:
DL 384000 UL 64000
R = -------------------- = 128000 bps and R = ---------------- = 64000 bps
3 1
Where 3 and 1 are the number of downlink and uplink timeslots, respectively.
The uplink and downlink processing gains are then calculated:
DL 140800 UL 140800
GP = -------------------- = 1.1 = 0.414 dB and G P = -------------------- = 2.2 = 3.4242 dB
128000 64000
Important: Although the number of beams in a GOB is not limited, calculation times with a large
number of beams will be longer.
The Atoll TD-SCDMA project template contains sample smart antenna equipment. You should create smart antenna
equipment according to the specifications of your equipment supplier, or import them in Atoll, in order to use real data in
calculations.
The following sections explain how to create and import grids of beams:
"Creating a Grid of Beams (GOB)" on page 855.
"Adding Antennas to a Grid of Beams (GOB)" on page 855.
"Importing a Grid of Beams (GOB)" on page 855.
"The Grid of Beams (GOB) Import Format" on page 855.
In Atoll, a grid of beams is a list of antennas. A list of antennas can include any number of antennas listed in the Antennas
folder.
To create an antenna list:
1. Click the Data tab in the Explorer window.
2. Right-click the Antennas folder. The context menu appears.
3. Select Antenna List > Open Table from the context menu. The Antenna Lists table appears.
4. Create a new antenna list in the row marked with the New Row icon ( ).
5. Click the Properties button. The New Antenna List Properties dialogue appears.
6. Select the antennas from the Antennas column to add to the antenna list in each new row.
7. Click OK to close the dialogue.
8. Click Close to close the Antenna Lists table.
You can also export an antenna list to an external file by clicking the Export button, or import an existing antenna list by
clicking the Import button in the New Antenna List Properties dialogue.
You can add antennas, or beams, from the antennas folder to an existing grid of beams or antenna list.
To add antennas to an antenna list:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Antennas folder.
3. Right-click the antenna that you want to add to an antenna list. The context menu appears.
4. Select Add the Antenna to a List from the context menu. The Antenna Addition in a List dialogue appears.
5. Select the antenna list to which you want to add the antenna from the Antenna List.
6. Click OK to add the antenna to the list.
You can also add all the antennas in the Antennas folder or a subfolder to an antenna list by selecting Antenna List >
Add Antennas to a List from the folders context menu.
You can import existing antenna lists to be used as grids of beams in Atoll.
To import an antenna list:
1. Click the Data tab in the Explorer window.
2. Right-click the Antennas folder. The context menu appears.
3. Select Antenna List > Import Antennas from a List from the context menu. The Open dialogue appears.
4. Select an Index file to import.
5. Click Open to import the antenna list to Atoll. The Import of antennas from a list dialogue appears.
6. Enter a name for the new antenna list.
7. Click OK to import the antenna list.
Atoll adds the antennas referred to in the index file to the Antennas folder, and adds the new antenna list to the
Antenna Lists table.
Atoll supports standard, Planet-like antenna list format for export and import. An index file contains the list of files contain-
ing the horizontal antenna patterns and a file containing the vertical antenna pattern.
The horizontal antenna pattern files have the following format:
DEGREEa Attenuation
Name of the antenna. "<ALL>" can be used to indicate that the vertical pattern is the
NAME
same for all the files containing the horizontal antenna patterns.
DEGREEa Attenuation
5. Click the Properties button. The smart antenna properties dialogue appears.
6. On the General tab of this dialogue, you can modify the Name, Smart Antenna Model, and Comments.
7. Under Smart Antenna Model, click the Parameters button. A dialogue opens with the parameters specific to the
selected smart antenna model.
If you selected Grid of Beams (GOB) as Smart Antenna Model, the Grid of Beams (GOB) Modelling dialogue
appears.
a. Select a DL grid of beams, the grid of beams to be used in downlink from the list of grid of beams listed in the
Antennas Lists table. For more information on creating grids of beams, see "Grid of Beams (GOB) Modelling"
on page 854.
b. Select a UL grid of beams, the grid of beams to be used in uplink. If you do not select a UL grid of beams,
Atoll uses the main antenna for uplink calculations.
c. Under Patterns, you can view the grid of beams separately or combined in the Grid of Beams Properties
dialogue.
i. Click the Separate button to display the antenna patterns of all the beams separately in the Grid of
Beams Properties dialogue.
ii. Click the Combined button to display the combined patterns of all the beams in the Grid of Beams Prop-
erties dialogue.
iii. Click OK to close the Grid of Beams Properties dialogue.
Notes:
If you opened the smart antenna properties dialogue by clicking the Browse ( ) button on
the Transmitter tab of a transmitters properties dialogue, these patterns will also include the
main antenna pattern, if any.
You can use the combined antenna pattern display to understand any inconsistencies in smart
antenna results. If the gird of beams and the main antenna do not have the same gains, the
smart antenna could provide worse results than the main antenna for traffic timeslots.
a. Select a Probability Threshold (%) used to read the CI gain graphs. For more information on the probability
threshold and CI gains, see "Statistical Modelling" on page 856.
b. Define a Spreading Angle () per column.
c. Click the Browse ( ) button corresponding to the CI Gain Graph for each column. The CI Gain Graph
dialogue appears. The CI Gain Graph provides the cumulative probability of each CI value.
d. Click OK to close the CI Gain Graph dialogue.
e. Click OK to close the Statistical Modelling dialogue.
If you selected Adaptive Beam as Smart Antenna Model, the Adaptive Beam Modelling dialogue appears:
a. Select a DL adaptive beam, the adaptive beam to be used in downlink from the list of adaptive beams listed
in the Antennas Lists table.
b. Select a UL adaptive beam, the adaptive beam to be used in uplink. If you do not select a UL adaptive beam,
Atoll uses the main antenna for uplink calculations.
c. Under Patterns, you can view the adaptive beam pattern separately or combined in the Adaptive Beam
Properties dialogue.
i. Click the Separate button to display the antenna patterns of all the beams separately in the Adaptive
Beam Properties dialogue.
ii. Click the Combined button to display the combined patterns of all the beams in the Adaptive Beam Prop-
erties dialogue.
iii. Click OK to close the Adaptive Beam Properties dialogue.
Notes:
If you opened the smart antenna properties dialogue by clicking the Browse ( ) button on
the Transmitter tab of a transmitters properties dialogue, these patterns will also include the
main antenna pattern, if any.
You can use the combined antenna pattern display to understand any inconsistencies in smart
antenna results. If the gird of beams and the main antenna do not have the same gains, the
smart antenna could provide worse results than the main antenna for traffic timeslots.
a. On the General tab, you can modify the name of the smart antenna model.
b. On the Properties tab, enter the Number of Elements in the smart antenna array and select a Single Element
Pattern to be used in downlink as well as uplink.
c. Click OK to close the Optimum Beamformer Properties dialogue.
If you selected Conventional Beamformer as the Smart Antenna Model, the Conventional Beamformer Prop-
erties dialogue appears:
a. On the General tab, you can modify the name of the smart antenna model.
b. On the Properties tab, enter the Number of Elements in the smart antenna array and select a Single Element
Pattern to be used in downlink as well as uplink.
c. Click OK to close the Conventional Beamformer Properties dialogue.
8. Click OK to close the smart antenna properties dialogue.
9. Click Close to close the Smart Antenna Equipment table.
Note: Properties of external third-party smart antenna models may vary. You can access their
properties from the Smart Antenna Models folder on the Modules tab of the Explorer
window.
Note: You can select whether the TCH thresholds you define are Eb/Nt or C/I thresholds by
selecting the corresponding option in the Global Parameters tab of the Transmitters
folders properties dialogue. For more information, see "The Global Transmitter
Parameters" on page 852.
Note: The maximum and minimum traffic channel powers can be either absolute values or
values relative to the pilot power; this depends on the option defined on the Global
Parameters tab of the Transmitters Properties dialogue. These values have to be
manually modified when the option is changed.
8. Under Resource Units, click the Browse button ( ) to the right of the timeslot field to access the Resource
Unit Consumption dialogue. In the Resource Unit Consumption dialogue, you can enter how many OVSF
codes of each length can be used for each timeslot. This information is used to carry out network dimensioning
and to simulate the Dynamic Channel Allocation (DCA) algorithm. For information on calculating network capacity,
see "TD-SCDMA Network Capacity" on page 816. For information on the dynamic channel allocation, see "The
Monte Carlo Simulation Algorithm" on page 829.
- DL: Enter or modify the number of downlink traffic timeslots for the service.
- UL: Enter or modify the number of uplink traffic timeslots for the service.
9. Click the Required Thresholds tab. On the Required Thresholds tab, you can define downlink and uplink EbNt or
CI requirements (in dB) and the TCH thresholds (in dBm). The EbNt, or CI, quality targets are used to determine
the coverage area for the service, and the TCH thresholds must be reached to provide users with the service.
These parameters depend on the mobility type and reception equipment; these parameters must be defined for
each possible combination of mobility type and reception equipment.
Using Transmission and Reception diversity results in a quality gain on received downlink and uplink EbNt or CI.
In Atoll, this is modelled by reducing the downlink and uplink EbNt or CI requirements. Therefore, in addition to
downlink and uplink EbNt or CI requirements, you can specify gains on received downlink and uplink EbNt or CI
for each possible diversity configuration. Atoll considers them when transmission and reception diversity config-
urations are assigned to transmitters.
4. In the Equipment table, each row describes a piece of equipment. For information on working with data tables,
see "Working with Data Tables" on page 50. For the new piece of TD-SCDMA equipment you are creating, enter
the following:
- Name: The name you enter will be the one used to identify this piece of equipment.
- Manufacturer: The name of the manufacturer of this piece of equipment.
- JD factor: Joint Detection (JD) is a technology used to decrease intra-cellular interference in the uplink. JD is
modelled by a coefficient from 0 to 1; this factor is considered in the UL interference calculation. In case JD is
not supported by equipment, enter 0 as value.
- MCJD factor: Multi-Cell Joint Detection (MCJD) is used to decrease uplink interference from mobiles in other
cells. MCJD is modelled by a coefficient from 0 to 1; this factor is considered in the UL interference calculation.
In case MCJD is not supported by equipment, enter 0 as value.
5. Click the Close button ( ) to close the table.
Note: You can create a new reception equipment type by entering a name in the row marked
with the New Row icon ( ) and pressing ENTER.
- You can define several pieces of reception equipment with separate thresholds for each. You can reserve low
bearer indexes for poor-performance reception equipment and higher bearer indexes for high-performance
equipment.
- You can specify bearer selection thresholds for each mobility. You can reserve low bearer indexes for high
speeds and higher bearer indexes for low speeds.
- You can also give priority to either one user by assigning him a high bearer index or to all users by assigning
them low bearer indexes.
8. Click OK to close the reception equipment types Properties dialogue.
- DL EbNt or CI: The DL EbNt or CI standard deviation. Atoll will display the DL EbNt or CI shadowing
margin.
- UL EbNt or CI: The UL EbNt or CI standard deviation. Atoll will display the UL EbNt or CI shadowing
margin
5. Click Calculate. The calculated shadowing margin is displayed.
6. Click Close to close the dialogue.
The maximum system range is half the distance that the RF signal can travel in DGP:
8
R System = 75 s 3 10 m/s- = 11250 m
----------------------------------------------------
2
Atoll
RF Planning and Optimisation Software
Chapter 13: WiMAX BWA Networks
Tip: Before working with the Atoll WiMAX module for the first time, it is highly recommended
to go through the "Glossary of WiMAX Terms" on page 995. This will help you get
accustomed to the terminology used in Atoll.
4. Allocate neighbours ( 4 ).
- "Planning Neighbours" on page 920.
5. Allocate frequencies ( 5 ).
- "Planning Frequencies" on page 929.
7. Before making more advanced coverage predictions, you need to define cell load conditions ( 7 ).
You can define cell load conditions in the following ways:
- You can generate realistic cell load conditions by creating a simulation based on traffic maps and subscriber
lists ( 7a , 7b , and 7c ) (see "Studying Network Capacity" on page 937).
- You can define cell load conditions manually either on the Cells tab of each transmitters Properties dialogue
or in the Cells table (see "Creating or Modifying a Cell" on page 875) ( 7d ).
8. Make WiMAX-specific signal quality coverage predictions using the defined cell load conditions ( 8 ).
- "WiMAX Coverage Predictions" on page 904.
9. If necessary, modify network parameters to study the network with a different frequency plan ( 10 ). After modifying
the networks frequency plan, you must perform steps 7 and 8 again.
6
7a
7c 7d
7b
7
9 10
Atoll enables you to model network traffic by allowing you to create services, users, user profiles, environments, and termi-
nals. This data can be then used to make studies that depend on network load, such as C/(I+N), WiMAX radio bearer, and
throughput coverage predictions.
In this section, the following are explained:
"Creating a WiMAX Base Station" on page 869.
"Creating a Group of Base Stations" on page 881.
"Modifying Sites and Transmitters Directly on the Map" on page 882.
"Display Tips for Base Stations" on page 882.
"Creating a Multi-Band WiMAX Network" on page 882.
"Setting the Working Area of an Atoll Document" on page 882.
"Studying a Single Base Station" on page 883.
"Studying Base Stations" on page 886.
"Planning Neighbours" on page 920.
"Planning Frequencies" on page 929.
"Planning Preamble Indexes" on page 933.
Tip: While this method allows you to place a site with precision, you can also place sites using
the mouse and then position them precisely with this dialogue afterwards. For information
on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 31.
- Altitude: The altitude, as defined by the DTM for the location specified under Position, is given here. You can
specify the actual altitude under Real, if you wish. If an altitude is specified here, Atoll will use this value for
calculations.
- Comments: You can enter comments in this field if you wish.
- Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are dis-
played in red in the Transmitters folder of the Data tab.
Note: Only active transmitters are taken into consideration during calculations.
- Transmitter Type: If you want Atoll to consider the transmitter as a potential server as well as an interferer,
set the transmitter type to Intra-Network (Server and Interferer). If you want Atoll to consider the transmitter
only as an interferer, set the type to Extra-Network (Interferer Only). No coverage for an Interferer Only
transmitter will be calculated for coverage predictions and it will not serve any mobile in Monte Carlo simula-
tions.
This feature enables you to model the co-existence of different networks in the same geographic area. For
more information on how to study interference between co-existing networks, see "Modelling the Co-existence
of Networks" on page 995.
- Transmission/Reception: Under Transmission/Reception, you can see the total losses and the noise
figure of the transmitter. Atoll calculates losses and noise according to the characteristics of the equipment
assigned to the transmitter. Equipment can be assigned using the Equipment Specifications dialogue which
appears when you click the Equipment button.
- On the Equipment Specifications dialogue (see Figure 13.4), the equipment you select and the gains and
losses you define are used to initialise total transmitter losses in the uplink and downlink:
- TMA: You can select a tower-mounted amplifier (TMA) from the list. You can click the Browse button
( ) to access the properties of the TMA. For information on creating a TMA, see "Defining TMA Equip-
ment" on page 147.
- Feeder: You can select a feeder cable from the list. You can click the Browse button ( ) to access the
properties of the feeder. For information on creating a feeder cable, see "Defining Feeder Cables" on
page 147.
- BTS: You can select a base transceiver station (BTS) equipment from the BTS list. You can click the
Browse button ( ) to access the properties of the BTS. For information on creating a BTS, see "Defin-
ing BTS Equipment" on page 148.
- Feeder Length: You can enter the feeder length at transmission and reception.
- Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value
you enter must be positive.
- Receiver Antenna Diversity Gain: You can enter a receiver antenna diversity gain. The value you enter
must be positive.
Atoll always considers the values in the Real boxes in coverage predictions even if they are different from the
values in the Computed boxes. The information in the real Total Noise Figure reception box is calculated
from the information you entered in the Equipment Specifications dialogue. You can modify the real Total
Losses at transmission and reception and the real Total Noise Figure at reception if you wish. Any value you
enter must be positive.
- Antennas:
- Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added
to the altitude of the site as given by the DTM. If the transmitter is situated on a building, the height entered
must include the height of building.
- Power Combining Gain: The Power Combining Gain is calculated automatically depending on the
number of antenna elements of the smart antenna equipment, if any, assigned to the transmitter. This gain
is applied to the downlink transmission power for preamble and other signals transmitted using the main
antenna.
- Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the
Browse button ( ) to access the properties of the antenna. The other fields, Azimuth, Mechanical
Downtilt, and Additional Electrical Downtilt, display additional antenna parameters. The mechanical
and additional electrical downtilts defined for the main antenna are also used for the calculations using the
smart antenna equipment.
- Smart Antenna: Under Smart Antenna, the available smart antenna equipment is available in the Equip-
ment list. You can click the Browse button ( ) to access the properties of the smart antenna equip-
ment. When you select a smart antenna equipment, you can choose whether to keep the current main
antenna model or to replace it with the main antenna model defined for the selected smart antenna equip-
ment, if any. For more information on smart antenna equipment, see "Defining Smart Antenna Equipment"
on page 983.
- Number of MIMO Antennas: Enter the number of antennas used for MIMO in the Transmission and
Reception fields. For more information on how the number of MIMO antennas are used, see "Multiple
Input Multiple Output Systems" on page 984.
- Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power, which is
the percentage of power reserved for this particular antenna. For example, for a transmitter with one
secondary antenna, if you reserve 40 % of the total power for the secondary antenna, 60 % is available
for the main antenna.
For information on working with data tables, see "Working with Data Tables" on page 50.
The main antenna is used to transmit the preamble. Coverage predictions based on the preamble signal are
performed using the main antenna. The main antenna is also used for traffic signals if there is no smart antenna
equipment selected for the transmitter, or if the cell (or permutation zones in WiMAX 802.16e) does not support
AAS.
If there is smart antenna equipment assigned to the transmitter and the cell (or permutation zones in WiMAX
802.16e) supports AAS, traffic data is transmitted and received using the smart antenna, whereas the preamble
is transmitted using the main antenna.
When you create a transmitter, Atoll reminds you to create a cell for the transmitter. The following explains the parameters
of a WiMAX cell. As you create a cell, Atoll calculates appropriate values for some fields based on the information you
have entered. You can, if you wish, modify these values.
The properties of a WiMAX cell are found on Cells tab of the Properties dialogue of the transmitter to which it is assigned.
The Cells tab has the following options:
Name: By default, Atoll names the cell after its transmitter, adding a suffix in parentheses. If you change trans-
mitter name, Atoll does not update the cell name. You can enter a name for the cell, but for the sake of consist-
ency, it is better to let Atoll assign a name. If you want to change the way Atoll names cells, see The Administrator
Manual.
BSID: The Base Station ID.
Active: If this cell is to be active, you must select the Active check box.
Order: The order of the cell among all the cells of the transmitter. It must be a positive integer value. This value is
automatically assigned when you create a new cell, but it is possible to modify it afterwards. The order is used
during calculations for selecting the service cell. For more information on the different cell selection options, see
"The Global Transmitter Parameters" on page 972.
Frequency Band: The cells frequency band from the Frequency Band list.
Channel Number: The number of the channel from the list of available channels.
Channel Allocation Status: The status of the current channel allocated to the cell:
- Not Allocated: The current channel has neither been allocated automatically nor manually. The AFP con-
siders that a Not Allocated channel is modifiable.
- Allocated: The current channel has been allocated automatically or manually. The AFP considers that an
Allocated preamble index is modifiable but it is not modified unless absolutely necessary.
- Locked: The current channel has been allocated automatically or manually. The AFP considers that a Locked
channel is not modifiable.
Min Reuse Distance: The minimum reuse distance after which the channel assigned to this cell can be assigned
to another cell by the AFP. The reuse distance is also used by the automatic preamble index allocation in 802.16e.
The cells preamble index can be allocated to another cell outside this reuse distance without any cost.
Preamble Power (dBm): The cells transmission power over the preamble of the frame.
Traffic Power Reduction (dB): The power reduction to be subtracted from the power defined in the Preamble
Power (dBm) field to determine the transmission power of the traffic subcarriers during the loaded part of the
frame. Traffic subcarriers are off during the empty part of the frame.
Pilot Power Reduction (dB): The power reduction to be subtracted from the power defined in the Preamble
Power (dBm) field to determine the transmission power of the pilot subcarriers during the loaded part of the frame.
Idle Pilot Power Reduction (dB): The power reduction to be subtracted from the power defined in the Preamble
Power (dBm) field to determine the transmission power of the pilot subcarriers during the empty part of the frame.
If the cells transmitter has a smart antenna equipment assigned, the transmission power of cell increases by
10 Log ( n ) (in dB), where n is the number of antenna elements of the smart antenna. This gain in the transmis-
sion power is referred to as the power combination gain.
WiMAX Equipment: You can select the cells WiMAX equipment from the WiMAX Equipment list. For more infor-
mation, see "Defining WiMAX Equipment" on page 978. The cells WiMAX equipment parameters are used in the
uplink calculations.
Scheduler: The scheduler used by the cell for resource allocation during Monte Carlo simulations. You can select
the scheduler from the list of schedulers available in the Schedulers table. For more information see "Defining
WiMAX Schedulers" on page 980.
Max Number of Users: The maximum number of simultaneous users supported by the cell.
Preamble C/N Threshold (dB): The minimum preamble C/N required for a user to be connected to the cell. The
preamble C/N is compared with this threshold to determine whether or not a user can be connected to a cell.
AMS/MU-MIMO Threshold (dB): For AMS, it is the preamble C/N threshold for switching from SU-MIMO to STTD/
MRC as the preamble signal conditions get worse than the given value. For MU-MIMO, it is the minimum required
preamble CNR for using MU-MIMO. For more information on Adaptive MIMO switching, see "Multiple Input Mul-
tiple Output Systems" on page 984.
Max Traffic Load (UL) (%): The uplink traffic load not to be exceeded. This limit can be taken into account during
Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have an uplink
traffic load greater than this maximum.
Traffic Load (UL) (%): The uplink traffic load percentage. By default, the uplink traffic load is set to 100%.
Max Traffic Load (DL) (%): The downlink traffic load not to be exceeded. This limit can be taken into account
during Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have a
downlink traffic load greater than this maximum.
Traffic Load (DL) (%): The downlink traffic load percentage. By default, the downlink traffic load is set to 100%.
UL Noise Rise (dB): The uplink noise rise in dB. By default, the uplink noise rise is set to 0.
Note: You can set the values for uplink and downlink traffic loads, and the uplink noise rise
manually to actual network values, or use the values computed during Monte Carlo
simulations. Monte Carlo simulation results can be stored in the cells by clicking the
Commit Results button in the simulation results dialogue.
AAS Usage (DL) (%): This is the percentage of the total downlink traffic load that corresponds to the traffic loads
of the users supported by the smart antenna equipment. For example, if the downlink traffic load is 80%, and you
set the AAS usage to 50%, it means that 40% downlink traffic load is supported by the smart antenna equipment
while the other 40% is supported by the main antenna. AAS usage is calculated during Monte Carlo simulations,
and cannot be modified manually because the AAS usage values correspond to the AAS simulation results dia-
grams.
AAS Simulation Results: This field stores the simulation results generated for transmitters using a smart
antenna. During the Monte Carlo simulations, both smart antenna models available in Atoll, conventional beam-
former and optimum beamformer, perform beamforming in downlink. In uplink, the conventional beamformer per-
forms beamforming only whereas the optimum beamformer uses the MMSE (Minimum Mean Square Error)
algorithm for cancelling interference. After the simulations, the smart antenna results can be stored in the cell prop-
erties. The results stored in this field are the angular distributions of the downlink traffic power spectral density and
the uplink noise rise. You can view these patterns in the Cells table. You can make the display of the downlink
results diagram take into account the effect of the antenna pattern of the single element. For more information,
see the Administrator Manual.
MU-MIMO Gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO. This can be user-defined
or an output of Monte Carlo simulations. In uplink throughput coverage predictions, the cell capacity will be multi-
plied by this gain at pixels where MU-MIMO is used.
The following parameters are only available in WiMAX 802.16d documents.
Diversity Support (DL): The type of antenna diversity technique (AAS, STTD/MRC, SU-MIMO, and AMS) sup-
ported by the cell in downlink. You cannot select more than one type of MIMO technique (STTD/MRC, SU-MIMO,
and AMS) at a time.
Diversity Support (UL): The type of antenna diversity technique (AAS, STTD/MRC, SU-MIMO, AMS, MU-MIMO)
supported by the cell in uplink. You cannot select more than one type of MIMO technique (STTD/MRC, SU-MIMO,
MU-MIMO, and AMS) at a time.
Specific calculations will be performed (gains will be applied) for terminals supporting AAS and MIMO. A cell that
only supports None does not have any antenna diversity mechanism, and all the terminal types can connect to
this cell. A cell that supports None and one or more antenna diversity techniques can also support terminals capa-
ble of those diversity techniques. For example, None+AAS can support simple as well as AAS-capable terminals,
and None+AMS can support simple and MIMO-capable terminals. Simple terminals cannot connect to a cell that
does not support None.
Max Number of Intra-technology Neighbours: The maximum number of neighbours from within the same Atoll
document that the cell can have.
Max Number of Inter-technology Neighbours: The maximum number of neighbours from other technology doc-
uments that the cell can have.
Neighbours: You can access a dialogue in which you can set both intra-technology and inter-technology neigh-
bours by clicking the Browse button ( ). For information on defining neighbours, see "Planning Neighbours"
on page 920.
Tip: The Browse button ( ) might not be visible in the Neighbours box if this is a new cell.
You can make the Browse button appear by clicking Apply.
Tips:
If you are creating several transmitters at the same time, or modifying several existing trans-
mitters, you can do it more quickly by editing or pasting the data directly in the Transmitters
table. You can open the Transmitters table by right-clicking the Transmitters folder on the
Data tab of the Explorer window and selecting Open Table from the context menu. For infor-
mation on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
If you want to add a transmitter to an existing site on the map, you can add the transmitter by
right-clicking the site and selecting New Transmitter from the context menu.
Tips:
If you are creating or modifying several cells at the same time, you can do it more quickly by
editing the data directly in the Cells table. You can open the Cells table by right-clicking the
Transmitters folder on the Data tab of the Explorer window and selecting Cells > Open
Table from the context menu. You can either edit the data in the table, paste data into the table
(see "Copying and Pasting in Tables" on page 56), or import data into the table (see "Importing
Tables from Text Files" on page 59).
If you want to add a cell to an existing transmitter on the map, you can add the cell by right-
clicking the transmitter and selecting New Cell from the context menu.
3. In the map window, move the pointer over the map to where you would like to
place the new station. The exact coordinates of the pointers current location
are visible in the Status bar.
Tips:
To place the base station more accurately, you can zoom in on the map before you click the
New Station button. For information on using the zooming tools, see "Changing the Map
Scale" on page 38.
If you let the pointer rest over the base station you have placed, Atoll displays its tip text with
its exact coordinates, allowing you to verify that the location is correct.
You can also place a series of base stations using a station template. You do this by defining an area on the map where
you want to place the base stations. Atoll calculates the placement of each base station according to the defined hexag-
onal cell radius in the station template. For information on defining the cell radius, see "Creating or Modifying a Station
Template" on page 877.
2. Click the Hexagonal Design button ( ), to the left of the template list. A hexagonal design is a group of base
stations created from the same station template.
Note: If the Hexagonal Design button is not available ( ), the hexagonal cell radius for this
template is not defined. For information on defining the cell radius, see "Creating or
Modifying a Station Template" on page 877.
3. Draw a zone delimiting the area where you want to place the series of base stations:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
Atoll fills the delimited zone with new base stations and their hexagonal shapes. Base station objects such as
sites and transmitters are also created and placed into their respective folders.
You can work with the sites and transmitters in these base stations as you work with any base station object, adding, for
example, another antenna to a transmitter.
When you place a new station using a station template as explained in "Placing a New Base Station Using a Station
Template" on page 876, the site is created at the same time as the station. However, you can also place a new station on
an existing site.
To place a base station on an existing site:
1. On the Data tab, clear the display check box beside the Hexagonal Design folder.
2. In the Radio toolbar, select a template from the list.
to offer complete coverage of the area, the Mechanical Downtilt, and the Additional Electrical Downtilt for
the antennas.
Under Smart Antenna, you can select the smart antenna Equipment used by the transmitter, and under
Number of MIMO Antennas, you can enter the number of antennas used for Transmission and for Recep-
tion for MIMO.
- Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both
the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Managing
Calculations in Atoll.
5. Click the Transmitter tab. In this tab (see Figure 13.7), if the Active check box is selected, you can modify the
following:
- Under Transmission/Reception, you can click the Equipment button to open the Equipment Specifica-
tions dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or base transceiver station
(BTS). For information on the Equipment Specifications dialogue, see "Transmitter Description" on
page 870.
The information in the computed Total Losses in transmission and reception boxes is calculated from the in-
formation you entered in the Equipment Specifications dialogue (see Figure 13.4 on page 872). Atoll al-
ways considers the values in the Real boxes in coverage predictions even if they are different from the values
in the Computed boxes. You can modify the real Total Losses at transmission and reception if you wish. Any
value you enter must be positive.
The information in the computed BTS Noise Figure reception box is calculated from the information you en-
tered in the Equipment Specifications dialogue. You can modify the real BTS Noise Figure at reception if
you wish. Any value you enter must be positive.
6. Click the WiMAX tab. In this tab (see Figure 13.8), you can modify the following:
- Under Powers, you can modify the Preamble Power, and the power reductions for the data and pilot subcar-
riers in Traffic Power Reduction, Pilot Power Reduction, and Idle Pilot Power Reduction.
- Frequency Band, Channel Number, Channel Allocation Status, Preamble Index (WiMAX 802.16e), Pre-
amble Index Status (WiMAX 802.16e), Min Reuse Distance, WiMAX Equipment, Scheduler, Max Number
of Users, Frame Configuration (WiMAX 802.16e), Preamble C/N Threshold, AMS/MU-MIMO Threshold
(WiMAX 802.16e), and the default MU-MIMO Gain (WiMAX 802.16e).
- Under Antenna Diversity in WiMAX 802.16d documents, you can select the Diversity Support in downlink
and in uplink. You cannot select more than one type of MIMO technique (STTD/MRC, SU-MIMO, MU-MIMO,
and AMS) at a time. You can also enter the AMS/MU-MIMO Threshold and the default MU-MIMO Gain.
- Under Default Loads, you can enter the default values for DL Traffic Load, UL Traffic Load, UL Noise Rise,
and the Max DL Traffic Load and Max UL Traffic Load. You can also enter the DL Segmentation Usage in
WiMAX 802.16e.
- Under Inter-technology Interference, you can set the DL Noise Rise and the UL Noise Rise. For more infor-
mation on inter-technology interference, see "Modelling Inter-Network Interferences" on page 236.
- Under Max Number of Neighbours in WiMAX 802.16e documents, you can set the maximum numbers of
Intra-technology and Inter-technology neighbours.
Figure 13.8: Station Template Properties dialogue WiMAX tab (WiMAX 802.16e)
7. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the
Sites table, or if you have defined an additional field in the Station Template Properties dialogue.
8. When you have finished setting the parameters for the station template, click OK to close the dialogue and save
your changes.
5. In the map window, move the pointer over the map to where you would like to place the new base station. The
exact coordinates of the pointers current location are visible in the Status bar.
Tips:
To place the station more accurately, you can zoom in on the map before you select Duplicate
from the context menu. For information on using the zooming tools, see "Changing the Map
Scale" on page 38.
If you let the pointer rest over the station you have placed, Atoll displays tip text with its exact
coordinates, allowing you to verify that the location is correct.
You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to
place each duplicate station.
For more information on the site, transmitter, and cell properties, see "Definition of a Base Station" on page 869.
Note: When you import data into your current Atoll document, the coordinate system of the
imported data must be the same as the display coordinate system used in the document.
If you cannot change the coordinate system of your source data, you can temporarily
change the display coordinate system of the Atoll document to match the source data.
For information on changing the coordinate system, see "Setting a Coordinate System"
on page 92.
Important: The table you copy from must have the same column layout as the table you are pasting
data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
Importing data: If you have base station data in text or comma-separated value (CSV) format, you can import it
into the tables in the current document. If the data is in another Atoll document, you can first export it in text or
CSV format and then import it into the tables of your current Atoll document. When you are importing, Atoll allows
you to select what values you import into which columns of the table.
When you create a group of base stations by importing data, you must import site data in the Sites table, trans-
mitter data in the Transmitters table, and cell data in the Cells table, in that order.
For information on exporting table data, see "Exporting Tables to Text Files" on page 58. For information on
importing table data, see "Importing Tables from Text Files" on page 59.
Note: You can quickly create a series of base stations for study purposes using the Hexagonal
Design tool on the Radio toolbar. For information, see "Placing a New Base Station
Using a Station Template" on page 876.
( and ). For information on defining the transmitter symbol, see "Defining the Display Type" on page 34.
It is important not to confuse the computation zone and the focus zone or hot spot zones. The computation zone
defines the area where Atoll computes path loss matrices, coverage predictions, Monte Carlo simulations, etc.,
while the focus zone or hot spot zones are the areas taken into consideration when generating reports and results.
For information on the computation zone, see "Creating a Computation Zone" on page 891.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be
studied.
2. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the fol-
lowing:
- Move the receiver to change the current position.
- Click to place the receiver at the current position. You can move the receiver again by clicking it a second time.
- Right-click the receiver to choose one of the following commands from the context menu:
- Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates.
- Target Site: Select a site from the list to place the receiver directly on a site.
4. Click the Profile tab.
The profile analysis appears in the Profile tab of the Point Analysis Tool window. The altitude is reported on the
vertical axis and the receiver-transmitter distance on the horizontal axis. A blue ellipsoid indicates the Fresnel zone
between the transmitter and the receiver, with a green line indicating the line of sight (LOS). Atoll displays the
angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an obstacle, this
causes attenuation with diffraction displayed by a red vertical line (if the propagation model used takes diffraction
mechanisms into account). The main peak is the one that intersects the most with the Fresnel ellipsoid. With some
propagation models using a 3 knife-edge Deygout diffraction method, the results may display two additional atten-
uations peaks. The total attenuation is displayed above the main peak.
The results of the analysis are displayed at the top of the Profile tab:
- The received signal strength from the selected transmitter for the cell with the highest preamble power
6. To end the point analysis, click the Point Analysis Tool ( ) in the Radio toolbar again.
Note: You can use the same procedure to study the signal level coverage of several base
stations by grouping the transmitters. For information on grouping transmitters, see
"Grouping Data Objects by a Selected Property" on page 65.
Tip: If you wish to study only sites by their status, at this step you could group them by status.
5. Select Coverage by Signal Level and click OK. A study properties dialogue appears.
6. You can configure the following parameters in the Properties dialogue:
- General tab: You can change the assigned Name of the coverage prediction, the Resolution, and the storage
Folder for the coverage prediction, and add some Comments. The resolution you set is the display resolution,
not the calculation resolution.
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:
City Centre 5m
City 20 m
County 50 m
State 100 m
Note: If you create a new coverage prediction from the context menu of either the Transmitters
or Predictions folder, you can select the sites using the Group By, Sort, and Filter
buttons under Configuration. Because you already selected the target sites, however,
only the Filter button is available.
- Condition tab: The coverage prediction parameters on the Condition tab allow you to define the signals that
will be considered for each pixel (see Figure 13.11).
- At the top of the Condition tab, you can set the signal level range to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the
same results because Atoll displays the results of the best server in either case. Selecting "Best Signal
Level" necessitates, however, a longer time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that
Atoll will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage
Probability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- Display tab: You can modify how the results of the coverage prediction will be displayed.
- Under Display Type, select "Value Intervals."
- Under Field, select "Best signal level."
- You can change the value intervals and their displayed colour. For information on changing display prop-
erties, see "Display Properties of Objects" on page 33.
- You can create a tooltip with information about the coverage prediction by clicking the Browse button
( ) beside the Tip Text box and selecting the fields you want to display in the tooltip.
- You can select the Add to Legend check box to add the displayed value intervals to the legend.
Note: If you change the display properties of a coverage prediction after you have calculated it,
you may make the coverage prediction invalid. You will then have to recalculate the
coverage prediction to obtain valid results.
7. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The signal level
coverage prediction can be found in the Predictions folder on the Data tab. Atoll automatically locks the results of a cover-
age prediction as soon as it is calculated, as indicated by the icon ( ) beside the coverage prediction in the Predictions
folder. When you click the Calculate button ( ), Atoll only calculates unlocked coverage predictions ( ).
Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices
using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main prop-
agation model with a shorter radius (displayed with a blue square in Figure 13.12) and a higher resolution and an extended
propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate
higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower reso-
lution path loss matrices outside the area covered by the main propagation model.
In this section, the following are explained:
"Path Loss Matrices" on page 887.
"Assigning a Propagation Model" on page 889.
"The Calculation Process" on page 891.
"Creating a Computation Zone" on page 891.
"Setting Transmitters or Cells as Active" on page 891.
"Signal Level Coverage Predictions" on page 892.
"Analysing a Coverage Prediction" on page 896.
"WiMAX Coverage Predictions" on page 904.
"Printing and Exporting Coverage Prediction Results" on page 920.
Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matri-
ces in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning
projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case
of large radio-planning projects, saving your path loss matrices externally will help reduce the size of the file and the use
of computer resources.
The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same
radio-planning project. In this case, the radio data is stored in a database and the path loss matrices are read-only and are
stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices,
the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These
will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more
information on working in a multi-user environment, see the Administrator Manual.
When you save the path loss matrices to an external directory, Atoll creates:
One file per transmitter with the extension LOS for its main path loss matrix.
A DBF file with validity information for all the main matrices.
A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
To set the storage location of the path loss matrices:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss
matrices and the location for the shared path loss matrices:
- Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are
loading path loss matrices from a shared location, where you store your changes to shared path loss matrices.
Click the button beside the Private Directory ( ) and select Embedded to save the path loss matrices in
the Atoll document, or Browse to select a directory where Atoll can save the path loss matrices externally.
Note: Path loss matrices you calculate locally are not stored in the same directory as shared
path loss matrices. Shared path loss matrices are stored in a read-only directory. In other
words, you can read the information from the shared path loss matrices but any changes
you make will be stored locally, either embedded in the ATL file or in a private external
folder, depending on what you have selected in Private Directory.
Caution: When you save the path loss files externally, the external files are updated as soon as
calculations are performed. In order to keep consistency between the Atoll document and
the stored calculations, you should save the Atoll document before closing it if you have
updated the path loss matrices.
- Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a
database and the path loss matrices are stored in a directory that is accessible to all users. Any changes you
make will not be saved to this directory; they will be saved in the location indicated in Private Directory. The
path loss matrices in the shared directory are updated by a user with administrator rights based on the updated
information in the database. For more information on shared directories, see the Administrator Manual.
5. Click OK.
Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want,
you can check whether the path loss matrices are valid without creating a coverage prediction.
To check whether the path loss matrices are valid:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. You have the
following display options:
- Display all the matrices: All path loss matrices are displayed.
- Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available Results table lists the following information for each displayed path loss matrix:
2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation
Model to All Transmitters" on page 889, this is the propagation model that will be used for all transmitters, except
for those to which you have assigned a propagation model either individually or as part of a group.
Important: When you assign a propagation model globally, you override any selection you might
have made to an individual transmitter or to a group of transmitters.
3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default
Propagation Model" on page 187, this is the propagation model that will be used for all transmitters whose main
propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main prop-
agation model, that is the propagation model that will be used.
In this section, the following are explained:
"Assigning a Propagation Model to All Transmitters" on page 889.
"Assigning a Propagation Model to a Group of Transmitters" on page 890.
"Assigning a Propagation Model to One Transmitter" on page 890.
For more information about the available propagation models, see Chapter 5: Managing Calculations in Atoll.
Transmitters that share the same parameters and environment will usually use the same propagation model and settings.
In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common
parameters and then assigning the propagation model.
To define a main and extended propagation model for a defined group of transmitters:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select from the Group by submenu of the context menu the property by which you want to group the transmitters.
The objects in the folder are grouped by that property.
Note: You can group transmitters by several properties by using the Group By button on the
Properties dialogue. For more information, see "Advanced Grouping" on page 66.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model
to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmit-
ters.
When you assign a main and extended propagation model to a single transmitter, it overrides any changes you have previ-
ously made globally.
To define a main and extended propagation model for all transmitters:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Transmitters folder.
3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu
appears.
4. Select Properties from the context menu. The Properties dialogue appears.
5. Click the Propagation tab.
6. Under Main Matrix:
- Select a Propagation Model.
- Enter a Radius and Resolution.
7. If desired, under Extended Matrix:
- Select a Propagation Model.
- Enter a Radius and Resolution.
8. Click OK. The selected propagation models will be used for the selected transmitter.
Note: You can also define the propagation models for a transmitter by right-clicking it in the map
window and selecting Properties from the context menu.
Notes:
You can stop any calculations in progress by clicking the Stop Calculations button ( ) in
the toolbar.
When you click the Force Calculation button ( ) instead of the Calculate button, Atoll cal-
culates all path loss matrices, unlocked coverages, and pending simulations.
You can also create a computation zone with one of the following methods:
Existing polygon: You can use any existing polygon on the map as a computation zone by right-clicking it and
selecting Use as Computation Zone from the context menu.
Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a computation zone. You can import it by right-clicking the Computa-
tion Zone folder on the Geo tab and selecting Import from the context menu.
Fit to Map Window: You can create a computation zone the size of the map window by right-clicking the Com-
putation Zone folder on the Geo tab and selecting Fit to Map Window from the context menu.
Note: You can save the computation zone in the user configuration. For information on
exporting the computation zone in the user configuration, see "Exporting a User
Configuration" on page 75.
You can set an individual transmitter as active from its context menu or you can set more than one transmitter as active
by activating them from the Transmitters context menu, by activating the transmitters cells from the Cells table, or by
selecting the transmitters with a zone and activating them from the zones context menu.
To set an individual transmitter as active:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the Transmitters folder.
3. Right-click the transmitter you want to activate. The context menu appears.
4. Select Active Transmitter from the context menu. The transmitter is now active.
To set more than one transmitter as active using the Transmitters context menu:
1. Click the Data tab of the Explorer window.
2. Select the transmitters you want to set as active:
- To set all transmitters as active, right-click the Transmitters folder. The context menu appears.
- To set a group of transmitters as active, click the Expand button ( ) to expand the Transmitters folder and
right-click the group of transmitters you want to set as active. The context menu appears.
3. Select Activate Transmitters from the context menu. The selected transmitters are set as active.
To set more than one transmitter as active using the Transmitters table:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Open Table. The Transmitters table appears with each transmitters parameters in a row.
4. For each transmitter that you want to set as active, select the check box in the Active column.
To set more than one cell as active using the Cells table:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Open Table. The Cells table appears with each cells parameters in a row.
4. For each cell that you want to set as active, select the check box in the Active column.
To set transmitters as active using a zone:
1. Click the Geo tab of the Explorer window.
2. Click the Expand button ( ) to the left of Zones folder to expand the folder.
3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears.
Note: If you do not yet have a zone containing the transmitters you want to set as active, you
can draw a zone as explained in "Using Zones in the Map Window" on page 41.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active.
Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on
choosing and configuring a propagation model, see Chapter 5: Managing Calculations in Atoll.
Calculating path loss matrices can be time and resource intensive when you are working on larger projects. Consequently,
Atoll offers you the possibility of distributing path loss calculations on several computers. You can install the distributed
calculation server application on other workstations or on servers. Once the distributed calculation server application is
installed on a workstation or server, the computer is available for distributed path loss calculation to other computers on
the network. For information on setting up the distributed calculation server application, see the Administrator Manual.
6. Click the Condition tab (see Figure 13.14). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same
results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level"
necessitates, however, the longest time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll
will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 13.15).
6. Click the Condition tab (see Figure 13.16). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same
results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level"
necessitates, however, the longest time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll
will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 13.17).
6. Click the Condition tab (see Figure 13.18). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same
results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level"
necessitates, however, the longest time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll
will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 13.19).
1. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
2. At the bottom of the Point Analysis Tool window, click the Reception tab (see Figure 13.21).
The predicted signal level from different transmitters is reported in the Reception tab in the form of a bar chart,
from the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the
colour of the transmitter it represents. For a transmitter with more than one cell, the signal level is calculated for
the cell with the highest preamble power.
In the Map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they
represent. A thick black line from the pointer to its best server is also displayed in the map window. The best server
of the pointer is the transmitter from which the pointer receives the highest signal level. If you let the pointer rest,
the signal level received from the corresponding transmitter at the pointer location is displayed in the tool-tip.
3. Right-click the Reception tab and select Properties from the context menu. The Analysis Properties dialogue
appears.
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and
select "From Model" from the Shadowing Margin list.
- Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class.
4. To end the point analysis, click the Point Analysis Tool ( ) in the Radio toolbar again.
13.2.8.7.4 Creating a Focus or Hot Spot Zone for a Coverage Prediction Report
The focus and hot spot zones define the area on which statistics can be drawn and on which reports are made. While you
can only have one focus zone, you can define several hot spot zones in addition to the focus zone.
It is important not to confuse the computation zone and the focus and hot spot zones. The computation zone defines the
area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo simulations, etc., while the focus and
hot spot zones are the areas taken into consideration when generating reports and results. When you create a coverage
prediction report, it gives the results for the focus zone and for each of the defined hot spot zones.
To define a focus zone or hot spot zone:
1. Click the Geo tab in the Explorer window.
2. Click the Expand button ( ) to expand the Zones folder.
3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or
a hot spot. The context menu appears.
4. Select Draw from the context menu.
5. Draw the focus or hot spot zone:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zones
visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but
will still be taken into account.
You can also create a focus or hot spot zone as follows:
Existing polygon: You can use any existing polygon on the map as a focus zone by right-clicking it and selecting
Use as Focus Zone from the context menu.
Note: You can only create a focus zone, and not a hot spot zone, from an existing polygon.
Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus
Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot
spot zones, you can import the name given to each zone as well.
Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map
Window from the context menu.
Notes: You can save the focus or hot spot zones so that you can use them in a different Atoll
document:
- You can save the focus zone in the user configuration. For information on exporting the
focus zone in the user configuration, see "Exporting a User Configuration" on page 75.
- You can right-click the Focus Zone folder or the Hot Spot Zones folder on the Data
tab of the Explorer window and select Export from the context menu.
You can include population statistics in the focus or hot spot zone by importing a
population map. For information on importing maps, see "Importing a Raster-format Geo
Data File" on page 107.
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
a. Under Configuration, click the Import button. The Open dialogue appears.
b. Select the configuration you want to import and click Open. The imported report configuration is applied
6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed
dialogue. The coverage prediction report table appears. The report is based on the hot spot zones and on the
focus zone if available or on the hot spot zones and computation zone if there is no focus zone.
To display a report on all coverage predictions:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears.
4. Define the format and content of the report:
You can select the columns that will be displayed in the report and define the order they are in:
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
Atoll saves the names of the columns you select and will automatically select them the next time you create a
coverage prediction report.
5. Click OK.
If you have created a custom data map with integrable data, the data can be used in prediction reports. The data will be
summed over the coverage area for each item in the report (for example, by transmitter or threshold). The data can be
value data (revenue, number of customers, etc.) or density data (revenue/km, number of customers/km, etc.). Data is
considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example,
socio-demographic classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable
Versus Non Integrable Data" on page 124.
In this section, there are two examples to explain how you can compare two similar predictions. You can display the results
of the comparison study coverage in one of the following ways:
Intersection: This display shows the area where both coverage predictions overlap (for example, pixels covered
by both coverage predictions are displayed in red).
Union: This display shows all pixels covered by both coverage predictions in one colour and pixels covered by
only one coverage prediction in a different colour (for example, pixels covered by both predictions are red and
pixels covered by only one prediction are blue).
Difference: This display shows all pixels covered by both coverage predictions in one colour, pixels covered by
only the first prediction with another colour and pixels covered only by the second prediction with a third colour (for
example, pixels covered by both predictions are red, pixels covered only by the first prediction only are green, and
pixels covered only by the second prediction are blue).
To compare two similar coverage predictions:
1. Create and calculate a coverage prediction of the existing network.
2. Examine the coverage prediction to see where coverage can be improved.
3. Make the changes to the network to improve coverage.
4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged).
5. Calculate the duplicate coverage prediction.
6. Compare the original coverage prediction with the new coverage prediction. Atoll displays differences in coverage
between them.
In this section, the following examples are explained:
"Example 1: Studying the Effect of a New Base Station" on page 901
"Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 903.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how you can verify if a newly added base station improves coverage.
A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal
Level" on page 893. The results are displayed in Figure 13.23. An area with poor coverage is visible on the right side of
the figure.
A new base station is added, either by creating the base station and adding the transmitters, as explained in "Creating a
WiMAX Base Station" on page 869, or by placing a station template, as explained in "Placing a New Base Station Using
a Station Template" on page 876. Once the new site has been added, the original coverage prediction can be recalculated,
but then it would be impossible to compare the results. Instead, the original signal level coverage prediction can be copied
by selecting Duplicate from its context menu. The copy is then calculated to show the effect of the new base station (see
Figure 13.24).
Figure 13.24: Signal level coverage prediction of network with new base station
4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes adding a new base station made, you should choose Difference.
5. Click OK to create the comparison. The comparison in Figure 13.25, shows clearly the area covered only by the
new base station.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how modifying transmitter tilt can improve coverage.
A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by
Transmitter" on page 894. The results are displayed in Figure 13.26. The coverage prediction shows that one transmitter
is covering its area poorly. The area is indicated with a red oval in the figure.
You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed
by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and
electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue.
Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it would be
impossible to compare the results. Instead, the original coverage prediction can be copied by selecting Duplicate from its
context menu. The copy is then calculated, to show how modifying the antenna tilt has affected coverage (see
Figure 13.27).
As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change
in coverage, you can compare the two predictions.
To compare two predictions:
1. Right-click one of the two predictions. The context menu appears.
2. From the context menu, select Compare with and, from the menu that opens, select the prediction you want to
compare with the first. The Comparison Properties dialogue appears.
3. Click the General tab. You can change the Name of the comparison and add Comments.
The General tab contains information about the coverage predictions being compared, including their names and
resolutions.
4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes modifying the antenna tilt made, you can choose Union. This will display all pixels
covered by both predictions in one colour and all pixels covered by only one prediction in another colour. The
increase in coverage, seen in only the second coverage prediction, will be immediately clear.
5. Click OK to create the comparison. The comparison in Figure 13.28, shows clearly the increase in coverage due
at the change in antenna tilt.
Using signal quality coverage predictions you can study the effective service coverage area and capacity of each cell in
the network. These coverage predictions depend on the interference in the network and the cell load conditions. For this
reason, the network load must be defined in order to calculate these coverage predictions.
For the purposes of these coverage predictions, each pixel is considered a non-interfering user with a defined service,
mobility type, and terminal. The following are explained in the following sections:
"Service and User Modelling" on page 905.
This section explains the coverage predictions available for analysing the effective signal level and signal quality. The
following are explained:
"Analysing the Effective Signal Levels" on page 907.
"Analysing the Signal Quality" on page 909.
You can also make a point analysis using the Point Analysis window to study the effective signal level at a point. Load
conditions can be selected for the analysis as well as the characteristics of the user-definable probe receiver, i.e., a termi-
nal, a mobility, and a service:
"Making an Effective Signal Analysis" on page 918.
Interferences coming from an external project can also be modelled and is explained in "Modelling Inter-Network Interfer-
ences" on page 236.
Modelling Services
Services are the various services available to users. These services can be either voice or data type services. This section
explains how to create a service. The following parameters are used in predictions:
Throughput scaling factor
Throughput offset
Body loss
To create or modify a service:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the WiMAX Parameters folder.
3. Right-click the Services folder. The context menu appears.
4. Select New from the context menu. The Services New Element Properties dialogue appears.
Note: You can modify the properties of an existing service by right-clicking the service in the
Services folder and selecting Properties from the context menu.
5. You can edit the fields on the General tab to define the new service. Some fields depend on the type of service
you choose. You can change the following parameters.
- Name: Atoll proposes a name for the new service, but you can set a more descriptive name.
- Type: You can select either Voice or Data as the service type.
- Priority: Enter a priority for this service. "0" is the lowest priority.
- QoS Class: Select a QoS class for the service. You have the option to choose from UGS (Unsolicited Grant
Service), ErtPS (Extended Real-Time Polling Service), rtPS (Real-Time Polling Service), nrtPS (Non-Real-
Time Polling Service), and BE (Best Effort). The information about the QoS class used by any service is used
by the schedulers for resource allocation. For more information about how schedulers work in Atoll, see
"Defining WiMAX Schedulers" on page 980.
- Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity for
users accessing a voice type service during Monte Carlo simulations.
- Highest Bearer: Select the highest bearer that the service can use in the uplink and downlink. This is consid-
ered as an upper limit during bearer determination.
- Max Throughput Demand: Enter the highest throughput that the service can demand in the uplink and down-
link. This value is not considered for services UGS as the quality of service.
- Min. Throughput Demand: Enter the minimum required throughput that the service should have in order to
be available in the uplink and downlink. This value is not considered for BE services.
- Average Requested Throughput: Enter the average requested throughput for uplink and downlink. The
average requested throughput is used in a simulation during user distribution generation in order to calculate
the number of users attempting a connection.
- Application Throughput: Under Application Throughput, you can set a Scaling Factor between the appli-
cation throughput and the MAC (Medium Access Control) throughput and a throughput Offset. These param-
eters model the header information and other supplementary data that does not appear at the application level.
The application throughput parameters are used in throughput coverage predictions and for application
throughput calculation.
- Body Loss: Enter a body loss for the service. The body loss is the loss due to the body of the user. For
example, in a voice connection the body loss, due to the proximity of the users head, is estimated to be 3 dB.
6. Click OK.
In WiMAX, information about the receiver mobility is required for determining which bearer selection threshold and quality
graph to use from the WiMAX equipment referred to in the terminal or cell. Mobiles used at high speeds and at walking
speeds do not have the same quality characteristics. C/(I+N) requirements for different radio bearers are largely depend-
ent on mobile speed.
To create or modify a mobility type:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the WiMAX Parameters folder.
3. Right-click the Mobility Types folder. The context menu appears.
4. Select New from the context menu. The Mobility Types New Element Properties dialogue appears.
Note: You can modify the properties of an existing mobility type by right-clicking the mobility
type in the Mobility Types folder and selecting Properties from the context menu.
5. You can enter or modify the following parameters in the Mobility Types New Element Properties dialogue:
- Name: Enter a descriptive name for the mobility type.
- Average Speed: Enter an average speed for the mobility type. This field is for information only; the average
speed is not used by any calculation.
6. Click OK.
Note: Subscriber lists use the mobility type "Fixed", i.e., 0 km/hr, in calculations. Do not delete
this mobility type from the document if you are working with subscriber lists.
Modelling Terminals
In WiMAX, a terminal is the user equipment that is used in the network, for example, a mobile phone, a PDA, or a cars
on-board navigation device.
The following parameters are used in predictions:
Antenna
WiMAX equipment
Maximum and minimum terminal power
Gain and losses
Noise figure
Supported antenna diversity technique
Number of transmission and reception antennas for MIMO
To create or modify a terminal:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the WiMAX Parameters folder.
3. Right-click the Terminals folder. The context menu appears.
4. Select New from the context menu. The Terminals New Element Properties dialogue appears.
Note: You can modify the properties of an existing terminal by right-clicking the terminal in the
Terminals folder and selecting Properties from the context menu.
5. You can enter or modify the following parameters in the Terminals New Element Properties dialogue:
- Name: Enter a descriptive name for the terminal.
- Under Transmission/Reception,
- Min Power: Enter the minimum transmission power of the terminal.
- Max Power: Enter the maximum transmission power of the terminal.
- Noise Figure: Enter the noise figure of the terminal (used to calculate the downlink total noise).
- Losses: Enter the losses of the terminal.
- WiMAX Equipment: Select a WiMAX equipment from the list of available equipment. For more informa-
tion on WiMAX equipment, see "Defining WiMAX Equipment" on page 978. The terminals WiMAX equip-
ment parameters are used in the downlink calculations.
- Under Antenna,
- Model: Select an antenna model from the list of available antennas. If you do not select an antenna for
the terminal, Atoll uses an isotropic antenna in calculations.
Note: Keep in mind that in case you do not select an antenna, Atoll uses an isotropic antenna,
not an omni-directional antenna, in calculations. An isotropic antenna has spherical
radiation patterns in the horizontal as well as vertical planes.
- Gain: Enter the terminal antenna gain if you have not selected an antenna model in the Model field. If you
have selected an antenna, the Gain field is disabled and shows the gain of the selected antenna.
- Antenna Diversity Support: Select the type of antenna diversity techniques supported by the terminal.
Antenna diversity gains will be applied to the users using any terminal type depending on the supported
antenna diversity techniques, i.e., AAS, MIMO, or AAS+MIMO. If a terminal that supports AAS+MIMO is
connected to a cell (permutation zone in WiMAX 802.16e) that supports both antenna diversity tech-
niques, both AAS and MIMO gains will be applied.
- Number of Transmission Antennas: Under MIMO, enter the number of antennas used by the terminal
in transmission.
- Number of Reception Antennas: Under MIMO, enter the number of antennas used by the terminal in
reception.
6. Click OK.
For more information on services, terminals, mobility types, and WiMAX equipment, see "Modelling Services" on
page 905, "Modelling Terminals" on page 906, "Modelling Mobility Types" on page 906, and "Defining WiMAX
Equipment" on page 978, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
the effective signal analysis calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
Figure 13.29: Condition settings for an effective signal analysis coverage prediction
10. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 13.30
and Figure 13.31).
If you are setting the traffic loads and the uplink noise rise for a single transmitter, you can set these parameters on the
Cells tab of the transmitters Properties dialogue. However, you can set the traffic loads and the uplink noise rise for all
the cells using the Cells table.
To set the traffic loads and the uplink noise rise using the Cells table:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Open Table from the context menu. The Cells table appears.
4. Enter a value in the following columns:
- Traffic Load (DL) (%)
- UL Noise Rise (dB)
- Segmentation Usage (DL) (%) (WiMAX 802.16e)
Although, you can also set a value for the Traffic Load (UL) (%) column as an indication of cells uplink loads,
this parameter is not used in the coverage prediction calculations. The measure of interference in the uplink
is given by the UL Noise Rise (dB). For a definition of the values, see "Cell Description" on page 872.
5. To enter the same values in one column for all cells in the table:
a. Enter the value in the first row in the column.
b. Select the entire column.
c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
Downlink and uplink coverage predictions by C/(I+N) level predict the interference levels and signal-to-interference levels
in the part of the network being studied.
Atoll calculates the best server for each pixel depending on the downlink preamble signal level. The serving transmitter
is determined according to the received preamble signal level from the cell with the highest preamble power. If more than
one cell cover the pixel, the one with the lowest order is selected as the serving (reference) cell. Then, depending on the
prediction definition, it calculates the interference from other cells, and finally calculates the C/(I+N). The pixel is coloured
if the display threshold condition is fulfilled (in other words, if the C/(I+N) is higher than C/(I+N) threshold).
Coverage prediction by C/(I+N) level calculates the co-channel interference as well as the adjacent channel interference,
which is reduced by the adjacent channel suppression factor defined in the Frequency Bands table. For more information
on frequency bands, see "Defining Frequency Bands" on page 971.
The preamble C/(I+N) is calculated using the preamble power and the main antenna. Interference on the preamble does
not depend on the cell load conditions. It depends only on the probabilities of collision between the subcarriers used to
transmit the preamble. The downlink traffic C/(I+N) is calculated using the traffic power, the main antenna or the smart
antenna equipment, downlink traffic load, the segmentation usage ratio, and any AAS simulation results stored either in
the cell properties or in the selected simulation results. The downlink traffic C/(I+N) also takes into account the probabilities
of collision between subcarriers when segmentation is used. The uplink C/(I+N) is calculated using the terminal power
calculated after power control, the main antenna or the smart antenna equipment, uplink noise rise, and any AAS simula-
tion results stored either in the cell properties or in the selected simulation results.
To make a coverage prediction by C/(I+N) level:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by C/(I+N) Level (DL) or Coverage by C/(I+N) Level (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The C/(I+N) coverage prediction is a best server
coverage prediction. The Noise Figure defined in the terminal types properties dialogue is used in the coverage
prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to determine
the total noise in the uplink.
For more information on services, terminals, mobility types, and WiMAX equipment, see "Modelling Services" on
page 905, "Modelling Terminals" on page 906, "Modelling Mobility Types" on page 906, and "Defining WiMAX
Equipment" on page 978, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 13.33
and Figure 13.34).
Downlink and uplink best radio bearer coverage predictions calculate and display the best WiMAX radio bearers based on
C(I+N) for each pixel.
To make a coverage prediction by best bearer:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Best Bearer (DL) or Coverage by Best Bearer (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The best bearer coverage prediction is always based
on the best server. The Noise Figure defined in the terminal types properties dialogue is used in the coverage
prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to determine
the total noise in the uplink. As well, the bearer selection for each pixel according to the traffic C(I+N) level is
performed using the bearer selection thresholds defined in the WiMAX equipment. This WiMAX equipment is the
one defined in the selected terminal for the downlink coverage predictions, and the one defined in the cell proper-
ties of the serving transmitter for the uplink coverage predictions. Mobility is used to index the bearer selection
threshold graph to use.
For more information on services, terminals, mobility types, and WiMAX equipment, see "Modelling Services" on
page 905, "Modelling Terminals" on page 906, "Modelling Mobility Types" on page 906, and "Defining WiMAX
Equipment" on page 978, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the WiMAX bearer coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 13.36
and Figure 13.37).
Downlink and uplink throughput coverage predictions calculate and display the channel throughputs and cell capacities
based on C(I+N) and bearer calculations for each pixel. These coverage predictions can also display aggregate cell
throughputs if Monte Carlo simulation results are available. For more information on making aggregate cell throughput
coverage predictions using simulation results, see "Making an Aggregate Throughput Coverage Prediction Using Simula-
tion Results" on page 916.
To make a coverage prediction by throughput:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Throughput (DL) or Coverage by Throughput (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The throughput coverage prediction is always based
on the best server. The Noise Figure defined in the terminal types Properties dialogue is used in the coverage
prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to determine
the total noise in the uplink. As well, the bearer selection for each pixel according to the C(I+N) level is performed
using the bearer selection thresholds defined in the WiMAX equipment. This WiMAX equipment is the one defined
in the selected terminal for the downlink coverage predictions, and the one defined in the cell properties of the
serving transmitter for the uplink coverage predictions. The mobility is used to indicate the bearer selection thresh-
old graph to use. The service is used for the application throughput parameters defined in the service Properties
dialogue.
For more information on services, terminals, mobility types, and WiMAX equipment, see "Modelling Services" on
page 905, "Modelling Terminals" on page 906, "Modelling Mobility Types" on page 906, and "Defining WiMAX
Equipment" on page 978, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage pre-
diction will display. You can set parameters to display the following results:
- Channel throughputs: Select Peak MAC Channel Throughput, Effective MAC Channel Throughput, or
Application Channel Throughput.
- Cell capacities: Select Peak MAC Cell Capacity, Effective MAC Cell Capacity, or Application Cell
Capacity.
- Allocated bandwidth throughputs in uplink: Select Peak MAC Allocated Bandwidth Throughput, Effective
MAC Allocated Bandwidth Throughput, or Application Allocated Bandwidth Throughput.
The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see
"Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Atoll calculates the peak MAC channel throughputs from the information provided in the Global Parameters and in the
terminal and mobility properties for the terminal and mobility selected in the coverage prediction. Atoll determines the total
number of symbols in the downlink and the uplink subframes from the information in the Global Parameters. Then, Atoll
determines the bearer at each pixel and multiplies the bearer efficiency by the number of symbols in the frame to determine
the peak MAC channel throughputs.
The effective MAC throughputs are the peak MAC throughputs reduced by retransmission due to errors, or the Block Error
Rate (BLER). Atoll uses the block error rate graphs of the WiMAX equipment defined in the selected terminal or the
WiMAX equipment of the cell of the serving transmitter.
The application throughput is the effective MAC throughput reduced by the overheads of the different layers between the
MAC and the Application layers.
The cell capacity display types let you calculate and display the throughputs available at each pixel of the coverage area
taking into account the maximum traffic load limits set for each cell. In other words, the cell capacity is equal to channel
throughput when the maximum traffic load is set to 100%, and is equal to a throughput limited by the maximum allowed
traffic loads otherwise. Cell capacities are, therefore, channel throughputs scaled down to respect the maximum traffic load
limits.
The allocated bandwidth throughputs are the throughputs corresponding to the number of subchannels allocated to the
terminal at different locations. Subchannelisation in uplink allows mobiles to use different numbers of subchannels
depending on the radio conditions. For example, users located far from the base stations use less subchannels than users
located near so that they can concentrate their transmission power over a bandwidth narrower than the channel bandwidth
in order to maintain the connection in uplink.
For more information on throughput calculation, see the Technical Reference Guide. For more information on the Global
Parameters, see "The Global Transmitter Parameters" on page 972.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Atoll calculates the aggregate peak MAC, effective MAC, and application cell throughputs during Monte Carlo simulations.
The aggregate cell throughputs are the sums of the cells user throughputs. You can create a coverage prediction that
calculates and displays the surface area covered by each cell, and colours the coverage area of each cell according to its
aggregate throughput.
To create an aggregate throughput coverage prediction:
1. Create and run a Monte Carlo simulation. For more information on creating Monte Carlo simulations, see "Calcu-
lating and Displaying Traffic Simulations" on page 949.
2. Create a coverage prediction by throughput as explained in "Making a Coverage by Throughput" on page 914,
with the following exceptions:
a. On the Condition tab, select a simulation or group of simulations from the Load Conditions list. The coverage
prediction will display the results based on the selected simulation or on the average results of the selected
group of simulations.
b. On the Display tab, you can display results by Peak MAC User Throughput, Effective MAC User Through-
put, or Application User Throughput. The coverage prediction results will be in the form of thresholds. For
information on defining the display, see "Display Properties of Objects" on page 33.
This coverage prediction displays the surface area covered by each cell and colours it according to its aggregate through-
put. For more information on using simulation results in coverage predictions, see "Making Coverage Predictions Using
Simulation Results" on page 963.
Downlink and uplink quality indicator coverage predictions calculate and display the values of different quality indicators
(BLER, BER, etc.) based on the best WiMAX radio bearers and on C(I+N) for each pixel.
To make a coverage prediction by quality indicator:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Quality Indicator (DL) or Coverage by Quality Indicator (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The quality indicator coverage prediction is always
based on the best server. The Noise Figure defined in the terminal types properties dialogue is used in the cover-
age prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to deter-
mine the total noise in the uplink. As well, the bearer selection for each pixel according to the traffic C(I+N) level
is performed using the bearer selection thresholds defined in the WiMAX equipment, and the quality indicator
graphs from the WiMAX equipment are used to determine the values of the selected quality indicator on each pixel.
This WiMAX equipment is the one defined in the selected terminal for the downlink coverage predictions, and the
one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used to
index the bearer selection threshold graph to use.
This WiMAX equipment is the one defined in the selected terminal for the downlink coverage predictions, and the
one defined in the cell properties of the serving transmitter for the uplink coverage predictions.
For more information on services, terminals, mobility types, and WiMAX equipment, see "Modelling Services" on
page 905, "Modelling Terminals" on page 906, "Modelling Mobility Types" on page 906, and "Defining WiMAX
Equipment" on page 978, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
age prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Prop-
erties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the quality indicator coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 13.42
and Figure 13.43).
The downlink traffic signal levels, downlink traffic loads, segmentation usage (WiMAX 802.16e), AAS simulation
results, and AAS usage, for determining the downlink traffic C/(I+N), bearer, and throughputs.
The uplink signal levels, uplink noise rise, and AAS simulation results, for determining the uplink C/(I+N), bearer,
and throughputs.
The downlink and uplink load conditions can be taken from the Cells table or from Monte Carlo simulations.
You can make an effective signal analysis to verify a coverage prediction. In this case, before you make the point analysis,
ensure the coverage prediction you want to verify is displayed on the map.
To make an effective signal analysis:
1. Click the Point Analysis button ( ) on the toolbar. The Point Analysis Tool window appears (see
Figure 13.45).
2. Click the Signal Analysis tab.
3. At the top of the Signal Analysis tab, select "Cells Table" from Load Conditions.
4. If you are making a signal analysis to verify a coverage prediction, you can recreate the conditions of the coverage
prediction:
a. Select the same Terminal, Service, and Mobility studied in the coverage prediction.
b. Right-click the Point Analysis window and select Properties from the context menu. The Properties dia-
logue appears.
- Edit the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and,
select "From Model" from the Shadowing Margin list.
c. Click OK to close the Properties dialogue.
5. Move the pointer over the map to make a signal analysis for the current location of the pointer.
As you move the pointer, Atoll indicates on the map which is the best server for the current position (see
Figure 13.44).
Information on the current position is given on the Signal Analysis tab of the Point Analysis window. See
Figure 13.45 for an explanation of the displayed information.
6. Click the map to leave the point analysis pointer at its current position.
To move the pointer again, click the point analysis pointer on the map and drag it to a new position.
7. Click the Point Analysis button ( ) on the toolbar again to end the point analysis.
The preamble reception from the best The connection status (preamble, downlink
server (top-most bar) and all interfering and uplink) for the current point.
cells. Solid bars indicate the signal levels
above the preamble C/N thresholds. : Service available
: Service unavailable
7. Under Exceptional Pairs, create a new exceptional pair in the row marked with the New Row icon ( ):
a. Select the cell from the list in the Neighbours column.
b. In the Status column, select one of the following:
- Forced: The selected cell will always be a neighbour of the reference cell.
- Forbidden: The selected cell will never be a neighbour of the reference cell.
8. Click elsewhere in the table when you have finished creating the new exceptional pair.
9. Click OK.
Notes: You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology
Neighbours table. You can open this table by right-clicking the Transmitters folder and
selecting Cells > Neighbours > Intra-Technology Exceptional Pairs.
- Shadowing taken into account: If desired, select the Shadowing taken into account check box and
enter a Cell Edge Coverage Probability.
- Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses defined per
clutter class in the calculations.
- Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic
neighbour allocation.
- % Min. Covered Area: Enter the minimum surface area, in percentage, that a possible neighbour cells cov-
erage area must overlap the reference cells coverage area.
6. Select the desired calculation parameters:
- Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want
cells located on the same site as the reference cell to be automatically considered as neighbours.
- Force adjacent cells as neighbours: Select the Force adjacent cells as neighbours check box if you want
cells that are adjacent to the reference cell to be automatically considered as neighbours. A cell is considered
adjacent if there is at least one pixel in the reference cells coverage area where the possible neighbour cell
is the best server, or where the possible neighbour cell is the second best server (respecting the handover
margin).
- Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In
other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neigh-
bour list of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from
the list of neighbours of the reference cell.
- Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or
forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see
"Defining Exceptional Pairs" on page 921.
- Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete
all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check
box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new
neighbours to the list.
Figure 13.46: The handover area between the reference cell and the possible neighbour
7. Click the Importance Weighting button to set the relative importance of possible neighbours:
- Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage
reasons.
- Adjacency Factor: If you have selected the Force adjacent cells as neighbours check box in step 6., set
the minimum and maximum importance of a possible neighbour cell being adjacent to the reference cell.
- Co-site Factor: If you have selected the Force co-site cells as neighbours check box in step 6., set the
minimum and maximum importance of a possible neighbour cell being located on the same site as reference
cell.
8. Click Calculate. Atoll begins the process of allocating neighbours. Atoll first checks to see whether the path loss
matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates them.
Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays
new neighbours. If no new neighbours have been found and if the Deleting existing neighbours check box is
cleared, the Results table will be empty.
- Cause: The reason Atoll has allocated the possible neighbour cell, as identified in the Neighbour column, to
the reference cell, as identified in the Cell column. The possible reasons are:
- Co-site
- Adjacency
- Symmetry
- Coverage
- Existing
- Coverage: The amount of reference cells coverage area that the neighbour overlaps, in percentage and in
square kilometres.
- Adjacency: The area of the reference cell, in percentage and in square kilometres, where the neighbour cell
is best server or second best server.
9. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atolls table
shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data
Tables" on page 50.
10. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neigh-
bours are listed in the Intra-technology Neighbours tab of each cells Properties dialogue.
Notes:
A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already
exists and the Delete existing neighbours check box is cleared when you start the new allo-
cation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint
on the forbidden neighbour will be ignored by the algorithm because the neighbour already
exists.
When the options Force exceptional pairs and Force symmetry are selected, Atoll con-
siders the constraints between exceptional pairs in both directions in order to respect sym-
metry. On the other hand, if the neighbour relation is forced in one direction and forbidden in
the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the
Event Viewer.
You can save automatic neighbour allocation parameters in a user configuration. For informa-
tion on saving automatic neighbour allocation parameters in a user configuration, see
"Exporting a User Configuration" on page 75.
1. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
2. Select Display Options from the context menu. The Visual Management dialogue appears.
3. Under Intra-technology Neighbours, select the Display Links check box.
4. Click the Browse button ( ) beside the Display Links check box.
5. The Intra-technology Neighbour Display dialogue appears.
6. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a cell with a
unique colour.
- Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you
want Atoll to colour the cells neighbour links according to a value from the Intra-technology Neighbours
table, or according to the neighbour frequency band.
- Value Intervals: Select "Value Intervals" to colour the cells neighbour links according the value interval of the
value selected from the Field list. For example, you can choose to display a cells neighbours according to the
importance, as determined by the weighting factors.
Tip: You can display the number of handoff attempts for each cell-neighbour pair by first
creating a new field of Type "Integer" in the Intra-Technology Neighbour table for the
number of handoff attempts. Once you have imported or entered the values in the new
column, you can select this field from the Field list along with "Value Intervals" as the
Display Type. For information on adding a new field to a table, see "Adding a Field to an
Object Types Data Table" on page 51.
Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you
can display or hide neighbour link display types individually.
For information on changing display properties, see "Display Properties of Objects" on page 33.
7. Select the Add to Legend check box to add the displayed neighbour links to the legend.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each neighbour link.
9. Click OK to save your settings.
10. Under Advanced, select which neighbour links to display:
- Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations
where the selected cell is the reference cell and where the neighbour relation is not symmetric.
- Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations
where the selected cell is neighbour and where the neighbour relation is not symmetric.
- Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the
selected cell and the neighbour.
11. Click OK to save your settings.
12. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
- The symmetric neighbour relations of the selected (reference) cell are indicated by a line.
- The outward neighbour relations are indicated with a line with an arrow pointing at the neighbour (e.g. see
Site1_2(0)) in Figure 13.47.).
- The inward neighbour relations are indicated with a line with an arrow pointing at the selected cell (e.g. see
Site9_3(0)) in Figure 13.47.).
In Figure 13.47, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward
neighbour links are coloured as the corresponding neighbour transmitters and the inward neighbour link is
coloured as the reference transmitter as it is neighbour of Site9_3(0) here.
In Figure 13.48, neighbour links are displayed according to the neighbour frequency. Here, all neighbour relations
are symmetric.
Figure 13.48: Neighbours of Site 22_3(0) - Display According to The Neighbour Frequency
Note: You can display either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting
either Forced Neighbours or Forbidden Neighbours.
2. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
3. Select Display Options from the context menu. The Neighbourhood Display dialogue appears.
4. Under Intra-technology Neighbours, select the Display Coverage Areas check box.
5. Click the Browse button ( ) beside the Display Coverage Areas check box.
6. The Intra-technology Neighbour Display dialogue appears.
7. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage area of a cells neigh-
bours with a unique colour.
- Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you
want Atoll to colour the coverage area of a cells neighbours according to a value from the Intra-technology
Neighbours table.
- Value Intervals: Select "Value Intervals" to colour the coverage area of a cells neighbours according the
value interval of the value selected from the Field list. For example, you can choose to display a cells neigh-
bours according to the importance, as determined by the weighting factors.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each coverage area.
9. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( ) in the
Radio toolbar.
Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete WiMAX 802.16e neighbours using the Cells tab of the transmitters Properties dialogue:
1. On the map, right-click the transmitter whose neighbours you want to change. The context menu appears.
2. Select Properties from the context menu. The transmitters Properties dialogue appears.
3. Click the Cells tab.
4. On the Cells tab, click the Browse button ( ) beside Neighbours. The cells Properties dialogue appears.
5. Click the Intra-technology Neighbours tab.
6. If desired, you can enter the maximum number of neighbours.
7. Allocate or delete a neighbour.
To allocate a new neighbour:
a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon
( ).
b. Click elsewhere in the table when you have finished creating the new neighbour.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Right-click the neighbour in the Neighbour column. The context menu appears.
c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation be-
tween the cell in the Neighbour column and the cell in the Cell column is deleted.
To delete a neighbour:
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Press DEL to delete the neighbour.
8. Click OK.
Note: For information on working with data tables, see "Working with Data Tables" on page 50.
a. In the row marked with the New Row icon ( ), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column.
c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
a. Right-click the neighbour in the Neighbour column. The context menu appears.
b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the
Neighbour column and the cell in the Cell column.
To make several neighbour relations symmetric:
a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select
contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contig-
uous rows by pressing CTRL and clicking each rows separately.
b. Right-click the Neighbours table. The context menu appears.
c. Select Symmetrise from the context menu.
To take into consideration all exceptionnal pairs:
Note: You can add or delete either some forced neighbours or some forbidden neighbours using
the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table,
select the exceptional pairs to be considered, right-click the table and select Force
Exceptional Pairs in the context menu.
a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select
contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contig-
uous rows by pressing CTRL and clicking each rows separately.
b. Right-click the Neighbours table. The context menu appears.
c. Select Delete Link and Symmetric Relation from the context menu.
To delete a neighbour:
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Press DEL to delete the neighbour.
You can allocate or delete intra-technology neighbours directly on the map using the mouse.
To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neigh-
bours on the map as explained in "Displaying Neighbour Relations on the Map" on page 923.
To add a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters
to the intra-technology neighbours list.
To remove a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both trans-
mitters from the intra-technology neighbours.
To add an outward neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference
transmitter to the intra-technology neighbour list of the transmitter.
Notes:
When there is more than one cell on the transmitter, clicking the transmitter in the map window
opens a context menu allowing you to select the cell you want (see "Selecting One of Several
Transmitters or Microwave Links" on page 30).
You can add or delete either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting either
Forced Neighbours or Forbidden Neighbours.
Note: If the field Max number of intra-technology neighbours in the Cells table is empty, the
Full Lists check and the Lists > Max Number check use the Default Max Number value
defined in the audit dialogue.
- Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
- Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
The AFP enables you to automatically allocate frequencies to cells in the current network.
To automatically allocate frequencies:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Frequency Plan > Automatic Allocation. The Frequency Allocation dialogue appears.
4. You can set the following parameters:
- In WiMAX 802.16e documents, under Allocate, you can select Frequencies to perform automatic frequency
planning or Preamble Indexes to allocate preamble indexes to cells automatically.
- In WiMAX 802.16e documents, if you have selected Preamble Indexes under Allocate,
- Select the Preamble Index Allocation Range. You can choose to allocate preamble indexes from the
Entire (0-113) range or a Reduced (0-95) range.
- Under Cell PermBase Allocation Strategy, you can either select Free or Same per Site as the allocation
strategy.
For more information on the strategies, see "Automatically Allocating Preamble Indexes to WiMAX 802.16e
Cells" on page 934.
- Under Relations, you can set the relations to take into account in automatic allocation.
- Under Interference Matrices, you can calculate and take interference matrices into account for the fre-
quency allocation. When the Frequency Allocation dialogue opens, the Take into account check box is
disabled because interference matrices are not yet calculated nor available.
To calculate interference matrices:
i. Enter a value for the Quality Margin.
ii. Click the Calculate button. Atoll calculates the interference matrices. The calculation progress is dis-
played in the Event Viewer window. To stop the interference matrices calculation at any moment, click
the Stop button. Interference matrices are calculated using the default calculation resolution set in the
Properties dialogue of the Predictions folder.
iii. Click the Close button once the interference matrices have been calculated. The Event Viewer window
closes.
To display details of the calculated interference matrices:
i. Click the Details button. The Interference Matrices Display dialogue appears. This dialogue lists all the
interfered and interfering cell pairs and their respective interference probabilities in co- and adjacent chan-
nel cases.
ii. Click the Close button. The Interference Matrices Display dialogue closes.
To delete the calculated interference matrices:
Interference matrices calculated by the AFP are the co- and adjacent channel interference probabilities
for each interfered and interfering cell pair. The probability of interference of a cell is defined as the ratio
of the interfered surface area within the best server coverage area of any studied cell to the total best serv-
er coverage area of the cell:
S Int
P Int = --------------
-
S Total
In words, S Total is the best server coverage area of the studied cell, and S Int is the surface area within
the best server area of the studied cell where the interference from another cell is higher than the preamble
C/N threshold of the studied cell plus the quality margin.
The quality margin is defined with respect to the preamble C/N thresholds of cells. By default the preamble
C/N threshold outlines the area of service of a cell. This means that where the preamble signal quality of
a cell is less than the preamble C/N threshold, there is no service. The AFP uses the quality margin to
calculate interference within the service areas of cells. It is possible to set a value of quality margin which
reflects the coverage area of a bearer.
- Take min reuse distance into account: Select this check box if you want the AFP to take relations based
on distance into account for the allocation. You can enter the Default radius within which two cells whose
channels have a co-channel overlap cannot have the same frequency or preamble index.
Note: A minimum reuse distance can be defined at the cell level (in the cell Properties dialogue
or in the Cells table). If defined, a cell-specific reuse distance will be used instead of
default the value entered here.
- Take neighbours into account: In WiMAX 802.16e documents, select this check box if you want the AFP
to take neighbour relations into account for the allocation. The AFP will try to avoid allocating the same
frequency or preamble index to neighbours of each cell being allocated.
Atoll can only take neighbour relations into account if neighbours have already been allocated. For infor-
mation on allocating neighbours, see "Planning Neighbours" on page 920.
5. Under Results, Atoll displays the Total Cost of the current frequency or preamble index allocation taking into
account the parameters set in step 4. You can modify the parameters and click Recalculate Cost to see the
change in the total cost.
6. Click Calculate. Atoll begins the process of allocating frequencies or preamble indexes.
Once Atoll has finished allocating frequencies or preamble indexes, the proposed allocation is visible under
Results.
When you allocate frequencies to a large number of cells, it is easiest to let Atoll allocate them automatically, as described
in "Automatically Allocating Frequencies to Cells" on page 930. However, if you want to assign a frequency or a preamble
index to one cell or to modify it, you can do it by accessing the properties of the cell.
To allocate the frequency or preamble index to a cell manually:
1. On the map, right-click the transmitter to whose cell you want to allocate the frequency or preamble index. The
context menu appears.
2. Select Properties from the context menu. The transmitters Properties dialogue appears.
3. Select the Cells tab.
4. Select a Frequency Band and Channel Number for the cell or enter a Preamble Index.
5. You can set the Channel Allocation Status or Preamble Index Status to Fixed if you want to lock the frequency
or preamble index that you assigned.
6. Click OK.
In Atoll, you can search for frequency bands and channel numbers using the Search Tool.
If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results
displayed by transmitter, the search results will be displayed by transmitter coverage. Frequencies and any potential prob-
lems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage Prediction
by Transmitter" on page 894.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
If you selected the Co-channel Only check box, transmitters with cells using the same channel number are
displayed in red, and all others, including transmitters with adjacent channels, are displayed in grey.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
Note: By including the frequency band and channel number of each cell in the transmitter label,
the search results will be easier to understand. For information on defining the label, see
"Defining the Object Type Label" on page 35.
You can display the frequency allocation on transmitters by using the transmitters display characteristics.
To display the frequency allocation on the map:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Display tab.
5. Select "Discrete Values" as the Display Type and "Cells: Channel Number" as the Field.
6. Click OK. Transmitters will be displayed by channel number.
You can also display the frequency band and channel number in the transmitter label or tooltip by selecting "Cells:
Frequency Band" and "Cells: Channel Number" from the Label or Tip Text Field Definition dialogue.
For information on display options, see "Display Properties of Objects" on page 33.
You can group transmitters on the Data tab of the Explorer window by their frequency bands or channel numbers.
To group transmitters by frequency bands or channel numbers:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the General tab, click Group by. The Group dialogue appears.
5. Under Available Fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
- Frequency Band
- Channel Number
- Min Reuse Distance
7. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to
the list of parameters on which the transmitters will be grouped.
8. If you do not want the transmitters to be sorted by a certain parameter, select the parameter in the Group these
fields in this order list and click . The selected parameter is removed from the list of parameters on which
the transmitters will be grouped.
9. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters
to be grouped:
10. Click OK to save your changes and close the Group dialogue.
You can create and compare preamble C/(I+N) coverage predictions before and after the automatic frequency allocation
in order to analyse and compare the improvements brought about by the AFP. For more information on creating preamble
C/(I+N) coverage predictions, see "Making a Coverage by C/(I+N) Level" on page 910. For more information on comparing
two coverage predictions, see "Comparing Coverage Predictions: Examples" on page 900.
Where n is the segment number (0, 1, or 2), and k is a running index from 0 to 567, 283, 142, and 35 for FFT sizes 2048,
1024, 512, and 128, respectively. Therefore, each preamble carrier set uses every third subcarrier.
You can assign preamble indexes manually or automatically to any cell in the network. Once allocation is completed, you
can audit the preamble indexes, view preamble index reuse on the map, and make an analysis of preamble index distri-
bution.
The procedure for planning preamble indexes for a WiMAX 802.16e project is:
Allocating preamble indexes
- "Automatically Allocating Preamble Indexes to WiMAX 802.16e Cells" on page 934.
- "Allocating Preamble Indexes to WiMAX 802.16e Cells Manually" on page 934.
"Checking the Consistency of the Preamble Index Plan" on page 935.
Displaying the allocation of preamble indexes
- "Using the Search Tool to Display Preamble Index Allocation" on page 935.
- "Displaying Preamble Index Allocation Using Transmitter Display Settings" on page 936.
- "Grouping Transmitters by Preamble Index" on page 936.
- "Displaying the Preamble Index Allocation Histogram" on page 936.
The allocation algorithm enables you to automatically allocate preamble indexes to cells in the current network. You can
choose from two allocation strategies for the cell permbase (for more information, see the Technical Reference Guide):
Free: The preamble index allocation will only be restricted by the segment number allocated to nearby cells. Cell
permbases will not necessarily be the same for all the cells of a site.
Same per Site: This strategy allocates preamble indexes to cells such that the same cell permbase is assigned
to all the cells of a site.
To automatically allocate preamble indexes:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Preamble Indexes > Automatic Allocation. The Preamble Index Allocation dialogue appears.
4. You can set the following parameters:
- Under Relations, you can set the relationships to take into account in automatic preamble index allocation.
- Neighbours: Select the Neighbours check box if you want to consider neighbour relations. The automat-
ic allocation algorithm will try to avoid allocating the same preamble index to neighbours of each cell being
allocated.
Atoll can only consider neighbour relations if neighbours have already been allocated. For information on
allocating neighbours, see "Planning Neighbours" on page 920.
- Min Reuse Distance: Select the Min Reuse Distance check box if you want to consider relations based
on distance. You can enter the Default radius within which two cells whose channels have a co-channel
overlap cannot have the same preamble index.
Note: A minimum reuse distance can be defined at the cell level (in the cell Properties dialogue
or in the Cells table). If defined, a cell-specific reuse distance will be used instead of
default the value entered here.
- Select the Preamble Index Allocation Range. You can choose to allocate preamble indexes from the Entire
(0-113) range or a Reduced (0-95) range.
- Under Cell PermBase Allocation Strategy, you can select one of the following automatic allocation strate-
gies:
- Free
- Same per Site
5. Under Results, Atoll displays the Total Cost of the current preamble index allocation taking into account the
parameters set in step 4. You can modify the parameters and click Recalculate Cost to see the change in the
total cost.
6. Click Calculate. Atoll begins the process of allocating preamble indexes.
Once Atoll has finished allocating preamble indexes, the indexes are visible under Results.
When you allocate preamble indexes to a large number of cells, it is easiest to let Atoll allocate preamble indexes auto-
matically, as described in "Automatically Allocating Preamble Indexes to WiMAX 802.16e Cells" on page 934. However, if
you want to assign a preamble index to one cell or to modify it, you can do it by accessing the properties of the cell.
To allocate a preamble index to a WiMAX 802.16e cell manually:
1. On the map, right-click the transmitter to whose cell you want to allocate a preamble index. The context menu
appears.
2. Select Properties from the context menu. The transmitters Properties dialogue appears.
3. Select the Cells tab.
4. Enter a Preamble Index in the cells column.
5. You can set the Preamble Index Status to Fixed if you want to lock the preamble index that you assigned.
6. Click OK.
In Atoll, you can search for preamble indexes, segment numbers, and cell permbases using the Search Tool.
If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results
displayed by transmitter, the search results will be displayed by transmitter coverage. Preamble indexes and any potential
problems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage
Prediction by Transmitter" on page 894.
To find a preamble index using the Search Tool:
1. Click View > Search Tool. The Search Tool window appears.
2. Select the Segment tab.
3. Select Preamble Index.
4. Enter a Preamble Index.
5. Click Search.
Transmitters whose cells use the entered preamble index are displayed in red. Transmitters with cells use other
preamble indexes are displayed in grey.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
Note: By including the preamble index of each cell in the transmitter label, the search results will
be easier to understand. For information on defining the label, see "Defining the Object
Type Label" on page 35.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
You can display preamble index allocation on transmitters by using the transmitters display characteristics.
To display preamble index allocation on the map:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Display tab.
5. Select "Discrete Values" as the Display Type and "Cells: Preamble Index" as the Field.
6. Click OK. Transmitters will be displayed by preamble index.
You can also display the preamble index in the transmitter label or tooltip by selecting "Cells: Preamble Index" from the
Label or Tip Text Field Definition dialogue.
For information on display options, see "Display Properties of Objects" on page 33.
You can group transmitters on the Data tab of the Explorer window by their preamble index or their reuse distance.
To group transmitters by preamble index:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the General tab, click Group by. The Group dialogue appears.
5. Under Available Fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
- Preamble Index
- Min Reuse Distance
- Preamble Index Status
7. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to
the list of parameters on which the transmitters will be grouped.
8. If you do not want the transmitters to be sorted by a certain parameter, select the parameter in the Group these
fields in this order list and click . The selected parameter is removed from the list of parameters on which
the transmitters will be grouped.
9. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters
to be grouped:
10. Click OK to save your changes and close the Group dialogue.
You can use a histogram to analyse the use of allocated preamble indexes in a network. The histogram represents the
preamble indexes as a function of the frequency of their use.
Traffic map per user profile can be used if you have marketing-based traffic data.
Traffic maps per density of user profiles, where each vector (polygon, line or point) describes subscriber densities
(or numbers of subscribers for points) with user profiles and mobility types, and traffic maps per environment of
user profiles, where each pixel has an assigned environment class. For more information, see "Importing a Traffic
Map Based on Densities of User Profiles" on page 941, "Importing a Traffic Map Based on Environments of User
Profiles" on page 942 and "Creating a Traffic Map Based on Environments of User Profiles" on page 942.
Traffic maps per density (number of users per km2) can be used if you have population-based traffic data,
or 2G network statistics.
Each pixel has an actual user density assigned. For more information, see "Creating Traffic Maps per User
Density (No. Users/km2)" on page 943, "Importing a Traffic Map per User Density" on page 943, "Converting 2G
Network Traffic" on page 945 and "Exporting Cumulated Traffic" on page 945
Note: You can also import a traffic map from a file by clicking the Import button. You can import
AGD (Atoll Geographic Data) format files that you have exported from another Atoll
document.
7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter.
8. Enter the data required in the Map per Sector dialogue:
- If you have selected Throughputs in Uplink and Downlink, enter the throughput demands in the uplink and
downlink for each sector and for each listed service.
- If you have selected Number of Users per Activity Status, enter the number of users active in the uplink, in
the downlink and in the uplink and downlink, for each sector and for each service.
Note: You can also import a text file containing the data by clicking the Actions button and
selecting Import Table from the menu. For more information on importing table data, see
"Importing Tables from Text Files" on page 59.
- The percentage of indoor users. An additional loss will be counted for indoor users during Monte-Carlo
simulations.
11. Click OK. Atoll creates the traffic map in the Traffic folder.
You can update the information, throughput demands and the number of users, on the map afterwards. You can update
Sector traffic maps. You must first recalculate the coverage prediction by transmitter. For more information, see "Making
a Coverage Prediction by Transmitter" on page 894. Once you have recalculated the coverage prediction, you can update
the traffic map.
To update the traffic map:
1. Click the Geo tab of the Explorer window.
2. Click the Expand button ( ) to expand the Traffic folder.
3. Right-click the sector traffic map that you want to update. The context menu appears.
4. Select Update from the context menu. The Map per Sector dialogue appears.
Select the updated coverage prediction by transmitter and define traffic values for the new transmitter(s) listed at
the bottom of the table. Deleted or deactivated transmitters are automatically removed from the table.
You can model variations in user behaviour by creating different profiles for different times of the day or for different circum-
stances. For example, a user may be considered a business user during the day, with video conferencing and voice, but
no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and
web browsing.
To create or modify a user profile:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the WiMAX Parameters folder.
3. Right-click the User Profiles folder. The context menu appears.
4. Select New from the context menu. The User Profiles New Element Properties dialogue appears.
Note: You can modify the properties of an existing user profile by right-clicking the user profile in
the User Profiles folder and selecting Properties from the context menu.
when he quits the browsing application. Between these two events, the user may be downloading web pages
and other times he may not be using the application, or he may be browsing local files, but the session is still
considered as open. A session, therefore, is defined by the volume transferred in the uplink and downlink and
not by the time.
Note: In order for all the services defined for a user profile to be taken into account during traffic
scenario elaboration, the sum of activity probabilities must be lower than 1.
- Duration (sec.): For services of the type "voice," enter the average duration of a call in seconds. For services
of the type "data," this field is left blank.
- UL Volume (KBytes): For services of the type "data," enter the average uplink volume per session in kilo-
bytes.
- DL Volume (KBytes): For services of the type "data," enter the average downlink volume per session in kil-
obytes.
6. Click OK.
Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a
given density (i.e., the number of users with the same profile per km). To get an appropriate user distribution, you can
assign a weight to each clutter class for each environment class. You can also specify the percentage of indoor subscribers
for each clutter class. In a Monte Carlo simulation, an additional loss (as defined in the clutter class properties) will be
added to the indoor users path loss.
To create or modify a WiMAX environment:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the WiMAX Parameters folder.
3. Right-click the Environments folder. The context menu appears.
4. Select New from the context menu. The Environments New Element Properties dialogue appears.
Note: You can modify the properties of an existing environment by right-clicking the
environment in the Environments folder and selecting Properties from the context
menu.
7. In the row marked with the New Row icon ( ), set the following parameters for each user profile/mobility com-
bination that this WiMAX environment will describe:
- User: Select a user profile.
- Mobility: Select a mobility type.
- Density (Subscribers/km2): Enter a density in terms of subscribers per square kilometre for the combination
of user profile and mobility type.
8. Click the Clutter Weighting tab.
9. For each clutter class, enter a weight that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk Sk
N k = N Area --------------------------
Wi Si
i
where:
For example: An area of 10 km with a user density of 100/km. Therefore, in this area, there are 1000 users. The
area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1" and for Building is
"4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter class and 800 in
the Building clutter class.
10. If you wish you can specify a percentage of indoor users for each clutter class. During a Monte Carlo simulation,
an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
11. Click OK.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 942.
- User Profile: If you want to import user profile information from the file, under Defined, select "By field" and
select the source field from the Choice column. If you want to assign a user profile from the WiMAX Param-
eters folder of the Data tab, under Defined, select "By value" and select the user profile in the Choice column.
- Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select
the source field from the Choice column. If you want to assign a mobility type from the WiMAX Parameters
folder of the Data tab, under Defined, select "By value" and select the mobility type in the Choice column.
- Density: If you want to import density information from the file, under Defined, select "By field" and select the
source field from the Choice column. If you want to assign a density, under Defined, select "By value" and
enter a density in the Choice column for the combination of user profile and mobility type. In this context, the
term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kil-
ometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers
when the map consists of points.
Important: When you import user profile or mobility information from the file, the values in the file
must be exactly the same as the corresponding names in the WiMAX Parameters folder
of the Data tab. If the imported user profile or mobility does not match, Atoll will display a
warning.
13. Under Clutter Distribution, enter a weight for each class that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk Sk
N k = N Area --------------------------
Wi Si
i
where:
14. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simu-
lation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
15. Click OK to finish importing the traffic map.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 942.
7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, BIL, IST,
BMP, PlaNET, GRC Vertical Mapper, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears.
11. Select the Description tab.
In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the
Code column.
12. For each Code, select the environment it corresponds to from the Name column.
The environments available are those available in the Environments folder, under WiMAX Parameters on the
Data tab of the Explorer window. For more information, see "Modelling Environments" on page 940.
13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects"
on page 33.
14. Click OK.
7. Select the environment class from the list of available environment classes.
8. Click the Draw Polygon button ( ) to draw the polygon on the map for the selected environment class.
9. Click the Delete Polygon button ( ) and click the polygon to delete the environment class polygon on the map.
10. Click the Close button to close the Environment Map Editor toolbar and end editing.
5. Click Close.
If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per
clutter class.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 942.
7. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP,
PlaNET, TIF, ISTAR, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears.
11. Select the Traffic tab.
12. Select whether the users are active in the Uplink/Downlink, only in the Downlink, or only in the Uplink.
13. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must
equal 100.
14. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must
equal 100.
15. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal
100.
16. Under Clutter Distribution, enter for each clutter class the percentage of indoor users.
An additional loss will be counted for indoor users during the Monte Carlo simulations. You do not have to define
a clutter weighting for traffic maps per user density because the traffic is provided in terms of user density per pixel.
17. Click OK. Atoll creates the traffic map in the Traffic folder.
12. Click OK. Atoll creates the traffic map in the Traffic folder.
13. Right-click the traffic map. The context menu appears.
14. Select Edit from the context menu.
15. Use the tools available in the Vector Edition toolbar in order to draw contours. For more information on how to edit
contours, see "Editing Contours, Lines, and Points" on page 131. Atoll creates an item called Density values in
the User Density Map folder.
16. Right-click the item. The context menu appears.
17. Select Open Table from the context menu.
18. In the table, enter a traffic density value (i.e. the number of users per km2) for each contour you have drawn.
Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains
at "0" and no data will be exported.
8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic
data to be exported.
- Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal.
- Service: Select the service that will be exported, or select "Circuit services" to export voice traffic, or select
"Packet services" to export data traffic.
- Mobility: Select the mobility type that will be exported or select "All" to export all mobility types.
- Activity: Select one of the following:
- All Activity Statuses: Select All Activity Statuses to export all users without any filter by activity status.
- Uplink: Select Uplink to export mobiles active in the uplink only.
- Downlink: Select Downlink to export mobiles active in the downlink only.
- Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity.
9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the
cumulated traffic.
10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.
4. Select Save As from the context menu. The Save As dialogue appears.
5. Enter a file name and select a file format for the traffic map.
6. Click Save.
If you are exporting a raster traffic map, you have to define:
5. Click the Table tab. On the Table tab you can modify the various fields in the subscriber list, add user-defined fields
to the table, or, most importantly, change the default parameters for the fields in the table. These default param-
eters will be assigned to all the subscribers in this list created by using the mouse on the map (see Figure 13.52).
To modify the default values for these fields:
a. Select the field whose default value you want to modify.
b. Click Properties. The Field Definition dialogue appears.
c. Enter the new default value.
d. Click OK.
- ID: The subscriber ID in the subscriber list. It is an automatically created identification number.
- X and Y coordinates: The geographical coordinates of the subscriber. A subscribers location is always fixed.
- Height: The altitude of the subscriber antenna with respect to the ground (DTM).
- Clutter: The name of the clutter class where the subscriber is located. This is a non-editable field whose con-
tents are automatically updated.
- Name: You can assign a descriptive name to each subscriber.
- User Profile: A user profile defines the traffic demand characteristics of subscribers. Atoll determines the ter-
minal used, the service accessed, and the activity status of subscribers during Monte Carlo simulations
according to the information in the user profiles. For more information, see "Modelling User Profiles" on
page 939.
- Terminal: The default terminal (CPE) is the user equipment with an antenna, WiMAX equipment, and noise
characteristics. The properties of this terminal are taken into consideration when performing calculations on
the subscriber list.
- Service: The service that the subscriber accesses by default. The properties of this service are taken into con-
sideration when performing calculations on the subscriber list.
Note: Subscriber lists use the mobility type "Fixed", i.e., 0 km/hr, in calculations. Make sure that
you have bearer selection thresholds defined for this mobility type in the WiMAX
equipment properties. For information on defining bearer selection thresholds, see
"Defining WiMAX Equipment" on page 978.
- Azimuth: The orientation of the subscriber antenna in the horizontal plane. Azimuth is always considered with
respect to the north. You can either define this value manually or let Atoll calculate it for the subscriber. Atoll
points the subscriber antenna towards its serving base station.
- Mechanical Downtilt: The orientation of the subscriber antenna in the vertical plane. Mechanical downtilt is
positive when it is downwards and negative when upwards. You can either define this value manually or let
Atoll calculate it for the subscriber. Atoll points the subscriber antenna towards its serving base station.
- Lock Status: You can choose to lock the subscriber antenna orientation and serving transmitter. Use this
option if you do not want Atoll to change the assigned server or the antenna orientation.
- Serving Base Station: The serving transmitter of the subscriber. You can either define this value manually
or let Atoll calculate it for the subscriber. The serving base station is determined according to the received
preamble signal level from the cell with the highest preamble power.
- Reference Cell: The reference cell of the serving transmitter of the subscriber. You can either define this value
manually or let Atoll calculate it for the subscriber. If more than one cell of the serving base station cover the
subscriber, the one with the lowest order is selected as the reference cell.
- Distance: The distance of the subscriber from its serving base station. This is a non-editable field whose con-
tents are automatically updated.
- Received Preamble Power (DL) (dBm): The preamble signal level received at the subscriber location in the
downlink. This value is calculated by Atoll during calculations on subscriber lists.
- Received Traffic Power (DL) (dBm): The traffic signal level received at the subscriber location in the down-
link. This value is calculated by Atoll during calculations on subscriber lists.
- Received Pilot Power (DL) (dBm): The pilot signal level received at the subscriber location in the downlink.
This value is calculated by Atoll during calculations on subscriber lists.
- Preamble Total Noise (I+N) (DL) (dBm): The sum of the preamble interference and noise experienced at the
subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists.
- Traffic Total Noise (I+N) (DL) (dBm): The sum of the traffic interference and noise experienced at the sub-
scriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists.
- Preamble C/(I+N) (DL) (dB): The preamble C/(I+N) at the subscriber location in the downlink. This value is
generated by Atoll during the calculations on subscriber lists.
- Traffic C/(I+N) (DL) (dB): The traffic C/(I+N) at the subscriber location in the downlink. This value is generated
by Atoll during the calculations on subscriber lists.
- Pilot C/(I+N) (DL) (dB): The pilot C/(I+N) at the subscriber location in the downlink. This value is generated
by Atoll during the calculations on subscriber lists.
- Bearer (DL): The highest WiMAX bearer available for the traffic C/(I+N) level at the subscriber location in the
downlink. This value is generated by Atoll during the calculations on subscriber lists.
- Permutation Zone (DL) (WiMAX 802.16e): The downlink permutation zone allocated to the subscriber.
- BLER (DL): The Block Error Rate read from the subscribers terminal types WiMAX equipment for the traffic
C(I+N) level at the subscriber location in the downlink. This value is generated by Atoll during the calculations
on subscriber lists.
- Diversity Mode (DL): The diversity mode supported by the cell or permutation zone in downlink.
- Peak MAC Channel Throughput (DL) (kbps): The maximum MAC channel throughput attainable using the
highest bearer available at the subscriber location in the downlink. This value is generated by Atoll during the
calculations on subscriber lists.
- Effective MAC Channel Throughput (DL) (kbps): The effective MAC channel throughput attainable using
the highest bearer available at the subscriber location in the downlink. This value is generated by Atoll during
the calculations on subscriber lists.
- Received Power (UL) (dBm): The signal level received at the serving transmitter from the subscriber terminal
in the uplink. This value is generated by Atoll during the calculations on subscriber lists.
- Total Noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the serving transmitter
of the subscriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists.
- C/(I+N) (UL) (dB): The C/(I+N) at the serving transmitter of the subscriber in the uplink. This value is gener-
ated by Atoll during the calculations on subscriber lists.
- Bearer (UL): The highest WiMAX bearer available for the C/(I+N) level at the serving transmitter of the sub-
scriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists.
- Permutation Zone (UL) (WiMAX 802.16e): The uplink permutation zone allocated to the subscriber.
- BLER (UL): The Block Error Rate read from the reference cells WiMAX equipment for the C/(I+N) level at the
serving transmitter of the subscriber in the uplink. This value is generated by Atoll during the calculations on
subscriber lists.
- Diversity Mode (UL): The diversity mode supported by the cell or permutation zone in uplink.
- Transmission Power (UL) (dBm): The transmission power of the subscribers terminal after power control in
the uplink. This value is generated by Atoll during the calculations on subscriber lists.
- Allocated Bandwidth (UL) (No. of Subchannels): The bandwidth allocated to the subscriber in terms of the
number of subchannels allocated in the uplink after subchannelisation. This value is generated by Atoll during
the calculations on subscriber lists.
- Peak MAC Channel Throughput (UL) (kbps): The maximum MAC channel throughput attainable using the
highest bearer available at the serving transmitter of the subscriber in the uplink. This value is generated by
Atoll during the calculations on subscriber lists.
- Effective MAC Channel Throughput (UL) (kbps): The effective MAC channel throughput available using the
highest bearer available at the serving transmitter of the subscriber in the uplink. This value is generated by
Atoll during the calculations on subscriber lists.
For more information on the calculations that you can carry out on subscriber lists, see "Performing Calculations
on Subscriber lists" on page 949.
6. Click the Display tab. You can modify how subscribers added to the list are displayed. For information on defining
the display properties, see "Display Properties of Objects" on page 33.
7. Click OK. Atoll creates a new subscriber list.
You can now move the pointer over the map and click once to place a new subscriber at the location of the pointer. Press
ESC or click the normal pointer button ( ), to finish adding subscribers on the map. For information on adding subscribers
to a list, see "Adding Subscribers to a Subscriber List Using the Mouse" on page 949.
You can open the subscriber list table containing all the subscribers and their parameters.
To open the subscriber list table:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Subscribers folder.
3. Right-click the subscriber list you want to open. The context menu appears.
4. Select Open Table from the context menu.
For information on working with data tables, see "Working with Data Tables" on page 50.
4. Select Add Subscribers from the context menu. The pointer changes to subscriber addition mode ( ).
5. Move the mouse over the Map window, and click once to add each subscriber.
6. Press ESC or click the normal pointer button ( ) to finish adding subscribers.
Tip: To place subscribers more accurately, before clicking the map, you can zoom in on the
map. For information on using the zooming tools, see "Changing the Map Scale" on
page 38.
Note: You can also export subscriber lists. For information on exporting table data, see
"Exporting Tables to Text Files" on page 58.
5. Click Calculate. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
6. Once the calculations are finished, click Close to close the Event Viewer.
7. Click Commit to store the results in the subscriber list. For the list of results that are available after the calculations,
see "Creating a Subscriber List" on page 946.
In Atoll, a simulation corresponds to a given distribution of WiMAX users. It is a snapshot of a WiMAX network. The prin-
cipal outputs of a simulation are a geographic user distribution with a certain traffic demand, resources allocated to each
user of this distribution, and cell loads.
You can create groups for one or more simulations and carry out as many simulations as required. A new simulation for
each different traffic scenario can help visualise the networks response to different traffic demands. Each user distribution
(each simulation generates a new user distribution) is a Poisson distribution of the number of active users. Therefore, each
simulation may have a varying number of users accessing the network.
WiMAX simulation results can be displayed on the map as well as listed in tabular form for analysis. Simulation outputs
include results related to sites, cells, and mobiles.
WiMAX simulation results can be stored in the cells table and used in C/(I+N) based coverage predictions.
In this section, the following are explained:
"WiMAX Traffic Simulation Algorithm" on page 950.
"Creating Simulations" on page 952.
"Displaying the Traffic Distribution on the Map" on page 953.
"Displaying the Results of a Single Simulation" on page 957.
"Updating Cell Load Values With Simulation Results" on page 962.
"Estimating a Traffic Increase" on page 962.
Each mobile generated during the simulations is assigned a service, a mobility type, and a terminal according to
the user profile assigned to it. A transmission status is determined according to the activity probabilities. The trans-
mission status is an important output of the simulation as it has a direct impact on the next step of the simulation
process, i.e., the radio resource management (RRM), and has an impact on the interference level in the network.
The geographical location of each mobile is determined randomly for the mobiles generated based on the traffic
data from traffic maps. The mobiles generated based on the traffic data from subscriber lists are located on the
subscriber locations.
3. Downlink Calculations
The downlink calculations include the calculation of downlink preamble and traffic C/(I+N), determination of the
best available bearer for the traffic C/(I+N), allocation of resources (RRM), and calculation of user throughputs.
Segmentation is performed if the frame configuration, selected for a cell, supports segmentation. Interference
calculation is based on the probabilities of collision between segments. The effect of power concentration is not
considered.
4. Uplink Calculations
The uplink calculations include the calculation of uplink C/(I+N), determination of the best available bearer for the
C/(I+N), uplink power control and subchannelisation depending on the bearer, allocation of resources (RRM),
update of uplink noise rise values for cells, and calculation of user throughputs.
Note: The service priority is determined by the pair QoS Class-Priority. A UGS-Priority 1 service
will have higher service priority than a UGS-Priority 0 service. The QoS classes are UGS,
ErtPS, rtPS, nrtPS, and Best Effort, in order of decreasing priority.
At the end of the simulations, an active user can be connected in the direction corresponding to his activity status if:
he has a best server assigned (step 2.),
he has a bearer in the direction corresponding to his activity status (step 3. and step 4.),
he is among the users selected by the scheduler for resource allocation (step 5.), and
he is not rejected due to resource saturation (step 5.).
If a user is rejected during step 2., step 3., or step 4., the cause of rejection is "No Service". If a user is rejected during
step 5., the cause of rejection can either be "Scheduler Saturation," i.e., the user is not among the users selected for
resource allocation, or he can be rejected due to "Resource Saturation," i.e., all of the cells resources were used up by
other users.
- Select Traffic Maps to be Used: Select the traffic maps you want to use for the simulation.
- Select Subscriber Lists to be Used: Select the subscriber lists you want to use for the simulation.
You can select traffic maps of any type. However, if you have several different types of traffic maps and want
to make a simulation on a specific type of traffic map, you must ensure that you select only traffic maps of the
same type. For information on the types of traffic maps, see "Creating a Traffic Map" on page 937.
Note: When you perform simulations for subscriber lists, Atoll does not base the calculations on
subscriber lists on the path loss matrices calculated for transmitters. This is because the
path loss matrices are calculated for a given receiver height (1.5 m by default), but each
subscriber in a subscriber list can have a different height. Therefore, Atoll recalculates
the path loss, received power, and other output, for each subscriber when you perform
simulations on subscribers.
Tip: Using the same generated user and shadowing error distribution for several simulations
can be useful when you want to compare the results of several simulations where only one
parameter changes.
Tip: You can make the traffic distribution easier to see by hiding geographic data and
coverage predictions. For information, see "Displaying or Hiding Objects on the Map
Using the Explorer" on page 28.
Figure 13.59: Displaying the traffic distribution by the uplink allocated bandwidth
Figure 13.60: Displaying the traffic simulation results using tool tips
The Statistics tab: The Statistics tab contains the following sections:
- Request: Under Request, is data on the connection requests:
- Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; radio resource allocation has not yet finished. The result depends on the traffic description and traffic
input.
- During the first random trial, each user is assigned a service and an activity status. The number of users
per activity status and the UL and DL throughput demands that all users could theoretically generate are
provided.
- The breakdown per service (total number of users, number of users per activity status, and UL and DL
throughput demands) is given.
- Results: Under Results, is data on the connection results:
- The number of iterations that were run in order to converge.
- The total number and percentage of users unable to connect: rejected users, and the number of rejected
users per rejection cause.
- The number and percentage of users connected to a cell, the number of users per activity status, and the
total UL and DL throughputs they generate. These data are also given per service.
The Sites tab: The Sites tab contains the following information per site:
- Peak MAC User Throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink in all the cells of the site.
- Effective MAC User Throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the downlink in all the cells of the site.
- Application User Throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink in all the cells of the site.
- Peak MAC User Throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink in all the cells of the site.
- Effective MAC User Throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the uplink in all the cells of the site.
- Application User Throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink in all the cells of the site.
- Peak MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink in all the cells of the site.
- Effective MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the downlink in all the cells of the site.
- Application User Throughput (DL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the downlink in all the cells of the site.
- Peak MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink in all the cells of the site.
- Effective MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the uplink in all the cells of the site.
- Application User Throughput (UL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the uplink in all the cells of the site.
- No Service: The number of users unable to connect to any cell of the site for which the rejection cause was
"No Service."
- Scheduler Saturation: The number of users unable to connect to any cell of the site for which the rejection
cause was "Scheduler Saturation."
- Resource Saturation: The number of users unable to connect to any cell of the site for which the rejection
cause was "Resource Saturation."
The Cells tab: The Cells tab contains the following information, per site and transmitter:
- Traffic Load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation.
- Traffic Load (UL) (%): The traffic loads of the cells calculated on the uplink during the simulation.
- UL Noise Rise (dB): The noise rise of the cells calculated on the uplink during the simulation.
- Segmentation Usage (DL) (%): (WiMAX 802.16e) The percentage of the downlink traffic load that corre-
sponds to the first downlink PUSC zone, if it is segmented.
- AAS Usage (DL) (%): The percentage of downlink traffic load that corresponds to the traffic carried by the
smart antennas.
- AAS Usage (UL) (%): The percentage of uplink traffic load that corresponds to the traffic carried by the smart
antennas.
- AAS Simulation Results: The simulation results generated for transmitters using a smart antenna. The
results stored in this field are the angular distributions of the downlink traffic power spectral density and the
uplink noise rise. You can make the display of the downlink results diagram take into account the effect of the
antenna pattern of the single element. For more information, see the Administrator Manual.
- MU-MIMO Gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO.
- Peak MAC User Throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink.
- Effective MAC User Throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the downlink.
- Application User Throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink.
- Peak MAC User Throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink.
- Effective MAC User Throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the uplink.
- Application User Throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink.
- Peak MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink.
- Effective MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the downlink.
- Application User Throughput (DL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the downlink.
- Peak MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink.
- Effective MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the uplink.
- Application User Throughput (UL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the uplink.
- No Service: The number of users unable to connect to the cell for which the rejection cause was "No Service."
- Scheduler Saturation: The number of users unable to connect to the cell for which the rejection cause was
"Scheduler Saturation."
- Resource Saturation: The number of users unable to connect to the cell for which the rejection cause was
"Resource Saturation."
The Mobiles tab: The Mobiles tab contains the following information:
- X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the
second random trial).
- Height: The height of the user terminal (antenna).
- User Profile: The assigned user profile. Atoll uses the assigned service and activity status to determine the
terminal and the user profile.
- Service: The service assigned during the first random trial during the generation of the user distribution.
- Terminal: The assigned terminal. Atoll uses the assigned service and activity status to determine the terminal
and the user profile.
- Mobility: The mobility type assigned during the first random trial during the generation of the user distribution.
- Activity Status: The assigned activity status. It can be DL, UL, or DL+UL.
- Connection Status: The connection status indicates whether the user is connected or rejected at the end of
the simulation. If connected, the connection status corresponds to the activity status. If rejected, the rejection
cause is given.
- Clutter Class: The code of the clutter class where the user is located.
- Subscriber ID: The ID of the user if the user is generated from a subscriber list and not from a traffic map.
- Subscriber List: The subscriber list of the user if the user is generated from a subscriber list and not from a
traffic map.
- Indoor: This field indicates whether indoor losses have been added or not.
- Serving Base Station: The serving transmitter of the subscriber.
- Reference Cell: The reference cell of the serving transmitter of the subscriber.
- Total Path Loss (dB): The path loss calculated for the user.
- Received Preamble Power (DL) (dBm): The preamble signal level received at the user location in the down-
link.
- Received Traffic Power (DL) (dBm): The traffic signal level received at the user location in the downlink.
- Received Pilot Power (DL) (dBm): The pilot signal level received at the user location in the downlink.
- Azimuth: The orientation of the users terminal antenna in the horizontal plane. Azimuth is always considered
with respect to the North. Atoll points the user antenna towards its serving base station.
- Downtilt: The orientation of the users terminal antenna in the vertical plane. Mechanical downtilt is positive
when it is downwards and negative when upwards. Atoll points the user antenna towards its serving base sta-
tion.
- Preamble Total Noise (I+N) (DL) (dBm): The sum of the preamble interference and noise experienced at the
user location in the downlink.
- Preamble C/(I+N) (DL) (dB): The preamble C/(I+N) at the user location in the downlink.
- Traffic Total Noise (I+N) (DL) (dBm): The sum of the traffic interference and noise experienced at the user
location in the downlink.
- Traffic C/(I+N) (DL) (dB): The traffic C/(I+N) at the user location in the downlink.
- Pilot C/(I+N) (DL) (dB): The pilot C/(I+N) at the user location in the downlink.
- Bearer (DL): The highest WiMAX bearer available for the traffic C/(I+N) level at the user location in the down-
link.
- Permutation Zone (DL) (WiMAX 802.16e): The downlink permutation zone allocated to the user.
- BLER (DL): The Block Error Rate read from the user terminals WiMAX equipment for the traffic C/(I+N) level
at the user location in the downlink.
- Diversity Mode (DL): The diversity mode supported by the cell or permutation zone in downlink.
- Peak MAC Channel Throughput (DL) (kbps): The maximum MAC channel throughput attainable using the
highest bearer available at the user location in the downlink.
- Effective MAC Channel Throughput (DL) (kbps): The effective MAC channel throughput attainable using
the highest bearer available at the user location in the downlink. It is calculated from the peak MAC throughput
and the BLER.
- Application Channel Throughput (DL) (kbps): The application throughput is the net throughput without
coding (redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the
throughput scaling factor of the service and the throughput offset.
- Peak MAC User Throughput (DL) (kbps): The maximum MAC user throughput attainable using the highest
bearer available at the user location in the downlink.
- Effective MAC User Throughput (DL) (kbps): The effective MAC user throughput attainable using the
highest bearer available at the user location in the downlink. It is calculated from the peak MAC throughput
and the BLER.
- Application User Throughput (DL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
- Received Power (UL) (dBm): The signal level received at the serving transmitter from the user terminal in
the uplink.
- Total Noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the serving transmitter
of the user in the uplink.
- C/(I+N) (UL) (dB): The C/(I+N) at the serving transmitter of the user in the uplink.
- Bearer (UL): The highest WiMAX bearer available for the C/(I+N) level at the serving transmitter of the user
in the uplink.
- Permutation Zone (UL) (WiMAX 802.16e): The uplink permutation zone allocated to the user.
- BLER (UL): The Block Error Rate read from the reference cells WiMAX equipment for the C/(I+N) level at the
serving transmitter of the user in the uplink.
- Diversity Mode (UL): The diversity mode supported by the cell or permutation zone in uplink.
- Transmission Power (UL) (dBm): The transmission power of the user terminal after power control in the
uplink.
- Allocated Bandwidth (UL) (No. of Subchannels): The bandwidth allocated to the user in terms of the
number of subchannels allocated in the uplink after subchannelisation.
- Peak MAC Channel Throughput (UL) (kbps): The maximum MAC channel throughput attainable using the
highest bearer available at user location in the uplink.
- Effective MAC Channel Throughput (UL) (kbps): The effective MAC channel throughput attainable using
the highest bearer available at the user location in the uplink. It is calculated from the peak MAC throughput
and the BLER.
- Application Channel Throughput (UL) (kbps): The application throughput is the net throughput without
coding (redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the
throughput scaling factor of the service and the throughput offset.
- Peak MAC Allocated Bandwidth Throughput (UL) (kbps): The maximum MAC throughput attainable for
the number of subchannels allocated to the user using the highest bearer available at the user location in the
uplink.
- Effective MAC Allocated Bandwidth Throughput (UL) (kbps): The effective MAC throughput attainable for
the number of subchannels allocated to the user using the highest bearer available at the user location in the
uplink. It is calculated from the peak MAC throughput and the BLER.
- Application Allocated Bandwidth Throughput (UL) (kbps): The application throughput is the net
throughput without coding (redundancy, overhead, addressing, etc.). It is calculated from the effective MAC
throughput, the throughput scaling factor of the service and the throughput offset.
- Peak MAC User Throughput (UL) (kbps): The maximum MAC user throughput attainable using the highest
bearer available at the user location in the uplink.
- Effective MAC User Throughput (UL) (kbps): The effective MAC user throughput attainable using the
highest bearer available at the user location in the uplink. It is calculated from the peak MAC throughput and
the BLER.
- Application User Throughput (UL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
Notes:
In Atoll, channel throughputs are peak MAC, effective MAC, or application throughputs
achieved at a given location using the highest WiMAX bearer with the entire channel resources.
If a user is rejected, his user throughput is zero.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
The Statistics tab: The Statistics tab contains the following sections:
- The number and percentage of users connected to a cell, the number of users per activity status, and the
total UL and DL throughputs they generate. These data are also given per service.
The Sites (Average) tab: The Sites (Average) tab contains the following information per site:
- Peak MAC User Throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink in all the cells of the site.
- Effective MAC User Throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the downlink in all the cells of the site.
- Application User Throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink in all the cells of the site.
- Peak MAC User Throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink in all the cells of the site.
- Effective MAC User Throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the uplink in all the cells of the site.
- Application User Throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink in all the cells of the site.
- Peak MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink in all the cells of the site.
- Effective MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the downlink in all the cells of the site.
- Application User Throughput (DL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the downlink in all the cells of the site.
- Peak MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink in all the cells of the site.
- Effective MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the uplink in all the cells of the site.
- Application User Throughput (UL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the uplink in all the cells of the site.
- No Service: The number of users unable to connect to any cell of the site for which the rejection cause was
"No Service."
- Scheduler Saturation: The number of users unable to connect to any cell of the site for which the rejection
cause was "Scheduler Saturation."
- Resource Saturation: The number of users unable to connect to any cell of the site for which the rejection
cause was "Resource Saturation."
The Cells (Average) tab: The Cells (Average) tab contains the following average information, per site and trans-
mitter:
- Traffic Load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation.
- Traffic Load (UL) (%): The traffic loads of the cells calculated on the uplink during the simulation.
- UL Noise Rise (dB): The noise rise of the cells calculated on the uplink during the simulation.
- Segmentation Usage (DL) (%): (WiMAX 802.16e) The percentage of the downlink traffic load that corre-
sponds to the first downlink PUSC zone, if it is segmented.
- AAS Usage (DL) (%): The percentage of downlink traffic load that corresponds to the traffic carried by the
smart antennas.
- AAS Usage (UL) (%): The percentage of uplink traffic load that corresponds to the traffic carried by the smart
antennas.
- AAS Simulation Results: The simulation results generated for transmitters using a smart antenna. The
results stored in this field are the angular distributions of the downlink traffic power spectral density and the
uplink noise rise. You can make the display of the downlink results diagram take into account the effect of the
antenna pattern of the single element. For more information, see the Administrator Manual.
- MU-MIMO Gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO.
- Peak MAC User Throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink.
- Effective MAC User Throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the downlink.
- Application User Throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink.
- Peak MAC User Throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink.
- Effective MAC User Throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the uplink.
- Application User Throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink.
- Peak MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink.
- Effective MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the downlink.
- Application User Throughput (DL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the downlink.
- Peak MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink.
- Effective MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the uplink.
- Application User Throughput (UL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the uplink.
- No Service: The number of users unable to connect to the cell for which the rejection cause was "No Service."
- Scheduler Saturation: The number of users unable to connect to the cell for which the rejection cause was
"Scheduler Saturation."
- Resource Saturation: The number of users unable to connect to the cell for which the rejection cause was
"Resource Saturation."
The Initial Conditions tab: The Initial Conditions tab contains the following information:
Note: If you are importing more than one file, you can select contiguous files by clicking the first
file you want to import, pressing SHIFT and clicking the last file you want to import. You
can select non-contiguous files by pressing CTRL and clicking each file you want to
import.
Note: Files with the extension PLN, as well as some FMT files (created with previous versions of
TEMS) are imported directly into Atoll; you will not be asked to define the data structure
using the Import of Measurement Files dialogue.
6. If you already have an import configuration defining the data structure of the imported file or files, you can select
it from the Configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have
an import configuration, continue with step 7.
a. Under Configuration, select an import configuration from the Configuration list.
b. Continue with step 10.
Notes:
When importing a test mobile data path file, existing configurations are available in the Files
of type list of the Open dialogue, sorted according to their date of creation. After you have
selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises
the extension. In case several configurations are associated with an extension, Atoll chooses
the first configuration in the list.
The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in
the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see
the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters:
- Name: By default, Atoll names the new test mobile data path after the imported file. You can change this
name if desired.
- Under Receiver, set the Height of the receiver antenna and the Gain and Losses.
- Under Measurement Conditions,
- Units: Select the measurement units used.
- Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document.
If the coordinates used in the file you are importing are different than the coordinates used in the Atoll
document, you must click the Browse button ( ) and select the coordinate system used in the test
mobile data file. Atoll will then convert the data imported to the coordinate system used in the Atoll docu-
ment.
8. Click the Setup tab (see Figure 13.61).
Figure 13.61: The Setup tab of the Import of Measurement Files dialogue
a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Dec-
imal Symbol used in the file.
b. Click Setup to link file columns and internal Atoll fields. The Test Mobile Data Configuration dialogue ap-
pears.
c. Select the columns in the imported file that give the X-Coordinates and the Y-Coordinates of each point in
the test mobile data file.
Note: You can also identify the columns containing the XY coordinates of each point in the test
mobile data file by selecting them from the Field row of the table on the Setup tab.
Important: If you have correctly entered the information under File on the Setup tab, and the
necessary values in the Test Mobile Data Configuration dialogue, Atoll should
recognize all columns in the imported file. If not, you can click the name of the column in
the table in the Field row and select the column name. For each field, you must ensure
that each column has the correct data type in order for the data to be correctly interpreted.
The default value under Type is "<Ignore>". Columns marked with "<Ignore>" will not be
imported.
9. If you wish to save the definition of the data structure so that you can use it again, you can save it as an import
configuration:
a. On the Setup tab, under Configuration, click Save. The Configuration dialogue appears.
b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atolls installation folder.
In case you cannot write into that folder, you can click Browse to choose a different location.
c. Enter a Configuration Name and an Extension of the files that this import configuration will describe (for ex-
ample, "*.txt").
d. Click OK.
Atoll will now select this import configuration automatically every time you import a test mobile data path file
with the selected extension. If you import a file with the same structure but a different extension, you can select
this import configuration from the Configuration list.
Notes:
You do not have to complete the import procedure to save the import configuration and have
it available for future use.
When importing a CW measurement file, you can expand the NumMeasINIfile.ini file by clicking
the button ( ) in front of the file in the Setup part to display all the available import configura-
tions. When selecting the appropriate configuration, the associations are automatically made
in the table at the bottom of the dialogue.
You can delete an existing import configuration by selecting the import configuration under
Setup and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The test
mobile data are imported into the current Atoll document.
Notes:
Fast Display forces Atoll to use the lightest symbol to display the points. This is useful when
you have a very large number of points.
You can not use Multiple Shadings if the Fast Display check box has been selected.
You can sort test mobile data paths in alphabetical order on the Data tab of the Explorer window
by right-clicking the Test Mobile Data Path folder and selecting Sort Alphabetically from the
context menu.
You can export the display settings of a test mobile data path in a configuration file to make them
available for future use. You can export the display settings or import display settings by clicking
the Actions button on the Display tab of the test mobile data paths Properties dialogue and
selecting Export or Import from the menu.
Note: You can permanently delete the points located in the clutter classes whose check boxes
you clear by selecting the Delete points outside the filter check box.
b. Underneath the name of each column, enter the criteria on which the column will be filtered as explained in
the following table:
9. Click OK to filter the data according to the criteria you have defined.
Filters are combined first horizontally, then vertically. For more information on filters, see "Advanced Data Filtering"
on page 71.
Note: The Refresh Geo Data option available in the context menu of test mobile data paths
enables you to update heights (Alt DTM, Clutter height, DTM+Clutter) and the clutter class
of test mobile data points after adding new geographic maps or modifying existing ones.
7. When you have finished setting the parameters for the coverage prediction, click OK.
You can create a new coverage prediction by repeating the procedure from step 1. to step 7. for each new cover-
age prediction.
8. When you have finished creating new coverage predictions for these test mobile data, right-click the test mobile
data. The context menu appears.
9. Select Calculations > Calculate All the Studies from the context menu.
A new column for each coverage prediction is added in the table for the test mobile data. The column contains the
predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned
to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Managing Calcu-
lations in Atoll).
You can display the information in these new columns in the Test Mobile Data window. For more information on
the Test Mobile Data window, see "Analysing Data Variations Along the Path" on page 969.
5. Click the Display button at the top of the Test Mobile Data window. The Display Parameters dialogue appears
(see Figure 13.64).
Note: You can change the display status or the colour of more than one field at the same time
by selecting several fields. You can select contiguous fields by clicking the first field,
pressing SHIFT and clicking the last field. You can select non-contiguous fields by
pressing CTRL and clicking each field. You can then change the display status or the
colour by right-clicking on the selected fields and selecting the choice from the context
menu.
The selected fields are displayed in the Test Mobile Data window.
7. You can display the data in the test mobile path in the following ways:
- Click the values in the Test Mobile Data window.
- Click the points on the test mobile path in the map window.
The test mobile data path appears in the map window as an arrow pointing towards the best server (see
Figure 13.63 on page 969) in the same colour as the transmitter.
8. You can display a secondary Y-axis on the right side of the window in order to display the values of a variable with
different orders of magnitude than the ones selected in the Display Parameters dialogue. You select the value to
be displayed from the right-hand list at the top of the Test Mobile Data window. The values are displayed in the
colour defined in the Display Parameters dialogue.
9. You can change the zoom level of the Test Mobile Data window display in the Test Mobile Data window in the
following ways:
- Zoom in or out:
i. Right-click the Test Mobile Data window.
ii. Select Zoom In or Zoom Out from the context menu.
- Select the data to zoom in on:
i. Right-click the Test Mobile Data window on one end of the range of data you want to zoom in on.
ii. Select First Zoom Point from the context menu.
iii. Right-click the Test Mobile Data window on the other end of the range of data you want to zoom in on.
iv. Select Last Zoom Point from the context menu. The Test Mobile Data window zooms in on the data be-
tween the first zoom point and the last zoom point.
10. Click the data in the Test Mobile Data window to display the selected point in the map window. Atoll will recentre
the map window on the selected point if it is not presently visible.
Tip: If you open the table for the test mobile data you are displaying in the Test Mobile Data
window, Atoll will automatically display in the table the data for the point that is displayed
in the map and in the Test Mobile Data window (see Figure 13.63 on page 969).
a. Select Print from the context menu. The Print dialogue appears.
b. Click OK to print the contents of the Test Mobile Data window.
Note: The relationship between the frequency band (spectrum), the channel width, and the
channel numbers can be defined as:
Frequency Band Width = Channel Bandwidth x (Last Channel + 1 - First Channel)
So, if you have a frequency band of 15 MHz, and you are deploying your network with
1.5 MHz allocated to each cell, you can find the First and Last Channel numbers by:
Last Channel - First Channel = (Frequency Band Width / Channel Bandwidth) - 1
If you plan to keep the First Channel number = 0, for our example:
Last Channel = (15 MHz / 1.5 MHz) - 1 = 9
- Excluded Channels: Enter the channel numbers which do not belong to the frequency band.
- Start Frequencies (MHz): Enter the start frequency for TDD frequency bands, and the downlink and the
uplink start frequencies for FDD frequency bands.
- Adjacent Channel Suppression Factor (dB): Enter the adjacent channel interference suppression factor in
dB. Interference received from adjacent channels is reduced by this factor during the calculations.
- Sampling Factor: Enter the sampling factor for converting the channel bandwidth into the sampling fre-
quency.
- Duplexing Method: Select the duplexing method used in the frequency band from the list.
5. When you have finished adding frequency bands, click Close.
You can also access the properties dialogue of each individual frequency band by clicking the Properties button.
Note: The exact number of symbol durations in one frame depends on various parameters
(channel bandwidth, frame duration, cyclic prefix lengths, sampling factor, etc.). Some of
these parameters can be different per cell. Therefore, the exact numbers of symbol
durations in downlink and uplink subframes can be different per cell as well. The exact
numbers of symbol durations in the downlink and uplink subframes are calculated by
Atoll for each cell according to the DL:UL ratio that you set in the Global Parameters. For
example, a DL:UL ratio of 36:12 would actually give 36:12 for a 5 MHz channel (sampling
factor = 1.12 and FFT size = 512) but would give 26:8 for a 7 MHz channel (sampling
factor = 1.14286 and FFT size = 1024) with the following configuration:
Frame Duration = 5 ms
Cyclic Prefix = 1/8
DL Fixed Overhead = UL Fixed Overhead = 0
TTG = RTG = 0 ms
DL:UL Ratio = 36:12
For more information on this calculation, see the Technical Reference Guide.
Transmission and reception time guards (TDD only): Transmission and reception time guards are also time
domain overheads, i.e., these are portions of the frame which cannot be used for data transfer. You can enter TTG
and RTG times in milliseconds.
Uplink power control margin: The margin (in dB) that will be added to the bearer selection threshold, for safety
against fast fading, when performing power control in uplink.
Serving (reference) cell selection method: The reference cell selection method is used for determining the ref-
erence cell in case of transmitters supporting more than one cell. The best serving transmitter for a pixel, sub-
scriber, or mobile is determined according to the received preamble signal level from the cell with the highest
preamble power. If more than one cell of the same transmitter cover the pixel, subscriber, or mobile, the reference
cell is determined according to the selected method:
- Random: In coverage prediction calculations and in calculations on subsriber lists, the cell with the lowest
order is selected as the serving (reference) cell. In Monte Carlo simulations, a random cell is selected as the
serving (reference) cell.
- Sequential: In coverage prediction calculations and in calculations on subsriber lists, the cell with the lowest
order is selected as the serving (reference) cell. In Monte Carlo simulations, cells are selected as serving (ref-
erence) cells for mobiles sequentially (one by one).
- Min DL Traffic Load: (Not implemented yet) The cell with the lowest downlink traffic load is selected as the
serving (reference) cell. If more than one cell has the same lowest downlink traffic load, the first cell among all
such cells is selected. During Monte Carlo simulations, as the cell traffic loads may vary, the serving cell for
mobiles may also change.
- Min UL Traffic Load: (Not implemented yet) The cell with the lowest uplink traffic load is selected as the
serving (reference) cell. If more than one cell has the same lowest uplink traffic load, the first cell among all
such cells is selected. During Monte Carlo simulations, as the cell traffic loads may vary, the serving cell for
mobiles may also change.
The Min DL Traffic Load and Min UL Traffic Load options model load balancing between cells. In coverage
predictions as the probe mobile selects the least loaded cell, i.e., tries to keep the traffic load balanced between
cells of the transmitter. Instead of loading already loaded cells even more, the base station chooses to load the
least loaded among them.
When using either the Random or the Sequential cell selection method, the reference cell once assigned to a
mobile does not change during Monte Carlo simulations.
The following parameters are only available in WiMAX 802.16d documents (based on the WiMAX 802.16d project
template).
Number of subchannels per channel: A channel can be divided into a number of subchannels. You can set the
number of these subchannels at the network level in Atoll.
Number of subcarriers per channel: The entire channel contains a number of subcarriers which compose the
upper and lower guard bands, the pilot subcarriers, and the data subcarriers. The guards, pilots, and the DC sub-
carrier can not be used for data transfer. The total thermal noise over the entire channel bandwidth is computed
according to the number of used subcarriers out of the total number of subcarriers. The used subcarriers are the
data and the pilot subcarriers. The data transfer capacity of a channel is calculated by considering the data sub-
carriers only.
Figure 13.65 depicts a WiMAX frame with the described parameters marked.
- Frame Structure: In this section (see Figure 13.66), you can modify the following: the Frame Duration of
WiMAX frame, the Cyclic Prefix Ratio, the fixed and variable overheads for the uplink and the downlink sub-
frames, and, for TDD networks, the downlink-to-uplink subframe ratio (DL:UL Ratio) either in percentage or
(WiMAX 802.16e only) in fractions of the number of available symbol durations in one frame, and the trans-
mission and reception time guards (TTG and RTG).
The DL:UL ratio entered in fractions must include the symbol duration(s) used by the preamble or any other
fixed-duration overheads. During calculations, Atoll first determines the total amount of resources available
in one frame and then the resources effectively available for user data by removing any fixed and variable
overheads that you have defined.
- Uplink Power Control: In this section, you can enter the uplink power control Margin.
- Serving Cell Selection: In this section, you can choose the serving cell selection Method.
The following section is only available in WiMAX 802.16d documents (based on the WiMAX 802.16d project
template).
- Channel Configuration: In this section, you can enter the following: the number of subchannels per
channel, the total number of subcarriers per channel, the number of used subcarriers per channel and
the number of data subcarriers per channel.
5. Click OK. The global parameters are used during coverage predictions and simulations for the entire network.
Note: Make sure that the permutation zone quality threshold values respect the traffic power
reduction defined for the cell, and whether the frame configuration supports segmentation
or not.
The quality threshold for a permutation zone is calculated in one of two ways:
- For any permutation zone of a frame configuration that does not support segmentation,
or for the segmented permutation zone in a frame configuration that supports segmen-
tation, the quality threshold is calculated as follows:
Quality Threshold (Preamble C/N) = Required Traffic C/N + Traffic Power Reduction
For example, if the required traffic C/N is 15 dB and the traffic power reduction is 3 dB, the
quality threshold for the segmented permutation zone in this case would be 18 dB, and for
a non-segmented permutation zone would be 22.77 dB.
- Max Speed: The maximum vehicular speed supported by the permutation zone.
- Priority: The priority of the permutation zone in terms of its allocation to a user.
- Diversity Support: The type of antenna diversity technique (AAS, STTD/MRC, SU-MIMO, AMS, and MU-
MIMO) supported by the permutation zone. You cannot select more than one type of MIMO technique (STTD/
MRC, SU-MIMO, MU-MIMO, and AMS) at a time.
Specific calculations will be performed (gains will be applied) for terminals supporting AAS and MIMO. A per-
mutation zone that only supports None does not have any antenna diversity mechanism, and all the terminal
types can connect to this zone. A permutation zone that supports None and one or more antenna diversity
techniques can also support terminals capable of those diversity techniques. For example, None+AAS can
support simple as well as AAS-capable terminals, and None+AMS can support simple and MIMO-capable ter-
minals. Simple terminals cannot connect to a permutation zone that does not support None.
- Max Distance: The maximum distance from the base station covered by the permutation zone.
- Subchannel Groups (Segment 0): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned
to the segments 0.
- Subchannel Groups (Segment 1): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned
to the segments 1.
- Subchannel Groups (Segment 2): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned
to the segments 2.
The primary subchannel groups (0, 2, 4) are determined directly from the preamble index and the segment
number. For a list of correspondence between preamble indexes and subchannel groups, and a list of corre-
spondence between subchannels and subchannel groups, see "Glossary of WiMAX Terms" on page 995.
Permutation zones are allocated to users based on the Quality Threshold (dB), Max Speed (km/h), Max Distance, and
Priority parameters. The quality threshold, maximum speed, and maximum distance criteria are used to determine the
possible permutation zones for each user. Then, the highest priority permutation zone among the possible permutation
zones is allocated to the user.
To see examples of how to setup cells with and without segmentation, and how to setup cells with PUSC, FUSC, and
permutation zones of other subchannel allocation modes, see "Tips and Tricks" on page 987.
Note: In the Atoll WiMAX module, a "bearer" refers to a combination of MCS, i.e., modulation,
and coding schemes.
The WiMAX Bearers table lists the radio bearers available in Atoll by default. You can add, remove, and modify bearer
properties, if you wish.
To define WiMAX bearers:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Network Settings > WiMAX Bearers from the context menu. The WiMAX Bearers table appears.
4. In the table, enter one bearer per row. For information on working with data tables, see "Working with Data Tables"
on page 50. For each WiMAX bearer, enter:
- Radio Bearer Index: Enter a bearer index. This bearer index is used to identify the bearer in other tables,
such as the bearer selection thresholds and the quality graphs in WiMAX equipment.
- Name: Enter a name for the bearer, for example, "16QAM3/4." This name will appear in other dialogues and
results.
- Modulation: Select a modulation from the list of available modulation types. This column is for information
and display purposes only.
- Coding Rate: Enter the coding rate used by the bearer. This column is for information and display purposes
only.
- Bearer Efficiency (bits/symbol): Enter the number of useful bits that the bearer can carry in a symbol. This
information is used in throughput calculations.
For information on the relation between bearer efficiency and spectral efficiency, see "Relation Between Bear-
er Efficiency And Spectral Efficiency" on page 990.
- Bearer Selection Thresholds: In this tab (see Figure 13.69), you can modify the Bearer Selection Thresh-
olds for different mobility types. A bearer is selected for data transfer at a given pixel if the received carrier-
to-interference-and-noise ratio is higher than its selection threshold. For more information on bearers and
mobility types, see "Defining WiMAX Radio Bearers" on page 977 and "Modelling Mobility Types" on
page 906, respectively.
i. Click the Best Bearer Thresholds button to open the C/(I+N) Thresholds (dB) dialogue (see
Figure 13.70).
ii. Enter the graph values.
iii. Click OK.
For more information on the default values of the bearer selection thresholds, see "Bearer Selection Thresh-
olds" on page 988. For converting receiver equipment sensitivity values (dBm) into bearer selection thresh-
olds, see "Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 989.
Note: Subscriber lists use the mobility type "Fixed", i.e., 0 km/hr, in calculations. Make sure that
you have bearer selection thresholds defined for this mobility type in the WiMAX
equipment properties if you are working with subscriber lists.
- Quality Graphs: On this tab (see Figure 13.71), you can modify the Quality Indicator Graphs for different
bearers for different mobility types. These graphs depict the behaviour of various quality indicators under dif-
ferent radio conditions. For more information on bearers, quality indicators, and mobility types, see "Defining
WiMAX Radio Bearers" on page 977, "Defining WiMAX Quality Indicators" on page 977, and "Modelling
Mobility Types" on page 906, respectively.
i. Click the Quality Graph button to open the Quality Graph dialogue (see Figure 13.72).
ii. Enter the graph values.
iii. Click OK.
- MIMO: On this tab (see Figure 13.73), you can modify the SU-MIMO and STTD/MRC gains for different
bearers, mobility types, subchannel allocation modes (WiMAX 802.16e), BLER values, and numbers of trans-
mission and reception antennas. The capacity gain due to spatial multiplexing is the increase in channel
capacity compared to a SISO system. For more information on bearers and mobility types, see "Defining
WiMAX Radio Bearers" on page 977 and "Modelling Mobility Types" on page 906, respectively.
For more information on the different MIMO systems, see "Multiple Input Multiple Output Systems" on
page 984.
TX RX
Note: No MIMO gain (STTD/MRC, SU-MIMO, and MU-MIMO) is applied if N Ant = N Ant = 1 .
i. Enter the STTD/MRC Gain for a combination of Subchannel Allocation Mode (WiMAX 802.16e), Mo-
bility, Radio Bearer Index, Max BLER, Number of Transmission Antennas, and Number of Recep-
tion Antennas.
ii. Click the Max SU-MIMO Gain Graphs button to open the Max SU-MIMO Gain dialogue for a combination
of Subchannel Allocation Mode (WiMAX 802.16e), Mobility, Radio Bearer Index, Max BLER, Number
of Transmission Antennas, and Number of Reception Antennas (see Figure 13.74).
iii. Enter the graph values.
iv. Click OK.
You can define the STTD/MRC and SU-MIMO gains for a specific combination of subchannel allocation mode,
mobility type, bearer, and BLER, as well as the default gains for "All" subchannel allocation modes, "All" mobility
types, "All" bearers, and a Max BLER of 1. During calculations, Atoll uses the gains defined for a specific combi-
nation if available, otherwise it uses the default gains.
6. Click OK. The Properties dialogue closes. The settings are stored.
7. Click the Close button ( ) to close the WiMAX Equipment table.
3. Resource allocation for supporting the Max Throughput Demands: Once the resources have been allocated
for supporting the minimum throughput demands in the previous step, the remaining resources can be allocated
in different ways to support the maximum throughput demands of the users. The last four QoS classes can have
maximum throughput demand requirements.
For allocating resources to support the maximum throughput demands, the following types of scheduling methods
are available:
- Proportional Fair: The proportional fair scheduling method allocates the same amount of resources to all the
users with a maximum throughput demand. Therefore, the resources allocated to each user are either the
resources it requires to achieve its maximum throughput demand or the total amount of resources divided by
the total number of users in the cell, which ever is smaller.
- Proportional Demand: The proportional demand scheduling method allocates resources proportional to the
demands of users who have a maximum throughput demand. Therefore, users with higher maximum
throughput demands will have higher resulting throughputs than the users with lower maximum throughput
demands.
- Biased (QoS Class): The biased scheduling method first determines the amount of resources available for
the users of each QoS class, and then allocates these resources among the users of each QoS class like a
proportional fair scheduler. The percentage of the remaining resources that are available for any QoS class is
determined based on the QoS Class Bias Factor and the priorities of the QoS classes:
1 i
N i ---
% of resources available for QoS Class i = ----------------------------------- 100
i
N 1 ---
i
i
Where i represents the QoS classes that have a maximum throughput demand, i.e., ErtPS (i = 1), rtPS (i = 2),
nrtPS (i = 3), and Best Effort (i = 4). N i is the number users of QoS class i, and is the QoS class bias de-
QoS
QoS f Bias
termined from the QoS Class Bias Factor f Bias as follows: = 1 + ----------
-.
100
Note: The QoS Class Bias Factor should be set so as to achieve a valid value of . For
example, for equal numbers of users in each QoS class,
QoS
- f Bias = 90 gives = 0.1 which allocates (approximately):
QoS
- f Bias = 9900 gives = 100 which allocates (approximately):
- Max Aggregate Throughput: This scheduling method allocates the resources required by the users to
achieve their maximum throughput demands in the order of their traffic C/(I+N). This means that users who
are under good radio conditions, high traffic C/(I+N), will get all the resources they require. The end result of
this scheduling method is that the aggregate cell throughputs are maximised.
For all the scheduling methods, resources are allocated to support the maximum throughput demand until either
the maximum throughput demands of all the users are satisfied or the scheduler runs out of resources.
The Schedulers table lists the schedulers available in Atoll by default. You can add, remove, and modify scheduler prop-
erties, if you wish.
To define WiMAX schedulers:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Network Settings > Schedulers from the context menu. The Schedulers table appears.
4. In the table, enter one scheduler per row. For information on working with data tables, see "Working with Data
Tables" on page 50. For each scheduler, enter:
- Name: Enter a name for the scheduler. This name will appear in the cell properties.
- Scheduling Method: Select the scheduling method used by the scheduler for allocating resources to support
the maximum throughput demands.
- QoS Class Bias Factor: For the schedulers using Biased (QoS Class) scheduling method, enter the bias
factor to be used for distributing resources between different QoS classes. QoS Class Bias Factor = 0 means
no bias.
- Target Throughput for Voice Services: Select the throughput that the scheduler will target to satisfy for all
voice-type services.
- Target Throughput for Data Services: Select the throughput that the scheduler will target to satisfy for all
data-type services.
5. Click the Close button ( ) to close the Schedulers table.
Atolls WiMAX BWA module includes the following smart antenna modelling types:
"Optimum Beamformer" on page 983.
"Conventional Beamformer" on page 983.
The following section explains how to work with smart antenna equipment in Atoll:
"Defining Smart Antenna Equipment" on page 983.
In the uplink, the powers received from served mobiles include the beamforming gains in their directions. For
taking into account the interfering mobiles, an inverse noise correlation matrix is calculated for each cell. Interfer-
ence cancellation is modelled using the MMSE adaptive algorithm. For each pair of interfered and interfering
users, the received interference and its direction are memorised. At the end of a simulation, this results in an angu-
lar distribution of the uplink noise rise calculated from the inverse noise correlation matrix.
The smart antenna simulation results include the angular distribution of the transmitted power spectral density
(downlink) and the angular distribution of the noise rise (uplink) for each cell. These results are then used to carry
out CINR-based coverage predictions for base stations using smart antennas.
In uplink, beamforming is performed to calculate the smart antenna gain towards each pixel of the studied cell
dynamically in order to determine the received power. The interference is read from the angular distribution of the
uplink noise rise (simulation result) calculated for the studied cell.
In the uplink, the powers received from served mobiles include the beamforming gains in their directions. For
taking into account the interfering mobiles, an inverse noise correlation matrix is calculated for each cell. For each
pair of interfered and interfering users, the received interference and its direction are memorised. At the end of a
simulation, this results in an angular distribution of the uplink noise rise calculated from the inverse noise correla-
tion matrix.
The smart antenna simulation results include the angular distribution of the transmitted power spectral density
(downlink) and the angular distribution of the noise rise (uplink) for each cell. These results are then used to carry
out CINR-based coverage predictions for base stations using smart antennas.
In uplink, beamforming is performed to calculate the smart antenna gain towards each pixel of the studied cell
dynamically in order to determine the received power. The interference is read from the angular distribution of the
uplink noise rise (simulation result) calculated for the studied cell.
Error) optimum beamformer. For more information on these smart antenna models in Atoll, see the Technical Reference
Guide
To create a smart antenna equipment:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Equipment > Smart Antenna Equipment from the context menu. The Smart Antenna Equipment table
appears.
4. In the Smart Antenna Equipment table, each row describes a piece of smart antenna equipment. For information
on working with data tables, see "Working with Data Tables" on page 50. For the new smart antenna equipment,
enter:
- Name: Enter a name for the smart antenna equipment.
- Antenna Model: Select Optimum Beamformer or Conventional Beamformer from the list.
- Main Antenna Model: Select the main antenna model to be used with the smart antenna equipment. The list
contains the antennas available in the Antennas folder. When you assign the smart antenna equipment to a
transmitter, you can choose to replace the current main antenna model with this model.
5. Click the Properties button. The smart antenna properties dialogue appears.
In the smart antenna properties dialogue you can modify the smart antenna equipment properties. You can also
modify the properties of the model.
a. Click the Parameters button. The smart antenna models properties dialogue appears.
b. Click the General tab. On the General tab, you can change the default Name of the smart antenna model.
c. Click the Properties tab (see Figure 13.75). On the Properties tab, you can define:
- Number of Elements: The number of antenna elements in the smart antenna system.
- Single Element Pattern: The antenna model to be used for each antenna element. You can select an
antenna model from the list. The list contains the antennas available in the Antennas folder.
STTD uses more than one transmission antenna to send more than one copy of the same signal. The signals are construc-
tively combined (using optimum selection or maximum ratio combining, MRC) at the receiver to extract the useful signal.
As the receiver gets more than one copy of the useful signal, the signal level at the receiver after combination of all the
copies is more resistant to interference than a single signal would be. Therefore, STTD improves the C/(I+N) at the
receiver. It is often used for the regions of a cell that have bad C/(I+N) conditions. STTD is also known as STC (Space
Time Coding) and STBC (Space-Time Block Codes).
In Atoll, you can set whether a cell (WiMAX 802.16d) or a permutation zone (WiMAX 802.16e) supports STTD/MRC by
selecting the corresponding diversity support mode in cell properties (see "Cell Description" on page 872) or frame config-
uration properties (see "Defining Frame Configurations" on page 975), respectively. STTD/MRC gains on downlink and
uplink can be defined in the WiMAX equipment for different numbers of transmission and reception antennas, mobility
types, bearers, subchannel allocation modes (WiMAX 802.16e), and maximum BLER. For more information on uplink and
downlink STTD/MRC gains, see "Defining WiMAX Equipment" on page 978. Additional gain values can be defined per
clutter class. For information on setting the additional STTD/MRC uplink and downlink gains for each clutter class or for
all clutter classes, see "Defining Clutter Class Properties" on page 115.
During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell
(uplink or downlink permutation zone in WiMAX 802.16e) that supports STTD/MRC, will benefit from the downlink and
uplink STTD/MRC C/(I+N) gains.
SU-MIMO uses more than one transmission antenna to send different signals (data streams) on each antenna. The
receiver can also have more than one antenna for receiving different signals. Using spatial multiplexing with M transmis-
sion and N reception antennas, the throughput over the transmitter-receiver link can be theoretically increased M or N
times, depending on which is smaller, M or N. SU-MIMO improves the throughput (channel capacity) for a given C/(I+N),
and is used for the regions of a cell that have sufficient C/(I+N) conditions. SU-MIMO (single-user MIMO) is also referred
to as SM (spatial multiplxing) or simply MIMO.
In Atoll, you can set whether a cell (WiMAX 802.16d) or a permutation zone (WiMAX 802.16e) supports SU-MIMO by
selecting the corresponding diversity support mode in cell properties (see "Cell Description" on page 872) or frame config-
uration properties (see "Defining Frame Configurations" on page 975), respectively. SU-MIMO capacity gains can be
defined in the WiMAX equipment for different numbers of transmission and reception antennas, mobility types, bearers,
subchannel allocation modes (WiMAX 802.16e), and maximum BLER. For more information on SU-MIMO gains, see
"Defining WiMAX Equipment" on page 978.
During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell
(uplink and downlink permutation zones in WiMAX 802.16e) that supports SU-MIMO, will benefit from the SU-MIMO gain
in its throughput depending on its traffic C/(I+N).
As SU-MIMO improves the channel capacity or throughputs, the traffic C/(I+N) of a user is first determined. Once the traffic
C/(I+N) is known, Atoll calculates the user throughput based on the bearer available at the user location. The obtained
user throughput is then increased according to the SU-MIMO capacity gain and the SU-MIMO Gain Factor of the users
clutter class. The capacity gains defined in Max SU-MIMO Gain graphs are the maximum theoretical capacity gains using
SU-MIMO. SU-MIMO requires rich multipath environment, without which the gain is reduced. In the worst case, there is
no gain. Therefore, it is possible to define an SU-MIMO Gain Factor per clutter class whose value can vary from 0 to 1 (0
= no gain, 1 = 100 % gain). For information on setting the SU-MIMO Gain Factor for each clutter class or for all clutter
classes, see "Defining Clutter Class Properties" on page 115.
The SU-MIMO capacity gain vs. C/(I+N) graphs available in Atoll by default have been generated based on the maximum
theoretical SU-MIMO capacity gains obtained using the following equations:
CC MIMO
G MIMO = ---------------------
-
CC SISO
TX RX C (I + N)
Where CC MIMO = Min ( N Ant, N Ant ) Log 2 1 + ------------------------------------------ is the channel capacity at a given C/(I+N) for a MIMO
TX RX
Min ( N Ant, N Ant )
TX RX
system using N Ant transmission and N Ant reception antenna ports. CC SISO = Log 2 ( 1 + C ( I + N ) ) is the channel
capacity for a single antenna system at a given C/(I+N). C/(I+N) is used as a ratio (not dB) in these formulas. You can
replace the default SU-MIMO capacity gain graphs with graphs extracted from simulated or measured values.
This is a technique for switching from SU-MIMO to STTD/MRC as the preamble signal conditions get worse than a given
threshold. AMS can be used in cells to provide SU-MIMO gains to users that have better preamble C/N conditions than a
given AMS threshold, and STTD/MRC gains to users that have worse preamble C/N conditions than the threshold. AMS
provides the optimum solution using STTD/MRC and SU-MIMO features to their best.
During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell
(uplink and downlink permutation zones in WiMAX 802.16e) that supports AMS, will benefit from the gain to be applied,
STTD/MRC or SU-MIMO, depending on the users preamble C/N and the AMS threshold defined in the cell properties.
STTD/MRC gain is applied to the users traffic C/(I+N) if the users preamble C/N is less than the AMS threshold, and SU-
MIMO is used if the preamble C/N is higher than the AMS threshold.
MU-MIMO (Multi-User MIMO) or Collaborative MIMO is a technique for spatially multiplexing more than one user who have
good enough radio conditions at their locations. This technique is used in uplink so that a cell with more than one reception
antenna can receive uplink transmissions from two different users over the same frequency-time allocation. This technique
provides considerable capacity gains in uplink, and can be used with single-antenna user equipment, i.e., it does not
require more than one antenna at the user equipment as opposed to SU-MIMO, which only provides considerable gains
with more than one antenna at the user equipment.
In Atoll, you can set whether a cell (WiMAX 802.16d) or an uplink permutation zone (WiMAX 802.16e) supports MU-MIMO
in uplink by selecting the corresponding diversity support mode in cell properties (see "Cell Description" on page 872) or
frame configuration properties (see "Defining Frame Configurations" on page 975), respectively. MU-MIMO capacity gains
result from the scheduling and RRM process. Using MU-MIMO, schedulers are able to allocate resources over two
spatially multiplexed parallel frames in the same frequency-time resource allocation plane. MU-MIMO can only work under
good radio conditions and if the cell has more than one reception antenna. Therefore, the preamble C/N must be higher
than the MU-MIMO threshold defined by cell in order for the scheduler to be able to multiplex users in uplink.
During the calculations of Monte Carlo simulations in Atoll, each new user connected to the first antenna creates virtual
resources available on the second antenna. These virtual resources can then be allocated to a second user connected to
the second antenna without increasing the overall load of the cell. In this way, each new mobile consumes the virtual
resources made available be the previous mobile, and may create new virtual resources available on the other antenna.
The MU-MIMO gain resulting from this uplink collaborative multiplexing is simply the ratio of the traffic loads of all the
mobiles connected to both parallel frames in uplink to the uplink traffic load of the cell. MU-MIMO is only possible for
mobiles that support MIMO and at which the preamble C/N is greater than the MU-MIMO threshold defined for their serving
cell. The MU-MIMO gain can be defined per cell by the user or it can be an output of the Monte Carlo simulations. This
gain is used during the calculation of uplink throughput coverage predictions. The channel throughput is multiplied by this
gain for pixels where MU-MIMO is used as the diversity mode.
Important: This procedure is only recommended if you have a correct subscriber list and have
complete knowledge of the services they use.
Atoll generates a realistic user distribution containing active users only during Monte Carlo simulations. The status of
these users is determined through the users service usage parameters defined in the user profile. In Atoll, all the subscrib-
ers have a user profile assigned to them. During Monte Carlo simulations based on subscriber lists, Atoll determines
active users from all the users in the subscriber list. If you perform calculations on subscriber lists, Atoll calculates the
channel throughputs and not the user throughputs as resource allocation is not performed in these calculations. However
in the simulations, RRM and resource allocation is carried out user throughputs can be determined.
If you want to determine user level throughputs for all the subscribers in a subscriber list, you can run a simulation on this
subscriber list after modifying the user profiles assigned to all the subscribers such that all the subscribers have an activity
probability of 100 %.
1. Create a subscriber list with subscribers having an activity probability of 100 %:
a. Create as many user profiles as there are services used by the subscribers in the list.
b. Assign only one service to each user profile.
c. Assign the following service usage parameters to the user profiles that you create:
i. For Voice services, set:
- Calls/Hour = 1.
- Duration (sec.) = 3600.
ii. For Data services:
- Calls/Hour = 1.
- UL Volume (KBytes) = UL Average Throughput x 3600 / 8.
- DL Volume (KBytes) = DL Average Throughput x 3600 / 8.
Where the UL Average Throughput and the DL Average Throughput are the uplink and downlink average
requested throughputs, respectively, of the service mentioned in the user profile.
The simulation results will contain all the subscribers in the subscriber list with their respective user throughputs
determined by Atoll after the scheduling process.
If you do not currently have reliable LTE multi-service traffic, you can provide Atoll with user density information per serv-
ice, for example, traffic data from adapted GSM Erlang maps. In this case, you do not have to create user profiles. As well,
Atoll does not have to determine the user activity probabilities to create traffic scenarios during simulations. The distribu-
tion of traffic during simulations will only depend on the user densities per service.
If you know the user densities for each service, you can set user activity probabilities to 100 % in your LTE document, as
shown below:
1. For Voice services, set:
- Calls/Hour = 1.
- Duration (sec.) = 3600.
2. For Data services:
- Calls/Hour = 1.
- UL Volume (KBytes) = UL Average Throughput x 3600 / 8.
- DL Volume (KBytes) = DL Average Throughput x 3600 / 8.
Where the UL Average Throughput and the DL Average Throughput are the uplink and downlink average re-
quested throughputs, respectively, of the service defined in the user profile.
The above settings will set the user activity probabilities to 100 %. If you create a traffic map based on environment
classes, the user density values that you define in your environment classes will be the actual user densities. This means
that, for X users/km defined in the environment class for a given user profile, the Monte Carlo simulator will generate
exactly X users/km for each service of the user profile.
In this way, you can know the exact number of active users and their services generated during the simulations before-
hand.
This procedure should only be used when appropriate traffic data is not available.
In WiMAX, and especially in IEEE 802.16d networks, it might be interesting to study the areas with LOS coverage only
and other areas separately. You can restrict the coverage to LOS areas only if you are using the Standard Propagation
Model. To restrict coverage to LOS areas, you have to enter a very high value for the parameter K4 in the properties of the
Standard Propagation Model.
You can define a maximum coverage range for all the transmitters in your network by entering a valid range as the Max
Range parameter.
To define the Max Range parameter:
1. Right-click the Predictions folder. The context menu appears.
2. Select Properties from the context menu. The Predictions folders properties dialogue appears.
3. Select the System tab.
4. Select the Max Range check box. The Max Range field in enabled.
5. Enter the Max Range of the network.
6. Click OK.
In TDD networks, the TTG and RTG parameters, available in the Global Parameters tab of the Transmitters folders prop-
erties dialogue, define the time delays required by the cell and mobile equipment to switch from transmission to reception
modes and vice versa. You can determine the maximum coverage range that the sectors of your WiMAX network should
have from the values of TTG and RTG and use this range as the Max Range parameter. You can calculate the maximum
system range from TTG and RTG values as follows:
Max Range (m) = Min(TTG, RTG) x 300000/2
Where TTG and RTG are values in milliseconds, Max Range is in meters, and the Min() function returns the lower of the
two values given to it in the parentheses. So, the maximum system range for TTG = 0.105 ms and RTG = 0.06 ms will be
9 km.
The default values of the bearer selection thresholds, the BLER quality graphs, and the bearer efficiency values in Atoll
have been extracted and estimated from the NS2 simulator results available with the WiMAX Forum (see Figure 13.77 and
Figure 13.78). These values correspond to to an ideal (AWGN) radio channel, and are too optimistic compared to real radio
channels. It is recommended to use more realistic values when available.
The spectral efficiency is the number of useful data bits that can be transmitted using any modulation and coding scheme
per Hz, the transition points between any two modulation and coding schemes give the default bearer selection thresholds
in Atoll, and the normalised values from the slopes of the graphs, that represent the reduction in the spectral efficiency,
give the block error rate.
You can convert the receiver sensitivity values, that are listed in the specifications of your equipment, into bearer selection
thresholds using the following conversion method:
n BW N Used
CNR = RS + 114 NF 10 Log ------------------------------------------ + 10 Log ( R ) L Imp
N Total
Where RS is the receiver sensitivity in dBm, NF is the noise figure of the receiver in dB, n is the sampling factor, BW is the
channel bandwidth in MHz, N Used is the number of used subcarriers, N Total is the total number of subcarriers, R is the
number of retransmissions, and L Imp is the implementation loss in dB.
If you do not know the values for R and L Imp , you can ignore the corresponding terms and simplify the equation.
In the above explanation, the term receiver refers to the base station in uplink and to the mobile/user equipment in the
downlink.
Spectral efficiency of a modulation and coding scheme is defined as the number of useful bits that can be transmitted each
second over a channel of 1 Hz bandwidth. Spectral efficiency is hence given in terms of bps/Hz.
In Atoll, the efficiency of bearers (modulation and coding schemes) are defined in the Bearers table. The bearer efficiency
is given in terms of bits/symbol. Remember that in Atoll a symbol refers to the data transmission unit which is 1 symbol
duration long and 1 subcarrier width wide, as shown in Figure 13.79.
The concept of bearer efficiency is similar to spectral efficiency. The only difference is in the units used to define the two
entities. Here is a simple example that compares spectral efficiency and bearer efficiency, and shows that the two are the
same.
Spectral efficiency is given by:
Where BLER is the Block Error Rate, r is the coding rate for the bearer, and M is the number of modulation states. For
simplification, we set BLER = 0, and use QPSK1/2, i.e., four modulation states and r = 0.5. With these values, we get a
spectral efficiency of 1 bps/Hz for QPSK1/2. In other words, a communication channel using QPSK1/2 modulation and
coding scheme can send 1 bps of useful data per unit bandwidth.
In order to compare the bearer efficiency and spectral efficiency of QPSK1/2, lets say that QPSK1/2 has a bearer effi-
ciency of 1 bits/symbol. Here as well, the number of bits refers to useful data bits. The width of a subcarrier in WiMAX
1
802.16e is F = 10.94 kHz , from which we can calculate the useful symbol duration as well: T U = ------- = 91.4 sec .
F
In one second, there can be 1 sec 91.4 sec = 10940 symbol durations. If 10940 symbols are transmitted using
QPSK1/2, this gives us a data rate of 10940 Symbols/sec 1 bits/Symbol = 10940 bps , which is the data rate achieva-
ble using one subcarrier of 10.94 kHz. We can find the spectral efficiency by normalizing the data rate to unit bandwidth.
This gives: 10940 bps/subcarrier 10.94 kHz/subcarrier = 1 bps/Hz
In order to compare equivalent quantities, we have ignored the system parameters such as the cyclic prefix, TTG, RTG,
and have considered that the entire frame is transmitted in one direction, uplink or downlink.
In TDD networks, the durations of the downlink and uplink subframes have to be properly set in order to optimally satisfy
the traffic demands in both downlink and uplink. You can use the simulation results to calculate the approximate value of
the DL:UL Ratio required for your network under the given traffic scenario of the simulation. The DL:UL Ratio can be
calculated by taking the ratio of the sum of the downlink traffic loads of all the cells and the sums of all the downlink and
uplink traffic loads of all the cells. The downlink and uplink traffic loads of all the cells are listed in the Cells tab of the simu-
lations results dialogue.
DL
TL
All Cells
DL:UL Ratio = ------------------------------------------------------------------
-
DL UL
TL + TL
All Cells All Cells
You can then set this value of DL:UL Ratio in the Global Parameters tab of the Transmitters folders properties dialogue,
for optimising your networks resource usage.
iii. Double-click the frame configuration FFT Size 512. The Permutation Zones table appears.
iv. Activate the permutation zones 0 (PUSC DL) and 8 (PUSC UL).
v. Click OK.
vi. Close the Frame Configurations tables.
b. Set up the cells:
i. Right-click the Transmitters folder. The context menu appears.
ii. Select Cells > Open Table from the context menu. The Cells table appears.
iii. In the Cells table, enter:
- Channel Number: 0
- Frame Configuration: FFT Size 512
iv. Close the Cells table.
c. Create a coverage by downlink traffic C/(I+N) level and a coverage by downlink channel throughput as ex-
plained in "Making a Coverage by C/(I+N) Level" on page 910 and "Making a Coverage by Throughput" on
page 914, respectively.
In this case, the same 5 MHz channel is allocated to the three sectors of each 3-sector site. The sectors receive
co-channel interference according to the downlink traffic loads of the interferers. The traffic C/(I+N) and throughput
coverage predictions would be as shown in Figure 13.80 and Figure 13.81.
Figure 13.80: Downlink Traffic C/(I+N) Coverage Prediction - PUSC Without Segmentation
Figure 13.81: Downlink Channel Throughput Coverage Prediction - PUSC Without Segmentation
2. With a segmented PUSC permutation zone, i.e., a frequency reuse plan of N=3.
a. Set up the frame configuration:
i. Open the Frame Configurations table as explained in "Defining Frame Configurations" on page 975.
ii. Select the Segmentation Support check box for FFT Size 512.
iii. Double-click the frame configuration FFT Size 512. The Permutation Zones table appears.
iv. Activate the permutation zones 0 (PUSC DL) and 8 (PUSC UL).
v. Click OK.
vi. Close the Frame Configurations tables.
b. Set up the cells:
i. Right-click the Transmitters folder. The context menu appears.
ii. Select Cells > Open Table from the context menu. The Cells table appears.
iii. In the Cells table, enter:
- Channel Number: 0
- Frame Configuration: FFT Size 512
- Preamble Index: 0 for the 1st sector, 32 for the 2nd sector, and 64 for the 3rd sector of each 3-sector site.
- Segmentation Usage (DL) (%): 100%
iv. Close the Cells table.
c. Create a coverage by downlink traffic C/(I+N) level and a coverage by downlink channel throughput as ex-
plained in "Making a Coverage by C/(I+N) Level" on page 910 and "Making a Coverage by Throughput" on
page 914, respectively.
In this case, the 5 MHz channel is divided into 3 segments. Each segment is allocated to one of the three sectors
of each 3-sector site. There is no interference between segments because the Preamble Indexes give a different
segment and same Cell PermBase (IDCell in IEEE specifications). Each segment uses 1/3rd of the total number
of used subcarriers, i.e., 140. The traffic C/(I+N) and throughput coverage predictions would be as shown in
Figure 13.82 and Figure 13.83.
Figure 13.82: Downlink Traffic C/(I+N) Coverage Prediction - PUSC With Segmentation
Figure 13.83: Downlink Channel Throughput Coverage Prediction - PUSC With Segmentation
3. With a segmented PUSC permutation zone and one or more non-segmented zones, i.e., a frequency reuse plan
of pseudo-N=3.
a. Set up the frame configuration:
i. Open the Frame Configurations table as explained in "Defining Frame Configurations" on page 975.
ii. Select the Segmentation Support check box for FFT Size 512.
iii. Double-click the frame configuration FFT Size 512. The Permutation Zones table appears.
iv. Activate the permutation zones 0 (PUSC DL), 2 (FUSC) and 8 (PUSC UL).
v. Click OK.
vi. Close the Frame Configurations tables.
b. Set up the cells:
i. Right-click the Transmitters folder. The context menu appears.
ii. Select Cells > Open Table from the context menu. The Cells table appears.
iii. In the Cells table, enter:
- Channel Number: 0
- Frame Configuration: FFT Size 512
- Preamble Index: 0 for the 1st sector, 32 for the 2nd sector, and 64 for the 3rd sector of each 3-sector site.
iv. Close the Cells table.
c. Allocate different segmentation usage ratios to the cells:
- Enter different segmentation usage ratios manually in the Cells table, or calculate the segmentation usage
ratios for all the cells using a Monte Carlo simulation as follows:
Create or import a traffic map, as explained in "Creating a Traffic Map" on page 937, to be used as input
to the Monte Carlo simulator.
Create a new Monte Carlo simulation as explained in "Creating Simulations" on page 952.
Open the simulation results, and commit the results to the Cells table as explained in "Updating Cell Load
Values With Simulation Results" on page 962.
d. Create a coverage by downlink traffic C/(I+N) level and a coverage by downlink channel throughput as ex-
plained in "Making a Coverage by C/(I+N) Level" on page 910 and "Making a Coverage by Throughput" on
page 914, respectively.
In this case, the 5 MHz channel is divided into 3 segments. Each segment is allocated to one of the three sectors
of each 3-sector site. There is no interference between segments because the Preamble Indexes give a different
segment and same Cell PermBase (IDCell in IEEE specifications). Each segment uses 1/3rd of the total number
of used subcarriers, i.e., 140. However, there is also a non-segmented FUSC permutation zone, which uses the
entire channel width of 5 MHz. The sectors receive co-channel interference during the FUSC part of the frame but
not during the segmented PUSC part of the frame. The traffic C/(I+N) and throughput coverage predictions would
be as shown in Figure 13.84 and Figure 13.85.
Figure 13.84: Downlink Traffic C/(I+N) Coverage Prediction - Segmented PUSC + FUSC
Figure 13.85: Downlink Channel Throughput Coverage Prediction - Segmented PUSC + FUSC
If you compare the traffic C/(I+N) and throughput coverage predictions in the above cases, you will observe that the traffic
C/(I+N) improves with segmentation, but the throughput is reduced.
VoIP codecs are application-layer elements in the OSI system model. Atoll models application throughputs using a
throughput offset and a scaling factor with respect to the MAC layer throughputs. You can model different VoIP codecs by
creating a new service for each VoIP codec, and setting the target throughput to the Application Throughput for the
scheduler used. Here are two examples of the most common VoIP codecs, and how they can be modelled in Atoll:
G.711 VoIP Codec
The actual voice data rate needed by the G.711 codec is 64 kbps, but with the lower layer headers and other
added bits, the needed MAC data rate could be between 66.4 and 107.2 kbps. In this example, we show how to
model the codec with header bits that lead to 85.6 kbps MAC data rate.
b. Set the Target Throughput for Voice Services to "2 - Application Throughput" for the scheduler being used.
In this way, Atoll will allocate resources to the users of this service such that they get 64 kbps application through-
put, and around 85.6 kbps of effective MAC throughput.
There are four types of AMC subchannels. The four types of AMC subchannels have different collections of bins in a band.
In the first type (6 x 1; default type), a subchannel consists of six consecutive bins in the same symbol. A subchannel is
two bins by three symbols in the second type (2 x 3), three bins by two symbols in the third type (3 x 2), and one bin by six
symbols in the fourth type (1 x 6). The default values of the numbers of subchannels per channel represent the first
(default) type of subchannels. The number of subchannels per channel is calculated by dividing the total number of subcar-
riers by the number of subcarriers in a subchannel. The number of subcarriers per subchannel is 54, 27, 18, and 9 in the
first (default), second, third, and fourth types, respectively. Therefore, for modelling a type of subchannels other than the
default (6 x 1), you will have to increase the number of subchannels per channel accordingly, i.e., multiply the current value
by 2, 3, and 6, for modelling the second, third, and fourth types, respectively.
In Atoll, you can study the effect of interference received by your network from other WiMAX networks. The interfering
WiMAX network can be a different part of your own network, or a network belonging to another operator.
To study interference from co-existing networks:
1. Import the interfering network data (sites, transmitters, and cells) in to your document as explained in "Creating a
Group of Base Stations" on page 881.
2. For the interfering networks transmitters, set the Transmitter Type to Extra-Network (Interferer Only) as
explained in "Transmitter Description" on page 870.
During calculations, Atoll will consider the transmitters of type Extra-Network (Interferer Only) when calculating
interference. These transmitters will not serve any pixel, subscriber, or mobile, and will only contribute to interfer-
ence.
Modelling the interference from co-existing networks will be as accurate as the data you have for the interfering network.
If the interfering network is a part of your own network, this information would be readily available. However, if the inter-
fering network belongs to another operator, the information available might not be accurate.
Moreover, for other operators networks, and if the interfering networks use OFDM but are not WiMAX networks,, you will
have to create specific frame configurations to assign to the cells of the interfering network. The number of subcarriers
used in these frame configurations would depend on the channel bandwidth on which transmitter is interfering. For more
information on frame configuration parameters, see "Defining Frame Configurations" on page 975.
Effective MAC Throughput: The net MAC layer throughput (user or channel) that can be achieved at a given
location using the highest WiMAX bearer available computed taking into account the reduction of throughput due
to retransmission due to errors.
Application Throughput: The application layer throughput (user or channel) that can be achieved at a given loca-
tion using the highest WiMAX bearer available computed taking into account the reduction of throughput due to
PDU/SDU header information, padding, encryption, coding, and other types of overhead.
Channel Throughputs: Peak MAC, effective MAC or application throughputs achieved at a given location using
the highest WiMAX bearer available with the entire cell resources (uplink or downlink).
User Throughputs: Peak MAC, effective MAC or application throughputs achieved at a given location using the
highest WiMAX bearer available with the amount of resources allocated to a user by the scheduler.
Traffic Loads: The uplink and downlink traffic loads are the percentages of the uplink and the downlink subframes
in use (allocated) to the traffic (mobiles) in the uplink and in the downlink, respectively.
Uplink Noise Rise: Uplink noise rise is a measure of uplink interference with respect to the uplink noise.
I UL + N UL
NR UL = ------------------------
-
N UL
Frame Configuration: A frame configuration is the description of a frame in the frequency as well as in the time
dimension. In the frequency domain, it defines how many subcarriers exist in the channel width used, and how
many of these subcarriers are used and for which purpose, i.e., pilot, data, DC, guard. In the time domain, it
defines how long the frame is, and its composition. The time-domain composition of the frame is simpler in WiMAX
802.16d than in 802.16e.
In WiMAX 802.16d networks, the frame configuration does not depend on the channel width and can be defined
in the Global Parameters tab of the Transmitters folders properties dialogue as explained in "The Options on the
Global Parameters Tab" on page 972.
In WiMAX 802.16e, the frame configuration depends on the channel width because the system uses Scalable
OFDMA. The IEEE specifications define different frame configurations for different channel widths. For example,
a cell using a 10 MHz channel width will have 1024 subcarriers, but one using a 5 MHz channel will have 512. As
well, in the time domain, the number of active permutation zones in the frame and the subchannel allocation
modes of these zones depend on the operator and the equipment used. You can create or modify frame configu-
rations and their corresponding permutation zones in Atoll as explained in "Defining Frame Configurations" on
page 975.
Permutation Zone: A permutation zone is a subdivision of a WiMAX frame in the time domain. According to the
IEEE specifications, there can be as many as 8 permutation zones in the downlink and 3 in the uplink. Each per-
mutation zone can use a different subchannel allocation mode (or a permutation scheme), and can have different
numbers of used, pilot, and data subcarriers. The different subchannel allocation modes are: PUSC, FUSC,
OFUSC, AMC, TUSC1, and TUSC2 in downlink, and PUSC, OPUSC, and AMC in uplink.
Segmentation: The PUSC subchannel allocation mode in downlink allows the allocation of groups of subchannels
to cells. According to the IEEE specifications, there are 6 subchannel groups in the downlink PUSC subchannel
allocation mode. You can, for example, use 2 subchannel groups at each sector of a 3-sector site, and completely
eliminate interference between these sectors by setting the preamble index parameter correctly. On one hand,
segmentation improves the CINR by allowing you to different segments of the same channel at different sectors.
But on the other hand, it reduces the available cell capacity (throughput) because the channel width used at each
sector is reduced. For examples on how to use segmentation in Atoll, see "Tips and Tricks" on page 987.
Primary and Secondary Subchannel Groups: For frame configurations with 1024 and 2048 total subcarriers,
you can choose which secondary subchannel groups are used at cells along with the one primary subchannel
group, which is given by the preamble index of the cell. Frame configurations with 128 and 512 total subcarriers
only have primary subchannel groups and no secondary subchannel groups. Therefore, the knowledge of only the
preamble index is sufficient in these cases (each segment uses 1/3rd of the channel bandwidth.)
The preamble index set in the cell gives the segment number as well as the primary subchannel group number in
the case of segmentation:
Primary
Preamble Index Segment Subchannel
Group
0-31, 96, 99, 102, 105, 108, 111 0 0
The secondary subchannel groups (1, 3, and 5) can be allocated to any cell as required.
1 N/A 1 6-9
2 1 2 10-15
128 1024
3 N/A 3 16-19
4 2 4 20-25
5 N/A 5 26-29
0 0-4 0 0-11
1 N/A 1 12-19
2 5-9 2 20-31
512 2048
3 N/A 3 32-39
4 10-14 4 40-51
5 N/A 5 52-59
Resources: In Atoll, the term "resource" is used to refer to the average number of slots, expressed in % (as traffic
loads, when the average is performed over a considerably long duration) of the total number of slots in a super-
frame of 1 sec.
Atoll
RF Planning and Optimisation Software
Chapter 14: LTE Networks
14 LTE Networks
LTE (Long Term Evolution) refers to the set of 3GPP (3rd Generation Partnership Project) Release 8 and Release 9 spec-
ifications which describe the next steps, or evolution, of the existing GERAN (GSM EDGE Radio Acces Networks) and
UTRAN (UMTS Terrestrial Radio Access Networks) specifications. The 3GPP LTE specifications describe the building
blocks of the eUTRA (evolved UTRA) networks. LTE uses SOFDMA (Scalable Orthogonal Frequency Division Multiple
Access) and SC-FDMA (Single-Carrier Frequency Division Multiple Access) technologies in the downlink and the uplink,
respectively. The aim of LTE is to provide mobile broadband wireless access that supports handovers between LTE cells
as well as between LTE and UMTS/GSM cells at high user speeds.
Atoll enables you to design LTE broadband wireless access networks. Atoll can predict radio coverage, manage mobile
and fixed subscriber data, and evaluate network capacity. Atoll LTE also supports MIMO.
Atoll enables you to model fixed and mobile users in LTE environments. The data input corresponding to mobile users
and fixed subscribers is modelled through comprehensive support of mobile user traffic maps and subscriber databases,
respectively. You can carry out calculations on fixed subscriber locations as well as base your calculations on mobile user
scenarios during Monte Carlo simulations. You can also perform interference predictions, resource allocation, and other
calculations on mobile users.
Atoll uses Monte Carlo simulations to generate realistic network scenarios (snapshots) using a Monte Carlo statistical
engine for scheduling and resource allocation. Realistic user distributions can be generated using different types of traffic
maps or subscriber data. Atoll uses these realistic user distributions as input for the simulations.
Coverage predictions can be created to study the following parameters:
The reference signal level received from cells
The effective reference signal level
The effective SCH/PBCH, PDSCH/PDCCH, and PUSCH/PUCCHsignal levels
The carrier-to-interference-and-noise ratio for the reference signals, SCH/PBCH, PDSCH/PDCCH, and PUSCH
The radio bearer coverage
The channel throughput and cell capacity per pixel, and the aggregate throughput per cell
Coverage predictions that depend on the networks traffic loads can be created from either Monte Carlo simulation results
or from a user-defined network load configuration (uplink and downlink traffic loads, and uplink noise rise). GSM GPRS
EGPRS, CDMA2000 1xRTT, CDMA2000 1xEV-DO, UMTS HSPA, and LTE: networks can be planned in the same Atoll
session.
Tip: Before working with the Atoll LTE module for the first time, it is highly recommended to
go through the "Glossary of LTE Terms" on page 1114. This will help you get accustomed
to the terminology used by the 3GPP and in Atoll.
4. Allocate neighbours ( 4 ).
- "Planning Neighbours" on page 1052.
5. Allocate frequencies ( 5 ).
- "Planning Frequencies" on page 1061.
7. Before making more advanced coverage predictions, you need to define cell load conditions ( 7 ).
You can define cell load conditions in the following ways:
- You can generate realistic cell load conditions by creating a simulation based on traffic maps and subscriber
lists ( 7a , 7b , and 7c ) (see "Studying Network Capacity" on page 1069).
- You can define cell load conditions manually either on the Cells tab of each transmitters Properties dialogue
or in the Cells table (see "Creating or Modifying a Cell" on page 1008) ( 7d ).
8. Make LTE-specific signal quality coverage predictions using the defined cell load conditions ( 8 ).
- "LTE Coverage Predictions" on page 1036.
9. If necessary, modify network parameters to study the network with a different frequency plan ( 10 ). After modifying
the networks frequency plan, you must perform steps 7 and 8 again.
6
7a
7c 7d
7b
7
9 10
Atoll enables you to model network traffic by allowing you to create services, users, user profiles, environments, and termi-
nals. This data can be then used to make studies that depend on network load, such as C/(I+N), LTE radio bearer, and
throughput coverage predictions.
In this section, the following are explained:
"Creating an LTE Base Station" on page 1003.
"Creating a Group of Base Stations" on page 1014.
"Modifying Sites and Transmitters Directly on the Map" on page 1014.
"Display Tips for Base Stations" on page 1014.
"Creating a Multi-Band LTE Network" on page 1015.
"Setting the Working Area of an Atoll Document" on page 1015.
"Studying a Single Base Station" on page 1015.
"Studying Base Stations" on page 1019.
"Planning Neighbours" on page 1052.
"Planning Frequencies" on page 1061.
"Planning Physical Cell IDs" on page 1065.
Tip: While this method allows you to place a site with precision, you can also place sites using
the mouse and then position them precisely with this dialogue afterwards. For information
on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 31.
- Altitude: The altitude, as defined by the DTM for the location specified under Position, is given here. You can
specify the actual altitude under Real, if you wish. If an altitude is specified here, Atoll will use this value for
calculations.
- Comments: You can enter comments in this field if you wish.
- Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are dis-
played in red in the Transmitters folder of the Data tab.
Note: Only active transmitters are taken into consideration during calculations.
- Transmitter Type: If you want Atoll to consider the transmitter as a potential server as well as an interferer,
set the transmitter type to Intra-Network (Server and Interferer). If you want Atoll to consider the transmitter
only as an interferer, set the type to Extra-Network (Interferer Only). No coverage for an Interferer Only
transmitter will be calculated for coverage predictions and it will not serve any mobile in Monte Carlo simula-
tions.
This feature enables you to model the co-existence of different networks in the same geographic area. For
more information on how to study interference between co-existing networks, see "Modelling the Co-existence
of Networks" on page 1114.
- Transmission/Reception: Under Transmission/Reception, you can see the total losses and the noise
figure of the transmitter. Atoll calculates losses and noise according to the characteristics of the equipment
assigned to the transmitter. Equipment can be assigned using the Equipment Specifications dialogue which
appears when you click the Equipment button.
- On the Equipment Specifications dialogue (see Figure 14.4), the equipment you select and the gains and
losses you define are used to initialise total transmitter losses in the uplink and downlink:
- TMA: You can select a tower-mounted amplifier (TMA) from the list. You can click the Browse button
( ) to access the properties of the TMA. For information on creating a TMA, see "Defining TMA Equip-
ment" on page 147.
- Feeder: You can select a feeder cable from the list. You can click the Browse button ( ) to access the
properties of the feeder. For information on creating a feeder cable, see "Defining Feeder Cables" on
page 147.
- BTS: You can select a base transceiver station (BTS) equipment from the BTS list. You can click the
Browse button ( ) to access the properties of the BTS. For information on creating a BTS, see "Defin-
ing BTS Equipment" on page 148.
- Feeder Length: You can enter the feeder length at transmission and reception.
- Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value
you enter must be positive.
- Receiver Antenna Diversity Gain: You can enter a receiver antenna diversity gain. The value you enter
must be positive.
Atoll always considers the values in the Real boxes in coverage predictions even if they are different from the
values in the Computed boxes. The information in the real BTS Noise Figure reception box is calculated from
the information you entered in the Equipment Specifications dialogue. You can modify the real Total Loss-
es at transmission and reception and the real BTS Noise Figure at reception if you wish. Any value you enter
must be positive.
- Antennas:
- Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added
to the altitude of the site as given by the DTM. If the transmitter is situated on a building, the height entered
must include the height of building.
- Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the
Browse button ( ) to access the properties of the antenna. The other fields, Azimuth, Mechanical
Downtilt, and Additional Electrical Downtilt, display additional antenna parameters.
- Number of Antenna Ports: Select the number of antenna ports used for MIMO in the Transmission and
Reception fields. For more information on how the number of antenna ports are used, see "Multiple Input
Multiple Output Systems" on page 1108.
- Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power, which is
the percentage of power reserved for this particular antenna. For example, for a transmitter with one
secondary antenna, if you reserve 40 % of the total power for the secondary antenna, 60 % is available
for the main antenna.
For information on working with data tables, see "Working with Data Tables" on page 50.
Reference Signal C/N Threshold (dB): The minimum reference signal C/N required for a user to be connected
to the cell. The reference signal C/N is compared with this threshold to determine whether or not a user is within
the cells coverage or not.
LTE Equipment: You can select the cells LTE equipment from the LTE Equipment list. For more information, see
"Defining LTE Equipment" on page 1104. The cells LTE equipment parameters are used in the uplink calcula-
tions.
Scheduler: The scheduler used by the cell for resource allocation during Monte Carlo simulations. You can select
the scheduler from the list of schedulers available in the Schedulers table. For more information see "Defining
LTE Schedulers" on page 1107.
Max Number of Users: The maximum number of simultaneous connected users supported by the cell.
Frame Configuration: The frame configuration used by the cell when the cells frequency band is TDD. If the net-
works switching point periodicity is set to "Half Frame", you can select a frame configuration of type D-UUU D-
UUU, D-UUD D-UUD, or D-UDD D-UDD. If the networks switching point periodicity is set to "Frame", you can
select a frame configuration of type D-UUU DDDDD, D-UUD DDDDD, or D-UDD DDDDD. For more information
on TDD switching point periodicity, see "The Global Transmitter Parameters" on page 1102.
Diversity Support (DL): The type of antenna diversity technique (None, Transmit Diversity, SU-MIMO, or AMS)
supported by the cell in downlink.
Diversity Support (UL): The type of antenna diversity technique (None, Receive Diversity, SU-MIMO, AMS, or
MU-MIMO) supported by the cell in uplink.
Specific calculations will be performed (gains will be applied) for terminals supporting MIMO.
AMS/MU-MIMO Threshold (dB): For AMS, it is the reference signal C/N threshold for switching from SU-MIMO
to Transmit Diversity as the reference signal C/N gets worse than the given value. For MU-MIMO, it is the minimum
required reference signal CNR for using MU-MIMO. For more information on Adaptive MIMO switching, see "Mul-
tiple Input Multiple Output Systems" on page 1108.
MU-MIMO Gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO. This can be user-defined
or an output of Monte Carlo simulations. In uplink throughput coverage predictions, the cell capacity will be multi-
plied by this gain at pixels where MU-MIMO is used.
Max Traffic Load (UL) (%): The uplink traffic load not to be exceeded. This limit can be taken into account during
Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have an uplink
traffic load greater than this maximum.
Traffic Load (UL) (%): The uplink traffic load percentage. By default, the uplink traffic load is set to 100 %.
Max Traffic Load (DL) (%): The downlink traffic load not to be exceeded. This limit can be taken into account
during Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have a
downlink traffic load greater than this maximum.
Traffic Load (DL) (%): The downlink traffic load percentage. By default, the downlink traffic load is set to 100 %.
UL Noise Rise (dB): The uplink noise rise in dB. By default, the uplink noise rise is set to 0 dB.
Note: You can set the values for uplink and downlink traffic loads, and the uplink noise rise
manually to actual network values, or use the values computed during Monte Carlo
simulations. Monte Carlo simulation results can be stored in the cells by clicking the
Commit Results button in the simulation results dialogue.
Max Number of Intra-technology Neighbours: The maximum number of neighbours from within the same Atoll
document that the cell can have.
Max Number of Inter-technology Neighbours: The maximum number of neighbours from other technology doc-
uments that the cell can have.
Neighbours: You can access a dialogue in which you can set both intra-technology and inter-technology neigh-
bours by clicking the Browse button ( ). For information on defining neighbours, see "Planning Neighbours"
on page 1052.
Tip: The Browse button ( ) might not be visible in the Neighbours box if this is a new cell.
You can make the Browse button appear by clicking Apply.
Tips:
If you are creating several transmitters at the same time, or modifying several existing trans-
mitters, you can do it more quickly by editing or pasting the data directly in the Transmitters
table. You can open the Transmitters table by right-clicking the Transmitters folder on the
Data tab of the Explorer window and selecting Open Table from the context menu. For infor-
mation on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
If you want to add a transmitter to an existing site on the map, you can add the transmitter by
right-clicking the site and selecting New Transmitter from the context menu.
Tips:
If you are creating or modifying several cells at the same time, you can do it more quickly by
editing the data directly in the Cells table. You can open the Cells table by right-clicking the
Transmitters folder on the Data tab of the Explorer window and selecting Cells > Open
Table from the context menu. You can either edit the data in the table, paste data into the table
(see "Copying and Pasting in Tables" on page 56), or import data into the table (see "Importing
Tables from Text Files" on page 59).
If you want to add a cell to an existing transmitter on the map, you can add the cell by right-
clicking the transmitter and selecting New Cell from the context menu.
3. In the map window, move the pointer over the map to where you would like to
place the new station. The exact coordinates of the pointers current location
are visible in the Status bar.
Tips:
To place the base station more accurately, you can zoom in on the map before you click the
New Transmitter or Station button. For information on using the zooming tools, see
"Changing the Map Scale" on page 38.
If you let the pointer rest over the base station you have placed, Atoll displays its tip text with
its exact coordinates, allowing you to verify that the location is correct.
You can also place a series of base stations using a station template. You do this by defining an area on the map where
you want to place the base stations. Atoll calculates the placement of each base station according to the defined hexag-
onal cell radius in the station template. For information on defining the cell radius, see "Creating or Modifying a Station
Template" on page 1010.
To place a series of base stations within a defined area:
1. In the Radio toolbar, select a template from the list.
2. Click the Hexagonal Design button ( ), to the left of the template list. A hexagonal design is a group of base
stations created from the same station template.
Note: If the Hexagonal Design button is not available ( ), the hexagonal cell radius for this
template is not defined. For information on defining the cell radius, see "Creating or
Modifying a Station Template" on page 1010.
3. Draw a zone delimiting the area where you want to place the series of base stations:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
You can work with the sites and transmitters in these base stations as you work with any base station object, adding, for
example, another antenna to a transmitter.
When you place a new station using a station template as explained in "Placing a New Base Station Using a Station
Template" on page 1009, the site is created at the same time as the station. However, you can also place a new station
on an existing site.
To place a base station on an existing site:
1. On the Data tab, clear the display check box beside the Hexagonal Design folder.
2. In the Radio toolbar, select a template from the list.
- Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both
the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Managing
Calculations in Atoll.
5. Click the Transmitter tab. In this tab (see Figure 14.7), if the Active check box is selected, you can modify the
following:
- Under Transmission/Reception, you can click the Equipment button to open the Equipment Specifica-
tions dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or base transceiver station
(BTS). For information on the Equipment Specifications dialogue, see "Transmitter Description" on
page 1004.
The information in the computed Total Losses in transmission and reception boxes is calculated from the in-
formation you entered in the Equipment Specifications dialogue (see Figure 14.4 on page 1005). Atoll al-
ways considers the values in the Real boxes in coverage predictions even if they are different from the values
in the Computed boxes. You can modify the real Total Losses at transmission and reception if you wish. Any
value you enter must be positive.
The information in the computed BTS Noise Figure reception box is calculated from the information you en-
tered in the Equipment Specifications dialogue. You can modify the real BTS Noise Figure at reception if
you wish. Any value you enter must be positive.
6. Click the LTE tab. In this tab (see Figure 14.8), you can modify the following:
- Under Power and EPRE Offsets Relative to the Reference Signals, you can modify the Max Power, and
the EPRE offsets for the SCH and PBCH, and the PDSCH and PDCCH in SCH/PBCH Offset, and PDSCH/
PDCCH Offset.
- Frequency Band, Channel Number, Channel Allocation Status, Physical Cell ID, Physical Cell ID
Status, Min Reuse Distance, LTE Equipment, Scheduler, Max Number of Users, Frame Configuration,
and Reference Signal C/N Threshold.
- Under Antenna Diversity, you can select the Diversity Support in downlink and in uplink, enter the AMS/
MU-MIMO Threshold, and define the default MU-MIMO Gain.
- Under Default Loads, you can enter the default values for DL Traffic Load, UL Traffic Load, UL Noise Rise,
and the Max DL Traffic Load and Max UL Traffic Load.
- Under Inter-technology Interference, you can set the DL Noise Rise and the UL Noise Rise. For more infor-
mation on inter-technology interference, see "Modelling Inter-Network Interferences" on page 236.
- Under Max Number of Neighbours, you can set the maximum numbers of Intra-technology and Inter-tech-
nology neighbours.
7. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the
Sites table, or if you have defined an additional field in the Station Template Properties dialogue.
8. When you have finished setting the parameters for the station template, click OK to close the dialogue and save
your changes.
5. In the map window, move the pointer over the map to where you would like to place the new base station. The
exact coordinates of the pointers current location are visible in the Status bar.
Tips:
To place the station more accurately, you can zoom in on the map before you select Duplicate
from the context menu. For information on using the zooming tools, see "Changing the Map
Scale" on page 38.
If you let the pointer rest over the station you have placed, Atoll displays tip text with its exact
coordinates, allowing you to verify that the location is correct.
You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to
place each duplicate station.
For more information on the site, transmitter, and cell properties, see "Definition of a Base Station" on page 1003.
Note: When you import data into your current Atoll document, the coordinate system of the
imported data must be the same as the display coordinate system used in the document.
If you cannot change the coordinate system of your source data, you can temporarily
change the display coordinate system of the Atoll document to match the source data.
For information on changing the coordinate system, see "Setting a Coordinate System"
on page 92.
Important: The table you copy from must have the same column layout as the table you are pasting
data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
Importing data: If you have base station data in text or comma-separated value (CSV) format, you can import it
into the tables in the current document. If the data is in another Atoll document, you can first export it in text or
CSV format and then import it into the tables of your current Atoll document. When you are importing, Atoll allows
you to select what values you import into which columns of the table.
When you create a group of base stations by importing data, you must import site data in the Sites table, trans-
mitter data in the Transmitters table, and cell data in the Cells table, in that order.
For information on exporting table data, see "Exporting Tables to Text Files" on page 58. For information on
importing table data, see "Importing Tables from Text Files" on page 59.
Note: You can quickly create a series of base stations for study purposes using the Hexagonal
Design tool on the Radio toolbar. For information, see "Placing a New Base Station
Using a Station Template" on page 1009.
from fields that you add. The label is always displayed, so you should choose information that you would want to
always be visible; too much information in the label will make it harder to distinguish the information you are looking
for. For information on defining the label, see "Defining the Object Type Label" on page 35.
Tooltips: You can display information about each object, such as each site or transmitter, in the form of a tooltip
that is only visible when you move the pointer over the object. You can choose to display more information than
in the label, because the information is only displayed when you move the pointer over the object. You can display
information from every field in that object types data table, including from fields that you add. For information on
defining the tool tips, see "Defining the Object Type Tip Text" on page 36.
Transmitter colour: You can set the transmitter colour to display information about the transmitter. For example,
you can select "Discrete Values" to distinguish transmitters by antenna type, or to distinguish inactive from active
transmitters. You can also define the display type for transmitters as "Automatic." Atoll then automatically assigns
a colour to each transmitter, ensuring that each transmitter has a different colour than the transmitters surrounding
it. For information on defining the transmitter colour, see "Defining the Display Type" on page 34.
Transmitter symbol: You can select one of several symbols to represent transmitters. For example, you can
select a symbol that graphically represents the antenna half-power beamwidth ( ). If you have two transmit-
ters on the same site with the same azimuth, you can differentiate them by selecting different symbols for each
( and ). For information on defining the transmitter symbol, see "Defining the Display Type" on page 34.
It is important not to confuse the computation zone and the focus zone or hot spot zones. The computation zone
defines the area where Atoll computes path loss matrices, coverage predictions, Monte Carlo simulations, etc.,
while the focus zone or hot spot zones are the areas taken into consideration when generating reports and results.
For information on the computation zone, see "Creating a Computation Zone" on page 1023.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be
studied.
Before studying a base station, you must assign a propagation model. The propagation model takes the radio and
geographic data into account and computes propagation losses along the transmitter-receiver path. This allows you to
predict the received signal level at any given point. Any coverage prediction you make on a base station uses the propa-
gation model to calculate its results.
In this section, the following are explained:
"Making a Point Analysis to Study the Profile" on page 1016.
"Studying Signal Level Coverage" on page 1017.
2. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the fol-
lowing:
- Move the receiver to change the current position.
- Click to place the receiver at the current position. You can move the receiver again by clicking it a second time.
- Right-click the receiver to choose one of the following commands from the context menu:
- Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates.
- Target Site: Select a site from the list to place the receiver directly on a site.
4. Click the Profile tab.
The profile analysis appears in the Profile tab of the Point Analysis Tool window. The altitude is reported on the
vertical axis and the receiver-transmitter distance on the horizontal axis. A blue ellipsoid indicates the Fresnel zone
between the transmitter and the receiver, with a green line indicating the line of sight (LOS). Atoll displays the
angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an obstacle, this
causes attenuation with diffraction displayed by a red vertical line (if the propagation model used takes diffraction
mechanisms into account). The main peak is the one that intersects the most with the Fresnel ellipsoid. With some
propagation models using a 3 knife-edge Deygout diffraction method, the results may display two additional atten-
uations peaks. The total attenuation is displayed above the main peak.
The results of the analysis are displayed at the top of the Profile tab:
- The received signal strength from the selected transmitter for the cell with the highest power
- The propagation model used
- The shadowing margin and the cell edge coverage probability used for calculating it
- The distance between the transmitter and the receiver.
You can change the following options at the top of the Profile tab:
- Transmitter: Select the transmitter from the list.
- Display Geo Data Only: Select the Display Geo Data Only check box if you want to view the geographic
profile between the transmitter and the receiver. Atoll displays the profile between the transmitter and the
receiver with clutter heights. An ellipsoid indicating the Fresnel zone is also displayed. Atoll does not calculate
nor display signal levels and losses.
5. Right-click the Profile tab to choose one of the following commands from the context menu:
- Properties: Select Properties to display the Analysis Properties dialogue. This dialogue is available from
the context menu on all tabs of the Point Analysis Tool window. You can:
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and,
select "From Model" from the Shadowing Margin list.
- Select Signal Level, Path loss, or Total losses from the Result Type list.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- Link Budget: Select Link Budget to display a dialogue with the link budget.
- Model Details: Select Model Details to display a text document with details on the displayed profile analysis.
Model details are only available for the Standard Propagation Model.
6. To end the point analysis, click the Point Analysis Tool ( ) in the Radio toolbar again.
Note: You can use the same procedure to study the signal level coverage of several base
stations by grouping the transmitters. For information on grouping transmitters, see
"Grouping Data Objects by a Selected Property" on page 65.
Tip: If you wish to study only sites by their status, at this step you could group them by status.
5. Select Coverage by Signal Level and click OK. A study properties dialogue appears.
6. You can configure the following parameters in the Properties dialogue:
- General tab: You can change the assigned Name of the coverage prediction, the Resolution, and the storage
Folder for the coverage prediction, and add some Comments. The resolution you set is the display resolution,
not the calculation resolution.
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:
City Centre 5m
City 20 m
County 50 m
State 100 m
Note: If you create a new coverage prediction from the context menu of either the Transmitters
or Predictions folder, you can select the sites using the Group By, Sort, and Filter
buttons under Configuration. Because you already selected the target sites, however,
only the Filter button is available.
- Condition tab: The coverage prediction parameters on the Condition tab allow you to define the signals that
will be considered for each pixel (see Figure 14.11).
- At the top of the Condition tab, you can set the signal level range to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the
same results because Atoll displays the results of the best server in either case. Selecting "Best Signal
Level" necessitates, however, a longer time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that
Atoll will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage
Probability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- Display tab: You can modify how the results of the coverage prediction will be displayed.
- Under Display Type, select "Value Intervals."
- Under Field, select "Best Signal Level."
- You can change the value intervals and their displayed colour. For information on changing display prop-
erties, see "Display Properties of Objects" on page 33.
- You can create a tooltip with information about the coverage prediction by clicking the Browse button
( ) beside the Tip Text box and selecting the fields you want to display in the tooltip.
- You can select the Add to Legend check box to add the displayed value intervals to the legend.
Note: If you change the display properties of a coverage prediction after you have calculated it,
you may make the coverage prediction invalid. You will then have to recalculate the
coverage prediction to obtain valid results.
7. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The signal level
coverage prediction can be found in the Predictions folder on the Data tab. Atoll automatically locks the results of a cover-
age prediction as soon as it is calculated, as indicated by the icon ( ) beside the coverage prediction in the Predictions
folder. When you click the Calculate button ( ), Atoll only calculates unlocked coverage predictions ( ).
Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices
using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main prop-
agation model with a shorter radius (displayed with a blue square in Figure 14.12) and a higher resolution and an extended
propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate
higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower reso-
lution path loss matrices outside the area covered by the main propagation model.
In this section, the following are explained:
"Path Loss Matrices" on page 1020.
"Assigning a Propagation Model" on page 1021.
"The Calculation Process" on page 1023.
"Creating a Computation Zone" on page 1023.
"Setting Transmitters or Cells as Active" on page 1024.
"Signal Level Coverage Predictions" on page 1024.
"Analysing a Coverage Prediction" on page 1028.
"LTE Coverage Predictions" on page 1036.
"Printing and Exporting Coverage Prediction Results" on page 1051.
Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matri-
ces in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning
projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case
of large radio-planning projects, saving your path loss matrices externally will help reduce the size of the file and the use
of computer resources.
The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same
radio-planning project. In this case, the radio data is stored in a database and the path loss matrices are read-only and are
stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices,
the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These
will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more
information on working in a multi-user environment, see the Administrator Manual.
When you save the path loss matrices to an external directory, Atoll creates:
One file per transmitter with the extension LOS for its main path loss matrix.
A DBF file with validity information for all the main matrices.
A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
To set the storage location of the path loss matrices:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss
matrices and the location for the shared path loss matrices:
- Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are
loading path loss matrices from a shared location, where you store your changes to shared path loss matrices.
Click the button beside the Private Directory ( ) and select Embedded to save the path loss matrices in
the Atoll document, or Browse to select a directory where Atoll can save the path loss matrices externally.
Note: Path loss matrices you calculate locally are not stored in the same directory as shared
path loss matrices. Shared path loss matrices are stored in a read-only directory. In other
words, you can read the information from the shared path loss matrices but any changes
you make will be stored locally, either embedded in the ATL file or in a private external
folder, depending on what you have selected in Private Directory.
Caution: When you save the path loss files externally, the external files are updated as soon as
calculations are performed. In order to keep consistency between the Atoll document and
the stored calculations, you should save the Atoll document before closing it if you have
updated the path loss matrices.
- Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a
database and the path loss matrices are stored in a directory that is accessible to all users. Any changes you
make will not be saved to this directory; they will be saved in the location indicated in Private Directory. The
path loss matrices in the shared directory are updated by a user with administrator rights based on the updated
information in the database. For more information on shared directories, see the Administrator Manual.
5. Click OK.
Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want,
you can check whether the path loss matrices are valid without creating a coverage prediction.
To check whether the path loss matrices are valid:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. You have the
following display options:
- Display all the matrices: All path loss matrices are displayed.
- Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available Results table lists the following information for each displayed path loss matrix:
Important: When you assign a propagation model globally, you override any selection you might
have made to an individual transmitter or to a group of transmitters.
3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default
Propagation Model" on page 187, this is the propagation model that will be used for all transmitters whose main
propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main prop-
agation model, that is the propagation model that will be used.
In this section, the following are explained:
"Assigning a Propagation Model to All Transmitters" on page 1021.
"Assigning a Propagation Model to a Group of Transmitters" on page 1022.
"Assigning a Propagation Model to One Transmitter" on page 1022.
For more information about the available propagation models, see Chapter 5: Managing Calculations in Atoll.
Transmitters that share the same parameters and environment will usually use the same propagation model and settings.
In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common
parameters and then assigning the propagation model.
To define a main and extended propagation model for a defined group of transmitters:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select from the Group by submenu of the context menu the property by which you want to group the transmitters.
The objects in the folder are grouped by that property.
Note: You can group transmitters by several properties by using the Group By button on the
Properties dialogue. For more information, see "Advanced Grouping" on page 66.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model
to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmit-
ters.
When you assign a main and extended propagation model to a single transmitter, it overrides any changes you have previ-
ously made globally.
To define a main and extended propagation model for all transmitters:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Transmitters folder.
3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu
appears.
4. Select Properties from the context menu. The Properties dialogue appears.
5. Click the Propagation tab.
Note: You can also define the propagation models for a transmitter by right-clicking it in the map
window and selecting Properties from the context menu.
Notes:
You can stop any calculations in progress by clicking the Stop Calculations button ( ) in
the toolbar.
When you click the Force Calculation button ( ) instead of the Calculate button, Atoll cal-
culates all path loss matrices, unlocked coverages, and pending simulations.
You can also create a computation zone with one of the following methods:
Existing polygon: You can use any existing polygon on the map as a computation zone by right-clicking it and
selecting Use as Computation Zone from the context menu.
Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a computation zone. You can import it by right-clicking the Computa-
tion Zone folder on the Geo tab and selecting Import from the context menu.
Fit to Map Window: You can create a computation zone the size of the map window by right-clicking the Com-
putation Zone folder on the Geo tab and selecting Fit to Map Window from the context menu.
Note: You can save the computation zone in the user configuration. For information on
exporting the computation zone in the user configuration, see "Exporting a User
Configuration" on page 75.
Note: If you do not yet have a zone containing the transmitters you want to set as active, you
can draw a zone as explained in "Using Zones in the Map Window" on page 41.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active.
Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on
choosing and configuring a propagation model, see Chapter 5: Managing Calculations in Atoll.
Calculating path loss matrices can be time and resource intensive when you are working on larger projects. Consequently,
Atoll offers you the possibility of distributing path loss calculations on several computers. You can install the distributed
calculation server application on other workstations or on servers. Once the distributed calculation server application is
installed on a workstation or server, the computer is available for distributed path loss calculation to other computers on
the network. For information on setting up the distributed calculation server application, see The Administrator Manual.
you clone a coverage prediction, by selecting Clone from the context menu, you can create a copy of the prediction with
the calculated coverage. You can then change the display, providing that the selected parameter does not invalidate the
calculated coverage prediction.
You can also save the list of all defined coverage predictions in a user configuration, allowing you or other users to import
it into a new Atoll document. When you save the list in a user configuration, the parameters of all existing coverage predic-
tions are saved; not just the parameters of calculated or displayed ones. For information on exporting user configurations,
see "Exporting a User Configuration" on page 75.
The following standard coverage predictions are explained in this section:
"Making a Coverage Prediction by Signal Level" on page 1025
"Making a Coverage Prediction by Transmitter" on page 1026
"Making a Coverage Prediction on Overlapping Zones" on page 1027.
6. Click the Condition tab (see Figure 14.14). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same
results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level"
necessitates, however, the longest time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll
will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 14.15).
6. Click the Condition tab (see Figure 14.16). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same
results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level"
necessitates, however, the longest time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll
will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 14.17).
6. Click the Condition tab (see Figure 14.18). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same
results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level"
necessitates, however, the longest time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll
will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 14.19).
1. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
2. At the bottom of the Point Analysis Tool window, click the Reception tab (see Figure 14.21).
The predicted signal level from different transmitters is reported in the Reception tab in the form of a bar chart,
from the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the
colour of the transmitter it represents. For a transmitter with more than one cell, the signal level is calculated for
the cell with the highest power.
In the Map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they
represent. A thick black line from the pointer to its best server is also displayed in the map window. The best server
of the pointer is the transmitter from which the pointer receives the highest signal level. If you let the pointer rest,
the signal level received from the corresponding transmitter at the pointer location is displayed in the tool-tip.
3. Right-click the Reception tab and select Properties from the context menu. The Analysis Properties dialogue
appears.
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and
select "From Model" from the Shadowing Margin list.
- Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class.
4. To end the point analysis, click the Point Analysis Tool ( ) in the Radio toolbar again.
14.2.8.7.4 Creating a Focus or Hot Spot Zone for a Coverage Prediction Report
The focus and hot spot zones define the area on which statistics can be drawn and on which reports are made. While you
can only have one focus zone, you can define several hot spot zones in addition to the focus zone.
It is important not to confuse the computation zone and the focus and hot spot zones. The computation zone defines the
area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo simulations, etc., while the focus and
hot spot zones are the areas taken into consideration when generating reports and results. When you create a coverage
prediction report, it gives the results for the focus zone and for each of the defined hot spot zones.
To define a focus zone or hot spot zone:
1. Click the Geo tab in the Explorer window.
2. Click the Expand button ( ) to expand the Zones folder.
3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or
a hot spot. The context menu appears.
4. Select Draw from the context menu.
5. Draw the focus or hot spot zone:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zones
visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but
will still be taken into account.
You can also create a focus or hot spot zone as follows:
Existing polygon: You can use any existing polygon on the map as a focus zone by right-clicking it and selecting
Use as Focus Zone from the context menu.
Note: You can only create a focus zone, and not a hot spot zone, from an existing polygon.
Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus
Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot
spot zones, you can import the name given to each zone as well.
Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map
Window from the context menu.
Notes: You can save the focus or hot spot zones so that you can use them in a different Atoll
document:
- You can save the focus zone in the user configuration. For information on exporting the
focus zone in the user configuration, see "Exporting a User Configuration" on page 75.
- You can right-click the Focus Zone folder or the Hot Spot Zones folder on the Data
tab of the Explorer window and select Export from the context menu.
You can include population statistics in the focus or hot spot zone by importing a population
map. For information on importing maps, see "Importing a Raster-format Geo Data File" on
page 107.
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
a. Under Configuration, click the Import button. The Open dialogue appears.
b. Select the configuration you want to import and click Open. The imported report configuration is applied.
6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed
dialogue. The coverage prediction report table appears. The report is based on the hot spot zones and on the
focus zone if available or on the hot spot zones and computation zone if there is no focus zone.
To display a report on all coverage predictions:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears.
4. Define the format and content of the report:
You can select the columns that will be displayed in the report and define the order they are in:
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
Atoll saves the names of the columns you select and will automatically select them the next time you create a
coverage prediction report.
5. Click OK.
If you have created a custom data map with integrable data, the data can be used in prediction reports. The data will be
summed over the coverage area for each item in the report (for example, by transmitter or threshold). The data can be
value data (revenue, number of customers, etc.) or density data (revenue/km, number of customers/km, etc.). Data is
considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example,
socio-demographic classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable
Versus Non Integrable Data" on page 124.
In this section, there are two examples to explain how you can compare two similar predictions. You can display the results
of the comparison study coverage in one of the following ways:
Intersection: This display shows the area where both coverage predictions overlap (for example, pixels covered
by both coverage predictions are displayed in red).
Union: This display shows all pixels covered by both coverage predictions in one colour and pixels covered by
only one coverage prediction in a different colour (for example, pixels covered by both predictions are red and
pixels covered by only one prediction are blue).
Difference: This display shows all pixels covered by both coverage predictions in one colour, pixels covered by
only the first prediction with another colour and pixels covered only by the second prediction with a third colour (for
example, pixels covered by both predictions are red, pixels covered only by the first prediction only are green, and
pixels covered only by the second prediction are blue).
To compare two similar coverage predictions:
1. Create and calculate a coverage prediction of the existing network.
2. Examine the coverage prediction to see where coverage can be improved.
3. Make the changes to the network to improve coverage.
4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged).
5. Calculate the duplicate coverage prediction.
6. Compare the original coverage prediction with the new coverage prediction. Atoll displays differences in coverage
between them.
In this section, the following examples are explained:
"Example 1: Studying the Effect of a New Base Station" on page 1033
"Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 1035.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how you can verify if a newly added base station improves coverage.
A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal
Level" on page 1025. The results are displayed in Figure 14.23. An area with poor coverage is visible on the right side of
the figure.
A new base station is added, either by creating the base station and adding the transmitters, as explained in "Creating an
LTE Base Station" on page 1003, or by placing a station template, as explained in "Placing a New Base Station Using a
Station Template" on page 1009. Once the new site has been added, the original coverage prediction can be recalculated,
but then it would be impossible to compare the results. Instead, the original signal level coverage prediction can be copied
by selecting Duplicate from its context menu. The copy is then calculated to show the effect of the new base station (see
Figure 14.24).
Figure 14.24: Signal level coverage prediction of network with new base station
4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes adding a new base station made, you should choose Difference.
5. Click OK to create the comparison. The comparison in Figure 14.25, shows clearly the area covered only by the
new base station.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how modifying transmitter tilt can improve coverage.
A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by
Transmitter" on page 1026. The results are displayed in Figure 14.26. The coverage prediction shows that one transmitter
is covering its area poorly. The area is indicated with a red oval in the figure.
You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed
by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and
electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue.
Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it would be
impossible to compare the results. Instead, the original coverage prediction can be copied by selecting Duplicate from its
context menu. The copy is then calculated, to show how modifying the antenna tilt has affected coverage (see
Figure 14.27).
As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change
in coverage, you can compare the two predictions.
To compare two predictions:
1. Right-click one of the two predictions. The context menu appears.
2. From the context menu, select Compare with and, from the menu that opens, select the prediction you want to
compare with the first. The Comparison Properties dialogue appears.
3. Click the General tab. You can change the Name of the comparison and add Comments.
The General tab contains information about the coverage predictions being compared, including their names and
resolutions.
4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes modifying the antenna tilt made, you can choose Union. This will display all pixels
covered by both predictions in one colour and all pixels covered by only one prediction in another colour. The
increase in coverage, seen in only the second coverage prediction, will be immediately clear.
5. Click OK to create the comparison. The comparison in Figure 14.28, shows clearly the increase in coverage due
at the change in antenna tilt.
Using signal quality coverage predictions you can study the effective service coverage area and capacity of each cell in
the network. These coverage predictions depend on the interference in the network and the cell load conditions. For this
reason, the network load must be defined in order to calculate these coverage predictions.
For the purposes of these coverage predictions, each pixel is considered a non-interfering user with a defined service,
mobility type, and terminal. The following are explained in the following sections:
"Service and User Modelling" on page 1037.
This section explains the coverage predictions available for analysing the effective signal level and signal quality. The
following are explained:
"Analysing the Effective Signal Levels" on page 1039.
"Analysing the Signal Quality" on page 1041.
You can also make a point analysis using the Point Analysis window to study the effective signal level at a point. Load
conditions can be selected for the analysis as well as the characteristics of the user-definable probe receiver, i.e., a termi-
nal, a mobility, and a service:
"Making an Effective Signal Analysis" on page 1050.
Interferences coming from an external project can also be modelled and is explained in "Modelling Inter-Network Interfer-
ences" on page 236.
Modelling Services
Services are the various services available to users. These services can be either voice or data type services. This section
explains how to create a service. The following parameters are used in predictions:
Throughput scaling factor
Throughput offset
Body loss
To create or modify a service:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the LTE Parameters folder.
3. Right-click the Services folder. The context menu appears.
4. Select New from the context menu. The Services New Element Properties dialogue appears.
Note: You can modify the properties of an existing service by right-clicking the service in the
Services folder and selecting Properties from the context menu.
5. You can edit the fields on the General tab to define the new service. Some fields depend on the type of service
you choose. You can change the following parameters.
- Name: Atoll proposes a name for the new service, but you can set a more descriptive name.
- Type: You can select either Voice or Data as the service type.
- Priority: Enter a priority for this service. "0" is the lowest priority.
- Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity for
users accessing a voice type service during Monte Carlo simulations.
- Highest Bearer: Select the highest bearer that the service can use in the uplink and downlink. This is consid-
ered as an upper limit during bearer determination.
- Max Throughput Demand: Enter the highest throughput that the service can demand in the uplink and down-
link.
- Min. Throughput Demand: Enter the minimum required throughput that the service should have in order to
be available in the uplink and downlink.
- Average Requested Throughput: Enter the average requested throughput for uplink and downlink. The
average requested throughput is used in a simulation during user distribution generation in order to calculate
the number of users attempting a connection.
- Application Throughput: Under Application Throughput, you can set a Scaling Factor between the appli-
cation throughput and the RLC (Radio Link Control) throughput and a throughput Offset. These parameters
model the header information and other supplementary data that does not appear at the application level.
The application throughput parameters are used in throughput coverage predictions and for application
throughput calculation.
- Body Loss: Enter a body loss for the service. The body loss is the loss due to the body of the user. For
example, in a voice connection the body loss, due to the proximity of the users head, is estimated to be 3 dB.
6. Click OK.
In LTE, information about the receiver mobility is required for determining which bearer selection threshold and quality
graph to use from the LTE equipment referred to in the terminal or cell. Mobiles used at high speeds and at walking speeds
do not have the same quality characteristics. C/(I+N) requirements for different radio bearers are largely dependent on
mobile speed.
To create or modify a mobility type:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the LTE Parameters folder.
3. Right-click the Mobility Types folder. The context menu appears.
4. Select New from the context menu. The Mobility Types New Element Properties dialogue appears.
Note: You can modify the properties of an existing mobility type by right-clicking the mobility
type in the Mobility Types folder and selecting Properties from the context menu.
5. You can enter or modify the following parameters in the Mobility Types New Element Properties dialogue:
- Name: Enter a descriptive name for the mobility type.
- Average Speed: Enter an average speed for the mobility type. This field is for information only; the average
speed is not used by any calculation.
6. Click OK.
Note: Subscriber lists use the mobility type "Fixed", i.e., 0 km/hr, in calculations. Do not delete
this mobility type from the document if you are working with subscriber lists.
Modelling Terminals
In LTE, a terminal is the user equipment that is used in the network, for example, a mobile phone, a PDA, or a cars on-
board navigation device.
The following parameters are used in predictions:
Antenna
LTE equipment
Maximum and minimum terminal power
Gain and losses
Noise figure
Supported antenna diversity technique
Number of transmission and reception antenna ports for MIMO
To create or modify a terminal:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the LTE Parameters folder.
3. Right-click the Terminals folder. The context menu appears.
4. Select New from the context menu. The Terminals New Element Properties dialogue appears.
Note: You can modify the properties of an existing terminal by right-clicking the terminal in the
Terminals folder and selecting Properties from the context menu.
5. You can enter or modify the following parameters in the Terminals New Element Properties dialogue:
- Name: Enter a descriptive name for the terminal.
- Under Transmission/Reception,
- Min Power: Enter the minimum transmission power of the terminal.
- Max Power: Enter the maximum transmission power of the terminal.
- Noise Figure: Enter the noise figure of the terminal (used to calculate the downlink total noise).
- Losses: Enter the losses of the terminal.
- LTE Equipment: Select an LTE equipment from the list of available equipment. For more information on
LTE equipment, see "Defining LTE Equipment" on page 1104. The terminals LTE equipment parameters
are used in the downlink calculations.
- Under Antenna,
- Model: Select an antenna model from the list of available antennas. If you do not select an antenna for
the terminal, Atoll uses an isotropic antenna in calculations.
Note: In case you do not select an antenna, Atoll uses an isotropic antenna, not an omni-
directional antenna, in calculations. An isotropic antenna has spherical radiation patterns
in the horizontal as well as vertical planes.
- Gain: Enter the terminal antenna gain if you have not selected an antenna model in the Model field. If you
have selected an antenna, the Gain field is disabled and shows the gain of the selected antenna.
- Diversity Support: Select whether the terminal type supports MIMO or not. Antenna diversity gains will
be applied to MIMO users.
- Under Number of Antenna Ports, enter the number of antenna ports available in the terminal for Trans-
mission and Reception.
6. Click OK.
For more information on services, terminals, mobility types, and LTE equipment, see "Modelling Services" on
page 1037, "Modelling Terminals" on page 1038, "Modelling Mobility Types" on page 1038, and "Defining LTE
Equipment" on page 1104, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
the effective signal analysis calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
Figure 14.29: Condition settings for an effective signal analysis coverage prediction
The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see
"Display Properties of Objects" on page 33.
10. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 14.30
and Figure 14.31).
If you are setting the traffic loads and the uplink noise rise for a single transmitter, you can set these parameters on the
Cells tab of the transmitters Properties dialogue. However, you can set the traffic loads and the uplink noise rise for all
the cells using the Cells table.
To set the traffic loads and the uplink noise rise using the Cells table:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Open Table from the context menu. The Cells table appears.
4. Enter a value in the following columns:
- Traffic Load (DL) (%)
- UL Noise Rise (dB)
Although, you can also set a value for the Traffic Load (UL) (%) column as an indication of cells uplink loads,
this parameter is not used in the coverage prediction calculations. The measure of interference in the uplink
is given by the UL Noise Rise (dB). For a definition of the values, see "Cell Description" on page 1006.
5. To enter the same values in one column for all cells in the table:
a. Enter the value in the first row in the column.
b. Select the entire column.
c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
Downlink and uplink coverage predictions by C/(I+N) level predict the interference levels and signal-to-interference levels
in the part of the network being studied.
Atoll calculates the serving transmitter for each pixel depending on the downlink reference signal level. The serving trans-
mitter is determined according to the received reference signal level from the cell with the highest power. If more than one
cell cover the pixel, the one with the lowest order is selected as the serving (reference) cell. Then, depending on the predic-
tion definition, it calculates the interference from other cells, and finally calculates the C/(I+N). The pixel is coloured if the
display threshold condition is fulfilled (in other words, if the C/(I+N) is higher than C/(I+N) threshold).
Coverage prediction by C/(I+N) level calculates the co-channel interference as well as the adjacent channel interference,
which is reduced by the adjacent channel suppression factor defined in the Frequency Bands table. For more information
on frequency bands, see "Defining Frequency Bands" on page 1101.
The reference signal C/(I+N) is calculated using the reference signal power. Interference on the reference signals is in part
caused by the reference signals from interfering cells and in part by the PDSCH/PDCCH transmission. The SCH/PBCH
C/(I+N) is calculated using the SCH/PBCH power. Interference on the SCH and PBCH is caused by the SCH and PBCH
transmission from interferering cells, respectively. The PDSCH/PDCCH C/(I+N) is calculated using the PDSCH/PDCCH
power. Interference on the PDSCH/PDCCH is caused by PDSCH/PDCCH transmission from interfereing cells. PDSCH/
PDCCH interference depends on the downlink traffic loads of interfering cells. The PUSCH/PUCCH C/(I+N) is calculated
using the terminal power calculated after power control and the uplink noise rise stored either in the cell properties or in
the selected simulation results.
To make a coverage prediction by C/(I+N) level:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by C/(I+N) Level (DL) or Coverage by C/(I+N) Level (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 14.32).
Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on
load conditions taken from a simulation. Atoll will calculate the coverage prediction using the cell loads stored in
the cell properties.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The C/(I+N) coverage prediction is a best server
coverage prediction. The Noise Figure defined in the terminal types properties dialogue is used in the coverage
prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to determine
the total noise in the uplink.
For more information on services, terminals, mobility types, and LTE equipment, see "Modelling Services" on
page 1037, "Modelling Terminals" on page 1038, "Modelling Mobility Types" on page 1038, and "Defining LTE
Equipment" on page 1104, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see
"Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 14.33
and Figure 14.34).
Downlink and uplink best radio bearer coverage predictions calculate and display the best LTE radio bearers based on
C(I+N) for each pixel.
To make a coverage prediction by best bearer:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Best Bearer (DL) or Coverage by Best Bearer (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The best bearer coverage prediction is always based
on the best server. The Noise Figure defined in the terminal types properties dialogue is used in the coverage
prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to determine
the total noise in the uplink. As well, the bearer selection for each pixel according to the PDSCH/PDCCH C(I+N)
level is performed using the bearer selection thresholds defined in the LTE equipment. This LTE equipment is the
one defined in the selected terminal for the downlink coverage predictions, and the one defined in the cell proper-
ties of the serving transmitter for the uplink coverage predictions. Mobility is used to index the bearer selection
threshold graph to use.
For more information on services, terminals, mobility types, and LTE equipment, see "Modelling Services" on
page 1037, "Modelling Terminals" on page 1038, "Modelling Mobility Types" on page 1038, and "Defining LTE
Equipment" on page 1104, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the LTE bearer coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 14.36
and Figure 14.37).
Downlink and uplink throughput coverage predictions calculate and display the channel throughputs and cell capacities
based on C(I+N) and bearer calculations for each pixel. These coverage predictions can also display aggregate cell
throughputs if Monte Carlo simulation results are available. For more information on making aggregate cell throughput
coverage predictions using simulation results, see "Making an Aggregate Throughput Coverage Prediction Using Simula-
tion Results" on page 1047.
To make a coverage prediction by throughput:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Throughput (DL) or Coverage by Throughput (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The throughput coverage prediction is always based
on the best server. The Noise Figure defined in the terminal types Properties dialogue is used in the coverage
prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to determine
the total noise in the uplink. As well, the bearer selection for each pixel according to the PDSCH/PDCCH C(I+N)
level is performed using the bearer selection thresholds defined in the LTE equipment. This LTE equipment is the
one defined in the selected terminal for the downlink coverage predictions, and the one defined in the cell proper-
ties of the serving transmitter for the uplink coverage predictions. The mobility is used to indicate the bearer selec-
tion threshold graph to use. The service is used for the application throughput parameters defined in the service
Properties dialogue.
For more information on services, terminals, mobility types, and LTE equipment, see "Modelling Services" on
page 1037, "Modelling Terminals" on page 1038, "Modelling Mobility Types" on page 1038, and "Defining LTE
Equipment" on page 1104, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage pre-
diction will display. You can set parameters to display the following results:
- Channel throughputs: Select Peak RLC Channel Throughput, Effective RLC Channel Throughput, or
Application Channel Throughput.
- Cell capacities: Select Peak RLC Cell Capacity, Effective RLC Cell Capacity, or Application Cell
Capacity.
- Allocated Bandwidth throughputs in uplink: Select Peak RLC Allocated Bandwidth Throughput, Effective
RLC Allocated Bandwidth Throughput, or Application Allocated Bandwidth Throughput.
The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see
"Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Atoll determines the total number of symbols in the downlink and the uplink frames from the information in the global trans-
mitter parameters and the frequency bands assigned to cells. Then, Atoll determines the bearer at each pixel and multi-
plies the bearer efficiency by the number of symbols in the frame to determine the peak RLC channel throughputs.
The effective RLC throughputs are the peak RLC throughputs reduced by retransmission due to errors, or the Block Error
Rate (BLER). Atoll uses the block error rate graphs of the LTE equipment defined in the selected terminal or the LTE
equipment of the cell of the serving transmitter.
The application throughput is the effective RLC throughput reduced by the overheads of the different layers between the
RLC and the Application layers.
The cell capacity display types let you calculate and display the throughputs available at each pixel of the coverage area
taking into account the maximum traffic load limits set for each cell. In other words, the cell capacity is equal to channel
throughput when the maximum traffic load is set to 100 %, and is equal to a throughput limited by the maximum allowed
traffic loads otherwise. Cell capacities are, therefore, channel throughputs scaled down to respect the maximum traffic load
limits.
The allocated bandwidth throughputs are the throughputs corresponding to the number of frequency blocks allocated to
the terminal at different locations. Users located far from the base stations use less numbers of frequency blocks than
users located near so that they can concentrate their transmission power over a bandwidth narrower than the channel
bandwidth in order to maintain the connection in uplink.
For more information on throughput calculation, see the Technical Reference Guide. For more information on the Global
Parameters, see "The Global Transmitter Parameters" on page 1102.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Atoll calculates the aggregate peak RLC, effective RLC, and application cell throughputs during Monte Carlo simulations.
The aggregate cell throughputs are the sums of the cells user throughputs. You can create a coverage prediction that
calculates and displays the surface area covered by each cell, and colours the coverage area of each cell according to its
aggregate throughput.
Downlink and uplink quality indicator coverage predictions calculate and display the values of different quality indicators
(BLER, BER, etc.) based on the best LTE radio bearers and on C(I+N) for each pixel.
To make a coverage prediction by quality indicator:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Quality Indicator (DL) or Coverage by Quality Indicator (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The quality indicator coverage prediction is always
based on the best server. The Noise Figure defined in the terminal types properties dialogue is used in the cover-
age prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to deter-
mine the total noise in the uplink. As well, the bearer selection for each pixel according to the PDSCH/PDCCH
C(I+N) level is performed using the bearer selection thresholds defined in the LTE equipment, and the quality indi-
cator graphs from the LTE equipment are used to determine the values of the selected quality indicator on each
pixel. This LTE equipment is the one defined in the selected terminal for the downlink coverage predictions, and
the one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used
to index the bearer selection threshold graph to use.
For more information on services, terminals, mobility types, and LTE equipment, see "Modelling Services" on
page 1037, "Modelling Terminals" on page 1038, "Modelling Mobility Types" on page 1038, and "Defining LTE
Equipment" on page 1104, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the quality indicator coverage prediction.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 14.42
and Figure 14.43).
1. Click the Point Analysis button ( ) on the toolbar. The Point Analysis Tool window appears (see
Figure 14.45).
2. Click the Signal Analysis tab.
3. At the top of the Signal Analysis tab, select "Cells Table" from Load Conditions.
4. If you are making a signal analysis to verify a coverage prediction, you can recreate the conditions of the coverage
prediction:
a. Select the same Terminal, Service, and Mobility studied in the coverage prediction.
b. Right-click the Point Analysis window and select Properties from the context menu. The Properties dia-
logue appears.
- Edit the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and,
select "From Model" from the Shadowing Margin list.
c. Click OK to close the Properties dialogue.
5. Move the pointer over the map to make a signal analysis for the current location of the pointer.
As you move the pointer, Atoll indicates on the map which is the best server for the current position (see
Figure 14.44).
Information on the current position is given on the Signal Analysis tab of the Point Analysis window. See
Figure 14.45 for an explanation of the displayed information.
6. Click the map to leave the point analysis pointer at its current position.
To move the pointer again, click the point analysis pointer on the map and drag it to a new position.
7. Click the Point Analysis button ( ) on the toolbar again to end the point analysis.
The reference signal reception from the The connection status (SCH/PBCH,
best server (top-most bar) and all downlink and uplink) for the current point.
interfering cells. Solid bars indicate the
signal levels above the reference signal C/ : Service available
N thresholds.
: Service unavailable
7. Under Exceptional Pairs, create a new exceptional pair in the row marked with the New Row icon ( ):
a. Select the cell from the list in the Neighbours column.
b. In the Status column, select one of the following:
- Forced: The selected cell will always be a neighbour of the reference cell.
- Forbidden: The selected cell will never be a neighbour of the reference cell.
8. Click elsewhere in the table when you have finished creating the new exceptional pair.
9. Click OK.
Notes: You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology
Neighbours table. You can open this table by right-clicking the Transmitters folder and
selecting Cells > Neighbours > Intra-Technology Exceptional Pairs.
- Shadowing taken into account: If desired, select the Shadowing taken into account check box and
enter a Cell Edge Coverage Probability.
- Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses defined per
clutter class in the calculations.
- Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic
neighbour allocation.
- % Min. Covered Area: Enter the minimum surface area, in percentage, that a possible neighbour cells cov-
erage area must overlap the reference cells coverage area.
6. Select the desired calculation parameters:
- Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want
cells located on the same site as the reference cell to be automatically considered as neighbours.
- Force adjacent cells as neighbours: Select the Force adjacent cells as neighbours check box if you want
cells that are adjacent to the reference cell to be automatically considered as neighbours. A cell is considered
adjacent if there is at least one pixel in the reference cells coverage area where the possible neighbour cell
is the best server, or where the possible neighbour cell is the second best server (respecting the handover
margin).
- Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In
other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neigh-
bour list of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from
the list of neighbours of the reference cell.
- Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or
forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see
"Defining Exceptional Pairs" on page 1052.
- Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete
all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check
box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new
neighbours to the list.
Figure 14.46: The handover area between the reference cell and the possible neighbour
7. Click the Importance Weighting button to set the relative importance of possible neighbours:
- Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage
reasons.
- Adjacency Factor: If you have selected the Force adjacent cells as neighbours check box in step 6., set
the minimum and maximum importance of a possible neighbour cell being adjacent to the reference cell.
- Co-site Factor: If you have selected the Force co-site cells as neighbours check box in step 6., set the
minimum and maximum importance of a possible neighbour cell being located on the same site as reference
cell.
8. Click Calculate. Atoll begins the process of allocating neighbours. Atoll first checks to see whether the path loss
matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates them.
Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays
new neighbours. If no new neighbours have been found and if the Deleting existing neighbours check box is
cleared, the Results table will be empty.
Notes:
A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already
exists and the Delete existing neighbours check box is cleared when you start the new allo-
cation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint
on the forbidden neighbour will be ignored by the algorithm because the neighbour already
exists.
When the options Force exceptional pairs and Force symmetry are selected, Atoll con-
siders the constraints between exceptional pairs in both directions in order to respect sym-
metry. On the other hand, if the neighbour relation is forced in one direction and forbidden in
the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the
Event Viewer.
You can save automatic neighbour allocation parameters in a user configuration. For informa-
tion on saving automatic neighbour allocation parameters in a user configuration, see
"Exporting a User Configuration" on page 75.
1. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
2. Select Display Options from the context menu. The Visual Management dialogue appears.
3. Under Intra-technology Neighbours, select the Display Links check box.
4. Click the Browse button ( ) beside the Display Links check box.
5. The Intra-technology Neighbour Display dialogue appears.
6. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a cell with a
unique colour.
- Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you
want Atoll to colour the cells neighbour links according to a value from the Intra-technology Neighbours
table, or according to the neighbour frequency band.
- Value Intervals: Select "Value Intervals" to colour the cells neighbour links according the value interval of the
value selected from the Field list. For example, you can choose to display a cells neighbours according to the
importance, as determined by the weighting factors.
Tip: You can display the number of handoff attempts for each cell-neighbour pair by first
creating a new field of Type "Integer" in the Intra-Technology Neighbour table for the
number of handoff attempts. Once you have imported or entered the values in the new
column, you can select this field from the Field list along with "Value Intervals" as the
Display Type. For information on adding a new field to a table, see "Adding a Field to an
Object Types Data Table" on page 51.
Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you
can display or hide neighbour link display types individually.
For information on changing display properties, see "Display Properties of Objects" on page 33.
7. Select the Add to Legend check box to add the displayed neighbour links to the legend.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each neighbour link.
9. Click OK to save your settings.
10. Under Advanced, select which neighbour links to display:
- Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations
where the selected cell is the reference cell and where the neighbour relation is not symmetric.
- Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations
where the selected cell is neighbour and where the neighbour relation is not symmetric.
- Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the
selected cell and the neighbour.
11. Click OK to save your settings.
12. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
- The symmetric neighbour relations of the selected (reference) cell are indicated by a line.
- The outward neighbour relations are indicated with a line with an arrow pointing at the neighbour (e.g. see
Site1_2(0)) in Figure 14.47.).
- The inward neighbour relations are indicated with a line with an arrow pointing at the selected cell (e.g. see
Site9_3(0)) in Figure 14.47.).
In Figure 14.47, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward
neighbour links are coloured as the corresponding neighbour transmitters and the inward neighbour link is
coloured as the reference transmitter as it is neighbour of Site9_3(0) here.
In Figure 14.48, neighbour links are displayed according to the neighbour frequency. Here, all neighbour relations
are symmetric.
Figure 14.48: Neighbours of Site 22_3(0) - Display According to The Neighbour Frequency
Note: You can display either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting
either Forced Neighbours or Forbidden Neighbours.
2. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
3. Select Display Options from the context menu. The Neighbourhood Display dialogue appears.
4. Under Intra-technology Neighbours, select the Display Coverage Areas check box.
5. Click the Browse button ( ) beside the Display Coverage Areas check box.
6. The Intra-technology Neighbour Display dialogue appears.
7. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage area of a cells neigh-
bours with a unique colour.
- Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you
want Atoll to colour the coverage area of a cells neighbours according to a value from the Intra-technology
Neighbours table.
- Value Intervals: Select "Value Intervals" to colour the coverage area of a cells neighbours according the
value interval of the value selected from the Field list. For example, you can choose to display a cells neigh-
bours according to the importance, as determined by the weighting factors.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each coverage area.
9. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( ) in the
Radio toolbar.
Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete LTE neighbours using the Cells tab of the transmitters Properties dialogue:
1. On the map, right-click the transmitter whose neighbours you want to change. The context menu appears.
2. Select Properties from the context menu. The transmitters Properties dialogue appears.
3. Click the Cells tab.
4. On the Cells tab, click the Browse button ( ) beside Neighbours. The cells Properties dialogue appears.
5. Click the Intra-technology Neighbours tab.
6. If desired, you can enter the maximum number of neighbours.
7. Allocate or delete a neighbour.
To allocate a new neighbour:
a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon
( ).
b. Click elsewhere in the table when you have finished creating the new neighbour.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Right-click the neighbour in the Neighbour column. The context menu appears.
c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation be-
tween the cell in the Neighbour column and the cell in the Cell column is deleted.
To delete a neighbour:
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Press DEL to delete the neighbour.
8. Click OK.
Note: For information on working with data tables, see "Working with Data Tables" on page 50.
a. In the row marked with the New Row icon ( ), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column.
c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
a. Right-click the neighbour in the Neighbour column. The context menu appears.
b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the
Neighbour column and the cell in the Cell column.
To make several neighbour relations symmetric:
a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select
contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contig-
uous rows by pressing CTRL and clicking each rows separately.
b. Right-click the Neighbours table. The context menu appears.
c. Select Symmetrise from the context menu.
To take into consideration all exceptionnal pairs:
Note: You can add or delete either some forced neighbours or some forbidden neighbours using
the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table,
select the exceptional pairs to be considered, right-click the table and select Force
Exceptional Pairs in the context menu.
a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select
contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contig-
uous rows by pressing CTRL and clicking each rows separately.
b. Right-click the Neighbours table. The context menu appears.
c. Select Delete Link and Symmetric Relation from the context menu.
To delete a neighbour:
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Press DEL to delete the neighbour.
You can allocate or delete intra-technology neighbours directly on the map using the mouse.
To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neigh-
bours on the map as explained in "Displaying Neighbour Relations on the Map" on page 1055.
To add a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters
to the intra-technology neighbours list.
To remove a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both trans-
mitters from the intra-technology neighbours.
To add an outward neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference
transmitter to the intra-technology neighbour list of the transmitter.
Notes:
When there is more than one cell on the transmitter, clicking the transmitter in the map window
opens a context menu allowing you to select the cell you want (see "Selecting One of Several
Transmitters or Microwave Links" on page 30).
You can add or delete either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting either
Forced Neighbours or Forbidden Neighbours.
Note: If the field Max number of intra-technology neighbours in the Cells table is empty, the
Full Lists check and the Lists > Max Number check use the Default Max Number value
defined in the audit dialogue.
- Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
- Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
The AFP enables you to automatically allocate frequencies to cells in the current network.
To automatically allocate frequencies:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Frequency Plan > Automatic Allocation. The Frequency Allocation dialogue appears.
4. You can set the following parameters:
- Under Allocate, you can select Frequencies to perform automatic frequency planning or Physical Cell IDs
to allocate physical cell IDs to cells automatically.
- If you have selected Physical Cell IDs under Allocate, under S-SCH ID Allocation Strategy, you can select
one of the following automatic allocation strategies:
- Free
- Same per Site
For more information on the strategies, see "Automatically Allocating Physical Cell IDs to LTE Cells" on
page 1065.
- Under Relations, you can set the relations to take into account in automatic allocation.
- Under Interference Matrices, you can calculate and take interference matrices into account for the fre-
quency allocation. When the Frequency Allocation dialogue opens, the Take into account check box is
disabled because interference matrices are not yet calculated nor available.
To calculate interference matrices:
i. Click the Details button. The Interference Matrices Display dialogue appears. This dialogue lists all the
interfered and interfering cell pairs and their respective interference probabilities in co- and adjacent chan-
nel cases.
ii. Click the Close button. The Interference Matrices Display dialogue closes.
To delete the calculated interference matrices:
- Click the Delete button.
To take the calculated interference matrices into account:
- Select the Take into account check box.
Interference Matrices Calculation and Quality Margin:
Interference matrices calculated by the AFP are the co- and adjacent channel interference probabilities
for each interfered and interfering cell pair. The probability of interference of a cell is defined as the ratio
of the interfered surface area within the best server coverage area of any studied cell to the total best serv-
er coverage area of the cell:
S Int
P Int = --------------
-
S Total
In words, S Total is the best server coverage area of the studied cell, and S Int is the surface area within
the best server area of the studied cell where the interference from another cell is higher than the refer-
ence signal C/N threshold of the studied cell plus the quality margin.
The quality margin is defined with respect to the reference signal C/N thresholds of cells. By default the
reference signal C/N threshold outlines the area of service of a cell. This means that where the reference
signal C/N of a cell is less than the reference signal C/N threshold, there is no service. The AFP uses the
quality margin to calculate interference within the service areas of cells.
- Take min reuse distance into account: Select this check box if you want the AFP to take relations based
on distance into account for the allocation. You can enter the Default radius within which two cells whose
channels have a co-channel overlap cannot have the same frequency or physical cell ID.
Note: A minimum reuse distance can be defined at the cell level (in the cell Properties dialogue
or in the Cells table). If defined, a cell-specific reuse distance will be used instead of
default the value entered here.
- Take neighbours into account: Select this check box if you want the AFP to take neighbour relations
into account for the allocation. The AFP will try to avoid allocating the same frequency or physical cell ID
to neighbours of each cell being allocated.
Atoll can only take neighbour relations into account if neighbours have already been allocated. For infor-
mation on allocating neighbours, see "Planning Neighbours" on page 1052.
5. Under Results, Atoll displays the Total Cost of the current frequency or physical cell ID allocation taking into
account the parameters set in step 4. You can modify the parameters and click Recalculate Cost to see the
change in the total cost.
6. Click Calculate. Atoll begins the process of allocating frequencies or physical cell IDs.
Once Atoll has finished allocating frequencies or physical cell IDs, the proposed allocation is visible under
Results.
When you allocate frequencies to a large number of cells, it is easiest to let Atoll allocate them automatically, as described
in "Automatically Allocating Frequencies to Cells" on page 1062. However, if you want to assign a frequency or a physical
cell ID to one cell or to modify it, you can do it by accessing the properties of the cell.
To allocate the frequency or physical cell ID to a cell manually:
1. On the map, right-click the transmitter to whose cell you want to allocate the frequency or physical cell ID. The
context menu appears.
2. Select Properties from the context menu. The transmitters Properties dialogue appears.
3. Select the Cells tab.
4. Select a Frequency Band and Channel Number for the cell or enter a Physical Cell ID.
5. You can set the Channel Allocation Status or Physical Cell ID Status to Fixed if you want to lock the frequency
or physical cell ID that you assigned.
6. Click OK.
In Atoll, you can search for frequency bands and channel numbers using the Search Tool.
If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results
displayed by transmitter, the search results will be displayed by transmitter coverage. Frequencies and any potential prob-
lems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage Prediction
by Transmitter" on page 1026.
To find a frequency band using the Search Tool:
1. Click View > Search Tool. The Search Tool window appears.
2. Select the Channel tab.
3. Select a Frequency Band from the list of available frequency bands.
4. Set Channel Number to All.
5. Click Search.
Transmitters whose cells use the selected frequency band are displayed in red. Transmitters with cells using other
frequency bands are displayed in grey.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
If you selected the Co-channel Only check box, transmitters with cells using the same channel number are
displayed in red, and all others, including transmitters with adjacent channels, are displayed in grey.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
Note: By including the frequency band and channel number of each cell in the transmitter label,
the search results will be easier to understand. For information on defining the label, see
"Defining the Object Type Label" on page 35.
You can display the frequency allocation on transmitters by using the transmitters display characteristics.
To display the frequency allocation on the map:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Display tab.
5. Select "Discrete Values" as the Display Type and "Cells: Channel Number" as the Field.
6. Click OK. Transmitters will be displayed by channel number.
You can also display the frequency band and channel number in the transmitter label or tooltip by selecting "Cells:
Frequency Band" and "Cells: Channel Number" from the Label or Tip Text Field Definition dialogue.
For information on display options, see "Display Properties of Objects" on page 33.
You can group transmitters on the Data tab of the Explorer window by their frequency bands or channel numbers.
To group transmitters by frequency bands or channel numbers:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the General tab, click Group by. The Group dialogue appears.
5. Under Available Fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
- Frequency Band
- Channel Number
- Min Reuse Distance
- Channel Allocation Status
7. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to
the list of parameters on which the transmitters will be grouped.
8. If you do not want the transmitters to be sorted by a certain parameter, select the parameter in the Group these
fields in this order list and click . The selected parameter is removed from the list of parameters on which
the transmitters will be grouped.
9. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters
to be grouped:
10. Click OK to save your changes and close the Group dialogue.
You can create and compare reference signal C/(I+N) coverage predictions before and after the automatic frequency allo-
cation in order to analyse and compare the improvements brought about by the AFP. For more information on creating
reference signal C/(I+N) coverage predictions, see "Making a Coverage by C/(I+N) Level" on page 1041. For more infor-
mation on comparing two coverage predictions, see "Comparing Coverage Predictions: Examples" on page 1032.
The allocation algorithm enables you to automatically allocate physical cell IDs to cells in the current network. You can
choose from two allocation strategies for the S-SCH ID (for more information, see the Technical Reference Guide):
Free: The physical cell ID allocation will only be restricted by the P-SCH ID allocated to nearby cells. S-SCH IDs
will not necessarily be the same for all the cells of a site.
Same per Site: This strategy allocates physical cell IDs to cells such that the same S-SCH ID is assigned to all
the cells of a site.
- Min Reuse Distance: Select the Min Reuse Distance check box if you want to consider relations based
on distance. You can enter the Default radius within which two cells whose channels have a co-channel
overlap cannot have the same physical cell ID.
Note: A minimum reuse distance can be defined at the cell level (in the cell Properties dialogue
or in the Cells table). If defined, a cell-specific reuse distance will be used instead of
default the value entered here.
- Under S-SCH ID Allocation Strategy, you can select one of the following automatic allocation strategies:
- Free
- Same per Site
5. Under Results, Atoll displays the Total Cost of the current physical cell ID allocation taking into account the
parameters set in step 4. You can modify the parameters and click Recalculate Cost to see the change in the
total cost.
6. Click Calculate. Atoll begins the process of allocating physical cell IDs.
Once Atoll has finished allocating physical cell IDs, the IDs are visible under Results.
When you allocate physical cell IDs to a large number of cells, it is easiest to let Atoll allocate physical cell IDs automati-
cally, as described in "Automatically Allocating Physical Cell IDs to LTE Cells" on page 1065. However, if you want to
assign a physical cell ID to one cell or to modify it, you can do it by accessing the properties of the cell.
To allocate a physical cell ID to an LTE cell manually:
1. On the map, right-click the transmitter to whose cell you want to allocate a physical cell ID. The context menu
appears.
2. Select Properties from the context menu. The transmitters Properties dialogue appears.
3. Select the Cells tab.
4. Enter a Physical Cell ID in the cells column.
5. You can set the Physical Cell ID Status to Fixed if you want to lock the physical cell ID that you assigned.
6. Click OK.
In Atoll, you can search for physical cell IDs, P-SCH IDs, and S-SCH IDs using the Search Tool.
If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results
displayed by transmitter, the search results will be displayed by transmitter coverage. Physical cell IDs and any potential
problems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage
Prediction by Transmitter" on page 1026.
To find a physical cell ID using the Search Tool:
1. Click View > Search Tool. The Search Tool window appears.
2. Select the Physical Cell ID tab.
3. Select Physical Cell ID.
4. Enter a Physical Cell ID.
5. Click Search.
Transmitters whose cells use the entered physical cell ID are displayed in red. Transmitters with cells use other
physical cell IDs are displayed in grey.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
Note: By including the physical cell ID of each cell in the transmitter label, the search results will
be easier to understand. For information on defining the label, see "Defining the Object
Type Label" on page 35.
Transmitters whose cells use the entered S-SCH ID are displayed in red. Transmitters with cells use other S-SCH
IDs are displayed in grey.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
You can display physical cell ID allocation on transmitters by using the transmitters display characteristics.
To display physical cell ID allocation on the map:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Display tab.
5. Select "Discrete Values" as the Display Type and "Cells: Physical Cell ID" as the Field.
6. Click OK. Transmitters will be displayed by physical cell ID.
You can also display the physical cell ID in the transmitter label or tooltip by selecting "Cells: Physical Cell ID" from the
Label or Tip Text Field Definition dialogue.
For information on display options, see "Display Properties of Objects" on page 33.
You can group transmitters on the Data tab of the Explorer window by their physical cell ID or their reuse distance.
To group transmitters by physical cell ID:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the General tab, click Group by. The Group dialogue appears.
5. Under Available Fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
- Physical Cell ID
- Min Reuse Distance
- Physical Cell ID Status
7. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to
the list of parameters on which the transmitters will be grouped.
8. If you do not want the transmitters to be sorted by a certain parameter, select the parameter in the Group these
fields in this order list and click . The selected parameter is removed from the list of parameters on which
the transmitters will be grouped.
9. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters
to be grouped:
10. Click OK to save your changes and close the Group dialogue.
You can use a histogram to analyse the use of allocated physical cell IDs in a network. The histogram represents the phys-
ical cell IDs as a function of the frequency of their use.
To display the physical cell ID histogram:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Physical Cell IDs > ID Distribution. The Distribution Histograms dialogue appears.
Each bar represents a physical cell ID, its height depending on the frequency of its use.
4. Move the pointer over the histogram to display the frequency of use of each physical cell ID. The results are high-
lighted simultaneously in the Detailed Results list.
Traffic map per user profile can be used if you have marketing-based traffic data.
Traffic maps per density of user profiles, where each vector (polygon, line or point) describes subscriber densities
(or numbers of subscribers for points) with user profiles and mobility types, and traffic maps per environment of
user profiles, where each pixel has an assigned environment class. For more information, see "Importing a Traffic
Map Based on Densities of User Profiles" on page 1072, "Importing a Traffic Map Based on Environments of User
Profiles" on page 1074 and "Creating a Traffic Map Based on Environments of User Profiles" on page 1074.
Traffic maps per density (number of users per km2) can be used if you have population-based traffic data,
or 2G network statistics.
Each pixel has an actual user density assigned. For more information, see "Creating Traffic Maps per User
Density (No. Users/km2)" on page 1075, "Importing a Traffic Map per User Density" on page 1075, "Converting
2G Network Traffic" on page 1076 and "Exporting Cumulated Traffic" on page 1077
Note: You can also import a traffic map from a file by clicking the Import button. You can import
AGD (Atoll Geographic Data) format files that you have exported from another Atoll
document.
7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter.
8. Enter the data required in the Map per Sector dialogue:
- If you have selected Throughputs in Uplink and Downlink, enter the throughput demands in the uplink and
downlink for each sector and for each listed service.
- If you have selected Number of Users per Activity Status, enter the number of users active in the uplink, in
the downlink and in the uplink and downlink, for each sector and for each service.
Note: You can also import a text file containing the data by clicking the Actions button and
selecting Import Table from the menu. For more information on importing table data, see
"Importing Tables from Text Files" on page 59.
4. Select Update from the context menu. The Map per Sector dialogue appears.
Select the updated coverage prediction by transmitter and define traffic values for the new transmitter(s) listed at
the bottom of the table. Deleted or deactivated transmitters are automatically removed from the table.
You can model variations in user behaviour by creating different profiles for different times of the day or for different circum-
stances. For example, a user may be considered a business user during the day, with video conferencing and voice, but
no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and
web browsing.
To create or modify a user profile:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the LTE Parameters folder.
3. Right-click the User Profiles folder. The context menu appears.
4. Select New from the context menu. The User Profiles New Element Properties dialogue appears.
Note: You can modify the properties of an existing user profile by right-clicking the user profile in
the User Profiles folder and selecting Properties from the context menu.
Note: In order for all the services defined for a user profile to be taken into account during traffic
scenario elaboration, the sum of activity probabilities must be lower than 1.
- Duration (sec.): For services of the type "voice," enter the average duration of a call in seconds. For services
of the type "data," this field is left blank.
- UL Volume (KBytes): For services of the type "data," enter the average uplink volume per session in kilo-
bytes.
- DL Volume (KBytes): For services of the type "data," enter the average downlink volume per session in kil-
obytes.
6. Click OK.
Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a
given density (i.e., the number of users with the same profile per km). To get an appropriate user distribution, you can
assign a weight to each clutter class for each environment class. You can also specify the percentage of indoor subscribers
for each clutter class. In a Monte Carlo simulation, an additional loss (as defined in the clutter class properties) will be
added to the indoor users path loss.
To create or modify an LTE environment:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the LTE Parameters folder.
3. Right-click the Environments folder. The context menu appears.
4. Select New from the context menu. The Environments New Element Properties dialogue appears.
Note: You can modify the properties of an existing environment by right-clicking the
environment in the Environments folder and selecting Properties from the context
menu.
7. In the row marked with the New Row icon ( ), set the following parameters for each user profile/mobility com-
bination that this LTE environment will describe:
- User: Select a user profile.
- Mobility: Select a mobility type.
- Density (Subscribers/km2): Enter a density in terms of subscribers per square kilometre for the combination
of user profile and mobility type.
8. Click the Clutter Weighting tab.
9. For each clutter class, enter a weight that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk Sk
N k = N Area --------------------------
Wi Si
i
where:
For example: An area of 10 km with a user density of 100/km. Therefore, in this area, there are 1000 users. The
area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1" and for Building is
"4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter class and 800 in
the Building clutter class.
10. If you wish you can specify a percentage of indoor users for each clutter class. During a Monte Carlo simulation,
an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
11. Click OK.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 1074.
- User Profile: If you want to import user profile information from the file, under Defined, select "By field" and
select the source field from the Choice column. If you want to assign a user profile from the LTE Parameters
folder of the Data tab, under Defined, select "By value" and select the user profile in the Choice column.
- Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select
the source field from the Choice column. If you want to assign a mobility type from the LTE Parameters folder
of the Data tab, under Defined, select "By value" and select the mobility type in the Choice column.
- Density: If you want to import density information from the file, under Defined, select "By field" and select the
source field from the Choice column. If you want to assign a density, under Defined, select "By value" and
enter a density in the Choice column for the combination of user profile and mobility type. In this context, the
term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kil-
ometre for polygons, the number of subscribers per kilometre in case of lines, and the number of subscribers
when the map consists of points.
Important: When you import user profile or mobility information from the file, the values in the file
must be exactly the same as the corresponding names in the LTE Parameters folder of
the Data tab. If the imported user profile or mobility does not match, Atoll will display a
warning.
13. Under Clutter Distribution, enter a weight for each class that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk Sk
N k = N Area --------------------------
Wi Si
i
where:
14. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simu-
lation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
15. Click OK to finish importing the traffic map.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 1074.
7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, BIL, IST,
BMP, PlaNET, GRC Vertical Mapper, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears.
11. Select the Description tab.
In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the
Code column.
12. For each Code, select the environment it corresponds to from the Name column.
The environments available are those available in the Environments folder, under LTE Parameters on the Data
tab of the Explorer window. For more information, see "Modelling Environments" on page 1072.
13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects"
on page 33.
14. Click OK.
7. Select the environment class from the list of available environment classes.
8. Click the Draw Polygon button ( ) to draw the polygon on the map for the selected environment class.
9. Click the Delete Polygon button ( ) and click the polygon to delete the environment class polygon on the map.
10. Click the Close button to close the Environment Map Editor toolbar and end editing.
5. Click Close.
If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per
clutter class.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 1074.
7. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP,
PlaNET, TIF, ISTAR, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic maps properties dialogue appears.
17. Click OK. Atoll creates the traffic map in the Traffic folder.
12. Click OK. Atoll creates the traffic map in the Traffic folder.
13. Right-click the traffic map. The context menu appears.
14. Select Edit from the context menu.
15. Use the tools available in the Vector Edition toolbar in order to draw contours. For more information on how to edit
contours, see "Editing Contours, Lines, and Points" on page 131. Atoll creates an item called Density values in
the User Density Map folder.
16. Right-click the item. The context menu appears.
17. Select Open Table from the context menu.
18. In the table, enter a traffic density value (i.e. the number of users per km2) for each contour you have drawn.
19. Right-click the item. The context menu appears.
20. Select Edit from the context menu to end editing.
Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains
at "0" and no data will be exported.
8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic
data to be exported.
- Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal.
- Service: Select the service that will be exported, or select "Circuit services" to export voice traffic, or select
"Packet services" to export data traffic.
- Mobility: Select the mobility type that will be exported or select "All" to export all mobility types.
- Activity: Select one of the following:
- All Activity Statuses: Select All Activity Statuses to export all users without any filter by activity status.
- Uplink: Select Uplink to export mobiles active in the uplink only.
- Downlink: Select Downlink to export mobiles active in the downlink only.
- Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity.
9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the
cumulated traffic.
10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.
- ID: The subscriber ID in the subscriber list. It is an automatically created identification number.
- X and Y coordinates: The geographical coordinates of the subscriber. A subscribers location is always fixed.
- Height: The altitude of the subscriber antenna with respect to the ground (DTM).
- Clutter: The name of the clutter class where the subscriber is located. This is a non-editable field whose con-
tents are automatically updated.
- Name: You can assign a descriptive name to each subscriber.
- User Profile: A user profile defines the traffic demand characteristics of subscribers. Atoll determines the ter-
minal used, the service accessed, and the activity status of subscribers during Monte Carlo simulations
according to the information in the user profiles. For more information, see "Modelling User Profiles" on
page 1071.
- Terminal: The default terminal is the user equipment with an antenna, LTE equipment, and noise character-
istics. The properties of this terminal are taken into consideration when performing calculations on the sub-
scriber list.
- Service: The service that the subscriber accesses by default. The properties of this service are taken into con-
sideration when performing calculations on the subscriber list.
Note: Subscriber lists use the mobility type "Fixed", i.e., 0 km/hr, in calculations. Make sure that
you have bearer selection thresholds defined for this mobility type in the LTE equipment
properties. For information on defining bearer selection thresholds, see "Defining LTE
Equipment" on page 1104.
- Azimuth: The orientation of the subscriber antenna in the horizontal plane. Azimuth is always considered with
respect to the north. You can either define this value manually or let Atoll calculate it for the subscriber. Atoll
points the subscriber antenna towards its serving base station.
- Mechanical Downtilt: The orientation of the subscriber antenna in the vertical plane. Mechanical downtilt is
positive when it is downwards and negative when upwards. You can either define this value manually or let
Atoll calculate it for the subscriber. Atoll points the subscriber antenna towards its serving base station.
- Lock Status: You can choose to lock the subscriber antenna orientation and serving transmitter. Use this
option if you do not want Atoll to change the assigned server or the antenna orientation.
- Serving Base Station: The serving transmitter of the subscriber. You can either define this value manually
or let Atoll calculate it for the subscriber. The serving base station is determined according to the received
reference signal level from the cell with the highest power.
- Reference Cell: The reference cell of the serving transmitter of the subscriber. You can either define this value
manually or let Atoll calculate it for the subscriber. If more than one cell of the serving base station cover the
subscriber, the one with the lowest order is selected as the reference cell.
- Distance: The distance of the subscriber from its serving base station. This is a non-editable field whose con-
tents are automatically updated.
- Received Reference Signal Power (DL) (dBm): The reference signal level received at the subscriber loca-
tion in the downlink. This value is calculated by Atoll during calculations on subscriber lists.
- Received SCH/PBCH Power (DL) (dBm): The SCH/PBCH signal level received at the subscriber location in
the downlink. This value is calculated by Atoll during calculations on subscriber lists.
- Received PDSCH/PDCCH Power (DL) (dBm): The PDSCH/PDCCH signal level received at the subscriber
location in the downlink. This value is calculated by Atoll during calculations on subscriber lists.
- SCH/PBCH Total Noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the sub-
scriber location in the downlink on the SCH and PBCH. This value is generated by Atoll during the calculations
on subscriber lists.
- PDSCH/PDCCH Total Noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the
subscriber location in the downlink on the PDSCH and PDCCH. This value is generated by Atoll during the
calculations on subscriber lists.
- Reference Signal C/(I+N) (DL) (dB): The reference signal C/(I+N) at the subscriber location in the downlink.
This value is generated by Atoll during the calculations on subscriber lists.
- SCH/PBCH C/(I+N) (DL) (dB): The SCH/PBCH C/(I+N) at the subscriber location in the downlink. This value
is generated by Atoll during the calculations on subscriber lists.
- PDSCH/PDCCH C/(I+N) (DL) (dB): The PDSCH/PDCCH C/(I+N) at the subscriber location in the downlink.
This value is generated by Atoll during the calculations on subscriber lists.
- Bearer (DL): The highest LTE bearer available for the PDSCH/PDCCH C/(I+N) level at the subscriber location
in the downlink. This value is generated by Atoll during the calculations on subscriber lists.
- BLER (DL): The Block Error Rate read from the subscribers terminal types LTE equipment for the PDSCH/
PDCCH C(I+N) level at the subscriber location in the downlink. This value is generated by Atoll during the
calculations on subscriber lists.
- Diversity Mode (DL): The diversity mode supported by the cell or permutation zone in downlink.
- Peak RLC Channel Throughput (DL) (kbps): The maximum RLC channel throughput attainable using the
highest bearer available at the subscriber location in the downlink. This value is generated by Atoll during the
calculations on subscriber lists.
- Effective RLC Channel Throughput (DL) (kbps): The effective RLC channel throughput attainable using the
highest bearer available at the subscriber location in the downlink. This value is generated by Atoll during the
calculations on subscriber lists.
- Received PUSCH/PUCCH Power (UL) (dBm): The PUSCH/PUCCH signal level received at the serving
transmitter from the subscriber terminal in the uplink. This value is generated by Atoll during the calculations
on subscriber lists.
- PUSCH/PUCCH Total Noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the
serving transmitter of the subscriber in the uplink on the PUSCH. This value is generated by Atoll during the
calculations on subscriber lists.
- PUSCH/PUCCH C/(I+N) (UL) (dB): The PUSCH/PUCCH C/(I+N) at the serving transmitter of the subscriber
in the uplink. This value is generated by Atoll during the calculations on subscriber lists.
- Bearer (UL): The highest LTE bearer available for the PUSCH/PUCCH C/(I+N) level at the serving transmitter
of the subscriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists.
- BLER (UL): The Block Error Rate read from the reference cells LTE equipment for the PUSCH/PUCCH C/
(I+N) level at the serving transmitter of the subscriber in the uplink. This value is generated by Atoll during the
calculations on subscriber lists.
- Diversity Mode (UL): The diversity mode supported by the cell or permutation zone in uplink.
- Transmission Power (UL) (dBm): The transmission power of the subscribers terminal after power control in
the uplink. This value is generated by Atoll during the calculations on subscriber lists.
- Allocated Bandwidth (UL) (No. of Frequency Blocks): The number of frequency blocks allocated to the
subscriber in the uplink by the eNode-B. This value is generated by Atoll during the calculations on subscriber
lists.
- Peak RLC Channel Throughput (UL) (kbps): The maximum RLC channel throughput attainable using the
highest bearer available at the serving transmitter of the subscriber in the uplink. This value is generated by
Atoll during the calculations on subscriber lists.
- Effective RLC Channel Throughput (UL) (kbps): The effective RLC channel throughput available using the
highest bearer available at the serving transmitter of the subscriber in the uplink. This value is generated by
Atoll during the calculations on subscriber lists.
For more information on the calculations that you can carry out on subscriber lists, see "Performing Calculations
on Subscriber lists" on page 1081.
6. Click the Display tab. You can modify how subscribers added to the list are displayed. For information on defining
the display properties, see "Display Properties of Objects" on page 33.
7. Click OK. Atoll creates a new subscriber list.
You can now move the pointer over the map and click once to place a new subscriber at the location of the pointer. Press
ESC or click the normal pointer button ( ), to finish adding subscribers on the map. For information on adding subscribers
to a list, see "Adding Subscribers to a Subscriber List Using the Mouse" on page 1080.
You can open the subscriber list table containing all the subscribers and their parameters.
To open the subscriber list table:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Subscribers folder.
3. Right-click the subscriber list you want to open. The context menu appears.
4. Select Open Table from the context menu.
For information on working with data tables, see "Working with Data Tables" on page 50.
4. Select Add Subscribers from the context menu. The pointer changes to subscriber addition mode ( ).
5. Move the mouse over the Map window, and click once to add each subscriber.
6. Press ESC or click the normal pointer button ( ) to finish adding subscribers.
Tip: To place subscribers more accurately, before clicking the map, you can zoom in on the
map. For information on using the zooming tools, see "Changing the Map Scale" on
page 38.
Note: You can also export subscriber lists. For information on exporting table data, see
"Exporting Tables to Text Files" on page 58.
5. Click Calculate. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
6. Once the calculations are finished, click Close to close the Event Viewer.
7. Click Commit to store the results in the subscriber list. For the list of results that are available after the calculations,
see "Creating a Subscriber List" on page 1078.
Each mobile generated during the simulations is assigned a service, a mobility type, and a terminal according to
the user profile assigned to it. A transmission status is determined according to the activity probabilities. The trans-
mission status is an important output of the simulation as it has a direct impact on the next step of the simulation
process, i.e., the radio resource management (RRM), and has an impact on the interference level in the network.
The geographical location of each mobile is determined randomly for the mobiles generated based on the traffic
data from traffic maps. The mobiles generated based on the traffic data from subscriber lists are located on the
subscriber locations.
3. Downlink Calculations
The downlink calculations include the calculation of downlink reference signal, SCH/PBCH, and PDSCH/PDCCH
C/(I+N), determination of the best available bearer for the PDSCH/PDCCH C/(I+N), allocation of resources (RRM),
and calculation of user throughputs.
4. Uplink Calculations
The uplink calculations include the calculation of PUSCH/PUCCH C/(I+N), determination of the best available
bearer for the PUSCH/PUCCH C/(I+N), uplink power control and calculation of the number of allocated frequency
blocks depending on the bearer, allocation of resources (RRM), update of uplink noise rise values for cells, and
calculation of user throughputs.
At the end of the simulations, an active user can be connected in the direction corresponding to his activity status if:
he has a best server assigned (step 2.),
he has a bearer in the direction corresponding to his activity status (step 3. and step 4.),
he is among the users selected by the scheduler for resource allocation (step 5.), and
he is not rejected due to resource saturation (step 5.).
If a user is rejected during step 2., step 3., or step 4., the cause of rejection is "No Service". If a user is rejected during
step 5., the cause of rejection can either be "Scheduler Saturation," i.e., the user is not among the users selected for
resource allocation, or he can be rejected due to "Resource Saturation," i.e., all of the cells resources were used up by
other users.