Atoll LTE Planning PDF

CHAPTER 0
LTE NETWORKS
Atoll
Global RF Planning Solution
Chapter 0: LTE Networks
0 LTE Networks
LTE (Long Term Evolution) refers to the set of 3GPP standards which use SOFDMA (Scalable Orthogonal Frequency Divi-
sion Multiple Access) and SC-FDMA (Single Carrier Frequency Division Multiple Acess) technologies. The 3GPP LTE
standard is currently under development, and, therefore, undergoes frequent modifications and updates. The aim of LTE
as the evolutionary next step for UMTS and GSM standards 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 transmit diversity and spatial multiplex-
ing (MIMO).
Atoll enables you to model fixed and mobile users in LTE environments. The data input corresponding to fixed subscribers
is modelled using a subscriber database integrated into the module. 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 realistic user distributions as input for simulations.
Coverage predictions can be created to study the following parameters:
The reference and SCH signal levels received from cells
The carrier-to-interference-and-noise ratio
The radio bearer coverage
The channel throughput 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, IS-95 cdmaOne, 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 87. This will help you get accustomed to the
terminology used in Atoll.
0.1 Designing an LTE Network

Figure 0.1 depicts the process of creating and planning an LTE network. The steps involved in planning an LTE network
are described below. The numbers refer to Figure 0.1.
1. Open an existing radio-planning document or create a new one ( 1 ).

- You can open an existing Atoll document by selecting File > Open.
- Creating a new Atoll document is explained in "Chapter 2: Starting an Atoll Project".
2. Configure the network by adding network elements and changing parameters ( 2 ).

You can add and modify the following elements of base stations:
- "Creating or Modifying a Site" on page 8.

- "Creating or Modifying a Transmitter" on page 9.
- "Creating or Modifying a Cell" on page 9.
You can also add base stations using a base station template (see "Placing a New Base Station Using a Station
Template" on page 9).
3. Carry out basic coverage predictions ( 3 ).

- "Making a Point Analysis to Study the Profile" on page 16.
- "Studying Signal Level Coverage" on page 17 and "Signal Level Coverage Predictions" on page 24.
4. Before making more advanced coverage predictions, you need to define cell load conditions ( 4 ).
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 ( 4a , 4b , and 4c ) (see "Studying Network Capacity" on page 52).
- 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 9) ( 4d ).
5. Make LTE-specific coverage predictions using the defined cell load conditions ( 5 ).
- "LTE Coverage Predictions" on page 36.
Forsk 2008 Unauthorized reproduction or distribution of this document is prohibited 3

Atoll User Manual
6. If necessary, modify network parameters to study the network with a different frequency plan ( 6 ). After modifying
the networks frequency plan, you must perform steps 4 and 5 again.
4a
4c 4d
4b
4
6 5a
Figure 0.1: Planning an LTE network - workflow
0.2 Planning and Optimising LTE Base Stations

As described in "Chapter 2: Starting an Atoll Project", you can start an Atoll document from a template, with no base
stations, or from a database with a set of base stations. As you work on your Atoll document, you will still need to create
base stations and modify existing ones.
In Atoll, a site is defined as a geographical point where one or more transmitters are located. Once you have created a
site, you can add transmitters. In Atoll, a transmitter is defined as the antenna and any other additional equipment, such
as the TMA, feeder cables, etc. In an LTE project, you must also add cells to each transmitter. A cell refers to the charac-
teristics of an RF channel on a transmitter.
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 and
a transmitter with its antennas, equipment, and cells.
In Atoll, you can study a single base station or a group of base stations using coverage predictions. Atoll allows you to
make a variety of coverage predictions, such as signal level or signal quality coverage predictions. The results of calcu-
lated coverage predictions can be displayed on the map, compared, and 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 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 4.
"Creating a Group of Base Stations" on page 14.
"Modifying Sites and Transmitters Directly on the Map" on page 14.
"Display Hints for Base Stations" on page 14.
"Creating a Multi-Band LTE Network" on page 15.
"Setting the Working Area of an Atoll Document" on page 15.
"Studying a Single Base Station" on page 15.
"Studying Base Stations" on page 19.
0.2.1 Creating an LTE Base Station

When you create an LTE site, you create only the geographical point; you must add the transmitters and cells afterwards.
The site with a transmitter and its antennas, equipment, and cells is called a base station.
In this section, each element of a base station is described. If you want to add a new base station, see "Placing a New
Base Station Using a Station Template" on page 9. If you want to create or modify one of the elements of a base station,
4 Unauthorized reproduction or distribution of this document is prohibited Forsk 2008

see "Creating or Modifying a Base Station Element" on page 8. If you need to create a large number of base stations, Atoll
allows you to import them from another Atoll document or from an external source. For information, see "Creating a Group
of Base Stations" on page 14.
This section explains the various parts of the base station process:
"Definition of a Base Station" on page 5.
"Creating or Modifying a Base Station Element" on page 8.
"Placing a New Base Station Using a Station Template" on page 9.
"Managing Station Templates" on page 10.
"Creating Duplicates of an Existing Station" on page 13.
0.2.1.1 Definition of a Base Station

A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for
example, cells. You will usually create a new base station using a station template, as described in "Placing a New Base
Station Using a Station Template" on page 9. This section describes the following elements of a base station and their
parameters:
"Site Description" on page 5
"Transmitter Description" on page 5
"Cell Description" on page 7.
0.2.1.1.1 Site Description

The parameters of a site can be found in the sites Properties dialogue. The Properties dialogue has two tabs:
The General tab (see Figure 0.2):
- 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 39.
- 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.
Figure 0.2: New Site dialogue
0.2.1.1.2 Transmitter Description

