ATOLL User - Manual-801-1190
ATOLL User - Manual-801-1190
- Coverage: The amount of reference cell’s coverage area that the neighbour overlaps, in percentage and in
square kilometres or miles.
8. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atoll’s table
shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data
Tables" on page 50.
9. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neigh-
bours are listed in the Intra-technology Neighbours tab of each cell’s Properties dialogue.
Notes:
• A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already
exists and the Delete existing neighbours check box is cleared when you start the new allo-
cation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint
on the forbidden neighbour will be ignored because the neighbour already exists.
• When the options Force exceptional pairs and Force symmetry are selected, Atoll con-
siders the constraints between exceptional pairs in both directions in order to respect sym-
metry. On the other hand, if the neighbour relation is forced in one direction and forbidden in
the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the
Event Viewer.
• You can save automatic neighbour allocation parameters in a user configuration. For informa-
tion on saving automatic neighbour allocation parameters in a user configuration, see
"Exporting a User Configuration" on page 75.
When you create a new base station, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of
the new base station and other cells whose coverage area intersects the coverage area of the cells of the new base station.
To allocate neighbours to a new base station:
1. On the Data tab of the Explorer window, group the transmitters by site, as explained in "Grouping Data Objects"
on page 65.
2. In the Transmitters folder, right-click the new base station. The context menu appears.
3. Select Cells > Global > Neighbours > Automatic Allocation from the context menu. The Automatic Neigh-
bour Allocation dialogue appears.
4. Define the automatic neighbour allocation parameters as described in "Allocating Frequencies Automatically" on
page 795.
When you add a new transmitter, you can let Atoll allocate neighbours to it automatically. Atoll considers the cells of the
new transmitters and other cells whose coverage area intersects the coverage area of the cells of the new transmitter.
To allocate neighbours to a new transmitter:
1. Click the Data tab of the Explorer window.
2. In the Transmitters folder, right-click the new transmitter. The context menu appears.
3. Select Allocate Neighbours from the context menu. The Automatic Neighbour Allocation dialogue appears.
4. Define the automatic neighbour allocation parameters as described in "Allocating Neighbours Automatically" on
page 798.
1. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
2. Select Display Options from the context menu. The Visual Management dialogue appears.
3. Under Intra-technology Neighbours, select the Display Links check box.
4. Click the Browse button ( ) beside the Display Links check box.
5. The Intra-technology Neighbour Display dialogue appears.
6. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a cell with a
unique colour.
- Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you
want Atoll to colour the cell’s neighbour links according to a value from the Intra-technology Neighbours
table, or according to the neighbour carrier. In this case, you can view on the map intra-carrier and inter-carrier
neighbour relations.
- Value Intervals: Select "Value Intervals" to colour the cell’s neighbour links according the value interval of the
value selected from the Field list. For example, you can choose to display a cell’s neighbours according to
their rank, in terms of automatic allocation, or according to the importance, as determined by the weighting
factors.
Tip: You can display the number of handoff attempts for each cell-neighbour pair first creating
a new field of Type "Integer" in the Intra-Technology Neighbour table for the number of
handoff attempts. Once you have imported or entered the values in the new column, you
can select this field from the Field list along with "Value Intervals" as the Display Type.
For information on adding a new field to a table, see "Adding a Field to an Object Type’s
Data Table" on page 51.
Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you
can display or hide neighbour link display types individually.
For information on changing display properties, see "Display Properties of Objects" on page 33.
7. Select the Add to Legend check box to add the displayed neighbour links to the legend.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each neighbour link.
9. Click OK to save your settings.
10. Under Advanced, select which neighbour links to display:
- Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations
where the selected cell is the reference cell and where the neighbour relation is not symmetric.
- Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations
where the selected cell is neighbour and where the neighbour relation is not symmetric.
- Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the
selected cell and the neighbour.
11. Click OK to save your settings.
12. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
- The symmetric neighbour relations of the selected (reference) cell are indicated by a line.
- The outward neighbour relations are indicated with a line with an arrow pointing at the neighbour (e.g. see
Site1_2(0)) in Figure 12.57.).
- The inward neighbour relations are indicated with a line with an arrow pointing at the selected cell (e.g. see
Site9_3(0)) in Figure 12.57.).
In Figure 12.57, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward
neighbour links are coloured as the corresponding neighbour transmitters and the inward neighbour link is
coloured as the reference transmitter as it is neighbour of Site9_3(0) here.
In Figure 12.58, neighbour links are displayed according to the neighbour carrier. You can view intra-carrier and
inter-carrier neighbour links. Here, all neighbour relations are symmetric.
Note: You can display either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting
either Forced Neighbours or Forbidden Neighbours.
2. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
3. Select Display Options from the context menu. The Neighbour Display dialogue appears.
4. Under Intra-technology Neighbours, select the Display Coverage Areas check box.
5. Click the Browse button ( ) beside the Display Coverage Areas check box.
6. The Intra-technology Neighbour Display dialogue appears.
7. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage area of a cell’s 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 cell’s neighbours according to a value from the Intra-technology
Neighbours table.
- Value Intervals: Select "Value Intervals" to colour the coverage area of a cell’s neighbours according the
value interval of the value selected from the Field list. For example, you can choose to display a cell’s neigh-
bours according to their rank, in terms of automatic allocation, or according to the importance, as determined
by the weighting factors.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each coverage area.
9. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( ) in the
Radio toolbar.
Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete TD-SCDMA neighbours using the Cells tab of the transmitter’s 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 transmitter’s Properties dialogue appears.
3. Click the Cells tab. On the Cells tab, there is a column for each cell.
4. Click the Browse button ( ) beside Neighbours in the cell for which you want to allocate or delete neighbours.
The cell’s Properties dialogue appears.
5. Click the Intra-technology Neighbours tab.
6. If desired, you can enter the maximum number of neighbours in the following boxes:
- Max Number Inter-Carrier
- Max Number Intra-Carrier
To allocate or delete TD-SCDMA neighbours using the Cells tab of the Transmitter Properties dialogue:
1. Select the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appear.
3. Select Cells > Global > Neighbours > Intra-technology Neighbours from the context menu. The Neighbours
table appears.
Note: For information on working with data tables, see "Working with Data Tables" on page 50.
4. To allocate a neighbour:
a. In the row marked with the new row icon ( ), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column.
c. Click another cell of the table to create the new neighbour and add a new blank row to the table.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
Note: You can add or delete either some forced neighbours or some forbidden neighbours using
the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table,
select the exceptional pairs to be considered, right-click the table and select Force
Exceptional Pairs in the context menu.
You can allocate or delete intra-technology neighbours directly on the map using the mouse.
To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neigh-
bours on the map as explained in "Displaying Frequency Allocation on the Map" on page 796.
To add a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters
to the intra-technology neighbours list.
To remove a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both trans-
mitters from the intra-technology neighbours.
To add an outward neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference
transmitter to the intra-technology neighbour list of the reference transmitter.
To remove an outward neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter you want to remove from the list of neighbours. Atoll removes the reference
transmitter from the intra-technology neighbours list of the reference transmitter.
To add an inward neighbour relation:
• Click the reference transmitter on the map. Atoll displays its neighbour relations.
- If the two transmitters already have a symmetric neighbour relation, press CTRL and click the other trans-
mitter. Atoll converts the symmetric relation to an inward non-symmetric inter-technology neighbour relation.
- If there is no existing neighbour relation between the two transmitters, first create a symmetric neighbour rela-
tion by pressing SHIFT and clicking the transmitter with which you want to create a symmetric relation. Then
press CTRL and click the other transmitter. Atoll converts the symmetric relation to an inwards non-symmetric
inter-technology neighbour relation.
To remove an inwards neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes the trans-
mitter from the intra-technology neighbours list of the reference transmitter.
Notes:
• When there is more than one cell on the transmitter, clicking the transmitter in the map window
opens a context menu allowing you to select the cell you want (see "Selecting One of Several
Transmitters or Microwave Links" on page 30).
• You can add or delete either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting either
Forced Neighbours or Forbidden Neighbours.
- Full Lists (default max number = Y): x⁄X; x number of cells out of a total of X have Y number of neighbours
listed in their respective neighbours lists.
Syntax: |CELL| |NUMBER| |MAX NUMBER|
- Lists > max number (default max number = Y): x⁄X; x number of cells out of a total of X have more than Y
number of neighbours listed in their respective neighbours lists.
Syntax: |CELL| |NUMBER| |MAX NUMBER|
Note: If the field Maximum number of neighbours in the Cells table is empty, the above two
checks take into account the Default Max Number value defined in the audit dialogue.
- Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Non symmetric links: X; total number of non-symmetric neighbour links in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
- Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
Note: Within the context of scrambling code allocation, "neighbours" refer to intra-carrier
neighbours.
You can convert a hexadecimal value to a decimal value with the following equation, where X, Y, and Z are decimal values
within the hexadecimal index ranges:
2
X × 16 + Y × 16 + Z
For example, the hexadecimal value "3Fh" would be calculated as shown below:
2
0 × 16 + 3 × 16 + 15 = 63
4. In the row marked with the New Row icon ( ), enter a Name for the new domain.
5. Click another cell of the table to create the new domain and add a new blank row to the table.
6. Double-click the domain to which you want to add a group. The domain’s Properties dialogue appears.
7. Under Groups, enter the following information for each group you want to create.
- Name: Enter a name for the new scrambling code group.
- Min.: Enter the lowest available scrambling code in this group’s range. The minimum and maximum scram-
bling codes must be entered in the format, decimal or hexadecimal, set for the Atoll document. For information
on setting the scrambling code format, see "Defining the Scrambling Code Format" on page 808.
- Max: Enter the highest available scrambling code in this group’s range.
- Step: Enter the separation interval between each scrambling code.
- Excluded: Enter the scrambling codes within the range defined by the Min. and Max fields that you do not
want to use.
- Extra: Enter any additional scrambling codes (i.e., outside the range defined by the Min. and Max fields) you
want to add to this group. You can enter a list of codes separated by either a comma, semi-colon, or a space.
You can also enter a range of scrambling codes separated by a hyphen. For example, entering, "1, 2, 3–6"
means that the extra scrambling codes are "1, 2, 3, 4, 5, 6".
8. Click another cell of the table to create the new group and add a new blank row to the table.
4. In the row marked with the New Row icon ( ), select one cell of the new exceptional pair in the Cell column
and the second cell of the new exceptional pair from the Cell_2 column.
5. Click another cell of the table to create the new exceptional pair and add a new blank row to the table.
You can define the costs of the different types of constraints used in the automatic scrambling code allocation algorithm.
To define the different constraint costs:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Global > Scrambling Codes > Constraint Costs. The Allocation Constraint Costs dialogue
appears. In this dialogue you can define the following costs of constraint violations for the automatic allocation
process (the cost is a value from 0 and 1):
- Max 1st, 2nd, and 3rd Order Neighbours: Enter the maximum costs for 1st, 2nd, and 3rd order neighbour
constraint violations.
- Max Cluster Share: Enter the maximum cost for the case where 1st or 2nd order neighbours have the same
cluster assigned when the Distributed per Site strategy is used.
- Co-planning Share: Enter the cost for inter-technology neighbour constraint violations.
- Max Reuse Distance: Enter the maximum cost for reuse distance constraint violations.
- Exceptional Pair: Enter the cost for exceptional pair constraint violations.
4. Click OK. The allocation constraint costs are stored and will be used in the automatic allocation.
The allocation algorithm enables you to automatically allocate scrambling code to cells in the current network. You can
choose among several automatic allocation strategies (for more information, see the Technical Reference Guide):
• Clustered: The purpose of this strategy is to choose for a group of mutually constrained cells, scrambling codes
among a minimum number of clusters. In this case, Atoll will preferentially allocate all the codes from same
cluster.
• Distributed per Cell: This strategy consists in using as many clusters as possible. Atoll will preferentially allocate
codes from different clusters.
• One SYNC_DL Code per Site: This strategy allocates one SYNC_DL code to each base station, then, one code
of the cluster associated with the SYNC_DL code to each cell of each base station. When all the SYNC_DL codes
have been allocated and there are still base stations remaining to be allocated, Atoll reuses the SYNC_DL codes
at another base station. Select this strategy if you want to allocate the same scrambling code to the master and
the slave carriers. For more information on master and slave carriers, see "Planning Frequencies" on page 795.
• Distributed per Site: This strategy allocates a group of adjacent clusters to each base station in the network, then,
one cluster to each transmitter of the base station, according to its azimuth, and finally one code of the cluster to
each cell of each transmitter. The number of adjacent clusters per group depends on the number of transmitters
per base station you have in your network; this information is required to start allocation based on this strategy.
When all the groups of adjacent clusters have been allocated and there are still base stations remaining to be allo-
cated, Atoll reuses the groups of adjacent clusters at another base station.
To automatically allocate scrambling codes:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Global > Scrambling Codes > Automatic Allocation. The Scrambling Codes and SYNC_DL
Codes dialogue appears.
4. Set the following parameters in the Scrambling Codes and SYNC_DL Codes dialogue:
- Under Constraints, you can set the constraints on automatic scrambling code allocation.
- Existing Neighbours: Select the Existing Neighbours check box if you want to consider neighbour re-
lations and then choose the neighbourhood level to take into account:
Neighbours of a cell are referred to as first order neighbours, neighbours’ neighbours are referred to as
second order neighbours and neighbours’ neighbours’ neighbours as third order neighbours.
First Order: No cell will be allocated the same scrambling code as its neighbours.
Second Order: No cell will be allocated the same scrambling code as its neighbours or its second order
neighbours.
Third Order: No cell will be allocated the same scrambling code as its neighbours or its second order
neighbours or its third order neighbours.
Atoll can only consider neighbour relations if neighbours have already been allocated. For information on
allocating neighbours, see "Planning Neighbours" on page 797.
Note: Atoll can take into account inter-technology neighbour relations as constraints to allocate
different scrambling codes to the TD-SCDMA neighbours of a GSM transmitter. In order
to consider inter-technology neighbour relations in scrambling code allocation, you must
make the Transmitters folder of the GSM Atoll document accessible in the TD-SCDMA
Atoll document. For information on making links between GSM and TD-SCDMA Atoll
documents, see "Creating a UMTS Sector From a GSM Sector" on page 226.
- Reuse Distance: Select the Reuse Distance check box, if you want to the automatic allocation process
to consider the reuse distance constraint. Enter the Default reuse distance within which two cells on the
same carrier cannot have the same scrambling code.
Note: A reuse distance can be defined at the cell level (in the cell Properties dialogue or in the
Cells table). If defined, a cell-specific reuse distance will be used instead of the value
entered here.
- Exceptional Pairs: Select the Exceptional Pairs check box if you want to the automatic allocation proc-
ess to consider the exceptional pair constraints.
- Under Strategy, you can select an automatic allocation strategy:
- Clustered
- Distributed per Cell
- One SYNC_DL Code per Site
- Distributed per Site
- Carrier: Select the carrier on which you want to run the allocation. You may choose one carrier (Atoll will
assign scrambling codes to transmitters using the selected carrier) or all of them.
- No. of Codes per SYNC_DL: According to 3GPP specifications, the number of scrambling codes per
SYNC_DL is 4. If you want, you can change the number of codes per SYNC_DL.
- Use a Max of Codes: Select the Use a Max of Codes check box to make Atoll use the maximum number of
codes. For example, if there are two cells using the same domain with two scrambling codes, Atoll will assign
the remaining code to the second cell even if there are no constraints between these two cells (for example,
neighbour relations, reuse distance, etc.). If you do not select this option, Atoll only checks the constraints,
and allocates the first ranked code in the list.
- Delete Existing Codes: Select the Delete Existing Codes check box if you want Atoll to delete currently
allocated scrambling codes and recalculate all scrambling codes. If you do not select this option, Atoll keeps
the currently allocated scrambling codes and only allocates scrambling codes to cells that do not yet have
codes allocated.
5. Click Run. Atoll begins the process of allocating scrambling codes.
If you have selected the Distributed per Site allocation strategy, a Distributed per Site Allocation Parameters
dialogue appears.
a. In the Distributed per Site Allocation Parameters dialogue, enter the Max Number of Transmitters per
Site.
b. Select the Neighbours in Other SYNC_DL or Secondary Neighbours in Other SYNC_DL check boxes in
the Additional Constraints section, if you want the automatic allocation to consider constraints related to first
order and second order neighbours.
c. Click OK.
Once Atoll has finished allocating scrambling codes, the codes are visible under Results. Atoll only displays
newly allocated scrambling codes.
Note: Atoll allocates the same scrambling code to each carrier of a transmitter.
6. Click Commit. The scrambling codes are stored in the cell properties.
Note: You can save automatic scrambling code allocation parameters in a user configuration.
For information on saving automatic scrambling code allocation parameters in a user
configuration, see "Exporting a User Configuration" on page 75.
Tips:
• If you need to allocate scrambling codes to the cells on a single transmitter, you can allocate
them automatically by selecting Allocate Scrambling Codes from the transmitter’s context
menu.
• If you need to allocate scrambling codes to all the cells in a group of transmitters, you can allo-
cate them automatically by selecting Cells > Global > Scrambling Codes > Automatic Allo-
cation from the transmitter group’s context menu.
When you allocate scrambling codes to a large number of cells, it is easiest to let Atoll allocate scrambling codes auto-
matically, as described in "Automatically Allocating Scrambling Codes to TD-SCDMA Cells" on page 810. However, if you
want to add a scrambling code to one cell or to modify the scrambling code of a cell, you can do it by accessing the prop-
erties of the cell.
After allocation, you can use the audit tool to check the reuse scrambling code distances between cells and the compati-
bility of the domains of the cells for each base station.
To allocate a scrambling code to a TD-SCDMA cell manually:
1. On the map, right-click the transmitter to whose cell you want to allocate a scrambling code. The context menu
appears.
2. Select Properties from the context menu. The transmitter’s Properties dialogue appears.
3. Select the Cells tab.
4. Enter a Scrambling Code in the cell’s column.
5. Click OK.
In Atoll, you can search for scrambling codes and scrambling code groups using the Search Tool. Results are displayed
in the map window in red.
If you have already calculated and displayed a coverage prediction by transmitter based on the best server P-CCPCH,
with the results displayed by transmitter, the search results will be displayed by transmitter coverage. Scrambling codes
and scrambling code groups and any potential problems will then be clearly visible.
To find scrambling codes or scrambling code groups using the Search Tool:
1. Create, calculate, and display a coverage prediction by P-CCPCH best server. For information, see "Making a
Coverage Prediction by P-CCPCH Best Server" on page 761.
2. Click View > Search Tool. The Search Tool window appears.
3. You can search either for a specific scrambling code or for a scrambling code group:
To search for a scrambling code:
You can use the display characteristics of transmitters to display scrambling code-related information.
To display scrambling code-related information on the map:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Display tab.
You can display the following information per transmitter:
- Scrambling code: Select "Discrete values" as the Display Type and "Cells: Scrambling Code" as the Field.
- Ranges of scrambling codes: Select "Value intervals" as the Display Type and "Cells: Scrambling Code"
as the Field.
- Scrambling code domain: Select "Discrete values" as the Display Type and "Cells: Scrambling Code
Domain" as the Field.
You can display the following information in the transmitter label or tooltip:
- Scrambling code: Select "Cells: Scrambling Code" from the Label or Tip Text Field Definition dialogue.
- Scrambling code domain: Select "Cells: Scrambling Code Domain" from the Label or Tip Text Field Defi-
nition dialogue.
5. Click OK.
For information on display options, see "Display Properties of Objects" on page 33.
You can group transmitters on the Data tab of the Explorer window by their scrambling code or scrambling code domain.
To group transmitters by scrambling code:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the General tab, click Group by. The Group dialogue appears.
5. Under Available Fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
- Scrambling Code Domain
- Scrambling Code
7. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to
the list of parameters on which the transmitters will be grouped.
8. If you do not want the transmitters to be sorted by a certain parameter, select it in the Group these fields in this
order list and click . The selected parameter is removed from the list of parameters on which the transmitters
will be grouped.
9. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters
to be grouped:
10. Click OK to save your changes and close the Group dialogue.
Note: If a transmitter has more than one cell, Atoll cannot arrange the transmitter by cell.
Transmitters that cannot be grouped by cell are arranged in a separate folder under the
Transmitters folder.
You can use a histogram to analyse the use of allocated scrambling codes in a network. The histogram represents the
scrambling codes or SYNC_DLs as a function of the frequency of their use.
To display the scrambling code histogram:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Global > Scrambling Codes > Code Distribution. The Distribution Histograms dialogue
appears.
Each bar represents a scrambling code or a SYNC_DL code, its height depending on the frequency of its use.
4. Select Scrambling Codes to display scrambling code use and Clusters to display SYNC_DL code use.
5. Move the pointer over the histogram to display the frequency of use of each scrambling code or SYNC_DL. The
results are highlighted simultaneously in the Detailed Results list.
You can make a scrambling code interference zones coverage prediction to view areas covered by cells using the same
scrambling code. The coverage prediction displays areas where transmitters other than the best server, whose received
signal level is within the Pollution Margin set in the coverage prediction properties, interfere the best server signal. The
interfered pixels are coloured according to the interfered scrambling code.
To make a scrambling code interference zone coverage prediction:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Scrambling Code Interference Zones and click OK. The prediction Properties dialogue appears.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 12.59). The coverage prediction parameters on the Conditions tab allow you
to define the signals that will be considered for each pixel. You can set:
- Terminal: The terminal to be considered in the coverage prediction. The gain and losses defined in the ter-
minal properties are used.
- Service: The R99 or HSDPA service to be considered in the coverage prediction. The body loss defined in
the service properties is used.
- Mobility: The mobility type to be considered in the coverage prediction. The P-CCPCH RSCP threshold
defined in the mobility properties is used as the minimum requirement for the coverage prediction.
- Carrier: You can select the carrier to be studied, or select "All" to have all carriers taken into account.
For each pixel, the serving base station is determined according to the P-CCPCH RSCP from the carrier with
the highest P-CCPCH power, or from the master carrier in case of N-frequency mode compatible transmitters.
Afterwards, the coverage prediction is calculated for the selected carrier. If the selected carrier does not exist
in a transmitter, there will not be any pixels covered by this transmitter. If you select "All," Atoll will display the
coverage prediction for the preferred carrier of the selected service. If no preferred carrier is defined in the
service properties, Atoll will display the coverage prediction for the carrier with the highest P-CCPCH power,
or the master carrier in case of N-frequency mode compatible transmitters.
- Timeslot: The scrambling code interference coverage prediction is performed for TS0.
- If you select the Shadowing taken into account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- Pollution Margin: The margin for determining which signals to consider. Atoll considers signal levels which
are within the defined margin of the best signal level.
Figure 12.59: Condition settings for a scrambling code interference zones coverage prediction
9. Click the Calculate button ( ) in the Radio toolbar to calculate the scrambling code interference zone coverage
prediction. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 12.60).
Figure 12.60: Condition settings for a scrambling code interference zones coverage prediction
A specific colour is assigned to areas where more than one scrambling code has interference. You can analyse these
areas in more detail using the Search Tool. For more information on using the Search Tool for scrambling code interfer-
ence analysis, see "Using the Search Tool to Display Scrambling Code Allocation" on page 813.
UUDDDD 32 64
UUUDDD 48 48
UUUUDD 64 32
UUUUUD 80 16
UpUDDDD 16 64
UpUUDDD 32 48
Assuming ideal dynamic channel allocation (DCA), all the resource units within a subframe, i.e., 6 x 16 = 96, can be allo-
cated and used. TS0 is not used for traffic. TS1 is not used for traffic either in case of UpPCH shifting. The total resource
units in a network, i.e., the network capacity, is given by:
Network Capacity = Number of Timeslots per Subframe × Number of Codes per Timeslot × Number of Carriers
Resource units from different carriers can be shared and allocated to the same mobile connected to an N-frequency mode
compatible transmitter.
This section explains the network capacity and network dimensioning analysis tools:
• "Calculating Available Network Capacity" on page 816.
• "Calculating Required Network Capacity" on page 818.
The uplink and downlink Resource Units Overhead defined for each timeslot per cell is considered when calculat-
ing the number of available resource units.
You can create a coverage prediction by P-CCPCH best server in order to display the available network capacity, i.e., the
number of available resource units in uplink or downlink.
To display the available cell and network capacity on the map:
1. Create a coverage by P-CCPCH best server, as explained in "Making a Coverage Prediction by P-CCPCH Best
Server" on page 761, with the following display parameters:
- In step 7., set the Display Type "Value intervals" based on the Field "Available DL Resource Units" or "Avail-
able DL Resource Units" according to what you would like to display. Each coverage zone will then be dis-
played according to the number of available resource units for the carrier used for the coverage prediction.
Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 12.62).
- Global Scaling Factor: If desired, enter a scaling factor to increase user density.
The global scaling factor enables you to increase user density without changing traffic parameters or traffic
maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of users
(for environment and user profile traffic maps) or the rates per users (for live traffic maps per sector).
- Select Traffic Maps to be Used: Select the traffic maps you want to use for dimensioning.
- Under Coverage, select the P-CCPCH best server Coverage to be used to distribute the traffic among
the cells of the network.
4. Click Calculate. Atoll distributes the traffic among cells using the information from traffic maps and the coverage
prediction, calculates the capacity of each cell, and displays the results in the Results per Cell tab.
The Results per Cell tab has five columns which list the names of the cells in the network, and the numbers of
uplink and downlink resource units available and required per cell. The last row in this dialogue displays the total
uplink and downlink resource units, required and available. Cells for which the required resource units exceed the
available units are displayed in red.
The uplink and downlink resource units overhead defined for each timeslot per cell is considered when calculating
the number of available resource units.
5. Click Commit to store the number of required resource units per cell in the Cells table.
6. Click Close to close the dialogue.
Changing transmitter parameters does not affect the dimensioning results if you have not updated the coverage by
P-CCPCH best server used for the dimensioning calculations. If you want to compare dimensioning results after modifying
some transmitter parameters, you will have to (re)calculate a coverage by P-CCPCH best server, and run the dimensioning
calculations based on the new coverage prediction.
You can create a coverage by P-CCPCH best server in order to display the required network capacity, i.e., the number of
required resource units in uplink or downlink, of your TD-SCDMA network on the map. The number of required resource
units is an output of network dimensioning stored in the Cells table. For more information, see "Calculating Required
Network Capacity" on page 818.
To display the required cell and network capacity on the map:
1. Create a coverage by P-CCPCH best server, as explained in "Making a Coverage Prediction by P-CCPCH Best
Server" on page 761, with the following display parameters:
- In step 7., set the Display Type "Value intervals" based on the Field "Cells: Required DL Resource Units" or
"Cells: Required UL Resource Units" according to what you would like to display. Each coverage zone will then
be displayed according to the number of required resource units for the cell (carrier used for the coverage pre-
diction).
Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 12.64).
You can create a coverage by P-CCPCH best server in order to display the usage of resource units, i.e., the percentage
of available resource units which are effectively used by the traffic in uplink or downlink, of your TD-SCDMA network on
the map.
To display the usage of resource units on the map:
1. Create a coverage by P-CCPCH best server, as explained in "Making a Coverage Prediction by P-CCPCH Best
Server" on page 761, with the following display parameters:
- In step 7., set the Display Type "Value intervals" based on the Field "Required DL Resource Units (%)" or
"Required UL Resource Units (%)" according to what you would like to display. Each coverage zone will then
be displayed according to the percentage of available resource units that are used in each cell (carrier used
for the coverage prediction).
Once Atoll has finished calculating the prediction, the results are displayed in the map window (see Figure 12.66).
• Traffic map per user profile can be used if you have marketing-based traffic data.
Traffic maps per density of user profiles, where each vector (polygon, line or point) describes subscriber densities
(or numbers of subscribers for points) with user profiles and mobility types, and traffic maps per environment of
user profiles, where each pixel has an assigned environment class. For more information, see "Importing a Traffic
Map Based on Densities of User Profiles" on page 824, "Importing a Traffic Map Based on Environments of User
Profiles" on page 825 and "Creating a Traffic Map Based on Environments of User Profiles" on page 825.
• Traffic maps per density (number of users per km2) can be used if you have population-based traffic data,
or 2G network statistics.
Each pixel has an actual user density assigned. For more information, see "Importing a Traffic Map per User
Density" on page 826, "Creating a Traffic Map per User Density" on page 827, see "Converting 2G Network Traf-
fic" on page 828 and "Exporting Cumulated Traffic" on page 828.
Note: You can also import a traffic map from a file by clicking the Import button. You can import
AGD (Atoll Geographic Data) format files that you have exported from another Atoll
document.
7. Select a coverage prediction by P-CCPCH best server from the list of available coverage predictions.
8. Enter the data required in the Map per Sector dialogue:
- If you have selected Throughputs in Uplink and Downlink, enter the throughput demands in the uplink and
downlink for each sector and for each listed service.
- If you have selected Number of Users per Activity Status, enter the number of inactive users, the number
of users active in the uplink, in the downlink and in the uplink and downlink, for each sector and for each
service.
Note: You can also import a text file containing the data by clicking the Actions button and
selecting Import Table from the menu. For more information on importing table data, see
"Importing Tables from Text Files" on page 59.
11. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must
equal 100.
12. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must
equal 100.
13. Under Clutter Distribution, for each clutter class, enter:
- A weight to spread the traffic over the vector.
- The percentage of indoor users. An additional loss will be counted for indoor users during Monte Carlo simu-
lations.
14. Click OK. Atoll creates the traffic map in the Traffic folder.
You can update the information, throughput demands, and the number of users, on the map afterwards. You can update
Live traffic per sector maps if you add or remove a base station. You must first recalculate the coverage prediction by P-
CCPCH best server. For more information, see "Making a Coverage Prediction by P-CCPCH Best Server" on page 761.
Once you have recalculated the coverage prediction, you can update the traffic map.
To update the traffic map:
1. Click the Geo tab of the Explorer window.
2. Click the Expand button ( ) to expand the Traffic folder.
3. Right-click the sector traffic map that you want to update. The context menu appears.
4. Select Update from the context menu. The Map per Sector dialogue appears.
Select the updated coverage prediction by P-CCPCH best server and define traffic values for the new transmit-
ter(s) listed at the bottom of the table. Deleted or deactivated transmitters are automatically removed from the
table.
You can model variations in user behaviour by creating different profiles for different times of the day or for different circum-
stances. For example, a user may be considered a business user during the day, with video conferencing and voice, but
no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and
web browsing.
To create or modify a user profile:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.
3. Right-click the User Profiles folder. The context menu appears.
4. Select New from the context menu. The User Profiles New Element Properties dialogue appears.
Note: You can modify the properties of an existing user profile by right-clicking the user profile in
the User Profiles folder and selecting Properties from the context menu.
- Calls⁄Hour: For circuit-switched services, enter the average number of calls per hour for the service. The calls
per hour is used to calculate the activity probability. For circuit-switched services, one call lasting 1000 sec-
onds presents the same activity probability as two calls lasting 500 seconds each.
For packet-switched services, the 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 packet-switched services, however, he may not use the service continually. For ex-
ample, with a web-browsing service, a session starts when the user opens his browsing application and ends
when he quits the browsing application. Between these two events, the user may be downloading web pages
and other times he may not be using the application or he may be browsing local files, but the session is still
considered as open. A session, therefore, is defined by the volume transferred in the uplink and downlink and
not by the time.
Note: In order for all the services defined for a user profile to be taken into account during traffic
scenario elaboration, the sum of activity probabilities must be lower than 1.
- Duration: For circuit-switched services, enter the average duration of a call in seconds. For packet-switched
services, this field is left blank.
- UL Volume: For packet-switched services, enter the average uplink volume per session in kilobytes.
- DL Volume: For packet-switched services, enter the average downlink volume per session in kilobytes.
Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a
given density (i.e., the number of subscribers with the same profile per km²). To get an appropriate user distribution, you
can assign a weight to each clutter class for each environment class. You can also specify the percentage of indoor
subscribers for each clutter class. In a Monte Carlo simulation, an additional loss (as defined in the clutter class properties)
will be added to the indoor users path loss.
To create or modify a TD-SCDMA environment:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the TD-SCDMA Parameters folder.
3. Right-click the Environments folder. The context menu appears.
4. Select New from the context menu. The Environments New Element Properties dialogue appears.
Note: You can modify the properties of an existing environment by right-clicking the
environment in the Environments folder and selecting Properties from the context
menu.
7. In the row marked with the New Row icon ( ), set the following parameters for each user profile⁄mobility com-
bination that this TD-SCDMA environment will describe:
- User: Select a user profile.
- Mobility: Select a mobility type.
- Density (Subscribers⁄km2): Enter a density in terms of subscribers per square kilometre for the combination
of user profile and mobility type.
8. Click the Clutter Weighting tab.
9. For each clutter class, enter a weight that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk × Sk
N k = N Area × --------------------------
∑
Wi × Si
i
where:
For example: An area of 10 km² with a subscriber density of 100⁄km². Therefore, in this area, there are 1000
subscribers. The area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1"
and for Building is "4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter
class and 800 in the Building clutter class.
10. If you want you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simu-
lation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 825.
- User Profile: If you want to import user profile information from the file, under Defined, select "By field" and
select the source field from the Choice column. If you want to assign a user profile from the TD-SCDMA
Parameters folder of the Data tab, under Defined, select "By value" and select the user profile in the Choice
column.
- Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select
the source field from the Choice column. If you want to assign a mobility type from the TD-SCDMA Parame-
ters folder of the Data tab, under Defined, select "By value" and select the mobility type in the Choice column.
- Density: If you want to import density information from the file, under Defined, select "By field" and select the
source field from the Choice column. If you want to assign a density, under Defined, select "By value" and
enter a density in the Choice column for the combination of user profile and mobility type. In this context, the
term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kil-
ometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers
when the map consists of points.
Important: The name of the imported user profile or mobility type must match the corresponding
name in the TD-SCDMA Parameters folder of the Data tab. If the names do not match,
Atoll will display a warning and will not import the file.
12. Under Clutter Distribution, enter a weight for each class that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk × Sk
N k = N Area × --------------------------
∑
Wi × Si
i
where:
13. If you want, you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo sim-
ulation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
14. Click OK to finish importing the traffic map.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 825.
7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, BIL, IST,
BMP, PlaNET©, GRC Vertical Mapper, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic map’s properties dialogue appears.
11. Select the Description tab.
In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the
Code column.
12. For each Code, select the environment it corresponds to from the Name column.
The environments available are those available in the Environments folder, under TD-SCDMA Parameters on
the Data tab of the Explorer window. For more information, see "Modelling Environments" on page 823.
13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects"
on page 33.
6. Select the environment class from the list of available environment classes.
7. Click the Draw Polygon button ( ) to draw the polygon on the map for the selected environment class.
8. Click the Delete Polygon button ( ) and click the polygon to delete the environment class polygon on the map.
9. Click the Close button to close the Environment Map Editor toolbar and end editing.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 825.
7. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP,
PlaNET©, TIF, ISTAR, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic map’s properties dialogue appears.
11. Select the Traffic tab.
12. Select whether the users are active in the Uplink⁄Downlink, only in the Downlink, or only in the Uplink.
13. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must
equal 100.
14. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must
equal 100.
15. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal
100.
16. Under Clutter Distribution, enter for each clutter class the percentage of indoor users.
An additional loss will be counted for indoor users during the Monte Carlo simulations. You do not have to define
a clutter weighting for traffic maps per user density because the traffic is provided in terms of user density per pixel.
17. Click OK. Atoll creates the traffic map in the Traffic folder.
18. In the table, enter a traffic density value (i.e. the number of users per km2) for each contour you have drawn.
Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains
at "0" and no data will be exported.
8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic
data to be exported.
- Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal.
- Service: Select the service that will be exported, or select "Circuit services" to export traffic using any circuit
service, or select "Packet services" to export traffic using any packet service.
- Mobility: Select the mobility type that will be exported or select "All" to export all mobility types.
- Activity: Select one of the following:
- All Activity Statuses: Select All Activity Statuses to export all users without any filter by activity status.
- Uplink: Select Uplink to export mobiles active in the uplink only.
- Downlink: Select Downlink to export mobiles active in the downlink only.
- Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity.
- Inactive: Select Inactive to export only inactive mobiles.
9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the
cumulated traffic.
10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.
4. Select Save As from the context menu. The Save As dialogue appears.
5. Enter a file name and select a file format for the traffic map.
6. Click Save.
If you are exporting a raster traffic map, you have to define:
The user activity status is an important output of the random trial and has direct consequences on the next step
of the simulation and on the network interferences. A user may be either active or inactive. Both active and inactive
users consume radio resources and create interference.
Then, Atoll randomly assigns a shadowing error to each user using the probability distribution that describes the
shadowing effect.
Finally, another random trial determines user positions in their respective traffic zone (according to the clutter
weighting and the indoor ratio per clutter class).
2. Modelling dynamic channel allocation and power control: Atoll performs dynamic channel allocation and
power control for mobiles generated in the previous step. The power control simulation algorithm is described in
"The Monte Carlo Simulation Algorithm" on page 829.
As shown in Figure 12.69, the simulation algorithm is divided in two parts. All users are evaluated by the R99 part of the
algorithm. HSDPA users, unless they have been rejected during the R99 part of the algorithm, are then evaluated by the
HSDPA part of the algorithm.
The R99 part of the algorithm simulates power control, congestion and radio resource control performed for R99 bearers
for both R99 and HSDPA users. Atoll considers each user in the order in which the users are generated, and determines
his best server. Atoll then selects the cell and the timeslot to be allocated to each user as follows:
• Atoll selects the preferred carrier defined in the properties of the service being used by the user if the preferred
carrier is available on the best server and if there are enough resources available on it to accommodate the user.
Otherwise, Atoll selects the carrier according to the selected DCA strategy.
• Load: The least loaded cell or timeslot is selected.
- Cell: Atoll calculates the ISCP (Interference Signal Code Power) for all the timeslots of all the cells of the
user’s best server considering the effect of smart antenna equipment, if any. Next, Atoll selects the carrier
with the lowest ISCP and the lowest load that has enough free timeslots to support the user’s service.
- Timeslot: Atoll selects the least loaded timeslots that have enough free OVSF codes for the user’s service.
• Available RUs: The cell or timeslot with the most available resource units is selected.
- Cell: Atoll calculates the number of available resource units for all the timeslots of all the cells of the user’s
best server. Next, Atoll selects the carrier with most number of available resource units.
- Timeslot: Atoll selects the timeslots with the most available resource units.
• Direction of Arrival: The cell or timeslot selected is the one which does not have an interfering mobile located
nearby at the same angle as the direction of arrival of the targeted mobile.
- Cell: Atoll calculates the number of interfering mobiles which are located in the same direction as the targeted
user for all the timeslots of all the cells of the user’s best server. Next, Atoll selects the carrier with the lowest
number of interfering mobiles in the direction of the targeted user.
- Timeslot: Atoll selects the timeslots with the lowest number of interfering mobiles in the direction of the tar-
geted user.
• Sequential: Cells and timeslots are selected in a sequential order.
- Cell: Atoll allocates the carriers to users one by one. For example, if there are 3 carriers, Atoll allocates car-
rier 0 to user 0, carrier 1 to user 1, carrier 2 to user 2, carrier 0 to user 3, and so on.
- Timeslot: Atoll allocates timeslots to users one by one.
DCA reduces interference and maximises the usage of resource units. Resource units from different carriers can be
shared and allocated to the same mobile connected to an N-frequency mode compatible transmitter.
In TD-SCDMA networks, interference for a given timeslot can be of the following four types:
• DL – DL: Cell A and cell B both transmitting in downlink.
• UL – UL: Cell A and cell B both receiving in uplink.
• DL – UL: Cell A receiving in uplink and cell B transmitting in downlink.
• UL – DL: Cell A transmitting in downlink and cell B receiving in uplink.
Next, Atoll performs uplink and downlink power control considering the effect of smart antenna equipment, if any. Atoll
first calculates the required terminal power in order to reach the Eb⁄Nt or C⁄I threshold required by the service in the uplink,
followed by the required traffic channel power in order to reach the Eb⁄Nt or C⁄I threshold required by the service in the
downlink. Atoll updates the downlink and uplink ISCP for all the users.
After carrying out power control, Atoll updates the cell load parameters. For each cell whose transmitter has smart
antenna equipment assigned, Atoll updates the geometrical distribution of power transmitted using the smart antenna in
the downlink for each timeslot, which has to be updated for each user. Atoll also saves the geometrical distribution of
uplink loads calculated using the smart antenna in the uplink.
Atoll then carries out congestion and radio resource control, verifying the UL load, the total transmitted power, the number
of resource units, and OVSF codes consumed considering the services which require several timeslots.
At this point, the users can be either connected or rejected. They are rejected if:
• The signal quality is not sufficient:
- On the downlink, the P-CCPCH RSCP is not high enough: status is " P-CCPCH RSCP < Min. P-CCPCH
RSCP"
- On the downlink, the power required to reach the user is greater than the maximum allowed: the status is
"Ptch > Max Ptch"
- On the uplink, there is not enough power to transmit: the status is "Pmob > Max Pmob"
• Even if constraints above are respected, the network (cell and timeslot) may be saturated:
- The maximum uplink load factor is exceeded (at admission or congestion): the status is either "Admission
Rejection" or "UL Load Saturation"
- There are not enough resource units in the cell: the status is "RU Saturation"
- There is not enough power for cells: the status is "DL Load Saturation"
In the HSDPA part, Atoll processes all HSDPA bearer users. The HSDPA part of the algorithm simulates fast link adap-
tation, the scheduling of HSDPA users, and radio resource control on downlink. Two fast link adaptations are done, one
before mobile scheduling and one after.
HSDPA bearer selection is based on look-up tables available in the HSDPA Bearer Selection tab of the reception equip-
ment properties. The HSDPA and HS-SCCH powers of a cell are evaluated before calculating HS-PDSCH Ec⁄Nt. The
HSDPA power (the power dedicated to HS-SCCH and HS-PDSCH of HSDPA bearer users) of a cell can be either fixed
(statically allocated) or dynamically allocated. If it is dynamically allocated, the power allocated to HSDPA depends on how
much power is required to serve R99 traffic. In other words, the power available after all common channels and all R99
traffic have been served is allocated to HS-PDSCH and HS-SCCH of HSDPA bearer users. Similarly, the power per
HS-SCCH can be either fixed or dynamically allocated in order to attain the HS-SCCH Ec⁄Nt threshold. Using the
HS-SCCH and HSDPA powers, Atoll evaluates the HS-PDSCH power (the difference between the HSDPA power and the
HS-SCCH power), calculates the HS-PDSCH Ec⁄Nt and, from that, the HSDPA bearer defined for the terminal reception
equipment and the user mobility).
Similarly, the terminal power per HS-SICH in the uplink can be either fixed or dynamically allocated in order to attain the
HS-SICH Ec⁄Nt threshold. Before mobile scheduling, each user is processed as if he is the only user in the cell. This means
that Atoll determines the HSDPA bearer for each HSDPA user by considering the entire HSDPA power available of the
cell.
During scheduling, cell radio resources are shared between HSDPA users by the scheduler. The scheduler simultaneously
manages the maximum number of users within each cell and ranks them according to the selected scheduling technique:
• Max C/I: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined) are sched-
uled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending order by
the HS-PDSCH Ec⁄Nt.
• Round Robin: HSDPA users are scheduled in the same order as in the simulation (i.e., in random order).
• Proportional Fair: "n" HSDPA users (where "n" corresponds to the maximum number of HSDPA users defined)
are scheduled in the same order as in the simulation (i.e., in random order). Then, they are sorted in descending
order according to a random parameter which corresponds to a combination of the user rank in the simulation and
the HS-PDSCH Ec⁄Nt.
After mobile scheduling, Atoll carries out a second fast link adaptation. HSDPA users are processed in the order defined
by the scheduler and the cell’s HSDPA power is shared among them.
Note: Execute Later enables you to automatically calculate TD-SCDMA coverage predictions
after simulations with no intermediary step by creating your simulations, creating your
predictions, and then clicking the Calculate button ( ).
- Information to retain: You can select the level of detail that will be available in the output:
- Only the Average Simulation and Statistics: None of the individual simulations are displayed or avail-
able in the group. Only an average of all simulations and statistics is available.
Note: Some calculation and display options available for coverage predictions are not available
when the option "Only the average simulation and statistics" is selected.
- No Information About Mobiles: All the simulations are listed and can be displayed. For each of them, a
properties window containing simulation output, divided among four tabs – Statistics, Sites, Cells, and
Initial Conditions – is available.
- Standard Information About Mobiles: All the simulations are listed and can be displayed. The properties
window of each simulation contains an additional tab with output related to mobiles.
- Detailed Information About Mobiles: All the simulations are listed and can be displayed. The properties
window for each simulation contains additional mobile-related output on the Mobiles and Mobiles (Shad-
owing values) tabs.
Tip: When you are working on very large radio-planning projects, you can reduce memory
consumption by selecting Only the Average Simulation and Statistics under
Information to retain.
6. Under Cell Load Constraints on the General tab, you can set the constraints that Atoll must respect during the
simulation:
- UL Load Factor: If you want the UL load factor to be considered in the simulation, select the UL Load Factor
check box.
- Max UL Load Factor: If you want to enter a global value for the maximum uplink load factor, click the button
( ) beside the box and select Global Threshold. Then, enter a maximum uplink load factor. If you want to
use the maximum uplink load factor defined for each timeslot in a cell, click the button ( ) beside the box
and select Defined per Cell.
- DL Load (% Pmax): If you want the DL load to be considered in the simulation, select the DL Load (% Pmax)
check box and enter a maximum downlink load in the Max DL Load box.
- Max DL Load (% Pmax): If you want to enter a global value for the maximum downlink load as a percentage
of the maximum power, click the button ( ) beside the box and select Global Threshold. Then, enter a max-
imum downlink load as a percentage of the maximum power. If you want to use the maximum downlink load
defined for each timeslot in a cell, click the button ( ) beside the box and select Defined per Cell.
7. On the TD-SCDMA tab of the dialogue, under Settings, enter an Angular Step in degrees which is used to build
the geometrical distributions of uplink and downlink loads. Angular step in used with grid of beams, statistical, and
adaptive beam modelling. For more information on the different smart antenna models, see "Types of Smart
Antenna Modelling" on page 854.
8. Under DCA Strategies, select the strategy to be used for selecting carriers and timeslots during the simulations.
There are four different strategies available:
- Load: The least loaded cell or timeslot is selected.
- Available RUs: The cell or timeslot with the most available resource units is selected.
- Direction of Arrival: The cell or timeslot selected is the one which does not have an interfering mobile located
nearby at the same angle as the direction of arrival of the targeted mobile.
- Sequential: Cells and timeslots are selected in a sequential order.
For more information about the DCA strategies, see "The Monte Carlo Simulation Algorithm" on page 829.
9. Select the Calculate Interference Between Mobiles check box and enter a maximum distance to consider
between interfering mobiles in the Max Distance field.
10. On the Source Traffic tab, enter the following:
- Global Scaling Factor: If desired, enter a scaling factor to increase user density.
The global scaling factor enables you to increase user density without changing traffic parameters or traffic
maps. For example, setting the global scaling factor to 2 is the same as doubling the initial number of subscrib-
ers (for environment and user profile traffic maps) or the rates or users (for live traffic maps per sector).
- Select Traffic Maps to Be Used: Select the traffic maps you want to use for the simulation.
You can select traffic maps of any type. However, if you have several different types of traffic maps and want
to make a simulation based on a specific type of traffic map, you must ensure that you select only traffic maps
of the same type. For information on the types of traffic maps, see "Creating a Traffic Map" on page 821.
Tip: Using the same generated user and shadowing error distribution for several simulations
can be useful when you want to compare the results of several simulations where only one
parameter changes.
Tip: You can make the traffic distribution easier to see by hiding geo data and predictions. For
information, see "Displaying or Hiding Objects on the Map Using the Explorer" on
page 28.
The Statistics tab: The Statistics tab contains the following two sections:
- Request: Under Request, you will find data on the connection requests:
- Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; power control has not yet finished. The result depends on the traffic description and traffic input.
- During the first random trial, each user is assigned a service and an activity status. The number of users
per activity status and the UL and DL rates that all users could theoretically generate are provided.
- The breakdown per service (total number of users, number of users per activity status, and UL and DL
rates) is given.
- Results: Under Results, you will find data on the connection results:
- The number of iterations that were run in order to converge.
- The number and the percentage of non-connected users is given along with the reason for rejection.
These figures include rejected and delayed users. These figures are determined at the end of the simula-
tion and depend on the network design.
- The number and percentage of R99 bearer users connected to a cell, the number of users per activity
status, and the UL and DL total rates they generate. These figures include R99 users as well as HSDPA
users (since all of them request an R99 bearer); they are determined in the R99 part of the algorithm.
These data are also given per service.
- The total number and the percentage of connected users with an HSDPA bearer, the number of users per
activity status, and the DL total rate that they generate.
The Sites tab: The Sites tab contains the following information per site:
- JD Factor: The joint detection factor, defined in the site equipment, is used to decrease intra-cellular interfer-
ence in uplink.
- MCJD Factor: The multi-cell joint detection factor, defined in the site equipment, is used to decrease uplink
interference from mobiles in other cells.
- Instantaneous HSDPA Rate (kbps): The instantaneous HSDPA rate in kbps.
- DL Throughput (kbps): For each service, the aggregate downlink throughput of all the transmitters at each
site.
- UL Throughput (kbps): For each service, the aggregate uplink throughput of all the transmitters at each site.
The Cells tab: Cell level results are determined from the results calculated per timeslot. The Cells tab contains
the following information, per site, transmitter, carrier:
- Max Power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties.
- P-CCPCH Power [TS0] (dBm): The P-CCPCH power as defined in the cell properties.
- DwPCH Power [DwPTS] (dBm): The DwPCH power as defined in the cell properties.
- Other CCH power [DL Traffic TS] (dBm): The power of other common channels per timeslot.
- Gain (dBi): The gain as defined in the antenna properties for that transmitter.
- Reception Loss (dB): The reception loss as defined in the transmitter properties.
- Transmission Loss (dB): The transmission loss as defined in the transmitter properties.
- Noise Figure (dB): The noise figure as defined in the transmitter properties.
- DL Traffic Power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic
timeslot.
- DL Load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total trans-
mitted power and the maximum power (powers stated in W). When the constraint "DL Load" is set, the DL
∑ PTimeslot
Used Used
Load cannot exceed the user-defined Max DL Load. P Cell =
i
i ∈ DL
- UL Load Factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between
UL – Load UL – Load
the uplink total interference and the uplink total noise. F Cell = Avg ( F Timeslot )
i
i ∈ UL
- UL Noise Rise (dB): The uplink noise rise is calculated from the uplink load factor. It indicates the signal deg-
radation due to cell load (interference margin in the link budget).
- DL Load Factor (%): The downlink load factor for downlink timeslots. This factor corresponds to the ratio
DL – Load DL – Load
between the downlink total interference and the downlink total noise. F Cell = Avg ( F Timeslot )
i
i ∈ DL
- DL Noise Rise (dB): The downlink noise rise is calculated from the downlink load factor. It indicates the signal
degradation due to cell load (interference margin in the link budget).
- Number of DL Radio Links: The number of downlink radio links corresponds to the number of user-trans-
mitter links on the same carrier (i.e., the sum of the number of connected mobiles and the number of inactive
mobiles). This data indicates the number of users connected to the cell on the downlink.
- Number of UL Radio Links: The number of uplink radio links corresponds to the number of user-transmitter
links on the same carrier (i.e., the sum of the number of connected mobiles and the number of inactive
mobiles). This data indicates the number of users connected to the cell on the uplink.
- Connection Success Rate (%): The percentage of users able to connect to the cell with respect to the total
number of users attempting to connect. It is the ratio between the number of connected mobiles and the
number of connected and rejected mobiles.
- UL Total Requested Rate (kbps): The sum of all the uplink throughputs requested by the mobiles attempting
to connect to a carrier.
- DL Total Requested Rate (kbps): The sum of all the downlink throughputs requested by mobiles attempting
to connect to a carrier.
- UL Total Obtained Rate (kbps): The traffic carried by the cell in terms of throughput in the uplink.
- DL Total Obtained Rate (kbps): The traffic carried by the cell in terms of throughput in the downlink.
- Required UL Resource Units: The number of resource units required to carry the traffic demand in the uplink.
- UL Resource Units: The number of resource units used in the cell in the uplink.
- Required DL Resource Units: The number of resource units required to carry the traffic demand in the down-
link.
- DL Resource Units: The number of resource units used in the cell in the downlink.
The Timeslots tab: The Timeslots tab contains the following information, per site, transmitter, carrier, and time-
slot:
- Max Power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties.
- P-CCPCH Power [TS0] (dBm): The P-CCPCH power as defined in the cell properties.
- Other CCH power (dBm): The power of other common channels per timeslot.
- Gain (dBi): The gain as defined in the antenna properties for that transmitter.
- Reception Loss (dB): The reception loss as defined in the transmitter properties.
- Transmission Loss (dB): The transmission loss as defined in the transmitter properties.
- Noise Figure (dB): The noise figure as defined in the transmitter properties.
- DL Traffic Power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic
timeslot.
- Angular Distribution of UL and DL Loads: The angular distribution of downlink transmitted power and uplink
loads computed for cells whose transmitters have smart antenna equipment. This field contains binary data if
you are using a third-party smart antenna model.
- Max DL Load (% Pmax): The maximum percentage of downlink power that a cell can use. It is defined either
in the cell properties or in the simulation creation dialogue.
- DL Load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total trans-
mitted power and the maximum power (powers stated in W). When the constraint "DL Load" is set, the DL
Load cannot exceed the user-defined Max DL Load.
- Max UL Load Factor (%): The maximum uplink load factor not to be exceeded. This limit is taken into account
during the simulation if the option UL Load is selected. If the UL load option is not selected during a simula-
tion, this value is not taken into consideration.
- UL Load Factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between
the uplink total interference and the uplink total noise.
- UL Noise Rise (dB): The uplink noise rise is calculated from the uplink load factor. It indicates the signal deg-
radation due to cell load (interference margin in the link budget).
- DL Load Factor (%): The downlink load factor for downlink timeslots. This factor corresponds to the ratio
between the downlink total interference and the downlink total noise.
- DL Noise Rise (dB): The downlink noise rise is calculated from the downlink load factor. It indicates the signal
degradation due to cell load (interference margin in the link budget).
- Resource Units: The number of resource units on a timeslot for carrying traffic. Each timeslot can have a
maximum of 16 resource units.
- Available HS-PDSCH Power (dBm): The available HS-PDSCH power as defined in the timeslot properties.
This is the power available for the HS-PDSCH of HSDPA users. The value is either defined when the HS-
PDSCH power is allocated statically, or determined by a simulation when the option HS-PDSCH Dynamic
Power Allocation is selected.
- Transmitted HSDPA Power (dBm): The power transmitted by the cell to serve users connected to HSDPA
radio bearers. If HSDPA power is allocated statically, the transmitted HSDPA power is equal to the available
HSDPA power. If HSDPA power is allocated dynamically, the transmitted HSDPA power is the remaining
power after allocation of power to the users connected to R99 radio bearers, and the power headroom.
The Mobiles tab: The Mobiles tab contains the following information:
- Name: The name of the mobile as assigned during the random user generation.
- X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the
second random trial).
- Service: The service assigned during the first random trial, during the generation of the user distribution.
- Terminal: The assigned terminal. Atoll uses the assigned service and activity status to determine the terminal
and the user profile.
- User: The assigned user profile. Atoll uses the assigned service and activity status to determine the terminal
and the user profile.
- Mobility: The mobility type assigned during the first random trial during the generation of the user distribution.
- DL Activity: The activity status on the downlink assigned during the first random trial, during the generation
of the user distribution.
- UL Activity: The activity status on the uplink assigned during the first random trial, during the generation of
the user distribution.
- Indoor: This field indicates whether indoor losses have been added or not.
- Connection Status: The connection status indicates whether the user is connected or rejected at the end of
the simulation. If connected, the connection status corresponds to the activity status. If rejected, the rejection
cause is given.
- HSDPA Connection Status: The connection status indicates whether the user is connected to an HSDPA
radio bearer, delayed, or rejected at the end of the simulation.
- Best Server: The user’s best server.
- P-CCPCH RSCP: The received signal code power on the P-CCPCH pilot channel.
- UL Total Requested Rate (kbps): For an R99 user, the uplink total requested rate corresponds to the uplink
nominal rate of the R99 bearer associated to the service. For an HSDPA user, the uplink total requested rate
corresponds to the nominal rate of ADPCH-UL64 R99 bearer.
- DL Total Requested Rate (kbps): For an R99 user, the downlink total requested rate corresponds to the
downlink nominal rate of the R99 bearer associated to the service. For an HSDPA user, the downlink total
requested rate is the sum of the ADPCH-UL64 radio bearer nominal rate and the RLC peak rate that the
selected HSDPA radio bearer can provide.
- UL Total Obtained Rate (kbps): For an R99 user, the total obtained rate is the same as the total requested
rate if he is connected. If the user was rejected, the total obtained rate is zero.
For an HSDPA user connected to an HSDPA bearer, the uplink total obtained rate equals the total requested
rate. If the HSDPA user is delayed (he is only connected to an R99 radio bearer), the uplink total obtained rate
corresponds to the uplink nominal rate of ADPCH-UL64 radio bearer. Finally, if the HSDPA user is rejected
either in the R99 part or in the HSDPA part (because the HSDPA scheduler is saturated), the uplink total ob-
tained rate is zero.
- DL Total Obtained Rate (kbps): For an R99 user, the total obtained rate is the same as the total requested
rate if he is connected. If the user was rejected, the total obtained rate is zero.
For an HSDPA user connected to an HSDPA bearer, the downlink total obtained rate corresponds to the in-
stantaneous rate; this is the sum of the ADPCH-UL64 radio bearer nominal rate and the RLC peak rate pro-
vided by the selected HSDPA radio bearer after scheduling and radio resource control. If the HSDPA user is
delayed (he is only connected to an R99 radio bearer), the downlink total obtained rate corresponds to the
downlink nominal rate of ADPCH-UL64 radio bearer. Finally, if the HSDPA user is rejected either in the R99
part or in the HSDPA part (because the HSDPA scheduler is saturated), the downlink total obtained rate is
zero.
- 1st, 2nd, 3rd DL TS Rank (Carrier): A mobile can have at most three timeslots allocated for traffic. These
timeslots can be located on different carriers (cells) of the same transmitter. These columns list the numbers
of the 1st, 2nd, and 3rd timeslot assigned to a user, and the carrier number on which the timeslots are located.
For example, if a user is assigned two downlink timeslots, 4 and 6, on the carriers 0 and 2, the 1st DL TS Rank
(Carrier) will be "4 (0)" and 2nd DL TS Rank (Carrier) will be "6 (2)".
- 1st, 2nd, 3rd UL TS Rank (Carrier): A mobile can have at most three timeslots allocated for traffic. These
timeslots can be located on different carriers (cells) of the same transmitter. These columns list the numbers
of the 1st, 2nd, and 3rd timeslot assigned to a user, and the carrier number on which the timeslots are located.
For example, if a user is assigned two uplink timeslots, 2 and 3, on the carriers 0 and 2, the 1st UL TS Rank
(Carrier) will be "2 (0)" and 2nd UL TS Rank (Carrier) will be "3 (2)".
- 1st, 2nd, 3rd TS Mobile Total Power (UL) (dBm): The total mobile power corresponds to the total power
transmitted by the terminal on the uplink and on the timeslots assigned to the mobile.
- 1st, 2nd, 3rd TS Cell Total Power (DL) (dBm): The cell traffic power corresponds to the power transmitted
by the cell on the downlink for a mobile on the timeslots assigned to the mobile.
The following columns only appear if, when creating the simulation as explained in "Creating Simulations" on
page 831, you select "Detailed information about mobiles" under Information to Retain:
- 1st, 2nd, 3rd TS Extra Interference of UL Mobiles (DL) (dBm): The interference received on downlink
timeslots from mobiles transmitting in the uplink. This interference is calculated if you select the Calculate
Interference Between Mobiles option when creating the simulation.
- 1st, 2nd, 3rd TS Required HSDPA Power (dBm): This is the HSDPA power required to provide the HSDPA
bearer user with the downlink requested rate.
- 1st, 2nd, 3rd TS Obtained HSDPA Power (dBm): This is the HSDPA power required to provide the HSDPA
bearer user with the downlink obtained rate.
- 1st, 2nd, 3rd HSDPA TS Rank (Carrier): These columns list the numbers of the 1st, 2nd, and 3rd timeslot
assigned to an HSDPA user, and the carrier number on which the timeslots are located.
- Requested HSDPA Bearer Index: The HSDPA bearer requested by an HSDPA user.
- Obtained HSDPA Bearer Index: The HSDPA bearer assigned to an HSDPA user by the DCA and resource
allocation algorithm.
- Clutter: The clutter class on which the mobile is located.
- DL and UL Orthogonality Factor: The orthogonality factor used in the simulation. The orthogonality factor is
the remaining orthogonality of the OVSF codes at reception. The value used is the orthogonality factor set in
the clutter classes.
- Spreading Angle (°): The spreading angle used in the simulation. The value used is the spreading angle set
in the clutter classes.
The Mobiles (Shadowing Values) tab: The Mobiles (Shadowing Values) tab contains information on the shad-
owing margin for each link between the receiver and up to ten closest potential transmitters:
Note: The Mobiles (Shadowing Values) tab only appears if, when creating the simulation as
explained in "Creating Simulations" on page 831, you select "Detailed information about
mobiles" under Information to Retain.
- The parameters defined per clutter class, such as the uplink and downlink orthogonality factors, indoor
loss, spreading angle, and the various standard deviations (Model, P-CCPCH Eb⁄Nt or C⁄I, DL Eb⁄Nt or C⁄I,
and UL Eb⁄Nt or C⁄I).
- The parameters related to the clutter classes, including the default values.
The Statistics tab: The Statistics tab contains the following two sections:
- Request: Under Request, you will find data on the connection requests:
- Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; power control has not yet finished. The result depends on the traffic description and traffic input.
- During the first random trial, each user is assigned a service and an activity status. The number of users
per activity status and the UL and DL rates that all users could theoretically generate are provided.
- The breakdown per service (total number of users, number of users per activity status, and UL and DL
rates) is given.
- Results: Under Results, you will find data on the connection results:
- The number of iterations that were run in order to converge.
- The number and the percentage of non-connected users is given along with the reason for rejection.
These figures include rejected and delayed users. These figures are determined at the end of the simula-
tion and depend on the network design.
- The number and percentage of R99 bearer users connected to a cell, the number of users per activity
status, and the UL and DL total rates they generate. These figures include R99 users as well as HSDPA
users (since all of them request an R99 bearer); they are determined in the R99 part of the algorithm.
These data are also given per service.
- The total number and the percentage of connected users with an HSDPA bearer, the number of users per
activity status, and the DL total rate that they generate.
The Sites (Average) and Sites (Standard Deviation) tabs: The Sites (Average) and Sites (Standard Deviation)
tabs contain the following average and standard deviation information, respectively, per site:
- JD Factor: The joint detection factor, defined in the site equipment, is used to decrease intra-cellular interfer-
ence in uplink.
- MCJD Factor: The multi-cell joint detection factor, defined in the site equipment, is used to decrease uplink
interference from mobiles in other cells.
- Instantaneous HSDPA Rate (kbps): The instantaneous HSDPA rate in kbps.
- DL Throughput (kbps): For each service, the aggregate downlink throughput of all the transmitters at each
site.
- UL Throughput (kbps): For each service, the aggregate uplink throughput of all the transmitters at each site.
The Cells (Average) and Cells (Standard Deviation) tabs: The Cells (Average) and Cells (Standard Deviation)
tabs contain the following average and standard deviation information, respectively, per site, transmitter, and
carrier:
- Max Power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties.
- P-CCPCH Power [TS0] (dBm): The P-CCPCH power as defined in the cell properties.
- DwPCH Power [DwPTS] (dBm): The DwPCH power as defined in the cell properties.
- Other CCH power [DL Traffic TS] (dBm): The power of other common channels per timeslot.
- Gain (dBi): The gain as defined in the antenna properties for that transmitter.
- Reception Loss (dB): The reception loss as defined in the transmitter properties.
- Transmission Loss (dB): The transmission loss as defined in the transmitter properties.
- Noise Figure (dB): The noise figure as defined in the transmitter properties.
- DL Traffic Power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic
timeslot.
- DL Load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total trans-
mitted power and the maximum power (powers stated in W). When the constraint "DL Load" is set, the DL
Load cannot exceed the user-defined Max DL Load.
- UL Load Factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between
the uplink total interference and the uplink total noise.
- Number of DL Radio Links: The number of downlink radio links corresponds to the number of user-trans-
mitter links on the same carrier. This data indicates the number of users connected to the cell on the downlink.
- Number of UL Radio Links: The number of uplink radio links corresponds to the number of user-transmitter
links on the same carrier. This data indicates the number of users connected to the cell on the uplink.
- Connection Success Rate (%): The percentage of users able to connect to the cell with respect to the total
number of users attempting to connect.
- UL Requested Rate (kbps): The traffic demand in terms of throughput in the uplink.
- UL Obtained Rate (kbps): The traffic carried by the cell in terms of throughput in the uplink.
- DL Requested Rate (kbps): The traffic demand in terms of throughput in the downlink.
- DL Obtained Rate (kbps): The traffic carried by the cell in terms of throughput in the downlink.
- Required UL Resource Units: The number of resource units required to carry the traffic demand in the uplink.
- UL Resource Units: The number of resource units available in the cell in the uplink.
- Required DL Resource Units: The number of resource units required to carry the traffic demand in the down-
link.
- DL Resource Units: The number of resource units available in the cell in the downlink.
The Timeslots (Average) and Timeslots (Standard Deviation) tabs: The Timeslots (Average) and Timeslots
(Standard Deviation) tabs contain the following average and standard deviation information, respectively, per site,
transmitter, carrier, and timeslot:
- Max Power [Traffic TS] (dBm): The maximum power per traffic timeslot as defined in the cell properties.
- P-CCPCH Power [TS0] (dBm): The P-CCPCH power as defined in the cell properties.
- Other CCH power (dBm): The power of other common channels per timeslot.
- Gain (dBi): The gain as defined in the antenna properties for that transmitter.
- Reception Loss (dB): The reception loss as defined in the transmitter properties.
- Transmission Loss (dB): The transmission loss as defined in the transmitter properties.
- Noise Figure (dB): The noise figure as defined in the transmitter properties.
- DL Traffic Power (dBm): The DL traffic power is the power transmitted by the cell on a downlink traffic
timeslot.
- Angular Distribution of UL and DL Loads: The angular distribution of downlink transmitted power and uplink
loads calculated for cells whose transmitters have smart antenna equipment. This field contains binary data if
you are using a third-party smart antenna model.
- Max DL Load (% Pmax): The maximum percentage of downlink power that a cell can use. It is defined either
in the cell properties or in the simulation creation dialogue.
- DL Load (% Pmax): The percentage of the maximum power used is determined by the ratio of the total trans-
mitted power and the maximum power (powers stated in W). When the constraint "DL Load" is set, the DL
Load cannot exceed the user-defined Max DL Load.
- Max UL Load Factor (%): The maximum uplink load factor not to be exceeded. This limit is taken into account
during the simulation if the option UL Load is selected. If the UL load option is not selected when the simula-
tion is defined, this value is not taken into consideration.
- UL Load Factor (%): The uplink load factor for uplink timeslots. This factor corresponds to the ratio between
the uplink total interference and the uplink total noise.
- UL Noise Rise (dB): The uplink noise rise is calculated from the uplink load factor. It indicates the signal deg-
radation due to cell load (interference margin in the link budget).
- DL Load Factor (%): The downlink load factor for downlink timeslots. This factor corresponds to the ratio
between the downlink total interference and the downlink total noise.
- DL Noise Rise (dB): The downlink noise rise is calculated from the downlink load factor. It indicates the signal
degradation due to cell load (interference margin in the link budget).
- Resource Units: The number of resource units on a timeslot for carrying traffic. Each timeslot can have a
maximum of 16 resource units.
- Available HS-PDSCH Power (dBm): The available HS-PDSCH power as defined in the timeslot properties.
This is the power available for the HS-PDSCH of HSDPA users. The value is either fixed by the user when the
HS-PDSCH power is allocated statically, or by a simulation when the option HS-PDSCH Dynamic Power
Allocation is selected.
- Transmitted HSDPA Power (dBm): The power transmitted by the cell to serve users connected to HSDPA
radio bearers. If HSDPA power is allocated statically, the transmitted HSDPA power is equal to the available
HSDPA power. If HSDPA power is allocated dynamically, the transmitted HSDPA power is the remaining
power after allocation of power to the users connected to R99 radio bearers, and the power headroom.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
• Replaying a group: When you replay an existing group of simulations, Atoll reuses the same user distribution
(users with a service, a mobility and an activity status) as the one used to calculate the initial simulation. The shad-
owing error distribution between simulations is different. Traffic parameter changes (such as, maximum and min-
imum traffic channel powers allowed, Eb⁄Nt or C⁄I thresholds, etc.) may be taken into account or not. Finally, radio
data modifications (new transmitters, changes to the antenna azimuth, etc.) are always taken into account during
the power control (or rate/power control) simulation.
To replay a group of simulations, see "Replaying a Simulation or Group of Simulations" on page 842.
• Using the Generator Initialisation Number: When you create groups of simulations using the same generator
initialisation number (which must be an integer other than 0), Atoll generates the same user and shadowing error
distributions (user with a service, a mobility, an activity status, and a shadowing error) in all groups using the same
number. However, any modifications to traffic parameters (such as, maximum and minimum traffic channel powers
allowed, Eb⁄Nt or C⁄I thresholds, etc.) and radio data (new transmitter, azimuth, etc.) are taken into account during
the power control simulation.
By creating and calculating one group of simulations, making a change to the network and then creating and calcu-
lating a new group of simulations using the same generator initialisation number, you can see the difference your
parameter changes make.
To create a new simulation to a group of simulations using the generator initialisation number, see "Adding a Simu-
lation to a Group of Simulations" on page 842.
• Duplicating a Group: When you duplicate a group, Atoll creates a group of simulations with the same simulation
parameters as those used to generate the group of simulations. You can then modify the simulation parameters
before calculating the group.
To duplicate a group of simulations, see "Duplicating a Group of Simulations" on page 843.
Note: When adding a simulation to an existing group of simulations, the parameters originally
used to calculate the group of simulations are used for the new simulations.
Consequently, few parameters can be changed for the added simulation.
5. On the General tab of the dialogue, if desired, change the Name and Comments for this group of simulations.
6. Under Execution on the General tab, you can set the following parameters:
- Number of Simulations: Enter the number of simulations to added to this group of simulations.
- Execute Later: If you select the Execute Later check box, the simulation will not be carried out until you click
the Calculate button ( ). If the Execute Later check box is not selected, the simulation will be carried out
as soon as you click OK and close the dialogue.
7. Click OK. Atoll immediately begins the simulation unless you selected the Execute Later check box on the Gen-
eral tab.
Note: When replaying an existing group of simulations, some parameters originally used to
calculate the group of simulations are reused for the replayed group. Consequently, few
parameters can be changed for the replayed group.
5. In the General tab of the dialogue, you can set the following parameters:
- Select the level of detail as explained in "Creating Simulations" on page 831 that will be available in the output
from the Information to retain list.
- Under Cell Load Constraints, you can set the constraints as explained in "Creating Simulations" on page 831
that Atoll must respect during the simulation.
6. In the Source Traffic tab of the dialogue, check the Refresh Traffic Parameters check box if you want to take into
account traffic parameter changes (such as, maximum and minimum traffic channel powers allowed, Eb/Nt thresh-
olds, etc.) in the replayed simulation.
7. In the Advanced tab, you can set the following parameters:
- Max Number of Iterations: Enter the maximum number of iterations that Atoll should run to make conver-
gence.
- UL Convergence Threshold: Enter the relative difference in terms of interference and connected users on
the uplink that must be reached between two iterations.
- DL Convergence Threshold: Enter the relative difference in terms of interference and connected users on
the downlink that must be reached between two iterations.
- Under Quality Threshold Type, select whether the simulations will be carried out using the Eb/Nt or C/I. For
more information on the quality threshold type selection, see "The Global Transmitter Parameters" on
page 852.
8. In the TD-SCDMA tab, you can set the following parameters:
- Angular Step: The angle in degrees used to build the geometrical distributions of uplink and downlink loads.
The angular step in used with grid of beams, statistical, and adaptive beam modelling. For more information
on the different smart antenna models, see "Types of Smart Antenna Modelling" on page 854.
- Carrier Selection and Timeslot Selection: The DCA strategies to be used for selecting carriers and timeslots
during the simulations. For more information about the DCA strategies, see "The Monte Carlo Simulation Algo-
rithm" on page 829.
- Calculate Interference Between Mobiles: Select the check box and enter a maximum distance to be con-
sidered between interfering mobiles in the Max Distance field.
9. Click OK. Atoll immediately begins the simulation unless you selected the Execute Later check box on the Gen-
eral tab.
Creating a New Simulation or Group of Simulations Using the Generator Initialisation Number
To create a new simulation or group of simulations using the generator initialisation number:
1. Click the Data tab in the Explorer window.
2. Right-click the TD-SCDMA Simulations folder. The context menu appears.
3. Select New from the context menu. The properties dialogue for a new simulation or group of simulations appears.
4. Click the Advanced tab.
5. Under Generator Initialisation, enter an integer as the generator initialisation value. The integer must be the
same generator initialisation number as used in the group of simulations with the user and shadowing error distri-
butions you want to use in this simulation or group of simulations. If you enter "0", the default, the user and shad-
owing error distribution will be random. If you enter any other integer, the same user and shadowing error
distribution will be used for any simulation using the same generator initialisation value.
6. For information on setting other parameters, see "Creating Simulations" on page 831.
Tip: You can create a new group of simulations with the same parameters as the original group
of simulations by duplicating an existing one as explained in "Duplicating a Group of
Simulations" on page 843.
- DwPCH Reception Analysis (C⁄I): For information on making a DwPCH reception analysis, see "Making a
DwPCH Signal Quality Prediction" on page 780.
- Service Area (Eb⁄Nt) Downlink or Service Area (C⁄I) Downlink: For information on making a coverage pre-
diction the downlink service area, see "Studying Downlink and Uplink Service Areas" on page 783.
- Service Area (C⁄I) Uplink: For information on making a coverage prediction the uplink service area, see
"Studying Downlink and Uplink Service Areas" on page 783.
- Effective Service Area (Eb⁄Nt) or Effective Service Area (C⁄I): For information on making a coverage anal-
ysis for the effective service area, see "Studying Effective Service Area" on page 785.
• Coverage predictions on noise and interference:
- Downlink Total Noise: For information on making a downlink total noise coverage prediction, see "Studying
Downlink Total Noise" on page 787.
- Cell to Cell Interference Zones: For information on making a coverage analysis for cell-to-cell interference,
see "Studying Cell to Cell Interference" on page 789.
- UpPCH Interference Zones: For information on making a coverage analysis for UpPCH interference in case
of UpPCH shifting, see "Studying UpPCH Interference" on page 790.
• A coverage prediction for baton handover analysis:
- Baton Handover: For information on making a baton handover coverage prediction, see "Making a Baton
Handover Coverage Prediction" on page 792.
• An HSDPA coverage prediction to analyse HS-PDSCH quality and HSDPA data rate:
- HSDPA Coverage Prediction: For information on making an HSDPA coverage prediction, see "HSDPA Cov-
erage Prediction" on page 793.
Note: Files with the extension PLN, as well as some FMT files (created with previous versions of
TEMS) are imported directly into Atoll; you will not be asked to define the data structure
using the Import of Measurement Files dialogue.
6. If you already have an import configuration defining the data structure of the imported file or files, you can select
it from the Configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have
an import configuration, continue with step 7.
a. Under Configuration, select an import configuration from the Configuration list.
b. Continue with step 10.
Notes:
• When importing a test mobile data path file, existing configurations are available in the Files
of type list of the Open dialogue, sorted according to their date of creation. After you have
selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises
the extension. In case several configurations are associated with an extension, Atoll chooses
the first configuration in the list.
• The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in
the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see
the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters:
- Name: By default, Atoll names the new test mobile data path after the imported file. You can change this
name if desired.
- Under Receiver, set the Height of the receiver antenna and the Gain and Losses.
- Under Measurement Conditions,
- Units: Select the measurement units used.
- Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document.
If the coordinates used in the file you are importing are different than the coordinates used in the Atoll
document, you must click the Browse button ( ) and select the coordinate system used in the test
mobile data file. Atoll will then convert the data imported to the coordinate system used in the Atoll docu-
ment.
8. Click the Setup tab (see Figure 12.74).
Figure 12.74: The Setup tab of the Import of Measurement Files dialogue
a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Dec-
imal Symbol used in the file.
b. Click Setup to link file columns and internal Atoll fields. The Test Mobile Data Configuration dialogue ap-
pears.
c. Select the columns in the imported file that give the X-Coordinates and the Y-Coordinates of each point in
the test mobile data file.
Note: You can also identify the columns containing the XY coordinates of each point in the test
mobile data file by selecting them from the Field row of the table on the Setup tab.
d. In the SC Group Identifier box, enter a string that must be found in the column names identifying the scram-
bling code group of scanned cells. For example, if the string "SC_Group" is found in the column names iden-
tifying the scrambling code group of scanned cells, enter it here. Atoll will then search for columns with this
string in the column name.
If there is no scrambling code group information contained in the test mobile data file, leave the SC Group
Identifier box empty.
e. In the SC Identifier box, enter a string that must be found in the column names identifying the scrambling code
of scanned cells. For example, if the string "SC" is found in the column names identifying the scrambling code
of scanned cells, enter it here. Atoll will then search for columns with this string in the column name.
f. From the Scramb. Code Format list, select the scrambling code format, either "Decimal" or "Hexadecimal."
g. Click OK to close the Test Mobile Data Configuration dialogue.
Important:
• If you have correctly entered the information under File on the Setup tab, and the necessary
values in the Test Mobile Data Configuration dialogue, Atoll should recognize all columns in
the imported file. If not, you can click the name of the column in the table in the Field row and
select the column name. For each field, you must ensure that each column has the correct data
type in order for the data to be correctly interpreted. The default value under Type is "<Ignore>".
If a column is marked with "<Ignore>", it will not be imported.
• The data in the file must be structured so that the columns identifying the scrambling code group
and the scrambling code are placed before the data columns for each cell. Otherwise Atoll will
not be able to properly import the file.
9. If you want to save the definition of the data structure so that you can use it again, you can save it as an import
configuration:
a. On the Setup tab, under Configuration, click Save. The Configuration dialogue appears.
b. By default, Atoll saves the configuration in a special file called "NumMeasINIfile.ini" found in Atoll’s installa-
tion folder. In case you cannot write into that folder, you can click Browse to choose a different location.
c. Enter a Configuration Name and an Extension of the files that this import configuration will describe (for ex-
ample, "*.csv").
d. Click OK.
Atoll will now select this import configuration automatically every time you import a test mobile data path file
with the selected extension. If you import a file with the same structure but a different extension, you will be
able to select this import configuration from the Configuration list.
Notes:
• You do not have to complete the import procedure to save the import configuration and have
it available for future use.
• When importing a CW measurement file, you can expand the NumMeasINIfile.ini file by clicking
the button ( ) in front of the file in the Setup part to display all the available import configura-
tions. When selecting the appropriate configuration, the associations are automatically made
in the table at the bottom of the dialogue.
• You can delete an existing import configuration by selecting the import configuration under
Setup and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The
mobile data are imported into the current Atoll document.
Notes:
• Fast Display forces Atoll to use the lightest symbol to display the points. This is useful when
you have a very large number of points.
• You can not use Multiple Shadings if the Fast Display check box has been selected.
• You can sort test mobile data paths in alphabetical order on the Data tab of the Explorer window
by right-clicking the Test Mobile Data Path folder and selecting Sort Alphabetically from the
context menu.
• You can export the display settings of a test mobile data path in a configuration file to make them
available for future use. You can export the display settings or import display settings by clicking
the Actions button on the Display tab of the test mobile data path’s Properties dialogue and
selecting Export or Import from the menu.
6. By default, the data in all clutter classes is displayed. Clear the check box of each clutter class whose points you
do not want to use.
Note: You can permanently delete the points located in the clutter classes whose check boxes
you clear by selecting the Delete points outside the filter check box.
b. Underneath each column name, enter the criterion on which the column will be filtered as explained in the fol-
lowing table:
9. Click OK to filter the data according to the criteria you have defined.
Filters are combined first horizontally, then vertically. For more information on filters, see "Advanced Data Filtering"
on page 71.
Note: The Refresh Geo Data option available in the context menu of Test Mobile Data paths
enables you to update heights (DTM, clutter heights, DTM + clutter) and the clutter class
of test mobile data points after adding new geographic maps or modifying existing ones.
Note: Atoll can display the best server. If you want to display, for example, the point signal
level, remember to select the check box for the point signal level for all servers in the For
the Fields list. The new column will then display the point signal level for the selected
transmitter for all servers if a value exists.
8. Click OK. Atoll creates a new column in the test mobile path data table for the selected transmitters and with the
selected values.
5. Click Display at the top of the Test Mobile Data window. The Display Parameters dialogue appears (see
Figure 12.77).
Note: You can change the display status or the colour of more than one field at a time. You can
select contiguous fields by clicking the first field, pressing SHIFT and clicking the last field
you want to import. You can select non-contiguous fields by pressing CTRL and clicking
each field. You can then change the display status or the colour by right-clicking on the
selected fields and selecting the choice from the context menu.
The selected fields are displayed in the Test Mobile Data window.
7. You can display the data in the test mobile path in two ways:
- Click the values in the Test Mobile Data window.
- Click the points on the test mobile path in the map window.
The test mobile data path appears in the map window as an arrow pointing towards the serving cell, with a number
identifying the best server (see Figure 12.76 on page 850). If the transmitter display type is "Automatic," both the
number and the arrow are displayed in the same colour as the transmitter. For information on changing the display
type to "Automatic," see "Defining the Display Type" on page 34.
8. You can display a second Y-axis on the right side of the window in order to display the values of a variable with
different orders of magnitude than the ones selected in the Display Parameters dialogue. You can select the sec-
ondary Y-axis from the right-hand list on the top of the Test Mobile Data window. The selected values are dis-
played in the colours defined for this variable in the Display Parameters dialogue.
9. You can change the zoom level of the Test Mobile Data window display in the following ways:
- Zoom in or out:
i. Right-click the Test Mobile Data window.
ii. Select Zoom In or Zoom Out from the context menu.
- Select the data to zoom in on:
i. Right-click the Test Mobile Data window on one end of the range of data you want to zoom in on.
ii. Select First Zoom Point from the context menu.
iii. Right-click the Test Mobile Data window on the other end of the range of data you want to zoom in on.
iv. Select Last Zoom Point from the context menu. The Test Mobile Data window zooms in on the data be-
tween the first zoom point and the last zoom point.
10. Click the data in the Test Mobile Data window to display the selected point in the map window. Atoll will recentre
the map window on the selected point if it is not presently visible.
Tip: If you open the table for the test mobile data you are displaying in the Test Mobile Data
window, Atoll will automatically display in the table the data for the point that is displayed
in the map and in the Test Mobile Data window (see Figure 12.76 on page 850).
a. Select Print from the context menu. The Print dialogue appears.
b. Click OK to print the contents of the Test Mobile Data window.
d. Press ENTER to create the carrier pair and to create a new row.
Important: When you have more than one frequency band, the carriers must be numbered
sequentially, contiguously (i.e., you cannot skip numbers in a range of carriers, and the
range of carriers in one band cannot overlap the range of carriers in another), and
uniquely (i.e., you can only use each number once).
For example:
Band 2010: First carrier: 0; Last carrier 1 and Band 900: First carrier: 2; Last carrier: 2
- Frame: The duration of a TD-SCDMA frame (10 ms). A frame includes two subframes of equal duration.
- Number of Chips per Timeslot: Under Number of Chips per Timeslot, you have the number of chips cor-
responding to the data, midamble, and the guard periods.
- Guard Period: The number of chips in the guard period of each timeslot (16).
- Data: The number of data chips in each timeslot (704).
- Midamble: The number of midamble chips in each timeslot (144).
The subframe duration, the number of timeslots per subframe, and the numbers of chips per timeslot are used
to calculate the processing gain for each service (see example below).
- Number of Pilot Chips: Under Number of Pilot Chips, you have the description of the pilot timeslot:
- Guard Period: The number of chips in the guard period between DwPTS and UpPTS (96).
- DwPTS: The Total number of chips used in the DwPTS timeslot (96), which are divided into a Guard
Period (32) and a Synch period (64).
- UpPTS: The Total number of chips used in the UpPTS timeslot (160), which are divided into a Guard
Period (32) and a Synch period (128).
The parameters that can be modified include:
• DL Powers: Under DL Powers, you can define whether the power values on the downlink are Absolute or Relative
to Pilot. The power values affected are the DwPCH powers and other common channel powers defined in the cell
properties for TS0 and for each timeslot, as well as the minimum and maximum traffic channel powers defined for
services. Atollautomatically converts the power values defined in the cell properties (i.e. DwPCH and other
common channel powers) when changing the option. On the other hand, the values for the minimum and max-
imum traffic channel powers have to be modified manually.
• Quality Threshold Type: Under Quality Threshold Type, you can select whether the signal quality thresholds
entered in the mobility types and radio bearers are Eb⁄Nt or C⁄(I+N).
Note: Atoll ensures consistency between the quality threshold parameter and the parameter
which is calculated during coverage predictions and Monte Carlo simulations. For
example, if you set the Quality Threshold Type to Eb⁄Nt in the Global Parameters tab, all
the signal quality thresholds are considered to be defined in terms of Eb⁄Nt. If you
calculate a C⁄I-based coverage prediction or simulation, Atoll converts the thresholds
from Eb⁄Nt to C⁄I, by removing the processing gain from the Eb⁄Nt values, in order to
calculate and compare C⁄I. Similarly, if the Quality Threshold Type is set to C⁄I, and the
calculations are performed for Eb/Nt, Atoll converts all C⁄I thresholds to Eb⁄Nt for the
calculations.
• Spreading Rate: The chip rate used in TD-SCDMA for spreading the user signals (1.28 Mcps by default).
• P-CCPCH Processing Gain: The processing gain is the ratio of the spread bandwidth to the unspread bandwidth.
It is set to 13.8 dB (= 24 times) by default.
• Spreading Factor: Under Spreading Factor, you have the minimum and maximum spreading factors allowed in
TD-SCDMA:
- Min.: The lowest spreading factor that can be used (1).
- Max: The highest spreading factor that can be used (16).
• Interferences: Under Interferences, you can define the parameter used to calculate interference on the downlink.
- Nt: You can select "Total noise" and Atoll will calculate Nt as the noise generated by all transmitters plus
thermal noise, or you can select "Without useful signal" and Atoll will calculate Nt as the total noise less the
signal of the studied cell.
• HSDPA: Under HSDPA, you can define how total noise is calculated for HSDPA.
- Nt: You can select "Total noise" and Atoll will calculate Nt as the noise generated by all transmitters plus
thermal noise or you can select "Without useful signal" and Atoll will calculate Nt as the total noise less the
signal of the studied cell.
The processing gain is the ratio between the chip rate transmitted on the air interface and the data rate of a service. The
processing gains on the uplink and downlink are calculated from the uplink and downlink data rates defined in the proper-
ties of the service that you have set. The following example shows how the processing gains are calculated for different
services.
W
G P = Processing Gain = -----
R
Where W is the chip rate for TD-SCDMA, and R is the data rate per timeslot of the service.
The chip rate is calculated from the number of data chips per timeslot and the subframe duration:
TS
N Data Chips 704
W = -------------------------- = --------------- = 140800 bps
D Subframe 0.005
TS
Where N Data Chips is the number of data chips per timeslot (704), and D Subframe is the subframe duration (5 ms).
Taking the service "Mobile Internet Access" for example, the service data rates per timeslot in uplink and downlink are
calculated to be:
DL 384000 UL 64000
R = -------------------- = 128000 bps and R = ---------------- = 64000 bps
3 1
Where 3 and 1 are the number of downlink and uplink timeslots, respectively.
The uplink and downlink processing gains are then calculated:
DL 140800 UL 140800
GP = -------------------- = 1.1 = 0.414 dB and G P = -------------------- = 2.2 = 3.4242 dB
128000 64000
Important: Although the number of beams in a GOB is not limited, calculation times with a large
number of beams will be longer.
The Atoll TD-SCDMA project template contains sample smart antenna equipment. You should create smart antenna
equipment according to the specifications of your equipment supplier, or import them in Atoll, in order to use real data in
calculations.
The following sections explain how to create and import grids of beams:
• "Creating a Grid of Beams (GOB)" on page 855.
• "Adding Antennas to a Grid of Beams (GOB)" on page 855.
• "Importing a Grid of Beams (GOB)" on page 855.
• "The Grid of Beams (GOB) Import Format" on page 855.
In Atoll, a grid of beams is a list of antennas. A list of antennas can include any number of antennas listed in the Antennas
folder.
To create an antenna list:
1. Click the Data tab in the Explorer window.
2. Right-click the Antennas folder. The context menu appears.
3. Select Antenna List > Open Table from the context menu. The Antenna Lists table appears.
4. Create a new antenna list in the row marked with the New Row icon ( ).
5. Click the Properties button. The New Antenna List Properties dialogue appears.
6. Select the antennas from the Antennas column to add to the antenna list in each new row.
7. Click OK to close the dialogue.
8. Click Close to close the Antenna Lists table.
You can also export an antenna list to an external file by clicking the Export button, or import an existing antenna list by
clicking the Import button in the New Antenna List Properties dialogue.
You can add antennas, or beams, from the antennas folder to an existing grid of beams or antenna list.
To add antennas to an antenna list:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Antennas folder.
3. Right-click the antenna that you want to add to an antenna list. The context menu appears.
4. Select Add the Antenna to a List from the context menu. The Antenna Addition in a List dialogue appears.
5. Select the antenna list to which you want to add the antenna from the Antenna List.
6. Click OK to add the antenna to the list.
You can also add all the antennas in the Antennas folder or a subfolder to an antenna list by selecting Antenna List >
Add Antennas to a List from the folder’s context menu.
You can import existing antenna lists to be used as grids of beams in Atoll.
To import an antenna list:
1. Click the Data tab in the Explorer window.
2. Right-click the Antennas folder. The context menu appears.
3. Select Antenna List > Import Antennas from a List from the context menu. The Open dialogue appears.
4. Select an Index file to import.
5. Click Open to import the antenna list to Atoll. The Import of antennas from a list dialogue appears.
6. Enter a name for the new antenna list.
7. Click OK to import the antenna list.
Atoll adds the antennas referred to in the index file to the Antennas folder, and adds the new antenna list to the
Antenna Lists table.
Atoll supports standard, Planet-like antenna list format for export and import. An index file contains the list of files contain-
ing the horizontal antenna patterns and a file containing the vertical antenna pattern.
The horizontal antenna pattern files have the following format:
DEGREEa Attenuation
Name of the antenna. "<ALL>" can be used to indicate that the vertical pattern is the
NAME
same for all the files containing the horizontal antenna patterns.
DEGREEa Attenuation
5. Click the Properties button. The smart antenna properties dialogue appears.
6. On the General tab of this dialogue, you can modify the Name, Smart Antenna Model, and Comments.
7. Under Smart Antenna Model, click the Parameters button. A dialogue opens with the parameters specific to the
selected smart antenna model.
If you selected Grid of Beams (GOB) as Smart Antenna Model, the Grid of Beams (GOB) Modelling dialogue
appears.
a. Select a DL grid of beams, the grid of beams to be used in downlink from the list of grid of beams listed in the
Antennas Lists table. For more information on creating grids of beams, see "Grid of Beams (GOB) Modelling"
on page 854.
b. Select a UL grid of beams, the grid of beams to be used in uplink. If you do not select a UL grid of beams,
Atoll uses the main antenna for uplink calculations.
c. Under Patterns, you can view the grid of beams separately or combined in the Grid of Beams Properties
dialogue.
i. Click the Separate button to display the antenna patterns of all the beams separately in the Grid of
Beams Properties dialogue.
ii. Click the Combined button to display the combined patterns of all the beams in the Grid of Beams Prop-
erties dialogue.
iii. Click OK to close the Grid of Beams Properties dialogue.
Notes:
• If you opened the smart antenna properties dialogue by clicking the Browse ( ) button on
the Transmitter tab of a transmitter’s properties dialogue, these patterns will also include the
main antenna pattern, if any.
• You can use the combined antenna pattern display to understand any inconsistencies in smart
antenna results. If the gird of beams and the main antenna do not have the same gains, the
smart antenna could provide worse results than the main antenna for traffic timeslots.
a. Select a Probability Threshold (%) used to read the C⁄I gain graphs. For more information on the probability
threshold and C⁄I gains, see "Statistical Modelling" on page 856.
b. Define a Spreading Angle (°) per column.
c. Click the Browse ( ) button corresponding to the C⁄I Gain Graph for each column. The C⁄I Gain Graph
dialogue appears. The C⁄I Gain Graph provides the cumulative probability of each C⁄I value.
d. Click OK to close the C⁄I Gain Graph dialogue.
e. Click OK to close the Statistical Modelling dialogue.
If you selected Adaptive Beam as Smart Antenna Model, the Adaptive Beam Modelling dialogue appears:
a. Select a DL adaptive beam, the adaptive beam to be used in downlink from the list of adaptive beams listed
in the Antennas Lists table.
b. Select a UL adaptive beam, the adaptive beam to be used in uplink. If you do not select a UL adaptive beam,
Atoll uses the main antenna for uplink calculations.
c. Under Patterns, you can view the adaptive beam pattern separately or combined in the Adaptive Beam
Properties dialogue.
i. Click the Separate button to display the antenna patterns of all the beams separately in the Adaptive
Beam Properties dialogue.
ii. Click the Combined button to display the combined patterns of all the beams in the Adaptive Beam Prop-
erties dialogue.
iii. Click OK to close the Adaptive Beam Properties dialogue.
Notes:
• If you opened the smart antenna properties dialogue by clicking the Browse ( ) button on
the Transmitter tab of a transmitter’s properties dialogue, these patterns will also include the
main antenna pattern, if any.
• You can use the combined antenna pattern display to understand any inconsistencies in smart
antenna results. If the gird of beams and the main antenna do not have the same gains, the
smart antenna could provide worse results than the main antenna for traffic timeslots.
a. On the General tab, you can modify the name of the smart antenna model.
b. On the Properties tab, enter the Number of Elements in the smart antenna array and select a Single Element
Pattern to be used in downlink as well as uplink.
c. Click OK to close the Optimum Beamformer Properties dialogue.
If you selected Conventional Beamformer as the Smart Antenna Model, the Conventional Beamformer Prop-
erties dialogue appears:
a. On the General tab, you can modify the name of the smart antenna model.
b. On the Properties tab, enter the Number of Elements in the smart antenna array and select a Single Element
Pattern to be used in downlink as well as uplink.
c. Click OK to close the Conventional Beamformer Properties dialogue.
8. Click OK to close the smart antenna properties dialogue.
9. Click Close to close the Smart Antenna Equipment table.
Note: Properties of external third-party smart antenna models may vary. You can access their
properties from the Smart Antenna Models folder on the Modules tab of the Explorer
window.
Note: You can select whether the TCH thresholds you define are Eb/Nt or C/I thresholds by
selecting the corresponding option in the Global Parameters tab of the Transmitters
folder’s properties dialogue. For more information, see "The Global Transmitter
Parameters" on page 852.
Note: The maximum and minimum traffic channel powers can be either absolute values or
values relative to the pilot power; this depends on the option defined on the Global
Parameters tab of the Transmitters Properties dialogue. These values have to be
manually modified when the option is changed.
8. Under Resource Units, click the Browse button ( ) to the right of the timeslot field to access the Resource
Unit Consumption dialogue. In the Resource Unit Consumption dialogue, you can enter how many OVSF
codes of each length can be used for each timeslot. This information is used to carry out network dimensioning
and to simulate the Dynamic Channel Allocation (DCA) algorithm. For information on calculating network capacity,
see "TD-SCDMA Network Capacity" on page 816. For information on the dynamic channel allocation, see "The
Monte Carlo Simulation Algorithm" on page 829.
- DL: Enter or modify the number of downlink traffic timeslots for the service.
- UL: Enter or modify the number of uplink traffic timeslots for the service.
9. Click the Required Thresholds tab. On the Required Thresholds tab, you can define downlink and uplink Eb⁄Nt or
C⁄I requirements (in dB) and the TCH thresholds (in dBm). The Eb⁄Nt, or C⁄I, quality targets are used to determine
the coverage area for the service, and the TCH thresholds must be reached to provide users with the service.
These parameters depend on the mobility type and reception equipment; these parameters must be defined for
each possible combination of mobility type and reception equipment.
Using Transmission and Reception diversity results in a quality gain on received downlink and uplink Eb⁄Nt or C⁄I.
In Atoll, this is modelled by reducing the downlink and uplink Eb⁄Nt or C⁄I requirements. Therefore, in addition to
downlink and uplink Eb⁄Nt or C⁄I requirements, you can specify gains on received downlink and uplink Eb⁄Nt or C⁄I
for each possible diversity configuration. Atoll considers them when transmission and reception diversity config-
urations are assigned to transmitters.
4. In the Equipment table, each row describes a piece of equipment. For information on working with data tables,
see "Working with Data Tables" on page 50. For the new piece of TD-SCDMA equipment you are creating, enter
the following:
- Name: The name you enter will be the one used to identify this piece of equipment.
- Manufacturer: The name of the manufacturer of this piece of equipment.
- JD factor: Joint Detection (JD) is a technology used to decrease intra-cellular interference in the uplink. JD is
modelled by a coefficient from 0 to 1; this factor is considered in the UL interference calculation. In case JD is
not supported by equipment, enter 0 as value.
- MCJD factor: Multi-Cell Joint Detection (MCJD) is used to decrease uplink interference from mobiles in other
cells. MCJD is modelled by a coefficient from 0 to 1; this factor is considered in the UL interference calculation.
In case MCJD is not supported by equipment, enter 0 as value.
5. Click the Close button ( ) to close the table.
Note: You can create a new reception equipment type by entering a name in the row marked
with the New Row icon ( ) and pressing ENTER.
- You can define several pieces of reception equipment with separate thresholds for each. You can reserve low
bearer indexes for poor-performance reception equipment and higher bearer indexes for high-performance
equipment.
- You can specify bearer selection thresholds for each mobility. You can reserve low bearer indexes for high
speeds and higher bearer indexes for low speeds.
- You can also give priority to either one user by assigning him a high bearer index or to all users by assigning
them low bearer indexes.
8. Click OK to close the reception equipment type’s Properties dialogue.
- DL Eb⁄Nt or C⁄I: The DL Eb⁄Nt or C⁄I standard deviation. Atoll will display the DL Eb⁄Nt or C⁄I shadowing
margin.
- UL Eb⁄Nt or C⁄I: The UL Eb⁄Nt or C⁄I standard deviation. Atoll will display the UL Eb⁄Nt or C⁄I shadowing
margin
5. Click Calculate. The calculated shadowing margin is displayed.
6. Click Close to close the dialogue.
The maximum system range is half the distance that the RF signal can travel in DGP:
8
R System = 75 μs × 3 × 10 m/s- = 11250 m
----------------------------------------------------
2
Atoll
RF Planning and Optimisation Software
Chapter 13: WiMAX BWA Networks
Tip: Before working with the Atoll WiMAX module for the first time, it is highly recommended
to go through the "Glossary of WiMAX Terms" on page 995. This will help you get
accustomed to the terminology used in Atoll.
4. Allocate neighbours ( 4 ).
- "Planning Neighbours" on page 920.
5. Allocate frequencies ( 5 ).
- "Planning Frequencies" on page 929.
7. Before making more advanced coverage predictions, you need to define cell load conditions ( 7 ).
You can define cell load conditions in the following ways:
- You can generate realistic cell load conditions by creating a simulation based on traffic maps and subscriber
lists ( 7a , 7b , and 7c ) (see "Studying Network Capacity" on page 937).
- You can define cell load conditions manually either on the Cells tab of each transmitter’s Properties dialogue
or in the Cells table (see "Creating or Modifying a Cell" on page 875) ( 7d ).
8. Make WiMAX-specific signal quality coverage predictions using the defined cell load conditions ( 8 ).
- "WiMAX Coverage Predictions" on page 904.
9. If necessary, modify network parameters to study the network with a different frequency plan ( 10 ). After modifying
the network’s frequency plan, you must perform steps 7 and 8 again.
6
7a
7c 7d
7b
7
9 10
Atoll enables you to model network traffic by allowing you to create services, users, user profiles, environments, and termi-
nals. This data can be then used to make studies that depend on network load, such as C/(I+N), WiMAX radio bearer, and
throughput coverage predictions.
In this section, the following are explained:
• "Creating a WiMAX Base Station" on page 869.
• "Creating a Group of Base Stations" on page 881.
• "Modifying Sites and Transmitters Directly on the Map" on page 882.
• "Display Tips for Base Stations" on page 882.
• "Creating a Multi-Band WiMAX Network" on page 882.
• "Setting the Working Area of an Atoll Document" on page 882.
• "Studying a Single Base Station" on page 883.
• "Studying Base Stations" on page 886.
• "Planning Neighbours" on page 920.
• "Planning Frequencies" on page 929.
• "Planning Preamble Indexes" on page 933.
Tip: While this method allows you to place a site with precision, you can also place sites using
the mouse and then position them precisely with this dialogue afterwards. For information
on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 31.
- Altitude: The altitude, as defined by the DTM for the location specified under Position, is given here. You can
specify the actual altitude under Real, if you wish. If an altitude is specified here, Atoll will use this value for
calculations.
- Comments: You can enter comments in this field if you wish.
- Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are dis-
played in red in the Transmitters folder of the Data tab.
Note: Only active transmitters are taken into consideration during calculations.
- Transmitter Type: If you want Atoll to consider the transmitter as a potential server as well as an interferer,
set the transmitter type to Intra-Network (Server and Interferer). If you want Atoll to consider the transmitter
only as an interferer, set the type to Extra-Network (Interferer Only). No coverage for an Interferer Only
transmitter will be calculated for coverage predictions and it will not serve any mobile in Monte Carlo simula-
tions.
This feature enables you to model the co-existence of different networks in the same geographic area. For
more information on how to study interference between co-existing networks, see "Modelling the Co-existence
of Networks" on page 995.
- Transmission/Reception: Under Transmission/Reception, you can see the total losses and the noise
figure of the transmitter. Atoll calculates losses and noise according to the characteristics of the equipment
assigned to the transmitter. Equipment can be assigned using the Equipment Specifications dialogue which
appears when you click the Equipment button.
- On the Equipment Specifications dialogue (see Figure 13.4), the equipment you select and the gains and
losses you define are used to initialise total transmitter losses in the uplink and downlink:
- TMA: You can select a tower-mounted amplifier (TMA) from the list. You can click the Browse button
( ) to access the properties of the TMA. For information on creating a TMA, see "Defining TMA Equip-
ment" on page 147.
- Feeder: You can select a feeder cable from the list. You can click the Browse button ( ) to access the
properties of the feeder. For information on creating a feeder cable, see "Defining Feeder Cables" on
page 147.
- BTS: You can select a base transceiver station (BTS) equipment from the BTS list. You can click the
Browse button ( ) to access the properties of the BTS. For information on creating a BTS, see "Defin-
ing BTS Equipment" on page 148.
- Feeder Length: You can enter the feeder length at transmission and reception.
- Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value
you enter must be positive.
- Receiver Antenna Diversity Gain: You can enter a receiver antenna diversity gain. The value you enter
must be positive.
Atoll always considers the values in the Real boxes in coverage predictions even if they are different from the
values in the Computed boxes. The information in the real Total Noise Figure reception box is calculated
from the information you entered in the Equipment Specifications dialogue. You can modify the real Total
Losses at transmission and reception and the real Total Noise Figure at reception if you wish. Any value you
enter must be positive.
- Antennas:
- Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added
to the altitude of the site as given by the DTM. If the transmitter is situated on a building, the height entered
must include the height of building.
- Power Combining Gain: The Power Combining Gain is calculated automatically depending on the
number of antenna elements of the smart antenna equipment, if any, assigned to the transmitter. This gain
is applied to the downlink transmission power for preamble and other signals transmitted using the main
antenna.
- Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the
Browse button ( ) to access the properties of the antenna. The other fields, Azimuth, Mechanical
Downtilt, and Additional Electrical Downtilt, display additional antenna parameters. The mechanical
and additional electrical downtilts defined for the main antenna are also used for the calculations using the
smart antenna equipment.
- Smart Antenna: Under Smart Antenna, the available smart antenna equipment is available in the Equip-
ment list. You can click the Browse button ( ) to access the properties of the smart antenna equip-
ment. When you select a smart antenna equipment, you can choose whether to keep the current main
antenna model or to replace it with the main antenna model defined for the selected smart antenna equip-
ment, if any. For more information on smart antenna equipment, see "Defining Smart Antenna Equipment"
on page 983.
- Number of MIMO Antennas: Enter the number of antennas used for MIMO in the Transmission and
Reception fields. For more information on how the number of MIMO antennas are used, see "Multiple
Input Multiple Output Systems" on page 984.
- Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power, which is
the percentage of power reserved for this particular antenna. For example, for a transmitter with one
secondary antenna, if you reserve 40 % of the total power for the secondary antenna, 60 % is available
for the main antenna.
For information on working with data tables, see "Working with Data Tables" on page 50.
The main antenna is used to transmit the preamble. Coverage predictions based on the preamble signal are
performed using the main antenna. The main antenna is also used for traffic signals if there is no smart antenna
equipment selected for the transmitter, or if the cell (or permutation zones in WiMAX 802.16e) does not support
AAS.
If there is smart antenna equipment assigned to the transmitter and the cell (or permutation zones in WiMAX
802.16e) supports AAS, traffic data is transmitted and received using the smart antenna, whereas the preamble
is transmitted using the main antenna.
When you create a transmitter, Atoll reminds you to create a cell for the transmitter. The following explains the parameters
of a WiMAX cell. As you create a cell, Atoll calculates appropriate values for some fields based on the information you
have entered. You can, if you wish, modify these values.
The properties of a WiMAX cell are found on Cells tab of the Properties dialogue of the transmitter to which it is assigned.
The Cells tab has the following options:
• Name: By default, Atoll names the cell after its transmitter, adding a suffix in parentheses. If you change trans-
mitter name, Atoll does not update the cell name. You can enter a name for the cell, but for the sake of consist-
ency, it is better to let Atoll assign a name. If you want to change the way Atoll names cells, see The Administrator
Manual.
• BSID: The Base Station ID.
• Active: If this cell is to be active, you must select the Active check box.
• Order: The order of the cell among all the cells of the transmitter. It must be a positive integer value. This value is
automatically assigned when you create a new cell, but it is possible to modify it afterwards. The order is used
during calculations for selecting the service cell. For more information on the different cell selection options, see
"The Global Transmitter Parameters" on page 972.
• Frequency Band: The cell’s frequency band from the Frequency Band list.
• Channel Number: The number of the channel from the list of available channels.
• Channel Allocation Status: The status of the current channel allocated to the cell:
- Not Allocated: The current channel has neither been allocated automatically nor manually. The AFP con-
siders that a Not Allocated channel is modifiable.
- Allocated: The current channel has been allocated automatically or manually. The AFP considers that an
Allocated preamble index is modifiable but it is not modified unless absolutely necessary.
- Locked: The current channel has been allocated automatically or manually. The AFP considers that a Locked
channel is not modifiable.
• Min Reuse Distance: The minimum reuse distance after which the channel assigned to this cell can be assigned
to another cell by the AFP. The reuse distance is also used by the automatic preamble index allocation in 802.16e.
The cell’s preamble index can be allocated to another cell outside this reuse distance without any cost.
• Preamble Power (dBm): The cell’s transmission power over the preamble of the frame.
• Traffic Power Reduction (dB): The power reduction to be subtracted from the power defined in the Preamble
Power (dBm) field to determine the transmission power of the traffic subcarriers during the loaded part of the
frame. Traffic subcarriers are off during the empty part of the frame.
• Pilot Power Reduction (dB): The power reduction to be subtracted from the power defined in the Preamble
Power (dBm) field to determine the transmission power of the pilot subcarriers during the loaded part of the frame.
• Idle Pilot Power Reduction (dB): The power reduction to be subtracted from the power defined in the Preamble
Power (dBm) field to determine the transmission power of the pilot subcarriers during the empty part of the frame.
If the cell’s transmitter has a smart antenna equipment assigned, the transmission power of cell increases by
10 × Log ( n ) (in dB), where n is the number of antenna elements of the smart antenna. This gain in the transmis-
sion power is referred to as the power combination gain.
• WiMAX Equipment: You can select the cell’s WiMAX equipment from the WiMAX Equipment list. For more infor-
mation, see "Defining WiMAX Equipment" on page 978. The cell’s WiMAX equipment parameters are used in the
uplink calculations.
• Scheduler: The scheduler used by the cell for resource allocation during Monte Carlo simulations. You can select
the scheduler from the list of schedulers available in the Schedulers table. For more information see "Defining
WiMAX Schedulers" on page 980.
• Max Number of Users: The maximum number of simultaneous users supported by the cell.
• Preamble C/N Threshold (dB): The minimum preamble C/N required for a user to be connected to the cell. The
preamble C/N is compared with this threshold to determine whether or not a user can be connected to a cell.
• AMS/MU-MIMO Threshold (dB): For AMS, it is the preamble C/N threshold for switching from SU-MIMO to STTD/
MRC as the preamble signal conditions get worse than the given value. For MU-MIMO, it is the minimum required
preamble CNR for using MU-MIMO. For more information on Adaptive MIMO switching, see "Multiple Input Mul-
tiple Output Systems" on page 984.
• Max Traffic Load (UL) (%): The uplink traffic load not to be exceeded. This limit can be taken into account during
Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have an uplink
traffic load greater than this maximum.
• Traffic Load (UL) (%): The uplink traffic load percentage. By default, the uplink traffic load is set to 100%.
• Max Traffic Load (DL) (%): The downlink traffic load not to be exceeded. This limit can be taken into account
during Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have a
downlink traffic load greater than this maximum.
• Traffic Load (DL) (%): The downlink traffic load percentage. By default, the downlink traffic load is set to 100%.
• UL Noise Rise (dB): The uplink noise rise in dB. By default, the uplink noise rise is set to 0.
Note: You can set the values for uplink and downlink traffic loads, and the uplink noise rise
manually to actual network values, or use the values computed during Monte Carlo
simulations. Monte Carlo simulation results can be stored in the cells by clicking the
Commit Results button in the simulation results dialogue.
• AAS Usage (DL) (%): This is the percentage of the total downlink traffic load that corresponds to the traffic loads
of the users supported by the smart antenna equipment. For example, if the downlink traffic load is 80%, and you
set the AAS usage to 50%, it means that 40% downlink traffic load is supported by the smart antenna equipment
while the other 40% is supported by the main antenna. AAS usage is calculated during Monte Carlo simulations,
and cannot be modified manually because the AAS usage values correspond to the AAS simulation results dia-
grams.
• AAS Simulation Results: This field stores the simulation results generated for transmitters using a smart
antenna. During the Monte Carlo simulations, both smart antenna models available in Atoll, conventional beam-
former and optimum beamformer, perform beamforming in downlink. In uplink, the conventional beamformer per-
forms beamforming only whereas the optimum beamformer uses the MMSE (Minimum Mean Square Error)
algorithm for cancelling interference. After the simulations, the smart antenna results can be stored in the cell prop-
erties. The results stored in this field are the angular distributions of the downlink traffic power spectral density and
the uplink noise rise. You can view these patterns in the Cells table. You can make the display of the downlink
results diagram take into account the effect of the antenna pattern of the single element. For more information,
see the Administrator Manual.
• MU-MIMO Gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO. This can be user-defined
or an output of Monte Carlo simulations. In uplink throughput coverage predictions, the cell capacity will be multi-
plied by this gain at pixels where MU-MIMO is used.
The following parameters are only available in WiMAX 802.16d documents.
• Diversity Support (DL): The type of antenna diversity technique (AAS, STTD/MRC, SU-MIMO, and AMS) sup-
ported by the cell in downlink. You cannot select more than one type of MIMO technique (STTD/MRC, SU-MIMO,
and AMS) at a time.
• Diversity Support (UL): The type of antenna diversity technique (AAS, STTD/MRC, SU-MIMO, AMS, MU-MIMO)
supported by the cell in uplink. You cannot select more than one type of MIMO technique (STTD/MRC, SU-MIMO,
MU-MIMO, and AMS) at a time.
Specific calculations will be performed (gains will be applied) for terminals supporting AAS and MIMO. A cell that
only supports None does not have any antenna diversity mechanism, and all the terminal types can connect to
this cell. A cell that supports None and one or more antenna diversity techniques can also support terminals capa-
ble of those diversity techniques. For example, None+AAS can support simple as well as AAS-capable terminals,
and None+AMS can support simple and MIMO-capable terminals. Simple terminals cannot connect to a cell that
does not support None.
• Max Number of Intra-technology Neighbours: The maximum number of neighbours from within the same Atoll
document that the cell can have.
• Max Number of Inter-technology Neighbours: The maximum number of neighbours from other technology doc-
uments that the cell can have.
• Neighbours: You can access a dialogue in which you can set both intra-technology and inter-technology neigh-
bours by clicking the Browse button ( ). For information on defining neighbours, see "Planning Neighbours"
on page 920.
Tip: The Browse button ( ) might not be visible in the Neighbours box if this is a new cell.
You can make the Browse button appear by clicking Apply.
Tips:
• If you are creating several transmitters at the same time, or modifying several existing trans-
mitters, you can do it more quickly by editing or pasting the data directly in the Transmitters
table. You can open the Transmitters table by right-clicking the Transmitters folder on the
Data tab of the Explorer window and selecting Open Table from the context menu. For infor-
mation on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
• If you want to add a transmitter to an existing site on the map, you can add the transmitter by
right-clicking the site and selecting New Transmitter from the context menu.
Tips:
• If you are creating or modifying several cells at the same time, you can do it more quickly by
editing the data directly in the Cells table. You can open the Cells table by right-clicking the
Transmitters folder on the Data tab of the Explorer window and selecting Cells > Open
Table from the context menu. You can either edit the data in the table, paste data into the table
(see "Copying and Pasting in Tables" on page 56), or import data into the table (see "Importing
Tables from Text Files" on page 59).
• If you want to add a cell to an existing transmitter on the map, you can add the cell by right-
clicking the transmitter and selecting New Cell from the context menu.
3. In the map window, move the pointer over the map to where you would like to
place the new station. The exact coordinates of the pointer’s current location
are visible in the Status bar.
Tips:
• To place the base station more accurately, you can zoom in on the map before you click the
New Station button. For information on using the zooming tools, see "Changing the Map
Scale" on page 38.
• If you let the pointer rest over the base station you have placed, Atoll displays its tip text with
its exact coordinates, allowing you to verify that the location is correct.
You can also place a series of base stations using a station template. You do this by defining an area on the map where
you want to place the base stations. Atoll calculates the placement of each base station according to the defined hexag-
onal cell radius in the station template. For information on defining the cell radius, see "Creating or Modifying a Station
Template" on page 877.
2. Click the Hexagonal Design button ( ), to the left of the template list. A hexagonal design is a group of base
stations created from the same station template.
Note: If the Hexagonal Design button is not available ( ), the hexagonal cell radius for this
template is not defined. For information on defining the cell radius, see "Creating or
Modifying a Station Template" on page 877.
3. Draw a zone delimiting the area where you want to place the series of base stations:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
Atoll fills the delimited zone with new base stations and their hexagonal shapes. Base station objects such as
sites and transmitters are also created and placed into their respective folders.
You can work with the sites and transmitters in these base stations as you work with any base station object, adding, for
example, another antenna to a transmitter.
When you place a new station using a station template as explained in "Placing a New Base Station Using a Station
Template" on page 876, the site is created at the same time as the station. However, you can also place a new station on
an existing site.
To place a base station on an existing site:
1. On the Data tab, clear the display check box beside the Hexagonal Design folder.
2. In the Radio toolbar, select a template from the list.
to offer complete coverage of the area, the Mechanical Downtilt, and the Additional Electrical Downtilt for
the antennas.
Under Smart Antenna, you can select the smart antenna Equipment used by the transmitter, and under
Number of MIMO Antennas, you can enter the number of antennas used for Transmission and for Recep-
tion for MIMO.
- Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both
the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Managing
Calculations in Atoll.
5. Click the Transmitter tab. In this tab (see Figure 13.7), if the Active check box is selected, you can modify the
following:
- Under Transmission/Reception, you can click the Equipment button to open the Equipment Specifica-
tions dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or base transceiver station
(BTS). For information on the Equipment Specifications dialogue, see "Transmitter Description" on
page 870.
The information in the computed Total Losses in transmission and reception boxes is calculated from the in-
formation you entered in the Equipment Specifications dialogue (see Figure 13.4 on page 872). Atoll al-
ways considers the values in the Real boxes in coverage predictions even if they are different from the values
in the Computed boxes. You can modify the real Total Losses at transmission and reception if you wish. Any
value you enter must be positive.
The information in the computed BTS Noise Figure reception box is calculated from the information you en-
tered in the Equipment Specifications dialogue. You can modify the real BTS Noise Figure at reception if
you wish. Any value you enter must be positive.
6. Click the WiMAX tab. In this tab (see Figure 13.8), you can modify the following:
- Under Powers, you can modify the Preamble Power, and the power reductions for the data and pilot subcar-
riers in Traffic Power Reduction, Pilot Power Reduction, and Idle Pilot Power Reduction.
- Frequency Band, Channel Number, Channel Allocation Status, Preamble Index (WiMAX 802.16e), Pre-
amble Index Status (WiMAX 802.16e), Min Reuse Distance, WiMAX Equipment, Scheduler, Max Number
of Users, Frame Configuration (WiMAX 802.16e), Preamble C/N Threshold, AMS/MU-MIMO Threshold
(WiMAX 802.16e), and the default MU-MIMO Gain (WiMAX 802.16e).
- Under Antenna Diversity in WiMAX 802.16d documents, you can select the Diversity Support in downlink
and in uplink. You cannot select more than one type of MIMO technique (STTD/MRC, SU-MIMO, MU-MIMO,
and AMS) at a time. You can also enter the AMS/MU-MIMO Threshold and the default MU-MIMO Gain.
- Under Default Loads, you can enter the default values for DL Traffic Load, UL Traffic Load, UL Noise Rise,
and the Max DL Traffic Load and Max UL Traffic Load. You can also enter the DL Segmentation Usage in
WiMAX 802.16e.
- Under Inter-technology Interference, you can set the DL Noise Rise and the UL Noise Rise. For more infor-
mation on inter-technology interference, see "Modelling Inter-Network Interferences" on page 236.
- Under Max Number of Neighbours in WiMAX 802.16e documents, you can set the maximum numbers of
Intra-technology and Inter-technology neighbours.
Figure 13.8: Station Template Properties dialogue – WiMAX tab (WiMAX 802.16e)
7. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the
Sites table, or if you have defined an additional field in the Station Template Properties dialogue.
8. When you have finished setting the parameters for the station template, click OK to close the dialogue and save
your changes.
5. In the map window, move the pointer over the map to where you would like to place the new base station. The
exact coordinates of the pointer’s current location are visible in the Status bar.
Tips:
• To place the station more accurately, you can zoom in on the map before you select Duplicate
from the context menu. For information on using the zooming tools, see "Changing the Map
Scale" on page 38.
• If you let the pointer rest over the station you have placed, Atoll displays tip text with its exact
coordinates, allowing you to verify that the location is correct.
You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to
place each duplicate station.
For more information on the site, transmitter, and cell properties, see "Definition of a Base Station" on page 869.
Note: When you import data into your current Atoll document, the coordinate system of the
imported data must be the same as the display coordinate system used in the document.
If you cannot change the coordinate system of your source data, you can temporarily
change the display coordinate system of the Atoll document to match the source data.
For information on changing the coordinate system, see "Setting a Coordinate System"
on page 92.
Important: The table you copy from must have the same column layout as the table you are pasting
data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
• Importing data: If you have base station data in text or comma-separated value (CSV) format, you can import it
into the tables in the current document. If the data is in another Atoll document, you can first export it in text or
CSV format and then import it into the tables of your current Atoll document. When you are importing, Atoll allows
you to select what values you import into which columns of the table.
When you create a group of base stations by importing data, you must import site data in the Sites table, trans-
mitter data in the Transmitters table, and cell data in the Cells table, in that order.
For information on exporting table data, see "Exporting Tables to Text Files" on page 58. For information on
importing table data, see "Importing Tables from Text Files" on page 59.
Note: You can quickly create a series of base stations for study purposes using the Hexagonal
Design tool on the Radio toolbar. For information, see "Placing a New Base Station
Using a Station Template" on page 876.
( and ). For information on defining the transmitter symbol, see "Defining the Display Type" on page 34.
It is important not to confuse the computation zone and the focus zone or hot spot zones. The computation zone
defines the area where Atoll computes path loss matrices, coverage predictions, Monte Carlo simulations, etc.,
while the focus zone or hot spot zones are the areas taken into consideration when generating reports and results.
For information on the computation zone, see "Creating a Computation Zone" on page 891.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be
studied.
2. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the fol-
lowing:
- Move the receiver to change the current position.
- Click to place the receiver at the current position. You can move the receiver again by clicking it a second time.
- Right-click the receiver to choose one of the following commands from the context menu:
- Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates.
- Target Site: Select a site from the list to place the receiver directly on a site.
4. Click the Profile tab.
The profile analysis appears in the Profile tab of the Point Analysis Tool window. The altitude is reported on the
vertical axis and the receiver-transmitter distance on the horizontal axis. A blue ellipsoid indicates the Fresnel zone
between the transmitter and the receiver, with a green line indicating the line of sight (LOS). Atoll displays the
angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an obstacle, this
causes attenuation with diffraction displayed by a red vertical line (if the propagation model used takes diffraction
mechanisms into account). The main peak is the one that intersects the most with the Fresnel ellipsoid. With some
propagation models using a 3 knife-edge Deygout diffraction method, the results may display two additional atten-
uations peaks. The total attenuation is displayed above the main peak.
The results of the analysis are displayed at the top of the Profile tab:
- The received signal strength from the selected transmitter for the cell with the highest preamble power
6. To end the point analysis, click the Point Analysis Tool ( ) in the Radio toolbar again.
Note: You can use the same procedure to study the signal level coverage of several base
stations by grouping the transmitters. For information on grouping transmitters, see
"Grouping Data Objects by a Selected Property" on page 65.
Tip: If you wish to study only sites by their status, at this step you could group them by status.
5. Select Coverage by Signal Level and click OK. A study properties dialogue appears.
6. You can configure the following parameters in the Properties dialogue:
- General tab: You can change the assigned Name of the coverage prediction, the Resolution, and the storage
Folder for the coverage prediction, and add some Comments. The resolution you set is the display resolution,
not the calculation resolution.
To improve memory consumption and optimise the calculation times, you should set the display resolutions of
coverage predictions according to the precision required. The following table lists the levels of precision that
are usually sufficient:
City Centre 5m
City 20 m
County 50 m
State 100 m
Note: If you create a new coverage prediction from the context menu of either the Transmitters
or Predictions folder, you can select the sites using the Group By, Sort, and Filter
buttons under Configuration. Because you already selected the target sites, however,
only the Filter button is available.
- Condition tab: The coverage prediction parameters on the Condition tab allow you to define the signals that
will be considered for each pixel (see Figure 13.11).
- At the top of the Condition tab, you can set the signal level range to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the
same results because Atoll displays the results of the best server in either case. Selecting "Best Signal
Level" necessitates, however, a longer time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that
Atoll will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage
Probability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- Display tab: You can modify how the results of the coverage prediction will be displayed.
- Under Display Type, select "Value Intervals."
- Under Field, select "Best signal level."
- You can change the value intervals and their displayed colour. For information on changing display prop-
erties, see "Display Properties of Objects" on page 33.
- You can create a tooltip with information about the coverage prediction by clicking the Browse button
( ) beside the Tip Text box and selecting the fields you want to display in the tooltip.
- You can select the Add to Legend check box to add the displayed value intervals to the legend.
Note: If you change the display properties of a coverage prediction after you have calculated it,
you may make the coverage prediction invalid. You will then have to recalculate the
coverage prediction to obtain valid results.
7. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The signal level
coverage prediction can be found in the Predictions folder on the Data tab. Atoll automatically locks the results of a cover-
age prediction as soon as it is calculated, as indicated by the icon ( ) beside the coverage prediction in the Predictions
folder. When you click the Calculate button ( ), Atoll only calculates unlocked coverage predictions ( ).
Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices
using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main prop-
agation model with a shorter radius (displayed with a blue square in Figure 13.12) and a higher resolution and an extended
propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate
higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower reso-
lution path loss matrices outside the area covered by the main propagation model.
In this section, the following are explained:
• "Path Loss Matrices" on page 887.
• "Assigning a Propagation Model" on page 889.
• "The Calculation Process" on page 891.
• "Creating a Computation Zone" on page 891.
• "Setting Transmitters or Cells as Active" on page 891.
• "Signal Level Coverage Predictions" on page 892.
• "Analysing a Coverage Prediction" on page 896.
• "WiMAX Coverage Predictions" on page 904.
• "Printing and Exporting Coverage Prediction Results" on page 920.
Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matri-
ces in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning
projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case
of large radio-planning projects, saving your path loss matrices externally will help reduce the size of the file and the use
of computer resources.
The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same
radio-planning project. In this case, the radio data is stored in a database and the path loss matrices are read-only and are
stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices,
the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These
will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more
information on working in a multi-user environment, see the Administrator Manual.
When you save the path loss matrices to an external directory, Atoll creates:
• One file per transmitter with the extension LOS for its main path loss matrix.
• A DBF file with validity information for all the main matrices.
• A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
To set the storage location of the path loss matrices:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss
matrices and the location for the shared path loss matrices:
- Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are
loading path loss matrices from a shared location, where you store your changes to shared path loss matrices.
Click the button beside the Private Directory ( ) and select Embedded to save the path loss matrices in
the Atoll document, or Browse to select a directory where Atoll can save the path loss matrices externally.
Note: Path loss matrices you calculate locally are not stored in the same directory as shared
path loss matrices. Shared path loss matrices are stored in a read-only directory. In other
words, you can read the information from the shared path loss matrices but any changes
you make will be stored locally, either embedded in the ATL file or in a private external
folder, depending on what you have selected in Private Directory.
Caution: When you save the path loss files externally, the external files are updated as soon as
calculations are performed. In order to keep consistency between the Atoll document and
the stored calculations, you should save the Atoll document before closing it if you have
updated the path loss matrices.
- Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a
database and the path loss matrices are stored in a directory that is accessible to all users. Any changes you
make will not be saved to this directory; they will be saved in the location indicated in Private Directory. The
path loss matrices in the shared directory are updated by a user with administrator rights based on the updated
information in the database. For more information on shared directories, see the Administrator Manual.
5. Click OK.
Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want,
you can check whether the path loss matrices are valid without creating a coverage prediction.
To check whether the path loss matrices are valid:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. You have the
following display options:
- Display all the matrices: All path loss matrices are displayed.
- Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available Results table lists the following information for each displayed path loss matrix:
2. If you have assigned a propagation model globally to all transmitters, as explained in "Assigning a Propagation
Model to All Transmitters" on page 889, this is the propagation model that will be used for all transmitters, except
for those to which you have assigned a propagation model either individually or as part of a group.
Important: When you assign a propagation model globally, you override any selection you might
have made to an individual transmitter or to a group of transmitters.
3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default
Propagation Model" on page 187, this is the propagation model that will be used for all transmitters whose main
propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main prop-
agation model, that is the propagation model that will be used.
In this section, the following are explained:
• "Assigning a Propagation Model to All Transmitters" on page 889.
• "Assigning a Propagation Model to a Group of Transmitters" on page 890.
• "Assigning a Propagation Model to One Transmitter" on page 890.
For more information about the available propagation models, see Chapter 5: Managing Calculations in Atoll.
Transmitters that share the same parameters and environment will usually use the same propagation model and settings.
In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common
parameters and then assigning the propagation model.
To define a main and extended propagation model for a defined group of transmitters:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select from the Group by submenu of the context menu the property by which you want to group the transmitters.
The objects in the folder are grouped by that property.
Note: You can group transmitters by several properties by using the Group By button on the
Properties dialogue. For more information, see "Advanced Grouping" on page 66.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model
to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmit-
ters.
When you assign a main and extended propagation model to a single transmitter, it overrides any changes you have previ-
ously made globally.
To define a main and extended propagation model for all transmitters:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Transmitters folder.
3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu
appears.
4. Select Properties from the context menu. The Properties dialogue appears.
5. Click the Propagation tab.
6. Under Main Matrix:
- Select a Propagation Model.
- Enter a Radius and Resolution.
7. If desired, under Extended Matrix:
- Select a Propagation Model.
- Enter a Radius and Resolution.
8. Click OK. The selected propagation models will be used for the selected transmitter.
Note: You can also define the propagation models for a transmitter by right-clicking it in the map
window and selecting Properties from the context menu.
Notes:
• You can stop any calculations in progress by clicking the Stop Calculations button ( ) in
the toolbar.
• When you click the Force Calculation button ( ) instead of the Calculate button, Atoll cal-
culates all path loss matrices, unlocked coverages, and pending simulations.
You can also create a computation zone with one of the following methods:
• Existing polygon: You can use any existing polygon on the map as a computation zone by right-clicking it and
selecting Use as Computation Zone from the context menu.
• Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a computation zone. You can import it by right-clicking the Computa-
tion Zone folder on the Geo tab and selecting Import from the context menu.
• Fit to Map Window: You can create a computation zone the size of the map window by right-clicking the Com-
putation Zone folder on the Geo tab and selecting Fit to Map Window from the context menu.
Note: You can save the computation zone in the user configuration. For information on
exporting the computation zone in the user configuration, see "Exporting a User
Configuration" on page 75.
You can set an individual transmitter as active from its context menu or you can set more than one transmitter as active
by activating them from the Transmitters context menu, by activating the transmitters’ cells from the Cells table, or by
selecting the transmitters with a zone and activating them from the zone’s context menu.
To set an individual transmitter as active:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the Transmitters folder.
3. Right-click the transmitter you want to activate. The context menu appears.
4. Select Active Transmitter from the context menu. The transmitter is now active.
To set more than one transmitter as active using the Transmitters context menu:
1. Click the Data tab of the Explorer window.
2. Select the transmitters you want to set as active:
- To set all transmitters as active, right-click the Transmitters folder. The context menu appears.
- To set a group of transmitters as active, click the Expand button ( ) to expand the Transmitters folder and
right-click the group of transmitters you want to set as active. The context menu appears.
3. Select Activate Transmitters from the context menu. The selected transmitters are set as active.
To set more than one transmitter as active using the Transmitters table:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Open Table. The Transmitters table appears with each transmitter’s parameters in a row.
4. For each transmitter that you want to set as active, select the check box in the Active column.
To set more than one cell as active using the Cells table:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Open Table. The Cells table appears with each cell’s parameters in a row.
4. For each cell that you want to set as active, select the check box in the Active column.
To set transmitters as active using a zone:
1. Click the Geo tab of the Explorer window.
2. Click the Expand button ( ) to the left of Zones folder to expand the folder.
3. Right-click the folder of the zone you will use to select the transmitters. The context menu appears.
Note: If you do not yet have a zone containing the transmitters you want to set as active, you
can draw a zone as explained in "Using Zones in the Map Window" on page 41.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active.
Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on
choosing and configuring a propagation model, see Chapter 5: Managing Calculations in Atoll.
Calculating path loss matrices can be time and resource intensive when you are working on larger projects. Consequently,
Atoll offers you the possibility of distributing path loss calculations on several computers. You can install the distributed
calculation server application on other workstations or on servers. Once the distributed calculation server application is
installed on a workstation or server, the computer is available for distributed path loss calculation to other computers on
the network. For information on setting up the distributed calculation server application, see the Administrator Manual.
6. Click the Condition tab (see Figure 13.14). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same
results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level"
necessitates, however, the longest time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll
will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 13.15).
6. Click the Condition tab (see Figure 13.16). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same
results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level"
necessitates, however, the longest time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll
will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 13.17).
6. Click the Condition tab (see Figure 13.18). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same
results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level"
necessitates, however, the longest time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll
will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 13.19).
1. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
2. At the bottom of the Point Analysis Tool window, click the Reception tab (see Figure 13.21).
The predicted signal level from different transmitters is reported in the Reception tab in the form of a bar chart,
from the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the
colour of the transmitter it represents. For a transmitter with more than one cell, the signal level is calculated for
the cell with the highest preamble power.
In the Map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they
represent. A thick black line from the pointer to its best server is also displayed in the map window. The best server
of the pointer is the transmitter from which the pointer receives the highest signal level. If you let the pointer rest,
the signal level received from the corresponding transmitter at the pointer location is displayed in the tool-tip.
3. Right-click the Reception tab and select Properties from the context menu. The Analysis Properties dialogue
appears.
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and
select "From Model" from the Shadowing Margin list.
- Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class.
4. To end the point analysis, click the Point Analysis Tool ( ) in the Radio toolbar again.
13.2.8.7.4 Creating a Focus or Hot Spot Zone for a Coverage Prediction Report
The focus and hot spot zones define the area on which statistics can be drawn and on which reports are made. While you
can only have one focus zone, you can define several hot spot zones in addition to the focus zone.
It is important not to confuse the computation zone and the focus and hot spot zones. The computation zone defines the
area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo simulations, etc., while the focus and
hot spot zones are the areas taken into consideration when generating reports and results. When you create a coverage
prediction report, it gives the results for the focus zone and for each of the defined hot spot zones.
To define a focus zone or hot spot zone:
1. Click the Geo tab in the Explorer window.
2. Click the Expand button ( ) to expand the Zones folder.
3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or
a hot spot. The context menu appears.
4. Select Draw from the context menu.
5. Draw the focus or hot spot zone:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zone’s
visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but
will still be taken into account.
You can also create a focus or hot spot zone as follows:
• Existing polygon: You can use any existing polygon on the map as a focus zone by right-clicking it and selecting
Use as Focus Zone from the context menu.
Note: You can only create a focus zone, and not a hot spot zone, from an existing polygon.
• Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus
Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot
spot zones, you can import the name given to each zone as well.
• Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map
Window from the context menu.
Notes: You can save the focus or hot spot zones so that you can use them in a different Atoll
document:
- You can save the focus zone in the user configuration. For information on exporting the
focus zone in the user configuration, see "Exporting a User Configuration" on page 75.
- You can right-click the Focus Zone folder or the Hot Spot Zones folder on the Data
tab of the Explorer window and select Export from the context menu.
You can include population statistics in the focus or hot spot zone by importing a
population map. For information on importing maps, see "Importing a Raster-format Geo
Data File" on page 107.
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
a. Under Configuration, click the Import button. The Open dialogue appears.
b. Select the configuration you want to import and click Open. The imported report configuration is applied
6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed
dialogue. The coverage prediction report table appears. The report is based on the hot spot zones and on the
focus zone if available or on the hot spot zones and computation zone if there is no focus zone.
To display a report on all coverage predictions:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears.
4. Define the format and content of the report:
You can select the columns that will be displayed in the report and define the order they are in:
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
Atoll saves the names of the columns you select and will automatically select them the next time you create a
coverage prediction report.
5. Click OK.
If you have created a custom data map with integrable data, the data can be used in prediction reports. The data will be
summed over the coverage area for each item in the report (for example, by transmitter or threshold). The data can be
value data (revenue, number of customers, etc.) or density data (revenue/km², number of customers/km², etc.). Data is
considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example,
socio-demographic classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable
Versus Non Integrable Data" on page 124.
In this section, there are two examples to explain how you can compare two similar predictions. You can display the results
of the comparison study coverage in one of the following ways:
• Intersection: This display shows the area where both coverage predictions overlap (for example, pixels covered
by both coverage predictions are displayed in red).
• Union: This display shows all pixels covered by both coverage predictions in one colour and pixels covered by
only one coverage prediction in a different colour (for example, pixels covered by both predictions are red and
pixels covered by only one prediction are blue).
• Difference: This display shows all pixels covered by both coverage predictions in one colour, pixels covered by
only the first prediction with another colour and pixels covered only by the second prediction with a third colour (for
example, pixels covered by both predictions are red, pixels covered only by the first prediction only are green, and
pixels covered only by the second prediction are blue).
To compare two similar coverage predictions:
1. Create and calculate a coverage prediction of the existing network.
2. Examine the coverage prediction to see where coverage can be improved.
3. Make the changes to the network to improve coverage.
4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged).
5. Calculate the duplicate coverage prediction.
6. Compare the original coverage prediction with the new coverage prediction. Atoll displays differences in coverage
between them.
In this section, the following examples are explained:
• "Example 1: Studying the Effect of a New Base Station" on page 901
• "Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 903.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how you can verify if a newly added base station improves coverage.
A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal
Level" on page 893. The results are displayed in Figure 13.23. An area with poor coverage is visible on the right side of
the figure.
A new base station is added, either by creating the base station and adding the transmitters, as explained in "Creating a
WiMAX Base Station" on page 869, or by placing a station template, as explained in "Placing a New Base Station Using
a Station Template" on page 876. Once the new site has been added, the original coverage prediction can be recalculated,
but then it would be impossible to compare the results. Instead, the original signal level coverage prediction can be copied
by selecting Duplicate from its context menu. The copy is then calculated to show the effect of the new base station (see
Figure 13.24).
Figure 13.24: Signal level coverage prediction of network with new base station
4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes adding a new base station made, you should choose Difference.
5. Click OK to create the comparison. The comparison in Figure 13.25, shows clearly the area covered only by the
new base station.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how modifying transmitter tilt can improve coverage.
A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by
Transmitter" on page 894. The results are displayed in Figure 13.26. The coverage prediction shows that one transmitter
is covering its area poorly. The area is indicated with a red oval in the figure.
You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed
by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and
electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue.
Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it would be
impossible to compare the results. Instead, the original coverage prediction can be copied by selecting Duplicate from its
context menu. The copy is then calculated, to show how modifying the antenna tilt has affected coverage (see
Figure 13.27).
As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change
in coverage, you can compare the two predictions.
To compare two predictions:
1. Right-click one of the two predictions. The context menu appears.
2. From the context menu, select Compare with and, from the menu that opens, select the prediction you want to
compare with the first. The Comparison Properties dialogue appears.
3. Click the General tab. You can change the Name of the comparison and add Comments.
The General tab contains information about the coverage predictions being compared, including their names and
resolutions.
4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes modifying the antenna tilt made, you can choose Union. This will display all pixels
covered by both predictions in one colour and all pixels covered by only one prediction in another colour. The
increase in coverage, seen in only the second coverage prediction, will be immediately clear.
5. Click OK to create the comparison. The comparison in Figure 13.28, shows clearly the increase in coverage due
at the change in antenna tilt.
Using signal quality coverage predictions you can study the effective service coverage area and capacity of each cell in
the network. These coverage predictions depend on the interference in the network and the cell load conditions. For this
reason, the network load must be defined in order to calculate these coverage predictions.
For the purposes of these coverage predictions, each pixel is considered a non-interfering user with a defined service,
mobility type, and terminal. The following are explained in the following sections:
• "Service and User Modelling" on page 905.
This section explains the coverage predictions available for analysing the effective signal level and signal quality. The
following are explained:
• "Analysing the Effective Signal Levels" on page 907.
• "Analysing the Signal Quality" on page 909.
You can also make a point analysis using the Point Analysis window to study the effective signal level at a point. Load
conditions can be selected for the analysis as well as the characteristics of the user-definable probe receiver, i.e., a termi-
nal, a mobility, and a service:
• "Making an Effective Signal Analysis" on page 918.
Interferences coming from an external project can also be modelled and is explained in "Modelling Inter-Network Interfer-
ences" on page 236.
Modelling Services
Services are the various services available to users. These services can be either voice or data type services. This section
explains how to create a service. The following parameters are used in predictions:
• Throughput scaling factor
• Throughput offset
• Body loss
To create or modify a service:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the WiMAX Parameters folder.
3. Right-click the Services folder. The context menu appears.
4. Select New from the context menu. The Services New Element Properties dialogue appears.
Note: You can modify the properties of an existing service by right-clicking the service in the
Services folder and selecting Properties from the context menu.
5. You can edit the fields on the General tab to define the new service. Some fields depend on the type of service
you choose. You can change the following parameters.
- Name: Atoll proposes a name for the new service, but you can set a more descriptive name.
- Type: You can select either Voice or Data as the service type.
- Priority: Enter a priority for this service. "0" is the lowest priority.
- QoS Class: Select a QoS class for the service. You have the option to choose from UGS (Unsolicited Grant
Service), ErtPS (Extended Real-Time Polling Service), rtPS (Real-Time Polling Service), nrtPS (Non-Real-
Time Polling Service), and BE (Best Effort). The information about the QoS class used by any service is used
by the schedulers for resource allocation. For more information about how schedulers work in Atoll, see
"Defining WiMAX Schedulers" on page 980.
- Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity for
users accessing a voice type service during Monte Carlo simulations.
- Highest Bearer: Select the highest bearer that the service can use in the uplink and downlink. This is consid-
ered as an upper limit during bearer determination.
- Max Throughput Demand: Enter the highest throughput that the service can demand in the uplink and down-
link. This value is not considered for services UGS as the quality of service.
- Min. Throughput Demand: Enter the minimum required throughput that the service should have in order to
be available in the uplink and downlink. This value is not considered for BE services.
- Average Requested Throughput: Enter the average requested throughput for uplink and downlink. The
average requested throughput is used in a simulation during user distribution generation in order to calculate
the number of users attempting a connection.
- Application Throughput: Under Application Throughput, you can set a Scaling Factor between the appli-
cation throughput and the MAC (Medium Access Control) throughput and a throughput Offset. These param-
eters model the header information and other supplementary data that does not appear at the application level.
The application throughput parameters are used in throughput coverage predictions and for application
throughput calculation.
- Body Loss: Enter a body loss for the service. The body loss is the loss due to the body of the user. For
example, in a voice connection the body loss, due to the proximity of the user’s head, is estimated to be 3 dB.
6. Click OK.
In WiMAX, information about the receiver mobility is required for determining which bearer selection threshold and quality
graph to use from the WiMAX equipment referred to in the terminal or cell. Mobiles used at high speeds and at walking
speeds do not have the same quality characteristics. C/(I+N) requirements for different radio bearers are largely depend-
ent on mobile speed.
To create or modify a mobility type:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the WiMAX Parameters folder.
3. Right-click the Mobility Types folder. The context menu appears.
4. Select New from the context menu. The Mobility Types New Element Properties dialogue appears.
Note: You can modify the properties of an existing mobility type by right-clicking the mobility
type in the Mobility Types folder and selecting Properties from the context menu.
5. You can enter or modify the following parameters in the Mobility Types New Element Properties dialogue:
- Name: Enter a descriptive name for the mobility type.
- Average Speed: Enter an average speed for the mobility type. This field is for information only; the average
speed is not used by any calculation.
6. Click OK.
Note: Subscriber lists use the mobility type "Fixed", i.e., 0 km/hr, in calculations. Do not delete
this mobility type from the document if you are working with subscriber lists.
Modelling Terminals
In WiMAX, a terminal is the user equipment that is used in the network, for example, a mobile phone, a PDA, or a car’s
on-board navigation device.
The following parameters are used in predictions:
• Antenna
• WiMAX equipment
• Maximum and minimum terminal power
• Gain and losses
• Noise figure
• Supported antenna diversity technique
• Number of transmission and reception antennas for MIMO
To create or modify a terminal:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the WiMAX Parameters folder.
3. Right-click the Terminals folder. The context menu appears.
4. Select New from the context menu. The Terminals New Element Properties dialogue appears.
Note: You can modify the properties of an existing terminal by right-clicking the terminal in the
Terminals folder and selecting Properties from the context menu.
5. You can enter or modify the following parameters in the Terminals New Element Properties dialogue:
- Name: Enter a descriptive name for the terminal.
- Under Transmission/Reception,
- Min Power: Enter the minimum transmission power of the terminal.
- Max Power: Enter the maximum transmission power of the terminal.
- Noise Figure: Enter the noise figure of the terminal (used to calculate the downlink total noise).
- Losses: Enter the losses of the terminal.
- WiMAX Equipment: Select a WiMAX equipment from the list of available equipment. For more informa-
tion on WiMAX equipment, see "Defining WiMAX Equipment" on page 978. The terminal’s WiMAX equip-
ment parameters are used in the downlink calculations.
- Under Antenna,
- Model: Select an antenna model from the list of available antennas. If you do not select an antenna for
the terminal, Atoll uses an isotropic antenna in calculations.
Note: Keep in mind that in case you do not select an antenna, Atoll uses an isotropic antenna,
not an omni-directional antenna, in calculations. An isotropic antenna has spherical
radiation patterns in the horizontal as well as vertical planes.
- Gain: Enter the terminal antenna gain if you have not selected an antenna model in the Model field. If you
have selected an antenna, the Gain field is disabled and shows the gain of the selected antenna.
- Antenna Diversity Support: Select the type of antenna diversity techniques supported by the terminal.
Antenna diversity gains will be applied to the users using any terminal type depending on the supported
antenna diversity techniques, i.e., AAS, MIMO, or AAS+MIMO. If a terminal that supports AAS+MIMO is
connected to a cell (permutation zone in WiMAX 802.16e) that supports both antenna diversity tech-
niques, both AAS and MIMO gains will be applied.
- Number of Transmission Antennas: Under MIMO, enter the number of antennas used by the terminal
in transmission.
- Number of Reception Antennas: Under MIMO, enter the number of antennas used by the terminal in
reception.
6. Click OK.
For more information on services, terminals, mobility types, and WiMAX equipment, see "Modelling Services" on
page 905, "Modelling Terminals" on page 906, "Modelling Mobility Types" on page 906, and "Defining WiMAX
Equipment" on page 978, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
the effective signal analysis calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
Figure 13.29: Condition settings for an effective signal analysis coverage prediction
10. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 13.30
and Figure 13.31).
If you are setting the traffic loads and the uplink noise rise for a single transmitter, you can set these parameters on the
Cells tab of the transmitter’s Properties dialogue. However, you can set the traffic loads and the uplink noise rise for all
the cells using the Cells table.
To set the traffic loads and the uplink noise rise using the Cells table:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Open Table from the context menu. The Cells table appears.
4. Enter a value in the following columns:
- Traffic Load (DL) (%)
- UL Noise Rise (dB)
- Segmentation Usage (DL) (%) (WiMAX 802.16e)
Although, you can also set a value for the Traffic Load (UL) (%) column as an indication of cells’ uplink loads,
this parameter is not used in the coverage prediction calculations. The measure of interference in the uplink
is given by the UL Noise Rise (dB). For a definition of the values, see "Cell Description" on page 872.
5. To enter the same values in one column for all cells in the table:
a. Enter the value in the first row in the column.
b. Select the entire column.
c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
Downlink and uplink coverage predictions by C/(I+N) level predict the interference levels and signal-to-interference levels
in the part of the network being studied.
Atoll calculates the best server for each pixel depending on the downlink preamble signal level. The serving transmitter
is determined according to the received preamble signal level from the cell with the highest preamble power. If more than
one cell cover the pixel, the one with the lowest order is selected as the serving (reference) cell. Then, depending on the
prediction definition, it calculates the interference from other cells, and finally calculates the C/(I+N). The pixel is coloured
if the display threshold condition is fulfilled (in other words, if the C/(I+N) is higher than C/(I+N) threshold).
Coverage prediction by C/(I+N) level calculates the co-channel interference as well as the adjacent channel interference,
which is reduced by the adjacent channel suppression factor defined in the Frequency Bands table. For more information
on frequency bands, see "Defining Frequency Bands" on page 971.
The preamble C/(I+N) is calculated using the preamble power and the main antenna. Interference on the preamble does
not depend on the cell load conditions. It depends only on the probabilities of collision between the subcarriers used to
transmit the preamble. The downlink traffic C/(I+N) is calculated using the traffic power, the main antenna or the smart
antenna equipment, downlink traffic load, the segmentation usage ratio, and any AAS simulation results stored either in
the cell properties or in the selected simulation results. The downlink traffic C/(I+N) also takes into account the probabilities
of collision between subcarriers when segmentation is used. The uplink C/(I+N) is calculated using the terminal power
calculated after power control, the main antenna or the smart antenna equipment, uplink noise rise, and any AAS simula-
tion results stored either in the cell properties or in the selected simulation results.
To make a coverage prediction by C/(I+N) level:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by C/(I+N) Level (DL) or Coverage by C/(I+N) Level (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The C/(I+N) coverage prediction is a best server
coverage prediction. The Noise Figure defined in the terminal type’s properties dialogue is used in the coverage
prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to determine
the total noise in the uplink.
For more information on services, terminals, mobility types, and WiMAX equipment, see "Modelling Services" on
page 905, "Modelling Terminals" on page 906, "Modelling Mobility Types" on page 906, and "Defining WiMAX
Equipment" on page 978, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C⁄(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 13.33
and Figure 13.34).
Downlink and uplink best radio bearer coverage predictions calculate and display the best WiMAX radio bearers based on
C⁄(I+N) for each pixel.
To make a coverage prediction by best bearer:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Best Bearer (DL) or Coverage by Best Bearer (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The best bearer coverage prediction is always based
on the best server. The Noise Figure defined in the terminal type’s properties dialogue is used in the coverage
prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to determine
the total noise in the uplink. As well, the bearer selection for each pixel according to the traffic C⁄(I+N) level is
performed using the bearer selection thresholds defined in the WiMAX equipment. This WiMAX equipment is the
one defined in the selected terminal for the downlink coverage predictions, and the one defined in the cell proper-
ties of the serving transmitter for the uplink coverage predictions. Mobility is used to index the bearer selection
threshold graph to use.
For more information on services, terminals, mobility types, and WiMAX equipment, see "Modelling Services" on
page 905, "Modelling Terminals" on page 906, "Modelling Mobility Types" on page 906, and "Defining WiMAX
Equipment" on page 978, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C⁄(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the WiMAX bearer coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 13.36
and Figure 13.37).
Downlink and uplink throughput coverage predictions calculate and display the channel throughputs and cell capacities
based on C⁄(I+N) and bearer calculations for each pixel. These coverage predictions can also display aggregate cell
throughputs if Monte Carlo simulation results are available. For more information on making aggregate cell throughput
coverage predictions using simulation results, see "Making an Aggregate Throughput Coverage Prediction Using Simula-
tion Results" on page 916.
To make a coverage prediction by throughput:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Throughput (DL) or Coverage by Throughput (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The throughput coverage prediction is always based
on the best server. The Noise Figure defined in the terminal type’s Properties dialogue is used in the coverage
prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to determine
the total noise in the uplink. As well, the bearer selection for each pixel according to the C⁄(I+N) level is performed
using the bearer selection thresholds defined in the WiMAX equipment. This WiMAX equipment is the one defined
in the selected terminal for the downlink coverage predictions, and the one defined in the cell properties of the
serving transmitter for the uplink coverage predictions. The mobility is used to indicate the bearer selection thresh-
old graph to use. The service is used for the application throughput parameters defined in the service Properties
dialogue.
For more information on services, terminals, mobility types, and WiMAX equipment, see "Modelling Services" on
page 905, "Modelling Terminals" on page 906, "Modelling Mobility Types" on page 906, and "Defining WiMAX
Equipment" on page 978, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C⁄(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage pre-
diction will display. You can set parameters to display the following results:
- Channel throughputs: Select Peak MAC Channel Throughput, Effective MAC Channel Throughput, or
Application Channel Throughput.
- Cell capacities: Select Peak MAC Cell Capacity, Effective MAC Cell Capacity, or Application Cell
Capacity.
- Allocated bandwidth throughputs in uplink: Select Peak MAC Allocated Bandwidth Throughput, Effective
MAC Allocated Bandwidth Throughput, or Application Allocated Bandwidth Throughput.
The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see
"Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Atoll calculates the peak MAC channel throughputs from the information provided in the Global Parameters and in the
terminal and mobility properties for the terminal and mobility selected in the coverage prediction. Atoll determines the total
number of symbols in the downlink and the uplink subframes from the information in the Global Parameters. Then, Atoll
determines the bearer at each pixel and multiplies the bearer efficiency by the number of symbols in the frame to determine
the peak MAC channel throughputs.
The effective MAC throughputs are the peak MAC throughputs reduced by retransmission due to errors, or the Block Error
Rate (BLER). Atoll uses the block error rate graphs of the WiMAX equipment defined in the selected terminal or the
WiMAX equipment of the cell of the serving transmitter.
The application throughput is the effective MAC throughput reduced by the overheads of the different layers between the
MAC and the Application layers.
The cell capacity display types let you calculate and display the throughputs available at each pixel of the coverage area
taking into account the maximum traffic load limits set for each cell. In other words, the cell capacity is equal to channel
throughput when the maximum traffic load is set to 100%, and is equal to a throughput limited by the maximum allowed
traffic loads otherwise. Cell capacities are, therefore, channel throughputs scaled down to respect the maximum traffic load
limits.
The allocated bandwidth throughputs are the throughputs corresponding to the number of subchannels allocated to the
terminal at different locations. Subchannelisation in uplink allows mobiles to use different numbers of subchannels
depending on the radio conditions. For example, users located far from the base stations use less subchannels than users
located near so that they can concentrate their transmission power over a bandwidth narrower than the channel bandwidth
in order to maintain the connection in uplink.
For more information on throughput calculation, see the Technical Reference Guide. For more information on the Global
Parameters, see "The Global Transmitter Parameters" on page 972.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Atoll calculates the aggregate peak MAC, effective MAC, and application cell throughputs during Monte Carlo simulations.
The aggregate cell throughputs are the sums of the cell’s user throughputs. You can create a coverage prediction that
calculates and displays the surface area covered by each cell, and colours the coverage area of each cell according to its
aggregate throughput.
To create an aggregate throughput coverage prediction:
1. Create and run a Monte Carlo simulation. For more information on creating Monte Carlo simulations, see "Calcu-
lating and Displaying Traffic Simulations" on page 949.
2. Create a coverage prediction by throughput as explained in "Making a Coverage by Throughput" on page 914,
with the following exceptions:
a. On the Condition tab, select a simulation or group of simulations from the Load Conditions list. The coverage
prediction will display the results based on the selected simulation or on the average results of the selected
group of simulations.
b. On the Display tab, you can display results by Peak MAC User Throughput, Effective MAC User Through-
put, or Application User Throughput. The coverage prediction results will be in the form of thresholds. For
information on defining the display, see "Display Properties of Objects" on page 33.
This coverage prediction displays the surface area covered by each cell and colours it according to its aggregate through-
put. For more information on using simulation results in coverage predictions, see "Making Coverage Predictions Using
Simulation Results" on page 963.
Downlink and uplink quality indicator coverage predictions calculate and display the values of different quality indicators
(BLER, BER, etc.) based on the best WiMAX radio bearers and on C⁄(I+N) for each pixel.
To make a coverage prediction by quality indicator:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Quality Indicator (DL) or Coverage by Quality Indicator (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The quality indicator coverage prediction is always
based on the best server. The Noise Figure defined in the terminal type’s properties dialogue is used in the cover-
age prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to deter-
mine the total noise in the uplink. As well, the bearer selection for each pixel according to the traffic C⁄(I+N) level
is performed using the bearer selection thresholds defined in the WiMAX equipment, and the quality indicator
graphs from the WiMAX equipment are used to determine the values of the selected quality indicator on each pixel.
This WiMAX equipment is the one defined in the selected terminal for the downlink coverage predictions, and the
one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used to
index the bearer selection threshold graph to use.
This WiMAX equipment is the one defined in the selected terminal for the downlink coverage predictions, and the
one defined in the cell properties of the serving transmitter for the uplink coverage predictions.
For more information on services, terminals, mobility types, and WiMAX equipment, see "Modelling Services" on
page 905, "Modelling Terminals" on page 906, "Modelling Mobility Types" on page 906, and "Defining WiMAX
Equipment" on page 978, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C⁄(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
age prediction results will be in the form of thresholds. For information on adjusting the display, see "Display Prop-
erties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the quality indicator coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 13.42
and Figure 13.43).
• The downlink traffic signal levels, downlink traffic loads, segmentation usage (WiMAX 802.16e), AAS simulation
results, and AAS usage, for determining the downlink traffic C/(I+N), bearer, and throughputs.
• The uplink signal levels, uplink noise rise, and AAS simulation results, for determining the uplink C/(I+N), bearer,
and throughputs.
The downlink and uplink load conditions can be taken from the Cells table or from Monte Carlo simulations.
You can make an effective signal analysis to verify a coverage prediction. In this case, before you make the point analysis,
ensure the coverage prediction you want to verify is displayed on the map.
To make an effective signal analysis:
1. Click the Point Analysis button ( ) on the toolbar. The Point Analysis Tool window appears (see
Figure 13.45).
2. Click the Signal Analysis tab.
3. At the top of the Signal Analysis tab, select "Cells Table" from Load Conditions.
4. If you are making a signal analysis to verify a coverage prediction, you can recreate the conditions of the coverage
prediction:
a. Select the same Terminal, Service, and Mobility studied in the coverage prediction.
b. Right-click the Point Analysis window and select Properties from the context menu. The Properties dia-
logue appears.
- Edit the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and,
select "From Model" from the Shadowing Margin list.
c. Click OK to close the Properties dialogue.
5. Move the pointer over the map to make a signal analysis for the current location of the pointer.
As you move the pointer, Atoll indicates on the map which is the best server for the current position (see
Figure 13.44).
Information on the current position is given on the Signal Analysis tab of the Point Analysis window. See
Figure 13.45 for an explanation of the displayed information.
6. Click the map to leave the point analysis pointer at its current position.
To move the pointer again, click the point analysis pointer on the map and drag it to a new position.
7. Click the Point Analysis button ( ) on the toolbar again to end the point analysis.
The preamble reception from the best The connection status (preamble, downlink
server (top-most bar) and all interfering and uplink) for the current point.
cells. Solid bars indicate the signal levels
above the preamble C/N thresholds. : Service available
: Service unavailable
7. Under Exceptional Pairs, create a new exceptional pair in the row marked with the New Row icon ( ):
a. Select the cell from the list in the Neighbours column.
b. In the Status column, select one of the following:
- Forced: The selected cell will always be a neighbour of the reference cell.
- Forbidden: The selected cell will never be a neighbour of the reference cell.
8. Click elsewhere in the table when you have finished creating the new exceptional pair.
9. Click OK.
Notes: You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology
Neighbours table. You can open this table by right-clicking the Transmitters folder and
selecting Cells > Neighbours > Intra-Technology Exceptional Pairs.
- Shadowing taken into account: If desired, select the Shadowing taken into account check box and
enter a Cell Edge Coverage Probability.
- Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses defined per
clutter class in the calculations.
- Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic
neighbour allocation.
- % Min. Covered Area: Enter the minimum surface area, in percentage, that a possible neighbour cell’s cov-
erage area must overlap the reference cell’s coverage area.
6. Select the desired calculation parameters:
- Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want
cells located on the same site as the reference cell to be automatically considered as neighbours.
- Force adjacent cells as neighbours: Select the Force adjacent cells as neighbours check box if you want
cells that are adjacent to the reference cell to be automatically considered as neighbours. A cell is considered
adjacent if there is at least one pixel in the reference cell’s coverage area where the possible neighbour cell
is the best server, or where the possible neighbour cell is the second best server (respecting the handover
margin).
- Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In
other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neigh-
bour list of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from
the list of neighbours of the reference cell.
- Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or
forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see
"Defining Exceptional Pairs" on page 921.
- Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete
all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check
box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new
neighbours to the list.
Figure 13.46: The handover area between the reference cell and the possible neighbour
7. Click the Importance Weighting button to set the relative importance of possible neighbours:
- Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage
reasons.
- Adjacency Factor: If you have selected the Force adjacent cells as neighbours check box in step 6., set
the minimum and maximum importance of a possible neighbour cell being adjacent to the reference cell.
- Co-site Factor: If you have selected the Force co-site cells as neighbours check box in step 6., set the
minimum and maximum importance of a possible neighbour cell being located on the same site as reference
cell.
8. Click Calculate. Atoll begins the process of allocating neighbours. Atoll first checks to see whether the path loss
matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates them.
Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays
new neighbours. If no new neighbours have been found and if the Deleting existing neighbours check box is
cleared, the Results table will be empty.
- Cause: The reason Atoll has allocated the possible neighbour cell, as identified in the Neighbour column, to
the reference cell, as identified in the Cell column. The possible reasons are:
- Co-site
- Adjacency
- Symmetry
- Coverage
- Existing
- Coverage: The amount of reference cell’s coverage area that the neighbour overlaps, in percentage and in
square kilometres.
- Adjacency: The area of the reference cell, in percentage and in square kilometres, where the neighbour cell
is best server or second best server.
9. Select the Commit check box for each neighbour you want to assign to a cell. You can use many of Atoll’s table
shortcuts, such as filtering and sorting. For information on working with data tables, see "Working with Data
Tables" on page 50.
10. Click Commit. All the neighbours whose Commit check box is selected are assigned to the reference cells. Neigh-
bours are listed in the Intra-technology Neighbours tab of each cell’s Properties dialogue.
Notes:
• A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already
exists and the Delete existing neighbours check box is cleared when you start the new allo-
cation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint
on the forbidden neighbour will be ignored by the algorithm because the neighbour already
exists.
• When the options Force exceptional pairs and Force symmetry are selected, Atoll con-
siders the constraints between exceptional pairs in both directions in order to respect sym-
metry. On the other hand, if the neighbour relation is forced in one direction and forbidden in
the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the
Event Viewer.
• You can save automatic neighbour allocation parameters in a user configuration. For informa-
tion on saving automatic neighbour allocation parameters in a user configuration, see
"Exporting a User Configuration" on page 75.
1. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
2. Select Display Options from the context menu. The Visual Management dialogue appears.
3. Under Intra-technology Neighbours, select the Display Links check box.
4. Click the Browse button ( ) beside the Display Links check box.
5. The Intra-technology Neighbour Display dialogue appears.
6. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a cell with a
unique colour.
- Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you
want Atoll to colour the cell’s neighbour links according to a value from the Intra-technology Neighbours
table, or according to the neighbour frequency band.
- Value Intervals: Select "Value Intervals" to colour the cell’s neighbour links according the value interval of the
value selected from the Field list. For example, you can choose to display a cell’s neighbours according to the
importance, as determined by the weighting factors.
Tip: You can display the number of handoff attempts for each cell-neighbour pair by first
creating a new field of Type "Integer" in the Intra-Technology Neighbour table for the
number of handoff attempts. Once you have imported or entered the values in the new
column, you can select this field from the Field list along with "Value Intervals" as the
Display Type. For information on adding a new field to a table, see "Adding a Field to an
Object Type’s Data Table" on page 51.
Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you
can display or hide neighbour link display types individually.
For information on changing display properties, see "Display Properties of Objects" on page 33.
7. Select the Add to Legend check box to add the displayed neighbour links to the legend.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each neighbour link.
9. Click OK to save your settings.
10. Under Advanced, select which neighbour links to display:
- Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations
where the selected cell is the reference cell and where the neighbour relation is not symmetric.
- Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations
where the selected cell is neighbour and where the neighbour relation is not symmetric.
- Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the
selected cell and the neighbour.
11. Click OK to save your settings.
12. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
- The symmetric neighbour relations of the selected (reference) cell are indicated by a line.
- The outward neighbour relations are indicated with a line with an arrow pointing at the neighbour (e.g. see
Site1_2(0)) in Figure 13.47.).
- The inward neighbour relations are indicated with a line with an arrow pointing at the selected cell (e.g. see
Site9_3(0)) in Figure 13.47.).
In Figure 13.47, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward
neighbour links are coloured as the corresponding neighbour transmitters and the inward neighbour link is
coloured as the reference transmitter as it is neighbour of Site9_3(0) here.
In Figure 13.48, neighbour links are displayed according to the neighbour frequency. Here, all neighbour relations
are symmetric.
Figure 13.48: Neighbours of Site 22_3(0) - Display According to The Neighbour Frequency
Note: You can display either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting
either Forced Neighbours or Forbidden Neighbours.
2. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
3. Select Display Options from the context menu. The Neighbourhood Display dialogue appears.
4. Under Intra-technology Neighbours, select the Display Coverage Areas check box.
5. Click the Browse button ( ) beside the Display Coverage Areas check box.
6. The Intra-technology Neighbour Display dialogue appears.
7. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage area of a cell’s 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 cell’s neighbours according to a value from the Intra-technology
Neighbours table.
- Value Intervals: Select "Value Intervals" to colour the coverage area of a cell’s neighbours according the
value interval of the value selected from the Field list. For example, you can choose to display a cell’s neigh-
bours according to the importance, as determined by the weighting factors.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each coverage area.
9. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( ) in the
Radio toolbar.
Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete WiMAX 802.16e neighbours using the Cells tab of the transmitter’s 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 transmitter’s Properties dialogue appears.
3. Click the Cells tab.
4. On the Cells tab, click the Browse button ( ) beside Neighbours. The cell’s Properties dialogue appears.
5. Click the Intra-technology Neighbours tab.
6. If desired, you can enter the maximum number of neighbours.
7. Allocate or delete a neighbour.
To allocate a new neighbour:
a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon
( ).
b. Click elsewhere in the table when you have finished creating the new neighbour.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Right-click the neighbour in the Neighbour column. The context menu appears.
c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation be-
tween the cell in the Neighbour column and the cell in the Cell column is deleted.
To delete a neighbour:
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Press DEL to delete the neighbour.
8. Click OK.
Note: For information on working with data tables, see "Working with Data Tables" on page 50.
a. In the row marked with the New Row icon ( ), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column.
c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
a. Right-click the neighbour in the Neighbour column. The context menu appears.
b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the
Neighbour column and the cell in the Cell column.
To make several neighbour relations symmetric:
a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select
contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contig-
uous rows by pressing CTRL and clicking each rows separately.
b. Right-click the Neighbours table. The context menu appears.
c. Select Symmetrise from the context menu.
To take into consideration all exceptionnal pairs:
Note: You can add or delete either some forced neighbours or some forbidden neighbours using
the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table,
select the exceptional pairs to be considered, right-click the table and select Force
Exceptional Pairs in the context menu.
a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select
contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contig-
uous rows by pressing CTRL and clicking each rows separately.
b. Right-click the Neighbours table. The context menu appears.
c. Select Delete Link and Symmetric Relation from the context menu.
To delete a neighbour:
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Press DEL to delete the neighbour.
You can allocate or delete intra-technology neighbours directly on the map using the mouse.
To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neigh-
bours on the map as explained in "Displaying Neighbour Relations on the Map" on page 923.
To add a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters
to the intra-technology neighbours list.
To remove a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both trans-
mitters from the intra-technology neighbours.
To add an outward neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference
transmitter to the intra-technology neighbour list of the transmitter.
Notes:
• When there is more than one cell on the transmitter, clicking the transmitter in the map window
opens a context menu allowing you to select the cell you want (see "Selecting One of Several
Transmitters or Microwave Links" on page 30).
• You can add or delete either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting either
Forced Neighbours or Forbidden Neighbours.
Note: If the field Max number of intra-technology neighbours in the Cells table is empty, the
Full Lists check and the Lists > Max Number check use the Default Max Number value
defined in the audit dialogue.
- Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
- Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
The AFP enables you to automatically allocate frequencies to cells in the current network.
To automatically allocate frequencies:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Frequency Plan > Automatic Allocation. The Frequency Allocation dialogue appears.
4. You can set the following parameters:
- In WiMAX 802.16e documents, under Allocate, you can select Frequencies to perform automatic frequency
planning or Preamble Indexes to allocate preamble indexes to cells automatically.
- In WiMAX 802.16e documents, if you have selected Preamble Indexes under Allocate,
- Select the Preamble Index Allocation Range. You can choose to allocate preamble indexes from the
Entire (0-113) range or a Reduced (0-95) range.
- Under Cell PermBase Allocation Strategy, you can either select Free or Same per Site as the allocation
strategy.
For more information on the strategies, see "Automatically Allocating Preamble Indexes to WiMAX 802.16e
Cells" on page 934.
- Under Relations, you can set the relations to take into account in automatic allocation.
- Under Interference Matrices, you can calculate and take interference matrices into account for the fre-
quency allocation. When the Frequency Allocation dialogue opens, the Take into account check box is
disabled because interference matrices are not yet calculated nor available.
To calculate interference matrices:
i. Enter a value for the Quality Margin.
ii. Click the Calculate button. Atoll calculates the interference matrices. The calculation progress is dis-
played in the Event Viewer window. To stop the interference matrices calculation at any moment, click
the Stop button. Interference matrices are calculated using the default calculation resolution set in the
Properties dialogue of the Predictions folder.
iii. Click the Close button once the interference matrices have been calculated. The Event Viewer window
closes.
To display details of the calculated interference matrices:
i. Click the Details button. The Interference Matrices Display dialogue appears. This dialogue lists all the
interfered and interfering cell pairs and their respective interference probabilities in co- and adjacent chan-
nel cases.
ii. Click the Close button. The Interference Matrices Display dialogue closes.
To delete the calculated interference matrices:
Interference matrices calculated by the AFP are the co- and adjacent channel interference probabilities
for each interfered and interfering cell pair. The probability of interference of a cell is defined as the ratio
of the interfered surface area within the best server coverage area of any studied cell to the total best serv-
er coverage area of the cell:
S Int
P Int = --------------
-
S Total
In words, S Total is the best server coverage area of the studied cell, and S Int is the surface area within
the best server area of the studied cell where the interference from another cell is higher than the preamble
C/N threshold of the studied cell plus the quality margin.
The quality margin is defined with respect to the preamble C/N thresholds of cells. By default the preamble
C/N threshold outlines the area of service of a cell. This means that where the preamble signal quality of
a cell is less than the preamble C/N threshold, there is no service. The AFP uses the quality margin to
calculate interference within the service areas of cells. It is possible to set a value of quality margin which
reflects the coverage area of a bearer.
- Take min reuse distance into account: Select this check box if you want the AFP to take relations based
on distance into account for the allocation. You can enter the Default radius within which two cells whose
channels have a co-channel overlap cannot have the same frequency or preamble index.
Note: A minimum reuse distance can be defined at the cell level (in the cell Properties dialogue
or in the Cells table). If defined, a cell-specific reuse distance will be used instead of
default the value entered here.
- Take neighbours into account: In WiMAX 802.16e documents, select this check box if you want the AFP
to take neighbour relations into account for the allocation. The AFP will try to avoid allocating the same
frequency or preamble index to neighbours of each cell being allocated.
Atoll can only take neighbour relations into account if neighbours have already been allocated. For infor-
mation on allocating neighbours, see "Planning Neighbours" on page 920.
5. Under Results, Atoll displays the Total Cost of the current frequency or preamble index allocation taking into
account the parameters set in step 4. You can modify the parameters and click Recalculate Cost to see the
change in the total cost.
6. Click Calculate. Atoll begins the process of allocating frequencies or preamble indexes.
Once Atoll has finished allocating frequencies or preamble indexes, the proposed allocation is visible under
Results.
When you allocate frequencies to a large number of cells, it is easiest to let Atoll allocate them automatically, as described
in "Automatically Allocating Frequencies to Cells" on page 930. However, if you want to assign a frequency or a preamble
index to one cell or to modify it, you can do it by accessing the properties of the cell.
To allocate the frequency or preamble index to a cell manually:
1. On the map, right-click the transmitter to whose cell you want to allocate the frequency or preamble index. The
context menu appears.
2. Select Properties from the context menu. The transmitter’s Properties dialogue appears.
3. Select the Cells tab.
4. Select a Frequency Band and Channel Number for the cell or enter a Preamble Index.
5. You can set the Channel Allocation Status or Preamble Index Status to Fixed if you want to lock the frequency
or preamble index that you assigned.
6. Click OK.
In Atoll, you can search for frequency bands and channel numbers using the Search Tool.
If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results
displayed by transmitter, the search results will be displayed by transmitter coverage. Frequencies and any potential prob-
lems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage Prediction
by Transmitter" on page 894.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
If you selected the Co-channel Only check box, transmitters with cells using the same channel number are
displayed in red, and all others, including transmitters with adjacent channels, are displayed in grey.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
Note: By including the frequency band and channel number of each cell in the transmitter label,
the search results will be easier to understand. For information on defining the label, see
"Defining the Object Type Label" on page 35.
You can display the frequency allocation on transmitters by using the transmitters’ display characteristics.
To display the frequency allocation on the map:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Display tab.
5. Select "Discrete Values" as the Display Type and "Cells: Channel Number" as the Field.
6. Click OK. Transmitters will be displayed by channel number.
You can also display the frequency band and channel number in the transmitter label or tooltip by selecting "Cells:
Frequency Band" and "Cells: Channel Number" from the Label or Tip Text Field Definition dialogue.
For information on display options, see "Display Properties of Objects" on page 33.
You can group transmitters on the Data tab of the Explorer window by their frequency bands or channel numbers.
To group transmitters by frequency bands or channel numbers:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the General tab, click Group by. The Group dialogue appears.
5. Under Available Fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
- Frequency Band
- Channel Number
- Min Reuse Distance
7. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to
the list of parameters on which the transmitters will be grouped.
8. If you do not want the transmitters to be sorted by a certain parameter, select the parameter in the Group these
fields in this order list and click . The selected parameter is removed from the list of parameters on which
the transmitters will be grouped.
9. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters
to be grouped:
10. Click OK to save your changes and close the Group dialogue.
You can create and compare preamble C/(I+N) coverage predictions before and after the automatic frequency allocation
in order to analyse and compare the improvements brought about by the AFP. For more information on creating preamble
C/(I+N) coverage predictions, see "Making a Coverage by C/(I+N) Level" on page 910. For more information on comparing
two coverage predictions, see "Comparing Coverage Predictions: Examples" on page 900.
Where n is the segment number (0, 1, or 2), and k is a running index from 0 to 567, 283, 142, and 35 for FFT sizes 2048,
1024, 512, and 128, respectively. Therefore, each preamble carrier set uses every third subcarrier.
You can assign preamble indexes manually or automatically to any cell in the network. Once allocation is completed, you
can audit the preamble indexes, view preamble index reuse on the map, and make an analysis of preamble index distri-
bution.
The procedure for planning preamble indexes for a WiMAX 802.16e project is:
• Allocating preamble indexes
- "Automatically Allocating Preamble Indexes to WiMAX 802.16e Cells" on page 934.
- "Allocating Preamble Indexes to WiMAX 802.16e Cells Manually" on page 934.
• "Checking the Consistency of the Preamble Index Plan" on page 935.
• Displaying the allocation of preamble indexes
- "Using the Search Tool to Display Preamble Index Allocation" on page 935.
- "Displaying Preamble Index Allocation Using Transmitter Display Settings" on page 936.
- "Grouping Transmitters by Preamble Index" on page 936.
- "Displaying the Preamble Index Allocation Histogram" on page 936.
The allocation algorithm enables you to automatically allocate preamble indexes to cells in the current network. You can
choose from two allocation strategies for the cell permbase (for more information, see the Technical Reference Guide):
• Free: The preamble index allocation will only be restricted by the segment number allocated to nearby cells. Cell
permbases will not necessarily be the same for all the cells of a site.
• Same per Site: This strategy allocates preamble indexes to cells such that the same cell permbase is assigned
to all the cells of a site.
To automatically allocate preamble indexes:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Preamble Indexes > Automatic Allocation. The Preamble Index Allocation dialogue appears.
4. You can set the following parameters:
- Under Relations, you can set the relationships to take into account in automatic preamble index allocation.
- Neighbours: Select the Neighbours check box if you want to consider neighbour relations. The automat-
ic allocation algorithm will try to avoid allocating the same preamble index to neighbours of each cell being
allocated.
Atoll can only consider neighbour relations if neighbours have already been allocated. For information on
allocating neighbours, see "Planning Neighbours" on page 920.
- Min Reuse Distance: Select the Min Reuse Distance check box if you want to consider relations based
on distance. You can enter the Default radius within which two cells whose channels have a co-channel
overlap cannot have the same preamble index.
Note: A minimum reuse distance can be defined at the cell level (in the cell Properties dialogue
or in the Cells table). If defined, a cell-specific reuse distance will be used instead of
default the value entered here.
- Select the Preamble Index Allocation Range. You can choose to allocate preamble indexes from the Entire
(0-113) range or a Reduced (0-95) range.
- Under Cell PermBase Allocation Strategy, you can select one of the following automatic allocation strate-
gies:
- Free
- Same per Site
5. Under Results, Atoll displays the Total Cost of the current preamble index allocation taking into account the
parameters set in step 4. You can modify the parameters and click Recalculate Cost to see the change in the
total cost.
6. Click Calculate. Atoll begins the process of allocating preamble indexes.
Once Atoll has finished allocating preamble indexes, the indexes are visible under Results.
When you allocate preamble indexes to a large number of cells, it is easiest to let Atoll allocate preamble indexes auto-
matically, as described in "Automatically Allocating Preamble Indexes to WiMAX 802.16e Cells" on page 934. However, if
you want to assign a preamble index to one cell or to modify it, you can do it by accessing the properties of the cell.
To allocate a preamble index to a WiMAX 802.16e cell manually:
1. On the map, right-click the transmitter to whose cell you want to allocate a preamble index. The context menu
appears.
2. Select Properties from the context menu. The transmitter’s Properties dialogue appears.
3. Select the Cells tab.
4. Enter a Preamble Index in the cell’s column.
5. You can set the Preamble Index Status to Fixed if you want to lock the preamble index that you assigned.
6. Click OK.
In Atoll, you can search for preamble indexes, segment numbers, and cell permbases using the Search Tool.
If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results
displayed by transmitter, the search results will be displayed by transmitter coverage. Preamble indexes and any potential
problems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage
Prediction by Transmitter" on page 894.
To find a preamble index using the Search Tool:
1. Click View > Search Tool. The Search Tool window appears.
2. Select the Segment tab.
3. Select Preamble Index.
4. Enter a Preamble Index.
5. Click Search.
Transmitters whose cells use the entered preamble index are displayed in red. Transmitters with cells use other
preamble indexes are displayed in grey.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
Note: By including the preamble index of each cell in the transmitter label, the search results will
be easier to understand. For information on defining the label, see "Defining the Object
Type Label" on page 35.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
You can display preamble index allocation on transmitters by using the transmitters’ display characteristics.
To display preamble index allocation on the map:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Display tab.
5. Select "Discrete Values" as the Display Type and "Cells: Preamble Index" as the Field.
6. Click OK. Transmitters will be displayed by preamble index.
You can also display the preamble index in the transmitter label or tooltip by selecting "Cells: Preamble Index" from the
Label or Tip Text Field Definition dialogue.
For information on display options, see "Display Properties of Objects" on page 33.
You can group transmitters on the Data tab of the Explorer window by their preamble index or their reuse distance.
To group transmitters by preamble index:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the General tab, click Group by. The Group dialogue appears.
5. Under Available Fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
- Preamble Index
- Min Reuse Distance
- Preamble Index Status
7. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to
the list of parameters on which the transmitters will be grouped.
8. If you do not want the transmitters to be sorted by a certain parameter, select the parameter in the Group these
fields in this order list and click . The selected parameter is removed from the list of parameters on which
the transmitters will be grouped.
9. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters
to be grouped:
10. Click OK to save your changes and close the Group dialogue.
You can use a histogram to analyse the use of allocated preamble indexes in a network. The histogram represents the
preamble indexes as a function of the frequency of their use.
• Traffic map per user profile can be used if you have marketing-based traffic data.
Traffic maps per density of user profiles, where each vector (polygon, line or point) describes subscriber densities
(or numbers of subscribers for points) with user profiles and mobility types, and traffic maps per environment of
user profiles, where each pixel has an assigned environment class. For more information, see "Importing a Traffic
Map Based on Densities of User Profiles" on page 941, "Importing a Traffic Map Based on Environments of User
Profiles" on page 942 and "Creating a Traffic Map Based on Environments of User Profiles" on page 942.
• Traffic maps per density (number of users per km2) can be used if you have population-based traffic data,
or 2G network statistics.
Each pixel has an actual user density assigned. For more information, see "Creating Traffic Maps per User
Density (No. Users/km2)" on page 943, "Importing a Traffic Map per User Density" on page 943, "Converting 2G
Network Traffic" on page 945 and "Exporting Cumulated Traffic" on page 945
Note: You can also import a traffic map from a file by clicking the Import button. You can import
AGD (Atoll Geographic Data) format files that you have exported from another Atoll
document.
7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter.
8. Enter the data required in the Map per Sector dialogue:
- If you have selected Throughputs in Uplink and Downlink, enter the throughput demands in the uplink and
downlink for each sector and for each listed service.
- If you have selected Number of Users per Activity Status, enter the number of users active in the uplink, in
the downlink and in the uplink and downlink, for each sector and for each service.
Note: You can also import a text file containing the data by clicking the Actions button and
selecting Import Table from the menu. For more information on importing table data, see
"Importing Tables from Text Files" on page 59.
- The percentage of indoor users. An additional loss will be counted for indoor users during Monte-Carlo
simulations.
11. Click OK. Atoll creates the traffic map in the Traffic folder.
You can update the information, throughput demands and the number of users, on the map afterwards. You can update
Sector traffic maps. You must first recalculate the coverage prediction by transmitter. For more information, see "Making
a Coverage Prediction by Transmitter" on page 894. Once you have recalculated the coverage prediction, you can update
the traffic map.
To update the traffic map:
1. Click the Geo tab of the Explorer window.
2. Click the Expand button ( ) to expand the Traffic folder.
3. Right-click the sector traffic map that you want to update. The context menu appears.
4. Select Update from the context menu. The Map per Sector dialogue appears.
Select the updated coverage prediction by transmitter and define traffic values for the new transmitter(s) listed at
the bottom of the table. Deleted or deactivated transmitters are automatically removed from the table.
You can model variations in user behaviour by creating different profiles for different times of the day or for different circum-
stances. For example, a user may be considered a business user during the day, with video conferencing and voice, but
no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and
web browsing.
To create or modify a user profile:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the WiMAX Parameters folder.
3. Right-click the User Profiles folder. The context menu appears.
4. Select New from the context menu. The User Profiles New Element Properties dialogue appears.
Note: You can modify the properties of an existing user profile by right-clicking the user profile in
the User Profiles folder and selecting Properties from the context menu.
when he quits the browsing application. Between these two events, the user may be downloading web pages
and other times he may not be using the application, or he may be browsing local files, but the session is still
considered as open. A session, therefore, is defined by the volume transferred in the uplink and downlink and
not by the time.
Note: In order for all the services defined for a user profile to be taken into account during traffic
scenario elaboration, the sum of activity probabilities must be lower than 1.
- Duration (sec.): For services of the type "voice," enter the average duration of a call in seconds. For services
of the type "data," this field is left blank.
- UL Volume (KBytes): For services of the type "data," enter the average uplink volume per session in kilo-
bytes.
- DL Volume (KBytes): For services of the type "data," enter the average downlink volume per session in kil-
obytes.
6. Click OK.
Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a
given density (i.e., the number of users with the same profile per km²). To get an appropriate user distribution, you can
assign a weight to each clutter class for each environment class. You can also specify the percentage of indoor subscribers
for each clutter class. In a Monte Carlo simulation, an additional loss (as defined in the clutter class properties) will be
added to the indoor users’ path loss.
To create or modify a WiMAX environment:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the WiMAX Parameters folder.
3. Right-click the Environments folder. The context menu appears.
4. Select New from the context menu. The Environments New Element Properties dialogue appears.
Note: You can modify the properties of an existing environment by right-clicking the
environment in the Environments folder and selecting Properties from the context
menu.
7. In the row marked with the New Row icon ( ), set the following parameters for each user profile/mobility com-
bination that this WiMAX environment will describe:
- User: Select a user profile.
- Mobility: Select a mobility type.
- Density (Subscribers/km2): Enter a density in terms of subscribers per square kilometre for the combination
of user profile and mobility type.
8. Click the Clutter Weighting tab.
9. For each clutter class, enter a weight that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk × Sk
N k = N Area × --------------------------
∑
Wi × Si
i
where:
For example: An area of 10 km² with a user density of 100/km². Therefore, in this area, there are 1000 users. The
area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1" and for Building is
"4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter class and 800 in
the Building clutter class.
10. If you wish you can specify a percentage of indoor users for each clutter class. During a Monte Carlo simulation,
an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
11. Click OK.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 942.
- User Profile: If you want to import user profile information from the file, under Defined, select "By field" and
select the source field from the Choice column. If you want to assign a user profile from the WiMAX Param-
eters folder of the Data tab, under Defined, select "By value" and select the user profile in the Choice column.
- Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select
the source field from the Choice column. If you want to assign a mobility type from the WiMAX Parameters
folder of the Data tab, under Defined, select "By value" and select the mobility type in the Choice column.
- Density: If you want to import density information from the file, under Defined, select "By field" and select the
source field from the Choice column. If you want to assign a density, under Defined, select "By value" and
enter a density in the Choice column for the combination of user profile and mobility type. In this context, the
term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kil-
ometre for polygons, the number of subscribers per kilometre in case of lines and the number of subscribers
when the map consists of points.
Important: When you import user profile or mobility information from the file, the values in the file
must be exactly the same as the corresponding names in the WiMAX Parameters folder
of the Data tab. If the imported user profile or mobility does not match, Atoll will display a
warning.
13. Under Clutter Distribution, enter a weight for each class that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk × Sk
N k = N Area × --------------------------
∑
Wi × Si
i
where:
14. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simu-
lation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
15. Click OK to finish importing the traffic map.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 942.
7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, BIL, IST,
BMP, PlaNET©, GRC Vertical Mapper, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic map’s properties dialogue appears.
11. Select the Description tab.
In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the
Code column.
12. For each Code, select the environment it corresponds to from the Name column.
The environments available are those available in the Environments folder, under WiMAX Parameters on the
Data tab of the Explorer window. For more information, see "Modelling Environments" on page 940.
13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects"
on page 33.
14. Click OK.
7. Select the environment class from the list of available environment classes.
8. Click the Draw Polygon button ( ) to draw the polygon on the map for the selected environment class.
9. Click the Delete Polygon button ( ) and click the polygon to delete the environment class polygon on the map.
10. Click the Close button to close the Environment Map Editor toolbar and end editing.
5. Click Close.
If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per
clutter class.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 942.
7. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP,
PlaNET©, TIF, ISTAR, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic map’s properties dialogue appears.
11. Select the Traffic tab.
12. Select whether the users are active in the Uplink/Downlink, only in the Downlink, or only in the Uplink.
13. Under Terminals (%), enter the percentage of each type of terminal used in the map. The total percentage must
equal 100.
14. Under Mobilities (%), enter the percentage of each mobility type used in the map. The total percentage must
equal 100.
15. Under Services (%), enter the percentage of each service type used in the map. The total percentage must equal
100.
16. Under Clutter Distribution, enter for each clutter class the percentage of indoor users.
An additional loss will be counted for indoor users during the Monte Carlo simulations. You do not have to define
a clutter weighting for traffic maps per user density because the traffic is provided in terms of user density per pixel.
17. Click OK. Atoll creates the traffic map in the Traffic folder.
12. Click OK. Atoll creates the traffic map in the Traffic folder.
13. Right-click the traffic map. The context menu appears.
14. Select Edit from the context menu.
15. Use the tools available in the Vector Edition toolbar in order to draw contours. For more information on how to edit
contours, see "Editing Contours, Lines, and Points" on page 131. Atoll creates an item called Density values in
the User Density Map folder.
16. Right-click the item. The context menu appears.
17. Select Open Table from the context menu.
18. In the table, enter a traffic density value (i.e. the number of users per km2) for each contour you have drawn.
Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains
at "0" and no data will be exported.
8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic
data to be exported.
- Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal.
- Service: Select the service that will be exported, or select "Circuit services" to export voice traffic, or select
"Packet services" to export data traffic.
- Mobility: Select the mobility type that will be exported or select "All" to export all mobility types.
- Activity: Select one of the following:
- All Activity Statuses: Select All Activity Statuses to export all users without any filter by activity status.
- Uplink: Select Uplink to export mobiles active in the uplink only.
- Downlink: Select Downlink to export mobiles active in the downlink only.
- Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity.
9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the
cumulated traffic.
10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.
4. Select Save As from the context menu. The Save As dialogue appears.
5. Enter a file name and select a file format for the traffic map.
6. Click Save.
If you are exporting a raster traffic map, you have to define:
5. Click the Table tab. On the Table tab you can modify the various fields in the subscriber list, add user-defined fields
to the table, or, most importantly, change the default parameters for the fields in the table. These default param-
eters will be assigned to all the subscribers in this list created by using the mouse on the map (see Figure 13.52).
To modify the default values for these fields:
a. Select the field whose default value you want to modify.
b. Click Properties. The Field Definition dialogue appears.
c. Enter the new default value.
d. Click OK.
- ID: The subscriber ID in the subscriber list. It is an automatically created identification number.
- X and Y coordinates: The geographical coordinates of the subscriber. A subscriber’s location is always fixed.
- Height: The altitude of the subscriber antenna with respect to the ground (DTM).
- Clutter: The name of the clutter class where the subscriber is located. This is a non-editable field whose con-
tents are automatically updated.
- Name: You can assign a descriptive name to each subscriber.
- User Profile: A user profile defines the traffic demand characteristics of subscribers. Atoll determines the ter-
minal used, the service accessed, and the activity status of subscribers during Monte Carlo simulations
according to the information in the user profiles. For more information, see "Modelling User Profiles" on
page 939.
- Terminal: The default terminal (CPE) is the user equipment with an antenna, WiMAX equipment, and noise
characteristics. The properties of this terminal are taken into consideration when performing calculations on
the subscriber list.
- Service: The service that the subscriber accesses by default. The properties of this service are taken into con-
sideration when performing calculations on the subscriber list.
Note: Subscriber lists use the mobility type "Fixed", i.e., 0 km/hr, in calculations. Make sure that
you have bearer selection thresholds defined for this mobility type in the WiMAX
equipment properties. For information on defining bearer selection thresholds, see
"Defining WiMAX Equipment" on page 978.
- Azimuth: The orientation of the subscriber antenna in the horizontal plane. Azimuth is always considered with
respect to the north. You can either define this value manually or let Atoll calculate it for the subscriber. Atoll
points the subscriber antenna towards its serving base station.
- Mechanical Downtilt: The orientation of the subscriber antenna in the vertical plane. Mechanical downtilt is
positive when it is downwards and negative when upwards. You can either define this value manually or let
Atoll calculate it for the subscriber. Atoll points the subscriber antenna towards its serving base station.
- Lock Status: You can choose to lock the subscriber antenna orientation and serving transmitter. Use this
option if you do not want Atoll to change the assigned server or the antenna orientation.
- Serving Base Station: The serving transmitter of the subscriber. You can either define this value manually
or let Atoll calculate it for the subscriber. The serving base station is determined according to the received
preamble signal level from the cell with the highest preamble power.
- Reference Cell: The reference cell of the serving transmitter of the subscriber. You can either define this value
manually or let Atoll calculate it for the subscriber. If more than one cell of the serving base station cover the
subscriber, the one with the lowest order is selected as the reference cell.
- Distance: The distance of the subscriber from its serving base station. This is a non-editable field whose con-
tents are automatically updated.
- Received Preamble Power (DL) (dBm): The preamble signal level received at the subscriber location in the
downlink. This value is calculated by Atoll during calculations on subscriber lists.
- Received Traffic Power (DL) (dBm): The traffic signal level received at the subscriber location in the down-
link. This value is calculated by Atoll during calculations on subscriber lists.
- Received Pilot Power (DL) (dBm): The pilot signal level received at the subscriber location in the downlink.
This value is calculated by Atoll during calculations on subscriber lists.
- Preamble Total Noise (I+N) (DL) (dBm): The sum of the preamble interference and noise experienced at the
subscriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists.
- Traffic Total Noise (I+N) (DL) (dBm): The sum of the traffic interference and noise experienced at the sub-
scriber location in the downlink. This value is generated by Atoll during the calculations on subscriber lists.
- Preamble C/(I+N) (DL) (dB): The preamble C/(I+N) at the subscriber location in the downlink. This value is
generated by Atoll during the calculations on subscriber lists.
- Traffic C/(I+N) (DL) (dB): The traffic C/(I+N) at the subscriber location in the downlink. This value is generated
by Atoll during the calculations on subscriber lists.
- Pilot C/(I+N) (DL) (dB): The pilot C/(I+N) at the subscriber location in the downlink. This value is generated
by Atoll during the calculations on subscriber lists.
- Bearer (DL): The highest WiMAX bearer available for the traffic C/(I+N) level at the subscriber location in the
downlink. This value is generated by Atoll during the calculations on subscriber lists.
- Permutation Zone (DL) (WiMAX 802.16e): The downlink permutation zone allocated to the subscriber.
- BLER (DL): The Block Error Rate read from the subscriber’s terminal type’s WiMAX equipment for the traffic
C⁄(I+N) level at the subscriber location in the downlink. This value is generated by Atoll during the calculations
on subscriber lists.
- Diversity Mode (DL): The diversity mode supported by the cell or permutation zone in downlink.
- Peak MAC Channel Throughput (DL) (kbps): The maximum MAC channel throughput attainable using the
highest bearer available at the subscriber location in the downlink. This value is generated by Atoll during the
calculations on subscriber lists.
- Effective MAC Channel Throughput (DL) (kbps): The effective MAC channel throughput attainable using
the highest bearer available at the subscriber location in the downlink. This value is generated by Atoll during
the calculations on subscriber lists.
- Received Power (UL) (dBm): The signal level received at the serving transmitter from the subscriber terminal
in the uplink. This value is generated by Atoll during the calculations on subscriber lists.
- Total Noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the serving transmitter
of the subscriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists.
- C/(I+N) (UL) (dB): The C/(I+N) at the serving transmitter of the subscriber in the uplink. This value is gener-
ated by Atoll during the calculations on subscriber lists.
- Bearer (UL): The highest WiMAX bearer available for the C/(I+N) level at the serving transmitter of the sub-
scriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists.
- Permutation Zone (UL) (WiMAX 802.16e): The uplink permutation zone allocated to the subscriber.
- BLER (UL): The Block Error Rate read from the reference cell’s WiMAX equipment for the C/(I+N) level at the
serving transmitter of the subscriber in the uplink. This value is generated by Atoll during the calculations on
subscriber lists.
- Diversity Mode (UL): The diversity mode supported by the cell or permutation zone in uplink.
- Transmission Power (UL) (dBm): The transmission power of the subscriber’s terminal after power control in
the uplink. This value is generated by Atoll during the calculations on subscriber lists.
- Allocated Bandwidth (UL) (No. of Subchannels): The bandwidth allocated to the subscriber in terms of the
number of subchannels allocated in the uplink after subchannelisation. This value is generated by Atoll during
the calculations on subscriber lists.
- Peak MAC Channel Throughput (UL) (kbps): The maximum MAC channel throughput attainable using the
highest bearer available at the serving transmitter of the subscriber in the uplink. This value is generated by
Atoll during the calculations on subscriber lists.
- Effective MAC Channel Throughput (UL) (kbps): The effective MAC channel throughput available using the
highest bearer available at the serving transmitter of the subscriber in the uplink. This value is generated by
Atoll during the calculations on subscriber lists.
For more information on the calculations that you can carry out on subscriber lists, see "Performing Calculations
on Subscriber lists" on page 949.
6. Click the Display tab. You can modify how subscribers added to the list are displayed. For information on defining
the display properties, see "Display Properties of Objects" on page 33.
7. Click OK. Atoll creates a new subscriber list.
You can now move the pointer over the map and click once to place a new subscriber at the location of the pointer. Press
ESC or click the normal pointer button ( ), to finish adding subscribers on the map. For information on adding subscribers
to a list, see "Adding Subscribers to a Subscriber List Using the Mouse" on page 949.
You can open the subscriber list table containing all the subscribers and their parameters.
To open the subscriber list table:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Subscribers folder.
3. Right-click the subscriber list you want to open. The context menu appears.
4. Select Open Table from the context menu.
For information on working with data tables, see "Working with Data Tables" on page 50.
4. Select Add Subscribers from the context menu. The pointer changes to subscriber addition mode ( ).
5. Move the mouse over the Map window, and click once to add each subscriber.
6. Press ESC or click the normal pointer button ( ) to finish adding subscribers.
Tip: To place subscribers more accurately, before clicking the map, you can zoom in on the
map. For information on using the zooming tools, see "Changing the Map Scale" on
page 38.
Note: You can also export subscriber lists. For information on exporting table data, see
"Exporting Tables to Text Files" on page 58.
5. Click Calculate. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
6. Once the calculations are finished, click Close to close the Event Viewer.
7. Click Commit to store the results in the subscriber list. For the list of results that are available after the calculations,
see "Creating a Subscriber List" on page 946.
In Atoll, a simulation corresponds to a given distribution of WiMAX users. It is a snapshot of a WiMAX network. The prin-
cipal outputs of a simulation are a geographic user distribution with a certain traffic demand, resources allocated to each
user of this distribution, and cell loads.
You can create groups for one or more simulations and carry out as many simulations as required. A new simulation for
each different traffic scenario can help visualise the network’s response to different traffic demands. Each user distribution
(each simulation generates a new user distribution) is a Poisson distribution of the number of active users. Therefore, each
simulation may have a varying number of users accessing the network.
WiMAX simulation results can be displayed on the map as well as listed in tabular form for analysis. Simulation outputs
include results related to sites, cells, and mobiles.
WiMAX simulation results can be stored in the cells table and used in C/(I+N) based coverage predictions.
In this section, the following are explained:
• "WiMAX Traffic Simulation Algorithm" on page 950.
• "Creating Simulations" on page 952.
• "Displaying the Traffic Distribution on the Map" on page 953.
• "Displaying the Results of a Single Simulation" on page 957.
• "Updating Cell Load Values With Simulation Results" on page 962.
• "Estimating a Traffic Increase" on page 962.
Each mobile generated during the simulations is assigned a service, a mobility type, and a terminal according to
the user profile assigned to it. A transmission status is determined according to the activity probabilities. The trans-
mission status is an important output of the simulation as it has a direct impact on the next step of the simulation
process, i.e., the radio resource management (RRM), and has an impact on the interference level in the network.
The geographical location of each mobile is determined randomly for the mobiles generated based on the traffic
data from traffic maps. The mobiles generated based on the traffic data from subscriber lists are located on the
subscriber locations.
3. Downlink Calculations
The downlink calculations include the calculation of downlink preamble and traffic C/(I+N), determination of the
best available bearer for the traffic C/(I+N), allocation of resources (RRM), and calculation of user throughputs.
Segmentation is performed if the frame configuration, selected for a cell, supports segmentation. Interference
calculation is based on the probabilities of collision between segments. The effect of power concentration is not
considered.
4. Uplink Calculations
The uplink calculations include the calculation of uplink C/(I+N), determination of the best available bearer for the
C/(I+N), uplink power control and subchannelisation depending on the bearer, allocation of resources (RRM),
update of uplink noise rise values for cells, and calculation of user throughputs.
Note: The service priority is determined by the pair QoS Class-Priority. A UGS-Priority 1 service
will have higher service priority than a UGS-Priority 0 service. The QoS classes are UGS,
ErtPS, rtPS, nrtPS, and Best Effort, in order of decreasing priority.
At the end of the simulations, an active user can be connected in the direction corresponding to his activity status if:
• he has a best server assigned (step 2.),
• he has a bearer in the direction corresponding to his activity status (step 3. and step 4.),
• he is among the users selected by the scheduler for resource allocation (step 5.), and
• he is not rejected due to resource saturation (step 5.).
If a user is rejected during step 2., step 3., or step 4., the cause of rejection is "No Service". If a user is rejected during
step 5., the cause of rejection can either be "Scheduler Saturation," i.e., the user is not among the users selected for
resource allocation, or he can be rejected due to "Resource Saturation," i.e., all of the cell’s resources were used up by
other users.
- Select Traffic Maps to be Used: Select the traffic maps you want to use for the simulation.
- Select Subscriber Lists to be Used: Select the subscriber lists you want to use for the simulation.
You can select traffic maps of any type. However, if you have several different types of traffic maps and want
to make a simulation on a specific type of traffic map, you must ensure that you select only traffic maps of the
same type. For information on the types of traffic maps, see "Creating a Traffic Map" on page 937.
Note: When you perform simulations for subscriber lists, Atoll does not base the calculations on
subscriber lists on the path loss matrices calculated for transmitters. This is because the
path loss matrices are calculated for a given receiver height (1.5 m by default), but each
subscriber in a subscriber list can have a different height. Therefore, Atoll recalculates
the path loss, received power, and other output, for each subscriber when you perform
simulations on subscribers.
Tip: Using the same generated user and shadowing error distribution for several simulations
can be useful when you want to compare the results of several simulations where only one
parameter changes.
Tip: You can make the traffic distribution easier to see by hiding geographic data and
coverage predictions. For information, see "Displaying or Hiding Objects on the Map
Using the Explorer" on page 28.
Figure 13.59: Displaying the traffic distribution by the uplink allocated bandwidth
Figure 13.60: Displaying the traffic simulation results using tool tips
The Statistics tab: The Statistics tab contains the following sections:
- Request: Under Request, is data on the connection requests:
- Atoll calculates the total number of users who try to connect. This number is the result of the first random
trial; radio resource allocation has not yet finished. The result depends on the traffic description and traffic
input.
- During the first random trial, each user is assigned a service and an activity status. The number of users
per activity status and the UL and DL throughput demands that all users could theoretically generate are
provided.
- The breakdown per service (total number of users, number of users per activity status, and UL and DL
throughput demands) is given.
- Results: Under Results, is data on the connection results:
- The number of iterations that were run in order to converge.
- The total number and percentage of users unable to connect: rejected users, and the number of rejected
users per rejection cause.
- The number and percentage of users connected to a cell, the number of users per activity status, and the
total UL and DL throughputs they generate. These data are also given per service.
The Sites tab: The Sites tab contains the following information per site:
- Peak MAC User Throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink in all the cells of the site.
- Effective MAC User Throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the downlink in all the cells of the site.
- Application User Throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink in all the cells of the site.
- Peak MAC User Throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink in all the cells of the site.
- Effective MAC User Throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the uplink in all the cells of the site.
- Application User Throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink in all the cells of the site.
- Peak MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink in all the cells of the site.
- Effective MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the downlink in all the cells of the site.
- Application User Throughput (DL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the downlink in all the cells of the site.
- Peak MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink in all the cells of the site.
- Effective MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the uplink in all the cells of the site.
- Application User Throughput (UL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the uplink in all the cells of the site.
- No Service: The number of users unable to connect to any cell of the site for which the rejection cause was
"No Service."
- Scheduler Saturation: The number of users unable to connect to any cell of the site for which the rejection
cause was "Scheduler Saturation."
- Resource Saturation: The number of users unable to connect to any cell of the site for which the rejection
cause was "Resource Saturation."
The Cells tab: The Cells tab contains the following information, per site and transmitter:
- Traffic Load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation.
- Traffic Load (UL) (%): The traffic loads of the cells calculated on the uplink during the simulation.
- UL Noise Rise (dB): The noise rise of the cells calculated on the uplink during the simulation.
- Segmentation Usage (DL) (%): (WiMAX 802.16e) The percentage of the downlink traffic load that corre-
sponds to the first downlink PUSC zone, if it is segmented.
- AAS Usage (DL) (%): The percentage of downlink traffic load that corresponds to the traffic carried by the
smart antennas.
- AAS Usage (UL) (%): The percentage of uplink traffic load that corresponds to the traffic carried by the smart
antennas.
- AAS Simulation Results: The simulation results generated for transmitters using a smart antenna. The
results stored in this field are the angular distributions of the downlink traffic power spectral density and the
uplink noise rise. You can make the display of the downlink results diagram take into account the effect of the
antenna pattern of the single element. For more information, see the Administrator Manual.
- MU-MIMO Gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO.
- Peak MAC User Throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink.
- Effective MAC User Throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the downlink.
- Application User Throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink.
- Peak MAC User Throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink.
- Effective MAC User Throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the uplink.
- Application User Throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink.
- Peak MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink.
- Effective MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the downlink.
- Application User Throughput (DL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the downlink.
- Peak MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink.
- Effective MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the uplink.
- Application User Throughput (UL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the uplink.
- No Service: The number of users unable to connect to the cell for which the rejection cause was "No Service."
- Scheduler Saturation: The number of users unable to connect to the cell for which the rejection cause was
"Scheduler Saturation."
- Resource Saturation: The number of users unable to connect to the cell for which the rejection cause was
"Resource Saturation."
The Mobiles tab: The Mobiles tab contains the following information:
- X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the
second random trial).
- Height: The height of the user terminal (antenna).
- User Profile: The assigned user profile. Atoll uses the assigned service and activity status to determine the
terminal and the user profile.
- Service: The service assigned during the first random trial during the generation of the user distribution.
- Terminal: The assigned terminal. Atoll uses the assigned service and activity status to determine the terminal
and the user profile.
- Mobility: The mobility type assigned during the first random trial during the generation of the user distribution.
- Activity Status: The assigned activity status. It can be DL, UL, or DL+UL.
- Connection Status: The connection status indicates whether the user is connected or rejected at the end of
the simulation. If connected, the connection status corresponds to the activity status. If rejected, the rejection
cause is given.
- Clutter Class: The code of the clutter class where the user is located.
- Subscriber ID: The ID of the user if the user is generated from a subscriber list and not from a traffic map.
- Subscriber List: The subscriber list of the user if the user is generated from a subscriber list and not from a
traffic map.
- Indoor: This field indicates whether indoor losses have been added or not.
- Serving Base Station: The serving transmitter of the subscriber.
- Reference Cell: The reference cell of the serving transmitter of the subscriber.
- Total Path Loss (dB): The path loss calculated for the user.
- Received Preamble Power (DL) (dBm): The preamble signal level received at the user location in the down-
link.
- Received Traffic Power (DL) (dBm): The traffic signal level received at the user location in the downlink.
- Received Pilot Power (DL) (dBm): The pilot signal level received at the user location in the downlink.
- Azimuth: The orientation of the user’s 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 user’s terminal antenna in the vertical plane. Mechanical downtilt is positive
when it is downwards and negative when upwards. Atoll points the user antenna towards its serving base sta-
tion.
- Preamble Total Noise (I+N) (DL) (dBm): The sum of the preamble interference and noise experienced at the
user location in the downlink.
- Preamble C/(I+N) (DL) (dB): The preamble C/(I+N) at the user location in the downlink.
- Traffic Total Noise (I+N) (DL) (dBm): The sum of the traffic interference and noise experienced at the user
location in the downlink.
- Traffic C/(I+N) (DL) (dB): The traffic C/(I+N) at the user location in the downlink.
- Pilot C/(I+N) (DL) (dB): The pilot C/(I+N) at the user location in the downlink.
- Bearer (DL): The highest WiMAX bearer available for the traffic C/(I+N) level at the user location in the down-
link.
- Permutation Zone (DL) (WiMAX 802.16e): The downlink permutation zone allocated to the user.
- BLER (DL): The Block Error Rate read from the user terminal’s WiMAX equipment for the traffic C/(I+N) level
at the user location in the downlink.
- Diversity Mode (DL): The diversity mode supported by the cell or permutation zone in downlink.
- Peak MAC Channel Throughput (DL) (kbps): The maximum MAC channel throughput attainable using the
highest bearer available at the user location in the downlink.
- Effective MAC Channel Throughput (DL) (kbps): The effective MAC channel throughput attainable using
the highest bearer available at the user location in the downlink. It is calculated from the peak MAC throughput
and the BLER.
- Application Channel Throughput (DL) (kbps): The application throughput is the net throughput without
coding (redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the
throughput scaling factor of the service and the throughput offset.
- Peak MAC User Throughput (DL) (kbps): The maximum MAC user throughput attainable using the highest
bearer available at the user location in the downlink.
- Effective MAC User Throughput (DL) (kbps): The effective MAC user throughput attainable using the
highest bearer available at the user location in the downlink. It is calculated from the peak MAC throughput
and the BLER.
- Application User Throughput (DL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
- Received Power (UL) (dBm): The signal level received at the serving transmitter from the user terminal in
the uplink.
- Total Noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the serving transmitter
of the user in the uplink.
- C/(I+N) (UL) (dB): The C/(I+N) at the serving transmitter of the user in the uplink.
- Bearer (UL): The highest WiMAX bearer available for the C/(I+N) level at the serving transmitter of the user
in the uplink.
- Permutation Zone (UL) (WiMAX 802.16e): The uplink permutation zone allocated to the user.
- BLER (UL): The Block Error Rate read from the reference cell’s WiMAX equipment for the C/(I+N) level at the
serving transmitter of the user in the uplink.
- Diversity Mode (UL): The diversity mode supported by the cell or permutation zone in uplink.
- Transmission Power (UL) (dBm): The transmission power of the user terminal after power control in the
uplink.
- Allocated Bandwidth (UL) (No. of Subchannels): The bandwidth allocated to the user in terms of the
number of subchannels allocated in the uplink after subchannelisation.
- Peak MAC Channel Throughput (UL) (kbps): The maximum MAC channel throughput attainable using the
highest bearer available at user location in the uplink.
- Effective MAC Channel Throughput (UL) (kbps): The effective MAC channel throughput attainable using
the highest bearer available at the user location in the uplink. It is calculated from the peak MAC throughput
and the BLER.
- Application Channel Throughput (UL) (kbps): The application throughput is the net throughput without
coding (redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the
throughput scaling factor of the service and the throughput offset.
- Peak MAC Allocated Bandwidth Throughput (UL) (kbps): The maximum MAC throughput attainable for
the number of subchannels allocated to the user using the highest bearer available at the user location in the
uplink.
- Effective MAC Allocated Bandwidth Throughput (UL) (kbps): The effective MAC throughput attainable for
the number of subchannels allocated to the user using the highest bearer available at the user location in the
uplink. It is calculated from the peak MAC throughput and the BLER.
- Application Allocated Bandwidth Throughput (UL) (kbps): The application throughput is the net
throughput without coding (redundancy, overhead, addressing, etc.). It is calculated from the effective MAC
throughput, the throughput scaling factor of the service and the throughput offset.
- Peak MAC User Throughput (UL) (kbps): The maximum MAC user throughput attainable using the highest
bearer available at the user location in the uplink.
- Effective MAC User Throughput (UL) (kbps): The effective MAC user throughput attainable using the
highest bearer available at the user location in the uplink. It is calculated from the peak MAC throughput and
the BLER.
- Application User Throughput (UL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective MAC throughput, the throughput
scaling factor of the service and the throughput offset.
Notes:
• In Atoll, channel throughputs are peak MAC, effective MAC, or application throughputs
achieved at a given location using the highest WiMAX bearer with the entire channel resources.
• If a user is rejected, his user throughput is zero.
The Initial Conditions tab: The Initial Conditions tab contains the following information:
The Statistics tab: The Statistics tab contains the following sections:
- The number and percentage of users connected to a cell, the number of users per activity status, and the
total UL and DL throughputs they generate. These data are also given per service.
The Sites (Average) tab: The Sites (Average) tab contains the following information per site:
- Peak MAC User Throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink in all the cells of the site.
- Effective MAC User Throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the downlink in all the cells of the site.
- Application User Throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink in all the cells of the site.
- Peak MAC User Throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink in all the cells of the site.
- Effective MAC User Throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the uplink in all the cells of the site.
- Application User Throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink in all the cells of the site.
- Peak MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink in all the cells of the site.
- Effective MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the downlink in all the cells of the site.
- Application User Throughput (DL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the downlink in all the cells of the site.
- Peak MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink in all the cells of the site.
- Effective MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the uplink in all the cells of the site.
- Application User Throughput (UL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the uplink in all the cells of the site.
- No Service: The number of users unable to connect to any cell of the site for which the rejection cause was
"No Service."
- Scheduler Saturation: The number of users unable to connect to any cell of the site for which the rejection
cause was "Scheduler Saturation."
- Resource Saturation: The number of users unable to connect to any cell of the site for which the rejection
cause was "Resource Saturation."
The Cells (Average) tab: The Cells (Average) tab contains the following average information, per site and trans-
mitter:
- Traffic Load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation.
- Traffic Load (UL) (%): The traffic loads of the cells calculated on the uplink during the simulation.
- UL Noise Rise (dB): The noise rise of the cells calculated on the uplink during the simulation.
- Segmentation Usage (DL) (%): (WiMAX 802.16e) The percentage of the downlink traffic load that corre-
sponds to the first downlink PUSC zone, if it is segmented.
- AAS Usage (DL) (%): The percentage of downlink traffic load that corresponds to the traffic carried by the
smart antennas.
- AAS Usage (UL) (%): The percentage of uplink traffic load that corresponds to the traffic carried by the smart
antennas.
- AAS Simulation Results: The simulation results generated for transmitters using a smart antenna. The
results stored in this field are the angular distributions of the downlink traffic power spectral density and the
uplink noise rise. You can make the display of the downlink results diagram take into account the effect of the
antenna pattern of the single element. For more information, see the Administrator Manual.
- MU-MIMO Gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO.
- Peak MAC User Throughput (DL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the downlink.
- Effective MAC User Throughput (DL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the downlink.
- Application User Throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink.
- Peak MAC User Throughput (UL) (kbps): The sum of peak MAC user throughputs of all the users connected
in the uplink.
- Effective MAC User Throughput (UL) (kbps): The sum of effective MAC user throughputs of all the users
connected in the uplink.
- Application User Throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink.
- Peak MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the downlink.
- Effective MAC User Throughput (DL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the downlink.
- Application User Throughput (DL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the downlink.
- Peak MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of peak MAC user
throughputs of the users connected in the uplink.
- Effective MAC User Throughput (UL) (kbps) For Each Service: For each service, the sum of effective MAC
user throughputs of the users connected in the uplink.
- Application User Throughput (UL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the uplink.
- No Service: The number of users unable to connect to the cell for which the rejection cause was "No Service."
- Scheduler Saturation: The number of users unable to connect to the cell for which the rejection cause was
"Scheduler Saturation."
- Resource Saturation: The number of users unable to connect to the cell for which the rejection cause was
"Resource Saturation."
The Initial Conditions tab: The Initial Conditions tab contains the following information:
Note: If you are importing more than one file, you can select contiguous files by clicking the first
file you want to import, pressing SHIFT and clicking the last file you want to import. You
can select non-contiguous files by pressing CTRL and clicking each file you want to
import.
Note: Files with the extension PLN, as well as some FMT files (created with previous versions of
TEMS) are imported directly into Atoll; you will not be asked to define the data structure
using the Import of Measurement Files dialogue.
6. If you already have an import configuration defining the data structure of the imported file or files, you can select
it from the Configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have
an import configuration, continue with step 7.
a. Under Configuration, select an import configuration from the Configuration list.
b. Continue with step 10.
Notes:
• When importing a test mobile data path file, existing configurations are available in the Files
of type list of the Open dialogue, sorted according to their date of creation. After you have
selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises
the extension. In case several configurations are associated with an extension, Atoll chooses
the first configuration in the list.
• The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in
the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see
the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters:
- Name: By default, Atoll names the new test mobile data path after the imported file. You can change this
name if desired.
- Under Receiver, set the Height of the receiver antenna and the Gain and Losses.
- Under Measurement Conditions,
- Units: Select the measurement units used.
- Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document.
If the coordinates used in the file you are importing are different than the coordinates used in the Atoll
document, you must click the Browse button ( ) and select the coordinate system used in the test
mobile data file. Atoll will then convert the data imported to the coordinate system used in the Atoll docu-
ment.
8. Click the Setup tab (see Figure 13.61).
Figure 13.61: The Setup tab of the Import of Measurement Files dialogue
a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Dec-
imal Symbol used in the file.
b. Click Setup to link file columns and internal Atoll fields. The Test Mobile Data Configuration dialogue ap-
pears.
c. Select the columns in the imported file that give the X-Coordinates and the Y-Coordinates of each point in
the test mobile data file.
Note: You can also identify the columns containing the XY coordinates of each point in the test
mobile data file by selecting them from the Field row of the table on the Setup tab.
Important: If you have correctly entered the information under File on the Setup tab, and the
necessary values in the Test Mobile Data Configuration dialogue, Atoll should
recognize all columns in the imported file. If not, you can click the name of the column in
the table in the Field row and select the column name. For each field, you must ensure
that each column has the correct data type in order for the data to be correctly interpreted.
The default value under Type is "<Ignore>". Columns marked with "<Ignore>" will not be
imported.
9. If you wish to save the definition of the data structure so that you can use it again, you can save it as an import
configuration:
a. On the Setup tab, under Configuration, click Save. The Configuration dialogue appears.
b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atoll’s installation folder.
In case you cannot write into that folder, you can click Browse to choose a different location.
c. Enter a Configuration Name and an Extension of the files that this import configuration will describe (for ex-
ample, "*.txt").
d. Click OK.
Atoll will now select this import configuration automatically every time you import a test mobile data path file
with the selected extension. If you import a file with the same structure but a different extension, you can select
this import configuration from the Configuration list.
Notes:
• You do not have to complete the import procedure to save the import configuration and have
it available for future use.
• When importing a CW measurement file, you can expand the NumMeasINIfile.ini file by clicking
the button ( ) in front of the file in the Setup part to display all the available import configura-
tions. When selecting the appropriate configuration, the associations are automatically made
in the table at the bottom of the dialogue.
• You can delete an existing import configuration by selecting the import configuration under
Setup and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The test
mobile data are imported into the current Atoll document.
Notes:
• Fast Display forces Atoll to use the lightest symbol to display the points. This is useful when
you have a very large number of points.
• You can not use Multiple Shadings if the Fast Display check box has been selected.
• You can sort test mobile data paths in alphabetical order on the Data tab of the Explorer window
by right-clicking the Test Mobile Data Path folder and selecting Sort Alphabetically from the
context menu.
• You can export the display settings of a test mobile data path in a configuration file to make them
available for future use. You can export the display settings or import display settings by clicking
the Actions button on the Display tab of the test mobile data path’s Properties dialogue and
selecting Export or Import from the menu.
Note: You can permanently delete the points located in the clutter classes whose check boxes
you clear by selecting the Delete points outside the filter check box.
b. Underneath the name of each column, enter the criteria on which the column will be filtered as explained in
the following table:
9. Click OK to filter the data according to the criteria you have defined.
Filters are combined first horizontally, then vertically. For more information on filters, see "Advanced Data Filtering"
on page 71.
Note: The Refresh Geo Data option available in the context menu of test mobile data paths
enables you to update heights (Alt DTM, Clutter height, DTM+Clutter) and the clutter class
of test mobile data points after adding new geographic maps or modifying existing ones.
7. When you have finished setting the parameters for the coverage prediction, click OK.
You can create a new coverage prediction by repeating the procedure from step 1. to step 7. for each new cover-
age prediction.
8. When you have finished creating new coverage predictions for these test mobile data, right-click the test mobile
data. The context menu appears.
9. Select Calculations > Calculate All the Studies from the context menu.
A new column for each coverage prediction is added in the table for the test mobile data. The column contains the
predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned
to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Managing Calcu-
lations in Atoll).
You can display the information in these new columns in the Test Mobile Data window. For more information on
the Test Mobile Data window, see "Analysing Data Variations Along the Path" on page 969.
5. Click the Display button at the top of the Test Mobile Data window. The Display Parameters dialogue appears
(see Figure 13.64).
Note: You can change the display status or the colour of more than one field at the same time
by selecting several fields. You can select contiguous fields by clicking the first field,
pressing SHIFT and clicking the last field. You can select non-contiguous fields by
pressing CTRL and clicking each field. You can then change the display status or the
colour by right-clicking on the selected fields and selecting the choice from the context
menu.
The selected fields are displayed in the Test Mobile Data window.
7. You can display the data in the test mobile path in the following ways:
- Click the values in the Test Mobile Data window.
- Click the points on the test mobile path in the map window.
The test mobile data path appears in the map window as an arrow pointing towards the best server (see
Figure 13.63 on page 969) in the same colour as the transmitter.
8. You can display a secondary Y-axis on the right side of the window in order to display the values of a variable with
different orders of magnitude than the ones selected in the Display Parameters dialogue. You select the value to
be displayed from the right-hand list at the top of the Test Mobile Data window. The values are displayed in the
colour defined in the Display Parameters dialogue.
9. You can change the zoom level of the Test Mobile Data window display in the Test Mobile Data window in the
following ways:
- Zoom in or out:
i. Right-click the Test Mobile Data window.
ii. Select Zoom In or Zoom Out from the context menu.
- Select the data to zoom in on:
i. Right-click the Test Mobile Data window on one end of the range of data you want to zoom in on.
ii. Select First Zoom Point from the context menu.
iii. Right-click the Test Mobile Data window on the other end of the range of data you want to zoom in on.
iv. Select Last Zoom Point from the context menu. The Test Mobile Data window zooms in on the data be-
tween the first zoom point and the last zoom point.
10. Click the data in the Test Mobile Data window to display the selected point in the map window. Atoll will recentre
the map window on the selected point if it is not presently visible.
Tip: If you open the table for the test mobile data you are displaying in the Test Mobile Data
window, Atoll will automatically display in the table the data for the point that is displayed
in the map and in the Test Mobile Data window (see Figure 13.63 on page 969).
a. Select Print from the context menu. The Print dialogue appears.
b. Click OK to print the contents of the Test Mobile Data window.
Note: The relationship between the frequency band (spectrum), the channel width, and the
channel numbers can be defined as:
Frequency Band Width = Channel Bandwidth x (Last Channel + 1 - First Channel)
So, if you have a frequency band of 15 MHz, and you are deploying your network with
1.5 MHz allocated to each cell, you can find the First and Last Channel numbers by:
Last Channel - First Channel = (Frequency Band Width / Channel Bandwidth) - 1
If you plan to keep the First Channel number = 0, for our example:
Last Channel = (15 MHz / 1.5 MHz) - 1 = 9
- Excluded Channels: Enter the channel numbers which do not belong to the frequency band.
- Start Frequencies (MHz): Enter the start frequency for TDD frequency bands, and the downlink and the
uplink start frequencies for FDD frequency bands.
- Adjacent Channel Suppression Factor (dB): Enter the adjacent channel interference suppression factor in
dB. Interference received from adjacent channels is reduced by this factor during the calculations.
- Sampling Factor: Enter the sampling factor for converting the channel bandwidth into the sampling fre-
quency.
- Duplexing Method: Select the duplexing method used in the frequency band from the list.
5. When you have finished adding frequency bands, click Close.
You can also access the properties dialogue of each individual frequency band by clicking the Properties button.
Note: The exact number of symbol durations in one frame depends on various parameters
(channel bandwidth, frame duration, cyclic prefix lengths, sampling factor, etc.). Some of
these parameters can be different per cell. Therefore, the exact numbers of symbol
durations in downlink and uplink subframes can be different per cell as well. The exact
numbers of symbol durations in the downlink and uplink subframes are calculated by
Atoll for each cell according to the DL:UL ratio that you set in the Global Parameters. For
example, a DL:UL ratio of 36:12 would actually give 36:12 for a 5 MHz channel (sampling
factor = 1.12 and FFT size = 512) but would give 26:8 for a 7 MHz channel (sampling
factor = 1.14286 and FFT size = 1024) with the following configuration:
Frame Duration = 5 ms
Cyclic Prefix = 1/8
DL Fixed Overhead = UL Fixed Overhead = 0
TTG = RTG = 0 ms
DL:UL Ratio = 36:12
For more information on this calculation, see the Technical Reference Guide.
• Transmission and reception time guards (TDD only): Transmission and reception time guards are also time
domain overheads, i.e., these are portions of the frame which cannot be used for data transfer. You can enter TTG
and RTG times in milliseconds.
• Uplink power control margin: The margin (in dB) that will be added to the bearer selection threshold, for safety
against fast fading, when performing power control in uplink.
• Serving (reference) cell selection method: The reference cell selection method is used for determining the ref-
erence cell in case of transmitters supporting more than one cell. The best serving transmitter for a pixel, sub-
scriber, or mobile is determined according to the received preamble signal level from the cell with the highest
preamble power. If more than one cell of the same transmitter cover the pixel, subscriber, or mobile, the reference
cell is determined according to the selected method:
- Random: In coverage prediction calculations and in calculations on subsriber lists, the cell with the lowest
order is selected as the serving (reference) cell. In Monte Carlo simulations, a random cell is selected as the
serving (reference) cell.
- Sequential: In coverage prediction calculations and in calculations on subsriber lists, the cell with the lowest
order is selected as the serving (reference) cell. In Monte Carlo simulations, cells are selected as serving (ref-
erence) cells for mobiles sequentially (one by one).
- Min DL Traffic Load: (Not implemented yet) The cell with the lowest downlink traffic load is selected as the
serving (reference) cell. If more than one cell has the same lowest downlink traffic load, the first cell among all
such cells is selected. During Monte Carlo simulations, as the cell traffic loads may vary, the serving cell for
mobiles may also change.
- Min UL Traffic Load: (Not implemented yet) The cell with the lowest uplink traffic load is selected as the
serving (reference) cell. If more than one cell has the same lowest uplink traffic load, the first cell among all
such cells is selected. During Monte Carlo simulations, as the cell traffic loads may vary, the serving cell for
mobiles may also change.
The Min DL Traffic Load and Min UL Traffic Load options model load balancing between cells. In coverage
predictions as the probe mobile selects the least loaded cell, i.e., tries to keep the traffic load balanced between
cells of the transmitter. Instead of loading already loaded cells even more, the base station chooses to load the
least loaded among them.
When using either the Random or the Sequential cell selection method, the reference cell once assigned to a
mobile does not change during Monte Carlo simulations.
The following parameters are only available in WiMAX 802.16d documents (based on the WiMAX 802.16d project
template).
• Number of subchannels per channel: A channel can be divided into a number of subchannels. You can set the
number of these subchannels at the network level in Atoll.
• Number of subcarriers per channel: The entire channel contains a number of subcarriers which compose the
upper and lower guard bands, the pilot subcarriers, and the data subcarriers. The guards, pilots, and the DC sub-
carrier can not be used for data transfer. The total thermal noise over the entire channel bandwidth is computed
according to the number of used subcarriers out of the total number of subcarriers. The used subcarriers are the
data and the pilot subcarriers. The data transfer capacity of a channel is calculated by considering the data sub-
carriers only.
Figure 13.65 depicts a WiMAX frame with the described parameters marked.
- Frame Structure: In this section (see Figure 13.66), you can modify the following: the Frame Duration of
WiMAX frame, the Cyclic Prefix Ratio, the fixed and variable overheads for the uplink and the downlink sub-
frames, and, for TDD networks, the downlink-to-uplink subframe ratio (DL:UL Ratio) either in percentage or
(WiMAX 802.16e only) in fractions of the number of available symbol durations in one frame, and the trans-
mission and reception time guards (TTG and RTG).
The DL:UL ratio entered in fractions must include the symbol duration(s) used by the preamble or any other
fixed-duration overheads. During calculations, Atoll first determines the total amount of resources available
in one frame and then the resources effectively available for user data by removing any fixed and variable
overheads that you have defined.
- Uplink Power Control: In this section, you can enter the uplink power control Margin.
- Serving Cell Selection: In this section, you can choose the serving cell selection Method.
The following section is only available in WiMAX 802.16d documents (based on the WiMAX 802.16d project
template).
- Channel Configuration: In this section, you can enter the following: the number of subchannels per
channel, the total number of subcarriers per channel, the number of used subcarriers per channel and
the number of data subcarriers per channel.
5. Click OK. The global parameters are used during coverage predictions and simulations for the entire network.
Note: Make sure that the permutation zone quality threshold values respect the traffic power
reduction defined for the cell, and whether the frame configuration supports segmentation
or not.
The quality threshold for a permutation zone is calculated in one of two ways:
- For any permutation zone of a frame configuration that does not support segmentation,
or for the segmented permutation zone in a frame configuration that supports segmen-
tation, the quality threshold is calculated as follows:
Quality Threshold (Preamble C/N) = Required Traffic C/N + Traffic Power Reduction
For example, if the required traffic C/N is 15 dB and the traffic power reduction is 3 dB, the
quality threshold for the segmented permutation zone in this case would be 18 dB, and for
a non-segmented permutation zone would be 22.77 dB.
- Max Speed: The maximum vehicular speed supported by the permutation zone.
- Priority: The priority of the permutation zone in terms of its allocation to a user.
- Diversity Support: The type of antenna diversity technique (AAS, STTD/MRC, SU-MIMO, AMS, and MU-
MIMO) supported by the permutation zone. You cannot select more than one type of MIMO technique (STTD/
MRC, SU-MIMO, MU-MIMO, and AMS) at a time.
Specific calculations will be performed (gains will be applied) for terminals supporting AAS and MIMO. A per-
mutation zone that only supports None does not have any antenna diversity mechanism, and all the terminal
types can connect to this zone. A permutation zone that supports None and one or more antenna diversity
techniques can also support terminals capable of those diversity techniques. For example, None+AAS can
support simple as well as AAS-capable terminals, and None+AMS can support simple and MIMO-capable ter-
minals. Simple terminals cannot connect to a permutation zone that does not support None.
- Max Distance: The maximum distance from the base station covered by the permutation zone.
- Subchannel Groups (Segment 0): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned
to the segments 0.
- Subchannel Groups (Segment 1): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned
to the segments 1.
- Subchannel Groups (Segment 2): The primary (0, 2, 4) and secondary (1, 3, 5) subchannel groups assigned
to the segments 2.
The primary subchannel groups (0, 2, 4) are determined directly from the preamble index and the segment
number. For a list of correspondence between preamble indexes and subchannel groups, and a list of corre-
spondence between subchannels and subchannel groups, see "Glossary of WiMAX Terms" on page 995.
Permutation zones are allocated to users based on the Quality Threshold (dB), Max Speed (km/h), Max Distance, and
Priority parameters. The quality threshold, maximum speed, and maximum distance criteria are used to determine the
possible permutation zones for each user. Then, the highest priority permutation zone among the possible permutation
zones is allocated to the user.
To see examples of how to setup cells with and without segmentation, and how to setup cells with PUSC, FUSC, and
permutation zones of other subchannel allocation modes, see "Tips and Tricks" on page 987.
Note: In the Atoll WiMAX module, a "bearer" refers to a combination of MCS, i.e., modulation,
and coding schemes.
The WiMAX Bearers table lists the radio bearers available in Atoll by default. You can add, remove, and modify bearer
properties, if you wish.
To define WiMAX bearers:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Network Settings > WiMAX Bearers from the context menu. The WiMAX Bearers table appears.
4. In the table, enter one bearer per row. For information on working with data tables, see "Working with Data Tables"
on page 50. For each WiMAX bearer, enter:
- Radio Bearer Index: Enter a bearer index. This bearer index is used to identify the bearer in other tables,
such as the bearer selection thresholds and the quality graphs in WiMAX equipment.
- Name: Enter a name for the bearer, for example, "16QAM3/4." This name will appear in other dialogues and
results.
- Modulation: Select a modulation from the list of available modulation types. This column is for information
and display purposes only.
- Coding Rate: Enter the coding rate used by the bearer. This column is for information and display purposes
only.
- Bearer Efficiency (bits/symbol): Enter the number of useful bits that the bearer can carry in a symbol. This
information is used in throughput calculations.
For information on the relation between bearer efficiency and spectral efficiency, see "Relation Between Bear-
er Efficiency And Spectral Efficiency" on page 990.
- Bearer Selection Thresholds: In this tab (see Figure 13.69), you can modify the Bearer Selection Thresh-
olds for different mobility types. A bearer is selected for data transfer at a given pixel if the received carrier-
to-interference-and-noise ratio is higher than its selection threshold. For more information on bearers and
mobility types, see "Defining WiMAX Radio Bearers" on page 977 and "Modelling Mobility Types" on
page 906, respectively.
i. Click the Best Bearer Thresholds button to open the C/(I+N) Thresholds (dB) dialogue (see
Figure 13.70).
ii. Enter the graph values.
iii. Click OK.
For more information on the default values of the bearer selection thresholds, see "Bearer Selection Thresh-
olds" on page 988. For converting receiver equipment sensitivity values (dBm) into bearer selection thresh-
olds, see "Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 989.
Note: Subscriber lists use the mobility type "Fixed", i.e., 0 km/hr, in calculations. Make sure that
you have bearer selection thresholds defined for this mobility type in the WiMAX
equipment properties if you are working with subscriber lists.
- Quality Graphs: On this tab (see Figure 13.71), you can modify the Quality Indicator Graphs for different
bearers for different mobility types. These graphs depict the behaviour of various quality indicators under dif-
ferent radio conditions. For more information on bearers, quality indicators, and mobility types, see "Defining
WiMAX Radio Bearers" on page 977, "Defining WiMAX Quality Indicators" on page 977, and "Modelling
Mobility Types" on page 906, respectively.
i. Click the Quality Graph button to open the Quality Graph dialogue (see Figure 13.72).
ii. Enter the graph values.
iii. Click OK.
- MIMO: On this tab (see Figure 13.73), you can modify the SU-MIMO and STTD/MRC gains for different
bearers, mobility types, subchannel allocation modes (WiMAX 802.16e), BLER values, and numbers of trans-
mission and reception antennas. The capacity gain due to spatial multiplexing is the increase in channel
capacity compared to a SISO system. For more information on bearers and mobility types, see "Defining
WiMAX Radio Bearers" on page 977 and "Modelling Mobility Types" on page 906, respectively.
For more information on the different MIMO systems, see "Multiple Input Multiple Output Systems" on
page 984.
TX RX
Note: No MIMO gain (STTD/MRC, SU-MIMO, and MU-MIMO) is applied if N Ant = N Ant = 1 .
i. Enter the STTD/MRC Gain for a combination of Subchannel Allocation Mode (WiMAX 802.16e), Mo-
bility, Radio Bearer Index, Max BLER, Number of Transmission Antennas, and Number of Recep-
tion Antennas.
ii. Click the Max SU-MIMO Gain Graphs button to open the Max SU-MIMO Gain dialogue for a combination
of Subchannel Allocation Mode (WiMAX 802.16e), Mobility, Radio Bearer Index, Max BLER, Number
of Transmission Antennas, and Number of Reception Antennas (see Figure 13.74).
iii. Enter the graph values.
iv. Click OK.
You can define the STTD/MRC and SU-MIMO gains for a specific combination of subchannel allocation mode,
mobility type, bearer, and BLER, as well as the default gains for "All" subchannel allocation modes, "All" mobility
types, "All" bearers, and a Max BLER of 1. During calculations, Atoll uses the gains defined for a specific combi-
nation if available, otherwise it uses the default gains.
6. Click OK. The Properties dialogue closes. The settings are stored.
7. Click the Close button ( ) to close the WiMAX Equipment table.
3. Resource allocation for supporting the Max Throughput Demands: Once the resources have been allocated
for supporting the minimum throughput demands in the previous step, the remaining resources can be allocated
in different ways to support the maximum throughput demands of the users. The last four QoS classes can have
maximum throughput demand requirements.
For allocating resources to support the maximum throughput demands, the following types of scheduling methods
are available:
- Proportional Fair: The proportional fair scheduling method allocates the same amount of resources to all the
users with a maximum throughput demand. Therefore, the resources allocated to each user are either the
resources it requires to achieve its maximum throughput demand or the total amount of resources divided by
the total number of users in the cell, which ever is smaller.
- Proportional Demand: The proportional demand scheduling method allocates resources proportional to the
demands of users who have a maximum throughput demand. Therefore, users with higher maximum
throughput demands will have higher resulting throughputs than the users with lower maximum throughput
demands.
- Biased (QoS Class): The biased scheduling method first determines the amount of resources available for
the users of each QoS class, and then allocates these resources among the users of each QoS class like a
proportional fair scheduler. The percentage of the remaining resources that are available for any QoS class is
determined based on the QoS Class Bias Factor and the priorities of the QoS classes:
1 i
N i × ⎛ ---⎞
⎝ β⎠
% of resources available for QoS Class i = ----------------------------------- × 100
i
⎛N × ⎛ 1 ---⎞ ⎞
⎝ ∑
i ⎝ β⎠ ⎠
i
Where i represents the QoS classes that have a maximum throughput demand, i.e., ErtPS (i = 1), rtPS (i = 2),
nrtPS (i = 3), and Best Effort (i = 4). N i is the number users of QoS class i, and β is the QoS class bias de-
QoS
QoS f Bias
termined from the QoS Class Bias Factor f Bias as follows: β = 1 + ----------
-.
100
Note: The QoS Class Bias Factor should be set so as to achieve a valid value of β . For
example, for equal numbers of users in each QoS class,
QoS
- f Bias = – 90 gives β = 0.1 which allocates (approximately):
QoS
- f Bias = 9900 gives β = 100 which allocates (approximately):
- Max Aggregate Throughput: This scheduling method allocates the resources required by the users to
achieve their maximum throughput demands in the order of their traffic C/(I+N). This means that users who
are under good radio conditions, high traffic C/(I+N), will get all the resources they require. The end result of
this scheduling method is that the aggregate cell throughputs are maximised.
For all the scheduling methods, resources are allocated to support the maximum throughput demand until either
the maximum throughput demands of all the users are satisfied or the scheduler runs out of resources.
The Schedulers table lists the schedulers available in Atoll by default. You can add, remove, and modify scheduler prop-
erties, if you wish.
To define WiMAX schedulers:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Network Settings > Schedulers from the context menu. The Schedulers table appears.
4. In the table, enter one scheduler per row. For information on working with data tables, see "Working with Data
Tables" on page 50. For each scheduler, enter:
- Name: Enter a name for the scheduler. This name will appear in the cell properties.
- Scheduling Method: Select the scheduling method used by the scheduler for allocating resources to support
the maximum throughput demands.
- QoS Class Bias Factor: For the schedulers using Biased (QoS Class) scheduling method, enter the bias
factor to be used for distributing resources between different QoS classes. QoS Class Bias Factor = 0 means
no bias.
- Target Throughput for Voice Services: Select the throughput that the scheduler will target to satisfy for all
voice-type services.
- Target Throughput for Data Services: Select the throughput that the scheduler will target to satisfy for all
data-type services.
5. Click the Close button ( ) to close the Schedulers table.
Atoll’s WiMAX BWA module includes the following smart antenna modelling types:
• "Optimum Beamformer" on page 983.
• "Conventional Beamformer" on page 983.
The following section explains how to work with smart antenna equipment in Atoll:
• "Defining Smart Antenna Equipment" on page 983.
In the uplink, the powers received from served mobiles include the beamforming gains in their directions. For
taking into account the interfering mobiles, an inverse noise correlation matrix is calculated for each cell. Interfer-
ence cancellation is modelled using the MMSE adaptive algorithm. For each pair of interfered and interfering
users, the received interference and its direction are memorised. At the end of a simulation, this results in an angu-
lar distribution of the uplink noise rise calculated from the inverse noise correlation matrix.
The smart antenna simulation results include the angular distribution of the transmitted power spectral density
(downlink) and the angular distribution of the noise rise (uplink) for each cell. These results are then used to carry
out CINR-based coverage predictions for base stations using smart antennas.
In uplink, beamforming is performed to calculate the smart antenna gain towards each pixel of the studied cell
dynamically in order to determine the received power. The interference is read from the angular distribution of the
uplink noise rise (simulation result) calculated for the studied cell.
In the uplink, the powers received from served mobiles include the beamforming gains in their directions. For
taking into account the interfering mobiles, an inverse noise correlation matrix is calculated for each cell. For each
pair of interfered and interfering users, the received interference and its direction are memorised. At the end of a
simulation, this results in an angular distribution of the uplink noise rise calculated from the inverse noise correla-
tion matrix.
The smart antenna simulation results include the angular distribution of the transmitted power spectral density
(downlink) and the angular distribution of the noise rise (uplink) for each cell. These results are then used to carry
out CINR-based coverage predictions for base stations using smart antennas.
In uplink, beamforming is performed to calculate the smart antenna gain towards each pixel of the studied cell
dynamically in order to determine the received power. The interference is read from the angular distribution of the
uplink noise rise (simulation result) calculated for the studied cell.
Error) optimum beamformer. For more information on these smart antenna models in Atoll, see the Technical Reference
Guide
To create a smart antenna equipment:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Equipment > Smart Antenna Equipment from the context menu. The Smart Antenna Equipment table
appears.
4. In the Smart Antenna Equipment table, each row describes a piece of smart antenna equipment. For information
on working with data tables, see "Working with Data Tables" on page 50. For the new smart antenna equipment,
enter:
- Name: Enter a name for the smart antenna equipment.
- Antenna Model: Select Optimum Beamformer or Conventional Beamformer from the list.
- Main Antenna Model: Select the main antenna model to be used with the smart antenna equipment. The list
contains the antennas available in the Antennas folder. When you assign the smart antenna equipment to a
transmitter, you can choose to replace the current main antenna model with this model.
5. Click the Properties button. The smart antenna properties dialogue appears.
In the smart antenna properties dialogue you can modify the smart antenna equipment properties. You can also
modify the properties of the model.
a. Click the Parameters button. The smart antenna model’s properties dialogue appears.
b. Click the General tab. On the General tab, you can change the default Name of the smart antenna model.
c. Click the Properties tab (see Figure 13.75). On the Properties tab, you can define:
- Number of Elements: The number of antenna elements in the smart antenna system.
- Single Element Pattern: The antenna model to be used for each antenna element. You can select an
antenna model from the list. The list contains the antennas available in the Antennas folder.
STTD uses more than one transmission antenna to send more than one copy of the same signal. The signals are construc-
tively combined (using optimum selection or maximum ratio combining, MRC) at the receiver to extract the useful signal.
As the receiver gets more than one copy of the useful signal, the signal level at the receiver after combination of all the
copies is more resistant to interference than a single signal would be. Therefore, STTD improves the C/(I+N) at the
receiver. It is often used for the regions of a cell that have bad C/(I+N) conditions. STTD is also known as STC (Space
Time Coding) and STBC (Space-Time Block Codes).
In Atoll, you can set whether a cell (WiMAX 802.16d) or a permutation zone (WiMAX 802.16e) supports STTD/MRC by
selecting the corresponding diversity support mode in cell properties (see "Cell Description" on page 872) or frame config-
uration properties (see "Defining Frame Configurations" on page 975), respectively. STTD/MRC gains on downlink and
uplink can be defined in the WiMAX equipment for different numbers of transmission and reception antennas, mobility
types, bearers, subchannel allocation modes (WiMAX 802.16e), and maximum BLER. For more information on uplink and
downlink STTD/MRC gains, see "Defining WiMAX Equipment" on page 978. Additional gain values can be defined per
clutter class. For information on setting the additional STTD/MRC uplink and downlink gains for each clutter class or for
all clutter classes, see "Defining Clutter Class Properties" on page 115.
During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell
(uplink or downlink permutation zone in WiMAX 802.16e) that supports STTD/MRC, will benefit from the downlink and
uplink STTD/MRC C/(I+N) gains.
SU-MIMO uses more than one transmission antenna to send different signals (data streams) on each antenna. The
receiver can also have more than one antenna for receiving different signals. Using spatial multiplexing with M transmis-
sion and N reception antennas, the throughput over the transmitter-receiver link can be theoretically increased M or N
times, depending on which is smaller, M or N. SU-MIMO improves the throughput (channel capacity) for a given C/(I+N),
and is used for the regions of a cell that have sufficient C/(I+N) conditions. SU-MIMO (single-user MIMO) is also referred
to as SM (spatial multiplxing) or simply MIMO.
In Atoll, you can set whether a cell (WiMAX 802.16d) or a permutation zone (WiMAX 802.16e) supports SU-MIMO by
selecting the corresponding diversity support mode in cell properties (see "Cell Description" on page 872) or frame config-
uration properties (see "Defining Frame Configurations" on page 975), respectively. SU-MIMO capacity gains can be
defined in the WiMAX equipment for different numbers of transmission and reception antennas, mobility types, bearers,
subchannel allocation modes (WiMAX 802.16e), and maximum BLER. For more information on SU-MIMO gains, see
"Defining WiMAX Equipment" on page 978.
During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell
(uplink and downlink permutation zones in WiMAX 802.16e) that supports SU-MIMO, will benefit from the SU-MIMO gain
in its throughput depending on its traffic C/(I+N).
As SU-MIMO improves the channel capacity or throughputs, the traffic C/(I+N) of a user is first determined. Once the traffic
C/(I+N) is known, Atoll calculates the user throughput based on the bearer available at the user location. The obtained
user throughput is then increased according to the SU-MIMO capacity gain and the SU-MIMO Gain Factor of the user’s
clutter class. The capacity gains defined in Max SU-MIMO Gain graphs are the maximum theoretical capacity gains using
SU-MIMO. SU-MIMO requires rich multipath environment, without which the gain is reduced. In the worst case, there is
no gain. Therefore, it is possible to define an SU-MIMO Gain Factor per clutter class whose value can vary from 0 to 1 (0
= no gain, 1 = 100 % gain). For information on setting the SU-MIMO Gain Factor for each clutter class or for all clutter
classes, see "Defining Clutter Class Properties" on page 115.
The SU-MIMO capacity gain vs. C/(I+N) graphs available in Atoll by default have been generated based on the maximum
theoretical SU-MIMO capacity gains obtained using the following equations:
CC MIMO
G MIMO = ---------------------
-
CC SISO
TX RX ⎛ C ⁄ (I + N) ⎞
Where CC MIMO = Min ( N Ant, N Ant ) × Log 2 ⎜ 1 + ------------------------------------------⎟ is the channel capacity at a given C/(I+N) for a MIMO
TX RX
⎝ Min ( N Ant, N Ant )⎠
TX RX
system using N Ant transmission and N Ant reception antenna ports. CC SISO = Log 2 ( 1 + C ⁄ ( I + N ) ) is the channel
capacity for a single antenna system at a given C/(I+N). C/(I+N) is used as a ratio (not dB) in these formulas. You can
replace the default SU-MIMO capacity gain graphs with graphs extracted from simulated or measured values.
This is a technique for switching from SU-MIMO to STTD/MRC as the preamble signal conditions get worse than a given
threshold. AMS can be used in cells to provide SU-MIMO gains to users that have better preamble C/N conditions than a
given AMS threshold, and STTD/MRC gains to users that have worse preamble C/N conditions than the threshold. AMS
provides the optimum solution using STTD/MRC and SU-MIMO features to their best.
During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell
(uplink and downlink permutation zones in WiMAX 802.16e) that supports AMS, will benefit from the gain to be applied,
STTD/MRC or SU-MIMO, depending on the user’s preamble C/N and the AMS threshold defined in the cell properties.
STTD/MRC gain is applied to the user’s traffic C/(I+N) if the user’s preamble C/N is less than the AMS threshold, and SU-
MIMO is used if the preamble C/N is higher than the AMS threshold.
MU-MIMO (Multi-User MIMO) or Collaborative MIMO is a technique for spatially multiplexing more than one user who have
good enough radio conditions at their locations. This technique is used in uplink so that a cell with more than one reception
antenna can receive uplink transmissions from two different users over the same frequency-time allocation. This technique
provides considerable capacity gains in uplink, and can be used with single-antenna user equipment, i.e., it does not
require more than one antenna at the user equipment as opposed to SU-MIMO, which only provides considerable gains
with more than one antenna at the user equipment.
In Atoll, you can set whether a cell (WiMAX 802.16d) or an uplink permutation zone (WiMAX 802.16e) supports MU-MIMO
in uplink by selecting the corresponding diversity support mode in cell properties (see "Cell Description" on page 872) or
frame configuration properties (see "Defining Frame Configurations" on page 975), respectively. MU-MIMO capacity gains
result from the scheduling and RRM process. Using MU-MIMO, schedulers are able to allocate resources over two
spatially multiplexed parallel frames in the same frequency-time resource allocation plane. MU-MIMO can only work under
good radio conditions and if the cell has more than one reception antenna. Therefore, the preamble C/N must be higher
than the MU-MIMO threshold defined by cell in order for the scheduler to be able to multiplex users in uplink.
During the calculations of Monte Carlo simulations in Atoll, each new user connected to the first antenna creates virtual
resources available on the second antenna. These virtual resources can then be allocated to a second user connected to
the second antenna without increasing the overall load of the cell. In this way, each new mobile consumes the virtual
resources made available be the previous mobile, and may create new virtual resources available on the other antenna.
The MU-MIMO gain resulting from this uplink collaborative multiplexing is simply the ratio of the traffic loads of all the
mobiles connected to both parallel frames in uplink to the uplink traffic load of the cell. MU-MIMO is only possible for
mobiles that support MIMO and at which the preamble C/N is greater than the MU-MIMO threshold defined for their serving
cell. The MU-MIMO gain can be defined per cell by the user or it can be an output of the Monte Carlo simulations. This
gain is used during the calculation of uplink throughput coverage predictions. The channel throughput is multiplied by this
gain for pixels where MU-MIMO is used as the diversity mode.
Important: This procedure is only recommended if you have a correct subscriber list and have
complete knowledge of the services they use.
Atoll generates a realistic user distribution containing active users only during Monte Carlo simulations. The status of
these users is determined through the user’s service usage parameters defined in the user profile. In Atoll, all the subscrib-
ers have a user profile assigned to them. During Monte Carlo simulations based on subscriber lists, Atoll determines
active users from all the users in the subscriber list. If you perform calculations on subscriber lists, Atoll calculates the
channel throughputs and not the user throughputs as resource allocation is not performed in these calculations. However
in the simulations, RRM and resource allocation is carried out user throughputs can be determined.
If you want to determine user level throughputs for all the subscribers in a subscriber list, you can run a simulation on this
subscriber list after modifying the user profiles assigned to all the subscribers such that all the subscribers have an activity
probability of 100 %.
1. Create a subscriber list with subscribers having an activity probability of 100 %:
a. Create as many user profiles as there are services used by the subscribers in the list.
b. Assign only one service to each user profile.
c. Assign the following service usage parameters to the user profiles that you create:
i. For Voice services, set:
- Calls/Hour = 1.
- Duration (sec.) = 3600.
ii. For Data services:
- Calls/Hour = 1.
- UL Volume (KBytes) = UL Average Throughput x 3600 / 8.
- DL Volume (KBytes) = DL Average Throughput x 3600 / 8.
Where the UL Average Throughput and the DL Average Throughput are the uplink and downlink average
requested throughputs, respectively, of the service mentioned in the user profile.
The simulation results will contain all the subscribers in the subscriber list with their respective user throughputs
determined by Atoll after the scheduling process.
If you do not currently have reliable LTE multi-service traffic, you can provide Atoll with user density information per serv-
ice, for example, traffic data from adapted GSM Erlang maps. In this case, you do not have to create user profiles. As well,
Atoll does not have to determine the user activity probabilities to create traffic scenarios during simulations. The distribu-
tion of traffic during simulations will only depend on the user densities per service.
If you know the user densities for each service, you can set user activity probabilities to 100 % in your LTE document, as
shown below:
1. For Voice services, set:
- Calls/Hour = 1.
- Duration (sec.) = 3600.
2. For Data services:
- Calls/Hour = 1.
- UL Volume (KBytes) = UL Average Throughput x 3600 / 8.
- DL Volume (KBytes) = DL Average Throughput x 3600 / 8.
Where the UL Average Throughput and the DL Average Throughput are the uplink and downlink average re-
quested throughputs, respectively, of the service defined in the user profile.
The above settings will set the user activity probabilities to 100 %. If you create a traffic map based on environment
classes, the user density values that you define in your environment classes will be the actual user densities. This means
that, for X users/km² defined in the environment class for a given user profile, the Monte Carlo simulator will generate
exactly X users/km² for each service of the user profile.
In this way, you can know the exact number of active users and their services generated during the simulations before-
hand.
This procedure should only be used when appropriate traffic data is not available.
In WiMAX, and especially in IEEE 802.16d networks, it might be interesting to study the areas with LOS coverage only
and other areas separately. You can restrict the coverage to LOS areas only if you are using the Standard Propagation
Model. To restrict coverage to LOS areas, you have to enter a very high value for the parameter K4 in the properties of the
Standard Propagation Model.
You can define a maximum coverage range for all the transmitters in your network by entering a valid range as the Max
Range parameter.
To define the Max Range parameter:
1. Right-click the Predictions folder. The context menu appears.
2. Select Properties from the context menu. The Predictions folder’s properties dialogue appears.
3. Select the System tab.
4. Select the Max Range check box. The Max Range field in enabled.
5. Enter the Max Range of the network.
6. Click OK.
In TDD networks, the TTG and RTG parameters, available in the Global Parameters tab of the Transmitters folder’s prop-
erties dialogue, define the time delays required by the cell and mobile equipment to switch from transmission to reception
modes and vice versa. You can determine the maximum coverage range that the sectors of your WiMAX network should
have from the values of TTG and RTG and use this range as the Max Range parameter. You can calculate the maximum
system range from TTG and RTG values as follows:
Max Range (m) = Min(TTG, RTG) x 300000/2
Where TTG and RTG are values in milliseconds, Max Range is in meters, and the Min() function returns the lower of the
two values given to it in the parentheses. So, the maximum system range for TTG = 0.105 ms and RTG = 0.06 ms will be
9 km.
The default values of the bearer selection thresholds, the BLER quality graphs, and the bearer efficiency values in Atoll
have been extracted and estimated from the NS2 simulator results available with the WiMAX Forum (see Figure 13.77 and
Figure 13.78). These values correspond to to an ideal (AWGN) radio channel, and are too optimistic compared to real radio
channels. It is recommended to use more realistic values when available.
The spectral efficiency is the number of useful data bits that can be transmitted using any modulation and coding scheme
per Hz, the transition points between any two modulation and coding schemes give the default bearer selection thresholds
in Atoll, and the normalised values from the slopes of the graphs, that represent the reduction in the spectral efficiency,
give the block error rate.
You can convert the receiver sensitivity values, that are listed in the specifications of your equipment, into bearer selection
thresholds using the following conversion method:
n × BW × N Used
CNR = RS + 114 – NF – 10 × Log ⎛ ------------------------------------------⎞ + 10 × Log ( R ) – L Imp
⎝ N Total ⎠
Where RS is the receiver sensitivity in dBm, NF is the noise figure of the receiver in dB, n is the sampling factor, BW is the
channel bandwidth in MHz, N Used is the number of used subcarriers, N Total is the total number of subcarriers, R is the
number of retransmissions, and L Imp is the implementation loss in dB.
If you do not know the values for R and L Imp , you can ignore the corresponding terms and simplify the equation.
In the above explanation, the term receiver refers to the base station in uplink and to the mobile/user equipment in the
downlink.
Spectral efficiency of a modulation and coding scheme is defined as the number of useful bits that can be transmitted each
second over a channel of 1 Hz bandwidth. Spectral efficiency is hence given in terms of bps/Hz.
In Atoll, the efficiency of bearers (modulation and coding schemes) are defined in the Bearers table. The bearer efficiency
is given in terms of bits/symbol. Remember that in Atoll a symbol refers to the data transmission unit which is 1 symbol
duration long and 1 subcarrier width wide, as shown in Figure 13.79.
The concept of bearer efficiency is similar to spectral efficiency. The only difference is in the units used to define the two
entities. Here is a simple example that compares spectral efficiency and bearer efficiency, and shows that the two are the
same.
Spectral efficiency is given by:
Where BLER is the Block Error Rate, r is the coding rate for the bearer, and M is the number of modulation states. For
simplification, we set BLER = 0, and use QPSK1/2, i.e., four modulation states and r = 0.5. With these values, we get a
spectral efficiency of 1 bps/Hz for QPSK1/2. In other words, a communication channel using QPSK1/2 modulation and
coding scheme can send 1 bps of useful data per unit bandwidth.
In order to compare the bearer efficiency and spectral efficiency of QPSK1/2, let’s say that QPSK1/2 has a bearer effi-
ciency of 1 bits/symbol. Here as well, the number of bits refers to useful data bits. The width of a subcarrier in WiMAX
1
802.16e is ΔF = 10.94 kHz , from which we can calculate the useful symbol duration as well: T U = ------- = 91.4 μ sec .
ΔF
In one second, there can be 1 sec ⁄ 91.4 μ sec = 10940 symbol durations. If 10940 symbols are transmitted using
QPSK1/2, this gives us a data rate of 10940 Symbols/sec × 1 bits/Symbol = 10940 bps , which is the data rate achieva-
ble using one subcarrier of 10.94 kHz. We can find the spectral efficiency by normalizing the data rate to unit bandwidth.
This gives: 10940 bps/subcarrier ⁄ 10.94 kHz/subcarrier = 1 bps/Hz
In order to compare equivalent quantities, we have ignored the system parameters such as the cyclic prefix, TTG, RTG,
and have considered that the entire frame is transmitted in one direction, uplink or downlink.
In TDD networks, the durations of the downlink and uplink subframes have to be properly set in order to optimally satisfy
the traffic demands in both downlink and uplink. You can use the simulation results to calculate the approximate value of
the DL:UL Ratio required for your network under the given traffic scenario of the simulation. The DL:UL Ratio can be
calculated by taking the ratio of the sum of the downlink traffic loads of all the cells and the sums of all the downlink and
uplink traffic loads of all the cells. The downlink and uplink traffic loads of all the cells are listed in the Cells tab of the simu-
lations results dialogue.
∑
DL
TL
All Cells
DL:UL Ratio = ------------------------------------------------------------------
-
∑ ∑
DL UL
TL + TL
All Cells All Cells
You can then set this value of DL:UL Ratio in the Global Parameters tab of the Transmitters folder’s properties dialogue,
for optimising your network’s resource usage.
iii. Double-click the frame configuration FFT Size 512. The Permutation Zones table appears.
iv. Activate the permutation zones 0 (PUSC DL) and 8 (PUSC UL).
v. Click OK.
vi. Close the Frame Configurations tables.
b. Set up the cells:
i. Right-click the Transmitters folder. The context menu appears.
ii. Select Cells > Open Table from the context menu. The Cells table appears.
iii. In the Cells table, enter:
- Channel Number: 0
- Frame Configuration: FFT Size 512
iv. Close the Cells table.
c. Create a coverage by downlink traffic C/(I+N) level and a coverage by downlink channel throughput as ex-
plained in "Making a Coverage by C/(I+N) Level" on page 910 and "Making a Coverage by Throughput" on
page 914, respectively.
In this case, the same 5 MHz channel is allocated to the three sectors of each 3-sector site. The sectors receive
co-channel interference according to the downlink traffic loads of the interferers. The traffic C/(I+N) and throughput
coverage predictions would be as shown in Figure 13.80 and Figure 13.81.
Figure 13.80: Downlink Traffic C/(I+N) Coverage Prediction - PUSC Without Segmentation
Figure 13.81: Downlink Channel Throughput Coverage Prediction - PUSC Without Segmentation
2. With a segmented PUSC permutation zone, i.e., a frequency reuse plan of N=3.
a. Set up the frame configuration:
i. Open the Frame Configurations table as explained in "Defining Frame Configurations" on page 975.
ii. Select the Segmentation Support check box for FFT Size 512.
iii. Double-click the frame configuration FFT Size 512. The Permutation Zones table appears.
iv. Activate the permutation zones 0 (PUSC DL) and 8 (PUSC UL).
v. Click OK.
vi. Close the Frame Configurations tables.
b. Set up the cells:
i. Right-click the Transmitters folder. The context menu appears.
ii. Select Cells > Open Table from the context menu. The Cells table appears.
iii. In the Cells table, enter:
- Channel Number: 0
- Frame Configuration: FFT Size 512
- Preamble Index: 0 for the 1st sector, 32 for the 2nd sector, and 64 for the 3rd sector of each 3-sector site.
- Segmentation Usage (DL) (%): 100%
iv. Close the Cells table.
c. Create a coverage by downlink traffic C/(I+N) level and a coverage by downlink channel throughput as ex-
plained in "Making a Coverage by C/(I+N) Level" on page 910 and "Making a Coverage by Throughput" on
page 914, respectively.
In this case, the 5 MHz channel is divided into 3 segments. Each segment is allocated to one of the three sectors
of each 3-sector site. There is no interference between segments because the Preamble Indexes give a different
segment and same Cell PermBase (IDCell in IEEE specifications). Each segment uses 1/3rd of the total number
of used subcarriers, i.e., 140. The traffic C/(I+N) and throughput coverage predictions would be as shown in
Figure 13.82 and Figure 13.83.
Figure 13.82: Downlink Traffic C/(I+N) Coverage Prediction - PUSC With Segmentation
Figure 13.83: Downlink Channel Throughput Coverage Prediction - PUSC With Segmentation
3. With a segmented PUSC permutation zone and one or more non-segmented zones, i.e., a frequency reuse plan
of pseudo-N=3.
a. Set up the frame configuration:
i. Open the Frame Configurations table as explained in "Defining Frame Configurations" on page 975.
ii. Select the Segmentation Support check box for FFT Size 512.
iii. Double-click the frame configuration FFT Size 512. The Permutation Zones table appears.
iv. Activate the permutation zones 0 (PUSC DL), 2 (FUSC) and 8 (PUSC UL).
v. Click OK.
vi. Close the Frame Configurations tables.
b. Set up the cells:
i. Right-click the Transmitters folder. The context menu appears.
ii. Select Cells > Open Table from the context menu. The Cells table appears.
iii. In the Cells table, enter:
- Channel Number: 0
- Frame Configuration: FFT Size 512
- Preamble Index: 0 for the 1st sector, 32 for the 2nd sector, and 64 for the 3rd sector of each 3-sector site.
iv. Close the Cells table.
c. Allocate different segmentation usage ratios to the cells:
- Enter different segmentation usage ratios manually in the Cells table, or calculate the segmentation usage
ratios for all the cells using a Monte Carlo simulation as follows:
Create or import a traffic map, as explained in "Creating a Traffic Map" on page 937, to be used as input
to the Monte Carlo simulator.
Create a new Monte Carlo simulation as explained in "Creating Simulations" on page 952.
Open the simulation results, and commit the results to the Cells table as explained in "Updating Cell Load
Values With Simulation Results" on page 962.
d. Create a coverage by downlink traffic C/(I+N) level and a coverage by downlink channel throughput as ex-
plained in "Making a Coverage by C/(I+N) Level" on page 910 and "Making a Coverage by Throughput" on
page 914, respectively.
In this case, the 5 MHz channel is divided into 3 segments. Each segment is allocated to one of the three sectors
of each 3-sector site. There is no interference between segments because the Preamble Indexes give a different
segment and same Cell PermBase (IDCell in IEEE specifications). Each segment uses 1/3rd of the total number
of used subcarriers, i.e., 140. However, there is also a non-segmented FUSC permutation zone, which uses the
entire channel width of 5 MHz. The sectors receive co-channel interference during the FUSC part of the frame but
not during the segmented PUSC part of the frame. The traffic C/(I+N) and throughput coverage predictions would
be as shown in Figure 13.84 and Figure 13.85.
Figure 13.84: Downlink Traffic C/(I+N) Coverage Prediction - Segmented PUSC + FUSC
Figure 13.85: Downlink Channel Throughput Coverage Prediction - Segmented PUSC + FUSC
If you compare the traffic C/(I+N) and throughput coverage predictions in the above cases, you will observe that the traffic
C/(I+N) improves with segmentation, but the throughput is reduced.
VoIP codecs are application-layer elements in the OSI system model. Atoll models application throughputs using a
throughput offset and a scaling factor with respect to the MAC layer throughputs. You can model different VoIP codecs by
creating a new service for each VoIP codec, and setting the target throughput to the Application Throughput for the
scheduler used. Here are two examples of the most common VoIP codecs, and how they can be modelled in Atoll:
• G.711 VoIP Codec
The actual voice data rate needed by the G.711 codec is 64 kbps, but with the lower layer headers and other
added bits, the needed MAC data rate could be between 66.4 and 107.2 kbps. In this example, we show how to
model the codec with header bits that lead to 85.6 kbps MAC data rate.
b. Set the Target Throughput for Voice Services to "2 - Application Throughput" for the scheduler being used.
In this way, Atoll will allocate resources to the users of this service such that they get 64 kbps application through-
put, and around 85.6 kbps of effective MAC throughput.
There are four types of AMC subchannels. The four types of AMC subchannels have different collections of bins in a band.
In the first type (6 x 1; default type), a subchannel consists of six consecutive bins in the same symbol. A subchannel is
two bins by three symbols in the second type (2 x 3), three bins by two symbols in the third type (3 x 2), and one bin by six
symbols in the fourth type (1 x 6). The default values of the numbers of subchannels per channel represent the first
(default) type of subchannels. The number of subchannels per channel is calculated by dividing the total number of subcar-
riers by the number of subcarriers in a subchannel. The number of subcarriers per subchannel is 54, 27, 18, and 9 in the
first (default), second, third, and fourth types, respectively. Therefore, for modelling a type of subchannels other than the
default (6 x 1), you will have to increase the number of subchannels per channel accordingly, i.e., multiply the current value
by 2, 3, and 6, for modelling the second, third, and fourth types, respectively.
In Atoll, you can study the effect of interference received by your network from other WiMAX networks. The interfering
WiMAX network can be a different part of your own network, or a network belonging to another operator.
To study interference from co-existing networks:
1. Import the interfering network data (sites, transmitters, and cells) in to your document as explained in "Creating a
Group of Base Stations" on page 881.
2. For the interfering network’s transmitters, set the Transmitter Type to Extra-Network (Interferer Only) as
explained in "Transmitter Description" on page 870.
During calculations, Atoll will consider the transmitters of type Extra-Network (Interferer Only) when calculating
interference. These transmitters will not serve any pixel, subscriber, or mobile, and will only contribute to interfer-
ence.
Modelling the interference from co-existing networks will be as accurate as the data you have for the interfering network.
If the interfering network is a part of your own network, this information would be readily available. However, if the inter-
fering network belongs to another operator, the information available might not be accurate.
Moreover, for other operators’ networks, and if the interfering networks use OFDM but are not WiMAX networks,, you will
have to create specific frame configurations to assign to the cells of the interfering network. The number of subcarriers
used in these frame configurations would depend on the channel bandwidth on which transmitter is interfering. For more
information on frame configuration parameters, see "Defining Frame Configurations" on page 975.
• Effective MAC Throughput: The net MAC layer throughput (user or channel) that can be achieved at a given
location using the highest WiMAX bearer available computed taking into account the reduction of throughput due
to retransmission due to errors.
• Application Throughput: The application layer throughput (user or channel) that can be achieved at a given loca-
tion using the highest WiMAX bearer available computed taking into account the reduction of throughput due to
PDU/SDU header information, padding, encryption, coding, and other types of overhead.
• Channel Throughputs: Peak MAC, effective MAC or application throughputs achieved at a given location using
the highest WiMAX bearer available with the entire cell resources (uplink or downlink).
• User Throughputs: Peak MAC, effective MAC or application throughputs achieved at a given location using the
highest WiMAX bearer available with the amount of resources allocated to a user by the scheduler.
• Traffic Loads: The uplink and downlink traffic loads are the percentages of the uplink and the downlink subframes
in use (allocated) to the traffic (mobiles) in the uplink and in the downlink, respectively.
• Uplink Noise Rise: Uplink noise rise is a measure of uplink interference with respect to the uplink noise.
I UL + N UL
NR UL = ------------------------
-
N UL
• Frame Configuration: A frame configuration is the description of a frame in the frequency as well as in the time
dimension. In the frequency domain, it defines how many subcarriers exist in the channel width used, and how
many of these subcarriers are used and for which purpose, i.e., pilot, data, DC, guard. In the time domain, it
defines how long the frame is, and its composition. The time-domain composition of the frame is simpler in WiMAX
802.16d than in 802.16e.
In WiMAX 802.16d networks, the frame configuration does not depend on the channel width and can be defined
in the Global Parameters tab of the Transmitters folder’s properties dialogue as explained in "The Options on the
Global Parameters Tab" on page 972.
In WiMAX 802.16e, the frame configuration depends on the channel width because the system uses Scalable
OFDMA. The IEEE specifications define different frame configurations for different channel widths. For example,
a cell using a 10 MHz channel width will have 1024 subcarriers, but one using a 5 MHz channel will have 512. As
well, in the time domain, the number of active permutation zones in the frame and the subchannel allocation
modes of these zones depend on the operator and the equipment used. You can create or modify frame configu-
rations and their corresponding permutation zones in Atoll as explained in "Defining Frame Configurations" on
page 975.
• Permutation Zone: A permutation zone is a subdivision of a WiMAX frame in the time domain. According to the
IEEE specifications, there can be as many as 8 permutation zones in the downlink and 3 in the uplink. Each per-
mutation zone can use a different subchannel allocation mode (or a permutation scheme), and can have different
numbers of used, pilot, and data subcarriers. The different subchannel allocation modes are: PUSC, FUSC,
OFUSC, AMC, TUSC1, and TUSC2 in downlink, and PUSC, OPUSC, and AMC in uplink.
• Segmentation: The PUSC subchannel allocation mode in downlink allows the allocation of groups of subchannels
to cells. According to the IEEE specifications, there are 6 subchannel groups in the downlink PUSC subchannel
allocation mode. You can, for example, use 2 subchannel groups at each sector of a 3-sector site, and completely
eliminate interference between these sectors by setting the preamble index parameter correctly. On one hand,
segmentation improves the CINR by allowing you to different segments of the same channel at different sectors.
But on the other hand, it reduces the available cell capacity (throughput) because the channel width used at each
sector is reduced. For examples on how to use segmentation in Atoll, see "Tips and Tricks" on page 987.
• Primary and Secondary Subchannel Groups: For frame configurations with 1024 and 2048 total subcarriers,
you can choose which secondary subchannel groups are used at cells along with the one primary subchannel
group, which is given by the preamble index of the cell. Frame configurations with 128 and 512 total subcarriers
only have primary subchannel groups and no secondary subchannel groups. Therefore, the knowledge of only the
preamble index is sufficient in these cases (each segment uses 1/3rd of the channel bandwidth.)
The preamble index set in the cell gives the segment number as well as the primary subchannel group number in
the case of segmentation:
Primary
Preamble Index Segment Subchannel
Group
0-31, 96, 99, 102, 105, 108, 111 0 0
The secondary subchannel groups (1, 3, and 5) can be allocated to any cell as required.
1 N/A 1 6-9
2 1 2 10-15
128 1024
3 N/A 3 16-19
4 2 4 20-25
5 N/A 5 26-29
0 0-4 0 0-11
1 N/A 1 12-19
2 5-9 2 20-31
512 2048
3 N/A 3 32-39
4 10-14 4 40-51
5 N/A 5 52-59
• Resources: In Atoll, the term "resource" is used to refer to the average number of slots, expressed in % (as traffic
loads, when the average is performed over a considerably long duration) of the total number of slots in a super-
frame of 1 sec.
Atoll
RF Planning and Optimisation Software
Chapter 14: LTE Networks
14 LTE Networks
LTE (Long Term Evolution) refers to the set of 3GPP (3rd Generation Partnership Project) Release 8 and Release 9 spec-
ifications which describe the next steps, or evolution, of the existing GERAN (GSM EDGE Radio Acces Networks) and
UTRAN (UMTS Terrestrial Radio Access Networks) specifications. The 3GPP LTE specifications describe the building
blocks of the eUTRA (evolved UTRA) networks. LTE uses SOFDMA (Scalable Orthogonal Frequency Division Multiple
Access) and SC-FDMA (Single-Carrier Frequency Division Multiple Access) technologies in the downlink and the uplink,
respectively. The aim of LTE is to provide mobile broadband wireless access that supports handovers between LTE cells
as well as between LTE and UMTS/GSM cells at high user speeds.
Atoll enables you to design LTE broadband wireless access networks. Atoll can predict radio coverage, manage mobile
and fixed subscriber data, and evaluate network capacity. Atoll LTE also supports MIMO.
Atoll enables you to model fixed and mobile users in LTE environments. The data input corresponding to mobile users
and fixed subscribers is modelled through comprehensive support of mobile user traffic maps and subscriber databases,
respectively. You can carry out calculations on fixed subscriber locations as well as base your calculations on mobile user
scenarios during Monte Carlo simulations. You can also perform interference predictions, resource allocation, and other
calculations on mobile users.
Atoll uses Monte Carlo simulations to generate realistic network scenarios (snapshots) using a Monte Carlo statistical
engine for scheduling and resource allocation. Realistic user distributions can be generated using different types of traffic
maps or subscriber data. Atoll uses these realistic user distributions as input for the simulations.
Coverage predictions can be created to study the following parameters:
• The reference signal level received from cells
• The effective reference signal level
• The effective SCH/PBCH, PDSCH/PDCCH, and PUSCH/PUCCHsignal levels
• The carrier-to-interference-and-noise ratio for the reference signals, SCH/PBCH, PDSCH/PDCCH, and PUSCH
• The radio bearer coverage
• The channel throughput and cell capacity per pixel, and the aggregate throughput per cell
Coverage predictions that depend on the network’s traffic loads can be created from either Monte Carlo simulation results
or from a user-defined network load configuration (uplink and downlink traffic loads, and uplink noise rise). GSM GPRS
EGPRS, CDMA2000 1xRTT, CDMA2000 1xEV-DO, UMTS HSPA, and LTE: networks can be planned in the same Atoll
session.
Tip: Before working with the Atoll LTE module for the first time, it is highly recommended to
go through the "Glossary of LTE Terms" on page 1114. This will help you get accustomed
to the terminology used by the 3GPP and in Atoll.
4. Allocate neighbours ( 4 ).
- "Planning Neighbours" on page 1052.
5. Allocate frequencies ( 5 ).
- "Planning Frequencies" on page 1061.
7. Before making more advanced coverage predictions, you need to define cell load conditions ( 7 ).
You can define cell load conditions in the following ways:
- You can generate realistic cell load conditions by creating a simulation based on traffic maps and subscriber
lists ( 7a , 7b , and 7c ) (see "Studying Network Capacity" on page 1069).
- You can define cell load conditions manually either on the Cells tab of each transmitter’s Properties dialogue
or in the Cells table (see "Creating or Modifying a Cell" on page 1008) ( 7d ).
8. Make LTE-specific signal quality coverage predictions using the defined cell load conditions ( 8 ).
- "LTE Coverage Predictions" on page 1036.
9. If necessary, modify network parameters to study the network with a different frequency plan ( 10 ). After modifying
the network’s frequency plan, you must perform steps 7 and 8 again.
6
7a
7c 7d
7b
7
9 10
Atoll enables you to model network traffic by allowing you to create services, users, user profiles, environments, and termi-
nals. This data can be then used to make studies that depend on network load, such as C/(I+N), LTE radio bearer, and
throughput coverage predictions.
In this section, the following are explained:
• "Creating an LTE Base Station" on page 1003.
• "Creating a Group of Base Stations" on page 1014.
• "Modifying Sites and Transmitters Directly on the Map" on page 1014.
• "Display Tips for Base Stations" on page 1014.
• "Creating a Multi-Band LTE Network" on page 1015.
• "Setting the Working Area of an Atoll Document" on page 1015.
• "Studying a Single Base Station" on page 1015.
• "Studying Base Stations" on page 1019.
• "Planning Neighbours" on page 1052.
• "Planning Frequencies" on page 1061.
• "Planning Physical Cell IDs" on page 1065.
Tip: While this method allows you to place a site with precision, you can also place sites using
the mouse and then position them precisely with this dialogue afterwards. For information
on placing sites using the mouse, see "Moving a Site Using the Mouse" on page 31.
- Altitude: The altitude, as defined by the DTM for the location specified under Position, is given here. You can
specify the actual altitude under Real, if you wish. If an altitude is specified here, Atoll will use this value for
calculations.
- Comments: You can enter comments in this field if you wish.
- Active: If this transmitter is to be active, you must select the Active check box. Active transmitters are dis-
played in red in the Transmitters folder of the Data tab.
Note: Only active transmitters are taken into consideration during calculations.
- Transmitter Type: If you want Atoll to consider the transmitter as a potential server as well as an interferer,
set the transmitter type to Intra-Network (Server and Interferer). If you want Atoll to consider the transmitter
only as an interferer, set the type to Extra-Network (Interferer Only). No coverage for an Interferer Only
transmitter will be calculated for coverage predictions and it will not serve any mobile in Monte Carlo simula-
tions.
This feature enables you to model the co-existence of different networks in the same geographic area. For
more information on how to study interference between co-existing networks, see "Modelling the Co-existence
of Networks" on page 1114.
- Transmission/Reception: Under Transmission/Reception, you can see the total losses and the noise
figure of the transmitter. Atoll calculates losses and noise according to the characteristics of the equipment
assigned to the transmitter. Equipment can be assigned using the Equipment Specifications dialogue which
appears when you click the Equipment button.
- On the Equipment Specifications dialogue (see Figure 14.4), the equipment you select and the gains and
losses you define are used to initialise total transmitter losses in the uplink and downlink:
- TMA: You can select a tower-mounted amplifier (TMA) from the list. You can click the Browse button
( ) to access the properties of the TMA. For information on creating a TMA, see "Defining TMA Equip-
ment" on page 147.
- Feeder: You can select a feeder cable from the list. You can click the Browse button ( ) to access the
properties of the feeder. For information on creating a feeder cable, see "Defining Feeder Cables" on
page 147.
- BTS: You can select a base transceiver station (BTS) equipment from the BTS list. You can click the
Browse button ( ) to access the properties of the BTS. For information on creating a BTS, see "Defin-
ing BTS Equipment" on page 148.
- Feeder Length: You can enter the feeder length at transmission and reception.
- Miscellaneous Losses: You can enter miscellaneous losses at transmission and reception. The value
you enter must be positive.
- Receiver Antenna Diversity Gain: You can enter a receiver antenna diversity gain. The value you enter
must be positive.
Atoll always considers the values in the Real boxes in coverage predictions even if they are different from the
values in the Computed boxes. The information in the real BTS Noise Figure reception box is calculated from
the information you entered in the Equipment Specifications dialogue. You can modify the real Total Loss-
es at transmission and reception and the real BTS Noise Figure at reception if you wish. Any value you enter
must be positive.
- Antennas:
- Height/Ground: The Height/Ground box gives the height of the antenna above the ground. This is added
to the altitude of the site as given by the DTM. If the transmitter is situated on a building, the height entered
must include the height of building.
- Main Antenna: Under Main Antenna, the type of antenna is visible in the Model list. You can click the
Browse button ( ) to access the properties of the antenna. The other fields, Azimuth, Mechanical
Downtilt, and Additional Electrical Downtilt, display additional antenna parameters.
- Number of Antenna Ports: Select the number of antenna ports used for MIMO in the Transmission and
Reception fields. For more information on how the number of antenna ports are used, see "Multiple Input
Multiple Output Systems" on page 1108.
- Under Secondary Antennas, you can select one or more secondary antennas in the Antenna column
and enter their Azimuth, Mechanical Downtilt, Additional Electrical Downtilt, and % Power, which is
the percentage of power reserved for this particular antenna. For example, for a transmitter with one
secondary antenna, if you reserve 40 % of the total power for the secondary antenna, 60 % is available
for the main antenna.
For information on working with data tables, see "Working with Data Tables" on page 50.
• Reference Signal C/N Threshold (dB): The minimum reference signal C/N required for a user to be connected
to the cell. The reference signal C/N is compared with this threshold to determine whether or not a user is within
the cell’s coverage or not.
• LTE Equipment: You can select the cell’s LTE equipment from the LTE Equipment list. For more information, see
"Defining LTE Equipment" on page 1104. The cell’s LTE equipment parameters are used in the uplink calcula-
tions.
• Scheduler: The scheduler used by the cell for resource allocation during Monte Carlo simulations. You can select
the scheduler from the list of schedulers available in the Schedulers table. For more information see "Defining
LTE Schedulers" on page 1107.
• Max Number of Users: The maximum number of simultaneous connected users supported by the cell.
• Frame Configuration: The frame configuration used by the cell when the cell’s frequency band is TDD. If the net-
work’s switching point periodicity is set to "Half Frame", you can select a frame configuration of type D-UUU D-
UUU, D-UUD D-UUD, or D-UDD D-UDD. If the network’s switching point periodicity is set to "Frame", you can
select a frame configuration of type D-UUU DDDDD, D-UUD DDDDD, or D-UDD DDDDD. For more information
on TDD switching point periodicity, see "The Global Transmitter Parameters" on page 1102.
• Diversity Support (DL): The type of antenna diversity technique (None, Transmit Diversity, SU-MIMO, or AMS)
supported by the cell in downlink.
• Diversity Support (UL): The type of antenna diversity technique (None, Receive Diversity, SU-MIMO, AMS, or
MU-MIMO) supported by the cell in uplink.
Specific calculations will be performed (gains will be applied) for terminals supporting MIMO.
• AMS/MU-MIMO Threshold (dB): For AMS, it is the reference signal C/N threshold for switching from SU-MIMO
to Transmit Diversity as the reference signal C/N gets worse than the given value. For MU-MIMO, it is the minimum
required reference signal CNR for using MU-MIMO. For more information on Adaptive MIMO switching, see "Mul-
tiple Input Multiple Output Systems" on page 1108.
• MU-MIMO Gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO. This can be user-defined
or an output of Monte Carlo simulations. In uplink throughput coverage predictions, the cell capacity will be multi-
plied by this gain at pixels where MU-MIMO is used.
• Max Traffic Load (UL) (%): The uplink traffic load not to be exceeded. This limit can be taken into account during
Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have an uplink
traffic load greater than this maximum.
• Traffic Load (UL) (%): The uplink traffic load percentage. By default, the uplink traffic load is set to 100 %.
• Max Traffic Load (DL) (%): The downlink traffic load not to be exceeded. This limit can be taken into account
during Monte Carlo simulations. If the cell traffic load is limited by this value, the cell will not be allowed to have a
downlink traffic load greater than this maximum.
• Traffic Load (DL) (%): The downlink traffic load percentage. By default, the downlink traffic load is set to 100 %.
• UL Noise Rise (dB): The uplink noise rise in dB. By default, the uplink noise rise is set to 0 dB.
Note: You can set the values for uplink and downlink traffic loads, and the uplink noise rise
manually to actual network values, or use the values computed during Monte Carlo
simulations. Monte Carlo simulation results can be stored in the cells by clicking the
Commit Results button in the simulation results dialogue.
• Max Number of Intra-technology Neighbours: The maximum number of neighbours from within the same Atoll
document that the cell can have.
• Max Number of Inter-technology Neighbours: The maximum number of neighbours from other technology doc-
uments that the cell can have.
• Neighbours: You can access a dialogue in which you can set both intra-technology and inter-technology neigh-
bours by clicking the Browse button ( ). For information on defining neighbours, see "Planning Neighbours"
on page 1052.
Tip: The Browse button ( ) might not be visible in the Neighbours box if this is a new cell.
You can make the Browse button appear by clicking Apply.
Tips:
• If you are creating several transmitters at the same time, or modifying several existing trans-
mitters, you can do it more quickly by editing or pasting the data directly in the Transmitters
table. You can open the Transmitters table by right-clicking the Transmitters folder on the
Data tab of the Explorer window and selecting Open Table from the context menu. For infor-
mation on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
• If you want to add a transmitter to an existing site on the map, you can add the transmitter by
right-clicking the site and selecting New Transmitter from the context menu.
Tips:
• If you are creating or modifying several cells at the same time, you can do it more quickly by
editing the data directly in the Cells table. You can open the Cells table by right-clicking the
Transmitters folder on the Data tab of the Explorer window and selecting Cells > Open
Table from the context menu. You can either edit the data in the table, paste data into the table
(see "Copying and Pasting in Tables" on page 56), or import data into the table (see "Importing
Tables from Text Files" on page 59).
• If you want to add a cell to an existing transmitter on the map, you can add the cell by right-
clicking the transmitter and selecting New Cell from the context menu.
3. In the map window, move the pointer over the map to where you would like to
place the new station. The exact coordinates of the pointer’s current location
are visible in the Status bar.
Tips:
• To place the base station more accurately, you can zoom in on the map before you click the
New Transmitter or Station button. For information on using the zooming tools, see
"Changing the Map Scale" on page 38.
• If you let the pointer rest over the base station you have placed, Atoll displays its tip text with
its exact coordinates, allowing you to verify that the location is correct.
You can also place a series of base stations using a station template. You do this by defining an area on the map where
you want to place the base stations. Atoll calculates the placement of each base station according to the defined hexag-
onal cell radius in the station template. For information on defining the cell radius, see "Creating or Modifying a Station
Template" on page 1010.
To place a series of base stations within a defined area:
1. In the Radio toolbar, select a template from the list.
2. Click the Hexagonal Design button ( ), to the left of the template list. A hexagonal design is a group of base
stations created from the same station template.
Note: If the Hexagonal Design button is not available ( ), the hexagonal cell radius for this
template is not defined. For information on defining the cell radius, see "Creating or
Modifying a Station Template" on page 1010.
3. Draw a zone delimiting the area where you want to place the series of base stations:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
You can work with the sites and transmitters in these base stations as you work with any base station object, adding, for
example, another antenna to a transmitter.
When you place a new station using a station template as explained in "Placing a New Base Station Using a Station
Template" on page 1009, the site is created at the same time as the station. However, you can also place a new station
on an existing site.
To place a base station on an existing site:
1. On the Data tab, clear the display check box beside the Hexagonal Design folder.
2. In the Radio toolbar, select a template from the list.
- Under Propagation, you can modify the following: the Propagation Model, Radius, and Resolution for both
the Main Matrix and the Extended Matrix. For information on propagation models, see Chapter 5: Managing
Calculations in Atoll.
5. Click the Transmitter tab. In this tab (see Figure 14.7), if the Active check box is selected, you can modify the
following:
- Under Transmission/Reception, you can click the Equipment button to open the Equipment Specifica-
tions dialogue and modify the tower-mounted amplifier (TMA), feeder cables, or base transceiver station
(BTS). For information on the Equipment Specifications dialogue, see "Transmitter Description" on
page 1004.
The information in the computed Total Losses in transmission and reception boxes is calculated from the in-
formation you entered in the Equipment Specifications dialogue (see Figure 14.4 on page 1005). Atoll al-
ways considers the values in the Real boxes in coverage predictions even if they are different from the values
in the Computed boxes. You can modify the real Total Losses at transmission and reception if you wish. Any
value you enter must be positive.
The information in the computed BTS Noise Figure reception box is calculated from the information you en-
tered in the Equipment Specifications dialogue. You can modify the real BTS Noise Figure at reception if
you wish. Any value you enter must be positive.
6. Click the LTE tab. In this tab (see Figure 14.8), you can modify the following:
- Under Power and EPRE Offsets Relative to the Reference Signals, you can modify the Max Power, and
the EPRE offsets for the SCH and PBCH, and the PDSCH and PDCCH in SCH/PBCH Offset, and PDSCH/
PDCCH Offset.
- Frequency Band, Channel Number, Channel Allocation Status, Physical Cell ID, Physical Cell ID
Status, Min Reuse Distance, LTE Equipment, Scheduler, Max Number of Users, Frame Configuration,
and Reference Signal C/N Threshold.
- Under Antenna Diversity, you can select the Diversity Support in downlink and in uplink, enter the AMS/
MU-MIMO Threshold, and define the default MU-MIMO Gain.
- Under Default Loads, you can enter the default values for DL Traffic Load, UL Traffic Load, UL Noise Rise,
and the Max DL Traffic Load and Max UL Traffic Load.
- Under Inter-technology Interference, you can set the DL Noise Rise and the UL Noise Rise. For more infor-
mation on inter-technology interference, see "Modelling Inter-Network Interferences" on page 236.
- Under Max Number of Neighbours, you can set the maximum numbers of Intra-technology and Inter-tech-
nology neighbours.
7. Click the Other Properties tab. The Other Properties tab will only appear if you have defined additional fields in the
Sites table, or if you have defined an additional field in the Station Template Properties dialogue.
8. When you have finished setting the parameters for the station template, click OK to close the dialogue and save
your changes.
5. In the map window, move the pointer over the map to where you would like to place the new base station. The
exact coordinates of the pointer’s current location are visible in the Status bar.
Tips:
• To place the station more accurately, you can zoom in on the map before you select Duplicate
from the context menu. For information on using the zooming tools, see "Changing the Map
Scale" on page 38.
• If you let the pointer rest over the station you have placed, Atoll displays tip text with its exact
coordinates, allowing you to verify that the location is correct.
You can also place a series of duplicate base stations by pressing and holding CTRL in step 6. and clicking to
place each duplicate station.
For more information on the site, transmitter, and cell properties, see "Definition of a Base Station" on page 1003.
Note: When you import data into your current Atoll document, the coordinate system of the
imported data must be the same as the display coordinate system used in the document.
If you cannot change the coordinate system of your source data, you can temporarily
change the display coordinate system of the Atoll document to match the source data.
For information on changing the coordinate system, see "Setting a Coordinate System"
on page 92.
Important: The table you copy from must have the same column layout as the table you are pasting
data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
• Importing data: If you have base station data in text or comma-separated value (CSV) format, you can import it
into the tables in the current document. If the data is in another Atoll document, you can first export it in text or
CSV format and then import it into the tables of your current Atoll document. When you are importing, Atoll allows
you to select what values you import into which columns of the table.
When you create a group of base stations by importing data, you must import site data in the Sites table, trans-
mitter data in the Transmitters table, and cell data in the Cells table, in that order.
For information on exporting table data, see "Exporting Tables to Text Files" on page 58. For information on
importing table data, see "Importing Tables from Text Files" on page 59.
Note: You can quickly create a series of base stations for study purposes using the Hexagonal
Design tool on the Radio toolbar. For information, see "Placing a New Base Station
Using a Station Template" on page 1009.
from fields that you add. The label is always displayed, so you should choose information that you would want to
always be visible; too much information in the label will make it harder to distinguish the information you are looking
for. For information on defining the label, see "Defining the Object Type Label" on page 35.
• Tooltips: You can display information about each object, such as each site or transmitter, in the form of a tooltip
that is only visible when you move the pointer over the object. You can choose to display more information than
in the label, because the information is only displayed when you move the pointer over the object. You can display
information from every field in that object type’s data table, including from fields that you add. For information on
defining the tool tips, see "Defining the Object Type Tip Text" on page 36.
• Transmitter colour: You can set the transmitter colour to display information about the transmitter. For example,
you can select "Discrete Values" to distinguish transmitters by antenna type, or to distinguish inactive from active
transmitters. You can also define the display type for transmitters as "Automatic." Atoll then automatically assigns
a colour to each transmitter, ensuring that each transmitter has a different colour than the transmitters surrounding
it. For information on defining the transmitter colour, see "Defining the Display Type" on page 34.
• Transmitter symbol: You can select one of several symbols to represent transmitters. For example, you can
select a symbol that graphically represents the antenna half-power beamwidth ( ). If you have two transmit-
ters on the same site with the same azimuth, you can differentiate them by selecting different symbols for each
( and ). For information on defining the transmitter symbol, see "Defining the Display Type" on page 34.
It is important not to confuse the computation zone and the focus zone or hot spot zones. The computation zone
defines the area where Atoll computes path loss matrices, coverage predictions, Monte Carlo simulations, etc.,
while the focus zone or hot spot zones are the areas taken into consideration when generating reports and results.
For information on the computation zone, see "Creating a Computation Zone" on page 1023.
You can combine a computation zone and a filter, in order to create a very precise selection of the base stations to be
studied.
Before studying a base station, you must assign a propagation model. The propagation model takes the radio and
geographic data into account and computes propagation losses along the transmitter-receiver path. This allows you to
predict the received signal level at any given point. Any coverage prediction you make on a base station uses the propa-
gation model to calculate its results.
In this section, the following are explained:
• "Making a Point Analysis to Study the Profile" on page 1016.
• "Studying Signal Level Coverage" on page 1017.
2. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
3. A line appears on the map connecting the selected transmitter and the current position. You can now do the fol-
lowing:
- Move the receiver to change the current position.
- Click to place the receiver at the current position. You can move the receiver again by clicking it a second time.
- Right-click the receiver to choose one of the following commands from the context menu:
- Coordinates: Select Coordinates to change the receiver position by entering new XY coordinates.
- Target Site: Select a site from the list to place the receiver directly on a site.
4. Click the Profile tab.
The profile analysis appears in the Profile tab of the Point Analysis Tool window. The altitude is reported on the
vertical axis and the receiver-transmitter distance on the horizontal axis. A blue ellipsoid indicates the Fresnel zone
between the transmitter and the receiver, with a green line indicating the line of sight (LOS). Atoll displays the
angle of the LOS read from the vertical antenna pattern. Along the profile, if the signal meets an obstacle, this
causes attenuation with diffraction displayed by a red vertical line (if the propagation model used takes diffraction
mechanisms into account). The main peak is the one that intersects the most with the Fresnel ellipsoid. With some
propagation models using a 3 knife-edge Deygout diffraction method, the results may display two additional atten-
uations peaks. The total attenuation is displayed above the main peak.
The results of the analysis are displayed at the top of the Profile tab:
- The received signal strength from the selected transmitter for the cell with the highest power
- The propagation model used
- The shadowing margin and the cell edge coverage probability used for calculating it
- The distance between the transmitter and the receiver.
You can change the following options at the top of the Profile tab:
- Transmitter: Select the transmitter from the list.
- Display Geo Data Only: Select the Display Geo Data Only check box if you want to view the geographic
profile between the transmitter and the receiver. Atoll displays the profile between the transmitter and the
receiver with clutter heights. An ellipsoid indicating the Fresnel zone is also displayed. Atoll does not calculate
nor display signal levels and losses.
5. Right-click the Profile tab to choose one of the following commands from the context menu:
- Properties: Select Properties to display the Analysis Properties dialogue. This dialogue is available from
the context menu on all tabs of the Point Analysis Tool window. You can:
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and,
select "From Model" from the Shadowing Margin list.
- Select Signal Level, Path loss, or Total losses from the Result Type list.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- Link Budget: Select Link Budget to display a dialogue with the link budget.
- Model Details: Select Model Details to display a text document with details on the displayed profile analysis.
Model details are only available for the Standard Propagation Model.
6. To end the point analysis, click the Point Analysis Tool ( ) in the Radio toolbar again.
Note: You can use the same procedure to study the signal level coverage of several base
stations by grouping the transmitters. For information on grouping transmitters, see
"Grouping Data Objects by a Selected Property" on page 65.
Tip: If you wish to study only sites by their status, at this step you could group them by status.
5. Select Coverage by Signal Level and click OK. A study properties dialogue appears.
6. You can configure the following parameters in the Properties dialogue:
- General tab: You can change the assigned Name of the coverage prediction, the Resolution, and the storage
Folder for the coverage prediction, and add some Comments. The resolution you set is the display resolution,
not the calculation resolution.
To improve memory consumption and optimise the calculation times, you should set the display resolutions of
coverage predictions according to the precision required. The following table lists the levels of precision that
are usually sufficient:
City Centre 5m
City 20 m
County 50 m
State 100 m
Note: If you create a new coverage prediction from the context menu of either the Transmitters
or Predictions folder, you can select the sites using the Group By, Sort, and Filter
buttons under Configuration. Because you already selected the target sites, however,
only the Filter button is available.
- Condition tab: The coverage prediction parameters on the Condition tab allow you to define the signals that
will be considered for each pixel (see Figure 14.11).
- At the top of the Condition tab, you can set the signal level range to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the
same results because Atoll displays the results of the best server in either case. Selecting "Best Signal
Level" necessitates, however, a longer time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that
Atoll will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage
Probability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
- Display tab: You can modify how the results of the coverage prediction will be displayed.
- Under Display Type, select "Value Intervals."
- Under Field, select "Best Signal Level."
- You can change the value intervals and their displayed colour. For information on changing display prop-
erties, see "Display Properties of Objects" on page 33.
- You can create a tooltip with information about the coverage prediction by clicking the Browse button
( ) beside the Tip Text box and selecting the fields you want to display in the tooltip.
- You can select the Add to Legend check box to add the displayed value intervals to the legend.
Note: If you change the display properties of a coverage prediction after you have calculated it,
you may make the coverage prediction invalid. You will then have to recalculate the
coverage prediction to obtain valid results.
7. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window. The signal level
coverage prediction can be found in the Predictions folder on the Data tab. Atoll automatically locks the results of a cover-
age prediction as soon as it is calculated, as indicated by the icon ( ) beside the coverage prediction in the Predictions
folder. When you click the Calculate button ( ), Atoll only calculates unlocked coverage predictions ( ).
Before calculating a coverage prediction, Atoll must have valid path loss matrices. Atoll calculates the path loss matrices
using the assigned propagation model. Atoll can use two different propagation models for each transmitter: a main prop-
agation model with a shorter radius (displayed with a blue square in Figure 14.12) and a higher resolution and an extended
propagation model with a longer radius and a lower resolution. Atoll will use the main propagation model to calculate
higher resolution path loss matrices close to the transmitter and the extended propagation model to calculate lower reso-
lution path loss matrices outside the area covered by the main propagation model.
In this section, the following are explained:
• "Path Loss Matrices" on page 1020.
• "Assigning a Propagation Model" on page 1021.
• "The Calculation Process" on page 1023.
• "Creating a Computation Zone" on page 1023.
• "Setting Transmitters or Cells as Active" on page 1024.
• "Signal Level Coverage Predictions" on page 1024.
• "Analysing a Coverage Prediction" on page 1028.
• "LTE Coverage Predictions" on page 1036.
• "Printing and Exporting Coverage Prediction Results" on page 1051.
Path loss matrices can be stored internally, in the Atoll document, or they can be stored externally. Storing path loss matri-
ces in the Atoll document results in a more portable but significantly larger document. In the case of large radio-planning
projects, embedding the matrices can lead to large documents which use a great deal of memory. Therefore, in the case
of large radio-planning projects, saving your path loss matrices externally will help reduce the size of the file and the use
of computer resources.
The path loss matrices are also stored externally in a multi-user environment, when several users are working on the same
radio-planning project. In this case, the radio data is stored in a database and the path loss matrices are read-only and are
stored in a location accessible to all users. When the user changes his radio data and recalculates the path loss matrices,
the calculated changes to the path loss matrices are stored locally; the common path loss matrices are not modified. These
will be recalculated by the administrator taking into consideration the changes to radio data made by all users. For more
information on working in a multi-user environment, see the Administrator Manual.
When you save the path loss matrices to an external directory, Atoll creates:
• One file per transmitter with the extension LOS for its main path loss matrix.
• A DBF file with validity information for all the main matrices.
• A folder called "LowRes" with LOS files and a DBF file for the extended path loss matrices.
To set the storage location of the path loss matrices:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the Predictions tab, under Path Loss Matrix Storage, you can set the location for your private path loss
matrices and the location for the shared path loss matrices:
- Private Directory: The Private Directory is where you store path loss matrices you generate or, if you are
loading path loss matrices from a shared location, where you store your changes to shared path loss matrices.
Click the button beside the Private Directory ( ) and select Embedded to save the path loss matrices in
the Atoll document, or Browse to select a directory where Atoll can save the path loss matrices externally.
Note: Path loss matrices you calculate locally are not stored in the same directory as shared
path loss matrices. Shared path loss matrices are stored in a read-only directory. In other
words, you can read the information from the shared path loss matrices but any changes
you make will be stored locally, either embedded in the ATL file or in a private external
folder, depending on what you have selected in Private Directory.
Caution: When you save the path loss files externally, the external files are updated as soon as
calculations are performed. In order to keep consistency between the Atoll document and
the stored calculations, you should save the Atoll document before closing it if you have
updated the path loss matrices.
- Shared Directory: When you are working in a multi-user Atoll environment, the project data is stored in a
database and the path loss matrices are stored in a directory that is accessible to all users. Any changes you
make will not be saved to this directory; they will be saved in the location indicated in Private Directory. The
path loss matrices in the shared directory are updated by a user with administrator rights based on the updated
information in the database. For more information on shared directories, see the Administrator Manual.
5. Click OK.
Atoll automatically checks the validity of the path loss matrices before calculating any coverage prediction. If you want,
you can check whether the path loss matrices are valid without creating a coverage prediction.
To check whether the path loss matrices are valid:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Propagation tab. The path loss matrix information is listed in the Available Results table. You have the
following display options:
- Display all the matrices: All path loss matrices are displayed.
- Display only invalid matrices: Only invalid path loss matrices are displayed.
The Available Results table lists the following information for each displayed path loss matrix:
Important: When you assign a propagation model globally, you override any selection you might
have made to an individual transmitter or to a group of transmitters.
3. If you have assigned a default propagation model for coverage predictions, as described in "Defining a Default
Propagation Model" on page 187, this is the propagation model that will be used for all transmitters whose main
propagation model is "(Default model)." If a transmitter has any other propagation model chosen as the main prop-
agation model, that is the propagation model that will be used.
In this section, the following are explained:
• "Assigning a Propagation Model to All Transmitters" on page 1021.
• "Assigning a Propagation Model to a Group of Transmitters" on page 1022.
• "Assigning a Propagation Model to One Transmitter" on page 1022.
For more information about the available propagation models, see Chapter 5: Managing Calculations in Atoll.
Transmitters that share the same parameters and environment will usually use the same propagation model and settings.
In Atoll, you can assign the same propagation model to several transmitters by first grouping them by their common
parameters and then assigning the propagation model.
To define a main and extended propagation model for a defined group of transmitters:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select from the Group by submenu of the context menu the property by which you want to group the transmitters.
The objects in the folder are grouped by that property.
Note: You can group transmitters by several properties by using the Group By button on the
Properties dialogue. For more information, see "Advanced Grouping" on page 66.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
If you have added a single transmitter, you can assign it a propagation model. You can also assign a propagation model
to a single transmitter after you have assigned a main and extended propagation model globally or to a group of transmit-
ters.
When you assign a main and extended propagation model to a single transmitter, it overrides any changes you have previ-
ously made globally.
To define a main and extended propagation model for all transmitters:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Transmitters folder.
3. Right-click the transmitter to which you want to assign a main and extended propagation model. The context menu
appears.
4. Select Properties from the context menu. The Properties dialogue appears.
5. Click the Propagation tab.
Note: You can also define the propagation models for a transmitter by right-clicking it in the map
window and selecting Properties from the context menu.
Notes:
• You can stop any calculations in progress by clicking the Stop Calculations button ( ) in
the toolbar.
• When you click the Force Calculation button ( ) instead of the Calculate button, Atoll cal-
culates all path loss matrices, unlocked coverages, and pending simulations.
You can also create a computation zone with one of the following methods:
• Existing polygon: You can use any existing polygon on the map as a computation zone by right-clicking it and
selecting Use as Computation Zone from the context menu.
• Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a computation zone. You can import it by right-clicking the Computa-
tion Zone folder on the Geo tab and selecting Import from the context menu.
• Fit to Map Window: You can create a computation zone the size of the map window by right-clicking the Com-
putation Zone folder on the Geo tab and selecting Fit to Map Window from the context menu.
Note: You can save the computation zone in the user configuration. For information on
exporting the computation zone in the user configuration, see "Exporting a User
Configuration" on page 75.
Note: If you do not yet have a zone containing the transmitters you want to set as active, you
can draw a zone as explained in "Using Zones in the Map Window" on page 41.
4. Select Activate Transmitters from the context menu. The selected transmitters are set as active.
Once you have ensured that all transmitters are active, you can set the propagation model parameters. For information on
choosing and configuring a propagation model, see Chapter 5: Managing Calculations in Atoll.
Calculating path loss matrices can be time and resource intensive when you are working on larger projects. Consequently,
Atoll offers you the possibility of distributing path loss calculations on several computers. You can install the distributed
calculation server application on other workstations or on servers. Once the distributed calculation server application is
installed on a workstation or server, the computer is available for distributed path loss calculation to other computers on
the network. For information on setting up the distributed calculation server application, see The Administrator Manual.
you clone a coverage prediction, by selecting Clone from the context menu, you can create a copy of the prediction with
the calculated coverage. You can then change the display, providing that the selected parameter does not invalidate the
calculated coverage prediction.
You can also save the list of all defined coverage predictions in a user configuration, allowing you or other users to import
it into a new Atoll document. When you save the list in a user configuration, the parameters of all existing coverage predic-
tions are saved; not just the parameters of calculated or displayed ones. For information on exporting user configurations,
see "Exporting a User Configuration" on page 75.
The following standard coverage predictions are explained in this section:
• "Making a Coverage Prediction by Signal Level" on page 1025
• "Making a Coverage Prediction by Transmitter" on page 1026
• "Making a Coverage Prediction on Overlapping Zones" on page 1027.
6. Click the Condition tab (see Figure 14.14). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same
results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level"
necessitates, however, the longest time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll
will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the signal level coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 14.15).
6. Click the Condition tab (see Figure 14.16). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same
results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level"
necessitates, however, the longest time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll
will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the transmitter coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 14.17).
6. Click the Condition tab (see Figure 14.18). On the Condition tab, you can define the signals that will be considered
for each pixel.
- At the top of the Condition tab, you can set the range of signal level to be considered.
- Under Server, select "All" to consider all servers. Selecting "All" or "Best Signal Level" will give you the same
results because Atoll displays the results of the best server in either case. Selecting "Best Signal Level"
necessitates, however, the longest time for calculation.
When you select "Best Signal Level" or "Second Best Signal Level," you can also define a Margin that Atoll
will take into consideration.
- If you select the Shadowing Taken into Account check box, you can change the Cell Edge Coverage Prob-
ability.
- You can select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter
class.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see
Figure 14.19).
1. Click the Point Analysis Tool ( ) in the Radio toolbar. The Point Analysis Tool window appears and the
pointer changes ( ) to represent the receiver.
2. At the bottom of the Point Analysis Tool window, click the Reception tab (see Figure 14.21).
The predicted signal level from different transmitters is reported in the Reception tab in the form of a bar chart,
from the highest predicted signal level on the top to the lowest one on the bottom. Each bar is displayed in the
colour of the transmitter it represents. For a transmitter with more than one cell, the signal level is calculated for
the cell with the highest power.
In the Map window, arrows from the pointer to each transmitter are displayed in the colour of the transmitters they
represent. A thick black line from the pointer to its best server is also displayed in the map window. The best server
of the pointer is the transmitter from which the pointer receives the highest signal level. If you let the pointer rest,
the signal level received from the corresponding transmitter at the pointer location is displayed in the tool-tip.
3. Right-click the Reception tab and select Properties from the context menu. The Analysis Properties dialogue
appears.
- Change the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and
select "From Model" from the Shadowing Margin list.
- Select the Indoor Coverage check box to add indoor losses. Indoor losses are defined per clutter class.
4. To end the point analysis, click the Point Analysis Tool ( ) in the Radio toolbar again.
14.2.8.7.4 Creating a Focus or Hot Spot Zone for a Coverage Prediction Report
The focus and hot spot zones define the area on which statistics can be drawn and on which reports are made. While you
can only have one focus zone, you can define several hot spot zones in addition to the focus zone.
It is important not to confuse the computation zone and the focus and hot spot zones. The computation zone defines the
area where Atoll calculates path loss matrices, coverage predictions, Monte Carlo simulations, etc., while the focus and
hot spot zones are the areas taken into consideration when generating reports and results. When you create a coverage
prediction report, it gives the results for the focus zone and for each of the defined hot spot zones.
To define a focus zone or hot spot zone:
1. Click the Geo tab in the Explorer window.
2. Click the Expand button ( ) to expand the Zones folder.
3. Right-click the Focus Zone or Hot Spot Zones folder, depending on whether you want to create a focus zone or
a hot spot. The context menu appears.
4. Select Draw from the context menu.
5. Draw the focus or hot spot zone:
a. Click once on the map to start drawing the zone.
b. Click once on the map to define each point on the map where the border of the zone changes direction.
c. Click twice to finish drawing and close the zone.
A focus zone is delimited by a green line; a hot spot zone is delimited by a heavy black line. If you clear the zone’s
visibility check box in the Zones folder of the Geo tab in the Explorer window, it will no longer be displayed but
will still be taken into account.
You can also create a focus or hot spot zone as follows:
• Existing polygon: You can use any existing polygon on the map as a focus zone by right-clicking it and selecting
Use as Focus Zone from the context menu.
Note: You can only create a focus zone, and not a hot spot zone, from an existing polygon.
• Importing a polygon: If you have a file with an existing polygon, for example, a polygon describing an adminis-
trative area, you can import it and use it as a focus or hot spot zone. You can import it by right-clicking the Focus
Zone or Hot Spot Zones folder on the Geo tab and selecting Import from the context menu. When you import hot
spot zones, you can import the name given to each zone as well.
• Fit to Map Window: You can create a focus or hot spot zone the size of the map window by selecting Fit to Map
Window from the context menu.
Notes: You can save the focus or hot spot zones so that you can use them in a different Atoll
document:
- You can save the focus zone in the user configuration. For information on exporting the
focus zone in the user configuration, see "Exporting a User Configuration" on page 75.
- You can right-click the Focus Zone folder or the Hot Spot Zones folder on the Data
tab of the Explorer window and select Export from the context menu.
You can include population statistics in the focus or hot spot zone by importing a population
map. For information on importing maps, see "Importing a Raster-format Geo Data File" on
page 107.
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
a. Under Configuration, click the Import button. The Open dialogue appears.
b. Select the configuration you want to import and click Open. The imported report configuration is applied.
6. When you have finished defining the format and content of the report, click OK in the Columns to Be Displayed
dialogue. The coverage prediction report table appears. The report is based on the hot spot zones and on the
focus zone if available or on the hot spot zones and computation zone if there is no focus zone.
To display a report on all coverage predictions:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select Generate Report from the context menu. The Columns to Be Displayed dialogue appears.
4. Define the format and content of the report:
You can select the columns that will be displayed in the report and define the order they are in:
a. Select the check box for each column you want to have displayed.
b. Define the order of the columns by selecting each column you want to move and clicking to move it up or
to move it down.
You can save the current report format in a configuration:
a. Under Configuration, click the Export button. The Save As dialogue appears.
b. In the Save As dialogue, browse to the folder where you want to save the configuration and enter a File name.
You can apply a configuration that you have saved previously:
Atoll saves the names of the columns you select and will automatically select them the next time you create a
coverage prediction report.
5. Click OK.
If you have created a custom data map with integrable data, the data can be used in prediction reports. The data will be
summed over the coverage area for each item in the report (for example, by transmitter or threshold). The data can be
value data (revenue, number of customers, etc.) or density data (revenue/km², number of customers/km², etc.). Data is
considered as non-integrable if the data given is per pixel or polygon and cannot be summed over areas, for example,
socio-demographic classes, rain zones, etc. For information on integrable data in custom data maps, see "Integrable
Versus Non Integrable Data" on page 124.
In this section, there are two examples to explain how you can compare two similar predictions. You can display the results
of the comparison study coverage in one of the following ways:
• Intersection: This display shows the area where both coverage predictions overlap (for example, pixels covered
by both coverage predictions are displayed in red).
• Union: This display shows all pixels covered by both coverage predictions in one colour and pixels covered by
only one coverage prediction in a different colour (for example, pixels covered by both predictions are red and
pixels covered by only one prediction are blue).
• Difference: This display shows all pixels covered by both coverage predictions in one colour, pixels covered by
only the first prediction with another colour and pixels covered only by the second prediction with a third colour (for
example, pixels covered by both predictions are red, pixels covered only by the first prediction only are green, and
pixels covered only by the second prediction are blue).
To compare two similar coverage predictions:
1. Create and calculate a coverage prediction of the existing network.
2. Examine the coverage prediction to see where coverage can be improved.
3. Make the changes to the network to improve coverage.
4. Duplicate the original coverage prediction (in order to leave the first coverage prediction unchanged).
5. Calculate the duplicate coverage prediction.
6. Compare the original coverage prediction with the new coverage prediction. Atoll displays differences in coverage
between them.
In this section, the following examples are explained:
• "Example 1: Studying the Effect of a New Base Station" on page 1033
• "Example 2: Studying the Effect of a Change in Transmitter Tilt" on page 1035.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how you can verify if a newly added base station improves coverage.
A signal level coverage prediction of the current network is made as described in "Making a Coverage Prediction by Signal
Level" on page 1025. The results are displayed in Figure 14.23. An area with poor coverage is visible on the right side of
the figure.
A new base station is added, either by creating the base station and adding the transmitters, as explained in "Creating an
LTE Base Station" on page 1003, or by placing a station template, as explained in "Placing a New Base Station Using a
Station Template" on page 1009. Once the new site has been added, the original coverage prediction can be recalculated,
but then it would be impossible to compare the results. Instead, the original signal level coverage prediction can be copied
by selecting Duplicate from its context menu. The copy is then calculated to show the effect of the new base station (see
Figure 14.24).
Figure 14.24: Signal level coverage prediction of network with new base station
4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes adding a new base station made, you should choose Difference.
5. Click OK to create the comparison. The comparison in Figure 14.25, shows clearly the area covered only by the
new base station.
If you have an area in a network that is poorly covered by current transmitters, you have several options for increasing
coverage. In this example, we will look at how modifying transmitter tilt can improve coverage.
A coverage prediction by transmitter of the current network is made as described in "Making a Coverage Prediction by
Transmitter" on page 1026. The results are displayed in Figure 14.26. The coverage prediction shows that one transmitter
is covering its area poorly. The area is indicated with a red oval in the figure.
You can try modifying the tilt on the transmitter to improve the coverage. The properties of the transmitter can be accessed
by right-clicking the transmitter in the map window and selecting Properties from the context menu. The mechanical and
electrical tilt of the antenna are defined on the Transmitter tab of the Properties dialogue.
Once the tilt of the antenna has been modified, the original coverage prediction can be recalculated, but then it would be
impossible to compare the results. Instead, the original coverage prediction can be copied by selecting Duplicate from its
context menu. The copy is then calculated, to show how modifying the antenna tilt has affected coverage (see
Figure 14.27).
As you can see, modifying the antenna tilt increased the coverage of the transmitter. However, to see exactly the change
in coverage, you can compare the two predictions.
To compare two predictions:
1. Right-click one of the two predictions. The context menu appears.
2. From the context menu, select Compare with and, from the menu that opens, select the prediction you want to
compare with the first. The Comparison Properties dialogue appears.
3. Click the General tab. You can change the Name of the comparison and add Comments.
The General tab contains information about the coverage predictions being compared, including their names and
resolutions.
4. Click the Display tab. On the display tab, you can choose how you want the results of the comparison to be dis-
played. You can choose among:
- Intersection
- Union
- Difference
In order to see what changes modifying the antenna tilt made, you can choose Union. This will display all pixels
covered by both predictions in one colour and all pixels covered by only one prediction in another colour. The
increase in coverage, seen in only the second coverage prediction, will be immediately clear.
5. Click OK to create the comparison. The comparison in Figure 14.28, shows clearly the increase in coverage due
at the change in antenna tilt.
Using signal quality coverage predictions you can study the effective service coverage area and capacity of each cell in
the network. These coverage predictions depend on the interference in the network and the cell load conditions. For this
reason, the network load must be defined in order to calculate these coverage predictions.
For the purposes of these coverage predictions, each pixel is considered a non-interfering user with a defined service,
mobility type, and terminal. The following are explained in the following sections:
• "Service and User Modelling" on page 1037.
This section explains the coverage predictions available for analysing the effective signal level and signal quality. The
following are explained:
• "Analysing the Effective Signal Levels" on page 1039.
• "Analysing the Signal Quality" on page 1041.
You can also make a point analysis using the Point Analysis window to study the effective signal level at a point. Load
conditions can be selected for the analysis as well as the characteristics of the user-definable probe receiver, i.e., a termi-
nal, a mobility, and a service:
• "Making an Effective Signal Analysis" on page 1050.
Interferences coming from an external project can also be modelled and is explained in "Modelling Inter-Network Interfer-
ences" on page 236.
Modelling Services
Services are the various services available to users. These services can be either voice or data type services. This section
explains how to create a service. The following parameters are used in predictions:
• Throughput scaling factor
• Throughput offset
• Body loss
To create or modify a service:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the LTE Parameters folder.
3. Right-click the Services folder. The context menu appears.
4. Select New from the context menu. The Services New Element Properties dialogue appears.
Note: You can modify the properties of an existing service by right-clicking the service in the
Services folder and selecting Properties from the context menu.
5. You can edit the fields on the General tab to define the new service. Some fields depend on the type of service
you choose. You can change the following parameters.
- Name: Atoll proposes a name for the new service, but you can set a more descriptive name.
- Type: You can select either Voice or Data as the service type.
- Priority: Enter a priority for this service. "0" is the lowest priority.
- Activity Factor: The uplink and downlink activity factors are used to determine the probability of activity for
users accessing a voice type service during Monte Carlo simulations.
- Highest Bearer: Select the highest bearer that the service can use in the uplink and downlink. This is consid-
ered as an upper limit during bearer determination.
- Max Throughput Demand: Enter the highest throughput that the service can demand in the uplink and down-
link.
- Min. Throughput Demand: Enter the minimum required throughput that the service should have in order to
be available in the uplink and downlink.
- Average Requested Throughput: Enter the average requested throughput for uplink and downlink. The
average requested throughput is used in a simulation during user distribution generation in order to calculate
the number of users attempting a connection.
- Application Throughput: Under Application Throughput, you can set a Scaling Factor between the appli-
cation throughput and the RLC (Radio Link Control) throughput and a throughput Offset. These parameters
model the header information and other supplementary data that does not appear at the application level.
The application throughput parameters are used in throughput coverage predictions and for application
throughput calculation.
- Body Loss: Enter a body loss for the service. The body loss is the loss due to the body of the user. For
example, in a voice connection the body loss, due to the proximity of the user’s head, is estimated to be 3 dB.
6. Click OK.
In LTE, information about the receiver mobility is required for determining which bearer selection threshold and quality
graph to use from the LTE equipment referred to in the terminal or cell. Mobiles used at high speeds and at walking speeds
do not have the same quality characteristics. C/(I+N) requirements for different radio bearers are largely dependent on
mobile speed.
To create or modify a mobility type:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the LTE Parameters folder.
3. Right-click the Mobility Types folder. The context menu appears.
4. Select New from the context menu. The Mobility Types New Element Properties dialogue appears.
Note: You can modify the properties of an existing mobility type by right-clicking the mobility
type in the Mobility Types folder and selecting Properties from the context menu.
5. You can enter or modify the following parameters in the Mobility Types New Element Properties dialogue:
- Name: Enter a descriptive name for the mobility type.
- Average Speed: Enter an average speed for the mobility type. This field is for information only; the average
speed is not used by any calculation.
6. Click OK.
Note: Subscriber lists use the mobility type "Fixed", i.e., 0 km/hr, in calculations. Do not delete
this mobility type from the document if you are working with subscriber lists.
Modelling Terminals
In LTE, a terminal is the user equipment that is used in the network, for example, a mobile phone, a PDA, or a car’s on-
board navigation device.
The following parameters are used in predictions:
• Antenna
• LTE equipment
• Maximum and minimum terminal power
• Gain and losses
• Noise figure
• Supported antenna diversity technique
• Number of transmission and reception antenna ports for MIMO
To create or modify a terminal:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the LTE Parameters folder.
3. Right-click the Terminals folder. The context menu appears.
4. Select New from the context menu. The Terminals New Element Properties dialogue appears.
Note: You can modify the properties of an existing terminal by right-clicking the terminal in the
Terminals folder and selecting Properties from the context menu.
5. You can enter or modify the following parameters in the Terminals New Element Properties dialogue:
- Name: Enter a descriptive name for the terminal.
- Under Transmission/Reception,
- Min Power: Enter the minimum transmission power of the terminal.
- Max Power: Enter the maximum transmission power of the terminal.
- Noise Figure: Enter the noise figure of the terminal (used to calculate the downlink total noise).
- Losses: Enter the losses of the terminal.
- LTE Equipment: Select an LTE equipment from the list of available equipment. For more information on
LTE equipment, see "Defining LTE Equipment" on page 1104. The terminal’s LTE equipment parameters
are used in the downlink calculations.
- Under Antenna,
- Model: Select an antenna model from the list of available antennas. If you do not select an antenna for
the terminal, Atoll uses an isotropic antenna in calculations.
Note: In case you do not select an antenna, Atoll uses an isotropic antenna, not an omni-
directional antenna, in calculations. An isotropic antenna has spherical radiation patterns
in the horizontal as well as vertical planes.
- Gain: Enter the terminal antenna gain if you have not selected an antenna model in the Model field. If you
have selected an antenna, the Gain field is disabled and shows the gain of the selected antenna.
- Diversity Support: Select whether the terminal type supports MIMO or not. Antenna diversity gains will
be applied to MIMO users.
- Under Number of Antenna Ports, enter the number of antenna ports available in the terminal for Trans-
mission and Reception.
6. Click OK.
For more information on services, terminals, mobility types, and LTE equipment, see "Modelling Services" on
page 1037, "Modelling Terminals" on page 1038, "Modelling Mobility Types" on page 1038, and "Defining LTE
Equipment" on page 1104, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
the effective signal analysis calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
Figure 14.29: Condition settings for an effective signal analysis coverage prediction
The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see
"Display Properties of Objects" on page 33.
10. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 14.30
and Figure 14.31).
If you are setting the traffic loads and the uplink noise rise for a single transmitter, you can set these parameters on the
Cells tab of the transmitter’s Properties dialogue. However, you can set the traffic loads and the uplink noise rise for all
the cells using the Cells table.
To set the traffic loads and the uplink noise rise using the Cells table:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Open Table from the context menu. The Cells table appears.
4. Enter a value in the following columns:
- Traffic Load (DL) (%)
- UL Noise Rise (dB)
Although, you can also set a value for the Traffic Load (UL) (%) column as an indication of cells’ uplink loads,
this parameter is not used in the coverage prediction calculations. The measure of interference in the uplink
is given by the UL Noise Rise (dB). For a definition of the values, see "Cell Description" on page 1006.
5. To enter the same values in one column for all cells in the table:
a. Enter the value in the first row in the column.
b. Select the entire column.
c. Select Edit > Fill > Down to copy the contents of the top cell of the selection into the other cells.
Note: If you want to copy the contents of the last cell in the selection into all other cells, you can
select Edit > Fill > Up. For more information on working with tables in Atoll, see "Working
with Data Tables" on page 50.
Downlink and uplink coverage predictions by C/(I+N) level predict the interference levels and signal-to-interference levels
in the part of the network being studied.
Atoll calculates the serving transmitter for each pixel depending on the downlink reference signal level. The serving trans-
mitter is determined according to the received reference signal level from the cell with the highest power. If more than one
cell cover the pixel, the one with the lowest order is selected as the serving (reference) cell. Then, depending on the predic-
tion definition, it calculates the interference from other cells, and finally calculates the C/(I+N). The pixel is coloured if the
display threshold condition is fulfilled (in other words, if the C/(I+N) is higher than C/(I+N) threshold).
Coverage prediction by C/(I+N) level calculates the co-channel interference as well as the adjacent channel interference,
which is reduced by the adjacent channel suppression factor defined in the Frequency Bands table. For more information
on frequency bands, see "Defining Frequency Bands" on page 1101.
The reference signal C/(I+N) is calculated using the reference signal power. Interference on the reference signals is in part
caused by the reference signals from interfering cells and in part by the PDSCH/PDCCH transmission. The SCH/PBCH
C/(I+N) is calculated using the SCH/PBCH power. Interference on the SCH and PBCH is caused by the SCH and PBCH
transmission from interferering cells, respectively. The PDSCH/PDCCH C/(I+N) is calculated using the PDSCH/PDCCH
power. Interference on the PDSCH/PDCCH is caused by PDSCH/PDCCH transmission from interfereing cells. PDSCH/
PDCCH interference depends on the downlink traffic loads of interfering cells. The PUSCH/PUCCH C/(I+N) is calculated
using the terminal power calculated after power control and the uplink noise rise stored either in the cell properties or in
the selected simulation results.
To make a coverage prediction by C/(I+N) level:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by C/(I+N) Level (DL) or Coverage by C/(I+N) Level (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
6. Click the Condition tab (see Figure 14.32).
Select "(Cells Table)" from Load Conditions. In this case, the coverage prediction is not going to be based on
load conditions taken from a simulation. Atoll will calculate the coverage prediction using the cell loads stored in
the cell properties.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The C/(I+N) coverage prediction is a best server
coverage prediction. The Noise Figure defined in the terminal type’s properties dialogue is used in the coverage
prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to determine
the total noise in the uplink.
For more information on services, terminals, mobility types, and LTE equipment, see "Modelling Services" on
page 1037, "Modelling Terminals" on page 1038, "Modelling Mobility Types" on page 1038, and "Defining LTE
Equipment" on page 1104, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C⁄(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see
"Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 14.33
and Figure 14.34).
Downlink and uplink best radio bearer coverage predictions calculate and display the best LTE radio bearers based on
C⁄(I+N) for each pixel.
To make a coverage prediction by best bearer:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Best Bearer (DL) or Coverage by Best Bearer (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The best bearer coverage prediction is always based
on the best server. The Noise Figure defined in the terminal type’s properties dialogue is used in the coverage
prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to determine
the total noise in the uplink. As well, the bearer selection for each pixel according to the PDSCH/PDCCH C⁄(I+N)
level is performed using the bearer selection thresholds defined in the LTE equipment. This LTE equipment is the
one defined in the selected terminal for the downlink coverage predictions, and the one defined in the cell proper-
ties of the serving transmitter for the uplink coverage predictions. Mobility is used to index the bearer selection
threshold graph to use.
For more information on services, terminals, mobility types, and LTE equipment, see "Modelling Services" on
page 1037, "Modelling Terminals" on page 1038, "Modelling Mobility Types" on page 1038, and "Defining LTE
Equipment" on page 1104, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C⁄(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the LTE bearer coverage prediction. The
progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 14.36
and Figure 14.37).
Downlink and uplink throughput coverage predictions calculate and display the channel throughputs and cell capacities
based on C⁄(I+N) and bearer calculations for each pixel. These coverage predictions can also display aggregate cell
throughputs if Monte Carlo simulation results are available. For more information on making aggregate cell throughput
coverage predictions using simulation results, see "Making an Aggregate Throughput Coverage Prediction Using Simula-
tion Results" on page 1047.
To make a coverage prediction by throughput:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Throughput (DL) or Coverage by Throughput (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The throughput coverage prediction is always based
on the best server. The Noise Figure defined in the terminal type’s Properties dialogue is used in the coverage
prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to determine
the total noise in the uplink. As well, the bearer selection for each pixel according to the PDSCH/PDCCH C⁄(I+N)
level is performed using the bearer selection thresholds defined in the LTE equipment. This LTE equipment is the
one defined in the selected terminal for the downlink coverage predictions, and the one defined in the cell proper-
ties of the serving transmitter for the uplink coverage predictions. The mobility is used to indicate the bearer selec-
tion threshold graph to use. The service is used for the application throughput parameters defined in the service
Properties dialogue.
For more information on services, terminals, mobility types, and LTE equipment, see "Modelling Services" on
page 1037, "Modelling Terminals" on page 1038, "Modelling Mobility Types" on page 1038, and "Defining LTE
Equipment" on page 1104, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C⁄(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
7. Click the Display tab. The settings you select on the Display tab determine the information that the coverage pre-
diction will display. You can set parameters to display the following results:
- Channel throughputs: Select Peak RLC Channel Throughput, Effective RLC Channel Throughput, or
Application Channel Throughput.
- Cell capacities: Select Peak RLC Cell Capacity, Effective RLC Cell Capacity, or Application Cell
Capacity.
- Allocated Bandwidth throughputs in uplink: Select Peak RLC Allocated Bandwidth Throughput, Effective
RLC Allocated Bandwidth Throughput, or Application Allocated Bandwidth Throughput.
The coverage prediction results will be in the form of thresholds. For information on adjusting the display, see
"Display Properties of Objects" on page 33.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the coverage prediction. The progress of the
calculation, as well as any error messages, is displayed in the Event Viewer.
Atoll determines the total number of symbols in the downlink and the uplink frames from the information in the global trans-
mitter parameters and the frequency bands assigned to cells. Then, Atoll determines the bearer at each pixel and multi-
plies the bearer efficiency by the number of symbols in the frame to determine the peak RLC channel throughputs.
The effective RLC throughputs are the peak RLC throughputs reduced by retransmission due to errors, or the Block Error
Rate (BLER). Atoll uses the block error rate graphs of the LTE equipment defined in the selected terminal or the LTE
equipment of the cell of the serving transmitter.
The application throughput is the effective RLC throughput reduced by the overheads of the different layers between the
RLC and the Application layers.
The cell capacity display types let you calculate and display the throughputs available at each pixel of the coverage area
taking into account the maximum traffic load limits set for each cell. In other words, the cell capacity is equal to channel
throughput when the maximum traffic load is set to 100 %, and is equal to a throughput limited by the maximum allowed
traffic loads otherwise. Cell capacities are, therefore, channel throughputs scaled down to respect the maximum traffic load
limits.
The allocated bandwidth throughputs are the throughputs corresponding to the number of frequency blocks allocated to
the terminal at different locations. Users located far from the base stations use less numbers of frequency blocks than
users located near so that they can concentrate their transmission power over a bandwidth narrower than the channel
bandwidth in order to maintain the connection in uplink.
For more information on throughput calculation, see the Technical Reference Guide. For more information on the Global
Parameters, see "The Global Transmitter Parameters" on page 1102.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window.
Atoll calculates the aggregate peak RLC, effective RLC, and application cell throughputs during Monte Carlo simulations.
The aggregate cell throughputs are the sums of the cell’s user throughputs. You can create a coverage prediction that
calculates and displays the surface area covered by each cell, and colours the coverage area of each cell according to its
aggregate throughput.
Downlink and uplink quality indicator coverage predictions calculate and display the values of different quality indicators
(BLER, BER, etc.) based on the best LTE radio bearers and on C⁄(I+N) for each pixel.
To make a coverage prediction by quality indicator:
1. Click the Data tab in the Explorer window.
2. Right-click the Predictions folder. The context menu appears.
3. Select New from the context menu. The Study Types dialogue appears.
4. Select Coverage by Quality Indicator (DL) or Coverage by Quality Indicator (UL) and click OK.
5. Click the General tab.
On the General tab, you can change the default Name, Resolution, and the storage Folder for the coverage
prediction, and add some Comments. For more information on the storage of coverage predictions, see "Defining
the Storage Location of Coverage Prediction Results" on page 200. Under Configuration, you can create a Filter
to select which sites to display in the results. For information on filtering, see "Filtering Data" on page 70.
Note: When you base a coverage prediction on simulations, you would select the simulations on
which you would be basing the coverage prediction from the Load Conditions list.
You must select a Terminal, a Mobility type, and a Service. The quality indicator coverage prediction is always
based on the best server. The Noise Figure defined in the terminal type’s properties dialogue is used in the cover-
age prediction to determine the total noise in the downlink, and the Noise Figure of the transmitter is used to deter-
mine the total noise in the uplink. As well, the bearer selection for each pixel according to the PDSCH/PDCCH
C⁄(I+N) level is performed using the bearer selection thresholds defined in the LTE equipment, and the quality indi-
cator graphs from the LTE equipment are used to determine the values of the selected quality indicator on each
pixel. This LTE equipment is the one defined in the selected terminal for the downlink coverage predictions, and
the one defined in the cell properties of the serving transmitter for the uplink coverage predictions. Mobility is used
to index the bearer selection threshold graph to use.
For more information on services, terminals, mobility types, and LTE equipment, see "Modelling Services" on
page 1037, "Modelling Terminals" on page 1038, "Modelling Mobility Types" on page 1038, and "Defining LTE
Equipment" on page 1104, respectively.
If you want the coverage prediction to consider shadowing, you can select the Shadowing taken into account
check box and enter a percentage in the Cell Edge Coverage Probability text box. The shadowing margin for
C⁄(I+N) calculations is based on the C/I standard deviation.
You can also have the coverage prediction take Indoor Coverage into consideration.
9. Click the Calculate button ( ) in the Radio toolbar to calculate the quality indicator coverage prediction.
The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
Once Atoll has finished calculating the coverage prediction, the results are displayed in the map window (see Figure 14.42
and Figure 14.43).
1. Click the Point Analysis button ( ) on the toolbar. The Point Analysis Tool window appears (see
Figure 14.45).
2. Click the Signal Analysis tab.
3. At the top of the Signal Analysis tab, select "Cells Table" from Load Conditions.
4. If you are making a signal analysis to verify a coverage prediction, you can recreate the conditions of the coverage
prediction:
a. Select the same Terminal, Service, and Mobility studied in the coverage prediction.
b. Right-click the Point Analysis window and select Properties from the context menu. The Properties dia-
logue appears.
- Edit the X and Y coordinates to change the present position of the receiver.
- Select the Shadowing taken into account check box and enter a Cell Edge Coverage Probability, and,
select "From Model" from the Shadowing Margin list.
c. Click OK to close the Properties dialogue.
5. Move the pointer over the map to make a signal analysis for the current location of the pointer.
As you move the pointer, Atoll indicates on the map which is the best server for the current position (see
Figure 14.44).
Information on the current position is given on the Signal Analysis tab of the Point Analysis window. See
Figure 14.45 for an explanation of the displayed information.
6. Click the map to leave the point analysis pointer at its current position.
To move the pointer again, click the point analysis pointer on the map and drag it to a new position.
7. Click the Point Analysis button ( ) on the toolbar again to end the point analysis.
The reference signal reception from the The connection status (SCH/PBCH,
best server (top-most bar) and all downlink and uplink) for the current point.
interfering cells. Solid bars indicate the
signal levels above the reference signal C/ : Service available
N thresholds.
: Service unavailable
7. Under Exceptional Pairs, create a new exceptional pair in the row marked with the New Row icon ( ):
a. Select the cell from the list in the Neighbours column.
b. In the Status column, select one of the following:
- Forced: The selected cell will always be a neighbour of the reference cell.
- Forbidden: The selected cell will never be a neighbour of the reference cell.
8. Click elsewhere in the table when you have finished creating the new exceptional pair.
9. Click OK.
Notes: You can also create exceptional pairs using the Exceptional Pairs of Intra-Technology
Neighbours table. You can open this table by right-clicking the Transmitters folder and
selecting Cells > Neighbours > Intra-Technology Exceptional Pairs.
- Shadowing taken into account: If desired, select the Shadowing taken into account check box and
enter a Cell Edge Coverage Probability.
- Indoor Coverage: Select the Indoor Coverage check box if you want to use indoor losses defined per
clutter class in the calculations.
- Resolution: You can enter the resolution used to calculate the coverage areas of cells for the automatic
neighbour allocation.
- % Min. Covered Area: Enter the minimum surface area, in percentage, that a possible neighbour cell’s cov-
erage area must overlap the reference cell’s coverage area.
6. Select the desired calculation parameters:
- Force co-site cells as neighbours: Select the Force co-site cells as neighbours check box if you want
cells located on the same site as the reference cell to be automatically considered as neighbours.
- Force adjacent cells as neighbours: Select the Force adjacent cells as neighbours check box if you want
cells that are adjacent to the reference cell to be automatically considered as neighbours. A cell is considered
adjacent if there is at least one pixel in the reference cell’s coverage area where the possible neighbour cell
is the best server, or where the possible neighbour cell is the second best server (respecting the handover
margin).
- Force symmetry: Select the Force symmetry check box if you want neighbour relations to be reciprocal. In
other words, a reference cell will be a possible neighbour to all of the cells that are its neighbours. If the neigh-
bour list of any cell is full, the reference cell will not be added as a neighbour and that cell will be removed from
the list of neighbours of the reference cell.
- Force exceptional pairs: Select the Force exceptional pairs check box if you want to be able to force or
forbid neighbour relations defined in the Exceptional Pairs table. For information on exceptional pairs, see
"Defining Exceptional Pairs" on page 1052.
- Delete existing neighbours: Select the Delete existing neighbours check box if you want Atoll to delete
all current neighbours when allocating neighbours. If you do not select the Delete existing neighbours check
box, Atoll will not delete any existing neighbours when automatically allocating neighbours; it will only add new
neighbours to the list.
Figure 14.46: The handover area between the reference cell and the possible neighbour
7. Click the Importance Weighting button to set the relative importance of possible neighbours:
- Coverage Factor: Set the minimum and maximum importance of a neighbour being admitted for coverage
reasons.
- Adjacency Factor: If you have selected the Force adjacent cells as neighbours check box in step 6., set
the minimum and maximum importance of a possible neighbour cell being adjacent to the reference cell.
- Co-site Factor: If you have selected the Force co-site cells as neighbours check box in step 6., set the
minimum and maximum importance of a possible neighbour cell being located on the same site as reference
cell.
8. Click Calculate. Atoll begins the process of allocating neighbours. Atoll first checks to see whether the path loss
matrices are valid before allocating neighbours. If the path loss matrices are not valid, Atoll recalculates them.
Once Atoll has finished calculating neighbours, the new neighbours are visible under Results. Atoll only displays
new neighbours. If no new neighbours have been found and if the Deleting existing neighbours check box is
cleared, the Results table will be empty.
Notes:
• A forbidden neighbour will not be listed as a neighbour unless the neighbour relation already
exists and the Delete existing neighbours check box is cleared when you start the new allo-
cation. In this case, Atoll displays a warning in the Event Viewer indicating that the constraint
on the forbidden neighbour will be ignored by the algorithm because the neighbour already
exists.
• When the options Force exceptional pairs and Force symmetry are selected, Atoll con-
siders the constraints between exceptional pairs in both directions in order to respect sym-
metry. On the other hand, if the neighbour relation is forced in one direction and forbidden in
the other one, symmetry cannot be respected. In this case, Atoll displays a warning in the
Event Viewer.
• You can save automatic neighbour allocation parameters in a user configuration. For informa-
tion on saving automatic neighbour allocation parameters in a user configuration, see
"Exporting a User Configuration" on page 75.
1. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
2. Select Display Options from the context menu. The Visual Management dialogue appears.
3. Under Intra-technology Neighbours, select the Display Links check box.
4. Click the Browse button ( ) beside the Display Links check box.
5. The Intra-technology Neighbour Display dialogue appears.
6. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour all neighbour links of a cell with a
unique colour.
- Discrete Values: Select "Discrete Values" as the Display Type, and then a value from the Field list, if you
want Atoll to colour the cell’s neighbour links according to a value from the Intra-technology Neighbours
table, or according to the neighbour frequency band.
- Value Intervals: Select "Value Intervals" to colour the cell’s neighbour links according the value interval of the
value selected from the Field list. For example, you can choose to display a cell’s neighbours according to the
importance, as determined by the weighting factors.
Tip: You can display the number of handoff attempts for each cell-neighbour pair by first
creating a new field of Type "Integer" in the Intra-Technology Neighbour table for the
number of handoff attempts. Once you have imported or entered the values in the new
column, you can select this field from the Field list along with "Value Intervals" as the
Display Type. For information on adding a new field to a table, see "Adding a Field to an
Object Type’s Data Table" on page 51.
Each neighbour link display type has a visibility check box. By selecting or clearing the visibility check box, you
can display or hide neighbour link display types individually.
For information on changing display properties, see "Display Properties of Objects" on page 33.
7. Select the Add to Legend check box to add the displayed neighbour links to the legend.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each neighbour link.
9. Click OK to save your settings.
10. Under Advanced, select which neighbour links to display:
- Outwards Non-Symmetric: Select the Outwards Non-Symmetric check box to display neighbour relations
where the selected cell is the reference cell and where the neighbour relation is not symmetric.
- Inwards Non-Symmetric: Select the Inwards Non-Symmetric check box to display neighbour relations
where the selected cell is neighbour and where the neighbour relation is not symmetric.
- Symmetric: Select the Symmetric check box to display neighbour relations that are symmetric between the
selected cell and the neighbour.
11. Click OK to save your settings.
12. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
13. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
- The symmetric neighbour relations of the selected (reference) cell are indicated by a line.
- The outward neighbour relations are indicated with a line with an arrow pointing at the neighbour (e.g. see
Site1_2(0)) in Figure 14.47.).
- The inward neighbour relations are indicated with a line with an arrow pointing at the selected cell (e.g. see
Site9_3(0)) in Figure 14.47.).
In Figure 14.47, neighbour links are displayed according to the neighbour. Therefore, the symmetric and outward
neighbour links are coloured as the corresponding neighbour transmitters and the inward neighbour link is
coloured as the reference transmitter as it is neighbour of Site9_3(0) here.
In Figure 14.48, neighbour links are displayed according to the neighbour frequency. Here, all neighbour relations
are symmetric.
Figure 14.48: Neighbours of Site 22_3(0) - Display According to The Neighbour Frequency
Note: You can display either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting
either Forced Neighbours or Forbidden Neighbours.
2. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
3. Select Display Options from the context menu. The Neighbourhood Display dialogue appears.
4. Under Intra-technology Neighbours, select the Display Coverage Areas check box.
5. Click the Browse button ( ) beside the Display Coverage Areas check box.
6. The Intra-technology Neighbour Display dialogue appears.
7. From the Display Type list, choose one of the following:
- Unique: Select "Unique" as the Display Type if you want Atoll to colour the coverage area of a cell’s 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 cell’s neighbours according to a value from the Intra-technology
Neighbours table.
- Value Intervals: Select "Value Intervals" to colour the coverage area of a cell’s neighbours according the
value interval of the value selected from the Field list. For example, you can choose to display a cell’s neigh-
bours according to the importance, as determined by the weighting factors.
8. Click the Browse button ( ) next to Tip Text and select the neighbour characteristics to be displayed in the
tooltip. This information will be displayed on each coverage area.
9. Click the menu button ( ) of the Visual Management button ( ) in the Radio toolbar. The menu appears.
10. Select Neighbours from the menu. The neighbours of a cell will be displayed when you select a transmitter.
13. In order to restore colours and cancel the neighbour display, click the Visual Management button ( ) in the
Radio toolbar.
Allocating or Deleting Neighbours Using the Cells Tab of the Transmitter Properties Dialogue
To allocate or delete LTE neighbours using the Cells tab of the transmitter’s 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 transmitter’s Properties dialogue appears.
3. Click the Cells tab.
4. On the Cells tab, click the Browse button ( ) beside Neighbours. The cell’s Properties dialogue appears.
5. Click the Intra-technology Neighbours tab.
6. If desired, you can enter the maximum number of neighbours.
7. Allocate or delete a neighbour.
To allocate a new neighbour:
a. Under List, select the cell from the list in the Neighbour column in the row marked with the New Row icon
( ).
b. Click elsewhere in the table when you have finished creating the new neighbour.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Right-click the neighbour in the Neighbour column. The context menu appears.
c. Select Delete Link and Symmetric Relation from the context menu. The symmetric neighbour relation be-
tween the cell in the Neighbour column and the cell in the Cell column is deleted.
To delete a neighbour:
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Press DEL to delete the neighbour.
8. Click OK.
Note: For information on working with data tables, see "Working with Data Tables" on page 50.
a. In the row marked with the New Row icon ( ), select a reference cell in the Cell column.
b. Select the neighbour in the Neighbour column.
c. Click elsewhere in the table to create the new neighbour and add a new blank row to the table.
When the new neighbour is created, Atoll automatically calculates the distance between the reference cell
and the neighbour and displays it in the Distance column, sets the Type to "manual," and sets the Importance
to "1."
a. Right-click the neighbour in the Neighbour column. The context menu appears.
b. Select Symmetrise from the context menu. A symmetric neighbour relation is created between the cell in the
Neighbour column and the cell in the Cell column.
To make several neighbour relations symmetric:
a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select
contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contig-
uous rows by pressing CTRL and clicking each rows separately.
b. Right-click the Neighbours table. The context menu appears.
c. Select Symmetrise from the context menu.
To take into consideration all exceptionnal pairs:
Note: You can add or delete either some forced neighbours or some forbidden neighbours using
the Exceptional Pairs of Intra-Technology Neighbours table. You can open this table,
select the exceptional pairs to be considered, right-click the table and select Force
Exceptional Pairs in the context menu.
a. Click in the left margins of the table rows containing the neighbours to select the entire rows. You can select
contiguous rows by clicking the first row, pressing SHIFT and clicking the last row. You can select non-contig-
uous rows by pressing CTRL and clicking each rows separately.
b. Right-click the Neighbours table. The context menu appears.
c. Select Delete Link and Symmetric Relation from the context menu.
To delete a neighbour:
a. Click in the left margin of the table row containing the neighbour to select the entire row.
b. Press DEL to delete the neighbour.
You can allocate or delete intra-technology neighbours directly on the map using the mouse.
To add or remove intra-technology neighbours using the mouse, you must activate the display of intra-technology neigh-
bours on the map as explained in "Displaying Neighbour Relations on the Map" on page 1055.
To add a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter with which you want to set a neighbour relation. Atoll adds both transmitters
to the intra-technology neighbours list.
To remove a symmetric neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press SHIFT and click the transmitter you want to remove from the list of neighbours. Atoll removes both trans-
mitters from the intra-technology neighbours.
To add an outward neighbour relation:
1. Click the reference transmitter on the map. Atoll displays its neighbour relations.
2. Press CTRL and click the transmitter with which you want to set a neighbour relation. Atoll adds the reference
transmitter to the intra-technology neighbour list of the transmitter.
Notes:
• When there is more than one cell on the transmitter, clicking the transmitter in the map window
opens a context menu allowing you to select the cell you want (see "Selecting One of Several
Transmitters or Microwave Links" on page 30).
• You can add or delete either forced neighbours or forbidden neighbours by clicking the menu
button ( ) of the Visual Management button ( ) in the Radio toolbar and selecting either
Forced Neighbours or Forbidden Neighbours.
Note: If the field Max number of intra-technology neighbours in the Cells table is empty, the
Full Lists check and the Lists > Max Number check use the Default Max Number value
defined in the audit dialogue.
- Missing Co-Sites: X; total number of missing co-site neighbours in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Non Symmetric Links: X; total number of non-symmetric neighbour links in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
- Missing Forced: X; total number of forced neighbours missing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR|
- Existing Forbidden: X; total number of forbidden neighbours existing in the audited neighbour plan.
Syntax: |CELL| |NEIGHBOUR| |TYPE| |REASON|
The AFP enables you to automatically allocate frequencies to cells in the current network.
To automatically allocate frequencies:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Frequency Plan > Automatic Allocation. The Frequency Allocation dialogue appears.
4. You can set the following parameters:
- Under Allocate, you can select Frequencies to perform automatic frequency planning or Physical Cell IDs
to allocate physical cell IDs to cells automatically.
- If you have selected Physical Cell IDs under Allocate, under S-SCH ID Allocation Strategy, you can select
one of the following automatic allocation strategies:
- Free
- Same per Site
For more information on the strategies, see "Automatically Allocating Physical Cell IDs to LTE Cells" on
page 1065.
- Under Relations, you can set the relations to take into account in automatic allocation.
- Under Interference Matrices, you can calculate and take interference matrices into account for the fre-
quency allocation. When the Frequency Allocation dialogue opens, the Take into account check box is
disabled because interference matrices are not yet calculated nor available.
To calculate interference matrices:
i. Click the Details button. The Interference Matrices Display dialogue appears. This dialogue lists all the
interfered and interfering cell pairs and their respective interference probabilities in co- and adjacent chan-
nel cases.
ii. Click the Close button. The Interference Matrices Display dialogue closes.
To delete the calculated interference matrices:
- Click the Delete button.
To take the calculated interference matrices into account:
- Select the Take into account check box.
Interference Matrices Calculation and Quality Margin:
Interference matrices calculated by the AFP are the co- and adjacent channel interference probabilities
for each interfered and interfering cell pair. The probability of interference of a cell is defined as the ratio
of the interfered surface area within the best server coverage area of any studied cell to the total best serv-
er coverage area of the cell:
S Int
P Int = --------------
-
S Total
In words, S Total is the best server coverage area of the studied cell, and S Int is the surface area within
the best server area of the studied cell where the interference from another cell is higher than the refer-
ence signal C/N threshold of the studied cell plus the quality margin.
The quality margin is defined with respect to the reference signal C/N thresholds of cells. By default the
reference signal C/N threshold outlines the area of service of a cell. This means that where the reference
signal C/N of a cell is less than the reference signal C/N threshold, there is no service. The AFP uses the
quality margin to calculate interference within the service areas of cells.
- Take min reuse distance into account: Select this check box if you want the AFP to take relations based
on distance into account for the allocation. You can enter the Default radius within which two cells whose
channels have a co-channel overlap cannot have the same frequency or physical cell ID.
Note: A minimum reuse distance can be defined at the cell level (in the cell Properties dialogue
or in the Cells table). If defined, a cell-specific reuse distance will be used instead of
default the value entered here.
- Take neighbours into account: Select this check box if you want the AFP to take neighbour relations
into account for the allocation. The AFP will try to avoid allocating the same frequency or physical cell ID
to neighbours of each cell being allocated.
Atoll can only take neighbour relations into account if neighbours have already been allocated. For infor-
mation on allocating neighbours, see "Planning Neighbours" on page 1052.
5. Under Results, Atoll displays the Total Cost of the current frequency or physical cell ID allocation taking into
account the parameters set in step 4. You can modify the parameters and click Recalculate Cost to see the
change in the total cost.
6. Click Calculate. Atoll begins the process of allocating frequencies or physical cell IDs.
Once Atoll has finished allocating frequencies or physical cell IDs, the proposed allocation is visible under
Results.
When you allocate frequencies to a large number of cells, it is easiest to let Atoll allocate them automatically, as described
in "Automatically Allocating Frequencies to Cells" on page 1062. However, if you want to assign a frequency or a physical
cell ID to one cell or to modify it, you can do it by accessing the properties of the cell.
To allocate the frequency or physical cell ID to a cell manually:
1. On the map, right-click the transmitter to whose cell you want to allocate the frequency or physical cell ID. The
context menu appears.
2. Select Properties from the context menu. The transmitter’s Properties dialogue appears.
3. Select the Cells tab.
4. Select a Frequency Band and Channel Number for the cell or enter a Physical Cell ID.
5. You can set the Channel Allocation Status or Physical Cell ID Status to Fixed if you want to lock the frequency
or physical cell ID that you assigned.
6. Click OK.
In Atoll, you can search for frequency bands and channel numbers using the Search Tool.
If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results
displayed by transmitter, the search results will be displayed by transmitter coverage. Frequencies and any potential prob-
lems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage Prediction
by Transmitter" on page 1026.
To find a frequency band using the Search Tool:
1. Click View > Search Tool. The Search Tool window appears.
2. Select the Channel tab.
3. Select a Frequency Band from the list of available frequency bands.
4. Set Channel Number to All.
5. Click Search.
Transmitters whose cells use the selected frequency band are displayed in red. Transmitters with cells using other
frequency bands are displayed in grey.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
If you selected the Co-channel Only check box, transmitters with cells using the same channel number are
displayed in red, and all others, including transmitters with adjacent channels, are displayed in grey.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
Note: By including the frequency band and channel number of each cell in the transmitter label,
the search results will be easier to understand. For information on defining the label, see
"Defining the Object Type Label" on page 35.
You can display the frequency allocation on transmitters by using the transmitters’ display characteristics.
To display the frequency allocation on the map:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Display tab.
5. Select "Discrete Values" as the Display Type and "Cells: Channel Number" as the Field.
6. Click OK. Transmitters will be displayed by channel number.
You can also display the frequency band and channel number in the transmitter label or tooltip by selecting "Cells:
Frequency Band" and "Cells: Channel Number" from the Label or Tip Text Field Definition dialogue.
For information on display options, see "Display Properties of Objects" on page 33.
You can group transmitters on the Data tab of the Explorer window by their frequency bands or channel numbers.
To group transmitters by frequency bands or channel numbers:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the General tab, click Group by. The Group dialogue appears.
5. Under Available Fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
- Frequency Band
- Channel Number
- Min Reuse Distance
- Channel Allocation Status
7. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to
the list of parameters on which the transmitters will be grouped.
8. If you do not want the transmitters to be sorted by a certain parameter, select the parameter in the Group these
fields in this order list and click . The selected parameter is removed from the list of parameters on which
the transmitters will be grouped.
9. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters
to be grouped:
10. Click OK to save your changes and close the Group dialogue.
You can create and compare reference signal C/(I+N) coverage predictions before and after the automatic frequency allo-
cation in order to analyse and compare the improvements brought about by the AFP. For more information on creating
reference signal C/(I+N) coverage predictions, see "Making a Coverage by C/(I+N) Level" on page 1041. For more infor-
mation on comparing two coverage predictions, see "Comparing Coverage Predictions: Examples" on page 1032.
The allocation algorithm enables you to automatically allocate physical cell IDs to cells in the current network. You can
choose from two allocation strategies for the S-SCH ID (for more information, see the Technical Reference Guide):
• Free: The physical cell ID allocation will only be restricted by the P-SCH ID allocated to nearby cells. S-SCH IDs
will not necessarily be the same for all the cells of a site.
• Same per Site: This strategy allocates physical cell IDs to cells such that the same S-SCH ID is assigned to all
the cells of a site.
- Min Reuse Distance: Select the Min Reuse Distance check box if you want to consider relations based
on distance. You can enter the Default radius within which two cells whose channels have a co-channel
overlap cannot have the same physical cell ID.
Note: A minimum reuse distance can be defined at the cell level (in the cell Properties dialogue
or in the Cells table). If defined, a cell-specific reuse distance will be used instead of
default the value entered here.
- Under S-SCH ID Allocation Strategy, you can select one of the following automatic allocation strategies:
- Free
- Same per Site
5. Under Results, Atoll displays the Total Cost of the current physical cell ID allocation taking into account the
parameters set in step 4. You can modify the parameters and click Recalculate Cost to see the change in the
total cost.
6. Click Calculate. Atoll begins the process of allocating physical cell IDs.
Once Atoll has finished allocating physical cell IDs, the IDs are visible under Results.
When you allocate physical cell IDs to a large number of cells, it is easiest to let Atoll allocate physical cell IDs automati-
cally, as described in "Automatically Allocating Physical Cell IDs to LTE Cells" on page 1065. However, if you want to
assign a physical cell ID to one cell or to modify it, you can do it by accessing the properties of the cell.
To allocate a physical cell ID to an LTE cell manually:
1. On the map, right-click the transmitter to whose cell you want to allocate a physical cell ID. The context menu
appears.
2. Select Properties from the context menu. The transmitter’s Properties dialogue appears.
3. Select the Cells tab.
4. Enter a Physical Cell ID in the cell’s column.
5. You can set the Physical Cell ID Status to Fixed if you want to lock the physical cell ID that you assigned.
6. Click OK.
In Atoll, you can search for physical cell IDs, P-SCH IDs, and S-SCH IDs using the Search Tool.
If you have already calculated and displayed a coverage prediction by transmitter based on the best server, with the results
displayed by transmitter, the search results will be displayed by transmitter coverage. Physical cell IDs and any potential
problems will then be clearly visible. For information on coverage predictions by transmitter, see "Making a Coverage
Prediction by Transmitter" on page 1026.
To find a physical cell ID using the Search Tool:
1. Click View > Search Tool. The Search Tool window appears.
2. Select the Physical Cell ID tab.
3. Select Physical Cell ID.
4. Enter a Physical Cell ID.
5. Click Search.
Transmitters whose cells use the entered physical cell ID are displayed in red. Transmitters with cells use other
physical cell IDs are displayed in grey.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
Note: By including the physical cell ID of each cell in the transmitter label, the search results will
be easier to understand. For information on defining the label, see "Defining the Object
Type Label" on page 35.
Transmitters whose cells use the entered S-SCH ID are displayed in red. Transmitters with cells use other S-SCH
IDs are displayed in grey.
To restore the initial transmitter colours, click the Reset Display button in the Search Tool window.
You can display physical cell ID allocation on transmitters by using the transmitters’ display characteristics.
To display physical cell ID allocation on the map:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. Click the Display tab.
5. Select "Discrete Values" as the Display Type and "Cells: Physical Cell ID" as the Field.
6. Click OK. Transmitters will be displayed by physical cell ID.
You can also display the physical cell ID in the transmitter label or tooltip by selecting "Cells: Physical Cell ID" from the
Label or Tip Text Field Definition dialogue.
For information on display options, see "Display Properties of Objects" on page 33.
You can group transmitters on the Data tab of the Explorer window by their physical cell ID or their reuse distance.
To group transmitters by physical cell ID:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Properties from the context menu. The Properties dialogue appears.
4. On the General tab, click Group by. The Group dialogue appears.
5. Under Available Fields, scroll down to the Cell section.
6. Select the parameter you want to group transmitters by:
- Physical Cell ID
- Min Reuse Distance
- Physical Cell ID Status
7. Click to add the parameter to the Group these fields in this order list. The selected parameter is added to
the list of parameters on which the transmitters will be grouped.
8. If you do not want the transmitters to be sorted by a certain parameter, select the parameter in the Group these
fields in this order list and click . The selected parameter is removed from the list of parameters on which
the transmitters will be grouped.
9. Arrange the parameters in the Group these fields in this order list in the order in which you want the transmitters
to be grouped:
10. Click OK to save your changes and close the Group dialogue.
You can use a histogram to analyse the use of allocated physical cell IDs in a network. The histogram represents the phys-
ical cell IDs as a function of the frequency of their use.
To display the physical cell ID histogram:
1. Click the Data tab in the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Cells > Physical Cell IDs > ID Distribution. The Distribution Histograms dialogue appears.
Each bar represents a physical cell ID, its height depending on the frequency of its use.
4. Move the pointer over the histogram to display the frequency of use of each physical cell ID. The results are high-
lighted simultaneously in the Detailed Results list.
• Traffic map per user profile can be used if you have marketing-based traffic data.
Traffic maps per density of user profiles, where each vector (polygon, line or point) describes subscriber densities
(or numbers of subscribers for points) with user profiles and mobility types, and traffic maps per environment of
user profiles, where each pixel has an assigned environment class. For more information, see "Importing a Traffic
Map Based on Densities of User Profiles" on page 1072, "Importing a Traffic Map Based on Environments of User
Profiles" on page 1074 and "Creating a Traffic Map Based on Environments of User Profiles" on page 1074.
• Traffic maps per density (number of users per km2) can be used if you have population-based traffic data,
or 2G network statistics.
Each pixel has an actual user density assigned. For more information, see "Creating Traffic Maps per User
Density (No. Users/km2)" on page 1075, "Importing a Traffic Map per User Density" on page 1075, "Converting
2G Network Traffic" on page 1076 and "Exporting Cumulated Traffic" on page 1077
Note: You can also import a traffic map from a file by clicking the Import button. You can import
AGD (Atoll Geographic Data) format files that you have exported from another Atoll
document.
7. Select a coverage prediction by transmitter from the list of available coverage predictions by transmitter.
8. Enter the data required in the Map per Sector dialogue:
- If you have selected Throughputs in Uplink and Downlink, enter the throughput demands in the uplink and
downlink for each sector and for each listed service.
- If you have selected Number of Users per Activity Status, enter the number of users active in the uplink, in
the downlink and in the uplink and downlink, for each sector and for each service.
Note: You can also import a text file containing the data by clicking the Actions button and
selecting Import Table from the menu. For more information on importing table data, see
"Importing Tables from Text Files" on page 59.
4. Select Update from the context menu. The Map per Sector dialogue appears.
Select the updated coverage prediction by transmitter and define traffic values for the new transmitter(s) listed at
the bottom of the table. Deleted or deactivated transmitters are automatically removed from the table.
You can model variations in user behaviour by creating different profiles for different times of the day or for different circum-
stances. For example, a user may be considered a business user during the day, with video conferencing and voice, but
no web browsing. In the evening the same user might not use video conferencing, but might use multi-media services and
web browsing.
To create or modify a user profile:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the LTE Parameters folder.
3. Right-click the User Profiles folder. The context menu appears.
4. Select New from the context menu. The User Profiles New Element Properties dialogue appears.
Note: You can modify the properties of an existing user profile by right-clicking the user profile in
the User Profiles folder and selecting Properties from the context menu.
Note: In order for all the services defined for a user profile to be taken into account during traffic
scenario elaboration, the sum of activity probabilities must be lower than 1.
- Duration (sec.): For services of the type "voice," enter the average duration of a call in seconds. For services
of the type "data," this field is left blank.
- UL Volume (KBytes): For services of the type "data," enter the average uplink volume per session in kilo-
bytes.
- DL Volume (KBytes): For services of the type "data," enter the average downlink volume per session in kil-
obytes.
6. Click OK.
Modelling Environments
An environment class describes its environment using a list of user profiles, each with an associated mobility type and a
given density (i.e., the number of users with the same profile per km²). To get an appropriate user distribution, you can
assign a weight to each clutter class for each environment class. You can also specify the percentage of indoor subscribers
for each clutter class. In a Monte Carlo simulation, an additional loss (as defined in the clutter class properties) will be
added to the indoor users’ path loss.
To create or modify an LTE environment:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the LTE Parameters folder.
3. Right-click the Environments folder. The context menu appears.
4. Select New from the context menu. The Environments New Element Properties dialogue appears.
Note: You can modify the properties of an existing environment by right-clicking the
environment in the Environments folder and selecting Properties from the context
menu.
7. In the row marked with the New Row icon ( ), set the following parameters for each user profile/mobility com-
bination that this LTE environment will describe:
- User: Select a user profile.
- Mobility: Select a mobility type.
- Density (Subscribers/km2): Enter a density in terms of subscribers per square kilometre for the combination
of user profile and mobility type.
8. Click the Clutter Weighting tab.
9. For each clutter class, enter a weight that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk × Sk
N k = N Area × --------------------------
∑
Wi × Si
i
where:
For example: An area of 10 km² with a user density of 100/km². Therefore, in this area, there are 1000 users. The
area is covered by two clutter classes: Open and Building. The clutter weighting for Open is "1" and for Building is
"4." Given the respective weights of each clutter class, 200 subscribers are in the Open clutter class and 800 in
the Building clutter class.
10. If you wish you can specify a percentage of indoor users for each clutter class. During a Monte Carlo simulation,
an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
11. Click OK.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 1074.
- User Profile: If you want to import user profile information from the file, under Defined, select "By field" and
select the source field from the Choice column. If you want to assign a user profile from the LTE Parameters
folder of the Data tab, under Defined, select "By value" and select the user profile in the Choice column.
- Mobility: If you want to import mobility information from the file, under Defined, select "By field" and select
the source field from the Choice column. If you want to assign a mobility type from the LTE Parameters folder
of the Data tab, under Defined, select "By value" and select the mobility type in the Choice column.
- Density: If you want to import density information from the file, under Defined, select "By field" and select the
source field from the Choice column. If you want to assign a density, under Defined, select "By value" and
enter a density in the Choice column for the combination of user profile and mobility type. In this context, the
term "density" depends on the type of vector traffic map. It refers to the number of subscribers per square kil-
ometre for polygons, the number of subscribers per kilometre in case of lines, and the number of subscribers
when the map consists of points.
Important: When you import user profile or mobility information from the file, the values in the file
must be exactly the same as the corresponding names in the LTE Parameters folder of
the Data tab. If the imported user profile or mobility does not match, Atoll will display a
warning.
13. Under Clutter Distribution, enter a weight for each class that will be used to calculate a user distribution.
The user distribution is calculated using the following equation:
Wk × Sk
N k = N Area × --------------------------
∑
Wi × Si
i
where:
14. If you wish you can specify a percentage of indoor subscribers for each clutter class. During a Monte Carlo simu-
lation, an additional loss (as defined in the clutter class properties) will be added to the indoor users path loss.
15. Click OK to finish importing the traffic map.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 1074.
7. Select the file to import. The file must be in one of the following supported raster formats (8 bit): TIF, BIL, IST,
BMP, PlaNET©, GRC Vertical Mapper, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic map’s properties dialogue appears.
11. Select the Description tab.
In the imported map, each type of region is defined by a number. Atoll reads these numbers and lists them in the
Code column.
12. For each Code, select the environment it corresponds to from the Name column.
The environments available are those available in the Environments folder, under LTE Parameters on the Data
tab of the Explorer window. For more information, see "Modelling Environments" on page 1072.
13. Select the Display tab. For information on changing the display parameters, see "Display Properties of Objects"
on page 33.
14. Click OK.
7. Select the environment class from the list of available environment classes.
8. Click the Draw Polygon button ( ) to draw the polygon on the map for the selected environment class.
9. Click the Delete Polygon button ( ) and click the polygon to delete the environment class polygon on the map.
10. Click the Close button to close the Environment Map Editor toolbar and end editing.
5. Click Close.
If a clutter classes map is available in the document, traffic statistics provided for each environment class are listed per
clutter class.
Note: You can also create a traffic map manually in Atoll by clicking the Create button in the
New Traffic Map dialogue. For information, see "Creating a Traffic Map Based on
Environments of User Profiles" on page 1074.
7. Select the file to import. The file must be in one of the following supported raster formats (16 or 32 bit): BIL, BMP,
PlaNET©, TIF, ISTAR, and Erdas Imagine.
8. Click Open. The File Import dialogue appears.
9. Select Traffic from the Data Type list.
10. Click Import. Atoll imports the traffic map. The traffic map’s properties dialogue appears.
17. Click OK. Atoll creates the traffic map in the Traffic folder.
12. Click OK. Atoll creates the traffic map in the Traffic folder.
13. Right-click the traffic map. The context menu appears.
14. Select Edit from the context menu.
15. Use the tools available in the Vector Edition toolbar in order to draw contours. For more information on how to edit
contours, see "Editing Contours, Lines, and Points" on page 131. Atoll creates an item called Density values in
the User Density Map folder.
16. Right-click the item. The context menu appears.
17. Select Open Table from the context menu.
18. In the table, enter a traffic density value (i.e. the number of users per km2) for each contour you have drawn.
19. Right-click the item. The context menu appears.
20. Select Edit from the context menu to end editing.
Important: You must enter a resolution before exporting. If you do not enter a resolution, it remains
at "0" and no data will be exported.
8. Under Traffic, define the data to be exported in the cumulated traffic. Atoll uses this information to filter the traffic
data to be exported.
- Terminal: Select the type of terminal that will be exported or select "All" to export traffic using any terminal.
- Service: Select the service that will be exported, or select "Circuit services" to export voice traffic, or select
"Packet services" to export data traffic.
- Mobility: Select the mobility type that will be exported or select "All" to export all mobility types.
- Activity: Select one of the following:
- All Activity Statuses: Select All Activity Statuses to export all users without any filter by activity status.
- Uplink: Select Uplink to export mobiles active in the uplink only.
- Downlink: Select Downlink to export mobiles active in the downlink only.
- Uplink/Downlink: Select Uplink/Downlink to export only mobiles with both uplink and downlink activity.
9. In the Select Traffic Maps to Be Used list, select the check box of each traffic map you want to include in the
cumulated traffic.
10. Click OK. The defined data is extracted from the selected traffic maps and cumulated in the exported file.
- ID: The subscriber ID in the subscriber list. It is an automatically created identification number.
- X and Y coordinates: The geographical coordinates of the subscriber. A subscriber’s location is always fixed.
- Height: The altitude of the subscriber antenna with respect to the ground (DTM).
- Clutter: The name of the clutter class where the subscriber is located. This is a non-editable field whose con-
tents are automatically updated.
- Name: You can assign a descriptive name to each subscriber.
- User Profile: A user profile defines the traffic demand characteristics of subscribers. Atoll determines the ter-
minal used, the service accessed, and the activity status of subscribers during Monte Carlo simulations
according to the information in the user profiles. For more information, see "Modelling User Profiles" on
page 1071.
- Terminal: The default terminal is the user equipment with an antenna, LTE equipment, and noise character-
istics. The properties of this terminal are taken into consideration when performing calculations on the sub-
scriber list.
- Service: The service that the subscriber accesses by default. The properties of this service are taken into con-
sideration when performing calculations on the subscriber list.
Note: Subscriber lists use the mobility type "Fixed", i.e., 0 km/hr, in calculations. Make sure that
you have bearer selection thresholds defined for this mobility type in the LTE equipment
properties. For information on defining bearer selection thresholds, see "Defining LTE
Equipment" on page 1104.
- Azimuth: The orientation of the subscriber antenna in the horizontal plane. Azimuth is always considered with
respect to the north. You can either define this value manually or let Atoll calculate it for the subscriber. Atoll
points the subscriber antenna towards its serving base station.
- Mechanical Downtilt: The orientation of the subscriber antenna in the vertical plane. Mechanical downtilt is
positive when it is downwards and negative when upwards. You can either define this value manually or let
Atoll calculate it for the subscriber. Atoll points the subscriber antenna towards its serving base station.
- Lock Status: You can choose to lock the subscriber antenna orientation and serving transmitter. Use this
option if you do not want Atoll to change the assigned server or the antenna orientation.
- Serving Base Station: The serving transmitter of the subscriber. You can either define this value manually
or let Atoll calculate it for the subscriber. The serving base station is determined according to the received
reference signal level from the cell with the highest power.
- Reference Cell: The reference cell of the serving transmitter of the subscriber. You can either define this value
manually or let Atoll calculate it for the subscriber. If more than one cell of the serving base station cover the
subscriber, the one with the lowest order is selected as the reference cell.
- Distance: The distance of the subscriber from its serving base station. This is a non-editable field whose con-
tents are automatically updated.
- Received Reference Signal Power (DL) (dBm): The reference signal level received at the subscriber loca-
tion in the downlink. This value is calculated by Atoll during calculations on subscriber lists.
- Received SCH/PBCH Power (DL) (dBm): The SCH/PBCH signal level received at the subscriber location in
the downlink. This value is calculated by Atoll during calculations on subscriber lists.
- Received PDSCH/PDCCH Power (DL) (dBm): The PDSCH/PDCCH signal level received at the subscriber
location in the downlink. This value is calculated by Atoll during calculations on subscriber lists.
- SCH/PBCH Total Noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the sub-
scriber location in the downlink on the SCH and PBCH. This value is generated by Atoll during the calculations
on subscriber lists.
- PDSCH/PDCCH Total Noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the
subscriber location in the downlink on the PDSCH and PDCCH. This value is generated by Atoll during the
calculations on subscriber lists.
- Reference Signal C/(I+N) (DL) (dB): The reference signal C/(I+N) at the subscriber location in the downlink.
This value is generated by Atoll during the calculations on subscriber lists.
- SCH/PBCH C/(I+N) (DL) (dB): The SCH/PBCH C/(I+N) at the subscriber location in the downlink. This value
is generated by Atoll during the calculations on subscriber lists.
- PDSCH/PDCCH C/(I+N) (DL) (dB): The PDSCH/PDCCH C/(I+N) at the subscriber location in the downlink.
This value is generated by Atoll during the calculations on subscriber lists.
- Bearer (DL): The highest LTE bearer available for the PDSCH/PDCCH C/(I+N) level at the subscriber location
in the downlink. This value is generated by Atoll during the calculations on subscriber lists.
- BLER (DL): The Block Error Rate read from the subscriber’s terminal type’s LTE equipment for the PDSCH/
PDCCH C⁄(I+N) level at the subscriber location in the downlink. This value is generated by Atoll during the
calculations on subscriber lists.
- Diversity Mode (DL): The diversity mode supported by the cell or permutation zone in downlink.
- Peak RLC Channel Throughput (DL) (kbps): The maximum RLC channel throughput attainable using the
highest bearer available at the subscriber location in the downlink. This value is generated by Atoll during the
calculations on subscriber lists.
- Effective RLC Channel Throughput (DL) (kbps): The effective RLC channel throughput attainable using the
highest bearer available at the subscriber location in the downlink. This value is generated by Atoll during the
calculations on subscriber lists.
- Received PUSCH/PUCCH Power (UL) (dBm): The PUSCH/PUCCH signal level received at the serving
transmitter from the subscriber terminal in the uplink. This value is generated by Atoll during the calculations
on subscriber lists.
- PUSCH/PUCCH Total Noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the
serving transmitter of the subscriber in the uplink on the PUSCH. This value is generated by Atoll during the
calculations on subscriber lists.
- PUSCH/PUCCH C/(I+N) (UL) (dB): The PUSCH/PUCCH C/(I+N) at the serving transmitter of the subscriber
in the uplink. This value is generated by Atoll during the calculations on subscriber lists.
- Bearer (UL): The highest LTE bearer available for the PUSCH/PUCCH C/(I+N) level at the serving transmitter
of the subscriber in the uplink. This value is generated by Atoll during the calculations on subscriber lists.
- BLER (UL): The Block Error Rate read from the reference cell’s LTE equipment for the PUSCH/PUCCH C/
(I+N) level at the serving transmitter of the subscriber in the uplink. This value is generated by Atoll during the
calculations on subscriber lists.
- Diversity Mode (UL): The diversity mode supported by the cell or permutation zone in uplink.
- Transmission Power (UL) (dBm): The transmission power of the subscriber’s terminal after power control in
the uplink. This value is generated by Atoll during the calculations on subscriber lists.
- Allocated Bandwidth (UL) (No. of Frequency Blocks): The number of frequency blocks allocated to the
subscriber in the uplink by the eNode-B. This value is generated by Atoll during the calculations on subscriber
lists.
- Peak RLC Channel Throughput (UL) (kbps): The maximum RLC channel throughput attainable using the
highest bearer available at the serving transmitter of the subscriber in the uplink. This value is generated by
Atoll during the calculations on subscriber lists.
- Effective RLC Channel Throughput (UL) (kbps): The effective RLC channel throughput available using the
highest bearer available at the serving transmitter of the subscriber in the uplink. This value is generated by
Atoll during the calculations on subscriber lists.
For more information on the calculations that you can carry out on subscriber lists, see "Performing Calculations
on Subscriber lists" on page 1081.
6. Click the Display tab. You can modify how subscribers added to the list are displayed. For information on defining
the display properties, see "Display Properties of Objects" on page 33.
7. Click OK. Atoll creates a new subscriber list.
You can now move the pointer over the map and click once to place a new subscriber at the location of the pointer. Press
ESC or click the normal pointer button ( ), to finish adding subscribers on the map. For information on adding subscribers
to a list, see "Adding Subscribers to a Subscriber List Using the Mouse" on page 1080.
You can open the subscriber list table containing all the subscribers and their parameters.
To open the subscriber list table:
1. Click the Data tab in the Explorer window.
2. Click the Expand button ( ) to expand the Subscribers folder.
3. Right-click the subscriber list you want to open. The context menu appears.
4. Select Open Table from the context menu.
For information on working with data tables, see "Working with Data Tables" on page 50.
4. Select Add Subscribers from the context menu. The pointer changes to subscriber addition mode ( ).
5. Move the mouse over the Map window, and click once to add each subscriber.
6. Press ESC or click the normal pointer button ( ) to finish adding subscribers.
Tip: To place subscribers more accurately, before clicking the map, you can zoom in on the
map. For information on using the zooming tools, see "Changing the Map Scale" on
page 38.
Note: You can also export subscriber lists. For information on exporting table data, see
"Exporting Tables to Text Files" on page 58.
5. Click Calculate. The progress of the calculation, as well as any error messages, is displayed in the Event Viewer.
6. Once the calculations are finished, click Close to close the Event Viewer.
7. Click Commit to store the results in the subscriber list. For the list of results that are available after the calculations,
see "Creating a Subscriber List" on page 1078.
Each mobile generated during the simulations is assigned a service, a mobility type, and a terminal according to
the user profile assigned to it. A transmission status is determined according to the activity probabilities. The trans-
mission status is an important output of the simulation as it has a direct impact on the next step of the simulation
process, i.e., the radio resource management (RRM), and has an impact on the interference level in the network.
The geographical location of each mobile is determined randomly for the mobiles generated based on the traffic
data from traffic maps. The mobiles generated based on the traffic data from subscriber lists are located on the
subscriber locations.
3. Downlink Calculations
The downlink calculations include the calculation of downlink reference signal, SCH/PBCH, and PDSCH/PDCCH
C/(I+N), determination of the best available bearer for the PDSCH/PDCCH C/(I+N), allocation of resources (RRM),
and calculation of user throughputs.
4. Uplink Calculations
The uplink calculations include the calculation of PUSCH/PUCCH C/(I+N), determination of the best available
bearer for the PUSCH/PUCCH C/(I+N), uplink power control and calculation of the number of allocated frequency
blocks depending on the bearer, allocation of resources (RRM), update of uplink noise rise values for cells, and
calculation of user throughputs.
At the end of the simulations, an active user can be connected in the direction corresponding to his activity status if:
• he has a best server assigned (step 2.),
• he has a bearer in the direction corresponding to his activity status (step 3. and step 4.),
• he is among the users selected by the scheduler for resource allocation (step 5.), and
• he is not rejected due to resource saturation (step 5.).
If a user is rejected during step 2., step 3., or step 4., the cause of rejection is "No Service". If a user is rejected during
step 5., the cause of rejection can either be "Scheduler Saturation," i.e., the user is not among the users selected for
resource allocation, or he can be rejected due to "Resource Saturation," i.e., all of the cell’s resources were used up by
other users.
Note: When you perform simulations for subscriber lists, Atoll does not base the calculations on
subscriber lists on the path loss matrices calculated for transmitters. This is because the
path loss matrices are calculated for a given receiver height (1.5 m by default), but each
subscriber in a subscriber list can have a different height. Therefore, Atoll recalculates
the path loss, received power, and other output, for each subscriber when you perform
simulations on subscribers.
Tip: Using the same generated user and shadowing error distribution for several simulations
can be useful when you want to compare the results of several simulations where only one
parameter changes.
Tip: You can make the traffic distribution easier to see by hiding geographic data and
coverage predictions. For information, see "Displaying or Hiding Objects on the Map
Using the Explorer" on page 28.
Figure 14.59: Displaying the traffic simulation results using tool tips
The Statistics tab: The Statistics tab contains the following sections:
- 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 User Throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink in all the cells of the site.
- Peak 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 User Throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink in all the cells of the site.
- Peak 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 User Throughput (DL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the downlink in all the cells of the site.
- Peak 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 User Throughput (UL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the uplink in all the cells of the site.
- No Service: The number of users unable to connect to any cell of the site for which the rejection cause was
"No Service."
- Scheduler Saturation: The number of users unable to connect to any cell of the site for which the rejection
cause was "Scheduler Saturation."
- Resource Saturation: The number of users unable to connect to any cell of the site for which the rejection
cause was "Resource Saturation."
The Cells tab: The Cells tab contains the following information, per site and transmitter:
- Traffic Load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation.
- Traffic Load (UL) (%): The traffic loads of the cells calculated on the uplink during the simulation.
- UL Noise Rise (dB): The noise rise of the cells calculated on the uplink during the simulation.
- MU-MIMO Gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO.
- Peak RLC User Throughput (DL) (kbps): The sum of peak RLC user throughputs of all the users connected
in the downlink.
- Effective RLC User Throughput (DL) (kbps): The sum of effective RLC user throughputs of all the users
connected in the downlink.
- Application User Throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink.
- Peak RLC User Throughput (UL) (kbps): The sum of peak RLC user throughputs of all the users connected
in the uplink.
- Effective RLC User Throughput (UL) (kbps): The sum of effective RLC user throughputs of all the users
connected in the uplink.
- Application User Throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink.
- Peak 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.
- 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.
- Application User Throughput (DL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the downlink.
- 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.
- 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.
- Application User Throughput (UL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the uplink.
- No Service: The number of users unable to connect to the cell for which the rejection cause was "No Service."
- Scheduler Saturation: The number of users unable to connect to the cell for which the rejection cause was
"Scheduler Saturation."
- Resource Saturation: The number of users unable to connect to the cell for which the rejection cause was
"Resource Saturation."
The Mobiles tab: The Mobiles tab contains the following information:
- X and Y: The coordinates of users who attempt to connect (the geographic position is determined by the
second random trial).
- Height: The height of the user terminal (antenna).
- User Profile: The assigned user profile. Atoll uses the assigned service and activity status to determine the
terminal and the user profile.
- Service: The service assigned during the first random trial during the generation of the user distribution.
- Terminal: The assigned terminal. Atoll uses the assigned service and activity status to determine the terminal
and the user profile.
- Mobility: The mobility type assigned during the first random trial during the generation of the user distribution.
- Activity Status: The assigned activity status. It can be DL, UL, or DL+UL.
- Connection Status: The connection status indicates whether the user is connected or rejected at the end of
the simulation. If connected, the connection status corresponds to the activity status. If rejected, the rejection
cause is given.
- Clutter Class: The code of the clutter class where the user is located.
- Subscriber ID: The ID of the user if the user is generated from a subscriber list and not from a traffic map.
- Subscriber List: The subscriber list of the user if the user is generated from a subscriber list and not from a
traffic map.
- Indoor: This field indicates whether indoor losses have been added or not.
- Serving Base Station: The serving transmitter of the subscriber.
- Reference Cell: The reference cell of the serving transmitter of the subscriber.
- Azimuth: The orientation of the user’s 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 user’s 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.
- Total Path Loss (dB): The path loss calculated for the user.
- Received Reference Signal Power (DL) (dBm): The reference signal level received at the user location in
the downlink.
- Received SCH/PBCH Power (DL) (dBm): The SCH/PBCH signal level received at the user location in the
downlink.
- Received PDSCH/PDCCH Power (DL) (dBm): The PDSCH/PDCCH signal level received at the user location
in the downlink.
- SCH/PBCH Total Noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the user
location in the downlink on the SCH and PBCH.
- PDSCH/PDCCH Total Noise (I+N) (DL) (dBm): The sum of the interference and noise experienced at the
user location in the downlink on the PDSCH and PDCCH.
- Reference Signal C/(I+N) (DL) (dB): The reference signal C/(I+N) at the user location in the downlink.
- SCH/PBCH C/(I+N) (DL) (dB): The SCH/PBCH C/(I+N) at the user location in the downlink.
- PDSCH/PDCCH C/(I+N) (DL) (dB): The PDSCH/PDCCH C/(I+N) at the user location in the downlink.
- Bearer (DL): The highest LTE bearer available for the PDSCH/PDCCH C/(I+N) level at the user location in
the downlink.
- BLER (DL): The Block Error Rate read from the user terminal’s LTE equipment for the PDSCH/PDCCH C/
(I+N) level at the user location in the downlink.
- Diversity Mode (DL): The diversity mode supported by the cell or permutation zone in downlink.
- Peak RLC Channel Throughput (DL) (kbps): The maximum RLC channel throughput attainable using the
highest bearer available at the user location in the downlink.
- 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 Channel Throughput (DL) (kbps): The application 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 User Throughput (DL) (kbps): The application 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.
- Received PUSCH/PUCCH Power (UL) (dBm): The PUSCH/PUCCH signal level received at the serving
transmitter from the user terminal in the uplink.
- PUSCH/PUCCH Total Noise (I+N) (UL) (dBm): The sum of the interference and noise experienced at the
serving transmitter of the user in the uplink on the PUSCH.
- PUSCH/PUCCH C/(I+N) (UL) (dB): The PUSCH/PUCCH C/(I+N) at the serving transmitter of the user in the
uplink.
- Bearer (UL): The highest LTE bearer available for the PUSCH/PUCCH C/(I+N) level at the serving transmitter
of the user in the uplink.
- BLER (UL): The Block Error Rate read from the reference cell’s LTE equipment for the PUSCH/PUCCH C/
(I+N) level at the serving transmitter of the user in the uplink.
- Diversity Mode (UL): The diversity mode supported by the cell or permutation zone in uplink.
- Transmission Power (UL) (dBm): The transmission power of the user terminal after power control in the
uplink.
- Allocated Bandwidth (UL) (No. of Frequency Blocks): The number of frequency blocks allocated to the
user in the uplink by the eNode-B.
- Peak RLC Channel Throughput (UL) (kbps): The maximum RLC channel throughput attainable using the
highest bearer available at the user location in the uplink.
- Effective RLC Channel Throughput (UL) (kbps): The effective RLC channel throughput attainable using the
highest bearer available at the user location in the uplink. It is calculated from the peak RLC throughput and
the BLER.
- Application Channel Throughput (UL) (kbps): The application throughput is the net throughput without
coding (redundancy, overhead, addressing, etc.). It is calculated from the effective RLC throughput, the
throughput scaling factor of the service and the throughput offset.
- Peak RLC Allocated Bandwidth Throughput (UL) (kbps): The maximum RLC throughput attainable for the
number of frequency blocks allocated to the user using the highest bearer available at the user location in the
uplink.
- Effective RLC Allocated Bandwidth Throughput (UL) (kbps): The effective RLC throughput attainable for
the number of frequency blocks allocated to the user using the highest bearer available at the user location in
the uplink. It is calculated from the peak RLC throughput and the BLER.
- Application Allocated Bandwidth Throughput (UL) (kbps): The application throughput is the net
throughput without coding (redundancy, overhead, addressing, etc.). It is calculated from the effective RLC
throughput, the throughput scaling factor of the service and the throughput offset.
- Peak RLC User Throughput (UL) (kbps): The maximum RLC user throughput attainable using the highest
bearer available at the user location in the uplink.
- Effective RLC User Throughput (UL) (kbps): The effective RLC user throughput attainable using the highest
bearer available at the user location in the uplink. It is calculated from the peak RLC throughput and the BLER.
- Application User Throughput (UL) (kbps): The application throughput is the net throughput without coding
(redundancy, overhead, addressing, etc.). It is calculated from the effective RLC throughput, the throughput
scaling factor of the service and the throughput offset.
Notes:
• In Atoll, channel throughputs are peak RLC, effective RLC, or application 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:
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:
- 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 User Throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink in all the cells of the site.
- Peak 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 User Throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink in all the cells of the site.
- Peak 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 User Throughput (DL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the downlink in all the cells of the site.
- Peak 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 User Throughput (UL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the uplink in all the cells of the site.
- No Service: The number of users unable to connect to any cell of the site for which the rejection cause was
"No Service."
- Scheduler Saturation: The number of users unable to connect to any cell of the site for which the rejection
cause was "Scheduler Saturation."
- Resource Saturation: The number of users unable to connect to any cell of the site for which the rejection
cause was "Resource Saturation."
The Cells (Average) tab: The Cells (Average) tab contains the following average information, per site and trans-
mitter:
- Traffic Load (DL) (%): The traffic loads of the cells calculated on the downlink during the simulation.
- Traffic Load (UL) (%): The traffic loads of the cells calculated on the uplink during the simulation.
- UL Noise Rise (dB): The noise rise of the cells calculated on the uplink during the simulation.
- MU-MIMO Gain (UL): The uplink capacity gain due to multi-user (collaborative) MIMO.
- Peak RLC User Throughput (DL) (kbps): The sum of peak RLC user throughputs of all the users connected
in the downlink.
- Effective RLC User Throughput (DL) (kbps): The sum of effective RLC user throughputs of all the users
connected in the downlink.
- Application User Throughput (DL) (kbps): The sum of application throughputs of all the users connected in
the downlink.
- Peak RLC User Throughput (UL) (kbps): The sum of peak RLC user throughputs of all the users connected
in the uplink.
- Effective RLC User Throughput (UL) (kbps): The sum of effective RLC user throughputs of all the users
connected in the uplink.
- Application User Throughput (UL) (kbps): The sum of application throughputs of all the users connected in
the uplink.
- Peak 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.
- 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.
- Application User Throughput (DL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the downlink.
- 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.
- 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.
- Application User Throughput (UL) (kbps) For Each Service: For each service, the sum of application
throughputs of the users connected in the uplink.
- No Service: The number of users unable to connect to the cell for which the rejection cause was "No Service."
- Scheduler Saturation: The number of users unable to connect to the cell for which the rejection cause was
"Scheduler Saturation."
- Resource Saturation: The number of users unable to connect to the cell for which the rejection cause was
"Resource Saturation."
The Initial Conditions tab: The Initial Conditions tab contains the following information:
Note: If you are importing more than one file, you can select contiguous files by clicking the first
file you want to import, pressing SHIFT and clicking the last file you want to import. You
can select non-contiguous files by pressing CTRL and clicking each file you want to
import.
Note: Files with the extension PLN, as well as some FMT files (created with previous versions of
TEMS) are imported directly into Atoll; you will not be asked to define the data structure
using the Import of Measurement Files dialogue.
6. If you already have an import configuration defining the data structure of the imported file or files, you can select
it from the Configuration list on the Setup tab of the Import of Measurement Files dialogue. If you do not have
an import configuration, continue with step 7.
a. Under Configuration, select an import configuration from the Configuration list.
b. Continue with step 10.
Notes:
• When importing a test mobile data path file, existing configurations are available in the Files
of type list of the Open dialogue, sorted according to their date of creation. After you have
selected a file and clicked Open, Atoll automatically proposes a configuration, if it recognises
the extension. In case several configurations are associated with an extension, Atoll chooses
the first configuration in the list.
• The defined configurations are stored, by default, in the file "NumMeasINIFile.ini", located in
the directory where Atoll is installed. For more information on the NumMeasINIFile.ini file, see
the Administrator Manual.
7. Click the General tab. On the General tab, you can set the following parameters:
- Name: By default, Atoll names the new test mobile data path after the imported file. You can change this
name if desired.
- Under Receiver, set the Height of the receiver antenna and the Gain and Losses.
- Under Measurement Conditions,
- Units: Select the measurement units used.
- Coordinates: By default, Atoll imports the coordinates using the display system of the Atoll document.
If the coordinates used in the file you are importing are different than the coordinates used in the Atoll
document, you must click the Browse button ( ) and select the coordinate system used in the test
mobile data file. Atoll will then convert the data imported to the coordinate system used in the Atoll docu-
ment.
8. Click the Setup tab (see Figure 14.60).
Figure 14.60: The Setup tab of the Import of Measurement Files dialogue
a. Under File, enter the number of the 1st Measurement Row, select the data Separator, and select the Dec-
imal Symbol used in the file.
b. Click Setup to link file columns and internal Atoll fields. The Test Mobile Data Configuration dialogue ap-
pears.
c. Select the columns in the imported file that give the X-Coordinates and the Y-Coordinates of each point in
the test mobile data file.
Note: You can also identify the columns containing the XY coordinates of each point in the test
mobile data file by selecting them from the Field row of the table on the Setup tab.
d. In the Physical Cell ID Identifier box, enter a string that must be found in the column name identifying the
physical cell IDs of scanned cells. For example, if the string "ID" is found in the column names identifying the
physical cell IDs of scanned cells, enter it here. Atoll will then search for the column with this string in the col-
umn name.
e. Click OK.
Important: If you have correctly entered the information under File on the Setup tab, and the
necessary values in the Test Mobile Data Configuration dialogue, Atoll should
recognize all columns in the imported file. If not, you can click the name of the column in
the table in the Field row and select the column name. For each field, you must ensure
that each column has the correct data type in order for the data to be correctly interpreted.
The default value under Type is "<Ignore>". Columns marked with "<Ignore>" will not be
imported.
9. If you wish to save the definition of the data structure so that you can use it again, you can save it as an import
configuration:
a. On the Setup tab, under Configuration, click Save. The Configuration dialogue appears.
b. By default, Atoll saves the configuration in a file called "NumMeasINIfile.ini" found in Atoll’s installation folder.
In case you cannot write into that folder, you can click Browse to choose a different location.
c. Enter a Configuration Name and an Extension of the files that this import configuration will describe (for ex-
ample, "*.txt").
d. Click OK.
Atoll will now select this import configuration automatically every time you import a test mobile data path file
with the selected extension. If you import a file with the same structure but a different extension, you can select
this import configuration from the Configuration list.
Notes:
• You do not have to complete the import procedure to save the import configuration and have
it available for future use.
• When importing a CW measurement file, you can expand the NumMeasINIfile.ini file by clicking
the button ( ) in front of the file in the Setup part to display all the available import configura-
tions. When selecting the appropriate configuration, the associations are automatically made
in the table at the bottom of the dialogue.
• You can delete an existing import configuration by selecting the import configuration under
Setup and clicking the Delete button.
10. Click Import, if you are only importing a single file, or Import All, if you are importing more than one file. The test
mobile data are imported into the current Atoll document.
Notes:
• Fast Display forces Atoll to use the lightest symbol to display the points. This is useful when
you have a very large number of points.
• You can not use Multiple Shadings if the Fast Display check box has been selected.
• You can sort test mobile data paths in alphabetical order on the Data tab of the Explorer window
by right-clicking the Test Mobile Data Path folder and selecting Sort Alphabetically from the
context menu.
• You can export the display settings of a test mobile data path in a configuration file to make them
available for future use. You can export the display settings or import display settings by clicking
the Actions button on the Display tab of the test mobile data path’s Properties dialogue and
selecting Export or Import from the menu.
Note: You can permanently delete the points located in the clutter classes whose check boxes
you clear by selecting the Delete points outside the filter check box.
b. Underneath the name of each column, enter the criteria on which the column will be filtered as explained in
the following table:
9. Click OK to filter the data according to the criteria you have defined.
Filters are combined first horizontally, then vertically. For more information on filters, see "Advanced Data Filtering"
on page 71.
Note: The Refresh Geo Data option available in the context menu of test mobile data paths
enables you to update heights (Alt DTM, Clutter height, DTM+Clutter) and the clutter class
of test mobile data points after adding new geographic maps or modifying existing ones.
7. When you have finished setting the parameters for the coverage prediction, click OK.
You can create a new coverage prediction by repeating the procedure from step 1. to step 7. for each new cover-
age prediction.
8. When you have finished creating new coverage predictions for these test mobile data, right-click the test mobile
data. The context menu appears.
9. Select Calculations > Calculate All the Studies from the context menu.
A new column for each coverage prediction is added in the table for the test mobile data. The column contains the
predicted values of the selected parameters for the transmitter. The propagation model used is the one assigned
to the transmitter for the main matrix (for information on the propagation model, see Chapter 5: Managing Calcu-
lations in Atoll).
You can display the information in these new columns in the Test Mobile Data window. For more information on
the Test Mobile Data window, see "Analysing Data Variations Along the Path" on page 1099.
5. Click the Display button at the top of the Test Mobile Data window. The Display Parameters dialogue appears
(see Figure 14.63).
Note: You can change the display status or the colour of more than one field at the same time
by selecting several fields. You can select contiguous fields by clicking the first field,
pressing SHIFT and clicking the last field. You can select non-contiguous fields by
pressing CTRL and clicking each field. You can then change the display status or the
colour by right-clicking on the selected fields and selecting the choice from the context
menu.
The selected fields are displayed in the Test Mobile Data window.
7. You can display the data in the test mobile path in the following ways:
- Click the values in the Test Mobile Data window.
- Click the points on the test mobile path in the map window.
The test mobile data path appears in the map window as an arrow pointing towards the best server (see
Figure 14.62 on page 1099) in the same colour as the transmitter.
8. You can display a secondary Y-axis on the right side of the window in order to display the values of a variable with
different orders of magnitude than the ones selected in the Display Parameters dialogue. You select the value to
be displayed from the right-hand list at the top of the Test Mobile Data window. The values are displayed in the
colour defined in the Display Parameters dialogue.
9. You can change the zoom level of the Test Mobile Data window display in the Test Mobile Data window in the
following ways:
- Zoom in or out:
i. Right-click the Test Mobile Data window.
ii. Select Zoom In or Zoom Out from the context menu.
- Select the data to zoom in on:
i. Right-click the Test Mobile Data window on one end of the range of data you want to zoom in on.
ii. Select First Zoom Point from the context menu.
iii. Right-click the Test Mobile Data window on the other end of the range of data you want to zoom in on.
iv. Select Last Zoom Point from the context menu. The Test Mobile Data window zooms in on the data be-
tween the first zoom point and the last zoom point.
10. Click the data in the Test Mobile Data window to display the selected point in the map window. Atoll will recentre
the map window on the selected point if it is not presently visible.
Tip: If you open the table for the test mobile data you are displaying in the Test Mobile Data
window, Atoll will automatically display in the table the data for the point that is displayed
in the map and in the Test Mobile Data window (see Figure 14.62 on page 1099).
a. Select Print from the context menu. The Print dialogue appears.
b. Click OK to print the contents of the Test Mobile Data window.
Note: The relationship between the frequency band (spectrum), the channel width, and the
channel numbers can be defined as:
Frequency Band Width = Channel Bandwidth x (Last Channel + 1 - First Channel)
So, if you have a frequency band of 15 MHz, and you are deploying your network with
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 (MHz): 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 Frequency Blocks (RB): Enter the number of frequency blocks (i.e., the number of resource block
widths in the frequency domain) 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.
• 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, for safety
against fast fading, when performing power control in uplink.
Figure 14.64 and Figure 14.65 give examples of downlink and uplink FDD resource blocks for the single antenna case
using the normal cyclic prefix.
- Frame Structure: In this section (see Figure 14.66), you can modify the Default Cyclic Prefix, the PDCCH
Overhead, the PUCCH Overhead, and, for TDD networks, the Switching Point Periodicity.
- Uplink Power Control: In this section, you can enter the uplink power control Margin.
5. Click OK. The global parameters are used during coverage predictions and simulations for the entire network.
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:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
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 50. 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 equipment.
- Name: Enter a name for the bearer, for example, "16QAM 3/4." This name will appear in other dialogues and
results.
- Modulation: Select a modulation from the list of available modulation types. This column is for information
and display purposes only.
- Coding Rate: Enter the coding rate used by the bearer. This column is for information and display purposes
only.
- Bearer Efficiency (bits/symbol): Enter the number of useful bits that the bearer can carry in a symbol. This
information is used in throughput calculations.
For information on the relation between bearer efficiency and spectral efficiency, see "Relation Between Bear-
er Efficiency And Spectral Efficiency" on page 1112.
- Bearer Selection Thresholds: In this tab (see Figure 14.67), 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 1103 and "Modelling Mobility Types" on page 1038,
respectively.
i. Click the Best Bearer Thresholds button. The C/(I+N) Thresholds (dB) dialogue appears (see
Figure 14.68).
ii. Enter the graph values.
iii. Click OK.
For more information on the default values of the bearer selection thresholds, see "Bearer Selection Thresh-
olds" on page 1112. For converting receiver equipment sensitivity values (dBm) into bearer selection thresh-
olds, see "Calculating Bearer Selection Thresholds From Receiver Sensitivity Values" on page 1112.
Note: Subscriber lists use the mobility type "Fixed", i.e., 0 km/hr, in calculations. Make sure that
you have bearer selection thresholds defined for this mobility type in the LTE equipment
properties if you are working with subscriber lists.
- Quality Graphs: On this tab (see Figure 14.69), 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 1103, "Defining LTE Quality Indicators" on page 1104, and "Modelling Mobility
Types" on page 1038, respectively.
i. Click the Quality Graph button. The Quality Graph dialogue appears (see Figure 14.70).
ii. Enter the graph values.
iii. Click OK.
- MIMO: On this tab (see Figure 14.71), you can modify the SU-MIMO and diversity gains for different bearers,
mobility types, BLER values, and numbers of transmission and reception antenna ports. The capacity gain
due to spatial multiplexing is the increase in channel capacity compared to a SISO system. For more informa-
tion on bearers and mobility types, see "Defining LTE Radio Bearers" on page 1103 and "Modelling Mobility
Types" on page 1038, respectively.
For more information on the different MIMO systems, see "Multiple Input Multiple Output Systems" on
page 1108.
TX RX
Note: No MIMO gain (diversity, SU-MIMO, and MU-MIMO) is applied if N Ant = N Ant = 1 .
i. Enter the Diversity Gain for a combination of Mobility, Radio Bearer Index, Max BLER, Number of
Transmission Antenna Ports, and Number of Reception Antenna Ports.
ii. Click the Max MIMO Gain Graphs button to open the Max MIMO Gain dialogue for a combination of Mo-
bility, Radio Bearer Index, Max BLER, Number of Transmission Antenna Ports, and Number of Re-
ception Antenna Ports (see Figure 14.72).
iii. Enter the graph values.
iv. Click OK.
You can define the diversity and SU-MIMO gains for a specific combination of mobility type, bearer, and BLER, as
well as the default gains for "All" mobility types, "All" bearers, and a Max BLER of 1. During calculations, Atoll uses
the gains defined for a specific combination if available, otherwise it uses the default gains.
6. Click OK. The Properties dialogue closes. The settings are stored.
7. Click the Close button ( ) to close the LTE Equipment table.
3. Resource allocation for supporting the Max Throughput Demands: Once the resources have been allocated
for supporting the minimum throughput demands in the previous step, the remaining resources can be allocated
in different ways to support the maximum throughput demands of the users.
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 PDSCH/PDCCH C/(I+N). This means that
users who are under good radio conditions, high PDSCH/PDCCH 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:
1. Click the Data tab of the Explorer window.
2. Right-click the Transmitters folder. The context menu appears.
3. Select Network Settings > Schedulers from the context menu. The Schedulers table appears.
4. In the table, enter one scheduler per row. For information on working with data tables, see "Working with Data
Tables" on page 50. For each scheduler, enter:
- Name: Enter a name for the scheduler. This name will appear in the cell properties.
- Scheduling Method: Select the scheduling method used by the scheduler for allocating resources to support
the maximum throughput demands.
- 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.
Transmit or receive diversity uses more than one transmission or reception antenna to send or receive more than one copy
of the same signal. The signals are constructively combined (using optimum selection or maximum ratio combining) at the
receiver to extract the useful signal. As the receiver gets more than one copy of the useful signal, the signal level at the
receiver after combination of all the copies is more resistant to interference than a single signal would be. Therefore, diver-
sity improves the C/(I+N) at the receiver. It is often used for the regions of a cell that have bad C/(I+N) conditions.
In Atoll, you can set whether a cell supports transmit or receive diversity by selecting the corresponding diversity support
modes in cell properties (see "Cell Description" on page 1006). Diversity gains on downlink and uplink can be defined in
the LTE equipment for different numbers of transmission and reception antenna ports, mobility types, bearers, and maxi-
mum BLER. For more information on uplink and downlink diversity gains, see "Defining LTE Equipment" on page 1104.
Additional gain values can be defined per clutter class. For information on setting the additional uplink and downlink diver-
sity gain for each clutter class or for all clutter classes, see "Defining Clutter Class Properties" on page 115.
During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell
that supports transmit or receive diversity, will benefit from the downlink or uplink diversity C/(I+N) gains.
SU-MIMO uses more than one transmission antenna to send different signals (data streams) on each antenna. The
receiver can also have more than one antenna for receiving different signals. Using spatial multiplexing with M transmis-
sion and N reception antenna ports, the throughput over the transmitter-receiver link can be theoretically increased M or
N times, depending on which is smaller, M or N. SU-MIMO improves the throughput (channel capacity) for a given C/(I+N),
and is used for the regions of a cell that have sufficient C/(I+N) conditions. SU-MIMO (single-user MIMO) is also referred
to as SM (spatial multiplxing) or simply MIMO.
In Atoll, you can set whether a cell supports SU-MIMO by selecting the corresponding diversity support mode in cell prop-
erties (see "Cell Description" on page 1006). SU-MIMO capacity gains can be defined in the LTE equipment for different
numbers of transmission and reception antenna ports, mobility types, bearers, and maximum BLER. For more information
on SU-MIMO gains, see "Defining LTE Equipment" on page 1104.
During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell
that supports SU-MIMO, will benefit from the SU-MIMO gain in its throughput depending on its PDSCH/PDCCH C/(I+N).
As SU-MIMO improves the channel capacity or throughputs, the PDSCH/PDCCH C/(I+N) of a user is first determined.
Once the PDSCH/PDCCH C/(I+N) is known, Atoll calculates the user throughput based on the bearer available at the user
location. The obtained user throughput is then increased according to the SU-MIMO capacity gain and the SU-MIMO Gain
Factor of the user’s clutter class. The capacity gains defined in Max SU-MIMO Gain graphs are the maximum theoretical
capacity gains using SU-MIMO. SU-MIMO requires rich multipath environment, without which the gain is reduced. In the
worst case, there is no gain. Therefore, it is possible to define an SU-MIMO Gain Factor per clutter class whose value
can vary from 0 to 1 (0 = no gain, 1 = 100 % gain). For information on setting the SU-MIMO Gain Factor for each clutter
class or for all clutter classes, see "Defining Clutter Class Properties" on page 115.
The SU-MIMO capacity gain vs. C/(I+N) graphs available in Atoll by default have been generated based on the maximum
theoretical SU-MIMO capacity gains obtained using the following equations:
CC MIMO
G MIMO = ---------------------
-
CC SISO
TX RX ⎛ C ⁄ (I + N) ⎞
Where CC MIMO = Min ( N Ant, N Ant ) × Log 2 ⎜ 1 + ------------------------------------------⎟ is the channel capacity at a given C/(I+N) for a MIMO
TX RX
⎝ Min ( N Ant, N Ant )⎠
TX RX
system using N Ant transmission and N Ant reception antenna ports. CC SISO = Log 2 ( 1 + C ⁄ ( I + N ) ) is the channel
capacity for a single antenna system at a given C/(I+N). C/(I+N) is used as a ratio (not dB) in these formulas. You can
replace the default SU-MIMO capacity gain graphs with graphs extracted from simulated or measured values.
This is a technique for switching from SU-MIMO to transmit or receive diversity as the reference signal conditions get
worse than a given threshold. AMS can be used in cells to provide SU-MIMO gains to users that have better reference
signal C/N conditions than a given AMS threshold, and diversity gains to users that have worse reference signal C/N condi-
tions than the threshold. AMS provides the optimum solution using transmit and receive diversity and SU-MIMO features
to their best.
During calculations in Atoll, a user (pixel, mobile, or subscriber) using a MIMO-capable terminal, and connected to a cell
that supports AMS, will benefit from the gain to be applied, diversity or SU-MIMO, depending on the user’s reference signal
C/N and the AMS threshold defined in the cell properties. Diversity gain is applied to the user’s PDSCH/PDCCH C/(I+N)
if the user’s reference signal C/N is less than the AMS threshold, and SU-MIMO is used if the reference signal C/N is higher
than the AMS threshold.
MU-MIMO (Multi-User MIMO) or Collaborative MIMO is a technique for spatially multiplexing more than one user who have
good enough radio conditions at their locations. This technique is used in uplink so that a cell with more than one reception
antenna port can receive uplink transmissions from two different users over the same frequency-time allocation. This tech-
nique provides considerable capacity gains in uplink, and can be used with single-antenna user equipment, i.e., it does
not require more than one antenna port at the user equipment as opposed to SU-MIMO, which only provides considerable
gains with more than one antenna at the user equipment.
In Atoll, you can set whether a cell supports MU-MIMO in uplink by selecting the corresponding diversity support mode in
cell properties (see "Cell Description" on page 1006). MU-MIMO capacity gains result from the scheduling and RRM proc-
ess. Using MU-MIMO, schedulers are able to allocate resources over two spatially multiplexed parallel frames in the same
frequency-time resource allocation plane. MU-MIMO can only work under good radio conditions and if the cell has more
than one reception antenna port. Therefore, the reference signal C/N must be higher than the MU-MIMO threshold defined
by cell in order for the scheduler to be able to multiplex users in uplink.
During the calculations of Monte Carlo simulations in Atoll, each new user connected to the first antenna port creates
virtual resources available on the second antenna port. These virtual resources can then be allocated to a second user
connected to the second antenna port without increasing the overall load of the cell. In this way, each new mobile
consumes the virtual resources made available be the previous mobile, and may make new virtual resources available on
the other antenna port. The MU-MIMO gain resulting from this uplink collaborative multiplexing is simply the ratio of the
traffic loads of all the mobiles connected to both parallel frames in uplink to the uplink traffic load of the cell. MU-MIMO is
only possible for mobiles that support MIMO and at which the reference signal C/N is greater than the MU-MIMO threshold
defined for their serving cell. The MU-MIMO gain can be defined per cell by the user or it can be an output of the Monte
Carlo simulations. This gain is used during the calculation of uplink throughput coverage predictions. The channel through-
put is multiplied by this gain for pixels where MU-MIMO is used as the diversity mode.
Important: This procedure is only recommended if you have a correct subscriber list and have
complete knowledge of the services they use.
Atoll generates a realistic user distribution containing active users only during Monte Carlo simulations. The status of
these users is determined through the user’s service usage parameters defined in the user profile. In Atoll, all the subscrib-
ers have a user profile assigned to them. During Monte Carlo simulations based on subscriber lists, Atoll determines
active users from all the users in the subscriber list. If you perform calculations on subscriber lists, Atoll calculates the
channel throughputs and not the user throughputs as resource allocation is not performed in these calculations. However
in the simulations, RRM and resource allocation is carried out user throughputs can be determined.
If you want to determine user level throughputs for all the subscribers in a subscriber list, you can run a simulation on this
subscriber list after modifying the user profiles assigned to all the subscribers such that all the subscribers have an activity
probability of 100 %.
1. Create a subscriber list with subscribers having an activity probability of 100 %:
a. Create as many user profiles as there are services used by the subscribers in the list.
b. Assign only one service to each user profile.
c. Assign the following service usage parameters to the user profiles that you create:
i. For Voice services, set:
- Calls/Hour = 1.
- Duration (sec.) = 3600.
ii. For Data services:
- Calls/Hour = 1.
- UL Volume (KBytes) = UL Average Throughput x 3600 / 8.
- DL Volume (KBytes) = DL Average Throughput x 3600 / 8.
Where the UL Average Throughput and the DL Average Throughput are the uplink and downlink average
requested throughputs, respectively, of the service mentioned in the user profile.
If you do not currently have reliable LTE multi-service traffic, you can provide Atoll with user density information per serv-
ice, for example, traffic data from adapted GSM Erlang maps. In this case, you do not have to create user profiles. As well,
Atoll does not have to determine the user activity probabilities to create traffic scenarios during simulations. The distribu-
tion of traffic during simulations will only depend on the user densities per service.
If you know the user densities for each service, you can set user activity probabilities to 100 % in your LTE document, as
shown below:
1. For Voice services, set:
- Calls/Hour = 1.
- Duration (sec.) = 3600.
2. For Data services:
- Calls/Hour = 1.
- UL Volume (KBytes) = UL Average Throughput x 3600 / 8.
- DL Volume (KBytes) = DL Average Throughput x 3600 / 8.
Where the UL Average Throughput and the DL Average Throughput are the uplink and downlink average re-
quested throughputs, respectively, of the service defined in the user profile.
The above settings will set the user activity probabilities to 100 %. If you create a traffic map based on environment
classes, the user density values that you define in your environment classes will be the actual user densities. This means
that, for X users/km² defined in the environment class for a given user profile, the Monte Carlo simulator will generate
exactly X users/km² for each service of the user profile.
In this way, you can know the exact number of active users and their services generated during the simulations before-
hand.
This procedure should only be used when appropriate traffic data is not available.
You can define a maximum coverage range for all the transmitters in your network by entering a valid range as the Max
Range parameter.
To define the Max Range parameter:
1. Right-click the Predictions folder. The context menu appears.
2. Select Properties from the context menu. The Predictions folder’s 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:
The default values of the bearer selection thresholds, the BLER quality graphs, and the bearer efficiency values in Atoll
have been extracted from the 3GPP TS 36.942 V8.0.0 (see Figure 14.74). These values correspond to to an ideal (AWGN)
radio channel, and are too optimistic compared to real radio channels. It is recommended to use more realistic values when
available.
The spectral efficiency is the number of useful data bits that can be transmitted using any modulation and coding scheme
per Hz, the transition points between any two modulation and coding schemes give the default bearer selection thresholds
in Atoll, and the normalised values from the slopes of the graphs, that represent the reduction in the spectral efficiency,
give the block error rate.
You can replace the bearer selection threshold values provided by default with other values, such as selection thresholds
for 10 % BLER:
Bearer 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Selection
-6.8 -4.4 -4 -2 0 1.6 5.6 8 10.4 11 11.4 12 13.2 15.6 16.2
Threshold
You can convert the receiver sensitivity values, that are listed in the specifications of your equipment, into bearer selection
thresholds using the following conversion method:
SF × NUsed
CNR = RS + 114 – NF – 10 × Log ⎛ ------------------------------⎞
⎝ N Total ⎠
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 frequency blocks, N Total is the total number of
subcarriers, i.e., the FFT size.
In the above explanation, the term receiver refers to the base station in uplink and to the mobile/user equipment in the
downlink.
Spectral efficiency of a modulation and coding scheme is defined as the number of useful bits that can be transmitted each
second over a channel of 1 Hz bandwidth. Spectral efficiency is hence given in terms of bps/Hz.
In Atoll, the efficiency of bearers (modulation and coding schemes) are defined in the Bearers table. The bearer efficiency
is given in terms of bits/symbol. Remember that in Atoll a symbol refers to one resource element, which is 1 symbol dura-
tion long and 1 subcarrier width wide, as shown in Figure 14.75.
The concept of bearer efficiency is similar to spectral efficiency. The only difference is in the units used to define the two
entities. Here is a simple example that compares spectral efficiency and bearer efficiency, and shows that the two are the
same.
Spectral efficiency is given by:
Where BLER is the Block Error Rate, r is the coding rate for the bearer, and M is the number of modulation states. For
simplification, we set BLER = 0, and use QPSK1/2, i.e., four modulation states and r = 0.5. With these values, we get a
spectral efficiency of 1 bps/Hz for QPSK1/2. In other words, a communication channel using QPSK1/2 modulation and
coding scheme can send 1 bps of useful data per unit bandwidth.
In order to compare the bearer efficiency and spectral efficiency of QPSK1/2, let’s say that QPSK1/2 has a bearer effi-
ciency of 1 bits/symbol. Here as well, the number of bits refers to useful data bits. The width of a subcarrier in LTE is
1
ΔF = 15 kHz , from which we can calculate the useful symbol duration as well: T U = ------- = 66.67 μ sec . In one second,
ΔF
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 subcar-
rier 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 equivalent quantities, we have ignored some system parameters, such as the cyclic prefix, and have
considered that the entire frame is transmitted in one direction, uplink or downlink.
VoIP codecs are application-layer elements in the OSI system model. Atoll models application throughputs using a
throughput offset and a scaling factor with respect to the RLC layer throughputs. You can model different VoIP codecs by
creating a new service for each VoIP codec, and setting the target throughput to the Application Throughput for the
scheduler used. Here are two examples of the most common VoIP codecs, and how they can be modelled in Atoll:
• G.711 VoIP Codec
The actual voice data rate needed by the G.711 codec is 64 kbps, but with the lower layer headers and other
added bits, the needed RLC data rate could be between 66.4 and 107.2 kbps. In this example, we show how to
model the codec with header bits that lead to 85.6 kbps RLC data rate.
a. Create a new service with the following parameters:
- Name: VoIP (G.711)
- Type: Voice
- Min Throughput Demand (DL) and Min Throughput Demand (UL): 64 kbps
- Max Throughput Demand (DL) and Max Throughput Demand (UL): 64 kbps
- Average Requested Throughput (DL) and Average Requested Throughput (UL): 64 kbps
- Scaling Factor: 74.77 %
- Offset: 0 kbps
b. Set the Target Throughput for Voice Services to "2 - Application Throughput" for the scheduler being used.
In this way, Atoll will allocate resources to the users of this service such that they get 64 kbps application through-
put, and around 85.6 kbps of effective RLC throughput.
In Atoll, carriers are assigned channel numbers in the frequency bands table. These channel numbers do not necessarily
have to be unique, i.e., a channel number can be reused in different bands. The 3GPP defines unique EARFCNs (Evolved
Absolute Radio Frequency Channel Numbers) for all the frequency bands. Each EARFCN has a fixed width of 100 kHz,
whereas channels (or carriers) in Atoll can have different widths.
If you want to work with EARFCNs instead of channel numbers, you can set EARFCNs as channel numbers in the
frequency bands table similar to as shown in the example below:
In Atoll, you can study the effect of interference received by your network from other LTE networks. The interfering LTE
network can be a different part of your own network, or a network belonging to another operator.
To study interference from co-existing networks:
1. Import the interfering network data (sites, transmitters, and cells) in to your document as explained in "Creating a
Group of Base Stations" on page 1014.
2. For the interfering network’s transmitters, set the Transmitter Type to Extra-Network (Interferer Only) as
explained in "Transmitter Description" on page 1004.
During calculations, Atoll will consider the transmitters of type Extra-Network (Interferer Only) when calculating
interference. These transmitters will not serve any pixel, subscriber, or mobile, and will only contribute to interfer-
ence.
Modelling the interference from co-existing networks will be as accurate as the data you have for the interfering network.
If the interfering network is a part of your own network, this information would be readily available. However, if the inter-
fering network belongs to another operator, the information available might not be accurate.
Moreover, for other operators’ networks, and if the interfering networks use OFDM but are not LTE networks, their model-
ling will not be accurate using LTE transmitters and cells. The number of subcarriers used in the interfering networks might
be very different.
• Resources: In Atoll, the term "resource" is used to refer to the average number of resource units, 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.
• Frame: An LTE frame is 10 ms long. The duration of a frame is a system-level constant. Each frame comprises
10 1 ms-long subframes, with each subframe containing 2 0.5 ms-long slots. Each slot can have 7 or 6 symbol
durations for normal or extended cyclic prefix, respectively, and for a 15 kHz subcarrier width. A slot can have 3
symbol durations for extended cyclic prefix used with a 7.5 kHz subcarrier width. LTE includes specific frame struc-
tures for FDD and TDD systems as shown in Figure 14.76. For TDD systems, two switching point periodicities can
be used; half-frame or full frame. Half-frame periodicity provides the same half-frame structure as a TD-SCDMA
subframe. The PBCH and the two SCH are carried by subframes 0 and 5, which means that these 2 subframes
are always used in downlink. A subframe is synonymous with TTI (transmission time interval), i.e., the minimum
unit of resource allocation in the time domain.
Figure 14.76: LTE frame structures (DL: blue, UL: orange, DL or UL: green)
• Resource Element, Symbol, or Modulation Symbol: In Atoll a symbol refers to one resource element or one
modulation symbol, which is 1 symbol duration long and 1 subcarrier width wide, as shown in Figure 14.75.
• Symbol Duration: In Atoll a symbol duration refers to one OFDM symbol, which is the duration of one modulation
symbol over all the subcarriers/frequency blocks being used.
• Subcarrier: An OFDM channel comprises many narrowband carriers called subcarriers. OFDM subcarriers are
orthogonal frequency-domain waveforms generated using fast fourier transforms (see Figure 14.77).
• Frequency Block: It is the minimum unit of resource allocation in the frequency domain, i.e., the width of a
resource block, 180 kHz. It is a system-level constant. A frequency block can either contain 12 subcarriers of
15 kHz each (see Figure 14.77) or 24 subcarriers of 7.5 kHz each.
• Resource Block: It is the minimum unit of resource allocation, i.e., 1 frequency block by 1 slot (see Figure 14.77).
Schedulers are able perform resource allocation every subframe (TTI, transmission time interval), however, the
granularity of resource allocation 1 slot in time, i.e., the duration of a resource block, and 1 frequency block in fre-
quency.
• LTE Logical Channels: LTE logical channels include (see Figure 14.78):
- Broadcast Control Channel (BCCH) (DL): Carries broadcast control information.
- Paging Contol Channel (PCCH) (DL): Carries paging control information.
- Common Control Channel (CCCH) (DL and UL): Carries common control information.
- Dedicated Control Channel (DCCH) (DL and UL): Carries control information dedicated to users.
- Dedicated Traffic Channel (DTCH) (DL and UL): Carries user traffic data.
- Multicast Control Channel (MCCH) (DL): Carries multicast control information.
- Multicast Traffic Channel (MTCH) (DL): Carries multicast traffic data.
• LTE Transport Channels: LTE transport channels include (see Figure 14.78):
- Broadcast Channel (BCH) (DL): Carries broadcast information.
- Paging Channel (PCH) (DL): Carries paging information.
- Downlink Shared Channel (DL-SCH) (DL): Carries common and dedicated control information and user
traffic data. It can also be used to carry broadcast and multicast control information and traffic in addition to
the BCH and MCH.
- Uplink Shared Channel (UL-SCH) (UL): Carries common and dedicated control information and user traffic
data.
- Multicast Channel (MCH) (DL): Carries multicast information.
- Random Access Channel (RACH) (UL): Carries random access requests from users.
• LTE Physical Layer Channels: LTE physical layer channels include (see Figure 14.78):
- Physical Broadcast Channel (PBCH) (DL): Carries broadcast information.
- Physical Downlink Shared Channel (PDSCH) (DL): Carries paging information, common and dedicated
control information, and user traffic data. It can also be used to carry broadcast and multicast control informa-
tion and traffic in addition to the PBCH and PMCH. Parts of this channel carry the primary and secondary syn-
chronisation channels (P-SCH and S-SCH), the downlink reference signals, the physical downlink control
channel (PDCCH), the physical HARQ indicator channel (PHICH), and the physical control format indicator
channel (PCFICH).
- Physical Uplink Shared Channel (PUSCH) (UL): Carries common and dedicated control information and
user traffic data.
- Physical Uplink Control Channel (PUCCH) (UL): Carries control information.
- Physical Multicast Channel (PMCH) (DL): Carries multicast information.
- Physical Random Access Channel (PRACH) (UL): Carries random access requests from users.
Figure 14.78: LTE logical, transport, and physical layer channels (DL: blue, UL: orange, DL or UL: green)
Atoll
RF Planning and Optimisation Software
Chapter 15: Microwave Link Project Management
Note: You must define the coordinate systems for the microwave project before starting the
design and analysis processes.
- Availability objectives (relevant performance parameter, link class, minimum and maximum data rates, etc.)
• Designing network
- Creating microwave links (with assigned antennas, equipment, link class, waveguides and cables, IRF, etc.)
- Creating repeaters
- Creating multi-hop microwave links (groups of microwave links considered as one in terms of engineering)
• Analysing
- Determing the probability of interruption
- Determing the line of sight
- Link budgets
- Interference studies
- Analysing the profile
- Studying reflection
- Meeting performance objectives (quality and availability)
- Diversity
- Parities
Optimisation and analysis are iterative steps. In some cases, the last four steps can be repeated in order to achieve the
optimum solution for the network.
- Pylon Height: You can define the height of the structure on which you can install antennas. Atoll can use
this height in several analyses (site analysis, antenna height optimisation, etc.).
- Support Type: You can describe the nature of site. This field is for information only.
4. Click OK.
Figure 15.1: Setting the calculation parameters for a line of sight report
file except over a specific distance around the sites (clearance), where Atoll bases its calculations only on the
DTM.
8. Click OK. Atoll displays the results in the Line of Sight Report table for each site in the focus zone if available
and computation zone if there is no focus zone (for information on the focus zone, "Setting a Focus Zone" on
page 1142 and for information on the computation zone, see "Setting a Computation Zone" on page 1141). As
well, Atoll displays a terrain section on the map between each pair of sites (see "Displaying the Terrain Profile
Between Microwave Sites" on page 1124).
The Line of Sight Report table contains the following information for each pair of sites. Site1 is the studied site and Site2
a candidate site within the focus zone if available and computation zone if there is no focus zone.
- Site1: Site1 is the transmitting site of the pair of sites.
- Site2: Site2 is the receiving site of the pair of sites.
- Distance (m): The distance between the sites.
- Line of Sight (%): The percentage of clearance or penetration of the Fresnel ellipsoid. The value can be
between -100 and 100%. A value from -100 to 0% corresponds to the percentage of penetration of the upper
half of the Fresnel ellipsoid. A value from 0 to 100% corresponds to the percentage of clearance of the lower
half of the Fresnel ellipsoid.
- Antenna 1 Height (m): The height of the transmitting antenna.
- Antenna 2 Height (m):The height of the receiving antenna.
- Frequency (MHz): The mean frequency used to calculate the line of sight between the transmitting site and
the receiving site.
- Direction (°): The angle from Site1 to Site2 in the horizontal plane.
You can remove the line of sight lines by selecting Delete Line of Sight Lines from the site’s context menu.
To perform a LOS study for all sites:
1. Click the Data tab in the Explorer window.
2. Right-click the Sites folder. The context menu appears.
3. Select Line of Sight Report from the context menu. The Line of Sight Parameters dialogue appears.
4. Click the Calculation Parameters tab.
5. Under Height - Transmitter Side and Height - Receiver Side you can select how pylon height will be defined on
the transmitter and receiver side of the microwave link, respectively. Select one of the following to define the pylon
height for the transmitter and the receiver:
- Use the pylon height defined by site: If you select Use the pylon height defined by site, Atoll will use the
pylon height defined by site for each line of sight.
- Use the default height: If you select Use the default height, Atoll will use the pylon height you define in the
Default Height box.
6. Define the Maximum Distance around the selected site to be considered in the line of sight and the value of the
Earth Curvature Factor k.
7. Under Penetration Condition, define the following parameters:
- Take clutter into account in diffraction: Select the Take clutter into account in diffraction check box if
you want to use clutter information when calculating diffraction in the line of sight.
- Frequency Band: Select the frequency band to be used when calculating the line of sight from the list. The
average frequency of the selected frequency band is displayed in the Frequency box.
8. Click the Clutter tab. On the Clutter tab you can set clutter-related parameters that will be used to calculate the
line of sight. The settings on the Clutter tab are independent from any clutter parameters you might have set for
the propagation model. For each clutter class, you can set the following:
- Receiver Height: You can define a receiver height for each clutter class. It is not used when calculating the
line of sight between sites.
- Clearance: If you want, you can define a clearance around each site for each clutter class. The clearance is
used when calculating diffraction. Both ground altitude and clutter height are considered along the whole pro-
file except over a specific distance around the sites (clearance), where Atoll bases its calculations only on the
DTM.
9. Click OK. Atoll displays the results in the Line of Sight Report table for each site in the focus zone if available
and computation zone if there is no focus zone (for information on the focus zone, "Setting a Focus Zone" on
page 1142 and for information on the computation zone, see "Setting a Computation Zone" on page 1141). As
well, Atoll displays a terrain section on the map between each pair of sites (see "Displaying the Terrain Profile
Between Microwave Sites" on page 1124).
The Line of Sight Report table contains the following information for each pair of sites. Site1 is the studied site and Site2
a candidate site within the focus zone if available and computation zone if there is no focus zone.
- Site1: Site1 is the transmitting site of the pair of sites.
- Site2: Site2 is the receiving site of the pair of sites.
- Distance: The distance between the sites.
- Line of Sight: The percentage of clearance or penetration of the Fresnel ellipsoid. The value can be between
-100 and 100%. A value from -100 to 0% corresponds to the percentage of penetration of the upper half of the
Fresnel ellipsoid. A value from 0 to 100% corresponds to the percentage of clearance of the lower half of the
Fresnel ellipsoid.
- Antenna 1 Height: The height of the transmitting antenna.
- Antenna 2 Height: The height of the receiving antenna.
- Frequency: The mean frequency used to calculate the line of sight between the transmitting site and the
receiving site.
You can remove the line of sight lines by selecting Delete Line of Sight Lines from the context menu of the Sites folder
of the Explorer window’s Data tab.
- Ellipsoid Clearance: Select Ellipsoid Clearance if you want to study the percentage of clearance of the
Fresnel ellipsoid and enter the percentage of clearance of the lower half of the Fresnel ellipsoid.
c. Frequency Band: Select the frequency band to be used when calculating the line of sight from the list. The
average frequency of the selected frequency band is displayed in the Frequency box.
9. Click the Clutter tab. On the Clutter tab you can set clutter-related parameters that will be used to calculate the
line-of-sight area. The settings on the Clutter tab are independent from any clutter parameters you might have set
for the propagation model. For each clutter class, you can set the following:
- Receiver Height: If you want, you can define a receiver height for each clutter class. This is the value that will
be taken into consideration if you selected Use heights defined per clutter class under Height - Receiver
Side on the Calculation Parameters tab.
- Clearance: If you want, you can define a clearance around each site for each clutter class. The clearance is
used when calculating diffraction. Both ground altitude and clutter height are considered along the whole pro-
file except over a specific distance around the sites (clearance), where Atoll bases its calculations only on the
DTM.
10. Click the Display tab. On the Display tab, you can define how the line-of-sight areas will be displayed on the map.
You can select one of the following display options:
- One Area per Site: Select One Area per Site to display a line-of-sight area for each site and then define the
colour the line-of-sight areas will be displayed in:
- Automatic Colour: If you select Automatic Colour, Atoll will automatically assign a different colour to
each line-of-sight area, and you will be able to distinguish the line-of-sight areas for each site.
- Unique Colour: If you select Unique Colour, selecting a colour from the palette, Atoll with display all
line-of-sight areas in the same colour, and the resulting display will show the cumulative line-of-sight
areas.
Set the transparency of the displayed line-of-sight area, by moving the slider.
- Overlapping: Select Overlapping to display the line-of-sight areas with coverage from the defined number
of sites:
- Areas covered by at least 2 sites: Check the Areas covered by at least 2 sites check box if you want
Atoll to display all areas covered by at least 2 sites in the colour selected from the palette.
- Areas covered by at least 3 sites: Check the Areas covered by at least 3 sites check box if you want
Atoll to display all areas covered by at least 3 sites in the colour selected from the palette.
- Areas covered by all sites: Check the Areas covered by all sites check box if you want Atoll to display
all areas covered by all sites in the colour selected from the palette.
11. Select the Add to Legend check box to add the options defined on the Display tab to the Legend. For information
on the Legend window, see "Displaying the Map Legend" on page 41.
12. Click OK. Atoll displays results on the map.
To delete the line of sight areas:
1. Right-click the Sites folder of the Explorer window’s Data tab. The context menu appears.
2. Select Delete Line of Sight Areas from the context menu.
Note: You can set further options using the Line of Sight Parameters dialogue. You can open
the Line of Sight Parameters dialogue by clicking the arrow next to the Height Profile
button ( ) on the toolbar and selecting Properties. For a description of the options
available in the Line of Sight Parameters dialogue, see "Studying LOS Between
Microwave Sites" on page 1121.
4. Move the pointer to another site on the map. When the frame appears around the site, indicating it is selected,
click to create the second analysis point.
5. The profile between both sites appears on the Terrain Section tab of the Profile Analysis window. Atoll displays
the terrain height along the profile as well as clutter classes and clutter heights when the visibility box of the Clutter
Classes folder on the Geo tab is selected. A blue ellipsoid indicates the Fresnel zone between both sites. By
default, Atoll considers the pylon heights defined for the selected sites to determine the profile. You can modify
them as well as the studied frequency in the Terrain Section Properties dialogue. If you do not want to display
the clutter along the profile, you can clear the visibility check box of the Clutter Classes folder on the Geo tab.
6. Right-click the terrain section on the map. The context menu appears.
7. Select Properties. The Terrain Section Properties dialogue appears.
8. In the Terrain Section Properties dialogue, you have the following parameters:
- Id: The terrain section reference number.
- Line of Sight (%): The percentage of clearance/penetration of the Fresnel zone. The value can vary between
-100 and 100%. A value from -100 to 0% corresponds to the percentage of penetration of the upper half of the
Fresnel ellipsoid. A value from 0 to 100% corresponds to the percentage of clearance of the lower half of the
Fresnel ellipsoid.
- Site1: The Site1 name.
- Site2: The Site2 name.
- Distance (m): The distance between Site1 and Site2.
- Pylon 1 Height (m): The pylon height on Site1 to be considered.
- Pylon 2 Height (m): The pylon height on Site2 to be considered.
- Frequency (MHz): The frequency to be considered.
9. Click OK to close the dialogue and apply the parameters.
If you have previously calculated a LOS report on a site or a group of sites (see "Studying LOS Between Microwave Sites"
on page 1121), proceed as follows:
1. On the map, click the terrain section you want to analyse.
- Altitudes Without Curvature: Atoll displays the horizon profile calculated without considering the curvature
of the earth.
- Height of the Selected Site: The height of the selected site is marked by a horizontal line (a blue dotted line
by default).
- Position of the Other Sites: The position of other sites within the view is marked by a red line (by default). If
the site is located in front of the first obstacle, the line is solid; otherwise this is a dotted line.
Note: You can also change these display options by right-clicking the 360° View tab of the
Microwave Link Analysis window and selecting Properties from the context menu.
5. Click OK. The 360° View tab of the Microwave Link Analysis window opens.
6. Atoll displays the horizon profile for the selected site. The terrain height along the horizon profile, as well as clutter
classes and cluter heights are displayed when the visibility check box of the Clutter Classes folder on the Geo
tab is selected. Every x° around the site (value user-defined in the Calculation Parameters dialogue), it considers
a fictitious link and determines the first diffraction obstacle along this link. Note that the curvature of the Earth is
considered in order to find the first diffracting obstacle and its height. Each obstacle is marked by a point. If you
click the point, you can view its position in the map window. Finally, if you place the mouse cursor on the point,
Atoll displays a popup with the following information: the diffraction obstacle coordinates, its distance from the
site, its angle with the site azimuth and its altitude.
7. Click OK.
Analysis and display parameters defined for each site are saved during the Atoll session by clicking OK. You can also
save a set of parameters as default configuration by clicking the Save Configuration button. Therefore, if a site has never
been calculated, the 360° view calculation will be initialized with the default configuration settings. Finally, even if you have
modified some parameters, it is still possible to apply the default configuration again by clicking Load Configuration. The
default configuration is memorized for the current Atoll session only.
You can modify some analysis parameters, such as the aperture, or the site azimuth, directly on the map.
To modify analysis parameters on the map:
1. Right-click the 360° View tab. The context menu appears.
2. Select Modify Sector from the context menu.
3. In the map window, click one extremity of the analysis area and change the the angle. The modifications (the dis-
tance, aperture, and new site azimuth) are displayed on the left side of the status bar.
4. After releasing the mouse, press any key to finalise your change.
5. Press F5 to refresh the displayed horizon profile.
- Model: The antenna model. By default, Atoll lists antennas that operate in the frequency band defined for
the microwave link. If you want, you can apply an additional filter by clicking the button ( ) beside the
antenna model field. When the filter is active, the appearance of the button changes ( ). In this case,
Atoll proposes in the list antennas compatible with the selected equipment as defined in the Antenna/
Equipment Compatibility table.
- Height/Ground: The antenna height with respect to the ground (in metres).
- Polarisation: The polarisation of the antenna to be used. This parameter helps Atoll determine which
antenna pattern diagrams to use for calculations.
- Az./Direct Ray: The azimuth with respect to the direct ray between the both extremities.
- Tilt./Direct Ray: The tilt with respect to the direct ray between the both extremities.
- Diversity Ant: You can define if a diversity antenna is used at either site to improve reception.
- Separation: The distance between the main and the diversity antennas when space diversity is used on
the site.
- Under Equipment, you can define equipment related parameters for the both sites of the link:
- Model: You can select a piece of equipment. By default, Atoll lists equipment that operates in the frequen-
cy band defined for the microwave link. If you want, you can apply an additional filter by clicking the button
( ) beside the antenna model field. When the filter is active, the appearance of the button changes
( ). In this case, Atoll proposes in the list equipment compatible with the selected antenna as defined
in the Antenna/Equipment Compatibility table.
- Maximum Power: The maximum power that the equipment can transmit. This parameter is taken from
the equipment properties.
- Tuning: Define a value different from 0 dB if you do not want to transmit at maximum power.
- Nominal power: The output power after tuning.
- ATPC: The power reserve used to increase the transmitted signal when it rains. This parameter can be
defined for biderectional links only. The value cannot exceed the Max ATPC value defined for the equip-
ment. ATPC value is considered in reliability and interference analysis only if power control is on. For infor-
mation on taking power control into consideration, see "Global Parameters" on page 209.
- Coordinated Power: The output power taken into account in calculations when power control is on.
- XPIC System: Select this option if the microwave link uses XPIC (Cross Polarisation Interference Cancel-
ler).
- Under Frequencies, you can define the following parameters:
- Sub-Band: The frequency sub-band.
- Frequency: The frequency on which the signal is transmitted. This value is used when no sub-band is
defined. By default, it equals the central frequency of the frequency band.
- Half-band: Define which half-band (either the upper or the lower half-band) is assigned to the site.
- Channels: tHe channel(s) allocated to the site. The corresponding frequency is indicated in brackets.
Channel(s) can be selected only after choosing a frequency sub-band.
- Port Settings: Click the Port Settings button to configure channel(s) in detail. The Ports Definition
dialogue appears. You can configure the channels, transmission and reception port numbers, values for
transmission and reception attenuation, the polarisation and the channel port status. The number of ports
you can define depends on the system configuration of the selected equipment and cannot exceed n+m
(where "n" is the number of channels in normal use and "m" is the number of channels available as
standby channels).
For further information on port settings, see "Defining Port Parameters" on page 1131.
microwave link. If you want, you can apply an additional filter by clicking the button ( ) beside the antenna
model field. When the filter is active, the appearance of the button changes ( ). In this case, Atoll proposes
in the list, waveguides compatible with the selected antenna and equipment as defined in the Antenna/
Waveguide Compatibility and Antenna/Equipment Compatibility tables. You can also enter the length of
each waveguide. Atoll displays the attenuation.
- Under Connection Losses, you can define additional losses to be taken into account on transmission, recep-
tion, or on both transmission and reception. You can also add a Shielding Factor.
• The Geoclimatic tab:
- Current Methods: Under Current Methods, you can see the calculation methods used to analyse the micro-
wave link quality and availability. The methods displayed are those set on the Models tab of the Microwave
Radio Links Properties dialogue.
- Atmospheric and Climatic Conditions: Under Atmospheric and Climatic Conditions, you can define the
conditions under which the microwave operates:
- Climatic Zone: Select the climatic zone that best describes the climate in which the microwave link oper-
ates. For dry areas, you can select from Polar (Dry), Polar (Moderate), Cold (Dry), Temperate Continental
(Dry), and Subtropical Arid (Dry). For continental areas, you can select from Cold (Moderate), Temperate
Continental (Moderate). For humid areas, you can select from Temperate Continental (Wet) correspond
to continental areas and Temperate Maritime, Subtropical Wet, Tropical Moderate, and Tropical.
- Temperature: Set the average temperature of the zone in which the microwave link operates. Clicking the
button ( ) beside the Temperature text box opens a dialogue where you can select the temperature
based on Rec. ITU-R P.1510-0, ITU-R P.835-3 (and select a season), or the temperature set in the geocli-
matic file.
- Rec. ITU-R P.530: The parameters found under Rec. ITU-R P.530 are those recommended by ITU-R
P.530 to calculate the availability of the microwave link:
Water Vapour Density: Set the water vapour density in grams per cubic metre. Clicking the button ( )
beside the Water Vapour Density text box opens a dialogue where you can select the water vapour den-
sity based on Rec. ITU-R P.836-3 (and select the percentage of the average year where the defined water
vapour density is exceeded), or based on Rec. ITU-R P.835-3 (and select a season), or the water vapour
density set in the geoclimatic file. The dialogue also displays the water vapour pressure in hectopascals
(hPa) calculated using your data and based on Rec. ITU-R P.836-3.
Rainfall exceeded 0.01% of the average year: Set the rainfall exceeded 0.01% of the average year (or,
in other words, the rainfall observed 99.99% of the average year). Clicking the button ( ) beside the
Rainfall exceeded 0.01% of the average year text box opens a dialogue where you can select the rainfall
exceeded 0.01% of the average year based on Rec. ITU-R P.837-4 or the rainfall exceeded 0.01% of the
average year set in the geoclimatic file.
Atmospheric Pressure: Set the atmospheric pressure in grams per cubic metre. Clicking the button
( ) beside the Atmospheric Pressure text box opens a dialogue where you can select the atmospher-
ic pressure based on Rec. ITU-R P.835-3 (and select a season), or the atmospheric pressure set in the
geoclimatic file.
Relative Humidity: The Relative Humidity displayed is calculated using the defined water vapour den-
sity.
Rec. ITU-R P.530-12: Under ITU-R P.530-12, you can enter the Rain Height (0°C Isotherm) in metres.
The rain height is the height of the top of the rain column above mean sea level from the 0°C isotherm.
Clicking the button ( ) beside the Rain Height text box opens a dialogue where you can select the rain
height based on Rec. ITU-R P.839-3 (and select a season), or the rain height set in the geoclimatic file.
- Refractivity: Under Refractivity, you can define the Refractivity gradient near the earth’s surface in
N-units per km. Clicking the button ( ) beside the Refractivity gradient near the earth’s surface text box
opens a dialogue where you can select the refractivity gradient based on Rec. ITU-R P.453-9, using a user-
defined reference altitude, or the refractivity gradient for less than 65 m., as well as the percentage of the year
that N is not exceeded, or the refractivity gradient set in the geoclimatic file.
Under Refractivity, the k factor median value, calculated using the set parameters, is displayed.
- Geoclimatic Factor: The parameters under Geoclimatic Factor are used to calculate the quality of the
microwave link and are broken down by calculation method. Under Geoclimatic Factor, you can set the fol-
lowing parameters:
- ITU-R P.530-5, -8 and Vigants-Barnett: Under ITU-R P.530-5, -8 and Vigants-Barnett, you can select
the Terrain Type: "Plain Zone" for terrestrial microwave links where the height of the lowest antenna in
the link is lower than 700 m; "Mountain Zone" for terrestrial microwave links where the height of the lowest
antenna in the link is higher than 700 m; "Lake Zone" for microwave links over an expanse of water and
"Link over the water" for microwave links over an extended expanse of water.
This information is taken into account when using ITU-R P.530-5, ITU-R P.530-8 and Vigants-Barnett cal-
culation methods.
- ITU-R P.530-5, -8: Under ITU-R P.530-5, -8, you can define the PL factor. PL is the percent of time the
relative refractivity gradient is less than -100 N⁄Km. The PL factor can be found on the ITU-R maps.
This parameter is taken into account when using ITU-R P.530-5 and ITU-R P.530-8 calculation methods.
- K.Q. Method: Under K.Q. Method, you can define K.Q. for the K.Q method. K models geo-climatic and
terrain effects on climate while Q is the factor for variables other than those dependent on distance and
frequency.
- ITU-R P.530: Under ITU-R P.530, you can define the K factor. K models geo-climatic and terrain effects
on climate. Clicking the button ( ) beside the K text box opens a dialogue where you can select the K
factor based on Rec. ITU-R P. 530-5 or Rec. ITU-R P. 530-8 (and select a terrain type and enter a value
for C0 and for the percentage of time the refractivity gradient (< 100 m.) is less than -100 N-units⁄km for
the worst average month) or based on Rec. ITU-R P. 530-10 and above (and select the simplified method
where you also define the refractivity gradient (< 65 m.) not exceeded during 1% of the average year or
select the method with terrain roughness taken into account where you define the refractivity gradient and
the terrain roughness).
- Vigants-Barnett: Factor C: Under Vigants-Barnett: Factor C, you can define C, the propagation condi-
tion factor for Vigants-Barnett method. You can either select Real and enter a value, or select Terrain
Type and the C factor will be calculated from the terrain.
• The Reliability tab:
- Link Class: Under Link Class, you can select the link class. Each link class can have different performance
objectives. By assigning the link class with the appropriate performance objectives, you assign the perform-
ance objectives to the link. For information on creating a link class, see "Microwave Link Classes" on
page 207.
Clicking the Browse button ( ) opens the Properties dialogue of the selected link class.
Clicking the Objectives button opens a dialogue where you can view and modify the performance objectives
of the selected link class.
- Bit Error Rate: Under Bit Error Rate, you can set the values for BER 1 and BER 2. Atoll displays the
resulting sensitivity for each BER.
• The Propagation tab, you can define propagation-related parameters:
- Model used for the useful signal: Under Model used for the useful signal, you can select the propagation
model that will be used to calculate the path loss as well as the margin required for quality and availability for
the microwave link. If no propagation model is selected, the quality and availability of the link will be defined
by the respective target values defined in the link class.
- Model used for the interfering signal: Under Model used for the interfering signal, you can select the
propagation model that will be used to calculate interference.
• The Display tab, you can define the appearance of the microwave link and its extremities.
2. Click the arrow next to New Link button ( ) on the Microwave toolbar.
3. Select Using The Mouse On The Map from the menu. The pointer changes ( ).
The sites that define the extremities of a microwave link can be already existing sites or Atoll will create new sites
automatically at the location clicked by the user. Each site in Atoll can support several microwave links, transmit-
ters, and passive repeaters.
a. Click once on the map to indicate the location of the first end of the link. The pointer now changes ( ).
b. Click again on the map to indicate the location of the other end of the link.
2. Click the arrow next to New Link button ( ) on the Microwave toolbar.
3. Select Between Sites from the menu. The Link Creation dialogue appears.
4. In the Link Creation dialogue, define the following parameters:
- Model: the link template you want to use in order to create the microwave link.
- Site A: the name of the site defining one extremity of the link.
- Site B: the name of the site defining the other extremity of the link.
5. Click OK.
By default, Atoll names the newly created microwave links in the following manner: SiteX – SiteY, where SiteX is the name
of the start site (existing or newly created) and SiteY is the name of the end site (existing or newly created).
You can also create a link template based on a link template selected in the Link Template Properties dialogue. The new
link template has the same parameters as the one it is based on. Therefore, by selecting the existing link template that
most closely resembles the link template you want to create, you can create a new template by only modifying the param-
eters that differ.
As well, you can modify the properties of any link template.
To create a link template based on an existing link template or modify a link template:
1. In the Microwave toolbar, click the arrow to the right of the list.
2. Select Manage Templates from the list. The Link Template Properties dialogue appears.
3. You can now create a new link template or modify an existing one:
- To create a new link template: Under Available Templates, select the link template that most closely resem-
bles the link template you want to create and click Add. The Properties dialogue appears.
- To modify an existing link template: Under Available Templates, select the link template whose properties
you want to modify and click Properties. The Properties dialogue appears.
4. For information on the fields available in the open window, see "Modifying Microwave Sites and Links Directly on
the Map" on page 1132.
5. Click OK.
The new link template will be available in the template menu.
Notes: If you add a field to the link templates, you must add an equivalent field to the Sites table
or the field will not be taken into account.
After defining the configuration for one direction, you can define the opposite direction by clicking the Initialise
Symmetrically button.
11. Click OK. The Ports Definition dialogue closes.
12. Click OK.
15.2.2.1 Placing a Passive Microwave Repeater on the Map Using the Mouse
In Atoll, you can create a passive microwave repeater and place it using the mouse. When you create a passive micro-
wave repeater, you can add it to an existing site, or have Atoll automatically create a new site.
Atoll permits a maximum of 2 passive repeaters in a single microwave link. The following terms are used in Atoll for
passive repeaters and related parameters:
• Passive repeaters (maximum 2) along a microwave link are named repeater P and repeater Q respectively.
• A part of the link is called a "Section." A section can be:
- One of the directions of a bi-directional link.
- One of the trajectories towards a repeater (if any).
- For example:
- Unidirectional link without repeater: 1 section, Site A Site B
- Bi-directional link without repeater: 2 sections, Site A Site B and Site B Site A
- Bi-directional link with 2 repeaters: 6 sections, Site A Site P, Site P Site Q, Site Q Site B, Site B Site Q,
Site Q Site P, Site P Site A.
To create a passive microwave repeater and place it using the mouse:
1. Select the microwave link. You can select it from the Links folder of the Explorer window’s Data tab, or directly
on the map.
2. Click the arrow next to New Repeater button ( ) on the Microwave toolbar.
3. Select Panel Reflector or Back-to-back Antennas from the menu according to the type of passive repeater you
want to create.
4. Click the map to place the repeater. The repeater is placed on the map, represented by the site symbol ( ).
Atoll automatically creates a new repeater in the Passive Repeaters table and a new site in the Sites table that
is assigned to the newly created repeater. The operating frequency band of the repeater is the frequency band
assigned to the microwave link and azimuth(s) for the repeater antenna(s) are calculated according to the direc-
tions of the two sections of the microwave link.
For information on defining the properties of the new microwave passive repeater, see "Defining the Properties of
a Passive Microwave Repeater" on page 1133.
Note: You can also insert a repeater in a microwave link by selecting Insert Repeater from the
microwave link’s context menu and then clicking on the microwave link where you want to
insert the repeater.
Important: The table you copy data from must have the same column layout as the table you are
pasting data into.
For information on copying and pasting data, see "Copying and Pasting in Tables" on page 56.
You can access the Properties of the selected site and frequency band by clicking the Browse button ( ) oppo-
site to the corresponding item.
You can click the Calculate button ( ) to automatically calculate azimuth and tilt angles.
- For a back-to-back antenna type repeater, define the following parameters:
- Under Antenna1, you can choose the antenna, define the antenna height, the azimuth and tilt angles to-
wards the site of transmission.
- Under Antenna2, you can choose the antenna, define the antenna height, the azimuth and tilt angles to-
wards the site of reception, and specify whether the antennas have a crossed polarisation.
- Under Waveguide, you can choose the waveguide and define the length. By default, Atoll lists
waveguides that operate in the frequency band defined for the repeater. If you want, you can apply an
additional filter by clicking the button ( ) beside the model field. When the filter is active, the appear-
ance of the button changes ( ). In this case, Atoll proposes in the list waveguides compatible with the
selected antennas as defined in the Antenna/Guides Compatibility table.
You can click the Calculate button ( ) to automatically calculate azimuth and tilts angles.
8. Click OK.
Note: In Atoll it is not obligatory to have all the links composing a multi-hop link to be
interconnected. But this is the practical case in almost all microwave networks worldwide.
The following sections describe the creation and deletion of microwave multi-hop links and the setting of global properties.
Note: An Other Properties tab window is also available if a user-defined field has been added to
the multi-hop links table.
a. In the map, click the line of the multi-hop link to which you want to add a microwave link.
b. Right-click on the multi-hop link. The context menu appears.
2. Select Add a Link from the context menu. The pointer shape changes to in the map window.
3. On the map, click the microwave link you want to add to the multi-hop link.
The microwave link is added to the list of links forming the multi-hop link and assigned an order automatically.
a. In the map, click the line of the multi-hop link you want to delete.
b. Right-click on the multi-hop link. The context menu appears.
2. Select Delete from the context menu. The multi-hop link is deleted.
Another alternative is to delete the row associated with the multi-hop link you want to delete in the Multi-hops table.
Notes
• Deleting a multi-hop link in this manner does not delete the corresponding sites even if there are
no other links or transmitters relating to that site.
• When selecting a multi-hop link, be careful to select the line representing the multi-hop link. Do
not select the site icon ( ). Since it is also possible to delete the sites on which multi-hop links
are built, be sure to select the line and not the site.
1. Click the new PMP button ( ) on the toolbar. The pointer changes to .
2. Click on the map to create the hub of the point-to-multipoint link.
3. Click on the map in each place you want to insert a new link. If you do not click an existing site, Atoll creates a
new site where you click.
4. Double-click when adding the last link to complete the point-to-multipoint link.
To create a new point-to-multipoint link using the Point-to-Multipoint folder:
1. Select the Data tab of the Explorer window.
2. Click the button of the Microwave Radio Links folder. The Microwave Radio Links folder opens.
3. Right-click on the Point-to-Multipoint folder. The context menu appears.
4. Select New… from the context menu. The Point to Multipoint New Element Properties dialogue appears.
5. Enter or modify the following fields on the General tab:
- Name: The Name field is filled automatically by Atoll, but can be modified.
- Frequency Band: You must select a frequency band when you create a point-to-multipoint link. Once you
have selected a frequency band, you can view and modify its properties by clicking the browse button ( ).
- Nodal Site: You must select the site that will be the hub of the point-to-multipoint link. Once you have selected
the hub site, you can view and modify its properties by clicking the browse button ( ).
- Type: Select the type: TDMA or FDMA.
- Antenna: Select the antenna and its parameters.
- Comments: Enter any comments for this new point-to-multipoint link.
6. Click OK. Atoll creates an empty point-to-multipoint link item in the Point-to-Multipoint folder.
7. To add microwave links to the created point-to-multipoint link, see "Graphically Adding a Microwave Link to a
Point-to-Multipoint Link" on page 1139
To create a new point-to-multipoint link using the Point-to-Multipoint links table:
1. Select the Data tab of the Explorer window.
2. Click the button of the Microwave Radio Links folder. The Microwave Radio Links folder opens.
3. Right-click on the Point-to-Multipoint folder. The context menu appears.
4. Select Open Table from the context menu. The Point to Multipoint table appears.
5. In the row marked with the new row icon ( ), enter the details of the new point-to-multipoint link. The following
fields must be filled: Name, Frequency Band, and Site.
6. To add microwave links to the created point-to-multipoint link, see "Graphically Adding a Microwave Link to a
Point-to-Multipoint Link" on page 1139.
By default, Atoll names the newly point-to-multipoint link "PMP HubX", where "X" increments with the creation of each
new point-to-multipoint link.
a. Select the antenna icon of the point-to-multipoint link hub whose properties you wish to change. The point-to-
Note: Be sure to select the antenna icon of the point-to-multipoint link hub. Do not select the site icon ( ).
Note: Before you can define a microwave link as part of the point-to-multipoint link, the
microwave link must first exist between the site of the hub of the point-to-multipoint link
and another site. For information on creating links, see "Definition of a Microwave Link" on
page 1126.
6. In the row marked with the new row icon ( ), select a link.
7. Click OK. The microwave link is added to the point-to-multipoint link.
Note: Before you can define a microwave link as part of the point-to-multipoint link, the
microwave link must first exist between the site of the hub of the point-to-multipoint link
and another site. For information on creating links, see "Definition of a Microwave Link" on
page 1126.
5. Select Add a Link … from the context menu. The pointer shape changes to in the map window.
6. On the map, click the microwave link you want to add to the point-to-multipoint link. The microwave link is added
to the list of links forming the point-to-multipoint link.
Note: Deleting a microwave link in this manner does not delete the corresponding sites even if
there are no other links or transmitters related to that site.
a. In the map, select the line of the point-to-multipoint link you want to delete.
b. Right-click on the Point-to-Multipoint link. The context menu appears.
2. Select Delete from the context menu. The point-to-multipoint link is deleted.
Notes
• You can also delete a point-to-multipoint link by deleting the row associated with it in the Point-
to-Multipoint table.
• Deleting a point-to-multipoint link in this manner does not delete the corresponding sites even
if there are no other links or transmitters relating to that site.
• When selecting a point-to-multipoint link, be careful to select the line representing the point-to-
multipoint link. Do not select the site icon ( ). Since it is also possible to delete the sites on
which point-to-multipoint links are built, be sure to select the line and not the site.
7. In the "Antenna" subsection, click the Calculate button ( ) to the right of the Tilt field. A dialogue appears with
the recalculated height, azimuth, and tilt values for the point-to-multipoint hub antenna.
8. When the values for the point-to-multipoint hub antenna are recalculated, the point-to-multipoint link antennas may
need to be adjusted accordingly. If you want Atoll calculate the effect of the recalculated values for the hub
antenna on the link antennas, select the Transfer the misalignments to links check box.
9. Click OK to update the values for the point-to-multipoint antennas.
15.2.4.10 Adjusting the Antenna of the Point-to-Multipoint Hub Using the Mouse
To use the mouse to graphically adjust the azimuth of the point-to-multipoint hub antenna:
1. Select the antenna icon of the point-to-multipoint hub. The point-to-multipoint icon changes ( ) and you can
now rotate it manually.
2. Click the antenna icon (the point changes: ) and rotate it to its new azimuth.
You can combine a computation zone and a filter, in order to create a very precise selection of the sites and microwave
links to be studied.
In addition, it is possible to set a focus zone in order to filter the results displayed in reports (link budgets, interference).
Note: You can save the computation zone in the user configuration. For information on the user
configuration, follow the instructions in "Exporting a Geo Data Set" on page 127.
Note: You can save the focus zone in the user configuration. For information on the user
configuration, follow the instructions in "Exporting a Geo Data Set" on page 127.
You can also access the Profile analysis window through button in the toolbar.
1. Click the button in the toolbar to activate the Microwave link analysis window Profile tab.
2. Select the microwave link to analyse either on the map, or in the Links folder in the Explorer window or from
the list available on the Profile tab.
The microwave profile analysis window provides an interactive real-time display of the microwave link profile from site A
to site B or vice versa. It includes any passive repeaters composing the link. The altitude (in metres) is reported on the
vertical axis and the distance on the horizontal axis. A blue ellipsoid indicates the Fresnel zone between the transmitter
and the receiver sites, with a green line indicating the line of sight (LOS). Atoll displays the terrain height along the profile
as well as clutter classes and clutter heights when the visibility check box of the Clutter Classes folder on the Geo tab is
selected. If you do not want to display the clutter along the profile, you can clear the visibility check box of the Clutter
Classes folder on the Geo tab. Along the profile, if the signal meets an obstacle, this causes attenuation with diffraction
displayed by a black vertical line (if the propagation model used takes diffraction into account). The main peak is the one
that intersects the Fresnel ellipsoid the most. The diffraction attenuation is displayed above the peak.
When a repeater is inserted on the link, it is displayed in the microwave link profile analysis window by a vertical line in the
profile. At the top of the Microwave Link Analysis window, you can select which part of the profile you want to display:
• Site A ==> Site P
• Site P ==> Site B
• Site B ==> Site P
• Site P ==> Site A
• Site A ==> Site B (profile "broken" at Site P)
• Site B ==> Site A (profile "broken" at Site P)
When a second repeater (Q) is inserted on the link, the profile display options include Site Q as well.
You can left-click the Link button in the profile analysis window and choose from the context menu:
• Properties to open the microwave link property dialogue.
Apart from this, you can right-click on the profile as well and select from the context menu:
• Zoom In to zoom in on the microwave link profile.
• Actual Size to reset the zoom level and restore the initial profile display.
• Copy to copy the profile in the clipboard.
• Print to print the microwave link profile.
• Display Options to define display parameters
• Display Information on the Current Point to display information on any point along the profile.
• Display Fresnel Ellipsoids to view Fresnel zones.
• Display Reflections to view zones and points of reflection along the profile.
• Insert Repeater to add a new repeater on the selected link.
values can be set through the advanced options available by pressing the button opposite the microwave links list.
Atoll displays the clearance (%) and the penetration of the Fresnel zone for each value of k. In addition, it indicates for
both antennas, the tilts/direct ray, the azimuths and the angles of incidence.
The first Fresnel ellipsoid corresponding to the first k value is shown in blue, while the second related to the second k value
is shown in red. It is also possible to display another Fresnel ellipsoid when a secondary antenna is installed at the receiver.
If there are obstructions in the path of the microwave link that introduce losses, a green coloured line is drawn from the
transmitter to the first obstacle’s highest point. A perpendicular from the horizontal axis is also drawn to mark the obstacle
that introduces the highest loss in the link, and the loss from this obstacle is displayed on the top of this perpendicular.
A common mode of operation would be to display the first Fresnel zone at 100% and the second at 60% so as to depict
the minimum clearance requirement directly on the profile. To manage the display of Fresnel ellipsoids, both first and
second, you have to access the Display options dialogue for the profile and modify these parameters.
Here, it is also possible to modify the antenna heights at both extremities manually and automatically, this feature is
described in detail in the Optimising microwave link antenna heights section.
5. Click the Zoom Area icon ( ) on the Zoom toolbar (or press CTRL+W).
6. Click in the profile on one of the four corners of the area you want to select.
7. Drag to the opposite corner. When you release the mouse button, Atoll zooms in on the selected area.
To restore the initial profile:
1. Open the microwave link Profile Analysis Window.
2. Select the microwave link to analyse
3. Right-click the window to open its context menu.
4. Select Actual Size (1:1) from the context menu.
As the mouse pointer is clicked-dragged along the profile of the microwave link in the microwave analysis window, a
special pointer pinpoints the location of the current point along the profile on the map window.
into account the values of the k factor, defining the curvature of the Earth, the geographic data defining any possible terrain
or clutter penetration in the microwave line-of-sight, the initial antenna heights and antenna tilt angles.
The following sections describe these functions in Atoll.
b. Click the antenna height icon (which now looks like this: ) with the mouse and drag it up or down to modify
the antenna height,
c. Right-click on the pointer to open its context menu,
d. Choose Save H? command to save the current antenna height in the microwave link,
• Or,
Notes
• H? can be Ha or Hb depending on the site of the microwave link under consideration.
• It is possible to specify a maximum pylon height for the receiving and transmitting sites not to
be exceeded. This parameter can be defined in each site properties dialogue (Other Properties
tab). If defined, these height limits are represented on the Profile tab.
- One is based on the clearance of the Fresnel ellipse: You may enter one or two values of the k factor and
define for each of them a target clearance. Atoll will determine antenna heights so as to fulfil the highest con-
straint.
If you have out-of-date clutter class maps, you can estimate the growth of vegetation. Atoll takes this value
into account for clutter categories from 6 to 14 and adds it to the clutter height.
- The other one is based on diffraction losses: Atoll determines antenna heights so as to minimise diffraction
losses due to the main obstacle (i.e. it will find the antenna heights so as to get a clearance of 60% of the first
Fresnel zone).
7. Click OK or Cancel.
8. Click the Height button for the site whose antenna height you want to optimise.The context menu appears.
9. Choose Optimise to calculate the optimum antenna heights for both extremities according to the k factor defined.
It is also possible through the same context menu to freeze the antenna height at a certain value. In this way, you can
disallow any modification in this height during the optimisation process. Only the other antenna height will be calculated
so as to optimise the link. Furthermore, you can always restore the last antenna height value through the Restore
command in the same menu.
Note: This context menu can also be accessed through right-clicking the pointer depicting
the antenna height at the extremities.
Once the optimum antenna heights have been calculated by Atoll, you can now save one or both the antenna heights in
the microwave link. This can be done through the same context menu as well.
This feature is only available for unbroken microwave link profiles, i.e., it is not accessible for microwave link profiles involv-
ing one or more repeaters. It enables you to calculate optimum antenna heights for two-site microwave link profiles (e.g.,
Site Site B or Repeater P Site B).
Notes
• It is possible to consider in the calculation a maximum pylon height for the receiving and trans-
mitting sites not to be exceeded. This parameter can be defined in each site properties dia-
logue (Other Properties tab). If defined, these height limits are represented on the Profile tab.
• Reflections are not taken into account in this calculation.
Notes
• Reflection paths and reflective surfaces can only be visualised and analysed over unbroken
microwave link profiles, i.e., the profile should not include repeaters.
• A reflection zone may be composed of several clutter classes.
It should be kept in mind that reflection point is a function of the k factor. It is possible by carefully positioning the antenna
heights to minimize the effects of reflection.
It is also possible to obtain detailed analyses of reflective surfaces and their impacts on the microwave links. You can get
detailed reflection losses analysis over any reflection zone along the path and you can also obtain a graph of differences
between reflection paths depicting the τ (tau) factor as a function of k factor. τ is the delay of the secondary signal
received through reflection.
To obtain the reflection losses analysis or graph of differences between reflection paths:
1. Display the reflection zones along the profile as explained above.
2. Right-click on a reflection zone or reflection path to study in the profile to display its context menu.
3. Select one of the following from the context menu:
- Display the Reflection Study Dialogue: To display the reflection losses related to the selected reflection
zone or reflection path.
- Graph of differences between reflected paths: To display the graph of τ (tau) with respect to the k factor
related to the selected reflection zone or reflection path.
Atoll lists roughness, ground type, humidity type, permittivity, conductivity, surface reflection coefficient, divergence factor,
specular reflection factor and effective reflection coefficient as ground characteristics, and attenuations due to antenna
tilts, reflected waves and maximum possible fade depth, for any reflection zone through the Reflection losses command.
Note: The calculation of the reflection point follows the recommendations 530.10 of the ITU-R.
- Either as a function of the earth curvature factor (k factor), for three different receiver antenna heights,
- Or as a function of the receiver antenna height, for three different values of the earth curvature factor (k factor).
The scales and other parameters corresponding to this calculation and display can be managed in the related display
options dialogue.
You can define display options by clicking the Actions button and choosing Display options in the menu. Here you can
manage the scales of the vertical and the horizontal axes depicting the variations in attenuation level and the varying
values of the k factor/receiver antenna height respectively. The effects of introducing diversity antennas can be directly
visualised on this graph by modifying the parameters available. The height H2 corresponds to the actual antenna height
at the receiver (Site B or Site A depending on the profile selected). The other heights (H1 and H3) correspond to imaginary
diversity antenna heights placed at a distance of Suggested Antenna Separation below and above the main antenna.
The Suggested Antenna Separation value is automatically determined by Atoll and represents the least separation
distance that provides that the attenuations and gains of the three antennas never coincide at any value of refractive index
within provided range.
Note: The required performance objectives are also listed in the report on the Report tab of the
Microwave Link Analysis window.
overall microwave link reliability. Thus, Atoll facilitates decision making by the user in terms of factors to be tuned or traded
off in order to realise the project.
Link budget calculations in Atoll can be performed on single microwave links as well as on a group of microwave links
simultaneously. The following sections present both of the link budget calculation methods.
Atoll provides the user with detailed microwave link budget tool. This tool generates a comprehensive report for each stud-
ied microwave link as detailed below.
Moreover, the results provided in this report are calculated in real-time. Therefore, it is possible to modify the properties
of the microwave link, or the calculation parameters, and immediately visualise the impacts of the modifications in the
microwave link analysis window (both Profile and Report tabs). Furthermore, any modifications made by the user in the
profile of the microwave link through the Profile tab of the microwave link analysis window or any modifications in the geog-
raphy of the microwave link profile made through the Values tab are also taken into account in the link budget on the Report
tab in real-time.
To generate a microwave link budget for a single microwave link:
1. Right-click the microwave link either directly on the map, or from the Links folder of the Explorer window’s Data
tab. The context menu appears.
2. Choose Engineering and Report from the context menu.
You can also access the Report tab by opening the Microwave Link Analysis window and clicking the Report tab.
The Report tab of the microwave link analysis window contains the link budget for the link being studied. Microwave link
budget results on the Report tab include the following information:
• Microwave Link Profile: A snapshot from the Profile tab of the Microwave Link Analysis window in order to facil-
itate direct visualisation and printing of the link profile with the link budget report.
• Summary: A summary of the link being studied, its operating frequency band, length, thermal fade margin, worst
month quality, average annual availability and whether quality and availability objectives are reached for both
directions of the link and the specified BER values. Finally, a global link estimation taking into account both link
quality and availability is provided over an average year.
• Link specifications: Information relating to the microwave link design; site names, locations, and altitudes for
both extremities, repeaters (if any), antennas used at both sites with their respective models, heights, azimuths,
tilts, gains, diameters and near fields, diversity antennas and repeater back-to-back antenna details such as the
models, heights, azimuths, tilts, gains and diameters, microwave transceiver equipment installed at both sites with
details such as the models, digital hierarchy employed, modulation used, data rates, minimal channel bandwidths,
capacities and configurations.
• Transmission parameters: Transmission related parameters for both extremities of the microwave link including
the EIRP, ATPC effects, transmitter powers, passive repeater gains (if any), total losses comprising filter losses,
connection losses, shared losses, shielding losses, port connection losses, and waveguides and cable losses,
polarisation at both sites, and the port and the channel for which the calculations have been performed (maybe
the central frequency of the microwave link’s operating frequency band).
• Port Configuration: Port configuration related parameters for both directions, the channel, the corresponding fre-
quency, the polarisation, if it is a main channel or a standby channel or a channel for frequency diversity, the trans-
mission and reception port numbers, the port circulator and attenuator losses.
• Reception parameters: Reception related parameters for both ends of the microwave link including the bit error
ratios and sensitivities at the receivers, overflow thresholds, thermal noise, the required C/I and total losses at
reception comprising filter losses, connection losses, shared losses, shielding losses, port connection losses, and
waveguides and cable losses.
• Geoclimatic parameters: Information about the type of environment and the climatic zone in which the link is
operating, climatic factor, rain intensity (exceeding 0.01% of time), PL percentage, temperature, water vapour den-
sity, earth curvature factor (k), effective earth curvature factor (ke) and the geoclimatic factor K.
• Calculation parameters: Parameters according to which the calculations for the link budget have been performed
such as the calculation methods used (propagation model, quality model, availability model, interference, if
enhancements and discrimination reduction are ignored, space diversity and frequency diversity), quality objec-
tives (SESR, ESR, BBER), and availability objectives (SESR, ESR, BBER).
• Propagation: the nominal received signal level, propagation results for both directions of the microwave link
including total attenuation, free space loss, losses due to dry air, losses due to water vapour, diffraction losses,
vegetation attenuation (displayed for information only because it is taken into consideration in total attenuation),
antenna losses and tropospheric scattering, epsilon and the type of path (LOS or NLOS).
• Non-quality due to multi-path (Clear-Air): Results depicting the quality of the microwave link in both directions,
for specified BER values and when interference is not taken into account. These results include the outage prob-
ability, the non-outage probability and the outage period for the worst month, the outage probability, the non-
outage probability and the outage period for the average year, performance objectives (probabilities of SESR
(required), ESR (required), BBER (required)), details for the worst month (dispersive fading, selective fading,
fading due to discrimination reduction, enhancement forecast).
• Unavailability due to rain: Results depicting the unavailability of the microwave link due to rain in both direction,
for specified BER values and when interference is not taken into account. These results include the outage prob-
ability, the non-outage probability and the outage period for the worst month, the outage probability, the non-
outage probability and the outage period for the average year, performance objectives (probabilities of SESR
(required), ESR (required), BBER (required)), details for the average year (rain fading, rain attenuation, fading due
to discrimination reduction).
• Unavailability due to faults: Results depicting the unavailability of the microwave link due to equipment failure.
These results include availability of hot standby, outage probability due to faults for the average year and the
outage period for the average year and the performance objective.
This is a comprehensive report and can be configured as described in the Configuring the link budget report display
section.
It is possible to study the influence of some parameters on the microwave link engineering by setting some calculation
options.
To modify analysis parameters for a link:
1. Select a microwave link.
2. Open the Microwave Link Analysis window.
3. Click the Report tab.
4. Click the Actions button. The context menu appears.
5. Select Analysis Parameters for the Hop. The Hop Analysis Parameters dialogue appears.
6. You can set the following options:
- Take Space Diversity Into Account: If you want to take space diversity into account, select the Take Space
Diversity into Account check box and define the following:
- Distance between antennas: Define the distance between main and diversity antennas.
- Gain difference between antennas: Define the difference of gain between both antennas.
- Take Frequency Diversity Into Account: If you want to take frequency diversity into account, select the Take
Frequency Diversity into Account check box and define the number of separation channels.
- Inverse Polarisation: Select the Inverse Polarisation check box if you want to take inverse polarisation into
account.
7. When you have finished modifying analysis parameters, click one of the following:
- Save in the Link: Click Save in the Link to save these changes in the microwave link properties and click
OK to close the dialogue.
- OK: Click OK without clicking Save in the Link to check the impact of the selected options on the report
without modifying the microwave link properties.
To modify calculation parameters for analysis:
1. Select one microwave link.
2. Open the Microwave Link Analysis window.
3. Click the Report tab.
4. Click the Actions button. The context menu appears.
5. Select Calculation Parameters. The Microwave Radio Link Properties dialogue appears. You can define the
studied port, BER values, etc., or change calculation models. For further information, see "Global Parameters" on
page 209.
6. Click OK to check the impact of the selected options on the report.
You can configure the display parameters of the report generated under the Report tab to display some or all of the param-
eters used in the calculations and results of the calculations with different styles.
To configure the link budget report display:
1. Open the microwave link analysis window,
2. Click on the Report tab,
3. Click the Actions button on the window to open its context menu,
4. Select Configure report… command to open the configuration dialogue
5. Use the What’s this help to get description of the fields available in the dialogue,
6. Click OK or Apply to validate.
This configuration dialogue lets you manage the display of the report through the options available in two tabs. The Report
content tab lets you select the level of information and detail you want to include in your report. You can check the infor-
mation you want to display and clear the rest. The Report content tab enables you to switch the display of the microwave
link profile snapshot on the report tab on or off as well. You can manage the font and paragraph characteristics of the
displayed report through the Style tab.
Note: You can save the choices you have made as a configuration file by clicking the Save As
button at the top of the dialogue and entering a name for the file in the Save As dialogue
that appears. The next time you configure a report, you can click Open in the dialogue
and select your configuration file with the same settings you used this time.
Atoll provides the user with the feature enabling to calculate multiple microwave link budgets for a group of microwave
links simultaneously. Microwave links in Atoll can be grouped in subfolders according to different property parameters
(e.g. frequency band). The user has the possibility of launching simultaneous link budget calculations for the microwave
links grouped in a subfolder. Before calculating one or more link budgets, you can create a computation zone. The compu-
tation zone is used to define the area where Atoll carries out calculations. When you create a computation zone, Atoll
carries out the calculation for all microwave links in the subfolder that are active, filtered (i.e., that are selected by the
current filter parameters), and intersects the computation zone.
The computation zone is taken into account whether or not it is visible. In other words, if you have drawn a computation
zone, it will be taken into account whether or not its visibility check box in the Zones folder of the Geo tab in the Explorer
window is selected. You will have to delete the computation zone if you no longer want to define an area for calculations.
When working with a large network, the computation zone allows you to restrict your studies to the part of the network you
are currently working on. By allowing you to reduce the number of microwave links studied, Atoll reduces both the time
and computer resources necessary for calculations.
If there is no computation zone defined, Atoll makes its calculations on all microwave links in the subfolder that are active
and filtered and for the entire extent of the geographical data available.
For information on the computation zone, see "Setting a Computation Zone" on page 1141.
To perform link budget calculations on a group of microwave links:
1. Click the Data tab of the Explorer window.
2. Expand the Microwave Radio Links folder by clicking the button.
• Either,
- Right-click on the Links folder to open its context menu.
• Or.
a. Expand the Links folder by clicking the button,
b. Right-click the subfolder under the Links folder for which you want to calculate link budgets to open its context
menu.
3. Choose the Calculate command from the Link Budgets menu. The progress of the calculations is displayed in
the Event Viewer window.
Note: You can stop any calculations in progress by clicking the Stop Calculations button ( )
in the toolbar.
This will open a table listing all the link budgets calculated for the microwave links included in the subfolder for
which calculations had been launched. This table contains the link budgets for both directions of each microwave
link:
4. To view each single microwave link budget, click on the table row corresponding to the microwave link being
studied.
5. Click on the Report tab.
Atoll indicates the characteristics of the link (sites, antennas and equipment installed), the signal level received, the fade
margin, and its quality and availability on the Report tab. It displays the transmission parameters (EIRP, various losses,
etc.), reception parameters (sensitivity, various losses, etc.), calculation options, and geo-climatic parameters. It also
details the propagation calculation (total attenuation) and the calculations related to link engineering (quality (Clear-Air),
unavailability due to rain, unavailability due to faults). All the results are provided in both the directions of the microwave
link being studied.
Link budget calculations performed for a group of microwave links (i.e., intermediate results such as propagation, outage
probabilities) are saved in the Atoll document. So, once calculations have been performed for all the links, you can quickly
perform a link budget for a group of links. Atoll only recalculates non-existent and invalid microwave links. Calculations
can become invalid for different reasons:
• If a calculation method or option has been changed,
• If microwave link properties have been modified,
• If geographic data maps have been updated.
For the first two reasons, Atoll automatically detects invalidity of the calculation when starting calculations and makes the
recalculation. In the last case (e.g., if you added a new clutter class map), you must force Atoll to recalculate.
To force Atoll to recalculate the link budget:
1. Click the Data tab of the Explorer window.
2. Click the Expand button ( ) to expand the Microwave Radio Links folder.
To recalculate the link budget for the entire Links folder:
To recalculate the link budget for a subfolder of links under the Links folder:
and filtered microwave links whose transmitter – receiver trajectory intersects or passes through the computation zone and
whose interfering transmitter – interfered receiver distance is less than a given value. Atoll also considers the adjacency
of frequency bands, i.e., microwave links with equipment operating frequency bands that overlap the operating frequency
band of the microwave link being studied.
Following parameters are taken into account when calculating interferences:
• Interferer ATPC: Can be user-defined as always on, always off or based on a calculated geometric correlation.
• IRFs defined on the IRF table if available
• "T/I curve, transmitter mask, receiver mask" graphs defined at the equipment level or theoretical graphs.
• Polarisation and equipment signatures.
• Co-channel and adjacent channel interference.
Atoll can perform quick interference analyses for single microwave links as well as for groups of microwave links. It can
generate qualitative analysis reports and detailed results in both and can display all the interference relations between
studied microwave links graphically on the map. The following sections describe how to carry out microwave link interfer-
ence analyses in Atoll.
- Interference: Calculation parameters taken into consideration for the interference study (power control, min-
imum threshold reduction, maximum distance, correlation area, interfered useful bandwidth) and results of
interference calculations over the microwave link (threshold reduction, nominal received carrier power level,
total interference in clear-air, threshold reduction for rain, total interference in rain and C/I).
- Propagation: The nominal received signal level, propagation results for both directions of the microwave link
including total attenuation, free space loss, losses due to dry air, losses due to water vapour, diffraction losses,
vegetation attenuation (displayed for information only because it is not considered in the total attenuation),
antenna losses and tropospheric scattering, epsilon and the type of path (LOS or NLOS).
- Non-quality due to multi-path (Clear-Air): Results depicting the quality of the microwave link in both direc-
tions, for the specified BER values and whether interference is taken into account. These results include the
outage probability, the non-outage probability and the outage period for the worst month, the outage proba-
bility, the non-outage probability and the outage period for the average year, performance objectives (proba-
bilities of SESR (required), ESR (required), BBER (required)), details for the worst month (dispersive fading,
selective fading, fadings due to discrimination reduction, enhancement forecast), if space and frequency diver-
sities are used.
- Unavailability due to rain: Results depicting the unavailability of the microwave link due to rain in both direc-
tions, for the specified BER values and whether interference is taken into account. These results include the
outage probability, the non-outage probability and the outage period for the worst month, the outage proba-
bility, the non-outage probability and the outage period for the average year, performance objectives (proba-
bilities of SESR (required), ESR (required), BBER (required)), details for the average year (rain fading, rain
attenuation, fading due to discrimination reduction).
- Unavailability due to failures: Results depicting the unavailability of the microwave link due to equipment
failure. These results include availability of hot standby, outage probability due to failures for the average year,
the outage period for the average year and the performance objective.
- Interference Details: List the microwave links that interfere the given extremity of the microwave link being
studied and the microwave links interfered by the given extremity of the microwave link being studied.
• Victim tabs: List the microwave links that interfere the given extremity of the microwave link being studied along
with relevant details of the interference study.
• Interferer tabs: List the microwave links that are interfered by the given extremity of the microwave link being
studied along with relevant details of the interference study.
Notes
• You can stop any calculations in progress by clicking the Stop Calculations button ( ) in
the toolbar.
• You can access each microwave link’s properties by double clicking the corresponding record
in the Victim/Interferer tabs.
Atoll calculates the interference levels on each channel of the frequency half-band (lower or upper) of the micro-
wave link and represents them as vertical lines on the graph. The red line shows the total noise level received on
the interfered channel and each blue line represents the signal level transmitted on each interfering channel.
You can easily locate the channels on which there is least or no level of interference and can allocate these "free"
channels where required.
Note: Each vertical line representing the interference level received at any channel depicts the
peak signal value. If there are more than one interfering signals, only the peak value is
displayed on the graph.
through this results window to allocate the best channels to the link by selecting the channels to assign and clicking the
Commit button.
The site parity checking tool enables the user to view the site parities on the map and hence detect any possible parity
conflicts.
To perform a site parity check and display:
1. Click on the Data tab of the Explorer window.
2. Expand the Microwave Radio Links folder by clicking the button.
3. Right-click the Link folder. The context menu appears.
4. Select Interferences, Channels Distribution per Site and Display on the Map from the context menu. The
Channel Distribution dialogue appears.
5. Select the operating frequency band for which you want to check the parities of microwave link extremities.
6. Choose an icon for the different cases.
- Lower: The site is assigned frequencies from the lower half-band.
- Upper: The site is assigned frequencies from the upper half-band.
- Multiple: The site is assigned frequencies from the lower and upper half-bands.
- Unspecified: No frequency is assigned to the site.
7. Enter the position of icons relative to the site (dpi).
8. Select the Add to Legend check box in order to add the displayed icons to a legend.
9. Click OK to start the calculations.
You can also access the same channel distribution configuration dialogue through the toolbar by clicking the button.
Once the site parities are displayed on the map, you can hide them by clicking the button again. You can also hide
the site parities through the context menu as follows:
1. Click on the Data tab of the Explorer window.
2. Expand the Microwave Radio Links folder by clicking the button.
3. Right-click the Link folder. The context menu appears.
4. Select Interferences and Hide Channel Distribution from the context menu.
Atoll enables the user to check site parities and to display the results in a report.
To display the result of the site parity checking in a report:
1. Click on the Data tab of the Explorer window.
2. Expand the Microwave Radio Links folder by clicking the button.
3. Right-click the Link folder. The context menu appears.
4. Select Interferences, Channels Distribution per Site and Generate Report from the context menu. The
Channel Distribution dialogue appears.
5. Select the operating frequency bands for which you want to check the parities of the microwave link extremities.
6. Click OK to start the calculations.
Atoll checks the site parities of all the microwave links working at the selected frequency bands. Once Atoll has
finished checking site parities, results are displayed in the Channel Distribution table.
- Cause: Information provided for multiple parity only. Atoll gives the name of microwave links whose the site
has a multiple parity.
- Longitude: The longitude of the site.
- Latitude: The latitude of the site.
You can sort and filter data in the Channel Distribution table. For more information, see "Sorting Data in Tables" on
page 68 and "Filtering in Data Tables by Selection" on page 70.
Index
modifying (TD-SCDMA) 823 min. Ec/Nt (UL), defining for mobility (CDMA) 651
modifying (UMTS) 513 mobility type parameters 651
modifying (WiMAX) 940 MUG table, defining (CDMA) 610
equipment noise rise threshold, defining (CDMA) 610
compatibility with antennas (microwave) 164, 165 pilot pollution, calculating (CDMA) 660
compatibility with antennas, assistant (microwave) 165, 166 PN offset domain, defining per cell (CDMA) 611
creating (LTE) 1104 PN offset reuse distance, defining per cell (CDMA) 611
creating (WiMAX) 978 point analysis 625
importing (microwave) 157 power control simulation algorithm 691
modifying (LTE) 1104 preferred carrier, defining for EV-DO Rev. 0 (CDMA) 649
modifying (WiMAX) 978 preferred carrier, defining for EV-DO Rev. A (CDMA) 650
transceiver, properties of (microwave) 157 priority, defining for EV-DO Rev. 0 (CDMA) 649
Equipment Specifications dialogue (CDMA) 608 priority, defining for EV-DO Rev. A (CDMA) 650
Equipment Specifications dialogue (GSM) 248 rate control, using to study capacity (CDMA) 680
Equipment Specifications dialogue (LTE) 1005 rate probabilities UL, defining for EV-DO Rev. 0 (CDMA)
Equipment Specifications dialogue (TD-SCDMA) 730 649
Equipment Specifications dialogue (UMTS) 435 rate probabilities UL, defining for EV-DO Rev. A (CDMA)
650
Equipment Specifications dialogue (WiMAX) 871
equipment, repeater, see "repeater equipment" Rev.0 reverse link data rates 648
Erceg-Greenstein (SUI) propagation model 181 reverse link power control 689
assigning environment formulas 182 reverse link radio bearer index 719
creating environment formula 182 reverse link radio bearer, defining 719
defining default environment formula 182 service area (Eb/Nt) reverse link, studying (CDMA) 656
modifying environment formula 182 service parameters, EV-DO Rev. 0-specific (CDMA) 649
taking diffraction into account 181 service parameters, EV-DO Rev. A-specific (CDMA) 650
EV-DO service parameters, EV-DO-specific (CDMA) 648
acceptable noise rise margin, defining (CDMA) 610 simulation results, cells (CDMA) 697
active set size on reverse link on terminal (CDMA) 653 simulation results, maximum number of channel elements
per carrier (CDMA) 696
application throughput, defining for EV-DO Rev. 0 (CDMA)
649 simulation results, mobiles (CDMA) 699
application throughput, defining for EV-DO Rev. A (CDMA) simulation results, number of channel elements (CDMA)
650 696
BCMCS throughput, defining (CDMA) 611 simulation results, number of channel elements due to
SHO overhead (CDMA) 696
body loss, defining for EV-DO Rev. 0 (CDMA) 650
simulation results, rejected users due to EV-DO resources
body loss, defining for EV-DO Rev. A (CDMA) 650
saturation (CDMA) 697, 701, 702
carrier type, defining globally (CDMA) 717
T_Drop, defining per cell (CDMA) 611
carrier type, defining in cell (CDMA) 609
terminal options, EV-DO Rev. 0-specific (CDMA) 653
carriers, options for (CDMA) 610
terminal options, EV-DO Rev. A-specific (CDMA) 653
data rates, available (CDMA) 717
terminal parameters, EV-DO Rev. 0-specific (CDMA) 652
DRC error rate, defining (CDMA) 610
terminal parameters, EV-DO Rev. A-specific (CDMA) 652
Ec/I0 threshold, defining per cell (CDMA) 611
timeslots dedicated to BCMCS (CDMA) 610
FCH active set size on terminal (CDMA) 653
timeslots dedicated to control channels (CDMA) 610
forward link radio bearer index 718
total transmitted power on DL, defining (CDMA) 611
forward link radio bearer, defining 718
transition flag in traffic simulations, assigned 689
forward link throughput, studying (CDMA) 656
UL load factor, defining (CDMA) 611
handoff status coverage prediction (CDMA) 661
UL throughput due to TCP acknowledgement, defining for
idle power gain, defining (CDMA) 610 EV-DO Rev. 0 (CDMA) 650
max channel elements per carrier, equipment (CDMA) 607 EV-DO Rev. A forward link radio bearer
max number of inter-carrier neighbours, defining (CDMA) defining (CDMA) 718
611
EV-DO Rev. A reverse link radio bearer
max number of inter-technology neighbours, defining
defining (CDMA) 718
(CDMA) 611
exceptional pairs
max number of intra-carrier neighbours, defining (CDMA)
611 neighbour, defining (CDMA) 664
max rate = f/C/1), defining for mobility (CDMA) 651 PN offsets, defining (CDMA) 674
maximum number of users per cell, defining (CDMA) 611 exceptional pairs, defining neighbour (GSM) 295
maximum power transmitted, defining (CDMA) 610 exceptional pairs, defining neighbour (LTE) 1052
maximum UL load factor, defining (CDMA) 611 exceptional pairs, defining neighbour (TD-SCDMA) 798
exceptional pairs, defining neighbour (UMTS) 493
automatically allocating (WiMAX) 930 grid of beams (GOB), creating (TD-SCDMA) 855
displaying allocation (LTE) 1063 grid of beams (GOB), import format (TD-SCDMA) 855
displaying allocation (WiMAX) 931 grid of beams (GOB), importing (TD-SCDMA) 855
displaying on transmitter (LTE) 1064 grouping 65
displaying on transmitter (WiMAX) 932 by a property 65
grouping transmitters by (GSM) 369 by several properties 66
grouping transmitters by (LTE) 1064 examples 67
grouping transmitters by (WiMAX) 932 with subfolders 79
using Search Tool with (LTE) 1063 groups, creating scrambling code (TD-SCDMA) 809
using Search Tool with (WiMAX) 931 groups, creating scrambling code (UMTS) 504
frequencies (TD-SCDMA) GSM/GPRS/EGPRS template 90
allocating automatically 795
displaying on the map 796 H
frequency allocation handoff status
displaying on transmitter (GSM) 369 coverage prediction (CDMA) 661
frequency bands displaying traffic distribution by (CDMA) 693
defining (CDMA) 716 handover status
defining (GSM) 382 displaying traffic distribution by (TD-SCDMA) 833
defining (LTE) 1101 displaying traffic distribution by (UMTS) 525
defining (TD-SCDMA) 730, 852 handover status coverage prediction (UMTS) 487
defining (UMTS) 434, 549 happy bit (UMTS) 522
defining (WiMAX) 971 HCS layers
frequency domains defining (GSM) 385
defining (GSM) 383 selecting (GSM) 248
frequency groups Hexagonal Design
defining (GSM) 383 hiding (CDMA) 613
frequency planning (microwave) 1154, 1157 hexagonal design
frequency, planning (TD-SCDMA) 795 definition (CDMA) 613
definition (GSM) 257
G definition (LTE) 1009
gain definition (TD-SCDMA) 737
defining antenna 143 definition (UMTS) 441
Geo tab 27 definition (WiMAX) 877
global scaling factor (CDMA) 704 histogram
global scaling factor (GSM) 315 PN offsets (CDMA) 678
global scaling factor (LTE) 1092 viewing coverage prediction (CDMA) 642
global scaling factor (TD-SCDMA) 843 histogram, physical cell ID 1068
global scaling factor (UMTS) 537 histogram, preamble index 936
global scaling factor (WiMAX) 962 histogram, scrambling code 509, 814
global transmitter parameters histogram, viewing coverage prediction (GSM) 289
modifying (CDMA) 717 histogram, viewing coverage prediction (LTE) 1032
modifying (LTE) 1103 histogram, viewing coverage prediction (TD-SCDMA) 770
modifying (TD-SCDMA) 854 histogram, viewing coverage prediction (UMTS) 470
modifying (UMTS) 550 histogram, viewing coverage prediction (WiMAX) 900
modifying (WiMAX) 974 hot spot zone
global transmitter parameters (CDMA) 717 creating 43
global transmitter parameters (LTE) 1102 creating (CDMA) 640
global transmitter parameters (TD-SCDMA) 852 creating (GSM) 287
global transmitter parameters (UMTS) 549 creating (LTE) 1030
global transmitter parameters (WiMAX) 972 creating (TD-SCDMA) 768
GPRS/EGPRS coding schemes coverage prediction (GSM) creating (UMTS) 468
355 creating (WiMAX) 898
GPRS/EGPRS equipment explanation 43
coding scheme thresholds, adapting (GSM) 399 explanation (CDMA) 640
coding scheme throughput graphs, displaying (GSM) 399 explanation (GSM) 287
terminals, assigning to (GSM) 399 explanation (TD-SCDMA) 768
transmitters, assigning to (GSM) 398 explanation (UMTS) 468
grid of beams (GOB) smart antenna model (TD-SCDMA) 854 Fit to Map Window 43
MUD, see "multi-user detection" allocating using Neighbours table (CDMA) 671
MUG table allocating using Neighbours table (GSM) 301
defining for EV-DO cells (CDMA) 610 allocating using Neighbours table (LTE) 1058
multi-band network, creating (LTE) 1015 allocating using Neighbours table (TD-SCDMA) 805
multi-band network, creating (WiMAX) 882 allocating using Neighbours table (UMTS) 500
multi-band transmitters allocating using Neighbours table (WiMAX) 926
modelling (GSM) 401 audit of allocation (CDMA) 672
multi-carrier network (CDMA) 609 audit of allocation (GSM) 304
multi-carrier network (TD-SCDMA) 732 audit of allocation (LTE) 1060
multi-carrier network (UMTS) 436 audit of allocation (TD-SCDMA) 807
multi-hop links 1134 audit of allocation (UMTS) 501
adding links to 1136 audit of allocation (WiMAX) 928
creating 1134 defining exceptional pairs of (LTE) 1052
deleting link 1136 defining exceptional pairs of (TD-SCDMA) 798
global properties 1135 defining exceptional pairs of (UMTS) 493
links, mapping to 1136 defining exceptional pairs of (WiMAX) 921
properties 1135 deleting on the map (CDMA) 672
reliability analysis 1154 deleting on the map (GSM) 302
multipoint link, see point-to-multipoint link deleting on the map (LTE) 1059
multi-service traffic data (GSM) 403 deleting on the map (TD-SCDMA) 806
multi-user detection factor deleting on the map (UMTS) 501
defining in site equipment (CDMA) 719 deleting on the map (WiMAX) 927
defining in site equipment (UMTS) 552 deleting per cell (CDMA) 670
defining in terminals (TD-SCDMA) 778 deleting per cell (LTE) 1058
defining in terminals (UMTS) 479 deleting per cell (TD-SCDMA) 804
mult-user environment 93 deleting per cell (UMTS) 499
deleting per cell (WiMAX) 926
N deleting per transmitter (GSM) 300
neighbours deleting using Cells tab of Transmitter Properties (CDMA)
allocating automatically (CDMA) 664 670
allocating automatically (GSM) 295 deleting using Cells tab of Transmitter Properties (LTE)
allocating automatically (LTE) 1053 1058
allocating automatically (TD-SCDMA) 798 deleting using Cells tab of Transmitter Properties (TD-
allocating automatically (UMTS) 493 SCDMA) 804
allocating automatically (WiMAX) 921 deleting using Cells tab of Transmitter Properties (UMTS)
499
allocating on the map (CDMA) 672
deleting using Cells tab of Transmitter Properties (WiMAX)
allocating on the map (GSM) 302
926
allocating on the map (LTE) 1059
deleting using Intra-Technology Neighbours tab of Trans-
allocating on the map (TD-SCDMA) 806 mitter Properties (GSM) 300
allocating on the map (UMTS) 501 deleting using Neighbours table (CDMA) 671
allocating on the map (WiMAX) 927 deleting using Neighbours table (GSM) 301
allocating per cell (CDMA) 670 deleting using Neighbours table (LTE) 1058
allocating per cell (LTE) 1058 deleting using Neighbours table (TD-SCDMA) 805
allocating per cell (TD-SCDMA) 804 deleting using Neighbours table (UMTS) 500
allocating per cell (UMTS) 499 deleting using Neighbours table (WiMAX) 926
allocating per cell (WiMAX) 926 displaying (CDMA) 667
allocating per transmitter (GSM) 300 displaying (GSM) 298
allocating using Cells tab of Transmitter Properties displaying (LTE) 1055
(CDMA) 670
displaying (TD-SCDMA) 801
allocating using Cells tab of Transmitter Properties (LTE)
displaying (UMTS) 497
1058
displaying (WiMAX) 923
allocating using Cells tab of Transmitter Properties (TD-
SCDMA) 804 displaying coverage (CDMA) 669
allocating using Cells tab of Transmitter Properties displaying coverage (LTE) 1057
(UMTS) 499 displaying coverage (TD-SCDMA) 803
allocating using Cells tab of Transmitter Properties displaying coverage (UMTS) 498
(WiMAX) 926 displaying coverage (WiMAX) 925
allocating using Intra-Technology Neighbours tab of Trans- displaying coverage of (GSM) 300
mitter Properties (GSM) 300 exceptional pairs of, defining (CDMA) 664
exceptional pairs of, defining (GSM) 295 assigning environment formulas 177
exporting (CDMA) 673 creating environment formula 178
exporting (GSM) 304 defining default environment formula 177
exporting (LTE) 1061 modifying environment formula 178
exporting (TD-SCDMA) 808 taking diffraction into account 177
exporting (UMTS) 502 optimisation
exporting (WiMAX) 929 creating new ACP process 566
importing (CDMA) 664 creating new co-planning ACP process 567
importing (GSM) 295 defining ACP optimisation 568
importing (LTE) 1052 deleting 588
importing (TD-SCDMA) 804 importing second technology 567
importing (UMTS) 493 properties, changing 588
importing (WiMAX) 920 running 588
possible (CDMA) 663 running ACP process 566
possible (GSM) 294 running saved ACP 586
possible (LTE) 1052 optimum beamformer modelling (TD-SCDMA) 856
possible (TD-SCDMA) 797 optimum beamformer modelling (WiMAX) 983
possible (UMTS) 492 Oracle, connecting to 95
possible (WiMAX) 920 overlapping zones coverage prediction (CDMA) 638
network capacity overlapping zones coverage prediction (GSM) 285
calculating (TD-SCDMA) 816 overlapping zones coverage prediction (LTE) 1027
dimensioning (TD-SCDMA) 818 overlapping zones coverage prediction (UMTS) 466
displaying network load on the map (TD-SCDMA) 819 overlapping zones coverage prediction (WiMAX) 895
displaying on the map (TD-SCDMA) 817, 818 OVSF codes
network, creating dual-band (CDMA) 619 calculation of consumption (TD-SCDMA) 830
network, creating dual-band (TD-SCDMA) 744 calculation of consumption (UMTS) 521
network, creating dual-band (UMTS) 448 default orthogonality factor (UMTS) 549
network, creating multi-band (LTE) 1015 maximum number of codes available for HS-PDSCH (TD-
network, creating multi-band (WiMAX) 882 SCDMA) 734
N-frequency mode (TD-SCDMA) maximum number of codes available for HS-PDSCH
carrier types 795 (UMTS) 438
definition 795 minimum number of codes available for HS-PDSCH (TD-
SCDMA) 734
setting up 795
minimum number of codes available for HS-PDSCH
noise rise threshold, defining for EV-DO cells (CDMA) 610
(UMTS) 438
non-symmetric neighbours, displaying (CDMA) 667
simulations (UMTS) 524
non-symmetric neighbours, displaying (GSM) 298
non-symmetric neighbours, displaying (LTE) 1055 P
non-symmetric neighbours, displaying (TD-SCDMA) 801 packet throughput per timeslot coverage prediction (GSM) 357
non-symmetric neighbours, displaying (UMTS) 497 Page Setup, see "printing"
non-symmetric neighbours, displaying (WiMAX) 923 Panoramic window 26, 39
passive microwave repeaters
O
creating 1132
objects
Path loss calculation 175, 176
changing transparency 35
Radial 175, 176
deleting 29
Systematic 175, 176
displaying 28
path loss matrices
displaying properties 30
adjusting using CW measurements 191
grouping 65
defining area to be adjusted with measurement data 190
grouping by a property 65
tuning using measurement data 190
grouping by several properties 66
path loss matrix
grouping, examples 67
calculation process (CDMA) 633
hiding 28
calculation process (GSM) 276
label 35
calculation process (LTE) 1023
tip text 36
calculation process (WiMAX) 891
visibility scale 35
checking validity (CDMA) 630
OFDM, definition (WiMAX) 867
checking validity (GSM) 273
Okumura-Hata model 177, 178
checking validity (LTE) 1020
Okumura-Hata propagation model 177, 178
based on environment of user profiles, creating (UMTS) per user density (GSM) 311
516 per user density (LTE) 1075
based on environment of user profiles, creating (WiMAX) per user density (TD-SCDMA) 826
942 per user density (UMTS) 517
based on environments of user profiles, importing (CDMA) per user density (WiMAX) 943
685
per user profile (GSM) 307
based on environments of user profiles, importing (GSM)
per user profile (UMTS) 513
310
statistics on traffic map based on environment of user
based on environments of user profiles, importing (UMTS)
profiles (CDMA) 686
516
statistics on traffic map based on environment of user
based on environments of user profiles, importing
profiles (GSM) 310
(WiMAX) 942
statistics on traffic map based on environment of user
cumulated traffic, exporting (GSM) 312
profiles (LTE) 1075
cumulated traffic, exporting (LTE) 1077
statistics on traffic map based on environment of user
cumulated traffic, exporting (WiMAX) 945 profiles (TD-SCDMA) 826
data sources (CDMA) 681 statistics on traffic map based on environment of user
data sources (GSM) 305 profiles (UMTS) 516
data sources (LTE) 1069 statistics on traffic map based on environment of user
data sources (TD-SCDMA) 821 profiles (WiMAX) 943
data sources (UMTS) 511 traffic map based on environment of user profiles
data sources (WiMAX) 937 creating (CDMA) 686
exporting cumulated traffic (CDMA) 688 creating (GSM) 310
exporting cumulated traffic (TD-SCDMA) 828 creating (LTE) 1074
exporting cumulated traffic (UMTS) 519 creating (TD-SCDMA) 825
importing traffic map based on densities of user profiles creating (UMTS) 516
(CDMA) 684 creating (WiMAX) 942
importing traffic map based on densities of user profiles statistics on (CDMA) 686
(GSM) 308 statistics on (GSM) 310
importing traffic map based on densities of user profiles statistics on (LTE) 1075
(LTE) 1072
statistics on (TD-SCDMA) 826
importing traffic map based on densities of user profiles
statistics on (UMTS) 516
(TD-SCDMA) 824
statistics on (WiMAX) 943
importing traffic map based on densities of user profiles
(UMTS) 514 traffic map based on environments of user profiles
importing traffic map based on densities of user profiles importing (CDMA) 685
(WiMAX) 941 importing (GSM) 310
importing traffic map per user density (CDMA) 686 importing (UMTS) 516
importing traffic map per user density (GSM) 311 importing (WiMAX) 942
importing traffic map per user density (LTE) 1075 traffic map per user density
importing traffic map per user density (TD-SCDMA) 826 creating (CDMA) 687
importing traffic map per user density (UMTS) 517 creating (GSM) 311
importing traffic map per user density (WIMAX) 943 creating (LTE) 1076
live data, creating from (CDMA) 681 creating (TD-SCDMA) 827
live data, creating from (GSM) 306 creating (UMTS) 518
live data, creating from (LTE) 1070 creating (WiMAX) 944
live data, creating from (TD-SCDMA) 821 traffic maps
live data, creating from (UMTS) 512 ACP, using with 562
live data, creating from (WiMAX) 938 converting 2G (CDMA) 688
marketing-based (CDMA) 682 converting 2G (GSM) 312
marketing-based (LTE) 1071 converting 2G (LTE) 1076
marketing-based (TD-SCDMA) 822 converting 2G (TD-SCDMA) 828
marketing-based (WiMAX) 939 converting 2G (UMTS) 518
per sector (CDMA) 681 converting 2G (WiMAX) 945
per sector (GSM) 306 traffic quality studies, see "quality studies"
per sector (LTE) 1070 traffic simulation algorithm (LTE) 1082
per sector (TD-SCDMA) 821 traffic simulation algorithm (WiMAX) 950
per sector (UMTS) 512 transceiver equipment
per sector (WiMAX) 938 properties of (microwave) 157
per user density (CDMA) 686 transmitter
calculating network capacity (TD-SCDMA) 816
~
version 2.8.0
~
~ AT280_UM_E0
February 2009
~
~
~
~ Head Office
7, rue des Briquetiers
31700 Blagnac - France
Tel: +33 562 747 210
Fax: +33 562 747 211
~ US Office
200 South Wacker Drive - Suite 3100
Chicago, IL 60606 - USA
Tel: +1 312 674 4846
Fax: +1 312 674 4847
~ China Office
Suite 302, 3/F, West Tower,
Jiadu Commercial Building,
No. 66 Jianzhong Road,
Tianhe Hi-Tech Industrial Zone,
Guangzhou, 510665, P. R. of China
Tel: +86 20 8553 8938
Fax: +86 20 8553 8285