The parameters of a transmitter can be found in the transmitters Properties dialogue. When you create a transmitter, the
Properties dialogue has two tabs: the General tab and the Transmitter tab. Once you have created a transmitter, its Prop-
erties dialogue has three additional tabs: the Cells tab (see "Cell Description" on page 7), the Propagation tab (see "Chap-
ter 5: Managing Calculations in Atoll"), and the Display tab (see "Display Properties of Objects" on page 40).
The General tab:
- Name: By default, Atoll names the transmitter after the site it is on, adding an underscore and a number. You
can enter a name for the transmitter, but for the sake of consistency, it is better to let Atoll assign a name. If
you want to change the way Atoll names transmitters, see the Administrator Manual.
- Site: You can select the Site on which the transmitter will be located. Once you have selected the site, you
can click the Browse button ( ) to access the properties of the site on which the transmitter will be located.
For information on the site Properties dialogue, see "Site Description" on page 5. You can click the New
button to create a new site on which the transmitter will be located.

Atoll User Manual
- Position relative to the site: You can modify the Position relative to the site, if you wish.
The Transmitter tab (see Figure 0.3):
Figure 0.3: Transmitter dialogue - Transmitter tab
- 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 using the Equipment Specifications dialogue which
appears when you click the Equipment button.
- On the Equipment Specifications dialogue (see Figure 0.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 137.
- 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 137.
- 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 137.
- 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.

Figure 0.4: The Equipment Specifications dialogue
Note: 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 Equip-
ment 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.
- 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.
- Number of Antenna Ports: Select the number of antenna ports used for transmit diversity or spatial multi-
plexing 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 80.
- 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 57.
0.2.1.1.3 Cell Description

In Atoll, a cell is defined as an RF channel, with all its characteristics, on a transmitter; the cell is the mechanism by which
you can configure an LTE network. Currently, the LTE module allows only one cell per transmitter.
When you create a transmitter, Atoll reminds you to create a cell for the transmitter. The following explains the parameters
of an LTE 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 an LTE 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.
Frequency Band: The cells frequency band from the Frequency Band list.
Channel Number: The number of the channel from the list of available channels.
Active: If this cell is to be active, you must select the Active check box.
Power (dBm): The cells transmission power.
Reception Equipment: You can select the cells reception equipment from the Reception Equipment list. For
more information, see "Defining LTE Reception Equipment" on page 78. The cells reception equipment parame-
ters are used in the uplink calculations.

Atoll User Manual
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 79.
Max Number of Users: The maximum number of simultaneous users supported by the cell.
AMS Threshold (dB): The C/N threshold for switching from spatial multiplexing to transmit diversity as the signal
conditions get worse than the given value. For more information on adaptive MIMO switching, see "Multiple Input
Multiple Output Systems" on page 80.
Reference Signal Quality Threshold (dB): The minimum reference signal C/N required for a user to be con-
nected to the cell. The referecen signal C/N is compared with this threshold to determine whether or not a user
can be connected to a cell.
Traffic Load (UL) (%): The uplink traffic load percentage. By default, the uplink traffic load is set to 100%.
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 manu-
ally to actual network values, or use the values calculated 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.
Antenna Diversity Support: The type of antenna diversity technique supported by the cell. You can select Single
Antenna, Transmit Diversity, Spatial Multiplexing, AMS, Single Antenna+Transmit Diversity, Single
Antenna+Spatial Multiplxing, or Single Antenna+AMS.
A cell that only supports Single Antenna does not have any antenna diversity mechanism, and only the users with
simple (non MIMO) terminals can connect to this cell. A cell that supports Transmit Diversity, Spatial Multiplex-
ing, or AMS can carry traffic using MIMO-capable terminals. For example, Single Antenna+AMS can support
ordinary as well as MIMO-capable terminals. Specific gains are applied according to the antenna diversity mech-
anisms supported by the cell and the terminal.
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 DUUU-DUUU,
DUUD-DUUD, or DUDD-DUDD. If the networks switching point periodicity is set to "Frame," you can select a
frame configuration of type DUUU-DDDDD, DUUD-DDDDD, or DUDD-DDDDD. For more information on the TDD
switching point periodicity, see "The Global Transmitter Parameters" on page 75.
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 48.
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.
0.2.1.2 Creating or Modifying a Base Station Element

A base station consists of the site, one or more transmitters, various pieces of equipment, and radio settings such as, for
example, cells. This section describes how to create or modify the following elements of a base station:
"Creating or Modifying a Site" on page 8
"Creating or Modifying a Transmitter" on page 9
"Creating or Modifying a Cell" on page 9
0.2.1.2.1 Creating or Modifying a Site

You can modify an existing site or you can create a new site. You can access the properties of a site, described in "Site
Description" on page 5, through the sites Properties dialogue. How you access the Properties dialogue depends on
whether you are creating a new site or modifying an existing site.
To create or modify a site:
1. If you are creating a new site:
a. Click the Data tab in the Explorer window.
b. Right-click the Sites folder. The context menu appears.
c. Select New from the context menu. The Sites New Element Properties dialogue appears (see Figure 0.2 on
page 5).
2. If you are modifying the properties of an existing site:
b. Click the Expand button ( ) to expand the Sites folder.
c. Right-click the site you want to modify. The context menu appears.
d. Select Properties from the context menu. The sites Properties dialogue appears.

3. Modify the parameters described in "Site Description" on page 5.

4. Click OK.
0.2.1.2.2 Creating or Modifying a Transmitter

You can modify an existing transmitter or you can create a new transmitter. You can access the properties of a transmitter,
described in "Transmitter Description" on page 5, through the transmitters Properties dialogue. How you access the
Properties dialogue depends on whether you are creating a new transmitter or modifying an existing transmitter.
To create or modify a transmitter:
1. If you are creating a new transmitter:
b. Right-click the Transmitters folder. The context menu appears.
c. Select New from the context menu. The Transmitters New Element Properties dialogue appears (see
Figure 0.3).
2. If you are modifying the properties of an existing transmitter:
b. Click the Expand button ( ) to expand the Transmitters folder.
c. Right-click the transmitter you want to modify. The context menu appears.
d. Select Properties from the context menu. The transmitters Properties dialogue appears.
3. Modify the parameters described in "Transmitter Description" on page 5.
4. Click OK. If you are creating a new transmitter, Atoll reminds you to create a cell. For information on creating a
cell, see "Creating or Modifying a Cell" on page 9.
Tips:
If you are creating several transmitters at the same time, or modifying several existing transmit-
ters, 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 63.
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.
0.2.1.2.3 Creating or Modifying a Cell

You can modify an existing cell or you can create a new cell. You can access the properties of a cell, described in "Cell
Description" on page 7, through the Properties dialogue of the transmitter where the cell is located. How you access the
Properties dialogue depends on whether you are creating a new cell or modifying an existing cell.
To create or modify a cell:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the Transmitters folder.
3. Right-click the transmitter on which you want to create a cell or whose cell you want to modify. The context menu
appears.
4. Select Properties from the context menu. The transmitters Properties dialogue appears.
5. Select the Cells tab.
6. Modify the parameters described in "Cell Description" on page 7.
7. Click OK.
0.2.1.3 Placing a New Base Station Using a Station Template

In Atoll, a base station is defined as a site with one or more transmitters sharing the same properties. With Atoll, you can
create a network by placing base stations based on station templates. This allows you to build your network quickly with
consistent parameters, instead of building the network by first creating the site, then the transmitters, and finally by adding
the cells.
To place a new station using a station template:
1. In the Radio toolbar, select a template from the list.

Atoll User Manual
2. Click the New Transmitter or Station button ( ) in the Radio toolbar.
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.
4. Click to place the station.
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 46.
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 11.
To place a series of base stations within a defined area:
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 Modify-
ing a Station Template" on page 11.
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.
Placing a Station on an Existing Site
When you place a new station using a station template as explained in "Placing a New Base Station Using a Station
Template" on page 9, 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.
3. Click the New Transmitter or Station button ( ) in the Radio toolbar.

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 station.
0.2.1.4 Managing Station Templates

Atoll comes with LTE station templates, but you can also create and modify station templates. The tools for working with
station templates can be found on the Radio toolbar (see Figure 0.5).
Figure 0.5: The Radio toolbar

0.2.1.4.1 Creating or Modifying a Station Template

When you create a station template, Atoll bases it on the station template selected in the Station Template Properties
dialogue. The new station template has the same parameters as the one it is based on. Therefore, by selecting the existing
station template that most closely resembles the station template you want to create, you can create a new template by
only modifying the parameters that differ.
As well, you can modify the properties of any station template.
To create or modify a station template:
1. In the Radio toolbar, click the arrow to the right of the list.
2. Select Manage Templates from the list. The Station Template Properties dialogue appears.
3. You can now create a new station template or modify an existing one:
- To create a new station template: 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.
- To modify an existing station template: Under Station Templates, select the station template whose prop-
erties you want to modify and click Properties. The Properties dialogue appears.
4. Click the General tab of the Properties dialogue. In this tab (see Figure 0.6), you can modify the following: the
Name of the station template, the number of Sectors, each with a transmitter, and the Hexagon Radius, i.e., the
theoretical radius of the hexagonal area covered by this base sector.
- Under Antennas, you can modify the following: the Height/Ground of the antennas 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 main antenna Model, 1st Sector Azimuth, from which the azimuth of the other sectors are offset
to offer complete coverage of the area, the Mechanical Downtilt, and the Additional Electrical Downtilt for
the antennas.
Under Number of Antenna Ports, you can enter the number of antenna ports available for Transmission
and for Reception.
- 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".
Figure 0.6: Station Template Properties dialogue General tab
5. Click the Transmitter tab. In this tab (see Figure 0.7), 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 5.
The information in the computed Total Losses in transmission and reception boxes is calculated from the
information you entered in the Equipment Specifications dialogue (see Figure 0.4 on page 7). 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 wish. Any value
you enter must be positive.

Atoll User Manual
The information in the computed Total Noise Figure reception box is calculated from the information you
entered in the Equipment Specifications dialogue. You can modify the real Total Noise Figure at reception
if you wish. Any value you enter must be positive.
Figure 0.7: Station Template Properties dialogue Transmitter tab
6. Click the LTE tab. In this tab (see Figure 0.8), you can modify the following:
- Power, Frequency Band, Channel Number, LTE Equipment, and Max Number of Users.
- Under Default Loads, you can enter the default values for Traffic Load (DL), Traffic Load (UL), and UL
Noise Rise.
- Under Antenna Diversity, you can select the type of antenna diversity mode supported by the transmitter.
Diversity Support can be Single Antenna, Transmit Diversity, Spatial Multiplexing, AMS, Single
Antenna+Transmit Diversity, Single Antenna+Spatial Multiplxing, or Single Antenna+AMS.
You can also enter the AMS Threshold.
Figure 0.8: Station Template Properties dialogue LTE tab
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.
0.2.1.4.2 Modifying a Field in a Station Template

To modify a field in a station template:
3. Select the template in the Available Templates list.
4. Click the Fields button.
5. In the dialogue that appears, you have the following options:
- 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 59) 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.

iii. 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.
iv. Enter, if desired, a Default value for the new field.
v. 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.
0.2.1.4.3 Deleting a Station Template

To delete a station template:
3. Under Station Templates, select the station template you want to delete and click Delete. The template is
deleted.
4. Click OK.
0.2.1.5 Creating Duplicates of an Existing Station

You can create new stations by duplicating an existing station. When you duplicate an existing station, the station you
create will have the same site, transmitter, and cell parameter values as the original one. Duplicating a station is a way to:
Quickly create a new station with the same settings as an original one in order to study the effect of a new station
on the coverage and capacity of the network, and
Quickly create a new homogeneous network with stations that have the same characteristics.
To duplicate an existing station:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Sites folder.
3. Right-click the site you want to duplicate. The context menu appears.
4. Select Duplicate > With Neighbours from the context menu, if you want to duplicate the station along with the
lists of intra- and inter-technology neighbours of its cells. Otherwise, select Duplicate > Without Neighbours.
You can now place the new station on the map using the mouse.
5. 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 Sta-
tion button. For information on using the zooming tools, see "Changing the Map Scale" on
page 46.
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.
6. Click to place the duplicate station.

A new station is placed on the map. The site, transmitters, and cells of the new station have the same names as
the site, transmitters, and cells of the original station, preceded by "Copy of." The site, transmitters, and cells of
the duplicate station have the same settings as those of the original station.
You can also place a series of duplicate stations by pressing and holding the CTRL key in step 6.

Atoll User Manual
For more information on the site, transmitter, and cell properties, see "Definition of a Base Station" on page 5.
0.2.2 Creating a Group of Base Stations

You can create base stations individually as explained in "Creating an LTE Base Station" on page 4, or you can create
one or several base stations by using station templates as explained in "Placing a New Base Station Using a Station
Template" on page 9. However, if you have a large project and you already have existing data, you can import this data
into your current Atoll document and create a group of base stations.
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 86.
You can import base station data in the following ways:

Copying and pasting data: If you have data in table form, either in another Atoll document or in a spreadsheet,
you can copy this data and paste it into the tables in your current Atoll document. When you create a group of
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 cell data in the Cells table, in that order.
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 63.
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 65. For information on
importing table data, see "Importing Tables from Text Files" on page 65.
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 9.
0.2.3 Modifying Sites and Transmitters Directly on the Map

In Atoll, you can access the Properties dialogue of a site or transmitter using the context menu on the Data tab of the
Explorer window. However, in a complex radio-planning project, it can be difficult to find the data object in the Data tab,
although it might be visible in the map window. Atoll lets you access the Properties dialogue of sites and transmitters
directly from the map. If there is more than one transmitter with the same azimuth, clicking the transmitters in the map
window opens a context menu allowing you to select the transmitter. You can also change the position of the station by
dragging it, or by letting Atoll find a higher location for it.
Modifying sites and transmitters directly on the map is explained in detail in "Chapter 1: The Working Environment":
"Selecting One of Several Transmitters or Microwave Links" on page 38.
"Moving a Site Using the Mouse" on page 39.
"Moving a Site to a Higher Location" on page 39.
"Changing the Azimuth of the Antenna Using the Mouse" on page 39.
"Changing the Position of the Transmitter Relative to the Site" on page 40.
0.2.4 Display Hints for Base Stations

Atoll allows to you to display information about base stations in a number of ways. This enables you not only to display
selected information, but also to distinguish base stations at a glance.
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 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 43.
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 44.
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 41.
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 41.
0.2.5 Creating a Multi-Band LTE Network

In Atoll, you can model a multi-band LTE network, for example, a network consisting of 1.9 GHz and 2 GHz cells, in one
document. Creating a multi-band LTE network consists of the following steps:
1. Defining the frequency bands in the document (see "Defining Frequency Bands" on page 75).
2. Selecting and calibrating a propagation model for each frequency band (see "Chapter 5: Managing Calculations
in Atoll").
3. Assigning a frequency band to each cell and a relevant propagation model to each transmitter (see "Creating or
Modifying a Cell" on page 9 and "Creating or Modifying a Transmitter" on page 9).
0.2.6 Setting the Working Area of an Atoll Document

When you load project data from a database, you will probably only modify the data in the region for which you are respon-
sible. For example, a complex radio-planning project may cover an entire region or even an entire country. You, however,
might be responsible for the radio planning for only one city. In such a situation, doing a coverage prediction that calculates
the entire network would not only take a lot of time, it is not necessary. Consequently, you can restrict a coverage prediction
to the base stations that you are interested in and generate only the results you need.
In Atoll, there are two ways of restricting the number of base stations covered by a coverage prediction, each with its own
advantages:
Filtering the desired base stations
You can simplify the selection of base stations to be studied by using a filter. You can filter base stations according
to one or more fields, or you can create an advanced filter by combining several criteria in several fields. You can
create a graphic filter by either using an existing vector polygon or creating a new vector polygon. For information
on graphic filters, see "Filtering Data Using a Filtering Zone" on page 86. This enables you to keep only the base
stations with the characteristics you want for your calculations. The filtering zone is taken into account whether or
not it is visible.
For information on filtering, see "Filtering Data" on page 76.
Setting a computation zone

Drawing a computation zone to encompass the base stations to be studied limits the number of base stations to
be calculated, which in turn reduces the time necessary for calculations. In a smaller project, the time savings may
not be significant. In a larger project, especially when you are making repeated calculations in order to see the
effects of small changes in the base station configuration, the savings in time is considerable. Limiting the number
of base stations by drawing a computation 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 zones. The computation zone
defines the area where Atoll computes path loss matrices, coverage predictions, Monte Carlo, power control
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 23.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be
studied.
0.2.7 Studying a Single Base Station

As you create a base station, you can study it to test the effectiveness of the set parameters. Coverage predictions on
groups of base stations can take a large amount of time and consume a lot of computer resources. Restricting your cover-
age prediction to the base station you are currently working on allows you get the results quickly. You can expand your
coverage prediction to a number of base stations once you have optimised the settings for each individual base station.
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

Atoll User Manual
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.
"Making a Point Analysis to Study the Profile" on page 16.
"Studying Signal Level Coverage" on page 17.
0.2.7.1 Making a Point Analysis to Study the Profile

In Atoll, you can make a point analysis to study reception along a profile between a reference transmitter and a user.
Before studying a site, you must assign a propagation model. The propagation model takes the radio and geographic data
into account and calculates losses along the transmitter-receiver path. The profile is calculated in real time, using the prop-
agation model, allowing you to study the profile and get a prediction on each selected point.
For information on assigning a propagation model, see "Assigning a Propagation Model" on page 21.
You can make a point analysis to:
study the reception in real time along a profile between a reference transmitter and an LTE user, and
evaluate the signal levels coming from the surrounding transmitters at a given point (using existing path loss
matrices).
To make a point analysis:
1. In the map window, select the transmitter from which you want to make a point analysis.
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 of the selected transmitter

- The propagation model used
- The shadowing margin
- 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.

- Line of Sight Clearance Only: Select the Line of Sight Clearance Only check box if you want to study the
line of sight clearance between the transmitter and the receiver. Atoll displays the profile between the trans-
mitter and the receiver including clutter heights. An ellipsoid indicating the Fresnel zone is also shown. Atoll
does not calculate the 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.

You can select a different transmitter and Displays data, including received signal, shadowing margin,
choose to display a profile only with a selected propagation model used, and transmitter-receiver distance.
carrier.
Fresnel ellipsoid Line of sight Attenuation with diffraction
Figure 0.9: Point Analysis Tool - Profile tab
6. To end the point analysis, click the Point Analysis Tool ( ) in the Radio toolbar again.
0.2.7.2 Studying Signal Level Coverage

As you are building your radio-planning project, you may want to check the coverage of a new base station without having
to calculate the entire project. You can do this by selecting the site with its transmitters and then creating a new coverage
prediction.
This section explains how to calculate the signal level coverage of a single base station. A signal level coverage prediction
displays the signal of the best server for each pixel of the area studied.
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 72.
To study the signal level coverage of a single base station:

2. Right-click the Transmitters folder and select Group by > Sites from the context menu. The transmitters are now
displayed in the Transmitters folder by the site on which they are situated.
Tip: If you wish to study only sites by their status, at this step you could group them by status.
3. Select the propagation parameters to be used in the coverage prediction:

a. Click the Expand button ( ) to expand the Transmitters folder.
b. Right-click the group of transmitters you want to study. The context menu appears.
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 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:
g. Close the table.
4. 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 coverage prediction types 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.
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:

Atoll User Manual
- 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:
Size of the Coverage

Display Resolution
Prediction
City Centre 5m
City 20 m
County 50 m
State 100 m
Country According to the size of the country
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 Fil-
ter 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 0.10).
- 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.
class.
Figure 0.10: Condition settings for a coverage prediction by signal level
- 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 40.
- 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 cover-
age 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 ( ).
0.2.8 Studying Base Stations

When you make a coverage prediction, Atoll calculates all base stations that are active, filtered (i.e., that are selected by
the current filter parameters), and whose propagation zone intersects the rectangle containing the computation zone.
Figure 0.11 gives an example of a computation zone. In Figure 0.11, the computation zone is displayed in red, as it is in
the Atoll map window. The propagation zone of each active site is indicated by a blue square. Each propagation zone that
intersects the rectangle (indicated by the green dashed line) containing the computation zone will be taken into consider-
ation when Atoll calculates the coverage prediction. Sites 78 and 95, for example, are not in the computation zone.
However, their propagation zones intersect the rectangle containing the computation zone and, therefore, they will be
taken into consideration in the coverage prediction. On the other hand, the coverage zones of three other sites do not inter-
sect the green rectangle. Therefore, they will not be taken into account in the coverage prediction. Site 130 is within the
coverage zone but has no active transmitters. Therefore, it will not be taken into consideration either.
Figure 0.11: An example of a computation zone
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 0.11) 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.
"Path Loss Matrices" on page 19.
"Assigning a Propagation Model" on page 21.
"The Calculation Process" on page 23.
"Creating a Computation Zone" on page 23.
"Setting Transmitters as Active" on page 23.
"Signal Level Coverage Predictions" on page 24.
"Analysing a Coverage Prediction" on page 28.
"LTE Coverage Predictions" on page 36.
"Printing and Exporting Coverage Prediction Results" on page 48.
0.2.8.1 Path Loss Matrices

Path loss is caused by objects in the transmitter-receiver path. In Atoll, the path loss matrices must be calculated before
predictions and simulations can be made.

Atoll User Manual
Storing Path Loss Matrices
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:
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, depend-
ing 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 cal-
culations 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.
Checking the Validity of Path Loss Matrices
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:
2. Right-click the Transmitters folder. The context menu 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:
- Transmitter: The name of the transmitter.
- Locked: If the check box is selected, the path loss matrix will not be updated even if the path loss matrices
are recalculated.
- Valid: This is a Boolean field indicating whether or not the path loss matrix is valid.
- Origin of Invalidity: If the path loss matrix is indicated as being invalid, the reason is given here.

- Size: The size of the path loss matrix for the transmitter.
- File: If the path loss matrix is not embedded, the location of the file is listed.
5. Click the Statistics button to display the number of path loss matrices to be recalculated. The Statistics dialogue
appears (see Figure 0.12) with the total number of invalid path loss matrices and the reasons for invalidity, as well
as a summary of the reasons for invalidity.
Figure 0.12: Path loss matrices statistics
0.2.8.2 Assigning a Propagation Model

In Atoll, you can assign a propagation model globally to all transmitters, to a defined group of transmitters, or a single
transmitter. As well, you can assign a default propagation model for coverage predictions. This propagation model is used
as for all transmitters where the main propagation model selected is "(Default model)."
Because you can assign a propagation model in several different ways, it is important to understand which propagation
model Atoll will use:
1. If you have assigned a propagation model to a single transmitter, as explained in "Assigning a Propagation Model
to One Transmitter" on page 22, or to a group of transmitters, as explained in "Assigning a Propagation Model to
a Group of Transmitters" on page 22, this is the propagation model that will be used.
The propagation model assigned to an individual transmitter or to a group of transmitters will always have prece-
dence over any other assigned propagation model.
2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation
Model to All Transmitters" on page 21, 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 171, 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.
"Assigning a Propagation Model to All Transmitters" on page 21.
"Assigning a Propagation Model to a Group of Transmitters" on page 22.
"Assigning a Propagation Model to One Transmitter" on page 22.
For more information about the available propagation models, see "Chapter 5: Managing Calculations in Atoll".
Assigning a Propagation Model to All Transmitters
In Atoll, you can choose a propagation model per transmitter or globally.

To define a main and extended propagation model for all transmitters:
4. Click the Propagation tab.
5. Under Main Matrix:
- Select a Propagation Model
6. If desired, under Extended Matrix:
- Select a Propagation Model

Atoll User Manual

7. Click OK. The selected propagation models will be used for all transmitters.
Note: Setting a different main or extended matrix on an individual transmitter as explained in

"Assigning a Propagation Model to One Transmitter" on page 22 will override this entry.
Assigning a Propagation Model to a Group of 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:
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 73.

5. Right-click the group of transmitters to which you want to assign a main and extended propagation model. The
context menu appears.
6. Select Open Table from the context menu. The Transmitters table appears with the transmitters from the
selected group.
For each transmitter, you can set the propagation model parameters in the following columns:
- Main Propagation Model

- Main Calculation Radius
- Main Resolution
- Extended Propagation Model
- Extended Calculation Radius
- Extended Resolution
7. To enter the same values in one column for all transmitters 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 57.
Assigning a Propagation Model to One Transmitter
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:
3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu
appears.
5. Click the Propagation tab.
6. Under Main Matrix:
7. If desired, under Extended Matrix:

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.
0.2.8.3 The Calculation Process

When you create a coverage prediction and click the Calculate button ( ), Atoll follows the following process:
1. Atoll first checks to see whether the path loss matrices exist and, if so, whether they are valid. There must be valid
path loss matrices for each active and filtered transmitter whose propagation radius intersects the rectangle
containing the computation zone.
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.
0.2.8.4 Creating a Computation Zone

To create a computation zone:
1. Click the Geo tab in the Explorer window.
2. Click the Expand button ( ) to expand the Zones folder.
3. Right-click the Computation Zone folder. The context menu appears.
4. Select Draw from the context menu.
5. Draw the computation zone:
The computation zone is delimited by a red line. If you clear the computation 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 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 81.
0.2.8.5 Setting Transmitters as Active

When you make a coverage prediction, Atoll considers all base stations that are active, filtered (i.e., that are selected by
the current filter parameters), and whose propagation zone intersects a rectangle containing the computation zone. There-
fore, before you define a coverage prediction, you must ensure that all the transmitters on the base stations you wish to
study have been activated. In the Explorer window, active transmitters are indicated with a red icon ( ) in the Transmit-
ters folder and inactive transmitters are indicated with a white icon ( ).
In Atoll, you can also set the cell on a transmitter as active or inactive.

Atoll User Manual
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:
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:
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:
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 more than one cell as active using the Cells table:
3. Select Cells > Open Table. The Cells table appears with each cells parameters in a second 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 49.
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.
0.2.8.6 Signal Level Coverage Predictions

Atoll offers a series of standard coverage predictions based on the measured signal level of each pixel; other factors, such
as interference, are not taken into consideration. Coverage predictions specific to LTE are covered in "LTE Coverage
Predictions" on page 36.
Once you have created and calculated a coverage prediction, you can use the coverage predictions context menu to make
the coverage prediction into a template (which will appear under the heading Customized Studies in the Study Types
dialogue. You can also select Duplicate from the coverage predictions context menu to create a copy. By duplicating an
existing 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 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 81.
The following standard coverage predictions are explained in this section:
"Making a Coverage Prediction by Signal Level" on page 25

"Making a Coverage Prediction by Transmitter" on page 26

"Making a Coverage Prediction on Overlapping Zones" on page 27.
0.2.8.6.1 Making a Coverage Prediction by Signal Level

A coverage prediction by signal level allows you to predict coverage zones by the transmitter signal strength at each pixel.
You can base the coverage on the signal level, path loss, or total losses within a defined range.
To make a coverage prediction by signal level:
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Signal Level and click OK.
5. Click the General tab.
On the General tab, you can change the default Name and Resolution of the coverage prediction, and add some
Comments. Under Configuration, you can create a Filter to select which sites to display in the results. For infor-
mation on filtering, see "Filtering Data" on page 76.
6. Click the Condition tab (see Figure 0.13). 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
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
class.
Figure 0.13: Condition settings for a coverage prediction by signal level
7. Click the Display tab.

If you choose to display the results by best signal level, the coverage prediction results will be in the form of thresh-
olds. If you choose to display the results by signal level, the coverage prediction results will be arranged according
to transmitter. For information on adjusting the display, see "Display Properties of Objects" on page 40.
8. Click OK to save your settings.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 0.14).

Atoll User Manual
Figure 0.14: Coverage prediction by signal level
0.2.8.6.2 Making a Coverage Prediction by Transmitter

A coverage prediction by transmitter allows the user to predict coverage zones by transmitter at each pixel. You can base
the coverage on the signal level, path loss, or total losses within a defined range.
To make a coverage prediction by transmitter:
4. Select Coverage by Transmitter and click OK.
for each pixel.
ability.
class.
Figure 0.15: Condition settings for a coverage prediction by transmitter

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 40.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The
Figure 0.16: Coverage prediction by transmitter
0.2.8.6.3 Making a Coverage Prediction on Overlapping Zones

Overlapping zones are composed of pixels that are, for a defined condition, covered by the signal of at least two transmit-
ters. You can base a coverage prediction on overlapping zones on the signal level, path loss, or total losses within a
defined range.
To make a coverage prediction on overlapping zones:
4. Select Overlapping Zones and click OK.
for each pixel.
ability.
class.

Atoll User Manual
Figure 0.17: Condition settings for a coverage prediction on overlapping zones

For a coverage prediction on overlapping zones, the Display Type "Value Intervals" based on the Field "Number
of Servers" is selected by default. Each overlapping zone will then be displayed in a colour corresponding to the
number of servers received per pixel. For information on defining display properties, see "Display Properties of
Objects" on page 40.
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.
Figure 0.18: Coverage prediction on overlapping zones
0.2.8.7 Analysing a Coverage Prediction

Once you have performed a coverage prediction study, you can analyse the results with the tools that Atoll provides.
The results are displayed graphically in the map window according to the settings you made on the Display tab when you
created the coverage prediction (step 5. of "Studying Signal Level Coverage" on page 17). If several coverage predictions
are visible on the map, it may be difficult to clearly see the results of the coverage prediction you wish to analyse. You can
select which coverage predictions to display or to hide by selecting or clearing the display check box. For information on
managing the display, see "Displaying or Hiding Objects on the Map Using the Explorer" on page 36.
In this section, the following tools are explained:
"Displaying the Legend Window" on page 29.
"Displaying Coverage Prediction Results Using Tooltips" on page 29.
"Using the Point Analysis Reception Tab" on page 29.
"Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on page 29.
"Displaying a Coverage Prediction Report" on page 30.
"Viewing Coverage Prediction Statistics" on page 32.
"Comparing Coverage Predictions: Examples" on page 32.

0.2.8.7.1 Displaying the Legend Window

When you create a coverage prediction, you can add the displayed values of the coverage prediction to a legend by select-
ing the Add to Legend check box on the Display tab.
To display the Legend window:
Select View > Legend Window. The Legend window is displayed, with the values for each displayed coverage
prediction identified by the name of the coverage prediction.
0.2.8.7.2 Displaying Coverage Prediction Results Using Tooltips

You can get information by placing the pointer over an area of the coverage prediction to read the information displayed
in the tool tips. The information displayed is defined by the settings you made on the Display tab when you created the
coverage prediction (step 5. of "Studying Signal Level Coverage" on page 17).
To get coverage prediction results in the form of tool tips:
In the map window, place the pointer over the area of the coverage prediction that you want more information on.
After a brief pause, the tooltip appears with the information defined in the Display tab of the coverage prediction
properties (see Figure 0.19).
Figure 0.19: Displaying coverage prediction results using tool tips
0.2.8.7.3 Using the Point Analysis Reception Tab

Once you have calculated the coverage prediction, you can use the Point Analysis tool.
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 0.20).
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.
Figure 0.20: Point Analysis Window - Reception tab
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.
0.2.8.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

Atoll User Manual
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 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 doc-
ument:
- 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 81.
- 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 99.
0.2.8.7.5 Displaying a Coverage Prediction Report

Atoll can generate a report for any coverage prediction whose display check box is selected ( ). The report displays the
covered surface and percentage for each threshold value defined in the Display tab of the coverage predictions Proper-
ties dialogue.
The coverage prediction report is displayed in a table. By default, the report table only displays the name and coverage
area columns. You can edit the table to select which columns to display or to hide. For information on displaying and hiding
columns, see "Displaying or Hiding a Column" on page 62.
Atoll bases the report on the area covered by the focus zone and hot spot zones; if no focus zone is defined, Atoll will
use the computation zone. Using a focus zone enables you to create a report without the border effect. In other words, the
results of a coverage prediction are delimited by the computation zone; results close to the border are influenced by fact
that no calculations have been made outside the computation zone. Basing a report on a focus zone that is smaller than
the computation zone eliminates the border effect. By using a focus zone for the report, you can create a report for a
specific number of base stations, instead of creating a report for every site that has been calculated.
The focus zone or hot spot zone must be defined before you display a report; it is not necessary to define it before comput-
ing coverage. The focus or hot spot zone does not, however, need to be visible; even if it is not displayed, Atoll will take
it into account when generating the report. For information on defining a focus zone or hot spot zone, see "Creating a
Focus or Hot Spot Zone for a Coverage Prediction Report" on page 29.
Atoll can generate a report for a single prediction, or for all displayed predictions.
To display a report on a single coverage prediction:
2. Click the Expand button ( ) to expand the Predictions folder.
3. Right-click the coverage prediction for which you want to generate a report. The context menu appears.
4. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears.
5. 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. 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:
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:
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
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 99. Normally, Atoll takes all geo data into consid-
eration, 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 36.
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 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 115.

Atoll User Manual
0.2.8.7.6 Viewing Coverage Prediction Statistics

Atoll can display statistics for any coverage prediction whose display check box is selected ( ). By default, Atoll displays
a histogram using the coverage study colours, interval steps, and shading as defined in the Display tab of the coverage
predictions Properties dialogue. You can also display a cumulative distribution function (CDF) or an inverse CDF (1
CDF). For a CDF or an inverse CDF, the resulting values are combined and shown along a curve. You can also display
the histogram or the CDFs as percentages of the covered area.
Atoll bases the statistics on the area covered by the focus zone; if no focus zone is defined, Atoll will use the computation
zone. However, by using a focus zone, you can display the statistics for a specific number of base stations, instead of
displaying statistics for every base station that has been calculated. Hot spot zones are not taken into consideration when
displaying statistics.
The focus zone must be defined before you display statistics; it is not necessary to define it before computing coverage.
For information on defining a focus zone, see "Creating a Focus or Hot Spot Zone for a Coverage Prediction Report" on
page 29.
To display the statistics on a coverage prediction:
2. Click the Expand button ( ) to expand the Predictions folder.
3. Right-click the coverage prediction whose statistics you want to display. The context menu appears.
4. Select Histogram from the context menu. The Statistics dialogue appears with a histogram of the area defined
by the focus zone (see Figure 0.21).
- 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 criterion calculated during the coverage calculations, if available.
Figure 0.21: Histogram of a coverage prediction by signal level
0.2.8.7.7 Comparing Coverage Predictions: Examples

Atoll allows you to compare two similar predictions to see the differences between them. This enables you to quickly see
how changes you make affect the network.
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 33
"Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 35.
Example 1: Studying the Effect of a 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 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 25. The results are displayed in Figure 0.22. An area with poor coverage is visible on the right side of the
figure.
Figure 0.22: Signal level coverage prediction of existing network
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 4, or by placing a station template, as explained in "Placing a New Base Station Using a Station
Template" on page 9. 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 0.23).

Atoll User Manual
Figure 0.23: Signal level coverage prediction of network with new base station
Now 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 adding a new base station made, you should choose Difference.
5. Click OK to create the comparison. The comparison in Figure 0.24, shows clearly the area covered only by the
new base station.

Figure 0.24: Comparison of both signal level coverage predictions
Example 2: Studying the Effect of a Change in Transmitter Tilt
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 26. The results are displayed in Figure 0.25. The coverage prediction shows that one transmitter is
covering its area poorly. The area is indicated with a red oval in the figure.
Figure 0.25: 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 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 0.26).

Atoll User Manual
Figure 0.26: 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 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 0.27, shows clearly the increase in coverage due at
the change in antenna tilt.
Figure 0.27: Comparison of both transmitter coverage predictions
0.2.8.8 LTE Coverage Predictions

Two types of LTE coverage predictions are available in Atoll: coverage predictions used to analyse signal quality, and
coverage predictions used to analyse the network response to traffic.
Signal quality coverage predictions can be used to analyse the reference signals in the downlink, as well as uplink signals.
These coverage predictions do not depend on the network load conditions.

You can study the network behaviour under traffic conditions by making coverage predictions used to analyse the network
response to traffic. Using these 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 condi-
tions. 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 37.
This section explains the coverage predictions available for analysing signal quality and for analysing the network
response to traffic. The following coverage prediction is explained:
"Analysing the Signal Quality" on page 39.
"Analysing the Network Response to Traffic" on page 40.
0.2.8.8.1 Service and User Modelling

Atoll can base LTE coverage predictions on the DL traffic loads and the UL noise rise values entered in the Cells table
(for more information, see "Setting the Traffic Loads and the UL Noise Rise" on page 41). Before you can model services,
you must define LTE radio bearers. For more information on LTE radio bearers, see "Defining LTE Radio Bearers" on
page 77.
"Modelling Services" on page 37.
"Modelling Mobility Types" on page 38.
"Modelling Terminals" on page 38.
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:
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. The priority is used by the schedulers for
resource allocation. For more information about how schedulers work in Atoll, see "Defining LTE Schedulers"
on page 79.
- 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 is the Maximum Bit Rate (MBR) of the 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 is the Guaranteed Bit Rate (GBR) of the service.
- 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 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.

Atoll User Manual
Modelling Mobility Types
In LTE, information about the receiver mobility is required for determining which bearer selection threshold and quality
graph to use from the reception equipment referred to in the terminal. 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:
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.
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
Reception equipment
Maximum terminal power
Gain and losses
Noise figure
Type of antenna diversity supported
Number of transmission and reception antenna ports
To create or modify a terminal:
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.
- Reception Equipment: Select a reception equipment from the list of available LTE equipment. For more
information on LTE equipment, see "Defining LTE Reception Equipment" on page 78. The terminals
reception 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: 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 radia-
tion 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 whether the terminal supports MIMO or not. MIMO-capable terminals
will be allocated to cells that support the transmit diversity, spatial multiplexing, or AMS.

- Number of Antenna Ports: Enter the number of antenna ports for the terminal in Transmission and
Reception.
6. Click OK.
0.2.8.8.2 Analysing the Signal Quality

Atoll offers a couple of LTE coverage predictions which can be based on the predicted signal level from the best server
and the thermal background noise at each pixel, i.e., received carrier power (C) and the carrier-to-noise ratio (C/N). This
section explains the coverage predictions available for analysing signal quality.
Downlink and uplink signal quality coverage predictions predict the signal quality of the downlink reference signals and
uplink signals in the part of the network being studied.
Atoll calculates the best server for each pixel depending on the downlink signal level. Then, depending on the prediction
definition, it calculates the signal quality (C or C/N). Pixels are coloured if the display threshold condition is fulfilled (in other
words, if the C or C/N is higher than the C or C/N threshold).
To make a signal quality analysis coverage prediction:
4. Select Signal Quality Analysis (DL) or Signal Quality Analysis (UL) and click OK.
6. Click the Condition tab (see Figure 0.28).

On the condition tab, you can select a Terminal, a Mobility type, and a Service. The signal quality 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 37, "Modelling Terminals" on page 38, "Modelling Mobility Types" on page 38, and "Defining LTE Reception
Equipment" on page 78, 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
signal quality calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
Figure 0.28: Condition settings for a signal quality coverage prediction

For Signal Quality Analysis (DL), you can choose between displaying results by Best Signal Level, or C/N
Level. For Signal Quality Analysis (UL), you can choose between displaying results by Signal Level or C/N
Level. The coverage prediction results will be in the form of thresholds. For information on adjusting the display,
see "Display Properties of Objects" on page 40.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 0.29
and Figure 0.30).

Atoll User Manual
Figure 0.29: Downlink C/N coverage prediction
Figure 0.30: Uplink C/N coverage prediction
0.2.8.8.3 Analysing the Network Response to Traffic

In LTE, the capacity and the effective service coverage areas of cells are influenced by network loads. As the network load
increases, the area where a cell provides service decreases. For this reason, network loads must be defined in order to
calculate these coverage predictions.
Atoll offers a series of coverage predictions which are based on the predicted signal level from the best server and the
predicted signal levels from other cells (interference) at each pixel, i.e., carrier-to-interference-and-noise ratio, or C/(I+N).
The downlink interference received from different cells of the network is weighted by their respective downlink traffic loads.
The measure of uplink interference for each cell is provided by the uplink noise rise.
If you have traffic maps, you can do a Monte Carlo simulation to determine the downlink traffic loads and the uplink noise
rise values for a generated user distribution. If you do not have traffic maps, Atoll can calculate these coverage predictions
using the downlink traffic loads and the uplink noise rise values defined for each cell.
In this section, these coverage predictions will be calculated using downlink traffic loads and the uplink noise rise values
defined at the cell level. Before making a prediction, you will have to set the downlink traffic loads and the uplink noise rise,
and the parameters that define the services and users. These are explained in the following sections:
"Setting the Traffic Loads and the UL Noise Rise" on page 41.

Several coverage predictions used to study the network response to traffic are explained in this section. The following stud-
ies are explained:
"Making a Coverage by C/(I+N) Level" on page 41.
"Making a Coverage by Best Bearer" on page 43.
"Making a Coverage by Throughput" on page 45.
"Making an Aggregate Throughput Coverage Prediction Using Simulation Results" on page 47.
Setting the Traffic Loads and the UL Noise Rise
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:
3. Select Cells > Open Table from the context menu. The Cells table appears.
4. Enter a value in the following columns:
- Traffic Load (DL) (%)
- Traffic Load (UL) (%)
- UL Noise Rise (dB)
For a definition of the values, see "Cell Description" on page 7.
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 57.
Making a Coverage by C/(I+N) Level
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 signal level. 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 75.
To make a coverage prediction by C/(I+N) level:
4. Select Coverage by C/(I+N) Level (DL) or Coverage by C/(I+N) Level (UL) and click OK.
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 downlink traffic load
or the uplink noise rise 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.

Atoll User Manual
C(I+N) calculations is based on the C/I standard deviation.
Figure 0.31: Condition settings for a coverage prediction by C/(I+N) level

You can choose between displaying results by C/(I+N) Level or Total Noise (I+N) level. The coverage prediction
results will be in the form of thresholds. For information on adjusting the display, see "Display Properties of
Objects" on page 40.
and Figure 0.33).
Figure 0.32: Coverage prediction by downlink C/(I+N)

Figure 0.33: Coverage prediction by uplink C/(I+N)
Making a Coverage by Best Bearer
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:
4. Select Coverage by Best Bearer (DL) or Coverage by Best Bearer (UL) and click OK.

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
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 reception equipment. This reception 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 thresh-
old graph to use.

Atoll User Manual
Figure 0.34: Condition settings for a coverage prediction on LTE bearers

You can display results by Best Bearer. The coverage prediction results will be in the form of thresholds. For infor-
mation on adjusting the display, see "Display Properties of Objects" on page 40.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the LTE bearer coverage prediction. The
and Figure 0.36).
Figure 0.35: Coverage prediction by downlink best bearer

Figure 0.36: Coverage prediction by uplink best bearer
Making a Coverage by Throughput
Downlink and uplink throughput coverage predictions calculate and display the channel throughputs 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 Simulation Results" on page 47.
To make a coverage prediction by channel throughput:
4. Select Coverage by Throughput (DL) or Coverage by Throughput (UL) and click OK.

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
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 reception equipment. This reception 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
threshold graph to use. The service is used for the application throughput parameters defined in the service Prop-
erties dialogue.

Atoll User Manual
Figure 0.37: Condition settings for a throughput coverage prediction

You can choose between displaying results by Peak RLC Channel Throughput, Effective RLC Channel
Throughput, or Application Level Channel 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 40.
Atoll calculates the peak RLC 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 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 reception equipment defined in the selected terminal or the
reception equipment of the cell of the serving transmitter.
The application level throughput is the effective RLC throughput reduced by the overheads of the different layers between
the RLC and the Application layers. 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 75.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Figure 0.38: Coverage prediction by downlink channel throughput

Figure 0.39: Coverage prediction by uplink channel throughput
Making an Aggregate Throughput Coverage Prediction Using Simulation Results
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.
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 64.
2. Create a coverage prediction by throughput as explained in "Making a Coverage by Throughput" on page 45, 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 RLC User Throughput, Effective RLC User Through-
put, or Application Level 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 40.
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 74.
0.2.8.9 Searching and Displaying Cell Parameters on the Map

In Atoll, you can search and display the frequency bands and channel numbers used by the cells of the network using the
Search Tool. Results are displayed in the map window. If you have already calculated and displayed a coverage predic-
tion by transmitter based on the best server, the search results will be displayed by transmitter coverage. Frequency reuse
and any potential problems will be clearly visible. For information on coverage predictions by transmitter, see "Making a
Coverage Prediction by Transmitter" on page 26.
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 43.
To find a frequency band using the Search Tool:

1. Click View > Search Tool. The Search Tool window appears.
2. In the Channel tab, select a Frequency Band from the list of available frequency bands.
3. Set Channel Number to All.
4. 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.

Atoll User Manual
To find a channel number using the Search Tool:

1. Click View > Search Tool. The Search Tool window appears.
2. In the Channel tab, select a Frequency Band from the list of available frequency bands.
3. Select the Channel Number from the list of available channel numbers.
4. If you want only want the channel entered in the Channel Number box to be displayed, select the Co-channel
Only check box.
5. Click Search.
Transmitters whose cells use the selected frequency band and channel number are displayed in red. Transmitters
with cells using two adjacent channel numbers in the same frequency band (i.e., a channel higher and a channel
lower) are displayed in yellow. Transmitters with cells using a lower adjacent channel number in the same
frequency band are displayed in green. Transmitters with cells using a higher adjacent channel number in the
same frequency band are displayed in blue. All other transmitters are displayed in grey.
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.
0.2.8.10 Printing and Exporting Coverage Prediction Results

Once you have made a coverage prediction, you may want to save the results displayed on the map in an external format,
either by printing the coverage prediction results, or by saving the results in an external format. You can also export a
selected area of the coverage as a bitmap.
Printing coverage prediction results: Atoll offers several options allowing you to customise and optimise the
printed coverage prediction results. Atoll supports printing to a variety of paper sizes, including A4 and A0. For
more information on printing coverage prediction results, see "Printing a Map" on page 68.
Defining a coverage export zone: If you want to export part of the coverage prediction as a bitmap, you can
define a coverage export zone. After you have defined a coverage export zone, when you export a coverage pre-
diction as a raster image, Atoll offers you the option of exporting only the area covered by the zone. For more
information on defining a coverage export zone, see "Using a Coverage Export Zone" on page 53.
Exporting coverage prediction results: In Atoll, you can export the coverage areas of a coverage prediction in
raster or vector formats. In raster formats, you can export in BMP, TIFF, ArcView grid, or Vertical Mapper (GRD
and GRC) formats. When exporting in GRD or GRC formats, Atoll allows you to export files larger than 2 GB. In
vector formats, you can export in ArcView, MapInfo, or AGD formats. For more information on exporting cov-
erage prediction results, see "Exporting Coverage Prediction Results" on page 54.
0.2.9 Planning Neighbours

You can set neighbours for each cell manually. When allocating neighbours, the cell to which you are allocating neighbours
is referred to as the reference cell. The cells that fulfil the requirements to be neighbours are referred to as possible neigh-
bours.
Usually, you will allocate neighbours globally during the beginning of a radio planning project. Afterwards, you will allocate
neighbours to base stations as you add them.
Atoll supports the following neighbour types in an LTE network:
Intra-technology neighbours: Intra-technology neighbours are cells defined as neighbours that also use LTE.
Intra-technology neighbour cells perform handover using a different carrier.
Inter-technology neighbours: Inter-technology neighbours are cells defined as neighbours that use a technology
other than LTE.
"Allocating and Deleting Neighbours per Cell" on page 48.
"Importing Neighbours" on page 50.
"Checking Neighbour Allocation" on page 50.
"Exporting Neighbours" on page 51.
0.2.9.1 Allocating and Deleting Neighbours per Cell

You can adjust the overall allocation of neighbours by allocating or deleting neighbours per cell. You can allocate or delete
neighbours directly on the map or using the Cells tab of the Transmitter Properties dialogue.
This section explains the following:
"Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue" on page 49.
"Allocating or Deleting Neighbours Using the Neighbours Table" on page 49.
"Allocating or Deleting Neighbours on the Map" on page 49.

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 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.
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. If you want the neighbour relation to be symmetric, select the check box in the Symmetric column.
Note: Atoll automatically sets the importance for manually allocated neighbours to "1."
c. Click elsewhere in the table when you have finished creating the new neighbour.
8. 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.
9. Click OK.
Allocating or Deleting Neighbours Using the Neighbours Table
To allocate or delete LTE neighbours using the Neighbours table:

1. Select the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appear.
3. Select Cells > 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 57.
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. Select the check box in the Symmetry column if you want the neighbour relation to be symmetric.
d. Click in 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."
5. To create a symmetric neighbour relation:

a. Select 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 all neighbour relations symmetric, right-click the Neighbours table and select Symmetrise All Neigh-
bour Relations.
7. To delete a symmetric neighbour relation:
a. Select the neighbour in the Neighbour column. The context menu appears.
b. 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.
8. 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.
Allocating or Deleting Neighbours on the Map
You can allocate or delete intra-technology neighbours directly on the map using the mouse.

Atoll User Manual
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 50.
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:
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:
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.
To remove an outward neighbour relation:
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 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:
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.
0.2.9.2 Importing Neighbours

You can import neighbour data in the form of ASCII text files (in TXT and CSV formats) into the current Atoll document
using the Neighbours table.
To import neighbours using the Neighbours table:
1. Open the Neighbours table:
a. Select the Data tab of the Explorer window.
b. Right-click the Transmitters folder. The context menu appears.
c. Select Cells > Neighbours > Intra-technology Neighbours from the context menu. The Neighbours table
appears.
2. Import the ASCII text file as explained in "Importing Tables from Text Files" on page 65.
0.2.9.3 Checking Neighbour Allocation

You can verify the neighbour allocation in the following ways:
"Displaying Neighbour Relations on the Map" on page 50.
"Displaying the Coverage of Each Neighbour of a Cell" on page 51.
0.2.9.3.1 Displaying Neighbour Relations on the Map

You can view neighbour relations directly on the map. Atoll can display them and indicate the direction of the neighbour
relation (in other words, Atoll indicates which is the reference cell and which is the neighbour) and whether the neighbour
relation is symmetric.
To display the neighbour relations of a cell on the map:
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 Neighbour Display dialogue appears.
3. 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.
5. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
6. Click a transmitter on the map to display the neighbour relations. Atoll displays the following information (see
Figure 0.40) on the selected carrier:
- The symmetric neighbour relations of the selected (reference) transmitter are indicated by a heavy black
line.
- The outward neighbour relations are indicated with a light black line with an arrow the colour of the selected
(reference) transmitter.
- The inward neighbour relations are indicated with a light black line with an arrow the colour of the transmitter
which has the selected (reference) transmitter as a neighbour.
Figure 0.40: Neighbours of Site 22(0)
0.2.9.3.2 Displaying the Coverage of Each Neighbour of a Cell

By combining the display characteristics of a coverage prediction with neighbour display options, Atoll can display the
coverage area of a cells neighbours and colour them according to any neighbour characteristic in the Neighbours table.
To display the coverage of each neighbour of a cell:
1. Create, calculate, and display a "Coverage by Transmitter" coverage prediction, with the Display Type set to
"Discrete Values" and the Field set to Transmitter (for information on creating a coverage by transmitter prediction,
see "Making a Coverage Prediction by Transmitter" on page 26).
3. Select Display Options from the context menu. The Neighbour Display dialogue appears.
4. Click the Browse button ( ) beside the Display Links list.
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 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, or according to the importance, as determined by the weighting factors.
7. 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.
8. In order to restore colours and cancel the neighbour display, click the left side of the Visual Management button
( ).
0.2.9.4 Exporting Neighbours

The neighbour data for an Atoll document is stored in a series of tables. You can export the neighbours data to use it in
another application or in another Atoll document.

Atoll User Manual
To export neighbour data:

3. Select Cells > Neighbours and then select the neighbours table containing the data you want to export from the
context menu:
- Intra-technology Neighbours: This table contains the data for the intra-technology neighbours in the current
Atoll document.
- Inter-technology Neighbours: This table contains the data for the inter-technology neighbours in the current
Atoll document.
4. When the selected neighbours table opens, you can export the content as described in "Exporting Tables to Text
Files" on page 65.
0.3 Studying Network Capacity

Interference is the major limiting factor in the performance of LTE networks. It has been recognized as the major bottleneck
in network capacity and is often responsible for poor performance. Frequency reuse means that in a given coverage area
there are several cells that use a given set of frequencies. The cells that use the same frequency are called co-channel
cells, and the interference from users with the same channel in the other co-channel cells is called co-channel interference.
Unlike thermal noise which can be overcome by increasing the signal-to-noise ratio (SNR), co-channel interference cannot
be countered by simply increasing the carrier power of a transmitter. This is because an increase in carrier transmission
power will increase the interference to neighbouring co-channel cells. To reduce co-channel interference, co-channel cells
must be physically separated sufficiently by a distance, called the reuse distance. For a network with a limited number of
frequency channels, a large reuse distance can guarantee a high QoS for the system, but the capacity will be decreased.
Another type of interference in LTE networks is adjacent channel interference. Adjacent channel interference results from
imperfect receiver filters which allow nearby frequencies to interfere with the used frequency channel. Adjacent channel
interference can be minimized through careful filtering and channel assignment.
In Atoll, a simulation is based on a realistic distribution of users at a given point in time. The distribution of users at a given
moment is referred to as a snapshot. Based on this snapshot, Atoll calculates various network parameters such as the
downlink and uplink traffic loads, the uplink noise rise, the user throughputs, etc. Simulations are calculated in an iterative
fashion.
When several simulations are performed at the same time using the same traffic information, the distribution of users will
be different, according to a Poisson distribution. Consequently you can have variations in user distribution from one snap-
shot to another.
To create snapshots, services and users must be modelled. As well, certain traffic information in the form of traffic maps
or subscriber lists must be provided. Once services and users have been modelled and traffic maps and subscriber lists
have been created, you can make simulations of the network traffic.
"Defining Multi-service Traffic Data" on page 52.
"Creating a Traffic Map" on page 53.
"Exporting a Traffic Map" on page 60.
"Working with a Subscriber Database" on page 60.
"Calculating and Displaying Traffic Simulations" on page 64.
"Making Coverage Predictions Using Simulation Results" on page 74.
0.3.1 Defining Multi-service Traffic Data

The first step in making a simulation is defining how the network is used. In Atoll, this is accomplished by creating all of
the parameters of network use, in terms of services, users, and equipment used.
The following services and users are modelled in Atoll in order to create simulations:
LTE radio bearers: Radio bearers are used by the network for carrying information. The LTE Radio Bearer table
lists all the available radio bearers. You can create new radio bearers and modify existing ones by using the LTE
Radio Bearer table. For information on defining radio bearers, see "Defining LTE Radio Bearers" on page 77.
Services: Services are the various services, such as VoIP, FTP download, etc., available to users. These services
can be either of the type "voice" or "data". For information on modelling end-user services, see "Modelling Serv-
ices" on page 37.
Mobility type: In LTE, information about receiver mobility is important to determine the users radio conditions and
throughputs. For information on modelling mobility types, see "Modelling Mobility Types" on page 38.
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. For information on modelling terminals, see "Modelling Terminals" on
page 38.

0.3.2 Creating a Traffic Map

The following sections describe the different types of traffic maps available in Atoll and how to create, import, and use
them. The different types of traffic data sources are:
The OMC (Operations and Maintenance Centre)
Marketing statistics
Population statistics
2G network traffic statistics
Atoll provides four types of traffic maps for LTE projects. These maps can be used for the different types of traffic data
sources as follows:
Live traffic data from the OMC: Traffic maps per transmitter and per service, where traffic is spread over the
best server coverage area of each transmitter and each coverage area is assigned either the total throughput
demand or the number of users. For more information, see "Live Traffic Data From the OMC" on page 53 and "Cre-
ating a Traffic Map Based on Live Data" on page 53.
Marketing-based traffic data: Traffic vector maps based on 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 raster maps based on environments, where each pixel has an environment class assigned. For more
information, see "Marketing-Based Traffic Data" on page 54, "Importing a User Profile-Based Traffic Map" on
page 56, and "Importing an Environment Class-Based Traffic Map" on page 57.
Population-based traffic data: Traffic raster maps based on user densities, where each pixel has an actual
user density assigned. For more information, see "Population-Based Traffic Data" on page 58 and "Importing a
Traffic Density Map" on page 58.
2G network statistics: Cumulated traffic maps. For more information, see "Converting 2G Network Traffic" on
page 59 and "Exporting Cumulated Traffic" on page 59.
0.3.2.1 Live Traffic Data From the OMC

The OMC (Operations and Maintenance Centre) collects data from all the cells in a network. This includes, for example,
the number of active users in each cell and the traffic characteristics related to different services. You can use this data to
create traffic maps containing the number of active users in each cell or the data transfer characteristics of all the services
in each cell.
The section "Creating a Traffic Map Based on Live Data" on page 53 explains how to use traffic data from the OMC in
Atoll to model traffic.
0.3.2.1.1 Creating a Traffic Map Based on Live Data

You can input the total throughput demand or the total number of users for each sector in this type of traffic map. A cover-
age prediction by transmitter is required to create this traffic map. If you do not already have a coverage prediction by trans-
mitter in your document, you must create and calculate it. For more information, see "Making a Coverage Prediction by
Transmitter" on page 26.
To create a traffic map based on live data:
2. Right-click the Traffic folder. The context menu appears.
3. Select New Map from the context menu. The New Traffic Map dialogue appears.
4. Select Map based on Transmitters and Services (Throughputs) or Map based on Transmitters and Services
(# Users).
5. Click the Create Map button. The Traffic per Transmitter dialogue appears.
Note: You can also import a traffic map from a file by clicking the Import a File button. You can
import AGD (Atoll Geographic Data) format files that you have exported from another Atoll
document.
6. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter.
7. Enter the data required in the Traffic per Transmitter dialogue:
- If you are creating a Map based on Transmitters and Services (Throughputs), enter the throughput
demands in the uplink and downlink for each sector and for each listed service.
- If you are creating a Map based on Transmitters and Services (# Users), enter the number of active users
in the uplink and downlink for each sector and for each listed service.
Note: You can also import a text file containing the data by clicking the Actions button and select-
ing Import Table from the menu. For more information on importing table data, see "Import-
ing Tables from Text Files" on page 65.
8. Click OK. The Cell Traffic Map Properties dialogue appears.

Atoll User Manual
9. Select the Traffic tab. Enter the following:

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 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
simulations.
10. 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 trans-
mitter. For more information, see "Making a Coverage Prediction by Transmitter" on page 26. Once you have recalculated
the coverage prediction, you can update the traffic map.
To update the traffic map:
2. Click the Expand button ( ) to expand the Traffic folder.
3. Right-click the traffic map based on live data that you want to update. The context menu appears.
4. Select Update from the context menu. The Traffic per Transmitter 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.
5. Click OK. The Traffic Map Properties dialogue appears.

6. Click OK. The traffic map is updated on the basis of the selected coverage prediction by transmitter.
0.3.2.2 Marketing-Based Traffic Data

The marketing department can provide information which can be used to create traffic maps. This information describes
the behaviour of different types of users. In other words, it describes which type of user accesses which services and for
how long. There may also be information about the type of terminal devices they use to access different services.
In Atoll, this type of data can be used to create traffic maps based on user profiles and environments.
A user profile models the behaviour of different user categories. Each user profile is defined by a list of services which are
in turn defined by the terminal used, the calls per hour, and duration (for calls of the type "voice") or uplink and downlink
volume (for calls of the type "data").
Environment classes are used to describe the distribution of users on a map. An environment class describes its environ-
ment 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).
The sections "Importing a User Profile-Based Traffic Map" on page 56 and "Importing an Environment Class-Based Traffic
Map" on page 57 describe how to use traffic data from the marketing department in Atoll to model traffic.
"Modelling User Profiles" on page 54.
"Modelling Environments" on page 55.
Modelling User Profiles
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:
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.
5. You can modify the following parameters:

- Name: Enter a descriptive name for the user profile.
- Service: Select a service from the list. For information on services, see "Modelling Services" on page 37.
- Terminal: Select a terminal from the list. For information on terminals, see "Modelling Terminals" on page 38.

- Calls/Hour: For services of the type "voice," enter the average number of calls per hour for the service. The
calls per hour is used to calculate the activity probability. For services of the type "voice," one call lasting 1000
seconds presents the same activity probability as two calls lasting 500 seconds each.
For services of the type "data," the Calls/Hour 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 services of the type "data," however, he may not use the service continually. For
example, 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 (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:
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.

6. Enter a Name for the new LTE environment.
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:
Nk = Number of users in the clutter k

N Area = Number of users in the zone Area
Wk = Weight of clutter k
Sk = Surface area of clutter k (in square km)
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

Atoll User Manual
"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.
0.3.2.2.1 Importing a User Profile-Based Traffic Map

User profile based traffic maps are composed of vectors (either points with a number of subscribers, lines with a number
of subscriberskm, or polygons with a number of subscriberskm) with a user profile, mobility type, and traffic density
assigned to each vector.
To import a user profile based traffic map:
4. Select Map based on User Profiles.
5. Click the Import a File button. The Open dialogue appears.
Note: You can also create a traffic map manually in Atoll by clicking the Create Map button in the
New Traffic Map dialogue. For information, see "Creating an Environment Class-Based
Traffic Map" on page 57.
6. Select the file to import.

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 (see Figure 0.41). 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.
Figure 0.41: Traffic map properties dialogue - Traffic tab
Define each of the following:
- 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.
11. 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:
Nk = Number of users in the clutter k

N Area = Number of users in the zone Area
Wk = Weight of clutter k
Sk = Surface area of clutter k (in square km)
12. 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.
13. Click OK to finish importing the traffic map.
0.3.2.2.2 Importing an Environment Class-Based Traffic Map

Environment classes describe the distribution of user profiles.
To import a traffic map based on environment classes:
4. Select Map based on Environments.

10. 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.
11. 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 55.
12. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects"
on page 40.
13. Click OK.
0.3.2.2.3 Creating an Environment Class-Based Traffic Map

Atoll enables you to create an environment class based traffic map by drawing it in the map window.
To draw a traffic map:
4. Select Map based on environments (raster) as the type of map you want to create.
5. Click Create Map. The Environment Map Editor toolbar appears (see Figure 0.42).

Atoll User Manual
Draw Map Delete Map
Figure 0.42: Environment Map Editor toolbar
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.
0.3.2.2.4 Displaying Statistics on an Environment Class-Based Traffic Map

You can display the statistics of an environment class-based traffic map. Atoll provides absolute (surface) and relative
(percentage of the surface) statistics on the focus zone for each environment class. If you do not have a focus zone
defined, statistics are determined for the computation zone.
To display traffic statistics of an environment class based traffic map:
3. Right-click the environment class based traffic map whose statistics you want to display. The context menu
appears.
4. Select Statistics from the context menu. The Statistics window appears.
The Statistics window lists the surface (Si in km) and the percentage of surface (% of i) for each environment
Si
class "i" within the focus zone. The percentage of surface is given by: % of i = -------------- 100
Sk
k
You can print the statistics by clicking the Print button.
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.
0.3.2.3 Population-Based Traffic Data

Population-based traffic data can be based on population statistics and user densities can be deduced from the density of
inhabitants. In the traffic maps based on population statistics, you can enter the number of active or potential users per
unit surface, i.e., the density of users.
0.3.2.3.1 Importing a Traffic Density Map

The traffic density map defines the density of users per pixel. For a traffic density of X users per km, Atoll will distribute
x users per pixel during the simulations, where x depends on the size of the pixels. These x users will have a terminal, a
mobility type, a service, and percentage of indoor users as defined in the Traffic tab of the traffic density maps properties
dialogue.
You can create a number of traffic density maps for different combinations of terminals, mobility types, and services. You
can add vector layers to the map and draw regions with different traffic densities.
To create a traffic density map:
4. Select Map based on Traffic Densities.


10. Select the Traffic tab.

11. Select whether the users are active in the Uplink/Downlink, only in the Downlink, or only in the Uplink.
12. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentages must
equal 100.
13. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentages must
equal 100.
14. Under Services (%), enter the percentage of each service type used in the map. The total percentages 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 density maps because the traffic is provided in terms of user density per pixel.
16. Click OK. Atoll creates the traffic map in the Traffic folder.
0.3.2.4 Converting 2G Network Traffic

Atoll can cumulate the traffic of the traffic maps that you select and export it to a file. The information exported is the
number of active users per km for a particular service of a particular type, i.e., data or voice. This allows you to export
your 2G network packet and circuit service traffic, and then import these maps as traffic density maps into your LTE docu-
ment. These maps can then be used in traffic simulations like any other type of map.
For more information on how to export cumulated traffic, see "Exporting Cumulated Traffic" on page 59, and for information
on importing traffic density maps, see "Importing a Traffic Density Map" on page 58.
To import a 2G traffic map into an LTE document:
1. Create a live data traffic map in your 2G document for each type of service, i.e., one map for packet-switched and
one for circuit-switched services. For more information on creating live data traffic maps, see "Creating a Traffic
Map Based on Live Data" on page 53.
2. Export the cumulated traffic of the maps created in step 1. For information on exporting cumulated traffic, see
"Exporting Cumulated Traffic" on page 59.
3. Import the traffic exported in step 2 to your LTE document as a traffic density map. For more information on
importing traffic density maps, see "Importing a Traffic Density Map" on page 58.
0.3.2.5 Exporting Cumulated Traffic

Atoll allows you to export the cumulated traffic of selected traffic maps in the form of traffic density maps. During export,
Atoll converts any map based on throughput to traffic density. The cumulated traffic is exported in 32-bit BIL, ArcView
Grid, or Vertical Mapper format. When exporting in BIL format, Atoll allows you to export files larger than 2 GB. The
exported traffic map can then be imported as a traffic density map.
To export the cumulated traffic:
3. Select Export Cumulated Traffic from the context menu. The Save As dialogue appears.
4. Enter a file name and select the file format.
5. Click Save. The Export dialogue appears.
6. Under Region, select the area to export:
- The Entire Project Area: This option allows you to export the cumulated traffic over the entire project.
- The Computation Zone: This option allows you to export the cumulated traffic contained by a rectangle
encompassing the computation zone.
7. Under Traffic, define the data to be exported in the cumulated traffic:
- Terminal: Select the type of terminal traffic that will be exported or select "All" to export traffic using any ter-
minal.
- Service: Select the service traffic that will be exported.
- Mobility: Select the mobility type that will be exported or select "All" to export all mobility types.
- Direction: Select one of the following:
- Uplink/Downlink: Select Uplink/Downlink to export only active mobiles with both uplink and downlink
traffic.
- Downlink: Select Downlink to export mobiles with downlink traffic only.
- Uplink: Select Uplink to export mobiles with uplink traffic only.
- the direction whether you want to cumulate traffic on the uplink and the downlink, only on the uplink, or
only on the downlink.
8. 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.
9. Define a Resolution in Metres. The resolution must be an integer and the minimum resolution allowed is 1.

Atoll User Manual
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.
10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.
0.3.3 Exporting a Traffic Map

To export a traffic map:
3. Right-click the traffic map you want to export. The context menu appears.
4. Select Save as from the context menu.
5. Enter a file name and select a file format for the traffic map.
6. Click Save.
For a raster traffic map you have to define:
The Export Region:
- Entire Project Area: Saves the entire traffic map.
- Only Pending Changes: Saves only the modifications made to the map.
- Computation Zone: Saves only the part of the traffic map inside the computation zone.
An export Resolution.
0.3.4 Working with a Subscriber Database

The LTE module includes a subscriber database for modelling fixed user distributions in a network. A subscriber database
can be used for Fixed Wireless Access (FWA). The subscriber database consists of subscriber lists. You can create
subscriber lists in Atoll by adding subscribers to the list using the mouse, or by copying data from any other source, such
as a spreadsheet. You can also directly import subscriber lists in Atoll from text (TXT) and comma separated value (CSV)
files.
Atoll can allocate reference or serving base stations (cells) to subscribers. You can also have the subscriber antenna
oriented towards its serving cell to decrease interference. The automatic server allocation performs a number of calcula-
tions on the subscriber locations.
"Creating a Subscriber List" on page 60.
"Performing Calculations on Subscriber lists" on page 63.
0.3.4.1 Creating a Subscriber List

You create subscribers in Atoll in two steps. First, you create a subscriber list, and then you add subscribers to the list.
You can add subscribers to the list directly on the map using the mouse. For more information, see "Adding Subscribers
to a Subscriber List Using the Mouse" on page 62.
If you need to create a large number of subscribers, Atoll allows you to import them from another Atoll document or from
an external source. For information, see "Importing a Subscriber List" on page 63.
To create a subscriber list:
2. Right-click the Subscribers folder. The context menu appears.
3. Select New List from the context menu. The Subscriber List N Properties dialogue appears (see Figure 0.43),
where N is an incremental digit.
Figure 0.43: New subscriber list dialogue - General tab

4. Select the General tab.

- You can enter a Name for the subscriber list.
- You can Sort the subscriber list. For information on filtering, see "Sorting Data" on page 75.
- You can create a Filter to select subscribers. For information on filtering, see "Filtering Data" on page 76.
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 0.44).
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.
Figure 0.44: New subscriber list dialogue - Table tab
The following parameters are available by default in a new subscriber list:
- 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 subscriber location is always fixed.
- Height: The altitude of the subscriber antenna with respect to the ground (DTM).
- 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 54.
- Terminal: A default terminal (CPE) is the user equipment with an antenna, reception 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.
- 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.
- 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.
- Received Power (DL) (dBm): The signal level received at the subscriber location in the downlink. This value
is calculated by Atoll during calculations on subscriber lists.
- Interference + Noise (DL) (dBm): The interference + noise level experienced at the subscriber location in the
downlink. This value is generated by Atoll during the calculations on subscriber lists.
- C/(I+N) (DL) (dB): The 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 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 reception equipment for the
C(I+N) level at the subscriber location in the downlink. This value is generated by Atoll during the calculations
on subscriber lists.

Atoll User Manual
- 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 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.
- Interference + Noise (UL) (dBm): The interference + noise level 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 LTE bearer available 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.
- BLER (UL): The Block Error Rate read from the reference cells reception 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.
- 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.
- Number of Used Resource Blocks (UL): The number of resource blocks being used by the subscriber in the
uplink. 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.
Note: In Atoll, channel throughputs are peak RLC, effective RLC, or application level throughputs
achieved at a given location using the highest LTE bearer with the entire channel
resources.
For more information on the calculations that you can carry out on subscriber lists, see "Performing Calculations
on Subscriber lists" on page 63.
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 40.
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 62.
You can open the subscriber list table containing all the subscribers and their parameters.
To open the subscriber list table:
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 57.
0.3.4.1.1 Adding Subscribers to a Subscriber List Using the Mouse

You can use the mouse to add subscribers to an existing subscriber list. Atoll applies the default parameters defined in
the Table tab of the subscriber list Properties dialogue to all the subscribers you add to the list. For more information on
the Table tab, see "Creating a Subscriber List" on page 60.
To add subscribers to a subscriber list using the mouse:
3. Right-click the subscriber list to which you want to add subscribers. The context menu appears.
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 46.

0.3.4.1.2 Importing a Subscriber List

You can also import subscriber lists from text files (TXT) or comma separated value files (CSV), including Microsoft Excel
files exported in CSV format.
To import a subscriber list:
2. Right-click the Subscribers folder. The context menu appears.
3. Select Import from the context menu.
For more information on importing table data, see "Importing Tables from Text Files" on page 65.
Note: You can also export subscriber lists. For information on exporting table data, see "Exporting
Tables to Text Files" on page 65.
0.3.4.2 Performing Calculations on Subscriber lists

You can perform calculations on subscriber lists without having to carry out simulations first. Atoll does not base calcula-
tions performed 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 calculations based on subscribers.
Atoll includes an Automatic Server Allocation feature which performs the following for all the subscribers in a list:
Azimuth: The orientation of the subscriber antenna in the horizontal plane. Azimuth is always considered with
respect to the North. Atoll calculates this value according to the serving base station if the Lock Status field is
set to either Server or None. 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 pos-
itive when it is downwards and negative when upwards. Atoll calculates this value according to the serving base
station if the Lock Status field is set to either Server or None. Atoll points the subscriber antenna towards its
serving base station.
Serving Base Station: The serving transmitter of the subscriber. Atoll determines the serving base station for
subscribers whose Lock Status field is set to None.
Reference Cell: The reference cell of the serving transmitter of the subscriber. Atoll determines the reference
cells for subscribers whose Lock Status field is set to None.
Received Power (DL) (dBm): The signal level received at the subscriber location in the downlink.
Interference + Noise (DL) (dBm): The interference + noise level experienced at the subscriber location in the
downlink.
C/(I+N) (DL) (dB): The C/(I+N) at the subscriber location in the downlink.
Bearer (DL): The highest LTE bearer available for the C/(I+N) level at the subscriber location in the downlink.
BLER (DL): The Block Error Rate read from the subscribers terminal types reception equipment for the C/(I+N)
level at the subscriber location in the 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.
Effective RLC Channel Throughput (DL) (kbps): The effective RLC channel throughput attainable using the
highest bearer available at the subscriber location in the downlink.
Received Power (UL) (dBm): The signal level received at the serving transmitter from the subscriber terminal in
the uplink.
Interference + Noise (UL) (dBm): The interference + noise level experienced at the serving transmitter of the
subscriber in the uplink.
C/(I+N) (UL) (dB): The C/(I+N) at the serving transmitter of the subscriber in the uplink.
Bearer (UL): The highest LTE bearer available for the C/(I+N) level at the serving transmitter of the subscriber in
the uplink.
BLER (UL): The Block Error Rate read from the reference cells reception equipment for the C/(I+N) level at the
serving transmitter of the subscriber in the uplink.
Transmission Power (UL) (dBm): The transmission power of the subscribers terminal after power control in the
uplink.
Number of Used Resource Blocks (UL): The number of resource blocks being used by the subscriber in the
uplink.
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.
Effective RLC Channel Throughput (UL) (kbps): The effective RLC channel throughput attainable using the
highest bearer available at the serving transmitter of the subscriber in the uplink.
Note: In Atoll, channel throughputs are peak RLC, effective RLC, or application level throughputs
achieved at a given location using the highest LTE bearer with the entire channel
resources.
To perform calculations on a subscriber list:


Atoll User Manual
3. Right-click the subscriber list on which you want to perform calculations. The context menu appears.
4. Select Calculations > Automatic Server Allocation from the context menu. The Automatic Server Allocation
dialogue appears.
If you want the calculations 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 signal level
calculations is based on the model standard deviation, and the shadowing margin for C/(I+N) calculations is based
on the C/I standard deviation.
5. Click Calculate to start the calculations. The progress of the calculation, as well as any error messages, is dis-
played 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.
0.3.5 Calculating and Displaying Traffic Simulations

To plan and optimise LTE networks, you will need to study the network capacity and to study the network coverage taking
into account realistic user distribution and traffic demand scenarios.
In Atoll, a simulation corresponds to a given distribution of LTE users. It is a snapshot of an LTE network. The principal
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.
LTE 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.
LTE simulation results can be stored in the cells table and used in C/(I+N), bearer, and throughput coverage predictions.
"LTE Traffic Simulation Algorithm" on page 64.
"Creating Simulations" on page 66.
"Displaying the Traffic Distribution on the Map" on page 67.
"Displaying the Results of a Single Simulation" on page 70.
"Updating Cell Load Values With Simulation Results" on page 74.
"Estimating a Traffic Increase" on page 74.
0.3.5.1 LTE Traffic Simulation Algorithm

Figure 0.45 shows the LTE simulation algorithm. The simulation process in LTE consists of the following steps:
1. Mobile Generation and Distribution
Simulations require traffic data, such as traffic maps (raster, vector, or live traffic data) or subscriber lists. Atoll
generates a user distribution for each simulation using a Monte Carlo algorithm. This user distribution is based on
the traffic data input and is weighted by a Poisson distribution.
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 connection probabilities. The
transmission status is an important output of the simulation as it has a direct impact on the next step of the simu-
lation 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.

Figure 0.45: LTE simulation algorithm
2. Best Server Determination

Atoll determines the best server for each mobile based on the signal level in the downlink.
3. Downlink Calculations
The downlink calculations include the calculation of downlink C/(I+N), determination of the best available bearer
for the C/(I+N), allocation of resources (RRM), and calculation of user throughputs.
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 calculation of the number of used resource blocks depending on the bearer, allo-
cation of resources (RRM), update of uplink noise rise values for cells, and calculation of user throughputs.
5. Radio Resource Management and Cell Load Calculation

Atoll uses an intelligent scheduling algorithm to perform radio resource management. The scheduling algorithm
is explained in detail in the Technical Reference Guide. The scheduler:
a. Determines the total amount of resources in each cell

b. Selects the first N users from the users generated in the first step, where N is the Max Number of Users de-
fined in the cell properties.
c. Sorts the users in decreasing order by service priority
d. Allocates the resources required to satisfy the minimum throughput demands of the users starting from the
first user (with the highest priority service) to the last user.
e. If resources still remain in the resource pool after this allocation, allocates resources to the users with maxi-
mum throughput demands according to the used scheduling algorithm.
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 re-

Atoll User Manual
source allocation, or he can be rejected due to "Resource Saturation," i.e., all of the cells resources were used up by other
users.
0.3.5.2 Creating Simulations

In Atoll, simulations enable you to study the capacity of your LTE network and model the different network regulation
mechanisms, such as power control and scheduling, in order to optimise network performance and maximise capacity.
You can create one simulation or a group of simulations that will be performed in sequence. You must have at least one
traffic map or subscriber list in your document to be able to perform simulations.
To create a simulation or a group of simulations:
2. Right-click the LTE 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. On the General tab of the dialogue, enter a Name and Comments for this simulation or group of simulations.
5. Under Execution on the General tab, you can set the following parameters:
- Number of Simulations: Enter the number of simulations to be carried out. All simulations created at the
same time are grouped together in a folder on the Data tab of the Explorer window.
- 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.
Note: Execute Later enables you to automatically calculate LTE coverage predictions after simu-
lations with no intermediary step by creating your simulations, creating your predictions and
then clicking the Calculate button ( ).
6. 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.
- 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 53.
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 simula-
tions on subscribers.
7. Click the Advanced tab.

8. 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.
9. Under Convergence, enter the following parameters:

- Max Number of Iterations: Enter the maximum number of iterations that Atoll should run to make conver-
gence.
- DL Traffic Load Convergence Threshold: Enter the relative difference in terms of downlink traffic load that
must be reached between two iterations.
- UL Traffic Load Convergence Threshold: Enter the relative difference in terms of uplink traffic load that
must be reached between two iterations.
- UL Noise Rise Convergence Threshold: Enter the relative difference in terms of uplink noise rise that must
be reached between two iterations.

10. Click OK. Atoll immediately begins the simulation unless you selected the Execute Later check box on the Gen-
eral tab.
All simulations created at the same time are grouped together in a folder on the Data tab of the Explorer window. You can
now use the results from completed simulations for LTE coverage predictions.
0.3.5.3 Displaying the Traffic Distribution on the Map

Atoll enables you to display on the map the distribution of the traffic generated by all simulations according to different
parameters. You can, for example, display the traffic according to activity status, service, reference cell, or throughputs.
You can set the display of the traffic distribution according to discrete values and the select the value to be displayed. Or,
you can select the display of the traffic distribution according to value intervals, and then select the parameter and the
value intervals that are to be displayed. You can also define the colours of the icon and the icon itself.
For information on changing display characteristics, see "Defining the Display Properties of Objects" on page 41.
In this section are the following examples of traffic distribution:
"Displaying the Traffic Distribution by Activity Status" on page 67.
"Displaying the Traffic Distribution by Connection Status" on page 67.
"Displaying the Traffic Distribution by Service" on page 68.
"Displaying the Traffic Distribution by Throughput" on page 68.
"Displaying the Traffic Distribution by Uplink Transmission Power" on page 69.
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 36.
0.3.5.3.1 Displaying the Traffic Distribution by Activity Status

In this example, the traffic distribution is displayed by the activity status.
To display the traffic distribution by the activity status:
3. Select Properties from the context menu. The LTE Simulations Properties dialogue appears.
4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "Activity Status" as the Field.
5. Click OK. The traffic distribution is now displayed by activity status (see Figure 0.46).
Figure 0.46: Displaying the traffic distribution by activity status
0.3.5.3.2 Displaying the Traffic Distribution by Connection Status

In this example, the traffic distribution is displayed by the connection status.
To display the traffic distribution by the connection status:
4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "Connection Status" as the
Field.
5. Click OK. The traffic distribution is now displayed by activity status (see Figure 0.47).

Atoll User Manual
Figure 0.47: Displaying the traffic distribution by connection status
0.3.5.3.3 Displaying the Traffic Distribution by Service

In this example, the traffic distribution is displayed by service.
To display the traffic distribution by service:
4. On the Display tab of the dialogue, select "Discrete values" as the Display Type and "Service" as the Field.
5. Click OK. The traffic distribution is now displayed by service (see Figure 0.48).
Figure 0.48: Displaying the traffic distribution by service
0.3.5.3.4 Displaying the Traffic Distribution by Throughput

In this example, the traffic distribution is displayed by throughput.
To display the traffic distribution by throughput:
4. On the Display tab of the dialogue, select "Value intervals" as the Display Type and one of the following
throughput types as the Field:
- Peak RLC Channel Throughput (DL)
- Effective RLC Channel Throughput (DL)
- Application Level Channel Throughput (DL)
- Peak RLC User Throughput (DL)
- Effective RLC User Throughput (DL)
- Application Level User Throughput (DL)

- Peak RLC Channel Throughput (UL)

- Effective RLC Channel Throughput (UL)
- Application Level Channel Throughput (UL)
- Peak RLC User Throughput (UL)
- Effective RLC User Throughput (UL)
- Application Level User Throughput (UL)
5. Click OK. The traffic distribution is now displayed by throughput (see Figure 0.49).
Figure 0.49: Displaying the traffic distribution by throughput
0.3.5.3.5 Displaying the Traffic Distribution by Uplink Transmission Power

In this example, the traffic distribution is displayed by the uplink transmission power of the mobiles. You can analyse the
effect of the uplink power control.
To display the traffic distribution by uplink transmission power:
4. On the Display tab of the dialogue, select "Value intervals" as the Display Type and "Transmission Power (UL)
(dBm)" as the Field.
5. Click OK. The traffic distribution is now displayed by uplink transmission power (see Figure 0.50).
Figure 0.50: Displaying the traffic distribution by uplink transmission power

Atoll User Manual
0.3.5.3.6 Displaying Traffic Simulation Results Using Tooltips

You can display information by placing the pointer over a mobile generated during a simulation to read the information
displayed in the tool tips. The information displayed is defined by the settings you made on the Display tab. For information
on defining the tool tips, see "Defining the Object Type Tip Text" on page 44
To display simulation results in the form of tool tips:
In the map window, place the pointer over the user that you want more information on. After a brief pause, the
tooltip appears with the information defined in the Display tab of the LTE Simulations folder properties (see
Figure 0.51).
Figure 0.51: Displaying the traffic simulation results using tool tips
0.3.5.4 Displaying the Results of a Single Simulation

After you have created a simulation, as explained in "Creating Simulations" on page 66, you can display the results.
To access the results of a single simulation:
2. Click the Expand button ( ) to expand the LTE Simulations folder.
3. Click the Expand button ( ) to expand the folder of the simulation group containing the simulation whose results
you want to access.
4. Right-click the simulation. The context menu appears.
5. Select Properties from the context menu. The simulation properties dialogue appears.
One tab gives statistics of the simulation results. Other tabs in the simulation properties dialogue contain simula-
tion results as identified by the tab title.
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 number and percentage 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 RLC User Throughput (DL) (kbps): The sum of peak RLC user throughputs of all the users connected
in the downlink in all the cells of the site.
- Effective RLC User Throughput (DL) (kbps): The sum of effective RLC user throughputs of all the users
connected in the downlink in all the cells of the site.
- Application Level User Throughput (DL) (kbps): The sum of application level throughputs of all the users
- Peak RLC User Throughput (UL) (kbps): The sum of peak RLC user throughputs of all the users connected
in the uplink in all the cells of the site.
- Effective RLC User Throughput (UL) (kbps): The sum of effective RLC user throughputs of all the users
connected in the uplink in all the cells of the site.
- Application Level User Throughput (UL) (kbps): The sum of application level throughputs of all the users
- Peak RLC User Throughput (DL) (kbps) For Each Service: For each service, the sum of peak RLC user
throughputs of the users connected in the downlink in all the cells of the site.
- Effective RLC User Throughput (DL) (kbps) For Each Service: For each service, the sum of effective RLC
user throughputs of the users connected in the downlink in all the cells of the site.

- Application Level User Throughput (DL) (kbps) For Each Service: For each service, the sum of application
level throughputs of the users connected in the downlink in all the cells of the site.
- Peak RLC User Throughput (UL) (kbps) For Each Service: For each service, the sum of peak RLC user
throughputs of the users connected in the uplink in all the cells of the site.
- Effective RLC User Throughput (UL) (kbps) For Each Service: For each service, the sum of effective RLC
user throughputs of the users connected in the uplink in all the cells of the site.
- Application Level User Throughput (UL) (kbps) For Each Service: For each service, the sum of application
level throughputs of the users connected in the uplink in all the cells of the site.
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.
in the downlink.
connected in the downlink.
in the uplink.
connected in the uplink.
throughputs of the users connected in the downlink.
user throughputs of the users connected in the downlink.
level throughputs of the users connected in the downlink.
throughputs of the users connected in the uplink.
user throughputs of the users connected in the uplink.
level throughputs of the users connected in the uplink.
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 Power (DL) (dBm): The 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.
- Interference + Noise (DL) (dBm): The interference + noise level experienced at the user location in the down-
link.
- C/(I+N) (DL) (dB): The C/(I+N) at the user location in the downlink.
- Bearer (DL): The highest LTE bearer available for the C/(I+N) level at the user location in the downlink.
- BLER (DL): The Block Error Rate read from the user terminals reception equipment for the C/(I+N) level at
the user location in the downlink.
- Peak RLC Channel Throughput (DL) (kbps): The maximum RLC channel throughput attainable using the
highest bearer available at the user location in the downlink.

Atoll User Manual
- Effective RLC Channel Throughput (DL) (kbps): The effective RLC channel throughput attainable using the
highest bearer available at the user location in the downlink. It is calculated from the peak RLC throughput and
the BLER.
- Application Level Channel Throughput (DL) (kbps): The application level throughput is the net throughput
without coding (redundancy, overhead, addressing, etc.). It is calculated from the effective RLC throughput,
the throughput scaling factor of the service and the throughput offset.
- Peak RLC User Throughput (DL) (kbps): The maximum RLC user throughput attainable using the highest
bearer available at the user location in the downlink.
- Effective RLC User Throughput (DL) (kbps): The effective RLC user throughput attainable using the highest
bearer available at the user location in the downlink. It is calculated from the peak RLC throughput and the
BLER.
- Application Level User Throughput (DL) (kbps): The application level throughput is the net throughput
- Received Power (UL) (dBm): The signal level received at the serving transmitter from the user terminal in
the uplink.
- Interference + Noise (UL) (dBm): The interference + noise level 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 LTE bearer available for the C/(I+N) level at the serving transmitter of the user in
the uplink.
- BLER (UL): The Block Error Rate read from the reference cells reception equipment for the C/(I+N) level at
the serving transmitter of the user in the uplink.
- Transmission Power (UL) (dBm): The transmission power of the user terminal after power control in the
uplink.
- Number of Used Resource Blocks (UL): The number of resource blocks being used by the user in the uplink.
- Peak RLC Channel Throughput (UL) (kbps): The maximum RLC channel throughput attainable using the
highest bearer available at the serving transmitter of the user in the uplink.
- Effective RLC Channel Throughput (UL) (kbps): The effective RLC channel throughput attainable using the
highest bearer available at the serving transmitter of the user in the uplink. It is calculated from the peak RLC
throughput and the BLER.
- Application Level Channel Throughput (UL) (kbps): The application level throughput is the net throughput
- Peak RLC User Throughput (UL) (kbps): The maximum RLC user throughput attainable using the highest
bearer available at the serving transmitter of the user in the uplink.
- Effective RLC User Throughput (UL) (kbps): The effective RLC user throughput attainable using the highest
bearer available at the serving transmitter of the user in the uplink. It is calculated from the peak RLC
throughput and the BLER.
- Application Level User Throughput (UL) (kbps): The application level throughput is the net throughput
Notes:
In Atoll, channel throughputs are peak RLC, effective RLC, or application level throughputs
achieved at a given location using the highest LTE 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 global transmitter parameters:
- The default cyclic prefix
- The PDCCH and PUCCH fixed overheads
- The TDD-specific parameter: Switching point periodicity
- The UL power control margin
- The input parameters specified when creating the simulation:
- The maximum number of iterations
- The uplink and downlink traffic load convergence thresholds
- The uplink noise rise convergence threshold
- The names of the traffic maps and subscriber lists used.
- The parameters related to the clutter classes, including the default values.
0.3.5.5 Displaying the Average Results of a Group of Simulations

After you have created a group of simulations, as explained in "Creating Simulations" on page 66, you can display the
average results of the group. If you wish to display the results of a single simulation in a group, see "Displaying the Results
of a Single Simulation" on page 70.
To display the averaged results of a group of simulations:

3. Right-click the group of simulations whose results you want to display.

4. Select Average Simulation from the context menu. A properties dialogue appears.
One tab gives statistics of the simulation results. Other tabs in the simulation properties dialogue contain the aver-
aged results for all simulations of the group.
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 number and percentage 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:
in the downlink in all the cells of the site.
in the uplink in all the cells of the site.
throughputs of the users connected in the downlink in all the cells of the site.
user throughputs of the users connected in the downlink in all the cells of the site.
level throughputs of the users connected in the downlink in all the cells of the site.
throughputs of the users connected in the uplink in all the cells of the site.
user throughputs of the users connected in the uplink in all the cells of the site.
level throughputs of the users connected in the uplink in all the cells of the site.
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.
in the downlink.
in the uplink.
throughputs of the users connected in the downlink.
user throughputs of the users connected in the downlink.
level throughputs of the users connected in the downlink.
throughputs of the users connected in the uplink.

Atoll User Manual
user throughputs of the users connected in the uplink.
level throughputs of the users connected in the uplink.
0.3.5.6 Updating Cell Load Values With Simulation Results

After you have created a simulation or a group of simulations, as explained in "Creating Simulations" on page 66, you can
update cell load values for each cell with the results calculated during the simulation.
To update cell values with simulation results:
1. Display the simulation results:
To display the results for a group of simulations:

b. Click the Expand button ( ) to expand the LTE Simulations folder.
c. Right-click the group of simulations whose results you want to access.
d. Select Average Simulation from the context menu. A properties dialogue appears.
One tab gives statistics of the results of the group of simulations. Other tabs in the properties dialogue contain
average simulation results for all simulations.
To display the results for a single simulation:

b. Click the Expand button ( ) to expand the LTE Simulations folder.
c. Click the Expand button ( ) to expand the folder of the simulation group containing the simulation whose re-
sults you want to access.
d. Select Properties from the context menu. The simulation properties dialogue appears.
2. Click the Cells tab.
3. On the Cells tab, click Commit Results. The following values are updated for each cell:
- Traffic Load (DL)
- Traffic Load (UL)
- UL Noise Rise
0.3.5.7 Estimating a Traffic Increase

When you create simulation or a group of simulations, you are basing it on a set of traffic conditions that represent the
situation you are creating the network for. However, traffic can, and in fact most likely will, increase. You can test the
performance of the network against an increase of traffic load without changing traffic parameters or maps by using the
global scaling factor. For example, setting the global scaling factor to 2 is the same as doubling the initial number of
subscribers (for environment and user profile traffic maps) or the rates/users (for live traffic maps per sector).
To change the global scaling factor:
1. Create a simulation or group of simulations as described in "Creating Simulations" on page 66.
2. Click the Source Traffic tab of the properties dialogue.
3. Enter a Global Scaling Factor. For example, setting the global scaling factor to 2 is the same as doubling the
initial number of subscribers (for environment and user profile traffic maps) or the rates/users (for live traffic maps
per sector).
0.3.6 Making Coverage Predictions Using Simulation Results

In Atoll, you can can analyse simulation results by making coverage predictions using simulation results. In a coverage
prediction each pixel is considered as a non-interfering probe user with a defined terminal, mobility, and service. The anal-
yses can be based on a single simulation or on an averaged group of simulations.
When no simulations are available, Atoll uses the downlink traffic load and the uplink noise rise stored for each cell to
make coverage predictions. For information on cell properties, see "Cell Description" on page 7; for information on modi-
fying cell properties, see "Creating or Modifying a Cell" on page 9.
Once you have made simulations, Atoll can use the information from the simulations instead of the defined parameters in
the cell properties to make coverage predictions. For each coverage prediction based on simulation results, you can base
the coverage prediction on a selected simulation or on a group of simulations, which uses the average of all simulations
in the group.
The coverage predictions that can use simulation results are:
Coverage by C/(I+N) Level: For information on making a downlink or uplink coverage by C/(I+N) level, see
"Making a Coverage by C/(I+N) Level" on page 41.
Coverage by Best Bearer: For information on making a downlink or uplink coverage by best bearer, see "Making
a Coverage by Best Bearer" on page 43.

Coverage by Throughput: For information on making a downlink or uplink coverage by throughput, see "Making
a Coverage by Throughput" on page 45.
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 simula-
tions.
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.
0.4 Advanced Configuration

The following sections describe different advanced parameters and options available in the LTE module that are used in
coverage predictions as well as Monte Carlo simulations.
In this section, the following advanced configuration options are explained:
"Defining Frequency Bands" on page 75.
"The Global Transmitter Parameters" on page 75.
"Defining LTE Radio Bearers" on page 77.
"Defining LTE Quality Indicators" on page 77.
"Defining LTE Reception Equipment" on page 78.
"Multiple Input Multiple Output Systems" on page 80.
"Modelling Shadowing" on page 82.
0.4.1 Defining Frequency Bands

To define frequency bands:
3. Select Network Settings > Frequencies > Bands from the context menu.
4. In the table, enter one frequency band per row. For information on working with data tables, see "Working with
Data Tables" on page 57. For each frequency band, enter:
- Name: Enter a name for the frequency band, for example, "1.91 GHz - 5 MHz." Each LTE frequency band has
a specific channel bandwidth. Mentioning the channel bandwidth in the frequency band name is a good
approach. This name will appear in other dialogues when you select a frequency band.
- Channel Width (MHz): Enter the channel bandwidth for each channel in the frequency band.
- 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. If this frequency band has only
one carrier, enter the same number as entered in the First Channel field.
Note: The relationship between the frequency band (spectrum), the channel width, and the chan-
nel 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
3 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 / 3 MHz) - 1 = 4
- Excluded Channels: Enter the channel numbers which do not constitute 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 Frequency: Enter the sampling frequency used for the channel bandwidth.
- Duplexing Method: Select the duplexing method used in the frequency band from the list.
- Number of Resource Blocks: Enter the number of resource blocks used for the channel bandwidth.
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.
0.4.2 The Global Transmitter Parameters

Atoll allows you to set network level parameters which are common to all the transmitters and cells in the network. These
parameters are used in coverage predictions as well as during Monte Carlo simulations by the radio resource management
and scheduling algorithms.

Atoll User Manual
This section explains the options available on the Global Parameters tab of the Transmitters Properties dialogue, and
explains how to access the tab:
"The Options on the Global Parameters Tab" on page 76.
"Modifying Global Transmitter Parameters" on page 76.
0.4.2.1 The Options on the Global Parameters Tab

The global LTE parameters include:
Default Cyclic Prefix: The total symbol duration in LTE comprises the useful part of the symbol, carrying the data
bits, and a cyclic prefix part, which is a portion of the useful data part repeated at the beginning of each symbol.
The cyclic prefix is the method used by LTE to counter inter-symbol interference (ISI). The cyclic prefix and the
orthogonality of subcarriers ensure that there is negligible intra-cell interference in LTE. LTE supports two cyclix
prefix types: normal and extended.
Fixed control channel overheads: The fixed control channel overheads in the downlink and uplink subframes
are used to model the PDCCH and PUCCH overheads, resepectively. The PDCCH can take up to 3 symbol dura-
tions in each resource block in the downlink. Whereas the PUCCH can take a number of resource blocks in the
uplink. This is the reason why the PDCCH overhead is available in terms of symbol duration (SD) and the PUCCH
overhead in terms of resource blocks. The PDCCH is considered to include the PFICH and PHICH as well.
The PBCH, P-SCH, S-SCH, and the downlink reference signals consume a fixed amount of resource elements in
the downlink. Similarly, the uplink demodulation and sounding reference signals consume a fixed amount of
resource elements in the uplink. These downlink and uplink overheads are hard-coded in Atoll and cannot be
changed.
Switching Point Periodicity (TDD only): For the TDD LTE frame, the switching point can either be after each
half-frame or each frame. You can select the frame configuration, i.e., the configuration of uplink and downlink
subframes in a frame, for each cell according to the selected switching point periodicity.
Uplink power control margin: The margin (in dB) that will be added to the bearer selection threshold of the
highest bearer for safety against fast fading when performing power control on the uplink.
Figure 0.52 and Figure 0.53 give examples of downlink and uplink FDD resource blocks for the single antenna case using
the normal cyclic prefix. an LTE frame with the described parameters marked.
Figure 0.52: LTE downlink resource blocks
Figure 0.53: LTE uplink resource blocks
0.4.2.2 Modifying Global Transmitter Parameters

You can change global transmitter parameters on the Global Parameters tab of the Transmitters Properties dialogue.
To set the network level parameters:
4. Select the Global Parameters tab.
The Global Parameters tab has three sections.

- Frame Structure: In this section (see Figure 0.54), you can modify the following: the Default Cyclic Prefix
and the fixed overheads for the uplink and the downlink subframes, and, for TDD networks, the switching point
periodicity.
- Power Control: In this section, you can enter the Uplink Power Control Margin.
Figure 0.54: LTE Global Parameters
5. Click OK. The global parameters are used during coverage predictions and simulations for the entire network.
0.4.3 Defining LTE Radio Bearers

LTE radio bearers carry the data in the uplink as well as in the downlink.
Note: In the Atoll LTE module, a "bearer" refers to a combination of MCS, i.e., modulation, and
coding schemes.
The LTE Bearers table lists the radio bearers available in Atoll by default. You can add, remove, and modify bearer prop-
erties, if you wish.
To define LTE bearers:
3. Select Network Settings > LTE Bearers from the context menu. The LTE 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 57. For each LTE 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 LTE reception 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.
- Bearer Efficiency (bits/symbol): Enter the number of useful bits that the bearer can transfer in a symbol.
This information is used in throughput calculations.
For information on the relation between bearer efficiency and spectral efficiency, see "Relation Between
Bearer Efficiency And Spectral Efficiency" on page 86.
5. Click the Close button ( ) to close the LTE Bearers table.
0.4.4 Defining LTE Quality Indicators

Quality indicators depict the coverage quality at different locations. The Quality Indicators table lists the quality indicators
available in Atoll by default. You can add, remove and modify quality indicators, if you wish.
To define quality indicators:
3. Select Network Settings > Quality Indicators from the context menu. The Quality Indicators table appears.
4. In the table, enter one quality indicator per row. For information on working with data tables, see "Working with
Data Tables" on page 57. For each quality indicator, enter:

Atoll User Manual
- Name: Enter a name for the quality indicator, for example, "BLER" for Block Error Rate. This name will appear
in other dialogues and results.
- Used for Data Services: Select this check box to indicate that this quality indicator can be used for data serv-
ices.
- Used for Voice Services: Select this check box to indicate that this quality indicator can be used for voice
services.
5. Click the Close button ( ) to close the Quality Indicators table.
0.4.5 Defining LTE Reception Equipment

LTE reception equipment model the reception characteristics of cells and user terminals. Bearer selection thresholds and
channel quality indicator graphs are defined in reception equipment.
To create a new piece of LTE reception equipment:
3. Select Equipment > LTE Equipment from the context menu. The LTE Equipment table appears.
4. In the LTE Equipment table, each row describes a piece of equipment. For the new piece of LTE equipment you
are creating, enter its name.
5. Double-click the equipment entry in the LTE Equipment table once your new equipment has been added to the
table. The equipments Properties dialogue opens.
The Properties dialogue has the following tabs:
- Bearer Selection Thresholds: In this tab (see Figure 0.55), 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 LTE Radio Bearers" on page 77 and "Modelling Mobility Types" on page 38,
respectively.
Figure 0.55: LTE Reception Equipment - Bearer Selection Thresholds
a. Click the Best Bearer Thresholds button. The C/(I+N) Thresholds (dB) dialogue appears (see Figure 0.56).
b. Enter the graph values.
c. Click OK.
Figure 0.56: C/(I+N) Thresholds (dB) dialogue

For more information on the default values of the bearer selection thresholds, see "Bearer Selection Thresh-
olds" on page 85. For converting receiver equipment sensitivity values (dBm) into bearer selection thresholds,
see "Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 85.
- Quality Graphs: On this tab (see Figure 0.57), 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
LTE Radio Bearers" on page 77, "Defining LTE Quality Indicators" on page 77, and "Modelling Mobility Types"
on page 38, respectively.
Figure 0.57: LTE Reception Equipment - Quality Indicator Graphs
a. Click the Quality Graph button. The the Quality Graph dialogue appears (see Figure 0.58).
b. Enter the graph values.
c. Click OK.
Figure 0.58: Quality Indicator Graph dialogue
6. Click OK. The Properties dialogue closes. The settings are stored.
7. Click the Close button ( ) to close the LTE Equipment table.
0.4.6 Defining LTE Schedulers

In Atoll, schedulers perform the selection of users for resource allocation, the radio resource allocation and management
according to the priorities of the services being accessed by the selected users.
The scheduling process is composed of the following three steps:
1. Selection of users for resource allocation: The Max Number of Users defined for each cell is the maximum
number of users that the cells scheduler can work with simultaneously. At the start of the scheduling process, the
scheduler keeps only as many users as the maximum number defined for resource allocation. If no limit has been

Atoll User Manual
set, all the users generated during the Monte Carlo simulations for this cell are considered, and the scheduler
continues to allocate resources until there are no more resources to allocate.
2. Resource allocation for supporting the Min Throughput Demands: The minimum throughput demand is the
guaranteed bit rate of a service. If there are enough resources available, the scheduler may be able to allocate
the exact amount of resources required to fully support the minimum throughput demands, otherwise the service
does not get any resources at all.
The scheduler allocates resources, for supporting the minimum throughput demands, in the order of service prior-
ity. In order to be connected, users who are active in downlink and uplink must be able to get their minimum
throughput in both directions. If a user who is active in downlink and uplink gets his minimum throughput in only
one direction, he will be rejected.
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.
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.
- Max Aggregate Throughput: This scheduling method allocates the resources required by the users to
achieve their maximum throughput demands in the order of their C/(I+N). This means that users who are under
good radio conditions, high 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 LTE schedulers:
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 57. 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.
- 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.
0.4.7 Multiple Input Multiple Output Systems

Multiple Input Multiple Output (MIMO) systems use different transmission and reception diversity techniques. MIMO diver-
sity systems can roughly be divided into the following types:
1. Transmit Diversity uses more than one transmission antenna to send the same signal on all antennas. The
signals are constructively combined 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 much more resistant
to interference than a single signal would be. Therefore, transmit diversity 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.
2. 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 multi-
plexing with M transmission 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. Spatial Multiplexing 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.
3. AMS (Adaptive MIMO Switch) is a technique for switching from spatial multiplexing to transmit diversity as the
signal conditions get worse than a given threshold. AMS can be used in cells to provide spatial multiplexing gains
to users that have better C/N conditions than a given AMS threshold, and transmit diversity gains to users that

have worse C/N conditions than the threshold. AMS provides the optimum solution using both MIMO features to
their best.
Atoll models all of the above three MIMO systems. The following sections describe how these three systems are modelled
and used in Atoll.
Transmit Diversity Modelling
During calculations, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell that
supports transmit diversity, will benefit from the downlink and uplink transmit diversity C/(I+N) gains depending on the
numbers of transmission and reception antennas, mobility, and its clutter class.
Transmit diversity gains on downlink and uplink can be defined in the MIMO configurations for different numbers of trans-
mission and reception antennas, and for different mobility types. Offsets with respect to these gain values can be defined
per clutter class. For information on setting the transmit diversity uplink and downlink gain offsets for each clutter class or
for all clutter classes, see "Defining Clutter Class Properties" on page 106. For more information on uplink and downlink
transmit diversity gains, see "Defining MIMO Configurations" on page 81.
Spatial Multiplexing Modelling
supports spatial multiplexing, will benefit from the spatial multiplexing gain in its throughput depending on its C/(I+N),
number of transmission and reception antennas, mobility, and its clutter class.
As spatial multiplexing improves the channel capacity or throughputs, the C/(I+N) of a user is first determined without
considering any MIMO gain. Once the 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 SM capacity gain, read from the
MIMO gain graphs for the users C/(I+N) level, mobility and numbers of transmission and reception antennas, and the SM
Gain Factor of the users clutter class.
The maximum theoretical capacity gains defined in Max MIMO Gain graphs (MIMO configurations) are the maximum
possible 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, it is possible to define an SM Gain Factor per clutter
class whose value can vary from 0 to 1 (0 = no gain, 1 = 100 % gain).
For information on setting the SM Gain Factor for each clutter class or for all clutter classes, see "Defining Clutter Class
Properties" on page 106. For more information about MIMO gain graphs, see "Defining MIMO Configurations" on page 81.
Adaptive MIMO Switch Modelling
supports AMS, will benefit from either the transmit diversity or the spatial multiplexing gain depending on the users C/N
and the AMS threshold defined in the cell properties. Transmit diversity gain is applied to the users C/(I+N) if the users
C/N is less than the AMS threshold, and spatial multiplexing gain is used if the C/N is higher than the AMS threshold.
TX RX
No MIMO gain is applied in case N Ant = N Ant = 1 .
0.4.7.1 Defining MIMO Configurations

MIMO gains are modelled in Atoll using MIMO configurations. A MIMO configuration contains uplink and downlink transmit
diversity gain values and spatial multiplexing capacity gain vs. C/(I+N) graphs for different numbers of transmission and
reception antennas. The capacity gain due to spatial multiplexing is the increase in channel capacity compared to a SISO
system.
To create a MIMO configuration:
3. Select Network Settings > MIMO Configurations from the context menu. The MIMO Configurations table
appears.
4. In the MIMO Configurations table, each row describes a different combination of number of transmission and
reception antennas, uplink and downlink transmit diversity gains, and the spatial multiplexing gain. For information
on working with data tables, see "Working with Data Tables" on page 57. For each MIMO configuration:
- Name: Enter a name for the MIMO configuration.
- Mobility: Select the mobility type corresponding to the MIMO configuration from the list.
- Number of Transmission Antennas: Enter the number of transmission antennas for MIMO.
- Number of Reception Antennas: Enter the number of reception antennas for MIMO.
- Transmit Diversity Gain (DL) (dB): Enter the downlink transmit diversity gain (in dB) for the number of trans-
mission and reception antennas.
- Transmit Diversity Gain (UL) (dB): Enter the uplink transmit diversity gain (in dB) for the number of trans-
mission and reception antennas.
- Max MIMO Gain: Enter the graph of the maximum MIMO (spatial multiplexing) gain vs. C/(I+N) for the number
of transmission and reception antennas.
You can access the Max MIMO Gain Graph dialogue of each MIMO configuration by double-clicking the corre-
sponding record in the MIMO Configurations table.

Atoll User Manual
Figure 0.59: Max MIMO Gain Graph dialogue
The MIMO capacity gain vs. C/(I+N) graphs available in Atoll by default have been generated based on the maximum
theoretical MIMO capacity gains obtained using the following equations:
CC MIMO
G MIMO = ---------------------
-
CC SISO
RX
TX RX N Ant C
Where CC MIMO = Min ( N Ant, N Ant ) Log 2 1 + -----------
- ----------------- is the channel capacity at a given C/(I+N) for a MIMO
N Ant
TX ( I + N )
system using N Ant transmission and N Ant reception antennas. CC SISO = Log 2 1 + ----------------- is the channel capacity for
TX RX C
( I + N )
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 create and modify MIMO configurations using MIMO capacity gain graphs generated through MIMO simulators
or measurements from an existing network.
To create MIMO capacity gain graphs from measurement data:
TX
1. Note the number of transmission antennas N Ant .
RX
2. Note the number of reception antennas N Ant .
TX RX
3. Measure the SISO throughputs at different C/(I+N) levels, i.e., for N Ant = N Ant = 1 .
TX RX
4. Measure the MIMO throughputs at the same C/(I+N) levels, i.e., for the numbers of antennas N Ant and N Ant
used.
5. Calculate the MIMO capacity gains for the C/(I+N) levels, at which you measured the throughputs, by taking the
ratio between the MIMO and the SISO throughputs.
6. Create a new MIMO configuration in Atoll for the number of transmission and reception antennas, and enter the
graph of MIMO capacity gain vs. C/(I+N).
0.4.8 Modelling Shadowing

Shadowing, or slow fading, is signal loss along a path that is caused by obstructions not taken into consideration by the
propagation model. Even when a receiver remains in the same location or in the same clutter class, there are variations
in reception due to the surrounding environment.
Normally, the signal received at any given point is spread on a gaussian curve around an average value and a specific
standard deviation. If the propagation model is correctly calibrated, the average of the results it gives should be correct.
In other words, in 50% of the measured cases, the result will be better and in 50% of the measured cases, the result will
be worse.
Atoll uses a model standard deviation for the clutter class with the defined cell edge coverage probability to model the
effect of shadowing and thereby create coverage predictions that are reliable more than fifty percent of the time. The addi-
tional losses or gains caused by shadowing are known as the shadowing margin. The shadowing margin is added to the
path losses calculated by the propagation model.
For example, a properly calibrated propagation model calculates a loss leading to a signal level of -70 dBm. You have set
a cell edge coverage probability of 85%. If the calculated shadowing margin is 7 dB for a specific point, the target signal
will be equal to or greater than -77 dBm 85% of the time.

In LTE projects, the model standard deviation is used to calculate shadowing margins on signal levels. You can also calcu-
late shadowing margins on C/I values. For information on setting the model standard deviation and the C/I standard devi-
ations for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 106.
Shadowing can be taken into consideration when Atoll calculates the signal level and C/(I+N) for:
A point analysis (see "Making a Point Analysis to Study the Profile" on page 16)
A coverage prediction (see "Studying Signal Level Coverage" on page 17).
Atoll always takes shadowing into consideration when calculating a Monte Carlo-based LTE simulation. Atoll uses the
values defined for the Model Standard Deviations per clutter class when calculating the signal level coverage predictions.
Atoll uses the values defined for the C/I Standard Deviations per clutter class when calculating the LTE coverage predic-
tions.
You can display the shadowing margins per clutter class. For information, see "Displaying the Shadowing Margins per
Clutter Class" on page 83.
0.4.8.1 Displaying the Shadowing Margins per Clutter Class

To display the shadowing margins per clutter class:
3. Select Shadowing Margins from the context menu. The Shadowing Margins dialogue appears (see
Figure 0.60).
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:
- From Model: The model standard deviation. Atoll will display the shadowing margin of the signal level.
- C/I: The C/I standard deviation. Atoll will display the C/I shadowing margin.
5. Click Calculate. The calculated shadowing margin is displayed.
6. Click Close to close the dialogue.
Figure 0.60: The Shadowing Margins dialogue
0.5 Tips and Tricks

The following tips and tricks are described below:
"Obtaining User Throughputs for All the Subscribers of a Subscriber List" on page 83.
"Working With User Densities Instead of User Profiles" on page 84.
"Limiting the Coverage Range of Transmitters in Order to Avoid Uplink-to-Downlink Interference in TDD Networks"
on page 84.
"Bearer Selection Thresholds" on page 85.
"Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 85.
"Relation Between Bearer Efficiency And Spectral Efficiency" on page 86.
"Displaying Coverage by Bearer Names" on page 86.
Obtaining User Throughputs for All the Subscribers of a Subscriber List
Important: This procedure is only recommended if you have a proper subscriber list and have com-
plete knowledge of the services they use.

Atoll User Manual
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 throughput and not the user throughput as the services being used by the subscribers are not known. In the simu-
lations, however, a service is determined for each subscriber in order to perform the RRM and determine the user through-
puts.
It might be useful to determine user level throughputs for all the subscribers in a subscriber list. You can calculate user
throughput for all the subscribers by running a simulation on this subscriber list after modifying the user profiles assigned
to all subscribers so that all subscribers have a connection probability of 100 %.
1. Create a subscriber list with subscribers having a connection 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.
d. Assign these user profiles to subscribers in the subscriber list.

2. Create a simulation based on this subscriber list only.
The simulation results will contain all the subscribers in the subscriber list with their respective user throughputs
determined by Atoll after the scheduling process.
Working With User Densities Instead of User Profiles
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 connection probabilities to create traffic scenarios during simulations. The distri-
bution 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 connection 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
requested throughputs, respectively, of the service defined in the user profile.
The above settings will set the user connection 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 connected users and their services generated during the simulations before-
hand.
This procedure should only be used when appropriate traffic data is not available.
Limiting the Coverage Range of Transmitters in Order to Avoid Uplink-to-Downlink Interference in

TDD Networks
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:
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.
For TDD networks, you can determine the maximum coverage range that the sectors of your LTE network should have
from the cyclic prefix duration and use this range as the Max Range parameter. You can calculate the maximum system
range from the cyclic prefix as follows:
Max Range (m) = Cyclic Prefix (in ms) x 300000/2
Bearer Selection Thresholds
The default values of the bearer selection thresholds, the BLER quality graphs, and the bearer efficiency values in Atoll
have been extracted from the graphs in the Figure 0.61 on page 85.
Figure 0.61: Link Adaptation in LTE
In the above graphs, 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.
If you want to model the bearer selection for a given level of BLER, instead of the default bearer selection which occurs at
the transition points (i.e., as soon as a bearer becomes better than the lower one, it is selected), then you can use the
following values of C/(I+N):
BLER
1% 2% 5% 10 %
1 1.4 1 0.8 0.5
2 4.7 4.3 3.9 3.7
3 7.9 7.8 7.2 6.9
Bearer
4 10.3 9.9 9.6 9.1

5 14.7 14.2 13.9 13.6
6 18.9 18.5 17.8 17.3
7 18.7 18.3 17.7 17.2
8 20.2 19.9 19.3 18.7
9 23.8 23.7 23.2 22.5
Calculating Bearer Selection Thresholds From Receiver Sensitivity Values
You can convert the receiver sensitivity values, from the specifications of your equipment, into bearer selection thresholds
using the following conversion method:
SF N Used
CNR = RS + 114 NF 10 Log ------------------------------
N Total

Atoll User Manual
Where RS is the receiver sensitivity in dBm, NF is the noise figure of the receiver in dB, SF is the sampling frequency in
MHz, N Used is the number of subcarriers corresponding to the number of used resource blocks, and N Total is the number
of subcarriers corresponding to the total number of resource blocks.
In the above explanation, the term receiver refers to the base station in uplink and to the mobile/user equipment in the
downlink.
Relation Between Bearer Efficiency And Spectral Efficiency
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 0.62.
Figure 0.62: Symbol
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:
SE = ( 1 BLER ) r Log 2 ( M ) bps Hz
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 symbol in LTE is
1
F = 15 kHz , from which we can calculate the useful symbol duration as well: T U = ------- = 66.67 sec . In one
F
second, there can be 1 sec 66.67 sec = 15000 symbol durations. If 15000 symbols are transmitted using QPSK1/2,
this gives us a data rate of 15000 Symbols/sec 1 bits/Symbol = 15000 bps , which is the data rate achievable using
one subcarrier of 15 kHz. We can find the spectral efficiency by normalizing the data rate to unit bandwidth. This gives:
15000 bps/subcarrier 15 kHz/subcarrier = 1 bps/Hz
In order to compare similar 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.
Displaying Coverage by Bearer Names
In addition to calculating and displaying coverage predictions by LTE bearers, i.e., bearer indexes, as explained in "Making
a Coverage by Best Bearer" on page 43, you can also calculate and display coverage predictions by bearer names.
To create a coverage prediction by bearer name:
Create a coverage prediction by best LTE bearer as explained in "Making a Coverage by Best Bearer" on page 43,
except for the following differences:
- Click the Display tab (see Figure 0.63).
- Edit the Legend column of the display thresholds and enter the bearer names instead of the bearer indexes.

Figure 0.63: Coverage by Best Bearer Display tab
You can also save these modified coverage predictions as templates so that you do not have to modify the display options
every time you want to create a similar coverage prediction.
0.6 Glossary of LTE Terms

Understanding the following terms and there use in Atoll is very helpful in understanding the LTE module:
User: A general term that can also designate a subscriber, mobile, and receiver.
Subscriber: Users with fixed geographical coordinates.
Mobile: Users generated and distributed during simulations. These users have, among other parameters, defined
services, terminal types, and mobility types assigned for the duration of the simulations.
Receiver: A probe mobile, with the minimum required parameters needed for the calculation of path loss, used
for propagation loss and raster coverage predictions.
Bearer: A Modulation and Coding Scheme (MCS) used to carry data over the channel.
Peak RLC Throughput: The maximum RLC layer throughput (user or channel) that can be achieved at a given
location using the highest LTE bearer. This throughput is the raw data rate without considering the effects of
retransmission due to errors and higher layer coding and encryption.
Effective RLC Throughput: The net RLC layer throughput (user or channel) that can be achieved at a given loca-
tion using the highest LTE bearer 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 LTE bearer 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 RLC, effective RLC or application level throughputs achieved at a given location
using the highest LTE bearer with the entire channel resources.
User Throughputs: Peak RLC, effective RLC or application level throughputs achieved at a given location using
the highest LTE bearer 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 the measurement of uplink interference with respect to the uplink noise.
I UL + N UL
NR UL = ------------------------
-
N UL
Resources: In Atoll, the term "resource" is used to refer to the average number of resource units, which is
expressed in % (as traffic loads, when the average is performed over a considerably long duration) of the total
number of resource units in a superframe of 1 sec.

Atoll User Manual

Atoll LTE Planning PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Atoll LTE Planning PDF

Hochgeladen von

Copyright:

Verfügbare Formate

CHAPTER 0

0.1 Designing an LTE Network

1. Open an existing radio-planning document or create a new one ( 1 ).

2. Configure the network by adding network elements and changing parameters ( 2 ).

- "Creating or Modifying a Site" on page 8.

3. Carry out basic coverage predictions ( 3 ).

Forsk 2008 Unauthorized reproduction or distribution of this document is prohibited 3

Figure 0.1: Planning an LTE network - workflow

0.2 Planning and Optimising LTE Base Stations

0.2.1 Creating an LTE Base Station

4 Unauthorized reproduction or distribution of this document is prohibited Forsk 2008

0.2.1.1 Definition of a Base Station

0.2.1.1.1 Site Description

Figure 0.2: New Site dialogue

0.2.1.1.2 Transmitter Description

Forsk 2008 Unauthorized reproduction or distribution of this document is prohibited 5

Figure 0.3: Transmitter dialogue - Transmitter tab

6 Unauthorized reproduction or distribution of this document is prohibited Forsk 2008

Figure 0.4: The Equipment Specifications dialogue

0.2.1.1.3 Cell Description

Forsk 2008 Unauthorized reproduction or distribution of this document is prohibited 7

0.2.1.2 Creating or Modifying a Base Station Element

0.2.1.2.1 Creating or Modifying a Site

8 Unauthorized reproduction or distribution of this document is prohibited Forsk 2008

3. Modify the parameters described in "Site Description" on page 5.

0.2.1.2.2 Creating or Modifying a Transmitter

0.2.1.2.3 Creating or Modifying a Cell

0.2.1.3 Placing a New Base Station Using a Station Template

1. In the Radio toolbar, select a template from the list.

Forsk 2008 Unauthorized reproduction or distribution of this document is prohibited 9

2. Click the New Transmitter or Station button ( ) in the Radio toolbar.

4. Click to place the station.

Placing a Station on an Existing Site

3. Click the New Transmitter or Station button ( ) in the Radio toolbar.

0.2.1.4 Managing Station Templates

Figure 0.5: The Radio toolbar

10 Unauthorized reproduction or distribution of this document is prohibited Forsk 2008

0.2.1.4.1 Creating or Modifying a Station Template

Figure 0.6: Station Template Properties dialogue General tab

Forsk 2008 Unauthorized reproduction or distribution of this document is prohibited 11

Figure 0.7: Station Template Properties dialogue Transmitter tab

Figure 0.8: Station Template Properties dialogue LTE tab

0.2.1.4.2 Modifying a Field in a Station Template

12 Unauthorized reproduction or distribution of this document is prohibited Forsk 2008

0.2.1.4.3 Deleting a Station Template

0.2.1.5 Creating Duplicates of an Existing Station

6. Click to place the duplicate station.

Forsk 2008 Unauthorized reproduction or distribution of this document is prohibited 13

0.2.2 Creating a Group of Base Stations

You can import base station data in the following ways:

0.2.3 Modifying Sites and Transmitters Directly on the Map

0.2.4 Display Hints for Base Stations

14 Unauthorized reproduction or distribution of this document is prohibited Forsk 2008

0.2.5 Creating a Multi-Band LTE Network

0.2.6 Setting the Working Area of an Atoll Document

For information on filtering, see "Filtering Data" on page 76.

Setting a computation zone

0.2.7 Studying a Single Base Station

Forsk 2008 Unauthorized reproduction or distribution of this document is prohibited 15

0.2.7.1 Making a Point Analysis to Study the Profile

- The received signal strength of the selected transmitter

- Transmitter: Select the transmitter from the list.

16 Unauthorized reproduction or distribution of this document is prohibited Forsk 2008